All news entries

2017-02-15 Eclipse NeoSCADA™ 0.4.0 released

We are proud to finally announce Eclipse NeoSCADA™ 0.4.0!

The short summary of this release is:

  • Switched to Eclipse Neon and Java 8 as base platform
  • Re-add the IEC 60870 protocol implementation

Also see the New and Noteworthy page in the wiki.

Full article
2016-12-08 Milestone 0.4.0-M5 released

Milestone 0.4.0-M5 features the integration of IEC 60870 and a bit a of refactoring and unit testing around the 60870 server API. While most of the IEC 60870 components were already part of 0.4.0-M4, this finally brings back the 60870 stack which had to be removed in milestone 0.2.0-M10.

This milestone also cleans up a few leftover issues with re-packaging of Eclipse Neon. Everything should be fine now for a release of 0.4.0.

Full article
2016-04-14 Eclipse NeoSCADA™ 0.3.0 released

We are proud to finally announce Eclipse NeoSCADA™ 0.3.0!

Again it took us a quite a bit longer than expected, although this time it was due to scheduling issues. We hope to pick up the pace with the new releases. In a couple of days the first 0.4 milestone will be available, but this will only be of interest at first to people who deploy to RPM based systems.

The 0.3 realease was more or less focused as it turned out to fix a lot of minor issues and improvement of usability in some corners of the system.

So the main improvements are:

  • Improved REST API
  • Upgrade to Mars
  • Systemd support
  • Filesystem watcher based configuration updates
  • Memory/Performance improvements in the HMI

Also see the New and Noteworthy page in the wiki.

Full article
2016-02-02 Eclipse NeoSCADA™ 0.2.2 and 0.3.0-M5 released

First of all there is a maintenance release 0.2.2 of the 0.2.x branche, which fixes two issues of the TLS implementation Eclipse NeoSCADA uses for communication. One issue in the NET/GMPP protocol and the other in the NGP protocol. Both issues were found and reported to us by Lorenzo Nicolodi. Thanks!

For the 0.3.0 branch, which is currently in development, the NGP protocol was also fixed. The NET/GMPP protocol however is deprecated and no longer part of Eclipse NeoSCADA starting with 0.3.x. Also does this milestone contain a few other fixes and improvements.

Full article
2015-11-19 A new name: Eclipse NeoSCADA™

A new name: With release 0.3 Eclipse SCADA will become Eclipse NeoSCADA

In 2013 through the move to the Eclipse foundation, the existing openSCADA project became Eclipse SCADA. Being a very industrial oriented project it naturally has a different audience than most other projects hosted at the Eclipse foundation. The presence there has encouraged new users to try it out, even if they won't use right now. Although industrial customers are traditionally very conservative in their choice of software, and more likely to use systems build by larger corporations, this is changing right now. Eclipse SCADA for instance, is now used in three different projects at E.ON. Projects like Eclipse SCADA are seen as a way to escape vendor lock-in, which has become stronger and more problematic over the past few years. That in turn means, we will see more and more of these approaches, also at the Eclipse Foundation.

Over time sometimes adjustments have to be made. Eclipse SCADA is now on a relatively stable path. That means that the upcoming 0.3 release will not bring a lot new features, but it is focused on improvements and refinements of the existing system. One big change on the other hand is the renaming of Eclipse SCADA to Eclipse NeoSCADA, which became necessary for trademark reasons. It also brings the naming more in line with the naming policy of other Eclipse projects. Since SCADA is a very generic term, NeoSCADA will improve the recognizability as a specific project within and out of the Eclipse foundation.

For now the new name mostly affects the name of the project itself and the infrastructure at the Eclipse foundation. New bundles and packages will get the new name, existing interfaces won't be affected for now. The goal for the 1.0 release, though, is to have all bundles and packages renamed to neoscada. The migration path will be outlined in due time.

Full article
2015-05-11 Eclipse SCADA 0.2.1 released

