...
- I/O tag address is mapped to the Information object address, i.e. it has 3 bytes and must be within the range of 0..16777215. It can be specified as a decimal number or as a hexadecimal number with a hash at the beginning (e.g. #0A).
The I/O tag with an address starting with %IGNORE will be ignored.
- Input tags must be of particular types (Ai, Ci, Di, Qi) for received ASDU, see table 1 and also table 2 in the balanced mode.
- For a particular type of output tag (Ao, Dout, Co), it is necessary to set an ASDU type, that has to be used, see table 2.
- Archive for providing historical values: if the client asks for historical values through ASDU 250, the server sends:
- the values of the historical value specified by this input entry field,
- if the input entry field is not filled, then the values of the historical value that archives the I/O tag,
- if the specified historical value does not exist, then the values of the I/O tag that archives the control object of the specified I/O tag,
- if the control object does not exist (or the archive is not available), the server returns an error.
Specification of a historical value allows configuring e.g. sending 10-minutes averages instead of sending all changes of given I/O tag. - If the Destination Column is configured, then the values received from the address configured at the I/O tag and above are stored in the corresponding items (e.g. objects with addresses 10, 11, 12 ... according to the number of rows of the destination structure).
Literature
...
- Ver. 1.0 – July 30th, 2003
- Ver. 1.1 – November 19th, 2003: extension of supported ASDU, new parameters
- Ver. 1.2 – March 20th, 2004: added ASDU for reading archive data
- Ver. 1.3 – June 20th, 2004: extension - redundancy support
- Ver. 1.4 – December 1st, 2004: extension - support of balanced mode
- Ver. 1.5 - December 12th, 2012 - updating, TELL commands
- Ver. 1.2 – November 16th, 2023 (support for the Destination Column)
...
{"serverDuration": 130, "requestCorrelationId": "61f35be9b2d20f68"}