一 4diac IDE ，Open Source PLC Framework forIndustrial Automation & Control

4diac IDE – IEC 61499 Compliant Development Environment

The 4diac IDE is an extensible, IEC 61499 compliant engineering environment for distributed control applications. The modelled applications can be downloaded to distributed field devices according the means defined by the IEC 61499 standard. The hardware capability definition allows to model the control hardware and its interconnections through networks.

The 4diac IDE is based on the Eclipse framework, which allows an easy integration of other plug-ins to the 4diac IDE providing new or extended functionality. IEC 61499 based systems follow an application centric design, which means that the application of the overall system is created at first. Each application is created by interconnecting the desired function blocks (FB) in terms of a function block network (FBN). As soon as the hardware structure is known it can be added to a project's system configuration and the already existing application can be distributed onto the available devices.

The IDE provides the following features:

System Explorer: manage IEC 61499 projects which consist of applications, a system configuration and a project specific type library Application Editor: modelling of IEC 61499 function block networks consisting of the type library's elements Hardware Editor: specification and parameterization of automation hardware by modelling of IEC 61499 devices Type Editors: creation of Basic FBs (BFB), Composite FBs (CFB), Service Interface FBs (SIFB), and Adapters

Distribution Editor: mapping of FBNs or single FBs to the specified resources Deployment: selective download of applications to their corresponding resources Monitoring and Debugging Functionalities: watch and force the values of interface elements as well as trigger events Testing Functionalities: test a single FB on its behavior either by manually setting data values and triggering events within the FBTester editor or by running a list of test cases specified through the service sequences of the specific FB within the FBTest editor