Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
List of Tables06/2012
Table 38: Digital Alarms.............................................................................................................................54
Table 56: Power Factor.............................................................................................................................. 66
Table 57: Frequency .................................................................................................................................. 66
Table 58: Fundamental .............................................................................................................................. 67
Table 59: Total Harmonic Distortion........................................................................................................... 68
Table 107: Energy ..................................................................................................................................... 117
Table 108: Current Demand .......................................................................................................
Table 109: Power Demand ........................................................................................................................ 117
Table 110: Maximum Values of Voltages .................................................................................................. 118
Table 111: Power Factor............................................................................................................................ 118
Table 112: Total Harmonic Distortion ........................................................................................................ 119
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 1—Micrologic Communication System
Section 1—Micrologic Communication System
IntroductionThe 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 AbbreviationsBCM – 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:
•4-wire Modbus,
•RTU, RS485 network,
•master / slave (Micrologic trip units are always slaves),
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 1—Micrologic Communication System06/2012
Communication System
Components
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 4-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•Trip units require 50 mA at 24 Vdc control power. 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 11.
•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 100 mA at 24 Vdc control power.
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 11.
•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.
Breaker Communication Module (BCM)•The BCM requires 50 mA at 24 Vdc control power. 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 11.
•The BCMcontrol 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 and connector into the BCM.
•See BCM instructions for each circuit breaker type for instructions and
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 1—Micrologic Communication System06/2012
System ProblemsMost 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 2-wire and 4-wire devices on the same daisy chain (2-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.
TroubleshootingGeneral
•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.
•Racking circuit breaker into Test position:
— 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:
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
Micrologic 3.0 A
menu
long time
alarm
instantaneous
.4
.5
.6
.7.8.9
.95.98
1
Ir
x In
.5
1
2
4
8
12
16
20
tr
(s)
@ 6 Ir
24
3
6
8
setting
Ii
1.5
2
4
5
10
12
x In
A
Max
Ir=
tr=
Isd=
s
tsd=
Im=
Ig
=
tg=
Digital Display
Change
to XX
Press Simultaneously
for 3 seconds
Navigation Buttons
47
(by default)
Ad47
2
.
.
.
3
1
46
06/2012Section 1—Micrologic Communication System
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
hold for 3-seconds.
Menus to change:Address
Baud Rate
Parity
Language
To step between parameters: Press and hold the arrow
button.
Display will “flash” twice when
value is saved.
NOTE: You cannot “go back”.
You will have to start over if
you need to make changes.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 2—Communication Architecture06/2012
Modbus FunctionsThe 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.
Event Log in the Breaker Communication Module
(see “Access to Files” on page 31).
NOTE: More detailed information on these registers is presented in the
Appendix, Table of Registers, “Breaker Communication Module @ Address xx”
on page 57.
Communication ProfileIn 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 CommandIn 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, neither 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 consult us).
The simplified Open/Close command is a share command (command
code = 57400).
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 2—Communication Architecture
NOTE: More detailed information on this command is presented in the
Appendix, List of Command, “Breaker Communication Module Commands
@ Address xx” on page 122.
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 RangeDescription
515–543Modbus Configuration and Identification
544–577Diagnostics Counters and Modbus Password
661–664Cradle Status
679–715Time-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 62.
Metering Module: @ Address xx + 200The 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),
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 2—Communication Architecture06/2012
Table 4:Metering Module Registers
Register
Range
1000–1299Real-Time MeasurementsThe metering module refreshes the real-time measurements every second.
1300–1599
1600–1899
2000–2199Energy Measurements
2200–2299Demand Values
3000–3299Time-Stamping
3300–3999Configuration of the Metering Module
4000–4099Reserved
4100–5699Spectral Components
5700–6899Analog Pre-Defined Alarm (1 to 53)
7100–7499
DescriptionDetails
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 Real-Time
Measurements
from 1000 to 1299
Maximum Values for the Real-Time
Measurements
from 1000 to 1299
File Header / Status (See “Access to
Files” on page 31)
• frequency,
•power,
• 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,
• RMS voltage,
• voltage unbalance,
• frequency,
•power,
• power factor,
• fundamental,
• total harmonic distortion,
• voltage crest factor,
• current crest factor.
The energy counters may be:
• reset to zero,
• 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 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 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.
The configuration registers may be read at all times. The registers may be modified via the command
interface in configuration mode.
• RMS / phase of voltage harmonic,
• RMS / phase of current harmonic.
The alarms registers may be read at all times. The registers may be modified via the command interface in
configuration mode. These alarms (available with Micrologic H only) can be used to trigger wave form capture.
Event log configuration / characteristics and format of records 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)
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 2—Communication Architecture
NOTE: More detailed information on these registers is presented in the
Appendix, Table of Registers, “Metering Module @ Address xx + 200” on
page 64.
Protection Module: @ Address xx + 100The 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 I
V
unbal
, frequency F
max
and F
min
, I
max
, voltages V
unbal
max
, maximum reverse power Rp
, V
max
and
min
, 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.
8833–8842Measurements Carried Out by the Protection Module
8843–8865Status of the Protection Module
9000–9599Time-Stamping and Trip / Alarm History
9600–9628Micrologic Configuration
9629–9799Advanced Protection Settings
9800–9899Relay Configuration (M2C / M6C)
9900–9924
9932–9956
9964–9989
Fine Settings for the Long-Time, Short-Time, Instantaneous, GroundFault and Earth-Leakage Protection Functions
Event Log (See Section: “Access to Files” on page 31)
File N° 20
Maintenance Event Log (See Section: “Access to Files” on page 31)
File N° 12
Fault Wave Form Capture (See Section: “Access to Files” on page 31)
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 83.
23
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 3—Command Interface06/2012
Section 3—Command Interface
Operating PrincipleWrite-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.
Slave @ xx
[breaker communication module]
Command Interface 7700 to 7729 Command Interface 7700 to 7729
Commands Intended for the
Breaker Communication Module
Commands Intended for the
Protection Module
Commands Intended for the
Metering Module
Slave @ xx+50
[cradle communication module]
Commands Intended for the
Cradle Communication Module Only
—
—
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 121 to determine the possible commandmanagement modes.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 3—Command Interface
Table 6:Command Interface Registers
Register
770010R / W——INT0..65535AP / H
77155R——INT0..65535AP / H
772010R / W——INT0..65535AP / H
7730100R——INT0..65535AP / H
1
See “Micrologic Command Interface for the Modbus Programmer”.
2
See “List of Commands” on page 121.
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
command interface in shared mode—
commands
command interface in protected mode—
state
command interface in protected mode—
commands
command interface in protected mode—
return
1, 2
1, 2
1, 2
1, 2
ShCmdIf
PrCmdIfState
PrCmdIf
PrCmdIfBuffer
Send Commands in Shared ModeThe shared mode uses the registers numbered 7700 to 7709 in the
command interface:
Table 7:Shared Mode Registers in the Command Interface
RegistersDescription
7700Command Number
7701Parameter P1
7702Parameter P2
7703Parameter P3
7704Parameter P4
7705Parameter P5
7706Parameter P6
7707Parameter P7
7708Parameter P8
7709Parameter P9
See the “List of Commands” on page 121 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.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 3—Command Interface06/2012
Send Commands in Protected
Mode
Registers 7715 to 7719:
May be read-accessed only and provide the
indications required to use the protected mode.
Register 7719:
Command result codes table.
The protected mode uses the registers numbered 7715 to 7829 in the
command interface.
Table 8:Protected Mode Registers in the Command Interface
RegistersDescription
7715Flag query.
7716Flag active.
7717Number of the command being executed.
7718Number of the last command executed.
7719Result code of the last command executed.
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 128.
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
he 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
1
2
3
4
4
Table 9:Command Result Codes
Result CodesDescription of Register 7719
0Command successfully executed.
10
11Command not executed, a local user is using the resources.
12
14
15Invalid record size.
16Illegal file command.
17Insufficient memory.
42Invalid file number.
81Command not defined.
82Command parameters not set or invalid.
107Invalid record number.
125Invalid number of records.
200Protected mode not active.
201End of time delay. Command not executed.
202Invalid password. Command not executed.
Command not executed, the necessary resources are not
available or the option is not installed or
remote access = NO.
Command not executed, the portable test kit is using the
local resources.
Command not executed, the resources are being used by a
remote user.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 3—Command Interface
Registers 7720 to 7729:
May be read-accessed. They are used to send
parameters and run execution of commands in
protected mode.
Table 10:Read-Accessed Commands
RegistersDescription
7720Command Number
7721Parameter P1
7722Parameter P2
7723Parameter P3
7724Parameter P4
7725Parameter P5
7726Parameter P6
7727Parameter P7
7728Parameter P8
7729Parameter P9
See the “List of Commands” on page 121 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 128. 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
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 3—Command Interface06/2012
Optimize Sending of CommandsIt 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
NOTE: Detailed information on the registers is
presented in the Appendix containing the “Table
of Registers” on page 55.
A number of simple concepts must be clear in order to remotely configure
the circuit breaker successfully.
•Configuration is carried out via the registers:
The configuration for all the modules (circuit breaker, cradle,
measurements, 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.
Breaker Communication ModuleSlave @ xx
Regular RangeConfiguration Registers
534–543
Identification of the Breaker Communication
Module
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 3—Command Interface
Metering ModuleSlave @ xx + 200
Regular RangeConfiguration Registers
3303–3355Configuration of the Metering Module
6000–6011Configuration of Analog Pre-Defined Alarm 1
6012–6635Configuration of Analog Pre-Defined Alarm 2 to 53
Protection ModuleSlave @ xx + 100
Regular RangeConfiguration Registers
8753–8803Fine Adjustments for the Basic Protection
9604–9618Configuration of the Protection Module
Continued on next page
9629–9798Settings for the Advanced Protections
9800–9846Configuration 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
visa-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.
New configurations are always checked before being accepted.
When writing in the configuration registers, the Modbus write functions are
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.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 3—Command Interface06/2012
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 127.
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.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 4—Access to Files
Section 4—Access to Files
IntroductionMicrologic 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 127.
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
Event Logs
Maintenance Event Logs
Min-Max Event Log
Breaker Communication
Module @ xx
Protection Module
@ xx + 100
Metering Module
@ xx + 200
Protection Module
@ xx + 100
Metering Module
@ xx + 200
Metering Module
@ xx + 200
Micrologic A / P / H
Micrologic P / H
Micrologic H
Micrologic H
Micrologic H
Micrologic H
The system stores the events that concern circuit breaker control
(for example: opening or closing of the contacts) in the file N° 30.
This file is made up of 100 records, each record is made up of 5 registers.
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
(for example: trips, alarms) in the file N° 20.
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
(for example: analog pre-defined alarms 1 to 53) in the file N° 10.
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.
This file is made up of 20 records, each record is made up of 6 registers.
This maintenance event log has been implemented as well on Micrologic P
with firmware Plogic2002AA and above.
The system stores the events that concern the maintenance metering module
(for example: counter reset, and so on) in the file N° 12.
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:
minimum and maximum values for the real time measurements 1000 to 1136)
in the file N° 11.
This file is made up of 136 records, each record is made up of 8 registers.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 4—Access to Files06/2012
Wave Form Capture (WFC)
The system stores the variables Va, Vb, Vc, Ia, Ib, Ic, Ineutral, during 4 cycles (64
points per cycles) in the file N° 5.
Wave Form Capture
Fault Wave Form Capture
In the Metering Module
@ xx + 200
In the Protection
Module @ xx + 100
Micrologic H
Micrologic H
The capture is triggered:
• manually (user request) by using the command “Forcelog“ (see the Appendix,
“Metering Module Commands @ Address xx + 200” on page 124),
• 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.
The capture is triggered:
• 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 11:Descriptor of the Event Log in the Breaker Communication Module
Register
Number of
Registers
Read /
Scale UnitFormat IntervalAP / H DescriptionLabel
Write
Event Log Configuration (HEADER)
File status.
7181R——INT0xFFFFAP / H
7191R——INT30AP / H
7201R——INT0xFFFFAP / H
7211Rx 1register INT5AP / H
7221R——INT0AP / H
0xFFFF: file enabled.
Always equal to: 0xFFFF.
Type of file.
Event log of the
Breaker Communication Module.
Always equal to: 30.
File allocation.
0xFFFF: file allocated.
Always equal to: 0xFFFF.
Size of records in register.
Always equal to: 5.
File filling mode.
0: circular.
Always equal to: 0.
Event Log Characteristics (STATUS)
7341Rx 1rec.INT100AP / H
7351Rx 1register INT5AP / H
7371Rx 1rec.INT0..100AP / H
7381Rx 1rec.INT0..8000AP / H
7391Rx 1rec.INT0..8000AP / H
7403R——DATE——P / H Date the last file was reset.
Size of file in records.
Always equal to: 100.
Size of a record in registers.
Always equal to: 5.
Number of records in the file.
0: no record in the file.
Sequence number of first record in the file
(the oldest).
0: no record in the file.
Sequence number of last record in the file
(the most recent).
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 4—Access to Files
Table 15:Format of Records in the Event Log of the Protection
Module
RegistersDescription
1–4
5Event number (see below).
6Event characteristics.
7Type of event.
8Logging bitmap associated to the alarm.
9Action bitmap associated to the alarm.
1
For 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.
2
Bits 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.
2
Bits 8 to 11
The value 1 indicates the start of an alarm.
The value 2 indicates the end of an alarm.
2
Bits 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.
3
Registers 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.
Event date, in the XDATE format
(see the Appendix, “Formats” on page 52).
1
2
3
3
Table 16:Events in the Event Log of the Protection Module
Event NumberDescription
1000..1015Basic protection
1016..1031Advanced protection
1100..1115Digital alarms
1
See description of the “Alarm Numbers” in the Appendix, “Trip / Alarm History” on page 53.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 4—Access to Files
Table 18:Format of Records in the Event Log of the Metering
Module
RegistersDescription
1–3
4Reserved.
5Event number (see below).
6Extreme value.
7Type of event.
8Logging bitmap associated to the alarm.
9Action bitmap associated to the alarm.
1
Bits 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.
1
Bits 8 to 11
The value 1 indicates the start of an alarm.
The value 2 indicates the end of an alarm.
1
Bits 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.
2
Registers 8 and 9 are a copy of the alarm-configuration registers at the moment the event
occurred. They depend entirely on the user configurations.
Event date, in the XDATE format
(see the Appendix, “Formats” on page 52).
1
2
2
Table 19:Events in the Event Log of the Metering Module
Event NumberDescription
1 to 53Analog pre-defined alarms.
See the “Analog Pre-Defined Alarms” on page 79, 1 to 53 in the Appendix, Table of Registers
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 4—Access to Files
This file consists of a fixed number of records (29). All records are of similar
size, for example, 64 registers wide.
Table 27:Format of Records in the Wave Form Capture of the
Metering Module
Record
Number
1
2 to 51–64Voltage A sample points (64 points – 4 cycles).
6 to 91–64Voltage B sample points (64 points – 4 cycles).
10 to 131–64Voltage C sample points (64 points – 4 cycles).
14 to 171–64Current A sample points (64 points – 4 cycles).
18 to 211–64Current B sample points (64 points – 4 cycles).
22 to 251–64Current C sample points (64 points – 4 cycles).
26 to 641–64
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.
RegistersDescription
1–4Extended date / time.
5–11Reserved.
12
13System type: 30, 31, 40 or 41 (see register 3314).
14Circuit breaker nominal current in amps.
15Voltage multiplier for phase A (format is SFIXPT).
16Voltage Offset for phase A (format is INT).
17Same as 15, for phase B.
18Same as 16, for phase B.
19Same as 15, for phase C.
20Same as 16, for phase C.
21Current multiplier for phase A (format is SFIXPT).
22Current Offset for phase A (format is INT).
23Same as 21, for phase B.
24Same as 22, for phase B.
25Same as 21, for phase C.
26Same as 22, for phase C.
27Current multiplier for neutral (format is SFIXPT).
28Same as 22, for neutral.
29Scaling factor used for SFIXPT math on voltage samples.
30
31
32–64Not used.
ID of WFC trigger (analog predefined alarm 1 to 53).
Available with firmware version H Logic 2005 AF.
Scaling factor used for SFIXPT math on phase current
samples.
Scaling factor used for SFIXPT math on neutral current
samples.
Current N sample points (64 points – 4 cycles)
Only valid in 41 system.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 4—Access to Files
This file consists of a fixed number of records (22). All records are of similar
size, for example, 64 registers wide.
Table 29:Format of Records in the Fault Wave Form Capture of the
Protection Module
Record
Number
1
2 to 41–64Voltage A sample points (16 points – 12 cycles).
5 to 71–64Voltage B sample points (16 points – 12 cycles).
8 to 101–64Voltage C sample points (16 points – 12 cycles).
11 to 131–64Current A sample points (16 points – 12 cycles).
14 to 161–64Current B sample points (16 points – 12 cycles).
17 to 191–64Current C sample points (16 points – 12 cycles).
20 to 221–64
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.
RegistersDescription
1–4Extended date / time.
5–11Reserved.
12
13System type: 30, 31, 40 or 41 (see register 3314).
14Circuit breaker nominal current in amps.
15Voltage multiplier for phase A (format is SFIXPT).
16Voltage offset for phase A (format is INT).
17Same as 15, for phase B.
18Same as 16, for phase B.
19Same as 15, for phase C.
20Same as 16, for phase C.
21Current multiplier for phase A (format is SFIXPT).
22Current Offset for phase A (format is INT).
23Same as 21, for phase B.
24Same as 22, for phase B.
25Same as 21, for phase C.
26Same as 22, for phase C.
27Current multiplier for neutral (format is SFIXPT).
28Same as 22, for neutral.
29Scaling factor used for SFIXPT math on voltage samples.
30
31
32–64Not used.
Id of fault WFC Trigger: Alarm number 1000 to 1031 (see the
Appendix, “Trip / Alarm History” on page 53).
Scaling factor used for SFIXPT math on phase current
samples.
Scaling factor used for SFIXPT math on neutral current
samples.
Current N sample points (16 points – 12 cycles)
Only valid in 41 system.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 5—Modbus Functions06/2012
Section 5—Modbus Functions
IntroductionModbus 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 ProtocolIn 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).
RequestResponse
Function—03Function—03
Starting AddressHi03Byte count—02
Starting AddressLoF7Register valueHi02
N° of registersHi00Register valueLo2B
N° of registersLo01———
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 Amps.
Modbus Exception ResponsesWhen 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.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 5—Modbus Functions
The exception response message has two fields that differentiate it from a
normal response:
Function code: Function code of the original request + 0x80 (hexa)
Exception code: See the following list
01ILLEGAL FUNCTION
02ILLEGAL DATA ADDRESS
03ILLEGAL DATA VALUE
04SLAVE DEVICE FAILURE
05ACKNOWLEDGE (in conjunction with programming commands)
06SLAVE DEVICE BUSY (in conjunction with programming commands)
08MEMORY PARITY ERROR (with function code 0x14)
Standard Modbus Functions
Table 30:Read Functions
Function
Code
3—Read n output or internal registers.
4—Read n input registers.
23—Simultaneously read / write n and p registers.
43—Read Device Identification
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).
Sub-Function Description
1, 2
1,2
1, 2
3
Table 31:Write Functions
Function
Code
6—Write one register.
16—
22—Write one register with mask.
23—
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 32:Diagnostic Functions
Function
Code
8—Management of the diagnostics counters.
810Clear the diagnostics counters.
811Read the bus-messages counter managed by the slave.
812Read the bus-errors counter managed by the slave.
813
814Read the counter for messages sent to the slave.
815
Sub-Function Description
Read the bus-exception answer counter managed by the
slave.
Read the counter for messages sent to the slave and to
which the slave did not answer.
Continued on next page
49
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Section 5—Modbus Functions06/2012
Table 32:Diagnostic Functions (continued)
Function
Code
816
817
818
11—Read the Modbus event counter.
17—Read the identifier of the Modbus slave.
Sub-Function Description
Read the counter for messages sent to the slave and to
which the slave replied with an exception code 07 “Negative
Acknowledge”.
Read the counter for messages sent to the slave and to
which the slave replied with an exception code 06 “Slave
Device Busy”.
Read the counter for messages sent to the slave that it could
not process due to a transmission error.
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.
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.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Section 5—Modbus Functions
Advanced Modbus FunctionsRead 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 33:Example of an Advanced Modbus Function
RequestAnswer
Name of FieldExampleName of FieldExample
Slave address47Slave address (identical)47
1
Function
Number of registers read + 26
Sub-function code
Transmission number
Address of first register to read
(most significant byte)
Address of first register to read
(least significant byte)
Address of second register to
read (most significant byte)
Address of second register to
read (least significant byte)
CRC highXXCRC highXX
CRC lowXXCRC lowXX
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.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
APPENDIX A— REGISTERS
Formats
UINT
INT
Mod10000
SFIXPT
Date
XDATE
ASCII
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).
UINT corresponds to a 16-bit unsigned integer with an interval of values
from 0x 0000…0 x FFFF (0…65535).
INT corresponds to a 16-bit signed integer with an interval of values
from 0x 8000…0 x 7FFF (-32768…+32767).
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.
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 corresponds to a normal date made up of three UINT, as follows:
• first UINT:
month expressed using the eight most-significant bits (January = 0x41)
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 corresponds to an extended date made up of four UINT, as follows:
• first UINT:
month expressed using the eight most-significant bits (January = 0x41)
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 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.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Trip / Alarm HistoryTrip 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 34:Trip Record Fields
Field
___.XtedDT4XDATECfformat0x8000Trip date.
___.ActCause AlarmNum 1INT0..10310x8000Number of alarm causing activation.
___.PuValue2MOD 1000See Text0x8000Value of protection setting that caused trip.
___.PuDelay1INTSee Text0x8000Value of time delay that caused trip.
___.FaultI[0]1INT0..160000x8000Trip current phase A, expressed with respect to the rated current.
___.FaultI[1]1INT0..160000x8000Trip current phase B, expressed with respect to the rated current.
___.FaultI[2]1INT0..160000x8000Trip current phase C, expressed with respect to the rated current.
___.FaultI[3]1INT0..160000x8000Trip current on neutral, expressed with respect to the rated current.
___.WorstContact Wear1INT0..327670x8000
___.AddInfo2See TextSee Text0x8000Reserved.
___.Reserved5——0x8000Reserved.
1
Expressed as x 0.1 of In (rated current).
Number of
Registers
FormatIntervalN/ADescription
New value of contact-wear indicator following a trip.
The control unit records one indicator per contact. Here, only the value
for the most worn contact is given. (See registers 9094 to 9097).
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:
1
1
1
1
Table 35:Alarm Record Fields
Field
___.XtedDT4XDATEcfformat0x8000Alarm date.
___.ActCause AlarmNum 1INT0..10310x8000Number of alarm causing activation.
___.PuValue2MOD 10000See Text0x8000Value of protection setting that caused alarm activation.
___.PuDelay1INTSee Text0x8000Value of time delay that caused alarm activation.
___.FaultI[0]1INT0..160000x8000Alarm current phase A, expressed with respect to the rated current.
___.FaultI[1]1INT0..160000x8000Alarm current phase B, expressed with respect to the rated current.
___.FaultI[2]1INT0..160000x8000Alarm current phase C, expressed with respect to the rated current.
___.FaultI[3]1INT0..160000x8000Alarm current on neutral, expressed with respect to the rated current.
___.AddInfo2See TextSee Text0x8000Additional information, depending on type of alarm.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table of Registers
Structure of the TableEach Modbus logical table is made up of the fields listed below.
Register
Number of Registers
Read / Write:
“R”
“W”
“R/W”
Scale (x n)
Unit
Format
Interval
A, P, H
Description
Label
Number of the Modbus register.
Number of registers that must be read or written for a given complete piece of information. This
data indicates the type of register
(8-bit, 16-bit or 32-bit register).
Register that may be accessed by the Modbus read functions
3, 4, 23, 20, 100 (see page 49).
Register that may be accessed by the Modbus write functions
6, 16, 22, 23 (see page 49).
Register that may be read and write accessed.
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 of measurement for the value contained in the register.
Format in which the information is coded.
Interval of the possible values that each register in the group
{Register, Register +1, ..., Register + Nb} can have.
Type of control unit using the register:
“A”: Micrologic A control unit
“P”: Micrologic P control unit
“H”: Micrologic H control unit
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.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 42:Diagnostics Counters and Password
Register
5441R——INT0..32767AP / H
5451R——INT0..32767AP / H
5461R——INT0..32767AP / H
5471R——INT0..32767AP / H
5481R——INT0..32767AP / H
5491R——INT0..32767AP / H
5501R——INT0..32767AP / H
5511R——INT0..32767AP / H
5531R——INT0..65535AP / H
5541R——INT0..65535AP / H
5551R——INT0..65535AP / H
5771R1—INT—AP / H
1
The counter automatically cycles from 32767 to 0.
2
The counter automatically cycles from 65535 to 0.
Number of
Registers
Read /
Scale UnitFormat IntervalAP / H DescriptionLabel
Write
Modbus diagnostics counter—messages
sent to the slave (identical to function
1
8-14).
Modbus diagnostics counter—messages
sent to other slaves.
Modbus diagnostics counter—bus
messages managed by the slave
(identical to function 8-11).
Modbus diagnostics counter—bus errors
managed by the slave (identical to function
1
8-12).
Modbus diagnostics counter—messages
sent to the slave comprising a nonsupported Modbus function.
Modbus event counter—
(identical to function 11).
Modbus diagnostics counter—bus
exception replies managed by the slave
(identical to function 8-13).
Modbus diagnostics counter—broadcast
messages received by the slave
(identical to function 8-17).
Control word of the Cradle Communication
Module. This control word cannot be set by
the user. It is randomly changed each time
the 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
Communication Module is energized.
Counter for the number of Cradle
Communication Module resets, whether
following power loss or not.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 45:Circuit Breaker Status, Auto / Manu
Register
6611R——
6621R——INT0..65535AP / H
6631R——INT0..65535AP / H
6641R——INT0..65535AP / H
6651R——INT0..65535AP / H
6691R——
6701R——INT0..1—P / H
SD: Trip indication.
SDE: Fault-trip indication.
OF: ON / OFF.
1
The counter automatically cycles from 65535 to 0.
Number of
Registers
Read /
Write
Scale UnitFormat IntervalAP / H DescriptionLabel
Bitmap
16
Bitmap
16
—AP / H
0..65535AP / H
Circuit breaker status:
see next page.
Counter for total number of
operations (OF):
the counter increments
when bit 0 in register 661
switches from 0 to 1.
Counter for operations (OF) since
last reset:
the counter increments
when bit 0 in register 661
switches from 0 to 1.
Counter for operations (SD):
the counter increments
when bit 1 in register 661
switches from 0 to 1.
Counter for operations (SDE):
the counter increments
when bit 2 in register 661
switches from 0 to 1.
Authorization word for actuation
by MX and XF auxiliaries:
• when bit 1 and 3 are set,
MX is authorized to 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
opening and closing of the
circuit breaker are enabled.
Auto / Manu mode can be
modified on Micrologic P / H
(only locally).
Default value = 1
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 46:List of Possible Values for Register 661 (Circuit Breaker
Status) in the Breaker Communication Module
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 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 RTC0x51 ON discharged not RTC
0x4C Tripped charged not RTC0x59 ON charged RTC
0x50 OFF discharged not RTC0x78 OFF charged RTC
Table 47:Time Stamping
Register
6713R——DATE—AP / H Date of last actuation of MX auxiliary.LastXFCoilActivationD_T
6741R——INT0..65535 AP / H MX actuation counter.
6753R——DATE—AP / H Date of last actuation of XF auxiliary.LastMXCoilActivationD _T
6781R——INT0..65535 AP / H XF actuation counter.
6794R——XDATE —AP / H
6843R——DATE—AP / H Date of last circuit breaker opening.LastOFContactOpenD_T
6873R——DATE—AP / H Date of last circuit breaker closing.LastOFContactCloseD_T
6903R——DATE—AP / H Date of last trip without an electrical fault.LastSDContactSetD_T
6933R——DATE—AP / H Date of last trip with an electrical fault.LastSDEContactSetD _T
6963R——DATE—AP / H Date of last PAF (ready-to-close) closing.LastPAFContactSetD _T
6993R——DATE—AP / H Date of last DLO (half moon) closing.LastDLOContactSetD _T
7023R——DATE—AP / H Date of last AD (charged) closing.LastADContactSetD_ T
7053R——DATE—AP / H Date of last address change (register 531). LastAddressChangeD_T
7083R——DATE—AP / H
7114R——XDATE —AP / H
7151R——INT0..65535 AP / H
8001R / W———0..1AP / H
8021R————AP / H Open command status.—
8031R————AP / H Close command status.—
Registers 718 to 740 file N° 30 (see “Access to Files” on page 31).
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)
Number of
Registers
Read /
Scale UnitFormat Interval AP / H DescriptionLabel
Write
1
1
Current date of Cradle Communication
Module.
Date of last reset of Cradle Communication
Module event log.
Date when time for Cradle Communication
Module was last set.
Counter for time setting for Cradle
Communication Module.
Communication profile activation
0 = Not activated
1 = activated
Default value = 0
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 50:Diagnostics Counters and Password (continued)
Register
553 1 R ——INT 0..65535AP / H
554 1 R ——INT 0..65535AP / H
555 1 R ——INT 0..65535AP / H
577 1 R 1—INT —AP / H
1
The counter automatically cycles from 32767 to 0.
2
The counter automatically cycles from 65535 to 0
Number of
Registers
Read /
Scale UnitFormat IntervalAP / H DescriptionLabel
Write
Table 51:Cradle Status
Register
6611R——
6621R——INT0..65535AP / H
6631R——INT0..65535AP / H
6641R——INT0..65535AP / H
1
The counter automatically cycles from 65535 to 0.
Number of
Registers
Read /
Scale UnitFormat IntervalAP / H DescriptionLabel
Write
Bitmap
16
—AP / H
Control register of the Cradle
Communication Module. This control word
cannot be set by the user. It is randomly
changed each time the 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
Communication Module is energized.
Counter for the number of Cradle
Communication Module resets, whether
following power loss or not.
Cradle Communication Module firmware
version.
Device status:
if bit 9 (0x0200) is set to 1,
the device is connected
if bit 8 (0x0100) is set to 1,
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:
the counter increments when bit 8 in
register 661 switches from 0 to 1.
Counter for change to the “disconnected”
position:
the counter increments when bit 9 in
register 661 switches from 0 to 1.
Counter for change to the “test” position:
the counter increments when bit 10 in
register 661 switches from 0 to 1.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 54:Currents
Register
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
10161Rx 1AINT0..32767AP / H RMS current on phase A.I_RMS[0]
10171Rx 1AINT0..32767AP / H RMS current on phase B.I_RMS[1]
10181Rx 1AINT0..32767AP / H RMS current on phase C.I_RMS[2]
10191Rx 1AINT0..32767AP / H RMS current on the neutral.
10201Rx 1AINT0..32767AP / H
10211Rx 1AINT0..32767AP / H
Maximum rms current in registers
1016, 1017, 1018 and 1019.
Ground-fault current:
if this current exceeds 32767 A,
the register blocks at 32767.
10221Rx 1mAINT0..32767AP / H
Earth-leakage current:
if this current exceeds 32767 A,
the register blocks at 32767.
1
2
3
I_RMS[3]
I_Max
I_RMSGnd
I_RMSVigi
10231Rx 1AINT0..32767—HApparent current phase A (peak √2).I_APP[0]
10241Rx 1AINT0..32767—HApparent current phase B (peak √2).I_APP[1]
10251Rx 1AINT0..32767—HApparent current phase C (peak √2).I_APP[2]
10261Rx 1AINT0..32767—HApparent current neutral (peak √2).I_APP[3]
10271Rx 1AINT0..32767—P / H
10281Rx 10%INT
10291Rx 10%INT
10301Rx 10%INT
10311Rx 10%INT
10321Rx 10%INT
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
—P / H
—P / H
—P / H
—P / H
—P / H
Arithmetic mean of phase currents
A, B and C: 1/3 x (I
I
current unbalance with respect to the
A
arithmetic mean of the phase currents.
I
current unbalance with respect to the
B
arithmetic mean of the phase currents.
I
current unbalance with respect to the
C
arithmetic mean of the phase currents.
I
current unbalance with respect to the
N
arithmetic mean of the phase currents.
A+IB+IC
).
Maximum current unbalance in registers
1028, 1029 and 1030.
1
I_Mean
I_Unbal[0]
I_Unbal[1]
I_Unbal[2]
I_Unbal[3]
I_UnbalMax
10331R—————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 55:Power
Register
Number of
Registers
10341Rx 1kWINT+/- 0..32767 —P / H Active power on phase A.
10351Rx 1kWINT+/- 0..32767 —P / H Active power on phase B.
10361Rx 1kWINT+/- 0..32767 —P / H Active power on phase C.
10371Rx 1kWINT+/- 0..32767 —P / H Total active power.
10381Rx 1kVAR INT+/- 0..32767 —P / H Reactive power on phase A.
10391Rx 1kVAR INT+/- 0..32767 —P / H Reactive power on phase B.
10401Rx 1kVAR INT+/- 0..32767 —P / H Reactive power on phase C.
10411Rx 1kVAR INT+/- 0..32767 —P / H Total reactive power.
10421Rx 1kVA INT0..32767—P / H
10431Rx 1kVA INT0..32767—P / H
10441Rx 1kVA INT0..32767—P / H
10451Rx 1kVA INT0..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.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 56:Power Factor
Register
10461Rx 1000 none INT
10471Rx 1000 none INT
10481Rx 1000 none INT
10491Rx 1000 none INT
10501Rx 1000 none INT
10511Rx 1000 none INT
10521Rx 1000 none INT
10531Rx 1000 none INT
1
Value not accessible when the configuration register 3314 returns type 31.
2
The sign of the power factor depends on configuration register 3318.
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
-1000..
+1000
Table 57:Frequency
—P / H
—P / H
—P / H
—P / H
—H
—HSame as above phase B.FundPF[1]
—HSame as above phase C.FundPF[2]
—H
Power factor on phase A (absolute value
equal to |P|/S).
Power factor on phase B (absolute value
equal to |P|/S).
Power factor on phase C (absolute value
equal to |P|/S).
Total power factor (absolute value
equal to |Ptotal|/Stotal).
Fundamental power factor on phase A
(its absolute value is equal to
|FundP|/FundS).
Sign convention the same as the one for
the real power factor.
N/A if type 31 network.
Total fundamental power factor
(its absolute value is equal to
|FundPtot|/FundStot).
Sign convention the same as
the one for the real power factor.
1, 2
1, 2
1, 2
2
PF[0]
PF[1]
PF[2]
PF[3]
FundPF[0]
FundPF[3]
Register
10541Rx 10HzINT0..4000—P / H System frequency.Frequency
10551Rx.001sINT0..32767—P / H
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Duration of the interval between the last
update of real time values and the current
table (about 1s).
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).
69
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 60:Energy
Register
20004Rx 1kWh
20044Rx 1kVARh
20084Rx 1kWh
20124Rx 1kWh
20164Rx 1kVARh
20204Rx 1kVARh
20244Rx 1kVAh
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).
Number of
Registers
Read /
Scale UnitFormat IntervalAP / H DescriptionLabel
Write
0..+/-
MOD
10000
MOD
10000
MOD
10000
MOD
10000
MOD
10000
MOD
10000
MOD
10000
9999
9999
9999
9999
0..+/9999
9999
9999
9999
0..+/9999
9999
9999
9999
0..+/9999
9999
9999
9999
0..+/9999
9999
9999
9999
0..+/9999
9999
9999
9999
0..+/9999
9999
9999
9999
—P / H Total active energy.
—P / H Total reactive energy.
—P / H
—P / H
—P / H
—P / H
—P / H Total apparent energy.EeApparentEnergy
Active energy positively
incremented.
Active energy negatively
incremented.
Reactive energy positively
incremented.
Reactive energy negatively
incremented.
1
1
2
2
2
2
EeActiveEnergy
EeReactiveEnergy
EeActiveEnergyln
EeActiveEnergyOut
EeReactiveEnergyIn
EeReactiveEnergyOut
Table 61:Demand Current
Register
22001Rx 1AINT0..32767—P / H Current demand on phase A.I_Dmd[0]
22011Rx 1AINT0..32767—P / H Current demand on phase B.I_Dmd[1]
22021Rx 1AINT0..32767—P / H Current demand on phase C.I_Dmd[2]
22031Rx 1AINT0..32767—P / H Current demand on the neutral.
22041Rx 1AINT0..32767—P / H
22051Rx 1AINT0..32767—P / H
22061Rx 1AINT0..32767—P / H
22071Rx 1AINT0..32767—P / H
1
Value not accessible when the configuration register 3314 returns type 31 or 40
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Current demand maximum on phase A
since the last reset.
Current demand maximum on phase B
since the last reset.
Current demand maximum on phase C
since the last reset.
Current demand maximum on the neutral
since the last reset.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 64:Time Stamping
Register
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
30004R——DATE——P / H Current date of the metering module.XtedDateTime
30053R——DATE——P / H
30083R——DATE——P / H
30113R——DATE——P / H
30143R——DATE——P / H
30173R——DATE——P / H
30203R——DATE——P / H
30233R——DATE——P / H
30263R——DATE——P / H
30293R——DATE——P / H
30323R——DATE——P / H
30353R——DATE——P / H
Date of last current demand maximum I
(register 2204).
Date of last current demand maximum I
(register 2205).
Date of last current demand maximum I
(register 2206).
Date of last current demand maximum on
the neutral (register 2207).
Date of last active-power demand
maximum (register 2224).
Date of last reactive-power demand
maximum (register 2230).
Date of last apparent-power demand
maximum (register 2236).
1
Date of last reset of current demand
maximum values.
Date of last reset of power demand
maximum values.
Date-Time of last min registers reset
(1300-1599).
Date-Time of last max registers reset
(1600-1899).
2
2
A
NvI_DmdPk[0]
B
NvI_DmdPk[1]
C
NvI_DmdPk[2]
NvI_DmdPk[3]
NvActivePwrDmdPk
NvReactivePwrDmdPk
NvApparentPwrDmdPk
NvLastI_DmdReset
NvLastPwrDmdReset
NvLastMinReset
NvLastMaxReset
30383R——DATE——P / H Date of last reset of energy meters.NvLastEnReset
30413R——DATE——P / H
30443R——DATE——P / H
30473R——DATE——P / H
30503R——DATE——P / H
30533R——DATE——P / H
30563R——DATE——P / H
30593R——DATE——P / H
30623R——DATE——P / H
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.
Date of appearance of last K-factor demand
peak (phase A).
Date of appearance of last K-factor demand
peak (phase B).
Date of appearance of last K-factor demand
peak (phase C).
Date of appearance of last K-factor demand
peak (neutral) N/A for type 31 & 40
networks.
2
Date of appearance of last I
demand
peak (phase A).
Date of appearance of last I
peak (phase B).
Date of appearance of last I
peak (phase C).
Date of appearance of last I
demand peak (neutral) N/A for type
31 & 40 networks.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 65:Configuration
Register
33001R——INT0..65535—P / H
33032R / W——ASCII0x00..0x7F —P / H
33058R / W——ASCII0x00..0x7F —P / H
33141R / W——INT
33161R / W——INT0,1—P / H
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
30, 31,
40, 41
—P / H
Control word for the metering module. This
control word may not be user set. It is
randomly modified and must be read before
sending certain commands to the metering
module.
Short identifier of the metering module,
coded over four ASCII characters.
Default value: “set!”
Long identifier of the metering module,
coded over 16 ASCII characters.
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-toneutral 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 current is
not available.
• If you have a system type: 3 phase,
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.
Sign convention for the power:
• 0: “+” if the active power flows from
upstream (top)
to downstream (bottom) (
• 1: “+” if the active power
flows from downstream
(bottom) to upstream (top) (
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 65:Configuration (continued)
Register
33171R / W——INT0,1—P / H
33181R / W——INT0,1, 2—P / H
33191R / W——INT0,1—H
33241R / W——INT0,1—P / H
33511R / W——INT——P / H
33521R / Wx 1min INT5..60—P / H
33541R / W——INT——P / H
33551R / Wx 1minINT5..60—P / H
38161R——INT0..32767AP / H
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.
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Sign convention for the reactive power:
• 0: alternate IEEE convention,
• 1: IEEE & IEC convention.
Default value: 1.
Sign convention for the power factor:
• 0: IEC convention,
• 1: alternate IEEE convention,
• 2: IEEE convention.
Default value: 2.
Reactive power calculation convention:
• 0: fundamental alone,
• 1: harmonics included [DEFAULT].
Total energy metering convention:
• 0: absolute accumulation (E = E+ + E-),
• 1: signed accumulatio.n (E = E+ - E-).
Default = 0: Absolute
Current-demand calculation method;
window type:
• 0: Block interval; sliding,
• 1: Thermal; sliding.
Default value: 1.
Duration in minutes of the current-demand
calculation window.
Default value: 15 minutes.
Power-demand calculation method; window
type:
• 0: Block interval; sliding,
• 1: Thermal; sliding,
• 2: Block interval; block,
• 5: Synchronized to communication.
Default value: 0.
Duration in minutes of the power-demand
calculation window.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 68:Analog Pre-Defined Alarms
Register
57001R——Bitmap 0.0xFFFF—H
57011R——Bitmap 0.0xFFFF—H
57021R——Bitmap 0.0xFFFF—H
57031R——Bitmap 0.0xFFFF—H
600012————Template——
60001R / W——INTSee Text—H
60011
60021
60031R / W
60041
60051R / Wx 1 sINT——H
60061R / W
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Read
——INT1016—H
Only
Read
——INT1 —H
Only
See
See
Text
Read
100%INT——H
Only
See
Text
INT——H
Text
See
INT——H
Text
Pre-Defined Alarms Status Bitmap.
Alarms 48 through 63.
Bit 0 represents status of Pre-Defined.
Alarm N°48. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarms Status Bitmap.
Alarms 32 through 47.
Bit 0 represents status of Pre-Defined
Alarm N°32. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarms Status Bitmap.
Alarms 16 through 31.
Bit 0 represents status of Pre-Defined
Alarm N°16. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarms Status Bitmap.
Alarms 0 through 15.
Bit 0 represents status of Pre-Defined
Alarm N°1. If set, Alarm is active.
Status tracks the actual alarm status.
Pre-Defined Alarm N° 1 Setting.
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 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
compared to the pickup setpoint and
to the dropout setpoint.
Default value: 1016.
Comparison mode.
MSB indicates Pickup mode.
LSB indicates Dropout mode.
MSB can be set to 1, 2 or 4.
LSB can be set to 1, 2 or 4.
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
must be taken to set this register with the
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
register, when Direct Mode is selected.
Otherwise, register is not used.
Default value: 0x8000.
Actuation time delay Time delay must be
set in seconds.
Default value: 0x8000.
Release set point.
When Immediate mode is selected, care
must be taken to set this register with the
same units and scale factors then the
Compare Register CompReg.
Default value: 0x8000.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 68:Analog Pre-Defined Alarms (continued)
Register
60071
60081R / Wx 1sINT——H
60091
60101R / W——INTBitmap—H
60111R / W—————HReserved.___.
601212————Template——
602412————Template——
603612————Template——
604812————Template——
606012————Template——
607212————Template——
608412————Template——
609612————Template——
610812————Template——
612012————Template——
613212————Template——
614412————Template——
615612————Template——
616812————Template——
618012————Template——
619212————Template——
620412————Template——
621612————Template——
622812————Template——
624012————Template——
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
This register contains a numerical value
Read
100%INT——H
Only
Read
——INT0, 1, 2, 3—H
Only
that is multiplied to the content of the
dropout register, when Direct Mode is
selected. Otherwise, register is not used.
Default value: 0x8000.
Release time delay.
Time delay must be set in seconds.
Default value: 0x8000.
Alarm Type.
0 indicates “Over”,
1 indicates “Under”,
2 indicates “Equal to”,
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 into the Wave Form Capture file (file N°
5). 0x0200
value is 0x0000.
Pre-Defined Alarm N° 2 Setting.
Over Current Phase B.
Pre-Defined Alarm N° 3 Setting.
Over Current Phase C.
Pre-Defined Alarm N° 4 Setting.
Over Neutral Current.
Pre-Defined Alarm N° 5 Setting.
Over Ground Current.
Pre-Defined Alarm N° 6 Setting.
Under Current Phase A.
Pre-Defined Alarm N° 7 Setting.
Under Current Phase B.
Pre-Defined Alarm N° 8 Setting.
Under Current Phase C.
Pre-Defined Alarm N° 9 Setting.
Over Current Unbalance Phase A.
Pre-Defined Alarm N° 10 Setting.
Over Current Unbalance Phase B.
Pre-Defined Alarm N° 11 Setting.
Over Current Unbalance Phase C.
Pre-Defined Alarm N° 12 Setting.
Over Voltage Phase A.
Pre-Defined Alarm N° 13 Setting.
Over Voltage Phase B.
Pre-Defined Alarm N° 14 Setting.
Over Voltage Phase C.
Pre-Defined Alarm N° 15 Setting.
Under Voltage Phase A.
Pre-Defined Alarm N° 16 Setting.
Under Voltage Phase B.
Pre-Defined Alarm N° 17 Setting.
Under Voltage Phase C.
Pre-Defined Alarm N° 18 Setting.
Over Voltage Unbalance Phase A.
Pre-Defined Alarm N° 19 Setting.
Over Voltage Unbalance Phase B.
Pre-Defined Alarm N° 20 Setting.
Over Voltage Unbalance Phase C.
Pre-Defined Alarm N° 21 Setting.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 75:Protection Module Me as ure m en ts
Register
Number of
Registers
88331Rx 10% In INT0..16000—P / H
88341Rx 10% In INT0..16000—P / H
88351Rx 10% In INT0..16000—P / H
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Maximum fault current (trip) recorded on
phase A since last reset.
Default value: 0x8000 (no fault recorded or
circuit breaker type not entered).
Maximum fault current (trip) recorded on
phase B since last reset.
Default value: 0x8000 (no fault recorded or
circuit breaker type not entered).
Maximum fault current (trip) recorded on
phase C since last reset.
1
1
1
Default value: 0x8000 (no fault recorded or
eeMaxFaultI[0]
eeMaxFaultI[1]
eeMaxFaultI[2]
circuit breaker type not entered).
88361Rx 10% In INT0..16000—P / H
88371Rx 1% IrINT0..32767AP / H
88381Rx 1% IrINT0..32767AP / H
88391Rx 1% IrINT0..32767AP / H
Maximum fault current (trip) recorded on
the neutral phase since last reset.
Default value: 0x8000 (no fault recorded or
circuit breaker code not supplied).
rms current on phase A expressed as a %
of the Ir long-time set point.
rms current on phase B expressed as a %
of the Ir long-time set point.
rms current on phase C expressed as a %
of the Ir long-time set point.
1
eeMaxFaultI[3]
I_RMSRelIr[0]
I_RMSRelIr[1]
I_RMSRelIr[2]
rms current on the neutral expressed as
88401Rx 1% IrINT0..32767AP / H
88411Rx 1% Ig INT0..32767AP / H
88421Rx 0.01 % Idn INT0..32767AP / H
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.
a % of the rated current In x the selected
neutral setting (x 1, x 2 or x 0.5).
"Residual" ground-fault current expressed
as a % of the Ig ground fault protection set
3
point.
Earth-leakage current expressed as a % of
the I∆N earth-leakage protection set point.
Modbus™ Communications System for Micrologic™ A, P, and H Trip Units 0613IB1201
Appendix A—Registers06/2012
Table 76:Status of the Protection Module
Register
88431Rx 1%INT0..100AP / H Battery-charge indicator.BatteryIndic
88571R——INTBitmap 16—P / H
88621R——INTBitmap 16—P / H
88631R——INTBitmap 16—P / H
8864————INTBitmap 16——
88652 Rx 0.1s
88921R———0..1—P / H
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
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
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 currentprotection 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: 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.
• 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.
Continuation of status word for overrun of
advanced protection set points.
• Bit 0: ground-fault alarm.
• Bit 1: earth-leakage alarm.
MOD
10000
——P / H Time remaining before long-time tripping.TimeLeftUntilLT_Trip
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 77:Time Stamping and Trip / Alarm Hist ory
Register
90004R——XDATE ——P / H Current date of the protection module.XtedDateTime
90103R——DATE——P / H
90703R——DATE——P / H
90733R——DATE——P / H
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Date of last reset of the maximum phase,
ground-fault and earth-leakage currents.
Date of last reset of the trip history (last ten
faults).
Date of last reset of the alarm history (last
ten alarms).
NvLastMaxI_Reset
NvLast10TripReset
NvLast10AlarmReset
Table 78:Trip History
Register
90944R1%INT0..32767 —P / H
90981R——INT0..10—P / H
90991R——INT0..9—P / H
910020R——
912020R——
914020R——
916020R——
918020R——
920020R——
922020R——
924020R——
926020R——
928020R——
For further details see “Trip / Alarm History” on page 53.
Number of
Registers
Read /
Scale Unit Format Interval AP / H DescriptionLabel
Write
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 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 history
(FIFO).
Value of the pointer for the last fault
recorded in the trip history.
The last fault recorded is in
nvLastTripQ_Entry. The next to last fault is
in nvLastTripQ_Entry-1 modulo 10.
0613IB1201 Modbus™ Communications System for Micrologic™ A, P, and H Trip Units
06/2012Appendix A—Registers
Table 80:Micrologic Configuration
Register
96001R——INT0..32767—P / H
96042R / W——ASCII0x00..0x7F —P / H
96068R / W——ASCII0x00..0x7F —P / H
96141R / W——INTBitmap 16—P / H
96151R / W——INTBitmap 16——
96161R / Wx 1VINT100..1150—P / H
96171R / Wx 1VINT100..1150—P / H
96181R / W——INT0,1, 2—P / H
Number of
Registers
Read /
Scale Unit Format IntervalAP / H DescriptionLabel
Write
Control word for the protection module. This
control word may not be user set. It is
randomly modified and must be read before
sending certain commands to the protection
module.
Short identifier of the protection module,
coded over four ASCII characters.
Default value: “set!”
Long identifier of the protection module,
coded over 16 ASCII characters.
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.
• 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 400 Hz
distribution system.
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
transformer.
Default value: 690 V.
Rated secondary voltage on the voltage
transformer.
Default value: 690 V.
• 0: no neutral CT (3-pole circuit breaker
without external CT).