MBM 0100 A

MODBUS Protocol
for MiCOM 30 Series
Version 1.0
=>?@ MODBUS Protocol for MiCOM 30
Series
Note
The operating manual for this device gives instructions for its installation, commissioning
and operation. However, the manual cannot cover all conceivable circumstances or
include detailed information on all topics. In the event of questions or specific problems,
do not take any action without proper authorization. Contact the appropriate ALSTOM
technical sales office and request the necessary information.
Any agreements, commitments, and legal relationships and any obligations on the part of
ALSTOM, including settlement of warranties, result solely from the applicable purchase
contract, which is not affected by the contents of this manual.
2 AFSV.12.09160 EN
=>?@ Modbus Protocol for MiCOM 30
Series
1 General 4
1.1 Transactions 4
1.2 Serial Transmission Modes 4
1.2.1 RTU Mode 4
1.2.2 RTU Framing 5
2 Configuring the MODBUS Protocol 6
3 Function Codes 8
3.1 Function Code 01 - Read Coil Status 8
3.2 Function Code 02 - Read Input Status 9
3.3 Function Code 03 - Read Holding Registers 10
3.4 Function Code 04 - Read Input Register 11
3.5 Function Code 05 - Force Single Coil 12
3.6 Function Code 06 - Preset Single Register 13
3.7 Function Code 07 – Read Exception Status 13
3.8 Function Code 08 – Diagnostics 14
3.9 Function Code 16 - Preset Multiple Registers 16
4 Error Handling, Exception Responses 17
5 Reading the Device Status and System
Information 18
5.1 Device Status 18
5.2 System Information Register 18
6 Procedures 19
6.1 Time Synchronization 19
6.2 Event Handling 20
6.2.1 Event Handling for MODBUS Variant
‘ALSTOM’ 20
6.2.2 Event Handling for MODBUS Variant
‘ALSTOM D’ 26
6.3 Transmission of Disturbances and Long-Time
Recorded Data 28
6.3.1 Transmission of Recorded Data for MODBUS
Variant ‘ALSTOM’ 28
6.3.2 Transmission of Recorded Data for MODBUS
Variant ‘ALSTOM D’ 42
6.4 Controlling Switching Devices 44
7 Appendix 46
7.1 Appendix A - MODBUS Register Allocation,
Setting ‘ALSTOM’ 46
7.2 Appendix B - MODBUS Register Allocation,
Setting ‘ALSTOM D’ 48
7.3 Appendix C – MODBUS Registers for Signals
and Measurements According to
IEC 60870-5-103 50
AFSV.12.09160 EN 3
Series
1 General
This document describes the specifics of the MODBUS implementation for MiCOM 30
Series devices. A general description of the MODBUS protocol can be found in the
MODBUS specification.
1.1 Transactions
MODBUS controllers communicate using a master-slave mechanism in which only one

device (the master) can initiate transactions (called queries). The other devices (the
slaves) respond by supplying the requested data to the master, or by taking the action
requested in the query.
The master can address individual slaves, or can initiate a broadcast message to all
slaves. Slaves return a message (called a response) to queries that are addressed to
them individually. No response is made to broadcast queries from the master.
1.2 Serial Transmission Modes
MODBUS can communicate using either of two transmission modes:
o ASCII (American Standard Code for Information Interchange)

o RTU (Remote Terminal Unit).
In the MiCOM 30 Series implementation only RTU mode is supported.
1.2.1 RTU Mode
Coding system 8-bit binary, hexadecimal 0-9, A-F

Two hexadecimal chars in each 8-bit field of the message
Bits per Byte 1 start bit
8 data bits, least significant bit sent first
1 bit for even / odd parity; no bit for no parity
1 stop bit if parity is used; 2 bits if no parity
4 AFSV.12.09160 EN
Series
1.2.2 RTU Framing
START ADDRESS FUNCTION DATA CRC END

CHECK
T1-T2-T3-T4 8 BITS 8 BITS n x 8 BITS 16 BITS T1-T2-T3-T4
START Silent interval of at least 3.5 character times

ADDRESS Address field, slave device addresses 1 - 247, address 0 is used
for broadcast
FUNCTION Function code
DATA Data field, sets of RTU characters, can be nonexistent
CRC CHECK CRC value, 16 bit
END Silent interval of at least 3.5 character times
AFSV.12.09160 EN 5
Series
2 Configuring the MODBUS Protocol
It is important to note that activation and configuration of the MODBUS protocol for
MiCOM 30 Series devices must be done via the local control panel or over the PC
interface. Device data items do not have fixed indices but instead the user may
configure the data items which are to be made available to the MODBUS master by
selecting items from ‘m out of n’ selection tables.
MODBUS register allocation depends on the MODBUS variant selected. The register
allocation for the two variants is as described in Appendix A and B.
The protocol is available on the ‘logical’ common interface 1 (COMM1) only.
Configuration is done in the menu tree branch:
Parameters\Config. parameters\COMM1
The MODBUS protocol must be activated and the device address and parity must be
correctly configured.
The following device parameter is used to select which MODBUS variant is to be used.
C O M M 1 : M O D B U S p r o t . v a r i a n t (003 214)
There are two MODBUS variants:
o ‘ALSTOM’
o ‘ALSTOM D’
The main difference between the two variants is the allocation of the MODBUS
registers (see Appendix A and B).
In the case of MODBUS variant ‘ALSTOM’, the following parameter is used to define
whether automatic event acknowledgement is to be used (see 6.2.1 Event Handling for
MODBUS Variant ‘ALSTOM’):
C O M M 1 : A u t o m . e v e n t c o n f i r m . (003 249)
The following parameter is used to configure the behavior of the device when refreshing
measurement values:
C O M M 1 : D e l t a t ( M O D B U S ) (003 152)
This parameter defines the time in seconds after which measurement values are
refreshed by the protection software in the device. The value of this parameter
should be chosen carefully because changes in the value of a measurement within
the configured time period are not registered.
6 AFSV.12.09160 EN
Series
The information which MiCOM P30 Series devices make available to the MODBUS
protocol can be divided into four groups:
o Binary information with ‘read/write’ attribute

