Version Version Version Version: : : : MiCOM P30, MODBUS Index Index Index Index: B Release Release Release Release: 08 / 2011 MODBUS Protocol for MiCOM P30 Series Substation Protocols Substation Protocols Substation Protocols Substation Protocols Technical Documentation Technical Documentation Technical Documentation Technical Documentation This document does not replace the Technical Manual
56
Embed
MODBUS Protocol for MiCOM P30 Series - … · MODBUS Protocol for MiCOM P30 Series [ [[ [Substation Protocols ]]]] 3 Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
MODBUS Protocol for MiCOM P30 Series Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols
Technical DocumentationTechnical DocumentationTechnical DocumentationTechnical Documentation This document does not replace the Technical Manual
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]] 3
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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 technical sales office and request the necessary information.
Any agreements, commitments, and legal relationships and any obligations on the part of the manufacturer, including settlement of warranties, result solely from the applicable purchase contract, which is not affected by the contents of this manual.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]] 4
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
CONTENT
1 General 5
1.1 Transactions 5 1.2 Serial Transmission Modes 5
2 Configuring the MODBUS Protocol 7
3 Function Codes 9
3.1 Function Code 01 - Read Coil Status 9 3.2 Function Code 02 - Read Input Status 10 3.3 Function Code 03 - Read Holding Registers 11 3.4 Function Code 04 - Read Input Register 12 3.5 Function Code 05 - Force Single Coil 13 3.6 Function Code 06 - Preset Single Register 14 3.7 Function Code 07 – Read Exception Status 14 3.8 Function Code 08 – Diagnostics 15 3.9 Function Code 16 - Preset Multiple Registers 17
4 Error Handling, Exception Responses 18
5 Reading the Device Status and System Information 19
5.1 Device Status 19 5.2 System Information Register 19
6 Procedures 20
6.1 Time Synchronization 20 6.2 Event Handling 21 6.3 Transmission of Disturbances and Long-Time Recorded Data 29 6.4 Controlling Switching Devices 45
7 Appendix 47
7.1 Appendix A - MODBUS Register Allocation, Setting ‘Compatible’ 47 7.2 Appendix B - MODBUS Register Allocation, Setting ‘Private’ 49 7.3 Appendix C – MODBUS Registers for Signals and Measurements
According to IEC 60870-5-103 51
[[[[Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]] MODBUS Protocol for MiCOM P30 Series 5
Transactions
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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.
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.21.21.21.2 Serial TrSerial TrSerial TrSerial Transmission Modesansmission Modesansmission Modesansmission Modes
MODBUS can communicate using either of two transmission modes:
� ASCII (American Standard Code for Information Interchange)
� 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
6 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Serial Transmission Modes
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
1.2.2 RTU Framing
START ADDRESS FUNCTION DATA CRC CHECK
END
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
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 7
Serial Transmission Modes
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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:
P a r a m e t e r s \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:
� ‘Compatible’
� ‘Private’
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 ‘Compatible’, the following parameter is used to define whether automatic event acknowledgement is to be used (see 6.2.1 Event Handling for MODBUS Variant ‘Compatible’):
C O M M 1 : Au 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.
8 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Serial Transmission Modes
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
The information which MiCOM P30 Series devices make available to the MODBUS protocol can be divided into four groups:
� Binary information with ‘read/write’ attribute
� Binary information with ‘read only’ attribute
� Analog information with ‘read/write’ attribute
� 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.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 9
Function Code 01 - Read Coil Status
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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.13.13.13.1 Function Code 01 Function Code 01 Function Code 01 Function Code 01 ---- Read Coil Status Read Coil Status Read Coil Status Read Coil Status
Setting ‘Compatible’ 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 ‘Private’ 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
Starting Address Hi Register no. 1st coil Byte Count (Data) Number of data bytes
Starting Address Lo minus base register 1 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
10 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Function Code 02 - Read Input Status
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
3.23.23.23.2 FunctionFunctionFunctionFunction CodeCodeCodeCode 02 02 02 02 ---- Read Input Status Read Input Status Read Input Status Read Input Status
Setting ‘Compatible’ 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 ‘Private’ Function code 02 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 02 Function 02
Starting Address Hi Register no. 1st coil Byte Count (Data) Number of data bytes
Starting Address Lo minus base register 2 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
2 see Appendix A or B
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 11
Function Code 03 - Read Holding Registers
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Setting ‘Compatible’ 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 ‘Private’ Function code 03 is used to read analog information with ‘read/write’ attribute. A maximum of 120 items can be read by a single query.
QUERY RESPONSE
Slave Address xx Slave Address xx
Function 03 Function 03
Starting Address Hi Register no. 1st coil Byte Count (Data) Number of data bytes
Starting Address Lo minus base register 3 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
3 see Appendix A or B
12 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Function Code 04 - Read Input Register
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
3.43.43.43.4 Function Code 04 Function Code 04 Function Code 04 Function Code 04 ---- Read Input Register Read Input Register Read Input Register Read Input Register
Setting ‘Compatible’ 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 ‘Private’ 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
Slave Address xx Slave Address xx
Function 04 Function 04
Starting Address Hi Register no. 1st coil minus base
register 4
Byte Count (Data) Number of data bytes
Starting Address Lo (word address) 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
4 see Appendix A or B
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 13
Function Code 05 - Force Single Coil
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
3.53.53.53.5 Function Code 05 Function Code 05 Function Code 05 Function Code 05 ---- Force Single Coil Force Single Coil Force Single Coil Force Single Coil
Setting ‘Compatible’ Function code 05 is used to write binary information with ‘read/write’ attribute.
Setting ‘Private’ Function code 05 is used to write binary information with ‘read/write’ attribute.
QUERY RESPONSE
Slave Address xx Slave Address xx
Function 05 Function 05
Coil Address Hi Register no. 1st coil minus base
register 5
Coil Address Hi Register no. 1st coil
minus base register 6
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
5 see Appendix A or B 6 see Appendix A or B
14 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Function Code 06 - Preset Single Register
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
3.63.63.63.6 Function Code 06 Function Code 06 Function Code 06 Function Code 06 ---- Preset Single Registe Preset Single Registe Preset Single Registe Preset Single Registerrrr
Setting ‘Compatible’ Function code 06 is used to write analog information with ‘read/write’ attribute and for acknowledging event and recorded data transmission.
Setting ‘Private’ 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
Slave Address xx Slave Address xx
Function 06 Function 06
Register Address Hi Register no. 1st coil minus base
register 7 Register Address Hi Register no. 1
st coil
minus base register 8
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.73.73.73.7 Function Code 07 Function Code 07 Function Code 07 Function Code 07 –––– Read Exception Status Read Exception Status Read Exception Status Read Exception Status
Setting ‘Compatible’ Function code 07 is used to read the exception status.
Setting ‘Private’ Function code 07 is not supported.
QUERY RESPONSE
Slave Address xx Slave Address xx
Function 07 Function 07
CRC Lo xx Coil Data Status
CRC Hi xx CRC Lo xx
CRC Hi xx
7 see Appendix A or B 8 see Appendix A or B
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 15
Function Code 08 – Diagnostics
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
3.83.83.83.8 Function Code 08 Function Code 08 Function Code 08 Function Code 08 –––– Diagnostics Diagnostics Diagnostics Diagnostics
Setting ‘Compatible’ 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 ‘Private’ 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
Slave Address xx Slave Address xx
Function 08 Function 08
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
16 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Function Code 08 – Diagnostics
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Diagnostic Subfunction Codes Used
Code (decimal) Name Function
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.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 17
Function Code 16 - Preset Multiple Registers
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
3.93.93.93.9 Function CodeFunction CodeFunction CodeFunction Code 16 16 16 16 ---- Preset Multiple R Preset Multiple R Preset Multiple R Preset Multiple Registersegistersegistersegisters
Setting ‘Compatible’ Function code 16 is used for time synchronization.
Setting ‘Private’ Function code 16 is used for time synchronization and for issuing commands for recorded data transfer.
QUERY RESPONSE
Slave Address xx Slave Address xx
Function 16 Function 16
Starting Address Hi Register no. 1st coil minus base
register 9
Starting Address Hi Register no. 1st coil
minus base register 10
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
9 see Appendix A or B 10 see Appendix A or B
18 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Function Code 16 - Preset Multiple Registers
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
4 Error Handling, Exception Responses
One of four possible events can occur as a result of a query from the master:
� If the slave device receives the query without a communication error and can handle the query normally, it returns a normal response.
� If the slave does not receive the query due to a communication error, no response is returned.
� If the slave receives the query but detects a communication error (parity or CRC), no response is returned.
� 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
Slave Address xx Slave Address xx
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 (decimal) Name Meaning
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.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 19
Device Status
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
5 Reading the Device Status and System Information
The device status and system information can be read only if variant ‘Compatible’ is configured.
5.15.15.15.1 Device StatusDevice StatusDevice StatusDevice 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.25.25.25.2 System InforSystem InforSystem InforSystem Informamamamation Registertion Registertion Registertion 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.
20 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Time Synchronization
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
6 Procedures
6.16.16.16.1 Time SynchronizationTime SynchronizationTime SynchronizationTime Synchronization
Setting ‘Compatible’ The time is kept in four registers in IEC 870-5 CP56Time2a format in reverse order.
Setting ‘Private’ The time is kept in four registers in IEC 870-5 CP56Time2a format in reverse order.
Register (decimal)
Register contents ‘Compatible’ ‘Private’
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.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 21
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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 ‘Compatible’
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:
� Event transmission without automatic event acknowledgement
� Event transmission with automatic event acknowledgement
The mode can be selected under C O M M 1 : Au t o m . e v e n t c o n f i r m . (003 249) .
22 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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:
MODBUSMaster
MODBUSSlave
Read Device Status
Send Device Status, bit 2 = 1
Read Event
Send Event
Send Event Acknowledgement
Confirm Event Acknowledgement
optional
1 Logic for Event Transmission without Automatic Acknowledgement
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 23
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
The following tables show the contents of the telegrams for event transmission without automatic acknowledgement:
Reading and Sending the Device Status (Event Presen t)
QUERY RESPONSE
Slave Address xx Slave Address xx
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
Slave Address xx Slave Address xx
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
Slave Address xx Slave Address xx
Function Code 06 Function Code 06
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
24 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 25
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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:
MODBUSMaster
MODBUSSlave
Read Device Status
Send Device Status, bit 2 = 1
Read Event
Send Event
optional
2 Logic for Event Transmission with Automatic Acknowledgement
26 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
The following tables show the contents of the telegrams for event transmission with automatic acknowledgement:
Reading and Sending the Device Status (Event Presen t)
QUERY RESPONSE
Slave Address xx Slave Address xx
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
Slave Address xx Slave Address xx
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) / 01 (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
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
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 27
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
6.2.2 Event Handling for MODBUS Variant ‘Private’
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 (decimal) Meaning
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
Register content Register (decimal) Meaning
Event command 40005
Event command register
0000 (hex) - Read next event
0001 (hex) - Reread last event
FFFF (hex) - Delete ring buffer
28 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Event Handling
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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).
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 29
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
6.36.36.36.3 Transmission of Transmission of Transmission of Transmission of DisturbancesDisturbancesDisturbancesDisturbances and Long and Long and Long and Long----Time Recorded DataTime Recorded DataTime Recorded DataTime 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 ‘Compatible’
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:
� Recorded data upload by column
� File upload
Recorded Data Upload by Column
Figure 3 shows the basic logic for mode ‘upload by column’:
30 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
MODBUSMaster
MODBUSSlave
Read Device Status
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
Send Acknowledgement of Reading of Recording
Confirm Acknowledgement of Reading of Recording
. . .
. . .
. . .
. . .
. . .
. . .
Read Last Block of Samples for Channel 8
Send Last Block of Samples for Channel 8
Read Recording Index
Send Recording Index
optional
3 Logic for Transmission of Recorded Data in Mode ‘Upload by Column’
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 31
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
The following tables show the contents of the telegrams for mode ‘upload by column’:
Reading and Sending the Device Status (Recorded Dat a Present)
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 07 Function Code 07
CRC Lo xx Coil data Bit 4 = 1
CRC Hi xx CRC Lo xx
CRC Hi xx
Reading and Sending of Recorded Data
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi 60 (hex) Byte Count (Data) 0C (hex)
Starting Address Lo 00 (hex) Data 1 Hi
No. of Points Hi 00 (hex) Data 1 Lo
No. of Points Lo 06 (hex) ...
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).
32 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Reading and Sending of the Data for a Channel
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi Byte Count (Data) 1C (hex)
Starting Address Lo
Channel information register
Data 1 Hi Channel data
No. of Points Hi 00 (hex) Data 1 Lo
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
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 33
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Contents of the ‘Channel Type’ Field (Channel Infor mation 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 response code 04 (see 4 Error Handling, Exception Responses).
Reading and Sending a Block of Samples for a Channe l
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi Byte Count (Data) xx
Starting Address Lo
Block register
Data 1 Hi Value of sample 1
No. of Points Hi Data 1 Lo
No. of Points Lo
Number of samples in 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.
If the slave device has no recorded data to send, it will respond with an exception response code 04 (see 4 Error Handling, Exception Responses).
34 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Reading and Sending the Recording Index
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi 61 (hex) Byte Count (Data) 12 (hex)
Starting Address Lo 80 (hex) Data 1 Hi Recording index
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
Structure of Recording Index
Data 1 Recording number
Data 2 Time stamp (inverted CP56Time2a)
Data 3
Data 4
Data 5
Data 6 Cause
Data 7 Sampling frequency
Data 8 Version number of the conversion tool
Data 9 Revision number of the conversion tool
If the slave device has no recorded data to send, it will respond with an exception response code 04 (see 4 Error Handling, Exception Responses).
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 35
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Sending and Confirming Acknowledgement of Reading o f Recording
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 06 Function Code 06
Register Address Hi 04 (hex) Register Address Hi 04 (hex)
Register Address Lo 00 (hex) Register Address Lo 00 (hex)
Preset Data Hi 10 (hex) Preset Data Hi 10 (hex)
Preset Data Lo 00 (hex) Preset Data Lo 00 (hex)
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 code 04 (see 4 Error Handling, Exception Responses).
36 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
File Upload Figure 4 shows the basic logic for mode ‘file upload’:
MODBUSMaster
MODBUSSlave
Read Device Status
Send Device Status, bit 4 = 1
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
. . .
. . .
optional
4 Logic for Transmission of Recorded Data in Mode ‘File Upload’
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 37
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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 Dat a Present)
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 07 Function Code 07
CRC Lo xx Coil data Bit 4 = 1
CRC Hi xx CRC Lo xx
CRC Hi xx
Reading and Sending of the Header
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi 61 (hex) Byte Count (Data) 30 (hex)
Starting Address Lo 90 (hex) Data 1 Hi Header
No. of Points Hi 00 (hex) Data 1 Lo
No. of Points Lo 18 (hex) ...
CRC Lo xx Data 24 Hi
CRC Hi xx Data 24 Lo
CRC Lo xx
CRC Hi xx
38 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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 15 Time stamp (inverted CP56Time2a)
Data 16
Data 17
Data 18
Data 19 Reserved
Data 20
Data 21
Data 22
Data 23
Data 24
If the slave device has no recorded data to send, it will respond with an exception response code 04 (see 4 Error Handling, Exception Responses).
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 39
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Reading and Sending of the Channel Information
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi 61 (hex) Byte Count (Data) 48 (hex)
Starting Address Lo B0 (hex) Data 1 Hi Channel information
No. of Points Hi 00 (hex) Data 1 Lo
No. of Points Lo 24 (hex) ...
CRC Lo xx Data 36 Hi
CRC Hi xx Data 36 Lo
CRC Lo xx
CRC Hi xx
40 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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 6 Type of channel 2
Data 7 Transformation ratio, primary
Data 8 Transformation ratio, secondary
Data 9 Internal scaling factor
Data 10 Type of channel 3
Data 11 Transformation ratio, primary
Data 12 Transformation ratio, secondary
Data 13 Internal scaling factor
Data 14 Type of channel 4
Data 15 Transformation ratio, primary
Data 16 Transformation ratio, secondary
Data 17 Internal scaling factor
Data 18 Type of channel 5
Data 19 Transformation ratio, primary
Data 20 Transformation ratio, secondary
Data 21 Internal scaling factor
Data 22 Type of channel 6
Data 23 Transformation ratio, primary
Data 24 Transformation ratio, secondary
Data 25 Internal scaling factor
Data 26 Type of channel 7
Data 27 Transformation ratio, primary
Data 28 Transformation ratio, secondary
Data 29 Internal scaling factor
Data 30 Type of channel 8
Data 31 Transformation ratio, primary
Data 32 Transformation ratio, secondary
Data 33 Internal scaling factor
Data 34 Sampling frequency
Data 35 Recording number
Data 36 Number of samples per channel
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 41
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Contents of the ‘Channel Type’ Field (Channel Infor mation 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
If the slave device has no recorded data to send, it will respond with an exception response code 04 (see 4 Error Handling, Exception Responses).
Reading and Sending a Block of Samples
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 03 or 04 Function Code 03 or 04
Starting Address Hi Byte Count (Data) xx
Starting Address Lo
Block register
Data 1 Hi
No. of Points Hi Data 1 Lo
Value of sample 1
No. of Points Lo
Number of samples in block
Data 2 Hi
CRC Lo xx Data 2 Lo
Value of sample 2
CRC Hi xx ... ...
Data n Hi
Data n Lo
Value of sample n
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.
If the slave device has no recorded data to send, it will respond with an exception response code 04 (see 4 Error Handling, Exception Responses).
42 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Sending and Confirming Acknowledgement of Reading o f Recording
QUERY RESPONSE
Slave Address xx Slave Address xx
Function Code 06 Function Code 06
Register Address Hi 04 (hex) Register Address Hi 04 (hex)
Register Address Lo 00 (hex) Register Address Lo 00 (hex)
Preset Data Hi 10 (hex) Preset Data Hi 10 (hex)
Preset Data Lo 00 (hex) Preset Data Lo 00 (hex)
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 code 04 (see 4 Error Handling, Exception Responses).
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 43
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
6.3.2 Transmission of Recorded Data for MODBUS Variant ‘Private’
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 ‘Private’ is configured:
� Binary data
� Disturbance measurements
� 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
Register content Register (decimal) Meaning
Command 40006
Transfer command register:
0000 (hex) - Read next telegram
0001 (hex) - Reread previous telegram
FFFF (hex) - Initialize transfer
44 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Transmission of Disturbances and Long-Time Recorded Data
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 45
Controlling Switching Devices
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
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 ‘Compatible’ or ‘Private’ is selected.
Structure of the External Device Register for MODBU S Variant ‘Compatible’
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.
46 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Controlling Switching Devices
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Structure of the External Device Register for MODBU S Variant ‘Private’
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.
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 47
Appendix A - MODBUS Register Allocation, Setting ‘Compatible’
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
7 Appendix
7.17.17.17.1 Appendix A Appendix A Appendix A Appendix A ---- MODBUS Register Allocation, S MODBUS Register Allocation, S MODBUS Register Allocation, S MODBUS Register Allocation, Setting ‘etting ‘etting ‘etting ‘CompatibleCompatibleCompatibleCompatible’’’’
The following table shows MODBUS register allocation for the ‘Compatible’ variant:
Base register (decimal)
Register (decimal) Information in registers Data Type Attribute
Used by function codes (decimal)
00001 00001 ... 01024 not used /
01025 system information, read only 03 ... 04
acknowledgement of events / recorded data
write only 06
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 function group SIG_1 in ascending order
binary read only 01 ... 04
06028 ... 06091
according to m out of n selection ‘COMM1: Reg.asg. selec. sig.’ (003 211)
binary read only 01 ... 04
06092 ... 06144 according to IEC 60870-5-103 (see Appendix C)
binary read only 01 ... 04
06145 ... 06152 according to IEC 60870-5-103 (see Appendix C) binary read/write
01 ... 04, 05
06153 ... 06216
according to m out of n selection ’COMM1: Reg.asg. selec. cmds’ (003 210)
binary read/write 01 ... 04, 05
06217 ... 06488 single-pole commands in function group CMD_1 in ascending order
binary read/write 05
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-103 (see Appendix C)
analog read only 03 ... 04
18369 ... 18432
according to m out of n selection ’COMM1: Reg.asg. sel. m.val.’ (003 212)
analog read only 03 ... 04
48 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Appendix A - MODBUS Register Allocation, Setting ‘Compatible’
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Base register (decimal)
Register (decimal) Information in registers Data Type Attribute
Used by function codes (decimal)
00001 18433 ... 18496
according to m out of n selection ’COMM1: Reg.asg. sel. param.’ (003 213)
according to m out of n selection ’COMM1: Reg.asg. sel. param.’ (003 213)
analog read/write 03, 06
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 51
Appendix C – MODBUS Registers for Signals and Measurements According to IEC 60870-5-103
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
7.37.37.37.3 AppendixAppendixAppendixAppendix C C C C –––– MODBUS Registers for Signals and Meas MODBUS Registers for Signals and Meas MODBUS Registers for Signals and Meas MODBUS Registers for Signals and Measurements urements urements urements
According to IECAccording to IECAccording to IECAccording to IEC 60870608706087060870----5555----103103103103
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 register Data Type Attribute ‘Compatible’ ‘Private’
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
52 MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]]
Appendix C – MODBUS Registers for Signals and Measurements According to IEC 60870-5-103
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Signals According to IEC 60870-5-103
Register according to configured MODBUS variant (decimal)
IEC Inf.-No. (decimal)
Information in register Data Type
Attribute ‘Compatible’ ‘Private’
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
24 Characteristic 2 binary read/write 06150 00025
25 Characteristic 3 binary read/write 06151 00026
26 Characteristic 4 binary read/write 06152 00027
27 Auxiliary input 1 binary read only 06095 10028
28 Auxiliary input 2 binary read only 06096 10029
29 Auxiliary input 3 binary read only 06097 10030
30 Auxiliary input 4 binary read only 06098 10031
32 Measurand supervision I binary read only 06099 10033
33 Measurand supervision U binary read only 06100 10034
35 Phase sequence supervision
binary read only 06101 10036
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
49 Earth fault L2 binary read only 06109 10050
50 Earth fault L3 binary read only 06110 10051
51 Earth fault forward, i.e. line binary read only 06111 10052
52 Earth fault reverse, i.e. busbar
binary read only 06112 10053
64 Star/pick-up L1 binary read only 06113 10065
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation PrSubstation PrSubstation PrSubstation Protocolsotocolsotocolsotocols]]]] 53
Appendix C – MODBUS Registers for Signals and Measurements According to IEC 60870-5-103
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
Register according to configured MODBUS variant (decimal)
IEC Inf.-No. (decimal)
Information in register Data Type
Attribute ‘Compatible’ ‘Private’
65 Star/pick-up L2 binary read only 06114 10066
66 Star/pick-up L3 binary read only 06115 10067
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
70 Trip L2 binary read only 06119 10071
71 Trip L3 binary read only 06120 10072
72 Trip I>> (back-up operation)
binary read only 06121 10073
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 transmitted
binary read only 06124 10077
77 Teleprotection signal received
binary read only 06125 10078
78 Zone 1 binary read only 06126 10079
79 Zone 2 binary read only 06127 10080
80 Zone 3 binary read only 06128 10081
81 Zone 4 binary read only 06129 10082
82 Zone 5 binary read only 06130 10083
83 Zone 6 binary read only 06131 10084
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
87 Trip measuring system L2 binary read only 06135 10088
88 Trip measuring system L3 binary read only 06136 10089
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
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
54 [[[[Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]] MODBUS Protocol for MiCOM P30 Series
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
[blank page]
MODBUS Protocol for MiCOM P30 Series [ [ [ [Substation ProtocolsSubstation ProtocolsSubstation ProtocolsSubstation Protocols]]]] 55
Mbm0100b.doc Schneider Electric Energy MiCOM P30, MODBUS
[blank page]
Customer CareCustomer CareCustomer CareCustomer Care Centre Centre Centre Centre