Micro Logic

63220-080-200
Instruction Bulletin September 2000
Using MICROLOGIC® Type A and Type P

electronic trip units in a POWERLOGIC®
system
Retain for future use
NOTICE Read these instructions carefully and look at the equipment to become
familiar with the device before trying to install, operate, service, or maintain
it. The following special messages may appear throughout this bulletin or on
the equipment to warn of potential hazards or to call attention to information
that clarifies or simplifies a procedure.
The addition of either symbol to a “Danger” or “Warning” safety label

indicates that an electrical hazard exists which will result in personal injury if
the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential personal
! injury hazards. Obey all safety messages that follow this symbol to avoid
possible injury or death.
DANGER
DANGER indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not
avoided, can result in death or serious injury.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not
avoided, can result in minor or moderate injury.
CAUTION
CAUTION, used without the safety alert symbol, indicates a potentially
hazardous situation which, if not avoided, can result in property damage.
NOTE: Provides additional information to clarify or simplify a procedure.
PLEASE NOTE Electrical equipment should be installed, operated, serviced, and maintained
only by qualified personnel. This document is not intended as an instruction
manual for untrained persons. No responsibility is assumed by Schneider
Electric for any consequences arising out of the use of this manual.
CLASS A FCC STATEMENT This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules. These limits are
designated to provide reasonable protection against harmful interference
when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if
not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in
a residential area is likely to cause harmful interference in which case the
user will be required to correct the interference at his own expense.
© 2000 Schneider Electric All Rights Reserved

Bulletin No. 63220-080-200
September 2000 Using MICROLOGIC Type A and Type P electronic trip units in a POWERLOGIC system
CONTENTS LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii

LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
ABOUT THIS DOCUMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
FEATURE SUPPORT FOR MICROLOGIC ELECTRONIC TRIP UNITS . . 1
REQUIREMENTS FOR USING MICROLOGIC
ELECTRONIC TRIP UNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
TECHNICAL SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Trip Unit System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Hardware Setup Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Setting Type A Communications Parameters . . . . . . . . . . . . . . . . . . . 6
Setting Type P Communications Parameters . . . . . . . . . . . . . . . . . . . 6
INSTALLATION AND DEVICE SETUP IN SMS . . . . . . . . . . . . . . . . . . . . . 7
Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Adding and Setting Up Trip Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
VIEWING REAL-TIME INFORMATION IN SMS . . . . . . . . . . . . . . . . . . . . . 9
USING QUANTITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
USING SMS ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Alarm Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Pre-assigned PC-based Alarms and Events . . . . . . . . . . . . . . . . . . . 11
Type P Pre-assigned On-board Alarms . . . . . . . . . . . . . . . . . . . . . . . 13
Pre-assigned Task—Resetting the Device Clock . . . . . . . . . . . . . . . 13
USING CONTROL OUTPUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
DEVICE RESETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
METERING CAPABILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Real-Time Metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Min/Max Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Power Factor Min/Max Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 16
Demand Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Demand Power and Current Calculation Methods . . . . . . . . . . . . . . 18
Predicted Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Peak Demands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Energy Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
ADVANCED TOPICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Changing the VAR and Power Factor Sign Convention . . . . . . . . . . 21
Changing VAR sign convention within SMS . . . . . . . . . . . . . . . . . . . 22
Changing VAR and PF sign conventions from the trip unit HMI . . . . 23
Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
APPENDIX A—STANDARD QUANTITIES . . . . . . . . . . . . . . . . . . . . . . . 28
APPENDIX A—STANDARD QUANTITIES . . . . . . . . . . . . . . . . . . . . . . . 28
APPENDIX B—MICROLOGIC TRIP UNIT ERROR CODES . . . . . . . . . . 35
APPENDIX C—SMS TABLE SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . 36
© 2000 Schneider Electric All Rights Reserved i

Bulletin No. 63220-080-200
Using MICROLOGIC Type A and Type P electronic trip units in a POWERLOGIC system September 2000
APPENDIX D—COMMUNICATIONS CONSIDERATIONS . . . . . . . . . . . 37

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
ii © 19xx–1999 Square D All Rights Reserved

63220-080-200 List of Figures
September 2000
LIST OF FIGURES Figure 1: Trip Unit Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 2: Communication via a PC Serial Port
(RS-485 MODBUS RTU) 4
Figure 3: Communication via a CM4000 Ethernet
Communication Card (CM4000 with ECC) 5
Figure 4: Communication via an Ethernet Gateway . . . . . . . . . . . . . . 5
Figure 5: Adding a Device Address for the
MICROLOGIC Trip Unit 8
Figure 6: Power Factor Min/Max Values . . . . . . . . . . . . . . . . . . . . . . 16
Figure 7: IEEE Sign Convention (default) . . . . . . . . . . . . . . . . . . . . . 17
Figure 8: MICROLOGIC Trip Unit Predicted Demand . . . . . . . . . . . . 19
Figure 9: IEEE Sign Convention (default) . . . . . . . . . . . . . . . . . . . . . 21
Figure 10: IEC Sign Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 11: Alternate (CM2) Sign Convention. . . . . . . . . . . . . . . . . . . . 22
Figure 12: Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 13: Activity Log illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 14: MICROLOGIC System Communication Wiring . . . . . . . . . 38
© 2000 Schneider Electric All Rights Reserved iii

List of Figures 63220-080-200
September 2000
iv © 2000 Schneider Electric All Rights Reserved

63220-080-200 List of Tables
September 2000
LIST OF TABLES Table 1: SMS Default Alarm Levels . . . . . . . . . . . . . . . . . . . . . . . . . 10

Table 2: MICROLOGIC Trip Unit Pre-assigned
PC-based Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 3: Type P Trip Unit On-board Alarms . . . . . . . . . . . . . . . . . . . 13
Table 4: MICROLOGIC Control Outputs . . . . . . . . . . . . . . . . . . . . . 13
Table 5: Micrologic Type A and Type P Device Resets . . . . . . . . . . 14
Table 6: Real-Time Readings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 7: Type P Trip Unit Demand Readings. . . . . . . . . . . . . . . . . . 17
Table 8: Type P Energy Readings . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 9: BCM/Trip Unit Values for Setting Date/Time . . . . . . . . . . . 24
Table 10: CCM Values for Setting Date/Time . . . . . . . . . . . . . . . . . . 24
Table 11: MICROLOGIC Type A Trip Unit Standard Quantities . . . . 28
Table 12: MICROLOGIC Type P Trip Unit Standard Quantities . . . . 29
Table 13: MICROLOGIC Trip Unit Error Codes in SMS. . . . . . . . . . . 35
Table 14: SMS Tables Supported by MICROLOGIC Devices . . . . . . 36
Table 15: Maximum Distances for 4-Wire Bus Topologies
(SY/MAX, MODBUS, Jbus devices) . . . . . . . . . . . . . . . . . . 37
(MODBUS, Jbus devices) . . . . . . . . . . . . . . . . . . . . . . . . . . 37
© 2000 Schneider Electric All Rights Reserved v

List of Tables 63220-080-200
September 2000
vi © 2000 Schneider Electric All Rights Reserved

63220-080-200
September 2000 Using MICROLOGIC Type A and Type P Electronic Trip Units in a POWERLOGIC System
ABOUT THIS DOCUMENT This document provides the following information:

• adding MICROLOGIC electronic trip units to your POWERLOGIC© system
• using alarms and events, control outputs, and device resets in SMS for
MICROLOGIC electronic trip units
• creating custom quantities and custom tables to view data in SMS from
MICROLOGIC electronic trip units
NOTE: This document contains specific information about the Type A and
Type P MICROLOGIC electronic trip units only.
Use this bulletin along with these other manuals:

• MICROLOGIC electronic trip unit instruction bulletin
• instruction bulletins for related devices, such as the MODBUS Breaker
Communication Module and the MODBUS Cradle Communication Module
• SMS online help file and other SMS documentation
FEATURE SUPPORT FOR MICROLOGIC This section describes the features that SMS supports for MICROLOGIC
ELECTRONIC TRIP UNITS electronic trip units and related devices. For specific instructions on using
these features in SMS, refer to the SMS online help file and the SMS
documentation.
SMS supports the following features for MICROLOGIC electronic trip units
and related devices:
• real-time data in tables, bar charts, and meters
• device resets (such as min/max, operational counter, energy, peak demands)
• automatically assigned control outputs (circuit breaker open and close)
• historical logging/trending
• automatically assigned PC-based alarms
• automatically assigned on-board device alarms (protection)
• interactive graphics (optional; GFX-1000 software required)
• pre-configured software logging templates
• standard and custom quantities
• on-board data and alarm log uploads
• device health checks and system communications test
• diagnostic register reads and writes
• on-board circuit breaker event log uploads
REQUIREMENTS FOR USING To use MICROLOGIC electronic trip units in SMS, the following requirements
MICROLOGIC ELECTRONIC TRIP UNITS must be met:
• You must have installed the SMS version 3.2 upgrade. To determine the
installed version, click About on the Help menu in the SMS client.
• If your system has MICROLOGIC electronic trip units daisy-chained to a
port of a POWERLOGIC® Ethernet Gateway, the gateway must use
Ethernet Gateway firmware version 2.5.0. or later.
• The ECM-2000 and ECM-RM are not compatible with the MICROLOGIC
trip unit system. Use the POWERLOGIC Ethernet Gateway or Series 4000
Circuit Monitor with ECC when connecting to an Ethernet network.
• If your system includes a mixed-mode daisy chain (POWERLOGIC
devices and MICROLOGIC electronic trip units on the same daisy chain),
Series 2000 Circuit Monitors on the daisy chain must have firmware
version 17.008 or later.
© 2000 Schneider Electric All Rights Reserved 1

63220-080-200
Using MICROLOGIC Type A and Type P Electronic Trip Units in a POWERLOGIC System September 2000
• If your system includes a mixed-mode daisy chain (POWERLOGIC and

MODBUS or Jbus devices), do not assign address 1 to any POWERLOGIC
device on the daisy chain; do not assign address 16 to any MODBUS or
Jbus device on the daisy chain.
• See “Appendix D—Communications Considerations” on page 37, for
2-wire and 4-wire distance and baud rate limitations.
TECHNICAL SUPPORT If you have questions about any POWERLOGIC product, contact your local
sales representative. For the address and telephone number for technical
support in your country, see the Product Registration and Technical Support
Contacts sheet; a PDF copy of this document is contained on the SMS
installation CD.
SYSTEM DESCRIPTION All of the trip units described in this bulletin provide adjustable tripping
functions for circuit breakers, including long-time and instantaneous
adjustments for overloads and short circuits. There are two types of trip units:
Type A, which provides basic trip features and ammeter measurements, and
Type P, which provides basic and advanced features and power/energy
measurements.
Type A and P trip units are self-powered by the circuit they protect, or they
can be powered by an external 24-Vdc control power supply. The external
power supply is recommended to ensure that metering and communication
continue, even if the circuit breaker is opened or tripped.
Drawout circuit breakers may include an optional cradle communication
module (CCM) that provides information about the position of the circuit
breaker in the cradle. This module automatically assigns correct
communications parameters to the circuit breaker when it’s racked into the
test or connected positions.
Trip Unit System Modules The MICROLOGIC trip unit system consists of three separate commun-
icating modules (plus a fourth optional module), described below. Each
module has an independent function. Together, they are viewed as a single
device from both the human-machine interface (HMI) and SMS. This
simplifies data reporting, recording, alarming, and general user interface.
The trip unit system includes:
• Trip Unit Protection Module (PM)—circuit protection feature of the trip
unit; the main function of the trip unit is the adjustable tripping function, so
the PM has priority over the other three modules. The PM can meter
current to 20 times the sensor plug (In). For example, for a 400 A sensor
plug, the PM can meter current up to 8,000 A.
• Trip Unit Metering Module (MM)—metering feature of the trip unit
provides true rms-metered data for energy management, and event
detection. The MM can record data up to 1.5 times the sensor plug. For
example, for a 400 A sensor plug, the MM can record data up to 600 A.
• MODBUS Breaker Communication Module (BCM)—required module for
communication between the trip unit and a MODBUS communication
network; the BCM acts as a communication gateway between the external
MODBUS network protocol and a peer-to-peer protocol used within the trip
unit system. The BCM provides circuit breaker status information—open,
closed, tripped, spring charged, spring discharged, ready to close, and
mechanism unlatched.
2 © 2000 Schneider Electric All Rights Reserved

