Version 4DIAC-IDE 0.3 of 4DIAC
Release Notes: The symbol for drawing connections will not be displayed now for the source and target of a selected connection, making reconnection easier for the user. For FORTE exportation, if a file already exists, it is now possible to open it in a merge editor. Instance names now check whether it is a valid "Identifier" according to the IEC 61499 specification. Timeout for the deployment can now be specified in the preferences. The corner dimension of FBs can be specified in the preferences page (a restart of the editor is necessary). The device/delete resource functionality in the "Download Selection" context menu of the elements has been cleaned.
Other releases
Release Notes: This is the the second maintenance release for 1.3, providing a set of bugfixes to 4DIAC-IDE (5) and FORTE (2).
Release Notes: This first maintenance release for 4DIAC 1.3 provides a large set of bugfixes to 4DIAC-IDE (12) and FORTE (2).
Release Notes: This is a combined release of all current 4DIAC projects. The major changes and improvements of 4DIAC-IDE are: simplified support to create boot projects, improvements in subapplication creation and usage, and the first support to monitor FBs inside sub-applications. The major changes and improvements for FORTE are: B&R POWERLINK support, support for constant values at ANY interface elements, and compile-time reduction for modules with a lot of FBs.
Release Notes: This first maintenance release for 4DIAC 1.2 provides a large set of bugfixes to 4DIAC-IDE (11) and FORTE (10).
Release Notes: This is a combined release of all 4DIAC projects. The major changes and improvements in 4DIAC-IDE are: an improved look and feel for FBs and Devices, an extended Type Navigator with drag-and-drop support, and support of visualization of transition order priorities in the ECC editor. The major changes and improvements for FORTE are: support for the control devices Bachmann M1 PLC and KIPR’s CBC robot controller, new serial communication on POSIX and with Lego Mindstorms, Ethernet Powerlink using Open Powerlink, and optimization of monitoring and debugging code.
