micro logic

Instruction Bulletin63220-080-200

September 2000

Using MICROLOGIC® Type A and Type P electronic trip units in a POWERLOGIC® system

Retain for future use

© 2000 Schneider Electric All Rights Reserved

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.

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

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.

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.

NOTICE

!

DANGERDANGER indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

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

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

CAUTIONCAUTION, used without the safety alert symbol, indicates a potentially hazardous situation which, if not avoided, can result in property damage.

PLEASE NOTE

CLASS A FCC STATEMENT

Bulletin No. 63220-080-200September 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Trip Unit System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Hardware Setup Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Setting Type A Communications Parameters . . . . . . . . . . . . . . . . . . . 6

Setting Type P Communications Parameters . . . . . . . . . . . . . . . . . . . 6

INSTALLATION AND DEVICE SETUP IN SMS . . . . . . . . . . . . . . . . . . . . . 7

Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Adding and Setting Up Trip Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

VIEWING REAL-TIME INFORMATION IN SMS . . . . . . . . . . . . . . . . . . . . . 9

USING QUANTITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

USING SMS ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Alarm Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Pre-assigned PC-based Alarms and Events . . . . . . . . . . . . . . . . . . . 11Type P Pre-assigned On-board Alarms . . . . . . . . . . . . . . . . . . . . . . . 13Pre-assigned Task—Resetting the Device Clock . . . . . . . . . . . . . . . 13

USING CONTROL OUTPUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

DEVICE RESETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

METERING CAPABILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Real-Time Metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Min/Max Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Power Factor Min/Max Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 16

Demand Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Demand Power and Current Calculation Methods . . . . . . . . . . . . . . 18Predicted Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Peak Demands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Energy Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

ADVANCED TOPICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Changing the VAR and Power Factor Sign Convention . . . . . . . . . . 21Changing VAR sign convention within SMS . . . . . . . . . . . . . . . . . . . 22

Changing VAR and PF sign conventions from the trip unit HMI . . . . 23Time 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

i

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

ii

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

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

© 19xx–1999 Square D All Rights Reserved

63220-080-200 List of FiguresSeptember 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 . . . . . . . . . . . . . . 5Figure 5: Adding a Device Address for the

MICROLOGIC Trip Unit 8Figure 6: Power Factor Min/Max Values . . . . . . . . . . . . . . . . . . . . . . 16Figure 7: IEEE Sign Convention (default) . . . . . . . . . . . . . . . . . . . . . 17

Figure 8: MICROLOGIC Trip Unit Predicted Demand. . . . . . . . . . . . 19Figure 9: IEEE Sign Convention (default) . . . . . . . . . . . . . . . . . . . . . 21Figure 10: IEC Sign Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 11: Alternate (CM2) Sign Convention. . . . . . . . . . . . . . . . . . . . 22Figure 12: Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 13: Activity Log illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 14: MICROLOGIC System Communication Wiring . . . . . . . . . 38

iii

List of Figures 63220-080-200September 2000

iv

63220-080-200 List of TablesSeptember 2000


LIST OF TABLES
Table 1: SMS Default Alarm Levels . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 2: MICROLOGIC Trip Unit Pre-assigned
PC-based Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 3: Type P Trip Unit On-board Alarms . . . . . . . . . . . . . . . . . . . 13Table 4: MICROLOGIC Control Outputs . . . . . . . . . . . . . . . . . . . . . 13Table 5: Micrologic Type A and Type P Device Resets . . . . . . . . . . 14Table 6: Real-Time Readings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 7: Type P Trip Unit Demand Readings. . . . . . . . . . . . . . . . . . 17Table 8: Type P Energy Readings . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 9: BCM/Trip Unit Values for Setting Date/Time . . . . . . . . . . . 24Table 10: CCM Values for Setting Date/Time . . . . . . . . . . . . . . . . . . 24Table 11: MICROLOGIC Type A Trip Unit Standard Quantities . . . . 28Table 12: MICROLOGIC Type P Trip Unit Standard Quantities . . . . 29Table 13: MICROLOGIC Trip Unit Error Codes in SMS. . . . . . . . . . . 35Table 14: SMS Tables Supported by MICROLOGIC Devices . . . . . . 36Table 15: Maximum Distances for 4-Wire Bus Topologies

(SY/MAX, MODBUS, Jbus devices) . . . . . . . . . . . . . . . . . . 37Table 16: Maximum Distances for 2-Wire Bus Topologies

(MODBUS, Jbus devices) . . . . . . . . . . . . . . . . . . . . . . . . . . 37

v

List of Tables 63220-080-200September 2000

vi

63220-080-200September 2000 Using MICROLOGIC Type A and Type P Electronic Trip Units in a POWERLOGIC System


ABOUT THIS DOCUMENT

FEATURE SUPPORT FOR MICROLOGIC ELECTRONIC TRIP UNITS

REQUIREMENTS FOR USING MICROLOGIC ELECTRONIC TRIP UNITS

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

This section describes the features that SMS supports for MICROLOGIC 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

To use MICROLOGIC electronic trip units in SMS, the following requirements 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.

1

63220-080-200Using MICROLOGIC Type A and Type P Electronic Trip Units in a POWERLOGIC System September 2000

2

TECHNICAL SUPPORT

SYSTEM DESCRIPTION

Trip Unit System Modules

• 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.

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.

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.

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.




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.

Figure 1: Trip Unit Architecture

Microlog

ic 2.0

CradleCommunicationModule (optional)

BreakerCommunicationModule

Modbus (RS-485) Communication

Trip Unit

CircuitBreaker

Cradle Secondary ConnectionsCircuit Breaker Secondary Connections

Cradle

MeterModule

ProtectionModule

Test KitPort

Peer-to-PeerProtocol

IR communications

3


4

Network Communication

POWERLOGICSystem ManagSoftware

MICROLOGElectronic T

RS-232

Figure 2: Communicatio

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).

er