63220-080-200
The BCM also contains:

— an alarm log of date/time stamps for recorded events
— circuit breaker maintenance information
— the means to control the circuit breaker remotely via MODBUS; this
feature requires optional communicating open/close coil(s)
The BCM requires an external 24-Vdc power supply.
NOTE: If the trip unit is externally powered, the power supply for the BCM
must be separate from the one used by the trip unit. This ensures that
electrical isolation between the trip unit and the communications network
is maintained.
An optional communicating module can be used with drawout
circuit breakers:
• Cradle Communication Module (CCM)—optional when a drawout
circuit breaker has a trip unit that communicates via MODBUS; the CCM
reads the position of the circuit breaker: connected, disconnected, or test.
The CCM automatically assigns communication parameters to a circuit
breaker when it’s racked into the test position from the disconnected
position—a feature that allows you to exchange circuit breakers between
compartments without having to change network communication
parameters. The CCM requires an external 24-Vdc power supply.
NOTE: The CCM may share the same power supply as the BCM, but it
must be separate from the one used by the trip unit.
The trip unit modules communicate using a dedicated peer-to-peer protocol

that is designed specifically for the MICROLOGIC Trip Unit system. This
protocol provides the communication link between the PM, MM, and BCM.
Figure 1 shows how the pieces of the circuit breaker and trip unit fit together.
Modbus (RS-485) Communication
Cradle Cradle
Communication
Module (optional)
Cradle Secondary Connections

Circuit Breaker Secondary Connections
Breaker
Communication
Module
IR communications
Circuit
ologic
2.0
Breaker
Micr
Trip Unit
Meter
Module
Peer-to-Peer
Protocol Protection
Module
Test Kit
Port
Figure 1: Trip Unit Architecture

63220-080-200
Network Communication MICROLOGIC trip units communicate via RS-485 MODBUS RTU protocol.
This protocol provides serial communications using either 2-wire or 4-wire
connections at speeds up to 19.2k baud. You can connect up to 32 devices
on a single daisy chain, at distances up to 10,000 feet (3,050 meters).
The trip unit connects to the POWERLOGIC system through one of three
standard communication methods:
• Serial (RS-485 MODBUS RTU), using an MCI-101 converter kit
• Ethernet (MODBUS TCP), using a CM4000 with Ethernet Communication
Card (ECC)
• Ethernet (MMS), using a POWERLOGIC Ethernet Gateway
Figures 2, 3, and 4 illustrate simple systems using each of these four
communication types. Other architectures are possible; contact your local
sales office for assistance.
For detailed information about system architecture, refer to the
POWERLOGIC System Architecture and Application Guide (order no.
3000DB0001).
POWERLOGIC
System Manager
Software
MCI-101
Converter Kit
RS-485 Daisy Chain
RS-232 MCT-485 or
MCTAS-485
Terminator
Series 4000 Series 2000

MICROLOGIC Circuit Monitor Circuit Monitor
Electronic Trip Unit Circuit Breaker or Power Meter
Figure 2: Communication via a PC Serial Port (RS-485 MODBUS RTU)

63220-080-200
POWERLOGIC
System Manager
Software
Series 4000
Circuit Monitor
with ECC
RS-485 Daisy Chain

Ethernet (Modbus TCP)
MCT-485 or
MCTAS-485
Terminator

Figure 3: Communication via a CM4000 Ethernet Communication Card (CM4000 with ECC)
POWERLOGIC
System Manager
Software
POWERLOGIC
Ethernet Gateway
Ethernet (MMS)
RS-485 Daisy Chain
MCT-485 or
MCTAS-485
Terminator

Figure 4: Communication via an Ethernet Gateway
Hardware Setup Checklist Before you add the MICROLOGIC trip unit to SMS, be sure that you have
completed all of the required hardware setup steps:
1. Be sure that all equipment shipping splits are connected.
2. Confirm that an external 24-Vdc power supply is connected to the BCM
(and CCM, if present).
3. Confirm that a second external 24-Vdc power supply is connected to the
trip unit, if it is not to be self-powered.
NOTE: If the trip unit is externally powered, the power supply for the BCM
must be separate from the one used by the trip unit. If you have a CCM,
it can share the BCM’s power supply.
4. Rack the breaker to the Test or Connected position.
5. Confirm that the trip unit has control power (the display will be powered).
6. Set the device address, baud rate, and parity from the HMI.

63220-080-200
Setting Type A Communications Parameters For the Type A trip unit, follow these steps:
a. From the default Current menu, simultaneously press and hold both
menu
and until the Communications Address menu displays. The
display will read Ad47.
b. To set the device address, press and release repeatedly until the
correct address displays. Address range = 01 through 47
(default = 47 ). On a mixed-mode daisy chain, avoid giving address 16
to MODBUS / Jbus devices, and avoid giving address 01 to
POWERLOGIC devices.
c. When the correct address displays, hold down until the display
begins to flash, then release. The baud rate menu displays
(default = b 19.2).
d. To set the baud rate, press and release repeatedly until the
correct rate displays. Baud rate range = 1,200 to 19,200.
e. When the correct baud rate displays, hold down until the display
begins to flash, then release. The parity menu displays (the default =
P E for even parity).
f. To set the parity, press and release repeatedly until the correct
parity displays. Possible entries are E or n (even or none)
g. When the correct parity displays, hold down until the display
begins to flash, then release. After several seconds, the trip unit
automatically returns to the Current menu.
Setting Type P Communications Parameters For the Type P trip unit, follow these steps:
a. From the default Main menu (providing real-time current display),
press ; the Setup menu displays.
b. Press or to select Com Setup. Press ( ); the Commun-
ication Setup menu displays with Com. parameters selected.
c. Press to open the Com. parameters window. The MODBUS Com
window displays with the Address selected (default = 47 ).
d. Press to highlight the address. Press or to change the
address to the one that the trip unit will use. Press to enter the
change. On a mixed-mode daisy chain, avoid giving address 16 to
MODBUS / Jbus devices, and avoid giving address 01 to
POWERLOGIC devices.
e. Press or to select Baud Rate (default = 19.2k).
f. Press to highlight the baud rate.
g. Press or to change the baud rate to the one that the trip
system modules will use.
h. Press to enter the change.
i. Press to select Parity (default = Even).
j. Press to highlight the parity.
k. Press or to change the parity to the one that the trip unit
will use (even or none).
l. Press to enter the change.
m. Press to leave the menu. The prompt “Do you want to save new
settings?” displays.
n. Press to select Yes. Press to save all of the changes that
you’ve made.
o. Press to return to the default Main menu.
7. Press the Address sync push button on the CCM (adjacent to the green
LED marked “Comm”). This causes the CCM to read the communications
setup (for this circuit breaker location) from the BCM.
8. Connect the trip system (trip unit, CCM, BCM) to the MODBUS network.

63220-080-200
9. Connect the MODBUS network to a PC workstation via Ethernet

(Ethernet Gateway connection or CM4000 with ECC) or RS-485 (serial
connection).
10. Test the communications.
INSTALLATION AND DEVICE SETUP If you encounter problems with any instructions in this section, refer to
IN SMS “Troubleshooting” on page 26 for troubleshooting help.
Installing the Software When you nstall the SMS V 3.2 upgrade, you also install the MICROLOGIC
device type software. To do this, follow the instructions in the System
Manager Software Setup Guide.
Once SMS V 3.2 is installed, you’ll need to add and set up the MICROLOGIC
trip units. See “Adding and Setting Up Trip Units,” below.
If you have any questions, contact your local sales representative. For the
address and telephone number for technical support in your country, see the
Product Registration and Technical Support Contacts sheet; a PDF copy of
this document is contained on the SMS installation CD.
Adding and Setting Up Trip Units After the software is installed, you’ll need to add and set up the MICROLOGIC
trip unit(s) in your SMS system.Iinstructions for adding and setting up devices
are in the SMS online help file. See the Quick Starts for step-by-step
instructions, which are organized by communication connection type.
The tasks you’ll need to complete are listed below.
1. Add and set up a serial connection in SMS.
2. Add the device.
3. Add the device address (sometimes called device route). This address
must match the address you assigned to the device at the HMI. This step
requires that you plan your addressing in advance.
When you add a MODBUS device in SMS, you add one address or route,
which SMS uses to communicate with that device. For the MICROLOGIC
trip unit, you add the address that you entered at the trip unit HMI; SMS
creates the additional device addresses that are required for the rest of
the trip unit system:
• BCM (breaker communication module)—the BCM address is set at the
trip unit HMI
• PM (trip unit protection module)—the system adds 100 to the BCM
address
• MM (trip unit metering module)—the system adds 200 to the BCM
address
• CCM (cradle communication module)—installed only if you are using a
drawout circuit breaker : the system adds 50 to the BCM address
NOTE: When entering a MICROLOGIC device in SMS, using an Ethernet
Gateway connection, the device ID should match the address of the BCM
(the address entered at the trip unit HMI).
4. After you add the address, SMS displays a dialog asking you whether you
have a CCM in your trip unit system. If the trip unit system includes a
CCM, check the box.

63220-080-200
Figure 5 illustrates how these addresses are determined, when the trip unit
is installed in a drawout circuit breaker.
.
Daisy Chain Connecting Devices POWERLOGIC

System Manager
Address Software
(51) CCM
POWERLOGIC
(1) BCM Ethernet Gateway
(101) PM
(201) MM
Circuit Monitors and/o
Other Devices:
In this example, do no
Circuit Circuit Breaker/Trip Unit:
Circuit assign address
Breaker Address 1 (51, 101, 201)
number 51, 101, or 201
Breaker Cradle
to any remaining devic
In this example, you might give the trip unit address #1. This step assigns address #1 to the
breaker communication module (BCM). SMS will automatically assign these addresses for the trip uni
#51 to the crade communication module (CCM)
#101 to the trip unit protection module (PM)
#201 to the trip unit meter module (MM)
You only assign the first address to the Ethernet Gateway; do not assign the remaining trip unit m
Figure 5: Adding a Device Address for the MICROLOGIC Trip Unit
When adding the MICROLOGIC trip unit to an SMS system, you must plan for
the additional addresses of the trip unit system. For example, when com-
municating via an Ethernet Gateway, be sure that other devices are not
assigned an address that will be automatically assigned to part of the trip
unit system.
The benefit of having the four addresses is that SMS polls the individual parts
of the trip unit system separately. Should an event occur to one part of the
trip unit system, the remaining parts will continue to function and deliver data
to SMS. For example, when the circuit breaker is racked out, the BCM and
trip unit modules cannot communicate, but the CCM continues to provide
circuit breaker position information.
The multiple addresses also help you when you’re troubleshooting problems
in the trip unit system.