o Binary information with ‘read only’ attribute
o Analog information with ‘read/write’ attribute
o Analog information with ‘read only’ attribute
MODBUS register areas are defined contiguously so that more than one item of
information may be accessed in a single query.
Values in the device data model which are to be made available to the MODBUS
protocol must be configured using the following parameters:
C O M M 1 : R e g . a s g . s e l e c . c m d s (003 210)
This parameter is used to select from an ‘m out of n’ selection table all the binary
commands (read/write) which are to be made available to the MODBUS master.
C O M M 1 : R e g . a s g . s e l e c . s i g . (003 211)
This parameter is used to select from an ‘m out of n’ selection table all the binary
signals (read only) which are to be made available to the MODBUS master.
C O M M 1 : R e g . a s g . s e l . m . v a l . (003 212)
This parameter is used to select from an ‘m out of n’ selection table all the analog
measurements (read only) which are to be made available to the MODBUS master.
C O M M 1 : R e g . a s g . s e l . p a r a m . (003 213)
This parameter is used to select from an ‘m out of n’ selection table all the analog
parameters (read/write) which are to be made available to the MODBUS master.
AFSV.12.09160 EN 7
Series
3 Function Codes
The function code in a request telegram from a MODBUS master is used to specify
whether the information in the slave device is to be read out or written to. It is important
to note that data addressing differs according to which MODBUS variant has been
selected (see 2 Configuring the MODBUS Protocol).
3.1 Function Code 01 - Read Coil Status
Setting ‘ALSTOM’ Function code 01 is used to read binary information with ‘read/write’ or ‘read only’
attribute. A maximum of 1920 items can be read by a single query.
Setting ‘ALSTOM D’ Function code 01 is used to read binary information with ‘read/write’ attribute. A
maximum of 1920 items can be read by a single query.
QUERY RESPONSE
Slave Address xx Slave Address xx
Function 01 Function 01
st
Starting Address Hi Register no. 1 coil Byte Count (Data) Number of data bytes
1
Starting Address Lo minus base register Data 1 Coil status,
No. of Points Hi Number of coils Data 2 starting with
No. of Points Lo ... data 1, bit 0
CRC Lo xx Data n 0 = OFF, 1 = ON
CRC Hi xx CRC Lo xx
CRC Hi xx
1
see Appendix A or B
8 AFSV.12.09160 EN
Series
3.2 Function Code 02 - Read Input Status
Setting ‘ALSTOM’ Function code 02 is used to read binary information with ‘read/write’ or ‘read only’
attribute. A maximum of 1920 items can be read by a single query.
Setting ‘ALSTOM D’ Function code 02 is used to read binary information with ‘read/write’ attribute. A
QUERY RESPONSE
st
1
Starting Address Lo minus base register Data 1 Coil status,
No. of Points Hi Number of coils Data 2 starting with
No. of Points Lo ... data 1, bit 0
CRC Lo xx Data n 0 = OFF, 1 = ON
CRC Hi xx CRC Lo xx
CRC Hi xx
1
see Appendix A or B
AFSV.12.09160 EN 9
Series
3.3 Function Code 03 - Read Holding Registers
Setting ‘ALSTOM’ Function code 03 is used to read binary or analog information with ‘read/write’ or
‘read only’ attribute, or for reading events and recorded data. A maximum of 120 items
of analog information can be read by a single query. When reading binary information,
blocks of n*16 items must be read, where n may be a maximum of 120.
Setting ‘ALSTOM D’ Function code 03 is used to read analog information with ‘read/write’ attribute. A
QUERY RESPONSE
st
1
Starting Address Lo minus base register Data 1 Hi
No. of Points Hi Number of information items Data 1 Lo Contents of registers
No. of Points Lo ...
CRC Lo xx Data n Hi
CRC Hi xx Data n Lo
CRC Lo xx
CRC Hi xx
1
see Appendix A or B
10 AFSV.12.09160 EN
Series
3.4 Function Code 04 - Read Input Register
Setting ‘ALSTOM’ Function code 04 is used to read binary or analog information with ‘read/write’ or
‘read only’ attribute, or for reading events and recorded data. A maximum of 120 items
of analog information can be accessed by a single query. When reading binary
information, blocks of n*16 items must be read, where n may be a maximum of 120.
Setting ‘ALSTOM D’ Function code 04 is used to read analog information with ‘read only’ attribute. A
maximum of 120 items of information can be accessed by a single query. This function
can also be used to read the ’event message registers’ and the ‘recorded data
message registers’.
QUERY RESPONSE
st
Starting Address Hi Register no. 1 coil minus base Byte Count (Data) Number of data bytes
1
register
Starting Address Lo (word address) Data 1 Hi
No. of Points Hi Number of information items Data 1 Lo Contents of registers
CRC Lo xx Data n Hi
CRC Hi xx Data n Lo
CRC Lo xx
CRC Hi xx
1
see Appendix A or B
AFSV.12.09160 EN 11
Series
3.5 Function Code 05 - Force Single Coil
Setting ‘ALSTOM’ Function code 05 is used to write binary information with ‘read/write’ attribute.
Setting ‘ALSTOM D’ Function code 05 is used to write binary information with ‘read/write’ attribute.
QUERY RESPONSE
st st
Coil Address Hi Register no. 1 coil minus base Coil Address Hi Register no. 1 coil
1 2
register minus base register
Coil Address Lo (bit address) Coil Address Lo (bit address)
Force Data Hi 0000 (hex) = OFF Force Data Hi 0000 (hex) = OFF
Force Data Lo FF00 (hex) = ON Force Data Lo FF00 (hex) = ON
CRC Lo xx CRC Lo xx
CRC Hi xx CRC Hi xx
1
see Appendix A or B
2
see Appendix A or B
12 AFSV.12.09160 EN
Series
3.6 Function Code 06 - Preset Single Register
Setting ‘ALSTOM’ Function code 06 is used to write analog information with ‘read/write’ attribute and for
acknowledging event and recorded data transmission.
Setting ‘ALSTOM D’ Function code 06 is used to write analog information with ‘read/write’ attribute. This
function can also be used to write the ‘event command register’, the ’event message
registers’ and the ‘recorded data message registers’.
QUERY RESPONSE
st st
Register Address Hi Register no. 1 coil minus base Register Address Hi Register no. 1 coil
1 2
Register Address Lo (word address) Register Address Lo (word address)
Preset Data Hi xx Preset Data Hi xx
Preset Data Lo xx Preset Data Lo xx
CRC Lo xx CRC Lo xx
CRC Hi xx CRC Hi xx
3.7 Function Code 07 – Read Exception Status
Setting ‘ALSTOM’ Function code 07 is used to read the exception status.