MCI-101 Converter Kit

Circuit BreakerIC

rip Unit

Series 4000 Circuit Monitor

RS-485 Daisy Chain

Series 2000Circuit Monitoror Power Meter

MCT-485 orMCTAS-485Terminator

n via a PC Serial Port (RS-485 MODBUS RTU)




Ethernet (Modbus T

MICElec

POWERLOGIC System ManagSoftware


Ethernet (MMS)

MICROLOGICElectronic Trip

POWERLOGIC System ManagSoftware


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.

CP)

Circuit BreakerROLOGIC tronic Trip Unit

Series 4000 Circuit Monitorwith ECC


RS-485 Daisy Chain



er

n via a CM4000 Ethernet Communication Card (CM4000 with ECC)

POWERLOGIC Ethernet Gateway

Circuit Breaker Unit


RS-485 Daisy Chain



er

n via an Ethernet Gateway

5


6

Setting Type A Communications Parameters

Setting Type P Communications Parameters

For the Type A trip unit, follow these steps:a. From the default Current menu, simultaneously press and hold both

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.

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.

menu




INSTALLATION AND DEVICE SETUP IN SMS

Installing the Software

Adding and Setting Up Trip Units

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.

If you encounter problems with any instructions in this section, refer to “Troubleshooting” on page 26 for troubleshooting help.

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.

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.

7


8

