Modbus™ Communications System for

Micrologic™ A, P, and H Trip Units

ENGLISH
Instruction Bulletin
0613IB1201 R03/17
03/2017
Retain for future use.
 Hazard Categories and Special Symbols
ENGLISH

Read these instructions carefully and look at the equipment to become familiar with the
device before trying to install, operate, service or maintain it. The following special
messages may appear throughout this bulletin or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies a procedure.
The addition of either symbol to a “Danger” or “Warning” safety label indicates that
an electrical hazard exists which will result in personal injury if the instructions are
not followed.

ANSI
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible injury
or death.

DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in
IEC death or serious injury.

WARNING
WARNING indicates a hazardous situation which, if not avoided, can result in
death or serious injury.

CAUTION
CAUTION indicates a hazardous situation which, if not avoided, can result in
minor or moderate injury.

NOTICE
NOTICE is used to address practices not related to physical injury. The safety
alert symbol is not used with this signal word.

NOTE: Provides additional information to clarify or simplify a procedure.

Please Note
Electrical equipment should be installed, operated, serviced, and maintained only
by qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.

FCC Notice
This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his
own expense. This Class A digital apparatus complies with Canadian ICES-003.
Table of Contents Four-Wire Modbus® Communications System

Table of Contents

ENGLISH
List of Tables: ..................................................................................................... 6
At a Glance .................................................................................................... 10
Validity Note ................................................................................................... 10
Related Documents ....................................................................................... 10
SECTION 1:MICROLOGIC COMMUNICATION SYSTEM ..................................................................... 11
Introduction .................................................................................................... 11
List of Abbreviations ....................................................................................... 11
Communication System Parameters ............................................................. 11
Communication System Components ............................................................ 12
Micrologic A Trip Units ............................................................................. 12
Micrologic P and H Trip Units .................................................................. 12
Breaker Communication Module (BCM) .................................................. 13
Communication Switches ........................................................................ 13
24 Vdc Control Power .............................................................................. 13
Daisy Chain Four-Wire Modbus Network ................................................ 13
Cradle Communication Module (CCM) .................................................... 14
Communicating Shunt Trip and Shunt Close Coils .................................. 14
Ethernet Gateway or Circuit Monitor ........................................................ 14
Micrologic Trip Unit, BCM and CCM ........................................................ 15
BCM to Daisy Chain ................................................................................ 16
BCM and CCM ......................................................................................... 17
Modbus TCP / IP Communication ........................................................... 17
Standard Wiring Practices ............................................................................. 18
Communication System ........................................................................... 18
System Problems ........................................................................................... 19
Troubleshooting ............................................................................................. 19
Addresses, Baud Rate, and Parity Settings ................................................... 20
Micrologic A Trip Unit ............................................................................... 20
Micrologic P and H Trip Unit .................................................................... 21
SECTION 2:COMMUNICATION ARCHITECTURE .................................................................................. 22
Introduction .................................................................................................... 22
Module ..................................................................................................... 22
Command Interface ................................................................................. 22
Modbus Functions .......................................................................................... 23
Breaker Communication Module: @ Address xx ..................................... 23
Communication Profile ............................................................................. 23
Simplified Open/Close Command ............................................................ 23
Cradle Communication Module: @ Address xx + 50 ............................... 24
Metering Module: @ Address xx + 200 .................................................... 24
Protection Module: @ Address xx + 100 ................................................. 26
SECTION 3:COMMAND INTERFACE .......................................................................................................... 28

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 3

 Four-Wire Modbus® Communications System Table of Contents

Operating Principle ........................................................................................ 28

Send Commands in Shared Mode ................................................................. 29
ENGLISH

Send Commands in Protected Mode ............................................................. 30

Optimize Sending of Commands ................................................................... 32
Remote Configuration .................................................................................... 32
Example of a Remote Parameter-Setting Sequence ............................... 34
SECTION 4:ACCESS TO FILES .......................................................................................................... 35
Introduction .................................................................................................... 35
Event Logs ..................................................................................................... 35
Wave Form Capture (WFC) ........................................................................... 36
Event Log of the Breaker Communication Module @ Address xx ................. 36
Event Log of the Protection Module @ Address xx + 100 .....................................38
Event Log of the Metering Module @ Address xx + 200 ................................ 40
Maintenance Event Logs of the Protection Module
@ Address xx + 100 ....................................................................................... 42
Maintenance Event Log of the Metering Module ........................................... 44
Min-Max Event Log of the Metering Module @ Address xx + 200 ................. 46
Wave Form Capture ....................................................................................... 48
Fault Wave Form Capture .............................................................................. 50
SECTION 5:MODBUS FUNCTIONS .......................................................................................................... 52
Introduction .................................................................................................... 52
Modbus / JBus Protocol ................................................................................. 52
Modbus Exception Responses ...................................................................... 52
Standard Modbus Functions .......................................................................... 53
Advanced Modbus Functions ......................................................................... 55
SECTION 6:INTERFACING LEGACY AND NEW COMMUNICATIONS SYSTEMS ..................... 56
Introduction .................................................................................................... 56
Typical Communication System Diagrams .................................................... 56
Interfacing New Two-Wire Modbus and Smart Communications Systems with
Four-Wire Modbus Systems .......................................................................... 57
Converting Legacy Four-Wire Modbus Communications to Smart System
Components. .................................................................................................. 61
General Information ................................................................................. 61
Fixed Circuit Breaker Communications System ....................................... 61
Drawout Circuit Breaker Communications System .................................. 63
Replacing the BCM (Breaker Communications Module) ............................... 65
Replacing the CCM (Cradle Communications Module) ........................... 76

4 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Table of Contents Four-Wire Modbus® Communications System

Convert to new system by using the IO module ...................................... 76

Determine the Address for the trip unit. ............................................. 77

ENGLISH
Customer Engineering Tool (Ecoreach) .................................................. 80
APPENDIX A:REGISTERS .......................................................................................................... 81
Formats .......................................................................................................... 81
Table of Registers .......................................................................................... 85
Structure of the Table .............................................................................. 85
Scale Factors ........................................................................................... 85
Breaker Communication Module @ Address xx ...................................... 87
Cradle Communication Module @ Address xx + 50 ................................ 92
Metering Module @ Address xx + 200 ..................................................... 95
Protection Module @ Address xx + 100 ................................................ 116
Advanced Protection Settings ................................................................ 127
Communication Profile @ Address xx ................................................... 145
Activation of the Communication Profile .......................................... 145
IO Status.......................................................................................... 146
Metering........................................................................................... 149
List of Commands ........................................................................................ 156
Cradle Communication Module Commands @ Address xx + 50 ........... 156
Breaker Communication Module Commands @ Address xx ................. 157
Metering Module Commands @ Address xx + 200 ............................... 159
Protection Module Commands @ Address xx + 100 ............................. 161
Send Commands in Shared Mode Simplified Open / Close .................. 163
Send Commands in Protected Mode ..................................................... 164
Remotely OPEN the Circuit Breaker Commands .................................. 165
Remotely CLOSE the Circuit Breaker Commands ................................ 166
Synchronize the Clocks Commands ...................................................... 167
Remotely Configure and Set Commands .............................................. 168
Run Remote Resets / Preset Commands .............................................. 171
Manage the Event Logs— Breaker
Communication Module Commands ...................................................... 172
Manage the Event Logs—Metering Module Commands ....................... 173
Manage the Event Logs— Configure Analog Predefined Alarm n°1:
Overcurrent Phase A Commands .......................................................... 174

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 5

 Four-Wire Modbus® Communications System List of Tables

List of Tables
ENGLISH

Table 1 – External 24 Vdc Control Power Supply Characteristics............................................................. 13

Table 2 – Breaker Communication Module Registers ............................................................................... 23
Table 3 – Cradle Communication Module Registers ................................................................................. 24
Table 4 – Metering Module Registers........................................................................................................ 25
Table 5 – Protection Module Registers ..................................................................................................... 27
Table 6: Command Interface ................................................................................................................... 28
Table 7 – Command Interface Registers................................................................................................... 29
Table 8 – Shared Mode Registers in the Command Interface .................................................................. 29
Table 9 – Protected Mode Registers in the Command Interface............................................................... 30
Table 10 – Command Result Codes ........................................................................................................... 30
Table 11 – Read-Accessed Commands...................................................................................................... 31
Table 12: Breaker Communication Module Remote Configuration ........................................................... 32
Table 13: Cradle Communication Module Remote Configuration ............................................................. 33
Table 14: Metering Module Remote Configuration.................................................................................... 33
Table 15: Protection Module Remote Configuration.................................................................................. 33
Table 16 – Descriptor of the Event Log in the Breaker Communication Module......................................... 36
Table 17 – Format of Records in the Event Log of the Breaker Communication Module ........................... 37
Table 18 – Events in the Event Log of the Breaker Communication Module .............................................. 37
Table 19 – Descriptor of the Event Log in the Protection Module ............................................................... 38
Table 20 – Format of Records in the Event Log of the Protection Module.................................................. 39
Table 21 – Events in the Event Log of the Protection Module..................................................................... 39
Table 22 – Descriptor of the Event Log in the Metering Module ................................................................. 40
Table 23 – Format of Records in the Event Log of the Metering Module .................................................... 41
Table 24 – Events in the Event Log of the Metering Module....................................................................... 41
Table 25 – Descriptor of the Maintenance Event Log in the Protection Module.......................................... 42
Table 26 – Format of Records in the Maintenance Event Log of the Protection Module ............................ 43
Table 27 – Descriptor of the Maintenance Event Log in the Metering Module............................................ 44
Table 28 – Format of Records in the Maintenance Event Log of the Metering Module .............................. 45
Table 29 – Descriptor of the Min-Max Event Log in the Metering Module................................................... 46
Table 30 – Format of Records in the Min-Max Even Log of the Metering Module ...................................... 47
Table 31 – Descriptor of the Wave Form Capture in the Metering Module ................................................. 48
Table 32 – Format of Records in the Wave Form Capture of the Metering Module.................................... 49
Table 33 – Descriptor of the Fault Wave Form Capture in the Protection Module ...................................... 50
Table 34 – Format of Records in the Fault Wave Form Capture of the Protection Module......................... 51
Table 35 – Read Functions ......................................................................................................................... 53
Table 36 – Write Functions.......................................................................................................................... 53

6 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

List of Tables Four-Wire Modbus® Communications System

Table 37 – Diagnostic Functions.................................................................................................................. 53

Table 38 – File Record Read ....................................................................................................................... 54

ENGLISH
Table 39 – Event Log................................................................................................................................... 54
Table 40 – Example of an Advanced Modbus Function .............................................................................. 55
Table 41 – Hex to Decimal Conversion ....................................................................................................... 67
Table 42 – Trip Record Fields...................................................................................................................... 82
Table 43 – Alarm Record Fields .................................................................................................................. 82
Table 44 – Basic Protections ....................................................................................................................... 83
Table 45 – Advanced Protections ................................................................................................................ 83
Table 46 – Digital Alarms............................................................................................................................. 84
Table 47 – Scale Factors ............................................................................................................................. 85
Table 48 – Configuration.............................................................................................................................. 87
Table 49 – Identification............................................................................................................................... 87
Table 50 – Diagnostics Counters and Password ......................................................................................... 88
Table 51 – Metering / Protection Module Event Notification ........................................................................ 89
Table 52 – Cause of Tripping....................................................................................................................... 89
Table 53 – Circuit Breaker Status, Auto / Manu........................................................................................... 90
Table 54 – List of Possible Values for Register 661 (Circuit Breaker
Status) in the Breaker Communication Module.......................................................................... 91
Table 55 – Time Stamping........................................................................................................................... 91
Table 56 – Configuration.............................................................................................................................. 92
Table 57 – Identification............................................................................................................................... 92
Table 58 – Diagnostics Counters and Password ......................................................................................... 93
Table 59 – Cradle Status ............................................................................................................................. 94
Table 60 – Time Stamping........................................................................................................................... 94
Table 61 – Voltages ..................................................................................................................................... 95
Table 62 – Currents ..................................................................................................................................... 96
Table 63 – Power......................................................................................................................................... 96
Table 64 – Power Factor.............................................................................................................................. 97
Table 65 – Frequency .................................................................................................................................. 97
Table 66 – Fundamental .............................................................................................................................. 98
Table 67 – Total Harmonic Distortion .......................................................................................................... 99
Table 68 – Energy...................................................................................................................................... 102
Table 69 – Demand Current ...................................................................................................................... 103
Table 70 – K-Factor Demand..................................................................................................................... 103
Table 71 – Demand Power ........................................................................................................................ 104
Table 72 – Time Stamping......................................................................................................................... 105
Table 73 – Configuration............................................................................................................................ 106
Table 74 – Spectral Components (Odd Rank)........................................................................................... 108

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 7

 Four-Wire Modbus® Communications System List of Tables

Table 75 – Spectral Components (Even Rank) ......................................................................................... 110

Table 76 – Analog Pre-Defined Alarms ..................................................................................................... 112
ENGLISH

Table 77 – Characteristics of the Protection Module................................................................................. 116

Table 78 – Basic Protections Settings (Long-Time Protection-Alarm N° 1000 Ir) ..................................... 117
Table 79 – Basic Protections Settings (Short-Time Protection-Alarm N° 1001 Isd) .................................. 118
Table 80 – Basic Protections Settings (Instantaneous Protection-Alarm N° 1002 Ii) ................................ 119
Table 81 – Basic Protections Settings (Ground-Fault Protection-Alarm N° 1003 Ig) ................................ 120
Table 82 – Basic Protections Settings (Earth-Leakage Protection Alarm N° 1004 Idelta n) ..................... 121
Table 83 – Protection Module Measurements........................................................................................... 122
Table 84 – Status of the Protection Module .............................................................................................. 123
Table 85 – Time Stamping and Trip / Alarm History.................................................................................. 124
Table 86 – Trip History .............................................................................................................................. 124
Table 87 – Alarm History ........................................................................................................................... 125
Table 88 – Micrologic Configuration .......................................................................................................... 126
Table 89 – Ground-Fault Alarm—Alarm N°1014 (Ig Protection) ............................................................... 127
Table 90 – Earth-Leakage Alarm—Alarm N°1015 (IΔn Protection)........................................................... 128
Table 91 – Current Unbalance—Alarm N°1016 (Iunbal Protection)............................................................ 129
Table 92 – Maximum Current—Alarm N°1017 (IA max Protection) ............................................................ 130
Table 93 – Maximum Current—Alarm N°1018 (IB max Protection) ............................................................ 131
Table 94 – Maximum Current—Alarm N°1019 (IC max Protection) ............................................................ 132
Table 95 – Maximum Current—Alarm N°1020 (IN max Protection) ............................................................ 133
Table 96 – Minimum Voltage—Alarm N°1021 (Vmin Protection) ............................................................... 134
Table 97 – Maximum Voltage—Alarm N°1022 (Vmax Protection) ............................................................. 135
Table 98 – Voltage Unbalance—Alarm N°1023 (Vunbal Protection) .......................................................... 136
Table 99 – Reverse Power—Alarm N°1025 (rPmax Protection) ................................................................ 137
Table 100 – Minimum Frequency—Alarm N°1026 (Fmin Protection) .......................................................... 138
Table 101 – Maximum Frequency—Alarm N°1027 (Fmax Protection)......................................................... 139
Table 102 – Phase Rotation Alarm—Alarm N° 1028................................................................................... 140
Table 103 – Load Shedding and Reconnection Based on Current—Alarm N°1029 ................................... 141
Table 104 – Load Shedding and Reconnection Based on Power—Alarm N°1030 ..................................... 142
Table 105 – Relay Configuration M2C/M6C................................................................................................ 143
Table 106 – Circuit Breaker......................................................................................................................... 146
Table 107 – Input......................................................................................................................................... 147
Table 108 – Tripping Cause ........................................................................................................................ 147
Table 109 – Alarm Setpoint ......................................................................................................................... 148
Table 110 – Currents................................................................................................................................... 149
Table 111 – Maximum Values of Currents .................................................................................................. 149
Table 112 – Voltages................................................................................................................................... 149
Table 113 – Frequency................................................................................................................................ 150

8 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

List of Tables Four-Wire Modbus® Communications System

Table 114 – Power....................................................................................................................................... 150

Table 115 – Energy...................................................................................................................................... 151

ENGLISH
Table 116 – Current Demand ...................................................................................................................... 151
Table 117 – Power Demand ........................................................................................................................ 151
Table 118 – Maximum Values of Voltages .................................................................................................. 152
Table 119 – Power Factor............................................................................................................................ 152
Table 120 – Total Harmonic Distortion ........................................................................................................ 153
Table 121 – Available and Reserved Registers........................................................................................... 153
Table 122 – Basic Protection Settings ......................................................................................................... 154
Table 123 – Circuit Breaker ID..................................................................................................................... 155
Table 124 – Miscellaneous .......................................................................................................................... 156
Table 125 – Cradle Communication Module Commands ............................................................................ 156
Table 126 – Breaker Communication Module Commands .......................................................................... 157
Table 127 – Metering Module Commands................................................................................................... 159
Table 128 – Protection Module Commands................................................................................................. 161

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 9

 Four-Wire Modbus® Communications System About the Book

About the Book

ENGLISH

At a Glance
The aim of this document is to provide users, installers, and maintenance
personnel with the technical information needed to operate the Modbus protocol on
the four ranges of circuit breakers and switches:
• PowerPact P-frame 250–1200 A
• PowerPact R-Frame 600–3000 A
• Masterpact NT 250–1200 A (800 A in ANSI and 1600 A in UL489)
• Masterpact NW 260–6000 A

Validity Note
This document is valid for Masterpact NT/NW and PowerPact P/R circuit breakers
with a BCM circuit breaker communications module connected with 4-wire Modbus
to a RS485 serial network.
See Introduction on the next page for two-wire Modbus and Smart System™
communication systems.

Related Documents
Title of Documentation Reference Number Reference Number
Masterpact NT Circuit Breakers and Switches - User Guide 0613IB1209 (EN, ES, FR)
Masterpact NW Circuit Breakers and Switches - User Guide 0613IB1204 (EN, ES, FR)
PowerPact P-Frame - Installation Guide 48049-148 (EN, ES, FR)
PowerPact Drawout P-Frame - Installation Guide 48049-336 (EN, ES, FR)
PowerPact R-Frame - Installation Guide 48049-243 (EN, ES, FR)
Micrologic A Trip Units - User Guide 48049-136 48049-136 (EN, ES, FR)
Micrologic P Trip Units - User Guide Guide 48049-137 (EN, ES, FR)
Micrologic H Trip Units - User Guide 48049-330 (EN, ES, FR)
Masterpact NT/NW, Compact NS, PowerPact P- and R-Frame
EAV36080 (EN, ES, FR)
Communication Option - Installation Manual
ULP (Universal Logic Plug) System - User Guide 48940-329 (EN, ES, FR)
Masterpact NT/NW and PowerPact P- and R-Frame Modbus
0613IB1313
Communications Guide
ULP (Universal Logic Plug) User Guide 0602IB1503

Download these technical publications and other technical information from our
website at www.schneider-electric.com

10 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 1—Micrologic Communication System Four-Wire Modbus® Communications System

Section 1— Micrologic Communication System

ENGLISH
Introduction
This instruction bulletin is for four-wire Modbus systems installed before the
introduction of two-wire Modbus and Smart System™ communications systems.
For two-wire Modbus systems and Smart System with ULP systems, see
0613IB1313 for instructions.
The Modbus communication option makes it possible to remotely use all the
functions of a MasterPact™, PowerPact™, or Compact™ circuit breaker, its
Micrologic trip unit, and all its options.
Remote operations are based on a secure communication architecture. The
Modbus communication system may be used to interconnect the control units (A,
P, or H) and a supervisor, and a PLC or Modbus master. The connection uses an
RS485 physical link and the Modbus-RTU protocol.

List of Abbreviations
BCM – Breaker Communication Module
CCM – Cradle Communication Module
HMI – Human Machine Interface (Control Pad)
LED – Light Emitting Diode
MM – Trip Unit Metering Module
PIF – Product Interface Module
PLC – Programmable Logic Controller
PM – Trip Unit Protection Module
RS485 – Specific Type of Communication System
RTU – Remote Terminal Unit
SMS – System Management Software
TCP / IP – Transmission Control Protocol / Internet Protocol

Communication System Parameters

Micrologic trip units use a system consisting of:
• four-wire Modbus,
• RTU, RS485 network,
• master / slave (Micrologic trip units are always slaves),
• any Modbus software (not proprietary),
• daisy chain using Belden® shielded / twisted cable (8723 recommended).
• Customer Engineering Tool (Ecoreach)
Download Ecoreach from the Schneider Electric website:
www.schneider-electric.com

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 11

 Four-Wire Modbus® Communications System Section 1—Micrologic Communication System

Communication System Components

ENGLISH

Circuit breakers that have Micrologic trip units are Powerpact, Compact, and
Masterpact.
The communication system consists of:
• Micrologic trip units (A, P, or H models are capable of communication),
• Breaker Communication Module (BCM),
• Communication switches that report circuit breaker status (open, closed,
tripped, ready to close) into the BCM,
• 24 Vdc control power,
• Daisy chain four-wire Modbus network,
• Drawout circuit breakers also have cradle communication module (CCM),
• Communicating shunt trip and shunt close coils,
• Ethernet gateway or circuit monitor to allow Modbus TCP / IP communication.
Micrologic A Trip Units
Micrologic A trip units require:
• Control power rated 50 mA at 24 Vdc.
• Control power source to the trip unit must be isolated from the 24 Vdc control
power to the BCM.
• The positive or negative output of the power supply must not be earth grounded.
• The DC output of the 24 Vdc power supply must also be isolated from its input.
See External 24 Vdc Control Power Supply Characteristics on page 13.
• Micrologic A trip units control power connections to F1 (-) and F2 (+).
• See the trip unit manual and the Masterpact NT/NW Universal Power Circuit
Breakers catalog for specific information about the trip unit and other components.
Micrologic P and H Trip Units
Micrologic P or H trip units require:
• Control power rated 100 mA at 24 Vdc.
• Control power source to the trip unit must be isolated from the 24 Vdc control
power to the BCM.
• The positive or negative output of the power supply must not be earth grounded.
• The DC output of the 24 Vdc power supply must also be isolated from its input.
See External 24 Vdc Control Power Supply Characteristics on page 13.
• P and H trip units control power connections to F1 (-) and F2 (+).
• See the trip unit manual and the Masterpact NT/NW Universal Power Circuit
Breakers catalog for specific information about the trip unit and other components.

12 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 1—Micrologic Communication System Four-Wire Modbus® Communications System

Breaker Communication Module (BCM)

The BCM requires:

ENGLISH
• Control power rated 50 mA at 24 Vdc.
• Control power source to the trip unit must be isolated from the 24 Vdc control
power to the BCM.
• The positive or negative output of the power supply must not be earth
grounded.
• The DC output of the 24 Vdc power supply must also be isolated from its input.
See External 24 Vdc Control Power Supply Characteristics on page 13.
• The BCM control power connections to E1 (+) and E2 (-).
Communication Switches
• Report circuit breaker status into BCM. Switches are actuated by the circuit
breaker mechanism to indicate open, closed, tripped, and ready to close status.
• Switches are installed in the circuit breaker mechanism and connected by
wiring into the BCM.
• See BCM instructions for each circuit breaker type for instructions and
mounting information.
24 Vdc Control Power
• The 24 Vdc (E1, E2) power supply for the BCM must be separate from the
24 Vdc power supply module for the Micrologic trip units (F1-, F2+).
• The separate power supplies provide isolation between the trip unit and the
communication system. The positive or negative output of the power supply
must not be earth grounded. The DC output of the 24 Vdc power supply must
also be isolated from its input. Specifications are in the table below:

Table 1 – External 24 Vdc Control Power Supply Characteristics

Rated Output Current 1A
Rated Voltage 24 Vdc
Overall Accuracy ± 5% Vn
Ripple 200 mV peak to peak
Noise 200 mV peak to peak
Voltage Output Variation Limit 21.6 V < Vout < 26.3 V
Capacitive Load 500 µF
Input / Output Capacitive Load 150 pF max

Daisy Chain Four-Wire Modbus Network

• Use 22 AWG Belden® shielded / twisted cable (8723).
• Ground shield at one end of the chain only.
• Respect Standard Wiring Practices as explained on page18.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 13

 Four-Wire Modbus® Communications System Section 1—Micrologic Communication System

Cradle Communication Module (CCM)

• Used with drawout construction.
ENGLISH

• CCM requires 50 mA at 24 Vdc control power.

• Control power source can be the same as the one powering the BCM.
• Control power source must be isolated and ungrounded. See External 24 Vdc
Control Power Supply Characteristics on page 13.
• Provides connections for daisy chain communication wires.
• Provides connections for 24 Vdc control power.
• Can be connected to cradle position switches to report circuit breaker position
(connected, test, disconnected) in the cradle.
• Maintains communication parameters (address, baud rate, parity) for the cradle
so when a spare circuit breaker is racked in, the communication parameters
are automatically transferred.
• CCM can be replaced with the Input/Output (IO) Module plus a Modbus
Interface Module (IFM) with firmware upgrade. See page 76 for information on
converting to the IO and IFM modules.
Communicating Shunt Trip and Shunt Close Coils
• Allows opening and closing the circuit breaker through the communication
network.
• Connected to BCM.
• Special three-wire shunt trip and close coils are required.
Ethernet Gateway or Circuit Monitor
• EGX100 and EGX300 ethernet gateways providing Modbus TCP / IP
Communication
• System wide communication
• Web pages
• Communication from any browser

14 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 1—Micrologic Communication System Four-Wire Modbus® Communications System

System Diagrams

ENGLISH
Micrologic Trip Unit, BCM and CCM
Drawout circuit breakers have four modules:
• BCM (Breaker Communication Module)
• Trip unit PM (Protection Module)
• Trip unit MM (Metering Module)
• CCM (Cradle Communication Module)

Figure 1 – Micrologic Trip Unit, BCM and CCM

Daisy Chain Connected Deviecs

Address

(51) CCM

BCM
(1)

(101) PM

(201) MM
Trip Unt

Circuit
Circuit Breaker Breaker
Cradle

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 15

 Four-Wire Modbus® Communications System Section 1—Micrologic Communication System

BCM to Daisy Chain

1. Trip unit
ENGLISH

2. BCM
3. CCM
4. Communicating shunt trip or shunt close coil
Figure 2: Micrologic Trip Unit, BCM, CCM and Communicating Shunt Trip or Shunt Close Co8il

Communicating System Using the Modbus Protocol

Connection
to the Bus
Communicating System

Connection
to the Bus

Connection
Between Modules

1 Drawout Unit

Fixed Unit

Drawout Circuit Breaker Connections

To Cradle Module

Connector

E6
E4E5
E1 E2E3

%
100

Prefabricated
Connector

Wires

E5 E6
Plug-In COM E1 E2
E3 E4

Connector

16 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 1—Micrologic Communication System Four-Wire Modbus® Communications System

BCM and CCM

ENGLISH
Figure 3: BCM and CCM Connections

Cradle Position Switches

1 CT +
2 CT -
3 CD +

4 CD - Secondary Connections
+24VDC
Gnd

5 CE +
12 6 CE - Com
11 7 +24VDC E1 E1 +24VDC 6
10 8 Gnd E2 E2 Gnd 5
9 E3 E3 Black 4
+24VDC

Modbus E4 E4 Red 3
Gnd

CCM E5 E5 White 2

E6 E6 Green 1
Green
White
Red
Black
Shield

Cradle Breaker
Modbus
BCM
1 1 Black
2 2 Red
O/F 1
3 3 White
PF 2
4 4 Green
SDE 3
5
DLO / Tumbler
Shield
Green

4
White

Black
Red

Gnd 5

OFO 6

Daisy Chain

Modbus TCP / IP Communication

Figure 4: Modbus TCP / IP Communication

Powerlogic
Network Server Web
Browser

SMS

Ethernet

RS-485 Mixed Mode T

Powerlogic
CM4000 with ECC
Or
EGX Ethernet
Gateway
Circuit Monitors or Power Meters

Circuit Breaker

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 17

 Four-Wire Modbus® Communications System Section 1—Micrologic Communication System

Standard Wiring Practices

ENGLISH

Communication System
• Belden® 8723
• 22 AWG shielded, twisted with bare drain wire from shield
• Standard Colors:
— Rx+ = green
— Rx- = white
— Tx+ = red
— Tx- = black
— shield – bare
• Up to 32 devices on a single daisy chain.
• Devices include:
— Circuit monitors
— Power meters
— PIF-3’s
— PIF-85’s
— Powerlink™ panels
— Digital relays
— Digitrip™ 810D’s
— Micrologic trip units
— Model 98 temperature controllers
— PLCs
• Requires unique addresses for each device on the daisy chain.
• Daisy chain wiring lengths:

Baud Rate 1–16 Devices 17–32 Devices

1200 10,000 ft. (3,050 m) 10,000 ft. (3,050 m)
2400 10,000 ft. (3,050 m) 5,000 ft. (1,525 m)
4800 10,000 ft. (3,050 m) 5,000 ft. (1,525 m)
9600 10,000 ft. (3,050 m) 4,000 ft. (1,220 m)
19200 10,000 ft. (3,050 m) 2,500 ft. (762.5 m)

• Requires resistor / capacitor terminator at the end of each daisy chain. Catalog
number: 3090MCTAS485
• Belden® cable shield must be connected to ground at only one point. We
recommend that this be done at the master device.
• Maintain color code throughout system.
• Ensure connections are on proper stripped wires and connection is on wire not
on insulation.
• Do not strip wires more than necessary or they may short together or to ground
and disrupt communication.
• Maintain baud rate and parity throughout the daisy chain.
• Do not use “T” connections except from CCM to BCM, when less than
1 M of cable is needed.

18 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 1—Micrologic Communication System Four-Wire Modbus® Communications System

System Problems

ENGLISH
Most Modbus system problems are related to wiring and addressing.
Never
• Connect 24 Vdc to communication terminals—it will damage the BCM.
• Allow the shield to touch ground at more than one point—it can cause
communication errors due to circulating currents in shield.
• Change cable type—it can cause communication errors.
• Use Modbus address 16 in a mixed-mode daisy chain (mixed mode means that
there are more than one type of communication on the daisy chain). Address
16 can be used by other components in the system leading to communication
errors.
• Use SY / MAX address 01 in a mixed-mode daisy chain. Address 01 can be used
by other components in the system leading to communication errors.
• Mix two-wire and four-wire devices on the same daisy chain (two-wire Modbus
is not recommended for Micrologic trip unit communication systems)—it can
cause additional load on the communication network and slow down or stop
communication.

Troubleshooting
General
• Ensure all shipping splits and other connections are made.
• Confirm 24 Vdc control power exists at the CCM and E1 / E2 at proper
polarities.
• Confirm circuit breaker is in Test or Connected positions.
• Confirm trip unit is powered (display should be active).
• Check communication parameters and press “address sync” on CCM.
• Check wiring color codes.
CCM LED Indicators
• No LEDs:
24 Vdc control power present.
• One LED solid Green:
24 Vdc control power; no network traffic.
• One LED solid Red:
CCM is defective.
• One LED solid Green with short voids:
seeing good Modbus packets on the wire.
• One LED solid Green with short Red flashes:
indicates the CCM is seeing Modbus packets with errors,
or
indicates the CCM is connected to a “mixed-mode” daisy chain.
• Pressing “Address Sync” push-button on CCM:
— three (3) flashes of red followed by three (3) flashes of green:
information successfully transferred from BCM to CCM,
— three (3) flashes of red followed by solid green:
error transferring information from BCM to CCM.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 19

 Four-Wire Modbus® Communications System Section 1—Micrologic Communication System

• Racking circuit breaker into Test position:

ENGLISH

— three (3) flashes of red followed by three (3) flashes of green:

information successfully transferred from CCM to BCM,
— three (3) flashes of red followed by solid green:
error transferring information from CCM to BCM.
Wiring Checks with Multi-Meter
• Continuity:
— disconnect master device,
— check continuity between each wire,
— twist each pair together and check for continuity,
— ensure no continuity between wires and ground.
• DC voltage:
— with system fully connected, but NO communication activity,
— measure between Rx+ / Rx- (green / white) on each slave device:
should measure approximately 4 Vdc,
— measure between Tx+ / Tx- (red / black) on each slave device:
should measure approximately 0.8 Vdc.

Addresses, Baud Rate, and Parity Settings

Micrologic communication system uses four addresses: BCM, CCM, trip unit
protection module, and trip unit metering module.
Addresses, baud rate, and parity are set through the HMI for the A, P, or H
Micrologic trip units. The HMI address setting actually addresses the BCM from 1
to 47 (47 is the default). The other three addresses are set automatically: CCM =
BCM + 50 (97 is default), trip unit protection module = BCM + 100 (147 is the
default), and trip unit metering module = BCM + 200 (247 is the default).
Micrologic A Trip Unit
Enter configuration mode: Press both buttons and Micrologic 3.0 A

hold for 3-seconds.

Menus to change: Address tsd= tr=
Isd=
Im= Ir=
Ig =
Max
s
A Digital Display
tg=

Baud Rate
Navigation Buttons
Parity
Language
To step between Press and hold the arrow
menu
Press Simultaneously
Ir
long time
tr alarm
for 3 seconds Change
parameters: button.
.8 (s) 4
8
.7 .9 12
.6 .95 2 16
.5
.4
x In
1
.98 1
.5
@ 6 Ir
20
24
to XX
Display will “flash” twice Ii
instantaneous

3
4
5
6
8
Ad47 47 (by default)
2 10

when value is saved.

1.5 12
x In
setting

1
NOTE: You cannot “go back”.
You will have to start over 2

if you need to make 3

changes.
.
.
.
46

20 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 1—Micrologic Communication System Four-Wire Modbus® Communications System

Micrologic P and H Trip Unit

Figure 5: Micrologic P and H Trip Unit Screens

ENGLISH
IP Data

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 21

 Four-Wire Modbus® Communications System Section 2—Communication Architecture

Section 2— Communication Architecture

ENGLISH

Introduction
Module
A module contains:
• a table of registers that may be read-accessed only,
• files such as the event log,
• commands for functions such as writing in the registers, turn the circuit breaker
ON or OFF, reset counters, etc.,
• Modbus functions used to remotely access the registers and the manger files.
NOTE: The commands for the metering and protection modules are controlled by
the breaker communication module.
Command Interface
A command interface in the breaker communication module (BCM) and cradle
communication module (CCM) is used to control the applications. This interface
monitors execution of the command and issues a report.

B Communications
Module Module Module

Modbus RS 485

22 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 2—Communication Architecture Four-Wire Modbus® Communications System

Modbus Functions

ENGLISH
The device and cradle Modbus options operate in slave mode and enable a
Modbus master to access all the registers, files and applications contained in the
modules.
Breaker Communication Module: @ Address xx
The Breaker Communication Module may be used to remotely monitor circuit
breaker status:
• open (OFF),
• closed (ON),
• tripped (SDE),
• ready to close (PF), and so on.
It is also possible to remotely open or close the circuit breaker if the MX and / or XF
communicating coils are installed.
Remote control may be disabled by locally setting the Micrologic control unit to
manual (“Manu”) mode. “Auto” mode enables remote control of the circuit breaker.
Table 2 – Breaker Communication Module Registers

Register Range Description

515–543 Modbus configuration and identification
544–577 Diagnostics counters and Modbus password
603–624 Metering / protection module event notification
650–670 Tripping cause and circuit breaker status
671–715 Time-stamping of last status changes
Event log in the Breaker Communication Module
718–740
(see “Access to Files” on page 35).
800 Communication profile activation
12000–12215 Communication profile

NOTE: More detailed information on these registers is presented in the Appendix,

Table of Registers, “Breaker Communication Module @ Address xx” on page 87.
Communication Profile
In order to optimize the number of Modbus request, a communication profile has
been implemented. The communication profile is located in the breaker
communication module @address xx. This communication profile contains
information coming from the breaker communication module, the metering module
and the protection module. The communication profile is defined in the register
range: 12000–12215.
Simplified Open/Close Command
In order to simplify the application software to remotely open or close the circuit
breaker, a simplified Open/Close command has been implemented. The simplified
Open/Close command is located in the Breaker Communication Module @ address xx.
With the simplified Open/Close command, it is not necessary to request the flag,
neither to enter in configuration mode or to read the control word. It is still necessary to
be in Auto mode (see register 670). Furthermore, this simplified Open/Close command
is password protected (default value = 0000). In order to change the password, it is
mandatory to use the « magic box » and the associated Micrologic utility RSU (please
contact Schneider Electric for more information).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 23

 Four-Wire Modbus® Communications System Section 2—Communication Architecture

The simplified Open/Close command is a share command (command code =

57400).
ENGLISH

NOTE: More detailed information on this command is presented in the Appendix,

List of Command, “Breaker Communication Module Commands @ Address xx” on
page 157.
NOTE: Communication profile and simplified Open/Close command are available
only with a Breaker Communication Module firmware version greater or equal to
V2.0 (register 577 must be greater or equal to 02000).
Cradle Communication Module: @ Address xx + 50
The cradle communication module indicates the position of the device on the
cradle:
• “connected” position,
• “test” position,
• “disconnected” position.
Table 3 – Cradle Communication Module Registers

Register Range Description

515–543 Modbus Configuration and Identification
544–577 Diagnostics Counters and Modbus Password
661–664 Cradle Status
679–715 Time-Stamping of Last Status Changes

NOTE: More detailed information on these registers is presented in the Appendix,

Table of Registers, “Cradle Communication Module @ Address xx + 50” on
page 92.
Metering Module: @ Address xx + 200
The metering module prepares the electrical values used to manage the low-
voltage distribution system.
Every second, the metering module refreshes the “real-time” RMS measurements.
Using this data, it then calculates the demand and energy values, and stores the
minimum / maximum values recorded since the last reset.
Metering-module operation depends on the Micrologic settings:
• type of neutral (internal, external, none),
• the normal direction for the flow of active power
(this setting determines the sign of the measured power),
• voltage-transformation ratio,
• rated frequency.
The metering module must be set independently of the protection module to
determine:
• the calculation mode for the power (type of distribution system),
• the calculation mode for the power factor (IEEE®, IEEE alt., IEC).

24 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 2—Communication Architecture Four-Wire Modbus® Communications System

Table 4 – Metering Module Registers

ENGLISH
Register
Description Details
Range
1000–1299 Real-Time Measurements The metering module refreshes the real-time measurements every second.
The minimum values for real-time measurements may be accessed at the registers of the real-time values
+ 300.
All the minimum values are stored in memory and may be reset to zero, group by group according to
the list below, by the command interface:
• RMS current,
• current unbalance,
• RMS voltage,
• voltage unbalance,
Minimum Values for the • frequency,
1300–1599 Real-Time Measurements • power,
from 1000 to 1299 • power factor,
• fundamental,
• total harmonic distortion,
• voltage crest factor,
• current crest factor.
NOTE:
The minimum and maximum values of the real-time measurements are stored in the memory.
They may be reset to zero.
The maximum values of the demand measurements are time stamped and stored in memory.
They may be reset to zero.
The maximum values for the real-time measurements may be accessed at the registers of the real-
time values + 600.
All the maximum values are stored in memory and may be reset to zero, group by group according to
the list below, by the command interface:
• RMS current,
• current unbalance,
Maximum Values for the • RMS voltage,
1600–1899 Real-Time Measurements • voltage unbalance,
from 1000 to 1299 • frequency,
• power,
• power factor,
• fundamental,
• total harmonic distortion,
• voltage crest factor,
• current crest factor.
The energy counters may be:
• reset to zero,
2000–2199 Energy Measurements
• preloaded with an initial value,
using the reset applications via the command interface.
The demand values are refreshed every 15 seconds for sliding windows or at the end of the time
2200–2299 Demand Values interval for block windows. When block windows are used, an estimation of the value at the end of the
time interval is calculated every 15 seconds.
The time-stamping function becomes useful once the time and date have been set on the Micrologic
control unit, either locally or via the communication network.
If power to the Micrologic control unit is cut, the time and date must be set again. With firmware
release “logic 2002 AA” and above, the clock is powered by the battery. So, it is no more necessary to
3000–3299 Time-Stamping
set time and date after power comes off on the Micrologic control unit.
If power to the communication option is cut, the time and date must be set again. The maximum drift
of the Micrologic clock is approximately 0,36 seconds per day. To avoid any significant drift, the clocks
must be periodically synchronized via the communication network.
Configuration of the Metering The configuration registers may be read at all times. The registers may be modified via the command
3300–3999
Module interface in configuration mode.
4000–4099 Reserved

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 25

 Four-Wire Modbus® Communications System Section 2—Communication Architecture

Table 4 – Metering Module Registers (continued)

Register
ENGLISH

Description Details
Range
• RMS / phase of voltage harmonic,
4100–5699 Spectral Components
• RMS / phase of current harmonic.
The alarms registers may be read at all times. The registers may be modified via the command
Analog Pre-Defined Alarm
5700–6899 interface in configuration mode. These alarms (available with Micrologic H only) can be used to trigger
(1 to 53)
wave form capture.
File Header / Status (See Event log configuration / characteristics and format of records
7100–7499
“Access to Files” on page 35) for:
Wave Form Capture (file n° 5)
Event Log of the Metering Module (file n° 10)
Min-Max Event Log (file n° 11)
Maintenance Event Log of the Metering Module (file n° 12)

NOTE: More detailed information on these registers is presented in the Appendix,

Table of Registers, “Metering Module @ Address xx + 200” on page 95.

Protection Module: @ Address xx + 100

The protection module ensures the critical circuit breaker functions. The Micrologic
control unit was designed to make this module completely independent to minimize
any issues with the protection functions of the trip units.
It does not use the measurements generated by the metering module, but rather
calculates the protection-function inputs and outputs itself. This ensures extremely
fast reaction times.
The protection module manages:
• the basic protection: the long-time (LT), short-time (ST), instantaneous and
ground-fault current protection functions,
• the advanced protection: currents Imax, Iunbal, voltages Vmax, Vmin and Vunbal,
frequency Fmax and Fmin, maximum reverse power Rpmax, phase rotation .
The protection module controls:
• the automatic load shedding and reconnection functions, depending on current
and power,
• the optional M2C and M6C contacts.
Remote access to the protection module depends on the parameters set locally on
the Micrologic control unit and on the position of the protective cover for the
settings.
A local operator may disable all remote access to the protection module. It is also
possible to limit access to certain users by setting up a password on the Micrologic
control unit.
A protection function intended to trip the circuit breaker cannot be modified if the
protective cover is closed, with or without the password.

26 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 2—Communication Architecture Four-Wire Modbus® Communications System

Table 5 – Protection Module Registers

ENGLISH
Register Range Description
8750–8753 Characteristics of the Protection Module
Fine Settings for the Long-Time, Short-Time, Instantaneous, Ground-Fault and
8754–8803
Earth-Leakage Protection Functions
8833–8842 Measurements Carried Out by the Protection Module
8843–8865 Status of the Protection Module
9000–9599 Time-Stamping and Trip / Alarm History
9600–9628 Micrologic Configuration
9629–9799 Advanced Protection Settings
9800–9899 Relay Configuration (M2C / M6C)
Event Log (See Section: “Access to Files” on page 35)
9900–9924
File N° 20
Maintenance Event Log (See Section: “Access to Files” on page 35)
9932–9956
File N° 12
Fault Wave Form Capture (See Section: “Access to Files” on page 35)
9964–9989
File N° 22

NOTE: More detailed information on these registers is presented in the Appendix,

Table of Registers, “Protection Module @ Address xx + 100” on page 116.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 27

 Four-Wire Modbus® Communications System Section 3—Command Interface

Section 3— Command Interface

ENGLISH

Operating Principle
Write-access to Micrologic data and control-unit options is monitored to inhibit
accidental operation and operation by unauthorized persons.
Commands sent to Micrologic control units are carried out using a command
interface.
The command interface manages transmission and execution of the various
commands using the registers numbered from 7700 to 7729 that may be accessed
by the Modbus read and write functions.
The breaker communication module supports the command interface for the
commands intended for the circuit breaker, measurement, and protection modules.
The cradle communication module supports its own command interface.
Table 6: Command Interface

Slave @ xx Slave @ xx+50

[breaker communication module] [cradle communication module]

Command Interface 7700 to 7729 Command Interface 7700 to 7729

Commands Intended for the Commands Intended for the
Breaker Communication Module Cradle Communication Module Only
Commands Intended for the
—
Protection Module
Commands Intended for the
—
Metering Module

The command interface offers two command modes:

• Shared Mode:
This mode may be used to send up to 20 commands in series. It returns
exclusively the indications on command transmission via the Modbus protocol.
This mode does not return the result of command execution.
• Protected Mode:
This mode may be used to monitor execution of a command and to manage
access by a number of supervisors to a single circuit breaker. This is the case
for the Modbus multi-master architectures on Ethernet TCP / IP.
When a command is written, the command interface updates its registers with
information on command execution. It is necessary to wait until the command is
terminated before sending the next command.
(Recommended time-out is 500 ms.)
Furthermore, when the command is terminated, it is necessary to respect a
delay before sending the next command.
(Recommended delay is 20 ms.)
Access control is achieved by a flag reservation and freeing mechanism. In
protected mode, a command may be issued only after receiving a flag.
NOTE: Certain commands may be accessed only in protected mode. See “List of
Commands” on page 156 to determine the possible command-management
modes.

28 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 3—Command Interface Four-Wire Modbus® Communications System

Table 7 – Command Interface Registers

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
command interface in shared mode—
7700 10 R/W — — INT 0..65535 A P/H ShCmdIf
commands 1, 2
command interface in protected
7715 5 R — — INT 0..65535 A P/H PrCmdIfState
mode—state 1, 2
command interface in protected
7720 10 R/W — — INT 0..65535 A P/H PrCmdIf
mode—commands 1, 2
command interface in protected
7730 100 R — — INT 0..65535 A P/H PrCmdIfBuffer
mode—return 1, 2
1 See “Micrologic Command Interface for the Modbus Programmer”.
2 See “List of Commands” on page 156.

Send Commands in Shared Mode

The shared mode uses the registers numbered 7700 to 7709 in the command
interface:
Table 8 – Shared Mode Registers in the Command Interface

Registers Description
7700 Command Number
7701 Parameter P1
7702 Parameter P2
7703 Parameter P3
7704 Parameter P4
7705 Parameter P5
7706 Parameter P6
7707 Parameter P7
7708 Parameter P8
7709 Parameter P9

See the “List of Commands” on page 156 that may be accessed in shared mode
and the corresponding parameters in the section with the list of commands for
Micrologic control units.
Proceed in the following manner to send a command in shared mode.
1. Parameters
Fill in the command parameters in registers 7701 to 7709.
2. Write Command
Write the command number to register 7700 to initiate execution.
It is possible to optimize data flow on the communication system by using function
16 in the Modbus protocol. In this case, the data may be written to registers 7700 to
7709 in a single step. The circuit breaker communication option will automatically
put steps 1 and 2 in the correct order.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 29

 Four-Wire Modbus® Communications System Section 3—Command Interface

Send Commands in Protected Mode

ENGLISH

The protected mode uses the registers numbered 7715 to 7829 in the command
interface.

Registers 7715 to 7719: Table 9 – Protected Mode Registers in the Command Interface
May be read-accessed only Registers Description
and provide the indications
7715 Flag query.1
required to use the protected
7716 Flag active.2
mode.
7717 Number of the command being executed.3
7718 Number of the last command executed.4
7719 Result code of the last command executed.4
1 Register 7715 must be read-accessed to ensure it is 0, if it is not 0 then another user is in
configuration mode and you cannot proceed to the next step, see page 164.
2 The active flag indicates to a supervisor the number of the flag with current access rights to the
command interface in protected mode. Only the supervisor that was attributed the given number
during a flag query has the right to use the command interface in protected mode. The active flag
returns to 0 if no command is sent for two minutes or if the user returns the flag (see the command
table for information on return).
3 The number of the command currently being executed remains set to 0 as long as no command is
sent to 7720. As soon as a command is sent, register 7717 indicates the number of the command. It
returns to 0 when command execution is terminated.
4 When command execution is terminated, register 7718 receives the number of the command and
register 7719 indicates the result code. The contents of registers 7718 and 7719 are not modified until
the next command has been completely executed.

Register 7719: Table 10 – Command Result Codes

Command result codes table. Result Codes Description of Register 7719
0 Command successfully executed.
Command not executed, the necessary resources are not available or the
10
option is not installed or remote access = NO.
11 Command not executed, a local user is using the resources.
12 Command not executed, the portable test kit is using the local resources.
14 Command not executed, the resources are being used by a remote user.
15 Invalid record size.
16 Illegal file command.
17 Insufficient memory.
42 Invalid file number.
81 Command not defined.
82 Command parameters not set or invalid.
107 Invalid record number.
125 Invalid number of records.
200 Protected mode not active.
201 End of time delay. Command not executed.
202 Invalid password. Command not executed.

30 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 3—Command Interface Four-Wire Modbus® Communications System

Registers 7720 to 7729: Table 11 – Read-Accessed Commands

May be read-accessed. They

ENGLISH
Registers Description
are used to send parameters
7720 Command Number
and run execution of
7721 Parameter P1
commands in protected
7722 Parameter P2
mode.
7723 Parameter P3
7724 Parameter P4
7725 Parameter P5
7726 Parameter P6
7727 Parameter P7
7728 Parameter P8
7729 Parameter P9

See the “List of Commands” on page 156 that may be accessed in protected mode
and the corresponding parameters in the section with the list of commands for
Micrologic control units.
Command interface registers 7730–7829 may be read accessed. They are used as
a buffer for the returned data.
Proceed as follows to send a command in protected mode.
1. Request the Flag
Read register 7715 to ensure it is 0, if it is not 0 then another user is in
configuration mode and you cannot proceed to the next step, see page 164. It
is possible, however, that you already took the flag for another command and
did not return it. For example: if you wished to sequence sending of a series of
commands. It is possible to check if you have the rights by reading the active
flag at register 7716. In this case, even if you did not read 0 at 7715 when you
made the request, it is possible to send the commands.
2. Fill in Parameters
Fill in the command parameters (P1 to P9) in registers 7721 to 7729.
3. Write Command
Write the command number to register 7720 to initiate execution.
4. Wait for Command Execution
Wait until the command is fully terminated, by reading registers 7717 and 7718
(recommended time-out = 500 ms).
5. Check Result Code
Check the result code for the command by reading register 7719.
6. Send New Command
Send new commands in protected mode by starting with step 2 or go on to
step 7 (recommended delay between command fully terminated and new
command = 20 ms).
7. Release the Flag
Return the flag to free the protected mode. See the command table for
information on returning the flag.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 31

 Four-Wire Modbus® Communications System Section 3—Command Interface

Optimize Sending of Commands

ENGLISH

It is possible to optimize data flow on the communication system by using function

16 in the Modbus protocol. In this case, the data may be written to registers 7720 to
7729 in a single step. The command interface will automatically put steps 2 and 3
in the correct order.
NOTE: Do not use function 23 to optimize steps 1, 2 and 3, because this function
does not check access rights to protected mode before sending the command. This
may cause problems for another supervisor who currently has the access rights.
Most of the commands that may be used to remotely control the circuit breaker
implement two steps, namely the request for the flag (step 1) and return of the flag
(step 7).
This mechanism makes it possible for a number of supervisors to issue commands,
on the condition that the two steps be implemented.
Using this procedure, you take and return the flag for each of the commands to be
issued. In this case, the possible degree of parallelism between the various
supervisors is increased, but at the cost of more traffic on the communication
system.
If you have a number of commands to send, optimize the mechanism by sending
all the commands between the two steps; for example, request the flag, send all
the commands in one shot and then return the flag. In this case, you occupy the
command interface for a longer time, but traffic on the communication system is
optimized.

Remote Configuration
A number of simple concepts must be clear in order to remotely configure the
NOTE: Detailed information circuit breaker successfully.
on the registers is presented
in the Appendix containing • Configuration is carried out via the registers:
the “Table of Registers” on The configuration for all the modules (circuit breaker, cradle, measurements,
page 85. and protection functions) may be read-accessed in the table of registers.
The only way to remotely modify a configuration is to modify the contents of the
configuration registers.
• The table of registers may be write-accessed in configuration mode only:
To modify the configuration registers, it is necessary to remove the register
write-protect function by running the command required to enter configuration
mode, via the command interface. Once in configuration mode, it is possible to
write access the configuration registers and you may modify one or more
registers using the standard Modbus write functions.

Table 12: Breaker Communication Module Remote Configuration

Breaker Communication Module Slave @ xx

Regular Range Configuration Registers
534–543 Identification of the Breaker Communication Module

32 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 3—Command Interface Four-Wire Modbus® Communications System

Table 13: Cradle Communication Module Remote Configuration

ENGLISH
Cradle Communication Module Slave @ xx + 50
Regular Range Configuration Registers
534–543 Identification of the Cradle Communication Module

Table 14: Metering Module Remote Configuration

Metering Module Slave @ xx + 200

Regular Range Configuration Registers
3303–3355 Configuration of the Metering Module
6000–6011 Configuration of Analog Pre-Defined Alarm 1
6012–6635 Configuration of Analog Pre-Defined Alarm 2 to 53

Table 15: Protection Module Remote Configuration

Protection Module Slave @ xx + 100

Regular Range Configuration Registers
8753–8803 Fine Adjustments for the Basic Protection
9604–9618 Configuration of the Protection Module
9629–9798 Settings for the Advanced Protections
9800–9846 Configuration of the Output Relays (M2C / M6C)
xx = breaker communication module address.

Specific conditions must be met to enter the configuration mode.

Remote access is not possible if local configuration is underway and vise
versa.
When a user is in the process of locally modifying the configuration of Micrologic or
of its options, it is not possible to start a remote-configuration sequence.
Micrologic considers that a local user is in the process of modifying the
configuration when a parameter field is highlighted or as soon as the Micrologic
plastic cover is opened.
Access to configuration mode is subject to different restrictions depending
on the module.
Access to configuration mode for the protection module requires the remote-
access code that was programmed on the front panel of the Micrologic control unit.
This code may be obtained only via the setting screen on the Micrologic control unit
itself. It is only possible to access the configuration mode for the protection module
if the Micrologic control unit has been set to authorize remote access. This setting
must be made manually via the front panel of the Micrologic control unit. It is
possible to consult the protection module register 9800 to check the status of this
parameter.
Access to configuration mode for the breaker communication, cradle
communication and metering modules requires a check word that must first be
read in the table of registers. This two-step operation is intended to avoid
inadvertent access to the configuration mode.
The access commands for configuration mode implement the protected mode and
systematically inform on the command result.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 33

 Four-Wire Modbus® Communications System Section 3—Command Interface

New configurations are always checked before being accepted.

When writing in the configuration registers, the Modbus write functions are
ENGLISH

accepted, even if the written value exceeds the limits presented in the tables of
registers that should be consulted first.
To assist in configuring the protection functions, Micrologic provides access to a
set of registers that list the minimum and maximum permissible values for the
various protection settings.
All the configuration data entered are checked before they enter into effect. This
check is run when you exit configuration mode, using the commands Out_pCfg,
Out_mCfg or Out_CommCfg.
If one of the configuration settings is incorrect, all the new configuration data are
rejected. The system indicates why the data are rejected via the result returned for
the command used to exit the configuration mode. The protection module indicates
the first ten faulty configuration registers. See the information on command
Out_pCfg for further details.
The new configuration data take effect only on exiting configuration mode.
The new configuration data take effect only on exiting configuration mode so that
the data can be checked; for example, it is when the Out_pCfg, Out_mCfg or
Out_CommCfg command has been successfully run that the new configuration
settings become active.
Example of a Remote Parameter-Setting Sequence
Below are the steps that must be followed to modify the long-time (LT) current
setting.
1. Check that remote access is authorized by reading register 9800 at address
@+100 [protection module].
2. Make sure you have the remote-access code, noted on the “Local / Remote”
screen in the “COM setup” menu of Micrologic.
3. Enter configuration mode for the protection module, using the In_pCfg
command. See the Appendix, “Examples of Commands” on page 163.
4. Enter the new setting in registers 8753 to 8803, at the address @+100
[protection module]. Make sure these new settings are below the value set by
the rotary switch.
5. Exit configuration mode for the protection module, using the Out_pCfg
command, and check first for an error code returned by the command interface,
then the parameters returned by Out_pCfg in registers 7730 to 7739 of the
circuit breaker command interface.
6. Read the contents of the registers 8756 and 8757. The settings should be
those entered, if step 5 did not return an error.

34 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

Section 4— Access to Files

ENGLISH
Introduction
Micrologic stores events and wave form in different files. These files may be read
with the command interface: ReadFileX_RecY. The requested recording may be
read starting in registers 7730.
See the Appendix, “Examples of Commands” on page 163.
A file is made up of records. All records in a file have the same structure and size.
Each file is linked to a descriptor. The descriptor is made up of a read zone for file
configuration (Header) and for file characteristics (Status). Descriptors are updated
each time new data is added to the file.
The file configuration (Header) gives information about size of file and records. The
file characteristics (Status) gives information about record numbers. The file
characteristics (Status) makes available to the supervisor two sequence registers
that indicate the first and last events recorded in the file. They enable the
supervisor to determine whether certain events were deleted before they could be
read. The sequence number for the last event increments from 1 to 8000 each time
a new event is recorded. When the file is full (maximum of 100), the new events
overwrite the oldest events. The sequence number for the last event continues to
increment normally. When the oldest event is overwritten, the sequence number for
the first event also increments.
When the sequence number reaches 8000, the next sequence number will be one.

Event Logs
The system stores the events that concern circuit breaker control
Breaker (for example: opening or closing of the contacts) in the file N° 30.
Communication Micrologic A / P / H
This file is made up of 100 records, each record is made up of 5 registers.
Module @ xx
This file is reset in case of 24 vdc power loss to the breaker communication module.
The system stores the events that concern the protection module
Event Logs Protection Module
Micrologic P / H (for example: trips, alarms) in the file N° 20.
@ xx + 100
This file is made up of 100 records, each record is made up of 9 registers.
The system stores the events that concern the metering module
Metering Module (for example: analog pre-defined alarms 1 to 53) in the file N° 10.
Micrologic H
@ xx + 200
This file is made up of 100 records, each record is made up of 9 registers.
The system stores the events that concern the maintenance protection module (for
example: power-up, M6C relays, max. peak fault current, and so on) in the file N° 21.
Protection Module
Micrologic H This file is made up of 20 records, each record is made up of 6 registers.
@ xx + 100
Maintenance This maintenance event log has been implemented as well on Micrologic P with
Event Logs firmware Plogic2002AA and above.
The system stores the events that concern the maintenance metering module (for
Metering Module example: counter reset, and so on) in the file N° 12.
Micrologic H
@ xx + 200
This file is made up of 20 records, each record is made up of 6 registers.
The system stores the events that concern the metering module (for example:
Min-Max Event Metering Module minimum and maximum values for the real time measurements 1000 to 1136) in the
Micrologic H file N° 11.
Log @ xx + 200
This file is made up of 136 records, each record is made up of 8 registers.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 35

 Four-Wire Modbus® Communications System Section 4—Access to Files

Wave Form Capture (WFC)

ENGLISH

The system stores the variables Va, Vb, Vc, Ia, Ib, Ic, Ineutral, during 4 cycles (64
points per cycles) in the file N° 5.
In the Metering The capture is triggered:
Wave Form
Module Micrologic H
Capture • manually (user request) by using the command “Forcelog“ (see the Appendix,
@ xx + 200 “Metering Module Commands @ Address xx + 200” on page 159),
• automatically attached to pre-defined analog alarms (1 to 53) by setting the log
action to 1 (see register 6010 for alarm N° 1, register 6634 for alarm N° 53).
The system stores the variables Va, Vb, Vc, Ia, Ib, Ic, Ineutral, during 12 cycles (16
points per cycles) in the file N° 22.
Fault Wave Form In the Protection
Micrologic H The capture is triggered:
Capture Module @ xx + 100
• automatically attached to alarms (1000 to 1030) by setting the log action to 1
(see register 8762 for alarm N° 1000, register 9797 for alarm N° 1030).

Event Log of the Breaker Communication Module @ Address xx

Table 16 – Descriptor of the Event Log in the Breaker Communication Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Event Log Configuration (HEADER)
File status.
NvCMFilHdrEvtLog
718 1 R — — INT 0xFFFF A P / H 0xFFFF: file enabled.
CtrlReg
Always equal to: 0xFFFF.
Type of file.
Event log of the NvCMFilHdrEvtLog
719 1 R — — INT 30 A P / H Breaker Communication Module.
FileType
Always equal to: 30.
File allocation.
NvCMFilHdrEvtLog
720 1 R — — INT 0xFFFF A P / H 0xFFFF: file allocated.
Allocation
Always equal to: 0xFFFF.
Size of records in register. NvCMFilHdrEvtLog
721 1 R x1 register INT 5 A P/H
Always equal to: 5. RecSize
File filling mode.
NvCMFilHdrEvtLog
722 1 R — — INT 0 A P / H 0: circular.
Mode
Always equal to: 0.
Event Log Characteristics (STATUS)
Size of file in records. NvCMFilStatusEvtLo
734 1 R x1 rec. INT 100 A P/H
Always equal to: 100. g_ AllocFileSize
Size of a record in registers. NvCMFilStatusEvtLo
735 1 R x1 register INT 5 A P/H
Always equal to: 5. g_ AllocRecSize
Number of records in the file. NvCMFilStatusEvtLo
737 1 R x1 rec. INT 0..100 A P/H
0: no record in the file. g_ NbOfRecords
Sequence number of first record in
NvCMFilStatusEvtLo
738 1 R x1 rec. INT 0..8000 A P / H the file (the oldest).
g_ FirstRecNum
0: no record in the file.
Sequence number of last record in
NvCMFilStatusEvtLo
739 1 R x1 rec. INT 0..8000 A P / H the file (the most recent).
g_ LastRecNum
0: no record in the file.
NvCMFilStatusEvtLo
740 3 R — — DATE — — P / H Date the last file was reset.
g_ LastResetTime

36 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

Table 17 – Format of Records in the Event Log of the Breaker

Communication Module

ENGLISH
Registers Description
Event date, in the XDATE format
1–4
(see the appendix, “Formats” on page 81).
5 Event number (see below).

Table 18 – Events in the Event Log of the Breaker Communication Module

Event Number Description

1 RESET or system energized.
2 Configuration data stored in the cradle communication module.
3 Spring charged.
4 Circuit breaker opened (O).
5 Circuit breaker closed (F).
6 Circuit breaker tripped (SD).
7 Circuit breaker fault tripped (SDE).
8 Reserved.
9 Reserved.
10 Closing command input remotely (AUTO) (XF).
11 Opening command input remotely (AUTO) (MX).
12 Modification of Modbus address.
13 Event log reset.
14 Clock update input locally accepted.
Clock update input locally rejected
15
(synchronization by the supervisor).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 37

 Four-Wire Modbus® Communications System Section 4—Access to Files

Event Log of the Protection Module @ Address xx + 100

ENGLISH

Table 19 – Descriptor of the Event Log in the Protection Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Event Log Configuration (Header)
File status.
0x0000, • 0xFFFF: file enabled. NvPMFilHdrEvtLog
9900 1 R/W — — INT — P/H
0xFFFF • 0: file disabled. CtrlReg
Default value: 0xFFFF.
Type of file.
NvPMFilHdrEvtLog
9901 1 R — — INT 20 — P / H Protection Module event log.
FileType
Always equal to: 20.
Size of file in records. NvPMFilHdrEvtLog
9902 1 R x1 rec. INT 100 — P/H
Always equal to: 100. Allocation
Size of a record in registers.
NvPMFilHdrEvtLog
9903 1 R x1 register INT 9 — P / H Always equal to: 9 registers per
RecSize
record.
File filling mode 0: circular. NvPMFilHdrEvtLog
9904 1 R — — INT 0 — P/H
Always equal to: 0. Mode
Event Log Characteristics (Status)
Size of file in records. NvPMFilStatusEvtLog
9916 1 R x1 rec. INT 100 — P/H
Always equal to: 100. _ AllocFileSize
Size of a record in registers. NvPMFilStatusEvtLog
9917 1 R x1 register INT 9 — P/H
Always equal to: 9. _ AllocFileSize
• 0: file OK.
• 10: record size smaller than
expected.
0, 10, 20, • 20: record size larger than
30, 250, expected.
253, 254, • 30: insufficient memory.
255, • 250: internal error. NvPMFilStatusEvtLog
9918 1 R x1 — INT — P/H
0xFF00, • 253: corrupted allocation table. _ FileStatus
0xFE00, • 254: configuration zero.
0xFD00, • 255: invalid configuration.
0xFC00 • 0xFF00: cannot allocate file.
• 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Number of records in the file. NvPMFilStatusEvtLog
9919 1 R x1 rec. INT 0..100 — P/H
0: no record in the file. _ NbOfRecords
Sequence number of first record in
NvPMFilStatusEvtLog
9920 1 R x1 rec. INT 0..8000 — P / H the file (the oldest).
_ FirstRecNum
0: no record in the file.
Sequence number of last record in
NvPMFilStatusEvtLog
9921 1 R x1 rec. INT 0..8000 — P / H the file (the most recent).
_ LastRecNum
0: no record in the file.
Date the last file was reset.
NvPMFilStatusEvtLog
9922 3 R — — DATE cfformat — P / H Default value: 0x8000 0x8000
_ LastResetTime
0x8000.

38 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

Table 20 – Format of Records in the Event Log of the Protection Module

ENGLISH
Registers Description
1–4 Event date, in the XDATE format (see the Appendix, “Formats” on page 81).
5 Event number (see below).
6 Event characteristics.1
7 Type of event.2
8 Logging bitmap associated to the alarm.3
9 Action bitmap associated to the alarm.3
1For alarms 1000 to 1004, the data is the value of the fault current interrupted by the circuit breaker. For
all other events, this value is forced to 32768.
2Bits 0 to 7
The value 1 indicates an alarm of the “Over” type.
The value 2 indicates an alarm of the “Under” type.
The value 3 indicates an alarm of the “Minimum” type.
The value 4 indicates an alarm of the “Maximum” type.
The value 5 indicates an alarm of the “Assorted” type.
2Bits 8 to 11
The value 1 indicates the start of an alarm.
The value 2 indicates the end of an alarm.
2Bits 12 to 15
Alarms 1100 to 1106 are priority 3. For the other alarms, the value contained in these four bits
represents the priority linked to the event (if applicable and depending on the alarm configuration.
3Registers 8 and 9 are a copy of the alarm-configuration registers at the moment the event occurred.
They depend entirely on the user configurations. For the events 1100 to 1106, these registers are
forced to 32768.

Table 21 – Events in the Event Log of the Protection Module

Event Number Description

1000..1015 Basic protection1
1016..1031 Advanced protection1
1100..1115 Digital alarms1
1See description of the “Alarm Numbers” in the Appendix, “Trip / Alarm History” on page 82.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 39

 Four-Wire Modbus® Communications System Section 4—Access to Files

Event Log of the Metering Module @ Address xx + 200

ENGLISH

Table 22 – Descriptor of the Event Log in the Metering Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Event Log Configuration (HEADER)
Log status.
0x0000, • 0xFFFF: file enabled. NvMMFilHdrEvtLog
7164 1 R/W — — INT — H
0xFFFF • 0: file disabled. CtrlReg
Default value: 0xFFFF.
Type of file:
Metering Module event log. NvMMFilHdrEvtLog
7165 1 R — — INT 10 — H
FileType
Default Value: 10.
Size of file in records. NvMMFilHdrEvtLog
7166 1 R x1 rec. INT 100 — H
Default Value: 100 records per file. Allocation
Size of a record in registers. NvMMFilHdrEvtLog
7167 1 R x1 register INT 9 — H
Default Value: 9 registers per record. RecSize
File filling mode.
0: circular. NvMMFilHdrEvtLog
7168 1 R — — INT 0 — H
Mode
Always equal to: 0.
Event Log Characteristics (STATUS)
Size of file in records: 100. NvMMFilStatusEvtLog
7180 1 R x1 rec. INT 100 — H
Always equal to: 100. _ AllocFileSize
Size of a record in registers. NvMMFilStatusEvtLog
7181 1 R x1 register INT 9 — H
Always equal to: 9. _ AllocRecSize
• 0: file OK.
• 10: record size smaller than
expected.
0, 10, 20, • 20: record size larger than
30, 250, expected.
253, 254, • 30: insufficient memory.
255, • 250: internal error. NvMMFilStatusEvtLog
7182 1 R x1 — INT — H
0xFF00, • 253: corrupted allocation table. _ FileStatus
0xFE00, • 254: configuration zero.
0xFD00, • 255: invalid configuration.
0xFC00 • 0xFF00: cannot allocate file.
• 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Number of records in the file. NvMMFilStatusEvtLog
7183 1 R x1 rec. INT 0..100 — H
0: no record in the file. _ NbOfRecords
Sequence number of first record in
the file (the oldest). NvMMFilStatusEvtLog
7184 1 R x1 rec. INT 0..8000 — H
_ FirstRecNum
0: no record in the file.
Sequence number of last record in
the file (the most recent). NvMMFilStatusEvtLog
7185 1 R x1 rec. INT 0..8000 — H
_ LastRecNum
0: no record in the file.
Date the last file was reset.
NvMMFilStatusEvtLog
7186 3 R — — DATE cfformat — H Default value: 0x8000 0x8000 _ LastResetTime
0x8000.

40 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

Table 23 – Format of Records in the Event Log of the Metering Module

ENGLISH
Registers Description
1–3 Event date, in the XDATE format (see the Appendix, “Formats” on page 81).
4 Reserved.
5 Event number (see below).
6 Extreme value.
7 Type of event.1
8 Logging bitmap associated to the alarm.2
9 Action bitmap associated to the alarm.2
1Bits 0 to 7
The value 0 indicates an alarm of the “Over” type.
The value 1 indicates an alarm of the “Under” type.
The value 2 indicates an alarm of the “Equal to” type.
The value 3 indicates an alarm of the “Different from” type.
The value 5 is used for all other alarms.
1Bits 8 to 11
The value 1 indicates the start of an alarm.
The value 2 indicates the end of an alarm.
1Bits 12 to 15
The value contained in these four bits represents the priority linked to the event (if applicable and
depending on the alarm configuration.
2Registers 8 and 9 are a copy of the alarm-configuration registers at the moment the event
occurred. They depend entirely on the user configurations.

Table 24 – Events in the Event Log of the Metering Module

Event Number Description

1 to 53 Analog pre-defined alarms.
See the “Analog Pre-Defined Alarms” on page 112, 1 to 53 in the Appendix, Table of Registers 6000 to
6624.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 41

 Four-Wire Modbus® Communications System Section 4—Access to Files

Maintenance Event Logs of the Protection Module

@ Address xx + 100
ENGLISH

Table 25 – Descriptor of the Maintenance Event Log in the Protection Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Event Log Configuration (HEADER)
File status.
NvPMFilHdrMaint
9932 1 R/W — — INT 0xFFFF — H 0xFFFF: file enabled.
CtrReg
Always equal to: 0xFFFF.
Type of file.
Maintenance Protection Module NvPMFilHdrMaint
9933 1 R — — INT 21 — H event log. FileType
Always equal to: 21.
Size of file in records. NvPMFilHdrMaint
9934 1 R x1 rec. INT 20 — H
Always equal to: 20 records per file. Allocation
Size of a record in registers.
NvPMFilHdrMaint
9935 1 R x1 register INT 6 — H Always equal to: 6 registers per RecSize
record.
Log filling mode.
1: inhibition is full. NvPMFilHdrMaint
9936 1 R — — INT 1 — H
Mode
Always equal to: 1.
Event Log Characteristics (STATUS)
Size of file in records: 20. NvPMFilStatusMaint
9948 1 R x1 rec. INT 20 — H
Always equal to: 20. _ AllocFileSize
Size of a record in registers. NvPMFilStatusMaint
9949 1 R x1 register INT 6 — H
Always equal to: 6. _ AllocRecSize
• 0: file OK.
• 10: record size smaller than
expected.
0, 10, 20, • 20: record size larger than
30, 250, expected.
253, 254, • 30: insufficient memory.
255, • 250: internal error. NvPMFilStatusMaint
9950 1 R x1 — INT — H
0xFF00, • 253: corrupted allocation table. _ FileStatus
0xFE00, • 254: configuration zero.
0xFD00, • 255: invalid configuration.
0xFC00 • 0xFF00: cannot allocate file.
• 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Number of records in the file. NvPMFilStatusMaint
9951 1 R x1 rec. INT 20 — H
Always equal to: 20. _ NbOfRecords
Sequence number of first record in
the file. NvPMFilStatusMaint
9952 1 R x1 rec. INT 1 — H
_ FirstRecNum
Always equal to: 1.
Sequence number of last record in
the file. NvPMFilStatusMaint
9953 1 R x1 rec. INT 20 — H
_ LastRecNum
Always equal to: 20.
Date the last file was reset.
NvPMFilStatusMaint
9954 3 R — — DATE cfformat — H Default value: 0x8000 0x8000 _ LastResetTime
0x8000.

42 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

This file consists of a fixed number of records (20). All records are of similar size,
for example, 6 registers wide.

ENGLISH
Table 26 – Format of Records in the Maintenance Event Log of the
Protection Module

Record
Registers Description
Number
1–3 Last power loss (XDATE format).
1
4–6 Reserved.
1–3 Date / time of last counter reset (DATE format).
2 4 Number of output operations for relay 1.
5–6 Reserved.
1–3 Date / time of last counter reset (DATE format).
3 to 6 4 Number of output operations for relay 3 to 6.
5–6 Reserved.
1–3 Date / time of last counter reset (DATE format).
7 4 Number of output operations for relay 6.
5–6 Reserved.
1–3 Date / time of last record updated (DATE format).
8 4 Worst contact wear.
5–6 Reserved.
1–3 Date / time of last record updated (DATE format).
9 4 Max reverse power.
5–6 Reserved.
1–3 Date / time of last record updated (DATE format).
10 4 Battery indicator (see register 8843).
5–6 Reserved.
1–3 Date / time of last record updated (DATE format).
11 4 Number of power losses.
5–6 Reserved.
12 1–6 Reserved.
13 1–6 Reserved.
14 1–6 Reserved.
15 1–6 Reserved.
1–3 Date / time of last record updated (DATE format).
16 4 Number of Max resets.
5–6 Reserved.
17 1–6 Reserved.
1–3 Date / time of last record updated (DATE format).
18 4 Max peak fault current circuit breaker ever opened.
5–6 Reserved.
19 1–6 Reserved.
20 1–6 Reserved.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 43

 Four-Wire Modbus® Communications System Section 4—Access to Files

Maintenance Event Log of the Metering Module

ENGLISH

Table 27 – Descriptor of the Maintenance Event Log in the Metering Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Event Log Configuration (HEADER)
File status.
NvMMFilHdrMaint
7228 1 R/W — — INT 0xFFFF — H 0xFFFF: file enabled.
CtrReg
Always equal to: 0xFFFF.
Type of file.
Maintenance Metering Module event NvMMFilHdrMaint
7229 1 R — — INT 12 — H log. FileType
Always equal to: 12.
Size of file in number of records. NvMMFilHdrMaint
7230 1 R x1 rec. INT 20 — H
Always equal to: 20 records per file. Allocation
Size of a record in number of
registers. NvMMFilHdrMaint
7231 1 R x1 register INT 6 — H
Always equal to: 6 registers per RecSize
record.
Log filling mode.
1: disabled if log is full. NvMMFilHdrMaint
7232 1 R — — INT 1 — H
Mode
Always equal to: 1.
Event Log Characteristics (STATUS)
Size of file in records: 20. NvMMFilStatusMaint
7244 1 R x1 rec. INT 20 — H
Always equal to: 20. _ AllocFileSize
Size of a record in registers. NvMMFilStatusMaint
7245 1 R x1 register INT 6 — H
Always equal to: 6. _ AllocFileSize
• 0: file OK.
• 10: record size smaller than
expected.
0, 10, 20, • 20: record size larger than
30, 250, expected.
253, 254, • 30: insufficient memory.
255, • 250: internal error. NvMMFilStatusMaint
7246 1 R x1 — INT — H
0xFF00, • 253: corrupted allocation table. _ FileStatus
0xFE00, • 254: configuration zero.
0xFD00, • 255: invalid configuration.
0xFC00 • 0xFF00: cannot allocate file.
• 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Number of records in the file. NvMMFilStatusMaint
7247 1 R x1 rec. INT 20 — H
Always equal to: 20. _ NbOfRecords
Sequence number of first record in
the file. NvMMFilStatusMaint
7248 1 R x1 rec. INT 1 — H
_ FirstRecNum
Always equal to: 1.
Sequence number of last record in
the file. NvMMFilStatusMaint
7249 1 R x1 rec. INT 20 — H
_ LastRecNum
Always equal to: 20.
Date the last file was reset.
NvMMFilStatusMaint
7250 3 R — — DATE cfformat — H Default value: 0x8000 0x8000 _ LastResetTime
0x8000.

44 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

This file consists of a fixed number of records (20). All records are of similar size,
for example, 6 registers wide.

ENGLISH
Table 28 – Format of Records in the Maintenance Event Log of the Metering
Module

Record
Registers Description
Number
1–3 Date / time of last counter reset (DATE format).
1 4 Number of min resets.
5–6 Reserved.
1–3 Date / time of last counter reset (DATE format).
2 4 Number of Max resets.
5–6 Reserved.
1–3 Date / time of last counter reset (DATE format).
3 4 Number of Peak current Demand resets.
5–6 Reserved.
1–3 Date / time of last record updated (DATE format).
4 4 Number of Peak power demand resets.
5–6 Reserved.
1–3 Date / time of last record updated (DATE format).
5 4 Number of Energy resets.
5–6 Reserved.
6 to 20 1–6 Reserved.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 45

 Four-Wire Modbus® Communications System Section 4—Access to Files

Min-Max Event Log of the Metering Module @ Address xx + 200

ENGLISH

Table 29 – Descriptor of the Min-Max Event Log in the Metering Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Event Log Configuration (HEADER)
File status.
NvMMFilHdrMinMax
7196 1 R/W — — INT 0xFFFF — H 0xFFFF: file enabled.
CtrlReg
Always equal to: 0xFFFF.
Type of file:
Min / Max event log: 11. NvMMFilHdrMinMax
7197 1 R — — INT 11 — H
FileType
Always equal to: 11.
Size of file in number of records.
Real Time Identical to: NvMMFilHdrMinMax
7198 1 R x1 rec. INT — H
zone size the size of the MM Real Time zone. Allocation
Always equal to: 136.
Size of a record in number of registers.
NvMMFilHdrMinMax
7199 1 R x1 register INT 8 — H Always equal to: 8 registers per RecSize
record.
Log filling mode.
1: disabled if log is full. NvMMFilHdrMinMax
7200 1 R — — INT 1 — H
Mode
Always equal to: 1.
Event Log Characteristics (STATUS)
Size of file in records.
Real Time Size always equal to: NvMMFilStatusMinMax
7212 1 R x1 rec. INT — H
zone size Real Time zone size. _ AllocFileSize
Value equal to: 136.
Size of a record in registers. NvMMFilStatusMinMax
7213 1 R x1 register INT 8 — H
Always equal to: 8. _ AllocRecSize
• 0: file OK.
• 10: record size smaller than
expected.
0, 10, 20, • 20: record size larger than
30, 250, expected.
253, 254, • 30: insufficient memory.
255, • 250: internal error. NvMMFilStatusMinMax
7214 1 R x1 — INT — H
0xFF00, • 253: corrupted allocation table. _ FileStatus
0xFE00, • 254: configuration zero.
0xFD00, • 255: invalid configuration.
0xFC00 • 0xFF00: cannot allocate file.
• 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Actual number of records in the file.
Real Time Always equal to: NvMMFilStatusMinMax
7215 1 R x1 rec. INT — H
zone size Real Time zone size. _ NbOfRecords
Value equal to: 136.
Number of first record present. NvMMFilStatusMinMax
7216 1 R x1 rec. INT 1 — H
Always equal to: 1. _ FirstRecNum

Real Time Number of first record present. NvMMFilStatusMinMax

7217 1 R x1 rec. INT — H
zone size Always equal to: 20. _ LastRecNum
Date the last file was reset. NvMMFilStatusMinMax
7218 3 R — — DATE cfformat — H
Default value: 0x8000 0x8000 0x8000. _ LastResetTime

46 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

This file contains the minimum and maximum values reached by the Real Time

ENGLISH
measurements.

Real Time Value: see registers 1000 to 1135.

Min of Real Time Value: see registers 1300 to 1435.
Max of Real Time Value: see registers 1600 to 1735.
All records are of similar size, for example, 8 registers wide.

Table 30 – Format of Records in the Min-Max Even Log of the Metering

Module

Record
Registers Description
Number
1 Last min value (register 1300).
2–4 Date / time of last min value (DATE format).
1
5 Last max value (register 1600).
6–8 Date / time of last max value (DATE format).
1 Last min value (register 1301).
2–4 Date / time of last min value (DATE format).
2
5 Last max value (register 1601).
6–8 Date / time of last max value (DATE format).
1 Last min value (register 130x).
2–4 Date / time of last min value (DATE format).
X (3 to 135)
5 Last max value (register 160x).
6–8 Date / time of last max value (DATE format).
1 Last min value (register 1435).
2–4 Date / time of last min value (DATE format).
136
5 Last max value (register 1735).
6–8 Date / time of last max value (DATE format).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 47

 Four-Wire Modbus® Communications System Section 4—Access to Files

Wave Form Capture

ENGLISH

Table 31 – Descriptor of the Wave Form Capture in the Metering Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Wave Form Capture Configuration (HEADER)
File status.
0x0000, • 0xFFFF: file enabled. NvMMFilHdrWFC
7132 1 R/W — — INT — H
0xFFFF • 0x000: file disabled. CtrlReg
Default value: 0xFFFF.
Type of file:
Wave Form Capture. NvMMFilHdrWFC
7133 1 R — — INT 5 — H
FileType
Always equal to: 5 (WFC).
Size of file in number records: 29. NvMMFilHdrWFC
7134 1 R x1 rec. INT 29 — H
Always equal to: 29 records / file. Allocation
Size of records in number of registers. NvMMFilHdrWFC
7135 1 R x1 register INT 64 — H
Always equal to: 64 registers per record. RecSize
File filling mode.
1: disabled if log is full. NvMMFilHdrWFC
7136 1 R — — INT 0,1 — H 0: circular. Mode
Default value: 0.
NvMMFilHdrWFC
Number of 4 cycle segments.
7137 — R 1 segment INT 1 — H MaxNumOfSegment
Always equal to: 1.
s
Number of cycle before capture. NvMMFilHdrWFC
7138 — R 1 cycle INT 2 — H
Always equal to: 2. PreAlarmCycles
Number of points per cycle. NvMMFilHdrWFC
7139 — R 1 points INT 64 — H
Always equal to: 64. PointsPerCycle
Wave Form Capture Characteristics (STATUS)
Size of file in records. NvMMFilStatusWFC
7148 1 R x1 rec. INT 0,29 — H
Either equal to: 0 or 29. _ AllocFileSize
Size of a record in registers. NvMMFilStatusWFC
7149 1 R x1 register INT 64 — H
Always equal to: 64. _ AllocRecSize
• 0: file OK.
• 10: record size smaller than
expected.
0, 10, 20,
• 20: record size larger than expected.
30, 250,
• 30: insufficient memory.
253, 254,
• 250: internal error.
255, NvMMFilStatusWFC
7150 1 R x1 — INT — H • 253: corrupted allocation table.
0xFF00, _ FileStatus
• 254: configuration zero.
0xFE00,
• 255: invalid configuration.
0xFD00,
• 0xFF00: cannot allocate file.
0xFC00
• 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Actual number of records in the file. NvMMFilStatusWFC
7151 1 R x1 rec. INT 0,29 — H
Either equal to: 0 or 29. _ NbOfRecords
Number of first record present. NvMMFilStatusWFC
7152 1 R x1 rec. INT 0,1 — H
Either equal to: 0 or 1. _ FirstRecNum
Number of last record present. NvMMFilStatusWFC
7153 1 R x1 rec. INT 0,29 — H
Either equal to: 0 or 29. _ LastRecNum
Date the last file was reset. NvMMFilStatusWFC
7154 3 R — — DATE cfformat — H
Default value: 0x8000 0x8000 0x8000. _ LastResetTime

48 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

This file consists of a fixed number of records (29). All records are of similar size,
for example, 64 registers wide.

ENGLISH
Table 32 – Format of Records in the Wave Form Capture of the Metering
Module

Record
Registers Description
Number
1–4 Extended date / time.
5–11 Reserved.
ID of WFC trigger (analog predefined alarm 1 to 53).
12
Available with firmware version H Logic 2005 AF.
13 System type: 30, 31, 40 or 41 (see register 3314).
14 Circuit breaker nominal current in amperes.
15 Voltage multiplier for phase A (format is SFIXPT).
16 Voltage Offset for phase A (format is INT).
17 Same as 15, for phase B.
18 Same as 16, for phase B.
19 Same as 15, for phase C.
20 Same as 16, for phase C.
1
21 Current multiplier for phase A (format is SFIXPT).
22 Current Offset for phase A (format is INT).
23 Same as 21, for phase B.
24 Same as 22, for phase B.
25 Same as 21, for phase C.
26 Same as 22, for phase C.
27 Current multiplier for neutral (format is SFIXPT).
28 Same as 22, for neutral.
29 Scaling factor used for SFIXPT math on voltage samples.
30 Scaling factor used for SFIXPT math on phase current samples.
31 Scaling factor used for SFIXPT math on neutral current samples.
32–64 Not used.
2 to 5 1–64 Voltage A sample points (64 points – 4 cycles).
6 to 9 1–64 Voltage B sample points (64 points – 4 cycles).
10 to 13 1–64 Voltage C sample points (64 points – 4 cycles).
14 to 17 1–64 Current A sample points (64 points – 4 cycles).
18 to 21 1–64 Current B sample points (64 points – 4 cycles).
22 to 25 1–64 Current C sample points (64 points – 4 cycles).
Current N sample points (64 points – 4 cycles)
26 to 64 1–64
Only valid in 41 system.
In order to derive phase A voltage, apply this rule:
Sample (volt) = [(sample – reg. 16 of 1st rec.) x reg. 15 of 1st rec.] / reg. 29 of 1st rec.
Register 18, 17 for phase B voltage; register 20, 19 for phase C voltage.
In order to derive phase A current, apply this rule:
Sample (amp) = [(sample – reg. 22 of 1st rec.) x reg. 21 of 1st rec.] / reg. 30 of 1st rec.
Register 24, 23 for phase B amp; register 26, 25 for phase C amp.
In order to derive neutral amp current, apply this rule:
Sample (amp) = [(sample – reg. 28 of 1st rec.) x reg. 27 of 1st rec.] / reg. 31 of 1st rec.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 49

 Four-Wire Modbus® Communications System Section 4—Access to Files

Fault Wave Form Capture

ENGLISH

Table 33 – Descriptor of the Fault Wave Form Capture in the Protection Module

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Fault Wave Form Capture Configuration (HEADER)
File status.
0x0000, • 0xFFFF: file enabled. NvPMFilHdrFWFC
9964 1 R/W — — INT — H
0xFFFF • 0: file disabled. CtrlReg
Default value: 0xFFFF.
Type of file:
Fault Wave Form Capture Default. NvPMFilHdrFWFC
9965 1 R — — INT 22 — H
FileType
Default value: 22 (FWFC).
Size of file in number records. NvPMFilHdrFWFC
9966 1 R x1 rec. INT 22 — H
Always equal to: 22 records / file. Allocation
Size of records in number of registers.
NvPMFilHdrFWFC
9967 1 R x1 register INT 64 — H Always equal to: 64 registers per
RecSize
record.
File filling mode.
1: disabled if log is full. NvPMFilHdrFWFC
9968 1 R — — INT 0 — H 0: circular. Mode
Default value: 0.
Number of 12 cycle segments. NvPMFilHdrFWFC
9969 — R 1 segment INT 1 — H
Always equal to: 1. MaxNumOfSegments
Number of cycle before capture. NvPMFilHdrFWFC
9970 — R 1 cycle INT 2 — H
Always equal to: 2. PreAlarmCycles
Number of points per cycle. NvPMFilHdrFWFC
9971 — R 1 points INT 16 — H
Always equal to: 16. PointsPerCycle
Fault Wave Form Capture Characteristics (STATUS)
Size of file in records. NvPMFilStatusFWFC
9980 1 R x1 rec. INT 0,22 — H
Either equal to: 0 or 22. _ AllocFileSize
Size of a record in registers. NvPMFilStatusFWFC
9981 1 R x1 register INT 64 — H
Always equal to: 64. _ AllocRecSize
• 0: file OK.
• 10: record size smaller than
0, 10, expected.
20, 30, • 20: record size larger than
250, expected.
253, • 30: insufficient memory.
254, • 250: internal error. NvPMFilStatusFWFC
9982 1 R x1 — INT — H
255, • 253: corrupted allocation table. _ FileStatus
0xFF00, • 254: configuration zero.
0xFE00, • 255: invalid configuration.
0xFD00, • 0xFF00: cannot allocate file.
0xFC00 • 0xFE00: file not supported.
• 0xFD00: invalid record number.
• 0xFC00: invalid file number.
Actual number of records in the file. NvPMFilStatusFWFC
9983 1 R x1 rec. INT 0,22 — H
Either equal to: 0 or 22. _ NbOfRecords
Number of first record present. NvPMFilStatusFWFC
9984 1 R x1 rec. INT 0,1 — H
Either equal to: 0 or 1. _ FirstRecNum
Number of last record present. NvPMFilStatusFWFC
9985 1 R x1 rec. INT 0,22 — H
Either equal to: 0 or 22. _ LastRecNum
Date the last file was reset. NvPMFilStatusFWFC
9986 3 R — — DATE cfformat — H
Default value: 0x8000 0x8000 0x8000. _ LastResetTime

50 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 4—Access to Files Four-Wire Modbus® Communications System

This file consists of a fixed number of records (22). All records are of similar size,
for example, 64 registers wide.

ENGLISH
Table 34 – Format of Records in the Fault Wave Form Capture of the
Protection Module

Record
Registers Description
Number
1–4 Extended date / time.
5–11 Reserved.
Id of fault WFC Trigger: Alarm number 1000 to 1031 (see the
12
Appendix, “Trip / Alarm History” on page 82).
13 System type: 30, 31, 40 or 41 (see register 3314).
14 Circuit breaker nominal current in amperes.
15 Voltage multiplier for phase A (format is SFIXPT).
16 Voltage offset for phase A (format is INT).
17 Same as 15, for phase B.
18 Same as 16, for phase B.
19 Same as 15, for phase C.
20 Same as 16, for phase C.
1
21 Current multiplier for phase A (format is SFIXPT).
22 Current Offset for phase A (format is INT).
23 Same as 21, for phase B.
24 Same as 22, for phase B.
25 Same as 21, for phase C.
26 Same as 22, for phase C.
27 Current multiplier for neutral (format is SFIXPT).
28 Same as 22, for neutral.
29 Scaling factor used for SFIXPT math on voltage samples.
30 Scaling factor used for SFIXPT math on phase current samples.
31 Scaling factor used for SFIXPT math on neutral current samples.
32–64 Not used.
2 to 4 1–64 Voltage A sample points (16 points – 12 cycles).
5 to 7 1–64 Voltage B sample points (16 points – 12 cycles).
8 to 10 1–64 Voltage C sample points (16 points – 12 cycles).
11 to 13 1–64 Current A sample points (16 points – 12 cycles).
14 to 16 1–64 Current B sample points (16 points – 12 cycles).
17 to 19 1–64 Current C sample points (16 points – 12 cycles).
Current N sample points (16 points – 12 cycles)
20 to 22 1–64
Only valid in 41 system.
In order to derive phase A voltage, apply this rule:
Sample (volt) = [(sample – reg. 16 of 1st rec.) x reg. 15 of 1st rec.] / reg. 29 of 1st rec.
Register 18, 17 for phase B voltage; register 20, 19 for phase C voltage.
In order to derive phase A current, apply this rule:
Sample (amp) = [(sample – reg. 22 of 1st rec.) x reg. 21 of 1st rec.] / reg. 30 of 1st rec.
Register 24, 23 for phase B amp; register 26, 25 for phase C amp.
In order to derive neutral amp current, apply this rule:
Sample (amp) = [(sample – reg. 28 of 1st rec.) x reg. 27 of 1st rec.] / reg. 31 of 1st rec.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 51

 Four-Wire Modbus® Communications System Section 5—Modbus Functions

Section 5— Modbus Functions

ENGLISH

Introduction
Modbus is an application layer messaging protocol, positioned at level 7 of the OSI
model, that provides client/server communication between devices connected on
different types of buses or networks.
The Internet community can access Modbus at a reserved system port 502 on the
TCP/IP stack.
Modbus is a request/reply protocol with services specified by function codes.

Modbus / JBus Protocol

In the Modbus protocol, register numbering begins with 1, whereas in the JBus
protocol, numbering of the equivalent registers begins with 0. However, a JBus
master can dialogue with a Modbus slave by addressing a register number –1 to
access the correct register on the Modbus slave.
Example of a request to read a register.
In order to read the rms current on phase A (register 1016), you will have to
address the register number 1016 – 1 = 1015
1015 = 0x03F7 (hexa).

Request Response
Function — 03 Function — 03
Starting Address Hi 03 Byte count — 02
Starting Address Lo F7 Register value Hi 02
N° of registers Hi 00 Register value Lo 2B
N° of registers Lo 01 — — —

The contents of register 1016 (rms current on phase A) are shown as the two byte
values of 02 2B (hexa), or 555 (decimal). Therefore, rms current on phase A is 555
amperes.

Modbus Exception Responses

When a client device (master) sends a request to a server device (slave) it expects
a normal response. One of four possible events can occur from the master’s query:
• If the server device receives the request without a communication error, and
can handle the query normally, it returns a normal response.
• If the server device does not receive the request due to a communication error,
no response is returned. The client program will eventually process a time out
condition for the request.
• If the server device receives the request, but detects a communication error
(parity, LRC, CRC,…), no response is returned. The client program will
eventually process a time out condition for the request.
• If the server device receives the request without a communication error, but
cannot handle it (for example, if the request is to read a non existing register),
the server will return an exception response informing the client of the nature of
the error.

52 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 5—Modbus Functions Four-Wire Modbus® Communications System

The exception response message has two fields that differentiate it from a normal
response:

ENGLISH
Function code: Function code of the original request + 0x80 (hexa)
Exception code: See the following list
01 ILLEGAL FUNCTION
02 ILLEGAL DATA ADDRESS
03 ILLEGAL DATA VALUE
04 SLAVE DEVICE FAILURE
05 ACKNOWLEDGE (in conjunction with programming commands)
06 SLAVE DEVICE BUSY (in conjunction with programming commands)
08 MEMORY PARITY ERROR (with function code 0x14)

Standard Modbus Functions

Table 35 – Read Functions

Function Code Sub-Function Description

3 — Read n output or internal registers.1, 2
4 — Read n input registers.1,2
23 — Simultaneously read / write n and p registers.1, 2
43 — Read Device Identification3
1 Registers 4XXXX and 3XXXX are linked to the same data in registers XXXX in the data tables.
2 The n (or p) registers constitute a block specified by the basic block address and the size of the block.
3 Read Device Identification is available only with a Breaker Communication Module firmware version
greater or equal to V2.0 (register 577 must be greater or equal to 02000).

Table 36 – Write Functions

Function Code Sub-Function Description

6 — Write one register.
16 — Write n registers.1,2
22 — Write one register with mask.
23 — Simultaneously read / write n and p registers.1,2
1 Registers 4XXXX and 3XXXX are linked to the same data in registers XXXX in the data tables.
2 The n (or p) registers constitute a block specified by the basic block address and the size of the block.

These functions act exclusively on the breaker communication module (@ XX) and the
cradle communication module (@ XX + 50).
Table 37 – Diagnostic Functions

Function Code Sub-Function Description

8 — Management of the diagnostics counters.
8 10 Clear the diagnostics counters.
8 11 Read the bus-messages counter managed by the slave.
8 12 Read the bus-errors counter managed by the slave.
Read the bus-exception answer counter managed by the
8 13
slave.
8 14 Read the counter for messages sent to the slave.
Read the counter for messages sent to the slave and to
8 15
which the slave did not answer.
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 53

 Four-Wire Modbus® Communications System Section 5—Modbus Functions

Table 37 – Diagnostic Functions (continued)

Function Code Sub-Function Description

ENGLISH

Read the counter for messages sent to the slave and to

8 16 which the slave replied with an exception code 07 “Negative
Acknowledge”.
Read the counter for messages sent to the slave and to
8 17 which the slave replied with an exception code 06 “Slave
Device Busy”.
Read the counter for messages sent to the slave that it could
8 18
not process due to a transmission error.
11 — Read the Modbus event counter.
17 — Read the identifier of the Modbus slave.

Read File Record: Function 20 (0x14).

This function acts exclusively on the protection module (@ xx +100) and the
metering module (@ xx + 200).
This function code is used to perform a file record read. All Request Data Lengths
are provided in terms of number of bytes and all Record Lengths are provided in
terms of registers.
The quantity of registers to be read, combined with all other fields in the expected
response, must not exceed the allowable length of Modbus messages: 256 bytes.
Table 38 – File Record Read

Request Response
Function Code 1 Byte 0x14 Function 1 Byte 0x14
Byte Count 1 Byte 0x07 Data Length 1 Byte 2 + Nx2
Reference Type 1 Byte 0x06 File Resp.Length 1 Byte 1 + Nx2
0x0000 to
File Number 2 Byte Reference Type 1 Byte 0x06
0xFFFF
0x0000 to
Record Number 2 Byte Record Data Nx2 Bytes Data
0x270F
Record Length 2 Byte N — — —

Example of a request to read the most recent record in the event log of the
protection module.
The event log of the protection module is the file N° 20 (0x0014). This file is made
up of 100 records, each record is made up of 9 registers. So, the record length is 9
(0x0009). The sequence number of last record in the file (the most recent) is the
content of register 9921.
Let’s take 0x1234 for the content of register 9921.
Table 39 – Event Log

Request Response
Function Code 1 Byte 0x14 Function 1 Byte 0x14
Byte Count 1 Byte 0x07 Data Length 1 Byte 0x14
Reference Type 1 Byte 0x06 File Resp.Length 1 Byte 0x13
File Number 2 Byte 0x0014 Reference Type 1 Byte 0x06
Record Number 2 Byte 0x1234 Record Data 9x2 Bytes Data
Record Length 2 Byte 0x0009 — — —

54 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 5—Modbus Functions Four-Wire Modbus® Communications System

Advanced Modbus Functions

ENGLISH
Read n non-contiguous registers (function 100, sub-function 4).
The n non-contiguous registers must be specified one after the other by their
register in the data table. The maximum for n is 100 (When using Micrologic A, it is
recommended to have n less than or equal to 21).
To optimize access to Micrologic and its COM options, it may be very useful to read
n non-contiguous registers in a data table.
Use of function 100, sub-function 4 avoids:
• reading a large block of contiguous data when only a few elements of data are
required,
• multiplying read functions for n registers (functions 3 and 4) or for one word
(function 1) simply to read a few elements of non-contiguous data.
The table below provides an example of reading the data in registers 101 and 103
of the slave with the Modbus address 47.
Table 40 – Example of an Advanced Modbus Function

Request Answer

Name of Field Example Name of Field Example

Slave address 47 Slave address (identical) 47
Function1 100 Function1 100
Number of bytes requested and
Number of registers read + 2 6 6
returned + 2
Sub-function code1 4 Sub-function code1 4
Transmission number2 0xXX Transmission number2 0xXX
Address of first register to read First word read
0 0x12
(most significant byte) (most significant bits)
Address of first register to read First word read
101 0x0A
(least significant byte) (least significant bits)
Address of second register to read Second word read
0 0xFA
(most significant byte) (most significant bits)
Address of second register to read Second word read
103 0x0C
(least significant byte) (least significant bits)
CRC high XX CRC high XX
CRC low XX CRC low XX
1 These values are constant.
2 The transmission number is provided by the master prior to each request for a non-contiguous read.
The slave device must return the same number.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 55

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

Section 6— Interfacing Legacy and New Communications Systems

ENGLISH

Introduction
There are thousands of existing installations with Masterpact and PowerPact circuit
breakers communicating on four-wire Modbus systems and two-wire Modbus systems
without Smart System™ components.This section describes systems that are existing
and how to interface the new two-wire systems and Smart System components.
The Smart System communication system is designed to connect installations to
real savings in three steps: Measure, connect, and save using Smart System
components which include Micrologic trip units, display modules (FDM121 and
FDM128), and communication devices (IO module, IFE module, IFM module). See
0613IB1313 Communication Guide for more information.
This section will also describe how to replace existing communication devices to
keep your existing communication system functioning properly.

Typical Communication System Diagrams

Figure 6 – Masterpact and PowerPact P/R Circuit Breakers (Four-Wire System)

Firewall
Modbus RS 485 4-wire
without ULP module
Internet
External power supply
24 V c
- +
Site Intranet
Ethernet (TCP/IP/Modbus) + -
EGX100
Rx- Rx+ Tx- Tx+
EGX100/300

Ethernet (TCP/IP/Modbus)
Modbus
ULP

Modbus + -

Network
A B A’ B’
CCM Breaker

A B A’ B’
+ -
CCM FDM121

E1 E2 E3 E4 E5 E6
24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1

customer terminal block

Masterpact NT/NW PowerPact P/R

These systems were used in switchboards, switchgear and motor control centers
and are covered by the information in the other sections of this instruction bulletin.

56 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

Figure 7 – Masterpact, PowerPact P/R-Frame in a System with H, J, and L-frame Micrologic (Two-Wire
Systems without Smart System Components)

ENGLISH
Automatic Modbus RS 485 2-wire + ULP
Firewall notification with ULP module
External power supply
Internet Nomad 24 V c
mode
- +

+ -
EGX100
Site Intranet
Ethernet (TCP/IP/Modbus) This configuration Rx- Rx+ Tx- Tx+
is only possible with
Consultation Consultation CCM marked
EGX100/300 EGX100/300
RSU RSU Schneider Electric
RCU RCU on the front face.

Ethernet (TCP/IP/Modbus)
Modbus + - + -

Network
ULP FDM121
A B A’ B’
version > V2.0.2
Modbus Modbus CCM

Breaker
A B A’ B’
+ -

CCM FDM121
Breaker ULP
cord
red black white blue

FDM121 FDM121
E1 E2 E3 E4 E5 E6

24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1
customer terminal block

Masterpact NT/NW PowerPact P/R PowerPact H/J/L Sepam PowerMeter

These systems were used in switchboards and motor control centers where
PowerPact H-, J-, and L-frame circuit breakers with Micrologic electronic trip units
were added into communication systems with Masterpact and/or PowerPact P- and
R-frame circuit breakers. These systems are covered in this instruction, 48940-
329-01 ULP User Guide and in 48940-313-01 PowerPact H-, J-, and L-Frame with
Micrologic Trip Unit User Guide.

Interfacing New Two-Wire Modbus and Smart Communications Systems with

Four-Wire Modbus Systems
Figure 8 shows the new Smart System wiring and components for two-wire
Modbus + ULP.
In most cases you can keep the four-wire Modbus system and interface with a new
installation at the Ethernet level either at the EGX gateway, IFE module, or at the
power meter device. See Figure 9 for recommended connections.
If you want to interface new and existing systems at the Modbus level, See Figure
10 for recommended connections.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 57

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

Figure 8 – Masterpact and PowerPact P/R Circuit Breakers in a System with H, J, and L-Frame Circuit
Breakers with Micrologic Trip Units (Two-Wire Systems with Smart System™ components)
ENGLISH

Ethernet
K
J
24 V DC

Modbus
A
A A
A A
A
24 V DC
24 V DC BB
+24V
0V

II II II
KK
C
Eth2

C Eth1

C
C +24V
0V
D
D

KK +24V
0V

Eth1
Eth2

Eth2

Eth1

II
II
II I5
C
I6
I4
C
I3
I2
C
I1

I6
C
I5
I4
C
I3
I2
C
I1
+
24VDC

A1
K
K
K
K O1
O2
O3

K
K dule
IO Mo

E
I6

E
C
I5
I4
C
I3
I2
C A1
I1
T2
O3 T1
34
I6 I6 O2 33
C C 24
I5 23
O1
I3 14
I2 13
C I2
C
I1 I1
+
24VDC
I6
C
I5

I3
I2
C
I1
+
24VDC

dule
IO Mo

A1
T2
T1

O2
24
O1 23
14
13
A1
T2
T1

M
O2

M
24
O1 23
14
13

F
F
LL L
L LL M
M

FF G
G H H
H
H

A. FDM121 (TRV00121) E. IO application module (LV434063) I. ULP termination (TRV00880) M. NSX cord
B. IFE master (LV434011) F. Masterpact NT/NW J. FDM128 (LV434128)
C. IFE (LV434010) G. PowerPact P/R K. ULP cable

D. IFM (TRV00210) H. PowerPact H/J/L L. Circuit breaker ULP cord

58 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

Figure 9 – Masterpact and PowerPact P/R-Frame in a System with H, J, and L-Frame Circuit Breakers with
Micrologic Trip Units (Four-Wire and Two-Wire) Connected at Ethernet Level

ENGLISH
Connect new system at the Ethernet level. Each circuit breaker in the new system needs an IFM module or an IFE
module to connect into the system. Each IFE module can provide a gateway to the Ethernet for up to 12 IFM modules.

Automatic Modbus RS 485 2-wire + ULP

Firewall notification with ULP module
External power supply
Internet Nomad 24 V c
mode
- +

+ -
EGX100
Site Intranet
Ethernet (TCP/IP/Modbus) This configuration Rx- Rx+ Tx- Tx+
is only possible with
Consultation Consultation CCM marked
EGX100/300 EGX100/300
RSU RSU Schneider Electric
RCU RCU on the front face.

Ethernet (TCP/IP/Modbus)
Modbus + - + -

Network
ULP FDM121
A B A’ B’
version > V2.0.2
Modbus Modbus CCM

Breaker
A B A’ B’
+ -

CCM FDM121
Breaker ULP
cord
red black white blue

FDM121 FDM121
E1 E2 E3 E4 E5 E6

24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1
customer terminal block

Masterpact NT/NW PowerPact P/R PowerPact H/J/L Sepam PowerMeter

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 59

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

Figure 10 – Masterpact and PowerPact P/R-Frame in a System with H, J, and L-Frame Circuit Breakers with
Micrologic Trip Units (Four-Wire and Two-Wire) Connected at Modbus Level
ENGLISH

Connect new system at the Modbus level. Each circuit breaker in the new system needs an IFM module to connect into the
system so that it can be addressed and respond to the Modbus system. Be sure to select Modbus addresses in the new
system that do not overlap with the addresses in the old system.

Automatic Modbus RS 485 2-wire + ULP

Firewall notification with ULP module
External power supply
Internet Nomad 24 V c
mode
- +

+ -
EGX100
Site Intranet
Ethernet (TCP/IP/Modbus) This configuration Rx- Rx+ Tx- Tx+
is only possible with
Consultation Consultation CCM marked
EGX100/300 EGX100/300
RSU RSU Schneider Electric
RCU RCU on the front face.

Ethernet (TCP/IP/Modbus)
Modbus + - + -

Network
ULP FDM121
A B A’ B’
version > V2.0.2
Modbus Modbus CCM

Breaker
A B A’ B’
+ -

CCM FDM121
Breaker ULP
cord
red black white blue

FDM121 FDM121
E1 E2 E3 E4 E5 E6

24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1
customer terminal block

Masterpact NT/NW PowerPact P/R PowerPact H/J/L Sepam PowerMeter

60 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

Converting Legacy Four-Wire Modbus Communications to Smart System

Components.

ENGLISH
General Information
For more information on Smart System with ULP, see 0613IB1313 and
0602IB1503 for instructions.
Fixed Circuit Breaker Communications System
Figure 11 – Existing Four-Wire Modbus System

Firewall

Internet

Site Intranet
Ethernet (TCP/IP/Modbus) External Power Supply
- + 24 V c

EGX100/300

+ -
Ethernet (TCP/IP/Modbus)
EGX100
Modbus
Rx- Rx+ Tx- Tx+

Modbus 4-Wire
Modbus 4-Wire
Without Smart System
Components

BCM Customer
Terminal Block E1 E2 E3 E4 E5 E6
24 V

0V

A / Tx - D0

B / Tx+ D1

A’ / Rx - D0

B’ / Rx + D1

BCM Customer
Terminal Block
BCM (Breaker
Communications
Module)
Customer Terminal Block

Fixed Circuit
Breaker

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 61

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

Figure 12 – New Smart System

ENGLISH

Ethernet
Direct to Ethernet
EGX100/300 TCP/IP
24 Vdc

24VDC

ETH2

4-Wire Modbus ETH1

ETH
1
ETH
2

LV434010IFE
Ethernet Module

CNV100 4-Wire to
2-Wire Converter

2-Wire Modbus Direct to Ethernet

TCP/IP
24 V
Or

+24V
0V

Eth2

STRV00210 IFM Eth1

Modbus Module
Circuit Breaker
Or ULP Cord (Various
lengths available) Other circuit
breakers
connected
for Modbus SL
through IFM
BCM Customer
Terminal Block Or
LV434011 IFE
Ethernet Module
BCM (Breaker and Switchboard
Communications Server
Module)

Fixed Circuit
Breaker

62 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

Drawout Circuit Breaker Communications System

Figure 13 – Existing Four-Wire Modbus System

ENGLISH
Firewall
Modbus RS 485 4-Wire
Without ULP Module
Internet
External Power Supply
+ 24 V c
-
Site Intranet
Ethernet (TCP/IP/Modbus) -
+
EGX100
EGX100/300
Rx- Rx+ Tx- Tx+

Ethernet (TCP/IP/Modbus)
Modbus

Modbus 4-Wire

Cradle + -

Network
Communications A B A’ B’
Module
CCM

Breaker
A B A’ B’
+ -

Mobus 4-Wire

Cradle Position
Switches
Cradle
Position BCM Customer
Switches Terminal Block
E1 E2 E3 E4 E5 E6
24 V

0V

A / Tx - D0

B / Tx + D1

A’ / Rx - D0

B’ / Rx+ D1

Customer Terminal Block

Drawout
Circuit
Breaker
BCM (Breaker
Communications
Module)

Micrologic
Trip Unit

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 63

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

Figure 14 – New Smart System

ENGLISH

Ethernet
EGX100/300 Direct to Ethernet
TCP/IP
24 Vdc

24VDC

4-Wire Modbus ETH2

2
ETH
ETH1
1
ETH

Direct to Ethernet
TCP/IP
LV434010IFE
CNV100 4-Wire to Ethernet Module
2-Wire Converter
+24V
0V

Eth2

Eth1

I6
C
I5
I4
C

LV434063 IO
I3
I2
C
I1

I6
C
I5

2-Wire Modbus
I4

Input/Output
C
I3
I2
C
I1
+
24VDC

Module
Other circuit
breakers
Or
connected
STRV00210 IFM O1
14
23
O2
24
33
O3
34
T1
A1
T2

for Modbus SL
Modbus Module
13

through IFM

Or
ULP Cord Various LV434011 IFE
lengths available) Ethernet Module
Or
and Switchboard
Circuit Breaker Server
ULP Cord Various
lengths available)
Cradle Position
Switches
Cradle
BCM Customer
Position
Terminal Block
Switches

BCM ULP
Cord
Red Black White Blue

Drawout E1 E2 E3 E4 E5 E6
Circuit
24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1

Breaker
BCM (Breaker
Communications
Module)
Micrologic BCM ULP Module
Trip Unit

64 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

Replacing the BCM (Breaker Communications Module)

ENGLISH
If you need to replace the BCM in an existing system with four-wire Modbus, do the
following steps.
NOTE: This option is only available for P & H trip units with firmware version
2010AK or later. If your trip unit does not have this option then follow the process
described in Step 3 for Micrologic A trip units.
1. Order a replacement BCM – part number S48384.
2. For a Micrologic P- or H-trip unit, change the communication parameter in the
BCM to four-wire Modbus by doing the following.
a. Replace the BCM using the Installation Bulletin that came with the new
BCM.
b. Connect the wiring to the BCM.
c. Turn on the 24 Vdc control power to the BCM E1(+)-E2(-) and the
Micrologic trip unit F1(-) and F2 (+).
d. Press the wrench key (Maintenance button) and scroll to COM SETUP.
e. Scroll to COM PARAMETER and to the bottom of the screen to
2wire+ULP/4wires.
f. Select 4wires and save selection.

Figure 15 – Setting Trip Unit Connection Value

Com. Modbus Modbus Modbus

parameters Com Com Com
Address Address Address
Remote Do o w nt
access 32 32 32 to s e new
Baud-rate Baud-rate Baud-rate settin s
Remote
control 9600 9600 9600
Parity Parity Parity o
IP Data
None None None
Connection Connection Connection es
2Wires+ULP 2Wires+ULP 4 Wires
Up/ Up/
Enter Down Down
Down Down
Enter Enter Enter Enter

Exit

3. If you have a Micrologic A trip unit, the communication parameter cannot be

changed with the trip unit interface. The communication parameter can be
changed by doing the following steps:
a. Order the following parts:

Qty Reference Number Description

1 S48384 BCM (breaker communications module)
1 LV434010 IFE Ethernet interface module
1 Depending on length needed Breaker ULP cord
LV434196 L = 1.3 m (4.26 ft)
LV434197 L = 3 m (9.84 ft)
1 Depending on length needed ULP cable
TRV00810 L = 1 m (3.28 ft), 5 cables
TRV00820 L = 2 m (6.56 ft), 5 cables

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 65

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

b. Replace the BCM using the Installation Bulletin that came with the new BCM.
c. Disconnect the 4-wire Modbus from the green connector for the BCM. Mark
ENGLISH

and disconnect the wires from terminals E3, E4, E5, and E6. Also
disconnect the 24 Vdc wiring from E1 and E2.

Disconnect 4-wire
E1 E2 E3 E4 E5 E6
Modbus from E3-E6

24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1
customer terminal block

d. Connect the ULP cord (LV434196 or LV434197 depending on length) white

wire to terminal E5 and the blue wire to terminal E6. Also connect the red
wire to E1(+) and black wire to E2(-). Plug the connector into the new BCM.
e. Plug the other end of the ULP cord into an IFE (LV434010). Connect
24 Vdc wiring that was connected to the E1 and E2 connector in the BCM
to the top of the IFE. Add terminals and additional wiring as necessary.

24 Vdc

IFE
24VDC

ETH2
2
ETH
ETH1
1
ETH

set)
(factory
.YY.ZZ
IFE_XX
CT
-100/A
LK/10
ETH1
IFE -100/A
CT
LK/10
ETH2 Sta tus
e
Modul
tus
rk Sta
Netwo
s-SL
Modbu

Breaker ULP
cord
red black white blue

E1 E2 E3 E4 E5 E6
24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1

customer terminal block

BCM Connector

66 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

f. Download the Customer Engineering Tool - Ecoreach V2.2 or later from the
Schneider Electric internet (http://www.schneider-electric.com). Install the

ENGLISH
Ecoreach software on your laptop.
g. Read the IFE address on the front of the IFE module (B) Example: IFE-
E3.15.92. Convert the last two characters in the address from hexadecimal
to decimal and add the decimal equivalents to the end of the default IP
address: 169.254.xx.xxx. Example: 15 converts to 21 and 92 converts to
146. Then – 169.254.21.146 is the IP address for the IFE module shown in
this example. Record the IP address from this step 169.254. __.___.

IFE-E3.15.92

Table 41 – Hex to Decimal Conversion

Hex Dec. Hex Dec. Hex Dec. Hex Dec. Hex Dec. Hex Dec. Hex Dec. Hex Dec. Hex Dec. Hex Dec.
0 0 1A 26 34 52 4E 78 68 104 82 130 9C 156 B6 182 D0 208 EA 234
1 1 1B 27 35 53 4F 79 69 105 83 131 9D 157 B7 183 D1 209 EB 235
2 2 1C 28 36 54 50 80 6A 106 84 132 9E 158 B8 184 D2 210 EC 236
3 3 1D 29 37 55 51 81 6B 107 85 133 9F 159 B9 185 D3 211 ED 237
4 4 1E 30 38 56 52 82 6C 108 86 134 A0 160 BA 186 D4 212 EE 238
5 5 1F 31 39 57 53 83 6D 109 87 135 A1 161 BB 187 D5 213 EF 239
6 6 20 32 3A 58 54 84 6E 110 88 136 A2 162 BC 188 D6 214 F0 240
7 7 21 33 3B 59 55 85 6F 111 89 137 A3 163 BD 189 D7 215 F1 241
8 8 22 34 3C 60 56 86 70 112 8A 138 A4 164 BE 190 D8 216 F2 242
9 9 23 35 3D 61 57 87 71 113 8B 139 A5 165 BF 191 D9 217 F3 243
A 10 24 36 3E 62 58 88 72 114 8C 140 A6 166 C0 192 DA 218 F4 244
B 11 25 37 3F 63 59 89 73 115 8D 141 A7 167 C1 193 DB 219 F5 245
C 12 26 38 40 64 5A 90 74 116 8E 142 A8 168 C2 194 DC 220 F6 246
D 13 27 39 41 65 5B 91 75 117 8F 143 A9 169 C3 195 DD 221 F7 247
E 14 28 40 42 66 5C 92 76 118 90 144 AA 170 C4 196 DE 222 F8 248
F 15 29 41 43 67 5D 93 77 119 91 145 AB 171 C5 197 DF 223 F9 249
10 16 2A 42 44 68 5E 94 78 120 92 146 AC 172 C6 198 E0 224 FA 250
11 17 2B 43 45 69 5F 95 79 121 93 147 AD 173 C7 199 E1 225 FB 251
12 18 2C 44 46 70 60 96 7A 122 94 148 AE 174 C8 200 E2 226 FC 252
13 19 2D 45 47 71 61 97 7B 123 95 149 AF 175 C9 201 E3 227 FD 253
14 20 2E 46 48 72 62 98 7C 124 96 150 B0 176 CA 202 E4 228 FE 254
15 21 2F 47 49 73 63 99 7D 125 97 151 B1 177 CB 203 E5 229 FF 255
16 22 30 48 4A 74 64 100 7E 126 98 152 B2 178 CC 204 E6 230
17 23 31 49 4B 75 65 101 7F 127 99 153 B3 179 CD 205 E7 231
18 24 32 50 4C 76 66 102 80 128 9A 154 B4 180 CE 206 E8 232
19 25 33 51 4D 77 67 103 81 129 9B 155 B5 181 CF 207 E9 233

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 67

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

h. Use an appropriate length of ULP cable to connect the laptop to the

Ethernet port ETH1 on top of the IFE module. Leave the Ethernet port
ENGLISH

ETH2 open.

Ethernet

24 Vdc

IFE
24VDC

ETH2
2
ETH
ETH1
1
ETH

Breaker ULP
cord
red black white blue

E1 E2 E3 E4 E5 E6

24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1
customer terminal block
BCM Connector

i. Open Ecoreach program and select Discover devices.

68 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

j. Ecoreach will normally discover the IFE connected. If the IFE is not
discovered, go to next step.

ENGLISH
k. If Ecoreach did not discover the IFE, click on add more gateways manually
and fill in the address you recorded in step g.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 69

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

l. Check box by Modbus and enter address 255. Press Start Deep Scan.
ENGLISH

m. Check the box in the device list and click Add to Project.

70 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

n. Click Apply.

ENGLISH
o. Click Connect to breaker.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 71

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

p. Click on Launch Configure.

ENGLISH

q. Click Write to project

72 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

r. Click on Communications

ENGLISH
s. Change Modbus serial line wiring to 4 wire.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 73

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

t. Click Write to device.

ENGLISH

u. Click the back arrow.

74 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

v. Click Disconnect.

ENGLISH
w. Close Ecoreach and click Leave.

x. Disconnect the laptop and ULP cable from the IFE. Disconnect the circuit
breaker ULP cord from the IFE. Disconnect the ULP cord wires from the
BCM connector.

Ethernet

24 Vdc

IFE
24VDC

ETH2
2
ETH
ETH1
1
ETH

Breaker ULP
cord
red black white blue

E1 E2 E3 E4 E5 E6
24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1

customer terminal block

BCM Connector

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 75

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

y. Disconnect the 24 Vdc connections from the IFE. Reconnect the 24 Vdc
red and black wires to the BCM connector at terminals E1(red) and E2
ENGLISH

(black). Also reconnect the 4-wire modbus connections to E3 – E6 per the

marking done during disassembly.

Reconnect 24 Vdc and

E1 E2 E3 E4 E5 E6
4-wire Modbus to the

24 V
0V
A / Tx- D0
B / Tx+ D1
A’ / Rx- D0
B’ / Rx+ D1
BCM Connector

customer terminal block

Replacing the CCM (Cradle Communications Module)

If you need to replace the CCM (S48377) in an existing system, there are two
options.
1. Order a replacement CCM. This will provide a direct replacement. Follow the
instructions that come with the CCM to install, wire, and test the CCM. Your
system will operate the same as before.
2. Convert to the new system by using an IO module to replace the CCM. This will
require the following steps to complete the conversion and to get your system
functioning as before.
Convert to new system by using the IO module
Order the following parts:

Qty Reference number Description L

1 LV434063 IO module
1 S48384 BCM (breaker communications module)
1 STRV00210 IFM module
1 CNV100 4-wire to 2-wire converter
Depending on length needed Breaker ULP cord
LV434195 L = 0.35 m (1.15 ft)
1
LV434196 L = 1.3 m (4.26 ft)
LV434197 L = 3 m (9.84 ft)
Depends on length needed ULP cable
TRV00803 L = 0.3 m (0.98 ft), 10 cables
1 TRV00806 L = 0.6 m (1.97 ft), 10 cables
TRV00810 L = 1 m (3.28 ft), 5 cables
TRV00820 L = 2 m (6.56 ft), 5 cables

76 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

Determine the Address for For Micrologic P or H trip units, press the wrench key (maintenance) and do the
the trip unit. following:

ENGLISH
Communication Module Setup

1. Use “Com. setup” menu to set communication module setup.

NOTE: Com. setup parameters can only be entered if a circuit breaker
communication module (BCM) is installed.
2. Record the Address.
Figure 16: Communication Module Setup

istor istor Com. Modbus

lo s lo s parameters Com
ont cts ont cts Address
Remote
/ / access 47
icrolo ic icrolo ic Baud-rate
set p set p
Remote
control 19.2k
eterin eterin Parity
set p set p IP Data
Even
om. om. Connection
set p set p 2Wires+ULP

Down Enter Enter

For Micrologic A trip units, do the following steps:

NOTE: Com. setup parameters can only be entered if a circuit breaker
communication module (BCM) is installed.
To access the communication module menu:
1. Current menu is displayed.
2. Simultaneously press both menu button and scroll button down for three
seconds.
3. Communication module addressing menu will appear.
4. Record the address.

Figure 17: Access Communication Module Menu

Current Menu Communications Address
06133354

06133707

06133703

menu

100 % 100 %

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 77

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

DANGER
ENGLISH

HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH

• Apply appropriate personal protective equipment (PPE) and follow safe
electrical work practices. See NFPA 70E or CSA Z462.
• This equipment must only be installed and serviced by qualified electrical
personnel.
• Turn off all power supplying this equipment before working on or inside equipment.
• Always use a properly rated voltage sensing device to confirm power is off.
• Replace all devices, doors and covers before turning on power to this
equipment.
Failure to follow these instructions will result in death or serious injury.

5. Replace the BCM (See Figure 18 and for system diagram).

a. Observe all safety instructions and warnings. Disconnect power to the
circuit breaker.
b. Use the instructions supplied with the BCM. Remove the trip unit and BCM
from the circuit breaker.
c. Install the new BCM and replace the trip unit.
d. Disconnect the Modbus wiring from the circuit breaker cradle connections
that come from the CCM.
e. Install the circuit breaker ULP cord to the circuit breaker cradle connection
for the BCM. Connect E1 – E6 as shown below.
Figure 18 – Connect E1 through E6

Cell switch connections that

were connected to CCM.

ULP cord
I/O Module

Circuit Breaker
ULP cord
Black White
Red Blue

E1 E2 E3 E4 E5 E6

Circuit Breaker
Microswitches Communication
Connected to BCM Module (BCM)

78 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Section 6—Interfacing Legacy and New Communications Systems Four-Wire Modbus® Communications System

f. Find the CCM on the DIN rail near the circuit breaker cradle. Mark the wires
connected to the CCM to make sure they can be installed correctly onto the

ENGLISH
IO module. Disconnect 24 Vdc power from the CCM.
g. Remove the CCM from the DIN rail.
h. Check the DIN rail for proper grounding – make sure the DIN rail is
grounded to a good system ground.
i. Install the IO module onto the DIN rail. There is a ground shoe in the DIN
rail mounting on the IO module.
j. Use the instructions with the IO module to connect the circuit breaker
cradle position switches to the IO module terminals.
k. Connect the circuit breaker ULP cord from the BCM to one of the ULP
connections in the IO module. See Figure 18 above.
l. Determine a suitable mounting area for the IFM module and the four-wire to
two-wire converter. Keep in mind that the 24 Vdc control power that was
connected to the CCM will need to be moved to power the IFM module and
the four-wire to two-wire converter. Also the four-wire Modbus wiring that
was connected to the CCM will need to be moved to the four-wire to two-
wire converter. Add terminals and additional wiring as necessary.
m. Install the IFM module and four-wire to two-wire converter near the IO
module as necessary. Connect the 24 Vdc control power that was on the
CCM to the IFM module and four-wire to two-wire converter.
n. Connect the four-wire Modbus wiring to the four-wire to two-wire converter
as described in the installation instructions.
o. Also connect two-wire Modbus between the four-wire to two-wire converter
and the IFM module terminals.
p. Use a ULP cable to connect between the IO module ULP connection to the
IFM module.
q. Use the dials on the IFM module to select the trip unit address that was
recorded in steps 2 or 4.
NOTE: The IFM module is shipped with the standard firmware. This standard
firmware responds to one unique Modbus slave address (set by the two rotary
switches on the front panel of the IFM module) and therefore is not compatible with
legacy application firmware using Modbus slave address offset (x + 100, x + 200 and
x + 50 for the CCM cradle communication module application with IO module). (See
page 15 for offset addresses.) In order to be compatible with legacy application
firmware using Modbus slave address offset (x + 100, x + 200 and x + 50 for the
CCM application using IO module), it is mandatory to download the Masterpact
legacy firmware into the IFM module. Please contact Schneider Electric customer
support for IFM legacy firmware.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 79

 Four-Wire Modbus® Communications System Section 6—Interfacing Legacy and New Communications Systems

Customer Engineering Tool (Ecoreach)

Definition
ENGLISH

The customer engineering tool used to configure the IFM module or IFE module is
Ecoreach, the Electrical Asset Manager software, or:
• Compact NSX RSU software
— to configure the IFM module
— to update the IFM and IFE firmware
— to manage the passwords
— to set date and time.
• Masterpact RSU software
— to configure the IFM module
— to configure the Masterpact predefined alarm.
• RCU software to check the network communication with IFM and IFE modules.
The customer engineering tools are available at www.schneider-electric.com.
Ecoreach
For more information, see the Ecoreach Online Help.

80 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Appendix A— Registers

ENGLISH
Formats
UINT UINT corresponds to a 16-bit unsigned integer with an interval of values
from 0x 0000…0 x FFFF (0…65535).

INT INT corresponds to a 16-bit signed integer with an interval of values

from 0x 8000…0 x 7FFF (-32768…+32767).

Mod10000 Mod10000 corresponds to n registers in the INT format.

Each register contains an integer from 0 to 9999.
A value V representing n registers is calculated as indicated below:
V = sum(R[n] + R[n + 1] x 10000 +..+ R[n + m] x 10000 (m-1)),
where Rn is the number of register n.
Example: Register 2000 = 123; Register 2001 = 4567; Register 2002 = 89; Register
2003=0 Energy = 123 + 4567 x 10 000 + 89 x (10 000)² + 0 = 89 4567 0123 kWh

SFIXPT SFIXPT corresponds to a signed INT integer with a fixed point.

The position of the point is indicated by the scale factor. The interval of values is:
-32767… +32767 with a scale factor “x 1”.
Other example:
-32.767 … +32.767 with a scale factor “x 1000”.

Date Date corresponds to a normal date made up of three UINT, as follows:

• first UINT:
month expressed using the eight most-significant bits (January = 0x41)1
day expressed using the eight least-significant bits,
• second UINT:
year expressed using the eight most-significant bits (modulo 100)
(00 to 49 = years 2000 to 2049, from 50 to 99 = years 1950 to 1999)
hours expressed using the eight least-significant bits,
• third UINT:
minutes expressed using the eight most-significant bits
seconds expressed using the eight least-significant bits.

XDATE XDATE corresponds to an extended date made up of four UINT, as follows:

• first UINT:
month expressed using the eight most-significant bits (January = 0x41)1
day expressed using the eight least-significant bits,
• second UINT:
year expressed using the eight most-significant bits (modulo 100)
(00 to 49 = years 2000 to 2049, from 50 to 99 = years 1950 to 1999)
hours expressed using the eight least-significant bits,
• third UINT:
minutes expressed using the eight most-significant bits
seconds expressed using the eight least-significant bits.
• fourth UINT: milliseconds.

ASCII ASCII corresponds to a series of n UINT registers forming a string of ASCII

characters. The first character is contained in the eight most-significant bits of the
register. The start of the string is in the first register.
1 If the most-significant bit is set, the date and time may be incorrect.
There are two possibilities:
• no synchronization with the supervisor,
• loss of power.
If power has been lost, the self-test bitmap “D/T loss” is enabled until the date and time are enabled
(via the control unit or the communication module).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 81

 Four-Wire Modbus® Communications System Appendix A—Registers

Trip / Alarm History

ENGLISH

Trip Record
Trip Record format matches the trip history displayed on the graphic screen of the
Micrologic (P/H only).
Trip Record format presents the characteristics of a fault trip. It corresponds to a series
of ten fields (9100, 9120, 9140,…,9280) with a total of 20 registers.
Register 9099 returns the value of the pointer for the last fault recorded in the trip
history.
Each field (containing 20 registers) is presented below:
Table 42 – Trip Record Fields

Number of
Field Format Interval N/A Description
Registers
___.XtedDT 4 XDATE Cfformat 0x8000 Trip date.
___.ActCause
1 INT 0..1031 0x8000 Number of alarm causing activation.
AlarmNum
___.PuValue 2 MOD 1000 See Text 0x8000 Value of protection setting that caused trip.
___.PuDelay 1 INT See Text 0x8000 Value of time delay that caused trip.
___.FaultI[0] 1 INT 0..16000 0x8000 Trip current phase A, expressed with respect to the rated current.1
___.FaultI[1] 1 INT 0..16000 0x8000 Trip current phase B, expressed with respect to the rated current.1
___.FaultI[2] 1 INT 0..16000 0x8000 Trip current phase C, expressed with respect to the rated current.1
Trip current on neutral, expressed with respect to the rated
___.FaultI[3] 1 INT 0..16000 0x8000
current.1
New value of contact-wear indicator following a trip.
___.WorstContact The control unit records one indicator per contact. Here, only the
1 INT 0..32767 0x8000
Wear value for the most worn contact is given. (See registers 9094 to
9097).
___.AddInfo 2 See Text See Text 0x8000 Reserved.
___.Reserved 5 — — 0x8000 Reserved.
1 Expressed as x 0.1 of In (rated current).

Alarm Record
Alarm Record format matches the alarm history displayed on the graphic screen of
the Micrologic (P/H only).
Alarm Record format presents the characteristics of a fault alarm. It corresponds to
a series of ten fields (9302, 9317, 9332, ..., 9437) with a total of 15 registers.
Register 9301 return the value of the pointer for the last alarm recorded in the
alarm history.
Each field (containing 15 registers) is presented below:
Table 43 – Alarm Record Fields

Number of
Field Format Interval N/A Description
Registers
___.XtedDT 4 XDATE cfformat 0x8000 Alarm date.
___.ActCause
1 INT 0..1031 0x8000 Number of alarm causing activation.
AlarmNum
___.PuValue 2 MOD 10000 See Text 0x8000 Value of protection setting that caused alarm activation.
___.PuDelay 1 INT See Text 0x8000 Value of time delay that caused alarm activation.

82 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 43 – Alarm Record Fields (continued)

Number of

ENGLISH
Field Format Interval N/A Description
Registers
Alarm current phase A, expressed with respect to the rated
___.FaultI[0] 1 INT 0..16000 0x8000
current.1
Alarm current phase B, expressed with respect to the rated
___.FaultI[1] 1 INT 0..16000 0x8000
current.1
Alarm current phase C, expressed with respect to the rated
___.FaultI[2] 1 INT 0..16000 0x8000
current.1
Alarm current on neutral, expressed with respect to the rated
___.FaultI[3] 1 INT 0..16000 0x8000
current.1
___.AddInfo 2 See Text See Text 0x8000 Additional information, depending on type of alarm.
___.Reserved 1 — — 0x8000 Reserved.
1 Expressed as x 0.1 of In (rated current)

Alarm Numbers
Table 44 – Basic Protections

Description Number
Long-time protection. Ir 1000
Short-time protection. Isd 1001
Instantaneous protection. Ii 1002
Ground-fault protection. Ig 1003
Earth-leakage protection. IDelta n 1004
Auto Protection (DIN). 1005
Reserved. 1006..1007
Trip due to advanced protection. 1008
Trip due to extended advanced protection. 1009
Reserved. 1010..1013
Ground-fault protection alarm. 1014
Earth-leakage protection alarm. 1015

Table 45 – Advanced Protections

Description Number
Current unbalance. 1016
Over current phase A. 1017
Over current phase B. 1018
Over current phase C. 1019
Over current on the neutral. 1020
Under voltage. 1021
Over voltage. 1022
Voltage unbalance. 1023
Over power. 1024
Reverse power. 1025
Under frequency. 1026
Over frequency. 1027
Phase rotation 1028
Current load shedding. 1029
Power load shedding. 1030
Reserved. 1031

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 83

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 46 – Digital Alarms

ENGLISH

Description Number
System energized / reset. 1100
Reserved. 1101..1105
Loss of date and time. 1106
Reserved. 1107..1114
Battery low. 1115

84 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table of Registers

ENGLISH
Structure of the Table
Each Modbus logical table is made up of the fields listed below.

Register Number of the Modbus register.

Number of Number of registers that must be read or written for a given complete piece of
Registers information. This data indicates the type of register
(8-bit, 16-bit or 32-bit register).

Read / Write:
“R” Register that may be accessed by the Modbus read functions
3, 4, 23, 20, 100 (see page 53).

“W” Register that may be accessed by the Modbus write functions

6, 16, 22, 23 (see page 53).

“R/W” Register that may be read and write accessed.

Scale (x n) Value contained in the register multiplied by n. The requested information is

obtained by dividing the register contents by n. The result is expressed in the
indicated unit.

Unit Unit of measurement for the value contained in the register.

Format Format in which the information is coded.

Interval Interval of the possible values that each register in the group
{Register, Register +1, ..., Register + Nb} can have.

A, P, H Type of control unit using the register:

“A”: Micrologic A control unit
“P”: Micrologic P control unit
“H”: Micrologic H control unit

Description Additional information describing the register, providing coding data and any
necessary information on how to modify the register, particularly when the
command interface is required to carry out the modification.

Label Name given to all the concerned registers.

Scale Factors
Table 47 – Scale Factors

Number of Read /
Register Scale Unit Format Interval Description
Registers Write
3 Scale Factor A (default value = 0)
2
1 3: Scale by 1000
0 2: Scale by 100
3325 1 R/W — — INT -1 1: Scale by 10
-2 0: Scale by 1 (no scaling)
-3 -1: Scale by 0.1
-2: Scale by 0.01
-3: Scale by 0.001
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 85

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 47 – Scale Factors (continued)

Number of Read /
ENGLISH

Register Scale Unit Format Interval Description

Registers Write
3 Scale Factor B (default value = 0)
2
1 3: Scale by 1000
0 2: Scale by 100
3326 1 R/W — — INT -1 1: Scale by 10
-2 0: Scale by 1 (no scaling)
-3 -1: Scale by 0.1
-2: Scale by 0.01
-3: Scale by 0.001
3 Scale Factor C (default value = 0)
2
1 3: Scale by 1000
0 2: Scale by 100
3327 1 R/W — — INT -1 1: Scale by 10
-2 0: Scale by 1 (no scaling)
-3 -1: Scale by 0.1
-2: Scale by 0.01
-3: Scale by 0.001
3 Scale Factor D (default value = 0)
2
1 3: Scale by 1000
0 2: Scale by 100
3328 1 R/W — — INT -1 1: Scale by 10
-2 0: Scale by 1 (no scaling)
-3 -1: Scale by 0.1
-2: Scale by 0.01
-3: Scale by 0.001
3 Scale Factor E (default value = 0)
2
1 3: Scale by 1000
0 2: Scale by 100
3329 1 R/W — — INT -1 1: Scale by 10
-2 0: Scale by 1 (no scaling)
-3 -1: Scale by 0.1
-2: Scale by 0.01
-3: Scale by 0.001
3 Scale Factor F (default value = -1)
2
1 3: Scale by 1000
0 2: Scale by 100
3330 1 R/W — — INT -1 1: Scale by 10
-2 0: Scale by 1 (no scaling)
-3 -1: Scale by 0.1
-2: Scale by 0.01
-3: Scale by 0.001

86 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Breaker Communication Module @ Address xx

Table 48 – Configuration

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Square D product identification.
515 1 R — — INT 15139 A P / H 15139 = Breaker Communication EeSQD_Prod_ID
Module.
Modbus address of the COM option
531 1 R/W — — INT 1..47 A P / H (@XX). EeAdrBus
Default value: 47.
Parity.
• 0: no parity.
532 1 R/W — — INT 0..1 A P/H EeParityBus
• 1: even parity.
Default value: 1.
Baud rate:
• 1200: 1200 baud
• 2400: 2400 baud
1200.... • 4800: 4800 baud
533 1 R/W — — INT A P/H EeBaudRate
38400 • 9600: 9600 baud
• 19200: 19200 baud
• 38400: 38400 baud
Default value: 19200.

Table 49 – Identification

Number
Read
Registe of Form
/ Scale Unit Interval A P / H Description Label
r Register at
Write
s
Short identifier of Breaker
0x00..0x7 Communication Module, coded over
534 2 R/W — — ASCII A P / H 4 ASCII characters. EeBCM_Loc
F
Default value: 0x00.
Long identifier of Breaker
0x00..0x7 Communication Module, coded over
536 8 R/W — — ASCII A P / H 16 ASCII characters. EeBCM_NamePlate
F
Default value: 0x00.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 87

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 50 – Diagnostics Counters and Password

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Modbus diagnostics counter—
544 1 R — — INT 0..32767 A P / H messages sent to the slave (identical CtrMsgSentThisUnit
to function 8-14).1
Modbus diagnostics counter—
545 1 R — — INT 0..32767 A P/H CtrMsgSentOtherUnit
messages sent to other slaves.1
Modbus diagnostics counter—bus
546 1 R — — INT 0..32767 A P / H messages managed by the slave CtrMsgRX_ValidCRC
(identical to function 8-11).1
Modbus diagnostics counter—bus
547 1 R — — INT 0..32767 A P / H errors managed by the slave CtrMsgRX_InvalidCRC
(identical to function 8-12).1
Modbus diagnostics counter—
messages sent to the slave
548 1 R — — INT 0..32767 A P/H CtrMsgRX_InvalidFC
comprising a non-supported Modbus
function.1
Modbus event counter—
549 1 R — — INT 0..32767 A P/H CtrModbusEvtCtr
(identical to function 11).1
Modbus diagnostics counter—bus
550 1 R — — INT 0..32767 A P / H exception replies managed by the CtrExceptionReplies
slave (identical to function 8-13).1
Modbus diagnostics counter—
551 1 R — — INT 0..32767 A P / H broadcast messages received by the CtrMsgRX_Broadcast
slave (identical to function 8-17).2
Control word of the Cradle
Communication Module. This control
word cannot be set by the user. It is
randomly changed each time the
553 1 R — — INT 0..65535 A P/H ControlWord
system is energized. It is necessary
to read the control word before
sending certain commands to the
Cradle Communication Module.
Counter for number of times the
554 1 R — — INT 0..65535 A P / H Cradle Communication Module is EeCtrPowerUp
energized.2
Counter for the number of Cradle
555 1 R — — INT 0..65535 A P / H Communication Module resets, EeCtrReset
whether following power loss or not.2
Breaker Communication Module
577 1 R 1 — INT — A P/H EeFWVersion
firmware version.
1 The counter automatically cycles from 32767 to 0.
2 The counter automatically cycles from 65535 to 0.

88 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 51 – Metering / Protection Module Event Notification

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Number of first (oldest) record
CurrentFirstRecord
603 1 R — — INT 1..8000 — H in the metering module event
OfMM_EvtLog
log (file N° 10).
Number of last (most recent)
CurrentLastRecord
604 1 R — — INT 1..8000 — H record in the metering module
OfMM_EvtLog
event log (file N° 10).
Number of first (oldest) record
CurrentFirstRecord
623 1 R — — INT 1..8000 — P / H in the protection module
OfPM_EvtLog
event log (file N° 20).
Number of last (most recent)
CurrentLastRecord
624 1 R — — INT 1..8000 — P / H record in the protection
OfPM_EvtLog
module event log (file N° 20).

Table 52 – Cause of Tripping

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
• 0x01: long-time protection
• 0x02: short-time protection
• 0x04: instantaneous protection
• 0x08: ground-fault protection
• 0x10: earth-leakage protection
650 1 R — — INT 0..65535 A P/H • 0x20: integrated instantaneous MitopBasActCause
protection
• 0x40: self-protection (temperature)
• 0x80: self-protection (overvoltage)
• 0x0100: other protection
(see registers 651 and 652).
Status word indicating cause of
tripping by protection functions:
• 0x01: current unbalance
• 0x02: over current phase A
• 0x04: over current phase B
• 0x08: over current phase C
• 0x10: over current on neutral
• 0x20: under voltage
• 0x40: over voltage
651 1 R — — INT 0..65535 — P/H • 0x80: voltage unbalance MitopAdvActCause
• 0x0100: over power
• 0x0200: reverse power
• 0x0400: under frequency
• 0x0800: over frequency
• 0x1000: phase rotation
• 0x2000: load shedding based on
current
• 0x4000: load shedding based on
power
Continuation of alarm status word:

652 1 R — — INT 0..65535 — P/H • 0x01: ground-fault alarm MitopAdvXtedActCause

• 0x02: earth-leakage alarm
• 0x04: ground-fault push to trip

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 89

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 53 – Circuit Breaker Status, Auto / Manu

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Bitmap Circuit breaker status:
661 1 R — — — A P/H BrStatus
16 see next page.
Counter for total number of
operations (OF):
662 1 R — — INT 0..65535 A P / H the counter increments CtrOF_OvrLife
when bit 0 in register 661
switches from 0 to 1.1
Counter for operations (OF)
since last reset:
663 1 R — — INT 0..65535 A P / H the counter increments CtrOF
when bit 0 in register 661
switches from 0 to 1.1
Counter for operations (SD):
the counter increments
664 1 R — — INT 0..65535 A P/H CtrSD
when bit 1 in register 661
switches from 0 to 1.1
Counter for operations (SDE):
the counter increments
665 1 R — — INT 0..65535 A P/H CtrSDE
when bit 2 in register 661
switches from 0 to 1. 1

Authorization word for

actuation by MX and XF
auxiliaries:

Bitmap • when bit 1 and 3 are set,

669 1 R — — 0..65535 A P/H MX is authorized to CoilControl
16
actuate the circuit breaker,
• when bit 2 and 3 are set,
XF is authorized to actuate
the circuit breaker.
Auto / Manu mode:
• 0, “Manu” mode: remote
opening and closing of the
circuit breaker are
disabled,
• 1, “Auto” mode: remote
670 1 R — — INT 0..1 — P/H opening and closing of the AutoManu
circuit breaker are
enabled. Auto / Manu
mode can be modified on
Micrologic P / H (only
locally).
Default value = 1
SD: Trip indication.
SDE: Fault-trip indication.
OF: ON / OFF.
1 The counter automatically cycles from 65535 to 0.

90 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 54 – List of Possible Values for Register 661 (Circuit Breaker

Status) in the Breaker Communication Module

ENGLISH
BrStatus Bitmap Detail:
Bit 0 (0x01): OF; Indication contacts
For Compact™ and Masterpact™: 0 = circuit breaker is opened, 1 = circuit breaker is closed
Bit 1 (0x02): SD; Trip indication contact
For Compact: 0 = no trip, 1 = circuit breaker has tripped due to electrical fault or shunt trip
For Masterpact: always 0
Bit 2 (0x04): SDE; Fault trip indication contact
For Compact and Masterpact: 0 = no trip, 1 = circuit breaker has tripped due to electrical fault
Bit 3 (0x08): CH; Charged (used only with motor mechanism)
For Compact: always 0
For Masterpact: 0 = Spring discharged, 1 = spring loaded
Bit 4 (0x10): Reserved (internal use only)
Bit 5 (0x20): Reserved (internal use only)
Bit 6 (0x40): Compact / Masterpact differentiation
0 = Compact NS, 1 = Masterpact
Bit 7–15: Reserved
NOTE: A bitmap mask should be used to test the circuit breaker status.
If a value test is used, the following values should be used for Masterpact:
0x44 Tripped discharged not RTC 0x51 ON discharged not RTC
0x4C Tripped charged not RTC 0x59 ON charged RTC
0x50 OFF discharged not RTC 0x78 OFF charged RTC

Table 55 – Time Stamping

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
671 3 R — — DATE — A P / H Date of last actuation of MX auxiliary. LastXFCoilActivationD_T
674 1 R — — INT 0..65535 A P / H MX actuation counter.1 CtrXFCoilActivation
675 3 R — — DATE — A P / H Date of last actuation of XF auxiliary. LastMXCoilActivationD _T
678 1 R — — INT 0..65535 A P / H XF actuation counter.1 CtrMXCoilActivation
Current date of Cradle
679 4 R — — XDATE — A P/H CurrentD_T
Communication Module.
684 3 R — — DATE — A P / H Date of last circuit breaker opening. LastOFContactOpenD_T
687 3 R — — DATE — A P / H Date of last circuit breaker closing. LastOFContactCloseD_T
Date of last trip without an electrical
690 3 R — — DATE — A P/H LastSDContactSetD_T
fault.
693 3 R — — DATE — A P / H Date of last trip with an electrical fault. LastSDEContactSetD _T
Date of last PAF (ready-to-close)
696 3 R — — DATE — A P/H LastPAFContactSetD _T
closing.
699 3 R — — DATE — A P / H Date of last DLO (half moon) closing. LastDLOContactSetD _T
702 3 R — — DATE — A P / H Date of last AD (charged) closing. LastADContactSetD_ T
Date of last address change (register
705 3 R — — DATE — A P/H LastAddressChangeD_T
531).
Date of last reset of Cradle
708 3 R — — DATE — A P/H LastCM_EvtLogResetD_T
Communication Module event log.
Date when time for Cradle
711 4 R — — XDATE — A P/H LastDateTimeSetD_T
Communication Module was last set.
Counter for time setting for Cradle
715 1 R — — INT 0..65535 A P/H CtrDateTimeSets
Communication Module.1
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 91

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 55 – Time Stamping (continued)

Number of Read /
ENGLISH

Register Scale Unit Format Interval A P / H Description Label

Registers Write
Communication profile activation
0 = Not activated
800 1 R/W — — — 0..1 A P/H —
1 = activated
Default value = 02
802 1 R — — — — A P / H Open command status. —
803 1 R — — — — A P / H Close command status. —
Registers 718 to 740 file N° 30 (see “Access to Files” on page 35).
1 The counter automatically cycles from 65535 to 0.
2 Communication profile is available only with a Breaker Communication Module firmware version greater or equal to V2.0 (register 577 must be
greater or equal to 02000)

Cradle Communication Module @ Address xx + 50

Table 56 – Configuration

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Square D product identification
515 1 R — — INT 15140 A P / H 15140 = Cradle Communication EeSQD_Prod_ID
Module.
Modbus address of the COM option
531 1 R/W — — INT 51..97 A P / H (@ xx + 50). EeAdrBus
Default value: 97.
Parity:
• 0: no parity
532 1 R/W — — INT 0..1 A P/H EeParityBus
• 1: even parity
Default value: 1.
Baud rate:
• 1200: 1200 baud
• 2400: 2400 baud
1200.. • 4800: 4800 baud
533 1 R/W — — INT A P/H EeBaudRate
38400 • 9600: 9600 baud
• 19200: 19200 baud
• 38400: 38400 baud
Default value: 19200.

Table 57 – Identification

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Short identifier of the cradle COM
534 2 R/W — — ASCII 0x00..0x7F A P / H option coded over 4 ASCII characters. CCM_Loc
Default value: 0x00.
Long identifier of the cradle COM
option coded over 16 ASCII
536 8 R/W — — ASCII 0x00..0x7F A P / H characters. CCM_NamePlate

Default value: 0x00.

92 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 58 – Diagnostics Counters and Password

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Modbus diagnostics counter—
544 1 R — — INT 0..32767 A P / H messages sent to the slave CtrMsgSentThisUnit
(identical to function 8-14).1
Modbus diagnostics counter—
545 1 R — — INT 0..32767 A P/H CtrMsgSentOtherUnit
messages sent to other slaves.1
Modbus diagnostics counter—bus
546 1 R — — INT 0..32767 A P / H messages managed by the slave CtrMsgRX_ValidCRC
(identical to function 8-11).1
Modbus diagnostics counter—bus
547 1 R — — INT 0..32767 A P / H errors managed by the slave CtrMsgRX_InvalidCRC
(identical to function 8-12).1
Modbus diagnostics counter—
548 1 R — — INT 0..32767 A P / H messages sent to the slave comprising CtrMsgRX_InvalidFC
a non-supported Modbus function.1
Modbus event counter
549 1 R — — INT 0..32767 A P/H CtrModbusEvtCtr
(identical to function 11).1
Modbus diagnostics counter—bus
exception replies managed by the
550 1 R — — INT 0..32767 A P/H CtrExceptionReplies
slave
(identical to function 8-13).1
Modbus diagnostics counter—
broadcast messages received by the
551 1 R — — INT 0..32767 A P/H CtrMsgRX_Broadcast
slave
(identical to function 8-17).1
Control register of the Cradle
Communication Module. This control
word cannot be set by the user. It is
randomly changed each time the
553 1 R — — INT 0..65535 A P/H ControlWord
system is energized. It is necessary to
read the control word before sending
certain commands to the Cradle
Communication Module.
Counter for number of times the Cradle
554 1 R — — INT 0..65535 A P/H EeCtrPowerUp
Communication Module is energized.2
Counter for the number of Cradle
555 1 R — — INT 0..65535 A P / H Communication Module resets, EeCtrReset
whether following power loss or not.2
Cradle Communication Module
577 1 R 1 — INT — A P/H EeFWVersion
firmware version.
1 The counter automatically cycles from 32767 to 0.
2 The counter automatically cycles from 65535 to 0

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 93

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 59 – Cradle Status

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Device status:
if bit 9 (0x0200) is set to 1,
Bitmap the device is connected
661 1 R — — — A P / H if bit 8 (0x0100) is set to 1, CradleStatus
16
the device is disconnected
if bit 10 (0x400) is set to 1,
the device is in the test position.
Counter for change to the “connected”
position:
662 1 R — — INT 0..65535 A P/H CtrRackedIn
the counter increments when bit 8 in
register 661 switches from 0 to 1.1
Counter for change to the
“disconnected” position:
663 1 R — — INT 0..65535 A P/H CtrRackedOut
the counter increments when bit 9 in
register 661 switches from 0 to 1.1
Counter for change to the “test”
position:
664 1 R — — INT 0..65535 A P/H CtrTestPosition
the counter increments when bit 10 in
register 661 switches from 0 to 1.1
1 The counter automatically cycles from 65535 to 0.

Table 60 – Time Stamping

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
current date of Cradle Communication
679 4 R — — XDATE — A P/H CurrentD_T
Module
date of the last change to the
684 3 R — — DATE — A P/H LastRackedInD_T
“connected” position
date of the last change to the
687 3 R — — DATE — A P/H LastRackedOutD_T
“disconnected” position
date of the last change to the
690 3 R — — DATE — A P/H LastTestPositionD_T
“test” position
date of the last change in address
705 3 R — — DATE — A P/H LastAddressChange D_T
(register 531)
date when time for Cradle
711 4 R — — XDATE — A P/H LastDateTimeSetD_T
Communication Module was last set
counter for time setting for Cradle
715 1 R — — INT 0..65535 A P/H CtrDateTimeSets
Communication Module

94 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Metering Module @ Address xx + 200

Table 61 – Voltages

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
1000 1 R x1 V INT 0..1200 — P / H RMS phase-to-phase voltage VAB. V_RMS[0]
1001 1 R x1 V INT 0..1200 — P / H RMS phase-to-phase voltage VBC. V_RMS[1]
1002 1 R x1 V INT 0..1200 — P / H RMS phase-to-phase voltage VCA. V_RMS[2]
1003 1 R x1 V INT 0..1200 — P / H RMS phase-to-neutral voltage VAN.1 V_RMS[3]
1004 1 R x1 V INT 0..1200 — P / H RMS phase-to-neutral voltage VBN .1 V_RMS[4]
1005 1 R x1 V INT 0..1200 — P / H RMS phase-to-neutral voltage VCN.1 V_RMS[5]
Arithmetic mean of the
1006 1 R x1 V INT 0..1200 — P / H phase-to-phase voltages V_AvRMS[0]
1/3 x (VAB+VBC+VCA).
Arithmetic mean of the
1007 1 R x1 V INT 0..1200 — P / H phase-to-neutral voltages V_AvRMS[1]
1/3 x (VAN+VBN+VCN).1
VAB phase-to-phase voltage
-1000.. unbalance with respect to the
1008 1 R x 10 % INT — P/H V_Unbal[0]
+1000 arithmetic mean of the phase-to
phase voltages.
VBC phase-to-phase voltage
-1000.. unbalance with respect to the
1009 1 R x 10 % INT — P/H V_Unbal[1]
+1000 arithmetic mean of the phase-to-
phase voltages.
VCA phase-to-phase voltage
-1000.. unbalance with respect to the
1010 1 R x 10 % INT — P/H V_Unbal[2]
+1000 arithmetic mean of the phase-to-
phase voltages.
VAN phase-to-neutral voltage
-1000.. unbalance with respect to the
1011 1 R x 10 % INT — P/H V_Unbal[3]
+1000 arithmetic mean of the phase-to-
neutral voltages.1
VBN phase-to-neutral voltage
-1000.. unbalance with respect to the
1012 1 R x 10 % INT — P/H V_Unbal[4]
+1000 arithmetic mean of the phase-to-
neutral voltages.1
VCN phase-to-neutral voltage
-1000.. unbalance with respect to the
1013 1 R x 10 % INT — P/H V_Unbal[5]
+1000 arithmetic mean of the phase-to-
neutral voltages.1
Maximum phase-to-phase voltage
-1000..
1014 1 R x 10 % INT — P / H unbalance value in registers V_UnbalMax[0]
+1000
1008, 1009 and 1010.
Maximum phase-to-neutral voltage
-1000..
1015 1 R x 10 % INT — P / H unbalance value in registers V_UnbalMax[1]
+1000
1011, 1012 and 1013.1
1 Value not accessible when the configuration register 3314 returns type 31.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 95

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 62 – Currents
ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
1016 1 R x1 A INT 0..32767 A P / H RMS current on phase A. I_RMS[0]
1017 1 R x1 A INT 0..32767 A P / H RMS current on phase B. I_RMS[1]
1018 1 R x1 A INT 0..32767 A P / H RMS current on phase C. I_RMS[2]
1019 1 R x1 A INT 0..32767 A P / H RMS current on the neutral.1 I_RMS[3]
Maximum rms current in registers
1020 1 R x1 A INT 0..32767 A P/H I_Max
1016, 1017, 1018 and 1019.
Ground-fault current:
1021 1 R x1 A INT 0..32767 A P / H if this current exceeds 32767 A, I_RMSGnd
the register blocks at 32767.2
Earth-leakage current:
1022 1 R x1 mA INT 0..32767 A P / H if this current exceeds 32767 A, I_RMSVigi
the register blocks at 32767.3
1023 1 R x1 A INT 0..32767 — H Apparent current phase A (peak √2). I_APP[0]
1024 1 R x1 A INT 0..32767 — H Apparent current phase B (peak √2). I_APP[1]
1025 1 R x1 A INT 0..32767 — H Apparent current phase C (peak √2). I_APP[2]
1026 1 R x1 A INT 0..32767 — H Apparent current neutral (peak √2). I_APP[3]
Arithmetic mean of phase currents
1027 1 R x1 A INT 0..32767 — P/H I_Mean
A, B and C: 1/3 x (IA+IB+IC).
IA current unbalance with respect to
-1000..
1028 1 R x 10 % INT — P / H the arithmetic mean of the phase I_Unbal[0]
+1000
currents.
IB current unbalance with respect to
-1000..
1029 1 R x 10 % INT — P / H the arithmetic mean of the phase I_Unbal[1]
+1000
currents.
IC current unbalance with respect to
-1000..
1030 1 R x 10 % INT — P / H the arithmetic mean of the phase I_Unbal[2]
+1000
currents.
IN current unbalance with respect to
-1000..
1031 1 R x 10 % INT — P / H the arithmetic mean of the phase I_Unbal[3]
+1000
currents.1
-1000.. Maximum current unbalance in
1032 1 R x 10 % INT — P/H I_UnbalMax
+1000 registers 1028, 1029 and 1030.
1033 1 R — — — — — P / H Reserved. —
1 Value not accessible when the configuration register 3314 returns type 31 or 40.
2 Accessible only with Micrologic 5.0 P / H and 6.0 A / P / H.
3 Accessible only with Micrologic 7.0 A / P / H.

Table 63 – Power

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
1034 1 R x1 kW INT +/- 0..32767 — P / H Active power on phase A.1, 2 ActivePwr[0]
1035 1 R x1 kW INT +/- 0..32767 — P / H Active power on phase B.1, 2 ActivePwr[1]
1036 1 R x1 kW INT +/- 0..32767 — P / H Active power on phase C.1, 2 ActivePwr[2]
1037 1 R x1 kW INT +/- 0..32767 — P / H Total active power.2 ActivePwr[3]
1038 1 R x1 kVAR INT +/- 0..32767 — P / H Reactive power on phase A.1, 2 ReactivePwr[0]
1039 1 R x1 kVAR INT +/- 0..32767 — P / H Reactive power on phase B.1, 2 ReactivePwr[1]
1040 1 R x1 kVAR INT +/- 0..32767 — P / H Reactive power on phase C.1, 2 ReactivePwr[2]
1041 1 R x1 kVAR INT +/- 0..32767 — P / H Total reactive power.2 ReactivePwr[3]
Continued on next page

96 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 63 – Power (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
1034 1 R x1 kW INT +/- 0..32767 — P / H Active power on phase A.1, 2 ActivePwr[0]
Apparent power on phase A with
1042 1 R x1 kVA INT 0..32767 — P/H ApparentPwr[0]
3 wattmeters.1
Apparent power on phase B with
1043 1 R x1 kVA INT 0..32767 — P/H ApparentPwr[1]
3 wattmeters.1
Apparent power on phase C with
1044 1 R x1 kVA INT 0..32767 — P/H ApparentPwr[2]
3 wattmeters.1
1045 1 R x1 kVA INT 0..32767 — P / H Total apparent power. ApparentPwr[3]
1 Value not accessible when the configuration register 3314 returns type 31.
2 The sign of the active and reactive power depends on configuration register 3316.

Table 64 – Power Factor

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
-1000.. Power factor on phase A (absolute value
1046 1 R x 1000 none INT — P/H PF[0]
+1000 equal to |P|/S).1, 2
-1000.. Power factor on phase B (absolute value
1047 1 R x 1000 none INT — P/H PF[1]
+1000 equal to |P|/S).1, 2
-1000.. Power factor on phase C (absolute value
1048 1 R x 1000 none INT — P/H PF[2]
+1000 equal to |P|/S).1, 2
-1000.. Total power factor (absolute value
1049 1 R x 1000 none INT — P/H PF[3]
+1000 equal to |Ptotal|/Stotal).2
Fundamental power factor on phase A (its
-1000.. absolute value is equal to |FundP|/FundS).
1050 1 R x 1000 none INT — H FundPF[0]
+1000 Sign convention the same as the one for the
real power factor. N/A if type 31 network.
-1000..
1051 1 R x 1000 none INT — H Same as above phase B. FundPF[1]
+1000
-1000..
1052 1 R x 1000 none INT — H Same as above phase C. FundPF[2]
+1000
Total fundamental power factor (its absolute
-1000.. value is equal to |FundPtot|/FundStot).
1053 1 R x 1000 none INT — H FundPF[3]
+1000 Sign convention the same as the one for the
real power factor.
1 Value not accessible when the configuration register 3314 returns type 31.
2 The sign of the power factor depends on configuration register 3318.

Table 65 – Frequency

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
1054 1 R x 10 Hz INT 0..4000 — P / H System frequency. Frequency
Duration of the interval between the last
1055 1 R x.001 s INT 0..32767 — P / H update of real time values and the current UpdateIval
table (about 1s).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 97

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 66 – Fundamental
ENGLISH

Number of Read /
Register Scale1 Unit Format Interval A P / H Description Label
Registers Write
Fundamental (RMS) of
1056 1 R D V INT 0..1200 — H FundV_RMS[0]
phase-to-phase voltage VAB.
1057 1 R D V INT 0..1200 — H Same as above VBC. FundV_RMS[1]
1058 1 R D V INT 0 to 1200 — H Same as above VBA. FundV_RMS[2]
Fundamental (RMS) of phase-to-
1059 1 R D V INT 0..1200 — H neutral voltage VAN. FundV_RMS[3]
—N/A if type 31 network.
1060 1 R D V INT 0..1200 — H Same as above VBN. FundV_RMS[4]
1061 1 R D V INT 0..1200 — H Same as above VCN. FundV_RMS[5]
1062 6 R — — — — — H Reserved. ReservedA
Fundamental (RMS) of phase A
1068 1 R A A INT 0..32767 — H FundI_RMS[0]
current.
Same as above phase B.
1069 1 R A A INT 0..32767 — H FundI_RMS[1]
Measured with type 31.
1070 1 R A A INT 0..32767 — H Same as above phase C. FundI_RMS[2]
Same as above neutral.
1071 1 R B A INT 0..32767 — H —N/A with type 31, 40 networks. FundI_RMS[3]
Measured with type 41.
1072 4 R — — — — — H Reserved. —
Phase A fundamental active power
with 3 wattmeters (type 40 & 41) N/A
1076 1 R E kW INT 0..32767 — H for type 31. FundActivePwr[0]
Same sign convention as with active
power.
Phase B fundamental active power
with 3 wattmeters (type 40 & 41) N/A
1077 1 R E KW INT 0..32767 — H for type 31. FundActivePwr[1]
Same sign convention as with active
power.
Phase C fundamental active power
with 3 wattmeters (type 40 & 41) N/A
1078 1 R E KW INT 0..32767 — H for type 31. FundActivePwr[2]
Same sign convention as with active
power.
Total fundamental active power.
1079 1 R E kW INT 0..32767 — H Same sign convention as with active FundActivePwr[3]
power
Phase A fundamental reactive power
1080 1 R E kVAR INT 0..32767 — H with 3 wattmeters (type 40 & 41) N/A FundReactivePwr[0]
for type 31.
Phase B fundamental reactive power
1081 1 R E kVAR INT 0..32767 — H with 3 wattmeters (type 40 & 41) N/A FundReactivePwr[1]
for type 31.
Phase C fundamental reactive power
1082 1 R E kVAR INT 0..32767 — H with 3 wattmeters (type 40 & 41). FundReactivePwr[2]
N/A for type 31.
1083 1 R E kVAR INT 0..32767 — H Total fundamental reactive power. FundReactivePwr[3]
Phase A fundamental apparent
1084 1 R E kVA INT 0..32767 — H power. FundApparentPwr[0]
N/A for type 31.
Continued on next page

98 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 66 – Fundamental (continued)

Number of Read /

ENGLISH
Register Scale1 Unit Format Interval A P / H Description Label
Registers Write
Phase B fundamental apparent
1085 1 R E KVA INT 0..32767 — H power. FundApparentPwr[1]
N/A for type 31.
Phase C fundamental apparent
1086 1 R E KVA INT 0..32767 — H power. FundApparentPwr[2]
N/A for type 31.
1087 1 R E kVA INT 0..32767 — H Total fundamental apparent power. FundApparentPwr[3]
Phase A distortion power.
1088 1 R E kVAR INT 0..32767 — H DistortionPwr[0]
N/A for type 31.
Phase B distortion power.
1089 1 R E kVAR INT 0..32767 — H DistortionPwr[1]
N/A for type 31.
Phase C distortion power.
1090 1 R E kVAR INT 0..32767 — H DistortionPwr[2]
N/A for type 31.
1091 1 R E kVAR INT 0..32767 — H Total distortion power. DistortionPwr[3]
1 For scale values, see page 85.

Table 67 – Total Harmonic Distortion

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Total harmonic distortion of VAB
1092 1 R x 10 % INT 0..5000 — H THD_V[0]
voltage compared to the fundamental.
1093 1 R x 10 % INT 0..5000 — H Same as above VBC. THD_V[1]
1094 1 R x 10 % INT 0..5000 — H Same as above VCA. THD_V[2]
Total harmonic distortion of VAN
1095 1 R x 10 % INT 0..5000 — H voltage compared to the fundamental. THD_V[3]
—N/A with type 31 network.
1096 1 R x 10 % INT 0..5000 — H Same as above VBN. THD_V[4]
1097 1 R x 10 % INT 0..5000 — H Same as above VCN. THD_V[5]
Total harmonic distortion of phase A
1098 1 R x 10 % INT 0..5000 — H THD_I[0]
current compared to the fundamental.
Same as above phase B.
1099 1 R x 10 % INT 0..5000 — H THD_I[1]
Measured with type 31.
1100 1 R x 10 % INT 0..5000 — H Same as above phase C. THD_I[2]
Same as above neutral.
—N/A with type 31 networks.
1101 1 R x 10 % INT 0..5000 — H THD_I[3]
Measured with type 41,
calculated with type 40.
Total harmonic distortion of VAB
1102 1 R x 10 % INT 0..1000 — H thd_V[0]
voltage compared to the RMS value.
1103 1 R x 10 % INT 0..1000 — H Same as above VBC. thd_V[1]
1104 1 R x 10 % INT 0..1000 — H Same as above VCA. thd_V[2]
Total harmonic distortion of VAN
1105 1 R x 10 % INT 0..1000 — H voltage compared to the RMS value. thd_V[3]
—N/A with type 31 network.
Continued on next page
1106 1 R x 10 % INT 0..1000 — H Same as above VBN. thd_V[4]
1107 1 R x 10 % INT 0..1000 — H Same as above VCN. thd_V[5]
Total harmonic distortion of phase A
1108 1 R x 10 % INT 0..1000 — H thd_I[0]
current compared to the RMS value.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 99

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 67 – Total Harmonic Distortion (continued)

Number of Read /
ENGLISH

Register Scale Unit Format Interval A P / H Description Label

Registers Write
Same as above phase B.
1109 1 R x 10 % INT 0..1000 — H thd_I[1]
Measured with type 31.
1110 1 R x 10 % INT 0..1000 — H Same as above phase C. thd_I[2]
Same as above neutral.
—N/A with type 31 networks.
1111 1 R x 10 % INT 0..1000 — H thd_I[3]
Measured with type 41,
calculated with type 40.
Phase shift VAB / IA with type 31;
1112 1 R x 10 Deg INT 0..3600 — H FundVI_Angle[0]
VAN / IA with type 40 & 41.
Phase shift VBC / IB with type 31;
1113 1 R x 10 Deg INT 0..3600 — H FundVI_Angle[1]
VBN / IB with type 40 & 41.
Phase shift VCA / IC with type 31;
1114 1 R x 10 Deg INT 0..3600 — H FundVI_Angle[2]
Vcn / Ic with type 40 & 41.
Phase A K-factor.
1115 1 R x 10 None INT 0..1000 — H —N/A in 400 Hz nominal freq. I_Kfactor[0]
networks.
Phase B K-factor.
1116 1 R x 10 None INT 0..1000 — H —N/A in 400 Hz nominal freq. I_Kfactor[1]
networks.
Phase C K-factor.
1117 1 R x 10 None INT 0..1000 — H —N/A in 400 Hz nominal freq. I_Kfactor[2]
networks.
Neutral K-factor.
—N/A with type 30 and 31 networks.
1118 1 R x 10 None INT 0..1000 — H I_Kfactor[3]
—N/A in 400 Hz nominal freq.
Networks.
VAB voltage peak factor.
1119 1 R x 100 None INT 0..10000 — H —N/A with type 40 and 41 networks. V_Crest[0]
—N/A in 400 Hz config.
VBCvoltage peak factor.
1120 1 R x 100 None INT 0..10000 — H —N/A with type 40 and 41 networks. V_Crest[1]
—N/A in 400 Hz config.
VCA voltage peak factor.
1121 1 R x 100 None INT 0..10000 — H —N/A with type 40 and 41 networks. V_Crest[2]
—N/A in 400 Hz config.
VAN voltage peak factor.
1122 1 R x 100 None INT 0..10000 — H —N/A with type 31 networks. V_Crest[3]
—N/A in 400 Hz config.
VBN voltage peak factor.
1123 1 R x 100 None INT 0..10000 — H —N/A with type 31 networks. V_Crest[4]
—N/A in 400 Hz config.
VCN voltage peak factor.
1124 1 R x 100 None INT 0..10000 — H —N/A with type 31 networks. V_Crest[5]
—N/A in 400 Hz config.
Phase A current peak factor.
1125 1 R x 100 None INT 0..10000 — H I_Crest[0]
—N/A in 400 Hz config.
Continued on next page

100 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 67 – Total Harmonic Distortion (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Phase B current peak factor.
1126 1 R x 100 None INT 0..10000 — H I_Crest[1]
—N/A in 400 Hz config.
Phase C current peak factor.
1127 1 R x 100 None INT 0..10000 — H I_Crest[2]
—N/A in 400 Hz config.
Neutral current peak factor.
—N/A with type 31, 40 networks.
1128 1 R x 100 None INT 0..10000 — H V_Crest[1]
Measured with type 41.
—N/A in 400 Hz config.
1129 4 R — — — — — H Reserved.
Phase shift VAB / VAB with type 31;
1133 1 R x 10 Deg INT 0..3600 — H VAN / VAN with type 40 & 41. Definition FundVV[0]
leads to content being always 0.
Phase shift VBC / VAB with type 31;
VBN / VAN with type 40 & 41. Under
1134 1 R x 10 Deg INT 0..3600 — H FundVV[1]
phase balanced conditions, equals
240 degrees.
Phase shift VCA / VAB with type 31;
VCN / VAN with type 40 & 41. Under
1135 1 R x 10 Deg INT 0..3600 — H FundVV[2]
phase balanced conditions, equals
120 degrees.

Registers 1300 to 1599: minimum values of the real-time measurements from

1000 to 1299.
The minimum values for the real-time measurements may be accessed at the
registers of the real-time values + 300 (available on Micrologic P and H).
Registers 1600 to 1899: maximum values of the real-time measurements from
1000 to 1299.
The maximum values for the real-time measurements may be accessed at the
registers of the real-time values + 600 (available on Micrologic P and H).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 101

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 68 – Energy
ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0..+/-
9999
MOD
2000 4 R x1 kWh 9999 — P / H Total active energy.1 EeActiveEnergy
10000
9999
9999
0..+/-
9999
kVAR MOD
2004 4 R x1 9999 — P / H Total reactive energy.1 EeReactiveEnergy
h 10000
9999
9999
0..+/-
9999
MOD Active energy positively
2008 4 R x1 kWh 9999 — P/H EeActiveEnergyln
10000 incremented.2
9999
9999
0..+/-
9999
MOD Active energy negatively
2012 4 R x1 kWh 9999 — P/H EeActiveEnergyOut
10000 incremented.2
9999
9999
0..+/-
9999
kVAR MOD Reactive energy positively
2016 4 R x1 9999 — P/H EeReactiveEnergyIn
h 10000 incremented.2
9999
9999
0..+/-
9999
kVAR MOD Reactive energy negatively EeReactiveEnergyO
2020 4 R x1 9999 — P/H
h 10000 incremented.2 ut
9999
9999
0..+/-
9999
MOD
2024 4 R x1 kVAh 9999 — P / H Total apparent energy. EeApparentEnergy
10000
9999
9999
1 As standard, the total calculated energy values are absolute total values. They represent the sum of the energy in and out values.
EP = EP in + EP out
EQ = EQ in + EQ out
2 The Energy in and Energy out values are incremented according to the power sign set in the Micrologic menu « Micrologic set-up » (see register
3316).

102 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 69 – Demand Current

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
2200 1 R x1 A INT 0..32767 — P / H Current demand on phase A. I_Dmd[0]
2201 1 R x1 A INT 0..32767 — P / H Current demand on phase B. I_Dmd[1]
2202 1 R x1 A INT 0..32767 — P / H Current demand on phase C. I_Dmd[2]
2203 1 R x1 A INT 0..32767 — P / H Current demand on the neutral.1 I_Dmd[3]
Current demand maximum on phase
2204 1 R x1 A INT 0..32767 — P/H NvI_DmdPk[0]
A since the last reset.
Current demand maximum on phase
2205 1 R x1 A INT 0..32767 — P/H NvI_DmdPk[1]
B since the last reset.
Current demand maximum on phase
2206 1 R x1 A INT 0..32767 — P/H NvI_DmdPk[2]
C since the last reset.
Current demand maximum on the
2207 1 R x1 A INT 0..32767 — P/H NvI_DmdPk[3]
neutral since the last reset.1
1 Value not accessible when the configuration register 3314 returns type 31 or 40

Table 70 – K-Factor Demand

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
2212 1 R x 10 None INT 0..1000 — H K-factor demand, phase A. K_Dmd[0]
2213 1 R x 10 None INT 0..1000 — H Same as above phase B. K_Dmd[1]
2214 1 R x 10 None INT 0..1000 — H Same as above phase C. K_Dmd[2]
Same as above neutral. N/A with type
2215 1 R x 10 None INT 0..1000 — H K_Dmd[3]
31 or 40 network.
K-factor demand peak, phase A,
2216 1 R x 10 None INT 0..1000 — H NvK_DmdPk[0]
since last reset.
2217 1 R x 10 None INT 0..1000 — H Same as above phase B. NvK_DmdPk[1]
2218 1 R x 10 None INT 0..1000 — H Same as above phase C. NvK_DmdPk[2]
Same as above neutral. N/A with type
2219 1 R x 10 None INT 0..1000 — H NvK_DmdPk[3]
31 or 40 network.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 103

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 71 – Demand Power

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
2224 1 R x1 kW INT 0..32767 — P / H Total active-power demand.1 ActivePwrDmd
Active-power demand maximum since
2225 1 R x1 kW INT 0..32767 — P/H NvActivePwrDmdPk
the last reset.
Predicted active-power demand at the
2226 1 R x1 kW INT 0..32767 — P/H ActivePwrDmdPred
end of the window.2
-1000.. Total power factor at last active-power NvPF_atActivePwrD
2227 1 R x 1000 sans INT — P/H
+1000 demand maximum. mdPk
Value of reactive-power demand at NvkVAR_atActivePwr
2228 1 R x1 kVAR INT 0..32767 — P/H
last active-power demand maximum. DmdPk
Value of apparent-power demand at NvkVA_atActivePwr
2229 1 R x1 kVA INT 0..32767 — P/H
last active-power demand maximum. DmdPk
2230 1 R x1 kVAR INT 0..32767 — P / H Total reactive-power demand.1 ReactivePwrDmd
Reactive-power demand maximum
2231 1 R x1 kVAR INT 0..32767 — P/H NvReactivePwrDmdPk
since the last reset.
Predicted reactive-power demand at
2232 1 R x1 kVAR INT 0..32767 — P/H ReactivePwrDmdPred
the end of the window.2
-1000.. Total power factor at last reactive- NvPF_atReactivePwr
2233 1 R x 1000 sans INT — P/H
+1000 power demand maximum. DmdPk
Value of active-power demand at last NvkW_atReactivePwr
2234 1 R x1 kW INT 0..32767 — P/H
reactive-power demand maximum. DmdPk
Value of apparent-power demand at
NvkVA_atReactivePwr
2235 1 R x1 kVA INT 0..32767 — P / H last reactive-power demand
DmdPk
maximum.
2236 1 R x1 kVA INT 0..32767 — P / H Total apparent power demand.1 ApparentPwrDmd
Apparent-power demand maximum
2237 1 R x1 kVA INT 0..32767 — P/H NvApparentPwrDmdPk
since the last reset.
Predicted apparent-power demand at
2238 1 R x1 kVA INT 0..32767 — P/H ApparentPwrDmdPred
the end of the window.2
-1000.. Total power factor at last apparent- NvPF_atApparentPwr
2239 1 R x 1000 sans INT — P/H
+1000 power demand maximum. DmdPk
Value of active-power demand at last NvkW_atApparentPwr
2240 1 R x1 kW INT 0..32767 — P/H
apparent-power demand maximum. DmdPk
Value of reactive-power demand at
NvkVAR_atApparent
2241 1 R x1 kVAR INT 0..32767 — P / H last apparent-power demand
PwrDmdPk
maximum.
1 Value updated at end of window for the “block” mode. For the “sliding” mode, the value is updated every 15 seconds.
2 Value updated every 15 seconds for both “block” and “sliding” modes.

104 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 72 – Time Stamping

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
3000 4 R — — DATE — — P / H Current date of the metering module. XtedDateTime
Date of last current demand maximum
3005 3 R — — DATE — — P/H NvI_DmdPk[0]
IA (register 2204).
Date of last current demand maximum
3008 3 R — — DATE — — P/H NvI_DmdPk[1]
IB (register 2205).
Date of last current demand maximum
3011 3 R — — DATE — — P/H NvI_DmdPk[2]
IC (register 2206).
Date of last current demand maximum
3014 3 R — — DATE — — P/H NvI_DmdPk[3]
on the neutral (register 2207).1
Date of last active-power demand
3017 3 R — — DATE — — P/H NvActivePwrDmdPk
maximum (register 2224).
Date of last reactive-power demand
3020 3 R — — DATE — — P/H NvReactivePwrDmdPk
maximum (register 2230).
Date of last apparent-power demand
3023 3 R — — DATE — — P/H NvApparentPwrDmdPk
maximum (register 2236).
Date of last reset of current demand
3026 3 R — — DATE — — P/H NvLastI_DmdReset
maximum values.
Date of last reset of power demand
3029 3 R — — DATE — — P/H NvLastPwrDmdReset
maximum values.
Date-Time of last min registers reset
3032 3 R — — DATE — — P/H NvLastMinReset
(1300-1599).2
Date-Time of last max registers reset
3035 3 R — — DATE — — P/H NvLastMaxReset
(1600-1899).2
3038 3 R — — DATE — — P / H Date of last reset of energy meters. NvLastEnReset
Date of appearance of last K-factor
3041 3 R — — DATE — — P/H NvK_DmdPk[0]
demand peak (phase A).
Date of appearance of last K-factor
3044 3 R — — DATE — — P/H NvK_DmdPk[1]
demand peak (phase B).
Date of appearance of last K-factor
3047 3 R — — DATE — — P/H NvK_DmdPk[2]
demand peak (phase C).
Date of appearance of last K-factor
3050 3 R — — DATE — — P / H demand peak (neutral) N/A for type 31 NvK_DmdPk[3]
& 40 networks.
Date of appearance of last I2 demand
3053 3 R — — DATE — — P/H NvI2_DmdPk[0]
peak (phase A).
Date of appearance of last I2 demand
3056 3 R — — DATE — — P/H NvI2_DmdPk[1]
peak (phase B).
Date of appearance of last I2 demand
3059 3 R — — DATE — — P/H NvI2_DmdPk[2]
peak (phase C).
Date of appearance of last I2
3062 3 R — — DATE — — P / H demand peak (neutral) N/A for type NvI2_DmdPk[3]
31 & 40 networks.
1 N/A for type 31 or 40 networks.
2 NOTE: This register is updated whenever any of the min register is reset. Command interface authorizes user to clear min of Current RMS &
Unbal values, Voltage rms & Unbal values, frequency, P/Q/S/PF, Fundamental quantities & THD, Voltage Crest & Current crest independently.
However, since only one date/time of last reset is maintained, it is recommended to always set all bits in the command that resets min values.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 105

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 73 – Configuration
Number of Read /
ENGLISH

Register Scale Unit Format Interval A P / H Description Label

Registers Write
Control word for the metering module.
This control word may not be user set. It
3300 1 R — — INT 0..65535 — P / H is randomly modified and must be read ControlWord
before sending certain commands to the
metering module.
Short identifier of the metering module,
3303 2 R/W — — ASCII 0x00..0x7F — P / H coded over four ASCII characters. NvUnitLabel
Default value: “set!”
Long identifier of the metering module,
3305 8 R/W — — ASCII 0x00..0x7F — P / H coded over 16 ASCII characters. NvUnitNamePlate
Default value: “please set me up”.
Selection of the calculation algorithm.
• If you have a system type: 3 Phase,
4 wire, 4 current transformer (3P circuit
breaker with external neutral CT
connected + external neutral voltage
tap not connected to VN), select
system type 30: measurement of the
phase-to-neutral voltage is not
available measurement of the neutral
current is available.
• If you have a system type: 3 phase,
3 wire, 3 current transformer (3P circuit
breaker without external neutral CT
connected, neutral not connected to
VN), select system type 31:
measurement of the phase-to-phase
voltages is available measurement of
the phase-to-neutral voltages is not
available measurement of the neutral
30, 31, current is not available.
3314 1 R/W — — INT — P/H • If you have a system type: 3 phase, NvSystemType
40, 41
4 wire, 3 current transformer (3P circuit
breaker without external neutral CT
connected, neutral connected to VN),
select system type 40: measurement
of the phase-to-phase voltages is
available measurement of the phase-
to-neutral voltages is available
measurement of the neutral current is
not available.
• If you have a system type: 3 phase,
4 wire, 4 current transformer (3P circuit
breaker with external neutral CT
connected or 4P circuit breaker,
neutral connected to VN), select
system type 41: measurement of the
phase-to-phase voltages is available
measurement of the phase-to-neutral
voltages is available measurement of
the neutral current is available.
Default value: type 41.
Continued on next page

106 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 73 – Configuration (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Sign convention for the power:
• 0: “+” if the active power flows from
upstream (top) to downstream
(bottom) (↓).
3316 1 R/W — — INT 0,1 — P/H NvConvPwrSign
• 1: “+” if the active power flows from
downstream (bottom) to upstream
(top) (↑).
Default value: 0.
Sign convention for the reactive power:
• 0: alternate IEEE convention,
3317 1 R/W — — INT 0,1 — P/H NvConvReactivePwrsign
• 1: IEEE & IEC convention.
Default value: 1.1
Sign convention for the power factor:
• 0: IEC convention,
3318 1 R/W — — INT 0,1, 2 — P/H • 1: alternate IEEE convention, NvConvPFSign
• 2: IEEE convention.
Default value: 2.1
Reactive power calculation convention:
3319 1 R/W — — INT 0,1 — H • 0: fundamental alone, NvConvReactivePwrCalc
• 1: harmonics included [DEFAULT].
Total energy metering convention:
• 0: absolute accumulation (E = E+ + E-
3324 1 R/W — — INT 0,1 — P/H ), NvEnAccumulationMode
• 1: signed accumulatio.n (E = E+ - E-).
Default = 0: Absolute
Current-demand calculation method;
window type:
3351 1 R/W — — INT — — P/H • 0: Block interval; sliding, NvDmdMethod_I
• 1: Thermal; sliding.
Default value: 1.
Duration in minutes of the current-
3352 1 R/W x1 min INT 5..60 — P / H demand calculation window. NvDmdIval_I
Default value: 15 minutes.2
Power-demand calculation method;
window type:
• 0: Block interval; sliding,
3354 1 R/W — — INT — — P/H • 1: Thermal; sliding, NvDmdMethod_Pwr
• 2: Block interval; block,
• 5: Synchronized to communication.
Default value: 0.
Duration in minutes of the power-demand
3355 1 R/W x1 min INT 5..60 — P / H calculation window. NvDmdIval_Pwr
Default value: 15 minutes.
Square D Identification number:
Micrologic A: PM = 15131,
3816 1 R — — INT 0..32767 A P/H EeSQD_Prod_ID
P: PM = 15133, MM = 15134,
H: PM = 15135, MM = 15136.
1 To have IEE alt., set 3317 to 0 and 3318 to 1.
To have IEC., set 3317 to 1 and 3318 to 0.
To have IEEE., set 3317 to 1 and 3318 to 2.
2 The duration in minutes of the current-demand calculation window set in this register is used for the maximum current IA, IB, IC and IN protection functions.
When these protection functions are active, it is possible to modify the duration of the calculation window whether the protective cover for the dial settings
is closed or not, whether remote access is authorized (Micrologic) or not, and whether the supervisor knows the remote-access control word or not.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 107

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 74 – Spectral Components (Odd Rank)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
% value (in respect with the fundamental) of
4100 1 R x 10 % INT 0..1200 — H the amplitude of harmonic 3 of VAB. V_h3[0]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
4101 1 R x 10 % INT 0..1200 — H of the amplitude of harmonic 3 of VBC. V_h3[1]
—N/A in 400 Hz systems
% value (in respect with the fundamental)
4102 1 R x 10 % INT 0..1200 — H of the amplitude of harmonic 3 of VCA. V_h3[2]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
of the amplitude of harmonic 3 of VAN.
4103 1 R x 10 % INT 0..1200 — H V_h3[3]
—N/A in 400 Hz systems.
—N/A with type 31.
% value (in respect with the fundamental)
of the amplitude of harmonic 3 of VBN.
4104 1 R x 10 % INT 0..1200 — H V_h3[4]
—N/A in 400 Hz systems.
—N/A with type 31.
% value (in respect with the fundamental)
of the amplitude of harmonic 3 of VCN.
4105 1 R x 10 % INT 0..1200 — H V_h3[5]
—N/A in 400 Hz systems.
—N/A with type 31.
4106 6 R x 10 % INT 0..1200 — H Same as above harmonic 5. V_h5[..]
4112 6 R x 10 % INT 0..1200 — H Same as above harmonic 7. V_h7[..]
4118 6 R x 10 % INT 0..1200 — H Same as above harmonic 9. V_h9[..]
4124 6 R x 10 % INT 0..1200 — H Same as above harmonic 11. V_h11[..]
4130 6 R x 10 % INT 0..1200 — H Same as above harmonic 13. V_h13[..]
4136 6 R x 10 % INT 0..1200 — H Same as above harmonic 15. V_h15[..]
4142 6 R x 10 % INT 0..1200 — H Same as above harmonic 17. V_h17[..]
4148 6 R x 10 % INT 0..1200 — H Same as above harmonic 19. V_h19[..]
4154 6 R x 10 % INT 0..1200 — H Same as above harmonic 21. V_h21[..]
4160 6 R x 10 % INT 0..1200 — H Same as above harmonic 23. V_h23[..]
4166 6 R x 10 % INT 0..1200 — H Same as above harmonic 25. V_h25[..]
4172 6 R x 10 % INT 0..1200 — H Same as above harmonic 27. V_h27[..]
4178 6 R x 10 % INT 0..1200 — H Same as above harmonic 29. V_h29[..]
4184 6 R x 10 % INT 0..1200 — H Same as above harmonic 31. V_h31[..]
% value (in respect with the fundamental)
4190 1 R x 10 % INT 0..32767 — H of the amplitude of harmonic 3 of Ia. I_h3[0]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
4191 1 R x 10 % INT 0..32767 — H of the amplitude of harmonic 3 of Ib. I_h3[1]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
4192 1 R x 10 % INT 0..32767 — H of the amplitude of harmonic 3 of Ic. I_h3[2]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
of the amplitude of harmonic 3 of In.
4193 1 R x 10 % INT 0..32767 — H I_h3[3]
—N/A in 400 Hz systems.
—N/A with type 31.
Continued on next page

108 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 74 – Spectral Components (Odd Rank) (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
4194 4 R x 10 % INT 0..32767 — H Same as above harmonic 5. I_h5[..]
4198 4 R x 10 % INT 0..32767 — H Same as above harmonic 7. I_h7[..]
4202 4 R x 10 % INT 0..32767 — H Same as above harmonic 9. I_h9[..]
4206 4 R x 10 % INT 0..32767 — H Same as above harmonic 11. I_h11[..]
4210 4 R x 10 % INT 0..32767 — H Same as above harmonic 13. I_h13[..]
4214 4 R x 10 % INT 0..32767 — H Same as above harmonic 15. I_h15[..]
4218 4 R x 10 % INT 0..32767 — H Same as above harmonic 17. I_h17[..]
4222 4 R x 10 % INT 0..32767 — H Same as above harmonic 19. I_h19[..]
4226 4 R x 10 % INT 0..32767 — H Same as above harmonic 21. I_h21[..]
4230 4 R x 10 % INT 0..32767 — H Same as above harmonic 23. I_h23[..]
4234 4 R x 10 % INT 0..32767 — H Same as above harmonic 25. I_h25[..]
4238 4 R x 10 % INT 0..32767 — H Same as above harmonic 27. I_h27[..]
4242 4 R x 10 % INT 0..32767 — H Same as above harmonic 29. I_h29[..]
4246 4 R x 10 % INT 0..32767 — H Same as above harmonic 31. I_h31[..]
Phase of harmonic 3 of VAB.
4250 1 R x 10 Deg INT 0..3600 — H V_Phi3[0]
—N/A in 400 Hz systems.
Phase of harmonic 3 of VBC.
4251 1 R x 10 Deg INT 0..3600 — H V_Phi3[1]
—N/A in 400 Hz systems.
Phase of harmonic 3 of VCA.
4252 1 R x 10 Deg INT 0..3600 — H V_Phi3[2]
—N/A in 400 Hz systems.
Phase of harmonic 3 of VAN.
4253 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. V_Phi3[3]
—N/A with type 31.
Phase of harmonic 3 of VBN.
4254 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. V_Phi3[4]
—N/A with type 31.
Phase of harmonic 3 of VCN.
4255 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. V_Phi3[5]
—N/A with type 31.
4256 6 R x 10 Deg INT 0..3600 — H Same as above harmonic 5. V_Phi5[..]
4262 6 R x 10 Deg INT 0..3600 — H Same as above harmonic 7. V_Phi7[..]
Phase of harmonic 3 of IA.
4340 1 R x 10 Deg INT 0..3600 — H I_Phi3[0]
—N/A in 400 Hz systems.
Phase of harmonic 3 of IB.
4341 1 R x 10 Deg INT 0..3600 — H I_Phi3[1]
—N/A in 400 Hz systems.
Phase of harmonic 3 of IC.
4342 1 R x 10 Deg INT 0..3600 — H I_Phi3[2]
—N/A in 400 Hz systems.
Phase of harmonic 3 of IN.
4343 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. I_Phi3[3]
—N/A with type 31.
4344 4 R x 10 Deg INT 0..3600 — H Same as above harmonic 5. I_Phi5[..]
4348 4 R x 10 Deg INT 0..3600 — H Same as above harmonic 7. I_Phi7[..]
4352 4 R x 10 Deg INT 0..3600 — H Same as above harmonic 9. I_Phi9[..]

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 109

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 75 – Spectral Components (Even Rank)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
% value (in respect with the fundamental)
4400 1 R x 10 % INT 0..1200 — H of the amplitude of harmonic 2 of VAB. V_h2[0]
—N/A in 400 Hz systems.
% value (in respect with the fundamental) of
4401 1 R x 10 % INT 0..1200 — H the amplitude of harmonic 2 of VBC. V_h2[1]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
4402 1 R x 10 % INT 0..1200 — H of the amplitude of harmonic 2 of VCA V_h2[2]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
of the amplitude of harmonic 2 of VAN.
4403 1 R x 10 % INT 0..1200 — H V_h2[3]
—N/A in 400 Hz systems.
—N/A with type 31.
% value (in respect with the fundamental)
of the amplitude of harmonic 2 of VBN.
4404 1 R x 10 % INT 0..1200 — H V_h2[4]
—N/A in 400 Hz systems.
—N/A with type 31.
% value (in respect with the fundamental)
of the amplitude of harmonic 2 of VCN.
4405 1 R x 10 % INT 0..1200 — H V_h2[5]
—N/A in 400 Hz systems.
—N/A with type 31.
4406 6 R x 10 % INT 0..1200 — H Same as above harmonic 4. V_h4[..]
4412 6 R x 10 % INT 0..1200 — H Same as above harmonic 6. V_h6[..]
4418 6 R x 10 % INT 0..1200 — H Same as above harmonic 8. V_h8[..]
4424 6 R x 10 % INT 0..1200 — H Same as above harmonic 10. V_h10[..]
4430 6 R x 10 % INT 0..1200 — H Same as above harmonic 12. V_h12[..]
4436 6 R x 10 % INT 0..1200 — H Same as above harmonic 14. V_h14[..]
4442 6 R x 10 % INT 0..1200 — H Same as above harmonic 16. V_h16[..]
4448 6 R x 10 % INT 0..1200 — H Same as above harmonic 18. V_h18[..]
4454 6 R x 10 % INT 0..1200 — H Same as above harmonic 20. V_h20[..]
4460 6 R x 10 % INT 0..1200 — H Same as above harmonic 22. V_h22[..]
4466 6 R x 10 % INT 0..1200 — H Same as above harmonic 24. V_h24[..]
4472 6 R x 10 % INT 0..1200 — H Same as above harmonic 26. V_h26[..]
4478 6 R x 10 % INT 0..1200 — H Same as above harmonic 28. V_h28[..]
4484 6 R x 10 % INT 0..1200 — H Same as above harmonic 30. V_h30[..]
% value (in respect with the fundamental)
4490 1 R x 10 % INT 0..32767 — H of the amplitude of harmonic 2 of IA. I_h2[0]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
4491 1 R x 10 % INT 0..32767 — H of the amplitude of harmonic 2 of IB. I_h2[1]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
4492 1 R x 10 % INT 0..32767 — H of the amplitude of harmonic 2 of IC. I_h2[2]
—N/A in 400 Hz systems.
% value (in respect with the fundamental)
of the amplitude of harmonic 2 of IN.
4493 1 R x 10 % INT 0..32767 — H I_h2[3]
—N/A in 400 Hz systems.
—N/A with type 31.
Continued on next page

110 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 75 – Spectral Components (Even Rank) (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
4494 4 R x 10 % INT 0..32767 — H Same as above harmonic 4. I_h4[..]
4498 4 R x 10 % INT 0..32767 — H Same as above harmonic 6. I_h6[..]
4502 4 R x 10 % INT 0..32767 — H Same as above harmonic 8. I_h8[..]
4506 4 R x 10 % INT 0..32767 — H Same as above harmonic 10. I_h10[..]
4510 4 R x 10 % INT 0..32767 — H Same as above harmonic 12. I_h12[..]
4514 4 R x 10 % INT 0..32767 — H Same as above harmonic 14. I_h14[..]
4518 4 R x 10 % INT 0..32767 — H Same as above harmonic 16. I_h16[..]
4522 4 R x 10 % INT 0..32767 — H Same as above harmonic 18. I_h18[..]
4526 4 R x 10 % INT 0..32767 — H Same as above harmonic 20. I_h20[..]
4530 4 R x 10 % INT 0..32767 — H Same as above harmonic 22. I_h22[..]
4534 4 R x 10 % INT 0..32767 — H Same as above harmonic 24. I_h24[..]
4538 4 R x 10 % INT 0..32767 — H Same as above harmonic 26. I_h26[..]
4542 4 R x 10 % INT 0..32767 — H Same as above harmonic 28. I_h28[..]
4546 4 R x 10 % INT 0..32767 — H Same as above harmonic 30. I_h30[..]
Phase of harmonic 2 of VAB.
4550 1 R x 10 Deg INT 0..3600 — H V_Phi2[0]
—N/A in 400 Hz systems.
Phase of harmonic 2 of VBC.
4551 1 R x 10 Deg INT 0..3600 — H V_Phi2[1]
—N/A in 400 Hz systems.
Phase of harmonic 2 of VCA.
4552 1 R x 10 Deg INT 0..3600 — H V_Phi2[2]
—N/A in 400 Hz systems.
Phase of harmonic 2 of VAN.
4553 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. V_Phi2[3]
—N/A with type 31.
Phase of harmonic 2 of VBN.
4554 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. V_Phi2[4]
—N/A with type 31.
Phase of harmonic 2 of VCN.
4555 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. V_Phi2[5]
—N/A with type 31.
4556 6 R x 10 Deg INT 0..3600 — H Same as above harmonic 4. V_Phi4[..]
4562 6 R x 10 Deg INT 0..3600 — H Same as above harmonic 6. V_Phi6[..]
4568 6 R x 10 Deg INT 0..3600 — H Same as above harmonic 8. V_Phi8[..]
Phase of harmonic 2 of IA.
4640 1 R x 10 Deg INT 0..3600 — H I_Phi2[0]
—N/A in 400 Hz systems.
Phase of harmonic 2 of IB.
4641 1 R x 10 Deg INT 0..3600 — H I_Phi2[1]
—N/A in 400 Hz systems.
Phase of harmonic 2 of IC.
4642 1 R x 10 Deg INT 0..3600 — H I_Phi2[2]
—N/A in 400 Hz systems.
Phase of harmonic 2 of IN.
4643 1 R x 10 Deg INT 0..3600 — H —N/A in 400 Hz systems. I_Phi2[3]
—N/A with type 31.
4644 4 R x 10 Deg INT 0..3600 — H Same as above harmonic 4. I_Phi4[..]
4648 4 R x 10 Deg INT 0..3600 — H Same as above harmonic 6. I_Phi6[..]
4652 4 R x 10 Deg INT 0..3600 — H Same as above harmonic 8. I_Phi8[..]

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 111

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 76 – Analog Pre-Defined Alarms

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Pre-Defined Alarms Status Bitmap.
Alarms 48 through 63.
5700 1 R — — Bitmap 0.0xFFFF — H Bit 0 represents status of Pre-Defined. PDefAlStatus[0]
Alarm N°48. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarms Status Bitmap.
Alarms 32 through 47.
5701 1 R — — Bitmap 0.0xFFFF — H Bit 0 represents status of Pre-Defined PDefAlStatus[1]
Alarm N°32. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarms Status Bitmap.
Alarms 16 through 31.
5702 1 R — — Bitmap 0.0xFFFF — H Bit 0 represents status of Pre-Defined PDefAlStatus[2]
Alarm N°16. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarms Status Bitmap.
Alarms 0 through 15.
5703 1 R — — Bitmap 0.0xFFFF — H Bit 0 represents status of Pre-Defined PDefAlStatus[3]
Alarm N°1. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarm N° 1 Setting.
6000 12 — — — — Template — — Nv_pDefAlCfg[0]
Over Current Phase A.
MSB: 0=ON, 1=OFF,
LSB: Priority set to 0, 1, 2 or 3.
When set to 0, MM will not log event into MM
6000 1 R/W — — INT See Text — H ___.Status
event log (file N°10) and MM will not log
event into MM Wave Form capture (file N°5).
Default value: 0x0101.
Register number which content gets
Read compared to the pickup setpoint and to the
6001 1 — — INT 1016 — H ___.CompReg
Only dropout setpoint.
Default value: 1016.
Comparison mode.
MSB indicates Pickup mode.
LSB indicates Dropout mode.
MSB can be set to 1, 2 or 4.
Read LSB can be set to 1, 2 or 4.
6002 1 — — INT 1 — H ___.Mode
Only 1 selects Immediate mode: register PuValue
contains the numerical value to which the
monitored register is compared. No
percentage is applied.
Default value is 0x0101.
Alarm Actuation set point.
When Immediate mode is selected, care
See See must be taken to set this register with the
6003 1 R/W INT — — H ___.PuValue
Text Text same units and scale factors then the
Compare Register CompReg.
Default value: 0x8000.
This register contains a numerical value that
is multiplied to the content of the pickup
Read
6004 1 100 % INT — — H register, when Direct Mode is selected. ___.PuPercentage
Only
Otherwise, register is not used.
Default value: 0x8000.
Actuation time delay Time delay must be set
6005 1 R/W x1 s INT — — H in seconds. ___.StatusPuDelay
Default value: 0x8000.
Continued on next page

112 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 76 – Analog Pre-Defined Alarms (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Release set point.
When Immediate mode is selected, care
See See must be taken to set this register with the
6006 1 R/W INT — — H ___.DoValue
Text Text same units and scale factors then the
Compare Register CompReg.
Default value: 0x8000.
This register contains a numerical value that
is multiplied to the content of the dropout
Read
6007 1 100 % INT — — H register, when Direct Mode is selected. ___.DoPercentage
Only
Otherwise, register is not used.
Default value: 0x8000.
Release time delay.
6008 1 R/W x1 s INT — — H Time delay must be set in seconds. ___.DoDelay
Default value: 0x8000.
Alarm Type.
0 indicates “Over”,
1 indicates “Under”,
Read
6009 1 — — INT 0, 1, 2, 3 — H 2 indicates “Equal to”, ___.AlarmType
Only
3 indicates “Different from”,
5 is used for all other alarms.
Default is: 1.
Action associated with overrunning of the set
point after the time delay has run out. Log
6010 1 R/W — — INT Bitmap — H into the Wave Form Capture file (file N° 5). ___.LogAction
0x0200 → action activated. Default value is
0x0000.
6011 1 R/W — — — — — H Reserved. ___.
Pre-Defined Alarm N° 2 Setting.
6012 12 — — — — Template — — nv_pDefAlCfg[1]
Over Current Phase B.
Pre-Defined Alarm N° 3 Setting.
6024 12 — — — — Template — — nv_pDefAlCfg[2]
Over Current Phase C.
Pre-Defined Alarm N° 4 Setting.
6036 12 — — — — Template — — nv_pDefAlCfg[3]
Over Neutral Current.
Pre-Defined Alarm N° 5 Setting.
6048 12 — — — — Template — — nv_pDefAlCfg[4]
Over Ground Current.
Pre-Defined Alarm N° 6 Setting.
6060 12 — — — — Template — — nv_pDefAlCfg[5]
Under Current Phase A.
Pre-Defined Alarm N° 7 Setting.
6072 12 — — — — Template — — nv_pDefAlCfg[6]
Under Current Phase B.
Pre-Defined Alarm N° 8 Setting.
6084 12 — — — — Template — — nv_pDefAlCfg[7]
Under Current Phase C.
Pre-Defined Alarm N° 9 Setting.
6096 12 — — — — Template — — nv_pDefAlCfg[8]
Over Current Unbalance Phase A.
Pre-Defined Alarm N° 10 Setting.
6108 12 — — — — Template — — nv_pDefAlCfg[9]
Over Current Unbalance Phase B.
Pre-Defined Alarm N° 11 Setting.
6120 12 — — — — Template — — nv_pDefAlCfg[10]
Over Current Unbalance Phase C.
Pre-Defined Alarm N° 12 Setting.
6132 12 — — — — Template — — nv_pDefAlCfg[11]
Over Voltage Phase A.
Pre-Defined Alarm N° 13 Setting.
6144 12 — — — — Template — — nv_pDefAlCfg[12]
Over Voltage Phase B.
Pre-Defined Alarm N° 14 Setting.
6156 12 — — — — Template — — nv_pDefAlCfg[13]
Over Voltage Phase C.
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 113

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 76 – Analog Pre-Defined Alarms (continued)

Number of Read /
ENGLISH

Register Scale Unit Format Interval A P / H Description Label

Registers Write
Pre-Defined Alarm N° 15 Setting.
6168 12 — — — — Template — — nv_pDefAlCfg[14]
Under Voltage Phase A.
Pre-Defined Alarm N° 16 Setting.
6180 12 — — — — Template — — nv_pDefAlCfg[15]
Under Voltage Phase B.
Pre-Defined Alarm N° 17 Setting.
6192 12 — — — — Template — — nv_pDefAlCfg[16]
Under Voltage Phase C.
Pre-Defined Alarm N° 18 Setting.
6204 12 — — — — Template — — nv_pDefAlCfg[17]
Over Voltage Unbalance Phase A.
Pre-Defined Alarm N° 19 Setting.
6216 12 — — — — Template — — nv_pDefAlCfg[18]
Over Voltage Unbalance Phase B.
Pre-Defined Alarm N° 20 Setting.
6228 12 — — — — Template — — nv_pDefAlCfg[19]
Over Voltage Unbalance Phase C.
Pre-Defined Alarm N° 21 Setting.
6240 12 — — — — Template — — nv_pDefAlCfg[20]
Over kVA 3-ph Total.
Pre-Defined Alarm N° 22 Setting.
6252 12 — — — — Template — — nv_pDefAlCfg[21]
Over kW Into The Load 3-ph Total.
Pre-Defined Alarm N° 23 Setting.
6264 12 — — — — Template — — nv_pDefAlCfg[22]
Over kW Out Of The Load 3-ph Total.
Pre-Defined Alarm N° 24 Setting.
6276 12 — — — — Template — — nv_pDefAlCfg[23]
Over kVAR Into The Load 3-ph Total.
Pre-Defined Alarm N° 25 Setting.
6288 12 — — — — Template — — nv_pDefAlCfg[24]
Over kVAR Out of The Load 3-ph Total.
Pre-Defined Alarm N° 26 Setting.
6300 12 — — — — Template — — nv_pDefAlCfg[25]
Under kVA 3-ph Total.
Pre-Defined Alarm N° 27 Setting.
6312 12 — — — — Template — — nv_pDefAlCfg[26]
Under kW Into The Load 3-ph Total.
Pre-Defined Alarm N° 28 Setting.
6324 12 — — — — Template — — nv_pDefAlCfg[27]
Under kW Out Of The Load 3-ph Total.
Pre-Defined Alarm N° 29 Setting.
6336 12 — — — — Template — — nv_pDefAlCfg[28]
Under kVAR Into The Load 3-ph Total.
Pre-Defined Alarm N° 30 Setting.
6348 12 — — — — Template — — nv_pDefAlCfg[29]
Under kVAR Into The Load 3-ph Total.
Pre-Defined Alarm N° 31 Setting.
6360 12 — — — — Template — — nv_pDefAlCfg[30]
Lagging True Power Factor 3-ph Total.
Pre-Defined Alarm N° 32 Setting.
6372 12 — — — — Template — — nv_pDefAlCfg[31]
Leading True Power Factor 3-ph Total.
Pre-Defined Alarm N° 33 Setting.
6384 12 — — — — Template — — Lagging Displacement Power Factor nv_pDefAlCfg[32]
3-ph Total.
Pre-Defined Alarm N° 34 Setting.
6396 12 — — — — Template — — Leading Displacement Power Factor nv_pDefAlCfg[33]
3-ph Total.
Pre-Defined Alarm N° 35 Setting.
6408 12 — — — — Template — — nv_pDefAlCfg[34]
Over Value THD Current Phase A.
Pre-Defined Alarm N° 36 Setting.
6420 12 — — — — Template — — nv_pDefAlCfg[35]
Over Value THD Current Phase B.
Pre-Defined Alarm N° 37 Setting.
6432 12 — — — — Template — — nv_pDefAlCfg[36]
Over Value THD Current Phase C.
Pre-Defined Alarm N° 38 Setting.
6444 12 — — — — Template — — nv_pDefAlCfg[37]
Over Value THD Voltage VAB.
Pre-Defined Alarm N° 39 Setting.
6456 12 — — — — Template — — nv_pDefAlCfg[38]
Over Value THD Voltage VBC.
Continued on next page

114 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 76 – Analog Pre-Defined Alarms (continued)

Number of Read /

ENGLISH
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Pre-Defined Alarm N° 40 Setting.
6468 12 — — — — Template — — nv_pDefAlCfg[39]
Over Value THD Voltage VCA.
Pre-Defined Alarm N° 41 Setting.
6480 12 — — — — Template — — nv_pDefAlCfg[40]
Over Value THD Voltage VAN.
Pre-Defined Alarm N° 42 Setting.
6492 12 — — — — Template — — nv_pDefAlCfg[41]
Over Value THD Voltage VBN
Pre-Defined Alarm N° 43 Setting.
6504 12 — — — — Template — — nv_pDefAlCfg[42]
Over Value THD Voltage VCN
Pre-Defined Alarm N° 44 Setting.
6516 12 — — — — Template — — nv_pDefAlCfg[43]
Over Predicted kVA Demand.
Pre-Defined Alarm N° 45 Setting.
6528 12 — — — — Template — — Over Predicted kW Demand into the Load 3- nv_pDefAlCfg[44]
ph Total
Pre-Defined Alarm N° 46 Setting.
6540 12 — — — — Template — — Over Predicted kW Demand out of the Load nv_pDefAlCfg[45]
3-ph Total.
Pre-Defined Alarm N° 47 Setting.
6552 12 — — — — Template — — Over Predicted kVAR Demand into nv_pDefAlCfg[46]
the Load 3-ph Total
Pre-Defined Alarm N° 48 Setting.
6564 12 — — — — Template — — Over Predicted kVAR Demand out of the nv_pDefAlCfg[47]
Load 3-ph Total
Pre-Defined Alarm N° 49 Setting.
6576 12 — — — — Template — — nv_pDefAlCfg[48]
Under Predicted kVA Demand
Pre-Defined Alarm N° 50 Setting.
6588 12 — — — — Template — — Under Predicted kW Demand into the Load nv_pDefAlCfg[49]
3-ph Total
Pre-Defined Alarm N° 51 Setting.
6600 12 — — — — Template — — Under Predicted kW Demand out of the Load nv_pDefAlCfg[50]
3-ph Total
Pre-Defined Alarm N° 52 Setting.
6612 12 — — — — Template — — Under Predicted kVAR Demand into the nv_pDefAlCfg[51]
Load 3-ph Total
Pre-Defined Alarm N° 53 Setting.
6624 12 — — — — Template — — Under Predicted kVAR Demand out of the nv_pDefAlCfg[52]
Load 3-ph Total

Wave Form Capture

Registers 7132 to 7157 file N° 5
(see “Access to Files” on page 35).
Event Log
Registers 7164 to 7188 file N° 10
(see “Access to Files” on page 35).
Min-Max Event Log
Registers 7196 to 7220 file N° 11
(see “Access to Files” on page 35).
Maintenance EventLog
Registers 7228 to 7252 file N° 12
(see “Access to Files” on page 35).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 115

 Four-Wire Modbus® Communications System Appendix A—Registers

Protection Module @ Address xx + 100

Table 77 – Characteristics of the Protection Module
ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
8700 4 R 1 — ASCII — A P / H Serial number encoded in ASCII. EeSerialNumber
8710 1 R 1 — INT — A P / H Protection module firmware version. EeFWVersion
Square D Identification number.
15131 = Micrologic A (PM).
8716 1 R 1 — INT — A P / H 15133 = Micrologic P (PM). EeSQD_Prod_ID
15135 = Micrologic H (PM).
Default value = 0x8000.
Control unit model.
20, 30, 40
8740 1 R 1 — ASCII A P / H 20 = Micrologic 2.0,... EeUnitModelNum
50, 60, 70
70 = Micrologic 7.0.
8741 1 R 1 — ASCII A, P, H A P / H Type of control unit: A, P or H. EeUnitType
Type of long time rating plug.
0 = missing
1= IEC standard
2 = IEC low
3 = IEC High
10 = OFF
7 = UL-A
8742 1 R 1 — INT 0..15 A P/H HwLT_PlugType
8 = UL-B
9 = UL-C
11= UL-D
12 = UL-E
13 = UL-F
14 = UL-G
15 = UL-H
Rated circuit breaker current.

8750 1 R x1 A INT 0..8000 A P / H Default value: 100 A HwBrNominalCurrent

(circuit breaker sensor plug not
present).
Type of neutral protection.

Notc • 0: OFF.
8753 1 R / W1 x 1 INT 0..3 A P/H • 1: N / 2. EeNeutralProtType
h
• 2: N.
• 3: N x 1.6.
1 Write access only with Micrologic P / H.

116 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 78 – Basic Protections Settings (Long-Time Protection-Alarm N° 1000 Ir)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
8754 1 R — — INT 0x0001 A P / H 0x0001 (protection active). LongTime_Status
Type of Idmtl curve.
• Bit 0: standard long-time curve I²t.
(default value).
8755 1 R / W1 — — INT Bitmap 16 A P/H • Bit 1: SIT curve. LongTime_Config
• Bit 2: VIT curve.
• Bit 3: EIT (#I²t on) curve.
• Bit 4: HVF curve.
• Bit 5: constant time (#I²t off).
MOD
8756 2 R / W1 x 1 A 40..8000 A P / H Ir pickup for the long-time protection. LongTime_PuValue
10000
500.. tr tripping delay for the long-time
8758 1 R / W1 x 1 ms INT A P/H LongTime_PuDelay
24000 protection.
Actions linked to overrun of set point at
the end of the delay.
8762 1 R / W1 — — INT Bitmap 16 — H Register set to 0x0100 will Log the LongTime_LogAction
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of “pickup” actions linked to
overrun of set point at the end of the
delay.
Bit set to 1: action activated.
• Bit 0: always set to 1 (trip action).
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
8763 1 R / W1 — — INT Bitmap 16 — P/H an M2C or M6C module is closed. LongTime_ActuAction
• If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0001—(trip action).
1 Write access only with Micrologic P / H.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 117

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 79 – Basic Protections Settings (Short-Time Protection-Alarm N° 1001 Isd)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
8764 1 R — — INT 0x0001 A P / H 0x0001 (protection active). ShortTime_Status
Type of protection.
8765 1 R / W1 — — INT 0, 1 A P / H • 0: type I2t on. ShortTime_Config
• 1: type I2t off.
MOD Isd pickup for the short-time
8766 2 R / W1 x 1 A 60..80000 A P/H ShortTime_PuValue
10000 protection.
tsd tripping delay for the short-time
protection.
8768 1 R / W1 x 1 ms INT 0..400 A P / H 0 s valid only for the I2t off position. ShortTime_PuDelay
100 to 400 ms: valid for the I2t on and
I2t off positions.
Actions linked to overrun of set point at
the end of the delay.
8772 1 R / W1 — — INT Bitmap 16 — H Register set to 0x0100 will Log the ShortTime_LogAction
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of “pickup” actions linked to
overrun of set point at the end of the
delay.
Bit set to 1: action activated.
• Bit 0: always set to 1 (trip action).
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
8773 1 R / W1 — — INT Bitmap 16 — P/H an M2C or M6C module is closed. ShortTime_ActuAction
• If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0001—(trip action).
1 Write access only with Micrologic P / H.

118 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 80 – Basic Protections Settings (Instantaneous Protection-Alarm N° 1002 Ii)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
• 0x0001 (protection active).
0x0001
8774 1 R — — INT A P / H • 0x0101 (protection OFF). Instant_Status
0x0101
Default value = 0x0001.
8775 1 R / W1 — — INT — — P / H Reserved. Instant_Config
MOD 200.. I pickup for the instantaneous
8776 2 R / W1 x 1 A A P/H Instant_PuValue
10000 120000 protection.
8778 1 R / W1 — — — — — — Reserved. Instant_PuDelay
Actions linked to overrun of set point
at the end of the delay.
8782 1 R / W1 — — INT Bitmap 16 — H Register set to 0x0100 will Log the Instant_LogAction
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of “pickup” actions linked to
overrun of set point at the end of the
delay.
Bit set to 1: action activated.
• Bit 0: always set to 1 (trip action).
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
8783 1 R / W1 — — INT Bitmap 16 — P/H an M2C or M6C module is closed. Instant_ActuAction
• If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0001—(trip action).
1 Write access only with Micrologic P / H.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 119

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 81 – Basic Protections Settings (Ground-Fault Protection-Alarm N° 1003 Ig)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
• 0x0001 (protection active).
0x0001
8784 1 R / W1 — — INT A P / H • 0x0101 (protection OFF). Res_Status
0x0101
Default value = 0x0001
Type of protection.
8785 1 R / W1 — — INT 0, 1 A P / H • 0: I2t on. Res_Config
• 1: I2t off.
MOD
8786 2 R / W1 x 1 A 30..1200 A P / H Ig pickup for the ground-fault protection. Res_PuValue
10000
tg tripping delay for the ground-fault
protection.
8788 1 R / W1 x 1 ms INT 0..400 A P/H • 0 s valid only for the I2t off position. Res_PuDelay
• 100 to 400 ms: valid for the I2t on and
I2t off positions actions.
Actions linked to overrun of set point at
the end of the delay.
8792 1 R / W1 — — INT Bitmap 16 — H Register set to 0x0100 will Log the Res_LogAction
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of “pickup” actions linked to overrun
of set point at the end of the delay.
Bit set to 1: action activated.
• Bit 0: always set to 1 (trip action).
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
• If bit 10 is set to 1, contact No. 3 on
an
8793 1 R / W1 — — INT Bitmap 16 — P/H M6C module is closed. Res_ActuAction
• If bit 11 is set to 1, contact No. 4 on
an
M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an
M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an
M6C module is closed.
Default value: 0x0001—(trip action).
1 Write access only with Micrologic P / H.

120 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 82 – Basic Protections Settings (Earth-Leakage Protection Alarm N° 1004 Idelta n)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
8794 1 R — — INT 0x0001 A P / H 0x0001 (protection active). Vigi_Status
8795 1 R/ W1 — — INT — A P / H Reserved. Vigi_Config
MOD IΔN pickup for the earth-leakage
8796 2 R / W1 x 1 mA 5..300 A P/H Vigi_PuValue
10000 protection.
Δt tripping delay for the earth-leakage
8798 1 R / W1 x 1 ms INT 0..1000 A P/H Vigi_PuDelay
protection.
Actions linked to overrun of set point
at the end of the delay.
8802 1 R / W1 — — INT Bitmap 16 — H Register set to 0x0100 will Log the Vigi_LogAction
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of “pickup” actions linked to
overrun of set point at the end of the
delay.
Bit set to 1: action activated.
• Bit 0: always set to 1 (trip action).
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
8803 1 R / W1 — — INT Bitmap 16 — P/H an M2C or M6C module is closed. Vigi_ActuAction
• If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0001—(trip action).
PM configuration change counter.
This counter is incremented each time
a PM setting change is applied
through HMI (keyboard or switches) or EePMCfgChangeCnt
8804 1 R — — UINT 0.0xFFFF — P/H
COM. r
If switches were changed during
power off, this counter is incremented
at power up.
1 Write access only with Micrologic P / H.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 121

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 83 – Protection Module Measurements

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Maximum fault current (trip) recorded
on phase A since last reset.1
8833 1 R x 10 % In INT 0..16000 — P / H Default value: 0x8000 (no fault eeMaxFaultI[0]
recorded or circuit breaker type not
entered).
Maximum fault current (trip) recorded
on phase B since last reset.1
8834 1 R x 10 % In INT 0..16000 — P / H Default value: 0x8000 (no fault eeMaxFaultI[1]
recorded or circuit breaker type not
entered).
Maximum fault current (trip) recorded
on phase C since last reset.1
8835 1 R x 10 % In INT 0..16000 — P / H Default value: 0x8000 (no fault eeMaxFaultI[2]
recorded or circuit breaker type not
entered).
Maximum fault current (trip) recorded
on the neutral phase since last reset.1
8836 1 R x 10 % In INT 0..16000 — P / H Default value: 0x8000 (no fault eeMaxFaultI[3]
recorded or circuit breaker code not
supplied).
rms current on phase A expressed as
8837 1 R x1 % Ir INT 0..32767 A P/H I_RMSRelIr[0]
a % of the Ir long-time set point.
rms current on phase B expressed as
8838 1 R x1 % Ir INT 0..32767 A P/H I_RMSRelIr[1]
a % of the Ir long-time set point.
rms current on phase C expressed as
8839 1 R x1 % Ir INT 0..32767 A P/H I_RMSRelIr[2]
a % of the Ir long-time set point.
rms current on the neutral expressed
as
8840 1 R x1 % Ir INT 0..32767 A P / H a % of the rated current In x the I_RMSRelIr[3]
selected neutral setting (x 1, x 2 or x
0.5).2
"Residual" ground-fault current
8841 1 R x1 % Ig INT 0..32767 A P / H expressed as a % of the Ig ground I_RMSGndRelIr
fault protection set point.3
Earth-leakage current expressed as a
8842 1 R x 0.01 % Idn INT 0..32767 A P / H % of the IΔN earth-leakage protection I_RMSVigiRelIr
set point.4
1 Auxiliary power is required to calculate the fault currents. Calculation is effective only when the circuit breaker selection code has been supplied
(see the Micrologic user manual).
2 Value not accessible when configuration register 9618 returns "no external CT"
3 Accessible only with Micrologic 6.0.
4 Accessible only with Micrologic 7.0.

122 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 84 – Status of the Protection Module

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
8843 1 R x1 % INT 0..100 A P / H Battery-charge indicator. BatteryIndic
Status word for the contacts on the M2C
or M6C module.
• Bit set to 1: contact latched.
• Bit set to 0: contact unlatched.
Reset not possible. Automatic update.
• Bit 0: contact 1 on an M2C or M6C
8857 1 R — — INT Bitmap 16 — P/H RlyStatus
module.
• Bit 1: contact 2 on an M2C or M6C
module.
• Bit 2: contact 3 on an M6C module.
• Bit 3: contact 4 on an M6C module.
• Bit 4: contact 5 on an M6C module.
• Bit 5: contact 6 on an M6C module.
Status word for overrun of current-
protection set points. This condition is
reached as soon as the protection set
point is overrun, even if the time delay
has not expired.
8862 1 R — — INT Bitmap 16 — P/H BasProtPickupStatus
• Bit 0: long-time and LT IDMTL
protection.
If the bit is set to:
• 0: set-point overrun = False.
• 1: set-point overrun = True.
Status word for overrun of protection set
points.
• Bit 0: current unbalance.
• Bit 1: maximum current on phase A.
• Bit 2: maximum current on phase B.
• Bit 3: maximum current on phase C.
• Bit 4: maximum current on the
neutral.
• Bit 5: minimum voltage.
8863 1 R — — INT Bitmap 16 — P/H • Bit 6: maximum voltage. AdvProtPickupStatus
• Bit 7: voltage unbalance.
• Bit 8: maximum power.
• Bit 9: reverse power.
• Bit 10: minimum frequency.
• Bit 11: maximum frequency.
• Bit 12: phase rotation.
• Bit 13: load shedding based on
current.
• Bit 14: load shedding based on
power.
Continuation of status word for overrun
of advanced protection set points.
8864 — — — — INT Bitmap 16 — — AdvXtedProtTripStatus
• Bit 0: ground-fault alarm.
• Bit 1: earth-leakage alarm.
MOD Time remaining before long-time
8865 2 R x 0.1 s — — P/H TimeLeftUntilLT_Trip
10000 tripping.
Phase rotation.
8892 1 R — — — 0..1 — P / H 0: ABC RotatePhase
1: ACB

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 123

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 85 – Time Stamping and Trip / Alarm History

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
9000 4 R — — XDATE — — P / H Current date of the protection module. XtedDateTime
Date of last reset of the maximum
9010 3 R — — DATE — — P / H phase, ground-fault and earth-leakage NvLastMaxI_Reset
currents.
Date of last reset of the trip history
9070 3 R — — DATE — — P/H NvLast10TripReset
(last ten faults).
Date of last reset of the alarm history
9073 3 R — — DATE — — P/H NvLast10AlarmReset
(last ten alarms).

Table 86 – Trip History

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Contact wear indicator per phase.
Default value = 0x8000.
The contacts must be inspected each
time the counter reaches a hundred
9094 4 R 1 % INT 0..32767 — P / H mark. The message "Not available or PhaseContactWear
circuit breaker type not defined" is
displayed if the type of the circuit
breaker has not been defined. (See
"Breaker selection" in the Micrologic
set-up menu and see register 9846.)
Number of faults recorded in the trip
9098 1 R — — INT 0..10 — P/H NvTotalTripQ_Entries
history (FIFO).
Value of the pointer for the last fault
recorded in the trip history.

9099 1 R — — INT 0..9 — P / H The last fault recorded is in NvLastTripQ_Entry

nvLastTripQ_Entry. The next to last
fault is in nvLastTripQ_Entry-1
modulo 10.
TRIP
9100 20 R — — — — P / H Record 0 in the FIFO. TripRecord[0]
RECORD
TRIP
9120 20 R — — — — P / H Record 1 in the FIFO. TripRecord[1]
RECORD
TRIP
9140 20 R — — — — P / H Record 2 in the FIFO. TripRecord[2]
RECORD
TRIP
9160 20 R — — — — P / H Record 3 in the FIFO. TripRecord[3]
RECORD
TRIP
9180 20 R — — — — P / H Record 4 in the FIFO. TripRecord[4]
RECORD
TRIP
9200 20 R — — — — P / H Record 5 in the FIFO. TripRecord[5]
RECORD
TRIP
9220 20 R — — — — P / H Record 6 in the FIFO. TripRecord[6]
RECORD
TRIP
9240 20 R — — — — P / H Record 7 in the FIFO. TripRecord[7]
RECORD
TRIP
9260 20 R — — — — P / H Record 8 in the FIFO. TripRecord[8]
RECORD
TRIP
9280 20 R — — — — P / H Record 9 in the FIFO. TripRecord[9]
RECORD
For further details see “Trip / Alarm History” on page 82.

124 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 87 – Alarm History

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Number of alarms recorded in the
NvTotalAlarmQ_Entrie
9300 1 R — — INT 0..10 — P / H alarm history (FIFO)
s
nvLast10AlarmQ[].
Value of the pointer for the last alarm
recorded in the alarm history.

9301 1 R — — INT 0..9 — P / H The last alarm recorded is in NvLastAlarmQ_Entry

nvLastAlarmQ_Entry.
The next to last alarm is in
nvLastAlarmQ_Entry-1 modulo 10.
ALARM
9302 15 R — — — — P / H Record 0 in the FIFO. AlarmRecord[0]
RECORD
ALARM
9317 15 R — — — — P / H Record 1 in the FIFO. AlarmRecord[1]
RECORD
ALARM
9332 15 R — — — — P / H Record 2 in the FIFO. AlarmRecord [2]
RECORD
ALARM
9347 15 R — — — — P / H Record 3 in the FIFO. AlarmRecord [3]
RECORD
ALARM
9362 15 R — — — — P / H Record 4 in the FIFO. AlarmRecord [4]
RECORD
ALARM
9377 15 R — — — — P / H Record 5 in the FIFO. AlarmRecord [5]
RECORD
ALARM
9392 15 R — — — — P / H Record 6 in the FIFO. AlarmRecord [6]
RECORD
ALARM
9407 15 R — — — — P / H Record 7 in the FIFO. AlarmRecord [7]
RECORD
ALARM
9422 15 R — — — — P / H Record 8 in the FIFO. AlarmRecord [8]
RECORD
ALARM
9437 15 R — — — — P / H Record 9 in the FIFO. AlarmRecord [9]
RECORD
For further details see “Trip / Alarm History” on page 82.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 125

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 88 – Micrologic Configuration

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
Control word for the protection
module. This control word may not be
9600 1 R — — INT 0..32767 — P / H user set. It is randomly modified and ControlWord
must be read before sending certain
commands to the protection module.
Short identifier of the protection
module, coded over four ASCII
9604 2 R/W — — ASCII 0x00..0x7F — P / H characters. eeBrLabel

Default value: “set!”

Long identifier of the protection
module, coded over 16 ASCII
9606 8 R/W — — ASCII 0x00..0x7F — P / H characters. eeBrNamePlate

Default value: “please set me up”.

Language used by the control unit.
May be modified via the control-unit
keypad.
Default value: “English” (but may be
factory set if necessary).
• Bit 0: French.
9614 1 R/W — — INT Bitmap 16 — P/H eeUnitLanguage
• Bit 1: US English.
• Bit 2: UK English.
• Bit 3: German.
• Bit 4: Spanish.
• Bit 5: Italian.
• Bit 6: optional language available
on order from Schneider Electric.
Rated circuit breaker operating
frequency.
Required by the protection module to
disable phase-rotation protection for
9615 1 R/W — — INT Bitmap 16 — — 400 Hz distribution system. eEeNominalFreq
Default value: 50 / 60 Hz,
other possible value: 400 Hz.
• Bit 0: 50 / 60 Hz.
• Bit 3: 400 Hz.
Rated primary voltage on the voltage
9616 1 R/W x1 V INT 100..1150 — P / H transformer. eePT_RatioPri
Default value: 690 V.
Rated secondary voltage on the
9617 1 R/W x1 V INT 100..1150 — P / H voltage transformer. eePT_RatioSec
Default value: 690 V.
• 0: no neutral CT (3-pole circuit
breaker without external CT).
• 1: internal Ct (4-pole circuit
9618 1 R/W — — INT 0,1, 2 — P/H breaker). eeNeutralCTType
• 2: external CTs connected (3-pole
circuit breaker with external CT).
Default value: 0.

126 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Advanced Protection Settings

The concerned protection functions are listed below.

ENGLISH
• Ground-Fault or Earth-Leakage Alarm
• Current Unbalance Iunbal
• Maximum Current IA max, IB max, IC max, and IN max
• Minimum and Maximum Voltage Vmin and Vmax
• Voltage Unbalance Vunbal
• Reverse Power rPmax
• Minimum and Maximum Frequency Fmin and Fmax
• Phase Rotation
• Load Shedding and Reconnection Based on Current and Power

Table 89 – Ground-Fault Alarm—Alarm N°1014 (Ig Protection)

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (alarm active).
0x0001 AlarmTerreRes_
9629 1 R/W — — INT — P / H 0x0101 (OFF).
0x0101 Status
Default value: 0x0101.
Pickup for the ground-fault protection alarm.
MOD AlarmTerreRes_
9631 2 R / W1 x 1 A 20..1200 — P / H Minimum limited to 5% of In.
10000 PuValue
Default value: 1200 A.
Pickup delay for the ground-fault protection alarm. AlarmTerreRes_
9633 1 R / W1 x 0.1 s INT 10..100 — P/H
Default value: 100 (10 s). PuDelay
Dropout for the ground-fault protection alarm.

MOD Maximum limited to AlarmTerreRes_PuValue. AlarmTerreRes_

9634 2 R / W1 x 1 A 20..1200 — P / H
10000 Minimum limited to 5% of In. DoValue

Default value: 1200 A.

Dropout delay for the ground-fault protection alarm. AlarmTerreRes_
9636 1 R / W1 x 0.1 s INT 10..100 — P/H
Default value: 10 (1s). DoDelay
Actions linked to overrun of set point at the end of
Bitmap the delay. AlarmTerreRes_
9637 1 R/W — — INT — H
16 Register set to 0x0100 will Log the Wave Form into LogAction
the Fault Wave Form Capture file (file N°22).
List of pick-up actions linked to overrun of set point
at the end of the delay.
• Bit 0: always set to 0 (trip disabled for this type
of alarm).
• If bit 8 is set to 1, contact No. 1 on an M2C or
M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an M2C or
M6C module is closed.
Bitmap AlarmTerreRes_
9638 1 R / W1 — — INT — P/H • If bit 10 is set to 1, contact No. 3 on an M6C
16 ActuAction
module is closed.
• If bit 11 is set to 1, contact No. 4 on an M6C
module is closed.
• If bit 12 is set to 1, contact No. 5 on an M6C
module is closed.
• If bit 13 is set to 1, contact No. 6 on an M6C
module is closed.
Default value: 0x0000—no action.
1 Accessible only with Micrologic 5.0 P, 6.0 P, 5.0 H, 6.0 H.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 127

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 90 – Earth-Leakage Alarm—Alarm N°1015 (IΔn Protection)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (alarm active).
0x0001
9639 1 R/ W1 — — INT — P / H 0x0101 (OFF). AlarmTerreVigi_Status
0x0101
Default value: 0x0101.
Pickup for the earth-leakage
MOD
9641 2 R / W1 x 0.1 A 5..300 — P / H protection alarm. AlarmTerreVigi_PuValue
10000
Default value: 300 (30 A).
Pickup delay for the earth-leakage
9643 1 R / W1 x 0.1 s INT 10..100 — P / H protection alarm. AlarmTerreVigi_PuDelay
Default value: 100 (10 s).
Dropout for the earth-leakage
protection alarm.
MOD
9644 2 R / W1 x 0.1 A 5..300 — P / H Maximum limited to AlarmTerreVigi_DoValue
10000
AlarmTerreVigi_PuValue.
Default value: 300 (30 A).
Dropout delay for the earth-leakage
9646 1 R / W1 x 0.1 s INT 10..100 — P / H protection alarm. AlarmTerreVigi_DoDelay
Default value: 10 (1 s).
Actions linked to overrun of set point
at the end of the delay.
Bitmap
9647 1 R/W — — INT — H Register set to 0x0100 will Log the AlarmTerreVigi_LogAction
16
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of pick-up actions linked to
overrun of set point at the end of the
delay.
• Bit 0: always set to 0 (trip disabled
for this type of alarm).
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
Bitmap an M2C or M6C module is closed.
9648 1 R / W1 — — INT — P/H AlarmTerreVigi_Actu Action
16 • If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.
1 Accessible only with Micrologic 7.0 P, 7.0 H.

128 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 91 – Current Unbalance—Alarm N°1016 (Iunbal Protection)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9649 1 R/W — — INT & — P / H 0x0101 (OFF). UnbalI_Status
0x0101 Default value: 0x0101.
Pickup for the current unbalance on
MOD
9651 2 R/W x1 % 5..60 — P / H phase A. UnbalI_PuValue
10000
Default value: 60%.
Pickup delay for the current
9653 1 R/W x 0.1 s INT 10..400 — P / H unbalance on phase A. UnbalI_PuDelay
Default value: 400 (40 s).
Dropout for the current unbalance on
MOD
9654 2 R/W x1 % 5..60 — P / H phase A. UnbalI_DoValue
10000
Default value: 60%.
Dropout delay for the current
100..360
9656 1 R/W x 0.1 s INT — P / H unbalance on phase A. UnbalI_DoDelay
0
Default value: 10 (1 s).
Actions linked to overrun of set point
at the end of the delay.
Bitmap
9657 1 R/W — — INT — H Register set to 0x0100 will Log the Unball_LogAction
16
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of pick-up actions linked to
overrun of set point at the end of the
delay.
• If bit 0 is set to1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
Bitmap an M2C or M6C module is closed.
9658 1 R/W — — INT — P/H UnbalI_ActuAction
16 • If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000 —no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 129

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 92 – Maximum Current—Alarm N°1017 (IA max Protection)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9659 1 R/W — — INT & — P / H 0x0101 (OFF). OverIA_Status
0x0101 Default value: 0x0101.
Pickup for the maximum current IA max.
• Maximum limited to
MOD 20..8000 1 x hwNominalCurrent.
9661 2 R/W x1 A — P/H OverIA_PuValue
10000 0 • Minimum limited to
0.2 x hwNominalCurrent.
• Default value: 1 x hwNominalCurrent.
Pickup delay for the maximum
9663 1 R/W x1 s INT 15..1500 — P / H current IA max. OverIA_PuDelay
Default value: 1500 s.
Dropout for the maximum
current IA max.

MOD 20..8000 • Maximum limited to

9664 2 R/W x1 A — P/H OverIa_PuValue. OverIA_DoValue
10000 0
• Minimum limited to
0.2 x hwNominalCurrent.
• Default value: 1 x hwNominalCurrent.
Dropout delay for the
9666 1 R/W x1 s INT 15..3000 — P / H maximum current IA max. OverIA_DoDelay
Default value: 15 s.
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9667 1 R/W — — INT — H Register set to 0x0100 will Log the Wave OverIA_LogAction
16
Form into the Fault Wave Form Capture
file (file N°22).
List of pick-up actions linked to overrun of
set point at the end of the delay.
• If bit 0 is set to1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9668 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on an OverIA_ActuAction
16
M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on an
M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on an
M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on an
M6C module is closed.
Default value: 0x0000—no action.

130 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 93 – Maximum Current—Alarm N°1018 (IB max Protection)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9669 1 R/W — — INT & — P / H 0x0101 (OFF). OverIB_Status
0x0101 Default value: 0x0101.
Pickup for the maximum current IB max.
• Maximum limited to
MOD 20..8000 1 x hwNominalCurrent.
9671 2 R/W x1 A — P/H OverIB_PuValue
10000 0 • Minimum limited to
0.2 x hwNominalCurrent.
• Default value: 1 x hwNominalCurrent.
Pickup delay for the maximum current
9673 1 R/W x1 s INT 15..1500 — P / H IB max. OverIB_PuDelay
Default value: 1500 s.
Dropout for the maximum current IB max.
• Maximum limited to
MOD 20..8000 OverIb_PuValue.
9674 2 R/W x1 A — P/H OverIB_DoValue
10000 0 • Minimum limited to
0.2 x hwNominalCurrent.
• Default value: 1 x hwNominalCurrent.
Dropout delay for the
9676 1 R/W x1 s INT 15..3000 — P / H maximum current IB max. OverI2_DoDelay
Default value: 15 s.
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9677 1 R/W — — INT — H Register set to 0x0100 will Log the Wave OverIB_LogAction
16
Form into the Fault Wave Form Capture
file (file N°22).
List of pick-up actions linked to overrun
of set point at the end of the delay.
• If bit 0 is set to1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9678 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on OverIB_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 131

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 94 – Maximum Current—Alarm N°1019 (IC max Protection)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9679 1 R/W — — INT & — P / H 0x0101 (OFF). OverIC_Status
0x0101 Default value: 0x0101.
Pickup for the maximum current IC max.
• Maximum limited to
MOD 20..8000 1 x hwNominalCurrent.
9682 2 R/W x1 A — P/H OverIC_PuValue
10000 0 • Minimum limited to
0.2 x hwNominalCurrent.
• Default value: 1 x hwNominalCurrent.
Pickup delay for the
9683 1 R/W x1 s INT 15..1500 — P / H maximum current IC max. OverIC_PuDelay
Default value: 1500 s
Dropout for the maximum current IC max.
• Maximum limited to
MOD 20..8000 OverIc_PuValue.
9685 2 R/W x1 A — P/H OverIC_DoValue
10000 0 • Minimum limited to
0.2 x hwNominalCurrent.
• Default value: 1 x hwNominalCurrent.
Dropout delay for the maximum
9686 1 R/W x1 s INT 15..3000 — P / H current IC max. OverIC_DoDelay
Default value: 15 s.
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9687 1 R/W — — INT — H Register set to 0x0100 will Log the Wave OverIC_LogAction
16
Form into the Fault Wave Form Capture
file (file N°22).
List of pick-up actions linked to overrun
of set point at the end of the delay.
• If bit 0 is set to1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9688 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on OverIC_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

132 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 95 – Maximum Current—Alarm N°1020 (IN max Protection)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9689 1 R/W — — INT & — P / H 0x0101 (OFF). OverIn_Status
0x0101 Default value: 0x0101.
Pickup for the maximum current IN max.
• Maximum limited to
MOD 20..8000 1 x hwNominalCurrent.
9692 2 R/W x1 A — P/H • Minimum limited to OverIn_PuValue
10000 0
0.2 x hwNominalCurrent.
• Default value: 1 x
hwNominalCurrent.
Pickup delay for the maximum current
9693 1 R/W x1 s INT 15..1500 — P / H IN max. OverIn_PuDelay
Default value: 1500 s.
Dropout for the maximum current IN max.
• Maximum limited to
MOD 20..8000 OverIn_PuValue.
9695 2 R/W x1 A — P/H • Minimum limited to OverIn_DoValue
10000 0
0.2 x hwNominalCurrent.
• Default value: 1 x
hwNominalCurrent.
Dropout delay for the maximum current
9696 1 R/W x1 s INT 15..3000 — P / H IN max. OverIn_DoDelay
Default value: 15 s.
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9697 1 R/W — — INT — H Register set to 0x0100 will Log the OverIn_LogAction
16
Wave Form into the Fault Wave Form
Capture file (file N°22).
Actions linked to overrun of set point at
the end of the delay.
• If bit 0 is set to 1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9698 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on OverIn_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 133

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 96 – Minimum Voltage—Alarm N°1021 (Vmin Protection)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9699 1 R/W — — INT & — P / H 0x0101 (OFF). UnderV_Status
0x0101 Default value: 0x0101.
Pickup for the minimum voltage Vmin.
MOD 100..120 Maximum limited to
9701 2 R/W x1 V — P/H • UnderV_PuValue
10000 0 OverV.PuValue.
• Default value: 100 V.
Pickup delay for the
9703 1 R/W x 0.01 s INT 20..500 — P / H minimum voltage Vmin. UnderV_PuDelay
Default value: 500 (5 s).
Dropout for the minimum voltage Vmin.
MOD 100..120 Minimum limited to
9704 2 R/W x1 V — P/H • UnderV_DoValue
10000 0 UnderV_PuValue.
• Default value: 100 V.
Dropout delay for the
9706 1 R/W x 0.01 s INT 20..3600 — P / H minimum voltage Vmin. UnderV_DoDelay
Default value: 20 (0.02 s).
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9707 1 R/W — — INT — H Register set to 0x0100 will Log the Wave UnderV_LogAction
16
Form into the Fault Wave Form Capture
file (file N°22).
Actions linked to overrun of set point at
the end of the delay.
• If bit 0 is set to 1,
the circuit breaker trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9708 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on UnderV_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

134 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 97 – Maximum Voltage—Alarm N°1022 (Vmax Protection)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9709 1 R/W — — INT & — P / H 0x0101 (OFF). OverV_Status
0x0101 Default value: 0x0101.
Pickup for the maximum voltage V max.

MOD 100..120 • Minimum limited to the pickup value.

9711 2 R/W x1 V — P/H • Default value: +5% above OverV_PuValue
10000 0
eePT_RatioPri (primary voltage on
the voltage transformer).
Pickup delay for the
9713 1 R/W x 0.01 s INT 20..500 — P / H maximum voltage V max. OverV_PuDelay
Default value: 500 (5 s).
Dropout for the maximum voltage V max.
• Maximum limited to
MOD 100..120 OverV_PuValue.
9714 2 R/W x1 V — P/H OverV_DoValue
10000 0 • Default value: +5 % above de
eePT_RatioPri (primary voltage on
the voltage transformer).
Dropout delay for the
9716 1 R/W x 0.01 s INT 20..3600 — P / H maximum voltage V max. OverV_DoDelay
Default value: 20 (0.02 s).
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9717 1 R/W — — INT — H Register set to 0x0100 will Log the Wave OverV_LogAction
16
Form into the Fault Wave Form Capture
file (file N°22).
Actions linked to overrun of set point at
the end of the delay.
• If bit 0 is set to 1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9718 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on OverV_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 135

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 98 – Voltage Unbalance—Alarm N°1023 (Vunbal Protection)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001
9719 1 R/W — — INT & — P / H 0x0101 (OFF). UnbalV_Status
0x0101 Default value: 0x0101.
MOD Pickup for the voltage unbalance Vunbal.
9721 2 R/W x1 % 2..30 — P/H UnbalV_PuValue
10000 Default value: 30%.
Pickup delay for the voltage unbalance
9723 1 R/W x 0.1 s INT 10..400 — P / H Vunbal. UnbalV_PuDelay
Default value: 400 (4 s).
Dropout for the voltage unbalance
Vunbal.
MOD
9724 2 R/W x1 % 2..30 — P/H • Maximum limited to UnbalV_DoValue
10000
UnbalV_PuValue.
• Default value: 30%.
Dropout delay for the
100..360
9726 1 R/W x 0.1 s INT — P / H voltage unbalance Vunbal. UnbalV_DoDelay
0
Default value: 100 (10 s).
Actions linked to overrun of set point at
the end of the delay.
Bitmap
9727 1 R/W — — INT — H Register set to 0x0100 will Log the UnbalV_LogAction
16
Wave Form into the Fault Wave Form
Capture file (file N°22).
Actions linked to overrun of set point at
the end of the delay.
• If bit 0 is set to 1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9728 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on UnbalV_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

136 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 99 – Reverse Power—Alarm N°1025 (rPmax Protection)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001 &
9739 1 R/W — — INT — P / H 0x0101 (OFF). RevPwr_Status
0x0101
Default value: 0x0101.
Direction of active-power flow.
• Bit 0 set to 0: “standard” - power
connections made to the lower
terminals of the circuit breaker.
• Bit set to 1: “reverse” - power
connections made to the upper
9740 1 R/W — — INT — — P/H terminals of the circuit breaker. RevPwr_Config

The direction may be modified by the

control unit or by directly writing to the
register after obtaining the right (using a
command).
Default value: 0x0000.
Pickup for the maximum
MOD
9741 2 R/W x1 kW 5..500 — P / H reverse power rPmax. RevPwr_PuValue
10000
Default value: 500 kW.
Pickup delay for the maximum
9743 1 R/W x 0.1 s INT 2..200 — P / H reverse power rPmax. RevPwr_PuDelay
Default value: 200 (20 s).
Dropout for the maximum
reverse power rPmax.
MOD
9744 2 R/W x1 kW 5..500 — P/H • Maximum limited to RevPwr_DoValue
10000
RevPwr_PuValue.
• Default value: 500 kW.
Dropout delay for the maximum reverse
9746 1 R/W x 0.1 s INT 10..3600 — P / H power rPmax. RevPwr_DoDelay
Default value: 10 (1 s).
Actions linked to overrun of set point at
the end of the delay.
9747 1 R/W — — INT Bitmap 16 — H Register set to 0x0100 will Log the Wave RevPwr_LogAction
Form into the Fault Wave Form Capture
file (file N°22).
Actions linked to overrun of set point at
the end of the delay.
• If bit 0 is set to 1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
9748 1 R/W — — INT Bitmap 16 — P/H • If bit 10 is set to 1, contact No. 3 on RevPwr_ActuAction
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 137

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 100 – Minimum Frequency—Alarm N°1026 (Fmin Protection)

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001 &
9749 1 R/W — — INT — P / H 0x0101 (OFF). UnderFreq_Status
0x0101
Default value: 0x0101.
Pickup for the minimum frequency Fmin.
MOD Maximum limited to
9751 2 R/W x 0.1 Hz 450..5400 — P/H • UnderFreq_PuValue
10000 OverFreq.PuValue.
• Default value: 450 (45 Hz).
Pickup delay for the
9753 1 R/W x 0.01 s INT 20..500 — P / H minimum frequency Fmin. UnderFreq_PuDelay
Default value: 500 (5 s).
Dropout for the minimum frequency
Fmin.
MOD
9754 2 R/W x 0.1 Hz 450..4400 — P/H • Minimum limited to UnderFreq_DoValue
10000
UnderFreq_PuValue.
• Default value: 450 (45 Hz).
Dropout delay for the
9756 1 R/W x 0.01 s INT 100..3600 — P / H minimum frequency Fmin. UnderFreq_DoDelay
Default value: 100 (1 s).
Actions linked to overrun of set point at
the end of the delay.
9757 1 R/W — — INT Bitmap 16 — H Register set to 0x0100 will Log the UnderFreq_LogAction
Wave Form into the Fault Wave Form
Capture file (file N°22).
Actions linked to overrun of set point at
the end of the delay.
• If bit 0 is set to 1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
an M2C or M6C module is closed.
9758 1 R/W — — INT Bitmap 16 — P/H • If bit 10 is set to 1, contact No. 3 on UnderFreq_ActuAction
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

138 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 101 – Maximum Frequency—Alarm N°1027 (Fmax Protection)

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm or protection active).
0x0001 &
9759 1 R/W — — INT — P / H 0x0101 (OFF). OverFreq_Status
0x0101
Default value: 0x0101.
Pickup for the maximum frequency Fmax.
MOD 450..540 Minimum limited to
9761 2 R/W x 0.1 Hz — P/H • OverFreq_PuValue
10000 0 UnderFreq.PuValue.
• Default value: 650 (65 Hz).
Pickup delay for the maximum
9763 1 R/W x 0.01 s INT 20..500 — P / H frequency Fmax. OverFreq_PuDelay
Default value: 500 (5 s).
Dropout for the maximum frequency Fmax.
MOD Maximum limited to
9764 2 R/W x 0.1 Hz 450..4400 — P/H • OverFreq_DoValue
10000 OverFreq_PuValue.
• Default value: 650 (65 Hz).
Dropout delay for the
9766 1 R/W x 0.01 s INT 100..3600 — P / H maximum frequency Fmax. OverFreq_DoDelay
Default value: 100 (1 s).
Actions linked to overrun of set point at the
end of the delay.
9767 1 R/W — — INT Bitmap 16 — H Register set to 0x0100 will Log the Wave OverFreq_LogAction
Form into the Fault Wave Form Capture file
(file N°22).
Actions linked to overrun of set point at the
end of the delay.
• If bit 0 is set to 1, the circuit breaker
trips.
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
9768 1 R/W — — INT Bitmap 16 — P/H • If bit 10 is set to 1, contact No. 3 on an OverFreq_ActuAction
M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on an
M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on an
M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on an
M6C module is closed.
Default value: 0x0000—no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 139

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 102 – Phase Rotation Alarm—Alarm N° 1028

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm active).
0x0001 &
9769 1 R/W — — INT — P / H 0x0101 (OFF). PhaRot _Status
0x0101
Default value: 0x0101.
• 0: pickup if the detected rotation is
Phase A, Phase B, Phase C.
MOD 1: pickup if the detected rotation is
9771 2 R/W — — 0, 1 — P/H • PhaRot_PuValue
10000 Phase A, Phase C, Phase B.
Default value: 0.
Actions linked to overrun of set point at
the end of the delay.
9777 1 R/W — — INT Bitmap 16 — H Register set to 0x0100 will Log the Wave PhaRot_LogAction
Form into the Fault Wave Form Capture
file (file N°22).
List of pick-up actions linked to overrun
of set point at the end of the delay.
• Bit 0: always set to 0 (trip disabled for
this type of alarm).
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9778 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on PhaRot_ActuAction
16
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

140 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 103 – Load Shedding and Reconnection Based on Current—Alarm N°1029

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm active).
0x0001
9779 1 R/W — — INT & — P / H 0x0101 (OFF). ShedI_Status
0x0101 Default value: 0x0101.
Pickup for load shedding and
MOD reconnection based on current, expressed
9781 2 R/W x1 % 50..100 — P / H as a % of the long-time Ir set point. ShedI_PuValue
10000
Default value: 100%.
Pickup delay for load shedding and
reconnection based on current, expressed
9783 1 R x1 %Tr INT 20..80 — P / H as a % of the long-time delay tr set point ShedI_PuDelay
(20 to 80%).
Default value: 80%.
Dropout for load shedding and
MOD reconnection based on current, expressed
9784 2 R x1 % 30..100 — P / H as a % of the long-time Ir set point. ShedI_DoValue
10000
Default value: 100%.
Dropout delay for load shedding and
9786 1 R x1 S INT 10..600 — P / H reconnection based on current. ShedI_DoDelay
Default value: 10 s.
Actions linked to overrun of set point at the
end of the delay.
Bitmap
9787 1 R/W — — INT — H Register set to 0x0100 will Log the Wave Shedl_LogAction
16
Form into the Fault Wave Form Capture
file (file N°22).
List of pick-up actions linked to overrun of
set point at the end of the delay.
• Bit 0: always set to 0 (trip disabled for
this type of alarm).
• If bit 8 is set to 1, contact No. 1 on an
M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on an
M2C or M6C module is closed.
Bitmap
9788 1 R/W — — INT — P/H • If bit 10 is set to 1, contact No. 3 on an ShedI_ActuAction
16
M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on an
M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on an
M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on an
M6C module is closed.
Default value: 0x0000—no action.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 141

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 104 – Load Shedding and Reconnection Based on Power—Alarm N°1030

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
0x0001 (Alarm active).
0x0001
9789 1 R/W — — INT & — P / H 0x0101 (OFF). ShedPwr_Status
0x0101 Default value: 0x0101.
Direction of active-power flow.
• Bit set to 0: “standard”—power
connections made to the lower
terminals of the circuit breaker.
• Bit set to 1: “reverse”—power
connections made to the upper
9790 1 R/W — — INT — — — terminals of the circuit breaker. ShedPwr_Config

The direction may be modified by the

command interface or by directly
writing to the register after obtaining
the right (using a command).
Default value: 0x0000.
Pickup for load shedding and
MOD 200..
9791 2 R/W x1 kW — P / H reconnection based on power. ShedPwr_PuValue
10000 10000
Default value: 10 MW.
Pickup delay for load shedding and
9793 1 R/W x1 s INT 10..3600 — P / H reconnection based on power. ShedPwr_PuDelay
Default value: 3600 s.
Dropout for load shedding and
MOD 100..
9794 2 R/W x1 kW — P / H reconnection based on power. ShedPwr_DoValue
10000 10000
Default value: 10 MW.
Dropout delay for load shedding and
9796 1 R/W x1 s INT 10..3600 — P / H reconnection based on power. ShedPwr_DoDelay
Default value: 10 s.
Actions linked to overrun of set point
at the end of the delay.
Bitmap
9797 1 R/W — — INT — H Register set to 0x0100 will Log the ShedPwr_LogAction
16
Wave Form into the Fault Wave Form
Capture file (file N°22).
List of pick-up actions linked to
overrun of set point at the end of the
delay.
• Bit 0: always set to 0 (trip disabled
for this type of alarm).
• If bit 8 is set to 1, contact No. 1 on
an M2C or M6C module is closed.
• If bit 9 is set to 1, contact No. 2 on
Bitmap an M2C or M6C module is closed.
9798 1 R/W — — INT — P/H ShedPwr_ActuAction
16 • If bit 10 is set to 1, contact No. 3 on
an M6C module is closed.
• If bit 11 is set to 1, contact No. 4 on
an M6C module is closed.
• If bit 12 is set to 1, contact No. 5 on
an M6C module is closed.
• If bit 13 is set to 1, contact No. 6 on
an M6C module is closed.
Default value: 0x0000—no action.

142 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 105 – Relay Configuration M2C/M6C

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label
Registers Write
• Bit set to 1: indicates that remote
access for configuration was
authorized via the menu using the
keypad on the control unit.
9800 1 R — — INT 0, 1 P/H • Bit set to 0: indicates that remote EeRemoteAccess
access for configuration was not
authorized via the menu using the
keypad on the control unit.
Default value: 0.
• 0: normal (non-latching) mode,
contact activated each time for as
long as the alarm remains active.
• 1: latching mode, contact activated for
each alarm and remains activated
until the alarm is reset by the user (via
the command interface or by a reset
on the control unit).
• 2: time-delay mode, contact activated
for a set time for each alarm. It is
deactivated at the end of the time
9801 1 R/W — — INT 0,1,2,3,4 — P/H delay, whether the alarm is still active EeRelay[0]_Mode
or not. The alarm must change status
at least once to activate the contact
again.
• 3: forced to 1, the contact remains
closed and is not controlled by the
alarm status.
• 4: forced to 0, the contact remains
open and is not controlled by the
alarm status.
Default value: 0x0001 (latching mode).
Contact activation delay for time-delay
9802 1 R/W x 0.1 s INT 10..3600 — P / H mode. EeRelay[0]_Duration
Default value: 3600 (360 s).
Contact name in ASCII (A..Z and 0..9)
using four characters.
0x00..
9803 4 R/W — — ASCII — P/H EeRelay[0]_Label
0x7F Update via the control unit not possible.
Default value: “set up!”.
Owner alarm number for the contact of
the first relay.
1000,
9807 1 R/W — — INT — P / H See alarm number in the trip/alarm EeRelay[0]_Owner
..1031
history, pages 124 and 125.
Default value: 0x8000 (no owner).
Register configuration identical to
9808 7 — — — — — — P/H EeRelay[1]_Owner
registers 9801 to 9807 for contact 2.
Register configuration identical to
9815 7 — — — — — — P/H EeRelay[2]_Owner
registers 9801 to 9807 for contact 3.
Register configuration identical to
9822 7 — — — — — — P/H EeRelay[3]_Owner
registers 9801 to 9807 for contact 4.
Register configuration identical to
9829 7 — — — — — — P/H EeRelay[4]_Owner
registers 9801 to 9807 for contact 5.
Register configuration identical to
9836 7 — — — — — — P/H EeRelay[5]_Owner
registers 9801 to 9807 for contact 6.
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 143

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 105 – Relay Configuration M2C/M6C (continued)

Number of Read /
ENGLISH

Register Scale Unit Format Interval A P / H Description Label

Registers Write
Type of output module.
• 0: none.
• 2: M2C.
9843 1 R — — INT 0,2,6 — P/H • 6: M6C. HwRelayModuleType
Selection is automatic, depending on the
type of module installed.
Data always supplied.
Circuit breaker characteristics.
The data may be supplied:
• by the user via the circuit breaker
selection menu using the keypad on
the Micrologic control unit,
• by downloading the characteristics
using the test kit.
The following registers then contain the
circuit breaker description in a
comprehensible format:
9846 8 R — — — — — P/H • BrCharacteristic[0] = standard: BrCharacteristic
0 = UL,
1 = IEC,
2 = ANSI,
• BrCharacteristic[1] = type:
0 = Masterpact™,
1 = Compact™ NS,
2 = PowerPact™,
• BrCharacteristic[2..7] =
ASCII character strings (e.g.
“NT08N”).
Default value: 0X8000.

Event Log
Registers 9900 to 9924 file N° 20 (see “Access to Files” on page 35).
Maintenance Event Log
Registers 9932 to 9956 file N° 12 (see “Access to Files” on page 35).
Fault Wave Form Capture
Registers 9964 to 9989 file N° 22 (see “Access to Files” on page 35).

144 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Communication Profile @ Address xx

Activation of the Following registers are available only with a Breaker Communication Module

ENGLISH
Communication Profile firmware version greater or equal to V2.0 (register 577 must be greater or equal to
02000) and only if the communication profile has been activated. In order to
activate the communication profile, it is necessary to set the register 800 to 1. Per
default, the communication profile is not activated (register = 0). When the
communication profile is not activated, the content of the registers are not
refreshed and therefore equal to 0x8000.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 145

 Four-Wire Modbus® Communications System Appendix A—Registers

IO Status
Table 106 – Circuit Breaker
ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
Bitmap that indicates the validity of
Bitmap
12000 1 R — — — A P / H each bit in the BrStatus register. BrStatusMask New
16
Default value = 0x7F
Bitmap Circuit breaker status:
12001 1 R — — — A P/H BrStatus 661
16 (see details below)
BrStatus Bitmap Detail:
Bit 0 (0x01): OF; indication contacts
For Compact™ and Masterpact™:
0 = circuit breaker is opened
1 = circuit breaker is closed
Bit 1 (0x02): SD; trip indication contact
For Compact:
0 = no trip
1 = circuit breaker has tripped due to electrical fault, shunt
trip, or push-to-trip
For Masterpact:
always 0
Bit 2 (0x04): SDE; fault trip indication contact
For Compact and Masterpact:
0 = no trip
1 = circuit breaker has tripped due to electrical fault (including
ground-fault test and earth-leakage test)
Bit 3 (0x08): CH; charged (used only with motor mechanism)
For Compact:
always 0
For Masterpact:
0 = spring discharged
1 = Spring loaded
Bit 4 (0x10): reserved (internal use only)
Bit 5 (0x20): PF; ready to close
For Compact:
always 0
For Masterpact:
0 = not ready to close
1 = ready to close
Bit 6 (0x40): Compact / Masterpact differentiation
0 = Compact NS
1 = Masterpact
Bit 7-15: reserved
Note: A bitmap mask should be used to test the circuit breaker
status.
If a value test is used, the following values should be used for
Masterpact:
0x44 tripped discharged not RTC
0x4C tripped charged not RTC
0x50 OFF discharged not RTC
0x51 ON discharged not RTC
0x59 ON charged RTC
0x78 OFF charged RTC

146 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 107 – Input

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12002 1 R — — Bitmap 16 — A P / H Reserved I_Mask —
12003 1 R — — Bitmap 16 — A P / H Reserved I_Status —

Table 108 – Tripping Cause

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
Bitmap indicating cause of
tripping for basic protection
functions:
Bit 0: Long-time protection.
Bit 1: Short-time protection
Bit 2: Instantaneous protection
Bit 3: Ground-fault protection
Bit 4: Earth-leakage protection
Bit 5: Integrated instantaneous
12004 1 R — — INT 0..65535 A P / H protection MitopBasActCause 650
Bit 6: Self-protection
(temperature)1
Bit 7: Self-protection
(overvoltage)1
Bit 8: Other protection detailed
in register 120051
Bits 9 to 14: Reserved
Bit 15: If this bit is set to 1 then
bits 0 to 14 are not valid
Bitmap indicating cause of
tripping for advanced protection
functions with Micrologic P/H:
Bit 0: Current unbalance
Bit 1: Over current phase A
Bit 2 Over current phase B
Bit 3: Over current phase C
Bit 4: Over current on neutral
Bit 5: Under voltage
Bit 6: Over voltage
12005 1 R — — INT 0..65535 — P / H Bit 7: Voltage unbalance MitopAdvActCause 651
Bit 8: Over power
Bit 9: Reverse power
Bit 10: Under frequency
Bit 11: Over frequency
Bit 12: Phase rotation
Bit 13: Load shedding based on
current
Bit 14: Load shedding based on
power
Bit 15: If this bit is set to 1 then
bits 0 to 14 are not valid
Bitmap
12006 1 R — — — A P / H Reserved
16
Bitmap
12007 1 R — — — A P / H Reserved I_Status —
16
1 This value is only available for Micrologic P or H trip units.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 147

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 109 – Alarm Setpoint

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
Status word for overrun of
current protection set points.
This condition is reached as
soon as the protection set point
is overrun, even if the time
Bitmap
12008 1 R — — INT — P / H delay has not expired. BasProtPickupStatus 8862
16
Bit 0: long-time and LT IDMTL
protection.
If the bit is set to:
0: Set-point overrun = false
1: Set-point overrun = true
Status word for overrun of
protection set points This
condition is reached as soon as
the protection set point is
overrun, even if the time delay
has not expired.
Bit 0: Current unbalance
Bit 1: Maximum current on
phase A
Bit 2: Maximum current on
phase B
Bit 3: Maximum current on
phase C
Bit 4: Maximum current on the
Bitmap
12009 1 R — — INT — P / H neutral AdvProtPickupStatus 8863
16
Bit 5: Minimum voltage
Bit 6: Maximum voltage
Bit 7: Voltage unbalance
Bit 8: Maximum power
Bit 9: Reverse power
Bit 10: Minimum frequency
Bit 11: Maximum frequency
Bit 12: Phase rotation
Bit 13: Load shedding based on
current
Bit 14: Load shedding based on
power
Bit 15: If this bit is set to 1, then
bits 0 to 14 are not valid.
Continuation of status word for
overrun of advanced protection
Bitmap set points.
12010 1 R — — INT — — AdvXtedProtTripStatus 8864
16
Bit 0: Ground-fault alarm
Bit 1: Earth-leakage alarm
12011 1 R — — Bitmap 16 — A P / H Reserved — —
12012 1 R — — Bitmap 16 — A P / H Reserved — —
12013 1 R — — Bitmap 16 — A P / H Reserved — —
12014 1 R — — Bitmap 16 — A P / H Reserved — —
12015 1 R — — Bitmap 16 — A P / H Reserved — —

148 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Metering
Table 110 – Currents

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12016 1 R x1 A INT 0..32767 A P / H Maximum rms current on phase A I_RMS[0] 1016
12017 1 R x1 A INT 0..32767 A P / H Maximum rms current on phase B I_RMS[1] 1017
12018 1 R x1 A INT 0..32767 A P / H Maximum rms current on phase C I_RMS[2] 1018
12019 1 R x1 A INT 0..32767 A P / H Maximum rms current on the neutral1 I_RMS[3] 1019
Maximum rms current in registers 816,
12020 1 R x1 A INT 0..32767 A P/H I_Max 1020
817, 818 and 819.
Ground-fault current.
12021 1 R x1 A INT 0..32767 A P / H If this current exceeds 32767 A, the I_RMSGnd 1021
register blocks at 32767.2
Earth-leakage current.
12022 1 R x1 mA INT 0..32767 A P / H If this current exceeds 32767 A, the I_RMSVigi 1022
register blocks at 32767.3
1 Value not accessible when the configuration register 3314 returns type 31 or 40.
2 Accessible only with Micrologic 5.0 P/H and 6.0 A/P/H.
3 Accessible only with Micrologic 7.0 A/P/H.

Table 111 – Maximum Values of Currents

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12023 1 R x1 A INT 0..32767 A P / H Maximum rms current on phase A Max_I_RMS[0] 1616
12024 1 R x1 A INT 0..32767 A P / H Maximum rms current on phase B Max_I_RMS[1] 1617
12025 1 R x1 A INT 0..32767 A P / H Maximum rms current on phase C Max_I_RMS[2] 1618
12026 1 R x1 A INT 0..32767 A P / H Maximum rms current on the neutral1 Max_I_RMS[3] 1619
Maximum rms current in registers
12027 1 R x1 A INT 0..32767 A P/H Max_I_Max 1620
12023, 12024, 12025 and 12026.
Maximum ground-fault current.
12027 1 R x1 A INT 0..32767 A P / H If this current exceeds 32767 A, the Max_I_RMSGnd 1621
register blocks at 32767.2
Maximum earth-leakage current.
12029 1 R x1 mA INT 0..32767 A P / H If this current exceeds 32767 A, the Max_I_RMSVigi 1622
register blocks at 32767.3
1 Value not accessible when the configuration register 3314 returns type 31 or 40.
2 Accessible only with Micrologic 5.0 P/H and 6.0 A/P/H.
3 Accessible only with Micrologic 7.0 A/P/H.

Table 112 – Voltages

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12030 1 R x1 V INT 0..1200 — P / H RMS phase-to-phase voltage VAB V_RMS[0] 1000
12031 1 R x1 V INT 0..1200 — P / H RMS phase-to-phase voltage VBC V_RMS[1] 1001
12032 1 R x1 V INT 0..1200 — P / H RMS phase-to-phase voltage VCA V_RMS[2] 1002
12033 1 R x1 V INT 0..1200 — P / H RMS phase-to-neutral voltage VAN1 V_RMS[3] 1003
12034 1 R x1 V INT 0..1200 — P / H RMS phase-to-neutral voltage VBN1 V_RMS[4] 1004
12035 1 R x1 V INT 0..1200 — P / H RMS phase-to-neutral voltage VCN1 V_RMS[5] 1005
1 Value not accessible when the configuration register 3314 returns type 31 or 40.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 149

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 113 – Frequency

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12036 1 R x 10 Hz INT 0..4000 — P / H System frequency. Frequency 1054
12037 1 R x 10 Hz INT 0..4000 — P / H Maximum value of frequency. Max Frequency 1654

Table 114 – Power

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12038 1 R x1 kW INT 0..32767 — P / H Active power on phase A.1, 2 ActivePwr[0] 1034
12039 1 R x1 kW INT 0..32767 — P / H Active power on phase B.1, 2 ActivePwr[1] 1035
12040 1 R x1 kW INT 0..32767 — P / H Active power on phase C.1, 2 ActivePwr[2] 1036
12041 1 R x1 kW INT 0..32767 — P / H Total active power.2 ActivePwr[3] 1037
kVA
12042 1 R x1 INT 0..32767 — P / H Reactive power on phase A.1, 2 ReactivePwr[0] 1038
R
kVA
12043 1 R x1 INT 0..32767 — P / H Reactive power on phase B.1, 2 ReactivePwr[1] 1039
R
kVA
12044 1 R x1 INT 0..32767 — P / H Reactive power on phase C.1, 2 ReactivePwr[2] 1040
R
kVA
12045 1 R x1 INT 0..32767 — P / H Total reactive power.2 ReactivePwr[3] 1041
R
Apparent power on phase A
12046 1 R x1 kVA INT 0..32767 — P/H ApparentPwr[0] 1042
with 3 wattmeters.1
Apparent power on phase B
12047 1 R x1 kVA INT 0..32767 — P/H ApparentPwr[1] 1043
with 3 wattmeters.1
Apparent power on phase C
12048 1 R x1 kVA INT 0..32767 — P/H ApparentPwr[2] 1044
with 3 wattmeters.1
12049 1 R x1 kVA INT 0..32767 — P / H Total apparent power ApparentPwr[3] 1045
1 Value not accessible when the configuration register 3314 returns type 31 or 40.
2 The sign of the active and reactive power depends on configuration register 3316

150 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 115 – Energy

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
+-
12050 2 R x1 kWh INT — P / H Active energy. EeActiveEnergy 2000
0..32767
+-
12052 2 R x1 kVARh INT — P / H Reactive energy. EeReactiveEnergy 2004
0..32767
Active energy positively
12054 2 R x1 kWh INT 0..32767 — P/H EeActiveEnergyIn 2008
incremented: unsigned value.
Active energy negatively
12056 2 R x1 kWh INT 0..32767 — P/H EeActiveEnergyOut 2012
incremented: unsigned value.
Reactive energy positively EeReactiveEnergy
12058 2 R x1 kVARh INT 0..32767 — P/H 2016
incremented: unsigned value. In
Reactive energy negatively EeReactiveEnergy
12060 2 R x1 kVARh INT 0..32767 — P/H 2020
incremented: unsigned value. Out
12062 2 R x1 kVAh INT 0..32767 — P / H Total apparent energy. EeApparentEnergy 2024
Non-resetable active energy
12064 2 R x1 kWh INT 0..32767 — — — 2028
positively incremented (reserved).
Non-resetable active energy
12066 2 R x1 kWh INT 0..32767 — — — 2032
negatively incremented (reserved).
12068 1 R x1 kWh INT 0..32767 — — Reserved — —
12069 1 R x1 kWh INT 0..32767 — — Reserved — —
12070 1 R x1 kWh INT 0..32767 — — Reserved — —
12071 1 R x1 kWh INT 0..32767 — — Reserved — —
12072 1 R x1 kWh INT 0..32767 — — Reserved — —
12073 1 R x1 kWh INT 0..32767 — — Reserved — —
12074 1 R x1 kWh INT 0..32767 — — Reserved — —
12075 1 R x1 kWh INT 0..32767 — — Reserved — —
12076 1 R x1 kWh INT 0..32767 — — Reserved — —
12077 1 R x1 kWh INT 0..32767 — — Reserved — —
12078 1 R x1 kWh INT 0..32767 — — Reserved — —
12079 1 R x1 kWh INT 0..32767 — — Reserved — —

Table 116 – Current Demand

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12080 1 R x1 A INT 0..32767 — P / H Current demand on phase A. I_Dmd[0] 2200
12081 1 R x1 A INT 0..32767 — P / H Current demand on phase B. I_Dmd[1] 2201
12082 1 R x1 A INT 0..32767 — P / H Current demand on phase C. I_Dmd[2] 2202
12083 1 R x1 A INT 0..32767 — P / H Current demand on the neutral.1 I_Dmd[3] 2203
1 Value is not accessible when the configuration register 3314 selects type 31 or 40.

Table 117 – Power Demand

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12084 1 R x1 kW INT 0..32767 — P / H Total active-power demand.1 ActivePwrDmd 2224
12085 1 R x1 kVAR INT 0..32767 — P / H Total reactive-power demand.1 ReactivePwrDmd 2230
12086 1 R x1 kVA INT 0..32767 — P / H Total apparent power demand.1 ApparentPwrDmd 2236
12087 — — — — — — — — Available — —
12088 — — — — — — — — Available — —
12089 — — — — — — — — Available — —
1 Value updated at end of window for the "block" mode. For the "sliding" mode, the value is updated every 15 seconds.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 151

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 118 – Maximum Values of Voltages

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
Max rms phase-to-phase
12090 1 R x1 V INT 0..1200 — P/H Max_V_RMS[0] 1600
voltage VAB.
Max rms phase-to-phase
12091 1 R x1 V INT 0..1200 — P/H Max_V_RMS[1] 1601
voltage VBC.
Max rms phase-to-phase
12092 1 R x1 V INT 0..1200 — P/H Max_V_RMS[2] 1602
voltage VCA.
Max rms phase-to-neutral
12093 1 R x1 V INT 0..1200 — P/H Max_V_RMS[3] 1603
voltage VAN. 1
Max rms phase-to-neutral
12094 1 R x1 V INT 0..1200 — P/H Max_V_RMS[4] 1604
voltage VBN. 1
Max rms phase-to-neutral
12095 1 R x1 V INT 0..1200 — P/H Max_V_RMS[5] 1605
voltage VCN. 1
1 Value not accessible when the configuration register 3314 returns type 31 or 40

Table 119 – Power Factor

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
-1000.. Power factor on phase A (absolute
12096 1 R x 1000 None INT — P/H PF[0] 1046
+1000 value equal to |P|/S). 1, 2
-1000.. Power factor on phase B (absolute
12097 1 R x 1000 None INT — P/H PF[1] 1047
+1000 value equal to |P|/S). 1, 2
-1000.. Power factor on phase C (absolute
12098 1 R x 1000 None INT — P/H PF[2] 1048
+1000 value equal to |P|/S). 1, 2
-1000.. Total power factor (absolute value
12099 1 R x 1000 None INT — P/H PF[3] 1049
+1000 equal to |Ptotal|/Stotal).
Fundamental power factor on
phase A (its absolute value is
-1000.. equal to |FundP|/FundS). Sign
12100 1 R x 1000 None INT — H FundPF[0] 1050
+1000 convention the same as the one for
the real power factor. N/A if type
31 network.
-1000..
12101 1 R x 1000 None INT — H Same as above phase B. FundPF[1] 1051
+1000
-1000..
12102 1 R x 1000 None INT — H Same as above phase C. FundPF[2] 1052
+1000
Total fundamental power factor (its
absolute value is equal to
-1000..
12103 1 R x 1000 None INT — H |FundPtot|/FundStot). Sign FundPF[3] 1053
+1000
convention the same as the one for
the real power factor.
1 Value not accessible when the configuration register 3314 returns type 31 or 40.
2 The sign of the active and reactive power depends on configuration register 3316.

152 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 120 – Total Harmonic Distortion

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
Total harmonic distortion of VAB
12104 1 R x 10 % INT 0..5000 — H voltage compared to the THD_V[0] 1092
fundamental.
12105 1 R x 10 % INT 0..5000 — H Same as above VBC THD_V[1] 1093
12106 1 R x 10 % INT 0..5000 — H Same as above VCA. THD_V[2] 1094
Total harmonic distortion of VAN
voltage compared to the
12107 1 R x 10 % INT 0..5000 — H fundamental. THD_V[3] 1095
– N/A with type 31 or 40
network.
12108 1 R x 10 % INT 0..5000 — H Same as above VBN THD_V[4] 1096
12109 1 R x 10 % INT 0..5000 — H Same as above VCN. THD_V[5] 1097
Total harmonic distortion of
12110 1 R x 10 % INT 0..5000 — H phase A current compared to THD_I[0] 1098
the fundamental.
12111 1 R x 10 % INT 0..5000 — H Same as above phase B. THD_I[1] 1098
12112 1 R x 10 % INT 0..5000 — H Same as above phase C. THD_I[2] 1099
same as above neutral – N/A
with type 31 networks.
12113 1 R x 10 % INT 0..5000 — H THD_I[3] 1100
Measured with type 41,
calculated with type 40.

Table 121 – Available and Reserved Registers

12114 to 12145 are available.
12146 to 12160 are reserved.
12170 to 12145 are available.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 153

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 122 – Basic Protection Settings

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
MOD Ir pickup for the long-time
12180 2 R x1 A 40..8000 A P/H LongTime_PuValue 8756
10000 protection.
500. tr tripping delay for the long-
12182 1 R x1 ms INT A P/H LongTime_PuDelay 8758
24000 time protection.
MOD 60.. Isd pickup for the short-time
12183 2 R x1 A A P/H ShortTime_PuValue 8766
10000 80000 protection.
tsd tripping delay for the short-
time protection.
12185 1 R x1 ms INT 0.400 A P / H 0 s valid only for the I²t off ShortTime_PuDelay 8768
position 100 to 400 ms: valid for
the I²t on and I²t off positions.
0x0001 (protection active)
0x0001
12186 1 R x1 — INT A P / H 0x0101 (protection OFF) Instant_Status 8774
0x0101
Default value = 0x0001
MOD 200.. I pickup for the instantaneous
12187 2 R x1 A A P/H Instant_PuValue 8776
10000 120 000 protection.
MOD Ig pickup for the ground-fault
12189 2 R x1 A 30..1200 A P/H Res_PuValue 8786
10000 protection
tg tripping delay for the ground-
fault protection.
12191 1 R x1 ms INT 0..400 A P / H 0 s valid only for the I²t off Res_PuDelay 8788
position 100 to 400 ms: valid for
the I²t on and I²t off positions.
MOD IΔN pickup for the earth-leakage
12192 2 R x1 mA 5..300 A P/H Vigi_PuValue 8796
10000 protection.
Δt tripping delay for the earth
12194 1 R x1 ms INT 0..1000 A P/H Vigi_PuDelay 8798
leakage protection.
12195 — — — — — — — — Available — —

154 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Table 123 – Circuit Breaker ID

ENGLISH
Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
12196 4 R 1 — Ascii — A P / H Serial number encoded in Ascii. EeSerialNumber 8700
Protection module firmware
12200 1 R 1 — INT — A P/H EeFWVersion 8710
version.
Square D Identification number
15131 = Micrologic A (PM)
12201 1 R 1 — INT — A P / H 15133 = Micrologic P (PM) EeSQD_Prod_ID 8716
15135 = Micrologic H (PM)
Default value = 0x8000
Type of protection
20,30,40
12202 1 R 1 — Ascii A P / H 20 = Micrologic 2.0,… EeUnitModelNum 8740
50,60,70
70 = Micrologic 7.0
12203 1 R 1 — Ascii A, P, H A P / H Type of control unit: A, P or H EeUnitType 8741
Type of long time rating plug.
0 = missing,
1= IEC standard,
2 = IEC low,
3 = IEC High,
10 = OFF,
7 = UL-A,
12204 1 R 1 — INT 0..15 A P/H HwLT_PlugType 8742
8 = UL-B,
9 = UL-C,
11= UL-D,
12 = UL-E,
13 = UL-F,
14 = ULG,
15 = UL-H
Rated circuit breaker current.
12205 1 R x1 A INT 0..8000 A P / H Default value: 100 A (circuit HwBrNominalCurrent 8750
breaker sensor plug not present).
Type of neutral protection.
0: OFF
12206 1 R/W x1 notch INT 0..3 A P / H 1: N / 2 (Ir / 2) EeNeutralProtType 8753
2: N (Ir)
3: N x 1.6 (1.6 x Ir)
Counter for total number of
operations (OF): the counter
12207 1 R — — INT 0..65535 A P/H CtrOF_OvrLife 662
increments when bit 0 in
register 661 switches from 0 to 1.
Counter for operations (OF) since
last reset: the counter increments
12208 1 R — — INT 0..65535 A P/H CtrOF 663
when bit 0 in register 661
switches from 0 to 1.
Counter for operations (SD): the
12209 1 R — — INT 0..65535 A P / H counter increments when bit 1 in CtrSD 664
register 661 switches from 0 to 1.
Counter for operations (SDE): the
12210 1 R — — INT 0..65535 A P / H counter increments when bit 2 in CtrSDE 665
register 661 switches from 0 to 1.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 155

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 124 – Miscellaneous

ENGLISH

Number of Read /
Register Scale Unit Format Interval A P / H Description Label Origin
Registers Write
Number of first (oldest) record in the
CurrentFirstRecord
12211 1 R — — INT 1..8000 — P / H protection module event log (file 623
OfPM_EvtLog
N°20).
Number of last (most recent) record
CurrentLarstRecord
12212 1 R — — INT 1..8000 — P / H in the protection module event log 624
OfPM_EvtLog
(file N°20).
MOD Time remaining before long-time
12213 2 R x 0.1 s — — P/H TimeLeftUntilLT_Trip 886
10000 tripping.
Contact wear indicator per phase
(Default value = 0x8000).
The contacts must be inspected each
time the counter reaches a hundred
mark. The message “Not available or
12215 4 R 1 % INT 0..32767 — P / H circuit breaker type not defined” is PhaseContactWear 909
displayed if the type of the circuit
breaker has not been defined. In this
case, see “Breaker Selection” in the
Micrologic set-up menu. See register
9846.

List of Commands
Cradle Communication Module Commands @ Address xx + 50
Table 125 – Cradle Communication Module Commands

Cmd # Description Parameter(s) Mode Label

P1 = control word read in register 553.
P2 = bitmap of counter to Preset.1
Preset Circuit Breaker Status
57856 P3 = Counter value 1.2 Protected PresetBrStatCtr
Counters
P4 = Counter value 2.2
P5 = Counter value 3.2
Set time and date for Cradle
Communication Module. P1 = MM:DD
Year YY is 0 for 1900,
61541 P2 = YY:HH Shared Protected SetD_T
100 for 2000,
101 for 2001, P3 = MIN:SEC
etc.
1 Bitmap of counter to Preset
Bit Circuit Breaker Counter Status Affected Counter Registers
8 (0x0100) CD: Disconnected position 663 @ xx + 50
9 (0x0100) CE: Connected position 662 @ xx + 50
10 (0x0100) CT: Test position 664 @ xx + 50
2 Control Value 1 = Value of counter corresponding to 1st bit set when bitmap is read from LSB to MSB (0000 to reset counter).
Control Value 2 = Value of counter corresponding to next bit set when bitmap is read from LSB to MSB (0000 to reset counter).

156 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Breaker Communication Module Commands @ Address xx

Table 126 – Breaker Communication Module Commands

ENGLISH
Cmd # Description Parameter(s) Mode Label
P1 = 3 1
P2 = 4 2
57394 Enter configuration mode. Protected. In_CommCfg
P3 = control word read in register 553 of the
Breaker Communication Module.
P1 = 3 1
Exit configuration mode and activate P2 = 4 2
57395 Protected. Out_CommCfg
the new parameters. P3 = control word read in register 553 of the
Breaker Communication Module.
P1 = 4 1
P2 = 4 2
57400 Simplified Open/Close. Shared Open/Close
P3 = 0 or 1 (0 for Open, 1 for Close)
P4 = password (default value = 0000)
P1 = 5 to 101
P2 = 42
P3 = control word read in register 553
P4 = bitmap of counter to Preset3
57856 Preset circuit breaker status counters. Protected PresetBrStatCtr
P5 = Counter value 14
P6 = Counter value 24
P7 = Counter value 34
P10 = Counter value 64
P1 = 61
P2 = 42
P3 = control word read in register 553
57857 Preset coils operation counters. Protected PresetCoilCtr
P4 = bitmap for coil control5
P5 = MX Counter value (0000 to reset)
P6 = XF Counter value (0000 to reset)
P1 = 41
P2 = 42
58769 Open circuit breaker using MX coil. Shared Protected OpenBr
P3 = control word read in register 553
P4 = 1
P1 = 41
P2 = 42
58770 Close circuit breaker using XF coil. Shared Protected CloseBr
P3 = control word read in register 553
P4 = 2
P1 = 41
Authorize activation of MX or XF coils, P2 = 42
58771 Protected EnCoilsactivation
or both. P3 = control word read in register 553
P4 = bitmap for coil-control5
P1 = 41
Disable activation of MX or XF coils, P2 = 42
58772 Protected EnCoilsdesactivation
or both. P3 = control word read in register 553
P4 = bitmap for coil-control5
P1 = 31
Release flag for access to protected
59492 P2 = 42 Protected ReleaseProt Flag
mode.
P3 = flag active
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 157

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 126 – Breaker Communication Module Commands (continued)

Cmd # Description Parameter(s) Mode Label

ENGLISH

Set time and date for

Breaker Communication Module and
the protection and measurement P1 = 51
modules P2 = 42
61541 Year YY is P3 = MM:DD Shared Protected SetD_T
0 for 1900, P4 = YY:HH
100 for 2000, P5 = MIN:SEC
101 for 2001,
etc.
1 Parameter P1 for the Breaker Communication Module command interface contains the total number of command parameters, including P1.
2 The value “4” for parameter P2 informs the Breaker Communication Module command interface that it must run the command itself.
3 Bitmap of counter to Preset:
Bit Circuit Breaker Counter Status Affected Counter Registers
0 (0x0001) OF: ON/OFF 663
1 (0x0002) SD: Trip indication 664
2 (0x0004) SDE: Fault-trip indication 665

4Control Value 1 = Value of counter corresponding to first bit set when bitmap is read from LSB to MSB (0000 to reset counter).
Control Value 2 = Value of counter corresponding to next bit set when bitmap is read from LSB to MSB (0000 to reset counter).
5 Bitmap for coil control:
Bit Coil Control Status Affected Counter Registers
1 (0x0002) MX coil-control bit 674
2 (0x0004) XF coil-control bit 678
3 (0x0008) To be set to 1 in order to activate MX or XF

158 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Metering Module Commands @ Address xx + 200

Table 127 – Metering Module Commands

ENGLISH
Cmd # Description Parameter(s) Mode Label
P1 = 31
P2 = 82
53298 Enter configuration mode. Protected In_mCfg
P3 = control word read in register 3300 of the metering
module.
P1 = 31
Exit configuration mode and activate P2 = 82
53299 Protected Out_mCfg
the new parameters. P3 = control word read in register 3300 of the metering
module.
P1 = 41

Reset minimeters / maximeters in the P2 = 82

61952 Protected Reset_m_M
metering module. P3 = bitmap of minimeters to reset3
P4 = bitmap of maximeters to reset3
P1 = 31
53762 Reset of current demand maximums. P2 = 82 Protected ResetI_PeakDmd
P3 = bitmap of maximum values to reset4
P1 = 31
53763 Reset of power demand maximums. P2 = 82 Protected ResetP_PeakDmd
P3 = bitmap of maximum values to reset5
P1 = 3 to 321
P2 = 82
P3 = bitmap of counters to preset or reset6
53760 Preset or reset the energy counters. Protected PresetAccEnCtr
P4 to P7 = first counter to preset according to P3
P8 to P11 = second counter to preset according to P3
P28 to P32 = seventh counter to preset according P3
Continued on next page

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 159

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 127 – Metering Module Commands (continued)

Cmd # Description Parameter(s) Mode Label

ENGLISH

P1 = 41
P2 = 82 Shared
55234 Forcelog into WFC (file N° 5). Forcelog
P3 = bitmap of file N° 5 = 0x0000 Protected

P4 = bitmap of file N° 5 = 0x0010

1 Parameter P1 for the Breaker Communication Module command interface contains the total number of command parameters, including P1.
2 The value “8” for parameter P2 informs the Breaker Communication Module command interface that the metering module must run the
command.
3 Bitmap for reset of minimeters / maximeters:
Affected Real-Time Measurement
Bit Minimeters / Maximeters
Registers
0 (0x0001) Currents 1016 to 1027
1 (0x0002) Current unbalance 1028 to 1032
3 (0x0008) Voltages 1000 to 1007
4 (0x0010) Voltage unbalance 1008 to 1015
6 (0x0040) Frequency 1054
7 (0x0080) Power, PF 1034 to 1053
11 (0x800) Fundamental, THD 1056 to 1118
13 (0x2000) V_Crest 1119 to 1124
14 (0x4000) I_Crest 1125 to 1128

4 Bitmap for reset of current demand maximums:

Bit Maximum of Current Demand Affected Data Registers
1 (0x0002) Phase A 2204 + 3005 to 3007 + 3026 to 3028
2 (0x0004) Phase B 2205 + 3008 to 3010 + 3026 to 3028
3 (0x0008) Phase C 2206 + 3011 to 3013 + 3026 to 3028
4 (0x0010) Neutral 2207 + 3014 to 3016 + 3026 to 3028

5 Bitmap for reset of power demand maximums:

Bit Maximums of Power Demand Affected Data Registers
4 (0x0010) Active power 2225 to 2229 + 3017 to 3019 + 3029 to 3031
8 (0x0100) Reactive power 2230 to 2235 + 3020 to 3022 + 3029 to 3031
12 (0x1000) Apparent power 2236 to 2241 + 3023 to 3025 + 3029 to 3031

6 A number of counters may be preset or reset at the same time. Each counter is coded over four 16-bit registers.
The counters to be preset are indicated in the bitmap. The values to be preset are transmitted as parameters, in the same order as the bits set to
one, starting with the least significant. The number of counters to be transmitted is equal to the number of bits set to one in the bitmap.
Bit Energy Counter Affected Data Registers
0 (0X0001) All the counters are simply reset —
1 (0X0002) Total Active-Energy 2000 to 2003
2 (0X0004) Total Reactive-Energy 2004 to 2007
3 (0X0008) Total Active-Energy IN (positively incremented) 2008 to 2011
4 (0X0010) Total Active-Energy OUT (negatively incremented) 2012 to 2015
5 (0X0020) Total Reactive-Energy IN (positively incremented) 2016 to 2019
6 (0X0040) Total Reactive-Energy OUT (negative incremented) 2020 to 2023
7 (0X0080) Total Apparent-Energy 2024 to 2027

160 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Protection Module Commands @ Address xx + 100

Table 128 – Protection Module Commands

ENGLISH
Cmd # Description Parameter(s) Mode Label
P1 = 31
P2 = 22
49202 Enter configuration mode. P3 = Password to be consulted in the menu of the Protected In_pCfg
control unit: Com set-up / Remote access (default
is 0000).
P1 = 31
P2 = 22
Exit configuration mode and activate
49203 P3 = Password to be consulted in the menu of the Protected Out_pCfg
the new parameters.
control unit: Com set-up / Remote access (default
is 0000).
P1 = 41
“Unlatching” of a relay on optional P2 = 22
M2C or M6C module, set to latching
50579 mode. Unlatching is effective if the P3 = Password to be consulted in the menu of the Protected DeactivateRly
alarm that tripped contact closing is control unit: Com set-up / Remote access (default
no longer active. is 0000).
P4 = bitmap of relay to reset3
P1 = 41 maximums
P2 = 22
“Activate” a relay of an optional M2C P3 = Password to be consulted in the menu of the Protected
50580 RearmBr
or M6C module. control unit: Com set-up / Remote access (default
is 0000).
P4 = bitmap of relay to activated3
P1 = 41
Clear the files.
P2 = 22 Shared
63176 NOTE: Note: In order to clear a file, it ClearFiles
P3 = bitmap of file reference4 Protected
is mandatory to disable the file before.
P4 = bitmap of file reference4
P1 = 41
P2 = 22 Shared
63177 Disable access to files. ClearFiles
P3 = bitmap of file reference4 Protected

P4 = bitmap of file reference4

Read a record in the Breaker P1 = 41
Communication Module even log (file
P2 = 22
63178 No. 20). Protected ReadFileX_RecY
P3 = 20 (number of the file to be read)
The contents of the record is available
starting in register 7730. P4 = number of event to be read

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 161

 Four-Wire Modbus® Communications System Appendix A—Registers

Table 128 – Protection Module Commands (continued)

Cmd # Description Parameter(s) Mode Label

ENGLISH

P1 = 41
P2 = 22 Shared
63376 Enable access to files. EnFiles
P3 = bitmap of file reference4 Protected

P4 = bitmap of file reference4

1 Parameter P1 for the Breaker Communication Module command interface contains the total number of command parameters, including P1.
2The value “2” for parameter P2 informs the Breaker Communication Module command interface that the protection module must run the
command.
3 Bit 0 corresponds to relay S1 (M2C or M6C option), bit 1 corresponds to relay S2 (M2C or M6C option), bits 2 to 5 correspond respectively to
relay S3 to S6 on the M6C module.
4 File reference:
Event log protection module. (File N°20) P3=0x0008 P4=0x0000
Event log metering module. (File N°10) P3=0x0000 P4=0x0200
Maintenance event log protection module. (File N°21) P3=0x0010 P4=0x0000
Maintenance event log metering module. (File N°12) P3=0x0000 P4=0x0800
Min-Max event log metering module. (File N°11) P3=0x0000 P4=0x0400
Event log of the breaker communication module. (File N°30) P3=0x2000 P4=0x0000
Wave form capture. (File N°5) P3=0x0000 P4=0x0010
Fault wave form capture. (File N°22) P3=0x0020 P4=0x0000

162 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Examples of Commands

ENGLISH
Send Commands in Shared Mode Simplified Open / Close
1. Fill in Parameters.
Command 57400
Simplified Open / Close Modbus Slave Address @ [breaker communication module]
Register Data To Be Written
7700 57400 (command number)
7701 P1 = 4 (total number of parameters including P1)
7702 P2 = 4 (breaker communication module)
7703 P3 = 0 for Open or P3 = 1 for Close
7704 P4 = 0000 (Password default value)

2. Write Command.
Write the previous registers by using function 16 of Modbus protocol.
After receiving the command, the status command register (802 for Open; 803 for
Close) is set to 1 if the simplified Open/Close command has been accepted by the
Breaker Communication Module.
Following table gives the values set in the Status command register.

Value Label Use Case

1 RES_OK Command accepted
2 ERR_NBR_PARAM Incorrect number of parameters
3 ERR_COIL_ID_VALUE Incorrect coil value (must be 0 or 1)
4 ERR_COIL_PASSWORD_VALUE Incorrect password value
5 ERR_MANU Register 670 in MANU mode

WARNING:
Simplified OPEN/CLOSE command are available only with a Breaker
Communication Module firmware version greater or equal to V2.0 (register 577
must be greater or equal to 02000). It is necessary to be in AUTO mode (see
register 670).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 163

 Four-Wire Modbus® Communications System Appendix A—Registers

Send Commands in Protected Mode

1. Request the flag.
ENGLISH

Read the following registers by using function 3 of Modbus protocol.

Modbus Slave Address @ [breaker communication module]

Register Data To Be Read
77151 Flag. The value read must be 0 to go on to the next step.
5532 Control word for commands.
1 The value read in 7715 is called a “flag”. If it is zero, another supervisor on a multi-supervisor system
is already in configuration mode. You must wait for the flag to be different than zero before starting to
configure.
2 The control word for commands is regularly modified. It must be read once before sending commands.

2. Fill in parameters.

Modbus Slave Address @ [breaker communication module]

Register Data To Be Written
Command number to be written
7720
(see “List of Commands” on page 156).
7721 P1 = Number of parameters to be sent (including P1).
P2 = Identification of the Micrologic module.
Protection Module = 2,
7722
Breaker Communication Module = 4,
Metering Module = 8.
7723 to 7729 P3 to P9 = Specific to the command.

3. Write command.
Write the previous registers by using function 16 of Modbus protocol.
4. Wait for the command being executed.
Read the following registers by using function 3 of Modbus protocol.

Modbus Slave Address @ [breaker communication module]

Register Data To Be Read
Command is active: as long as the command is being executed, the data
7717 is the command number. When command execution is finished, the data
is 0.
Command is executed: as long as the command is being executed, the
7718 data is 0. When command execution is finished, the data is the command
number.

Repeat readings until command execution is finished.

5. Check result code.
Read the following registers by using function 3 of Modbus protocol.

Modbus Slave Address @ [breaker communication module]

Register Data To Be Read
Result code for the executed command, indicated in 7719. See the
7719 command result-code table for information on the meaning of the code.
(see “Protected Mode Registers in the Command Interface” on page 30).

164 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

6. Release the flag.

ENGLISH
Write the following registers by using function 16 of Modbus protocol.

Command 59492 Modbus Slave Address @ [breaker communication module]

ReleaseProtFlag Register Data To Be Written
7720 59492 (command number)
7721 P1 = 3
7722 P2 = 4 (Breaker Communication Module)
7723 P3 = flag (value read in register 7715 at step 1)

Remotely OPEN the Circuit Breaker Commands

Open the Circuit Breaker
Some preliminary operations are required to send the command.
On the menu of Micrologic P or H control unit, within <<Com set up>> menu,
Remote control must be set to Auto
(Register 670 must be equal to 1).
Then circuit breaker may be remotely controlled.
NOTE: To open the circuit breaker using the COM option, the device must be
equipped with an MX <<communicating>> voltage release.
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag. Get the control word from register 553.
2. Enable activation of the MX coil.
Write the following registers by using function 16 of Modbus protocol.

Command 58771 Modbus Slave Address @ [breaker communication module]

EnCoilactivation Register Data To Be Written
7720 58771 (command number)
7721 P1 = 4
7722 P2 = 4 (Breaker Communication Module)
7723 P3 = Control word for commands read in step 1 (register 553)
7724 P4 = 10 (0x000A) See bitmap for MX coil control.

3. Wait for the command being executed.

4. Check result code.
5. Open the circuit breaker.
Write the following registers by using function 16 of Modbus protocol.

Command 58769 Modbus Slave Address @ [breaker communication module]

OpenBr Register Data To Be Written
7720 58769 (command number)
7721 P1 = 4
7722 P2 = 4 (Breaker Communication Module)
7723 P3 = Control word for commands read in step 1 (register 553)
7724 P4 = 1

6. Wait for the command being executed.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 165

 Four-Wire Modbus® Communications System Appendix A—Registers

7. Check result code.

8. Disable activation of the MX coil.
ENGLISH

Write the following registers by using function 16 of Modbus protocol.

Command 58772
DisCoilactivation

Modbus Slave Address @ [breaker communication module]

Register Data To Be Written
7720 58772 (command number)
7721 P1 = 4
7722 P2 = 4 (Breaker Communication Module)
P3 = Control word for commands read in step 1 (register
7723
553)
7724 P4 = 10 (0x000A) See Bitmap for MX Coil Control.

9. Wait for the command being executed.

10. Check result code.
11. Return the flag.
Remotely CLOSE the Circuit Breaker Commands
Close the Circuit Breaker
Some preliminary operations are required to send the command.
On the menu of Micrologic P or H control unit, within <<Com set up>> menu,
Remote control must be set to Auto
(Register 670 must be equal to 1).
Then circuit breaker may be remotely controlled.
NOTE: To close the circuit breaker using the COM option, the device must be
equipped with an XF <<communicating>> voltage release.
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag. Get the control word from register 553.
2. Enable activation of the XF coil.
Write the following registers by using function 16 of Modbus protocol.

Command 58771
EnCoilactivation

Modbus Slave Address @ [breaker communication module]

Register Data To Be Written
7720 58771 (command number)
7721 P1 = 4
7722 P2 = 4 (Breaker Communication Module)
P3 = Control word for commands read in step 1 (register
7723
553)
7724 P4 = 12 (0x000C) See bitmap for XF Coil Control.

3. Wait for the command being executed.

4. Check result code.

166 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

5. Close the circuit breaker.

Write the following registers by using function 16 of Modbus protocol.

ENGLISH
Command 58770
CloseBr

Modbus Slave Address @ [breaker communication module]

Register Data To Be Written
7720 58770 (command number)
7721 P1 = 4
7722 P2 = 4 (Breaker Communication Module)
7723 P3 = Control word for commands read in step 1 (register 553)
7724 P4 = 1

6. Wait for the command being executed.

7. Check result code.
8. Disable activation of the XF coil.
Write the following registers by using function 16 of Modbus protocol.

Command 58772 Modbus Slave Address @ [breaker communication module]

DisCoilactivation Register Data To Be Written
7720 58772 (command number)
7721 P1 = 4
7722 P2 = 4 (Breaker Communication Module)
7723 P3 = Control word for commands read in step 1 (register 553)
7724 P4 = 12 (0x000C) See Bitmap for XF Coil Control.

9. Wait for the command being executed.

10. Check result code.
11. Return the flag.
Synchronize the Clocks Commands
Set the time and synchronize the protection and metering module.
When the time is set for the COM option, it in turn automatically sets the time for
the protection and metering modules.
Each time the supervision-system and COM-option clocks are synchronized, the
COM option automatically synchronizes with the protection and metering modules.
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
Set the time and synchronize the Breaker Communication Module.
The time set for the Breaker Communication Module is automatically used for the
protection and metering modules.
To set the time, proceed as follows.
1. Request the flag.
2. Set date time of the Breaker Communication Module.
WRITE the following registers by using function 16 of Modbus protocol.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 167

 Four-Wire Modbus® Communications System Appendix A—Registers

Command 61541 Modbus Slave Address @ [breaker communication module]

SetD_T Register Data To Be Written
ENGLISH

7720 61541 (command number)

7721 P1 = 5
7722 P2 = 4 (Breaker Communication Module)
P3: bits 15 to 8 = month (1 to 12)
7723
P3: bits 7 to 0 = day (1 to 31)
P4: bits 15 to 8 = year (0 to 199, 0 represents 1900, 102represents 2002)
7724
P4: bits 7 to 0 = hours (0 to 23)
P5: bits 15 to 8 = minutes (0 to 59)
7725
P5: bits 7 to 0 = minutes (0 to 59)

3. Wait for the command being executed.

4. Check result code.
5. Return the flag.
Depending on the procedure used to synchronize the system clocks, it is
advised to: broadcast the time-setting command.
Set the time and synchronize the Cradle Communication Module.
The time must be set for the Cradle Communication Module even if the Breaker
Communication Module is already set. Follow the same procedure described for
the Breaker Communication Module.
NOTE: When sending a command to the Cradle Communication Module, you do
not have to fill the two first parameters (P1 = Number of parameters, P2 = ID of the
module)
WRITE the following registers by using function 16 of Modbus protocol.

Command 61541 Modbus Slave Address @ [breaker communication module] + 50

SetD_T Register Data To Be Written
7720 61541 (command number)
7721 P1 = 5 (total number of parameters including P1)
7722 P2 = 4 (Breaker Communication Module)
P3: bits 15 to 8 = month (1 to 12)
7723
P3: bits 7 to 0 = day (1 to 31)
P4: bits 15 to 8 =
7724 year (0 to 199, 0 represents 1900, 102 represents 2002)
P4: bits 7 to 0 = hours (0 to 23)
P5: bits 15 to 8 = minutes (0 to 59)
7725
P5: bits 7 to 0 = seconds (0 to 59)

Remotely Configure and Set Commands

Write settings of the long time protection.
By setting the protection module to configuration mode, it is possible to write the
setup registers (8754 to 8803 and 9604 to 9798). The new configuration is not
taken into account until after exiting configuration mode.
Some preliminary operations are required to send the command. On the Micrologic
P or H front panel, within “Com set up” menu, remote access must be set to Yes
(Register 9800 must be equal to 1).
Then enter the password. The protection module configuration is protected by this
password that may be programmed and viewed exclusively on the Micrologic front

168 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

panel. This password must be noted before starting. Default access code is 0000.
Then you can access the configuration mode.

ENGLISH
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag.
2. Access the configuration mode.
WRITE the following registers by using function 16 of Modbus protocol.

Command 49202 Modbus Slave Address @ [breaker communication module]

In_pCfg Register Data To Be Written
7720 49202 (command number)
7721 P1 = 3
7722 P2 = 2 (protection module)
P3 = Password to be consulted in the menu of the control unit: Com set-
7723
up / Remote access (default is 0000).

3. Wait for the command being executed.

4. Check result code.
5. Enter new settings.
For the fine adjustments of the long time, short time, instantaneous, ground
fault, and earth leakage protection functions, you have to WRITE the following
registers (8754 to 8803) at the address @+100 [Protection Module] by using
function 6 or 16 of Modbus protocol. If you change the Ir setting, you have to
change accordingly the Isd setting since Isd expressed in amperes = (Isd rotary
switch position) x Ir.
For example with the long-time protection settings (assuming a 1000 A circuit
breaker):
Write 850 into register 8756 and 0 into register 8757 will set 850 A as fine
adjustment for Ir setting (assuming Ir rotary switch set at position .9 or higher).
Write 1500 into register 8758 will set 1.5 s as fine adjustment for tr setting
(assuming tr rotary switch set at position 2 or higher).
Write 3400 into register 8766 and 0 into register 8767 will set 3400 A (3400 =
850 x 4) as fine adjustment for Isd setting (assuming Isd rotary switch set at
position 4 or higher).
Write 0 x 0100 into register 8762 will actuate the log of the long time protection
into the Fault Wave Form capture (File N°22).

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 169

 Four-Wire Modbus® Communications System Appendix A—Registers

6. Exit the configuration mode.

WRITE the following registers by using function 16 of Modbus protocol.
ENGLISH

Command 49203 Modbus Slave Address @ [breaker communication module]

Out_pCfg Register Data To Be Written
7720 49203 (command number)
7721 P1 = 3
7722 P2 = 2 (protection module)
P3 = Password to be consulted in the menu of the control unit: Com set-up
7723
/ Remote access (default is 0000).

7. Wait for the command being executed.

8. Check result code.
9. Return the flag.
10. Check new settings.
READ the contents of the registers (8754 to 8803) by using function 3 of
Modbus protocol. The settings should be those entered in step 5.

170 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Run Remote Resets / Preset Commands

Reset the current and Voltage maximeters in the metering module.

ENGLISH
The minimeters / maximeters of the real-time measurements are reset using the
Reset_m_M command. This operation may be carried out at the same time as the
reset for other maximeters. Precise operation depends on the parameters sent with
the command (see the Appendix, List of Commands, in the “Metering Module
Commands @ Address xx + 200” on page 159).
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag.
2. Reset minimeters / reset maximeters for current and Voltage.
WRITE the following registers by using function 16 of Modbus protocol.

Command 61952 Modbus Slave Address @ [breaker communication module]

Reset_m_M Register Data To Be Written
7720 61952 (command number)
7721 P1 = 4
7722 P2 = 8 (metering module)
7723 P3 = 0 (bitmap of minimeters to reset)
7724 P4 = 9 (bitmap of maximeters to reset)

3. Wait for the command being executed.

4. Check Result code.
5. Return the flag.
Preset the total active-energy and the total apparent energy
The Energy counter values are preset using the PresetAccEnCtr command. This
operation may be carried out at the same time as the preset for active, reactive or
apparent energy counter values. Precise operation depends on the parameters
sent with the command (see the Appendix, List of Commands, in the “Metering
Module Commands @ Address xx + 200” on page 159). Follow the same
procedure described for the Breaker Communication Module.
6. Preset the total Active energy counter to 8,0364,0905,0372 kWh and preset
the total Apparent energy counter to 373,0904,0365,0009 kVAh.
WRITE the following registers by using function 16 of Modbus protocol.

Command 53760 Modbus Slave Address @ [breaker communication module]

PresetAccEnCtr Register Data To Be Written
7720 53760 (command number)
7721 P1 = 11
7722 P2 = 8 (metering module)
7723 P3 = 130 (0x0082) preset active and apparent energy counter
7724 P4 = 372 (0x174) Register 2000
7725 P5 = 905 (0x0389) Register 2001
7726 P6 = 364 (0x016c) Register 2002
7727 P7 = 8 (0x0008) Register 2003
7728 P8 = 9 (0x0009) Register 2024
7729 P9 = 365 (0x016d) Register 2025
7730 P10 = 904 (0x0388) Register 2026
7731 P11 = 373 (0x175) Register 2027

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 171

 Four-Wire Modbus® Communications System Appendix A—Registers

Manage the Event Logs— Breaker

Communication Module Commands
ENGLISH

Read a recording in event log of the Breaker Communication Module.

The event log of the Breaker Communication Module is file No. 30.
This file is always enabled.
This file will record the events associated to the alarms (1000 to 1106).
The size of each recording and the valid recording numbers may be read in
registers 718 to 743.
The event log of the Breaker Communication Module may be read using the
standard read/write functions (3, 4, 6, 16, 23).
Simply follow steps. When the command is finished, the contents of the requested
recording may be read starting in register 7730 (see “Event Log of the Breaker
Communication Module @ Address xx” on page 36).
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag.
2. Read event log characteristics (status).
Read the following registers by using function 3 of Modbus protocol.
737 = Number of records in the file (0 = no record).
738 = Sequence number of first record (the oldest) in the file.
739 = Sequence number of last record (the most recent) in the file.
3. Read event log recording.
Write the following registers by using function 16 of Modbus protocol.

Command 63178 Modbus Slave Address @ [breaker communication module]

ReadFileX_RecY Register Data To Be Written
7720 63178 (command number)
7721 P1 = 4
7722 P2 = 4 (breaker communication module)
7723 P3 = 10 (number of the file to be read)
P4 = number of the recording to be read, between the numbers of the
7724
oldest (738) and most recent (739) recordings, as per results in step 2.

4. Wait for the command being executed.

5. Check result code.
The requested recording may be read starting in registers 7730 (see “Event
Log of the Breaker Communication Module @ Address xx” on page 36) by
using function 3 of Modbus protocol. Repeat step 3 until all the records (737)
have been read.
6. Return the flag.

172 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Manage the Event Logs—Metering Module Commands

Read a recording in event log of the metering module.

ENGLISH
The event log of the metering module is file No. 10.
This file is normally enabled (register 7164 = 0xFFFF). If not, you have to enable it
by using the command 63376: EnFiles.
This file will record the events associated to the analog pre-defined alarms (1 to
53). It is therefore mandatory to configure these alarms (see the example, “Manage
the Event Logs— Configure Analog Predefined Alarm n°1: Overcurrent Phase A
Commands” on page 174).
The size of each recording and the valid recording numbers may be read in
registers 7164 to 7189.
The event log of the metering module may be read using the standard read/write
functions (3, 4, 6, 16, 23). Simply follow the steps.
When the command is finished, the contents of the requested recording may be
read starting in register 7730 (see “Event Log of the Breaker Communication
Module @ Address xx” on page 36).
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag.
2. Read event log characteristics (status).
Read the following registers by using function 3 of Modbus protocol.
7183 = Number of records in the file (0 = no record).
7184= Sequence number of first record (the oldest) in the file.
7185 = Sequence number of last record (the most recent) in the file.
3. Read event log recording.
Write the following registers by using function 16 of Modbus protocol.

Command 63178 Modbus Slave Address @ [breaker communication module]

ReadFileX_RecY Register Data To Be Written
7720 63178 (command number)
7721 P1 = 4
7722 P2 = 4 (metering module)
7723 P3 = 10 (number of the file to be read)
P4 = number of the recording to be read, between the numbers of the
7724
oldest (7184) and most recent (7185) recordings, as per results in step 2.

4. Wait for the command being executed.

5. Check result code.
The requested recording may be read starting in registers 7730 (see “Event
Log of the Breaker Communication Module @ Address xx” on page 36) by
using function 3 of Modbus protocol. Repeat step 3 until all the records (7183)
have been read.
6. Return the flag.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 173

 Four-Wire Modbus® Communications System Appendix A—Registers

Manage the Event Logs— Configure Analog Predefined Alarm n°1:

Overcurrent Phase A Commands
ENGLISH

Write settings of the alarm n°1.

By setting the metering module to configuration mode, it is possible to write access
the setup registers (6000 to 6624). The new configuration is not taken into account
until after exiting configuration mode.
Some preliminary operations are required to send the command.
On the front panel of Micrologic P or H, within “com set up” menu, Remote access
must be set to Yes (register 9800 must be equal to 1).
Then read the control word. The metering module configuration is protected by a
control word that may be read in register 3300.
Then you can access the configuration mode.
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag.
2. Get Control word.
Read the control word in register 3300 of the metering module.
3. Access the configuration mode.
WRITE the following registers by using function 16 of Modbus protocol.

Command 53298 Modbus Slave Address @ [breaker communication module]

In_mCfg Register Data To Be Written
7720 53298 (command number)
7721 P1 = 3
7722 P2 = 8 (metering module)
7723 P3 = content of register 3300 read in step 2

4. Wait for the command being executed.

5. Check Result code.
6. Enter new settings.
For the adjustments of the analog pre-defined Alarm n°1, you have to WRITE
the following registers (6000 to 6010) at the address @+200 [Metering Module]
by using function 6 or 16 of Modbus protocol.
Write 0x0001 into register 6000 will activate the alarm n°1 (Over Current Phase
A).
Write 900 into register 6003 will set the Pick-up value to 900 A. Write 7 into
register 6005 will set the Pick-up time delay to 7 s.
Write 650 into register 6006 will set the Drop-out value to 650 Amps.
Write 11 into register 6008 will set the Drop-out time delay to 11 s.
Write 0x0200 into register 6010 will actuate the log of Alarm n°1 into the Wave
Form capture (file N° 5).
7. Get Control word.
Read the control word in register 3300 of the metering module.
8. Exit the configuration mode.
WRITE the following registers by using function 16 of Modbus protocol.

174 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

Command 53299 Modbus Slave Address @ [breaker communication module]

Out_mCfg

ENGLISH
Register Data To Be Written
7720 53299 (command number)
7721 P1 = 3
7722 P2 = 8 (metering module)
7723 P3 = content of register 3300 read in step 7

9. Wait for the command being executed.

10. Check Result code.
11. Return the flag.
12. Check new settings.
READ the contents of the registers (6000 to 6624) by using function 3 of
Modbus protocol. The settings should be those entered in step 6.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 175

 Four-Wire Modbus® Communications System Appendix A—Registers

Manage the Wave Form Capture

ENGLISH

Read the metering module wave form capture record after a user request.
The wave form capture of the metering module is file No. 5.
This file is normally enabled (register 7132 = 0xFFFF). If not, you have to enable it
by using the command 63376: EnFiles.
This file will record the wave form capture triggered either by the analog pre-
defined alarms (1 to 53). It is therefore mandatory to configure these alarm (See
the example, “Manage the Event Logs— Configure Analog Predefined Alarm n°1:
Overcurrent Phase A Commands” on page 174) either on user request by using
the command forcelog.
This file consists of a fixed number of records (29). All records are of similar size,
i.e. 64 registers wide.
The record of wave form capture may be read using the standard read/write
functions (3, 4, 6, 16, 23).
Simply follow steps. When the command is finished, the contents of the requested
recording may be read starting in register 7730.
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag
2. Forcelog
Write the following registers by using function 16 of Modbus protocol.

Command 55234 Modbus Slave Address @ [breaker communication module]

Forcelog Register Data To Be Written
7720 55234 (command number)
7721 P1 = 4
7722 P2 = 8 (metering module)
7723 P3 = 0 (0x0000) bitmap of file N° 5
7724 P4 = 16 (0x0010) bitmap of file N° 5

3. Read wave form capture characteristics (Status).

Read the following registers by using function 3 of Modbus protocol
7151 = Actual Number of records in the log (0 or 29).
If 0, there is no record.
If 29, you can read the records.
4. Read wave form capture recording.
Write the following registers by using function 16 of Modbus protocol.

Command 63179 Modbus Slave Address @ [breaker communication module]

ReadFileX_RecY Register Data To Be Written
7720 63178 (command number)
7721 P1 = 4
7722 P2 = 8 (metering module)
7723 P3 = 5 (number of the file to be read)
7724 P4 = number of the recording to be read, between 1 and 29

5. Wait for the command being executed.

176 © 2012–2017 Schneider Electric All Rights Reserved 0613IB1201 R03/17

Appendix A—Registers Four-Wire Modbus® Communications System

6. Check Result code.

The requested recording may be read starting in registers 7730 (see “Format of

ENGLISH
Records in the Wave Form Capture of the Metering Module” on page 49) by
using function 3 of Modbus protocol. Repeat step 4 until all the records (29) have
been read.
7. Return the flag.

Manage the Fault Wave Form Capture

Read the protection module fault wave form capture record after a trip
condition.
The fault wave form capture of the protection module is file No. 22. This file is
normally enabled (register 9964 = 0xFFFF). If not, you have to enable it by using
the Command 63376: EnFiles.
This file will record the fault wave form capture triggered by the alarms (1000 to
1038). It is therefore mandatory to actuate the log of these alarm into the FWFC
(file N°22). See the example: remotely configure and set. This file consists of a
fixed number of records (29). All records are of similar size, i.e. 64 registers wide.
The record of fault wave form capture may be read using the standard read/write
functions (3, 4, 6, 16, 23).
Simply follow steps. When the command is finished, the contents of the requested
recording may be read starting in register 7730.
NOTE: For the standard steps such as request the flag, wait for command being
executed, check result code and return the flag, please refer to the first example of
command “Send Commands in Protected Mode” on page 164.
1. Request the flag.
2. Read Wave Form Capture characteristics (Status).
Read the following registers by using function 3 of Modbus protocol.
9983 = Actual Number of records in the log (0 or 29).
If 0, there is no record.
If 29, you can read the records.
3. Read wave form capture recording.
Write the following registers by using function 16 of Modbus protocol.

Command 63178 Modbus Slave Address @ [breaker communication module]

ReadFileX_RecY Register Data To Be Written
7720 63178 (command number)
7721 P1 = 4
7722 P2 = 2 (protection module)
7723 P3 = 22 (number of the file to be read)
7724 P4 = number of the recording to be read, between 1 and 29

4. Wait for the command being executed.

5. Check Result code.
The requested recording may be read starting in registers 7730 (see “Format of
Records in the Wave Form Capture of the Metering Module” on page 49) by
using function 3 of Modbus protocol. Repeat step 3 until all the records (29)
have been read.
Return the flag.

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 177

Index Four-Wire Modbus® Communications System

ENGLISH
Abbreviations 10–11 C power 150
Activation of the communication CCM see Cradle communication power demand 151
profile 145 module 14 power factor 152
Addresses 20 Circuit breaker ID register 155 total harmonic distortion 153
Advanced protection settings Circuit monitor 14 voltages 149
earth-leakage alarm 128 Command examples modbus functions 23
minimum voltage registers 134 manage fault wave form capture registers 145
registers 177 tripping cause registers 147
current unbalance 129 manage wave form capture 176 Communication switches 13
ground- fault alarm 127 remotely close circuit breaker 166 Communication system
load shedding and remotely configure and set 168 components 12
reconnection 141 remotely open 165 parameters 10–11
maximum current 130 send commands in protected standard wiring practices 18
maximum frequency 139 mode 164 Control power 13
maximum voltage 135 Command interface 28 characteristics 13
minimum frequency 138 communication architecture 22 Cradle communication module 14
phase rotation alarm 140 registers 29 commands 156
relay configuration 143 Command result codes 30 modbus functions 24
reverse power 137 Commands registers 24, 92
voltage unbalance 136 breaker communication module configuration 92
Alarm 157 cradle status 94
advanced protections numbers cradle communication module diagnostics counters 93
83 156 identification 92
basic protections numbers 83 examples 163 password 93
digital alarms numbers 84 metering module 159 time stamping 94
history 82
numbers 83
protection module 161 D
Communicating shunt close 14
record 82 Daisy chain system diagram 16
Communicating shunt trip 14
B Communication architecture 22 E
command interface 22 Ethernet gateway 14
Baud rate 20
module 22 Event log 35
BCM see Breaker communication
Communication module 77 breaker communication module
module 13
Communication profile 36
Breaker communication module 13
activation 145 fault wave form capture 50
cause of tripping register 89
activation registers 145 metering module 40
circuit breaker status, auto /
alarm setpoint register 148 protection module 38
manu 90
circuit breaker IO status registers wave form capture 36, 48
commands 157
146
configuration registers 87
IO registers F
diagnostics counters and
input 147 Fault wave form capture
password registers 88
status 146 event log 50
event log 36
metering registers 149 manage event logs 177
metering module event log
basic protection settings 154 File access 35
register 89
circuit breaker ID 155
modbus functions 23
current demand 151 I
protection module event log
currents 149 I/O status communication profile 146
register 89
energy 151
registers 23, 87
frequency 150 J
time stamping registers 91 JBus protocol 52
maximum currents 149
maximum voltages 152
L
miscellaneous 156
List of commands 156

0613IB1201 R03/17 © 2012–2017 Schneider Electric All Rights Reserved 178

Index Four-Wire Modbus® Communications System

M standard functions 53 current demand 151

Maintenance event log Modbus network daisy chain 13 current unbalance 129

ENGLISH
metering module 44 Module communication architecture currents 96, 149
protection module 42 22 demand current 103
demand power 104
Metering module O diagnostics counters and
commands 159
Operating principle 28 password 88
event log 40
energy 151
maintenance event log 44 P
min-max event log 46 frequency 97, 150
Parity settings 20 fundamental (RMS) 98
Modbus functions 24 Protected mode send commands 30
registers 25, 95, 149 ground- fault alarm 127
Protection module IO input 147
analog pre-defined alarms commands 161
112 k-factor demand 103
event log 38 load shedding and reconnection
configuration 106 maintenance event log 42
currents 96 141
modbus functions 26 maximum current 130
demand current 103 registers 27
demand power 104 maximum currents 149
alarm history 125 maximum frequency 139
frequency 97 basic protections settings 117
fundamental (RMS) 98 maximum voltage 135
measurements 122 maximum voltages 152
k-factor demand 103 protection module
power 96 metering configuration 106
characteristics 116 metering module 95
power factor 97 status 123
spectral components (even metering module event log 89
trip history 124 minimum frequency 138
rank) 110 times stamping 124
spectral components (odd minimum voltage 134
trip / alarm history 124 miscellaneous 156
rank) 108
time stamping 105 R phase rotation alarm 140
total harmonic distortion 99 power 96, 150
Read-accessed commands 31
voltages 95 power demand 151
Registers 85, 124
Micrologic communication system 11 power factor 97, 152
alarm history 125
Micrologic configuration registers protection module 116
analog pre-defined alarms 112
126 protection module event log 89
basic protection settings 154
Micrologic trip units protection module
basic protections settings 117
Micrologic A 12 measurements 122
breaker communication module
Micrologic H 12 protection module status 123
87
Micrologic P 12 relay configuration 143
breaker communication module
system diagram 15 reverse power 137
configuration 87
Min-max event log 46 spectral components (even rank)
cause of tripping 89
Modbus com values 77 110
circuit breaker ID 155
Modbus functions 23, 52 spectral components (odd rank)
circuit breaker IO status 146
advanced functions 55 108
communication profile 145, 149
breaker communication module time stamping 91, 105
communication profile activation
23 total harmonic distortion 99, 153
145
communication profile 23 voltage unbalance 136
communication profile alarm
cradle communication module 24 voltages 95, 149
setpoint 148
exception responses 52 Remote
communication profile IO status
logical table structure 85 close circuit breaker 166
146
metering module 24 configuration 32
cradle communication module 92
metering module registers 25 configure and set 168
cradle configuration 92
protection module 26 open circuit breaker 165
cradle diagnostics counter 93
protection module registers 27 operations 10–11
cradle identification 92
protocol 52 parameter setting 34
cradle password 93
simplified open/close command cradle status 94 S
23 cradle time stamping 94 Send commands

0613IB1201 R03/17 179

© 2012–2017 Schneider Electric All Rights Reserved
 Four-Wire Modbus® Communications System Index

optimize 32
protected mode 30
ENGLISH

protected mode example 164

shared mode 29
shared mode example 163
Shared mode
example simplified open/close
163
registers 29
send commands 29
Shunt close 14
Shunt trip 14
Simplified open/close commands 23
Standard wiring practices 18
System diagrams 15
BCM and CCM 17
BCM to daisy chain 16
Micrologic trip units, BCM and
CCM 15
Modbus TCP / IP communication
17
System problems 19
T
Table structure 85
Trip history 82, 124
Trip record 82
Troubleshooting 19
W
Wave form capture (WFC)
event log 36, 48
manage event logs 176

180 0613IB1201 R03/17

© 2012–2017 Schneider Electric All Rights Reserved
ENGLISH

Schneider Electric USA, Inc.

800 Federal Street
Andover, MA 01810 USA
888-778-2733
www.schneider-electric.us

Standards, specifications, and designs may change, so please ask for

confirmation that the information in this publication is current.

Schneider Electric and Square D are trademarks and the property of

Schneider Electric SE, its subsidiaries, and affiliated companies. All other
trademarks are the property of their respective owners.

© 2012–2017 Schneider Electric All Rights Reserved

0613IB1201 R03/17, 03/2017

Replaces 0613IB1201 06/2012