We released Eclipse SCADA 0.2.1, which provides a few bug fixes to the 0.2.x release cycle of Eclipse SCADA.

Beside a few issues with the configuration tool and a possible login exception a huge performance improvement on the HD server make up the main parts of this release. Read on for more details. Thanks to everybody who helped with this release!

Full article
2015-02-25 Eclipse IoT survey

The Eclipse IoT working group is currently doing a survey about IoT technologies. As member of the Eclipse IoT working group and top level project, we from Eclipse SCADA would kindly ask you to give back a few minutes of your time and answer a few questions. This will help make the IoT world a little bit better. Thanks.

Link to the survey: https://www.surveymonkey.com/s/IoTWG

Full article
2015-01-29 Eclipse SCADA 0.2.0 released

We are proud to finally announce Eclipse SCADA 0.2.0!

It took us a little bit longer than expected, but this was due to the issues with IEC 60870. We had to remove this for the moment and will hopefully provide this in Eclipse SCADA 0.3.0. In the meantime it is available in openSCADA 1.3, also licensed under the EPL.

So the main new features (besides numerous cleanups, fixes and minor enhancements) are:

  • Compatibility with Java 8
  • An enhanced chart
  • An improved test client
  • A greatly improved configuration IDE (wizard, server manager, ...)
  • The rsyslog protocol RELP
  • Preview of Charts and VI process screens in the IDE
  • Reduced deployment footprint

Also see the New and Noteworthy page in the wiki.

Full article
2014-10-31 Milestone 0.2.0-M10 released

The milestone 0.2.0-M10 is a follow up to M9 with the IEC 60870 protocol stack and functionality removed. Hopefully there will be a way to implement IEC standards in the future at the Eclipse Foundation, but for now it was decided to remove the functionality from Eclipse SCADA and host the development at openSCADA.org. It still is licensed under the EPL and will still be available as open source.

On the other hand, this clears the remaining issue before the 0.2.0 release. So with a little bit of luck, the 0.2.0 release will be done before the end of the year.

Full article
2014-10-31 Milestone 0.2.0-M9 released

This milestone release fixes a few issues in the maven repository, provides an easier way to create a ready to run target platform, and of course fixes a few bugs.

There will be at least another milestone release, since the decision was made to remove the IEC 60870 protocol for now. It sill is in this milestone release, but will be removed in the following -M10. However the functionality will be moved over to openSCADA.org, the license will stay EPL and as soon as the legal state of IEC standards is fully understood, the code will, if possible, be moved back to Eclipse SCADA.

On the other side this was the last issue that stood in our way to release 0.2.0, so if all goes well we will have a release in the next few weeks.

Full article
2014-10-17 Industrial IoT @ EclipseCon Europe 2014

Eclipse SCADA will have two talks at the Eclipse Con Europe 2014 in Ludwigsburg. One is about creating an industrial communication infrastructure with Eclipse SCADA.

The other one is a joint effort of eTrice, 4DIAC and Eclipse SCADA to show what IoT looks like in the industrial world.

Full article
2014-10-09 Milestone 0.2.0-M8 released

On the road to the 0.2.0 release we just made another milestone build: 0.2.0-M8. Again the main changes are bug fixes and some cleanups bringing us closer to the final release.

Still there are two enhancements we wanted to add into this milestone. The first one was long overdue, the generation and hosting of the Javadoc Documentation for Eclipse SCADA. So starting with M8 we will have an up to date Javadoc Documentation, which we also can link to. The documentation is an aggregated documentation of the full Eclipse SCADA project, excluding the IDE/Configurator componentns, since these are not intended to be used outside of Eclipse SCADA. However the protocol packages, the utilites, base, chart and core are all available.

And second we added a small package for creating Modbus Slave applications outside of Eclipse SCADA. You can easily start up a new SlaveHost instance and add a few Slave instances. And there you have a custom Modbus Slave Application.