In this example, you might give tbreaker communication module (BCM

#51 to the crade communication #101 to the trip unit protectio #201 to the trip unit meter mod

You only assign the first address

CircuitBreaker Cradle

Daisy Chain Connecting Devices

CCM

BCM

PM

MM

Address

(51)

(1)

(101)

(201)

CircuitBreaker

Figure 5: Adding a Device Address f

Figure 5 illustrates how these addresses are determined, when the trip unit is installed in a drawout circuit breaker.

.

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 tripunit 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.

POWERLOGIC System ManagerSoftware

POWERLOGIC Ethernet Gateway

Circuit Breaker/Trip Unit:Address 1 (51, 101, 201)

Circuit Monitors and/oOther Devices:In this example, do noassign address number 51, 101, or 201to any remaining devic

he trip unit address #1. This step assigns address #1 to the ). SMS will automatically assign these addresses for the trip uni

module (CCM)n module (PM)ule (MM)

to the Ethernet Gateway; do not assign the remaining trip unit m

or the MICROLOGIC Trip Unit




VIEWING REAL-TIME INFORMATION IN SMS

USING QUANTITIES

USING SMS ALARMS

Once you have added the trip unit to your system, you can view real-time 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.

Standard QuantitiesFor 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 QuantitiesIn 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.

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.

9


10

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

SeverityLevel Audible1 Visible2 Acknowledge

Required3PasswordRequired4

Alarm 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.




Table 2: MICROLOGIC Trip Unit Pre-assigned

Digital Function Name1 Module2 Pickup Text /

Alarm Level3DropoutAlarm Le

Long Delay Pickup PM In Progress(level 2)

Not Picked(no alarm)

Protection Settings Change PM Detected

(level 4)Not Detec(no alarm)

Rating/Sensor Plug Changeout PM

Detected(level 4)

Not Detec(no alarm)

Trip Unit Changeout

PM Detected(level 4)

Not Detec(no alarm)

Trip Unit Door Open PM Yes(level 5)

No(no alarm)

Breaker Changeout BCMDetected(level 4)

Not Detec(no alarm)

Breaker Status BCM Closed(no alarm)

Open(no alarm)

Loss of Logging and Alarming Capability

BCM Detected(level 1)

Not Detec(no alarm)

Ready to Close BCM Yes(no alarm)

No(no alarm)

Remote Closing Enabled

BCM Yes(no alarm)

No(no alarm)

Remote Control Enabled BCM

Auto(no alarm)

Manual(no alarm)

Remote Opening Enabled

BCM Yes(no alarm)

No(no alarm)

Spring Charged BCM Yes(no alarm)

No(no alarm)

Time Loss—Breaker Comms Module


Not Detec(no alarm)

Trip Unit Internal Comms Failure


Not Detec(no alarm)

Trip Unit Status (SDE) BCM Fault Tripped

(level 1)Not Trippe(no alarm)

Breaker Between Positions CCM True

(level 9)False(no alarm)

Breaker Connected (CE) CCM True

(no alarm)False(no alarm)

Breaker Disconnected (CD) CCM

True(level 9)

False(no alarm)

Breaker in Test (CT)

CCM True(level 9)

False(no alarm)

1. This name displays in the SMS Activity Log and Active Alarm2. The module that generates the alarm; BCM = breaker comm3. Although you can change the level for an alarm, keep in min

the SMS Activity Log, but does not display in the Active Alarmon page 11.

4. These functions are polled only when they are included in a

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.
PC-based Alarms

Text /vel3

Polling Interval

Remarks

Up 15 sec. Type P trip units only. Long delay pickup setpoint is exceeded and trip is imminent if current is not reduced.

ted 300 sec. Alarm appears when any trip unit protection setpoint is changed.

ted300 sec.

Alarm appears when the rating plug type or sensor plug current rating changes from the last time SMS communicated with the breaker.

ted 300 sec. Alarm appears when the PM serial number changes from the last time SMS communicated with the breaker.

300 sec. Type P trip units only. Indicates trip unit door is open and basic protection settings switches are exposed.

ted300 sec.

Alarm appears when the BCM serial number changes from the last time SMS communicated with the breaker.

N/A4

ted 60 sec. Indicates loss of internal communication to the trip unit. Could be caused by trip unit being removed or by loss of trip unit auxiliary power.

N/A4

N/A4If Remote Closing is disabled, an attempt to close the breaker in SMS will result in error code 4500. See Appendix B—MICROLOGIC Trip Unit Error Codes for information.

N/A4

Remote control is enabled/disabled at the trip unit HMI by placing the unit in Auto /Manual.

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.

N/A4If Remote Opening is disabled, an attempt to open the breaker in SMS will result in error code 4500. See Appendix B—MICROLOGIC Trip Unit Error Codes for information.

N/A4 Indicates status of motor-charged closing springs.

ted 60 sec. Indicates that the BCM lost power. An SMS clock reset task automatically performs the reset with no user action required.

ted 60 sec. Indicates loss of internal communication to the trip unit. Could be caused by trip unit being removed or by loss of trip unit auxiliary power.

d 15 sec. Protective trip alarm. This alarm remains until the trip unit is reset. If the trip unit is Type P, onboard alarms also appear with the type of trip.

60 sec.Only for models with CCM.Indicates that the circuit breaker is between Connected and Test or between Test and Disconnected positions.

60 sec. Only for models with a CCM.Indicates that the circuit breaker is in Connected position.

60 sec.Only for models with CCM.Indicates that the circuit breaker is in Disconnected position.

60 sec. Only for models with a CCM.Indicates that the circuit breaker is in Test position.

log.unication module, CCM = cradle communication module, PM = protection moduled that each alarm level has specific characteristics: For example, alarm level 9 displays an entry in s Log. For a detailed discussion of alarm levels, see “Pre-assigned PC-based Alarms and Events”

file such as a real-time table. The polling is updated according to the interval chosen for that display.

11


12

Time Loss—Cradle Comms Module CCM Detected

(level 9)Not Detec(no alarm)

Table 2: MICROLOGIC Trip Unit Pre-assigned

Digital Function Name1 Module2 Pickup Text /

Alarm Level3DropoutAlarm Le

1. This name displays in the SMS Activity Log and Active Alarm2. The module that generates the alarm; BCM = breaker comm3. Although you can change the level for an alarm, keep in min

the SMS Activity Log, but does not display in the Active Alarmon page 11.

4. These functions are polled only when they are included in a

ted 60 sec.Only for models with a CCM. Indicates that the CCM lost power. An SMS clock reset task automatically performs the reset with no user action required.

PC-based Alarms

Text /vel3

Polling Interval

Remarks

log.unication module, CCM = cradle communication module, PM = protection moduled that each alarm level has specific characteristics: For example, alarm level 9 displays an entry in s Log. For a detailed discussion of alarm levels, see “Pre-assigned PC-based Alarms and Events”

file such as a real-time table. The polling is updated according to the interval chosen for that display.




Type P Pre-assigned On-board Alarms

Pre-assigned Task—Resetting the Device Clock

USING CONTROL OUTPUTS

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.

The clock reset is the only pre-assigned task for a device reset. For more 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.

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.

Remote control (Auto/Manual) must be enabled from the trip unit HMI for any output to be controlled from SMS.

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

Table 4: MICROLOGIC Control Outputs

Control Target Device

Circuit Breaker (close/open) BCM

Open Permissive (enable/disable) BCM

Close Permissive (enable/disable) BCM

13


14

DEVICE RESETS

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.

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.




METERING CAPABILITIES

Real-Time Metering

Min/Max Values

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.

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.

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.

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

15


16

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.

Figure 6: Power Factor Min/Max Values

Unity1.00

Lag(–)

Lead(+)

MaximumPower Factor0.8 (leading)

Range of PowerFactor Values

MinimumPower Factor–0.7 (lagging)

-0 +0

.8

.6

.4

.2 .2

.4

.6

.8




Demand Readings

Figure 7: IEEE Sign Convention (default)

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

RealPower

ReactivePower

Quadrant1

Quadrant2

Quadrant3

Quadrant4

Watts Negative (–)VARs Positive (+)

PF Leading (+)

Reverse Power Flow Normal Power Flow

Watts Positive (+)VARs Positive (+)

PF Lagging (–)

Watts Negative (–)VARs Negative (–)

PF Lagging (–)

Watts Positive (+)VARs Negative (–)

PF Leading (+)

17


18

Demand Power and Current Calculation Methods

To be compatible with electric utility billing practices, the Type P trip unit 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 DemandThe 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.

2. Press or to select Metering Setup. 3. Press ; the Metering Setup menu displays.

4. Press or to select Current Demand.




Predicted Demand

Predicted dem

Bo

Demand forlast completedinterval

Figure 8: M

Peak Demands

Energy Readings

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.

9. Press to select Yes. Press to save the change that you’ve made.

10. Press to return to the default Main menu.

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.

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.

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

and is updated every second until the interval is complete.

15-minute interval

Time

eginning f interval

Predicted demand if load is added during interval, predicted demand increases to reflect increased demand

Predicted demand if no load is added

Partial IntervalDemand

1:00 1:06 1:15

Change in Load

ICROLOGIC Trip Unit Predicted Demand

19


20

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.




ADVANCED TOPICS

Changing the VAR and Power Factor Sign Convention

Table 8 lists available accumulated energy values.

This section includes discussion of these advanced topics:

• VAR sign and power factor sign conventions

• time synchronization

The trip unit offers two reactive power (VAR) sign conventions and three 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.

Figure 9: IEEE Sign Convention (default)

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

RealPower

ReactivePower

Quadrant1

Quadrant2

Quadrant3

Quadrant4


PF Leading (+)



PF Lagging (–)


PF Lagging (–)


PF Leading (+)

21


22

The IEC sign convention, shown in Figure 10, is achieved by combining the IEEE VAR sign convention with the IEC power factor sign convention.

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.

Figure 11: Alternate (CM2) Sign Convention

Changing VAR sign convention within SMSTo 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.

RealPower

ReactivePower

Quadrant1

Quadrant2

Quadrant3

Quadrant4


PF Leading (–)



PF Lagging (+)


PF Lagging (–)


PF Leading (+)

RealPower

ReactivePower

Quadrant1

Quadrant2

Quadrant3

Quadrant4


PF Leading (+)



PF Lagging (–)


PF Lagging (–)


PF Leading (+)




Time Synchronization

Changing VAR and PF sign conventions from the trip unit HMIFor 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.

2. Press or to select Metering Setup. 3. Press ; the Metering 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.8. Press to select Yes. Press to save the change that you’ve

made.

9. Press to return to the default Main menu.

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.

23


24

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).

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).

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.

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

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




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.

