...
- I/O tag address is mapped to the Information Object Address, i.e. contains 3 bytes and must be within the interval of 0...16777215.
For better orientation, the I/O tag address may be defined in the form of ByteHI, ByteMIDDLE, ByteLO, i.e. address 1,2,3 is the same as 66051 (1*256*256 + 2*256 + 3). See a note about the IOA address.
The I/O tag with an address starting with %IGNORE will be ignored. - The input I/O tags must have corresponding types (Ai, Ci, Di, Qi) for received ASDU, see table 1.
- For a particular type of output I/O tag (Ao, Dout, Co), it is necessary to set an ASDU type that should be used, see Table 1 and Table 2.
- It is possible to configure one input I/O tag and multiple output I/O tags on the same address, as long as the output I/O tags have different ASDUs. Example:
- I/O tag M1, Di type, address 1,
- I/O tag M2, Dout type, address 1, ASDU 1 (single-point information)
- I/O tag M3, Dout type, address 1, ASDU 45 (single command)
Configuration on partner's side:- I/O tag P1, Dout type, address 1, ASDU 1 (single-point information)
- I/O tag P2, Di type, address 1
Writing into the I/O tag P1 from the partner's side results in a new value written to the I/O tag M1. Writing to the I/O tags M2, M3 results in a new value to the I/O tag P2 on the partner's side.
...