design once use everywhere Framework for Industrial
Automation & Control
4diac @ CPSE Labs Event “Designing for Digital Transformation”
2018-04-03 10:20 Age: 15 days

The European CPSE Labs project supported SMEs and mid-caps to experiment with new technologies like 4diac. On April 19th, together with the Platforms4CPS project, results of the project as well as from the experiments will be presented in Munich.

This is a great chance to see how 4diac has been used in three CPSE Labs experiments, to meet 4diac developers, and to hear about future funding possibilities for similar acitivties. A detailed agenda and registration information can be found at the event’s web-page.

See you there,
The 4diac Team


4diac 1.9.0 Release Candidate 3 Published!
2018-03-27 11:40 release Age: 22 days

In our work on the 4diac 1.9.0 release we finally reached a next step! We handled 20 issues for 4diac-ide and 3 for 4diac-rte. For both we mainly fixed stability and usability issues.

With this release we are behind our planned release date. The main reason for this is that we wanted to wait for the 0.3 release of open62541 so that we can give you an improved OPC UA experience in 4diac. As this release is now available we are now finalizing the formal procedures for Eclipse project releases. This should be finished with in the next weeks so that we finally have the 1.9.0 release in April.

4diac 1.9. RC3 reached now a state where we strongly recommend all 1.8.4 users to migrate now!

Cheers,
The 4diac Team


P.S.: Please also activate the automatic error reporting facility. This really helps us improving 4diac-ide.


4diac 1.9.0 Release Candidate 2 Published!
2018-02-14 08:13 release Age: 63 days

In our work on the 4diac 1.9.0 release we reached a next step! We handled 6 issues for 4diac-ide and 3 for 4diac-rte. For both we mainly fixed stability and usability issues.

With this release we are well on track for the final release on the 1st of March.

Cheers,
The 4diac Team


4diac 1.9.0 Release Candidate 1 Published!
2018-02-06 11:45 release Age: 71 days

In our work on the 4diac 1.9.0 release we reached a next step! We handled 12 issues for 4diac-ide and 1 for forte. For both we mainly fixed stability and usability issues. With this release we are on track for the final release 1. March.

With this release we are well on track for the final release 1. March.

Cheers,
The 4diac Team


4diac 1.9.0 Milestone 3 Released!
2018-01-22 15:25 release Age: 87 days

In our work on the 4diac 1.9.0 release we reached a next major milestone! We handled 24 issues for 4diac-ide and 4 for forte. For both we mainly fixed smaller stability and usability issues.

With this release we are well on track for the final release 1. March.

Cheers,
The 4diac Team


The End is Near!
2018-01-17 20:06 Age: 91 days

Yes, we are entering the final phase for the 1.9.0 release. After nearly two years of hard work consisting of more then 1000 commits handling nearly 190 issues the endeavor of cleaning up the internal structures of 4diac-ide are finally paying of. Therefore we started the end-phase for the release. Our currently planed timeline is as follows:

Further information on the 1.9.0 release can be found here. There you will also find an overview on all issues and their current state.

Cheers,
The 4diac Team


Dynamic Type Load Prototype
2018-01-07 20:06 BaSys4.0 Age: 101 days

As part of the BaSys4.0 project, which receives funding of the Federal Ministry of Education and Research, 4diac has been extended to support dynamic type load. This functionality allows to add new function block types during runtime, which is required for adaptable systems. It also simplifies testing, since the 4diac-rte does not have to be compiled anymore for every new function block or adapter type. The implementation is based on the work Reduction of development time by using scriptable IEC 61499 function blocks in a dynamically loadable type library by Plasch, Hofman, Ebenhofer and Rooker.

The dynamic type load feature has been realized by LUA/LUAJit support. During the deployment of a function block instance, its type is matched with the types supported by the 4diac-rte. In case it is missing, the function block type is converted into lua and sent to the 4diac-rte for type creation. Open issues are collected here. Current features are:

Special thanks to Martin Jobst, who provided the initial contributon for the LUA engine integration, the basic function block type support and the infastructure for adapters. Also many thanks for his support during the extensions for composite function block types and adapter types.

Cheers,
The 4diac Team