63220-080-200
VIEWING REAL-TIME INFORMATION Once you have added the trip unit to your system, you can view real-time
IN SMS data in SMS as you would for any other POWERLOGIC system compatible
device. See the SMS online help file for information about displaying bar
charts, meters, tables, and function tables for devices within SMS.
USING QUANTITIES Standard Quantities

For each POWERLOGIC device type, including the MICROLOGIC trip unit,
SMS maintains a database of standard quantities available in the device.
When you define a logging template or display a quick table for a trip unit,
SMS knows the quantities that are available for that device type.
Custom Quantities
In addition to these standard quantities, SMS gives you the option of setting
up additional quantities, called custom quantities. To use these custom
quantities, you must identify them by specifying their location (register
number). When you define custom quantities and assign them to the
device type, you are adding to the database of quantities available for that
device type.
For instructions on adding and assigning custom quantities, see the SMS
online help file.
USING SMS ALARMS Global alarms are automatically assigned when the trip unit is added to SMS.
However, you can add custom alarms to SMS. The process of setting up
alarms includes these steps:
• creating global analog or digital functions that are to be used to monitor
power system conditions. When you define an analog or digital function,
you select a quantity, then define the conditions (or setpoints) under which
SMS generates the alarm. You also determine the severity of the alarm,
for example, whether the alarm will annunciate (give visual or audible
indication from within SMS) and whether a user must acknowledge it.
• assigning the function to a specific device within the SMS system.
Because you might not want the same alarms for each trip unit, you can
specify the alarms for each one.
For complete instructions on adding global functions and assigning them to

a device, see the SMS online help file.

63220-080-200
Alarm Levels SMS uses a feature called Alarm Severity to determine the level of an alarm
and the information that the alarm provides. There are ten levels of alarm,
0 through 9. Although MICROLOGIC alarms and levels are pre-assigned,
you can change the level (severity) of any alarm. However, keep in mind
that changes to a level will change the amount of information that you will
receive when the alarm becomes active.The following table lists the default
alarm severity levels and their characteristics:
Table 1: SMS Default Alarm Levels

Severity Acknowledge Password Alarm
Audible1 Visible2
Level Required3 Required4 Log5
0 X X X X X
1 X X X X X
2 X X X X X
3 X X X X
4 X X X X
5 X X X
6 X X
7 X X
8 X X
9 X
1. Alarm will sound when it becomes active.
2. Alarm will make the Active Alarms dialog pop up when it becomes active.
3. Operator must acknowledge the alarm before it will disappear.
4. Alarm is password-protected: operator must enter a password (assigned
when adding the user ID) to acknowledge the alarm.
5. Alarm information displays in the SMS Alarm Log.

63220-080-200
Pre-assigned PC-based Alarms and Events The MICROLOGIC trip unit includes automatically assigned alarms.
However, you can unassign or modify any pre-assigned alarm for a specific
device. Table 2 describes these pre-assigned alarms. Unless otherwise
indicated in the Remarks column, all alarms operate for both Type A and
Type P trip units.
Table 2: MICROLOGIC Trip Unit Pre-assigned PC-based Alarms

Digital Function Pickup Text / Dropout Text / Polling
Module2 Remarks
Name1 Alarm Level3 Alarm Level3 Interval
In Progress Not Picked Up Type P trip units only. Long delay pickup setpoint is exceeded and trip is
Long Delay Pickup PM 15 sec.
(level 2) (no alarm) imminent if current is not reduced.
Protection Settings Detected Not Detected
PM 300 sec. Alarm appears when any trip unit protection setpoint is changed.
Change (level 4) (no alarm)
Rating/Sensor Plug Detected Not Detected Alarm appears when the rating plug type or sensor plug current rating
PM 300 sec.
Changeout (level 4) (no alarm) changes from the last time SMS communicated with the breaker.
Trip Unit Detected Not Detected Alarm appears when the PM serial number changes from the last time SMS
PM 300 sec.
Changeout (level 4) (no alarm) communicated with the breaker.
Yes No Type P trip units only. Indicates trip unit door is open and basic protection
Trip Unit Door Open PM 300 sec.
(level 5) (no alarm) settings switches are exposed.
Detected Not Detected Alarm appears when the BCM serial number changes from the last time
Breaker Changeout BCM 300 sec.
(level 4) (no alarm) SMS communicated with the breaker.
Closed Open
Breaker Status BCM N/A4
(no alarm) (no alarm)
Loss of Logging
Detected Not Detected Indicates loss of internal communication to the trip unit. Could be caused by
and Alarming BCM 60 sec.
(level 1) (no alarm) trip unit being removed or by loss of trip unit auxiliary power.
Capability
Yes No
Ready to Close BCM N/A4
If Remote Closing is disabled, an attempt to close the breaker in SMS will
Remote Closing Yes No
BCM N/A4 result in error code 4500. See Appendix B—MICROLOGIC Trip Unit Error
Enabled (no alarm) (no alarm)
Codes for information.
Remote control is enabled/disabled at the trip unit HMI by placing the unit in
Auto / Manual.
Remote Control Auto Manual
BCM N/A4 When remote control is disabled, the SMS pre-defined control outputs
(enable/disable remote closing and opening, and close / open the breaker)
will not operate.
If Remote Opening is disabled, an attempt to open the breaker in SMS will
Remote Opening Yes No
BCM N/A4 result in error code 4500. See Appendix B—MICROLOGIC Trip Unit Error
Codes for information.
Yes No
Spring Charged BCM N/A4 Indicates status of motor-charged closing springs.
Time Loss—
Detected Not Detected Indicates that the BCM lost power. An SMS clock reset task automatically
Breaker Comms BCM 60 sec.
(level 9) (no alarm) performs the reset with no user action required.
Module
Trip Unit Internal Detected Not Detected Indicates loss of internal communication to the trip unit. Could be caused by
BCM 60 sec.
Comms Failure (level 1) (no alarm) trip unit being removed or by loss of trip unit auxiliary power.
Trip Unit Status Fault Tripped Not Tripped Protective trip alarm. This alarm remains until the trip unit is reset. If the trip
BCM 15 sec.
(SDE) (level 1) (no alarm) unit is Type P, onboard alarms also appear with the type of trip.
Only for models with CCM.
Breaker Between True False
CCM 60 sec. Indicates that the circuit breaker is between Connected and Test or between
Positions (level 9) (no alarm)
Test and Disconnected positions.
Breaker Connected True False Only for models with a CCM.
CCM 60 sec.
(CE) (no alarm) (no alarm) Indicates that the circuit breaker is in Connected position.
Breaker True False Only for models with CCM.
CCM 60 sec.
Disconnected (CD) (level 9) (no alarm) Indicates that the circuit breaker is in Disconnected position.
Breaker in Test True False Only for models with a CCM.
CCM 60 sec.
(CT) (level 9) (no alarm) Indicates that the circuit breaker is in Test position.
1. This name displays in the SMS Activity Log and Active Alarm log.
2. The module that generates the alarm; BCM = breaker communication module, CCM = cradle communication module, PM = protection module
3. Although you can change the level for an alarm, keep in mind that each alarm level has specific characteristics: For example, alarm level 9 displays an entry in
the SMS Activity Log, but does not display in the Active Alarms Log. For a detailed discussion of alarm levels, see “Pre-assigned PC-based Alarms and Events”
on page 11.
4. These functions are polled only when they are included in a file such as a real-time table. The polling is updated according to the interval chosen for that display.

63220-080-200
Table 2: MICROLOGIC Trip Unit Pre-assigned PC-based Alarms

Digital Function Pickup Text / Dropout Text / Polling
Module2 Remarks
Name1 Alarm Level3 Alarm Level3 Interval
Only for models with a CCM.
Time Loss—Cradle Detected Not Detected
CCM 60 sec. Indicates that the CCM lost power. An SMS clock reset task automatically
Comms Module (level 9) (no alarm)
performs the reset with no user action required.
1. This name displays in the SMS Activity Log and Active Alarm log.
2. The module that generates the alarm; BCM = breaker communication module, CCM = cradle communication module, PM = protection module
3. Although you can change the level for an alarm, keep in mind that each alarm level has specific characteristics: For example, alarm level 9 displays an entry in
the SMS Activity Log, but does not display in the Active Alarms Log. For a detailed discussion of alarm levels, see “Pre-assigned PC-based Alarms and Events”
on page 11.
4. These functions are polled only when they are included in a file such as a real-time table. The polling is updated according to the interval chosen for that display.

63220-080-200
Type P Pre-assigned On-board Alarms Table 3 lists on-board alarms for Type P trip units. To enable them and to
enter pickup and dropout setpoints, you must use the HMI. See the trip unit
instruction bulletin for instructions.
The settings and present status of each alarm can be viewed in the
MICROLOGIC Protection Settings table. See “Appendix C—SMS Table
Support” on page 36 for a list of tables included in SMS. See the SMS online
file for help viewing tables.
Table 3: Type P Trip Unit On-board Alarms
Function Name Alarm Level

Long Time Trip (Ir) 2
Short Time Trip (Isd) 2
Instantaneous Trip (Ii) 2
Residual Ground Fault (Ig) 2
Ground Fault - Residual Alarm 4
Current Unbalance 4
Over Current Demand Phase A 4
Over Current Demand Phase B 4
Over Current Demand Phase C 4
Over Current Demand Neutral 4
Under Voltage 2
Over Voltage 4
Voltage Unbalance 4
Reverse Power 4
Under Frequency 4
Over Frequency 4
Phase Rotation 4
Current Load Shedding 4
Power Load Shedding 4
Pre-assigned Task—Resetting the The clock reset is the only pre-assigned task for a device reset. For more
Device Clock information about the automatic device clock reset, see “Device Resets” on
page 14. For instructions on using tasks to perform resets, see the SMS
online help file.
USING CONTROL OUTPUTS SMS uses control outputs to provide remote manual control of devices. For
example, you can use SMS as an interface to open or close a circuit breaker
via a serial, MODBUS, or Ethernet communications network.
Table 4 lists the predefined MICROLOGIC control outputs used in SMS.
Table 4: MICROLOGIC Control Outputs
Control Target Device

Circuit Breaker (close/open) BCM
Open Permissive (enable/disable) BCM
Close Permissive (enable/disable) BCM
Remote control (Auto/Manual) must be enabled from the trip unit HMI for any
output to be controlled from SMS.

63220-080-200
However, if remote control is enabled, but the SMS open/close feature is

disabled for the control you are trying to operate, that control output will not
operate. You will see this message:
“Control Output Failed!” Communication Error 4500 occurred while
sending the control to the target device. Visual inspection of the
device is recommneded.”
The solution is to enable the desired control from the SMS control
output feature.
If remote control (Auto/Manual) is disabled from the trip unit HMI, the attempt
to operate the control from SMS will not work. You will see this message:
“Control Output Failed!”
The solution is to enable the remote control from the trip unit HMI.
DEVICE RESETS The device reset feature allows you to reset certain data entries for a device.
Use this feature to reset data for a device or group of devices. Reset options
vary, depending on the device type. You can perform a reset manually or as
a scheduled task. Resets are logged in the SMS Activity Log.
Table 5 lists the resets that SMS supports for the Type A and Type P trip
units:
Table 5: Micrologic Type A and Type P Device Resets
Device Reset Type A Type P