Full article
2014-09-29 Milestone 0.2.0-M7 released

Last week we built the Milestone release 0.2.0-M7 of Eclipse SCADA. While the major changes are in now, we intend to focus on bug fixes in order to head towards the release 0.2.0. The main issue preventing us from releasing 0.2.0 is more a legal issue than a technical one. Hopefully we will resolve this the next few weeks so we can release 0.2.0.

Beside some bug fixes and cleanups, and a few enhancements in the protocols and UI area, we added a nice little feature to the Alarms & Events system. Eclipse SCADA itself has now an implementation of the RELP protocol stack for reliable syslog event transmission over TCP. These events can then be streamed from external syslog servers directly into the Eclipse SCADA Alarms & Events system. And also is it possible to defined state monitors on these events, just like for the HTTP based event source.

Full article
2014-08-29 Wrapup: IoT Top Level Project, Syslog (RELP), SFP, Validation

Again a lot as happened in the last few weeks. So I will try to wrap it all up in a short blog post.

IoT top level project

The most notebable topic migth be the move from the Technology top level project, to the new IoT top level project. With this step we can focus our efforts more on the area of IoT.

Syslog/RELP

The most interesting new feature in Eclipse SCADA is the new Syslog (RELP) protocol stack and the Syslog receiver module for AE. The protocol stack implements the RELP protocol, which can be used to link syslog servers (rsyslog) together. One server can stream events to the other without the possibility to loose messages, thanks to the RELP protocol. Eclipse SCADA now has a native Java implementation of RELP (which can also be used for other purposes) and can receive syslog events from another syslog server. Of course will these events go through the AE injector system so that they can be filtered and monitoring conditions be created from these messages. So now it is not only possible to receive events using HTTP, but also using Syslog.

SFP

Also did we find a little bit of time to bring the first phase of SFP (small footprint protocol) to a more mature state. The intention of SFP is to provide an easy to implement way of small devices to publish their internal values. The server side reference implemenation is done using libevent and is planned to be migrated from openSCADA to Eclipse SCADA in the coming weeks. If all goes according to plan, we will have a first ready-to-run version pretty soon. For the moment it can be found at openSCADA and Ubuntu Launchpad.

EMF Model Validation

The bigger our configuration model gets, the more important validation of the model becomes. Up to now we used a combination of plain Ecore validation methods and the EMF Validation. However EMF Validation caused lots more problems for us than is was worth. So instead we created a very small adapter layer, which allows us to use plain Ecore validation in combination with our new validation framework, which can be easily extended using extension points, having Java classes as way to validate model elements.

Full article
2014-08-08 Milestone release 0.2.0-M6

We proudly announce the milestone release M6 of Eclipse SCADA 0.2.0. This feature fixes a few bugs and adds some new functionality as well.

There are a few enhancements coming from the joint JavaOne 2014 demonstration effort of the IoT working group. First of all we did add initial support for MQTT. MQTT topics can now be used from the parser driver as an input source. This means that the parser system can be used to split, scan, transform values coming in from MQTT topic and then be used inside Eclipse SCADA. The demo system already shows a few working examples. The next steps will be to add triggers based on MQTT (sending out commands) and also exporting all Eclipse SCADA information to MQTT as well.

In order to enhance the demo system we also added a few new features to the visual interface and the detail dialogs. Adding webcam feed and some new graphics primitives.

In order to be prepared for the transition to Luna, we started to perform first tests with Luna. Up to now everything seems fine. As does the transition to full Java 8 support. Finding the right JVM on the target system is now more automatic and can still be influenced by the user when required.

PS: And yes, I really whish I had started the build a minute earlier ;-)

Full article
2014-08-04 Turn on the light

Turning on a light is the Hello World of the hardware world ;-) At least this was the consent of the embedded guys at our last IoT Biergarten event.

So we added a real light to the Eclipse SCADA Demo Setup, just to say "Hello World!".

You can try it for yourself or have a look right here:

Full article
2014-07-30 Wrapup: IoT Biergarten, new feed generator, MQTT

A lot of things happened in the last days, so I would like to wrap it up a little bit.

  • Updated RSS feed generator
  • IoT Biergarten Event
  • Java One Demonstration
  • MQTT

Full article
2014-07-23 Enhance the demo system

In order to show more capabilities of Eclipse SCADA and to bring something to the IoT interoperabitlity effort we enhanced our demo system running on scada.eclipse.org.

We added a few more sensors to the Arduino providing now also Humidity and Temperature. We also changed the light sensor to some Grove pre-build light sensor, but will change that back to the original version of the light sensor, since the new one reaches his maximum value pretty early and does not give a nice curve as the older version.

Also did we include some values that we gather from fortiss Living Lab photovoltaic setup. These values are fetched from a SolarLog and feed into Eclipse SCADA using the enhanced parser driver (exec3). The also get archived in the historical database (HD) in order to create some nice charts.

Beside that also the new demo client provide some enhance functionality, showing a chart in the dashboard, and providing the new values in main screens and detail views. Also the Alarms and Event (AE) module is now running on the client and server, however at the moment there are no monitors configured.

There will be more in the future ;-)

In order to show more capabilities of Eclipse SCADA and to bring something to the IoT interoperabitlity effort we enhanced our demo system running on "scada.eclipse.org". We added a few more sensors to the Arduino providing now also Humidity and Temperature. We also changed the light sensor to some Grove pre-build light sensor, but will change that back to the original version of the light sensor, since the new one reaches his maximum value pretty early and does not give a nice curve as the older version. Also did we include some values that we gather from fortiss Living Lab photovoltaic setup. These values are fetched from a SolarLog and feed into Eclipse SCADA using the enhanced parser driver (exec3). The also get archived in the historical database (HD) in order to create some nice charts. Beside that also the new demo client provide some enhance functionality, showing a chart in the dashboard, and providing the new values in main screens and detail views. Also the Alarms and Event (AE) module is now running on the client and server, however at the moment there are no monitors configured. [Screenshots] There will be more in the future ;-)
Full article
2014-07-21 Milestone 0.2.0-M5

Release 0.2.0-M5 is out and brings in new features and bug fixes. A already describes several of them in a previous blog post.

In addition to what already was described we added the ability to re-use the modbus exporter for a standalone Hive/Driver setup. This is also described in the Eclipse SCADA book.

We also switched the package naming of RPM and DEB files to not include the version numbers of the upstream version in their package name. While there are rules in place which should allow a seamless upgrade, but you never know ;-)

Release 0.2.0-M5 is out and brings in new features and bug fixes. A already describes several of them in a previous blog post. In addition to what already was described we added the ability to re-use the modbus exporter for a standalone Hive/Driver setup. This is also described in the Eclipse SCADA book. We also switched the package naming of RPM and DEB files to not include the version numbers of the upstream version in their package name. While there are rules in place which should allow a seamless upgrade, but you never know ;-)
Full article
2014-07-17 A bunch of new features

While we are moving towards Milestone 4 we added a bunch of new features. A custom SCADA perspective for the IDE, a complete Client Application Wizard, a preview for VI screens, a test server for the IDE and a load of bug fixes and other minor cleanups and improvements.

The Eclipse SCADA Configurator Plugins now brings a custom "SCADA" perspective, which cleans up the mixture of CA, DA, … perspectives in the Eclipse IDE once the configurator was installed. The base for this perspective is the Plugin perspective, but it is enhanced by the Active Servers View, the Connections View and a few more. The preview editor for VI interface screens is also something that was added recently. I allows the live preview of a VI screen in the IDE while editing the model.

Also new in the configurator is the ability to mass change connections, names and types and items. This allows one to prototype with Persistent items for testing and change the type to External in order to connect to the real source of the data. The renaming functionality is a two step approach. In order two mass rename first the set of items is selected, then an expression is entered which will create the new name based on a script and finally, before applying the names, a preview is shown, which allows checking the result.

