Depending on the data object type and protocol profile selection, different configuration fields are used in the definitions of different data object mapping items.
Exchangeable CPU Data Object
Located and unlocated variables can be exchanged between the CPU and the RTU module after you have defined and managed the memory map of the CPU to exchange data.
The CPU data objects are mapped and only linked for the RTU module purpose.
Data Exchanging Performance
To sustain a high rate of data exchange, we recommend that you define the RTU memory for data objects in a continuous sequence.
NOTE: For each unlocated variable, configured length cannot exceed 1000 bytes.
Module Behavior After Control Expert Application Transfer
NOTE:
After a Control Expert application transfer, the following behavior occurs:
-
The RTU protocol service is not restarted (it is only restarted if the RTU module IP address has been modified).
-
Depending on the Control Expert application settings, PLC data could be either reset or not.
-
Unexpected new events may occur in case of data reset after download.
If you want the system to behave differently, uncheck the Initialize %MWi on cold start option in the PLC configuration screen of the Control Expert application.
If you want to reset the RTU protocol service, use the menu Reset Communication in the Web site. It is recommended in case of modification of the number of %M or %MW variables in the Control Expert application.
This figure shows the dialog box for configuring the data object mapping for an item with the example data type M_SP for IEC 60870-5-101/104 slave/server:
Data object mapping items can be
exported as a profile in the *.XSY format. Such files can be imported into Control Expert software.
WARNING 