Breaker Event Log X X
Device Date/Time1 X x
Min/Max X X
Accumulated Energy X
Trip Unit Alarm Log X
Peak Demand Current X
Peak Demand Power X
Set Alternate (CM2) PF/Var Sign Convention X
Set IEC PF/Var Sign Convention X
Set IEEE PF/Var Sign Convention X
Operations Counter X X
1. Device date/time is reset in one of two ways
• At 12:30 a.m., a scheduled task in SMS resets the trip unit’s time.
• When the trip unit loses and regains power, a pre-assigned
PC-based alarm performs the reset with no user action required.

63220-080-200
METERING CAPABILITIES The MICROLOGIC Trip Unit system (Types A and P) provides real-time
readings, demand readings, and energy readings. Each reading type is
discussed fully in the following paragraphs.
Real-Time Metering All MICROLOGIC trip units measure currents and report rms values for all
three phases, including neutral/ground current. In addition to these values,
the Type P trip unit measures voltage and calculates power factor, real
power, reactive power, and more. Table 6 lists the real-time readings and
shows which parameters are available.
Table 6: Real-Time Readings

Current Range
Per-Phase 0 to 32,767 A (or 0–100% capacity)
Neutral 0 to 32,767 A (or 0–100% capacity)
Ground 0 to 32,767 A (or 0–100% capacity)
Max of 3 Phases and Neutral 0 to 32,767 A
3-Phase Average (Type P only) 0 to 32,767 A
Current Unbalance (Type P only) –100% to +100%
Voltage (Type P only) Range
Line–to–Line, per-phase 0 to 1,200 V
3-Phase Average, Line-to-Line 0 to 1,200 V
Line-to-Neutral, per-phase 0 to 1,200 V
3-Phase Average, Line-to-Neutral 0 to 1,200 V
Voltage Unbalance –100% to +100%
Real Power (Type P only) Range
3-Phase Total 0 to +/–32,767 kW
Per-Phase 0 to +/–32,767 kW
Reactive Power (Type P only) Range
3-Phase Total 0 to +/–32,767 kVAR
Per-Phase 0 to +/–32,767 kVAR
Apparent Power (Type P only) Range
3-Phase Total 0 to 32,767 kVA
Power Factor—True (Type P only) Range
3-Phase Total –1.00 to +1.00
Per Phase –1.00 to +1.00
Frequency (Type P only) Range
System Frequency 50-60 Hz or 400 Hz
Min/Max Values The trip unit stores minimum and maximum (min/max) values for all real-time
readings in nonvolatile memory.
Using SMS, you can:
• view all min/max values
• reset all min/max values
For instructions on using SMS software to view, save, and reset min/max
data, refer to the SMS online help file.

63220-080-200
Power Factor Min/Max Conventions Running min/max values, with the exception of power factor, are arithmetic
minimums and maximums. For example, the minimum phase A–B voltage is
simply the lowest value in the range 0 to 1200V that has occurred since the
min/max values were last reset. In contrast, because a power factor meter’s
midpoint is unity (illustrated in Figure 6), power factor min/max values are not
true arithmetic minimums and maximums. Instead, the minimum value
represents the measurement closest to –0 (most lagging) on a continuous
scale of –0 to 1.00 to +0. The maximum value is the measurement closest to
+0 (most leading) on the same scale.
See “Advanced Topics” on page 21 for information about changing sign
conventions.
Figure 6 shows the power factor min/max values in a typical environment,
assuming a positive power flow. In Figure 6, the minimum power factor is –
0.70 (lagging) and the maximum is +0.80 (leading). It is important to note that
the maximum power factor need not be leading. For example, if the power
factor values ranged from –0.75 (lagging) to –0.95 (lagging), then the
minimum power factor would be –0.75 (lagging) and the maximum power
factor would be –0.95 (lagging). Likewise, if the power factor ranged from
+0.90 to +0.95, the minimum would be +0.95 (leading) and the maximum
would be +0.90 (leading).
Figure 7 shows a sign convention chart for the default IEEE sign convention.
Minimum Maximum
Power Factor Power Factor
Range of Power
–0.7 (lagging) 0.8 (leading)
Factor Values
Unity
1.00
.8 .8
.6 .6
Lag Lead
(–) (+)
.4 .4
.2 .2
-0 +0
Figure 6: Power Factor Min/Max Values

63220-080-200
Reactive
Power
Quadrant Quadrant
2 1
Watts Negative (–) Watts Positive (+)

VARs Positive (+) VARs Positive (+)
PF Leading (+) PF Lagging (–)
Reverse Power Flow Normal Power Flow

Real
Power

VARs Negative (–) VARs Negative (–)
PF Lagging (–) PF Leading (+)
Quadrant Quadrant
3 4
Figure 7: IEEE Sign Convention (default)
Demand Readings The Type P trip unit provides a variety of demand readings, including
coincident readings and predicted demands. Table 7 lists the available
demand readings.
Table 7: Type P Trip Unit Demand Readings

Demand Current
Present, Per-Phase and Neutral 0 to 32,767 A
Peak, Per-Phase and Neutral 0 to 32,767 A
Average Power Factor (True), 3-Phase Total
Present -1.00 to +1.00
Coincident with kW Peak -1.00 to +1.00
Coincident with kVAR Peak -1.00 to +1.00
Coincident with kVA Peak -1.00 to +1.00
Demand Real Power, 3-Phase Total
Present 0 to 32,767 kW
Predicted 0 to 32,767 kW
Peak 0 to 32,767 kW
Coincident kVAR 0 to 32,767 kVAR
Coincident kVA 0 to 32,767 kVA
Demand Reactive Power, 3-Phase Total
Present 0 to 32,767 kVAR
Predicted 0 to 32,767 kVAR
Peak 0 to 32,767 kVAR
Coincident kW 0 to 32,767 kW
Coincident kVA 0 to 32,767 kVA
Demand Apparent Power, 3-Phase Total
Present 0 to 32,767 kVA
Predicted 0 to 32,767 kVA
Peak 0 to 32,767 kVA
Coincident kW 0 to 32,767 kW
Coincident kVAR 0 to 32,767 kVAR

63220-080-200
Demand Power and Current To be compatible with electric utility billing practices, the Type P trip unit
Calculation Methods provides the following types of demand power calculations:
• sliding demand
• block interval demand
A brief description of each demand method follows:

Sliding Demand (default)
The sliding demand method calculates the demand based on a running
average value and updates its demand calculation every 15 seconds on a
sliding window basis. You can select the demand interval from 5 to 60
minutes in 1-minute increments.
Block Interval Demand

The block interval demand mode supports a standard block interval
calculation for compatibility with electric utility electronic demand registers.
In standard block interval mode, you can select a demand interval from 5 to
60 minutes in 1-minute increments. The demand calculation is performed at
the end of each interval. The present demand value displayed by the trip unit
is the value for the last completed demand interval.
The demand calculation method and interval are set up from the HMI. To
change the demand method or interval, follow these steps:
Changing the Demand Power Method or Interval

1. From the default Main menu of a Type P trip unit, press ; the Setup
menu displays.
2. Press or to select Metering Setup.
3. Press ; the Metering Setup menu displays.
4. Press or to select Power Demand.
5. Press ; the Power Demand window displays with the window type
selected (default = Sliding Window).
6. To change the window type, press to highlight the type.
7. Press or to change the type; the two options are Block and
Sliding.
8. Press to enter the change.
9. Press to select the interval time.
10. Press to highlight the interval time (default = 15 minutes).
11. To change the default, press or until the correct interval
displays. The interval range is 5–60 minutes.
12. Press then press to set the desired interval. The prompt “Do you
want to save new settings?” displays.
13. Press to select Yes. Press to save the change that you’ve
made.
14. Press to return to the default Main menu.
Changing the Demand Current Method or Interval

1. From the default Main menu of a Type P trip unit, press ( ); the Setup
menu displays.
4. Press or to select Current Demand.

63220-080-200
5. Press to display the current demand window. The default method

(Sliding Window) cannot be changed. Demand interval is selected.
6. Press to highlight the interval time (default = 5 minutes).
7. To change the default, press or until the correct interval
displays. The interval range is 5–60 minutes.
8. Press then press to set the desired interval. The prompt “Do you
want to save new settings?” displays.
made.
Predicted Demand The Type P trip unit calculates predicted demand for kW, kVAR, and kVA.
The predicted demand is calculated by extrapolating the present value of
demand to the end of the interval. This calculation method responds very
quickly and provides an excellent approximation of the actual demand at the
end of the interval. The predicted demand values are updated every 15
seconds.
Figure 8 shows how a change in load can affect predicted demand.
Beginning
of interval
15-minute interval
Predicted demand if load is
Demand for added during interval,
Partial Interval
last completed predicted demand increases
Demand
interval to reflect increased demand
Predicted demand if no load

is added
Time
1:00 1:06 1:15
Change in Load
Predicted demand is updated every second until the interval is complete.
Figure 8: MICROLOGIC Trip Unit Predicted Demand
Peak Demands The Type P trip unit maintains, in nonvolatile memory, a running maximum—
called peak demand—for each demand current and demand power value. It
also stores the date and time of each peak demand. In addition to the peak
demand, the trip unit stores the coinciding average (demand) 3-phase power
factor. The average 3-phase power factor is defined as “demand kW /
demand kVA” for the demand interval.
Peak demand values can be reset over the communications link using SMS.
Energy Readings The Type P trip unit provides total accumulated energy values for kWh,
kVARh, and kVAh. The trip unit also calculates and stores in nonvolatile
memory accumulated values for real energy (kWh) and reactive energy
(kVARh) both into and out of the load. These values can be displayed on the
trip unit, or read over the communications link.
The Type P trip unit can accumulate energy values in one of two modes:
signed or absolute (unsigned). In signed mode, the trip unit considers the
direction of power flow, allowing the accumulated energy magnitude to both

63220-080-200
increase and decrease. In absolute mode, the trip unit accumulates energy
as positive, regardless of the direction of power flow; in other words, the
energy value increases, even during reverse power flow. The default
accumulation mode is absolute.

63220-080-200
Table 8 lists available accumulated energy values.
Table 8: Type P Energy Readings
Energy Type Accumulated Energy Values

Real (Signed/Absolute) 0 to 9,999,999,999,999,999 kWh
Reactive (Signed/Absolute) 0 to 9,999,999,999,999,999 kVARh
Apparent (Absolute) 0 to 9,999,999,999,999,999 kVAh
Real (In) 0 to 9,999,999,999,999,999 kWh
Real (Out) 0 to 9,999,999,999,999,999 kWh
Reactive (In) 0 to 9,999,999,999,999,999 kVARh
Reactive (Out) 0 to 9,999,999,999,999,999 kVARh
ADVANCED TOPICS This section includes discussion of these advanced topics:

• VAR sign and power factor sign conventions
• time synchronization
Changing the VAR and Power Factor The trip unit offers two reactive power (VAR) sign conventions and three
Sign Convention power factor sign conventions. The trip unit allows three combinations of the
VAR sign convention and the power factor (PF) sign convention.
The IEEE sign convention, shown in Figure 9, is achieved by combining the

