Function Block CI_MOD_CI52x¶
| Firmware | V2.6 |
| Library_File_Name | CI52x_AC500_V26.lib |
| Type | Type_Function_Block_History |
CI_MOD_CI52x function block is to establish the communication between AC500 PLC and communication interface module CI521 or CI522 using this function block, status of the CI52x module configured in the network can be known.
Note
The diagnosis info (CI_MOD_CI52x function block outputs) from CI52x communication interface module can be read out only once, so e.g. the secondary CPU once it was read.
So if change happens in CI52x diagnosis, it is not reflected in secondary CPU, leading to different diagnosis information in Primary and Secondary CPU.
Hence it is recommend to the user that the diagnosis info handled in application program e.g. should be synchronized in a separate structure OR handled e.g. on SCADA side
Attention
For updating the state of inputs and outputs actions of the CI_MOD_CI52x function block must be called:
- Action “ACTION_INPUT_REFRESH” for refreshing the inputs,
- Action “ACTION_OUTPUT_REFRESH” for refreshing the outputs.
Input refresh should be done at the beginning of the task, output refresh at the end.
When there is a different task for the application logic, where the inputs and outputs are read/written it is mandatory that these actions are called from the task which is reading/writing the IO data.
For example, two Tasks: Modbus task and application task. In the Modbus Task the CI_MOD_CI52x function block is called.
The action “ACTION_INPUT_REFRESH” of the function block is called in beginning of the application task. Than all necessary calls for the application logic are done.
At the end of the application task the action “ACTION_OUTPUT_REFRESH” of the function block is called.