The most helpful feature added in this milestone might be the possibility to create a full client application project using a wizard. There is also a tutorial in the openSCADA book.

The milestone is planned to be release in the coming week. The changes are all already in the nightly builds.

While we are moving towards Milestone 4 we added a bunch of new features. A custom "SCADA" perspective for the IDE, a complete Client Application Wizard, a preview for VI screens, a test server for the IDE and a load of bug fixes and other minor cleanups and improvements.
Full article
2014-07-01 Releases: 0.1.3 and 0.2.0-M3

Yesterday was quite a busy day, we produced two new builds of Eclipse SCADA – 0.1.3 and 0.2.0-M3.

For the 0.1 series we have a maintenance release (0.1.3) which only fixes bug #438619. So it is a rather small change and only applies when you need the REST interface.

The 0.2 series received a lot more. New features (e.g. IEC 60870, plain Java Debian Package generation), improved functionality (e.g. chart enhancements, configurator tools) and of course some bug fixes and cleanups.

The most notable new addition might be the implementation of the protocol IEC 60870-5-104. It is a from the scratch implementation of the protocol and the application layer on top of it. However the final legal review has not been completed. So the (although unlikely) possibility still exists that the feature might get removed from Eclipse SCADA in the final release of 0.2. If that should happen, it will be migrated to openSCADA, which now works as an addition to Eclipse SCADA (like for the OPC and SNMP interface right now). At the moment data can be exported from Eclipse SCADA and provided to other systems using IEC 60870-5-104, the next step will be to also import data using the protocol for processing in Eclipse SCADA. Of course all the protocol modules can be combined, so right now Eclipse SCADA provides a base for, reading, for example, modbus data and providing it using IEC 60870 to other systems.

The configurator IDE received a few new functions which for example allow to change the type of data sources, by replacing with a different type, or mass-renaming sources, mass-assigning connections.

Java 8 gave us a bit of a headache when it comes to the JavaScript integration. The switch from Rhino to Nashorn changed a lot in the backend and we had to adapt Eclipse SCADA to handle this correctly. For existing configuration projects there might be some manual changes needed, but new configuration projects will create the correct code now to run either using Rhino or Nashhorn, on Java 7 or 8, Oracle or IBM.

A nifty new feature also is the creation of Debian packages (deb) from the configurator IDE using plain Java. In this past this was done by the Debian package builder (debuild), by running it in the background as a command line tool. Now the functionality was re-implemented using plain Java which means it can also run on other platforms. So you can now use the configurator to create Debian configuration packages for Eclipse SCADA on Windows (and of course Mac OS). A nice side effect of this is, that processing the configuration a lot faster by the new Java implementation.

Of course the M3 milestone also contains the enhancements we made for the chart viewer, which we described in the last post. And there are a lot more little changes which did not make it into this post ;-)

Yesterday was quite a busy day, we produced two new builds of Eclipse SCADA – 0.1.3 and 0.2.0-M3. For the 0.1 series we have a maintance release (0.1.3) which only fixes bug #438619. So it is a rather small change and only applies when you need the REST interface. The 0.2 series received a lot more. New features (e.g. IEC60870), improved functionality (e.g. chart enhancements, configurator tools) and of course some bug fixes and cleanups.
Full article
2014-06-04 Enhancing the chart

The last few days we worked a bit on the chart views, and we got a few new features:

  • Legend showing selected values
  • Modify multiple axis at once
  • Live preview in the model editor
  • Many bug fixes

See for yourself…

The last few days we worked a bit on the chart views, and we got a few new features: * Legend showing selected values * Modify multiple axis at once * Live preview in the model editor * Many bug fixes See for yourself…
Full article
2014-05-22 Maintenance release & milestone release