IEEE VAR sign convention with the IEEE power factor sign convention. The
IEEE sign convention is the default.
Reactive
Power
Quadrant Quadrant
2 1


Real
Power

Quadrant Quadrant
3 4
Figure 9: IEEE Sign Convention (default)

63220-080-200
The IEC sign convention, shown in Figure 10, is achieved by combining the
IEEE VAR sign convention with the IEC power factor sign convention.
Reactive
Power
Quadrant Quadrant
2 1

PF Leading (–) PF Lagging (+)

Real
Power

Quadrant Quadrant
3 4
Figure 10: IEC Sign Convention
The third sign convention is identified as Alternate (CM2). The Alternate sign
convention allows the MICROLOGIC trip unit reactive power and power factor
data to match existing POWERLOGIC circuit monitors and power meters.
The Alternate sign convention shown in Figure 11, is achieved by combining

the Alternate (CM2) VAR sign convention with the IEEE power factor
sign convention.
Quadrant Quadrant
2 1


Real
Power

Quadrant Quadrant
3 4
Reactive
Power
Figure 11: Alternate (CM2) Sign Convention
Changing VAR sign convention within SMS

To change the VAR sign convention within SMS, use the Reset feature
(Control > Resets). Select the MICROLOGIC device type, then select the
reset for the desired sign convention. For a list of MICROLOGIC device
resets within SMS, see Table 5 on page 14.

63220-080-200
Changing VAR and PF sign conventions from the trip unit HMI
For the Type P trip unit, you can change the VAR/PF sign conventions from
the trip unit HMI. Follow these instructions:
1. From the default Main menu of a Type P trip unit, press ( ); the Setup
menu displays.
4. Press or to select Sign convention.
5. Press to display the Sign Convention window (default = IEEE).
6. To change the default, press or until the correct convention
displays. Selections are IEEE, IEC, and Alternate (CM2).
7. Press then press to set the desired convention. The prompt “Do
you want to save new settings?” displays.
made.
Time Synchronization The MICROLOGIC trip unit system modules rely on external sources to set
and synchronize their internal clocks.
If either the SMS Alarm Log or the Trip Unit Alarm Log displays a date that is
25 years earlier than the correct date, the trip unit has lost, and then
regained, power. You do not need to take any action; SMS will reset the
date/time the next time it communicates with the trip unit.
Bit 15 of the Month/Day register for the trip unit (register 9001), BCM (register
679), and CCM (register 679) indicates that the date/time has not been set in
the module since it was last powered. To clear this bit, use one of the
following methods:
BCM and Trip Unit:
Use the MODBUS network (SMS Resets or a MODBUS master device) or the
trip unit HMI.
CCM:
Use the MODBUS network (SMS Resets or a MODBUS master device).
Instructions for using each method follow.
Setting Date/Time via SMS Resets

1. From the SMS Main menu, click Control > Resets. The Reset Device
Data dialog box displays.
2. At the Device Types field, click the type of device you want to reset
(MicroLogic Type A or MicroLogic Type P). The resets for that device type
are listed in the Resets Available box at the bottom left of the dialog box.
3. At the Devices Available field, select the specific device(s) that you want
to reset. To select a device, click the device name, then click >; or drag
and drop the device in the Devices Chosen box.
4. At the Resets Available field, select the reset(s) you want to include. To
select a reset, click the reset name, then click >; or drag and drop the
reset in the Resets Chosen box.
5. Click Reset. The message Reset Operation(s) passed displays. Click
Close to return to the SMS main window.
See Table 5 on page 14 for a list of resets that you can perform for
MICROLOGIC trip units.

63220-080-200
Setting Date/Time via MODBUS Master Device

Write the following values to the BCM and trip unit via the MODBUS network
(BCM address is set through and shown on the trip unit HMI).
Table 9: BCM/Trip Unit Values for Setting Date/Time

Register Data Description
7700 61541 (0xF065) Command to set date/time
7701 5 Number of parameters included with the command
7702 4 Trip system module ID (BCM = 4, PM = 2, MM = 8)
7703 MM:DD MM = month (1-12)1, DD = day (1-31)2
7704 YY:HH YY = year (0-199)1, HH = hour (0-23)2
7705 MM:SS MM = minute (0-59)1, SS = second (0-59)2
1. high byte 2. low byte
Write the following values to the CCM via the MODBUS network (CCM
address is equal to the BCM address plus 50; example: BCM address = 1,
CCM address = 51).
Table 10: CCM Values for Setting Date/Time

Register Data Description
7700 61541 (0xF065) Command to set date/time
7703 MM:DD MM = month (1-12)1, DD = day (1-31)2
7704 YY:HH YY = year (0-199)1, HH = hour (0-23)2
7705 MM:SS MM = minute (0-59)1, SS = second (0-59)2
1. high byte 2. low byte
Changing the Date/Time via the HMI

To set the date/time in the BCM and Type P trip unit via the trip unit HMI,
follow
these steps.
1. From the default Main menu of a Type P trip unit, press ); the Setup
menu displays.
2. Press or to select Micrologic setup.
3. Press ; the Micrologic setup menu displays.
4. Press or to select Date/hour.
5. Press ; the Date/Hour dialog displays.
6. Press or to select the Date.
7. Press to highlight the Month.
8. Press or to select the two-digit month (01–12).
9. Press to highlight the Date field.
10. Press or to select the two-digit date (01–31).
11. Press to highlight the Year field.
12. Press or to select the four-digit year.
13. Press to select the Hour.
14. Press to highlight the Hour field.
15. Press or to select the two-digit hour (01–24).
16. Press to highlight the Minute field.
17. Press or to select the two-digit minute (01–60).
18. Press to highlight the Second field.

63220-080-200
19. Press or to select the two-digit seconds (01–60).

20. When you’ve finished setting the date/hour, press twice to return to
the default Main menu.

63220-080-200
TROUBLESHOOTING If the trip unit is not communicating with SMS, follow the list below to ensure
that the equipment is properly installed and configured.
1. If the trip unit and BCM are communicating in SMS, but the CCM is not
communicating, it’s likely that you didn’t press the Address sync push
button when you set up the hardware. See “Hardware Setup Checklist”
on page 5 for complete instructions.
2. View the position indicator on the front panel of the circuit breaker to
ensure that the circuit breaker is in the test or connected position.
3. Referring to the drawings included with the equipment, confirm that all
equipment shipping splits are connected.
4. Confirm that 24-Vdc power sources are connected for the CCM, BCM,
and trip unit. Follow these procedures:
• View the LEDs on the CCM (see steps 7 and 8 in this list for an
explanation of LED combinations)
• measure the voltage on the “Comms” secondary on terminals E1 and E2
• examine the trip unit display
5. Examine the communications cabling at the CCM and circuit breaker
secondaries; make sure the communications wires are correctly
connected (see Figure 14 on page 38 for wire color coding).
6. Check the address, baud rate, and parity of the trip unit at the HMI, in
SMS, and, if applicable, in the Ethernet Gateway. Make sure that you’ve
assigned the same settings in each place.
7. View the LEDs on the CCM to be sure there is MODBUS activity on the
network and at the device. The options are:
No LEDs:
24-Vdc control power not present.
One solid green LED:
24-Vdc control power is present, but there is no traffic on the MODBUS network.
One solid red LED:
CCM has failed its self test.
One solid green LED with short voids:
CCM is receiving good MODBUS packets.
One solid green LED with short red flashes:
CCM is receiving MODBUS packets with errors.
Red and green LEDs flash intermittently:
In a mixed-mode system (POWERLOGIC and MODBUS / Jbus devices), this
is normal.
8. After pressing the “Address sync” push button on the CCM, or after
racking a circuit breaker into Test position, the red and green LEDs will
blink simultaneously while the system attempts to synchronize
communications parameters. This could take up to ten seconds.
Then, the LEDs will indicate the success or failure of the process.
Possible status indications are:
Three flashes of the green LED, followed by a quick flash of the red LED:
Communications information was successfully transferred.
Three flashes of the red LED:
An error occurred in transferring communications information.
9. When a control output does not operate, consider the following causes:
• non-communicating shunt trip and close coils
• remote control is not enabled (must be done from the HMI)
• the circuit breaker is tripped
• when attempting to close, remote close is not enabled
• when attempting to open, remote open is not enabled

63220-080-200
10. If you see error 4608 in the SMS Alarm Log, one or more sub-devices are
not communicating.
The alarm information in the Alarm Log displays the trip unit device and
the words “Communication Loss.”
the SMS Activity Log displays in the following manner:
Figure 12: Activity Log
In this example, the error 401 entries show that communication was lost
with the trip unit and the BCM.

63220-080-200
APPENDIX A—STANDARD QUANTITIES This is an abbreviated list of standard quantities that you can use in DDE for
spreadsheets and drawings, for setting up reports, and for creating custom
tables. For a complete list of registers, contact your local sales represen-
tative. The quantities are listed in alphabetical order according to the SMS
topic name. Table 11 lists the quantities for the Type A trip unit. Table 12 on
page 29 lists the quantities for the Type P trip unit.
Table 11: MICROLOGIC Type A Trip Unit Standard Quantities

Number of
SMS Topic Name User Description Register1 Module1 Units1 Scale/Bitmask1
Registers1
810DBrkrStatus Breaker Status 1 661 BCM Bit 0; ON = closed, OFF = open
810DBrkrTripStat Breaker Trip Unit Status 1 661 BCM Bit 2 ON = tripped, OFF = not tripped
BCM_SN BCM Serial Number 4 516 BCM ASCII text
Bit 8 = disconnected
BkrPos Breaker Position 1 661 CCM Bit 9 = connected
Bit 10 = test position
DT_3Regs Device Clock Date/Time 3 679 BCM 3-register date/time format2
EnableCloseBkr Remote Closing Enabled 1 669 BCM Bit 2; ON = enabled, OFF = not enabled
EnableOpenBkr Remote Opening Enabled 1 669 BCM Bit 1; ON = enabled; OFF = not enabled
Bit 3; ON = auto (enabled);
EnableRemCtrl Remote Control Enabled 1 669 BCM
OFF = manual (not enabled)
IA Current A 1 8821 PM A Unity
IA_PCT Current A % Load 1 8837 PM % Unity
IB Current B 1 8822 PM A Unity
IB_PCT Current B % Load 1 8838 PM % Unity
IC Current C 1 8823 PM A Unity
IC_PCT Current C % Load 1 8839 PM % Unity
IG Current G 1 8825 PM A Unity
IG_PCT Current G % Load 1 8841 PM % Unity
IG_PCT_VIGI Current G (VIGI) % Load 1 8842 PM % Hundredths
IG_VIGI Current G (VIGI) 1 8826 PM A Thousandths
IMax Current Max Present 1 8820 PM A Unity
IN Current N 1 8824 PM A Unity
IN_PCT Current N % Load 1 8840 PM % Unity
LDPUValue Long Delay Pickup Value 2 8756 PM A Modulo 10,000 format3
MaxIA Max Current A 1 8827 PM A Unity
MaxIB Max Current B 1 8828 PM A Unity
MaxIC Max Current C 1 8829 PM A Unity
MaxIG Max Current G 1 8831 PM A Unity
MaxIG_VIGI Max Current G (VIGI) 1 8832 PM A Thousandths
MaxIN Max Current N 1 8830 PM A Unity
NominalCurrent Breaker Nominal Current 1 8750 PM A Unity
ReadyToClose Breaker Ready to Close 1 661 BCM Bit 5; ON = yes, OFF = no
TU_BATT_PCT Trip Unit % Battery 1 8843 PM % Unity
TU_SN Trip Unit Serial Number 4 8700 PM ASCII text
TUCommStatus Trip Unit Internal Comms Status 1 552 BCM Bit 11; ON = not responding, OFF = OK
1. 3-register date/time format: register 1: month (byte 1) = 1–12; day (byte 2) = 1–31
register 2: year (byte 1) = 0–199 (add to 1900 to determine the actual year); hour (byte 2) = 0–23
register 3: minutes (byte 1) = 0–59; seconds (byte 2) = 0–59
Note: Bits 14 and 15 of the month/day register must be masked.