Setting ‘ALSTOM D’ Function code 07 is not supported.
QUERY RESPONSE
CRC Lo xx Coil Data Status
CRC Hi xx CRC Lo xx
CRC Hi xx
1
see Appendix A or B
2
see Appendix A or B
AFSV.12.09160 EN 13
Series
3.8 Function Code 08 – Diagnostics
Setting ‘ALSTOM’ Function code 08 provides a series of diagnostic tests for checking communications
between the master and slave or for checking various internal error conditions in the
slave.
Setting ‘ALSTOM D’ Function code 08 provides a series of diagnostic tests for checking communications
between the master and slave or for checking various internal error conditions in the
slave.
QUERY RESPONSE
Subfunction Hi Subfunction Subfunction Hi Subfunction
Subfunction Lo Subfunction Lo
Data Hi Diagnostic data Data Hi Diagnostic data
Data Lo Data Lo
CRC Lo xx CRC Lo xx
CRC Hi xx CRC Hi xx
14 AFSV.12.09160 EN
Series
Diagnostic Subfunction Codes Used
Code Name Function

(decimal)
00 Return Query Data The data passed in the query data field is to be
returned (looped back) in the response.
01 Restart Communications Option Initialize communication interface, clear all
communication event counters, bring the interface
out of ‘Listen Only Mode’.
04 Force Listen Only Mode Forces the addressed slave to ‘Listen Only Mode’.
All active communication controls are turned off.
Messages or broadcasts are monitored, but no
action will be taken and no response will be sent.
Only the function Restart Communication option
(function code 8, subfunction 1) will be processed.
10 Clear Counters and Diagnostic Reg. Clears all counters.
11 Return Bus Message Count The response data field returns the number of
messages detected by the slave.
12 Return Bus Comm. Error Count The response data field returns the number of CRC
errors encountered by the slave.
13 Return Bus Exception Error Count The response data field returns the number of
MODBUS exception responses returned by the
slave.
14 Return Slave Message Count The response data field returns the number of
messages addressed to the slave or broadcast,
that the slave has processed.
15 Return Slave No Respond Count The response data field returns the number of
messages addressed to the slave for which it
returned no response.
17 Return Slave BUSY Count The response data field returns the number of
messages addressed to the slave for which it
returned a Slave Device Busy.
18 Return Bus Character Overrun Count The response data field returns the number of
messages addressed to the slave that it could not
handle due to a character overrun condition.
AFSV.12.09160 EN 15
Series
3.9 Function Code 16 - Preset Multiple Registers
Setting ‘ALSTOM’ Function code 16 is used for time synchronization.

Setting ‘ALSTOM D’ Function code 16 is used for time synchronization and for issuing commands for
recorded data transfer.
QUERY RESPONSE
st st
Starting Address Hi Register no. 1 coil minus base Starting Address Hi Register no. 1 coil
1 2
Starting Address Lo (word address) Starting Address Lo (word address)
No. of Registers Hi Number of registers No. of Registers Hi Number of registers
No. of Registers Lo No. of Registers Lo
Byte Count xx CRC Lo xx
Data 1 Hi Contents of registers CRC Hi xx
Data 1 Lo
...
Data n Hi Contents of registers
Data n Lo
CRC Lo xx
CRC Hi xx
1
see Appendix A or B
2
see Appendix A or B
16 AFSV.12.09160 EN
Series
4 Error Handling, Exception Responses
One of four possible events can occur as a result of a query from the master:
o If the slave device receives the query without a communication error and can handle
the query normally, it returns a normal response.
o If the slave does not receive the query due to a communication error, no response is
returned.
o If the slave receives the query but detects a communication error (parity or CRC), no
response is returned.
o If the slave receives the query without a communication error, but cannot handle it
(for example if the request is to a non-existent coil or register), the slave returns an
exception response informing the master of the nature of the error.
In exception responses, the slave sets the most-significant bit of the function code to 1.
Master Query and Exception Response
QUERY RESPONSE
Function 0xxx xxxx (binary) Function 1xxx xxxx (binary)
Parameter or Exception Code xx
structure CRC Lo xx
depending on CRC Hi xx
function code
CRC Lo xx
CRC Hi xx
Exception Codes Used
Code Name Meaning

(decimal)
01 Illegal Function The function code received in the query is not an
allowable action for the slave.
02 Illegal Data Address The data address received in the query is not an
allowable address for the slave.
03 Illegal Data Value A value contained in the query is not an allowable
value for the slave.
04 Slave Device Failure The slave has an internal communication error.
06 Slave Device Busy The slave is processing a long duration command.
AFSV.12.09160 EN 17
Series
5 Reading the Device Status and System Information
The device status and system information can be read only if variant ‘ALSTOM’ is
configured.
5.1 Device Status
The MODBUS master uses function code 07 to read the device status.
Bit
7 6 5 4 3 2 1 0 Meaning
x x x x x x x 0 Device is offline.
x x x x x x x 1 Device is online.
x x x x x x 1 x At least one entry in monitoring signal
memory.
x x x x x 1 x x Event(s) present.
x x x x 0 x x x Time synchronization: device is not
synchronized.
x x x x 1 x x x Time synchronization: device is
synchronized.
x x x 1 x x x x Recorded data present.
5.2 System Information Register
The MODBUS master uses function code 03 or 04 to read the system information from
register 01025 (decimal).
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Meaning
x x x 0 x x x x x x x x x x x x Without automatic event
acknowledgement.
x x x 1 x x x x x x x x x x x x With automatic event
acknowledgement.
x x 1 x x x x x x x x x x x x x Event ring buffer overflow.
x 1 x x x x x x x x x x x x x x Recording memory overflow.
18 AFSV.12.09160 EN
Series
6 Procedures
6.1 Time Synchronization
Setting ‘ALSTOM’ The time is kept in four registers in IEC 870-5 CP56Time2a format in reverse order.
Setting ‘ALSTOM D’ The time is kept in four registers in IEC 870-5 CP56Time2a format in reverse order.
Register (decimal)
Register contents ‘ALSTOM’ ‘ALSTOM D’
0000 0000 Year 02049 40001
0000 Month DOW DOM 02050 40002
SU 0 0 Hours IV 0 Minutes 02051 40003
Milliseconds Milliseconds 02052 40004
Note: DOW - Day of week (1: Monday)

