Eclipse NeoSCADA 0.2.0

Release Date

The following components will be delivered:

  • OSGi P2 repositories – All java based components will be available as OSGi bundles, contained in P2 repositories.
  • Ready to run applications
    • Admin Client Application (ESAC) – This will be a a read-to-run application which provides administrative and testing access to Eclipse SCADA services.
  • Installation packages
    • Debian based (deb)
    • RedHat based (rpm & yum)
    • Windows (msi)
  • Eclipse Platform Plugins – Components that extend the Eclipse IDE
    • Configurator – This will be an extension to the Eclipse IDE. It will generate configuration artifacts for an easier setup and configuration.



This release should be fully compatible with the Eclipse SCADA release 0.1.0. The OPC and the SNMP driver will need some changes to keep them in line with the other parts of Eclipse SCADA

  • Namespaces of XML files have been changed from to
  • Classes will be prefixed with org.eclipse.scada instead of org.openscada
  • System properties will be prefixed with org.eclipse.scada instead of org.openscada

These are basically the same issues as they were during the original contribution. See also for more information.



The main language will be English. Some components are translated into German.

Target Environments

This release targets the Eclipse Luna Release.

It requires Java 7. And will be compatible with Java 8.

The following operating systems are supported:

  • Linux 32bit/64bit (Ubuntu 12.04+, RHEL 6, CentOS 6, Suse 13.x)
  • Windows 32bit/64bit 7+
  • Mac OS X (User Interface Only)

The software might still run on other operating system variants.


Name Date Description
0.2.0-M1 2013/07/30
0.2.0-M8 2014/10/08

Bug Fixing

No items.
No items.


In electrical engineering and power system automation, the International Electrotechnical Commission 60870 standards define systems used for telecontrol (supervisory control and data acquisition). Such systems are used for controlling electric power transmission grids and other geographically widespread control systems. By use of standardized protocols, equipment from many different suppliers can be made to interoperate. IEC 60870 part 5 provides a communication profile for sending basic telecontrol messages between two systems, which uses permanent directly connected data circuits between the systems. The IEC TC 57 WG3 have developed a protocol standard for telecontrol, teleprotection, and associated telecommunications for electric power systems. The result of this work is IEC 60870-5. We are going to implement a library based on: IEC 60870-5-104 Transmission Protocols, Network access for IEC 60870-5-101 using standard transport profiles
No items.
No items.

Finish openSCADA migration

During the initial contribution there were two important drivers left at the openSCADA project. In both cases it was because of licensing issues that the decision was made to keep them there. Utgard, the library which we implemented for OPC DA 2.0 access, is based on jinterop which was LGPL. This situation has changed as of August 2013, when the license was changed to EPL. Therfore it can now be included in Orbit and Utgard and the OPC driver can be migrated to the Eclipse SCADA project as well. The SNMP driver is based on SNMP4J which is apache licensed. So it should be easy to include it in Orbit and migrate the SNMP driver.
  • Move Utgard from openSCADA to Eclipse SCADA [432251] (target milestone:  ---)
  • Move SNMP driver from openSCADA to Eclipse SCADA [432252] (target milestone:  ---)