ProSoft Technology 5201-MNET-101S - Manual (Page 124)

Reference IEC-101 Slave ♦ ProLinx Communication Gateway
Protocol Manual IEC 60870-5-101 v3 Slave (Firmware version 3.xx)
Page 124 of 159 ProSoft Technology, Inc.
August 6, 2010
Each event contains the following data structure:
Start Byte End Byte Data Field(s) Description
0 1 DB Index This is the index for the point in the gateway’s
database. This corresponds to the order of point
definition for the gateway data types. This is not the
point address for the event.
2 2 ASDU This is the ASDU data type for the event message.

1=single point,
 3=double-point,
 5=step,
 9=normalized,
 11=scaled,
 13=short-float
 15=integrated total.
3 3 Qualifier This is the qualifier code for the event message. Refer
to the IEC protocol specification for a full listing of valid
qualifier codes for each ASDU type.
4 5 Year This field contains the four-digit year for the event.
6 6 Month This field contains the month value for the event. Valid
entry for this field is in the range of 1 to 12.
7 7 Day This field contains the day value for the event. Valid
entry for this field is in the range of 1 to 31.
8 8 Hour This field contains the hour value for the event. Valid
entry for this field is in the range of 0 to 23 (bits 0 to 4).
Bit 7 of the byte can be used to set the summer time
flag (0=standard, 1=summer time)
9 9 Minute This field contains the minute value for the event. Valid
entry for this field is in the range of 0 to 59 (bits 0 to 5).
Bit 7 of the byte can be used to set the invalid bit for
the time (0=valid, 1=invalid).
10 11 Seconds &
Milliseconds
This field contains the seconds and milliseconds value
for the event. Valid entry for this field is in the range of
0 to 59,999.
12 15 Data These bytes contain the data for the event. For single-
and double-point, step events, the first byte is used.
For measured value events, the first two bytes are
used. For integrated total and short-float events, all four
bytes are used.