DOM - Day of month
SU - Summer time (0: standard time, 1: daylight saving time)
IV - Invalid (0: valid, 1: invalid)
Time synchronization is done according to IEC 60870-5-103.
The MODBUS Master sends the time to the slave(s) using function code 16 (‘Preset
Multiple Registers’). A slave adjusts the time taken from the telegram (taking into
account the elapsed communication and internal processing time) and sets its internal
clock. The newly set time is written to the time synchronization registers so that the
master can check that time synchronization was successful.
Note! All fields must be provided in a time synchronization telegram.
AFSV.12.09160 EN 19
Series
6.2 Event Handling
All MiCOM 30 Series devices have a ring buffer for storing the most recent 100 state
changes (referred to as events). Event transmission is handled differently depending on
the configured MODBUS variant.
6.2.1 Event Handling for MODBUS Variant ‘ALSTOM’
If more events occur than can fit in the ring buffer, the oldest event is overwritten by the
new event. In addition, bit 13 of the system information register (see 5.2 System Infor-
mation Register) is set, and an additional event ‘buffer overflow start’ is generated with
register number and contents of the system information register. When an event has
been read and acknowledged, the event is deleted from the ring buffer, bit 13 of the
system information register is reset and an additional event ‘buffer overflow end’ is
generated with register number and contents of the system information register.
For this MODBUS variant there are two possible modes for event transmission:
o Event transmission without automatic event acknowledgement

o Event transmission with automatic event acknowledgement
The mode can be selected under C O M M 1 : A u t o m . e v e n t c o n f i r m . (003 249).
20 AFSV.12.09160 EN
Series
Event Transmission
without Automatic
Acknowledgement
In this mode the MODBUS master sends a telegram with function code 03 or 04 to read
register 13825 (decimal). The MODBUS slave device returns the oldest event. If the
master receives the event successfully, it sends a telegram with function code 06 to
write to register 01025 (decimal), acknowledging receipt of the event. The slave
responds by echoing the telegram, deletes the event from the ring buffer, and may reset
bit 2 of the device status register (see 5.1 Device Status) and bit 13 of the system
information register (see 5.2 System Information Register) where appropriate. If the
master detects an error during reception of the event, the master may read register
13825 (decimal) again to retrieve the same event. If the slave device has no events to
send, it will respond with an exception response code 04 (see 4 Error Handling,
Exception Responses).
Figure 1 shows the basic logic for event transmission without automatic
acknowledgement:
MODBUS MODBUS
Master Slave
Read Device Status
optional
Send Device Status, bit 2 = 1
Read Event
Send Event
Send Event Acknowledgement
Confirm Event Acknowledgement
1 Logic for Event Transmission without Automatic Acknowledgement
AFSV.12.09160 EN 21
Series
The following tables show the contents of the telegrams for event transmission without
automatic acknowledgement:
Reading and Sending the Device Status (Event Present)
QUERY RESPONSE
Function Code 07 Function Code 07
CRC Lo xx Coil data Bit 2 = 1
CRC Hi xx CRC Lo xx
CRC Hi xx
Reading and Sending an Event
QUERY RESPONSE
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi 36 (hex) Byte Count (Data) 12 (hex)
Starting Address Lo 00 (hex) Data 1 Hi Event
No. of Points Hi 00 (hex) Data 1 Lo
No. of Points Lo 09 (hex) ...
CRC Lo xx Data 9 Hi
CRC Hi xx Data 9 Lo
CRC Lo xx
CRC Hi xx
Acknowledging an Event
QUERY RESPONSE
Register Address Hi 04 (hex) Register Address Hi 04 (hex)
Register Address Lo 00 (hex) Register Address Lo 00 (hex)
Preset Data Hi 20 (hex) Preset Data Hi 20 (hex)
Preset Data Lo 00 (hex) Preset Data Lo 00 (hex)
CRC Lo xx CRC Lo xx
CRC Hi xx CRC Hi xx
22 AFSV.12.09160 EN
Series
Event Structure
Data 1 Reserved
Data 2 Value
Data 3 Register
Data 4 Reserved
Data 5 Time stamp (inverted CP56Time2a)
Data 6
Data 7
Data 8
Data 9 Reserved
AFSV.12.09160 EN 23
Series
Event Transmission with

Automatic
Acknowledgement
In this mode the MODBUS master sends a telegram with function code 03 or 04 to read
register 13825 (decimal). The MODBUS slave device returns the oldest event. The slave
deletes the event from the ring buffer and may reset bit 2 of the device status register
(see 5.1 Device Status) and bit 13 of the system information register (see 5.2 System
Information Register) where appropriate. If the master detects an error during reception
of the event, the master may read register 13826 (decimal) to retrieve the same event. If
the slave device has no events to send, or if the master reads register 13286 (decimal)
without first reading register 13825 (decimal), the slave will respond with an exception
response code 04 (see 4 Error Handling, Exception Responses).
Figure 2 shows the basic logic for event transmission with automatic acknowledgement:
MODBUS MODBUS
Master Slave
Read Device Status

optional
Read Event
Send Event
2 Logic for Event Transmission with Automatic Acknowledgement
24 AFSV.12.09160 EN
Series
The following tables show the contents of the telegrams for event transmission with
automatic acknowledgement:
Reading and Sending the Device Status (Event Present)
QUERY RESPONSE
CRC Hi xx CRC Lo xx
CRC Hi xx
Reading and Sending an Event
QUERY RESPONSE
Starting Address Lo 00 (hex) / 01 (hex) Data 1 Hi Event
CRC Lo xx Data 9 Hi
CRC Hi xx Data 9 Lo
CRC Lo xx
CRC Hi xx
Event Structure
Data 1 Reserved
Data 2 Value
Data 3 Register
Data 4 Reserved
Data 6
Data 7
Data 8
Data 9 Reserved
AFSV.12.09160 EN 25
Series
6.2.2 Event Handling for MODBUS Variant ‘ALSTOM D’
MODBUS registers are updated when state changes occur. In addition, event telegrams
are generated for all registers in the 0xxxx range, for external device registers, and for
disturbance measurements.
Each event is stored in a ring buffer along with a time stamp. If the ring buffer is full, the
oldest event is overwritten by the new event and the ring buffer overflow is flagged.
Event handling is done using the event command register and the event message
registers.
Event Message Registers
Register content Register Meaning