63220-080-200
Table 12: MICROLOGIC Type P Trip Unit Standard Quantities

Number of
Registers1
810D_LDPU Breaker LDPU in Progress 1 8862 PM Scaling N/A
810DBrkrStatus Breaker Status 1 661 BCM Bit 0; ON = closed, OFF = open
810DBrkrTripStat Breaker Trip Unit Status 1 661 BCM Bit 2; ON = tripped; OFF = not tripped
BCM_SN BCM Serial Number 4 516 BCM ASCII text
Bit 8 = disconnected
BkrPos Breaker Position 1 661 CCM Bit 9 = connected
Bit 10 = test position
DT_3Regs Device Clock Date/Time 3 679 BCM 3-register date/time format2
DTLastTrip D/T of Last Trip 3 693 BCM 3-register date/time format2
DTPkIAD D/T Peak Demand Current A 3 3005 MM 3-register date/time format2
DTPkIBD D/T Peak Demand Current B 3 3008 MM 3-register date/time format2
DTPkICD D/T Peak Demand Current C 3 3011 MM 3-register date/time format2
DTPkIND D/T Peak Demand Current N 3 3014 MM 3-register date/time format2
DTPkkVAD D/T Peak Demand Apparent Power 3 3023 MM 3-register date/time format2
DTPkkVARD D/T Peak Demand Reactive Power 3 3020 MM 3-register date/time format2
DTPkkWD D/T Peak Demand Real Power 3 3017 MM 3-register date/time format2
DTResetEnergy D/T Last Reset Accum. Energies 3 3038 MM 3-register date/time format2
DTResetMinMax D/T Last Reset Min/Max 3 9010 PM 3-register date/time format2
DTResetPkID D/T Last Reset Peak Dmd Currents 3 3026 MM 3-register date/time format2
DTResetPkkWD D/T Last Reset Peak Dmd Power 3 3029 MM 3-register date/time format2
EnableCloseBkr Remote Closing Enabled 1 669 BCM Bit 2; ON = enabled; OFF = not enabled
EnableOpenBkr Remote Opening Enabled 1 669 BCM Bit 1; ON = enabled; OFF = not enabled
Bit 3; ON = auto (enabled);
EnableRemCtrl Remote Control Enabled 1 669 BCM
OFF = manual (not enabled)
GFAlarmStatus GF Alarm Status 1 8860 PM Bit 0; ON = active; OFF = inactive
GFPreAlarmStatus GF Alarm Pre-Alarm Status 1 8864 PM Bit 0; ON = active; OFF = inactive
Hz Frequency 1 1054 MM Hz Tenths
IA Current A 1 1016 MM A Unity
IA_PCT Current A % Load 1 8837 PM % Unity
IAD Demand Current A 1 2200 MM A Unity
IAvg Current Avg 1 1027 MM A Unity
IB Current B 1 1017 MM A Unity
IB_PCT Current B % Load 1 8838 PM % Unity
IBD Demand Current B 1 2201 MM A Unity
IC Current C 1 1018 MM A Unity
IC_PCT Current C % Load 1 8839 PM % Unity
ICD Demand Current C 1 2202 MM A Unity
IG Current G 1 1021 MM A Unity
IG_PCT Current G % Load 1 8841 PM % Unity
IG_PCT_VIGI Current G (VIGI) % Load 1 8842 PM % Hundredths
IG_VIGI Current G (VIGI) 1 8826 PM A Thousandths
1. For register entries that are not listed, please refer to the MICROLOGIC device type register list. Contact your local sales representative.
3. Power factor format: –1 to –999 for lagging power factors, 1000 for unity power factor 1.000, and 1 to 999 for leading power factors.
4. Modulo 10,000 format: 1 to 4 sequential registers. Each register is Modulo 10,000 (range = –9,999 to +9,999).
Result is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1. Range is zero to 9,999,999,999,999,999.

63220-080-200

Number of
Registers1
IMax Current Max Present 1 1020 MM A Unity
IN Current N 1 1019 MM A Unity
IN_PCT Current N % Load 1 8840 PM % Unity
IND Demand Current N 1 2203 MM A Unity
IUnbalA Current Unbalance A 1 1028 MM % Tenths
IUnbalAlrm Current Unbalance Alarm Status 1 8859 PM Bit 0; ON = active; OFF = inactive
IUnbalB Current Unbalance B 1 1029 MM % Tenths
IUnbalC Current Unbalance C 1 1030 MM % Tenths
IUnbalPreAlrm Current Unbalance Pre-Alarm Status 1 8863 PM Bit 0; ON = active, OFF = inactive
IUnbalW Current Unbalance Worst 1 1032 MM % Tenths
kVAA Apparent Power A 1 1042 MM kVA Unity
kVAB Apparent Power B 1 1043 MM kVA Unity
kVAC Apparent Power C 1 1044 MM kVA Unity
kVAD Demand Apparent Power (KVAD) 1 2236 MM kVA Unity
kVAD_PkkVARD KVA Dmd Coincident w/Peak KVAR Dmd 1 2235 MM kVA Unity
kVAD_PkkWD KVA Dmd Coincident w/Peak KW Dmd 1 2229 MM kVA Unity
kVAHr Apparent Energy 4 2024 MM kVAH Modulo 10,000 format4
kVARA Reactive Power A 1 1038 MM kVAR Unity
kVARB Reactive Power B 1 1039 MM kVAR Unity
kVARC Reactive Power C 1 1040 MM kVAR Unity
kVARD Demand Reactive Power (KVARD) 1 2230 MM kVAR Unity
kVARD_PkkVAD KVAR Dmd Coincident w/Peak KVA Dmd 1 2241 MM kVAR Unity
kVARD_PkkWD KVAR Dmd Coincident w/Peak KW Dmd 1 2228 MM kVAR Unity
kVARHr Reactive Energy 4 2004 MM kVARH Modulo 10,000 format4
kVARHr_I Reactive Energy Into the Load 4 2016 MM kVARH Modulo 10,000 format4
kVARHr_O Reactive Energy Out of the Load 4 2020 MM kVARH Modulo 10,000 format4
kVARTtl Reactive Power Total 1 1041 MM kVAR Unity
kVATtl Apparent Power Total 1 1045 MM kVA Unity
kWA Real Power A 1 1034 MM kW Unity
kWB Real Power B 1 1035 MM kW Unity
kWC Real Power C 1 1036 MM kW Unity
kWD Demand Real Power (KWD) 1 2224 MM kW Unity
kWD_PkkVAD KW Dmd Coincident w/Peak KVA Dmd 1 2240 MM kW Unity
kWD_PkkVARD KW Dmd Coincident w/Peak KVAR Dmd 1 2234 MM kW Unity
kWHr Real Energy 4 2000 MM kWH Modulo 10,000 format4
kWHr_I Real Energy Into the Load 4 2008 MM kWH Modulo 10,000 format4
kWHr_O Real Energy Out of the Load 4 2012 MM kWH Modulo 10,000 format4
kWTtl Real Power Total 1 1037 MM kW Unity
LDPUValue Long Delay Pickup Value 2 8756 PM A Modulo 10,000 format4
LSCurrAlrm Load Shed Current Alarm Status 1 8859 PM Bit 13; ON = active; OFF = inactive
LSCurrPreAlrm Load Shed Current Pre-Alarm Status 1 8863 PM Bit 13; ON = active; OFF = inactive

63220-080-200

Number of
Registers1
LSPwrAlrm Load Shed Power Alarm Status 1 8859 PM Bit 14; ON = active; OFF = inactive
LSPwrPreAlrm Load Shed Power Pre-Alarm Status 1 8863 PM Bit 14; ON = active; OFF = inactive
M2C_M6CR1Status Relay Module R1 Status 1 8857 PM Bit 0; ON = on; OFF = off
MaxHz Max Frequency 1 1654 MM Hz Tenths
MaxIA Max Current A 1 1616 MM A Unity
MaxIAvg Max Current Avg 1 1627 MM A Unity
MaxIB Max Current B 1 1617 MM A Unity
MaxIC Max Current C 1 1618 MM A Unity
MaxIG Max Current G 1 8831 PM A Unity
MaxIG_VIGI Max Current G (VIGI) 1 8832 PM A Thousandths
MaxIN Max Current N 1 1619 MM A Unity
MaxIUnbalA Max Current Unbalance A 1 1628 MM % Tenths
MaxIUnbalB Max Current Unbalance B 1 1629 MM % Tenths
MaxIUnbalC Max Current Unbalance C 1 1630 MM % Tenths
MaxIUnbalW Max Current Unbalance Worst 1 1632 MM % Tenths
MaxkVAA Max Apparent Power A 1 1642 MM kVA Unity
MaxkVAB Max Apparent Power B 1 1643 MM kVA Unity
MaxkVAC Max Apparent Power C 1 1644 MM kVA Unity
MaxkVARA Max Reactive Power A 1 1638 MM kVAR Unity
MaxkVARB Max Reactive Power B 1 1639 MM kVAR Unity
MaxkVARC Max Reactive Power C 1 1640 MM kVAR Unity
MaxkVARTtl Max Reactive Power Total 1 1641 MM kVAR Unity
MaxkVATtl Max Apparent Power Total 1 1645 MM kVA Unity
MaxkWA Max Real Power A 1 1634 MM kW Unity
MaxkWB Max Real Power B 1 1635 MM kW Unity
MaxkWC Max Real Power C 1 1636 MM kW Unity
MaxkWTtl Max Real Power Total 1 1637 MM kW Unity
MaxPFA Max Power Factor A 1 1646 MM PF format3
MaxPFB Max Power Factor B 1 1647 MM PF format3
MaxPFC Max Power Factor C 1 1648 MM PF format3
MaxPFTtl Max Power Factor Total 1 1649 MM PF format3
MaxVAB Max Voltage A-B 1 1600 MM V Unity
MaxVAN Max Voltage A-N 1 1603 MM V Unity
MaxVBC Max Voltage B-C 1 1601 MM V Unity
MaxVBN Max Voltage B-N 1 1604 MM V Unity
MaxVCA Max Voltage C-A 1 1602 MM V Unity

63220-080-200

