Addressing
Monitor ASDUs
To determine the address representing the information object in the monitor direction, use the following template:
The Read=1 specifier affects the request procedure if the Enable Reads parameter of the device is set to True.
The table below lists the possible values for ASDU_TYPE.
The table below lists the possible values for Option.
Note that if the information object contains the timestamp CP56Time2a, it will be used as the timestamp of the tag (taking into account the time zone of the station), otherwise the time ASDU arrival to the server will be used.
It should also be noted that for buffered ASDUs (containing several states of the same information object), the “last” state of the information object will be used as the resulting tag state, but the entire sequence of states will be written to the store (for example, InfluxDB), if such feature is used.
Examples of allowed addresses in the monitor direction:
M_SP.1.COT
M_SP.62.Quality,Read=1
M_SP.40.Timestamp,Read=1
M_SP.1.Value
M_ME_SV.1.Value,Read=1
M_BO.1.Value,Read=1
M_IT.9.Value
M_ME_FV.1.Value
Control ASDUs
To determine the address representing the information object in the control direction, use the following template:
The table below lists the possible values for ASDU_TYPE.
The table below lists the possible values for Option.
The table below lists the possible values for SubOption.
Examples of allowed addresses in the control direction:
C_SC.1.Execute
C_DC.15.Select.ShortPulse
C_DC.1.Select.Timestamp
C_SC.73.Select.ShortPulse.Timestamp
C_SC.1.Select.Persistent
C_SC.3219.Deselect.LongPulse
C_SC.1.Deselect.Persistent
Last updated