(decimal)
Number of events 30101 Number of events in the ring buffer
Function code 30102 Hi: default = 0
ring buffer overflow = FF (hex)
Lo: function code depending on register range
Event register number 30103 Register or bit address of the event
Event data 30104 Binary: bit 0 = Information
bits 1 to 15 = 0
Analog: register contents
Year 30105 Event time stamp
Month / Day 30106
Hour / Minute 30107
Milliseconds 30108
Event Command Register

(decimal)
Event command 40005 Event command register
0000 (hex) - Read next event
0001 (hex) - Reread last event
FFFF (hex) - Delete ring buffer
26 AFSV.12.09160 EN
Series
The ‘number of events’ register 30101 (decimal) contains the number of event
telegrams currently stored in the ring buffer. The master can cyclically poll this register to
check for events. Registers 30102 (decimal) to 30108 (decimal) contain the data from
the last event which was read.
The event command is initialized to 0.
When registers 30101 (decimal) to 30108 (decimal) have been read and there is at least
one event present in the ring buffer, the oldest event is copied to these registers and the
number of events is decremented.
The master can reread the previous event by setting the event command register to
0001 (hex). This is useful when a transmission error has occurred.
The master can also reread registers outside the range 30101 (decimal) to 30108
(decimal).
AFSV.12.09160 EN 27
Series
6.3 Transmission of Disturbances and Long-Time Recorded Data
Transmission of recorded data is handled differently depending on the configured

MODBUS variant.
6.3.1 Transmission of Recorded Data for MODBUS Variant ‘ALSTOM’
All MiCOM 30 Series devices have memory for storing analog samples for a maximum
of eight recordings.
There are two possible modes for transmission of recorded data:
o Recorded data upload by column

o File upload
Recorded Data Upload by

Column
Figure 3 shows the basic logic for mode ‘upload by column’:
28 AFSV.12.09160 EN
Series
MODBUS MODBUS
Master Slave
Read Device Status

optional
Send Device Status,bit 4 = 1
Read Recording Information
Send Recording Information
Read Channel 1 Data
Send Channel 1 Data
Read First Block of Samples for Channel 1
Send First Block of Samples for Channel 1
...
...
Read Last Block of Samples for Channel 1
Send Last Block of Samples for Channel 1
...
...
Read Channel 8 Data
Send Channel 8 Data
...
...
Read Last Block of Samples for Channel 8
Send Last Block of Samples for Channel 8
Read Recording Index
Send Recording Index
Send Acknowledgement of Reading of Recording
Confirm Acknowledgement of Reading of Recording
3 Logic for Transmission of Recorded Data in Mode ‘Upload by Column’
AFSV.12.09160 EN 29
Series
The following tables show the contents of the telegrams for mode ‘upload by column’:
Reading and Sending the Device Status (Recorded Data Present)
QUERY RESPONSE
CRC Hi xx CRC Lo xx
CRC Hi xx
Reading and Sending of Recorded Data
QUERY RESPONSE
Starting Address Hi 60 (hex) Byte Count (Data) 0C (hex)
Starting Address Lo 00 (hex) Data 1 Hi
CRC Lo xx Data 6 Hi
CRC Hi xx Data 6 Lo
CRC Lo xx
CRC Hi xx
Structure of Recorded Data
Data 1 Channel information register for channel 1: 24833 (decimal)

Data 2 Recording read acknowledgement register: 01024 (decimal)
Data 3 Number of channels
Data 4 Maximum number of samples per block: 100 (decimal)
Data 5 Register of first block: 25089 (decimal)
Data 6 Register of last block
If the slave device has no events to send, it will respond with an exception response
code 04 (see 4 Error Handling, Exception Responses).
30 AFSV.12.09160 EN
Series
Reading and Sending of the Data for a Channel
QUERY RESPONSE
Starting Address Hi Channel information Byte Count (Data) 1C (hex)
register
Starting Address Lo Data 1 Hi Channel data
No. of Points Lo 0E (hex) ...
CRC Lo xx Data 14 Hi
CRC Hi xx Data 14 Lo
CRC Lo xx
CRC Hi xx
Channel Data
Data 1 Number of samples

Data 2 Number of samples in the pre-fault time
Data 3 Number of samples in the post-fault time
Data 4 Transformation ratio, primary voltage
Data 5 Transformation ratio, secondary voltage
Data 6 Transformation ratio, primary current
Data 7 Transformation ratio, secondary current
Data 8 Internal voltage scaling factor
Data 9 Internal current scaling factor
Data 10 Register of first block of samples
Data 11 Register of last block of samples
Data 12 Number of samples in last block
Data 13 Sampling frequency
Data 14 Channel type
AFSV.12.09160 EN 31
Series
Contents of the ‘Channel Type’ Field (Channel Information Data Item 14)
Value Meaning
1 IA
2 IB
3 IC
4 IN
5 VA-G
6 VB-G
7 VC-G
8 VN-G
If the slave device has no recorded data to send, it will respond with an exception
Reading and Sending a Block of Samples for a Channel
QUERY RESPONSE
Starting Address Hi Block register Byte Count (Data) xx
Starting Address Lo Data 1 Hi Value of sample 1
No. of Points Hi Number of samples in Data 1 Lo
block
CRC Lo xx Data n Hi Value of sample n
CRC Hi xx Data n Lo
CRC Lo xx
CRC Hi xx
When a block of samples for a channel is read, all samples must be read. This means
that the number of samples is always 100. For the last block, the number of samples is
the value in the field ‘number of samples in last block’ (channel information data item
12).
A primary measurement value is calculated by multiplying the value of the sample by the
internal scaling factor of the voltage or current.
32 AFSV.12.09160 EN
Series
Reading and Sending the Recording Index
QUERY RESPONSE
Starting Address Lo 80 (hex) Data 1 Hi Recording index
CRC Lo xx Data 9 Hi
CRC Hi xx Data 9 Lo
CRC Lo xx
CRC Hi xx
Structure of Recording Index
Data 1 Recording number

Data 3
Data 4
Data 5
Data 6 Cause
Data 8 Version number of the conversion tool
Data 9 Revision number of the conversion tool
AFSV.12.09160 EN 33
Series
Sending and Confirming Acknowledgement of Reading of Recording
QUERY RESPONSE
CRC Lo xx CRC Lo xx
CRC Hi xx CRC Hi xx
If no recorded data has been read, the slave will respond with an exception response
34 AFSV.12.09160 EN
Series
File Upload
Figure 4 shows the basic logic for mode ‘file upload’:
MODBUS MODBUS
Master Slave
Read Device Status