Number of
Registers1
MaxVCN Max Voltage C-N 1 1605 MM V Unity
MaxVLLAvg Max Voltage L-L Avg 1 1606 MM V Unity
MaxVLNAvg Max Voltage L-N Avg 1 1607 MM V Unity
MaxVUnbalAB Max Voltage Unbalance A-B 1 1608 MM % Tenths
MaxVUnbalAN Max Voltage Unbalance A-N 1 1611 MM % Tenths
MaxVUnbalBC Max Voltage Unbalance B-C 1 1609 MM % Tenths
MaxVUnbalBN Max Voltage Unbalance B-N 1 1612 MM % Tenths
MaxVUnbalCA Max Voltage Unbalance C-A 1 1610 MM % Tenths
MaxVUnbalCN Max Voltage Unbalance C-N 1 1613 MM % Tenths
MaxVUnbalLLW Max Voltage Unbalance L-L Worst 1 1614 MM % Tenths
MaxVUnbalLNW Max Voltage Unbalance L-N Worst 1 1615 MM % Tenths
MinHz Min Frequency 1 1354 MM Hz Tenths
MinIA Min Current A 1 1316 MM A Unity
MinIAvg Min Current Avg 1 1327 MM A Unity
MinIB Min Current B 1 1317 MM A Unity
MinIC Min Current C 1 1318 MM A Unity
MinIN Min Current N 1 1319 MM A Unity
MinIUnbalA Min Current Unbalance A 1 1328 MM % Tenths
MinIUnbalB Min Current Unbalance B 1 1329 MM % Tenths
MinIUnbalC Min Current Unbalance C 1 1330 MM % Tenths
MinIUnbalW Min Current Unbalance Worst 1 1332 MM % Tenths
MinkVAA Min Apparent Power A 1 1342 MM kVA Unity
MinkVAB Min Apparent Power B 1 1343 MM kVA Unity
MinkVAC Min Apparent Power C 1 1344 MM kVA Unity
MinkVARA Min Reactive Power A 1 1338 MM kVAR Unity
MinkVARB Min Reactive Power B 1 1339 MM kVAR Unity
MinkVARC Min Reactive Power C 1 1340 MM kVAR Unity
MinkVARTtl Min Reactive Power Total 1 1341 MM kVAR Unity
MinkVATtl Min Apparent Power Total 1 1345 MM kVA Unity
MinkWA Min Real Power A 1 1334 MM kW Unity
MinkWB Min Real Power B 1 1335 MM kW Unity
MinkWC Min Real Power C 1 1336 MM kW Unity
MinkWTtl Min Real Power Total 1 1337 MM kW Unity
MinPFA Min Power Factor A 1 1346 MM PF format3
MinPFB Min Power Factor B 1 1347 MM PF format3
MinPFC Min Power Factor C 1 1348 MM PF format3
MinPFTtl Min Power Factor Total 1 1349 MM PF format3
MinVAB Min Voltage A-B 1 1300 MM V Unity
MinVAN Min Voltage A-N 1 1303 MM V Unity
MinVBC Min Voltage B-C 1 1301 MM V Unity
MinVBN Min Voltage B-N 1 1304 MM V Unity

63220-080-200

Number of
Registers1
MinVCA Min Voltage C-A 1 1302 MM V Unity
MinVCN Min Voltage C-N 1 1305 MM V Unity
MinVLLAvg Min Voltage L-L Avg 1 1306 MM V Unity
MinVLNAvg Min Voltage L-N Avg 1 1307 MM V Unity
MinVUnbalAB Min Voltage Unbalance A-B 1 1308 MM % Tenths
MinVUnbalAN Min Voltage Unbalance A-N 1 1311 MM % Tenths
MinVUnbalBC Min Voltage Unbalance B-C 1 1309 MM % Tenths
MinVUnbalBN Min Voltage Unbalance B-N 1 1312 MM % Tenths
MinVUnbalCA Min Voltage Unbalance C-A 1 1310 MM % Tenths
MinVUnbalCN Min Voltage Unbalance C-N 1 1313 MM % Tenths
MinVUnbalLLW Min Voltage Unbalance L-L Worst 1 1314 MM % Tenths
MinVUnbalLNW Min Voltage Unbalance L-N Worst 1 1315 MM % Tenths
NominalCurrent Breaker Nominal Current 1 8750 PM A Unity
OverFreqAlrm Over Frequency Alarm Status 1 8859 PM Bit 11; ON = active, OFF = inactive
OverFreqPreAlrm Over Frequency Pre-Alarm Status 1 8863 PM Bit 11; ON = active, OFF = inactive
OverIAAlrm Over IA Demand Alarm Status 1 8859 PM Bit 1; ON = active, OFF = inactive
OverIAPreAlrm Over IA Demand Pre-Alarm Status 1 8863 PM Bit 1; ON = active, OFF = inactive
OverIBAlrm Over IB Demand Alarm Status 1 8859 PM Bit 2; ON = active, OFF = inactive
OverIBPreAlrm Over IB Demand Pre-Alarm Status 1 8863 PM Bit 2; ON = active, OFF = inactive
OverICAlrm Over IC Demand Alarm Status 1 8859 PM Bit 3; ON = active, OFF = inactive
OverICPreAlrm Over IC Demand Pre-Alarm Status 1 8863 PM Bit 3; ON = active, OFF = inactive
OverINAlrm Over IN Demand Alarm Status 1 8859 PM Bit 4; ON = active, OFF = inactive
OverINPreAlrm Over IN Demand Pre-Alarm Status 1 8863 PM Bit 4; ON = active, OFF = inactive
OverVoltAlrm Over Voltage Alarm Status 1 8859 PM Bit 6; ON = active, OFF = inactive
OverVoltPreAlrm Over Voltage Pre-Alarm Status 1 8863 PM Bit 6; ON = active, OFF = inactive
PF_PkkVAD PF Coincident w/Peak KVA Demand 1 2239 MM PF format3
PF_PkkVARD PF Coincident w/Peak KVAR Demand 1 2233 MM PF format3
PF_PkkWD PF Coincident w/Peak KW Demand 1 2227 MM PF format3
PFA Power Factor A 1 1046 MM PF format3
PFB Power Factor B 1 1047 MM PF format3
PFC Power Factor C 1 1048 MM PF format3
PFTtl Power Factor Total 1 1049 MM PF format3
PhaRotAlrm Phase Rotation Alarm Status 1 8859 PM Bit 12; ON = active, OFF = inactive
PkIAD Peak Demand Current A 1 2204 MM A Unity
PkIBD Peak Demand Current B 1 2205 MM A Unity
PkICD Peak Demand Current C 1 2206 MM A Unity
PkIND Peak Demand Current N 1 2207 MM A Unity
PkkVAD Peak Demand Apparent Power (KVAD) 1 2237 MM kVA Unity
PkkVARD Peak Demand Reactive Power (KVARD) 1 2231 MM kVAR Unity
PkkWD Peak Demand Real Power (KWD) 1 2225 MM kW Unity
PredkVAD Predicted KVA Demand 1 2238 MM kVA Unity

63220-080-200

Number of
Registers1
PredkVARD Predicted KVAR Demand 1 2232 MM kVAR Unity
PredkWD Predicted KW Demand 1 2226 MM kW Unity
R1OpsCounter Relay 1 Operations Counter 1 9081 PM Unity
ReadyToClose Breaker Ready to Close 1 661 BCM Bit 5; ON = yes, OFF = no
RevPwrAlrm Reverse Power Alarm Status 1 8859 PM Bit 9; ON = active; OFF = inactive
RevPwrPreAlrm Reverse Power Pre-Alarm Status 1 8863 PM Bit 9; ON = active; OFF = inactive
TimeToTrip Time Remaining to LT Trip 2 8865 PM Seconds Tenths
TU_BATT_PCT Trip Unit % Battery 1 8843 PM % Unity
TU_SN Trip Unit Serial Number 4 8700 PM ASCII text
TUCommStatus Trip Unit Internal Comms Status 1 552 BCM Bit 11; ON = not responding; OFF = OK
UnderFreqAlrm Under Frequency Alarm Status 1 8859 PM Bit 10; ON = active; OFF = inactive
UnderFreqPreAlrm Under Frequency Pre-Alarm Status 1 8863 PM Bit 10; ON = active; OFF = inactive
UnderVoltAlrm Under Voltage Alarm Status 1 8859 PM Bit 5; ON = active; OFF = inactive
UnderVoltPreAlrm Under Voltage Pre-Alarm Status 1 8863 PM Bit 5; ON = active; OFF = inactive
VAB Voltage A-B 1 1000 MM V Unity
VAN Voltage A-N 1 1003 MM V Unity
VBC Voltage B-C 1 1001 MM V Unity
VBN Voltage B-N 1 1004 MM V Unity
VCA Voltage C-A 1 1002 MM V Unity
VCN Voltage C-N 1 1005 MM V Unity
VigiAlarm Vigi Alarm Status 1 8860 PM Bit 1; ON = active; OFF = inactive
VigiPreAlrm Vigi Pre-Alarm Status 1 8864 PM Bit 1; ON = active; OFF = inactive
VLLAvg Voltage L-L Avg 1 1006 MM V Unity
VLNAvg Voltage L-N Avg 1 1007 MM V Unity
VUnbalAB Voltage Unbalance A-B 1 1008 MM % Tenths
VUnbalAlrm Voltage Unbalance Alarm Status 1 8859 PM Bit 7; ON = active, OFF = inactive
VUnbalAN Voltage Unbalance A-N 1 1011 MM % Tenths
VUnbalBC Voltage Unbalance B-C 1 1009 MM % Tenths
VUnbalBN Voltage Unbalance B-N 1 1012 MM % Tenths
VUnbalCA Voltage Unbalance C-A 1 1010 MM % Tenths
VUnbalCN Voltage Unbalance C-N 1 1013 MM % Tenths
VUnbalLLW Voltage Unbalance L-L Worst 1 1014 MM % Tenths
VUnbalLNW Voltage Unbalance L-N Worst 1 1015 MM % Tenths
VUnbalPreAlrm Voltage Unbalance Pre-Alarm Status 1 8863 PM Bit 7; ON = active, OFF = inactive

63220-080-200
APPENDIX B—MICROLOGIC TRIP UNIT Table 13 shows the most common error codes that occur for the
ERROR CODES MICROLOGIC Trip Unit in SMS. The error code number (but not the
description) displays in the SMS Activity Log.
Table 13: MICROLOGIC Trip Unit Error Codes in SMS

Error Code Description Solution
4500 An attempt was made to close, but remote close was Enable the desired control from the SMS control
not enabled; output feature.
OR
An attempt was made to open, but remote open was
not enabled.
4608 Comms error with a sub-device within the trip unit system. One The Activity Log lists the sub-device that failed.
or more sub-devices are not communicating. See the SMS Use this information and read the Troubleshooting
Activity Log for details. section for details.
The sample Activity Log in Figure 13 illusrates an error 4500 condition. Note
that both the trip unit and BCM have lost communication.
Figure 13: Activity Log illustration

63220-080-200
APPENDIX C—SMS TABLE SUPPORT These are the standard real-time data tables included in SMS for
MICROLOGIC trip units. To learn how to use tables in SMS, see the SMS
online help file.
Table 14 lists existing and new SMS tables that MICROLOGIC trip
units support.
Table 14: SMS Tables Supported by MICROLOGIC Devices
Table Name Type A Type P