25


26

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 display5. 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




Figure 12: A

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:

In this example, the error 401 entries show that communication was lost with the trip unit and the BCM.

ctivity Log

27


28

Table 11: MICROLOGIC Type A Trip Unit Stand

SMS Topic Name User Description

810DBrkrStatus Breaker Status

810DBrkrTripStat Breaker Trip Unit Status

BCM_SN BCM Serial Number

BkrPos Breaker Position

DT_3Regs Device Clock Date/Time

EnableCloseBkr Remote Closing Enabled

EnableOpenBkr Remote Opening Enabled

EnableRemCtrl Remote Control Enabled

IA Current A

IA_PCT Current A % Load

IB Current B

IB_PCT Current B % Load

IC Current C

IC_PCT Current C % Load

IG Current G

IG_PCT Current G % Load

IG_PCT_VIGI Current G (VIGI) % Load

IG_VIGI Current G (VIGI)

IMax Current Max Present

IN Current N

IN_PCT Current N % Load

LDPUValue Long Delay Pickup Value

MaxIA Max Current A

MaxIB Max Current B

MaxIC Max Current C

MaxIG Max Current G

MaxIG_VIGI Max Current G (VIGI)

MaxIN Max Current N

NominalCurrent Breaker Nominal Current

ReadyToClose Breaker Ready to Close

TU_BATT_PCT Trip Unit % Battery

TU_SN Trip Unit Serial Number

TUCommStatus Trip Unit Internal Comms Status

1. 3-register date/time format: register 1: month (byte 1) = 1–1register 2: year (byte 1) = 0–199register 3: minutes (byte 1) = 0–

Note: Bits 14 and 15 of the month/day register must be maske

APPENDIX A—STANDARD QUANTITIESAPPENDIX 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.
ard Quantities

Number ofRegisters1 Register1 Module1 Units1 Scale/Bitmask1

1 661 BCM Bit 0; ON = closed, OFF = open

1 661 BCM Bit 2 ON = tripped, OFF = not tripped

4 516 BCM ASCII text

1 661 CCMBit 8 = disconnectedBit 9 = connectedBit 10 = test position

3 679 BCM 3-register date/time format2

1 669 BCM Bit 2; ON = enabled, OFF = not enabled

1 669 BCM Bit 1; ON = enabled; OFF = not enabled

1 669 BCM Bit 3; ON = auto (enabled); OFF = manual (not enabled)

1 8821 PM A Unity

1 8837 PM % Unity

1 8822 PM A Unity

1 8838 PM % Unity

1 8823 PM A Unity

1 8839 PM % Unity

1 8825 PM A Unity

1 8841 PM % Unity

1 8842 PM % Hundredths

1 8826 PM A Thousandths

1 8820 PM A Unity

1 8824 PM A Unity

1 8840 PM % Unity

2 8756 PM A Modulo 10,000 format3

1 8827 PM A Unity

1 8828 PM A Unity

1 8829 PM A Unity

1 8831 PM A Unity


1 8830 PM A Unity

1 8750 PM A Unity

1 661 BCM Bit 5; ON = yes, OFF = no

1 8843 PM % Unity

4 8700 PM ASCII text

1 552 BCM Bit 11; ON = not responding, OFF = OK

2; day (byte 2) = 1–31 (add to 1900 to determine the actual year); hour (byte 2) = 0–2359; seconds (byte 2) = 0–59d.




Table 12: MICROLOGIC Type P Trip Unit Standa


810D_LDPU Breaker LDPU in Progress

810DBrkrStatus Breaker Status

810DBrkrTripStat Breaker Trip Unit Status

BCM_SN BCM Serial Number

BkrPos Breaker Position

DT_3Regs Device Clock Date/Time

DTLastTrip D/T of Last Trip

DTPkIAD D/T Peak Demand Current A

DTPkIBD D/T Peak Demand Current B

DTPkICD D/T Peak Demand Current C

DTPkIND D/T Peak Demand Current N

DTPkkVAD D/T Peak Demand Apparent Power

DTPkkVARD D/T Peak Demand Reactive Power

DTPkkWD D/T Peak Demand Real Power

DTResetEnergy D/T Last Reset Accum. Energies

DTResetMinMax D/T Last Reset Min/Max

DTResetPkID D/T Last Reset Peak Dmd Currents

DTResetPkkWD D/T Last Reset Peak Dmd Power

EnableCloseBkr Remote Closing Enabled

EnableOpenBkr Remote Opening Enabled

EnableRemCtrl Remote Control Enabled

GFAlarmStatus GF Alarm Status

GFPreAlarmStatus GF Alarm Pre-Alarm Status

Hz Frequency

IA Current A

IA_PCT Current A % Load

IAD Demand Current A

IAvg Current Avg

IB Current B

IB_PCT Current B % Load

IBD Demand Current B

IC Current C

IC_PCT Current C % Load

ICD Demand Current C

IG Current G

IG_PCT Current G % Load

IG_PCT_VIGI Current G (VIGI) % Load

IG_VIGI Current G (VIGI)

1. For register entries that are not listed, please refer to the MIC2. 3-register date/time format: register 1: month (byte 1) = 1

register 2: year (byte 1) = 0–1register 3: minutes (byte 1) =

Note: Bits 14 and 15 of the month/day register must be mask3. Power factor format: –1 to –999 for lagging power factors, 100

4. Modulo 10,000 format: 1 to 4 sequential registers. Each regisResult is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1.

rd Quantities

Number of Registers1 Register1 Module1 Units1 Scale/Bitmask1