optional
Read Header
Send Header
Read Channel Information
Send Channel Information
Read First Block of Samples
Send First Block of Samples
...
...
Read Last Block of Samples
Send Last Block of Samples
Send Acknowledgement of Reading of Recording
Confirm Acknowledgement of Reading of Recording
4 Logic for Transmission of Recorded Data in Mode ‘File Upload’
AFSV.12.09160 EN 35
Series
The following tables show the contents of the telegrams for transmission of recorded
data in mode ‘file upload’:
Reading and Sending the Device Status (Recorded Data Present)
QUERY RESPONSE
CRC Hi xx CRC Lo xx
CRC Hi xx
Reading and Sending of the Header
QUERY RESPONSE
Starting Address Lo 90 (hex) Data 1 Hi Header
CRC Lo xx
CRC Hi xx
36 AFSV.12.09160 EN
Series
Structure of the Header
Data 1 Data transmission type: 00000

Data 2 Number of channel information data items: 36 (decimal)
Data 3
Data 4 Number of samples per channel
Data 5
Data 6 Manufacturer
Data 7 Product designation
Data 8
Data 9 Version number of the transmission mechanism
Data 10 Device serial number
Data 11
Data 12
Data 13
Data 14 Type of transmission: 0003 (hex) = recorded data transmission
Data 16
Data 17
Data 18
Data 19 Reserved
Data 20
Data 21
Data 22
Data 23
Data 24
AFSV.12.09160 EN 37
Series
Reading and Sending of the Channel Information
QUERY RESPONSE
Starting Address Lo B0 (hex) Data 1 Hi Channel information
CRC Lo xx
CRC Hi xx
38 AFSV.12.09160 EN
Series
Structure of the Channel Information
Data 1 Number of channels

Data 2 Type of channel 1
Data 3 Transformation ratio, primary
Data 4 Transformation ratio, secondary
Data 5 Internal scaling factor
Data 35 Recording number
Data 36 Number of samples per channel
AFSV.12.09160 EN 39
Series
Contents of the ‘Channel Type’ Field (Channel Information Data Items 2, 6, 10, 14, 18, 22, 26, 30)
Value Meaning
1 IA
2 IB
3 IC
4 IN
5 VA-G
6 VB-G
7 VC-G
8 VN-G
Reading and Sending a Block of Samples
QUERY RESPONSE
Starting Address Hi Block register Byte Count (Data) xx
Starting Address Lo Data 1 Hi Value of sample 1
No. of Points Hi Number of samples in Data 1 Lo
block
No. of Points Lo Data 2 Hi Value of sample 2
CRC Lo xx Data 2 Lo
CRC Hi xx ... ...
Data n Hi Value of sample n
Data n Lo
CRC Lo xx
CRC Hi xx
When a block of samples for a channel is read, all samples must be read. This means
that the number of samples is always 100, with the exception of the last block which may
have less samples.
40 AFSV.12.09160 EN
Series
Sending and Confirming Acknowledgement of Reading of Recording
QUERY RESPONSE
CRC Lo xx CRC Lo xx
CRC Hi xx CRC Hi xx
If no recorded data has been read, the slave will respond with an exception response
AFSV.12.09160 EN 41
Series
6.3.2 Transmission of Recorded Data for MODBUS Variant ‘ALSTOM D’
All MiCOM 30 Series devices have memory for storing a maximum of eight recordings
with the following data which can be read if MODBUS variant ‘ALSTOM D’ is configured:
o Binary data
o Disturbance measurements
o Analog samples
Transmission of recorded data is done by reading the the disturbance or long-time

recording information from the recorded data registers and by writing the command or
acknowledgement telegrams to the recorded data command registers.
The following registers are used for the transmission of recorded data:
Recorded Data Message Registers
Register content Register

(decimal)
Number of telegrams 30110
Type ID Variable structure ID 30111
Cause of transmission Device address 30112
Function type Information number 30113
30114
Data structure according to
ASDU 23, 26, 27, 28, 29, 30, 31 ...
according to IEC 60870-5-103
30132
Recorded Data Command Register

(decimal)
Command 40006 Transfer command register:
0000 (hex) - Read next telegram
0001 (hex) - Reread previous telegram
FFFF (hex) - Initialize transfer
42 AFSV.12.09160 EN
Series
Recorded Data Order Registers
Register content Register

