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.