1 8862 PM Scaling N/A

1 661 BCM Bit 0; ON = closed, OFF = open

1 661 BCM Bit 2; ON = tripped; OFF = not tripped

4 516 BCM ASCII text

1 661 CCMBit 8 = disconnectedBit 9 = connectedBit 10 = test position



3 3005 MM 3-register date/time format2








3 9010 PM 3-register date/time format2





1 669 BCMBit 3; ON = auto (enabled); OFF = manual (not enabled)

1 8860 PM Bit 0; ON = active; OFF = inactive


1 1054 MM Hz Tenths

1 1016 MM A Unity

1 8837 PM % Unity

1 2200 MM A Unity

1 1027 MM A Unity

1 1017 MM A Unity

1 8838 PM % Unity

1 2201 MM A Unity

1 1018 MM A Unity

1 8839 PM % Unity

1 2202 MM A Unity

1 1021 MM A Unity

1 8841 PM % Unity

1 8842 PM % Hundredths


ROLOGIC device type register list. Contact your local sales representative.–12; day (byte 2) = 1–3199 (add to 1900 to determine the actual year); hour (byte 2) = 0–23

0–59; seconds (byte 2) = 0–59ed.0 for unity power factor 1.000, and 1 to 999 for leading power factors.

ter is Modulo 10,000 (range = –9,999 to +9,999). Range is zero to 9,999,999,999,999,999.

29


30

IMax Current Max Present

IN Current N

IN_PCT Current N % Load

IND Demand Current N

IUnbalA Current Unbalance A

IUnbalAlrm Current Unbalance Alarm Status

IUnbalB Current Unbalance B

IUnbalC Current Unbalance C

IUnbalPreAlrm Current Unbalance Pre-Alarm Status

IUnbalW Current Unbalance Worst

kVAA Apparent Power A

kVAB Apparent Power B

kVAC Apparent Power C

kVAD Demand Apparent Power (KVAD)

kVAD_PkkVARD KVA Dmd Coincident w/Peak KVAR Dmd

kVAD_PkkWD KVA Dmd Coincident w/Peak KW Dmd

kVAHr Apparent Energy

kVARA Reactive Power A

kVARB Reactive Power B

kVARC Reactive Power C

kVARD Demand Reactive Power (KVARD)

kVARD_PkkVAD KVAR Dmd Coincident w/Peak KVA Dmd

kVARD_PkkWD KVAR Dmd Coincident w/Peak KW Dmd

kVARHr Reactive Energy

kVARHr_I Reactive Energy Into the Load

kVARHr_O Reactive Energy Out of the Load

kVARTtl Reactive Power Total

kVATtl Apparent Power Total

kWA Real Power A

kWB Real Power B

kWC Real Power C

kWD Demand Real Power (KWD)

kWD_PkkVAD KW Dmd Coincident w/Peak KVA Dmd

kWD_PkkVARD KW Dmd Coincident w/Peak KVAR Dmd

kWHr Real Energy

kWHr_I Real Energy Into the Load

kWHr_O Real Energy Out of the Load

kWTtl Real Power Total

LDPUValue Long Delay Pickup Value

LSCurrAlrm Load Shed Current Alarm Status

LSCurrPreAlrm Load Shed Current Pre-Alarm Status




register 2: year (byte 1) = 0–register 3: minutes (byte 1) =

Note: Bits 14 and 15 of the month/day register must be mask

3. Power factor format: –1 to –999 for lagging power factors, 1004. Modulo 10,000 format: 1 to 4 sequential registers. Each regis

Result is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1.

1 1020 MM A Unity

1 1019 MM A Unity

1 8840 PM % Unity

1 2203 MM A Unity

1 1028 MM % Tenths


1 1029 MM % Tenths

1 1030 MM % Tenths

1 8863 PM Bit 0; ON = active, OFF = inactive

1 1032 MM % Tenths

1 1042 MM kVA Unity

1 1043 MM kVA Unity

1 1044 MM kVA Unity

1 2236 MM kVA Unity

1 2235 MM kVA Unity

1 2229 MM kVA Unity

4 2024 MM kVAH Modulo 10,000 format4

1 1038 MM kVAR Unity






4 2004 MM kVARH Modulo 10,000 format4




1 1045 MM kVA Unity

1 1034 MM kW Unity

1 1035 MM kW Unity

1 1036 MM kW Unity

1 2224 MM kW Unity

1 2240 MM kW Unity

1 2234 MM kW Unity

4 2000 MM kWH Modulo 10,000 format4



1 1037 MM kW Unity

2 8756 PM A Modulo 10,000 format4



rd Quantities


ROLOGIC device type register list. Contact your local sales representative.–12; day (byte 2) = 1–31

199 (add to 1900 to determine the actual year); hour (byte 2) = 0–23 0–59; seconds (byte 2) = 0–59ed.

0 for unity power factor 1.000, and 1 to 999 for leading power factors.ter is Modulo 10,000 (range = –9,999 to +9,999). Range is zero to 9,999,999,999,999,999.




LSPwrAlrm Load Shed Power Alarm Status

LSPwrPreAlrm Load Shed Power Pre-Alarm Status

M2C_M6CR1Status Relay Module R1 Status






MaxHz Max Frequency

MaxIA Max Current A

MaxIAvg Max Current Avg

MaxIB Max Current B

MaxIC Max Current C

MaxIG Max Current G

MaxIG_VIGI Max Current G (VIGI)

MaxIN Max Current N

MaxIUnbalA Max Current Unbalance A

MaxIUnbalB Max Current Unbalance B

MaxIUnbalC Max Current Unbalance C

MaxIUnbalW Max Current Unbalance Worst

MaxkVAA Max Apparent Power A

MaxkVAB Max Apparent Power B

MaxkVAC Max Apparent Power C

MaxkVARA Max Reactive Power A

MaxkVARB Max Reactive Power B

MaxkVARC Max Reactive Power C