(decimal)
Type ID Variable structure ID 40007
Cause of transmission Device address 40008
Function type Information number 40009
Type of order Type of recorded data 40010
Recording number Lo Recording number Hi 40011
Channel number 00 40012
The telegrams for information transfer are kept in a ring buffer. The number of
telegrams can be read from register 30110 (decimal). After initialization, the telegram
‘list of recordings’ is present in the ring buffer.
The procedures for reading from the recorded data message registers use the same
mechanisms as the event handling logic, depending on the contents of the recorded
data command register. The next telegram can be read by writing a read command to
registers 30110 (decimal) to 30132 (decimal).
The MODBUS master writes ASDU 24 (‘recorded data transfer order’) and ASDU 25
(‘recorded data transfer acknowledgement’) commands to the recorded data order
registers in IEC 60870-5-103 format.
AFSV.12.09160 EN 43
Series
6.4 Controlling Switching Devices
MiCOM 30 Series devices offer the possibility of controlling switching devices over their
serial interfaces. A register (called an external device register) is defined for each
switching device. The following tables show how these registers are used. It is important
to note that the structure depends on whether variant ‘ALSTOM’ or ‘ALSTOM D’ is
selected.
Structure of the External Device Register for MODBUS Variant ‘ALSTOM’
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Meaning
x x x x x x x x x x x x x 0 0 1 Position: open
x x x x x x x x x x x x x 0 1 0 Position: closed
x x x x x x x x x x x x x 1 0 0 Position: off-end
x x x x x x x x x x x x x 1 1 1 Position: faulty
x x x x x x x x x x x x 0 x x x Local control
x x x x x x x x x x x x 1 x x x Remote control
x x x x x x x x x x x 0 x x x x Unlocked
x x x x x x x x x x x 1 x x x x Locked
x x x x x x x x x x 0 x x x x x Reserved
x x x x x x x x x 0 x x x x x x Reserved
x x x x x x x x 1 x x x x x x x Error: CB running monitor
timeout
x x x x x x x 1 x x x x x x x x Error: target position = actual
position
x x x x x x 0 x x x x x x x x x Reserved
x x x x x 1 x x x x x x x x x x Error: interlocking conditions not
met
x x x x 1 x x x x x x x x x x x Enable command execution
0 0 0 1 x x x x x x x x x x x x Switch command: open
0 0 1 0 x x x x x x x x x x x x Switch command: close
Note: - Bits 0 to 11: binary state information is read only for the master and masked for
write operation.
- Bits 12 to 15: binary state is written by the master. After command execution, the
binary state is cleared.
44 AFSV.12.09160 EN
Series
Structure of the External Device Register for MODBUS Variant ‘ALSTOM D’
Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Meaning
x x x x x x x x x x x x x x 0 0 Position: off-end
x x x x x x x x x x x x x x 0 1 Position: open
x x x x x x x x x x x x x x 1 0 Position: closed
x x x x x x x x x x x 0 0 0 x x External device not present
x x x x x x x x x x x 0 0 1 x x Single signal
x x x x x x x x x x x 0 1 0 x x Double signal
x x x x x x x x x x x 0 1 1 x x Single command
x x x x x x x x x x x 1 0 1 x x Single signal with command
x x x x x x x x x x x 1 1 0 x x Double signal with command
x x x x x x x x x 0 1 x x x x x Signal: local open command
x x x x x x x x x 1 0 x x x x x Signal: local close command
x x x x x x x 0 1 x x x x x x x Command execution enabled
x x x x x x x 1 0 x x x x x x x Command execution disabled
x x x x x 0 1 x x x x x x x x x Command execution
successful
x x x x x 1 0 x x x x x x x x x Command execution aborted
x x x x 1 x x x x x x x x x x x Error: interlocking conditions
not met
0 0 0 1 x x x x x x x x x x x x Switch command: open
0 0 1 0 x x x x x x x x x x x x Switch command: close
Note: - Bits 0 to 11: binary state information is read only for the master and masked for
write operation.
- Bits 12 to 15: binary state is written by the master. After command execution, the
binary state is cleared.
AFSV.12.09160 EN 45
Series
7 Appendix
7.1 Appendix A - MODBUS Register Allocation, Setting ‘ALSTOM’
The following table shows MODBUS register allocation for the ‘ALSTOM’ variant:
Base Register Information in registers Data Type Attribute Used by

register (decimal) function
(decimal) codes
(decimal)
00001 00001 ... 01024 not used /
01025 system information, read only 03 ... 04
acknowledgement of write only 06
events / recorded data
01026 ... 02048 not used /
02049 ... 02052 time synchronization 16
02053 ... 04096 not used
04097 ... 05483 not used binary read only /
05484 ... 06027 single-pole signals in binary read only 01 ... 04
function group SIG_1 in
ascending order
06028 ... 06091 according to m out of n binary read only 01 ... 04
selection ‘COMM1:
Reg.asg. selec. sig.’
(003 211)
06092 ... 06144 according to IEC 60870-5- binary read only 01 ... 04
103 (see Appendix C)
06145 ... 06152 according to IEC 60870-5- binary read/write 01 ... 04,
103 (see Appendix C) 05
06153 ... 06216 according to m out of n binary read/write 01 ... 04,
selection ’COMM1: 05
Reg.asg. selec. cmds’
(003 210)
06217 ... 06488 single-pole commands in binary read/write 05
function group CMD_1 in
ascending order
06489 ... 08192 not used binary write only
08193 ... 13824 not used /
13825 ... 13826 event transmission read only 03 ... 04
13827 ... 16384 not used
16385 ... 18358 not used
18359 ... 18368 according to IEC 60870-5- analog read only 03 ... 04
18369 ... 18432 according to m out of n analog read only 03 ... 04
selection ’COMM1:
Reg.asg. sel. m.val.’
(003 212)
46 AFSV.12.09160 EN
Series

(decimal) codes
(decimal)
00001 18433 ... 18496 according to m out of n analog read/write 03 ... 04,
selection ’COMM1: 06
Reg.asg. sel. param.’
(003 213)
18497 ... 18528 external device registers analog read/write 03 ... 04,
(switching device control) 06
18529 ... 20480 not used analog write only
24576 ... 32767 recorded data
transmission
AFSV.12.09160 EN 47
Series
7.2 Appendix B - MODBUS Register Allocation, Setting ‘ALSTOM D’
The following table shows MODBUS register allocation for the ‘ALSTOM D’ variant:

(decimal) codes
(decimal)
00001 00001 ... 00100 according to IEC 60870-5- binary read/write 01, 05
00101 ... 00300 not used
00301 ... 00400 according to m out of n binary read/write 01, 05
selection ’COMM1:
Reg.asg. selec. cmds’
(003 210)
00401 ... 00800 single-pole commands in binary write only 05
function group CMD_1 in
ascending order
00801 ... 10000 not used
10001 10001 ... 10200 according to IEC 60870-5- binary read only 02
10201 ... 10300 not used
10301 ... 10400 according to m out of n binary read only 02
selection ’COMM1:
Reg.asg. selec. sig.’
(003 211)
10401 ... 10800 status signals from single- binary read only 02
pole commands in function
group CMD_1 in
ascending order
10801 ... 11000 not used
11001 ... 11700 single-pole signals in binary read only 02
function group SIG_1 in
ascending order
11701 ... 30000 not used
30001 30001 ... 30100 according to IEC 60870-5- analog read only 04
30101 ... 30108 event message registers analog read only
30109 not used
30110 ... 30132 recorded data message analog read only 04
registers
30133 ... 30300 not used
48 AFSV.12.09160 EN
Series

(decimal) codes
(decimal)
30001 30301 ... 30400 according to m out of n analog read only 04
selection ’COMM1:
Reg.asg. sel. m.val.’
(003 212)
30401 ... 40000 not used /
40001 40001 ... 40004 time synchronization analog 16
40005 event command register analog 06
40006 recorded data command analog write only 06
register
40007 ... 40012 recorded data order analog write only 16
registers
40013 ... 40100 not used
40101 ... 40300 external device registers Analog read/write 03, 06
(switching device control)
40301 ... 40400 according to m out of n analog read/write 03, 06
selection ’COMM1:
Reg.asg. sel. param.’
(003 213)
AFSV.12.09160 EN 49
Series
7.3 Appendix C – MODBUS Registers for Signals and Measurements According

