NOJA-5074-00 Modbus User Guide
NOJA-5074-00 Modbus User Guide
NOJA-5074-00 Modbus User Guide
www.nojapower.com.au
NOJA-5074-00
Revision History
This document is copyright and is intended for users and distributors of NOJA Power Switchgear product. It
contains information that is the intellectual property of NOJA Power Switchgear and the document, or any part
thereof, should not be copied or reproduced in any form without written permission from NOJA Power
Switchgear.
NOJA Power ® is a trademark of NOJA Power Switchgear and should not be reproduced or used in any
way without written authorisation.
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.
Contents
1 Introduction ............................................................................................................................................................. 1
1.1 Applicability .............................................................................................................................................................1
2 Implementation ....................................................................................................................................................... 1
2.1 Data Access and Types ............................................................................................................................................1
2.2 Serial Channel Multi-Protocol..................................................................................................................................1
2.3 Reading/writing of double-word (32-bits) values....................................................................................................2
2.4 Supported Function Codes ......................................................................................................................................2
2.4.1 Function 01 Read Coil Status ...............................................................................................................................2
2.4.2 Function 02 Read Input Status ............................................................................................................................3
2.4.3 Function 03 Read Holding Registers ....................................................................................................................3
2.4.4 Function 04 Read Input Registers .......................................................................................................................3
2.4.5 Function 05 Write Single Coil ..............................................................................................................................3
2.4.6 Function 06 Write Single Register .......................................................................................................................3
2.4.7 Function 15 (0F Hex) Write Multiple Coils ..........................................................................................................3
2.4.8 Function 16 (10 Hex) Write Multiple Registers ...................................................................................................4
2.5 Modbus Exception Responses .................................................................................................................................4
3 Datapoints ................................................................................................................................................................ 5
3.1 Coils (0X Reference) .................................................................................................................................................5
3.2 Discrete Inputs (1X Reference) ................................................................................................................................6
3.3 Input Registers (3X Reference) ................................................................................................................................9
3.4 Holding Registers (4X Reference) ..........................................................................................................................12
4 Configuration ......................................................................................................................................................... 12
4.1 SGA Function Block ................................................................................................................................................13
NOJA-5074-00
1 Introduction
The Modbus Protocol is commonly used network protocol in the industrial manufacturing environment. This
manual describes support for the Modbus Protocol in the NOJA Power Recloser series of controllers
(RC10/15/20).
1.1 Applicability
Support for the MODBUS Protocol was included in firmware versions 1.26.y.0 onwards for the RC10/15 and
firmware version 2.0 onwards for the RC20. If you have a software version earlier than this, then this document
does not apply. Please contact your NOJA Power representative for further information.
2 Implementation
Within the NOJA Power devices, the Modbus Protocol is implemented through Smart Grid Automation (SGA). It
supports Modbus RTU for serial communication and Modbus TCP for use over ethernet. The NOJA Power
controller can be configured as a Modbus Server device, accepting requests from a Modbus Client device.
3 Datapoints
3.1 Coils (0X Reference)
Address Settings Description
Trip allphases(1). Trip control will always return exception code 0x05
00001 Trip(All)
Acknowledge.
Close all phases(1). Close control will always return exception code 0x05
00002 Close(All)
Acknowledge.
00003 On (Grp1) Switch Group1 On
00004 On (Grp2) Switch Group2 On
00005 On (Grp3) Switch Group3 On
00006 On (Grp4) Switch Group4 On
00007 On (Prot) Switch protection On
00008 Off (Prot) Switch protection Off
00009 On (EF) Switch earth fault overcurrent element On
00010 Off (EF) Switch earth fault overcurrent element Off
00011 On (SEF) Switch sensitive earth fault element On
00012 Off (SEF) Switch sensitive earth fault element Off
00013 On (AR) Switch autoreclosing element On
00014 Off (AR) Switch autoreclosing element Off
00015 On (LL) Switch live line element On
00016 Off (LL) Switch live line element Off
00017 On (CLP) Switch cold load pickup element On
00018 Off (CLP) Switch cold load pickup element Off
00019 On (UV) Switch undervoltage element On
00020 Off (UV) Switch undervoltage element Off
00021 On (UF) Switch underfrequency load shed element On
00022 Off (UF) Switch underfrequency load shed element Off
00023 On (ABR) Switch ABR element On
00024 Off (ABR) Switch ABR element Off
00025-00030 On/Off (IO1, Outputs 1–6) Switch IO1 Module (Outputs 1–6) On/Off
00031-00036 On/Off (IO2, Outputs 1–6) Switch IO2 Module (Outputs 1–6) On/Off
00037-00038 On/Off (IO1, Outputs 7–8) Switch IO1 Module (Outputs 7–8) On/Off
00039-00040 On/Off (IO2, Outputs 7–8) Switch IO2 Module (Outputs 7–8) On/Off
00041-00072 VAR1 – VAR32 Logic output Variables 1 – 32
Notes:
1. Individual phases for single triple are not natively supported. Individual phases can be implemented through logic
with VARs.
2. Attempting to read/write to a coil not in the above range will result in an error.
Notes:
1. 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.
2. Attempting to read/write to a coil not in the above range will result in an error.
30021 B kW B kW 0 – 65535 1
30022 C kW C kW 0 – 65535 1
30028 KW KW 0 – 65535 1
Lifetime counters
30072 CO Total CO Total
30073 Mech.wear,% Mech.wear,%
30074 Contact wear,% Contact wear,%
Fault counters
30075 OC A trips OC A trips
Notes:
• In order to obtain the value of frequency in Hz the value obtained from Modbus must be multiplied by 0.001.
• If a situation occurs where it is not possible to conduct the calculation of power factor or frequency then Modbus
returns value equal 0x7FFF.
• In order to obtain power factor the value obtained from Modbus must be multiplied by 0.001.
• Attempting to read/write to a coil not in the above range will result in an error.
Notes:
• Attempting to read/write to a coil not in the above range will result in an error.
4 Configuration
Modbus is configured through SGA. It is important to note that this function is only used to start, stop and
configure the Modbus Protocol. The protocol itself runs in a separate instance within the relay, meaning it is not
affected by SGA Throttling.
SLAVE_ID Server ID used for addressing the controller when using Modbus RTU
CHANNEL A numeric value which represents the communication channel to use. The channel selection
will also determine if Modbus will communicate over serial or ethernet. See below for channels
and associated Modbus mode.
The Modbus Outstation function block differs from all other function blocks in that it is not event driven on delete.
• When the Modbus FB receives an event the configuration settings on the input of the function block will
be applied.
• When the Modbus FB is deleted, Modbus will be disabled.
• If multiple Modbus FB's are in resources, there will be no interaction/interlocking between the multiple
instances.
• On power up Modbus will assume its last state until changed by the Modbus FB.
• If Modbus is disabled by another process (for example, misconfiguration with CMS over serial), the
Modbus FB will not automatically enable Modbus once the issue is resolved
The Modbus FB can be correctly deployed via SGA as shown. In the first instance, the Modbus channel is set to
use RS232, placing the protocol in Modbus RTU mode. The Slave_ID is specified as 247, but can be changed to
suit the specific Modbus network as required. The TCP_Port value is not used and will be ignored.
The following instance shows Modbus channel set to 10, indicating LAN communication port and Modbus TCP
mode. In this case, the TCP_Port is specified as 502, the default for Modbus.
It can be seen from the above examples that the only difference between the two is the “Channel” setting. This is
the overriding setting required to ensure the correct Modbus mode is activated within the device.