MaxkVARTtl Max Reactive Power Total

MaxkVATtl Max Apparent Power Total

MaxkWA Max Real Power A

MaxkWB Max Real Power B

MaxkWC Max Real Power C

MaxkWTtl Max Real Power Total

MaxPFA Max Power Factor A

MaxPFB Max Power Factor B

MaxPFC Max Power Factor C

MaxPFTtl Max Power Factor Total

MaxVAB Max Voltage A-B

MaxVAN Max Voltage A-N

MaxVBC Max Voltage B-C

MaxVBN Max Voltage B-N

MaxVCA Max Voltage C-A







Result is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1.



1 8857 PM Bit 0; ON = on; OFF = off






1 1654 MM Hz Tenths

1 1616 MM A Unity

1 1627 MM A Unity

1 1617 MM A Unity

1 1618 MM A Unity

1 8831 PM A Unity


1 1619 MM A Unity

1 1628 MM % Tenths

1 1629 MM % Tenths

1 1630 MM % Tenths

1 1632 MM % Tenths

1 1642 MM kVA Unity

1 1643 MM kVA Unity

1 1644 MM kVA Unity





1 1645 MM kVA Unity

1 1634 MM kW Unity

1 1635 MM kW Unity

1 1636 MM kW Unity

1 1637 MM kW Unity

1 1646 MM PF format3




1 1600 MM V Unity

1 1603 MM V Unity

1 1601 MM V Unity

1 1604 MM V Unity

1 1602 MM V Unity

rd Quantities



0–59; seconds (byte 2) = 0–59ed.


31


32

MaxVCN Max Voltage C-N

MaxVLLAvg Max Voltage L-L Avg

MaxVLNAvg Max Voltage L-N Avg

MaxVUnbalAB Max Voltage Unbalance A-B

MaxVUnbalAN Max Voltage Unbalance A-N

MaxVUnbalBC Max Voltage Unbalance B-C

MaxVUnbalBN Max Voltage Unbalance B-N

MaxVUnbalCA Max Voltage Unbalance C-A

MaxVUnbalCN Max Voltage Unbalance C-N

MaxVUnbalLLW Max Voltage Unbalance L-L Worst

MaxVUnbalLNW Max Voltage Unbalance L-N Worst

MinHz Min Frequency

MinIA Min Current A

MinIAvg Min Current Avg

MinIB Min Current B

MinIC Min Current C

MinIN Min Current N

MinIUnbalA Min Current Unbalance A

MinIUnbalB Min Current Unbalance B

MinIUnbalC Min Current Unbalance C

MinIUnbalW Min Current Unbalance Worst

MinkVAA Min Apparent Power A

MinkVAB Min Apparent Power B

MinkVAC Min Apparent Power C

MinkVARA Min Reactive Power A

MinkVARB Min Reactive Power B

MinkVARC Min Reactive Power C

MinkVARTtl Min Reactive Power Total

MinkVATtl Min Apparent Power Total

MinkWA Min Real Power A

MinkWB Min Real Power B

MinkWC Min Real Power C

MinkWTtl Min Real Power Total

MinPFA Min Power Factor A

MinPFB Min Power Factor B

MinPFC Min Power Factor C

MinPFTtl Min Power Factor Total

MinVAB Min Voltage A-B

MinVAN Min Voltage A-N

MinVBC Min Voltage B-C

MinVBN Min Voltage B-N







Result is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1.

1 1605 MM V Unity

1 1606 MM V Unity

1 1607 MM V Unity

1 1608 MM % Tenths

1 1611 MM % Tenths

1 1609 MM % Tenths

1 1612 MM % Tenths

1 1610 MM % Tenths

1 1613 MM % Tenths

1 1614 MM % Tenths

1 1615 MM % Tenths

1 1354 MM Hz Tenths

1 1316 MM A Unity

1 1327 MM A Unity

1 1317 MM A Unity

1 1318 MM A Unity

1 1319 MM A Unity

1 1328 MM % Tenths

1 1329 MM % Tenths

1 1330 MM % Tenths

1 1332 MM % Tenths

1 1342 MM kVA Unity

1 1343 MM kVA Unity

1 1344 MM kVA Unity





1 1345 MM kVA Unity

1 1334 MM kW Unity

1 1335 MM kW Unity

1 1336 MM kW Unity

1 1337 MM kW Unity





1 1300 MM V Unity

1 1303 MM V Unity

1 1301 MM V Unity

1 1304 MM V Unity

rd Quantities



199 (add to 1900 to determine the actual year); hour (byte 2) = 0–23 0–59; seconds (byte 2) = 0–59ed.





MinVCA Min Voltage C-A

MinVCN Min Voltage C-N

MinVLLAvg Min Voltage L-L Avg

MinVLNAvg Min Voltage L-N Avg

MinVUnbalAB Min Voltage Unbalance A-B

MinVUnbalAN Min Voltage Unbalance A-N

MinVUnbalBC Min Voltage Unbalance B-C

MinVUnbalBN Min Voltage Unbalance B-N

MinVUnbalCA Min Voltage Unbalance C-A

MinVUnbalCN Min Voltage Unbalance C-N

MinVUnbalLLW Min Voltage Unbalance L-L Worst

MinVUnbalLNW Min Voltage Unbalance L-N Worst

NominalCurrent Breaker Nominal Current

OverFreqAlrm Over Frequency Alarm Status

OverFreqPreAlrm Over Frequency Pre-Alarm Status

OverIAAlrm Over IA Demand Alarm Status

OverIAPreAlrm Over IA Demand Pre-Alarm Status

OverIBAlrm Over IB Demand Alarm Status

OverIBPreAlrm Over IB Demand Pre-Alarm Status

OverICAlrm Over IC Demand Alarm Status

OverICPreAlrm Over IC Demand Pre-Alarm Status

OverINAlrm Over IN Demand Alarm Status

OverINPreAlrm Over IN Demand Pre-Alarm Status