to IEC 60870-5-103
The following tables show MODBUS register allocation for signals and measurements
according to IEC 60870-5-103:
Measurements According to IEC 60870-5-103
Register according to
configured MODBUS variant
(decimal)
Information in Data Type Attribute ‘ALSTOM’ ‘ALSTOM D’
register
current A analog read only 18359 30001
current B analog read only 18360 30002
current C analog read only 18361 30003
voltage A-G analog read only 18362 30004
voltage B-G analog read only 18363 30005
voltage C-G analog read only 18364 30006
active power P analog read only 18365 30007
reactive power Q analog read only 18366 30008
frequency f analog read only 18367 30009
50 AFSV.12.09160 EN
Series
Signals According to IEC 60870-5-103
(decimal)
IEC Inf.- Information in register Data Type Attribute ‘ALSTOM’ ‘ALSTOM D’
No.
(decimal)
16 Auto-recloser active binary read/write 06145 00017
17 Teleprotection active binary read/write 06146 00018
18 Protection active binary read/write 06147 00019
19 LED reset binary read/write 06148 00020
20 Monitor direction blocked binary read only 06092 10021
21 Test mode binary read only 06093 10022
22 Local parameter setting binary read only 06094 10023
23 Characteristic 1 binary read/write 06149 00024
27 Auxiliary input 1 binary read only 06095 10028
32 Measurand supervision I binary read only 06099 10033
33 Measurand supervision U binary read only 06100 10034
35 Phase sequence binary read only 06101 10036
supervision
36 Trip circuit supervision binary read only 06102 10037
37 I>> back-up operation binary read only 06103 10038
38 VT fuse failure binary read only 06104 10039
39 Teleprotection disturbed binary read only 06105 10040
46 Group warning binary read only 06106 10047
47 Group alarm binary read only 06107 10048
48 Earth fault L1 binary read only 06108 10049
51 Earth fault forward, i.e. line binary read only 06111 10052
52 Earth fault reverse, i.e. binary read only 06112 10053
busbar
AFSV.12.09160 EN 51
Series
(decimal)
No.
(decimal)
64 Star/pick-up L1 binary read only 06113 10065
67 Star/pick-up N binary read only 06116 10068
68 General trip binary read only 06117 10069
69 Trip L1 binary read only 06118 10070
72 Trip I>> (back-up binary read only 06121 10073
operation)
73 Fault location X in ohms analog read only 18368 30074
74 Fault forward/line binary read only 06122 10075
75 Fault reverse/busbar binary read only 06123 10076
76 Teleprotection signal binary read only 06124 10077
transmitted
77 Teleprotection signal binary read only 06125 10078
received
78 Zone 1 binary read only 06126 10079
84 General start/pick-up binary read only 06132 10085
85 Breaker failure binary read only 06133 10086
86 Trip measuring system L1 binary read only 06134 10087
89 Trip measuring system E binary read only 06137 10090
90 Trip I> binary read only 06138 10091
91 Trip I>> binary read only 06139 10092
92 Trip IN> binary read only 06140 10093
93 Trip IN>> binary read only 06141 10094
52 AFSV.12.09160 EN
Series
(decimal)
No.
(decimal)
128 CB ‘on’ by AR binary read only 06142 10129
129 CB ‘on’ by long-time AR binary read only 06143 10130
130 AR blocked binary read only 06144 10131
AFSV.12.09160 EN 53

MBM 0100 A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MBM 0100 A

Uploaded by

Copyright:

Available Formats

MODBUS Protocol

for MiCOM 30 Series

MODBUS controllers communicate using a master-slave mechanism in which only one

1.2 Serial Transmission Modes

MODBUS can communicate using either of two transmission modes:

o ASCII (American Standard Code for Information Interchange)

In the MiCOM 30 Series implementation only RTU mode is supported.

1.2.1 RTU Mode

Coding system 8-bit binary, hexadecimal 0-9, A-F

1.2.2 RTU Framing

START ADDRESS FUNCTION DATA CRC END

START Silent interval of at least 3.5 character times

2 Configuring the MODBUS Protocol

The protocol is available on the ‘logical’ common interface 1 (COMM1) only.

Configuration is done in the menu tree branch:

There are two MODBUS variants:

o Binary information with ‘read/write’ attribute

3.1 Function Code 01 - Read Coil Status

3.2 Function Code 02 - Read Input Status

3.3 Function Code 03 - Read Holding Registers

3.4 Function Code 04 - Read Input Register

3.5 Function Code 05 - Force Single Coil

3.6 Function Code 06 - Preset Single Register

3.7 Function Code 07 – Read Exception Status

Setting ‘ALSTOM’ Function code 07 is used to read the exception status.

3.8 Function Code 08 – Diagnostics

Diagnostic Subfunction Codes Used

Code Name Function

3.9 Function Code 16 - Preset Multiple Registers

Setting ‘ALSTOM’ Function code 16 is used for time synchronization.

4 Error Handling, Exception Responses

Master Query and Exception Response

Exception Codes Used

Code Name Meaning

5 Reading the Device Status and System Information

5.1 Device Status

5.2 System Information Register

6.1 Time Synchronization

Note: DOW - Day of week (1: Monday)

Time synchronization is done according to IEC 60870-5-103.

Note! All fields must be provided in a time synchronization telegram.

6.2 Event Handling

6.2.1 Event Handling for MODBUS Variant ‘ALSTOM’

o Event transmission without automatic event acknowledgement

The mode can be selected under C O M M 1 : A u t o m . e v e n t c o n f i r m . (003 249).

Read Device Status

Send Event Acknowledgement

Confirm Event Acknowledgement

1 Logic for Event Transmission without Automatic Acknowledgement

Reading and Sending the Device Status (Event Present)

Reading and Sending an Event

Event Transmission with

Read Device Status

2 Logic for Event Transmission with Automatic Acknowledgement

Reading and Sending the Device Status (Event Present)

Reading and Sending an Event

6.2.2 Event Handling for MODBUS Variant ‘ALSTOM D’

Event Message Registers

Register content Register Meaning

Event Command Register

Register content Register Meaning

The event command is initialized to 0.

6.3 Transmission of Disturbances and Long-Time Recorded Data