Flexible AC500 Configuration\ \ \ΒΆ
As of Automation_Builder Version 1.1 feature for flexible AC500 configuration is introduced. This feature enables you to use only one Automation_Builder project for multiple different hardware configurations. Especially for product lines with many hardware variants, flexible configuration is a cost and time saving way for AC500 configuration.
Note
Flexible configuration is not supported for CM574-RS/RCOM and SM560 devices.
An Automation_Builder project consists of IEC 61131-3 editor V3 hardware configuration and IEC 61131-3 editor V2 IEC application. Usually, from hardware configuration a *.ccf file is created and downloaded with IEC application to the PLC. Whenever an application is loaded to the PLC firmware, this *.ccf file is evaluated by I/O drivers.
By default, for configuration Config.ccf with FlexConfID 0 is created. When flexible configuration is enabled, Automation_Builder creates one individual *.ccf file for each variant of hardware configuration: Cfg1.ccf with FlexConfID 1, Cfg2.ccf with FlexConfID2 etc. IEC application loads all available *.ccf files to the PLC, however, only one *.ccf file can be analyzed by PLC firmware at a time. The user decides which *.ccf file to be used by activation of the desired file. The active configuration is represented by the FlexConfID.
Note
Maximum number of manageable *.ccf files is limited to 255. FlexConfID 0 is occupied by the default configuration Config.ccf. Cfg0.ccf is not allowed.
Note
Application configuration and hardware configuration are separated but linked via I/O Mapping. Hence, flexible configuration is only operable in combination with an I/O bus. In order to use several hardware configurations with one application configuration I/O Mapping must be identical.
It is currently not possible to have alternative configurations of safety devices in a project with flexible configuration. However, if configuration of the safety devices is equal in all alternative configurations, flexible configuration is operable.