In the last few days we prepared two new releases of Eclipse SCADA. First of all we did a maintanance release for the 0.1.0 series (0.1.2) and second we pushed out the first milestone build of the 0.2 release cycle.

As always the changes are described in their release pages (0.1.0 and 0.2.0).

For the release cycle 0.2 we started to change a few things we learned during the creating of Eclipse SCADA 0.1.0. First of all we will change the directory names on the download area for update sites and repositories from e.g. 0.2.0 to 0.2. For the drops directory it makes sense to have each version in a different directory, but for P2, APT and YUM repositories you only want to have one latest 0.2 URL.

Besides a lot of work in the background on the build system, the major new thing in 0.2.0-M2 is the addition of the S7 (dave) components to the configurator engine. It is now possible to create an S7 PLC configuration using the memory description model, including nested structures. Also did the realtime list of ESAC get a timestamp column. A feature we wanted to add for a long time.

And since the start of the 0.2 release cycle allows us to try out a few new things, we added the "armhf" architecture to our debian deployment packages. The idea is to let the configurator tool create ready-to-run packages for the Raspberry PI, the BeagleBone and whatever ARM platform is out there. The M2 release contains the first few bits for this, the packaged P2 director and the system configuration package. The rest is already underway and should be part of the M3 release.

In the last few days we prepared two new releases of Eclipse SCADA. First of all we did a maintanance release for the 0.1.0 series (0.1.2) and second we pushed out the first milestone build of the 0.2 release cycle.
Full article
2014-05-06 Eclipse SCADA Release 0.1.0

We are proud to announce the 0.1.0 release of the Eclipse SCADA project!

http://www.eclipse.org/eclipsescada/releases/0.1.0/

Although one could infer from the version, that it is a brand new project, this isn’t actually the case. Eclipse SCADA 0.1.0 is essentially the successor of openSCADA 1.1, which is already in production on many sites in Europe and the U.S., running 24/7. The only reason for the renumbering is that in transition to Eclipse we had to reset the version number to something smaller than 1.0. This big step also gave us the chance to reorganize the repositories and sub projects in a more meaningful way. Additionally there was a review of all the source code and its dependencies regarding the legality of their origins involved, which we passed with flying colors.

During the time we of course also developed a lot new features. The most notable changes are:

  • a new extensible configuration IDE
  • REST API
  • enhanced tooling in general
  • new modbus sub-system (master & slave)
  • a lot of small bugfixes
  • switched build from PDE to Maven/Tycho

For a complete list please visit https://wiki.eclipse.org/EclipseSCADA/Release/0.1.0 and https://projects.eclipse.org/projects/technology.eclipsescada/releases/0.1.0/plan

This release is only the first step, for the next version there are already some interesting features in the pipeline:

  • Implementation of protocol IEC 60870-5-104
  • Migration of OPC and SNMP driver from openSCADA to Eclipse SCADA
  • a new, much more flexible and reconfigurable Exec driver

A new project which we will propose in the near future is Project Haystack, a set of clearly defined interfaces for storing and retrieving time series data as well as a storage implementation.

For the roadmap please look at https://wiki.eclipse.org/EclipseSCADA/Roadmap#Release_0.2.0 and https://projects.eclipse.org/projects/technology.eclipsescada/releases/0.2.0/plan.

For more information:

We are proud to announce the 0.1.0 release of the Eclipse SCADA project! http://www.eclipse.org/eclipsescada/releases/0.1.0/ Although one could infer from the version, that it is a brand new project, this isn’t actually the case. Eclipse SCADA 0.1.0 is essentially the successor of openSCADA 1.1, which is already in production on many sites in Europe and the U.S., running 24/7. The only reason for the renumbering is that in transition to Eclipse we had to reset the version number to something smaller than 1.0. This big step also gave us the chance to reorganize the repositories and sub projects in a more meaningful way. Additionally there was a review of all the source code and its dependencies regarding the legality of their origins involved, which we passed with flying colors. During the time we of course also developed a lot new features. The most notable changes are:
Full article
2014-05-02 Release candidate RC2