OverVoltAlrm Over Voltage Alarm Status

OverVoltPreAlrm Over Voltage Pre-Alarm Status

PF_PkkVAD PF Coincident w/Peak KVA Demand

PF_PkkVARD PF Coincident w/Peak KVAR Demand

PF_PkkWD PF Coincident w/Peak KW Demand

PFA Power Factor A

PFB Power Factor B

PFC Power Factor C

PFTtl Power Factor Total

PhaRotAlrm Phase Rotation Alarm Status

PkIAD Peak Demand Current A

PkIBD Peak Demand Current B

PkICD Peak Demand Current C

PkIND Peak Demand Current N

PkkVAD Peak Demand Apparent Power (KVAD)

PkkVARD Peak Demand Reactive Power (KVARD)

PkkWD Peak Demand Real Power (KWD)

PredkVAD Predicted KVA Demand







Result is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1.

1 1302 MM V Unity

1 1305 MM V Unity

1 1306 MM V Unity

1 1307 MM V Unity

1 1308 MM % Tenths

1 1311 MM % Tenths

1 1309 MM % Tenths

1 1312 MM % Tenths

1 1310 MM % Tenths

1 1313 MM % Tenths

1 1314 MM % Tenths

1 1315 MM % Tenths

1 8750 PM A Unity





















1 2204 MM A Unity

1 2205 MM A Unity

1 2206 MM A Unity

1 2207 MM A Unity

1 2237 MM kVA Unity


1 2225 MM kW Unity

1 2238 MM kVA Unity

rd Quantities



0–59; seconds (byte 2) = 0–59ed.


33


34

PredkVARD Predicted KVAR Demand

PredkWD Predicted KW Demand

R1OpsCounter Relay 1 Operations Counter






ReadyToClose Breaker Ready to Close

RevPwrAlrm Reverse Power Alarm Status

RevPwrPreAlrm Reverse Power Pre-Alarm Status

TimeToTrip Time Remaining to LT Trip

TU_BATT_PCT Trip Unit % Battery

TU_SN Trip Unit Serial Number

TUCommStatus Trip Unit Internal Comms Status

UnderFreqAlrm Under Frequency Alarm Status

UnderFreqPreAlrm Under Frequency Pre-Alarm Status

UnderVoltAlrm Under Voltage Alarm Status

UnderVoltPreAlrm Under Voltage Pre-Alarm Status

VAB Voltage A-B

VAN Voltage A-N

VBC Voltage B-C

VBN Voltage B-N

VCA Voltage C-A

VCN Voltage C-N

VigiAlarm Vigi Alarm Status

VigiPreAlrm Vigi Pre-Alarm Status

VLLAvg Voltage L-L Avg

VLNAvg Voltage L-N Avg

VUnbalAB Voltage Unbalance A-B

VUnbalAlrm Voltage Unbalance Alarm Status

VUnbalAN Voltage Unbalance A-N

VUnbalBC Voltage Unbalance B-C

VUnbalBN Voltage Unbalance B-N

VUnbalCA Voltage Unbalance C-A

VUnbalCN Voltage Unbalance C-N

VUnbalLLW Voltage Unbalance L-L Worst

VUnbalLNW Voltage Unbalance L-N Worst

VUnbalPreAlrm Voltage Unbalance Pre-Alarm Status





Note: Bits 14 and 15 of the month/day register must be mask3. Power factor format: –1 to –999 for lagging power factors, 1004. Modulo 10,000 format: 1 to 4 sequential registers. Each regis

Result is [R4*10,000^3 + R3*10,000^2 + R2*10,000^1] + R1.


1 2226 MM kW Unity

1 9081 PM Unity

1 9082 PM Unity

1 9083 PM Unity

1 9084 PM Unity

1 9085 PM Unity

1 9086 PM Unity

1 661 BCM Bit 5; ON = yes, OFF = no



2 8865 PM Seconds Tenths

1 8843 PM % Unity

4 8700 PM ASCII text

1 552 BCM Bit 11; ON = not responding; OFF = OK





1 1000 MM V Unity

1 1003 MM V Unity

1 1001 MM V Unity

1 1004 MM V Unity

1 1002 MM V Unity

1 1005 MM V Unity



1 1006 MM V Unity

1 1007 MM V Unity

1 1008 MM % Tenths


1 1011 MM % Tenths

1 1009 MM % Tenths

1 1012 MM % Tenths

1 1010 MM % Tenths

1 1013 MM % Tenths

1 1014 MM % Tenths

1 1015 MM % Tenths


rd Quantities



199 (add to 1900 to determine the actual year); hour (byte 2) = 0–23 0–59; seconds (byte 2) = 0–59ed.0 for unity power factor 1.000, and 1 to 999 for leading power factors.ter is Modulo 10,000 (range = –9,999 to +9,999). Range is zero to 9,999,999,999,999,999.




Table 13: MICROLOGIC

Error Code Description

4500 An attempt wasnot enabled; ORAn attempt wasnot enabled.

4608 Comms error wor more sub-devActivity Log for

APPENDIX B—MICROLOGIC TRIP UNIT ERROR CODES

Figure 13: A

Table 13 shows the most common error codes that occur for the MICROLOGIC Trip Unit in SMS. The error code number (but not the description) displays in the SMS Activity Log.

The sample Activity Log in Figure 13 illusrates an error 4500 condition. Note that both the trip unit and BCM have lost communication.

Trip Unit Error Codes in SMS

Solution

made to close, but remote close was

made to open, but remote open was

Enable the desired control from the SMS control output feature.

ith a sub-device within the trip unit system. One ices are not communicating. See the SMS

details.

The Activity Log lists the sub-device that failed. Use this information and read the Troubleshooting section for details.

ctivity Log illustration

35


36

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




APPENDIX D—COMMUNICATIONS CONSIDERATIONS

