Search

SCADA Articles on SCADA World

How To Use the Software Development Kit For Ignition

2010-10-13 10:36:06views: 1005Inductive Automation

How To Use the Software Development Kit For Ignition

The Module SDK is for experienced developers who want to develop modules for Ignition; it is not geared towards beginner users. Proficiency with Java is required and familiarity with Eclipse and Ant are recommended, though you are free to use the IDE and build tools of your choice. The Module SDK is available with the rest of the Ignition downloads at http://www.inductiveautomation.com/downloads. An Ignition module is just a collection of JAR files that can be dynamically loaded and unloaded and an XML descriptor that lets the gateway know how to do so. These files are zipped and given a .modl extension. Vision, SQLBridge and the OPC-UA server that come with Ignition are all simply modules developed using the same APIs that are available in the Module SDK.

There are three different module “scopes”: gateway, client, and designer. These effectively indicate what areas of Ignition your module will be adding to. A module can be more than one scope. The descriptor contains a list of JAR files as well as an indicator into which scope they should be loaded. A JAR file can be loaded into more than one scope as well. The descriptor also indicates your “hook” classes – the entry point(s) into your module. This is the class that will be loaded by the Ignition module system and will manage the life-cycle of your module. Modules can and commonly will have dependencies on other modules. For example, if you are writing a module that provides a driver then you must indicate that you depend on the OPC-UA module being present. If you are adding a Vision component then you rely on the Vision module.

An example of the XML descriptor is available in the sample project.

SDK Contents

The contents of the Module SDK are as follows:

client-api.jar Needed for “client” scope
designer-api.jar Needed for “designer” scope
gateway-api.jar Needed for “gateway” scope

Vision
vis-client-api.jar
vis-designer-api.jar
vis-common.jar

driver-api.jar The API exposed by the OPC-UA module for creating additional drivers.

Setting Up Eclipse

The sample project shows a common way to set up your workspace for module development – a build project, and an additional project for each scope the module will add to, as well as a driver project if the module will add a driver.
To run the sample project you need to:

  • Install Eclipse and choose your workspace.
  • Unzip the sample projects into your workspace.
  • Import the projects via File > Import in Eclipse.

You can open the build.xml file, right-click “BuildAndInstallModule” Ant target, and choose “Run as Ant Build”. This will build the sample module and install it into a running Ignition with a development license installed.

How Licenses Work

Developer licenses can be obtained by filling out the developer license request form at http://www.inductiveautomation.com/developers. Ignition requires that modules be cryptographically signed (by Inductive Automation) before running. During development of a module the presence of a “Developer” license will allow unsigned modules to run.

How To Install And Test Your Module

Developer modules can be installed through the Ignition gateway the same as any other module or they can be be installed using a special developer module-loading servlet that is only running when a developer license is present. The example project contains a simple AntTask (in ant-post-module.jar) that will let you automate the installation of your module during your build process.

Getting Your Module Signed

Getting your module signed is a manual process. All third-party modules must be reviewed approved prior to being signed by Inductive automation. When your module is ready for distribution you can contact developers@inductiveautomation.com to start the review process. This part of the program is still under development. We will be working closely with module developers to ensure the the program is mutually beneficial for everyone involved.

Further Information

The Ignition Module SDK is in beta right now. The API may change. Documentation is being worked on constantly. Right now the best way to get help starting development is to join the forums at http://www.inductiveautomation.com/forum.

Link: http://www.inductiveautomation.com/

SCADA Articles

Using Free Tools To Detect Attacks On SCADA Networks
2015-05-09 14:28:25views: 1864

ICS/SCADA experts say open-source network security monitoring software is a simple and cheap way to catch hackers targeting plant operations. Operators at Natanz nuclear facility in Iran might well have caught Stuxnet before it spread and sabotaged operations at the plant if they had been watching the wires for anomalous network traffic, a pair of ICS/SCADA experts say.

Hackers gain full control of critical SCADA systems
2015-05-09 14:04:07views: 1964

Russian researchers have found vulnerabilities in industrial control systems that they say grant full control of systems running energy, chemical and transportation systems. The vulnerabilities were discovered by researchers who over the last year probed popular and high-end ICS and SCADA systems used to control everything from home solar panel installations to critical national infrastructure.

SCADA Attacks Double in 2014
2015-05-06 07:17:15views: 1731

Annual threat report from Dell Security shows not only a significant surge in the number of attacks on retail credit card systems, but industrial SCADA systems as well, which are much more likely to go unreported.
For Dell to report an annual surge in point-of-sale (POS) attacks aimed at payment card infrastructures might not be such a surprise to people who pay any attention to the news.

The Industrial Software Revolution Begins Now
2013-10-16 11:33:59views: 2311

Invensys is kicking off the conference “The Industrial Software Revolution Begins Now” and underscoring the ‘revolution’ concept with the release of its Wonderware InTouch 2014 and Wonderware System Platform 2014 software.

Integrating Video into HMI/SCADA
2012-06-29 10:19:55views: 2594

The useful integration of video with industrial control systems has been a reality for a few years, but a burst of applications and installations is on the horizon. Cheaper bandwidth, wide availability of Internet protocol (IP) cameras, and greater familiarity with industrial Ethernet networks seem to be driving user interest.

AdvancedHMI - a different approach to HMI development
2012-06-14 10:46:48views: 1857

AdvancedHMI base package is a free software used to build HMIs that display information residing in a PLC. You will find it to be one of the fastest platforms to build an HMI with. The software takes advantage of the Visual Basic .NET development environment so effort is focused on the core software and not reinventing a development environment.

Web Services and SCADA
2012-06-12 23:06:33views: 1414

Web services can be another method for connectivity to SCADA and MES systems. They can retrieve tomorrow's weather, the price of stocks or commodities, the time of sunrise and sunset, and a slew of other publicly-available resources.

SCADA virtualisation with WinCC Version 7
2011-12-21 12:01:11views: 1353

As automation solutions become increasingly complex, it follows that the effort required to maintain both hardware and software will also increase. PCs must be provided with suitable specification and operating systems to support the applications.

Cloud-Based SCADA Systems: The Benefits and Risks
2011-12-20 22:57:31views: 969

Cloud computing is a hot topic. As people become increasingly reliant on accessing important information through the Internet, the idea of storing or displaying vital real-time data in the cloud has become more commonplace. With tech giants like Apple, Microsoft, and Google pushing forward the cloud computing concept, it seems to be more than just a passing trend.

An alternative to DCS or PLC/SCADA
2011-10-04 13:46:22views: 922

Traditionally, users have had a choice between a DCS or a PLC/SCADA approach when selecting a control system for use in process control applications. A key benefit of traditional DCSs was that the suppliers took a ‘systems approach’ and it was designed for large scale applications.