ProSoft Technology MVI56-103M - Manual (Page 108)

Reference MVI56-103M ♦ ControlLogix Platform
User Manual IEC 60870-5-103 Master Communication Module
Page 108 of 152 ProSoft Technology, Inc.
February 22, 2013
The format of each 10-word data region in the block is as follows:
Word Offset Definitions Description
0 Session Index/Sector
Index This field contains the session and sector indices used
to define the controlled unit in the module from which
the event was generated. The MSB contains the
session index and the LSB contains the sector index.
1 ASDU Type This field contains the ASDU type code for the data
contained in the message.
2 Function Code/Point
Index* This field contains the function code and the point index
associated with the event message. The MSB contains
the function code and the LSB contains the point index.
3 Fault Number This is the fault number for the event if applicable. Only
valid for ASDU types 2 and 4.
4 Sec/milliseconds This word contains the seconds and millisecond values
with a range of 0 to 59999 time at which the message
was generated by the slave device.
5 Hr/Min. This word contains the hour and minutes the message
was generated by the slave. The MSB contains the
hour and the LSB contains the minute value.
6 Invalid/DST This word contains two bits that relate to the time value
recorded in the slave device for the message. Bit 0
corresponds to the validity of the time (0=valid,
1=invalid) and Bit 1 defines if daylight savings time is
used in the time (0=no, 1=yes).
7 Relative Time This field contains the relative time value if applicable
to the object. Only valid for ASDU types 2 and 4.
8 to 9 Value This double-word value contains the value for the point
index/function code in the event message. For ASDU
types 1 and 2, this value is only 2 bits wide. For ASDU
type 4, this double-word value contains the floating-
point number (short circuit location).
In order for this feature to be activated, the event pass-through parameter must
be set. When a Master driver receives an event message from a controlled
station, it will build an event message corresponding to the event in the event
buffer of the module. This buffer is then sent to the processor when any
messages are present. Therefore, these blocks are sent to the processor on a
high priority. After the block is sent, the event message is removed from the
module’s event buffer.
If too many events are present in the buffer (>200), the module will set the event
message overflow flag in the error/status data area of the normal read data
block. There is no response block to be received by the module from the
processor.