The following tables show the maximum distances of the communications link at different baud rates. The maximum distances are measured from the PC to the farthest device on the communications link.

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.

Table 15: Maximum Distances for 4-Wire Bus Topologies (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)

Table 16: Maximum Distances for 2-Wire Bus Topologies (MODBUS, Jbus devices)

Maximum Distances

Baud Rate 1–8 Devices1 9–16 Devices1

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.

37


38

Comm

BreakCommModu

24 Vd

Groun

+24

Vd

c

Gro

un

d

Cra

Bl

E1 E2

BreakerSecondaryConnections

PrimaryBreakerDisconnect(top)

Current

Figure 14: MICROLOGIC Sys

Figure 14 illustrates the communications wiring for the MICROLOGIC trip unit system.

F2+ F1– 24 Vdc #2(optional, but recommended)

UC3

ProtectionModule

MeterModule

erunication

le

Out–

Out+

In–

In+

c

dO

ut–

Ou

t+

In–

In+

Peer-to-PeerInternalCommunication

Trip Unit

dle Communication Module

ack Red White Green

E3 E4 E5 E6

+24 V

Ground

Previous Device

Next Device

Voltage pickup

PrimaryBreakerDisconnect(bottom)

Shield

+24 V

Ground

Sensor

Previous Device

Next Device

(Black)

(Red)

(White)

(Green)

IR

tem Communication Wiring


63220-080-200September 2000

© 2000 Schneider Electric All R

INDEX

Aaccumulated energy 19address

for the MICROLOGIC trip unit, illustration 8Address sync push button 6, 26advanced topics 21alarms

levels (severities)described 10

pre-assigned 11setup 9

alternate (CM2) sign convention 22Appendix A—Standard Quantities 28Appendix B—MICROLOGIC Trip Unit Error

Codes 35Appendix C—SMS Table Support 36Appendix D—Communications Considerations

37architecture

trip unit 3

Bbaud rate (from the HMI) 5BCM (Modbus breaker communication module)

described 2block interval demand 18

CCCM (cradle communication module)

described 2–3changing the demand current 18changing the demand power 19changing the demand power method or interval

18changing the VAR and power factor sign conven-

tion 21checklist

hardware setup 5CM2 sign convention 22CM2000 Circuit Monitors

firmware version 1CM4000

communication through 5communication

(RS-485 Modbus RTU) 4link (peer-to-peer protocol) 3with SMS

types 4communications considerations 37communications parameters

setting 6composite device

defined 2

ights Reserved

control outputserrors 13using 13

cradle communication module (CCM) 2described 3

custom and standard quantities 9

Ddate/time

changing via HMI 24synchronization 23via Modbus master device 24

default alarm level characteristics (table) 10demand

current, changing method or interval 18methods 18peak 19predicted 19readings 17

demand power calculation methods 18device

address limitations, mixed-mode daisy chain 2

address, from the HMI 5resets 14setup in SMS 7setup tasks, overview 7

Eenergy readings 19error codes, list 35Ethernet

(MMS)communication 4

(Modbus TCP) communication, CM-4000 with Ethernet Communication Card 4

Ethernet Gatewayfirmware version 1

Ffeatures

MICROLOGIC Electronic Trip Units 1functions

global, analog and digital 9

Hhardware

setup 5HMI

defined 2setting the address, baud rate, and parity 5setting the demand calculation method and

interval 18trip unit 26

human-machine interfacesee HMI 2

39

63220-080-200September 2000

40

IIEC sign convention 22IEEE sign convention 17, 21installation

SMS 7installation and device setup in SMS 7instruction bulletin

MICROLOGIC trip unit 1

Mmetering

capabilities 15module (MM)

described 2real-time 15

MICROLOGICelectronic trip unit instruction bulletin 1

MICROLOGIC Protection Settings table 13min/max

conventions (power factor) 16values 15

mixed-mode daisy chaindevice address limitations 2

MM (trip unit metering module)described 2

Nnonvolatile memory 15, 19

Oon-board alarms

Type P 13

Pparity (from the HMI) 5peak demands 19peer-to-peer protocol 3PM (trip unit protection module)

described 2power factor

changing the sign 21min/max conventions 16

power supplyBCM 3BCM and CCM 5CCM 3isolation of 3trip unit 2

POWERLOGIC Ethernet Gatewayversion 1

POWERLOGIC System Architecture and Appli-cation Guide 4

pre-assigned alarms 11pre-assigned alarms (table) 11pre-assigned alarms and events 11pre-assigned task

device clock reset 13predicted demand 19

Product Registration and Technical Support Con-tacts document 2, 7

protection module (PM)described 2

Qquantities

using 9Quick Starts

SMS 7

Rreal-time metering 15Requirements for Using MICROLOGIC

Devices 1reset

MICROLOGIC trip units 14resetting the device clock 13RS-485 Modbus RTU protocol (trip unit commu-

nication) 4

Sserial (RS-485 Modbus RTU)

communication 4Series 2000 Circuit Monitors

firmware 1setpoints, on-board alarms 13setting communications parameters 6setup

hardware 5setup in SMS 7severity (alarm level) 10sign conventions 17

VAR sign and power factor 21sliding demand 18SMS 1

Activity Log 27, 35Alarm Log 27installation 7online help file 1version requirement 1

standard quantitieslist 28

system architecture 4

TTechnical Support 2, 28time synchronization 23trip unit

address, illustration 8described 2errror codes 35metering module (MM), described 2power supply 2protection module (PM), described 2

trip unit system 2, 8troubleshooting 26Type P Energy Readings (table) 21Type P on-board alarms 13


63220-080-200September 2000

© 2000 Schneider Electric All R

Uusing control outputs 13using custom quantities 9

VVAR and PF sign conventions

changing from HMI 23VAR sign convention

changing 21changing in SMS 22

viewing information in SMS 9

Wwiring distances 37

ights Reserved
41

63220-080-200September 2000

42

micro logic

Documents