Existing SMS Tables Supported by MICROLOGIC Trip Units
Instantaneous Ratings X X
Basic Readings Summary X X
Load Current Summary X X
System Voltage Summary X
Demand Current Summary X
Demand Readings X
Energy Readings X
Reactive Energy Contribution Summary X
Real Energy Contribution Summary X
Energy Summary X
Phase Unbalance Readings X
Power Factor Readings X
Power Factor Summary X
Power Flow Summary X
Power Readings X
Power Capacity Utilization Summary X
New SMS Tables Supported by MICROLOGIC Trip Units
MicroLogic Protection Settings X X
MicroLogic Trip Curve X X
MicroLogic Circuit Loading Capacity Summary X X
MicroLogic Maintenance Information X X
Circuit Breaker Status Summary (Low Voltage) X X
MicroLogic Metering Configuration X
MicroLogic Trip History X
MicroLogic Type A Trip Unit Data X

63220-080-200
APPENDIX D—COMMUNICATIONS The following tables show the maximum distances of the communications
CONSIDERATIONS link at different baud rates. The maximum distances are measured from the
PC to the farthest device on the communications link.

(SY/MAX, MODBUS, Jbus devices)
Maximum Distances
Baud Rate 1–16 Devices 17–32 Devices
1200 10,000 ft. (3,050 m) 10,000 ft. (3,050 m)
2400 10,000 ft. (3,050 m) 5,000 ft. (1,525 m)
4800 10,000 ft. (3,050 m) 5,000 ft. (1,525 m)
9600 10,000 ft. (3,050 m) 4,000 ft. (1,220 m)
19200 10,000 ft. (3,050 m) 2,500 ft. (762.5 m)

(MODBUS, Jbus devices)
Maximum Distances
Baud Rate 1–8 Devices 1 9–16 Devices 1
1200 10,000 ft. (3,050 m) 10,000 ft. (3,050 m)
2400 10,000 ft. (3,050 m) 5,000 ft. (1,525 m)
4800 10,000 ft. (3,050 m) 5,000 ft. (1,525 m)
9600 10,000 ft. (3,050 m) 4,000 ft. (1,220 m)
19200 10,000 ft. (3,050 m) 2,500 ft. (762.5 m)
1 The number of devices shown applies to daisy chains that include
POWERLOGIC devices that are wired as 2-wire devices. If the daisy
chain contains only true 2-wire devices (and therefore no
POWERLOGIC devices) refer to the device manufacturer’s
instruction book for device number and distance limitations.
NOTE: To wire 4-wire devices as 2-wire, connect the Rx+ and Tx+ terminals
together, then connect the Rx- and the Tx- terminals together. The Rx+/Tx+
terminals connect to the Lx+ line, and the Rx-/Tx- terminals connect to the
Lx- line. Refer to the device’s instruction manual for device pinouts and other
communications specifications.

63220-080-200
Figure 14 illustrates the communications wiring for the MICROLOGIC trip

unit system.
Cradle Communication Module

Shield
Out– (Black)
Previous Device
Out+ (Red)
In– (White)
Next Device
In+ (Green)
+24 V
Previous Device
24 Vdc +24 V
Ground
Ground
Ground Next Device
Black Red White Green F2+ F1– 24 Vdc #2

Breaker (optional, but recommended)
Secondary
Connections Comm UC3
E1 E2 E3 E4 E5 E6
Trip Unit
+24 Vdc
Ground
Out+
Out–
Protection
In+
In–
Module
IR
Peer-to-Peer
Breaker
Internal
Communication
Communication
Module
Meter
Module
Primary Primary
Breaker Breaker
Disconnect Current Sensor
Disconnect
Voltage pickup
(top) (bottom)
Figure 14: MICROLOGIC System Communication Wiring

63220-080-200
September 2000
INDEX control outputs

errors 13
A using 13
accumulated energy 19 cradle communication module (CCM) 2
address described 3
for the MICROLOGIC trip unit, illustration 8 custom and standard quantities 9
Address sync push button 6, 26 D
advanced topics 21 date/time
alarms changing via HMI 24
levels (severities) synchronization 23
described 10 via Modbus master device 24
pre-assigned 11 default alarm level characteristics (table) 10
setup 9 demand
alternate (CM2) sign convention 22 current, changing method or interval 18
Appendix A—Standard Quantities 28 methods 18
Appendix B—MICROLOGIC Trip Unit Error peak 19
Codes 35 predicted 19
Appendix C—SMS Table Support 36 readings 17
Appendix D—Communications Considerations demand power calculation methods 18
37 device
architecture address limitations, mixed-mode daisy chain
trip unit 3 2
address, from the HMI 5
B resets 14
baud rate (from the HMI) 5 setup in SMS 7
BCM (Modbus breaker communication module) setup tasks, overview 7
described 2
E
block interval demand 18
energy readings 19
C error codes, list 35
CCM (cradle communication module) Ethernet
described 2–3 (MMS)
changing the demand current 18 communication 4
changing the demand power 19 (Modbus TCP) communication, CM-4000
changing the demand power method or interval with Ethernet Communication Card 4
18 Ethernet Gateway
changing the VAR and power factor sign conven- firmware version 1
tion 21
F
checklist
features
hardware setup 5
MICROLOGIC Electronic Trip Units 1
CM2 sign convention 22
functions
CM2000 Circuit Monitors
global, analog and digital 9
firmware version 1
CM4000 H
communication through 5 hardware
communication setup 5
(RS-485 Modbus RTU) 4 HMI
link (peer-to-peer protocol) 3 defined 2
with SMS setting the address, baud rate, and parity 5
types 4 setting the demand calculation method and
communications considerations 37 interval 18
trip unit 26
communications parameters
setting 6 human-machine interface
see HMI 2
composite device
defined 2

63220-080-200
September 2000
I Product Registration and Technical Support Con-

IEC sign convention 22 tacts document 2, 7
IEEE sign convention 17, 21 protection module (PM)
installation described 2
SMS 7 Q
installation and device setup in SMS 7 quantities
instruction bulletin using 9
MICROLOGIC trip unit 1 Quick Starts
M SMS 7
metering R
capabilities 15 real-time metering 15
module (MM) Requirements for Using MICROLOGIC
described 2 Devices 1
real-time 15 reset
MICROLOGIC MICROLOGIC trip units 14
electronic trip unit instruction bulletin 1 resetting the device clock 13
MICROLOGIC Protection Settings table 13 RS-485 Modbus RTU protocol (trip unit commu-
min/max nication) 4
conventions (power factor) 16 S
values 15
serial (RS-485 Modbus RTU)
mixed-mode daisy chain communication 4
device address limitations 2
Series 2000 Circuit Monitors
MM (trip unit metering module) firmware 1
described 2
setpoints, on-board alarms 13
N setting communications parameters 6
nonvolatile memory 15, 19 setup
O hardware 5
on-board alarms setup in SMS 7
Type P 13 severity (alarm level) 10
P sign conventions 17
VAR sign and power factor 21
parity (from the HMI) 5
sliding demand 18
peak demands 19
SMS 1
peer-to-peer protocol 3
Activity Log 27, 35
PM (trip unit protection module)
Alarm Log 27
described 2
installation 7
power factor online help file 1
changing the sign 21 version requirement 1
min/max conventions 16
standard quantities
power supply list 28
BCM 3
system architecture 4
BCM and CCM 5
CCM 3 T
isolation of 3 Technical Support 2, 28
trip unit 2 time synchronization 23
POWERLOGIC Ethernet Gateway trip unit
version 1 address, illustration 8
POWERLOGIC System Architecture and Appli- described 2
cation Guide 4 errror codes 35
pre-assigned alarms 11 metering module (MM), described 2
pre-assigned alarms (table) 11 power supply 2
pre-assigned alarms and events 11 protection module (PM), described 2
pre-assigned task trip unit system 2, 8
device clock reset 13 troubleshooting 26
predicted demand 19 Type P Energy Readings (table) 21
Type P on-board alarms 13

63220-080-200
September 2000
U
using control outputs 13
using custom quantities 9
V
VAR and PF sign conventions
changing from HMI 23
VAR sign convention
changing 21
changing in SMS 22
viewing information in SMS 9
W
wiring distances 37

63220-080-200
September 2000

Bulletin No. 63220-080-200 September 2000 © 2000 Schneider Electric All Rights Reserved.
PBG 1M 9/2000 Class 612

Micro Logic

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Micro Logic

Hochgeladen von

Copyright:

Verfügbare Formate

63220-080-200

Instruction Bulletin September 2000

Using MICROLOGIC® Type A and Type P

The addition of either symbol to a “Danger” or “Warning” safety label

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

© 2000 Schneider Electric All Rights Reserved

CONTENTS LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii

© 2000 Schneider Electric All Rights Reserved i

APPENDIX D—COMMUNICATIONS CONSIDERATIONS . . . . . . . . . . . 37

ii © 19xx–1999 Square D All Rights Reserved

LIST OF FIGURES Figure 1: Trip Unit Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

© 2000 Schneider Electric All Rights Reserved iii

iv © 2000 Schneider Electric All Rights Reserved

LIST OF TABLES Table 1: SMS Default Alarm Levels . . . . . . . . . . . . . . . . . . . . . . . . . 10

© 2000 Schneider Electric All Rights Reserved v

vi © 2000 Schneider Electric All Rights Reserved

ABOUT THIS DOCUMENT This document provides the following information:

Use this bulletin along with these other manuals:

© 2000 Schneider Electric All Rights Reserved 1

• If your system includes a mixed-mode daisy chain (POWERLOGIC and

2 © 2000 Schneider Electric All Rights Reserved

The BCM also contains:

The trip unit modules communicate using a dedicated peer-to-peer protocol

Modbus (RS-485) Communication

Cradle Secondary Connections

Figure 1: Trip Unit Architecture

© 2000 Schneider Electric All Rights Reserved 3

Series 4000 Series 2000

Figure 2: Communication via a PC Serial Port (RS-485 MODBUS RTU)

4 © 2000 Schneider Electric All Rights Reserved

RS-485 Daisy Chain

Series 4000 Series 2000

Series 4000 Series 2000

Figure 4: Communication via an Ethernet Gateway

© 2000 Schneider Electric All Rights Reserved 5

6 © 2000 Schneider Electric All Rights Reserved

9. Connect the MODBUS network to a PC workstation via Ethernet

© 2000 Schneider Electric All Rights Reserved 7

Daisy Chain Connecting Devices POWERLOGIC

Figure 5: Adding a Device Address for the MICROLOGIC Trip Unit

8 © 2000 Schneider Electric All Rights Reserved

USING QUANTITIES Standard Quantities

For complete instructions on adding global functions and assigning them to

© 2000 Schneider Electric All Rights Reserved 9

Table 1: SMS Default Alarm Levels

10 © 2000 Schneider Electric All Rights Reserved

Table 2: MICROLOGIC Trip Unit Pre-assigned PC-based Alarms

© 2000 Schneider Electric All Rights Reserved 11

Table 2: MICROLOGIC Trip Unit Pre-assigned PC-based Alarms

12 © 2000 Schneider Electric All Rights Reserved

Table 3: Type P Trip Unit On-board Alarms

Function Name Alarm Level

Table 4: MICROLOGIC Control Outputs

Control Target Device

© 2000 Schneider Electric All Rights Reserved 13

However, if remote control is enabled, but the SMS open/close feature is

Table 5: Micrologic Type A and Type P Device Resets

Device Reset Type A Type P

14 © 2000 Schneider Electric All Rights Reserved

Table 6: Real-Time Readings

© 2000 Schneider Electric All Rights Reserved 15

Figure 6: Power Factor Min/Max Values

16 © 2000 Schneider Electric All Rights Reserved