NOJA 508 02 Modbus Protocol Implementation
NOJA 508 02 Modbus Protocol Implementation
www.nojapower.com.au
NOJA-508-02
Revision History
Contents
1 INTRODUCTION .......................................................................................................................................... 3
2 MPM FIRMWARE......................................................................................................................................... 3
3 IMPLEMENTATION ..................................................................................................................................... 3
4 TRANSMISSION MODE .............................................................................................................................. 3
5 SUPPORTED FUNCTION CODES.............................................................................................................. 4
5.1 Function 01 Read Coil Status .......................................................................................................... 5
5.2 Function 02 Read Input Status ........................................................................................................ 6
5.3 Function 03 Read Holding Registers............................................................................................ 10
5.4 Function 04 Read Input Registers ................................................................................................ 11
5.5 Function 05 Force Single Coil ....................................................................................................... 16
5.6 Function 06 Preset Single Register .............................................................................................. 16
5.7 Function 15 (0F Hex) Force Multiple Coils ................................................................................... 16
5.8 Function 16 (10 Hex) Preset Multiple Registers .......................................................................... 16
6 MODBUS EXCEPTION RESPONSES ...................................................................................................... 17
NOJA Power® is a registered trademark of NOJA Power Switchgear Pty Ltd. This document is copyright ©
2010 NOJA Power Switchgear Pty Ltd. It contains confidential intellectual property that belongs to NOJA
Power Switchgear Pty Ltd. It does NOT invest any rights to that intellectual property in the recipient. It is
provided solely for limited use by the recipient, who is NOT permitted in any way to copy or to disclose to
any other party, any part of the contents of this document directly or indirectly without the express written
permission of NOJA Power Switchgear Pty Ltd.
NOJA Power Switchgear applies a policy of ongoing development and reserves the right to change product
without notice. NOJA Power Switchgear does not accept any responsibility for loss or damage incurred as a
result of acting or refraining from action based on information in this Document.
1 INTRODUCTION
The MODBUS Protocol is a messaging structure developed by Modicon in 1979, used to establish master-
slave/client-server communication between intelligent devices. It is a de facto standard, truly open and the most
widely used network protocol in the industrial manufacturing environment.
The purpose of this document is to describe the specific implementation of the Modicon Modbus protocol on the
Recloser Control Cubicle RC-01E(S).
This document, in conjunction with the Modicon Modbus Protocol Reference Guide (PI-MBUS-300) and the
MODBUS Application Protocol Specification V1.1, published by Modicon, Inc., provides complete information on
how to communicate with the RC-01ES via Modbus
2 MPM FIRMWARE
This document describes the Modbus points list available in firmware versions S02.03.04-6802 and above.
3 IMPLEMENTATION
The RC-01ES supports the Modbus protocol. Modbus can be assigned to either the RS485 or RS232 port and
supports transmit/receive data rates of 300, 600, 1200, 2400, 4800, 9600, 14400 and 19200 baud. Half-duplex
or full-duplex connections can be used on the RS-485 port. RC-01ES is always slave and supports only RTU
(binary) mode.
Valid slave device addresses are in the range of 0 – 247 decimal. The individual slave devices are assigned
addresses in the range of 1 – 247. A master addresses a slave by placing the slave address in the address field
of the message. When the slave sends its response, it places its own address in this address field of the
response to let the master know which slave is responding.
This Modbus implementation supports broadcast message receiving on address 0.
4 TRANSMISSION MODE
THE RC-01ES supports communication on a Modbus network using RTU (Remote Terminal Unit) mode, each
8–bit byte in a message contains two 4–bit hexadecimal characters. The main advantage of this mode is that its
greater character density allows better data throughput than ASCII for the same baud rate. Each message must
be transmitted in a continuous stream.
Supports format for each byte in RTU mode is:
Coding System:
1 start bit
1 stop bit
Start 1 2 3 4 5 6 7 8 Stop
The listing below shows the function codes supported by this Modbus implementation. Codes are listed in
decimal. ‘Yes’ indicates that the function is supported. ‘No’ indicates that it is not supported.
Closing time (including driver recognition time) exceeds 100ms: within 100ms after
10107 Excessive Tc activation of C(E) control signal PS has not been deactivated. "Excessive Tc" signal
is deactivated when PS is activated or when T(E) control signal is activated.
NOTE 1: Reserved – This coil is always 0. The coil status in the response message is packed as one coil per bit
of the data field. Status is indicated as: 1 = ON; 0 = OFF.
NOTE 2: The following conditions are necessary to perform control of IO Modules from SCADA:
- IO mode is enabled in I/O settings;
- IO Output# has Type equal to Disable in I/O settings;
- IO faults are absent.
NOTE: Date and time are established in the seconds beginning from 1997.
Register Description
30005 Ua
30006 Ub
Phase to earth voltages 30007 Uc 0÷18kV 1V
30008 Ur
30009 Us
30010 Ut
Register Description
30011 Uab
30012 Ubc
Line to line voltages
30013 Uca 0-30kV 1V
30014 Urs
30015 Ust
30016 Uta
Register Description
30017 A kVA
30018 B kVA
30019 C kVA
30020 A kW
Single and three phase total, 30021 B kW
active and reactive power 30022 C kW 0÷65535 1
30023 A kVAr
30024 B kVAr
30025 C kVAr
30026 KVA
30027 KVAr
30028 KW
Measured
Measured value Register and Designation Resolution
range
Register Description
30029-30030 A+kVA*h
30031-30032 B+kVA*h
30033-30034 C+kVA*h
30035-30036 A+kVAr*h
30037-30038 B+kVAr*h
Single and three phase total and 30039-30040 C+kVAr*h
reactive energy related to 30041-30042 +kVA*h
forward and reverse power flow 30043-30044 +kVAr*h 0÷999999999 1
directions 30045-30046 A-kVA*h
30047-30048 B-kVA*h
30049-30050 C-kVA*h
30051-30052 A-kVAr*h
30053-30054 B-kVAr*h
30055-30056 C-kVAr*h
30057-30058 -kVA*h
30059-30060 -kVAr*h
Value
Meaning
Phase sequence from ABC and (Hex)
RST sides Phase seq. 0x00 ACB(RTS)
0x01 ABC(RST)
0x02 ?
Value
Meaning
(Hex)
OC, EF, SEF power flow direction
0x00 +
0x01 -
0x02 ?
NOTE 1: In order to obtain the value of frequency in Hz the value obtained from Modbus must be multiplied by
0.001.
NOTE 2: If a situation occurs where it is not possible to conduct the calculation of power factor or frequency then
Modbus returns value equal 0x7FFF.
NOTE 3: In order to obtain power factor the value obtained from Modbus must be multiplied by 0.001.
The setting of coils does not occur with the appearance of exception.
The list of coils is given in Table 5.2.
NOTE 1: The setting of coil in 0 doesn’t affect the protection algorithms in the RC-01E(S).
NOTE 2: The setting of "Reserved" coil in 0 or 1 will not result in any changes in the RC-01E(S).
The exception response message has two fields that differentiate it from a normal response:
Function Code Field: In a normal response, the server echoes the function code of the original request in the
function code field of the response. All function codes have a most–significant bit (MSB) of 0 (their values are all
below 80 hexadecimal). In an exception response, the server sets the MSB of the function code to 1. This makes
the function code value in an exception response exactly 80 hexadecimal higher than the value would be for a
normal response.
With the function code’s MSB set, the client's application program can recognize the exception response and
can examine the data field for the exception code.
Data Field: In a normal response, the server may return data or statistics in the data field (any information that
was requested in the request). In an exception response, the server returns an exception code in the data field,
defining the server condition that caused the exception.
This Modbus implementation returns three types of errors; they are given in table 5.1. The complete list of
possible errors are documented in the PI-MBUS-300 document.