We just released the second release candidate RC2.

Well in the RC1 we did find some serious issues in the packaging for OpenSUSE and the handling of embedded JavaScript snippets. The JavaScript snippets issue came up when master server components of Eclipse SCADA were used with the IBM Java VM or Java 8 (see bug 433409). It actually was a quick fix to make it work on these virtual machines, so we did not want to delay the fix until after the 0.1.0 release. And since we had to make another build we also fixed some minor things in ESAC.

This intended to be the last stable build before the final release of 0.1.0. This time for real ;-)

We just released the second release candidate RC2. Well in the RC1 we did find some serious issues in the packaging for OpenSUSE and the handling of embedded JavaScript snippets. The JavaScript snippets issue came up when master server components of Eclipse SCADA were used with the IBM Java VM or Java 8 (see bug 433409). It actually was a quick fix to make it work on these virtual machines, so we did not want to delay the fix until after the 0.1.0 release. And since we had to make another build we also fixed some minor things in ESAC. This intended to be the last stable build before the final release of 0.1.0. This time for real ;-)
Full article
2014-04-29 APT repositories are back

Since the RC1 build of 0.1.0 we finally have the APT repositories back. On Debian based systems the Eclipse SCADA packages can be installed using the apt-get command.

In order to add the repositories to your system either add the line (for milestones) to your sources.list file.

dev http://download.eclipse.org/eclipsescada/repos/milestone/0.1.0/apt/ default main

For more information and other ways of adding the repositories see https://wiki.eclipse.org/EclipseSCADA/Installation/APT

Since the RC1 build of 0.1.0 we finally have the APT repositories back. On Debian based systems the Eclipse SCADA packages can be installed using the "apt-get" command. In order to add the repositories to your system either add the line (for milestones) to your "sources.list" file. dev http://download.eclipse.org/eclipsescada/repos/milestone/0.1.0/apt/ default main For more information and other ways of adding the repositories see https://wiki.eclipse.org/EclipseSCADA/Installation/APT
Full article
2014-04-09 Release candidate RC1

We just released the first release candidate RC1.

It is intended to be the last stable build before the final release of 0.1.0 and contains only minor cleanups and fixes.

There will be no more changes to the code, unless we find some serious issues.

We just released the first release candidate RC1. It is intended to be the last stable build before the final release of 0.1.0 and contains only minor cleanups and fixes. There will be no more changes to the code, unless we find some serious issues.
Full article
2014-03-26 Milestone release M5

Nearing the 0.1.0 end of April we pushed out another milestone build (M5) which irons out some issues we had with the previous release.

The focus was on bugfixing and cleaning up stuff as resources and meta data. The plan is to freeze the current state and use it for the final 0.1.0 build. Unless we find some serious issue of course.

So now it is time for us and the Eclipse Staff to do our legal work in order to get out the release.

Nearing the 0.1.0 end of April we pushed out another milestone build (M5) which irons out some issues we had with the previous release.
Full article
2014-03-14 Milestone release M4

On the road to our first 0.1.0 release we did create milestone release 0.1.0-M4.

The most notable additions are the MSI based deployment in the configurator application and the ability to directly use Eclipse SCADA artifacts as a Maven 2 repository, in addition to the already existing P2 repository.

The configurator application can now create deployments for the Windows platform using MSI. Since MSI is all different than RPM or DEB, it is a totally different workflow. Also not all features of the Linux based deployment are available. But it is a good start. All this is based on the WiX Toolset. The configurator created ready to run Ant and WiX build files which can then be processed either locally from the Eclipse IDE or on a separate build server.

In addition to providing P2 repositories, also a plain maven 2 repository is being created. Also see EclipseSCADA/GettingStarted/WithMaven in the wiki. It is a conversion of the P2 artifacts and metadata, but honors some parts of maven 2 repositories. The idea was to easily add Eclipse SCADA to an already existing maven 2 based project. Together with fortiss GmbH we added Eclipse SCADA to their Akka based simulation framework.

In addition to our original schedule we will add an additional (M5) milestone before we perform the final release in the end of April.

On the road to our first 0.1.0 release we did create milestone release 0.1.0-M4. The most notable additions are the MSI based deployment in the configurator application and the ability to directly use Eclipse SCADA artifacts as a Maven 2 repository, in addition to the already existing P2 repository.
Full article
2014-03-12 Creating maven repositories

Eclipse SCADA is built using Tycho. While tycho is based on maven, is does not produce a usable maven repository output if you are using the "manifest first" approach.

In the recent nightly build we started to convert the P2 repository to a maven 2 compatible layout. The output will also be available for the upcoming M4 milestone build.

For more information about the conversion and how to use the repositories see https://wiki.eclipse.org/EclipseSCADA/GettingStarted/WithMaven.

Eclipse SCADA is built using Tycho. While tycho is based on maven, is does not produce a usable maven repository output if you are using the "manifest first" approach. In the recent nightly build we started to convert the P2 repository to a maven 2 compatible layout. The output will also be available for the upcoming M4 milestone build.
Full article
2014-03-06 Common driver MSI package

In order to better support server deployments on the Windows system (bug #428905), we started to provide ready to run common driver packages.

The package is available for 32bit and 64bit Windows installations and actually provide two things. First they install a ready to run common driver setup. Although it is disabled for automatic startup in the service control manager, it can be activated through the windows service layer pretty easily.

Second, it creates a base which can be used for the new MSI deployment system in the configurator application. Since everything works different on Windows, also the workflow is a bit different here. The configurator application allows to create specific deployment packages for each node in the system. But in the case of MSI, these also contain the binaries. This makes the packages a bit bigger and reduced the flexibility a bit, but on the other hand provides a much cleaner setup experience.

The main entry point for more information is the wiki page, which describes not only the common driver installation, but all MSI packages.

In order to better support server deployments on the Windows system (bug #428905), we started to provide "ready to run" common driver packages.
Full article
2014-02-14 Demo System Updated

We were finally able to update the demo system. We are still missing some functionaly from the older version, but at least it is upgraded to the recent integration build of Eclipse SCADA 0.1.0.

The demo systems connects to an driver instance that is running in our office and connects to the Arduino board next to it. On the Arduino board there is a light sensor which provides that current value to the driver. The communication between the arduino ethernet shield and the driver is our custom arduino UDP based protocol, which is polling the arduino for data. The uplink the the demo system is realized using the Eclipse SCADA DA protocol using the NGP protocol stack and an IPv6 TCP connection. It connects the driver with the master server, that is running on a virtual machine at our ISP "in the cloud".

While the value archive server (historian) is already running and values and monitoring events can already be accessed using the Eclipe SCADA Admin Client, the specially configured rich client and the web interface still need some work and need to be upgraded as well. Hopefully we can do this in the next few weeks.

Also see the page DemoSystem in the Eclipse SCADA wiki.

We were finally able to update the demo system. We are still missing some functionaly from the older version, but at least it is upgraded to the recent integration build of Eclipse SCADA 0.1.0.
Full article
2014-02-12 Welcome to the new homepage

Finally we had some time to prepare the new homepage which is now also hosted by the Eclipse Foundation. That also required us to move away from the blog software that we already had on openSCADA, and change it to something new.

So, as a quick start for creating a simple static homepage, we used a combination of EMF and Acceleo for creating some static HTML pages from our custom website model that we defined. There might be lots of other ways, but this one worked too ;-)

On the down side of all this, we lost the ability to have comments for each post in the blog. Since we gathered a lot of spam there as well, this is not so much trouble. Also does the Eclipse SCADA project have its dedicated forum at eclipse.org and its own mailing list. Just see the contacts page of the project information page.

Full article