Catalog Number 1503 - RockwellAutomation.com · 2015-03-27 · 1 – Logical Mask 0 (Mask Local) ..... 9-2 2 – Logical Mask 1 (Mask ... Data Table Layout ... F-1 . viii Table of

IntelliVAC Plus Contactor Control ModuleCatalog Number 1503

User Manual

Important User Information

Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.

Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice.

If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

Labels may also be on or inside the equipment to provide specific precautions.

Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

Table of Contents

1503-UM054D-EN-P – March 2015

Chapter 1 Product Description

Introduction .............................................................................. 1-1 Scope ...................................................................................... 1-1 Description .............................................................................. 1-2 IntelliVAC Features ......................................................... 1-5 IntelliVAC Base Module Versions .................................. 1-5 Specifications .......................................................................... 1-6 Mounting and Connections .............................................. 1-6 Configuration .................................................................... 1-6 Firmware ........................................................................... 1-6 Mechanical Ratings ........................................................... 1-7 Electrical Ratings .............................................................. 1-8 Operating Ambient Derating based on Altitude ................ 1-9

Chapter 2 Receiving and Storage

Receiving ............................................................................... 2-1 Storage .................................................................................... 2-1

Chapter 3 Installation

General Precautions ................................................................ 3-1 Safety and Codes .................................................................... 3-1 Arrangements .......................................................................... 3-2 Integral to an Allen-Bradley MV Controller .................... 3-2 OEM ................................................................................. 3-2 Control with Solid-State Devices ..................................... 3-3

Chapter 4 Description of Features

Time Delayed Under-Voltage Ridethrough (TDUV) ............. 4-1 TDUV Using Internal Capacitor ............................................. 4-1 TDUV Using External Capacitor ............................................. 4-1 TDUV Programmability .......................................................... 4-2 Contactor Drop-Out Time ........................................................ 4-3 Contactor Close Time .............................................................. 4-4 Re-Closing Control Features ................................................... 4-5

Anti-Kiss ........................................................................... 4-5 Anti-Pumping .................................................................... 4-5 Delayed Restart (General) ................................................. 4-6 Temporary Jog Function ................................................... 4-7 Event Log ................................................................................ 4-8 Coil Currents .......................................................................... 4-11 Open Coil Test ....................................................................... 4-12

ii Table of Contents

1503-UM054D-EN-P – March 2015

Chapter 4 Description of Features (cont.)

Supply Voltages .................................................................... 4-13 Real-Time Clock (RTC) ....................................................... 4-14 Time Zone Selection ............................................................. 4-15 Altitude/Air Pressure Compensation (400A Contactors) ..... 4-16 Operations Counter ............................................................... 4-16 “Master” Counter .................................................................. 4-17 “Operations Since” Counter ................................................. 4-17 “Average Operations” Counter ............................................. 4-20 Configuration ........................................................................ 4-21 HIM ................................................................................. 4-21 RS NetWorx Software ..................................................... 4-21 Dual Power Supply Operation ......................................... 4-21 Power Fail Operation ...................................................... 4-21 Status Display Items ............................................................. 4-22 Status Indicators .............................................................. 4-22 Status LEDs ..................................................................... 4-22 Base Module Faults/Warnings .............................................. 4-23 Healthy Module and Contactor OPEN ............................ 4-23 Healthy Module and Contactor CLOSED ....................... 4-24 Invalid Command Present ............................................... 4-24 Mechanical Latch Fail to Trip ......................................... 4-25 Power up with Contactor CLOSED ................................ 4-25 Contactor Fails to Pick Up .............................................. 4-26 Contactor Drop Out During Hold .................................... 4-27 Long Contactor Drop Out Time ...................................... 4-27 Microcontroller Malfunction ........................................... 4-28 PowerUp with Invalid DIP Switch Configuration ......... 4-28 Contactor Fails to Drop Out ............................................ 4-29 RS485 Communications Error ........................................ 4-29 Undervoltage with a CLOSE Command Preset .............. 4-30 Module/Network Status LEDs ............................................... 4-31 Module Status .................................................................. 4-31 Application Firmware Running ....................................... 4-33 Application Disable Jumper In ........................................ 4-33 Programming Base Unit(s) .............................................. 4-34 No Power From IB or DeviceNet .................................... 4-34 RTC Fail .......................................................................... 4-34 Line Undervoltage ........................................................... 4-35 Line Overvoltage ............................................................ 4-35 Extended Close Time ...................................................... 4-35 DeviceNet Power Loss .................................................... 4-36 MC Altitude Setting Warning ......................................... 4-37 In Reset Mode or Firmware (F/W) Crash ....................... 4-37 POST Failure - RAM ...................................................... 4-37 Application Programming Error - CRC .......................... 4-38 RS485 Communications Fault (IB Fault) ........................ 4-38 Coil Open ........................................................................ 4-38

Table of Contents iii

1503-UM054D-EN-P – March 2015

Chapter 4 Description of Features (cont.) Network Status (DeviceNet) .................................................. 4-39 No Power from IB or DeviceNet ..................................... 4-39 IE Determining Network Baud Rate ............................... 4-40 On-line but not Allocated to Master ................................ 4-40 Normal Operation & Allocated to a Master .................... 4-40 I/O Connection Timed Out ............................................. 4-40 Bus Off or Duplicate DeviceNet Address Detected or Invalid Baud Rate ................................................. 4-40 Module Status (DeviceNet) ............................................ 4-40 No Power from IB or DeviceNet .................................... 4-41 In Standby – Needs Commissioning .............................. 4-41 Normal Operation .......................................................... 4-41 Recoverable Fault ........................................................... 4-42 Unrecoverable Fault ....................................................... 4-42 Device Self Testing ........................................................ 4-42 7-Segment LED Display ...................................................... 4-42 RS485 Incorrect / Duplicate Addresses ......................... 4-43 MC Bad MC #1 .............................................................. 4-44 MC Bad MC #2 .............................................................. 4-44 MC Bad MC #3 .............................................................. 4-44 MC Bad MC #4 .............................................................. 4-44 MC Bad MC #5 .............................................................. 4-44 Incorrect MC RTERM Installed ......................................... 4-44 System Lock-Out State ................................................... 4-45 Bad / No DeviceLogix Program for MC ........................ 4-45 Lost + 15V Rail from IB1 .............................................. 4-45 Watchdog Timeout – Fatal Error ................................... 4-46 Hardware Input Status LEDs ................................................ 4-46 Hardware Output Status LEDs .............................................. 4-46

Chapter 5 IntelliVAC Plus Basic Wiring

IntelliVAC Base Wiring ......................................................... 5-1 Fuse Protection ................................................................ 5-1 Grounding ............................................................................... 5-2 Connections ............................................................................ 5-2 Control Power .................................................................. 5-2 Status Relays .................................................................... 5-2 Interface Connections ............................................................. 5-3 Wiring Guidelines Electrically Held Contactors .................... 5-4 Two-Wire Control .............................................................. 5-4 Three-Wire Control ............................................................ 5-5 Wiring Guidelines Mechanical Latch Contactors ................... 5-7 Mechanical Latch Contactors ................................................. 5-8 Capacitor Trip .................................................................. 5-8 Time Delay Undervoltage ....................................................... 5-9

iv Table of Contents

1503-UM054D-EN-P – March 2015

Chapter 6 Wiring

Wiring (MC) ........................................................................... 6-1 Pre Configured Logic Mode ............................................. 6-1 Wiring Diagrams for: – Full Voltage Reversing .................................................. 6-3 – SMC .............................................................................. 6-4 – SMC with PFCC ........................................................... 6-6 – Reduced Voltage Reactor .............................................. 6-8 Incomplete Sequence Timer ................................... 6-9 Transition Timer ..................................................... 6-9 – Reduced Voltage Auto Transformer ........................... 6-10 Incomplete Sequence Timer ................................. 6-11 Transition Timer ................................................... 6-11

Chapter 7 Communications

Communications ..................................................................... 7-1 RS232 Communications ................................................... 7-1 RS485 Communications ................................................... 7-1 DeviceNet Communications ................................................... 7-2 DeviceNet Baud Rates ..................................................... 7-2 AutoBaud Rate ................................................................. 7-2 DeviceNet MAC ID ......................................................... 7-3 DeviceNet Profile ............................................................. 7-4 Compatibility with IntelliCENTER ................................. 7-4 DeviceNet Communications Loss .................................... 7-4 Hold State ......................................................................... 7-5 Mask Network .................................................................. 7-5 Mask Device Logix .......................................................... 7-5 Reset State ........................................................................ 7-5 Mask HIM/PC .................................................................. 7-6 Multi-Contactor Control Bus (MC) .................................. 7-6

Chapter 8 Configurations

Configurations ........................................................................ 8-1 IB Board DIP Switches .................................................... 8-1 Altitude ............................................................................. 8-1 Contactor Drop Out Time ....................................................... 8-2 Contactor Type ........................................................................ 8-2 Time Delay Undervoltage Enable (TDUV) ..................... 8-3 Time Delay Undervoltage Configuration (TDUV) .......... 8-4 Power-up Safety ............................................................... 8-4 Future Use ........................................................................ 8-5 MC Board DIP Switches .................................................. 8-5

Table of Contents v

1503-UM054D-EN-P – March 2015

Chapter 8 Configurations (cont.)

MC RS485 Addressing ........................................................... 8-6 RS485 Termination Resistor .................................................. 8-6 Programming .......................................................................... 8-7 IntelliVAC Base Module Bootloader ............................... 8-7 IntelliVAC Base Module Application Code .................... 8-7 IntelliVAC Plus Bootloader ............................................. 8-7 Programming the IntelliVAC Base Module ..................... 8-8 Programming the IB using an IE Board ........................... 8-8 Flashing IntelliVAC Base Module Using Bootloader .... 8-10 Verify Current Firmware ................................................ 8-11 Upload New Firmware ................................................... 8-12 Power on Reset IntelliVAC ............................................ 8-14 Updating IntelliVAC Plus Application Code ................. 8-14 Updating the IntelliVAC Plus using ControlFlash ......... 8-15 Flashing FW using Control Flash ................................... 8-15 IE/IB Firmware Revisions .............................................. 8-17

Chapter 9 DeviceLogix

Common Acronyms and Short Forms .................................... 9-1 Logical Masks .................................................................. 9-1 Important Terms for Logical Masks ................................. 9-1 Direct Commands ............................................................. 9-2 1 – Logical Mask 0 (Mask Local) ..................................... 9-2 2 – Logical Mask 1 (Mask Network) ................................ 9-2 3 – Logical Mask 2 (Mask DeviceLogix) ......................... 9-2 4 – Logical Mask 3 (Mask HIM/PC) ................................ 9-2 DeviceLogix ........................................................................... 9-3 What is DeviceLogix ........................................................ 9-3 Inputs and Outputs ........................................................... 9-3 Input and Output Bits ....................................................... 9-3 Local Function Block Logic ............................................. 9-4 RSNetworx for DeviceLogix Operating Modes ............... 9-5 DeviceLogix Operating Modes ........................................ 9-5 Launching the DeviceLogix Editor ................................... 9-6 DeviceLogix Function Block Elements ......................... 9-10 I/O Components ............................................................. 9-10 Digital Input Point (DIP) ................................................. 9-10 Digital Output Point (DOP) ............................................ 9-11 DLX Function Blocks .................................................... 9-11 Boolean Function Blocks ....................................................... 9-12 Bistable Function Blocks ................................................ 9-12 Timers ............................................................................. 9-13 Pulse Timer ..................................................................... 9-13 On Delay Timer ............................................................... 9-14 Off Delay Timer .............................................................. 9-15 Up Counter ...................................................................... 9-16

vi Table of Contents

1503-UM054D-EN-P – March 2015

Chapter 9 DeviceLogix (cont.) Up Down Counter ........................................................... 9-17 Offline Operations ........................................................... 9-18 Online Operations ........................................................... 9-18 Go Online ........................................................................ 9-19 Change Function Block Attribute Values ....................... 9-19 Online Animation ............................................................ 9-20 Change Logic .................................................................. 9-20 Entering Logic Into the Editor .............................................. 9-21 Add a Logical Element .................................................... 9-21 Assume Data Available .................................................. 9-22 Assume Data Available (Alternative) ............................. 9-23 Forcing ............................................................................ 9-23 Forcing Inputs ................................................................. 9-24 Forcing Outputs ............................................................... 9-25 Dual Forcing Inputs ......................................................... 9-25 Network Boolean Inputs.................................................. 9-32 Hardware Boolean Outputs ............................................. 9-33 Network Boolean Outputs ............................................... 9-33 Customized Logic .................................................................. 9-35

Chapter 10 Troubleshooting

IB Operational Troubleshooting Procedures ........................ 10-1 IE Operational Troubleshooting Procedures ......................... 10-4 MC Operational Troubleshooting Procedures ...................... 10-9 DeviceNet Troubleshooting Procedures ............................. 10-10

Appendix A Fuse Protection .................................................................... A-1

Appendix B Parameters ............................................................................ B-1

Introduction ............................................................................ B-1 Interpreting Bit-Encoded Parameters .............................. B-1 Parameter Numbers ............................................................... B-3 Control Parameters ................................................................ B-3 Communication Parameters ................................................. B-41 Configuration Parameters .................................................... B-49 Diagnostics Parameters ........................................................ B-86

Appendix C Maintenance .......................................................................... C-1

Introduction ............................................................................ C-1 Main Input Fuse .............................................................. C-1 RTC Battery ........................................................................... C-2

Table of Contents vii

1503-UM054D-EN-P – March 2015

Appendix D Spare Parts ........................................................................... D-1

Appendix E DeviceNet Information ......................................................... E-1

Identify Object ................................................................ E-1 DeviceNet Object ............................................................ E-2 Explicit Connection ......................................................... E-4 Parameter Object ............................................................. E-5 Common Service ............................................................. E-6 Output (Consumed) Assembly & Layout ........................ E-7 Input (Produced) Assembly & Layout ............................ E-8 DNI (IE) Object ................................................................ E-9 IntelliVAC Base Module Object ................................... E-11 PCP Object (Motor Control Center Object) .................. E-15 Data Table Layout ......................................................... E-16

Appendix F IntelliVAC Plus Firmware ...................................................... F-1

Introduction ............................................................................. F-1

viii Table of Contents

1503-UM054D-EN-P – March 2015

Chapter 1

1503-UM054D-EN-P – March 2015

Product Description

Introduction This document contains information for the Allen-Bradley Bulletin 1503VC IntelliVAC™ Plus control module. The Bulletin 1503VC is used to control the Allen-Bradley Bulletin 1502 vacuum contactors that are a significant component of the Bulletin 1500/1900 CENTERLINE Medium Voltage Motor Controllers and Bulletin 7000 Medium Voltage Drives offered by Rockwell Automation.

The IntelliVAC Plus is an enhanced version of the IntelliVAC control

module which is typically provided as the standard means of controlling the vacuum contactors in medium voltage controllers and drives. IntelliVAC Plus may be supplied with IntelliVAC Multi-Contactor (MC) modules in control schemes that require more than one vacuum contactor. In this case there will be one IntelliVAC Plus unit and up to four IntelliVAC MC units.

An IntelliVAC Plus control module may also be provided as a loose

component, for application with a Bulletin 1502 contactor by a third party (OEM).

Scope This document applies to the following equipment:

Description Series

IntelliVAC Plus Module A IntelliVAC Multi-Contactor (MC) E

Refer to the following publications 1503-UM05_ _-EN-P for

information related to the following IntelliVAC equipment. Description Series Publication

IntelliVAC Module A to B 1503-UM051_-EN-P IntelliVAC Module C to D 1503-UM052_-EN-P IntelliVAC Module E (current) 1503-UM053_-EN-P

1-2 Product Description

1503-UM054D-EN-P – March 2015

Description IntelliVAC Plus is an efficient and flexible solution for controlling

medium voltage vacuum contactors used in medium voltage motor control, feeder and drive applications. IntelliVAC Plus may be used to control both 400 and 800 Amp contactors. Both electrically held and mechanically latched contactor types can be controlled with IntelliVAC Plus.

Figure 1.1 – IntelliVAC Plus Contactor Control Module

Figure 1.2 – IntelliVAC Plus Contactor Control Module (cover removed)

Product Description 1-3

1503-UM054D-EN-P – March 2015

Figure 1.3 – IntelliVAC Plus Base Model


1503-UM054D-EN-P – March 2015

Description (cont.)

BASE MODULE

IntelliVAC MODULE I/O

TOP VIEW

CUSTOMER I/O

MC

BASE CONNECTOR

ENHANCED CONNECTOR

Base/EnhancedConnector

CLOSE/HOLD COILS

CLOSE/OPEN COMMANDS

TDUV CAP

Inputs

8 IN

(9 p

in)

DIP

SW

ITC

HE

S (8po

s x 2)

CONTACTOR/MODULE STATUS

OUTPUTS

AC INPUT

ENHANCEDMODULE

RS485(4 pins)

RS232 header

DE

VIC

EN

ET

(5pin

)

COMMUNICATIONS

MCC ADDRESS& FAULTS

7 Sg

. LE

DD

isplay

(00 - 63)

DeviceNetAddress

(Development Use Only)

Status LED's(x12)

+ 2 ON BASE

DeviceNet

COMMUNICATIONS

STANDOFF(X3)

Ou

tputs2 O

UT

(4pin)

S2 S1(MSB) (LSB)

Figure 1.4 – IntelliVAC Plus I/O Layout


1503-UM054D-EN-P – March 2015

A wide range of supply voltage (110 – 240 V AC 50/60Hz, 110 - 250 V DC) allows implementation in multiple applications

Consistent vacuum contactor pick-up time (at a given supply voltage) ensures repeatable performance

Selectable vacuum contactor drop-out time improves coordination with upstream power fuses

Electronic altitude compensation (400 A only) eliminates mechanical compensation required for altitudes above 1,000 meters (800 A contactors include an integral user-friendly altitude adjustment)

Power loss ride-through (TDUV) allows the vacuum contactor to remain closed during short power loss (may require an optional external capacitor, dependant on ride-through time required)

Anti-kiss and anti-pumping protection ensure that the vacuum

contactor close – open sequence occurs as expected, avoiding rapid re-closure due to faulty control devices

Delayed restart protects the vacuum contactor by ensuring that the rated duty cycle is not exceeded

Temporary jog function (electrically held contactors only) allows the motor to be positioned for process set-up

Series A There are two versions of IntelliVAC control. The

first type is used to control vacuum contactors that are electrically held, with a single electrical coil that is economized electronically. The second is used to control mechanically latched vacuum contactors.

Series B There is a single version of IntelliVAC, to control both electrically held and mechanically latched vacuum contactors.

Series C Updated version of the Series B module.

Series D Minor functionality (firmware) enhancements (primarily related to definition and handling of Faults and Warnings).

Series E Revised hardware to allow connection to the IntelliVAC Plus or IntelliVAC MC. Removal of the mini DIN connector for flashing firmware (firmware is now flashed using the IntelliVAC Plus or IntelliVAC MC boards). New input circuits to reduce thermal output and decrease sensitivity to leakage current.

IntelliVAC Features

IntelliVAC Base Module Versions


1503-UM054D-EN-P – March 2015

Refer to IntelliVAC manual 1503-UM053_ _-EN-P for catalog numbers for each version of IntelliVAC.

Any Series C, D or Series E IntelliVAC module can be used to replace a Series A or Series B module. When replacing an older series of IntelliVAC with a newer one, note that the Module and Contactor Status outputs may function differently. Refer to publication 1503-UM051_-EN-P and/or Chapter 5 of this document, and make any necessary changes to the control circuit.

Specifications Mounting and Connections

The IntelliVAC Plus control modules are mounted using two screws (see Figure 1.5). They are typically located in the low voltage control panel of the medium voltage controller (Bulletin 1500/1900, 7700 controllers, in the case of Rockwell Automation). IntelliVAC Plus is interfaced to the Bulletin 1502 vacuum contactors using a “quick” connector, located at the module, a wire harness and “quick” connector at the contactor. Control power and other control circuit connections are similarly achieved with “quick” connectors.

Configuration

The IntellliVAC Plus is easily configured for a wide variety of medium voltage motor and feeder control applications. Configuration can be performed by two methods:

DIP switches located on the IntelliVAC Plus Via DeviceNet and the units parameters page

Bulletin 1500/1900, 7700 controllers are shipped with IntelliVAC Plus pre-configured for the required application. Please refer to the documents provided with the order.

Firmware

The IntelliVAC Plus has firmware stored in Flash EEPROM; therefore, this may be updated in the field (if necessary). The board firmware is updated via either the multi-contactor board, or the RS-485 ports on the IntelliVAC Plus board. For further information regarding programming of firmware see Chapter 8 “Configuration Programming”.

I M P O R T A N TI M P O R T A N T


1503-UM054D-EN-P – March 2015

Through RSNetWorx, IntelliVAC Plus firmware version can be viewed in device general page and base module version can be viewed in parameter page. Series Letter Firmware Version A Version 2.003 B Version 2.003 C Version 2.003 D Version 3.001 or 3.002 E Version 4.001

This firmware is not compatible with any other Series letter modules. Refer to IntelliVAC manual 1503-UM053_-EN-P for part numbers of the various series of modules. The Series Letter of the module is printed on the label on the cover of the module, beside the part number.

Table 1.A – Mechanical Ratings

Temperature Operating: 0…60°C ambient at the control module

Non-Operating: -40…85°C

Altitude -1000…5000 m

Pollution Pollution level II (as defined by UL 840 and IEC 60664-1)

Humidity 95% non-condensing

Shock and Vibration (Operational)

Shock – 15 g peak, 11 milliseconds

Vibration – 10…57 Hz, 0.015 in. displacement peak to peak

– 57…150 Hz, 2.5 g acceleration

Ambient temperature is derated at altitudes above 1000 m (3300 ft). Please refer to Table 1.C.


1503-UM054D-EN-P – March 2015

Specifications (cont.) Table 1.B – Electrical Ratings

Main Input Voltage (L1 to L2/N)

AC – 110 to 240 V rms, +10/-15%, 47 to 63 Hz

DC – 110 to 250 V, +10/-15%

Main Input Current (L1 to L2/N)

Description Contactor Ratings

(Amps) Control Voltage

(AC or DC) AC Rating DC Rating

Inrush Current 400/800 120/240 25 A peak (1/2 cycle)

25 A peak

Idle Current (Maximum without contactor coil energized)

400/800 120/240 125 mA 35 mA

Hold Current (maximum) 400/800 120/240 300 mA 100 mA

Close Current

(0.2 s)

400 120 4.6 A 3.6 A

240 3.4 A 3.3 A

800 120 11.3 A 4.8 A

240 8.9 A 4.5 A

Trip Current (latch)

(0.2 s)

400 120 7.0 A 3.7 A

240 3.6 A 2.0 A

800 120 7.0 A 3.3 A

240 4.3 A 1.9 A

Command Inputs

AC – 70 to 240 V rms DC – 70 to 250 V Maximum on state current for open or close command:

11mAAC @ 276 V AC, 60Hz, TA = 60°C 2.4mADC @ 276 V DC, TA = 60°C Minimum on state current for open or close command:

2.5mAAC @ 70 V AC, 60Hz, TA = 60°C 1.2 mA @ 68 V DC, TA = 60°C Maximum off state current for open or close command:

1.9 A @ 60 V AC, 60 Hz, TA = 60°C 900 A @ 60 V DC, TA = 60°C

Output Contacts AC – 250 V rms, 5 A, R load; 2 A (reactive), PF = 0.4 DC – 30 V, 5 A, R load; 2 A (reactive), L/R = 7 ms

Standards and Approvals

CE, cULus, CSA, IEC pending

TA = Ambient Temperature Includes idle current. Ensure compatibility of IntelliVAC input ratings with those of circuit components activating these inputs.

Consider means of isolating/loading these signals, as required (using interposing relays or load resistors.) Consult factory for assistance, if needed. The Series C, D and E IntelliVACs are compatible with most PLC outputs, and have been verified with Rockwell Automation OA type 120V triac outputs. See Chapter 3, Wiring Guidelines.

Includes operation of Auxiliary input and 8 discrete inputs. Includes module/Contactor Status contacts as well as 2 discrete output contacts.


1503-UM054D-EN-P – March 2015

5.1 (0.20)

Dimensions in mm (inches)

29.7(1.17)

174.8(6.88)

185.3(7.29)

59.4(2.34)

165.9 (6.53)

5.8 (0.228)2 places

5.1 (0.20)


29.7(1.17)

174.8(6.88)

185.3(7.29)

59.4(2.34)

165.9 (6.53)

5.8 (0.228)2 places

Figure 1.5 – Mechanical Dimensions

Table 1.C – Operating Ambient Derating based on Altitude

Altitude Maximum Operating Ambient at the control module (°C)

-1000…0 60

1…1000 60

1001…2000 58

2001…3000 56

3001…4000 54

4001…5000 52

Derate by 2°C / 1000 m for high altitude operation


1503-UM054D-EN-P – March 2015

Chapter 2

1503-UM054D-EN-P – March 2015

Receiving and Storage Receiving Upon receiving the controller, remove the packing and check for

damage that may have occurred during shipping. Report any damage immediately to the claims office of the carrier.

NOTE: If the IntelliVAC Plus module is an integral component of a

complete MV controller (Bulletin 1500/1900/7700), special receiving and handling instructions will apply. For details, refer to the service manual provided with the equipment.

Storage It is important to consider the following storage requirements if you

are not installing your controller immediately after receiving it. • Store the controller in a clean, dry, dust-free environment. • Storage temperature should be maintained between -40…85°C

(-40… 185°F). • Relative humidity must not exceed 85%, non-condensing.

2-2 Receiving and Storage

1503-UM054D-EN-P – March 2015

Chapter 3

1503-UM054D-EN-P – March 2015

Installation General Precautions In addition to the precautions listed throughout this manual, the

following statements, which are general to the system, must be read and understood.

A T T E N T I O NA T T E N T I O N

The controller contains ESD (electrostatic discharge) sensitive parts and assemblies. Static control precautions are required when installing testing, servicing, or repairing the assembly. Component damage may result if ESD control procedures are not followed. If you are not familiar with static control procedures, refer to applicable ESD protection handbooks.


An incorrectly applied or installed controller can damage components or reduce product life. Wiring or application errors, such as incorrect or inadequate AC supply, or excessive ambient temperatures, may result in malfunction of the system.


Only personnel familiar with the controller and associated machinery should plan or implement the installation, start-up, and subsequent maintenance of the system. Failure to do this may result in personal injury and/or equipment damage.


The Canadian Electrical Code (CEC), National Electrical Code (NEC), or other local codes outline provisions for safely installing electrical equipment. Installation MUST comply with specifications regarding wire type, conductor sizes, branch circuit protection, interlocking and disconnect devices. Failure to do so may result in personal injury and/or equipment damage.

Safety and Codes

3-2 Installation

1503-UM054D-EN-P – March 2015

Arrangements The IntelliVAC Plus is offered in two arrangements, Integral (part of

a Bulletin 1500/1900, 7700 MV controller) or as an OEM component.

Integral to an Allen-Bradley MV Controller The IntelliVAC Plus and IntelliVAC MC are available as primary

components of an Allen-Bradley Bulletin 1500/1900, 7700 MV controller as shown in Figure 3.1.

Figure 3.1 – Typical IntelliVAC Installation within a Bulletin 1500/1900 MV Controller (Shown with optional external capacitor)

OEM

The IntelliVAC may be ordered as an OEM component. This allows the OEM to mount the components in a configuration most suitable to the motor controller equipment layout. Care must be exercised to ensure the IntelliVAC has adequate ventilation provided around it. Refer to Figure 3.2 for mounting the IntelliVAC. A minimum of 1.5 in. (38.1 mm) of free air space be provided between the IntelliVAC and any solid barrier above or below. The OEM is responsible for controller fusing, motor overload protection, control devices (eg. Start/Stop push buttons), and wiring between the IntelliVAC and 1502 vacuum contactor (using optional wire harness). Wiring and mounting for optional items, such as TDUV Capacitor, are also the OEM’s responsibility. Refer to Chapter 5 for basic connections.

Installation 3-3

1503-UM054D-EN-P – March 2015

38.1 (1.50)

38.1 (1.50)

6.4 (0.25)

Additional Modules(as required)

Minimum bottom clearance

Minimum top clearance


Figure 3.2 – Typical Mounting Configurations Note: Adjacent IntelliVAC Plus modules may be mounted with a minimum separation of 6.4 mm (0.25 inches).

Control with Solid-State Devices

If control devices that employ electronic or suppressed output circuits are used in the rung(s) that control the inputs to the IntelliVAC, alternate arrangements may be required. Devices employing transistor or triac output circuits have finite impedance and allow a leakage current to flow in the blocking or off state. Some PLC and I/O modules with relay outputs also have R-C snubber circuits across the contacts to suppress noise generated during contact opening. The impedance of these circuits also allows leakage current to flow when the contacts are open. The high impedance input circuits of the IntelliVAC Plus have been designed to minimize sensitivity to these leakage currents, however, they may be triggered by excessive leakage current or residual terminal voltage, causing unintended operation of the contactor, or maintenance of the closed state when the control signal is removed.

3-4 Installation

1503-UM054D-EN-P – March 2015

It is recommended the user interface with the IntelliVAC Plus using

interposing relays if possible. In the event that the IntelliVAC Plus must be interfaced to a Solid State Output consult Table 3.A for allowable leakage current values.

Table 3.A – Input Circuit Specifications

MOV32

1EC

-+

4TCO

12

11AUX CCO

5

6

L1 L2/NG

+ -

STOPSTARTOVERLOAD

CONTROLPOWERFUSE

*

7 8OPEN

16

15

CONTACTORSTATUS

M

M-INTELLIVAC

M

CAPACITOR(OPTIONA L)

+ -9 10CLOSE

14

13

MODULESTATUS

CONTROL POWER

INPUT POWER

CONFIGURATIONDIP SWITCHES

Figure 3.3 – IntelliVAC Typical Schematic (Electrically Held Vacuum Contactor)

Command Inputs

AC – 70 to 240 V rms DC – 70 to 250 V Maximum on state current for input circuit: 11mAAC @ 276 V AC, 60Hz, TA = 60°C 2.4mADC @ 276 V DC, TA = 60°C Minimum on state current for input circuit: 2.5mAAC @ 74 V AC, 60Hz, TA = 60°C 1.2 mA @ 68 V DC, TA = 60°C Maximum off state current for input circuit: 1.9 A @ 20 V AC, 60 Hz, TA = 60°C 900 A @ 60 V DC, TA = 60°C

Chapter 4

1503-UM054D-EN-P – March 2015

Description of Features

The IntelliVAC Plus incorporates a TDUV feature, which will keep the contactor closed during an input voltage dip or brief power loss. The TDUV time begins, this might be called as ‘low voltage’ protections – see Undervoltage with a CLOSE Command Preset on Page 4-30, once the input line voltage goes <95Vrms just before a Close command is issued or when the input line voltage goes <80Vrms when the Hold cycle is in progress. This feature is implemented in one of two manners:

• TDUV Using Internal Capacitor • TDUV Using External Capacitor


Do not enable the TDUV feature if the input contactor is feeding a PowerFlex 7000 drive with the Safe Torque Off option.

The Basic module has been designed to provide a TDUV based on its internal storage capacitance. The amount of time that it can provide on its own is shown in Table 4.A.

Table 4.A – TDUV without External Capacitor

Control Voltage Max. TDUV Time (seconds)

400A 800A

110/120V 0.2 0.2 220/240V 1.0 1.0

These maximum times are inherent in the design of the Basic module and are programmable up to the maximums in Table 4.A. They are only valid when the TDUV feature is enabled.

This means of providing TDUV will require a capacitor to be used, which, due to its size, will be mounted outside the IntelliVAC Plus module. The maximum ride-through time is shown in Table 4.B

Table 4.B – TDUV with External Capacitor

Control Voltage Max. TDUV Time (seconds)

400A 800A

110/120V 2.0 2.0 220/240V 2.0 2.0

Time Delayed Under-Voltage Ridethrough (TDUV)

TDUV Using Internal Capacitor

TDUV Using External Capacitor

4-2 Description of Features

1503-UM054D-EN-P – March 2015

TDUV Programmability The TDUV settings parameter has the following range/resolution for

400 A and 800 A contactors:

0.2 Sec to Maximum 2.000 Sec. with 1 mSec. resolution

Therefore for a 400A contactor this would be from 0.2 sec to 2.000 sec and for an 800A contactor this would be from 0.2 sec to 2.000 sec. The default value of the TDUV time will be dependant on the TDUV settings from the IntelliVAC Basic module (IB), in the following manner. If the TDUV Configuration is set to disabled (see TDUV Configuration Table 8.D) then the TDUV time will be set to 0.2 Sec. If the TDUV Configuration is set to enabled (see TDUV Configuration Table 8.D) then the TDUV time will be set to the time from the TDUV Hold-up Time sent from the IB DIP switches (0.200, 0.500, 1.000 or 2.000 Sec). This will only occur for the first time, after power up, that the TDUV Configuration bit and TDUV Hold-up Time is read from the Basic module. From then on, the source of the TDUV Hold-up Time will be determined from a parameter that indicates if the source of the TDUV Hold-up Time is derived from the Base module DIP switch or from a DeviceNet setting. The parameter which is used to determine the source of the TDUV Hold-up Time will be set on DeviceNet in the following manner:

‘TDUV Hold-up Time Source = ‘‘IB’ or ‘DeviceNet’

This parameter will affect all five of the IB units in an MC system

This scheme will allow having a TDUV time value from the IB and the IntelliVAC Enhanced Module (IE) units, with both values being visible and a third parameter which indicates which of the two parameters will be used for control of the contactor.

The TDUV data will be available, for each of the five IB units, on DeviceNet in the following manner:

‘IB1 TDUV time = ‘‘0.2 Sec’ to ‘2.000 Sec’ (resolution is 1mS) ‘IB2 TDUV time = ‘‘0.2 Sec’ to ‘2.000 Sec’ (resolution is 1mS) ‘IB3 TDUV time = ‘‘0.2 Sec’ to ‘2.000 Sec’ (resolution is 1mS) ‘IB4 TDUV time = ‘‘0.2 Sec’ to ‘2.000 Sec’ (resolution is 1mS) ‘IB5 TDUV time = ‘‘0.2 Sec’ to ‘2.000 Sec’ (resolution is 1mS)

Default value is 0.2 Sec.

The TDUV Hold-up Time values transferred from the IB units will be available on DeviceNet in the following manner:

Description of Features 4-3

1503-UM054D-EN-P – March 2015

‘IB1 TDUV time DIP setting = ‘‘0.2’ or ‘0.500’ or ‘1.000’ or ‘2.000’ ‘Sec’





Contactor Drop-Out Time Contactor Drop-Out Time is the amount of time that will pass from

when a Close command is removed to the time that the Contactor Auxiliary input indicates that the contactor has opened.

With the IntelliVAC Plus unit the Contactor Drop-Out Time settings will be altered via a parameter which has the following range/resolution:

50 mSec to Maximum 240 mSec. with 1 mSec. resolution

The default value of the Contactor Drop-Out time will be dependant on the Drop out Time settings from the IB unit, in the following manner. The Contactor Drop-Out time will be set to the Contactor Drop-Out time sent from the IB DIP switches (50, 75, 100, 130, 150, 175, 200 or 240 mSec). Furthermore, in Version 4.006, the drop out time is 6ms longer than the values give here if the close command is given through IB. This will only occur for the first time, after power up, that the Contactor Drop-Out Time is read from the IB. From then on, the source of the Contactor Drop-Out Time will be determined from a parameter that indicates if the source of the Contactor Drop-Out Time is taken from the IB DIP switch or from a DeviceNet setting. The parameter which is used to determine the source of the Contactor Drop-Out Time and will be set on DeviceNet in the following manner:

‘Drop-Out Time Source = ‘‘IB’ or ‘DeviceNet’

This parameter will affect all five of the IB units in a MC system

This scheme will allow having a Contactor Drop-Out Time value from the IB and IE unit, with both values being visible and a third parameter which indicates which of the two parameters will be used for control of the contactor.

The Contactor Drop-Out Time will be available, for each of the five (5) IB units, on DeviceNet in the following manner:


1503-UM054D-EN-P – March 2015

‘IB1 Drop-Out Time = ‘ ’50 mSec’ to ‘240 mSec’ (resolution is 1mS) ‘IB2 Drop-Out Time = ‘ ’50 mSec’ to ‘240 mSec’ (resolution is 1mS) ‘IB3 Drop-Out Time = ‘ ’50 mSec’ to ‘240 mSec’ (resolution is 1mS) ‘IB4 Drop-Out Time = ‘ ’50 mSec’ to ‘240 mSec’ (resolution is 1mS) ‘IB5 Drop-Out Time = ‘ ’50 mSec’ to ‘240 mSec’ (resolution is 1mS)

The Contactor Drop-Out Time values transferred from the IB units will be available on DeviceNet in the following manner:

‘IB1 Drop-Out Time DIP Setting = ‘‘50’ or ‘75’ or ‘100’ or

‘130’ or ‘150’ or ‘175’ or ‘200’ or ‘240’ ‘Sec’ ‘IB2 Drop-Out Time DIP Setting = ‘‘50’ or ‘75’ or ‘100’ or




‘130’ or ‘150’ or ‘175’ or ‘200’ or ‘240’ ‘Sec’

The IntelliVAC Plus measures the close time of the contactor that it is controlling. This measurement determines the precise time from when a Close command is issued, to the time that the Contactor Auxiliary input status toggles to indicate a closed contactor state. There will be a parameter sent from the IB unit that indicates the close time of the contactor that was closed. The Close Times for all of the five (5) contactors used in an MC system will be available on DeviceNet in the following manner:

‘IB1 Pick Up Time = ‘ ‘000’ to ‘255mS’ (000 indicates contactor

has not been closed yet) ‘IB2 Pick Up Time = ‘ ‘000’ to ‘255mS’ (255 indicates contactor

did not close on last close ‘IB3 Pick Up Time = ‘ ‘000’ to ‘255mS’ command) ‘IB4 Pick Up Time = ‘ ‘000’ to ‘255mS’ ‘IB5 Pick Up Time = ‘ ‘000’ to ‘255mS’

Before a contactor has been commanded to close, this time will be set to 0mS. If a contactor does not close within the close time period, which is programmed as 200mS in the IB unit, then the contactor open routine will be initiated and a ‘Contactor Fails to Pick Up’ warning will be generated, which the IntelliVAC Plus will acknowledge and display (see Table 4.F – IB Fault/Warning Descriptions). The general coil timing for a contactor coil is to provide it with a 200mS close current of a large value and then to decrease the coil current to a lower hold value for the remaining hold

Contactor Close Time


1503-UM054D-EN-P – March 2015

Time. If the contactor did not close within 200mS then there is a major problem and it probably would not pick up any time after that. A contactor should, if it does not have any mechanical or electrical problems, close within 150mS. If a contactor requires longer than 150mS to close, then this is a sign that it is beginning to have problems. This condition, although it does not cause any faults or warnings, will be logged to the Event Log (see Event Log in Chapter 4).

To determine component wear of the contactor over its lifetime, the close time will be monitored as a wear indicator. To perform this measurement the close time will be averaged over the last 5 closures and when the present value has exceeded the table value threshold, then, an extended close time alarm will be annunciated. See Table 4.F – Plus Fault/Warning Description for the warning description and Table 4.G – Contactor Extended Close Times for limits which define an extended close time.

Anti-Kiss

The IntelliVAC Plus has an anti-kiss protection feature. This feature will ensure that the main contacts are closed and sealed before they are allowed to open. The IntelliVAC Plus makes all decisions on whether to open or close the contactor. Once a contactor has been commanded to close, it cannot be commanded to open until it has actually closed first. To determine if the contactor has actually closed, it monitors the contactor Auxiliary input at terminals TB 11/12 (see table 5.B). The IntelliVAC Plus will wait for a ‘contactor closed’ status before issuing an open command, assuming that an active open command has become issued shortly after a close command has been issued. Open and close commands are also available from the DeviceNet network as status bits (see Appendix E for details). The basic rule for this feature is that the removal of the Close command must have at least a 200mS delay from the time that a Close command was initiated, even if the Auxiliary status indicates that the contactor has closed before the 200mS time.

Anti-Pumping

Anti-pumping protection is intended to prevent the contactor from rapid open-close cycling due to an inappropriate or faulty control circuit, a faulty holding coil or control electronics, or the failure of a latch mechanism to engage.

The input control signal is required to toggle before issuing another close command. If the contactor receives a signal to close, and the contactor closes, but immediately opens, the close command will be ignored unless the close command is removed and re-applied.

Re-Closing Control Features


1503-UM054D-EN-P – March 2015

Delayed Restart (General)

The contactors are assigned rated duties, which define how frequently the contactor can be switched on and off. A timer will be used to prevent the contactor from being re-closed until the amount of time has passed, which represents the rated duty of the contactor. This delay is six (6) seconds for the electrically held contactors, and twelve (12) seconds for the mechanically latched contactors.

This feature may also be used for motor protection, by preventing a motor from being started too frequently. In this case, it shall be possible to increase the restart delay as follow:

Minimum (6 or 12 sec.) to 3600 sec. (60 minutes)

1 sec. resolution

The Delayed Restart data will be available, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Delay Restart Time = ‘ ‘6 Sec’ to ‘3600 Sec’

(Note: Minimum time limited to 12 Sec for mechanically latched contactor)

‘IB2 Delay Restart Time = ‘ ‘6 Sec’ to ‘3600 Sec’ (Note: Minimum time limited to 12 Sec for mechanically latched contactor)




This time value is used by the IE unit to delay the time between issuing a close command to the IB unit, issuing an open command to the IB unit and then issuing another close command.

While the IntelliVAC Plus is counting down this delayed restart time, this parameter will be made available, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Delay Restart Wait Time = ‘ ‘x Sec’

(Note: This value, as it is being viewed, will be constantly updated as the wait time decreases.)

‘IB2 Delay Restart Wait Time = ‘ ‘x Sec’ (Note: This value, as it is being viewed, will be constantly updated as the wait time decreases.)


1503-UM054D-EN-P – March 2015




Temporary Jog Function

It shall be possible to connect the “Open” input to function as a “Temporary Jog” (for electrically held contactors only). Thus, this feature shall be permitted when an electrically held contactor is selected.

It shall be possible to Jog a motor under the following conditions:

Maximum of 30 sec. continuously No more than “x” sec. of Jog activity during “y” seconds (to be

determined by testing)

This value should be programmable for the IE unit with the Jog time “x” being from 0 to 30 seconds in 1 second increments and the repetition time “y” being from 0 to 60 seconds in 1 second increments.

The Temporary Jog parameters will be available, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Jog Time = ‘0 Sec’ to ’30 Sec’ in 1 second increments ‘IB2 Jog Time = ‘0 Sec’ to ’30 Sec’ in 1 second increments ‘IB3 Jog Time = ‘0 Sec’ to ’30 Sec’ in 1 second increments ‘IB4 Jog Time = ‘0 Sec’ to ’30 Sec’ in 1 second increments ‘IB5 Jog Time = ‘0 Sec’ to ’30 Sec’ in 1 second increments

‘IB1 Jog Repetition Time = ‘0 Sec’ to ’60 Sec’ in 1 second

increments ‘IB2 Jog Repetition Time = ‘0 Sec’ to ’60 Sec’ in 1 second




increments


1503-UM054D-EN-P – March 2015

Counters must be implemented to keep track of the Jog time as well as for the Jog Repetition time. When a valid Jog command is detected (Open input is active) and the close command is not active, the contactor will be given a close command. The Open input command can also originate from an Open network bit (see Appendix B). The IntelliVAC Plus will also keep track of the length of a jog command, defined as the time from the beginning of the jog command to the end of the jog command. The most five (5) recent jog events will be logged to memory, containing the length of the jog as well as the date/time stamp.

Event Log During operation of the IntelliVAC Plus unit, the contactor will undergo many operations and experience faults and warning conditions. All of these events will be logged in non-volatile memory along with a time stamp. The events for any attached MC units in an MC configuration will be logged as well. A list of the available events is listed in Table 4.D. Once the memory array has been filled with events, newer events will be written over older events in a circular fashion. Note that the Fault and Warning data will be written whenever a new fault or warning occurs. Therefore, if a particular Fault occurs (i.e. CODE #16 – IE Fault) at a particular time and later on a different IE Fault occurs, the #16 fault will be written again with the new Fault data along with the new time stamp. Note: The ‘Faults/Status/Warnings’ word, from the Basic Module, will not be written to the Event Log when either the ‘Contactor Status’ or ‘Module Status’ bits become active. Jog even can only store up to latest 5 events. This feature avoids too many continuous job override other events. Each of the 5 IntelliVAC units will provide for a maximum of 100 events. If fewer than 5 IntelliVAC units are present then there will be a capability of storing more events per module. Table 4.C shows the number of events that can be stored as a function of the number of IntelliVAC units, before older events are overwritten by newer events.

Table 4.C - Number of Events Stored per # of IntelliVAC Units

# of IntelliVAC Units Maxmimum Number of Events Stored 1 500 2 250 3 166 4 125 5 100


1503-UM054D-EN-P – March 2015

Items #30 to #49, in the Event Log, which apply to the DeviceLogix I/O, will only be logged when the DeviceLogix engine is operating. This occurs when the Logic Mask is set to #2 – DeviceLogix (see Chapter 9). All other changes of these input states which occur while Logic Mask is not set to #2, will not be logged to the Event Log. Table 4.D – Event Log Data

Event Code Data Time Stamp Contactor #1 Closed 1 None Mnth/Date/Yr/Hr/Min/Sec/10mSecContactor #2 Closed 2 None “ Contactor #3 Closed 3 None “ Contactor #4 Closed 4 None “ Contactor #5 Closed 5 None “ Contactor #1 Open 6 None “ Contactor #2 Open 7 None “ Contactor #3 Open 8 None “ Contactor #4 Open 9 None “ Contactor #5 Open 10 None “ Jog Event #1 11 Byte “ Jog Event #2 12 Byte “ Jog Event #3 13 Byte “ Jog Event #4 14 Byte “ Jog Event #5 15 Byte “ IE Fault 16 Fault Byte “ IE Warning 17 Warning Byte “ IE DNet Fault 18 Fault Byte “ IE DNet Warning 19 Warning Byte “ IB #1 Fault 20 Fault Byte “ IB #2 Fault 21 Fault Byte “ IB #3 Fault 22 Fault Byte “ IB #4 Fault 23 Fault Byte “ IB #5 Fault 24 Fault Byte “ IB #1 Warning 25 Warning Byte “ IB #2 Warning 26 Warning Byte “ IB #3 Warning 27 Warning Byte “ IB #4 Warning 28 Warning Byte “ IB #5 Warning 29 Warning Byte “ IN1 Close 30 None “ IN2 Close 31 None “ IN3 Close 32 None “ IN4 Close 33 None “ IN5 Close 34 None “ IN6 Close 35 None “ IN7 Close 36 None “ IN8 Close 37 None “ IN1 Open 38 None “ IN2 Open 39 None “ IN3 Open 40 None “ IN4 Open 41 None “ IN5 Open 42 None “ IN6 Open 43 None “ IN7 Open 44 None “ IN8 Open 45 None “


1503-UM054D-EN-P – March 2015

Table 4.D – Event Log Data (cont.)

Event Code Data Time Stamp OUTA Close 46 None “OUTB Close 47 None “OUTA Open 48 None “OUTB Open 49 None “Line Undervoltage1 50 None “Line Undervoltage2 51 None “Line Undervoltage3 52 None “Line Undervoltage4 53 None “Line Undervoltage5 54 None “Line Overvoltage1 55 None “Line Overvoltage2 56 None “Line Overvoltage3 57 None “Line Overvoltage4 58 None “Line Overvoltage5 59 None “Line Loss1 60 None “Line Loss2 61 None “Line Loss3 62 None “Line Loss4 63 None “Line Loss5 64 None “Main Coil Open1 65 None “Main Coil Open2 66 None “Main Coil Open3 67 None “Main Coil Open4 68 None “Main Coil Open5 69 None “Trip Coil Open1 70 None “Trip Coil Open2 71 None “Trip Coil Open3 72 None “Trip Coil Open4 73 None “Trip Coil Open5 74 None “Close Time 1 75 Close time “Close Time 2 76 Close time “Close Time 3 77 Close time “Close Time 4 78 Close time “Close Time 5 79 Close time “Reset all Faults/Warnings 80 None “Reset all Warnings 81 None “IE F/W App Code Update 82 Major Rev Byte “IE F/W App Code Update 83 Minor Rev Byte “IB F/W App Code Update 84 Rev Byte “

Note: Line Undervoltage 1/2/3/4/5 could mean ‘Line Undervoltage Close 1/2/3/4/5’ or ‘Line Undervoltage Hold 1/2/3/4/5’.


1503-UM054D-EN-P – March 2015

Coil Currents The coil currents represent the average value of the particular coil

that is being controlled in each of the IntelliVAC Plus/MC units. The coil current values for each of the five (5) IB units, shall be made available on DeviceNet in the following manner:

‘IB1 Close Current = ‘ ‘xx.xxx’A (for electrically held or mechanically latched)





‘IB1 Hold Current = ‘ ‘xx.xxx’A (for electrically held) ‘IB2 Hold Current = ‘ ‘xx.xxx’A (for electrically held) ‘IB3 Hold Current = ‘ ‘xx.xxx’A (for electrically held) ‘IB4 Hold Current = ‘ ‘xx.xxx’A (for electrically held) ‘IB5 Hold Current = ‘ ‘xx.xxx’A (for electrically held)

‘IB1 Contactor Coil Current = ‘xx.xxx’A (for electrically held or mechanically latched)





‘IB1 Contactor Coil Current = ‘ ‘xx.xxx’A (for mechanically latched only)





The ‘IBx Contactor Coil Current’ values are the real time currents for each of the main coils (main single coil for the electrically held contactor and the main coil for the mechanically latched contactor). The ‘IBx Contactor Coil Current’ values are the real time currents for each of the mechanically latched trip coils.


1503-UM054D-EN-P – March 2015

Open Coil Test To check that there is a coil(s) connected to the IntelliVAC Plus unit

a test is performed to confirm that the coil current is greater than 200mA. If the coil current measured is lower than this threshold then it can be assumed that the particular Coil Under Test (CUT) is open. If the coil is an open circuit then the IntelliVAC Plus Module Status LED will annunciate the fault (see Table 4.F). This fault will indicate an open coil for any of the up to five (5) contactors connected in an MC system. This open coil test will be performed on a regular basis only when the contactor is not being commanded to be closed. It will be performed for all of the up to five (5) contactors attached and will be executed once every minute. When an open coil is found the event will be logged to the Event Log table (see Event Log Table 4.D) and the IntelliVAC Plus Module Status LED will be turned on. If one or more open coils are detected and then at some point the coil(s) is no longer found to be open, then the IntelliVAC Plus Module Status LED will be turned off. Below are the DeviceNet messages displayed when an open coil condition is detected: ‘IB1 Main Coil Open’ = Present or Not Present ‘IB2 Main Coil Open’ = Present or Not Present ‘IB3 Main Coil Open’ = Present or Not Present ‘IB4 Main Coil Open’ = Present or Not Present ‘IB5 Main Coil Open’ = Present or Not Present

The following are for mechanically latched contactors only. ‘IB1Trip Coil Open’ = Present or Not Present ‘IB2 Trip Coil Open’ = Present or Not Present ‘IB3 Trip Coil Open’ = Present or Not Present ‘IB4 Trip Coil Open’ = Present or Not Present ‘IB5 Trip Coil Open’ = Present or Not Present

For the Electrically Held contactor, this test for the main coil can be performed whenever the coil is not in the pick-up or closed mode. For the Mechanically Latched contactor, the test for the main coil can be performed whenever the coil is not in the close mode and for the trip coil, whenever this coil in not being activated.


1503-UM054D-EN-P – March 2015

Supply Voltages The AC and DC supply voltage measurements represent the RMS

values of the input mains for each of the IntelliVAC Plus/MC modules. The voltage values for each of the five (5) IB units, shall be made available on DeviceNet in the following manner:

‘IB1 Line Voltage = ‘ ‘xxx.xx’V ‘IB2 Line Voltage = ‘ ‘xxx.xx’V ‘IB3 Line Voltage = ‘ ‘xxx.xx’V ‘IB4 Line Voltage = ‘ ‘xxx.xx’V ‘IB5 Line Voltage = ‘ ‘xxx.xx’V

‘IB1 DC Bus Voltage = ‘ ‘xxx.xx’V ‘IB2 DC Bus Voltage = ‘ ‘xxx.xx’V ‘IB3 DC Bus Voltage = ‘ ‘xxx.xx’V ‘IB4 DC Bus Voltage = ‘ ‘xxx.xx’V ‘IB5 DC Bus Voltage = ‘ ‘xxx.xx’V

If the input voltage is too high, too low or missing, then the following messages will be made available on DeviceNet: ‘IB1 Line Undervoltage Close’ (Line voltage1 < 95Vrms) ‘IB2 Line Undervoltage Close’ (Line voltage2 < 95Vrms) ‘IB3 Line Undervoltage Close’ (Line voltage3 < 95Vrms) ‘IB4 Line Undervoltage Close’ (Line voltage4 < 95Vrms) ‘IB5 Line Undervoltage Close’ (Line voltage5 < 95Vrms)

‘IB1 Line Undervoltage Hold’ (Line voltage1 < 80Vrms) ‘IB2 Line Undervoltage Hold’ (Line voltage2 < 80Vrms) ‘IB3 Line Undervoltage Hold’ (Line voltage3 < 80Vrms) ‘IB4 Line Undervoltage Hold’ (Line voltage4 < 80Vrms) ‘IB5 Line Undervoltage Hold’ (Line voltage5 < 80Vrms)

‘IB1 Line Overvoltage’ (Line voltage1 > 265Vrms) ‘IB2 Line Overvoltage’ (Line voltage2 > 265Vrms) ‘IB3 Line Overvoltage’ (Line voltage3 > 265Vrms) ‘IB4 Line Overvoltage’ (Line voltage4 > 265Vrms) ‘IB5 Line Overvoltage’ (Line voltage5 > 265Vrms)

‘IB1 Line Loss’ (Line voltage1 < 50Vrms); electronics, only,

function in this range ‘IB2 Line Loss’ (Line voltage2 < 50Vrms); electronics, only,




function in this range


1503-UM054D-EN-P – March 2015

The ‘IBx Line Undervoltage’ and ‘IBx Line Undervoltage’ values are included to allow a distinction for Undervoltage conditions during different intervals of the contactor coil operation.

Real-Time Clock (RTC) The IntelliVAC Plus Unit contains an RTC with an external 3V lithium battery (see Appendix D for battery replacement type) which will maintain the correct time for a period of at least 20 years when no external power is provided. The RTC will be set-up at the factory, and provision shall be made to adjust the setting via the DeviceNet interface (Time Zone Selection in Chapter 4). The RTC will be used to support several features associated with the IntelliVAC Plus as well as to provide the date and time information over the DeviceNet interface. Time stamping of events will be stored in the Event Log which resides in non-volatile memory. The RTC is capable of a resolution as low as 10mS which will allow more precise stamping of the events for better knowledge of when events occurred, thus helping to define which event occurred first.

The time format that should be used is the 24 hour mode.

The RTC data will be settable on DeviceNet in the following manner:

Valid Data Range

‘Year = ‘ ‘2000’ to ‘2099’ ‘Month = ‘ ‘01’ to ‘12’ ‘Date = ‘ ‘01’ to ‘31’ ‘Hour = ‘ ‘01’ to ‘24’ (uses 24 hour time) ‘Minute = ‘ ‘00’ to ‘59’ ‘Second = ‘ ‘00’ to ‘59’ ’10milliSecond=‘‘00’to‘99’

The RTC data will be viewable on DeviceNet in the following manner: RTC Date: Month/Day/Year RTC Time: Hour/Minute/Second/Millisecond The ’10 millisecond’ parameter will only be used to time stamp events and will not be viewable in the RTC data viewing mode. Various operating transactions will be time stamped using the RTC values in the following format: Year, Month, Date, Hour, Minute, Second and 0.01 Second.


1503-UM054D-EN-P – March 2015

Time Zone Selection To facilitate in the setting of the time of day for different world time

zones, there will be a feature added, which allows the time zone of the area where the IntelliVAC Plus will be operated, to be programmed. This will be implemented, using DeviceNet, by selecting the appropriate time zone from a list as follows:

‘Time Zone Selection = GMT -12:00’ ‘Time Zone Selection = GMT -11:00’ ‘Time Zone Selection = GMT -10:00’ ‘Time Zone Selection = GMT - 9:00’ ‘Time Zone Selection = GMT - 8:00’ ‘Time Zone Selection = GMT - 7:00’ ‘Time Zone Selection = GMT - 6:00’ ‘Time Zone Selection = GMT - 5:00’ ‘Time Zone Selection = GMT - 4:00’ ‘Time Zone Selection = GMT - 3:30’ ‘Time Zone Selection = GMT - 3:00’ ‘Time Zone Selection = GMT - 2:00’ ‘Time Zone Selection = GMT - 1:00’ ‘Time Zone Selection = GMT - 0:00’ ‘Time Zone Selection = GMT + 1:00’ ‘Time Zone Selection = GMT + 2:00’ ‘Time Zone Selection = GMT + 3:00’ ‘Time Zone Selection = GMT + 3:30’ ‘Time Zone Selection = GMT + 4:00’ ‘Time Zone Selection = GMT + 4:30’ ‘Time Zone Selection = GMT + 5:00’ ‘Time Zone Selection = GMT + 5:30’ ‘Time Zone Selection = GMT + 5:45’ ‘Time Zone Selection = GMT + 6:00’ ‘Time Zone Selection = GMT + 6:30’ ‘Time Zone Selection = GMT + 7:00’ ‘Time Zone Selection = GMT + 8:00’ ‘Time Zone Selection = GMT + 9:00’ ‘Time Zone Selection = GMT + 9:30’ ‘Time Zone Selection = GMT +10:00’ ‘Time Zone Selection = GMT +11:00’ ‘Time Zone Selection = GMT +12:00’ ‘Time Zone Selection = GMT +13:00’

When the time zone is read from DeviceNet, one of the above selected time zones will be displayed.


1503-UM054D-EN-P – March 2015

The IntelliVAC Plus is adaptable to a range of atmospheric pressures and altitudes. This should eliminate the need for special return springs within the contactors, by regulating the coil current to apply the appropriate closing, holding and opening force.

The range of altitudes covered is: –1,000 → 5,000 metres In this case, a simple “altitude parameter” will be used to adapt the contactor closing force. The parameter would be settable, between –1,000 and 5,000 metres, with a display resolution of 1000 metres.

The IntelliVAC Plus provides for altitude set-up in discrete settings, via DIP switches on the IB unit as follows:

-1000 → 0000 meters 0001 → 1000 meters 1001 → 2000 meters 2001 → 3000 meters 3001 → 4000 meters 4001 → 5000 meters

The altitude setting is one of the parameters used to determine the contactor coil current values. The Altitude parameter will not be settable on DeviceNet, but only configured through the DIP switches on the IB unit(s) and will be viewable on DeviceNet as follows: ‘Altitude = ‘ ‘-1000 to 0000m’ or ‘0001 to 1000m’ or ‘1001 to 2000m’ or ‘2001 to 3000m’ or ‘3001 to 4000m’ or ‘4001 to 5000m’

In an MC topology, if the Altitude and settings from the DIP switches from the two or more IB units are not consistent, then a warning will be indicated. The warning will be indicated as in Table 4.F. In this situation, the following message will be displayed on DeviceNet:

‘MC Altitude Set Warning’

Operations Counter The IntelliVAC Plus includes a counter that tracks the number of contactor operations. The following sub-registers shall be associated with the Operations Counter: ‘Master’ Counter ‘Operations Since’ Counter ‘Average Operations’ Counter

Altitude/Air Pressure Compensation (400A Contactors)


1503-UM054D-EN-P – March 2015

“Master” Counter The Master counter will include all operations, since initial use of the

IntelliVAC Plus product.

Each operation refers to the completion of a ‘Close’ operation. If a close command is initiated but the contactor does not close (i.e. due to an under-voltage condition) then the count will not be incremented.

A Master Counter shall be provided for each of the IntelliVAC MC units in an MC configuration. The Master Counter parameters will be viewable, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Master Counter = ‘ ‘0’ to ‘16777215’ (24 bit counter) ‘IB2 Master Counter = ‘ ‘0’ to ‘16777215’ (24 bit counter) ‘IB3 Master Counter = ‘ ‘0’ to ‘16777215’ (24 bit counter) ‘IB4 Master Counter = ‘ ‘0’ to ‘16777215’ (24 bit counter) ‘IB5 Master Counter = ‘ ‘0’ to ‘16777215’ (24 bit counter)

This parameter will default to 0 for a new IntelliVAC Plus product and cannot be reset.

“Operations Since” Counter The Operations Since counter will include all operations since a

register reset has occurred, associated with a date/time set by the real-time clock. Settings are provided for three (3) values: the most current and the previous two. This counter will keep track of all ‘Close’ operations since a new unit has been powered up or since it was last reset. A date/time will be associated with the start of implementation of this counter. Once the RTC has been adjusted, this counter should be reset to have it begin counting from a realistic date/time. Once a register reset has been implemented, the previous date/time and count value will be copied into a set of registers. This will occur for one more cycle, after another register reset has been implemented, so that there will always be a history of the most current “operations since” counter, along with its reset time and for two previous “operations since” counters, along with their reset times. An Operations Counter will be reset in the following manner-data will be available, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Reset Ops Since Counter’ (present ‘IB1 Ops Since 0

data/time’ saved to ‘IB1 Ops Since 1’ along with counter value and ‘IB1 Ops Since 1 data/time’ saved to ‘IB1 Ops Since 2’ along with counter value) with ‘IB1 Ops Since0’ counter = ‘0’


1503-UM054D-EN-P – March 2015

‘IB2 Reset Ops Since Counter’ (present ‘IB2 Ops Since 0 data/time’ saved to ‘IB2 Ops Since 1’ along with counter value and ‘IB2 Ops Since 1 data/time’ saved to ‘IB2 Ops Since 2’ along with counter value) with ‘IB2 Ops Since’ counter = ‘0’

‘IB3 Reset Ops Since counter’ (present ‘IB3 Ops Since data/time’ saved to ‘IB3 Ops Since 1’ along with counter value and ‘IB3 Ops Since 1 data/time’ saved to ‘IB3 Ops Since 2’ along with counter value) with ‘IB3 Ops Since’ counter = ‘0’

‘IB4 Reset Ops Since counter’ (present ‘IB4 Ops Since data/time’ saved to ‘IB4 Ops Since 1’ along with counter value and ‘IB4 Ops Since1 data/time’ saved to ‘IB4 Ops Since 2’ along with counter value) with ‘IB4 Ops Since’ counter = ‘0’

‘IB5 Reset Ops Since counter’ (present ‘IB5 Ops Since data/time’ saved to ‘IB5 Ops Since 1’ along with counter value and ‘IB5 Ops Since 1 data/time’ saved to ‘IB5 Ops Since 2’ along with counter value) with ‘IB5 Ops Since’ counter = ‘0’

An “Operations Since” Counter is provided for each of the IntelliVAC MC units in an MC configuration.

The Operations Since Counter parameters will be viewable, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Operation Since 0 Count Value =’ ‘0’ to ‘16777215’

(24 bit counter) ‘IB1 Operation Since 0 Date =’ ‘Month-Date-Year’ ‘IB1 Operation Since 0 Time =’ ‘Hours-minutes-Seconds-10mS’ ‘IB1 Operation Since 1 Count Value =’ ‘0’ to ‘16777215’





(24 bit counter) ‘IB2 Operation Since 2 Date =’ ‘Month-Date-Year’ ‘IB2 Operation Since 2 Time =’ ‘Hours-minutes-Seconds-10mS’


1503-UM054D-EN-P – March 2015

‘IB3 Operation Since 0 Count Value =’ ‘0’ to ‘16777215’ 24 bit counter) ‘IB3 Operation Since 0 Date =’ ‘Month-Date-Year’ ‘IB3 Operation Since 0 Time =’ ‘Hours-minutes-Seconds-10mS’ ‘IB3 Operation Since 1 Count Value =’ ‘0’ to ‘16777215’








(24 bit counter) ‘IB5 Operation Since 2 Date =’ ‘Month-Date-Year’ ‘IB5 Operation Since 2 Time =’ ‘Hours-minutes-Seconds-10mS’

An interpretation of the coding used for these parameters follows:

‘IB4 Ops Since 2 Count Value’ means the Operations Since counter for an MC contactor #4 for the second last reset from the present reset.


1503-UM054D-EN-P – March 2015

“Average Operations” Counter The Average Operations counter will include Average operations per

time period (selectable for hours, days or weeks), since a last reset occurred (see “Operations Since” Counter section).

This parameter will calculate the average number of operations (valid Close commands) between the last reset time and the present RTC value. It can be viewed as an average over the number of hours, days or weeks, between the last operations reset time and the present RTC value. An “Average Ops” Counter shall be provided for each of the IB units in an MC configuration.

The Average Ops Counter will be viewable, for each of the five (5) IB units, on DeviceNet in the following manner:

‘IB1 Average Operations per Time Unit =’ ‘Hour’ or ‘Day’ or ‘Week’ ‘IB1 Average Operations Value =’ ‘0’ to ‘16777215’ (24 bit counter) ‘IB2 Average Operations per Time Unit =’ ‘Hour’ or ‘Day’ or ‘Week’ ‘IB2 Average Operations Value =’ ‘0’ to ‘16777215’ (24 bit counter) ‘IB3 Average Operations per Time Unit =’ ‘Hour’ or ‘Day’ or ‘Week’ ‘IB3 Average Operations Value =’ ‘0’ to ‘16777215’ (24 bit counter) ‘IB4 Average Operations per Time Unit =’ ‘Hour’ or ‘Day’ or ‘Week’ ‘IB4 Average Operations Value =’ ‘0’ to ‘16777215’ (24 bit counter) ‘IB5 Average Operations per Time Unit =’ ‘Hour’ or ‘Day’ or ‘Week’ ‘IB5 Average Operations Value =’ ‘0’ to ‘16777215’ (24 bit counter)

Set the time unit for the average operations on DeviceNet, as follows: ‘IBx Average Operations per Time Units = ‘Hour’ or ‘Day’ or ‘Week’ This parameter will apply to all five of the ‘IBx Average Operations value’ features. As soon as this parameter is altered, all of the ‘IBx Average Operations Value’ will be redisplayed with the new time units, when selected.


1503-UM054D-EN-P – March 2015

Configuration The IntelliVAC Plus Unit will be configured in one of two manners:

HIM The standard means of configuring an IntelliVAC Plus shall be with a hand-held configurator for DeviceNet (HIM). It shall be possible to access all “Customer Use” parameters (need to define Customer Use parameters) using the HIM. When accessed via the HIM, parameters will be grouped/selected according to the following – Control, Communications, Configuration & Diagnostics, see Appendix B. RS NetWorx Software The IntelliVAC shall be configurable via DeviceNet, using RS Networx software. This will include any parameters accessible via the HIM. In addition, RS Networx shall be used to configure all DeviceLogix function blocks. Please use RSNetWorx 8 or above to support RTC setting.

Dual Power Supply Operation The IntelliVAC Plus module is capable of operating on two different power sources. The first of these sources is from the input power at terminals TB1-TB2. This power source is used to generate the internal DC voltages required for operation of the IntelliVAC Plus module. The second power source is from the DeviceNet power, if it is supplied. Operation of the IntelliVAC Plus module will always operate from the input power at the TB1-TB2 terminals, if both power sources are available. If only the DeviceNet power source is available, then the IntelliVAC Plus unit will operate using this power source. When the power source at the TB1-TB2 terminals is available, then all of the features of the IntelliVAC Plus will be operable. However, when only the DeviceNet power source is available, then all of the operational features of the contactor, such as closing the contactor coil, etc, will not be available. Only communications over DeviceNet will be operable. All information which requires RS485 communications will not be available. This will also cease operation of the MC system.

Power Fail Operation

The internal 15VDC power supply will be monitored and failure of this power rail will cause all RS485 communications to cease. With a stand-alone IntelliVAC Plus unit only DeviceNet communications will be operating, assuming that there is a DeviceNet power source.


1503-UM054D-EN-P – March 2015

In an MC system all MC operation will cease and communications between the various MC modules will stop as well. A fault message will be made available on DeviceNet signifying that the IntelliVAC Plus unit is not completely functioning. This condition will indicate that the contactor will be out of order. The following fault parameter will be made available on DeviceNet in the following manner:

‘IB1 Power Fail Status = ‘Good’ or ‘Bad’ See Table 4.J for the 7-segment LED display code for this condition.

Status Indicators

The IntelliVAC Plus unit has five sets of status indicators:

Two (2) red/green bi-colour type status indicators on the IB unit for Module/Contactor status Two (2) red/green bi-colour type status indicators on the IE unit for Module/Network status

One (1) red 7 segment status indicator display for Warning/Fault status Eight (8) yellow status indicators for the DeviceLogix inputs status Two (2) yellow status indicators for the DeviceLogix outputs status Status LEDs

Figure 4.1 – Status Indicators

Table 4.E shows the Faults/Warnings conditions for the IB module only. These conditions are only valid for the IB module contained within the IntelliVAC Plus unit and not the IB modules within the other MC modules within an MC system.

Status Display Items


1503-UM054D-EN-P – March 2015

Table 4.E – Base Module Fault/Warning Descriptions

IntelliVAC Status Indication (Series E only)

Conditions Description

Module Status Contactor Status

LED Color Relay LED Color Relay

Normal Healthy Module and Contactor OPEN Green Closed Off Open

Normal Healthy Module and Contactor CLOSED Green Closed Yellow Closed

Warning Invalid Command Present 12 Yellow Closed Off Open

Warning Mechanical Latch Fail to Trip Yellow Closed Yellow Closed

Fault Power Up with Contactor CLOSED Red – Flash 2 Open Yellow Closed

Warning Contactor Fails to Pick Up Yellow – R1 Closed Off / Yellow Open/Closed

Warning Contactor Drop Out During Hold Yellow – R2 Closed Off / Yellow Open/Closed

Warning Long Contactor Drop Out Time Yellow – R3 Closed Off / Yellow Open/Closed

Fault Microcontroller Malfunction Red Open Red Open

Fault Power Up with Invalid DIP Switch Configuration Red – Flash 1 Open Off Open

Fault Contactor Fails to Drop Out Red – Flash 3 Open Red Open

Fault RS485 Communications Error Red – Flash 4 Open Off Open

Warning Undervoltage with a CLOSE Command Present Yellow – Flashing Open/Closed Off / Yellow Open/Closed

Warnings will be cleared when a change of input state occurs, and the condition has been resolved. Faults require control power to be removed until the unit resets Flash 1 = 1 Flash Red LED followed by a pause Flash 2 = 2 Consecutive Red LED flashes followed by a pause Flash 3 = 3 Consecutive Red LED flashes followed by a pause Flash 4 = 4 Consecutive Red LED flashes followed by a pause Yellow – R1 = Yellow with 1 Red flash followed by a pause Yellow – R2 = Yellow with 2 consecutive Red flashes followed by a pause Yellow – R3 = Yellow with 3 consecutive Red flashes followed by a pause Open during undervoltage, Closed if voltage restored

Will reflect actual status of the contactor 12 Invalid Command Types: 1. Close, Jog or Trip commands present during power up sequence 2. Close or Jog command re-applied too quickly (before contactor opening sequence is verified). Allow at least 60 msec, plus drop out delay time, before re-applying these signals. NOTE: Contactor will only respond to a close command re-applications after the re-start delay timer has expired. 3. Close and Trip commands present simultaneously (valid with Mechanical Latch contactors only).

Base Module Faults / Warnings Healthy Module and Contactor OPEN

This is a Normal condition and no additional action is required. This indicates that the Basic module within the IntelliVAC Plus unit has no faults or warnings and the status of the contactor being controlled is in an Open condition. The Module status LED is Green to indicate a good module and the Module status relay is closed to allow externally connected circuits to function.


1503-UM054D-EN-P – March 2015

The Contactor status LED is off to indicate that the contactor is in an Open condition and the Contactor status relay is open to reflect the status of the contactor thus preventing externally connected circuits from functioning.

This condition is valid for both Electrically Held and Mechanically Latched contactors. Healthy Module and Contactor CLOSED

This is a Normal condition and no additional action is required. This indicates that the Basic module within the IntelliVAC Plus unit has no faults or warnings and the status of the contactor being controlled is in a Closed condition. The Module status LED is Green to indicate a good module and the Module status relay is closed to allow externally connected circuits to function. The Contactor status LED is Yellow to indicate that the contactor is in a Closed condition and the Contactor status relay is closed to reflect the status of the contactor thus allowing externally connected circuits to function.

This condition is valid for both Electrically Held and Mechanically Latched contactors.

Invalid Command Present

This is a Warning condition and the action of the Close/Jog/Trip commands should be analyzed. This indicates that the Basic module within the IntelliVAC Plus unit has a warning due to an invalid command and the status of the contactor being controlled is in an Open condition. The Module status LED is Yellow to indicate a module with warning level problems and the Module status relay is closed to allow externally connected circuits to function. The Contactor status LED is off to indicate that the contactor is in an Open condition and the Contactor status relay is open to reflect the status of the contactor thus preventing externally connected circuits from functioning. The types of commands that are considered invalid are as follows: Close, Jog or Trip commands are present during a power on sequence.


1503-UM054D-EN-P – March 2015

Note: Close and Jog are for an Electrically Held contactor and Close and Trip are for a Mechanically Latched contactor. The Close or Jog commands are re-applied before the contactor opening sequence can be verified. Once a Close or Jog command are issued, the commands must be removed for a period of at least 60mS, plus the Drop Out Delay time, before re-applying the commands (see Figure 5.5 for a timing representation of the contactor control commands). Note: The contactor will only respond to a close command re-application after the re-start delay timer has expired (see Delayed Restart in Chapter 4 for an explanation of the Delayed Restart Timer). The Close and Trip commands are present simultaneously (valid for Mechanical Latch contactors only). This condition is valid for both Electrically Held and Mechanically Latched contactors.

Mechanical Latch Fail to Trip This is a Warning condition and the status of the Trip coil circuits/wiring should be analyzed. This indicates that the Basic module within the IntelliVAC Plus unit has a warning due to a Mechanical Latch contactor not tripping off after being given a Trip command and the status of the contactor being controlled is in a Closed condition. The Module status LED is Yellow to indicate a module with warning level problems and the Module status relay is closed to allow externally connected circuits to function. The Contactor status LED is Yellow to indicate that the contactor is in a Closed condition and the Contactor status relay is closed to reflect the status of the contactor thus allowing externally connected circuits to function. This condition is valid for Mechanically Latched contactors only.

Power up with Contactor CLOSED After TDUV, if the module can not detect the contactor is dropped off source the power supply is still lost/low, this fault condition would also be triggered.


1503-UM054D-EN-P – March 2015

This is a Fault condition and the IntelliVAC Plus will not respond to other commands until this condition is restored to normal. Check the condition of the contactor or the status of the Contactor Auxiliary Input. This indicates that the Basic module within the IntelliVAC Plus unit has a fault due to a power up condition occurring with the contactor in a Closed position and the status of the contactor being controlled is in a Closed condition. The Module status LED is flashing Red with 2 consecutive red flashes followed by a pause to indicate a module with fault level problem and the Module status relay is open to prevent externally connected circuits from functioning. The Contactor status LED is Yellow to indicate that the contactor is in a Closed condition and the Contactor status relay is closed to reflect the status of the contactor thus allowing externally connected circuits to function. This condition is valid for Electrically Held contactors only.

Contactor Fails to Pick Up This is a Warning condition and the status of the contactor coil or Contactor Auxiliary Input should be checked. This indicates that the Basic module within the IntelliVAC Plus unit has a warning due to the contactor failing to pick up after being given a Close or Jog command and the status of the contactor being controlled is in an Open or Closed condition (dependant on the status of the contactor). The Module status LED is flashing Yellow followed by 1 consecutive red flash followed by a pause, to indicate a module that has failed to pick up the contactor and the Module status relay is closed to allow externally connected circuits to function. The Contactor status LED is Yellow or off to indicate that the contactor is in a Closed or Open condition and the Contactor status relay is Closed or Open to reflect the status of the contactor thus allowing or preventing externally connected circuits to function. This condition is valid for both Electrically Held and Mechanically Latched contactors.


1503-UM054D-EN-P – March 2015

Contactor Drop Out During Hold This is a Warning condition and the status of the contactor coil or Contactor Auxiliary Input should be checked. This indicates that the Basic module within the IntelliVAC Plus unit has a warning due to the contactor dropping out when it should be in the hold mode after being given a Close or Jog command and the status of the contactor being controlled is in an Open or Closed condition (dependant on the status of the contactor). The Module status LED is flashing Yellow followed by 2 consecutive red flashes followed by a pause, to indicate a contactor that has dropped out during the hold operation and the Module status relay is closed to allow externally connected circuits to function. The Contactor status LED is Yellow or off to indicate that the contactor is in a Closed or Open condition and the Contactor status relay is Closed or Open to reflect the status of the contactor thus allowing or preventing externally connected circuits to function. This condition is valid for both Electrically Held and Mechanically Latched contactors.

Long Contactor Drop Out Time This is a Warning condition and the status of the contactor coil or Contactor Auxiliary Input should be checked. This indicates that the Basic module within the IntelliVAC Plus unit has a warning due to the contactor requiring too long of a drop out time and the status of the contactor being controlled is in an Open or Closed condition (dependant on the status of the contactor). The drop out time would be up to 130mS after the programmed Drop Out Time set by the DIP switches (see Table 8.B). The Module status LED is flashing Yellow followed by 3 consecutive red flashes followed by a pause, to indicate a contactor that has required too long of a time to drop out and the Module status relay is closed to allow externally connected circuits to function. The Contactor status LED is Yellow or off to indicate that the contactor is in a Closed or Open condition and the Contactor status relay is Closed or Open to reflect the status of the contactor thus allowing or preventing externally connected circuits to function. This condition is valid for Electrically Held contactors only.


1503-UM054D-EN-P – March 2015

Microcontroller Malfunction This is a serious Fault condition and the IntelliVAC Plus will not respond to other commands. Refer all servicing to a qualified service personnel or see the trouble shooting section in Chapter 10. This indicates that the Basic module within the IntelliVAC Plus unit has a severe fault due to a microcontroller malfunction and the status of the contactor being controlled is in an Open condition. The Module status LED is solid red indicating a severe module fault and the Module status relay is open to prevent externally connected circuits from functioning. The Contactor status LED is Red to indicate that the contactor is in an Open condition and the Contactor status relay is Open to reflect the status of the contactor thus preventing externally connected circuits to function.


Power Up with Invalid DIP Switch Configuration

This is a Fault condition and the IntelliVAC Plus will not respond to other commands until this condition is restored to normal. Check the settings of the DIP switches and make sure that they are set correctly. This indicates that the Basic module within the IntelliVAC Plus unit has a fault due to the module powering up with an invalid DIP switch configuration and the status of the contactor being controlled is in an Open condition. The Module status LED is flashing Red followed by a pause, to indicate a contactor module that has powered up with an invalid DIP switch configuration and the Module status relay is open to prevent externally connected circuits from functioning. The Contactor status LED is off to indicate that the contactor is in an Open condition and the Contactor status relay is Open to reflect the status of the contactor thus preventing externally connected circuits from functioning.



1503-UM054D-EN-P – March 2015

Contactor Fails to Drop Out

This is a Fault condition and the IntelliVAC Plus will not respond to other commands until this condition is restored to normal. Check the condition of the contactor or the Contactor Auxiliary Input. This indicates that the Basic module within the IntelliVAC Plus unit has a fault due to the contactor failing to drop out once the Close of Jog command is removed (for Electrically Held Contactors) or a Trip command has been issued (for Mechanically Latched Contactors) and the status of the contactor being controlled is in an Open condition. The contactor may actually have dropped out but required longer than normal time to do so, having exceeded the time for a Long Contactor Drop Out Time, which is set to 1S. Therefore, the contactor required >1S for a Long Contactor Drop Out. The Module status LED is flashing Red with 3 consecutive red flashes followed by a pause to indicate a contactor that has not dropped out at all or has required too long of a time to drop out and the Module status relay is open to prevent externally connected circuits from functioning. The Contactor status LED is Red to indicate that the contactor has a severe fault and has not dropped out at all, or at least not within the maximum allowed time of 240mS and the Contactor status relay is Open to prevent externally connected circuits from functioning. This condition is valid for both Electrically Held and Mechanically Latched contactors.

RS485 Communications Error This is a Fault condition and the IntelliVAC Plus will not respond to other commands until this condition is restored to normal. Check the condition of any external RS485 cables/resistor terminators that may be connected. This indicates that the Basic module within the IntelliVAC Plus unit has a fault due to RS485 communications errors between itself and the IE unit and the status of the contactor being controlled is in an Open condition. The Module status LED is flashing Red with 4 consecutive red flashes followed by a pause to indicate that there is an RS485 communications error with the commanding IE unit and the Module status relay is open to prevent externally connected circuits from functioning.


1503-UM054D-EN-P – March 2015

The Contactor status LED is off to indicate that the contactor is in an Open condition and the Contactor status relay is Open to reflect the status of the contactor thus preventing externally connected circuits from functioning.


Undervoltage with a CLOSE Command Preset This is a Warning condition and the level of the input mains voltage should be checked. This indicates that the Basic module within the IntelliVAC Plus unit has an input line under-voltage condition while the Close command is present and the status of the contactor being controlled is in an Open or Closed condition (dependant on the status of the contactor). The Module status LED is flashing Yellow to indicate that there is an under-voltage condition while the Close command is present and the Module status relay is open, while the under-voltage is present and closed once the condition is restored. When a Close command is given and the line voltage is <95Vrms and the TDUV setting is disabled or set to zero (see TDUV in Chapter 4) then the Module status LED will flash. This will only occur when the line voltage is <95Vrms and the Close command is then applied. In this case the contactor will not even be picked up. To have the contactor close, the line voltage must increase to >95Vrms and the Close command must be removed and then reapplied. If the TDUV is enabled then the contactor must have been in the hold state (electrically held contactors), the TDUV time must have expired and the line voltage must decrease to <80V before the module status LED flashes yellow. In this case the contactor will drop out. The Module status relay will be open if the voltage is still in an under-voltage condition (<95Vrms without the contactor being closed or <80Vrms during a hold condition and TDUV time expired) or it will be closed if the voltage has been restored to >95Vrms. The Contactor status LED is Yellow or off to indicate that the contactor is in a Closed or Open condition and the Contactor status relay is Closed or Open to reflect the status of the contactor thus allowing or preventing externally connected circuits to function.


1503-UM054D-EN-P – March 2015

This condition is valid for both Electrically Held and Mechanically Latched contactors (TDUV and <80Vrms during hole conditions do not apply for Mechanically Latched contactors).


On a fault occurrence, of either the IB or IE units, the contactor will be opened either by removing power to the hold coil in an electrically held contactor or by pulsing the trip coil in a mechanically latched contactor.

Module Status

Figure 4.2 – Fault/Warning on IntelliVAC Plus

Table 4.F shows the Faults/Warnings conditions for the IntelliVAC Plus module only.

Module/Network Status LEDs


1503-UM054D-EN-P – March 2015

Table 4.F – IntelliVAC Plus Fault/Warning Description

Fault/Warning Red LED Green LED Description

None Off Solid On Application Firmware Running

None Off Flash @ 0.25Hz Application Disable Jumper In

None Off Flash @ 0.50Hz Programming Base Unit(s)

None Off Off No power from IB or DeviceNet

Warning Off 2 Pulses RTC Fail

Warning Off 3 Pulses Line Undervoltage

Warning Off 4 Pulses Line Overvoltage

Warning Off 5 Pulses Extended Close Time (See Table 4.G)

Warning Off 6 Pulses DeviceNet Power Loss

(only if Power was available on power up – need historical value)

Warning Off 7 Pulses MC Altitude Setting Warning

Fault Solid On Undefined In RESET mode or F/W Crash

Fault 2 Pulses Off POST failure –RAM

Fault 5 Pulses Off Appl. Programming Error – CRC

Fault 6 Pulses Off RS485 Comm Fault (IB Fault)

Fault 7 Pulses Off IB1 Power Loss

Fault 8 Pulses Off Coil Open

Fault 9 Pluses Off System Lock Up

Table 4.F shows the operation of the Plus Status LED and the faults/warnings that they indicate. This table makes use of two methods of indicating a particular fault/warning. The first method will flash the particular LED at a certain frequency rate. Flashing at a rate of 0.25Hz, for example, means that the LED will cycle from being off to on and to off again in 4 seconds, so that it will be on for 2 seconds and off for 2 seconds. A flashing rate of 2.0Hz means that the LED will be on for 0.25 seconds and then off for 0.25 seconds for a cycle time of 0.5 seconds. The second method of indication is to flash a LED for a certain number of pulses and then incorporate a pause in the cycle. The pattern for a ‘2 Pulses’ pattern will be as follows:

1 – maintain LED on for 0.5 seconds 2 – maintain LED off for 0.5 seconds 3 – maintain LED on for 0.5 seconds 4 – maintain LED off for 0.5 seconds 5 – maintain LED off for 2 seconds 6 – repeat 1


1503-UM054D-EN-P – March 2015

When a fault/warning occurs, the appropriate LED will flash and the appropriate fault/warning will be written to the Event Log. When the fault/warning goes away, the LED pattern will stop flashing but if the fault warning reappears again later, the process will repeat.

If only faults or warnings exist then the latest fault or warning will be annunciated. If faults and warnings both exist, then only the last fault occurrence will be displayed.

Application Firmware Running This is a Normal condition and no additional action is required. The application firmware on the Advanced Module is operating correctly and there are no CRC errors. The Plus status LED is solid Green.

Application Disable Jumper In This is a Normal firmware flashing condition and no additional action is required. The application disable jumper at JP3 is installed in position 1-2 and then power to the IntelliVAC Plus module was applied or cycled. Note: IntelliVAC Plus power refers to the 120V/240V mains input power or to the 24VDC DeviceNet Power.

This jumper is used to allow flashing of the Basic and Advanced modules.

With only DeviceNet power, only the Advanced module can be flashed.

In this mode the product firmware will not be operational as this is strictly a flashing mode. The application jumper at JP3 must be installed in position 2-3 and then power cycled to allow the product firmware to operate. See Chapter 8 for Firmware Flashing. The Plus status LED is flashing Green at a 0.25Hz rate so that the LED is on for 2 seconds, then off for 2 seconds and then it repeats.


1503-UM054D-EN-P – March 2015

Programming Base Unit(s) This is a Normal firmware flashing condition and no additional action is required. The Basic module is in the process of being flashed from a PC over the RS485 communications link. The data rate for this process is 9600 baud. See Chapter 8 for Firmware Flashing. The Plus status LED is flashing Green at a 0.50Hz rate so that the LED is on for 1 second, then off for 1 second and then it repeats.

No Power from IB or DeviceNet This is a Normal condition if there are no input power sources to the IntelliVAC Plus module. If this condition exists and there is at least one source of external power supplied to the IntelliVAC Plus unit then a serious problem may exist. Refer all servicing for qualified service personnel or see the trouble shooting section in Chapter 10. The Advanced module has no power from either the Basic module or from DeviceNet. The causes of the loss of Basic module power are either that there is no 120/240V mains input power to the IntelliVAC Plus module or that this input voltage is <50Vrms. Also, the internal DC power source on the Basic module has failed or the internal DC power source on the Advanced module has failed, or both. Also, there is no DeviceNet power or the internal DC power source of the Advanced module has failed. The IntelliVAC Plus status LED is off.

RTC Fail This is a Warning condition which may not be rectified by the user. Refer all servicing to qualified service personnel, or see the trouble shooting section in Chapter 10. The Real Time Clock circuitry is not responding which will prevent the Event Log (see Event Log in Chapter 4) from time stamping events with the correct local time. The Plus status LED is pulsing Green with a pattern of 2 pulses.


1503-UM054D-EN-P – March 2015

Line Undervoltage This is a Warning condition which may not be rectified by the user. Check input line voltage levels and rectify if possible. The line mains input voltage has gone to a voltage level of <95Vrms when the contactor is initiating a close cycle or the input voltage has gone below a voltage level of 80Vrms when the contactor is in a hold cycle. If the Time Delay Undervoltage (TDUV) feature is enabled (see Appendix B) them the contactor will remain energized for as long as the TDUV feature is set (see Appendix B). The Line Undervoltage warning is an aggregate warning for each of the five (5) IB units. The Plus status LED is pulsing Green with a pattern of 3 pulses.

Line Overvoltage This is a Warning condition which may not be rectified by the user. Check the input line voltage levels and rectify if possible. The line input voltage has gone to a voltage level of >265Vrms which may be a dangerous voltage level for the IntelliVAC Plus unit. If the input line voltage exceeds 280Vrms then the integrity of the product will be jeopardized and a critical failure may occur.

The Line Overvoltage warning is an aggregate warning for each of the five (5) IB units.

The Plus status LED is pulsing Green with a pattern of 4 pulses.

Extended Close Time This is a Warning condition used as a wear indicator of the contactor over its lifetime which may not be rectified by the user. Check the mechanical condition of the contactor. The close time of the contactor has increased to a value beyond the normally accepted time of 90mS to a value >150mS (see Table 4.G for maximum close values for each contactor). The Extended Close Time warning is an aggregate warning for each of the five (5) IB units. The Plus status LED is pulsing Green with a pattern of 5 pulses.


1503-UM054D-EN-P – March 2015

Table 4.G – Contactor Extended Close Times

CONTACTOR CONFIGURATION @ Vinput Max Close Time

@ 120V Max Close

Time @ 240V

400A Mech. Latch (7.2 kV) 150 ms 150 ms 400A Elec. Held (7.2 kV) 150 ms 150 ms

800A Mech. Latch (7.2 kV) 150 ms 150 ms 800A Elec. Held (7.2 kV) 150 ms 150 ms

The ‘Extended Close Time’ Warning is used to indicate that there is a potential problem with one or more of the up to five contactors in an MC system. The normal close time for a contactor should never exceed 200 ms, however, if it exceeds the values in Table 4.G, then this is an indication that there may be a potential problem with one or more contactors. To perform this measurement the close time will be averaged over the last 5 closures. A measurement of the actual close time for each of the five contactors is available as a DeviceNet parameter (see Appendix B). To indicate to the user which contactor(s) have an ‘Extended Close Time’ problem the following DeviceNet messaging should be displayed as follows: ‘IB1 Extended Pick Up Time =’ ‘Present’ or ‘Not Present’ ‘IB2 Extended Pick Up Time =’ ‘Present’ or ‘Not Present’ ‘IB3 Extended Pick Up Time =’ ‘Present’ or ‘Not Present’ ‘IB4 Extended Pick Up Time =’ ‘Present’ or ‘Not Present’ ‘IB5 Extended Pick Up Time =’ ‘Present’ or ‘Not Present’

These messages will indicate all of the contactors that have had an Extended Close Time condition.

DeviceNet Power Loss This is a Warning condition which indicates that the DeviceNet power on connector P1 (pins 5,1) has decreased below 10VDC. For this warning to be annunciated, the DeviceNet power must have been good (i.e. >10VDC) before the loss of this power. If an IntelliVAC Plus were to power up without any DeviceNet power then this warning would not occur. DeviceNet power must have been available at some point and then lost before this warning is annunciated. Check the DeviceNet power source or the connections on the P1 (pins 5.1) connector. The IntelliVAC Plus status LED is pulsing Green with a pattern of 6 pulses.


1503-UM054D-EN-P – March 2015

MC Altitude Setting Warning

This is a Warning condition which indicates that the Altitude DIP switch settings on the Basic modules in an MC system (one [1] Basic module on the IntelliVAC Plus module and up to four [4] Basic modules on the IntelliVAC MC units) are not all set to the same value. This is an issue because all of the contactors in an MC system will be installed at the same altitude so that there would not be a reason for each of the contactors to have different altitude settings. Because of this all of the units must have the same altitude settings. Having incorrect settings for altitude will cause the coil currents, for contactors with the incorrect altitude settings, from being correct thus preventing proper closure of the contactor (too little current) or causing contactor damage (too much coil current). The Plus status LED is pulsing Green with a pattern of 7 pulses.

In RESET Mode or Firmware (F/W) Crash This is a Fault condition which indicates that the IntelliVAC Plus is in RESET mode or that the F/W has crashed and is no longer operating correctly. To alleviate this problem, the mains power and/or the DeviceNet power should be cycled. The Plus status LED is solid Red or it could be Green or it could be Yellow or it could be pulsing between Red and Yellow or pulsing between Green and Yellow. The reason for this variation is that the Plus status LED is actually comprised of two individual internal LEDs; a Red LED and a Green LED. During a RESET mode the Red LED is forced on but the Green LED will be off. However, during a F/W crash both the Red and Green LEDs will be under control of runaway F/W which could cause any of the two LEDs to be turned on at any time. This F/W crash condition will be short lived because protection circuitry will eventually force the IntelliVAC Plus module into RESET which will cause the Plus status LED to be Red only.

POST Failure – RAM This is a Fault condition which indicates that the internal RAM of the IntelliVAC Plus module is faulty. This will prevent proper operation of the firmware. Because of this the product firmware cannot be executed. The Plus status LED is pulsing Red with a pattern of 2 pulses.


1503-UM054D-EN-P – March 2015

Application Programming Error – CRC

This is a Fault condition which indicates that the Application Firmware being programmed into the internal Flash did not program correctly. This error was detected by way of the CRC from the programmed memory not corresponding to the CRC of the original source file. The only functionality that the IntelliVAC Plus has is that it will run the BootLoader firmware and send out the menu over the RS485 link at a 9600 baud rate to a PC. Another attempt can now be made to Flash the IntelliVAC Plus unit again. The Plus status LED is pulsing Red with a pattern of 5 pulses.

RS485 Communications Fault (IB Fault) This is a Fault condition which indicates that the one or more of the Basic units connected, has an RS485 communications error. This may be the Basic unit contained in the IntelliVAC Plus or one of the Basic units in an IntelliVAC MC module. When this error occurs, proper operation of the IntelliVAC Plus or IntelliVAC MC system is no longer possible. The Plus status LED is pulsing Red with a pattern of 6 pulses.

IB1 Power Loss

This is a Fault condition which indicates that the Basic module, within the IntelliVAC Plus, has lost its internal DC power. Because of this, the Basic module is not operational so that contactor control cannot be performed. The reason for the loss of the Basic module power may be due to loss of the main input power or because of a faulty internal power supply. The Plus status LED is pulsing Red with a pattern of 7 pulses.

Coil Open This is a Fault condition which indicates that there are one or more open contactor coils. The fault monitors both the main coil(s) in an electrically held contactor or the close and trip coils in a mechanically latched contactor. The Plus status LED is pulsing Red with a pattern of 8 pulses.


1503-UM054D-EN-P – March 2015

There is a Red/Green bi-color LED which is used to indicate the DeviceNet network operating status. Only the Red or Green LED should be on at any one time.

Table 4.H shows the operation of the DeviceNet Network Status LED as well as the faults/warnings that it indicates.

Table 4.H – DeviceNet Network Status LED



Warning Off Flashing IE determining network baud rate or device is in idle mode

Warning Off Flashing On-line but not allocated to master

None Off Solid On Normal operation & allocated to master

Warning Flashing Off Output fault or configuration error, or I/O connection timed out, or illegal DeviceLogix program downloaded to this device

Fault Solid On Off Bus Off or Duplicate DeviceNet address detected or

Invalid baud rate or other unrecoverable fault

No Power from IB or DeviceNet This is a Normal condition if there are no input power sources to the IntelliVAC Plus module. If this condition exists and there is at least one source of external power supplied to the IntelliVAC Plus unit then a serious problem may exist. Refer all servicing to qualified service personnel or see the Troubleshooting section in Chapter 10. The Advanced module has no power from either the Basic module or from DeviceNet.

The causes of the loss of Basic module power are either that there is no 120/240V main input power to the IntelliVAC Plus module or that this input voltage is <50Vrms. Also, the internal DC power source on the Basic module has failed or the internal DC power source on the Advanced module has failed, or both. Also, there is no DeviceNet power or the internal DC power source of the advanced module has failed.

The DeviceNet status LED is off.

Network Status (DeviceNet)


1503-UM054D-EN-P – March 2015

IE Determining Network Baud Rate

The DeviceNet status LED is flashing Green.

On-Line but Not Allocated to Master The DeviceNet status LED is flashing Green.

Normal Operation & Allocated to a Master This is a Normal condition and indicates that the IntelliVAC Plus is on-line and has connections in the established state. As a UCMM capable device it means that it has one or more established connections. The DeviceNet status LED is solid Green.

I/O Connection Timed Out This is a Warning condition and indicates that the IntelliVAC Plus has one or more I/O connections in a timed-out state. The DeviceNet status LED is flashing Red.

Bus Off or Duplicate DeviceNet Address Detected or Invalid Baud Rate

This is a Fault condition and indicates that the IntelliVAC Plus has failed communication. The device has detected an error that has rendered it incapable of communicating on the network. This may be due to one of the following conditions: i) DeviceNet failure during power-up ii) duplicate DeviceNet address detected and iii) Invalid baud rate).

The DeviceNet status LED is solid Red.

Module Status (DeviceNet)

As per the ODVA rules the LED used for IE Faults/Warnings (Module Status LED) will also be used for DeviceNet Module Status. The function of this status LED is already defined in Table 4.F for the IE module. However, this IE module status LED will also have a combined usage along with the DeviceNet Module Status. The functionality of the DeviceNet Module Status LED is shown in Table 4.I.

Network Status (DeviceNet) (cont.)


1503-UM054D-EN-P – March 2015

Table 4.I – DeviceNet Module Status LED



Warning Off Flashing In standby – needs commissioning

None Off Solid On Normal operation

Warning Flashing Off Recoverable fault or device MAC switch address is

changed online

Fault Solid On Off Unrecoverable fault

None Flashing Flashing Device self testing

No Power from IB or DeviceNet This is a Normal condition if there are no input power sources to the IntelliVAC Plus module. If this condition exists and there is at least one source of external power supplied to the IntelliVAC Plus unit then a serious problem may exist. Refer all servicing to qualified service personnel or see the trouble shooting section in Chapter 10. The Advanced module has no power from either the Basic module or from DeviceNet. The causes of the loss of Basic module power are either that there is no 120/240V mains input power to the IntelliVAC plus module or that this input voltage is <50Vrms. Also, the internal DC power source on the Basic module has failed or the internal DC power source on the Advanced module has failed, or both. Also, there is no DeviceNet power or the internal DC power source of the Advanced module has failed. The DeviceNet status LED is off.

In Standby – Needs Commissioning This is a Warning condition and indicates that the IntelliVAC Plus needs commissioning due to a missing, incomplete or incorrect configuration. The DeviceNet status LED is flashing Green.

Normal Operation This is a Normal condition and indicates that the IntelliVAC Plus is operating in a normal condition. The DeviceNet status LED is solid Green.


1503-UM054D-EN-P – March 2015

Recoverable Fault This is a Warning condition and indicates that the IntelliVAC Plus has a minor recoverable fault: for example, the node MAC switch address is changed online. The DeviceNet status LED is flashing Red.

Unrecoverable Fault This is a Fault condition and indicates that the IntelliVAC Plus has an unrecoverable fault. The unit may require replacement. The DeviceNet status LED is solid Red.

Device Self Testing This is a Normal condition and indicates that the IntelliVAC Plus is in a self-test mode. The DeviceNet status LED is alternately flashing Red and Green.

7-Segment LED Display The 7-segment LED display (see Figure 4.3) is used mainly to

display the IntelliVAC Plus RS485 address. For a stand-alone IntelliVAC Plus unit this address is set to 1. The secondary function of the 7-segment display is to annunciate faults/warnings which are present. These faults/warnings are listed in Table 4.J.

Figure 4.3 --Segment LED Address/Fault/Warning Display

If only faults or warnings exist then the latest fault or warning will be annunciated. If faults and warnings both exist, then only the last fault occurrence will be displayed.


1503-UM054D-EN-P – March 2015

For the 7-segment LED display, the ‘Watchdog Timeout’ and the ‘System Lock-Out State’ will have the highest priority with the ‘Watchdog Timeout’ being the higher of the two.

If there are multiple MC faults, then the highest MC fault, only, will be displayed on the 7-segment display.

Note: See Figure 4.1 for the 7-segment LED display

Note that all of the Fault codes displayed on the 7-segment LED display refer to RS485 errors or fatal errors where the display would no longer be useful for displaying address information.

RS485 Incorrect/Duplicate Addresses

This is a Fault condition and indicates that the IntelliVAC MC system has IntelliVAC MC units with incorrect and/or duplicate RS485 addresses. The MC address for the individual units must be changed using the DIP switches on the IntelliVAC MC module (see Table 8.H and figure 8.2). The RS485 addresses must contain only the addresses up to and including the maximum number of units in the MC system. For example, in an MC system with three units, there must only be addresses ‘2’ and ‘3’ selected by the two IntelliVAC MC modules, as address 1 is already defined by the IntelliVAC Plus unit. If addresses ‘2’ and ‘2’ are selected (duplicated addresses) or addresses ‘2’ and ‘4’ (incorrect addresses) are selected then this Fault code will be displayed.

The 7-segment display will display the solid character ‘-1’.

Table 4.J – 7-Segment LED Display Fault Codes

FAULT/WARNING SEGMENT

MODE DESCRIPTION a b c d e f g DP

RS485 Incorrect/Duplicate Addresses Off On On Off Off Off On Off Solid ‘-1’ MCC Bad MC #1 Off On On Off Off Off Off Off Flash ‘1’ MCC Bad MC #2 On On Off On On Off On Off Flash ‘2’ MCC Bad MC #3 On On On On Off Off On Off Flash ‘3’ MCC Bad MC #4 Off On On Off Off On On Off Flash ‘4’ MCC Bad MC #5 On Off On On Off On On Off Flash ‘5’

Incorrect MCC RTERM Installed Off Off On On On On On Off Flash ‘6’ System Lock-Out State On On On Off Off Off Off Off Flash ‘L’ + MC address ‘1’

Bad/no DeviceLogix Prog for MC System On On On On Off Off On Off Solid ‘3’

Lost +15V Rail From IB1 On On On Off Off Off Off On Flash ‘7+DP’ Watchdog Timeout – Fatal Error (NMI) On On On On On On On On Flash ‘8+DP’


1503-UM054D-EN-P – March 2015

MC Bad MC #1

This is a Fault condition and indicates that the IntelliVAC MC #1, which is contained in the IntelliVAC Plus module, has a faulty RS485 communications. The 7-segment display will display the flashing character ‘1’.

MC Bad MC #2

This is a Fault condition and indicates that the IntelliVAC MC #2, which is an external module, has a faulty RS485 communications. The 7-segment display will display the flashing character ‘2’.

MC Bad MC #3


MC Bad MC #4


MC Bad MC #5


Incorrect MC RTERM Installed This is a Fault condition and indicates that there is an incorrectly enabled RS485 termination resistor installed in an MC system. In an MC system, where an IntelliVAC Plus and one or more IntelliVAC MC units are installed, there must be a termination resistor enabled on the last IntelliVAC MC unit in the system. Therefore, for a two unit system, i.e. one IntelliVAC Plus and one IntelliVAC MC unit, the termination resistor must be enabled on the IntelliVAC MC unit.

Note: There is no provision to install a termination resistor on the IntelliVAC Plus unit as this unit already has this resistor permanently installed.


1503-UM054D-EN-P – March 2015

See Table 8.K for a definition of which IntelliVAC unit is to have the termination resistor inserted. See Table 8.J for instructions detailing how to enable the termination, resistor using the DIP switches on the MC board. The 7-segment display will display the flashing character ‘6’.

System Lock-Out State This is a Fault condition and indicates that in an MC system configuration, a particular fault has been reset three times without having the fault clear. This indicates that the fault is problematic and that the problem needs to be inspected. An MC system will not accept any command inputs, when in the ‘System Lock-Out’ state. The 7-segment display will alternate between displaying the character ‘L’ + and the MC address which is ‘1’.

Bad/No DeviceLogix Program for MC This is a Fault condition and indicates that in the DeviceLogix Custom configuration (module #0), either there is no program present or there is an operational error present. A possible error would be to have both the Set and Reset inputs of an R-S flip flop set to an active level. Normally the error would have been flagged by the software that generated the DeviceLogix program, such as RSNetWorx, but could still have been downloaded to the IntelliVAC Plus unit.

The 7-segment display will display the solid character ‘3’.

Lost +15V Rail from IB1 This is a Fault condition which indicates that the Basic module, within the IntelliVAC Plus, has lost its internal DC power. Because of this, the Basic module is not operational so that contactor control cannot be performed. The reason for the loss of the Basic module power may be due to loss of the mains input power or because of a faulty internal power supply.

Note: The ‘IB1 Power Loss’ fault in Table 4.F and the ‘Lost +15V Rail From IB1’ fault in Table 4.J, are the same faults. This duplication is provided so that if there are multiple faults present, in an IE unit, from either Table 4.F or Table 4.J, then a user will still have an indication of the IB1 power loss from one of the indicators (LED or 7-segment LED display).


1503-UM054D-EN-P – March 2015

The 7-segment display will display the flashing character ‘7’ + ‘Decimal Point’.

Watchdog Timeout – Fatal Error This is a fatal Fault condition which indicates that the Enhanced module program has crashed and is no longer executing correctly. In this case the watchdog timer has been allowed to time out. The 7-segment display will display the flashing character ‘8’ + ‘Decimal Point’.

The IntelliVAC Plus unit has eight (8) hardware inputs that can be programmed either for use by DeviceLogix (see Chapter 9) or for use by external devices on DeviceNet.

Each of the eight (8) inputs has an associated Yellow LED on the front panel of the IntelliVAC Plus unit. The LEDs will turn on when the corresponding hardware input has a valid input voltage. For a description of the voltage levels which will cause the input LEDs to turn on see Table 3.A.

The IntelliVAC Plus unit has two (2) hardware outputs that can be programmed either for use by DeviceLogix (see Chapter 9) or for use by external devices on DeviceNet.

Each of the two (2) outputs has an associated Yellow LED on the front panel of the IntelliVAC Plus unit. The LEDs will turn on when the corresponding hardware output has been turned on. For a description of the load ratings which the outputs can sustain see Table 1.B.

Output LEDs

Input LEDs

Figure 4.4 – Input/Output LEDs

Hardware Input Status LEDs

Hardware Output Status LEDs

Chapter 5

1503-UM054D-EN-P – March 2015

IntelliVAC Plus Basic Wiring

Fuse Protection The IntelliVAC module requires external fuse protection to

coordinate with the power supply and contactor. The fuse ratings shown in Table 5.A allow the passage of inrush currents expected when the contactor is closed, or from recommended external capacitors for the TDUV option. They will also protect the contactor coils in the event of a module malfunction.

The recommended fuses have been tested to ensure reliable

protection of the module. If the supply voltage is DC, the module must be used with an external fuse that is approved for and rated to interrupt the DC voltage supply. The types listed are Ferraz-Shawmut Midget Fuses (1-1/2" X 13/32"). The TRM is a time-delay type, rated 250 VAC. The ATM is a fast-acting type, rated 500 VDC.

Table 5.A – IntelliVAC Plus Fuse Protection

Rated Supply Voltage Contactor Type Recommended Fuse

(minimum) (maximum)

110/120 VAC 400A EH TRM 2 TRM 3.2 800A EH TRM 2 TRM 6.25

400/800A ML TRM 2 TRM 3.2


400/800A ML TRM 2 TRM 6.25

125 VDC 400A EH/ML ATM 3 ATM 3 800A EH/ML ATM 5 ATM 6


EH = Electrically Held vacuum contactor ML = Mechanical Latch vacuum contactor

Note: If external capacitors are connected, or more than one

IntelliVAC module is protected by a common control fuse, the maximum recommended fuse should be used to prevent fuse opening due to increased inrush current when control power is applied.

IntelliVAC Base Wiring

5-2 IntelliVAC Plus Basic Wiring

1503-UM054D-EN-P – March 2015

Grounding The IntelliVAC module must be connected to a common ground terminal (PE) on the controller panel. The ground terminal is located on the bottom of module enclosure (refer to Figure 5.1).


It is important that IntelliVAC is properly grounded using the ground connection provided. Failure to do so may result in damage to equipment or personal injury.

Connections There are five green connectors on the IntelliVAC Plus module for

connections to the control circuitry. Connector plugs are provided with the module. If additional plugs are required, refer to Appendix D, Spare parts.

Control Power The IntelliVAC can accept either AC or DC control power. Refer to

Table 1.B for acceptable input power and control signal ratings. Control power is applied to the module with a two-pole connector

located at the bottom rear portion of the module. Refer to Figure 5.1 for connections. The ‘L1’ connection is intended to be the ‘Hot’ or ‘+’ side of the control power, and the ‘L2/N’ connection is intended to be the ‘Neutral’, ‘Return’, or ‘-’ side of the control power.

Status Relays Status relay connections are accessed with a four-pole connector

located at the bottom front portion of the module. Refer to Figure 5.1 for connections. There are two status relays, each with one normally-open contact:

Module Status: Terminals 13 and 14 Contactor Status: Terminals 15 and 16

L2/NL1CONTACTOR STATUS OUTPUT (N.O.) MODULE STATUS OUTPUT (N.O.) POWER INPUT

13 14 15 16

Ground Connection

Figure 5.1 – IntelliVAC Base Bottom Side Connections

IntelliVAC Plus Basic Wiring 5-3

1503-UM054D-EN-P – March 2015

Interface Connections Further control interface connections are made at a twelve-pole

connector located on the top of the module. Refer to Figure 5.2 and Table 5.B for connections (and Table 1.B for electrical ratings).

CONTACTOR INTERFACE

11 128 9 105 6 72 3 41

EX. CAP.

Figure 5.2 – Top side connections

Table 5.B – Terminal Assignments for IntelliVAC Base Interface Connections

Terminal No. Terminal Designation Description

1 External capacitor (negative) Power connection for TDUV or capacitor trip options only

2 External capacitor (positive)

3 Latch trip coil (common) Output for mechanical latch contactor trip coil

4 Latch trip coil

5 Close coil (common) Output to close coil of electrically held & mechanical latch contactors

6 Close coil

7 Open / Jog command / IB Input 2

Input to open a mechanical latch contactor or jog an electrically held contactor (mutually exclusive). Also used as a Digital input point to DeviceLogix

8 Open / Jog command / IB Input 12(common)

9 Close command / IB Input 1 Input to initiate the closure of electrically held and mechanical latch contactors. Also used as a Digital Input Point to DeviceLogix

10 Close command / IB Input 1 (common)

11 Contactor auxiliary contact Input to indicate the state of the contactor (typically wired to a normally closed auxiliary contact) 12 Contactor auxiliary contact

Refer to Table 1.B for electrical ratings. No connection required if option is not used or DeviceLogix control mask is selected. Functionality of input is dependent on the connected contactor, and user selected logical mask.

Mask 0 forces this input to be a dedicated open command if a mechanically latched contactor is connected, or a Jog command if an electrically held contactor is connected. Logic Masks 1 and 3 cause this input to be ignored. Logic Mask 2 causes this input to be a Digital Input point into DeviceLogix control Logic.

Functionality of input is dependent on the connected contactor, and user selected logical mask. Mask 0 forces this input to be a dedicated close command. Logic Masks 1 and 3 cause this input to be ignored. Logic Mask 2 causes this input to be a Digital Input point into DeviceLogix control Logic.


1503-UM054D-EN-P – March 2015

When configured for basic control the IntelliVAC Plus can be applied with two- or three-wire control circuits. The control system utilized will determine the configuration of the input wiring. Consider the following input and output for the type of control used:

• Terminals 9 and 10 – Close Contactor/ IB-Input1 • Terminals 15 and 16 – Contactor Status

In either case, the CLOSE input must receive a maintained voltage

high to keep the contactor closed.

Notes:

1. When used with electrically held contactors, the IntelliVAC allows close commands every six seconds. This is to ensure the rated contactor duty cycle is not exceeded.

2. If the IntelliVAC powers up configured for an electrically held contactor, and the vacuum contactor is detected as being closed, the module will not respond to a close command until the vacuum contactor auxiliary contact input is in the correct (closed) state and module power is removed and re-applied.

3. In general, a Close command should only be applied 4 seconds after energizing IntelliVAC.

Two-Wire Control If using two-wire control, the CLOSE/ IB input 1 contactor input is

maintained high using a single contact. Momentarily opening this input will cause the IntelliVAC to open the contactor. Maintaining the contact will provide a CLOSE command to IntelliVAC (given that all permissives are satisfied). If a fault occurs, in addition to cycling control power to the IntelliVAC module, the CLOSE command must be removed for a minimum of 4 seconds, before being re-applied. Refer to Figure 5.3.

Some two-wire control schemes may be configured such that a close

command is present when IntelliVAC is energized. In this case, the Power-Up Safety feature may be disabled by setting DIP switch 12 accordingly. Refer to Table 8.F.


Only disable the Power-Up safety feature when absolutely necessary. Doing so can create unsafe operating conditions.

Wiring Guidelines Electrically Held Contactors


1503-UM054D-EN-P – March 2015


For Emergency Stop applications requiring removal of power, a contact should be placed in the “L1” control power rung to the IntelliVAC. If the TDUV feature is used, the contactor will not open until the programmed TDUV time has expired.

CONTROLPOWERFUSE

CAPACITOR(OPTIONAL) M-IV

EC TCO

AUX CCO

L2/NL1 G

MOV

M

OVERLOAD RUNM-IV

CLOSE

EMERGENCY STOP(when requ ired)

M

1

2

4

3

11 6

12 5

CONTROL POWER

Figure 5.3 – Two-Wire Control

Three-Wire Control If using three-wire control, the CLOSE contactor input is maintained

high using two contacts. Momentarily opening this input will cause the IntelliVAC to open the contactor. Momentarily closing the START contact will provide a CLOSE command to IntelliVAC (given that all permissives are satisfied).

In this configuration, the STATUS output acts as a seal-in contact. If a

fault occurs, in addition to cycling control power over to the IntelliVAC module, the CLOSE command must be removed for a minimum of 4 seconds before being re-applied. Refer to Figure 5.4.


For Emergency Stop applications requiring removal of power, a contact should be placed in the “L1” control power rung to the IntelliVAC. If the TDUV feature is used, the contactor will not open until the programmed TDUV time has expired.

* Refer to Appendix A for recommended sizing.


1503-UM054D-EN-P – March 2015

MOV32

1EC

-

+

4TCO

12

11AUX CCO

5

6

L1 L2/NG

+ -STOP

STARTOVERLOAD

CONTROLPOWERFUSE

*

M-IV

9 10CLOSEM-IV

15 16CONTACTOR

STATUS

M

M-IV

M

CAPACITOR(OPTIONAL)

CONTROL POWER

EMERGENCY STOP(when required)

Figure 5.4 – Three-Wire Control

Figure 5.5 – Timing Diagram 400A (Electrically Held) Contactor for IntelliVAC Control with three-wire Control

Note: The drop-off time would be 6 mS longer if the close command is applied on 1B

Wiring Guidelines Electrically Held Contactors (cont.)

* Refer to Appendix A for recommended fuse sizing.


1503-UM054D-EN-P – March 2015

IntelliVAC control may be used for mechanical latch contactors.

A momentary control signal is needed to close the contactor, and a second momentary control signal is needed to open the contactor. The momentary open/close commands must be at least 50 milliseconds in duration.

Refer to Figure 5.6 for a typical mechanical latch control scheme.

Note:

1. A mechanical latch contactor may already be closed when power is applied to the IntelliVAC control module.

2. It is permissible to apply an open command to the IntelliVAC module as power is re-applied.

MOV

32

1EC

-

+

4TCO

12

11AUX CCO

5

6

L1 L2/NG

+ -

CLOSE

OVERLOAD

CONTROLPOWERFUSE

*

CONTROL POWER

M-IV

9 10

CLOSE

CC

M-IV

M

MOV

TC

M

+ -

M-IV

7 8

OPEN

OPEN

OVERLOAD

* Refer to Table 5.A for recommended fuse sizing.

Figure 5.6 – Mechanical Latch Contactor Control

Wiring Guidelines Mechanical Latch Contactors


1503-UM054D-EN-P – March 2015

Capacitor Trip The IntelliVAC can be configured to provide capacitor trip

functionality with mechanical latch contactors. A capacitor must be connected to the IntelliVAC (terminals #1 and #2) in order to provide this capability. The capacitor provides control power for the IntelliVAC as well as stored energy to trip the contactor. Maximum recommended capacitor size is 1650 µF for 120V control or 330 µF for 240V control. Use of larger capacitors will require a current limiting circuit to prevent opening the control fuse on energization.

The IntelliVAC must receive an ‘OPEN’ command within a few

seconds of losing AC control power. This time limit depends on voltage and capacitor size as shown in the table below. If the elapsed time exceeds this limit, the contactor cannot be tripped by IntelliVAC. In this case, the contactor can be tripped by pressing the release button on the door in front of the contactor.

A separate voltage source is needed to provide the ‘OPEN’ command.

This may be taken from the external capacitor as shown in Figure 5.7.

Table 5.C – Mechanical Latch Contactor – Capacitor Trip Times

Contactor Rating

Nominal Voltage (Vac)

Actual Vinput (Vac)

Ext. Capacitor

(µF)

Max. time for trip (sec)

400 Amp

120

120

1650

3.5

110 2.7

100 1.7

240 240

330 7.5

200 4.7

Note: Minimum capacitor voltage ratings:

• 120V applications – 200V DC (250V DC preferred)

• 240V applications – 400V DC (450V DC preferred)

Mechanical Latch Contactors


1503-UM054D-EN-P – March 2015

MOV

321

EC-

+

4TCO

1211

AUX CCO56

L1 L2/NG

+ -

CLOSE

OVERLOADCONTROLPOWERFUSE

*

CONTROL POWER

M-IV

9 10CLOSE

CC

M-IV

M

MOV

TC

M

+ -

M-IV

7 8OPEN

OPEN

CAPACITOR

OVERLOAD


Figure 5.7 – Mechanical Latch Contactor with Capacitor Trip Option

Time Delay Undervoltage The IntelliVAC can be configured to provide time delay undervoltage (TDUV) protection. The feature is available to keep electrically held contactors closed during a voltage dip or brief power loss. This option may require the addition of a capacitor (see Table 5.D). Refer to Table 5.E for typical capacitor sizing. The capacitor is connected to terminals 1(-) and 2(+) of the IntelliVAC. (Refer to Figure 5.8)


If the TDUV feature is used, the contactor will not open until the programmed TDUV time has expired. Therefore, applications requiring an immediate removal of power during emergency stop conditions are not compatible with the TDUV feature.


Do not enable the TDUV feature if the input contactor is feeding a PowerFlex 7000 drive with the Safe Torque Off option. Refer to Table 8.D


1503-UM054D-EN-P – March 2015

Table 8.E of the “Configuration/Programming” Chapter 8 has the DIP switch settings to provide TDUV from 0.2 to 2 seconds. IntelliVAC can provide TDUV protection without the use of an external capacitor, as shown in Table 5.D.

Table 5.D – Maximum TDUV Time (without Capacitor)

Control Voltage Max. TDUV Time (secs)

400 A 800 A

110/120 V 0.2 0.2 220/240 V 1.0 1.0

If the undervoltage condition persists beyond the set delay time, the

contactor will be opened and an undervoltage fault or warning condition will occur (see Line Undervoltage and Table 4.F in Chapter 4).

Table 5.E – Maximum TDUV Time (with Capacitor)

Control Voltage Max. TDUV Time (sec)

Capacitor 400A 800A

110/120V 2.0 2.0 1650uF - 80158-779-51-R 220/240V 2.0 2.0 330uF - 80158-779-52-R


MOV32

1EC

-

+

4TCO

12

11AUX CCO

5

6

L1 L2/NG

+ -STOP

STARTOVERLOAD

CONTROLPOWERFUSE

*

CONTROL POWER

M-IV

9 10

CLOSEM-IV

15 16

CONTACTORSTATUS

M

M-IV

M

CAPACITOR

Figure 5.8 – TDUV Control Circuit


1503-UM054D-EN-P – March 2015

Figure 5.9 – Wiring Diagram for Full Voltage Non-Reversing Logic Mask


1503-UM054D-EN-P – March 2015

Figure 5.10 – Wiring Diagram for Full Voltage Non-Reversing Logic Mask (2)

Note: In this configuration the user must upload appropriate control logic to the DeviceLogix Control engine.

Chapter 6

1503-UM054D-EN-P – March 2015

Wiring

Wiring (MC) Pre Configured Logic Mode The IntelliVAC Plus comes with five (5) preprogrammed logic programs corresponding to the five most common types of Rockwell Automation MV controllers requiring multi contactor control. The five preconfigured logic blocks are: RVAT (reduced voltage autotransformer starter) RVR (reduced voltage reactor starter) FVR (full voltage reversing starter) SMC (“smart motor controller” solid state reduced voltage starter) SMC+ PFCC (“smart motor controller” with the addition of

power factor correcting capacitors) These control profiles can be selected in the device parameters page in RSNetworx. They are located in the Control parameter group.

Figure 6.1 – Example Parameter List

6-2 Wiring (MC)

1503-UM054D-EN-P – March 2015

Wiring (MC) (cont.) After selecting the desired control program, the IntelliVAC Plus

module must be reset to adopt its new settings and load the logic from main memory into the DeviceLogix engine. In order to accomplish this simply cycle the control power of the unit. Note: Be sure to remove both the 120VAC power to the

IntelliVAC module, and the 24VDC DeviceNet power. When power is restored to the IntelliVAC Plus the new program will be active in DeviceLogix. In order to view the logic in the DeviceLogix editor you must first refresh the RSNetworx network file. In order to accomplish this delete the IntelliVAC Plus icon from the network view and perform a scan of the network in order to obtain the updated settings. When the scan is complete, select the IntelliVAC Plus module and open the DeviceLogix editor in Function block mode select upload for the prompt.

Note: In order for pre programmed logic to function correctly the

hardware inputs to the IntelliVAC Plus MUST be wired according to the Multi contactor wiring guide of Chapter 6.

Note: Only timer values may be changed in pre programmed

program. If any other changes are required the user must use the “User Customized Logic” option. Their logic is read-only in firmware. If you would like to modify the logic or force I/O value in DeviceLogix editor, an error message will pop up. The only changeable attribute is the timer’s preset value.

Note: The following conditions must be met in order to enable a

pre configured logic block: The system must be running free of faults or warnings All Hardware inputs on the Plus module must be “0”

or all HW inputs on the module must be disconnected All contactors must be OPEN and the DeviceLogix

engine must be in the “stopped” state The IE module must be configured for the appropriate

number of contactors see Configuration The “DeviceLogix” control mask must be selected.

See “Logical Masks” in Chapter 9.

Wiring (MC) 6-3

1503-UM054D-EN-P – March 2015

Figure 6.2 – Wiring Diagram for Full Voltage Reversing

Configuration Required:

Gate #34 Off Delay Timer Reverse Contactor Gate #32 Off Delay Timer Forward Contactor Gates # 32 and 34 are the close command disable timers for the respective contactors, typically these timers are set to an equal value. The purpose of these timers is to allow a motor turning in the forward direction a pre determined amount of time to come to a stop before the reverse contactor can be closed and vice versa. Preset Value: 10 Seconds

6-4 Wiring (MC)

1503-UM054D-EN-P – March 2015

Figure 6.3 – Wiring Diagram for SMC Flex

ATTENTION This circuit is set up for Soft Start or Current Limit Starting.

Maximum two starts per hour with a minimum of five minutes between starts.

Wiring (MC) 6-5

1503-UM054D-EN-P – March 2015

Figure 6.4 – Wiring Diagram for SMC Flex (cont.) Configuration Required: None



6-6 Wiring (MC)

1503-UM054D-EN-P – March 2015

Figure 6.5 – Wiring Diagram for SMC Flex with PFCC



Wiring (MC) 6-7

1503-UM054D-EN-P – March 2015

Figure 6.6 – Wiring Diagram for SMC Flex with PFCC (cont.)

Configuration Required: None



6-8 Wiring (MC)

1503-UM054D-EN-P – March 2015

Figure 6.7 – Wiring Diagram for Reduced Voltage Reactor

RVR Configuration Required:

Gate 21 On delay timer (Incomplete Sequence Timer, IST) Gate 18 On delay timer (Transition Timer, 1TR)

Wiring (MC) 6-9

1503-UM054D-EN-P – March 2015

Incomplete Sequence Timer The Incomplete sequence timer is designed to ensure that the duty cycle of the reactor is not exceeded in a single start. It controls the maximum amount of time which the unit will pass current through the reactor. If a transition to full voltage has not been made before the incomplete sequence timer expires the start will be aborted, and the unit will be locked from beginning another start until it is manually reset using the reset push button. Default setting: 15 Seconds

Transition Timer The Transition Timer controls the amount of time the starter will provide reduced voltage to the motor. When this timer expires the run contactor will close which will bypass the reactor and provide full voltage to the motor. Default setting: 10 Seconds

6-10 Wiring (MC)

1503-UM054D-EN-P – March 2015

Figure 6.8 – Wiring Diagram for Reduced Voltage Auto Transformer

RVAT Configuration Required:

Gate 23 On delay timer (Incomplete Sequence Timer, IST) Gate 21 On delay timer (Transition Timer, 1TR)

Wiring (MC) 6-11

1503-UM054D-EN-P – March 2015

Incomplete Sequence Timer The Incomplete sequence timer is designed to ensure that the duty cycle of the autotransformer is not exceeded in a single start. It controls the maximum amount of time which the unit will pass current through the autotransformer. If a transition to full voltage has not been made before the incomplete sequence timer expires the start will be aborted, and the unit will be locked from beginning another start until it is manually reset using the reset push button. Default setting: 15 Seconds

Transition Timer The Transition Timer controls the amount of time the starter will provide reduced voltage to the motor. When this timer expires the run contactor will close which will bypass the reactor and provide full voltage to the motor. Default setting: 10 Seconds

6-12 Wiring (MC)

1503-UM054D-EN-P – March 2015

Chapter 7

1503-UM054D-EN-P – March 2015

Communications

The communications systems implemented within the IntelliVAC Plus product can be divided into three sections:

1) RS232 2) RS485 3) DeviceNet

RS232 Communications

This interface is used for factory programming of the CPU and is only to be used by factory authorized personnel.

RS485 Communications

This interface is used for three purposes:

1. For internal communications between the IntelliVAC Base and IntelliVAC Enhanced boards which are contained within the IntelliVAC Plus product.

2. For inter-module communications between the IntelliVAC Plus and the IntelliVAC MC products, to coordinate control actions amongst up to five medium voltage vacuum contactors.

3. For Flashing the IntelliVAC Base and IntelliVAC Enhanced boards in an IntelliVAC Plus product or Flashing the IntelliVAC Base board within an IntelliVAC MC product.

For Item 1 & 2

The communications within the IntelliVAC Plus module, as well as within the IntelliVAC MC system, operates at a 125K baud rate. Extensive error checking is provided to prevent incorrect data from corrupting operation of the entire system. Various error indicators and DeviceNet parameters are available to indicate that there is an RS485 communications error present. See Chapter 10 for RS485 Faults/Warnings. For Item 3

When the RS485 interface is used for Flashing product firmware, the system operates at a 9600 baud rate. The RS485 interface does not use any hardware handshaking lines to control bus access or software handshaking such as XON/XOFF. In this configuration a PC should be connected to the RS485 port using a shielded cable and an RS232 to RS485 converter such as the Moxa Technologies model TCC-1001. This adapter also requires the use of an external 24VDC power supply. See Programming in Chapter 8 for details on Flashing using

7-2 Communications

1503-UM054D-EN-P – March 2015

the RS485 interface, for both the IntelliVAC Base and IntelliVAC Enhanced modules.

This interface is used for two purposes:

For external communications to a DeviceNet network allow the IntelliVAC Plus and IntelliVAC MC product to be controlled and monitored by an external controller unit.

For Flashing the IntelliVAC Plus using ControlFLASH. i) This communications protocol operates at three different baud

rates: 125K, 250K and 500K. Various error indicators and DeviceNet parameters are available to indicate that there is a DeviceNet communications error present. See Tables 4.H and 4.I for DeviceNet Faults/Warnings.

ii) When the DeviceNet interface is used for Flashing product

firmware, the ControlFLASH utility must be used. In this configuration a PC should be connected to the DeviceNet port using a shielded cable and a DeviceNet card such as a 1747-SDNPT or 1789-PCD PCMCIA card. See Updating IntelliVAC Plus Application Code in Chapter 8 for details on Flashing using the DeviceNet interface.

DeviceNet Baud Rates The IntelliVAC shall support 125, 250 and 500k Baud data rates, selectable via a parameter. The default baud rate will be 125k. Selection of the DeviceNet baud rate will be as follows:

‘Select DNet Baud = ‘ ‘125/250/500’ The DeviceNet baud rate parameter will be available on DeviceNet in the following manner:

‘DNet Baud = ‘ ‘125k’ or ‘250k’ ‘ or ‘500k’

AutoBaud Rate The AutoBaud Rate feature allows the DeviceNet communications baud rate to be set automatically when the IntelliVAC plus is part of a network with at least one other device attached. This feature will override the DeviceNet Baud Rate setting feature when it is enabled. Selection of the AutoBaud operation will be as follows:

‘Select AutoBaud =’ ‘Enabled’ or ‘Disabled’

DeviceNet Communications

Communications 7-3

1503-UM054D-EN-P – March 2015

If AutoBaud is enabled then the DNet Baud that was selected will be overridden with the baud rate detected on the network. If no network activity is detected, then the baud rate will be set to the default baud rate of 125k.

DeviceNet MAC ID The address of the IntelliVAC Plus device shall be settable either through DeviceNet or through the MAC ID rotary switches which are accessible on the side of the IntelliVAC Plus enclosure. These rotary switches allow an address range of 00 to 99 although only values of 00 to 63 are allowable. Note: The data read from the rotary switches must be inverted due

to the operation of the switches.

Rotary Switch

Figure 7.1 – Rotary Switch

Selection of the MAC ID will be as follows:

‘Set MAC ID = ‘ ‘00’ to ‘63’ The default MAC ID shall be set to ‘01’ The MAC ID setting can be viewed as follows:

‘MAC ID = ‘ ‘00’ to ‘63’ There shall be a DeviceNet parameter which will allow the MAC ID to be set, either from DeviceNet or from the rotary switches. If the rotary switches do not contain a valid address then the default address will be used.

The MAC ID (read-only parameter) selection source setting will be as follows:

‘MAC ID Source = ‘ ‘DNet’ or ‘Switches’ default is Dnet

7-4 Communications

1503-UM054D-EN-P – March 2015

DeviceNet Profile The IntelliVAC Plus is defined within the “miscellaneous device” object class; however, extended functions may be required compared to devices currently included in this class. It will have the following capabilities with respect to DeviceNet:

Slave operation, with Master (scanner) devices Peer-to-peer messaging (Explicit, I/O) Explicit Messaging I/O Messaging (Bit-Strobe, Poll Command/Response, Change of

State/Cyclic and Multicast Poll) Unconnected Message Manager (UCMM)

Compatibility with IntelliCENTER The IntelliVAC Plus is compatible with IntelliCENTER software. This will include the “PCP Object”, as used by the IntelliCENTER software to define attributes related to a device.

It shall be possible for IntelliCENTER to properly display the type of contactor controlled by the IntelliVAC by reading IntelliVAC parameters. DeviceNet Communications Loss With a loss of the DeviceNet communications, the IntelliVAC Plus module has a selection of two modes to define its operation for DeviceLogix. To accomplish this, a parameter will be used. This parameter will have two selectable options: ‘Hold State’ and ‘Reset’. Selection of the DeviceNet communications loss parameter will be as follows: Select DeviceNet Loss = ‘ ‘Hold State’ or Reset State’ The DeviceNet communications loss parameter will be available on DeviceNet in the following manner: DeviceNet Loss = ‘ ‘Hold State’ or ‘Reset State’ Hold State will cause all DeviceLogix outputs to maintain their last operating state. Reset State will cause all DeviceLogix outputs to reset to their default state.

Communications 7-5

1503-UM054D-EN-P – March 2015

Hold State In general when the hold state option is selected the unit will continue to function based on the last known state of the network commands. This will require the unit to function slightly differently dependent on the logic mask selected, and the number of IntelliVAC MC units which are connected.

Mask Network Logic mask 1 is considered a direct command mask; this means that the commands are acted upon directly without the use of DeviceLogix. If the Hold state option is selected as well as logic mask 1 all contactors will simply retain their current state until a connection is re-established and a command is given to change their state. Only 1 IB option has this mask. Note: In logic mask 1 a “Net Start” command will be considered an

“energize IB-OUTA” command and a “net stop” command will either be considered a “de-energize IB-OUTA” (electrically held contactor) or a “energize IB-OUTB” (mechanically latched contactor)

Mask DeviceLogix Logic mask 2 requires the functionality of DeviceLogix in order to create direct commands to the contactor(s). As such, it is possible that when communication is lost, that the DeviceLogix code may be in the process of executing a sequence of timed commands. If this occurs the IntelliVAC Plus will assume all network inputs to be unchanged and continue to execute the DeviceLogix logic. It is important that if a network command is required in the logic for a critical event, (one that could cause damage if not executed in a certain time frame, i.e. the transition of an autotransformer which is only rated to carry current for 15 seconds) that sufficient logic be built into the DeviceLogix logic such that if a command is not received within the critical time the logic will abort the start sequence.

Reset State If the RESET STATE option is selected and the selected logic mask is 1, or 2 the IE will reset all outputs to the OFF (0) state and wait until a network connection is established, at which point it will begin executing logic as if power had been cycled on the IE unit.

7-6 Communications

1503-UM054D-EN-P – March 2015

Mask HIM/PC Logic mask 3 is considered a test and diagnostic state. As such if network communication is lost when operating with logic mask 3 selected the unit will always reset regardless of the selected loss of communication state parameter. Note: Logic mask 0 is not affected by a loss of communication

regardless of whether the “HOLD STATE” or “RESET STATE” options are selected since this logic mask accepts commands only from local HW I/O.

Multi-Contactor Control Bus (MC) An MC system is capable of controlling up to four (4) IntelliVAC MC units with one (1) IntelliVAC Plus unit being the main controller. In an MC system the address of each of the IntelliVAC MC units must be correct so that there will be the correct number of units in the particular MC configuration with no duplicate addresses selected. The address is set by DIP switches on the MC module that is attached to each IB unit in the IntelliVAC MC unit. The IB unit that is attached to the IE unit in an IntelliVAC Plus will always be address 1 and the IE unit will always be address 0. See Table 8.H for a description of the DIP switch settings. The 7-segment LED display on the IntelliVAC Plus unit, will display address 1 and not 0 (the address of the IE unit is not displayed). Other IntelliVAC MC units will display the address selected by the DIP switches. If the addresses selected are not in the range of 2 to 5, then the display will remain blank.

Chapter 8

1503-UM054D-EN-P – March 2015

Configuration/Programming

Configuration IB Board DIP Switches

Some of the functionality of the IntelliVAC Plus product is derived from the settings of the DIP switches on the IB board. The DIP switch settings are only read once after a power up sequence occurs. If changes are to be made to the DIP switch inputs, then control power must be recycled before the changes will take affect.

Firmware Label

DIP Switch

Figure 8.1 – IntelliVAC Base Module Configuration DIP Switches Altitude This set of switches defines the altitude, above/below sea level, that the vacuum contactor will be operating at. The altitude settings define the operating currents required for the contactor coils with the required compensation for the varying force on the bellows of the vacuum contactor bottles due to the changes in atmospheric pressure. Note: These altitude settings are used exclusively to determine the

altitude. These settings cannot be set on the IE module but can only be read from the IB module.

8-2 Configuration/Programming

1503-UM054D-EN-P – March 2015

This set of switches defines the amount of time, after an OPEN command has been issued, when the contactor actually drops out. This setting may be overridden by the DeviceNet parameter associated with each IntelliVAC base. See Appendix B for a description.

Table 8.B – Drop Out Time Settings

DROP OUT TIME DIP SW1

4 5 6

50 mS OFF OFF OFF

75 mS OFF OFF ON

100 mS OFF ON OFF

130 mS OFF ON ON

150 mS ON OFF OFF

175 mS ON OFF ON

200 mS ON ON OFF

240 mS ON ON ON

Note: The drop off time would be 6mS longer if the close command

is applied on IB.

Contactor Type This set of switches defines the type of vacuum contactor that is to be controlled. Note: These settings are used exclusively to determine the

contactor type. These setting cannot be set on the IntelliVAC Plus module but can only be read from the IB module.

Table 8.A – Altitude Settings

ALTITUDE (m)

DIP SW1

1 2 3

-1000…0 OFF OFF OFF

0…1000 OFF OFF ON

1001…2000 OFF ON OFF

2001…3000 OFF ON ON

3001…4000 ON OFF OFF

4001…5000 ON OFF ON

Not defined ON ON OFF

Not defined ON ON ON

Contactor Drop Out Time

Configuration/Programming 8-3

1503-UM054D-EN-P – March 2015

Table 8.C – Contactor Type

CONTACTOR CONFIGURATION DIP SW1 DIP SW2

7 8 1 2 400A Mech. Latch (7.2kV) OFF OFF OFF OFF 400A Elec. Held (7.2kV) OFF OFF OFF ON 800A Mech. Latch (7.2kV) OFF OFF ON OFF 800A Elec. Held (7.2kV) OFF OFF ON ON Not Allowed OFF ON OFF OFF Not Allowed OFF ON OFF ON Not Allowed OFF ON ON OFF Not Allowed OFF ON ON ON Not Allowed ON OFF OFF OFF Not Allowed ON OFF OFF ON Not Allowed ON OFF ON OFF Not Allowed ON OFF ON ON Not Allowed ON ON OFF OFF Not Allowed ON ON OFF ON Not Allowed ON ON ON OFF Not Allowed ON ON ON ON

Time Delay Undervoltage Enable (TDUV)

This setting determines whether the contactor maintains closed during the occurrence of an input line voltage dip or brief power outage. An undervoltage will occur when the input line decreases to <95Vrms, just before a Close cycle is initiated or the input line decreases to <80Vrms during the Hold cycle. This setting is used exclusively to determine the TDUV Configuration. This setting cannot be set on the IE module but can only be read from the IB module.

Table 8.D – TDUV Configuration

TDUV Configuration DIP SW2

3 TDUV disabled OFF

TDUV enabled ON


Do not enable the TDUV feature if the input contactor is feeding a PowerFlex 7000 drive with the Safe Torque Off option (-24STO, -24STORK). Set DP SW2 – 3 to OFF.


1503-UM054D-EN-P – March 2015

Time Delay Undervoltage Configuration (TDUV)

This setting controls the amount of time that the contactor maintains closed on the occurrence of an input line voltage dip. This setting may be overridden by the DeviceNet parameter TDUV Hold-Up Time Source See Section TDUV Programmability in Appendix B for a description.

Table 8.E – TDUV Hold-Up Times

TDUV Hold-up Time DIP SW2

4 5

0.2 Sec OFF OFF

0.5 Sec OFF ON 1.0 Sec ON OFF 2.0 Sec ON ON

Power-up Safety

This setting determines how the unit will respond to having a CLOSE, JOG or TRIP command present during power-up, in the following manner. If the Power-up Safety feature is Enabled:

– The unit will ignore the CLOSE or JOG command and generate a warning condition.

– The unit will respond to a TRIP command and immediately open the contactor (ML contactor).

– After power-up, if the command is removed the unit will respond to the reapplication of a CLOSE or JOG command.

If the line voltage goes below the Undervoltage Close (Vin < 95V) or below the Undervoltage Hold (Vin < 80V) or below the Line Loss/Power Loss (Vin < 50V), even if the TDUV feature is enabled, then, once the voltage recovers to > 95V (as long as the electronics has not completely reset), then the IE/IB will be seen as having gone through a power-up sequence. In this case the IE/IB will treat the Power-up Safety feature just as it would when the unit is freshly powered up from a zero voltage line condition and it will follow the Power-up safety rules above.

If the Power-up safety feature is Disabled:

– The unit will respond to a CLOSE command and immediately close the contactor.

– The unit will respond to a TRIP command and immediately open the contactor (ML contactor).

– The unit will treat a JOG command the same as if the Power-up safety feature is Enabled.


1503-UM054D-EN-P – March 2015

This function is useful for applications that require a contactor to re-close after a voltage dip or voltage loss. This setting is used exclusively to determine the Power-up safety mode. It cannot be set on the IE module, but can be read from the IB module.

Table 8.F – Power-Up Safety Configuration

Power-up Safety DIP SW2

6 Enabled OFF Disabled ON

Future Use

These DIP switches are not used and are for future use. Table 8.G – Future Use

Future Use DIP SW2

7 8 Not used OFF OFF Not used OFF ON Not used ON OFF Not used ON ON

MC Board DIP Switches

Some of the functionality of the IntelliVAC MC product is derived from the settings of the DIP switches on the MC board. The DIP switch settings are only read once after a power up sequence occurs. If changes are to be made to the DIP switch inputs, then control power must be recycled before the changes will take affect.

Figure 8.2 – MC Board Configuration DIP Switches


1503-UM054D-EN-P – March 2015

MC RS485 Addressing This set of DIP switches defines the RS485 address of the

IntelliVAC MC unit(s) within an MC system.

Table 8.H – MC RS485 Address Settings

MC Address DIP S1

Description 1 2 3

0 OFF OFF OFF Not allowed – allocated to Advanced Module

1 OFF OFF ON Not allowed – allocated to IB1 module 2 OFF ON OFF Valid MC Address 3 OFF ON ON Valid MC Address 4 ON OFF OFF Valid MC Address 5 ON OFF ON Valid MC Address 6 ON ON OFF Invalid MC Address 7 ON ON ON Invalid MC Address

RS485 Termination Resistor This one DIP switch defines whether a termination resistor will be inserted between the RS485A and RS485B differential data lines on the particular IntelliVAC MC unit. It is used only on the IntelliVAC MC module with the highest address in an MC system. This resistor provides a load for the transmitter such that there are no reflections of the transmitted signal. In effect the termination resistor provides the load with a received signal which is a duplicate of the transmitted signal, with no distortion.

Table 8.J – RS485 Termination Resistor Configuration

RTERMINATION DIP S1

6

Termination resistor not inserted OFF Termination resistor inserted ON


In an MC system the termination resistor must be installed in the IntelliVAC MC unit with the highest address, only. If the correct termination resistor is not installed, then an ‘Incorrect MC RTERM Installed’ fault will be displayed on the 7-segment LED display. (See Troubleshooting Procedures in Chapter 10).


1503-UM054D-EN-P – March 2015

Table 8.K – Termination Resistor Installation in IntelliVAC MC System

Units in MC

System

IntelliVAC Plus

Address 1

IntelliVAC MC #1

Address 2

IntelliVAC MC #2

Address 3

IntelliVAC MC #3

Address 4

IntelliVAC MC #4

Address 5 RTERM Status RTERM Status RTERM Status RTERM Status RTERM Status

1 Inherent N/A N/A N/A N/A 2 Inherent Inserted N/A N/A N/A 3 Inherent Not Installed Inserted N/A N/A 4 Inherent Not Installed Not Installed Inserted N/A 5 Inherent Not Installed Not Installed Not Installed Inserted

The IntelliVAC plus system is made of up two boards each of which contains distinct firmware modules. The IntelliVAC Plus contains a bootloader and an application, and the IntelliVAC Base contains a separate bootloader and application. These pieces of firmware have been designed to operate together to offer several different options for updating firmware of both modules.

IntelliVAC Base Module Bootloader The IntelliVAC base module bootloader is a program which is programmed onto the main processor of the IntelliVAC base module during construction of the module. The purpose of the base module bootloader is to allow the IntelliVAC base module firmware to be upgraded in the field. It uses a simple interface and can be accessed through the serial port, and hyper terminal program included with any windows based personal computer.

IntelliVAC Base Module Application Code The application code is the code responsible for performing all functions of the IntelliVAC base. It is upgradeable via the IntelliVAC base module bootloader, and any PC with a serial port, and hyper terminal software.

IntelliVAC Plus Bootloader The IntelliVAC plus bootloader firmware is programmed onto the main processor of the IntelliVAC plus during manufacturing. It has the ability to be upgraded in the field, via either DeviceNet using the control flash application, or using a serial port and hyper terminal on any personal computer.

Programming


1503-UM054D-EN-P – March 2015

Programming the IntelliVAC Base Module The IntelliVAC base module firmware is updated using the RS-485 terminal on either an IntelliVAC MC, or an IntelliVAC Plus board. In order to perform a firmware update on the IntelliVAC Base module you will require the following: 1. Either an MC or IE board 2. An RS-485 to RS-232 converter 3. RS-232 cable 4. A personal computer with a functional serial port.

Programming the IB using an IE Board In order to flash firmware to the base module using the IntelliVAC Plus module take the following steps.

Power down the unit.

Remove The RS-485 link that goes from the IE module to any other MC modules, and connect this cable to the RS-485 to RS-232 converter per the following picture.

Figure 8.3 – Hardware Set-up for Flashing Firmware


1503-UM054D-EN-P – March 2015

Move the application disable jumper to the “Program” position as noted on the printed circuit board.

Connect the RS-485 to RS-232 converter to the personal computer using an RS-232 cable.

Open a new connection in hyper terminal and configure the connection as shown below:

Figure 8.4 – Serial Port Configuration

With hyper terminal running power up the unit, the following IntelliVAC Plus bootloader screen will appear:


1503-UM054D-EN-P – March 2015

Figure 8.5 – IntelliVAC Plus Bootloader Menu

Select the option “Update IntelliVAC base” which will pass control to the IntelliVAC base module, which will then flash its bootloader menu to the screen. Refer to the section Flashing IntelliVAC Base using bootloader

Flashing IntelliVAC Base Module using Bootloader

Code can only be flashed to the IntelliVAC base module using the RS-485 interface, and hyper terminal with any personal computer with a usable serial port. There are two ways to display the IntelliVAC base bootloader screen. The first is to select “Update IntelliVAC base” from the IntelliVAC plus bootloader menu, and the second is by using an IntelliVAC MC board with application disable jumper set to program mode. When using an IntelliVAC MC board to enter the bootloader screen any key on the PC keyboard must be pressed within the first second after seeing the bootloader menu appear otherwise the bootloader will perform its usual startup checks and begin running application code.


1503-UM054D-EN-P – March 2015

Figure 8.6 – IntelliVAC Base Bootloader Menu

The IntelliVAC base bootloader screen has four options: 1. Verify current firmware 2. Upload new firmware 3. Power on reset IntelliVAC 4. Run current firmware

Verify Current Firmware This option performs a CRC check on the full program memory of the IntelliVAC and compares the calculated value to the correct value which is stored in the firmware. If the two CRCs match, then “OK” is displayed. Additionally this screen also checks and displays the revision number of the firmware for reference purpose. This information is also available in the IntelliVAC plus parameters page on DeviceNet. Once the CRC and firmware revision are displayed a prompt to press any key will be displayed. Pressing any key on the PC keyboard will return the user to the main IntelliVAC base module bootloader menu.


1503-UM054D-EN-P – March 2015

Figure 8.7 – IntelliVAC Base Programming Completed

Upload New Firmware

The upload new firmware option allows the application firmware of the IntelliVAC to be updated to a new version. The file should be provided by Rockwell technical support only. When the “Upload new firmware “option is selected a prompt will appear to begin an X-MODEM-CRC transfer. The user must:

Click on the “Transfer” menu in the upper right of the Hyper Terminal screen

Select “send file”

When the dialog box opens select “Xmodem” in the protocol drop down box

Select browse and select the firmware file provided by Rockwell technical support

Select “send”


1503-UM054D-EN-P – March 2015

Figure 8.8 - Upload new firmware prompt and send file dialog box

After selecting “Send” the following dialog box will appear and the progress of the transfer will be displayed

Figure 8.9 - modem transfer dialog box


1503-UM054D-EN-P – March 2015

Upon completion of the transfer the transfer dialog box will disappear. The CRC of the new firmware file will be calculated and displayed. If the CRC is good an “OK” will appear beside the CRC and the user will be prompted for input. Pressing any key on the keyboard will return the user to the bootloader main menu.

Figure 8.10 - Transfer complete

Power on Reset IntelliVAC

The power on reset option allows the user to restart the IntelliVAC unit without removing power. This allows the user to keep the hyper terminal window open and observe the boot up sequence. The correct boot up sequence for a unit with valid firmware is to display the bootloader menu for a period of approximately 1 second then run the application code. The user can determine when the application code is running by observing the Module status LED. The module status LED is orange when in bootloader mode and green when the application code is running.

Updating IntelliVAC Plus Application Code

The most common method of updating the application code of the IntelliVAC Plus module is using a DeviceNet connection to the module, and Control flash software. Alternatively the firmware can be updated using RS-485 interface similar to the IntelliVAC base module.


1503-UM054D-EN-P – March 2015

Updating the IntelliVAC Plus using Control Flash

In order to update the firmware of the IntelliVAC Plus module using DeviceNet you will need the following:

1. Personal computer equipped with a DeviceNet interface such as a 1784-PCD or 1770-KFD

2. RS-Links Software 3. Control Flash Software 4. A functioning device net network including 24VDC DeviceNet

power supply.

Flashing FW using Control Flash

Browse DeviceNet network using RSLinx to ensure that the network is communicating correctly and the IntelliVAC Plus is found

Figure 8.11 - View IntelliVAC Plus using RSLinx

Once you have verified that your network is functioning correctly by finding the IntelliVAC Plus open Control flash software

Select “Next” at the opening screen, you will then be prompted to locate the firmware file to be flashed. Select the “Browse” option and locate the firmware file which has been supplied by Rockwell technical support. Once this is complete select “Next”

A browser window similar to RSLinx will appear select the IntelliVAC Plus then select “OK”


1503-UM054D-EN-P – March 2015

Figure 8.12 - Select IntelliVAC Plus in Control Flash

After selecting “OK” the serial number of the device and firmware number to be flashed will be displayed select “Finish”

A progress bar will appear displaying the status of the transfer. When the transfer is complete the unit will be restarted and the following screen will be displayed after a diagnostic delay of approximately 20 seconds. The firmware update is now complete.

Figure 8.13 Firmware Update Complete


1503-UM054D-EN-P – March 2015


It will be necessary to cycle power on all modules in the Multi contactor network to re-establish communication between master and slave modules.

IE/IB Firmware Revisions

The firmware revisions for all of the IB units will be made available on DeviceNet as follows:

‘IB1 Firmware Version = ’ ‘xx.y’ ‘IB2 Firmware Version = ’ ‘xx.y’ ‘IB3 Firmware Version = ’ ‘xx.y’ ‘IB4 Firmware Version = ’ ‘xx.y’ ‘IB5 Firmware Version = ’ ‘xx.y’

For the IBx revisions, ‘xx’ can be from 0 to 31 and ‘y’ can be from 0 to 7. If a particular IB unit is not installed or does not respond, ie. due to not having any input power, then its revision will be displayed as 0.0. Note that all leading zeroes of the major revisions will be suppressed.

The IE firmware revision will be made available through either RSNetWorx, in the General window under the Revision parameter, or by use of a HIM, under the Revision menu when the IE unit is selected. There is no special parameter made available on DeviceNet for the IE firmware revision.

Once the IE Firmware is successfully programmed into the IE unit, the event will be recorded to the Event Log as two separate parameters, these being the Major Rev Byte and the Minor Rev Byte. Once the IB firmware is successfully programmed into the IB unit, the event will be recorded to the Event Log.


1503-UM054D-EN-P – March 2015

Chapter 9

1503-UM054D-EN-P – March 2015

DeviceLogix DLX – DeviceLogix refers to the integrated logic capability of the

IntelliVAC Plus. IE – IntelliVAC Enhanced (IntelliVAC Plus module) refers to the module which contains both the IntelliVAC base module, and IntelliVAC Plus boards. IB – IntelliVAC base module refers to a series E or later IntelliVAC module with no additional circuit boards attached. MC – IntelliVAC Multi Contactor module refers to a module which contains both the IntelliVAC base module and the IntelliVAC multi contactor board.

Logical Masks

The purpose of the Logic Mask is to allow the user of the IntelliVAC Plus the ability to prioritize control inputs arriving from different sources i.e. local push-buttons/switches vs. direct network I/O commands. This allows a structured approach as to where commands may originate from. The logic mask defines and prioritizes the source of the command inputs. There will be four different types of masks provided.

Important Terms for Logical Masks

Commands - The IntelliVAC Plus has 5 higher level commands available for use. All commands are available regardless of the number of IB modules connected, or the logic program which is selected.

START STOP FORWARD REVERSE JOG

The commands can be triggered by any input source dependant on the applied logical mask. Each command when given will execute the appropriate control logic dependant on the logic loaded into DeviceLogix.

Common Acronyms and Short forms

9-2 DeviceLogix

1503-UM054D-EN-P – March 2015

Direct Commands

Direct commands are specific commands such as 'open contactor 1' or 'close contactor 4'

1 – Logical Mask 0 (Mask Local) Logic mask 0 can only be selected when the system consists of a single IE/IB combination. In Logic Mask 0, commands will be accepted only from local (hardware) I/O.

In Logic Mask 0, the two inputs on the IB unit will not be generic inputs as they are in all other masks. When operating in Mask 0 the IB input 1 is the close command, and the IB input 2 is the Open command for a mechanically latched contactor. Alternatively IB input 2 may be used as a “JOG” input for an electrically held contactor. 2 – Logical Mask 1 (Mask Network) Logic Mask 1 may only be selected when the system consists of a single IE/IB combination. In Logic Mask 1, commands will be accepted only from remote (network) I/O. 3 – Logical Mask 2 (Mask DeviceLogix) Logical Mask 2 enables commands to be received from DeviceLogix using either network or local sources. In this logic mask the inputs must be prioritized manually within the DeviceLogix control logic. This logic mask will be used for Multi-Contactor (MC) customized scenarios and will use standard logic blocks. For MC control (standard applications), the local I/O (Close, Open/Jog) will default to values as shown in Chapter 6. 4 – Logical Mask 3 (Mask HIM/PC) Logical Mask 3 is a direct control option which is only to be enabled for testing/troubleshooting purposes. When this mask is enabled the IE unit and its attached IB slaves will accept either direct commands (ex. close contactor #2) or higher level commands. The source of these commands may be only from a DeviceNet node #63 which is the standard node for a DeviceNet HIM. The selection of the Logic Mask in DeviceNet is as follows: Select Logic Mask = ‘0 – Local’

‘1 – Network’ ‘2 – DeviceLogix’ ‘3 – HIM’

DeviceLogix 9-3

1503-UM054D-EN-P – March 2015

DeviceLogix What is DeviceLogix DeviceLogix functionality has been added to a number of Rockwell Automation devices to control outputs and manage status information locally within a device. The configuration of the DeviceLogix functionality is accomplished through the DeviceLogix Editor. The DeviceLogix Editor includes two kinds of logic configuration tools for DeviceLogix devices to meet different configuration preferences:

Function Block Editor – Provides a graphical interface for configuring functional blocks to provide local control within DeviceLogix capable devices.

Ladder Editor – Provides a ladder-style configuration tool for DeviceLogix capable devices.


The IntelliVAC Plus has been optimized for use only with the function block editor. It is required not to use the ladder editor with the IntelliVAC Plus.

The DeviceLogix editor is an applet of the RSNetWorx for DeviceNet software and DriveTools software, and it can be launched directly from those host applications. With DeviceLogix capable devices, you can enable logic operation using the DeviceLogix editor to provide local control over the device’s operation. A DeviceLogix device consists of:

A specific number of inputs and/or outputs.

Local logic that determines its behavior.

Inputs and Outputs Inputs and outputs can be one of two types:

Physical – Inputs and outputs realized by physical connections to the device. These are referred to as Discrete Inputs or Discrete Outputs.

Networked – Inputs consumed by the device from the network and outputs produced by the device onto the network.

Input and Output Bits There are five types of DeviceLogix inputs. Inputs are read from the Electronic Data Sheet (EDS) file or are created dynamically during logic configuration. The inputs that are read from the EDS file cannot be modified. The DeviceLogix inputs are:

9-4 DeviceLogix

1503-UM054D-EN-P – March 2015

Device Input – A physical input of the device. Device inputs

represent the actual inputs, such as sensors or switches which are attached to a particular device.

Network Input – Formerly called Consumed Network Bit (CNB), network input is data sent from a master that can be used in the device’s logic.

Device Status – Status inputs indicate the state of the device. For example, if an explicit message connection exists between the device and a master, and input called “explicit connection exists’ is set to true and possibly affects logic the device performs.

Device Fault – Faults are conditions that report device errors. For example, if a device detects a short circuit on an output a fault input is set to true and possibly affects the logic the device performs.

There are two types of DeviceLogix outputs: Device Output – Hardware outputs that are actual outputs, such

as lights and actuators, attached to a particular device. Without DeviceLogix functionality, the master would normally control the outputs via consumed data. In fact, if there is no local logic controlling an output, the master controls the output as it would if DeviceLogix functionality were not running on the device. However, within DeviceLogix functionality, if the local logic controls an output, the master no longer controls the output. The only way the master can affect the state of an output that is under local control is to route requests to the local logic by using network inputs. Some outputs can be under local control while others can still be controlled by the master.

Network Output – Formerly called Produced Network Bit (PNB). Network outputs report the results of the local logic to a master and are part of the produced data from the device.

Local Function Block Logic The local logic of a DeviceLogix device consists of function blocks, inputs, outputs and connections (wires) between them. Function blocks contain connection points (called pins) and perform a specific function. Inputs and outputs also have connection pins and represent the actual hardware devices, networked data, and fault and status bits that are available for use in the local logic.

DeviceLogix 9-5

1503-UM054D-EN-P – March 2015

A connection (wire) between function blocks is defined when an input pin of one function block is bound to an output pin of another function block. A Pin can be Bound to a:

Pin of another function block. Physical input/output. Networked input/output. Fault or status bit. Miscellaneous bit. Function blocks may also have attributes that influence their function. Configuring a DeviceLogix device consists of defining or editing the local logic that is present on the device along with the EDS parameters for that device.

RSNetworx for DeviceNet Software Operating Modes RsNetWorx for DeviceNet software lets you select online or offline mode, as described below: Offline – RSNetWorx for DeviceNet software is not connected to

the network Online – RSNetWorx for DeviceNet software is connected to the

network and is capable of communicating with devices on the network

DeviceLogix Operating Modes The mode that RSNetWorx for DeviceNet software is in directly affects the way DeviceLogix Editor behaves when it is launched. When online with the device, DeviceLogix functionality provides two alternative states: Pending Edits and Animated

Table 9.A – DeviceLogix Operating Modes

Mode Description

Offline

The DeviceLogix Editor does not communicate with the device. If RSNetWorx software is offline, the DeviceLogix Editor is also offline. When offline, you can edit existing DeviceLogix configurations or create new configurations.

Online

Pending Edits

When online with a device, pressing the edit button or selecting Tools > Edit enables Pending Edits. Pending Edits allows a device’s configuration to be edited while online. When your edits are complete, the configuration must be downloaded to the device.

Animated

When online and animated, DeviceLogix functionality allows a device’s configuration to be monitored in “real time”. Real time includes comms throughput latencies. Depending on the device, you may be able to change presets and accumulated values.

9-6 DeviceLogix

1503-UM054D-EN-P – March 2015

Launching the DeviceLogix Editor

After you configure the properties for the IntelliVAC Plus, you can launch the DeviceLogix Editor. There is an additional tab in the device properties dialog box for all DeviceLogix enabled devices. This tab is labeled DeviceLogix. The tab provides access to the start up window for the DeviceLogix Editor. You have the option to fill in your name, a revision number and a description of your configuration (all optional fields).

Figure 9.1 – Launching DeviceLogix Editor

Note: If you are online and you click either the Parameters of the DeviceLogix tab, you may be prompted to upload or download the device. When you are online, the dialog checks the configuration in the device and compares it to the current configuration. If the configurations are not the same, you must upload from or download to the device to make the configurations the same before you can make changes. If you need to make changes without uploading or downloading, you can exit the dialog bog, go offline and re-enter the dialog box to make the desired changes.

To start the DeviceLogix Editor for a DeviceLogix enabled device, click “Start Logic Editor”. On the DeviceLogix Editor style Selection Dialog, you are prompted to select the editor type that you want to launch. Select the Function Block editor, click “OK”.

DeviceLogix 9-7

1503-UM054D-EN-P – March 2015

Figure 9.2 – Select Logic Editor Type


The IntelliVAC Plus is optimized for use with the Function Block Editor. It is recommended that users select the Function Block Editor at all times.

Figure 9.3 – DeviceLogix Editor Screenshot

9-8 DeviceLogix

1503-UM054D-EN-P – March 2015

1. Upload Logic

To upload logic click the Upload Logic icon or alternatively select Communications> Upload. The logic configuration in the device is read and displayed in the Function Block Editor. Any unsaved changes will be discarded and Online Animation Begins.

When you upload, the uploaded information is not automatically stored into the RSNetWorx for DeviceNet software .dnt file. You must make sure that you save any changes after you exit the DeviceLogix Editor to ensure that any changes made to the schematic are saved, including changes made as a result of an upload.

2. Download Logic

To download logic, click the Download Logic icon, or alternatively select Communications > Download. The logic configuration in the Function Block Editor is duplicated and transferred to the device. Before a download can be performed, the logic must pass the verification process. See Verify Logic for more information.

3. Logic Enable On

Use the Logic Enable On icon or alternatively select Communications> Logic Enable On in order to begin logic execution. When set this parameter notifies the device to start processing the stored logic diagram.

4. Logic Enable Off

Use the Logic Enable Off icon or alternatively Communications > Logic Enable Off in order to stop logic execution. When set this parameter causes the device to enter an idle state.

5. Compare Logic

Use the Compare option to determine if the logic in the Function Block Editor matches the logic in the device. The results of the comparison display in a pop up window. To use the compare function select the Compare Logic icon, or select Tools > Compare.

DeviceLogix 9-9

1503-UM054D-EN-P – March 2015

6. Verify Logic

To verify the logic’s syntax, click the Verify icon in the standard toolbar or select Tools> Verify. The verify results will be displayed in the message log window. If an error is identified, double click the error message to have the current caret jump to the error block.

Tip: You can only download the logic to the device after verifying and passing the verification without an error.

7. Toggle Edit Mode

Selecting the Edit icon will change the edit status of the Function Block Editor, and allow editing of the control logic.

8. Add Digital Input Point (DIP)

Selecting the Add DIP icon will add a digital input point to the Function Block Editor. Clicking and releasing the icon will place the DIP in the top left corner of the screen currently in view. Clicking the icon and holding the button will allow the user to drag the new DIP to a desired location.

9. Add Digital Output Point (DOP)

Selecting the Add DOP icon will add a digital output point to the Function Block Editor. Clicking and releasing the icon will place the DOP in the top left corner of the screen currently in view. Clicking the icon and holding the button will allow the user to drag the new DOP to a desired location.

10. Timer/Counter Tab

Selecting the Timer/Counter Tab, will display the timer and counter function blocks in the instruction toolbar.

11. Move/Logical Tab

Selecting the Move/Logical Tab, will display the logical and latch function blocks in the instruction toolbar.

12. Instruction Toolbar

Function blocks are displayed in the Instruction Toolbar. Function blocks can be added by clicking on the desired function.

9-10 DeviceLogix

1503-UM054D-EN-P – March 2015

DeviceLogix Function Block Elements

Function block elements consist of:

I/O components: the input and output source of the product, or I/O information from the network

Function block instructions: all types of DeviceLogix instructions. An instructions I/O path needs to be bound with I/O components of the inputs and outputs of another instruction

Text Comments

I/O Components

In the following sections we will briefly describe each of the I/O components and include their graphic from the Function Block Editor. You can drag each of these I/O components from the instruction toolbar, or click the icon and have it added to the current schematic, or select EDIT> Add Element to add the I/O component. Each newly added I/O component does not have a binding name; you can click it to display a drop down list related to this component type, and then select the one you need.

Digital Input Point (DIP) The following kinds of digital inputs are supported: Physical local Boolean input point Local Boolean fault status Network Boolean input point Local Boolean miscellaneous point

Figure 9.4 – Digital Input Point

DeviceLogix 9-11

1503-UM054D-EN-P – March 2015

Digital Output Point (DOP) The following kinds of digital outputs are supported: Physical local Boolean output point Network Boolean output point

Figure 9.5 – Digital Output Point

DLX Function Blocks Boolean

Boolean AND Boolean OR Boolean XOR Boolean NOT Boolean NAND Boolean NOR Boolean XNOR Bi-stable Function blocks

Latch Set Latch Reset Timers

On delay timer Off Delay timer Pulse Timer Counters

Count Up Counter Up down Counter

9-12 DeviceLogix

1503-UM054D-EN-P – March 2015

Boolean Function Blocks The following truth table describe the boolean function blocks by

listing all possible combinations of inputs and indicating the outputs for each combination.

Table 9.B - Truth Table for Boolean Function Blocks

Function Input 1 Input 2

Output

AND

0 0 0

0 1 0

1 0 0

1 1 1

NAND

0 0 1

0 1 1

1 0 1

1 1 0

OR

0 0 0

0 1 1

1 0 1

1 1 1

NOR

0 0 1

0 1 0

1 0 0

1 1 0

XOR

0 0 0

0 1 1

1 0 1

1 1 0

XNOR

0 0 1

0 1 0

1 0 0

1 1 1

NOT 1 N/A 0

0 N/A 1

Bistable Function Blocks The Bistable function blocks implement standard latches. These include the SR latch (set dominant) and the RS latch (reset dominant). Each latch block has two inputs called input and reset and an output called output. Following is the truth table for the bistable function blocks.

DeviceLogix 9-13

1503-UM054D-EN-P – March 2015

Table 9.C – Bistable Function Block Output Table

Function Reset Input (Set) Output Value

at time = t0 Output Value at time = t0+1

SR set dominant (A set dominant block goes to the set state if both inputs are true.)

0 0 0 00 1 0 11 0 0 01 1 0 10 0 1 10 1 1 11 0 1 01 1 1 1

RS reset dominant (A reset dominant block goes to the false state if

both inputs are true.)

0 0 0 00 1 0 11 0 0 01 1 0 00 0 1 10 1 1 11 0 1 01 1 1 0

Timers

Timer function blocks control the state of a single output based on the value of the accumulator and a Preset. They have two inputs called input and reset which control the counting of the accumulator. In the case of timers the accumulator accumulates time as opposed to events such as a counter. The three timer blocks available are the Pulse Timer, The On-Delay Timer and the Off-Delay Timer. All three timers have a selectable time base of either 1 millisecond or 10 milliseconds. The timers are non-retentive. Only the output status is available for use. No Timer Timing or Timer Done bits are available. The different timers are described below.

Pulse Timer The Pulse timer generates a TRUE value on its output for a fixed amount of time. The duration of the TRUE pulse is determined by the preset value along with the time base of the timer. When the input to the timer changes from FALSE to TRUE, it sends the output to TRUE and starts the accumulator counting. It then increments the accumulator each time the time base number of milliseconds has expired. When the accumulator reaches the preset value the timer resets the output to FALSE. In the pulse timer, the input acts only as a trigger to start the accumulator counting. Once the accumulator starts timing, it continues to rise regardless of the state of the input. As long as the output is TRUE and the accumulator is counting, additional triggers of the input do not affect the state of the output or the count of the accumulator. Once the accumulator reaches the preset value and the

9-14 DeviceLogix

1503-UM054D-EN-P – March 2015

timer resets the output to FALSE the pulse timer can again trigger the process by sensing a FALSE to TRUE transition on the input pin. Even if the input remains on the entire time the accumulator is counting, when the accumulator reaches the preset value the timer resets the output to FALSE. At any point during the operation of the timer, if it detects a TRUE level on the Reset input it will disable the timer and set the output to FALSE. The timer must again be triggered by a FALSE to TRUE transition on the input. This means that if the input is TRUE and the Timer is reset the timer will remain inactive. Even if the reset changes back to FALSE while the INPUT is TRUE, the timer remains inactive. In order to start a new pulse operation, the input must change to FALSE then back to TRUE.

Figure 9.6 – Timing diagram for the Pulse Timer

Table 9.D – Pulse Time Valid Data Ranges

Parameters Data Range

PRE 0 ~ 65535 ACC 0 ~ 65535 Time Base 0 (1 ms), 1 (10 ms)

On Delay Timer

The on delay timer delays the output response to an input by a desired amount of time. When the input is TRUE, the timer increments the accumulator and when the inputs goes FALSE the timer resets the accumulator. For each timebase unit of time, the timer increments the accumulator. When the Accumulator reaches the preset value, the timer sets the output to TRUE. The timer maintains the output TRUE as long as the input remains TRUE. When the input changes from TRUE to FALSE, the timer resets both the output and the accumulator. If the input goes false before the time period specified by the timebase and preset, the output remains FALSE and the accumulator is cleared, essentially ignoring the input.

DeviceLogix 9-15

1503-UM054D-EN-P – March 2015

If the timer senses a TRUE level on the RESET input at any time during the operation of the timer, it resets the output to FALSE and clears the accumulator. Because the reset line is level sensitive the timer remains reset until the timer detects a false on the reset input. Also, because the input is level sensitive, the timer will again begin to increment the accumulator if the reset line goes FALSE while the input remains TRUE.

Figure 9.7 – Timing Diagram for the On-Delay Timer

Table 9.E – On Delay Timer Valid Data Ranges



Off Delay Timer

The off-delay timer works the same way as the on-delay timer but instead of delaying the TRUE status of the output it delays the FALSE status of the output. The input to the timer is a level sensitive FALSE with an edge-triggered reset on the FALSE to TRUE transition. This means that when the input is false, the timer increments the accumulator and when the input goes TRUE the timer resets the accumulator. For each timebase unit of time, the timer increments the accumulator. When the accumulator reaches the preset value, the timer sets the output to FALSE. The timer maintains the output FALSE status as long as the input remains FALSE. When the input changes from FALSE to TRUE, the timer sets the output TRUE and reset the accumulator. If the input goes true before the time period specified by the timebase and preset, the

9-16 DeviceLogix

1503-UM054D-EN-P – March 2015

output remains TRUE, and the accumulator is cleared, essentially ignoring the input. If the timer senses a true level on the reset input at any time during the operation of the timer, it resets the output to false and clears the accumulator. Because the reset line is level sensitive, the timer remains reset until the timer detects a false on the reset input. Also, because the input is level sensitive, the timer will again begin to increment the accumulator if the reset line goes FALSE while the input remains FALSE. However, because the reset logic already set the output to FALSE, the time delay causes no effect because the output is already FALSE. If the input is TRUE when the reset goes FALSE, the timer sets the output to true.

Figure 9.8 – Timing Diagram for the Off-Delay Timer

Table 9.F – Off Delay Timer Valid Data Ranges



Up Counter

The up counter has two inputs called input and reset and out output called output. The up counter simply counts up on a FALSE to TRUE transition and sets its output to TRUE when the accumulator reaches the present value. The accumulator continues to count up until the counter is reset or it reaches 65,535. A TRUE value on the reset input zeroes the accumulator and sets the output to FALSE.

DeviceLogix 9-17

1503-UM054D-EN-P – March 2015

Figure 9.9 – Timing Diagram for the Counter Function with a Preset Value = 3

Table 9.G – Count Up Timer Valid Data Ranges


PRE 0 ~ 65535 ACC 0 ~ 65535

Up Down Counter

The UP/DOWN counter has three inputs called Input, Reset, and count down, and one output called output. The counter increments the accumulator any time the input changes from FALSE to TRUE and decrements the counter any time the counter down input changes from FALSE to TRUE. When the accumulator falls below the preset, the counter resets its output to false. Like the up counter, the UP/DOWN counter resets when a TRUE level is detected on the reset input. When a reset occurs, the counter zeroes the accumulator and sets the output to FALSE

9-18 DeviceLogix

1503-UM054D-EN-P – March 2015

Figure 9.10 – Timing Diagram for the Up/Down Counter with a Preset Value = 3

Table 9.H – Up/Down Counter Valid Data Ranges


PRE 0 ~ 65535 ACC 0 ~ 65535

Offline Operations Once configured the IntelliVAC Plus can operate without a network and perform local control functions. When a network is not used, enable the Comm. Status Override Parameter on the Device Parameters Tab. This will override any errors that are generated because there is no network. If this parameter is not enabled, the Outputs will not react to the local logic.

Online Operations You can perform the following functions when you work Online:

Communicate with devices View the status of I/O with online animation Change Logic Change the value of timers and counters Enable and disable logic Verify logic Compare logic Upload old logic from device to editor Download new logic from editor to device Force Clear Latched hardware faults

DeviceLogix 9-19

1503-UM054D-EN-P – March 2015

Go Online

Once you’ve created your logic and set up your Scanlist or Override parameters, you are ready to go online. While the system is online, you can make changes (for example to the Timer and Counter values) and to the program itself. Perform the following steps to go online in RSNetWorx software: 1. Click the Online icon on the RSNetWorx software toolbar. 2. Once the network browse is completed, double-click the device

that you would like to connect to. The Device Properties tab for that device will then be displayed.

3. Click the DeviceLogix tab. 4. You will be prompted to upload from device or download to the

device. Select the appropriate action and wait for the transfer to complete.

5. Click the Start logic Editor button. You will see:

The local logic resident in the device The real-time status of the inputs and outputs indicated by data

on the connecting wires. Logic Enabled or Logic Disabled displayed in the online toolbar,

depending on the state of the device. You can change the state by selecting the desired state.


The module must be free of faults and warnings to change this state.

The word animated displayed in the status bar, which indicates

that the logic on the screen matches the logic in the device. If you do not see Animated and you and the logic on the screen to match the logic in the device, you must perform and upload or download to synchronize the logic.

6. Double-click on an element. Then select the Parameter tab to

view the updating parameter values.

Change Function Block Attribute Values

Many function blocks have attributes which can be modified online. For example you can change timer block’s preset (PRE) and Accumulator (ACC) while the logic is running. See Figure 9.11

9-20 DeviceLogix

1503-UM054D-EN-P – March 2015

Figure 9.11 – Modify Function Block Attributes

In order to change a value: 1. Double-Click on the face of the function block you want to change. 2. Select Parameters tab 3. Locate the value that you want to change (values which can be

changed are white). Enter the new value in the box 4. Click OK. The new value takes immediate effect. If you are

changing a preset, remember to Save the configuration the next time you exit from the Function Block Editor.

Online Animation

Once you go online and the Logic Enable is set to ON, online animation starts. The status of the I/O can be seen in the Function Block Editor schematic. Note that in the online animation mode you cannot edit instructions.

Change Logic While the Function Block Editor is running and animated, you can change the logic that appears on the schematic by first pressing the Edit button or selecting Tools> Edit. When you change the logic, the Function Block Editor will change from the animated mode into Pending Edits mode. The logic in the device will not be affected and the current program will continue to run. However, the screen will not reflect the real-time status of the logic. The data on the wires will be frozen to whatever it was when you modified the logic. To ensure your changes take effect, perform the following steps:

DeviceLogix 9-21

1503-UM054D-EN-P – March 2015

1. Select Tools>Edit so that a check mark appears on the menu,

indicating that you are in Edit mode. 2. Select Communications>Download You will see a message which tells you that logic is running and asks if you would like to stop it if you:

Select NO – the logic is not downloaded to the device and the current logic continues to run on the device.

Select NO - the online toolbar displays Logic Enable Off.

Select YES – the logic does not continue to run in the device and new logic is downloaded to the device. When the download is complete, you are asked if you want to start the logic running again. If you:

Select YES – the online toolbar displays Logic Enable On; the Function Block Editor is animated. The message Not Saved displays in the status bar until you exit the Function Block Editor and save the new configuration in RSNetWorx for DeviceNet software.

TIP: Note that you can use the edit icon on the standard toolbar to enter edit mode

You can use the download icon on the online toolbar to download logic to the device. Add a Logical Element There are 4 groups of logical elements which can be added to the editor:

Input tags Output Tags Timers/Counters Logical gates/Latches

Add a digital input point (DIP) In order to add an input tag, click the “Bit Input” button. Clicking the button will add an input tag to the top left of the logic currently being displayed the user is then permitted to move the tag to the desired location. Alternatively the user can click the “Bit Input” button and hold the mouse button depressed and drag the new tag onto the screen in the desired location. Once the tag has been added double clicking the tag will display a drop down box with the available input bits to assign to the tag.

Entering Logic Into The Editor

9-22 DeviceLogix

1503-UM054D-EN-P – March 2015

Add a digital output point (DOP) In order to add an output tab click the “Bit Output” button. Clicking the button will add an input tag to the top left of the logic currently being displayed. The user is then permitted to move the tag to the desired location. Alternatively the user can click the “Bit Output” button, hold the mouse button depressed and drag the new tag onto the screen in the desired location. Once the tag has been added double clicking the tag will display a drop down box with the available output bits which can be assigned to the tag. Bit Negation It is possible to Negate a bit (change from a “1” to “0” and vice versa) without the use of a “NOT” gate. This allows the user to minimize the number of gates used, and keep the interface screen less cluttered. In order to negate a bit right click on the line connecting the output of one element to an input of another. Upon clicking the line a drop down box will appear with three options “DELETE”, “ASSUME DATA AVAILABLE”, and “NEGATE”. Select negate. A circle will appear a around the connection line to indicate that it is negated.

Figure 9.12 – Bit Negation Assume Data Available There are some cases in which the logic is executed in a loop and the DeviceLogix compiler cannot determine the execution order of the function blocks. During these cases, the user must manually determine the execution order. In order to identify situations where this must be done use the logic verification tool. If there is a loop in the newly created logic an error message will be displayed upon logic verification. If this is the case the loop which cannot be compiled will be displayed in orange. Follow these steps to resolve the error:

1. Rick click the orange connection. A pull down menu will be displayed.

2. Chose “Assume Data Available”. This will cause the connection to execute first.

3. Use the logic verify tool to ensure that the logic will now execute correctly.

DeviceLogix 9-23

1503-UM054D-EN-P – March 2015

Note: A double arrow will appear on the connection for which data has been assumed available to indicate its status.

Figure 9.13 – Assume Data Available Assume Data Available (alternate method)

There is an alternate technique for creating feedback loops. It is recommended that this method be used for more complex feedback loops, or for bits which must be fed back to multiple input locations. The alternative method makes use of the dual bit functionality of the “Interim 1-5” bits. In order use the alternate method connect the output portion of the dual function bit to the output of bit to be fed back, then simply connect the input portion of the bit to be fed back to the feedback input. Figure 9.14 illustrates the same logical implementation of as figure 9.13 using this alternative method. For further information regarding dual function bits refer to “Dual Function Bits” description further in this chapter.

Figure 9.14 – Assume Data Available Alternate Method

Forcing

The DeviceLogix Function Block Editor provides troubleshooting capabilities by allowing you to force inputs and outputs that allow you to verify the run time result of your logic. To aid in troubleshooting and debugging your schematic, you can force hardware inputs, and outputs. No other inputs or outputs can be forced within the Function Block Editor. Network inputs can be forced in the device from where they originate. If you exit the Function Block Editor with a force enabled, that force will remain in effect until you remove it.

9-24 DeviceLogix

1503-UM054D-EN-P – March 2015

To apply forces, right click on the input or output element you wish to force. A pop-up appears that lists the forcing options.

Figure 9.15 – Forcing

Tip: You cannot use the Force Function in offline mode. Tip: If Logic Enable is Off (logic is not running in the product), the Force function has no effect. In this case, if the Force value is modified, it will not take effect until Logic Enable is On. Tip: You do not have to be in the Edit mode to use forces.

Forcing Inputs The following list describes the input force options.

Table 9.I – Input Forcing

Input Force Option Description

Force On Forces the input ON. Force Off Forces the input OFF.

Remove Force Returns control of the input to the hardware device and turns the instruction color back to white.

Figure 9.16 shows the result of placing a force on an input. When forced, an input element turns yellow with a red triangle indicator and the status value reflects the force state chosen

Figure 9.16 – Input Forced Indication

DeviceLogix 9-25

1503-UM054D-EN-P – March 2015

Forcing Outputs

The following list describes the output force options.

Table 9.J – Output Forcing

Ouput Force Option Description

Force On Forces the input ON. Force Off Forces the input OFF.

Remove Force Returns control of the input to the hardware device and turns the instruction color back to white.

Clear Fault When a device supports latching of faults, this selection clears a hardware output fault indication (for example, off-wire or short circuit).

Figure 9.17 shows the result of placing a force on an output. When force, an output element turns yellow with a red triangle indicator and the status value reflects the force state chosen.

Figure 9.17 – Output Force Indication

Dual Function Inputs

There are several bits which exhibit special behavior for a logic engine. These bits consist of two “tags” to be used in the execution of logic. There is an input tag and an output tag. Stimulus is connected to the output tag which then controls the status of the input tag. The purpose for this is to allow a user to assign an important bit such as “stop status” to a hardware input so that when reviewing the logic the user will be able to use the “stop status” bit as opposed to the “DLX input 1” bit. This is to help a user create his logic in a way which is easier to follow. See the example below for clarification:

9-26 DeviceLogix

1503-UM054D-EN-P – March 2015

Figure 9.18 – Dual Function Bit Behavior

In Figure 9.18, the “Stop” output tag is connected to the hardware input “DLX input 1” and the “protection status” output tag is tied to hardware input “DLX input 2”. The associated “stop” and “protection status” bits are then used to control the status of one of the relay outputs of the IntelliVAC Plus module. List of bits which are dual function:

-Interim 1-Interim 2 -Interim 3-Interim 4 -Interim 5-Protection Status -Speed SW FWD status-Speed SW REV status -Isolation SW status

-Remote Mode Status -Local Mode status -Normal Mode Status -Test Mode Status -Start -Stop -FWD -REV -JOG

Note: None of these status bits will be set without first connecting it to an input tag. All of the bits noted above will not be applicable to any situation.

DeviceLogix 9-27

1503-UM054D-EN-P – March 2015

Customized Logic Mode: This mode allows the user to freely create control logic using all available inputs and outputs associated with the IntelliVAC Plus. Available Inputs: The input tags in DeviceLogix are divided into 4 groups:

Hardware Boolean Status Input Fault Input Network Boolean Hardware Boolean inputs These are the digital input points associated with the 8 hardware inputs in the IntelliVAC Plus module. They are labeled “DLX Input” 1 to input 8 according to the labeling on the external case of the IntelliVAC Plus.

Status Inputs The status digital input points represent a variety of parameters ranging from additional hardware inputs physically located on the IntelliVAC base modules to bits which represent the connectivity status of the network. A list of the available status inputs and their definitions can be found below.

IBX- Aux. This bit represents the status of the auxiliary feedback of its associated contactor. Rockwell standard it to connect a normally closed contactor auxiliary contact to this input. This bit will be “1” when its associated contactor is open and “0” when its associated contactor is closed. There may be up to a total of five IBX-Aux, (ie. IB1-AUX) bits depending on the number of slave contactors connected to the IntelliVAC Plus module.

IBX-Input1 This bit represents the status of the corresponding “close” input on the IntelliVAC Base. When an IntelliVAC is used in a multi contactor system this input does not directly close the contactor but is simply a generic input into the DeviceLogix engine. For further information refer to the section detailing LOGICAL MASKS.

9-28 DeviceLogix

1503-UM054D-EN-P – March 2015

IBX-Input2 This bit represents the status of the corresponding “open” input on the IntelliVAC Base. When an IntelliVAC is used in a multi contactor system this input does not directly open the contactor but is simply a generic input into the DeviceLogix engine. For further information see the section detailing LOGICAL MASKS. Stop Status This is a dual function bit which can be used to describe the status of the multi contactor system. In most systems this bit would be set low whenever any of the contactors in the system are closed and set high only when all contactors in a system are open. The bit would then be communicated via network to give an indication of the status of the system to a remote computer or PLC. Interim 1-5 These are dual function bits which can be used for any purpose the user desires. MC Start Status This bit has a similar function to the recommended use of the stop status bit. It is “1” if any of the contactors in the system are closed, “0” only when all contactors are open. Start

This is a dual function bit which can be used to represent the status of the “START” push button, or other form of start command such as a network input. Stop This is a dual function bit which can be used to represent the status of the “STOP” push button, or other form of stop command such as a network input.

FWD

This is a dual function bit which can be used to represent the status of the “FORWARD” push button, or other form of forward command. This command would be used in a reversing starter. REV

This is a dual function bit which can be used to represent the status of the “REVERSE” push button, or other form of reverse command. This command would be used in a reversing starter.

DeviceLogix 9-29

1503-UM054D-EN-P – March 2015

JOG This is a dual function bit which can be used to represent the status of a “JOG” push button. The purpose of a jog push button is to close the contactor momentarily without having to push the stop push button to open it. This functionality will have to be implemented in the DeviceLogix control logic. Protection Status This is a dual function bit which can be used to describe the status of any protection equipment which is connected to the inputs of the IntelliVAC Plus. Speed SW FWD Status This is a dual function bit which can be used to describe the status of the forward speed switch. These switches are commonly used on a motor which is connected to a reversing starter. Speed SW REV Status This is a dual function bit which can be used to describe the status of the reverse speed switch. These switches are commonly used on a motor which is connected to a reversing starter. Isolation SW Status This is a Dual Function bit which can be used to describe the status of the medium voltage isolation means. This may be an auxiliary contact of the isolation switch, draw out device, or load break switch. Remote Mode Status This is a dual function bit which can be used to describe the status of a selector switch which chooses between local control, and remote control. Local mode status This is a dual function bit which can be used to describe the status of a selector switch which chooses between local, and remote control. Normal Mode Status This is a dual function bit which can be used to describe the status of a selector switch which chooses between normal operation mode, and test operation mode.

9-30 DeviceLogix

1503-UM054D-EN-P – March 2015

Test Mode Status This is a dual function bit which can be used to describe the status of a selector switch which chooses between normal operation, and test operation mode. IBX Out A Status This is a bit which describes the status of its respective IntelliVAC Output A (close coil) output, a “1” indicated the output is energized and the contactor closed. A “0” indicates the output is not energized and the contactor may or may not be open dependent on contactor type (Electrically held vs. mechanically latched) IBX Out B Status This is a bit which describes the status of its respective IntelliVAC Output B (Open coil for mechanically latched contactors). A “1” indicates an energized output resulting in the opening of a mechanically latched contactor. A “0” indicates an output which is not energized. Fault Status This is a bit which describes the fault status of the IntelliVAC Plus module. If any of the fault states exist in the module this bit will “1” otherwise it will be “0” IBX- Healthy Module Contactor open This is a bit which describes the health status of its associated IntelliVAC base module. If there are no faults on the module and the contactor is open this bit will be “1”. The bit will be “0” of there is a fault present on the IB module. IBX-Healthy Module Contactor closed This is a bit which describes the health status of its associated IntelliVAC base module. If there are no faults on the module, and the contactor is closed this bit will be “1”. The bit will be “0” if there is a fault present on the IB module. IBX-Invalid Command Present This bit is set when an invalid command is present on the module. For example if both an open and close command is given simultaneously.

DeviceLogix 9-31

1503-UM054D-EN-P – March 2015

IBX-Mechanical latch Fail to Trip This is a fault bit which only applies to a mechanically latched contactor. The bit is set if a mechanical latch contactor fails to open after being given an open command. IBX-Power up with contactor closed This is a fault bit which applies only to an electrically held contactor. The bit is set if the module powers up and detects that a contactor is already closed before a close command is given. This fault may indicate two potentially hazardous situations.

1) A mechanically latched contactor is installed instead of an electrically held model,

2) The arcing contacts of the medium voltage contactor have failed and the moving contacts have permanently welded together in the closed position.

IBX- Contactor Fails To Pick UP This bit is set if a contactor fails to pick up when a close command is given. IBX-Contactor drop out during hold This is a fault bit associated with an electrically held contactor. It is set if the contactor opens without the close command being removed. IBX- Long Contactor Drop Out Time This is a warning bit which is set when a contactor successfully drops out but the drop out time exceeds the amount of time set in the “drop out time” selection parameter. This can be indicative of contactor wear or other mechanical stress or misalignment. IBX- CPU malfunction This is a fault bit which is set when the IntelliVAC Plus module detects a main CPU malfunction on an associated IntelliVAC Base module. IBX - Power Up With Invalid Dip Configuration This bit is set when a module is powered up with an invalid configuration. This may that the configuration of the dips does not match the contactor which is attached to the IntelliVAC, or that the dip switches have been set to a combination which is not defined.

9-32 DeviceLogix

1503-UM054D-EN-P – March 2015

IBX-Under voltage with close command present This is a warning bit which will be set when the control voltage has dropped below nominal levels, but is either being held up temporarily using the time delay under voltage feature, or is not sufficiently low to cause the contactor to drop out.

Network Boolean Inputs Net In 1-10 These are bits which are can be written to via Device-Net and the input table of the IntelliVAC Plus. The function of these bits is to allow the user to influence the behavior of the module via external inputs from a PLC or other network device. Dedicated Network command bits Net In 11/Net Start The “Net Start” bit behaves differently dependent on the logical mask which is selected. If logical mask 1 is selected the status of this bit is directly tied to the IB1 output A (close coil) output. The contactor will close when this bit is set, and remain closed as long as the bit remains set. The contactor will open with the bit is reset. For further information, refer to Logical Masks. Net In 12/Net Stop The “Net Stop” bit also behaves differently dependent on the selected logical mask. This bit is only functional when the logical mask 1 is selected and a mechanically latched contactor is connected to the IntelliVAC Base. In this circumstance the “Net Stop” bit is directly tied to the IB1 Output B (open coil). Energizing this bit will result in the opening of the mechanically latched contactor. Net In 13/Net FWD, Net In 14/Net Rev, Net In 15/Net Jog These bits are network inputs which have been given descriptive names for the purpose of helping the user identify their function in the control logic. These bits behave similar to the generic Net In 1-10 bits.

DeviceLogix 9-33

1503-UM054D-EN-P – March 2015

Output bits/tags Hardware Boolean Outputs Net out A This bit controls the status of the IntelliVAC Plus relay output A as marked on the front panel of the module. Setting this bit closes the relay output. Resetting the bit opens the relay output Net Out B This bit controls the status of the IntelliVAC Plus relay output B as marked on the front panel of the module. Setting this bit closes the relay output. Resetting the bit opens the relay output.

Network Boolean Outputs Net Out 0/Reset All Faults This bit is used to reset all faults on the IntelliVAC Plus module. Setting this bit high momentarily will reset all the IntelliVAC Plus module faults provided the stimulus causing the fault has been corrected. Caution should be taken when using this feature. Resetting a fault three times simultaneously without removing the stimulus causing the fault will cause the system to enter a “lock” mode which requires power to be cycled on the module in order to resume normal functionality. Net out 1, 2 These are generic bits which can be set at various points in the control logic. These bits are part of the output table of the IntelliVAC Plus and can be read by exterior devices such as a PLC in order to give status indication as to the operation of the control logic. Note there may be additional generic “Net Outputs” available depending on the number of IB slave devices connected. Net Out 3-7/ Interim 1-5 These tags are the output portions of the interim 1-5 dual function tags. The output tags are connected to a stimulus in the logic circuit and will cause their associated interim 1-5 input tags to change state per the example and figure 9.18. Net Out 8/Protection Status This is the output portion of the Protection status dual function bit.

9-34 DeviceLogix

1503-UM054D-EN-P – March 2015

Net Out9/Speed SW FWD Status This is the output portion of the Speed SW FWD Status dual function bit. Net out 10/Speed SW REV Status This is the output portion of the Speed SW REV Status dual function bit. Net Out 11/Isolation SW status This is the output portion of the Isolation SW status dual function bit. Net Out 12/Remode Mode Status This is the output portion of the Remote Mode Status dual function bit. Net Out 13/Local Mode Status This is the output portion of the Local Mode Status dual function bit. Net out 14/ Normal Mode Status This is the output portion of the Normal Mode Status dual function bit. Net Out 15/Test Mode Status This is the output portion of the Test Mode Status dual function bit Net out 16, 18, 20, 22, 24/ IBX Trip Coil These bits represent the “Trip” or “Open” coil for a mechanically latched contactor. Setting this bit will result in opening a mechanically latched contactor. Net Out 17, 19, 21, 23, 25/ IBX Close coil These bits represent the “Close” coil for both the mechanically latched and electrically held contactors. For an electrically held contactor the contactor is closed when the bit is set, and opens when the bet is reset. For a mechanically latched contactor the bit is pulsed to close the contactor and does not require to be maintained set for the contactor to remain closed. Net Out 26/Stop Status This is the output portion of the “Stop Status” dual function bit. Net Out 27/Start This is the output portion of the “Start” dual function bit.

DeviceLogix 9-35

1503-UM054D-EN-P – March 2015

Net Out 28/Stop This is the output portion of the “Stop” dual function bit. Net Out 29/FWD This is the output portion of the “FWD” dual function bit. Net Out 30/REV This is the output portion of the “REV” dual function bit. Net Out 31/Jog This is the output portion of the “Jog” dual function bit.

Customized Logic Simple example Hardware set up for this example:

A Normally open pushbutton is connected to DLX Input 1 A Normally closed pushbutton is connected to DLX Input 2 An Electrically held contactor is connected to the IntelliVAC

Plus unit Per Rockwell Standard a Normally closed contactor Auxiliary

contact is connected to IB1-Aux.

Figure 9.19 – Basic Logic Program

9-36 DeviceLogix

1503-UM054D-EN-P – March 2015

This is an example of a basic logical replacement for a typical relay control circuit. Pushing the start pushbutton will cause the DLX1 Input 1 to go to “1” which is then tied to the “Net out 27/Start” output tag which is a dual function bit which controls the “Start” input tag. When this goes to “1” the output gate of the “OR” gate goes to “1” and assuming the Normally closed “STOP” pushbutton is not depressed the output of the “AND” gate will got to “1” and close the contactor. The auxiliary input of the contactor will then close which will keep the “OR” gate at “1”. This means the contactor will remain closed until the “STOP” pushbutton is depressed.

Pre configured Logic Mode:

The IntelliVAC Plus comes with five preprogrammed logic programs corresponding to the 5 most common types of Rockwell Automation MV controllers requiring multi contactor control. The five preconfigured logic blocks are:

RVAT (reduced voltage autotransformer starter) RVR (reduced voltage reactor starter) FVR (full voltage reversing starter) SMC (“smart motor controller” solid-state reduced voltage starter) SMC+ PFCC (“smart motor controller” with the addition of

power factor correcting capacitors) These control profiles can be selected in the device parameters page in RSNetworx. They are located in the Control parameter group.

Figure 9.20 – Select Pre-Configured Logic Program

DeviceLogix 9-37

1503-UM054D-EN-P – March 2015

After selecting the desired control program the IntelliVAC Plus module must be reset to adopt its new settings and load the logic from main memory into the DeviceLogix engine. In order to accomplish this simply cycle the control power of the unit. Be sure to remove both the 120VAC power to the IntelliVAC module, and the 24VDC DeviceNet power. When power is restored to the IntelliVAC Plus the new program will be active in DeviceLogix. In order to view the logic in RS-Networx you must delete the IntelliVAC Plus icon from the network view and perform a scan of the network in order to obtain the new settings.

Note: In order for pre programmed logic to function correctly the

hardware inputs to the IntelliVAC Plus MUST be wired according to the Multi contactor wiring guide of Chapter 6.

Note: Only timer values may be changed in pre programmed

program. If any other changes are required the user must use the “User Customized Logic” option. The logic is ready only in Firmware. If modification or forced I/O value in DeviceLogix editor and error message will pop up. The only changeable attribute is the timer’s preset value.

Note: The following conditions must be met in order to change a

pre configured logic block.


The system must be running free of faults or warnings.

All Hardware inputs on the Plus module must be “0” or all HW inputs on the module must be disconnected.

All contactors must be OPEN and the DeviceLogix engine must be in the “stopped’ state

The IE module must be configured for the appropriate number of contactors, see Configuration.

The “DeviceLogix” control mask must be selected.

9-38 DeviceLogix

1503-UM054D-EN-P – March 2015

Chapter 10

1503-UM054D-EN-P – March 2015

Troubleshooting

IB Operational Troubleshooting Procedures

The following table identifies possible causes and corrective actions when troubleshooting IB related faults using the IntelliVAC Plus Module Status/Contactor Status LEDs. NOTE: All parameters indicated in this section refer to a 5IB-MC

system. See the appropriate section of Appendix B for the corresponding parameter for other IB-MC version.

Table 10.A – IB Operational Troubleshooting Procedures

LED Color

State Condition/Possible Cause Corrective Action Module Status

Contactor Status

Green Off Normal The module is healthy and the contactor is open.

No action required.

Green Yellow Normal The module is healthy and the contactor is closed.

No action required

Yellow Off Warning An invalid command was present The Close, Jog or Trip commands were

present during a power up sequence.

The Close or Jog command was re-applied too quickly (before the contactor opening sequence is verified)

The Close and Trip commands are

present simultaneously (only valid for Mechanical Latch contactors)

Prevent Close, Jog or Trip commands from being present during a power up sequence. The Close command can only be re-applied as described in the Delayed Restart section. Increase the delay time between removal of the Close command and its reapplication. The Jog command can only be reapplied as described in the Temporary Jog Function section. Increase the delay time between removal of the Jog command and its reapplication. Prevent the Close and Trip commands from simultaneously being applied. The Trip command can only be applied within a minimum of 200mS from the application of the Close command.

10-2 Troubleshooting

1503-UM054D-EN-P – March 2015

Table 10.A – IB Operational Troubleshooting Procedures (cont.)

LED Color


Contactor Status

Yellow Yellow Warning The mechanical latch contactor failed to trip. Trip command not present.

Contactor Auxiliary status missing

Trip coil open

Check that the Trip command is present on the Trip input and that the voltage is greater than or equal to the minimum level listed in the Electrical Specifications section. Check that the Contactor Auxiliary status connection between the contactor and TB2-11/1,2 on the IntellilVAC Plus is correct. Check that there is not a Trip Coil open message fault on DeviceNet or that the Coil Open fault is not present on the Plus Status LED. This could be caused by a bad (open) coil or an open coil connection.

Red 2 flash Yellow Fault Power up with contactor Closed. Contactor Auxiliary status missing Contactor Auxiliary status contact bad

Contactor bottles bad

Obstruction in contactor

Check that the Contactor Auxiliary status connection between the contactor and TB11/1,2 on the IntelliVAC Plus is correct. Check that the contactor Auxiliary status contacts are functioning. Check that the contactor bottles are not welded closed. Check that there is not an obstruction (or possible binding in the contactor pivot points) in the contactor which prevents the bottle armature from opening.

Yellow-Red 1 flash

Off/Yellow

(depends on status

of contactor)

Warning Contactor fails to pick up Contactor Auxiliary status missing

Obstruction in contactor

1. Check that the Contactor Auxiliary status connection between the contactor and TB11/1,2 on the IntelliVAC Plus is correct.

2. Check that there is not an obstruction (or possible binding in the contactor pivot points) in the contactor which prevents the bottle armature from closing.

Yellow -Red 2 flash

Off/Yellow

(depends on status

of contactor)

Warning Contactor drop out during hold Contactor Auxiliary status missing Faulty contactor coil

1. Check that the Contactor Auxiliary status connection between the contactor and TB11/1,2 on the IntelliVAC Plus is correct.

2. Check the condition of the main contactor coil.

Troubleshooting 10-3

1503-UM054D-EN-P – March 2015


LED Color


Contactor Status

Yellow-Red 3 flash

Off/Yellow

(depends on status

of contactor)

Warning Long contactor drop out time Contactor Auxiliary status missing Faulty contactor coil Faulty vacuum bottles

Check that the Contactor Auxiliary status connection between the contactor and TB11/1,2 on the IntelliVAC Plus is correct. Check the condition of the main contactor coil. Check the mechanical condition of the vacuum bottles.

Red Red Fault Microcontroller malfunction Low input mains voltage

Faulty IntelliVAC Plus

Check that the IntelliVAC Plus input voltage is greater than or equal to the minimum level listed in the Electrical Specifications section. Recycle the input power, as well as the DeviceNet power, if present. Replace the IntelliVAC Plus unit.

Red 1 flash Off Fault Power up with invalid DIP switch configuration DIP switches set incorrectly

1. The SW1/SW2 DIP switches are set. See DIP switch configuration and confirm that it is correct for the contactor being controlled.

Red 3 flash Red Fault Contactor fails to drop out 1. Contactor Auxiliary status missing

2. Contactor Auxiliary status contact

bad 3. Faulty vacuum bottles

4. Obstruction in contactor

Check that the Contactor Auxiliary status connection between the contactor and TB11/1,2 on the IntelliVAC Plus is correct. Check that the contactor Auxiliary status contacts are functioning. Check that the contactor bottles are not welded closed. Check that there is not an obstruction (or possible binding in the contactor pivot points) in the contactor which prevents the bottle armature from opening.

Red 4 flash Off Fault RS 485 communications error Application jumper incorrectly installed Enhanced module in reset state RS485 cables missing/bad

1. Check that the Enhanced module Application Disable jumper (JP3) is in position 2-3 and not in position 1-2.

2. Check that the Plus Status LED is not solid red (Advanced module has a microcontroller malfunction).

3. In an MC system check that the RS485 cable connection s between all of the modules is correct.

Red 4 flash Off Fault Application jumper incorrectly installed in other MC units

4. In an MC system check that the IntelliVAC MC units programming jumpers (JP1) are in position 2-3 and not in position 1-2.


1503-UM054D-EN-P – March 2015


LED Color


Contactor Status

Yellow

flash Off/Yellow

(depends on status

of contactor)

Warning Undervoltage with a Close command present 1. Input mains voltage low 2. Faulty contactor coil 3. Faulty vacuum bottles

Check that the IntelliVAC Plus input voltage is above the undervoltage limit as defined. Check the condition of the main contactor coil. Check the mechanical condition of the vacuum bottles.

Off Off Normal No input power on the mains input Input mains voltage low Input mains connections faulty

Failed internal fuse

Check that the mains input voltage is within the operating voltage range defined in the Electrical Specification. Check the connections to the mains input voltage. If the mains input voltage is present, check the internal fuse.

IE Operational Troubleshooting Procedures

The following table identifies possible causes and corrective actions when troubleshooting IE related faults using the IntelliVAC Plus Status LED.

Table 10.B - IE Operations Troubleshooting Procedures

Plus Status LED Color

State Condition/Possible Cause Corrective Action

Green Normal The module is healthy and the application firmware is running correctly.

No action required.

Green 0.25Hz

flash Normal The module is healthy and the Enhanced

module Application Disable jumper (JP3) is in position 1-2 (programming mode)

No action required.

Green 0.50Hz

flash Normal The module is healthy and the Basic

module is being Flashed No action required

Off Normal There is no power from the mains input or from DeviceNet. 1. Low input mains voltage 2. Input mains connections faulty 3. DeviceNet connections faulty 4. No/low DeviceNet input power

5. No/low DeviceNet input power and

mains input power present

Check that the mains input voltage is within the operating voltage range defined in the Electrical Specification. Check the connections to the mains input voltage. Check the DeviceNet connections. Check that the DeviceNet input power (if present) is within the operating voltage range defined in the Electrical specification. If there is no DeviceNet power and the mains input voltage is present, check the internal fuse.


1503-UM054D-EN-P – March 2015

Table 10.B - IE Operations Troubleshooting Procedures (cont.)



Green 2 pulses Warning RTC failureRTC not responding

1. Replace the IntelliVAC Plus module.

Green 3 pulses Warning Line undervoltageInput mains voltage is too low

Input mains voltage is too low on other MC units

Check the mains input line and verify that it remains greater than 95Vrms to allow a contactor to be closed. If the input voltage remains less than 95Vrms then improvements to the source must be made. This warning can be from any of the IntelliVAC MC units in an MC system. Perform the same checks for those units as well.

Green 4 pulses Warning Line overvoltageInput mains voltage is too high Input mains voltage is too high on other

MC units

Check the mains input line and verify that it remains lower than 265Vrms to prevent damage to the IntelliVAC Plus module. This warning can be from any of the IntelliVAC MC units in an MC system. Perform the same checks for those units as well.

Green 5 pulses Warning Extended close timeFaulty contactor mechanics

Faulty contactor coil

Faulty contactor coil on other MC units

Check the mechanical condition of the contactor as this warning is an indication that the moving mechanisms of the contactor are beginning to wear. Check the resistance of the contactor coil and compare it to the values. This warning can be from any of the IntelliVAC MC units in an MC system. Perform the same checks for those units as well.

Green 6 pulses Warning DeviceNet power loss1. DeviceNet connection faulty

2. DeviceNet input voltage too low

Check that the DeviceNet connections to the IntelliVAC Plus are correct and that the DeviceNet source connections are correct as well. Check that the DeviceNet input voltage at terminals TB1-5,1 is greater than the minimum voltage as defined in the Electrical Specification

Green 7 pulses Warning MC Altitude settingIncorrect altitude DIP switch setting The altitude setting defined by the DIP switches

(SW1-1,2,3) on the Basic module is not consistently set on all units in an MC system. Adjust the DIP switches on all units to the same altitude setting.


1503-UM054D-EN-P – March 2015




Red Fault RESET mode or firmware crash+5V logic rail is too low

Faulty Enhanced microcontroller

Firmware crash

A RESET condition has occurred due to the +5V logic rail being less than +4.65V. Check that the input mains voltage is within the operating range as defined in the Electrical Specification A RESET condition has occurred due to a faulty microcontroller on the Enhanced module. Replace the IntelliVAC Plus module. A RESET condition has occurred due to a firmware crash. This may be due to a high level of externally generated EMI entering the wires connecting to the IntelliVAC Plus module. Recycle the input power for both the mains input as well as the DeviceNet power. If there is no improvement then analyze the wiring to the IntelliVAC Plus to determine if there is an unusual amount of electrical noise present. If there is excessive noise present, then rectify the situation. If the unit still remains in RESET mode then replace the IntelliVAC Plus module.

Red 2 pulses Fault POST failure – RAMExcessive EMI

A failure of one or more of the internal microcontroller RAM cells has been detected. This may be due to externally generated EMI entering the wires connecting to the IntelliVAC Plus module, corrupting the RAM memory. This may be due to a high level of externally generated EMI entering the wires connecting to the IntelliVAC Plus module. Recycle the input power for both the mains input as well as the DeviceNet power. If there is no improvement then analyze the wiring to the IntelliVAC Plus to determine if there is an unusual amount of electrical noise present. If there is excessive noise present, then rectify the situation. If not and the RAM fault persists then replace the IntelliVAC Plus module.

Faulty RAM memory The internal microcontroller RAM has one or more defective cells and the IntelliVAC Plus must be replaced.

Red 5 pulses Fault Application programming error – CRCRS485 cables faulty Excessive EMI in vicinity

Incorrect program being Flashed Incorrect communications parameters

1. Check that the RS485 cable connecting the IntelliVAC Plus module and the PC is correct.

2. Check that there is not an unusual amount of EMI being emitted from external sources.

3. Check that the program being flashed is correct. 4. Check that the communications parameters are

correct (i.e. baud rate, star/stop bits, parity, flow control).

Red 6 pulses Fault RS485 Communications fault from IB1Faulty interboard connector

External RS485 source connected Faulty IntelliVAC Plus unit

Remove the IntelliVAC Plus front panel, remove the three mounting screws and then remove the Enhanced circuit card. Check that the 16-pin interboard connector is properly mating and that there is no dirt in the connector.

Remove the external RS485 communications source. Replace the IntelliVAC Plus module.


1503-UM054D-EN-P – March 2015




Red 7 pulses Fault IB1 power loss Input mains voltage is too low

Failed internal fuse Faulty IntelliVAC Plus power supply

Check the mains input line and verify that it is greater than the minimum operating level as defined in the Electrical Specifications. For proper operation the input line must be greater than 95Vrms to allow a contactor to be closed. If the input voltage remains less than 95Vrms then improvements to the source must be made. Although the electronics in the IntelliVAC Plus and IntelliVAC MC units will operate to a much lower voltage level than 95Vrms, the contactor will not be able to be closed at such low levels. Replace the internal fuse. Replace the IntelliVAC Plus module.

Red 8 pulses Fault Coil open Contactor coil connections faulty Faulty coil Contactor coil connections faulty on

other MC units Faulty coils on other MC units

Faulty IntelliVAC Plus unit Faulty IntelliVAC MC unit(s)

Check the connections between the IntelliVAC Plus and the contactor. Check the resistance of the coil and confirm that it is in the range. Check the connections between the other IntelliVAC MC units and their contactors.

Check the resistance of the coils controlled by other IntelliVAC MC units and confirm that they are in the range. Replace the IntelliVAC Plus unit. Replace other IntelliVAC MC unit(s).

IE Operational Troubleshooting Procedures

The following table identifies possible causes and corrective actions when troubleshooting IE related faults using the IntelliVAC Plus 7-Segment LED Display.

Table 10.C – IE Operational Trouble Shooting Procedures

7-Segment Display


‘-1’ solid Fault RS485 Incorrect duplicate address(es) Incorrect Address(es) selected Invalid address(es) selected Duplicate address(es) selected Incorrect RTERM selected

In an IntelliVAC MC system, the correct number of addresses has not been selected. Set the additional IntelliVAC MC addresses to 2,3,4 or 5 only. In an IntelliVAC MC system, invalid addresses have been selected. Set the additional IntelliVAC MC address to 2,3,4 or 5 only. Addresses 0,1,6 and 7 are not valid for the additional IntelliVAC MC units. In an IntelliVAC MC system, there can be no duplication of addresses. Addresses 2,3,4 or 5 can only be used by one individual IntelliVAC MC unit. In an IntelliVAC MC system, an incorrect RTERM

resistor on only the last IntelliVAC MC unit in an IntelliVAC MC system.


1503-UM054D-EN-P – March 2015

Table 10.C – IE Operational Trouble Shooting Procedures (cont.)

7-Segment Display


‘1’flash Fault MC system bad MC #1IntelliVAC MC #1 not communicating

Check the interboard connector between the Basic and Enhanced modules in the IntelliVAC Plus module. Also, check the RS485 communications cable between other IntelliVAC MC units, if they are in the system.

‘1’flash

Fault Incorrect RTERM Selected In an IntelliVAC MC system, an incorrect RTERM

setting can Cause communication errors which will generate this fault. Set the RTERM resistor on only the last IntelliVAC MC unit in an IntelliVAC MC system. In a single unit IntelliVAC MC system, there is no need to install an additional RTERM resistor as it is already installed on the Enhanced module contained in the IntelliVAC Plus unit.


Incorrect RTERM selected

1. Check the RS485 communications cable between IntelliVAC MC unit #2 and other IntelliVAC MC units, if they are in the system. 2. In an IntelliVAC MC system, an incorrect RTERM setting can cause communication errors which will generate this fault. Set the RTERM resistor on only the last IntelliVAC MC unit in an IntelliVAC MC system



Check the RS485 communications cable between IntelliVAC MC unit #3 and other IntelliVAC MC units, if they are in the system. In an IntelliVAC MC system, an incorrect RTERM setting can cause communication errors which will generate this fault. Set the RTERM resistor on only the last IntelliVAC MC unit in an IntelliVAC MC system








1503-UM054D-EN-P – March 2015

Table 10.C – IE Operational Trouble Shooting Procedures (cont.)

7-Segment Display


‘6’flash Fault Incorrect MC RTERM installed1. Incorrect RTERM selected

Set the RTERM resistor on only the last IntelliVAC MC unit in an IntelliVAC MC system

‘L’+MC address ‘1’flash

Fault System lock-out stateFault present, in MC system which will

not clear Determine the fault that is occurring in the IntelliVAC MC system and eliminate its source.

‘3’solid Fault Bad or no DeviceLogix program for MC system

1. The Custom DeviceLogix module is selected and has no program entered.

2. The Custom DeviceLogix module is selected and has errors.

Enter a valid program for the Custom DeviceLogix module. Correct any errors present in the Custom DeviceLogix module.

‘7’+’DP’flash Fault Lost +15V rail from IntelliVAC Plus Basic module

Input mains voltage is too low

Failed internal fuse Faulty IntelliVAC Plus power supply

Check the mains input line and verify that it is greater than the minimum operating level as defined in the Electrical Specifications section in Appendix A. For proper operation the input line must be greater than 95Vrms to allow a contactor to be closed. If the input voltage remains less than 95Vrms then improvements to the source must be made. Although the electronics in the IntelliVAC Plus and IntelliVAC MC units will operate to a much lower voltage level than 95Vrms, the contactor will not be able to be closed at such low levels. Replace the internal fuse. Replace the IntelliVAC Plus module.

‘8’+’DP’flash Fault Watchdog timeout – fatal errorFirmware crash occurred due to a faulty

microcontroller Firmware crash occurred due to

excessive external EMI

Caused by a faulty microcontroller on the Enhanced module. Replace the IntelliVAC Plus module. Caused due to a high level of externally generated EMI entering the wires connecting to the IntelliVAC Plus module. Recycle the input power for both the mains input as well as the DeviceNet power. If there is no improvement then analyze the wiring to the IntelliVAC Plus to determine if there is an unusual amount of electrical noise present. If there is excessive noise present, then rectify the situation. If the unit still remains in a watchdog timeout fault then replace the IntelliVAC Plus module.

MC Operational Troubleshooting Procedures

The following table identifies possible causes and corrective actions when troubleshooting MC related faults using the IntelliVAC MC 7-Segment LED Display.


1503-UM054D-EN-P – March 2015

Table 10.D – MC Operational Troubleshooting Procedures

7-Segment Display


Off Normal No input power on the mains input Input mains voltage low

Input mains connections faulty Failed internal fuse

Check that the mains input voltage, on the IntelliVAC MC unit is within the operating voltage range defined in the Electrical Specification. Check the connections to the mains input voltage. If the mains input voltage is present, check the internal fuse.

Off Fault Invalid MC address selectedMC address is invalid

Set the MC address to either 2,3,4 or 5. Addresses 0,1,6 or 7 are invalid and will not be displayed on the 7-segment LED display of the IntelliVAC MC module.

DeviceNet Troubleshooting Procedures

The following table identifies possible causes and corrective actions when troubleshooting IE related faults using the DeviceNet Network Status LED.

Table 10.E – DeviceNet Troubleshooting Procedures

Network Status LED

Color State Condition/Possible Cause Corrective Action

Off Normal There is no power from the mains input or from DeviceNet. 1. Low input mains voltage 2. Input mains connections faulty 3. DeviceNet connections faulty 4. No/low DeviceNet input power

5. No/low DeviceNet input power and

mains input power present

Check that the mains input voltage is within the operating voltage range defined in the Electrical Specification. Check the connections to the mains input voltage. Check the DeviceNet connections. Check that the DeviceNet input power (if present) is within the operating voltage range defined in the Electrical specification. If there is no DeviceNet power and the mains input voltage is present, check the internal fuse.

Green flashing

Warning

Determining network baud rate1. IntelliVAC Plus is on-line but not

allocated to a master. Check DeviceNet master and its scan list for correct scanner configuration.

Green flashing Warning On-line but not allocated to master. IntelliVAC Plus is on-line but not allocated to a master.

Check DeviceNet master and its scan list for correct scanner configuration.

Green solid None Normal operation and allocated to master 1. No action required Red flashing Warning I/O connection timed-out Reset DeviceNet master device. Red solid Fault Bus Off or Duplicate address or Invalid

baud Diagnostics test failed on power-up reset. Internal fault exists. Duplicate DeviceNet node address exists (two DeviceNet nodes cannot have the same address). Invalid baud rate (if autobaud is disabled).

Cycle power to the unit and network. If the fault still exists, replace the IntelliVAC Plus unit. Change the value of Parameter 57, NonVol MAC ID, to a valid address and reset the device. This will only occur if Parameter 55, AutoBaudEnable, is set to ‘disabled’. Set Parameter 55 to ‘enabled’ and reset the IntelliVAC Plus unit or set Parameter 56, NonVol Baud Rate, to the correct setting and reset the IntelliVAC Plus unit.

Appendix A

1503-UM054D-EN-P – March 2015

Fuse Protection Introduction The IntelliVAC module requires external fuse protection to

coordinate with the power supply and contactor. The fuse ratings shown in Table 3.A allow the passage of inrush currents expected when the contactor is closed, or from recommended external capacitors for the TDUV option. They will also protect the contactor coils in the event of a module malfunction.

The recommended fuses have been tested to ensure reliable

protection of the module. If the supply voltage is DC, the module must be used with an external fuse that is approved for and rated to interrupt the DC voltage supply. The types listed are Ferraz-Shawmut Midget Fuses (1-1/2" X 13/32"). The TRM is a time-delay type, rated 250 VAC. The ATM is a fast-acting type, rated 500 VDC.

Table A.1 – IntelliVAC Plus Fuse Protection

Rated Supply Voltage Contactor Type Recommended Fuse

(minimum) (maximum)


400/800A ML TRM 2 TRM 3.2


400/800A ML TRM 2 TRM 6.25



EH = Electrically Held vacuum contactor ML = Mechanical Latch vacuum contactor

Note: If external capacitors are connected, or more than one

IntelliVAC module is protected by a common control fuse, the maximum recommended fuse should be used to prevent fuse opening due to increased inrush current when control power is applied.

A-2 Fuse Protection

1503-UM054D-EN-P – March 2015

Appendix B

1503-UM054D-EN-P – March 2015

Parameters

Introduction This section provides a detailed description of the parameters used in the control of the IntelliVAC Plus. The parameters are arranged into functional groups. Each description begins with the full name of the parameter, followed by the name displayed in RSNetworx. The linear number of the parameter is given followed by the minimum and maximum values showing the position of the decimal point and the units, if applicable. Next is the default value for a new IntelliVAC Plus. Finally, there is a short functional description of the parameter.

Interpreting Bit-Encoded Parameters

Most bit-encoded parameters follow a basic format. A one (1) in an associated bit represents a true or active condition. A zero (0) in an associated bit represents a false or inactive condition. The data type and value in the following parameter description is based on RSNetWorx parameter page visibility. For an expert user who wants to use explicit messaging to access the parameters, please refer to the EDS for data type and valid data range. The methodology is best illustrated using an example:

Status Word for IB1 [IB 1 Status Word] Parameter Number: 335, 276, 217, 158, 98 Access rule: Get Data Type: WORD Object Mapping: 0x384-1-62 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IB1 Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present.

B-2 Parameters

1503-UM054D-EN-P – March 2015

Table B.1 – Status Word for IB1

Bit Enum Text Description

0 Bit 0: unused unused 1 Bit 1: unused unused 2 Bit 2: unused unused 3 Bit 3: Power Up with Contactors Closed Power Up with Contactor Closed IB1 4 Bit 4: Open Coil Open Trip Coil Open on IB1 5 Bit 5: Close Coil Open Close Coil Open on IB1 6 Bit 6: Power Up with Invalid DIPs Power Up with Invalid DIPs on IB1 7 Bit 7: MC Malfunction MC Malfunction on IB1 8 Bit 8: Drop Out During Hold Drop Out During Hold on IB1 9 Bit 9: Contactor Fails to Drop Out Contactor Fails to Drop Out on IB1 10 Bit 10: Power Up with Close Command Power Up with Close Command on IB1 11 Bit 11: Long Close Time Long Close Time on IB1

12 Bit 12: Undervoltage with Close Command Present

Undervoltage with Close Command Present on IB1

13 Bit 13: Long Drop Out Time Long Drop Out Time on IB1 14 Bit 14: Mechanical Latch Trip Fail Mechanical Latch Trip Fail on IB1 15 Bit 15: Invalid Command Invalid Command on IB1

The description in the manual will always be structured in the same way. The top most description (in this case not used) is always the least-significant bit, or right-most bit. As you move down the list of descriptions, you advance to the left on the bit-encoded word. Any unused bits will be identified, but unused bits will nave no description. This is why a 16-bit word may only have a few descriptions. The rest are reserved for future expansion. When a bit-encoded parameter is viewed in its associated group, it is actually displayed as a hexadecimal number. The right-most four bits represent the right-most hexadecimal digit. Each subsequent group of 4 represents the next hexadecimal digit. Table B.2 below illustrates the relationship.

Table B.2 – Sample Bit to Hexadecimal Conversion

Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Value 8 4 2 1 8 4 2 1 8 4 2 1 8 4 2 1

Example 1 1 1 0 0 1 0 0 0 1 1 1 1 1 1 1

8 + 4 + 2 + 0 0 + 4 + 0 + 0 0 + 4 + 2 + 1 8 + 4 + 2 + 1

Sums E 4 7 F

When you display a specific bit-encoded parameter, or choose to modify a bit-encoded parameter, it will be displayed in bit format, with an individual description of each bit (see Table B.3). When modifying a parameter, selecting the bit parameter will allow it to be altered.

Parameters B-3

1503-UM054D-EN-P – March 2015

Table B.3 – Conversion Table

Binary Hex Binary Hex Binary Hex Binary Hex

0000 0 0100 4 1000 8 1100 C 0001 1 0101 5 1001 9 1101 D 0010 2 0110 6 1010 A 1110 E 0011 3 0111 7 1011 B 1111 F

Parameter Numbers The parameter number value, for each parameter type, lists 5 values separated by commas. The description of these 5 values is as follows:

a, b, c, d, e

a = parameter number for a 5IB multi-contactor system

b = parameter number for a 4IB multi-contactor system

c = parameter number for a 3IB multi-contactor system

d = parameter number for a 2IB multi-contactor system

e = parameter number for a 1IB multi-contactor system Depending on the multi-contactor system which is used, simply select the value of the parameter number corresponding to the appropriate system.

Control Parameters Auxiliary Input Status from IntelliVAC Base Unit #1 [IB 1 Module Aux. Status]

Parameter Number: 1,1,1,1,1. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-1 Group: Control Units: - Minimum Value: 0 = Closed Maximum Value: 1 = Open Default Value: 0

This parameter allows the user to view the status of the contactor Auxiliary input from the IntelliVAC Basic Module #1. A Closed status refers to the contactor Auxiliary input having no input voltage which indicates that the contactor is Closed. An Open status refers to the contactor Auxiliary input having a valid input voltage which indicates that the contactor is Open. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Closed and Open input.

B-4 Parameters

1503-UM054D-EN-P – March 2015

Auxiliary Input Status from IntelliVAC Base Unit #2 [IB 2 Module Aux. Status]

Parameter Number: 2,2,2,2,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-1 Group: Control Units: - Minimum Value: 0 = Closed Maximum Value: 1 = Open Default Value: 0 This parameter allows the user to view the status of the contactor Auxiliary input from the IntelliVAC Basic Module #2. A Closed status refers to the contactor Auxiliary input having no input voltage which indicates that the contactor is Closed. An Open status refers to the contactor Auxiliary input having a valid input voltage which indicates that the contactor is Open. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Closed and Open input. Auxiliary Input Status from IntelliVAC Base Unit #3 [IB 3 Module Aux. Status]

Parameter Number: 3,3,3,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-1 Group: Control Units: - Minimum Value: 0 = Closed Maximum Value: 1 = Open Default Value: 0 This parameter allows the user to view the status of the contactor Auxiliary input from the IntelliVAC Basic Module #3. A Closed status refers to the contactor Auxiliary input having no input voltage which indicates that the contactor is Closed. An Open status refers to the contactor Auxiliary input having a valid input voltage which indicates that the contactor is Open. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Closed and Open input.

Parameters B-5

1503-UM054D-EN-P – March 2015

Auxiliary Input Status from IntelliVAC Base Unit #4 [IB 4 Module Aux. Status]

Parameter Number: 4,4,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-1 Group: Control Units: - Minimum Value: 0 = Closed Maximum Value: 1 = Open Default Value: 0 This parameter allows the user to view the status of the contactor Auxiliary input from the IntelliVAC Basic Module #4. A Closed status refers to the contactor Auxiliary input having no input voltage which indicates that the contactor is Closed. An Open status refers to the contactor Auxiliary input having a valid input voltage which indicates that the contactor is Open. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Closed and Open input. Auxiliary Input Status from IntelliVAC Base Unit #5 [IB 5 Module Aux. Status]

Parameter Number: 5,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-1 Group: Control Units: - Minimum Value: 0 = Closed Maximum Value: 1 = Open Default Value: 0 This parameter allows the user to view the status of the contactor Auxiliary input from the IntelliVAC Basic Module #5. A Closed status refers to the contactor Auxiliary input having no input voltage which indicates that the contactor is Closed. An Open status refers to the contactor Auxiliary input having a valid input voltage which indicates that the contactor is Open. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Closed and Open input.

B-6 Parameters

1503-UM054D-EN-P – March 2015

Close Input Status from IntelliVAC Base Unit #1 [IB 1 Module Close Status]

Parameter Number: 6,5,4,3,2. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-2 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Close input from the IntelliVAC Basic Module #1. An Off status refers to the Close input having no input voltage indicating an absence of a Close input. An On status refers to the Close input having a valid input voltage indicating a presence of a Close input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.


Parameter Number: 7,6,5,4,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-2 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Close input from the IntelliVAC Basic Module #2. An Off status refers to the Close input having no input voltage indicating an absence of a Close input. An On status refers to the Close input having a valid input voltage indicating a presence of a Close input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.

Parameters B-7

1503-UM054D-EN-P – March 2015


Parameter Number: 8,7,6,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-2 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Close input from the IntelliVAC Basic Module #3. An Off status refers to the Close input having no input voltage indicating an absence of a Close input. An On status refers to the Close input having a valid input voltage indicating a presence of a Close input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.


Parameter Number: 9,8,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-2 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Close input from the IntelliVAC Basic Module #4. An Off status refers to the Close input having no input voltage indicating an absence of a Close input. An On status refers to the Close input having a valid input voltage indicating a presence of a Close input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.

B-8 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 10,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-2 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Close input from the IntelliVAC Basic Module #5. An Off status refers to the Close input having no input voltage indicating an absence of a Close input. An On status refers to the Close input having a valid input voltage indicating a presence of a Close input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input. Open Input Status from IntelliVAC Base Unit #1 [IB 1 Module Open Status]

Parameter Number: 11,9,7,5,3. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-3 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Open input from the IntelliVAC Basic Module #1. An Off status refers to the Open input having no input voltage indicating the absence of an Open input. An On status refers to the Open input having a valid input voltage indicating the presence of an Open input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.

Parameters B-9

1503-UM054D-EN-P – March 2015

Open Input Status from IntelliVAC Base Unit #2 [IB 2 Module Open Status]

Parameter Number: 12,10,8,6,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-3 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Open input from the IntelliVAC Basic Module #2. An Off status refers to the Open input having no input voltage indicating the absence of an Open input. An On status refers to the Open input having a valid input voltage indicating the presence of an Open input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.


Parameter Number: 13,11,9,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-3 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Open input from the IntelliVAC Basic Module #3. An Off status refers to the Open input having no input voltage indicating the absence of an Open input. An On status refers to the Open input having a valid input voltage indicating the presence of an Open input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.

B-10 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 14,12,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-3 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Open input from the IntelliVAC Basic Module #4. An Off status refers to the Open input having no input voltage indicating the absence of an Open input. An On status refers to the Open input having a valid input voltage indicating the presence of an Open input. See the Electrical Specifications section in Table 1.A for the voltage level for a valid Off and On input.


Parameter Number: 15_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-3 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the contactor Open input from the IntelliVAC Basic Module #5. An Off status refers to the Open input having no input voltage indicating the absence of an Open input. An On status refers to the Open input having a valid input voltage indicating the presence of an Open input. See the Electrical Specifications section in Appendix A for the voltage level for a valid Off and On input.

Parameters B-11

1503-UM054D-EN-P – March 2015

Close Coil Command for IntelliVAC Base Unit #1 [IB 1 Close Coil Command]

Parameter Number: 16,13,10,7,4. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-1-4 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Close Coil command for the IntelliVAC Basic Module #1. An Off refers to the Close command not being present and not applying power to the Close coil. An On refers to the Close command being present and applying power to the Close coil.


Parameter Number: 17,14,11,8,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-2-4 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Close Coil command for the IntelliVAC Basic Module #2. An Off refers to the Close command not being present and not applying power to the Close coil. An On refers to the Close command being present and applying power to the Close coil.

B-12 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 18,15,12,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-3-4 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Close Coil command for the IntelliVAC Basic Module #3. An Off refers to the Close command not being present and not applying power to the Close coil. An On refers to the Close command being present and applying power to the Close coil.


Parameter Number: 19,16,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-4-4 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Close Coil command for the IntelliVAC Basic Module #4. An Off refers to the Close command not being present and not applying power to the Close coil. An On refers to the Close command being present and applying power to the Close coil.

Parameters B-13

1503-UM054D-EN-P – March 2015


Parameter Number: 20_,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-5-4 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Close Coil command for the IntelliVAC Basic Module #5. An Off refers to the Close command not being present and not applying power to the Close coil. An On refers to the Close command being present and applying power to the Close coil. Trip Coil Command for IntelliVAC Base Unit #1 [IB 1 Trip Coil Command]

Parameter Number: 21,17,13,9,5. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-1-5 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Trip Coil command for the IntelliVAC Basic Module #1. An Off refers to the Trip command not being present and not applying power to the Trip coil. An On refers to the Trip command being present and applying power to the Trip coil.

B-14 Parameters

1503-UM054D-EN-P – March 2015

Trip Coil Command for IntelliVAC Base Unit #2 [IB 2 Trip Coil Command]

Parameter Number: 22,18,14,10,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-2-5 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Trip Coil command for the IntelliVAC Basic Module #2. An Off refers to the Trip command not being present and not applying power to the Trip coil. An On refers to the Trip command being present and applying power to the Trip coil. Trip Coil Command for IntelliVAC Base Unit #3 [IB 3 Trip Coil Command]

Parameter Number: 23,19,15,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-3-5 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Trip Coil command for the IntelliVAC Basic Module #3. An Off refers to the Trip command not being present and not applying power to the Trip coil. An On refers to the Trip command being present and applying power to the Trip coil.

Parameters B-15

1503-UM054D-EN-P – March 2015

Trip Coil Command for IntelliVAC Base Unit #4 [IB 4 Trip Coil Command] Parameter Number: 24,20,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-4-5 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Trip Coil command for the IntelliVAC Basic Module #4. An Off refers to the Trip command not being present and not applying power to the Trip coil. An On refers to the Trip command being present and applying power to the Trip coil. Trip Coil Command for IntelliVAC Base Unit #5 [IB 5 Trip Coil Command]

Parameter Number: 25,_,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-5-5 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view as well as change the Trip Coil command for the IntelliVAC Basic Module #5. An Off refers to the Trip command not being present and not applying power to the Trip coil. An On refers to the Trip command being present and applying power to the Trip coil.

B-16 Parameters

1503-UM054D-EN-P – March 2015

Contactor Relay Status for IntelliVAC Base Unit #1 [IB 1 Contactor Status Relay Status]

Parameter Number: 26,21,16,11,6. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-6 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Contactor Status relay for the IntelliVAC Basic Module #1. An Open refers to the Contactor Status relay contacts being in an Open state. A Closed status refers to the Contactor Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Contactor Status relay contact ratings. Contactor Relay Status for IntelliVAC Base Unit #2 [IB 2 Contactor Status Relay Status] Parameter Number: 27,22,17,12,_.

Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-6 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Contactor Status relay for the IntelliVAC Basic Module #2. An Open refers to the Contactor Status relay contacts being in an Open state. A Closed status refers to the Contactor Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Contactor Status relay contact ratings.

Parameters B-17

1503-UM054D-EN-P – March 2015


Parameter Number: 28,23,18,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-6 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Contactor Status relay for the IntelliVAC Basic Module #3. An Open refers to the Contactor Status relay contacts being in an Open state. A Closed status refers to the Contactor Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Contactor Status relay contact ratings.


Parameter Number: 29,24,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-6 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Contactor Status relay for the IntelliVAC Basic Module #4. An Open refers to the Contactor Status relay contacts being in an Open state. A Closed status refers to the Contactor Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Contactor Status relay contact ratings.

B-18 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 30,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-6 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Contactor Status relay for the IntelliVAC Basic Module #5. An Open refers to the Contactor Status relay contacts being in an Open state. A Closed status refers to the Contactor Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Contactor Status relay contact ratings. Module Status Relay Status for IntelliVAC Base Unit #1 [IB 1 Module Status Relay Status]

Parameter Number: 31,25,19,13,7. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-7 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Module Status relay for the IntelliVAC Basic Module #1. An Open refers to the Module Status relay contacts being in an Open state. A Closed status refers to the Module Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Module Status relay contact ratings.

Parameters B-19

1503-UM054D-EN-P – March 2015

Module Status Relay Status for IntelliVAC Base Unit #2 [IB 2 Module Status Relay Status]

Parameter Number: 32,26,20,14,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-7 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Module Status relay for the IntelliVAC Basic Module #2. An Open refers to the Module Status relay contacts being in an Open state. A Closed status refers to the Module Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Module Status relay contact ratings. Module Status Relay Status for IntelliVAC Base Unit #3 [IB 3 Module Status Relay Status]

Parameter Number: 33,27,21,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-7 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Module Status relay for the IntelliVAC Basic Module #3. An Open refers to the Module Status relay contacts being in an Open state. A Closed status refers to the Module Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Module Status relay contact ratings.

B-20 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 34,28,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-7 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Module Status relay for the IntelliVAC Basic Module #4. An Open refers to the Module Status relay contacts being in an Open state. A Closed status refers to the Module Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Module Status relay contact ratings.


Parameter Number: 35_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-7 Group: Control Units: - Minimum Value: 0 = Open Maximum Value: 1 = Closed Default Value: 0 This parameter allows the user to view the status of the Module Status relay for the IntelliVAC Basic Module #5. An Open refers to the Module Status relay contacts being in an Open state. A Closed status refers to the Module Status relay contacts being in a Closed state. See the Electrical Specifications section in Table 1.A for the Module Status relay contact ratings.

Parameters B-21

1503-UM054D-EN-P – March 2015

Close Coil Current for IntelliVAC Base Unit #1 [IB 1 Close Current]

Parameter Number: 36,29,22,15,8. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-1-8 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Close coil current on the IntelliVAC Basic Module #1. This coil current is only valid for the first 200mS after the Close coil is energized. Close Coil Current for IntelliVAC Base Unit #2 [IB 2 Close Current]

Parameter Number: 37,30,23,16,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-8 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Close coil current on the IntelliVAC Basic Module #2. This coil current is only valid for the first 200mS after the Close coil is energized.

B-22 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 38,31,24,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-8 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Close coil current on the IntelliVAC Basic Module #3. This coil current is only valid for the first 200mS after the Close coil is energized. Close Coil Current for IntelliVAC Base Unit #4 [IB 4 Close Current]

Parameter Number: 39,32,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-8 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999 Default Value: 00.000A This parameter allows the user to view the average value for the Close coil current on the IntelliVAC Basic Module #4. This coil current is only valid for the first 200mS after the Close coil is energized.

Parameters B-23

1503-UM054D-EN-P – March 2015


Parameter Number: 40_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-8 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Close coil current on the IntelliVAC Basic Module #5. This coil current is only valid for the first 200mS after the Close coil is energized.

Hold Coil Current for IntelliVAC Base Unit #1 [IB 1 Hold Current]

Parameter Number: 41,33,25,17,9. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-1-9 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Hold coil current on the IntelliVAC Basic Module #1. This coil current is only valid after the first 200mS after the Close coil is energized and the Close coil is in the Hold state.

B-24 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 42,34,26,18,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-9 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Hold coil current on the IntelliVAC Basic Module #2. This coil current is only valid after the first 200mS after the Close coil is energized and the Close coil is in the Hold state. Hold Coil Current for IntelliVAC Base Unit #3 [IB 3 Hold Current]

Parameter Number: 43,35,27,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-9 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Hold coil current on the IntelliVAC Basic Module #3. This coil current is only valid after the first 200mS after the Close coil is energized and the Close coil is in the Hold state.

Parameters B-25

1503-UM054D-EN-P – March 2015


Parameter Number: 44,36,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-9 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Hold coil current on the IntelliVAC Basic Module #4. This coil current is only valid after the first 200mS after the Close coil is energized and the Close coil is in the Hold state.


Parameter Number: 45,_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-9 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Hold coil current on the IntelliVAC Basic Module #5. This coil current is only valid after the first 200mS after the Close coil is energized and the Close coil is in the Hold state.

B-26 Parameters

1503-UM054D-EN-P – March 2015

Trip Coil Current for IntelliVAC Base Unit #1 [IB 1 Trip Current]

Parameter Number: 46,37,28,19,10. Access rule: Get Data Type: Float Object Mapping: 0x384-1-10 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Trip coil current on the IntelliVAC Basic Module #1. This coil current is only valid for the first 200mS after the Trip coil is energized. Trip Coil Current for IntelliVAC Base Unit #2 [IB 2 Trip Current]

Parameter Number: 47,38,29,20,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-10 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Trip coil current on the IntelliVAC Basic Module #2. This coil current is only valid for the first 200mS after the Trip coil is energized.

Parameters B-27

1503-UM054D-EN-P – March 2015


Parameter Number: 48,39,30,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-10 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Trip coil current on the IntelliVAC Basic Module #3. This coil current is only valid for the first 200mS after the Trip coil is energized.


Parameter Number: 49,40,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-10 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Trip coil current on the IntelliVAC Basic Module #4. This coil current is only valid for the first 200mS after the Trip coil is energized.

B-28 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 50,_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-10 Group: Control Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the average value for the Trip coil current on the IntelliVAC Basic Module #5. This coil current is only valid for the first 200mS after the Trip coil is energized. Input Line Voltage for IntelliVAC Base Unit #1 [IB 1 Line Voltage]

Parameter Number: 51,41,31,21,11. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-1-11 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the RMS value for the Input Line voltage on the IntelliVAC Basic Module #1. The input voltage may be either AC or DC.

Parameters B-29

1503-UM054D-EN-P – March 2015

Input Line Voltage for IntelliVAC Base Unit #2 [IB 2 Line Voltage]

Parameter Number: 52,42,32,22,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-11 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the RMS value for the Input Line voltage on the IntelliVAC Basic Module #2. The input voltage may be either AC or DC. Input Line Voltage for IntelliVAC Base Unit #3 [IB 3 Line Voltage]

Parameter Number: 53,43,33,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-11 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the RMS value for the Input Line voltage on the IntelliVAC Basic Module #3. The input voltage may be either AC or DC.

B-30 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 54,44,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-11 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the RMS value for the Input Line voltage on the IntelliVAC Basic Module #4. The input voltage may be either AC or DC.


Parameter Number: 55,_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-11 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the RMS value for the Input Line voltage on the IntelliVAC Basic Module #5. The input voltage may be either AC or DC.

Parameters B-31

1503-UM054D-EN-P – March 2015

DC Bus Voltage for IntelliVAC Base Unit #1 [IB 1 DC Bus Voltage]

Parameter Number: 56,45,34,23,12. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-1-12 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the DC value for the DC Bus voltage on the IntelliVAC Basic Module #1. DC Bus Voltage for IntelliVAC Base Unit #2 [IB 2 DC Bus Voltage]

Parameter Number: 57,46,35,24,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-12 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the DC value for the DC Bus voltage on the IntelliVAC Basic Module #2.

B-32 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 58,47,36,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-12 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the DC value for the DC Bus voltage on the IntelliVAC Basic Module #3. DC Bus Voltage for IntelliVAC Base Unit #4 [IB 4 DC Bus Voltage]

Parameter Number: 59,48,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-12 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the DC value for the DC Bus voltage on the IntelliVAC Basic Module #4.

Parameters B-33

1503-UM054D-EN-P – March 2015


Parameter Number: 60,_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-12 Group: Control Units: Volts Minimum Value: 00.000V Maximum Value: 399.999V Default Value: 00.000V This parameter allows the user to view the DC value for the DC Bus voltage on the IntelliVAC Basic Module #5. Enhanced Module Hardware Input Status [IE Hardware Inputs]

Parameter Number: 61,49,37,25,13. Access rule: Get Data Type: BYTE Object Mapping: 0x4-11-3 Group: Control Units: - Minimum Value: - Maximum Value: - Default Value: None This parameter allows the user to view the status of the eight (8) hardware inputs. Each bit position of the parameter defines the state of one of the hardware inputs. If the voltage to an input is lower than the maximum required, as defined in the Electrical Specifications in Table 1.A, then the corresponding bit will indicate a ‘0’. If the voltage to an input exceeds the minimum required, as defined in the Electrical Specifications in Table 1.A, then the corresponding bit will indicate a ‘1’.

Table B.4 – Enhanced Module Hardware Input States


0 Bit 0: DLX Input 1 Status of DeviceLogix Input #1 1 Bit 1: DLX Input 2 Status of DeviceLogix Input #2 2 Bit 2: DLX Input 3 Status of DeviceLogix Input #3 3 Bit 3: DLX Input 4 Status of DeviceLogix Input #4 4 Bit 4: DLX Input 5 Status of DeviceLogix Input #5 5 Bit 5: DLX Input 6 Status of DeviceLogix Input #6 6 Bit 6: DLX Input 7 Status of DeviceLogix Input #7 7 Bit 7: DLX Input 8 Status of DeviceLogix Input #8

B-34 Parameters

1503-UM054D-EN-P – March 2015

Enhanced Module Hardware Output State [IE Hardware Outputs]

Parameter Number: 62,50,38,26,14. Access rule: Get/Set Data Type: BYTE Object Mapping: 0x4-2-3 Group: Control Units: - Minimum Value: - Maximum Value: - Default Value: None This parameter allows the user to view, as well as to control, the state of the two (2) hardware output relays. Each bit position of the parameter defines the state of one of the hardware outputs. If the bit for a particular output is ‘0’ then that relay output will be Off but if the bit is a ‘1’ then that relay output will be On.

Table B.5 – Enhanced Module Hardware Output States


0 Bit 0: DLX Output A Status of DeviceLogix Output A 1 Bit 0: DLX Output B Status of DeviceLogix Output B 2 Unused 3 Unused 4 Unused 5 Unused 6 Unused 7 Unused

The outputs can each be toggled On or Off as shown in the following RSNetworx screen in Figure B.1.

Defines the Power Source for the IE Board [Current Power Source]

Parameter Number: 63,51,39,27,15. Access rule: Get Data Type: BOOL Object Mapping: 0x3-1-102 Group: Control Units: - Minimum Value: 0 = Power from DeviceNet Maximum Value: 1 = Power from IB Default Value: 0 This parameter allows the user to determine the source of operating power for the IE board. This power can either be obtained from the IB board or from DeviceNet.

Parameters B-35

1503-UM054D-EN-P – March 2015

DeviceNet Voltage [24V DeviceNet Voltage]

Parameter Number: 64,52,40,28,16. Access rule: Get Data Type: FLOAT Object Mapping: 0x3-1-100 Group: Control Units: Volts Minimum Value: 0V Maximum Value: 50.000V Default Value: 0V This parameter allows the user to view the DeviceNet DC voltage level.

15V Supply Voltage from the IB [15V IB Voltage]

Parameter Number: 65,53,41,29,17. Access rule: Get Data Type: FLOAT Object Mapping: 0x3-1-101 Group: Control Units: Volts Minimum Value: 0V Maximum Value: 30.000V Default Value: 0V This parameter allows the user to view the DC supply voltage level from the IB board.

DeviceLogix Program Selection [Preload DeviceLogix Program]

Parameter Number: 66,54,42,30,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0xB4-1-114 Group: Control Units: - Minimum Value: 0 = User customized DeviceLogix Prog. Maximum Value: 5 = PFCC DeviceLogix Program Default Value: 0 This parameter allows the user to view, as well as to select, the DeviceLogix program that will be executed. There are six different programs that can be selected. This is shown in the following RSNetworx screen in Figure B.2.

For each of the Programs listed, a status of ‘0’ indicates that the Program is disabled and a status of ‘1’ indicates that the Program is enabled.

B-36 Parameters

1503-UM054D-EN-P – March 2015

Table B.6 – DeviceLogix Programs


0 User customized DeviceLogix Prog. Custom Logical operation – DEFAULT

1 FVR DeviceLogix Program Full Voltage Reversing Starter 2 SMC DeviceLogix Program Smart Motor Controller

3 RVR DeviceLogix Program Reduced Voltage Reactor, Non-Reversing Starter

4 RVAT DeviceLogix Program Reduced Voltage Auto-Transformer, Non-Reversing Starter

5 PFCC DeviceLogix Program Reduced Voltage Auto-Transformer, Non-Reversing Starter

6 Unused 7 unused

A detailed description of each of the DeviceLogix programs can be found in Chapter 6. Configuration of Control Inputs [Control Mask]

Parameter Number: 67,55,43,31,11. Access rule: Get/Set Data Type: USINT Object Mapping: 0xB4-1-118 Group: Control Units: - Minimum Value: 2 = DeviceLogix Maximum Value: 3 = HIM/PC Default Value: 2 This parameter allows the user to view, as well as to select, the Control Mask which defines the source of commands for the IntelliVAC Plus to use. There are four different sources available but only two can be selected for a 5 IB MC system. For each of the Masks listed, a status of ‘0’ indicates that the Mask is disabled and a status of ‘1’ indicates that the Mask is enabled.

Table B.7 – Control Masks


0 Local NOT ALLOWED 1 Network NOT ALLOWED 2 DeviceLogix Control from DeviceLogix 3 HIM/PC Control from HIM/PC 4 Unused 5 Unused 6 Unused 7 Unused

A detailed description of each of the Control masks can be found in Chapter 9, Logical Masks.

Parameters B-37

1503-UM054D-EN-P – March 2015

IntelliVAC Plus Action on Loss of DeviceNet Communications [Loss Communication Action]

Parameter Number: 68,56,44,32,19. Access rule: Get/Set Data Type: BOOL Object Mapping: 0xB4-1-125 Group: Control Units: - Minimum Value: Hold Maximum Value: Reset Default Value: Hold This parameter allows the user to view, as well as to select, the control action which occurs after a loss of DeviceNet communications occurs. There are two different actions that can be selected, either Hold or Reset. A detailed description for each of the Loss of Communications Actions can be found in Chapter 7, DeviceNet Communications Loss. Control Bits Which Consumed on DeviceNet [Consumed Net Work Bits]

Parameter Number: 69,57,45,33,20. Access rule: Get Data Type: WORD Object Mapping: 0x4-3-3 Group: Control Units: - Minimum Value: - Maximum Value: - Default Value: None This parameter allows the user to view the status of the sixteen (16) DeviceNet Consumed Network bits. Each bit position of the parameter defines the state of one of the consumed network bits. For each of the Consumed Network Bit’s listed, a status of ‘0’ indicates that the bit is disabled and a status of ‘1’ indicates that the bit is enabled.

B-38 Parameters

1503-UM054D-EN-P – March 2015

Table B.8 – Consumed Network Bits


0 Consumed Network Bit 0 Status of Consumed Network Bit 0 1 Consumed Network Bit 1 Status of Consumed Network Bit 1 2 Consumed Network Bit 2 Status of Consumed Network Bit 2 3 Consumed Network Bit 3 Status of Consumed Network Bit 3 4 Consumed Network Bit 4 Status of Consumed Network Bit 4 5 Consumed Network Bit 5 Status of Consumed Network Bit 5 6 Consumed Network Bit 6 Status of Consumed Network Bit 6 7 Consumed Network Bit 7 Status of Consumed Network Bit 7 8 Consumed Network Bit 8 Status of Consumed Network Bit 8 9 Consumed Network Bit 9 Status of Consumed Network Bit 9 10 Consumed Network Bit 10 Status of Consumed Network Bit 10 11 Consumed Network Bit 11/Net Start Status of Consumed Net Start 12 Consumed Network Bit 12/Net Stop Status of Consumed Net Stop 13 Consumed Network Bit 13/Net FWD Status of Consumed Net FWD 14 Consumed Network Bit 14/Net REV Status of Consumed Net REV 15 Consumed Network Bit 15/Net Jog Status of Consumed Net Jog

Contactor Network Commands [Network commands]

Parameter Number: 70,58,46,34,21. Access rule: Get/Set Data Type: BYTE Object Mapping: 0xB4-1-119 Group: Control Units: - Minimum Value: - Maximum Value: - Default Value: None This parameter allows the user to view and set the conditions of the five (5) DeviceNet Network commands. Each bit position of the parameter defines the state of one of the network command bits. For each of the Network Commands listed, a status of ‘0’ indicates that the bit is disabled and a status of ‘1’ indicates that the bit is enabled.

Table B.9 – Network Command


0 Bit 0: Start Status of Network Command Bit 0 1 Bit 1: Stop Status of Network Command Bit 1 2 Bit 2: FWD Status of Network Command Bit 2 3 Bit 3: REV Status of Network Command Bit 3 4 Bit 4: Jog Status of Network Command Bit 4

Parameters B-39

1503-UM054D-EN-P – March 2015

Produced Network Bits [Produced Network Bits]

Parameter Number: 71,59,47,35,22. Access rule: Get/Set Data Type: DWORD Object Mapping: 4-12-3 Group: Control Units: - Minimum Value: - Maximum Value: - Default Value: None This parameter allows the user to view and set the conditions of the five (5) DeviceNet Network commands. Each bit position of the parameter defines the state of one of the network command bits. For each of the Produced Network Bits listed, a status of ‘0’ indicates that the bit is disabled and a status of ‘1’ indicates that the bit is enabled.

Table B.10 – Produced Network Bits


0 Produced Network Bit 0/Reset All Faults Status of Produced Network Bit 01 Produced Network Bit 1 Status of Produced Network Bit 12 Produced Network Bit 2 Status of Produced Network Bit 23 Produced Network Bit 3/Interim1 Status of Produced Network Bit 34 Produced Network Bit 4/Interim2 Status of Produced Network Bit 45 Produced Network Bit 5/Interim3 Status of Produced Network Bit 56 Produced Network Bit 6/Interim4 Status of Produced Network Bit 67 Produced Network Bit 7/Interim5 Status of Produced Network Bit 78 Produced Network Bit 8/Protection status Status of Produced Network Bit 89 Produced Network Bit 9/Speed SW FWD status Status of Produced Network Bit 910 Produced Network Bit 10/Speed SW REV status Status of Produced Network Bit 1011 Produced Network Bit 11/Isolation SW status Status of Produced Network Bit 1112 Produced Network Bit 12/Remote mode status Status of Produced Network Bit 1213 Produced Network Bit 13/Local mode status Status of Produced Network Bit 1314 Produced Network Bit 14/Normal mode status Status of Produced Network Bit 1415 Produced Network Bit 15/Test mode status Status of Produced Network Bit 1516 Produced Network Bit 16/IB1-Trip Coil(M/L) Status of Produced Network Bit 1617 Produced Network Bit 17/IB1-Close Coil Status of Produced Network Bit 1718 Produced Network Bit 18/IB2-Trip Coil(M/L) Status of Produced Network Bit 1819 Produced Network Bit 19/IB2-Close Coil Status of Produced Network Bit 1920 Produced Network Bit 20/IB3-Trip Coil(M/L) Status of Produced Network Bit 2021 Produced Network Bit 21/IB3-Close Coil Status of Produced Network Bit 2122 Produced Network Bit 22/IB4-Trip Coil(M/L) Status of Produced Network Bit 2223 Produced Network Bit 23/IB4-Close Coil Status of Produced Network Bit 2324 Produced Network Bit 24/IB5-Trip Coil(M/L) Status of Produced Network Bit 2425 Produced Network Bit 25/IB5-Close Coil Status of Produced Network Bit 2526 Produced Network Bit 26/Stop status Status of Produced Network Bit 2627 Produced Network Bit 27/Stop Status of Produced Network Bit 2728 Produced Network Bit 28/Start Status of Produced Network Bit 2829 Produced Network Bit 29/FWD Status of Produced Network Bit 2930 Produced Network Bit 30/REV Status of Produced Network Bit 3031 Produced Network Bit 31/Jog Status of Produced Network Bit 31

B-40 Parameters

1503-UM054D-EN-P – March 2015

Discrete Output Point Fault Action [DOP Fault Action]

Parameter Number: 72,60,48,36,23. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x1E-1-7 Group: Control Units: - Minimum Value: 0 = Go to Fault Value Maximum Value: 1 = Hold Last State Default Value: 0 Describes the action on the occurrence of a DOP fault. Discrete Output Point Fault Value [DOP Fault Value]

Parameter Number: 73,61,49,37,24. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x1E-1-8 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 Dictates if any extra action will be performed on the occurrence of a DOP fault. Discrete Output Point Idle Action [DOP Idle Action]

Parameter Number: 74,62,50,38,25. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x1E-1-9 Group: Control Units: - Minimum Value: 0 = Go to Idle Value Maximum Value: 1 = Hold Last State Default Value: 0 Describes the action on the existence of a DOP idle condition.

Parameters B-41

1503-UM054D-EN-P – March 2015

Discrete Output Point Idle Value [DOP Idle Value]

Parameter Number: 75,63,51,34,26. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x1E-1-10 Group: Control Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 Dictates if any extra action will be performed on the existence of a DOP idle condition.

Communication Parameters DeviceNet Baud Rate [DNet Baudrate]

Parameter Number: 76,64,52,40,27. Access rule: Get/Set Data Type: SINT Object Mapping: 0x3-1-2 Group: Communication Units: - Minimum Value: 0 = 125K Maximum Value: 2 = 500K Default Value: 2 This parameter allows the user to view and set the baud rate of the DeviceNet communications network. For each of the Baud Rate Values listed, the corresponding Baud Rate is indicated.

Table B11 – DeviceNet Band Rate

Value Enum Text Description

0 125 K Baud Rate set to 125K 1 250 K Baud Rate set to 250K 2 500 K Baud Rate set to 500K

B-42 Parameters

1503-UM054D-EN-P – March 2015

DeviceNet Media Access Carrier Identification [DNet MAC ID]

Parameter Number: 77,65,53,41,28. Access rule: Get/Set Data Type: SINT Object Mapping: 0x3-1-1 Group: Communication Units: - Minimum Value: 0 Maximum Value: 63 Default Value: 0 This parameter allows the user to view and set the MAC ID of the DeviceNet communications network. The value can be anywhere in the range of 0 to 63. DeviceNet Media Access Carrier Identification Source [MAC ID Source]

Parameter Number: 78,66,54,42,29. Access rule: Get Data Type: SINT Object Mapping: 0x3-1-103 Group: Communication Units: - Minimum Value: 0 = MAC ID from Switch Maximum Value: 1 = MAC ID from DNet Default Value: 0 This parameter allows the user to view the source of the MAC ID for the DeviceNet communications network. The value is defined by the setting of the MAC ID switch settings. If the MAC ID switch setting contains a value between 0 and 63, then this parameter will be set to 0. If the MAC ID switch setting contains a value greater than 63 (i.e. 64 to 99), then this parameter will be set to 1.

Parameters B-43

1503-UM054D-EN-P – March 2015

Enabling of the AutoBaud Rate Feature [Autobaud Enable]

Parameter Number: 79,67,55,43,30. Access rule: Get/Set Data Type: BOOL Object Mapping: 0xB4-1-15 Group: Communication Units: - Minimum Value: 0 = Enabled Maximum Value: 1 = Disabled Default Value: 0 This parameter allows the user to view and set the AutoBaud Rate Enable feature. If it is enabled then the baud rate will be set by the network traffic rate, if network traffic is found. If it is disabled, then the Baud rate will be set by the DeviceNet Baud Rate parameter #76. Produced IO Bit Size [Produced IO Size]

Parameter Number: 80,68,56,44,31. Access rule: Get Data Type: USINT Object Mapping: 0xB4-1-23 Group: Communication Units: - Minimum Value: 1 Maximum Value: 7 Default Value: 7 This parameter allows the user to view the size (in bytes) of the Produced IO. Consumed IO Bit Size [Consumed IO Size]

Parameter Number: 81,69,57,45,32. Access rule: Get Data Type: USINT Object Mapping: 0xB4-1-24 Group: Communication Units: - Minimum Value: 1 Maximum Value: 3 Default Value: 3 This parameter allows the user to view the size (in bytes) of the Consumed IO.

B-44 Parameters

1503-UM054D-EN-P – March 2015

Status of the Change Of State Mask [Status COS Mask]

Parameter Number: 82,70,58,46,33. Access rule: Get/Set Data Type: DWORD Object Mapping: 0xB4-1-111 Group: Communication Units: - Minimum Value: 0 Maximum Value: 0xFFFFFFFF Default Value: 0 This parameter allows the user to view and set the status of the COS Mask. When a bit is set, that bit will not trigger a status COS message.

Table B.12 – Status COS Mask Bit Definition


0 Status COS Mask Bit 0 Status COS Mask Bit 0 “IE: Input 0” 1 Status COS Mask Bit 1 Status COS Mask Bit 1 “IE: Input 1” 2 Status COS Mask Bit 2 Status COS Mask Bit 2 “IE: Input 2” 3 Status COS Mask Bit 3 Status COS Mask Bit 3 “IE: Input 3” 4 Status COS Mask Bit 4 Status COS Mask Bit 4 “IE: Input 4” 5 Status COS Mask Bit 5 Status COS Mask Bit 5 “IE: Input 5” 6 Status COS Mask Bit 6 Status COS Mask Bit 6 “IE: Input 6” 7 Status COS Mask Bit 7 Status COS Mask Bit 7 “IE: Input 7” 8 Status COS Mask Bit 8 Status COS Mask Bit 8 “IB1: Aux Status” 9 Status COS Mask Bit 9 Status COS Mask Bit 9 “IB1: Close Status”

10 Status COS Mask Bit 10 Status COS Mask Bit 10 “IB1: Open Status 11 Status COS Mask Bit 11 Status COS Mask Bit 11 “IB2: Aux Status” 12 Status COS Mask Bit 12 Status COS Mask Bit 12 “IB2: Close Status” 13 Status COS Mask Bit 13 Status COS Mask Bit 13 “IB2: Open Status” 14 Status COS Mask Bit 14 Status COS Mask Bit 14 “IB3: Aux Status” 15 Status COS Mask Bit 15 Status COS Mask Bit 15 “IB3: Close Status” 16 Status COS Mask Bit 16 Status COS Mask Bit 16“IB3: Open Status” 17 Status COS Mask Bit 17 Status COS Mask Bit 17 “IB4: Aux Status” 18 Status COS Mask Bit 18 Status COS Mask Bit 18 “IB4: Close Status” 19 Status COS Mask Bit 19 Status COS Mask Bit 19 “IB4: Open Status” 20 Status COS Mask Bit 20 Status COS Mask Bit 20 “IB5: Aux Status” 21 Status COS Mask Bit 21 Status COS Mask Bit 21 “IB5: Close Status” 22 Status COS Mask Bit 22 Status COS Mask Bit 22 “IB5: Open Status” 23 Status COS Mask Bit 23 Status COS Mask Bit 23 “unused” 24 Status COS Mask Bit 24 Status COS Mask Bit 24 “Protection Status” 25 Status COS Mask Bit 25 Status COS Mask Bit 25 “Speed SW FWD Status” 26 Status COS Mask Bit 26 Status COS Mask Bit 26 “Speed SW REV Status” 27 Status COS Mask Bit 27 Status COS Mask Bit 27 “Isolation SW Status” 28 Status COS Mask Bit 28 Status COS Mask Bit 28 “Remote Mode Status” 29 Status COS Mask Bit 29 Status COS Mask Bit 29 “Local Mode Status” 30 Status COS Mask Bit 30 Status COS Mask Bit 30 “Normal Mode Status” 31 Status COS Mask Bit 31 Status COS Mask Bit 31 “Test Mode Status”

Parameters B-45

1503-UM054D-EN-P – March 2015

Status of the Change Of State Mask [Set to Defaults]

Parameter Number: 83,71,59,47,34. Access rule: Get/Set Data Type: USINT Object Mapping: 0xB4-1-19 Group: Communication Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Set DNet & DLX Defaults Default Value: 0 This parameter allows the user to view and set the IntelliVAC Plus to the factory default values. The parameters which are set to defaults and their values are listed below.

Table B.12a – Status of the Change of State mask Defaults

Parameter Description Default Setting Parameter Group Parameter #

DNet MAC ID 63 DeviceNet 77 DNet Baudrate 500k DeviceNet 76 Autobaud enable Disabled DeviceNet 79 Consumed I/O assembly Default assembly DeviceNet 84 Produced I/O assembly Default assembly DeviceNet 85 Produced network bits & Status bits COS mask No mask DeviceNet 86

Preload DLX Program Selection User Customized Program DeviceLogix 66

Control Mask Local DeviceLogix 67 IE DeviceLogix output fault action Fault value (0) DeviceLogix 72 IE DeviceLogix output idle action Idle value (0) DeviceLogix 74 Network override Disabled DeviceNet 91 Communications override Disabled DeviceNet 92 Time Zone GMT 00:00 DeviceNet 90 TDUV time source From IB DeviceNet 328 Drop out time source From IB DeviceNet 329 Altitude -1000 – 0000m DeviceNet 87 Loss communications action Hold DeviceNet 68 MC system locked Clear DeviceNet 349 IE status word Clear DeviceNet 345 MC status word Clear DeviceNet 346 IB1 status word Clear DeviceNet 335 IB2 status word Clear DeviceNet 336 IB3 status word Clear DeviceNet 337 IB4 status word Clear DeviceNet 338 IB5 status word Clear DeviceNet 339

B-46 Parameters

1503-UM054D-EN-P – March 2015

Selects the Format of the I/O Data Consumed [Consumed IO Assy]

Parameter Number: 84,72,60,48,35. Access rule: Get/Set Data Type: USINT Object Mapping: 0xB4-1-16 Group: Communication Units: - Minimum Value: 1 Maximum Value: 3 Default Value: 1 This parameter allows the user to view and set the format of the IO Data consumed.

Table B.13 – Format of I/O Data Consumed


1 Default Consumed Assembly: # 1

Assembly corresponds to 2 parameters and depends on product option. See Assem1 part in EDS for specific option.

2 Hardware Output Only Assembly: # 2

Assembly corresponds to 1 parameter and depends on product option. See Assem2 part in EDS for specific option.

3 Network Output Only Assembly: # 3


Selects the Format of the I/O Data Produced [Produced IO Assy]

Parameter Number: 85,73,61,49,46. Access rule: Get/Set Data Type: USINT Object Mapping: 0xB4-1-17 Group: Communication Units: - Minimum Value: 10 Maximum Value: 13 Default Value: 10 This parameter allows the user to view and set the format of the IO Data produced.

Parameters B-47

1503-UM054D-EN-P – March 2015

Table B.14 – Format of I/O Data Produced


10 Default Produced Assembly: # 10

Assembly corresponds to several parameters and depends on product option. See Assem10 part in EDS for specific option.

11 Hardware Input Only Assembly: # 11


12 Network Input Only Assembly: # 12


13 IE and IB Hardware Input Assembly: #13

Assembly corresponds to several parameters and depends on product option. See Assem13 part in EDS for specific option.

Network Output Change Of State Mask [Net Out COS Mask]

Parameter Number: 86,74,62,50,37. Access rule: Get/Set Data Type: DWORD Object Mapping: 0xB4-1-110 Group: Communication Units: - Minimum Value: 0 Maximum Value: 0xFFFFFFFF Default Value: 0 This parameter allows the user to view and set the network output COS Mask When a bit is set the network output will not trigger a COS message.

Table B.15 – Network Output COS Mask Definition

Bit Enum Text Description Action

0 Net Output Mask Bit 0 Net Output Mask Bit 0 When bit is set the network output won’t trigger a COS message.










B-48 Parameters

1503-UM054D-EN-P – March 2015

Table B.15 – Network Output COS Mask Definition (cont.)

Bit Enum Text Description Action























Parameters B-49

1503-UM054D-EN-P – March 2015

Configuration Parameters Altitude Above Sea Level [Altitude]

Parameter Number: 87,75,63,51,38. Access rule: Get/Set Data Type: USINT Object Mapping: 0xB4-1-116 Group: Configuration Units: Meters Minimum Value: 0 Maximum Value: 5 Default Value: 0 This parameter allows the user to view and set the altitude of the contactor relative to sea level For each of the Altitude Values listed, the corresponding altitude is indicated.

Table B.16 – Altitude Settings


0 -1000 ~ 0000 M Altitude of -1000 to 0000M 1 0001 ~ 1000 M Altitude of 0001 to 1000M 2 1001 ~ 2000 M Altitude of 1001 to 2000M 3 2001 ~ 3000 M Altitude of 2001 to 3000M 4 3001 ~ 4000 M Altitude of 3001 to 4000M 5 4001 ~ 5000 M Altitude of 4001 to 5000M

Real Time Clock Date [RTC Date]

Parameter Number: 88,76,64,52,39. Access rule: Get/Set Data Type: DATE Object Mapping: 0xB4-1-112 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view and set the Date on the internal Real Time Clock. To set or get this valve please use RSNetWorx. For reference, 0=1972-1-1, need to consider leap years.

B-50 Parameters

1503-UM054D-EN-P – March 2015

Real Time Clock Time [RTC Time]

Parameter Number: 89,77,65,53,40. Access rule: Get/Set Data Type: TIME_OF_DAY Object Mapping: 0xB4-1-113 Group: Configuration Units: Meters Minimum Value: 0 Maximum Value: 0x05265BFF Default Value: 0 This parameter allows the user to view and set the Time of Day on the internal Real Time Clock.

To set/set this valve, please use RSNetWorx. For reference 0=00:00:00:00ms. World Time Zone Selection [Time Zone Selection]

Parameter Number: 90,78,66,54,41. Access rule: Get/Set Data Type: SINT Object Mapping: 0xB4-1-117 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 32 Default Value: 13 This parameter allows the user to view and set the World Time Zone. This is useful when the Event Log data is required in an area with a different time zone than that in which the contactor is installed, thereby allowing the correct time to be evaluated.

Table B.17 – RTC World Time Zone Selection Local


0 GMT -12:00 Greenwich Mean Time - 12 hours 1 GMT -11:00 Greenwich Mean Time - 11 hours 2 GMT -10:00 Greenwich Mean Time - 10 hours 3 GMT - 09:00 Greenwich Mean Time - 9 hours 4 GMT - 08:00 Greenwich Mean Time - 8 hours 5 GMT - 07:00 Greenwich Mean Time - 7 hours 6 GMT - 06:00 Greenwich Mean Time - 6 hours 7 GMT - 05:00 Greenwich Mean Time - 5 hours 8 GMT - 04:00 Greenwich Mean Time - 4 hours 9 GMT - 03:30 Greenwich Mean Time - 3.5 hours

10 GMT - 03:00 Greenwich Mean Time - 3 hours 11 GMT - 02:00 Greenwich Mean Time - 2 hours 12 GMT - 01:00 Greenwich Mean Time - 1 hour

Parameters B-51

1503-UM054D-EN-P – March 2015

Table B.17 – RTC World Time Zone Selection Local (cont.)


13 GMT 00:00 Greenwich Mean Time 14 GMT + 01:00 Greenwich Mean Time + 1 hour 15 GMT + 02:00 Greenwich Mean Time + 2 hours 16 GMT + 03:00 Greenwich Mean Time + 3 hours 17 GMT + 03:30 Greenwich Mean Time + 3.5 hours 18 GMT + 04:00 Greenwich Mean Time + 4 hours 19 GMT + 04:30 Greenwich Mean Time + 4.5 hours 20 GMT + 05:00 Greenwich Mean Time + 5 hours 21 GMT + 05:30 Greenwich Mean Time + 5.5 hours 22 GMT + 05:45 Greenwich Mean Time + 5.75 hours 23 GMT + 06:00 Greenwich Mean Time + 6 hours 24 GMT + 06:30 Greenwich Mean Time + 6.5 hours 25 GMT + 07:00 Greenwich Mean Time + 7 hours 26 GMT + 08:00 Greenwich Mean Time + 8 hours 27 GMT + 09:00 Greenwich Mean Time + 9 hours 28 GMT + 09:30 Greenwich Mean Time + 9.5 hours 29 GMT + 10:00 Greenwich Mean Time + 10 hours 30 GMT + 11:00 Greenwich Mean Time + 11 hours 31 GMT + 12:00 Greenwich Mean Time + 12 hours 32 GMT + 13:00 Greenwich Mean Time + 13 hours

Override a Network Fault [Network Override]

Parameter Number: 91,79,67,55,42. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x1E-1-104 Group: Configuration Units: - Minimum Value: 0 = Disabled Maximum Value: 1 = Enabled Default Value: 1 This parameter allows the user to view and set the condition where the local logic (DeviceLogix) will override a DeviceNet Network Fault (ie. Bus off or duplicate MACID). If it is disabled then the local logic (DeviceLogix) cannot override a DeviceNet Network Fault and it will cease operating. If it is enabled then the logic (DeviceLogix) can override a DeviceNet Network Fault and it will continue to operate.

B-52 Parameters

1503-UM054D-EN-P – March 2015

Override the Loss of an IO Connection [Comm Override]

Parameter Number: 92,80,68,56,43. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x1E-1-105 Group: Configuration Units: - Minimum Value: 0 = Disabled Maximum Value: 1 = Enabled Default Value: 1 This parameter allows the user to view and set the condition where the local logic (DeviceLogix will override a DeviceNet Communications Fault (ie. Communication loss or time out). If it is disabled then the local logic (DeviceLogix) cannot override a DeviceNet Communications Fault and it will cease operating. If it is enabled then the logic (DeviceLogix) can override a DeviceNet Communications Fault and it will continue to operate.

Type of Contactor Selected for IB1 [IB 1 Contactor Type]

Parameter Number: 93,81,69,57,44. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-14 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the status of the type of contactor that is being controlled by the IB1 module. This value is set by the DIP switches on the IB1 module only (see Table 8.C).

Table B.18 – Type of Contactor for IB1 Unit


0 400A Mech. Latch IB1 is a 400A Mechanically Latched contactor 1 400A Elec. Held IB1 is a 400A Electrically Held contactor 2 800A Mech. Latch IB1 is an 800A Mechanically Latched contactor 3 800A Elec. Held IB1 is an 800A Electrically Held contactor

Parameters B-53

1503-UM054D-EN-P – March 2015


Parameter Number: 94,82,70,58,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-14 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the status of the type of contactor that is being controlled by the IB2 module. This value is set by the DIP switches on the IB2 module only (see Table 8.C).





Parameter Number: 95,83,71,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-14 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the status of the type of contactor that is being controlled by the IB3 module. This value is set by the DIP switches on the IB3 module only (see Table 8.C).




B-54 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 96,84,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-14 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the status of the type of contactor that is being controlled by the IB4 module. This value is set by the DIP switches on the IB4 module only (see Table 8.C).





Parameter Number: 97,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-14 Group: Configuration Units: - Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the status of the type of contactor that is being controlled by the IB5 module. This value is set by the DIP switches on the IB5 module only (see Table 8.C).




Parameters B-55

1503-UM054D-EN-P – March 2015

Time Delay UnderVoltage Setting for IB1 [IB 1 TDUV Configure]

Parameter Number: 98,85,72,59,45. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-1-15 Group: Configuration Units: - Minimum Value: 0 = Disable Maximum Value: 1 = Enable Default Value: 0 This parameter allows the user to view and set the status of the Time Delay UnderVoltage setting for the IB1 contactor module. If it is disabled then the TDUV feature for the IB1 contactor is disabled. If it is enabled then the TDUV feature for the IB1 contactor is enabled. See TDUV in Chapter 8 and Table 8.D. Time Delay UnderVoltage Setting for IB2 [IB 2 TDUV Configure]

Parameter Number: 99,86,73,60,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-2-15 Group: Configuration Units: - Minimum Value: 0 = Disable Maximum Value: 1 = Enable Default Value: 0 This parameter allows the user to view and set the status of the Time Delay UnderVoltage setting for the IB2 contactor module. If it is disabled then the TDUV feature for the IB2 contactor is disabled. If it is enabled then the TDUV feature for the IB2 contactor is enabled. See TDUV in Chapter 8 and Table 8.D.

B-56 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 100,87,74,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-3-15 Group: Configuration Units: - Minimum Value: 0 = Disable Maximum Value: 1 = Enable Default Value: 0 This parameter allows the user to view and set the status of the Time Delay UnderVoltage setting for the IB3 contactor module. If it is disabled then the TDUV feature for the IB3 contactor is disabled. If it is enabled then the TDUV feature for the IB3 contactor is enabled. See TDUV in Chapter 8 and Table 8.D. Time Delay UnderVoltage Setting for IB4 [IB 4 TDUV Configure] Parameter Number: 101,88,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-4-15 Group: Configuration Units: - Minimum Value: 0 = Disable Maximum Value: 1 = Enable Default Value: 0 This parameter allows the user to view and set the status of the Time Delay UnderVoltage setting for the IB4 contactor module. If it is disabled then the TDUV feature for the IB4 contactor is disabled. If it is enabled then the TDUV feature for the IB4 contactor is enabled. See TDUV in Chapter 8 and Table 8.D.

Parameters B-57

1503-UM054D-EN-P – March 2015


Parameter Number: 102,_,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-5-15 Group: Configuration Units: - Minimum Value: 0 = Disable Maximum Value: 1 = Enable Default Value: 0 This parameter allows the user to view and set the status of the Time Delay UnderVoltage setting for the IB5 contactor module. If it is disabled then the TDUV feature for the IB5 contactor is disabled. If it is enabled then the TDUV feature for the IB5 contactor is enabled. See TDUV in Chapter 8 and Table 8.D.

Power-Up Safety Setting for IB1 [IB 1 Power-Up Safety Setting]

Parameter Number: 103,89,75,61,46. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-16 Group: Configuration Units: - Minimum Value: 0 = Enable Maximum Value: 1 = Disable Default Value: 0 This parameter allows the user to view the status of the Power-Up Safety setting for the IB1 module. If it is enabled then the IB1 contactor will not close the contactor if the unit powers up with a Close command present. If it is disabled then the IB1 contactor will close the contactor if the unit powers up with a Close command present. See Power-up Safety in Chapter 8 and Table 8.F.

B-58 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 104,90,76,62,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-16 Group: Configuration Units: - Minimum Value: 0 = Enable Maximum Value: 1 = Disable Default Value: 0 This parameter allows the user to view the status of the Power-Up Safety setting for the IB2 module. If it is enabled then the IB2 contactor will not close the contactor if the unit powers up with a Close command present. If it is disabled then the IB2 contactor will close the contactor if the unit powers up with a Close command present. See Power-up Safety in Chapter 8 and Table 8.F. Power-Up Safety Setting for IB3 [IB 3 Power-Up Safety Setting]

Parameter Number: 105,91,77,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-16 Group: Configuration Units: - Minimum Value: 0 = Enable Maximum Value: 1 = Disable Default Value: 0 This parameter allows the user to view the status of the Power-Up Safety setting for the IB3 module. If it is enabled then the IB3 contactor will not close the contactor if the unit powers up with a Close command present. If it is disabled then the IB3 contactor will close the contactor if the unit powers up with a Close command present. See Power-up Safety in Chapter 8 and Table 8.F.

Parameters B-59

1503-UM054D-EN-P – March 2015


Parameter Number: 106,92,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-16 Group: Configuration Units: - Minimum Value: 0 = Enable Maximum Value: 1 = Disable Default Value: 0 This parameter allows the user to view the status of the Power-Up Safety setting for the IB4 module. If it is enabled then the IB4 contactor will not close the contactor if the unit powers up with a Close command present. If it is disabled then the IB4 contactor will close the contactor if the unit powers up with a Close command present. See Power-up Safety in Chapter 8 and Table 8.F. Power-Up Safety Setting for IB5 [IB 5 Power-Up Safety Setting]

Parameter Number: 107,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-16 Group: Configuration Units: - Minimum Value: 0 = Enable Maximum Value: 1 = Disable Default Value: 0 This parameter allows the user to view the status of the Power-Up Safety setting for the IB5 module. If it is enabled then the IB5 contactor will not close the contactor if the unit powers up with a Close command present. If it is disabled then the IB5 contactor will close the contactor if the unit powers up with a Close command present. See Power-up Safety in Chapter 8 and Table 8.F.

B-60 Parameters

1503-UM054D-EN-P – March 2015

Learn Mode Setting From IB1 [IB 1 Learn Mode Setting]

Parameter Number: 108,93,78,63,47. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-17 Group: Configuration Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the Learn Mode setting for the IB1 module. If it is Off, then the IB1 contactor will not try to determine the type of contactor that it is connected to. If it is On, then the IB1 contactor will try to determine the type of contactor that it is connected to. This feature is not functional on the Rev 1.01 firmware release. Learn Mode Setting From IB2 [IB 2 Learn Mode Setting]

Parameter Number: 109,94,79,64,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-17 Group: Configuration Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0

This parameter allows the user to view the status of the Learn Mode setting for the IB2 module. If it is Off, then the IB2 contactor will not try to determine the type of contactor that it is connected to. If it is On, then the IB2 contactor will try to determine the type of contactor that it is connected to. This feature is not functional on the Rev 1.01 firmware release.

Parameters B-61

1503-UM054D-EN-P – March 2015


Parameter Number: 110,95,80,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-17 Group: Configuration Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the Learn Mode setting for the IB3 module. If it is Off, then the IB3 contactor will not try to determine the type of contactor that it is connected to. If it is On, then the IB3 contactor will try to determine the type of contactor that it is connected to. This feature is not functional on the Rev 1.01 firmware release.


Parameter Number: 111,96,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-17 Group: Configuration Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the Learn Mode setting for the IB4 module. If it is Off, then the IB4 contactor will not try to determine the type of contactor that it is connected to. If it is On, then the IB4 contactor will try to determine the type of contactor that it is connected to. This feature is not functional on the Rev 1.01 firmware release.

B-62 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 112,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-17 Group: Configuration Units: - Minimum Value: 0 = Off Maximum Value: 1 = On Default Value: 0 This parameter allows the user to view the status of the Learn Mode setting for the IB5 module. If it is Off, then the IB5 contactor will not try to determine the type of contactor that it is connected to. If it is On, then the IB5 contactor will try to determine the type of contactor that it is connected to. This feature is not functional on the Rev 1.01 firmware release. Drop Out Time Setting for IB1 [IB 1 Drop Out Time]

Parameter Number: 113,97,81,65,48. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-1-13 Group: Configuration Units: milliseconds Minimum Value: 50 Maximum Value: 240 Default Value: 50 This parameter allows the user to view and set the Drop Out Time setting for the IB1 module. The Drop Out Time is the time required from the moment that an Open or Trip command is issued to the time that the Contactor Auxiliary Status contact, on IB1, closes, to indicate that the contactor has opened. See Contactor Drop Out Time in Chapter 8 and Table 8.B.

Parameters B-63

1503-UM054D-EN-P – March 2015

Drop Out Time Setting for IB2 [IB 2 Drop Out Time]

Parameter Number: 114,98,82,66,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-2-13 Group: Configuration Units: Milliseconds Minimum Value: 50 Maximum Value: 240 Default Value: 50 This parameter allows the user to view and set the Drop Out Time setting for the IB2 module. The Drop Out Time is the time required from the moment that an Open or Trip command is issued to the time that the Contactor Auxiliary Status contact, on IB2, closes, to indicate that the contactor has opened. See Contactor Drop Out Time in Chapter 8 and Table 8.B. Drop Out Time Setting for IB3 [IB 3 Drop Out Time]

Parameter Number: 115,99,83,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-3-13 Group: Configuration Units: milliseconds Minimum Value: 50 Maximum Value: 240 Default Value: 50 This parameter allows the user to view and set the Drop Out Time setting for the IB3 module. The Drop Out Time is the time required from the moment that an Open or Trip command is issued to the time that the Contactor Auxiliary Status contact, on IB3, closes, to indicate that the contactor has opened. See Contactor Drop Out Time in Chapter 8 and Table 8.B.

B-64 Parameters

1503-UM054D-EN-P – March 2015

Drop Out Time Setting for IB4 [IB 4 Drop Out Time]

Parameter Number: 116,100,_,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-4-13 Group: Configuration Units: milliseconds Minimum Value: 50 Maximum Value: 240 Default Value: 50 This parameter allows the user to view and set the Drop Out Time setting for the IB4 module. The Drop Out Time is the time required from the moment that an Open or Trip command is issued to the time that the Contactor Auxiliary Status contact, on IB4, closes, to indicate that the contactor has opened. See Contactor Drop Out Time in Chapter 8 and Table 8.B. Drop Out Time Setting for IB5 [IB 5 Drop Out Time]

Parameter Number: 117,_,_,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-5-13 Group: Configuration Units: milliseconds Minimum Value: 50 Maximum Value: 240 Default Value: 50 This parameter allows the user to view and set the Drop Out Time setting for the IB5 module. The Drop Out Time is the time required from the moment that an Open or Trip command is issued to the time that the Contactor Auxiliary Status contact, on IB5, closes, to indicate that the contactor has opened. See Contactor Drop Out Time in Chapter 8 and Table 8.B.

Parameters B-65

1503-UM054D-EN-P – March 2015

Drop Out Time Setting From IB1 DIP Switches [IB 1 Drop Out Time DIP Setting]

Parameter Number: 118,101,84,67,49. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-49 Group: Configuration Units: milliseconds Minimum Value: 0 Maximum Value: 7 Default Value: 0 This parameter allows the user to view the Drop Out Time Setting set from the IB1 DIP switches. The Drop Out Time is initially set by the IB1 DIP switches but can be over-ridden by Parameter #113 after which time the original IB1 DIP switch settings will no longer be used.

Table B.23 – Drop Out Time Settings From IB1 DIP Switches


0 50 ms 50 ms from IB1 DIP switches 1 75 ms 75 ms from IB1 DIP switches 2 100 ms 100 ms from IB1 DIP switches 3 130 ms 130 ms from IB1 DIP switches 4 150 ms 150 ms from IB1 DIP switches 5 175 ms 175 ms from IB1 DIP switches 6 200 ms 200 ms from IB1 DIP switches 7 240 ms 240 ms from IB1 DIP switches


Parameter Number: 119,102.85,68,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-49 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 7 Default Value: 0 This parameter allows the user to view the Drop Out Time Setting set from the IB2 DIP switches. The Drop Out Time is initially set by the IB2 DIP switches but can be over-ridden by Parameter #114 after which time the original IB2 DIP switch settings will no longer be used.

B-66 Parameters

1503-UM054D-EN-P – March 2015

Table B.24 – Drop Out Time Settings from IB2 DIP Switches




is applied on IB. Drop Out Time Setting From IB3 DIP Switches [IB 3 Drop Out Time DIP Setting]

Parameter Number: 120,103,86,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-49 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 7 Default Value: 0 This parameter allows the user to view the Drop Out Time Setting set from the IB3 DIP switches. The Drop Out Time is initially set by the IB3 DIP switches but can be over-ridden by Parameter #115 after which time the original IB3 DIP switch settings will no longer be used.




Note: The drop off time would be 6 ms longer if the close command

is applied on IB.

Parameters B-67

1503-UM054D-EN-P – March 2015


Parameter Number: 121,104,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-49 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 7 Default Value: 0 This parameter allows the user to view the Drop Out Time Setting set from the IB4 DIP switches. The Drop Out Time is initially set by the IB4 DIP switches but can be over-ridden by Parameter #116 after which time the original IB4 DIP switch settings will no longer be used.





is applied on IB. Drop Out Time Setting From IB5 DIP Switches [IB 5 Drop Out Time DIP Setting]

Parameter Number: 122,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-49 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 7 Default Value: 0 This parameter allows the user to view the Drop Out Time Setting set from the IB5 DIP switches. The Drop Out Time is initially set by the IB5 DIP switches but can be over-ridden by Parameter #117 after which time the original IB5 DIP switch settings will no longer be used.

B-68 Parameters

1503-UM054D-EN-P – March 2015




Contactor Pick Up Time for IB1 [IB 1 Pick Up Time]

Parameter Number: 123,105,87,69,50. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-18 Group: Configuration Units: mSeconds Minimum Value: 0 Maximum Value: 255 Default Value: 0 This parameter allows the user to view the Pick Up Time for the IB1 contactor. The Pick Up Time is the interval from when a Close or Trip command is issued to the time that the Contactor Auxiliary contact on IB1 opens, indicating that the contactor is closed.


Parameter Number: 124,106,88,70,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-18 Group: Configuration Units: mSeconds Minimum Value: 0 Maximum Value: 255 Default Value: 0 This parameter allows the user to view the Pick Up Time for the IB2 contactor. The Pick-Up Time is the interval from when a Close or Trip command is issued to the time that the Contactor Auxiliary contact on IB2 opens, indicating that the contactor is closed.

Parameters B-69

1503-UM054D-EN-P – March 2015


Parameter Number: 125,107,89,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-18 Group: Configuration Units: mSeconds Minimum Value: 0 Maximum Value: 255 Default Value: 0 This parameter allows the user to view the Pick Up Time for the IB3 contactor. The Pick Up Time is the interval from when a Close or Trip command is issued to the time that the Contactor Auxiliary contact on IB3 opens, indicating that the contactor is closed. Contactor Pick Up Time for IB4 [IB 4 Pick Up Time]

Parameter Number: 126,108,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-18 Group: Configuration Units: mSeconds Minimum Value: 0 Maximum Value: 255 Default Value: 0 This parameter allows the user to view the Pick Up Time for the IB4 contactor. The Pick Up Time is the interval from when a Close or Trip command is issued to the time that the Contactor Auxiliary contact on IB4 opens, indicating that the contactor is closed.

B-70 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 127,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-18 Group: Configuration Units: mSeconds Minimum Value: 0 Maximum Value: 255 Default Value: 0 This parameter allows the user to view the Pick Up Time for the IB5 contactor. The Pick Up Time is the interval from when a Close or Trip command is issued to the time that the Contactor Auxiliary contact on IB5 opens, indicating that the contactor is closed. TDUV Time Setting from IB1 DIP Switches [IB 1 TDUV Time DIP Setting]

Parameter Number: 128,109,90,71,51. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-58 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the Time Delay Undervoltage Setting set from the IB1 DIP switches. The Time Delay Undervoltage Setting is initially set by the IB1 DIP switches but can be over-ridden by Parameter #133 after which time the original IB1 DIP switch settings will no longer be used. See TDUV in Chapter 8 and Table 8.E.

Table B.28 – TDUV Time Setting From IB1 DIP Switches


0 0.2 Sec 0.2 Sec TDUV setting from IB1 DIP switches 1 0.5 Sec 0.5 Sec TDUV setting from IB1 DIP switches 2 1.0 Sec 1.0 Sec TDUV setting from IB1 DIP switches 3 2.0 Sec 2.0 Sec TDUV setting from IB1 DIP switches

Parameters B-71

1503-UM054D-EN-P – March 2015

TDUV Time Setting from IB2 DIP Switches [IB 2 TDUV Time DIP Setting]

Parameter Number: 129,110,91,72,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-58 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the Time Delay Undervoltage Setting set from the IB2 DIP switches. The Time Delay Undervoltage Setting is initially set by the IB2 DIP switches but can be over-ridden by Parameter #134 after which time the original IB2 DIP switch settings will no longer be used. See TDUV in Chapter 8 and Table 8.E.





Parameter Number: 130,111,92,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-58 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the Time Delay Undervoltage Setting set from the IB3 DIP switches. The Time Delay Undervoltage Setting is initially set by the IB3 DIP switches but can be over-ridden by Parameter #135 after which time the original IB3 DIP switch settings will no longer be used. See TDUV in Chapter 8 and Table 8.E.

B-72 Parameters

1503-UM054D-EN-P – March 2015





Parameter Number: 131,112,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-58 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the Time Delay Undervoltage Setting set from the IB4 DIP switches. The Time Delay Undervoltage Setting is initially set by the IB4 DIP switches but can be over-ridden by Parameter #136 after which time the original IB4 DIP switch settings will no longer be used. See TDUV in Chapter 8 and Table 8.E.




Parameters B-73

1503-UM054D-EN-P – March 2015


Parameter Number: 132,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-58 Group: Configuration Units: see table Minimum Value: 0 Maximum Value: 3 Default Value: 0 This parameter allows the user to view the Time Delay Undervoltage Setting set from the IB5 DIP switches. The Time Delay Undervoltage Setting is initially set by the IB5 DIP switches but can be over-ridden by Parameter #137 after which time the original IB5 DIP switch settings will no longer be used. See TDUV in Chapter 8 and Table 8.E.




TDUV Time Setting for IB1 [IB 1 TDUV Time]

Parameter Number: 133,113,93,73,52 Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-1-50 Group: Configuration Units: Seconds error in EDS file Minimum Value: 0.2 Maximum Value: 2.0 Default Value: 0.2 This parameter allows the user to view and set the Time Delay Undervoltage setting for the IB1 module. The Time Delay Undervoltage setting is the time allowed for contactor IB1 to remain operational when the mains input voltage goes below the minimum operating voltage (see Electrical Specifications section for both Close and Hold modes). See TDUV Programmability in Chapter 4 for a detailed description of this feature.

B-74 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 134,114,94,74,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-2-50 Group: Configuration Units: Seconds error in EDS file Minimum Value: 0.2 Maximum Value: 2.0 Default Value: 0.2 This parameter allows the user to view and set the Time Delay Undervoltage setting for the IB2 module. The Time Delay Undervoltage setting is the time allowed for contactor IB2 to remain operational when the mains input voltage goes below the minimum operating voltage (see Electrical Specifications section for both Close and Hold modes). See TDUV Programmability in Chapter 4 for a detailed description of this feature. TDUV Time Setting for IB3 [IB 3 TDUV Time]

Parameter Number: 135,115,95,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-3-50 Group: Configuration Units: Seconds error in EDS file Minimum Value: 0.2 Maximum Value: 2.0 Default Value: 0.2 This parameter allows the user to view and set the Time Delay Undervoltage setting for the IB3 module. The Time Delay Undervoltage setting is the time allowed for contactor IB3 to remain operational when the mains input voltage goes below the minimum operating voltage (see Electrical Specifications section for both Close and Hold modes). See TDUV Programmability in Chapter 4 for a detailed description of this feature.

Parameters B-75

1503-UM054D-EN-P – March 2015


Parameter Number: 136,116,_,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-4-50 Group: Configuration Units: Seconds error in EDS file Minimum Value: 0.2 Maximum Value: 2.0 Default Value: 0.2 This parameter allows the user to view and set the Time Delay Undervoltage setting for the IB4 module. The Time Delay Undervoltage setting is the time allowed for contactor IB4 to remain operational when the mains input voltage goes below the minimum operating voltage (see Electrical Specifications section for both Close and Hold modes). See TDUV Programmability in Chapter 4 for a detailed description of this feature.


Parameter Number: 137,_,_,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-5-50 Group: Configuration Units: Seconds error in EDS file Minimum Value: 0.2 Maximum Value: 2.0 Default Value: 0.2 This parameter allows the user to view and set the Time Delay Undervoltage setting for the IB5 module. The Time Delay Undervoltage setting is the time allowed for contactor IB5 to remain operational when the mains input voltage goes below the minimum operating voltage (see Electrical Specifications section for both Close and Hold modes). See TDUV Programmability in Chapter 4 for a detailed description of this feature.

B-76 Parameters

1503-UM054D-EN-P – March 2015

Delay Restart Time for IB1 [IB 1 Delay Restart Time]

Parameter Number: 138,117,96,75,53. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-1-19 Group: Configuration Units: Seconds Minimum Value: 6 Maximum Value: 3600 Default Value: 12 This parameter allows the user to view and set the Delay Restart Time between successive Open/Trip and Close commands for contactor IB1. This sets a maximum repetition time for the cycling of the contactor. It can also be used to prevent rapid restating of the motor. See Delayed Restart in Chapter 4 for a more detailed description of this feature.


Parameter Number: 139,118,97,76,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-2-19 Group: Configuration Units: Seconds Minimum Value: 6 Maximum Value: 3600 Default Value: 12 This parameter allows the user to view and set the Delay Restart Time between successive Open/Trip and Close commands for contactor IB2. This sets a maximum repetition time for the cycling of the contactor. It can also be used to prevent rapid restating of the motor. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

Parameters B-77

1503-UM054D-EN-P – March 2015


Parameter Number: 140,119,98,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-3-19 Group: Configuration Units: Seconds Minimum Value: 6 Maximum Value: 3600 Default Value: 12 This parameter allows the user to view and set the Delay Restart Time between successive Open/Trip and Close commands for contactor IB3. This sets a maximum repetition time for the cycling of the contactor. It can also be used to prevent rapid restating of the motor. See Delayed Restart in Chapter 4 for a more detailed description of this feature.


Parameter Number: 141,120,_,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-4-19 Group: Configuration Units: Seconds Minimum Value: 6 Maximum Value: 3600 Default Value: 12 This parameter allows the user to view and set the Delay Restart Time between successive Open/Trip and Close commands for contactor IB4. This sets a maximum repetition time for the cycling of the contactor. It can also be used to prevent rapid restating of the motor. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

B-78 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 142,_,_,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-5-19 Group: Configuration Units: Seconds Minimum Value: 6 Maximum Value: 3600 Default Value: 12 This parameter allows the user to view and set the Delay Restart Time between successive Open/Trip and Close commands for contactor IB5. This sets a maximum repetition time for the cycling of the contactor. It can also be used to prevent rapid restating of the motor. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

Delay Restart Wait Time for IB1 [IB 1 Delay Restart Wait Time]

Parameter Number: 143,121,99,77,54. Access rule: Get Data Type: UINT Object Mapping: 0x384-1-20 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 3600 Default Value: 0 This parameter allows the user to view the Delay Restart Wait Time for IB1. It shows the time left, as a constantly updated real time, after the contactor has closed, before it is permitted to close again. This parameter works in conjunction with parameter #138 which defines the minimum time allowed between successive closings of contactor IB1. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

Parameters B-79

1503-UM054D-EN-P – March 2015


Parameter Number: 144,122,100,78,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-2-20 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 3600 Default Value: 0 This parameter allows the user to view the Delay Restart Wait Time for IB2. It shows the time left, as a constantly updated real time, after the contactor has closed, before it is permitted to close again. This parameter works in conjunction with parameter #139 which defines the minimum time allowed between successive closings of contactor IB2. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

Delay Restart Wait Time For IB3 [IB 3 Delay Restart Wait Time]

Parameter Number: 145,123,101,_,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-3-20 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 3600 Default Value: 0 This parameter allows the user to view the Delay Restart Wait Time for IB3. It shows the time left, as a constantly updated real time, after the contactor has closed, before it is permitted to close again. This parameter works in conjunction with parameter #140 which defines the minimum time allowed between successive closings of contactor IB3. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

B-80 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 146,124,_,_,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-4-20 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 3600 Default Value: 0 This parameter allows the user to view the Delay Restart Wait Time for IB4. It shows the time left, as a constantly updated real time, after the contactor has closed, before it is permitted to close again. This parameter works in conjunction with parameter #141 which defines the minimum time allowed between successive closings of contactor IB4. See Delayed Restart in Chapter 4 for a more detailed description of this feature. Delay Restart Wait Time for IB5 [IB 5 Delay Restart Wait Time]

Parameter Number: 147,_,_,_,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-5-20 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 3600 Default Value: 0 This parameter allows the user to view the Delay Restart Wait Time for IB5. It shows the time left, as a constantly updated real time, after the contactor has closed, before it is permitted to close again. This parameter works in conjunction with parameter #142 which defines the minimum time allowed between successive closings of contactor IB5. See Delayed Restart in Chapter 4 for a more detailed description of this feature.

Parameters B-81

1503-UM054D-EN-P – March 2015

Jog Time for IB1 [IB 1 Jog Time]

Parameter Number: 148,125,102,79,55. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-1-21 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 30 Default Value: 12 This parameter allows the user to view and set the Jog Time for contactor IB1. It indicates the amount of time that a contactor can be Jogged (momentarily closed) for. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature. Jog Time for IB2 [IB 2 Jog Time]

Parameter Number: 149,126,103,80,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-2-21 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 30 Default Value: 12 This parameter allows the user to view and set the Jog Time for contactor IB2. It indicates the amount of time that a contactor can be Jogged (momentarily closed) for. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature.

B-82 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 150,127,104,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-3-21 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 30 Default Value: 12 This parameter allows the user to view and set the Jog Time for contactor IB3. It indicates the amount of time that a contactor can be Jogged (momentarily closed) for. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature. Jog Time for IB4 [IB 4 Jog Time]

Parameter Number: 151,128,_,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-4-21 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 30 Default Value: 12 This parameter allows the user to view and set the Jog Time for contactor IB4. It indicates the amount of time that a contactor can be Jogged (momentarily closed) for. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature.

Parameters B-83

1503-UM054D-EN-P – March 2015


Parameter Number: 152,_,_,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-5-21 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 30 Default Value: 12 This parameter allows the user to view and set the Jog Time for contactor IB5. It indicates the amount of time that a contactor can be Jogged (momentarily closed) for. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature. Jog Repetition Time for IB1 [IB 1 Jog Repetition Time]

Parameter Number: 153,129,105,81,56. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-1-22 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 60 Default Value: 6 This parameter allows the user to view and set the Jog Repetition Time for contactor IB1. It indicates the amount of time between successive Jog intervals. Therefore, once a Jog interval has begun, it cannot be repeated until the Jog Repetition Time has elapsed for contactor IB1. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature.

B-84 Parameters

1503-UM054D-EN-P – March 2015

Jog Repetition Time for IB2 [IB 2 Jog Repetition Time]

Parameter Number: 154,130,106,82,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-2-22 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 60 Default Value: 6 This parameter allows the user to view and set the Jog Repetition Time for contactor IB2. It indicates the amount of time between successive Jog intervals. Therefore, once a Jog interval has begun, it cannot be repeated until the Jog Repetition Time has elapsed for contactor IB2. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature. Jog Repetition Time for IB3 [IB 3 Jog Repetition Time]

Parameter Number: 155,131,107,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-3-22 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 60 Default Value: 6 This parameter allows the user to view and set the Jog Repetition Time for contactor IB3. It indicates the amount of time between successive Jog intervals. Therefore, once a Jog interval has begun, it cannot be repeated until the Jog Repetition Time has elapsed for contactor IB3. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature.

Parameters B-85

1503-UM054D-EN-P – March 2015

Jog Repetition Time for IB4 [IB 4 Jog Repetition Time] Parameter Number: 156,132,_,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-4-22 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 60 Default Value: 6 This parameter allows the user to view and set the Jog Repetition Time for contactor IB4. It indicates the amount of time between successive Jog intervals. Therefore, once a Jog interval has begun, it cannot be repeated until the Jog Repetition Time has elapsed for contactor IB4. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature.

Jog Repetition Time for IB5 [IB 5 Jog Repetition Time] Parameter Number: 157,_,_,_,_. Access rule: Get/Set Data Type: UINT Object Mapping: 0x384-5-22 Group: Configuration Units: Seconds Minimum Value: 0 Maximum Value: 60 Default Value: 6 This parameter allows the user to view and set the Jog Repetition Time for contactor IB5. It indicates the amount of time between successive Jog intervals. Therefore, once a Jog interval has begun, it cannot be repeated until the Jog Repetition Time has elapsed for contactor IB5. This is only for Electrically Held contactors and makes use of the Open command. See Temporary Jog Function in Chapter 4 for a more detailed description of this feature.

B-86 Parameters

1503-UM054D-EN-P – March 2015

Diagnostics Parameters Invalid Command on IB1 Level [IB 1 Invalid Command]

Parameter Number: 158,133,108,83,57. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-23 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Invalid Command warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Invalid Command in Chapter 4 for a detailed description of this warning. Invalid Command on IB2 Level [IB 2 Invalid Command]

Parameter Number: 159,134,109,84. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-23 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Invalid Command warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Invalid Command in Chapter 4 for a detailed description of this warning.

Parameters B-87

1503-UM054D-EN-P – March 2015

Invalid Command on IB3 Level [IB 3 Invalid Command] Parameter Number: 160,135,110,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-23 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Invalid Command warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Invalid Command in Chapter 4 for a detailed description of this warning.

Invalid Command on IB4 Level [IB 4 Invalid Command] Parameter Number: 161,136,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-23 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Invalid Command warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Invalid Command in Chapter 4 for a detailed description of this warning.

B-88 Parameters

1503-UM054D-EN-P – March 2015

Invalid Command on IB5 Level [IB 5 Invalid Command] Parameter Number: 162,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-23 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Invalid Command warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Invalid Command in Chapter 4 for a detailed description of this warning.

Mechanical Latch Fails to Trip on IB1 [IB 1 Mechanical Latch Fail to Trip] Parameter Number: 163,137,111,85,58. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-24 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Mechanical Latch Fail to Trip warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Mechanical Latch Fail to Trip in Chapter 4 for a detailed description of this warning.

Parameters B-89

1503-UM054D-EN-P – March 2015

Mechanical Latch Fails to Trip on IB2 [IB 2 Mechanical Latch Fail to Trip] Parameter Number: 164,138,112,86,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-24 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Mechanical Latch Fail to Trip warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Mechanical Latch Fail to Trip in Chapter 4 for a detailed description of this warning.

Mechanical Latch Fails to Trip on IB3 [IB 3 Mechanical Latch Fail to Trip] Parameter Number: 165,139,113,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-24 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Mechanical Latch Fail to Trip warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Mechanical Latch Fail to Trip in Chapter 4 for a detailed description of this warning.

B-90 Parameters

1503-UM054D-EN-P – March 2015

Mechanical Latch Fails to Trip on IB4 [IB 4 Mechanical Latch Fail to Trip] Parameter Number: 166,140,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-24 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Mechanical Latch Fail to Trip warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Mechanical Latch Fail to Trip in Chapter 4 for a detailed description of this warning. Mechanical Latch Fails to Trip on IB5 [IB 5 Mechanical Latch Fail to Trip] Parameter Number: 167,_,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-24 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Mechanical Latch Fail to Trip warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Mechanical Latch Fail to Trip in Chapter 4 for a detailed description of this warning.

Parameters B-91

1503-UM054D-EN-P – March 2015

Contactor Fails to Pick-Up on IB1 [IB 1 Contactor Fails to Pick-Up] Parameter Number: 168,141,114,87,59. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-25 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Fails to Pick-Up warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Pick Up in Chapter 4 for a detailed description of this warning. Contactor Fails to Pick-Up on IB2 [IB 2 Contactor Fails to Pick-Up] Parameter Number: 169,142,115,88,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-25 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Fails to Pick-Up warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Pick Up in Chapter 4 for a detailed description of this warning.

B-92 Parameters

1503-UM054D-EN-P – March 2015

Contactor Fails to Pick-Up on IB3 [IB 3 Contactor Fails to Pick-Up] Parameter Number: 170,143,116,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-25 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Fails to Pick-Up warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Pick Up in Chapter 4 for a detailed description of this warning. Contactor Fails to Pick-Up on IB4 [IB 4 Contactor Fails to Pick-Up] Parameter Number: 171,144,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-25 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Fails to Pick-Up warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Pick Up in Chapter 4 for a detailed description of this warning.

Parameters B-93

1503-UM054D-EN-P – March 2015

Contactor Fails to Pick-Up on IB5 [IB 5 Contactor Fails to Pick-Up] Parameter Number: 172,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-25 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Fails to Pick-Up warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Pick Up in Chapter 4 for a detailed description of this warning. Contactor Drop-Out during Hold on IB1 [IB 1 Contactor Drop-out During Hold] Parameter Number: 173,145,117,89,60. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-26 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Drop-Out during Hold warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Drop-Out during Hold in Chapter 4 for a detailed description of this warning.

B-94 Parameters

1503-UM054D-EN-P – March 2015

Contactor Drop-Out during Hold on IB2 [IB 2 Contactor Drop-out During Hold] Parameter Number: 174,146,118,90,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-26 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Drop-Out during Hold warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Drop-Out during Hold in Chapter 4 for a detailed description of this warning.

Contactor Drop-Out during Hold on IB3 [IB 3 Contactor Drop-out During Hold] Parameter Number: 175,147,119,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-26 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Drop-Out during Hold warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Drop-Out during Hold in Chapter 4 for a detailed description of this warning.

Parameters B-95

1503-UM054D-EN-P – March 2015

Contactor Drop-Out during Hold on IB4 [IB 4 Contactor Drop-out During Hold] Parameter Number: 176,148,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-26 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Drop-Out during Hold warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Drop-Out during Hold in Chapter 4 for a detailed description of this warning.

Contactor Drop-Out during Hold on IB5 [IB 5 Contactor Drop-out During Hold] Parameter Number: 177,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-26 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Drop-Out during Hold warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Drop-Out during Hold in Chapter 4 for a detailed description of this warning.

B-96 Parameters

1503-UM054D-EN-P – March 2015

Contactor Long Drop Out Time on IB1 [IB 1 Contactor Long Drop Out Time] Parameter Number: 178,149,120,91,61. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-60 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Long Drop Out Time warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Long Contactor Drop Out Time in Chapter 4 for a detailed description of this warning.

Contactor Long Drop Out Time on IB2 [IB 2 Contactor Long Drop Out Time] Parameter Number: 179,150,121,92,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-60 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Long Drop Out Time warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Long Contactor Drop Out Time in Chapter 4 for a detailed description of this warning.

Parameters B-97

1503-UM054D-EN-P – March 2015

Contactor Long Drop Out Time on IB3 [IB 3 Contactor Long Drop Out Time] Parameter Number: 180,151,122,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-60 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Long Drop Out Time warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Long Contactor Drop Out Time in Chapter 4 for a detailed description of this warning. Contactor Long Drop Out Time on IB4 [IB 4 Contactor Long Drop Out Time] Parameter Number: 181,152,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-60 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Long Drop Out Time warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Long Contactor Drop Out Time in Chapter 4 for a detailed description of this warning.

B-98 Parameters

1503-UM054D-EN-P – March 2015

Contactor Long Drop Out Time on IB5 [IB 5 Contactor Long Drop Out Time] Parameter Number: 182,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-60 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Long Drop Out Time warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Long Contactor Drop Out Time in Chapter 4 for a detailed description of this warning. Contactor Fails to Drop Out on IB1 [IB 1 Contactor Fails To Drop Out] Parameter Number: 183,153,123,93,62. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-27 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor Fails to Drop Out fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Drop Out in Chapter 4 for a detailed description of this warning.

Parameters B-99

1503-UM054D-EN-P – March 2015

Contactor Fails to Drop Out on IB2 [IB 2 Contactor Fails To Drop Out] Parameter Number: 184,154,124,94,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-27 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Fails to Drop Out fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Drop Out in Chapter 4 for a detailed description of this warning.

Contactor Fails to Drop Out on IB3 [IB 3 Contactor Fails To Drop Out] Parameter Number: 185,155,125,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-27 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Fails to Drop Out fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Drop Out in Chapter 4 for a detailed description of this warning.

B-100 Parameters

1503-UM054D-EN-P – March 2015

Contactor Fails to Drop Out on IB4 [IB 4 Contactor Fails To Drop Out] Parameter Number: 186,156,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-27 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Fails to Drop Out fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Drop Out in Chapter 4 for a detailed description of this warning.

Contactor Fails to Drop Out on IB5 [IB 5 Contactor Fails To Drop Out] Parameter Number: 187,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-27 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor Fails to Drop Out fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Fails to Drop Out in Chapter 4 for a detailed description of this warning.

Parameters B-101

1503-UM054D-EN-P – March 2015

Long Close Time on IB1 [IB 1 Long Close Time] Parameter Number: 188,157,126,95,63. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-54 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Long Close Time warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Extended Close Time in Chapter 4 for a detailed description of this warning.

Long Close Time on IB2 [IB 2 Long Close Time] Parameter Number: 189,158,127,96,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-54 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Long Close Time warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Extended Close Time in Chapter 4 for a detailed description of this warning.

B-102 Parameters

1503-UM054D-EN-P – March 2015

Long Close Time on IB3 [IB 3 Long Close Time] Parameter Number: 190,159,128,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-54 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Long Close Time warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Extended Close Time in Chapter 4 for a detailed description of this warning.

Long Close Time on IB4 [IB 4 Long Close Time] Parameter Number: 191,160,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-54 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Long Close Time warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Extended Close Time in Chapter 4 for a detailed description of this warning.

Parameters B-103

1503-UM054D-EN-P – March 2015

Long Close Time on IB5 [IB 5 Long Close Time] Parameter Number: 192,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-54 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Long Close Time warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Extended Close Time in Chapter 4 for a detailed description of this warning.

Power Up with Contactor Closed on IB1 [IB 1 Power-up with Contactor Closed] Parameter Number: 193,161,129,97,64. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-29 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Power Up with Contactor Closed fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Contactor Close in Chapter 4 for a detailed description of this warning.

B-104 Parameters

1503-UM054D-EN-P – March 2015

Power Up with Contactor Closed on IB2 [IB 2 Power-up with Contactor Closed] Parameter Number: 194,162,130,98,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-29 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Power Up with Contactor Closed fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Contactor Closed in Chapter 4 for a detailed description of this warning.

Power Up with Contactor Closed on IB3 [IB 3 Power-up with Contactor Closed] Parameter Number: 195,163,131,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-29 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Power Up with Contactor Closed fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Contactor Close in Chapter 4 for a detailed description of this warning.

Parameters B-105

1503-UM054D-EN-P – March 2015

Power Up with Contactor Closed on IB4 [IB 4 Power-up with Contactor Closed] Parameter Number: 196,164,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-29 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Power Up with Contactor Closed fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Contactor Close in Chapter 4 for a detailed description of this warning.

Power Up with Contactor Closed on IB5 [IB 5 Power-up with Contactor Closed] Parameter Number: 197,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-29 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Power Up with Contactor Closed fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Contactor Close in Chapter 4 for a detailed description of this warning.

B-106 Parameters

1503-UM054D-EN-P – March 2015

Power Up with Invalid DIP Switch Configuration on IB1 [IB 1 Power-up with Invalid DIP Switch Configuration] Parameter Number: 198,165,132,99,65. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-30 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Power Up with Invalid DIP Switch Configuration fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Invalid DIP Switch Configuration in Chapter 4 for a detailed description of this warning. Power Up with Invalid DIP Switch Configuration on IB2 [IB 2 Power-up with Invalid DIP Switch Configuration] Parameter Number: 199,166,133,100,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-30 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Power Up with Invalid DIP Switch Configuration fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Invalid DIP Switch Configuration in Chapter 4 for a detailed description of this warning.

Parameters B-107

1503-UM054D-EN-P – March 2015

Power Up with Invalid DIP Switch Configuration on IB3 [IB 3 Power-up with Invalid DIP Switch Configuration] Parameter Number: 200,167,134,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-30 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Power Up with Invalid DIP Switch Configuration fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Invalid DIP Switch Configuration in Chapter 4 for a detailed description of this warning. Power Up with Invalid DIP Switch Configuration on IB4 [IB 4 Power-up with Invalid DIP Switch Configuration] Parameter Number: 201,168,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-30 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Power Up with Invalid DIP Switch Configuration fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Invalid DIP Switch Configuration in Chapter 4 for a detailed description of this warning.

B-108 Parameters

1503-UM054D-EN-P – March 2015

Power Up with Invalid DIP Switch Configuration on IB5 [IB 5 Power-up with Invalid DIP Switch Configuration] Parameter Number: 202,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-30 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Power Up with Invalid DIP Switch Configuration fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Power Up with Invalid DIP Switch Configuration in Chapter 4 for a detailed description of this warning.

Under Voltage with Close Command Present on IB1 [IB 1 U/V with Close Command Present] Parameter Number: 203,169,135,101,66. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-31 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Under Voltage with Close Command Present warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Undervoltage with a Close Command Present in Chapter 4 for a detailed description of this warning.

Parameters B-109

1503-UM054D-EN-P – March 2015

Under Voltage with Close Command Present on IB2 [IB 2 U/V with Close Command Present] Parameter Number: 204,170,136,102,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-31 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Under Voltage with Close Command Present warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Undervoltage with a Close Command Present in Chapter 4 for a detailed description of this warning. Under Voltage with Close Command Present on IB3 [IB 3 U/V with Close Command Present] Parameter Number: 205,171,137,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-31 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Under Voltage with Close Command Present warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Undervoltage with a Close Command Present in Chapter 4 for a detailed description of this warning.

B-110 Parameters

1503-UM054D-EN-P – March 2015

Under Voltage with Close Command Present on IB4 [IB 4 U/V with Close Command Present] Parameter Number: 206,172,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-31 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Under Voltage with Close Command Present warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Undervoltage with a Close Command Present in Chapter 4 for a detailed description of this warning. Under Voltage with Close Command Present on IB5 [IB 5 U/V with Close Command Present] Parameter Number: 207,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-31 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Under Voltage with Close Command Present warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Undervoltage with a Close Command Present in Chapter 4 for a detailed description of this warning.

Parameters B-111

1503-UM054D-EN-P – March 2015

Module not Healthy on IB1 [IB 1 Module not Healthy] Parameter Number: 208,173,138,103,67. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-28 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Module not Healthy fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning. Module not Healthy on IB2 [IB 2 Module not Healthy] Parameter Number: 209,174,139,104,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-28 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Module not Healthy fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

B-112 Parameters

1503-UM054D-EN-P – March 2015

Module not Healthy on IB3 [IB 3 Module not Healthy] Parameter Number: 210,175,140,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-28 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Module not Healthy fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

Module not Healthy on IB4 [IB 4 Module not Healthy] Parameter Number: 211,176,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-28 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Module not Healthy fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

Parameters B-113

1503-UM054D-EN-P – March 2015

Module not Healthy on IB5 [IB 5 Module not Healthy] Parameter Number: 212,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-28 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Module not Healthy fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

Contactor not Healthy on IB1 [IB 1 Contactor Not Healthy] Parameter Number: 213,177,141,105,68. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-56 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor not Healthy fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

Contactor not Healthy on IB2 [IB 2 Contactor Not Healthy] Parameter Number: 214,178,142,106,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-56 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor not Healthy fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

B-114 Parameters

1503-UM054D-EN-P – March 2015

Contactor not Healthy on IB3 [IB 3 Contactor Not Healthy]

Parameter Number: 215,179,143,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-56 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor not Healthy fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.


Parameter Number: 216,180,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-56 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Contactor not Healthy fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.


Parameter Number: 217,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-56 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Contactor not Healthy fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Table 4.E and related description for a detailed description of this warning.

Parameters B-115

1503-UM054D-EN-P – March 2015

Input Line Undervoltage during Close on IB1 [IB 1 Line Undervoltage Close] Parameter Number: 218,181,144,107,69. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-45 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Close period fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Input Line Undervoltage during Close on IB2 [IB 2 Line Undervoltage Close] Parameter Number: 219,182,145,108,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-45 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Close period fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

B-116 Parameters

1503-UM054D-EN-P – March 2015

Input Line Undervoltage During Close on IB3 [IB 3 Line Undervoltage Close] Parameter Number: 220,183,146,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-45 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Close period fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Input Line Undervoltage during Close on IB4 [IB 4 Line Undervoltage Close] Parameter Number: 221,184,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-45 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Close period fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

Parameters B-117

1503-UM054D-EN-P – March 2015

Input Line Undervoltage during Close on IB5 [IB 5 Line Undervoltage Close] Parameter Number: 222,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-45 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Undervoltage during a Close period fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

Input Line Undervoltage during Hold on IB1 [IB 1 Line Undervoltage Hold] Parameter Number: 223,185,147,109,70. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-59 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Undervoltage during a Hold period fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

B-118 Parameters

1503-UM054D-EN-P – March 2015

Input Line Undervoltage during Hold on IB2 [IB 2 Line Undervoltage Hold] Parameter Number: 224,186,148,110,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-59 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Hold period fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Input Line Undervoltage during Hold on IB3 [IB 3 Line Undervoltage Hold] Parameter Number: 225,187,144,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-59 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Hold period fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

Parameters B-119

1503-UM054D-EN-P – March 2015

Input Line Undervoltage during Hold on IB4 [IB 4 Line Undervoltage Hold Parameter Number: 226,188,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-59 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Undervoltage during a Hold period fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Input Line Undervoltage during Hold on IB5 [IB 5 Line Undervoltage Hold] Parameter Number: 227,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-59 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Undervoltage during a Hold period fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

B-120 Parameters

1503-UM054D-EN-P – March 2015

Input Line Overvoltage on IB1 [IB 1 Line Overvoltage] Parameter Number: 228,189,150,111,71. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-46 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Overvoltage fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Input Line Overvoltage on IB2 [IB 2 Line Overvoltage] Parameter Number: 229,190,151,112,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-46 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Overvoltage fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

Parameters B-121

1503-UM054D-EN-P – March 2015

Input Line Overvoltage on IB3 [IB 3 Line Overvoltage] Parameter Number: 230,191,152,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-46 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of the Input Line Overvoltage fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Input Line Overvoltage on IB4 [IB 4 Line Overvoltage] Parameter Number: 231,192,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-46 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Overvoltage fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

B-122 Parameters

1503-UM054D-EN-P – March 2015

Input Line Overvoltage on IB5 [IB 5 Line Overvoltage] Parameter Number: 232,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-46 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the Input Line Overvoltage fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning. Loss of Input Line Power on IB1 [IB 1 Line Loss] Parameter Number: 233,193,153,113,72. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-47 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0

This parameter allows the user to view the status of Loss of Input Line Power fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

Parameters B-123

1503-UM054D-EN-P – March 2015

Loss of Input Line Power on IB2 [IB 2 Line Loss]

Parameter Number: 234,194,154,114,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-47 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Loss of Input Line Power fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.


Parameter Number: 235,195,155,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-47 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Loss of Input Line Power fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.


Parameter Number: 236,196,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-47 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Loss of Input Line Power fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

B-124 Parameters

1503-UM054D-EN-P – March 2015


Parameter Number: 237,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-47 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Loss of Input Line Power fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Supply Voltage in Chapter 4 for a detailed description of this warning.

Main Coil Open on IB1 [IB 1 Main Coil Open]

Parameter Number: 238,197,156,115,73. Access rule: Get Data Type: USINT Object Mapping: 0x384-1-48 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Main Coil Open fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.


Parameter Number: 239,198,157,116,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-2-48 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Main Coil Open fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.

Parameters B-125

1503-UM054D-EN-P – March 2015


Parameter Number: 240,199,158,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-3-48 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Main Coil Open fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.


Parameter Number: 241,200,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-4-48 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Main Coil Open fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.


Parameter Number: 242,_,_,_,_. Access rule: Get Data Type: USINT Object Mapping: 0x384-5-48 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Main Coil Open fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.

B-126 Parameters

1503-UM054D-EN-P – March 2015

Trip Coil Open on IB1 [IB 1 Trip Coil Open]

Parameter Number: 243,201,159,117,74. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-57 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Trip Coil Open fault from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.


Parameter Number: 244,202,160,118,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-57 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Trip Coil Open fault from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.


Parameter Number: 245,203,161,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-57 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Trip Coil Open fault from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.

Parameters B-127

1503-UM054D-EN-P – March 2015


Parameter Number: 246,204,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-57 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Trip Coil Open fault from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.


Parameter Number: 247,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-57 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Trip Coil Open fault from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Open Coil Test in Chapter 4 for a detailed description of this warning.

Extended Close Time on IB1 [IB 1 Extended Pick up Time]

Parameter Number: 248,205,162,119,75. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-55 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Extended Pick up Time warning from the IB1 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Close Time, Extended Close Time & Tables 4.F & 4.G in Chapter 4 for a detailed description of this warning.

B-128 Parameters

1503-UM054D-EN-P – March 2015

Extended Close Time on IB2 [IB 2 Extended Pick up Time] Parameter Number: 249,206,163,120,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-55 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Extended Pick up Time warning from the IB2 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Close Time, Extended Close Time & Tables 4.F & 4.G in Chapter 4 for a detailed description of this warning. Extended Close Time on IB3 [IB 3 Extended Pick up Time] Parameter Number: 250,207,164,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-55 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Extended Pick up Time warning from the IB3 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Close Time, Extended Close Time & Tables 4.F & 4.G in Chapter 4 for a detailed description of this warning.

Parameters B-129

1503-UM054D-EN-P – March 2015

Extended Close Time on IB4 [IB 4 Extended Pick up Time] Parameter Number: 251,208,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-55 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Extended Pick up Time warning from the IB4 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Close Time, Extended Close Time & Tables 4.F & 4.G in Chapter 4 for a detailed description of this warning.

Extended Close Time on IB5 [IB 5 Extended Pick up Time] Parameter Number: 252,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-55 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of Extended Pick up Time warning from the IB5 module. If the bit is ‘0’ then the warning is not present. If the bit is ‘1’ then the warning is present. See Contactor Close Time, Extended Close Time & Tables 4.F & 4.G in Chapter 4 for a detailed description of this warning.

B-130 Parameters

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB1 [IB 1 Average Operations per Time Unit] Parameter Number: 253,209,165,121,76. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-1-43 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 2 Default Value: 0 This parameter allows the user to view and set the status of the Average Number of Operations per Unit Time for IB1. The Time Unit is used to set the period over which the Average number of Operations is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

Table B.33 – Time Unit for Average # Close Operators for IB1


0 Hour Average Close operations per Hour for IB1 1 Day Average Close operations per Day for IB1 2 Week Average Close operations per Week for IB1

Average Number of Operations on IB1 [IB 1 Average Operations Value] Parameter Number: 254,210,166,111,77. Access rule: Get Data Type: UDINT Object Mapping: 0x384-1-44 Group: Diagnostics Units: Avg. # of Close operations per unit time Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the status of the Average Number of Close Operations, for IB1, as measured per the Unit Time set in parameter #253. The Time Unit is used to set the period over which the Average number of Operations, for IB1, is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

Parameters B-131

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB2 [IB 2 Average Operations per Time Unit] Parameter Number: 255,211,167,123,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-2-43 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 2 Default Value: 0 This parameter allows the user to view and set the status of the Average Number of Operations per Unit Time for IB2. The Time Unit is used to set the period over which the Average number of Operations is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

Table B.34 – Time Unit for Average # Close Operations for IB2



Average Number of Operations on IB2 [IB 2 Average Operations Value] Parameter Number: 256,212,168,124,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-2-44 Group: Diagnostics Units: Avg. # of Close operations per unit time Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the status of the Average Number of Close Operations, for IB2, as measured per the Unit Time set in parameter #255. The Time Unit is used to set the period over which the Average number of Operations, for IB2, is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

B-132 Parameters

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB3 [IB 3 Average Operations per Time Unit] Parameter Number: 257,213,169,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-3-43 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 2 Default Value: 0 This parameter allows the user to view and set the status of the Average Number of Operations per Unit Time for IB3. The Time Unit is used to set the period over which the Average number of Operations is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.




Average Number of Operations on IB3 [IB 3 Average Operations Value] Parameter Number: 258,214,170,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-3-44 Group: Diagnostics Units: Avg. # of Close operations per unit time Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the status of the Average Number of Close Operations, for IB3, as measured per the Unit Time set in parameter #257. The Time Unit is used to set the period over which the Average number of Operations, for IB3, is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

Parameters B-133

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB4 [IB 4 Average Operations per Time Unit] Parameter Number: 259,215,_,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-4-43 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 2 Default Value: 0 This parameter allows the user to view and set the status of the Average Number of Operations per Unit Time for IB4. The Time Unit is used to set the period over which the Average number of Operations is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.




Average Number of Operations on IB4 [IB 4 Average Operations Value] Parameter Number: 260,216,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-4-44 Group: Diagnostics Units: Avg. # of Close operations per unit time Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the status of the Average Number of Close Operations, for IB4, as measured per the Unit Time set in parameter #259. The Time Unit is used to set the period over which the Average number of Operations, for IB4, is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

B-134 Parameters

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB5 [IB 5 Average Operations per Time Unit] Parameter Number: 261,_,_,_,_. Access rule: Get/Set Data Type: USINT Object Mapping: 0x384-5-43 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 2 Default Value: 0 This parameter allows the user to view and set the status of the Average Number of Operations per Unit Time for IB5. The Time Unit is used to set the period over which the Average number of Operations is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

Table B.37 – Time Unit for Average # Close Operation for IB5



Average Number of Operations on IB5 [IB 5 Average Operations Value] Parameter Number: 262,_,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-5-44 Group: Diagnostics Units: Avg. # of Close operations per unit time Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the status of the Average Number of Close Operations, for IB5, as measured per the Unit Time set in parameter #261. The Time Unit is used to set the period over which the Average number of Operations, for IB5, is to be calculated for. See “Average Operations” Counter in Chapter 4 for a detailed description of this feature.

Parameters B-135

1503-UM054D-EN-P – March 2015

Total Number of Close Operations on IB1 [IB 1 Master Counter] Parameter Number: 263,217,171,125,78. Access rule: Get Data Type: UDINT Object Mapping: 0x384-1-32 Group: Diagnostics Units: Total number of Close operations for IB1 Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0

This parameter allows the user to view the Total Number of Close Operations that has occurred on IB1 since its initial use. This value cannot be reset. See Master Counter in Chapter 4 for a detailed description of this feature. Total Number of Close Operations on IB2 [IB 2 Master Counter] Parameter Number: 264,218,172,126,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-2-32 Group: Diagnostics Units: Total number of Close operations for IB2 Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the Total Number of Close Operations that has occurred on IB2 since its initial use. This value cannot be reset. See Master Counter in Chapter 4 for a detailed description of this feature.

B-136 Parameters

1503-UM054D-EN-P – March 2015

Total Number of Close Operations on IB3 [IB 3 Master Counter] Parameter Number: 265,219,173,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-3-32 Group: Diagnostics Units: Total number of Close operations for IB3 Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the Total Number of Close Operations that has occurred on IB3 since its initial use. This value cannot be reset. See Master Counter in Chapter 4 for a detailed description of this feature. Total Number of Close Operations on IB4 [IB 4 Master Counter] Parameter Number: 266,220,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-4-32 Group: Diagnostics Units: Total number of Close operations for IB4 Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the Total Number of Close Operations that has occurred on IB4 since its initial use. This value cannot be reset. See Master Counter in Chapter 4 for a detailed description of this feature.

Parameters B-137

1503-UM054D-EN-P – March 2015

Total Number of Close Operations on IB5 [IB 5 Master Counter] Parameter Number: 267,_,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-5-32 Group: Diagnostics Units: Total number of Close operations for IB5 Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the Total Number of Close Operations that has occurred on IB5 since its initial use. This value cannot be reset. See Master Counter in Chapter 4 for a detailed description of this feature. Average Number of Operations per Time Unit on IB1 [IB 1 Reset Operations since Counter] Parameter Number: 268,221,174,127,79. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-1-33 Group: Diagnostics Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Reset Default Value: 0 This parameter allows the user to view and set the status of the Reset “Operations Since” Counter for IB1. If the bit is a ‘0’ then No Operation is performed on the Average Counting vs. Time update feature for IB1. If the bit is a ‘1’ then a counter Reset is performed whereby the present number of Close operations that have occurred, on IB1, will be transferred to the Operations-1 Event Count, along with the Date and Time. Likewise, the previous Operations-1 Event Count, along with the Date and Time, will be transferred to the Operations-1 Event Since -1, along with the Date and Time. Finally the previous Operations-1 Event Count, along with the Date and Time, will be transferred to the Operations-1 Event Since -2, along with the Date and Time. This sequence is like a single ended queue whereby the present counter value is stored in a location and the previous data stored in that location is moved to another location, and so on. This particular system uses a queue with three levels whereby the highest level will always contain the latest Operations Counter value along with the Date/Time and the second highest level will contain the data that was in the highest level and finally the third

B-138 Parameters

1503-UM054D-EN-P – March 2015

highest level will contain the data that was in the second highest level. This system will provide that there will always be three sets of Counter operation records for three discrete times. Thus, this feature allows the user to monitor the number of Close operations that have occurred over three discrete time periods for historical operation of the contactor or for maintenance reasons. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Average Number of Operations per Time Unit on IB2 [IB 2 Reset Operations Since Counter] Parameter Number: 269,222,175,128,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-2-33 Group: Diagnostics Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Reset Default Value: 0 This parameter allows the user to view and set the status of the Reset “Operations Since” Counter for IB2. If the bit is a ‘0’ then No Operation is performed on the Average Counting vs. Time update feature for IB2. If the bit is a ‘1’ then a counter Reset is performed whereby the present number of Close operations that have occurred, on IB2, will be transferred to the Operations-2 Event Count, along with the Date and Time. Likewise, the previous Operations-2 Event Count, along with the Date and Time, will be transferred to the Operations-2 Event Since -1, along with the Date and Time. Finally the previous Operations-2 Event Count, along with the Date and Time, will be transferred to the Operations-2 Event Since -2, along with the Date and Time. This sequence is like a single ended queue whereby the present counter value is stored in a location and the previous data stored in that location is moved to another location, and so on. This particular system uses a queue with three levels whereby the highest level will always contain the latest Operations Counter value along with the Date/Time and the second highest level will contain the data that was in the highest level and finally the third highest level will contain the data that was in the second highest level. This system will provide that there will always be three sets of Counter operation records for three discrete times. Thus, this feature allows the user to monitor the number of Close operations that have occurred over three discrete time periods for historical operation of the contactor or for maintenance reasons. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-139

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB3 [IB 3 Reset Operations Since Counter] Parameter Number: 270,223,176,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-3-33 Group: Diagnostics Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Reset Default Value: 0 This parameter allows the user to view and set the status of the Reset “Operations Since” Counter for IB3. If the bit is a ‘0’ then No Operation is performed on the Average Counting vs. Time update feature for IB3. If the bit is a ‘1’ then a counter Reset is performed whereby the present number of Close operations that have occurred, on IB3, will be transferred to the Operations-3 Event Count, along with the Date and Time. Likewise, the previous Operations-3 Event Count, along with the Date and Time, will be transferred to the Operations-3 Event Since -1, along with the Date and Time. Finally the previous Operations-3 Event Count, along with the Date and Time, will be transferred to the Operations-3 Event Since -2, along with the Date and Time. This sequence is like a single ended queue whereby the present counter value is stored in a location and the previous data stored in that location is moved to another location, and so on. This particular system uses a queue with three levels whereby the highest level will always contain the latest Operations Counter value along with the Date/Time and the second highest level will contain the data that was in the highest level and finally the third highest level will contain the data that was in the second highest level. This system will provide that there will always be three sets of Counter operation records for three discrete times. Thus, this feature allows the user to monitor the number of Close operations that have occurred over three discrete time periods for historical operation of the contactor or for maintenance reasons. See “Operations Since” Counter in Chapter 4 9 for a more detailed description of this feature.

B-140 Parameters

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB4 [IB 4 Reset Operations Since Counter] Parameter Number: 271,224,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-4-33 Group: Diagnostics Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Reset Default Value: 0 This parameter allows the user to view and set the status of the Reset “Operations Since” Counter for IB4. If the bit is a ‘0’ then No Operation is performed on the Average Counting vs. Time update feature for IB4. If the bit is a ‘1’ then a counter Reset is performed whereby the present number of Close operations that have occurred, on IB4, will be transferred to the Operations-4 Event Count, along with the Date and Time. Likewise, the previous Operations-4 Event Count, along with the Date and Time, will be transferred to the Operations-4 Event Since -1, along with the Date and Time. Finally the previous Operations-4 Event Count, along with the Date and Time, will be transferred to the Operations-4 Event Since -2, along with the Date and Time. This sequence is like a single ended queue whereby the present counter value is stored in a location and the previous data stored in that location is moved to another location, and so on. This particular system uses a queue with three levels whereby the highest level will always contain the latest Operations Counter value along with the Date/Time and the second highest level will contain the data that was in the highest level and finally the third highest level will contain the data that was in the second highest level. This system will provide that there will always be three sets of Counter operation records for three discrete times. Thus, this feature allows the user to monitor the number of Close operations that have occurred over three discrete time periods for historical operation of the contactor or for maintenance reasons. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-141

1503-UM054D-EN-P – March 2015

Average Number of Operations per Time Unit on IB5 [IB 5 Reset Operations Since Counter] Parameter Number: 272,_,_,_,_. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x384-5-33 Group: Diagnostics Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Reset Default Value: 0 This parameter allows the user to view and set the status of the Reset “Operations Since” Counter for IB5. If the bit is a ‘0’ then No Operation is performed on the Average Counting vs. Time update feature for IB5. If the bit is a ‘1’ then a counter Reset is performed whereby the present number of Close operations that have occurred, on IB5, will be transferred to the Operations-5 Event Count, along with the Date and Time. Likewise, the previous Operations-5 Event Count, along with the Date and Time, will be transferred to the Operations-5 Event Since -1, along with the Date and Time. Finally the previous Operations-5 Event Count, along with the Date and Time, will be transferred to the Operations-5 Event Since -2, along with the Date and Time. This sequence is like a single ended queue whereby the present counter value is stored in a location and the previous data stored in that location is moved to another location, and so on. This particular system uses a queue with three levels whereby the highest level will always contain the latest Operations Counter value along with the Date/Time and the second highest level will contain the data that was in the highest level and finally the third highest level will contain the data that was in the second highest level. This system will provide that there will always be three sets of Counter operation records for three discrete times. Thus, this feature allows the user to monitor the number of Close operations that have occurred over three discrete time periods for historical operation of the contactor or for maintenance reasons. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-142 Parameters

1503-UM054D-EN-P – March 2015

Operations since 0 Count Value on IB1 [IB 1 Operations Since 0 Count Value] Parameter Number: 273,225,177,129,80. Access rule: Get Data Type: UDINT Object Mapping: 0x384-1-34 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB1 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Date of Operations since 0 Count Value on IB1 [IB 1 Operations Since 0 Date] Parameter Number: 274,226,178,130,81. Access rule: Get Data Type: DATE Object Mapping: 0x384-1-35 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0

This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB1 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-143

1503-UM054D-EN-P – March 2015

Time of Operations Since 0 Count Value on IB1 [IB 1 Operations since 0 Time] Parameter Number: 275,227,179,131,82. Access rule: Get Data Type: TIME Object Mapping: 0x384-1-36 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB1 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Operations Since 1 Count Value on IB1 [IB 1 Operations Since 1 Count Value] Parameter Number: 276,228,180,132,83. Access rule: Get Data Type: UDINT Object Mapping: 0x384-1-37 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB1 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-144 Parameters

1503-UM054D-EN-P – March 2015

Date of Operations Since 1 Count Value on IB1 [IB 1 Operations Since 1 Date] Parameter Number: 277,229,181,133,84. Access rule: Get Data Type: DATE Object Mapping: 0x384-1-38 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB1 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Time of Operations Since 1 Count Value on IB1 [IB 1 Operations Since 1 Time] Parameter Number: 278,230,182,134,85. Access rule: Get Data Type: TIME Object Mapping: 0x384-1-39 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB1 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-145

1503-UM054D-EN-P – March 2015

Operations Since 2 Count Value on IB1 [IB 1 Operations Since 2 Count Value] Parameter Number: 279,231,183,135,86. Access rule: Get Data Type: UDINT Object Mapping: 0x384-1-40 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB1 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Date of Operations Since 2 Count Value on IB1 [IB 1 Operations Since 2 Date] Parameter Number: 280,232,184,136,87. Access rule: Get Data Type: DATE Object Mapping: 0x384-1-41 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB1 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-146 Parameters

1503-UM054D-EN-P – March 2015

Time of Operations Since 2 Count Value on IB1 [IB 1 Operations Since 2 Time] Parameter Number: 281,233,185,137,88. Access rule: Get Data Type: TIME Object Mapping: 0x384-1-42 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB1 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Operations Since 0 Count Value on IB2 [IB 2 Operations Since 0 Count Value] Parameter Number: 282,234,186,138,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-2-34 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB2 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-147

1503-UM054D-EN-P – March 2015

Date of Operations Since 0 Count Value on IB2 [IB 2 Operations Since 0 Date] Parameter Number: 283,235,187,139,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-2-35 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB2 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Time of Operations Since 0 Count Value on IB2 [IB 2 Operations Since 0 Time] Parameter Number: 284,236,188,140,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-2-36 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB2 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-148 Parameters

1503-UM054D-EN-P – March 2015

Operations Since 1 Count Value on IB2 [IB 2 Operations Since 1 Count Value] Parameter Number: 285,237,189,141,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-2-37 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB2 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Date of Operations Since 1 Count Value on IB2 [IB 2 Operations Since 1 Date] Parameter Number: 286,238,190,142,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-2-38 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB2 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-149

1503-UM054D-EN-P – March 2015

Time of Operations Since 1 Count Value on IB2 [IB 2 Operations Since 1 Time] Parameter Number: 287,239,191,143,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-1-39 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB2 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Operations Since 2 Count Value on IB2 [IB 2 Operations Since 2 Count Value] Parameter Number: 288,240,192,144,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-2-40 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB2 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-150 Parameters

1503-UM054D-EN-P – March 2015

Date of Operations Since 2 Count Value on IB2 [IB 2 Operations Since 2 Date] Parameter Number: 289,241,193,145,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-2-41 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB2 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Time of Operations Since 2 Count Value on IB2 [IB 2 Operations Since 2 Time] Parameter Number: 290,242,194,146,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-2-42 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB2 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-151

1503-UM054D-EN-P – March 2015

Operations Since 0 Count Value on IB3 [IB 3 Operations Since 0 Count Value] Parameter Number: 291,243,195,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-3-34 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB3 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Date of Operations Since 0 Count Value on IB3 [IB 3 Operations Since 0 Date] Parameter Number: 292,244,196,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-3-35 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB3 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-152 Parameters

1503-UM054D-EN-P – March 2015

Time of Operations Since 0 Count Value on IB3 [IB 3 Operations Since 0 Time] Parameter Number: 293,245,197,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-3-36 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB3 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Operations Since 1 Count Value on IB3 [IB 3 Operations Since 1 Count Value] Parameter Number: 294,246,198,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-3-37 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB3 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-153

1503-UM054D-EN-P – March 2015

Date of Operations Since 1 Count Value on IB3 [IB 3 Operations Since 1 Date] Parameter Number: 295,247,199,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-3-38 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB3 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Time of Operations Since 1 Count Value on IB3 [IB 3 Operations Since 1 Time] Parameter Number: 296,248,200,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-3-39 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB3 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-154 Parameters

1503-UM054D-EN-P – March 2015

Operations Since 2 Count Value on IB3 [IB 3 Operations Since 2 Count Value] Parameter Number: 297,249,201,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-3-40 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB3 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Date of Operations Since 2 Count Value on IB3 [IB 3 Operations Since 2 Date] Parameter Number: 298,250,202,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-3-41 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB3 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-155

1503-UM054D-EN-P – March 2015

Time of Operations Since 2 Count Value on IB3 [IB 3 Operations Since 2 Time] Parameter Number: 299,251,203,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-3-42 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB3 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Operations Since 0 Count Value on IB4 [IB 4 Operations Since 0 Count Value] Parameter Number: 300,252,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-4-34 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB4 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-156 Parameters

1503-UM054D-EN-P – March 2015

Date of Operations Since 0 Count Value on IB4 [IB 4 Operations Since 0 Date] Parameter Number: 301,253,_,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-4-35 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB4 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Time of Operations Since 0 Count Value on IB4 [IB 4 Operations Since 0 Time] Parameter Number: 302,254,_,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-4-36 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB4 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-157

1503-UM054D-EN-P – March 2015

Operations Since 1 Count Value on IB4 [IB 4 Operations Since 1 Count Value] Parameter Number: 303,255,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-4-37 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB4 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Date of Operations Since 1 Count Value on IB4 [IB 4 Operations Since 1 Date] Parameter Number: 304,256,_,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-4-38 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB4 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-158 Parameters

1503-UM054D-EN-P – March 2015

Time of Operations Since 1 Count Value on IB4 [IB 4 Operations Since 1 Time] Parameter Number: 305,257,_,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-4-39 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB4 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Operations Since 2 Count Value on IB4 [IB 4 Operations Since 2 Count Value] Parameter Number: 306,258,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-4-40 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB4 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-159

1503-UM054D-EN-P – March 2015

Date of Operations Since 2 Count Value on IB4 [IB 4 Operations Since 2 Date] Parameter Number: 307,259,_,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-4-41 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0

This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB4 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Time of Operations Since 2 Count Value on IB4 [IB 4 Operations Since 2 Time] Parameter Number: 308,260,_,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-4-42 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB4 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-160 Parameters

1503-UM054D-EN-P – March 2015

Operations Since 0 Count Value on IB5 [IB 5 Operations Since 0 Count Value] Parameter Number: 309,_,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-5-34 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB5 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Date of Operations Since 0 Count Value on IB5 [IB 5 Operations Since 0 Date] Parameter Number: 310,_,_,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-5-35 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB5 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-161

1503-UM054D-EN-P – March 2015

Time of Operations Since 0 Count Value on IB5 [IB 5 Operations Since 0 Time] Parameter Number: 311,_,_,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-5-36 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB5 event occurred. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Operations Since 1 Count Value on IB5 [IB 5 Operations Since 1 Count Value] Parameter Number: 312,_,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-5-37 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0

This parameter allows the user to view the number of Operations since a Reset Counter on IB5 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-162 Parameters

1503-UM054D-EN-P – March 2015

Date of Operations Since 1 Count Value on IB5 [IB 5 Operations Since 1 Date] Parameter Number: 313,_,_,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-5-38 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB5 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Time of Operations Since 1 Count Value on IB5 [IB 5 Operations Since 1 Time] Parameter Number: 314,_,_,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-5-39 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB5 event occurred and transferred the Since 0 count value to the Since 1 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

Parameters B-163

1503-UM054D-EN-P – March 2015

Operations Since 2 Count Value on IB5 [IB 5 Operations Since 2 Count Value] Parameter Number: 315,_,_,_,_. Access rule: Get Data Type: UDINT Object Mapping: 0x384-5-40 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFFFF Default Value: 0 This parameter allows the user to view the number of Operations since a Reset Counter on IB5 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Date of Operations Since 2 Count Value on IB5 [IB 5 Operations Since 1 Date] Parameter Number: 316,_,_,_,_. Access rule: Get Data Type: DATE Object Mapping: 0x384-5-41 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the Date for which the Operations since a Reset Counter on IB5 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature.

B-164 Parameters

1503-UM054D-EN-P – March 2015

Time of Operations Since 2 Count Value on IB5 [IB 5 Operations Since 1 Time] Parameter Number: 317,_,_,_,_. Access rule: Get Data Type: TIME Object Mapping: 0x384-5-42 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0

This parameter allows the user to view the Time for which the Operations since a Reset Counter on IB5 event occurred and transferred the Since 1 count value to the Since 2 count value. See “Operations Since” Counter in Chapter 4 for a more detailed description of this feature. Length of Event Log on IB1 [IB 1 Event Present Length] Parameter Number: 318,261,204,147,89. Access rule: Get Data Type: UINT Object Mapping: 0x384-1-52 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 100 Default Value: 0 This parameter allows the user to view the Length of the Event Log for IB1. Up to a maximum of 100 Events can be stored, for IB1, in the Event Log before older Events are overwritten with newer Events. See Event Log in Chapter 4 for a more detailed description of this feature.

Parameters B-165

1503-UM054D-EN-P – March 2015

Length of Event Log on IB2 [IB 2 Event Present Length] Parameter Number: 319,262,205,148,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-2-52 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 100 Default Value: 0 This parameter allows the user to view the Length of the Event Log for IB2. Up to a maximum of 100 Events can be stored, for IB2, in the Event Log before older Events are overwritten with newer Events. See Event Log in Chapter 4 for a more detailed description of this feature. Length of Event Log on IB3 [IB 3 Event Present Length] Parameter Number: 320,263,206,_,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-3-52 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 100 Default Value: 0 This parameter allows the user to view the Length of the Event Log for IB3. Up to a maximum of 100 Events can be stored, for IB3, in the Event Log before older Events are overwritten with newer Events. See Event Log in Chapter 4 for a more detailed description of this feature.

B-166 Parameters

1503-UM054D-EN-P – March 2015

Length of Event Log on IB4 [IB 4 Event Present Length] Parameter Number: 321,264,_,_,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-4-52 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 100 Default Value: 0 This parameter allows the user to view the Length of the Event Log for IB4. Up to a maximum of 100 Events can be stored, for IB4, in the Event Log before older Events are overwritten with newer Events. See Event Log in Chapter 4 for a more detailed description of this feature. Length of Event Log on IB5 [IB 5 Event Present Length] Parameter Number: 322,_,_,_,_. Access rule: Get Data Type: UINT Object Mapping: 0x384-5-52 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 100 Default Value: 0 This parameter allows the user to view the Length of the Event Log for IB5. Up to a maximum of 100 Events can be stored, for IB5, in the Event Log before older Events are overwritten with newer Events. See Event Log in Chapter 4 for a more detailed description of this feature.

Parameters B-167

1503-UM054D-EN-P – March 2015

Module Status of IB1 [IB Status] Parameter Number: 323,265,207,149,90. Access rule: Get Data Type: BYTE Object Mapping: 0xB4-1-120 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFF Default Value: 0 This parameter allows the user to view the Module Status of IB1.

Table B.38 – Module Status of IB1


0 Bit 0: Test Mode IB1 in Test Mode 1 Bit 1: Normal Mode IB1 in Normal Mode 2 Bit 2: Local Mode IB1 in Local Mode 3 Bit 3: Remote Mode IB1 in Remote Mode 4 Bit 4: Isolation SW IB1 Isolation SW 5 Bit 5: Speed REV IB1 in REV Speed 6 Bit 6: Speed FWD IB1 in FWD Speed 7 Bit 7: Protection IB1 in Protection Mode

See “Status Inputs” in DeviceLogix, Chapter 9 for an explanation of each of those bits. Run the DeviceLogix Module [Run DeviceLogix] Parameter Number: 324,266,208,150,91. Access rule: Get/Set Data Type: BOOL Object Mapping: 0x30E-1-1 Group: Diagnostics Units: - Minimum Value: 0 = Stop DeviceLogix Program Maximum Value: 1 = Run DeviceLogix Program Default Value: 0 This parameter allows the user to view and set the operating mode for the DeviceLogix Module that has been selected. If the bit is a ‘0’ then the selected DeviceLogix Program will be Stopped. If the bit is a ‘1’ then the selected DeviceLogix Program will be Run.

B-168 Parameters

1503-UM054D-EN-P – March 2015

Invalid DeviceLogix Program Loaded [Invalid DeviceLogix Program] Parameter Number: 325,267,209,151,92. Access rule: Get Data Type: BOOL Object Mapping: 0xB4-1-115 Group: Diagnostics Units: - Minimum Value: 0 = Invalid DLX Prog. Maximum Value: 1 = Valid or No DLX Prog. Default Value: 1 This parameter allows the user to view the status of the DeviceLogix Program that has been selected for operation. If the bit is a ‘0’ then the DeviceLogix Program is invalid. This can occur if a Custom DeviceLogix Program is loaded which has an incorrect setting that would prevent the program from operating in a correct logical manner. If the bit is a ‘1’ then the DeviceLogix Program selected is either valid or is blank. A blank program could only occur if the ‘User customized DeviceLogix Prog.’ was selected as setting ‘0’ in parameter #66, Preload DeviceLogix Program and the custom program was blank.

Power Fail Status for IB1 [IB1 Power Fail Status] Parameter Number: 326,268,210,152,93. Access rule: Get Data Type: BOOL Object Mapping: 0xB4-1-121 Group: Diagnostics Units: - Minimum Value: 0 = Bad Maximum Value: 1 = Good Default Value: 0 This parameter allows the user to view the status of the IB1 power level. This refers to the +15VDC power supply on the IB unit which powers the IE unit. If the bit is a ‘0’ then the IB1 power is bad. If the bit is a ‘1’ then the IB1 power is good.

Parameters B-169

1503-UM054D-EN-P – March 2015

Altitude Settings on MC Units Inconsistent [MC Altitude Set Warning] Parameter Number: 327,269,211,153,94. Access rule: Get Data Type: BOOL Object Mapping: 0xB4-1-122 Group: Diagnostics Units: - Minimum Value: 0 = Not Fault Maximum Value: 1 = MC Altitude setting inconsistent Default Value: 0

This parameter allows the user to view the status of the Altitude settings from the various IntelliVAC MC units. If this bit is a ‘0’ then all MC units have the same altitude setting and no further action is required. If this bit is a ‘1’ then not all of the MC units have the same altitude setting. Since all of the contactors in an IntelliVAC MC system will be located at the same altitude, the altitude parameter should be the same for each of the units. If all of the units are not set to the same altitude, then there will definitely be a problem with the coil operating currents of some of the units. See Table 8.A for setting the altitude parameters for each of the IB units in an MC system.

Time Delay UnderVoltage Time Source [TDUV Time Source] Parameter Number: 328,270,212,154,95. Access rule: Get/Set Data Type: BOOL Object Mapping: 0xB4-1-123 Group: Diagnostics Units: - Minimum Value: 0 = From IB Maximum Value: 1 = From IE Default Value: 0

This parameter allows the user to view and set the status of the TDUV Time Source. If this bit is a ‘0’ then the IB DIP switch setting is used as the TDUV Time Source. If this bit is a ‘1’ then the IE setting in DeviceLogix is used as the TDUV Time Source.

B-170 Parameters

1503-UM054D-EN-P – March 2015

Drop Out Time Source [Drop Out Time Source] Parameter Number: 329,271,213,155,96. Access rule: Get/Set Data Type: BOOL Object Mapping: 0xB4-1-124 Group: Diagnostics Units: - Minimum Value: 0 = From IB Maximum Value: 1 = From IE Default Value: 0 This parameter allows the user to view and set the status of the Drop Out Time Source. If this bit is a ‘0’ then the IB DIP switch setting is used as the Drop Out Time Source. If this bit is a ‘1’ then the IE setting is used as the Drop Out Time Source.

Contactor Coil Current for IB1 [IB 1 Contactor Coil Current] Parameter Number: 330,272,214,156,97. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-1-61 Group: Diagnostics Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the real time operating Coil Current for IB1. The current will be the Hold current for Electrically Held contactors, only, because the Close/Trip coils for Mechanically Latched contactors are only momentary currents and are not sustained for extended time periods. See “Coil Currents” in Chapter 4 for a more detailed description of this feature.

Parameters B-171

1503-UM054D-EN-P – March 2015

Contactor Coil Current for IB2 [IB 2 Contactor Coil Current] Parameter Number: 331,273,215,157,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-61 Group: Diagnostics Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the real time operating Coil Current for IB2. The current will be the Hold current for Electrically Held contactors, only, because the Close/Trip coils for Mechanically Latched contactors are only momentary currents and are not sustained for extended time periods. See “Coil Currents” in Chapter 4 for a more detailed description of this feature. Contactor Coil Current for IB3 [IB 3 Contactor Coil Current] Parameter Number: 332,274,216,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-61 Group: Diagnostics Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the real time operating Coil Current for IB3. The current will be the Hold current for Electrically Held contactors, only, because the Close/Trip coils for Mechanically Latched contactors are only momentary currents and are not sustained for extended time periods. See “Coil Currents” in Chapter 4 for a more detailed description of this feature.

B-172 Parameters

1503-UM054D-EN-P – March 2015

Contactor Coil Current for IB4 [IB 4 Contactor Coil Current] Parameter Number: 333,275,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-61 Group: Diagnostics Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999 A Default Value: 00.000A This parameter allows the user to view the real time operating Coil Current for IB4. The current will be the Hold current for Electrically Held contactors, only, because the Close/Trip coils for Mechanically Latched contactors are only momentary currents and are not sustained for extended time periods. See “Coil Currents” in Chapter 4 for a more detailed description of this feature.

Contactor Coil Current for IB5 [IB 5 Contactor Coil Current] Parameter Number: 334,_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-61 Group: Diagnostics Units: Amperes Minimum Value: 00.000A Maximum Value: 99.999A Default Value: 00.000A This parameter allows the user to view the real time operating Coil Current for IB5. The current will be the Hold current for Electrically Held contactors, only, because the Close/Trip coils for Mechanically Latched contactors are only momentary currents and are not sustained for extended time periods. See “Coil Currents” in Chapter 4 for a more detailed description of this feature.

Parameters B-173

1503-UM054D-EN-P – March 2015

Status Word for IB1 [IB 1 Status Word] Parameter Number: 335,276,217,158,98. Access rule: Get Data Type: WORD Object Mapping: 0x384-1-62 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IB1 Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present.



0 Bit 0: unused unused 1 Bit 1: unused unused 2 Bit 2: unused unused 3 Bit 3: Power Up with Contactors Closed Power Up with Contactor Closed IB1 4 Bit 4: Open Coil Open Trip Coil Open on IB1 5 Bit 5: Close Coil Open Close Coil Open on IB1 6 Bit 6: Power Up with Invalid DIPs Power Up with Invalid DIPs on IB1 7 Bit 7: MC Malfunction MC Malfunction on IB1 8 Bit 8: Drop Out During Hold Drop Out During Hold on IB1 9 Bit 9: Contactor Fails to Drop Out Contactor Fails to Drop Out on IB1 10 Bit 10: Power Up with Close Command Power Up with Close Command on IB1 11 Bit 11: Long Close Time Long Close Time on IB1 12 Bit 12: Undervoltage with Close Command Present Undervoltage with Close Command Present on IB1 13 Bit 13: Long Drop Out Time Long Drop Out Time on IB1 14 Bit 14: Mechanical Latch Trip Fail Mechanical Latch Trip Fail on IB1 15 Bit 15: Invalid Command Invalid Command on IB1

B-174 Parameters

1503-UM054D-EN-P – March 2015

Status Word for IB2 [IB 2 Status Word] Parameter Number: 336,277,218,159,_. Access rule: Get Data Type: WORD Object Mapping: 0x384-2-62 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IB2 Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present.




Parameters B-175

1503-UM054D-EN-P – March 2015

Status Word for IB3 [IB 3 Status Word] Parameter Number: 337,278,219,_,_. Access rule: Get Data Type: WORD Object Mapping: 0x384-3-62 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IB3 Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present.




B-176 Parameters

1503-UM054D-EN-P – March 2015

Status Word for IB4 [IB 4 Status Word] Parameter Number: 338,279,_,_,_. Access rule: Get Data Type: WORD Object Mapping: 0x384-4-62 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IB4 Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present.



0 Bit 0: unused unused 1 Bit 1: unused unused 2 Bit 2: unused unused 3 Bit 3: Power Up with Contactors Closed Power Up with Contactor Closed IB4 4 Bit 4: Open Coil Open Trip Coil Open on IB4 5 Bit 5: Close Coil Open Close Coil Open on IB4 6 Bit 6: Power Up with Invalid DIPs Power Up with Invalid DIPs on IB4 7 Bit 7: MC Malfunction MC Malfunction on IB4 8 Bit 8: Drop Out During Hold Drop Out During Hold on IB4 9 Bit 9: Contactor Fails to Drop Out Contactor Fails to Drop Out on IB4 10 Bit 10: Power Up with Close Command Power Up with Close Command on IB4 11 Bit 11: Long Close Time Long Close Time on IB4 12 Bit 12: Undervoltage with Close Command Present Undervoltage with Close Command Present on IB413 Bit 13: Long Drop Out Time Long Drop Out Time on IB4 14 Bit 14: Mechanical Latch Trip Fail Mechanical Latch Trip Fail on IB4 15 Bit 15: Invalid Command Invalid Command on IB4

Parameters B-177

1503-UM054D-EN-P – March 2015

Status Word for IB5 [IB 5 Status Word] Parameter Number: 339,_,_,_,_. Access rule: Get Data Type: WORD Object Mapping: 0x384-5-62 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IB5 Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present.




B-178 Parameters

1503-UM054D-EN-P – March 2015

Correct Termination Resistor Installed in MC System [Correct MC Termination Resistor] Parameter Number: 340,280,220,160,99. Access rule: Get Data Type: BOOL Object Mapping: 0x384-1-63 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the MC Termination Resistor installation. If this bit is ‘0’, then the correct MC Termination Resistor is not installed in the MC system. If this bit is ‘1’, then the correct MC Termination Resistor is installed in the MC system. For the MC system to have the correct Termination Resistor installed, only the last MC unit in the MC system must have its resistor turned on.

Termination Resistor Installed in IB2 [IB2 Termination Resistor] Parameter Number: 341,281,221,161,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-2-63 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the MC Termination Resistor installation on IB2. If this bit is ‘0’, then the MC Termination Resistor is not installed on the IB2 unit. If this bit is ‘1’, then the MC Termination Resistor is installed on the IB2 unit. For the MC system to have the correct Termination Resistor installed, only the last MC unit in the MC system must have its resistor turned on.

Parameters B-179

1503-UM054D-EN-P – March 2015

Termination Resistor Installed in IB3 [IB3 Termination Resistor] Parameter Number: 342,282,222,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-3-63 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the MC Termination Resistor installation on IB3. If this bit is ‘0’, then the MC Termination Resistor is not installed on the IB3 unit. If this bit is ‘1’, then the MC Termination Resistor is installed on the IB3 unit. For the MC system to have the correct Termination Resistor installed, only the last MC unit in the MC system must have its resistor turned on.

Termination Resistor Installed in IB4 [IB4 Termination Resistor] Parameter Number: 343,282,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-4-63 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the MC Termination Resistor installation on IB4. If this bit is ‘0’, then the MC Termination Resistor is not installed on the IB4 unit. If this bit is ‘1’, then the MC Termination Resistor is installed on the IB4 unit. For the MC system to have the correct Termination Resistor installed, only the last MC unit in the MC system must have its resistor turned on.

B-180 Parameters

1503-UM054D-EN-P – March 2015

Termination Resistor Installed in IB5 [IB5 Termination Resistor]

Parameter Number: 344,_,_,_,_. Access rule: Get Data Type: BOOL Object Mapping: 0x384-5-63 Group: Diagnostics Units: - Minimum Value: 0 = Not Present Maximum Value: 1 = Present Default Value: 0 This parameter allows the user to view the status of the MC Termination Resistor installation on IB5. If this bit is ‘0’, then the MC Termination Resistor is not installed on the IB5 unit. If this bit is ‘1’, then the MC Termination Resistor is installed on the IB5 unit. For the MC system to have the correct Termination Resistor installed, only the last MC unit in the MC system must have its resistor turned on.

Status Word for the IE [IE Status Word]

Parameter Number: 345,284,223,162,100. Access rule: Get/Set Data Type: WORD Object Mapping: 0xB4-1-128 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the IE Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present. See Table 4.F and Table 4.J in Chapter 4 for a detailed description of each of the IE Status Word bits.

Table B.44 – Status Word for IE


0 System locked System locked due to repeated fault1 Line under-voltage Line under-voltage 2 Line over-voltage Line over-voltage 3 Altitude setting warning Altitude settings inconsistent in MC system4 RTC failure RTC failure5 DNet power loss DeviceNet power loss 6 IB5 not responding IB5 not responding on RS485 7 IB4 not responding IB4 not responding on RS485 8 IB3 not responding IB3 not responding on RS485 9 IB2 not responding IB2 not responding on RS485

10 IB1 not responding IB1 not responding on RS485 11 unused unused12 RS485 incorrect address RS485 incorrect address 13 RS485 communication fault RS485 communication fault 14 unused unused15 unused unused

Parameters B-181

1503-UM054D-EN-P – March 2015

Status Word for the MC System [MC System Status] Parameter Number: 346,285,224,163,101. Access rule: Get/Set Data Type: WORD Object Mapping: 0xB4-1-127 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 0xFFFF Default Value: 0 This parameter allows the user to view the MC System Status Word. If a bit is ‘0’ then the fault or warning is not present. If a bit is a ‘1’ then the fault or warning is present. See Table 4.H in Chapter 4 for a detailed description of each of the MC System Status Word bits.

Table B.45 – Status Word for MC System


0 Aggregate warning status Aggregate warning status 1 Aggregate fault status Aggregate fault status 2 IE warning status IE warning status 3 IE fault status IE fault status 4 IB5 warning status IB5 warning status 5 IB5 fault status IB5 fault status 6 IB4 warning status IB4 warning status 7 IB4 fault status IB4 fault status 8 IB3 warning status IB3 warning status 9 IB3 fault status IB3 fault status 10 IB2 warning status IB2 warning status 11 IB2 fault status IB2 fault status 12 IB1 warning status IB1 warning status 13 IB1 fault status IB1 fault status 14 System running status System running status 15 System ready status System ready status

B-182 Parameters

1503-UM054D-EN-P – March 2015

MC System Ready Status [MC System Ready Status] Parameter Number: 347,286,225,164,102. Access rule: Get Data Type: BOOL Object Mapping: 0xB4-1-126 Group: Diagnostics Units: - Minimum Value: 0 = False Maximum Value: 1 = True Default Value: 0 This parameter allows the user to view the Ready Status of the MC System. If this bit is False then there is an MC System fault or warning present. If this bit is True, then there is no MC System fault or warning present. See Table 4.H in Chapter 4 for a detailed description of each of the MC System Status Word bits. MC System Running Status [MC System Running Status] Parameter Number: 348,287,226,165,103. Access rule: Get Data Type: BOOL Object Mapping: 0xB4-1-129 Group: Diagnostics Units: - Minimum Value: 0 = False Maximum Value: 1 = True Default Value: 0 This parameter allows the user to view the Running Status of the MC System. If this bit is False then the MC System is not running. If this bit is True, then the MC System is running. See Table 4.H in Chapter 4 for a detailed description of each of the MC System Status Word bits.

Parameters B-183

1503-UM054D-EN-P – March 2015

MC System Locked [MC System Locked] Parameter Number: 349,288,227,166,104. Access rule: Get Data Type: SINT Object Mapping: 0xB4-1-130 Group: Diagnostics Units: - Minimum Value: 0 Maximum Value: 1 Default Value: 0 This parameter allows the user to view the status of the MC System Locked state. If a bit is a ‘1’ then the fault or warning is present. If a bit is a ‘1’ then the fault or warning is present. See Table 4.J in Chapter 4 for a detailed description of the MC System Locked feature.

Table B.46 – MC System Locked Operation


0 Normal Normal operation – no faults/warnings on IB/IE/MC 1 Warning Warning(s) present on IB/IE/MC 2 Fault Fault(s) present on IB/IE/MC 3 Locked MC system in a locked state

Reset All Faults [Reset All Faults] Parameter Number: 350,289,228,167,105. Access rule: Get/Set Data Type: BOOL Object Mapping: 0xB4-1-131 Group: Diagnostics Units: - Minimum Value: 0 = No Operation Maximum Value: 1 = Reset Default Value: 0 This parameter allows the user to view as well as to Reset all Faults. If this bit is ‘0’, then No Operation is performed. If this bit is ‘1’, then a Reset operation is performed on all faults. If a fault is still present then it will re-occur as soon as the Reset operation is performed. See Reset in Chapter 4 for a detailed description of the Reset operation.

B-184 Parameters

1503-UM054D-EN-P – March 2015

IB1 Firmware Version [IB1 Firmware Version] Parameter Number: 351,290,229,168,106. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-1-64 Group: Diagnostics Units: - Minimum Value: 0.00 Maximum Value: 3.17 Default Value: 0.01 This parameter allows the user to view the Version of the Firmware in IB1. See IE/IB Firmware Revisions in Chapter 8 for a detailed description of the format for the Firmware Version. IB2 Firmware Version [IB2 Firmware Version] Parameter Number: 352,291,230,169,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-2-64 Group: Diagnostics Units: - Minimum Value: 0.00 Maximum Value: 3.17 Default Value: 0.01 This parameter allows the user to view the Version of the Firmware in IB2. See IE/IB Firmware Revisions in Chapter 8 for a detailed description of the format for the Firmware Version.

IB3 Firmware Version [IB3 Firmware Version] Parameter Number: 353,292,231,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-3-64 Group: Diagnostics Units: - Minimum Value: 0.00 Maximum Value: 3.17 Default Value: 0.01 This parameter allows the user to view the Version of the Firmware in IB3. See IE/IB Firmware Revisions in Chapter 8 for a detailed description of the format for the Firmware Version.

Parameters B-185

1503-UM054D-EN-P – March 2015

IB4 Firmware Version [IB4 Firmware Version] Parameter Number: 354,293,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-4-64 Group: Diagnostics Units: - Minimum Value: 0.00 Maximum Value: 3.17 Default Value: 0.01 This parameter allows the user to view the Version of the Firmware in IB4. See IE/IB Firmware Revisions in Chapter 8 for a detailed description of the format for the Firmware Version.

IB5 Firmware Version [IB5 Firmware Version] Parameter Number: 355,_,_,_,_. Access rule: Get Data Type: FLOAT Object Mapping: 0x384-5-64 Group: Diagnostics Units: - Minimum Value: 0.00 Maximum Value: 3.17 Default Value: 0.01 This parameter allows the user to view the Version of the Firmware in IB5. See IE/IB Firmware Revisions in Chapter 8 for a detailed description of the format for the Firmware Version.

B-186 Parameters

1503-UM054D-EN-P – March 2015

Appendix C

1503-UM054D-EN-P – March 2015

Maintenance

Introduction The IntelliVAC Plus product has is a very robust device which contains only two user serviceable parts. These parts are:

the fuse for the mains input line and

the battery used by the Real Time Clock (RTC) circuitry.

Main Input Fuse This fuse is designed to protect the IntelliVAC Plus unit in the event of the failure of a contactor coil or failure of an internal electronic component. If power is applied to the mains input at TB1-2 and the unit does not respond then the problem may be that the input fuse has failed.


A properly grounded anti-static strap should be used at this point.

Begin by removing power to the IntelliVAC unit. To change the fuse (see Fig C.1 below), remove the two screws on the front of the case and then remove the front section of the enclosure. Next, remove the three screws that hold the IE circuit board to the IB circuit board. Carefully remove the IE circuit board (note that there is a 16 pin connector between the two boards) and place it on a static free surface. Now remove the fuse on the lower right side of the IB module and replace it with a new fuse (see Spare Parts list in Appendix C).

Fuse

Figure C.1 – Fuse Location

C-2 Maintenance

1503-UM054D-EN-P – March 2015


The cause of the fuse failure should be identified before the fuse is replaced otherwise it may fail again once the IntelliVAC Plus module is powered up.

RTC Battery The RTC battery should have a lifetime of at least 10 years so that its replacement should not be necessary. However, if the RTC should show to not be operating correctly and resetting the date/time through RSNetworx does not function correctly, then the battery may be in need of changing.


A properly grounded anti-static strap should be used at this point.

Begin by removing power to the IntelliVAC unit. To change the RTC battery (see Fig C.2 below), remove the two screws on the front of the case and then remove the front section of the enclosure. Next, remove the three screws that hold the IE circuit board to the IB circuit board. Carefully remove the IE circuit board (note that there is a 16 pin connector between the two boards) and place it on a static free surface. Flip the IE board with the 16 pin connector facing upwards and remove the battery from its socket and replace it with a new battery (see Spare Parts list in Appendix C).

Battery Holder

Figure C.2 – Battery Location on Circuit Board

Appendix D

1503-UM054D-EN-P – March 2015

Spare Parts

Table D.1 – Spare Parts

Item Description Part Number

Internal Fuse 6.3A, 250V (Littlefuse 21506.3) 80174-902-14-R

Internal Battery 3V, 195 mAh (RAYOVAC BR2032) 24011-019-01-R

D-2 Spare Parts

1503-UM054D-EN-P – March 2015

Appendix E

1503-UM054D-EN-P – March 2015

DeviceNet Information

Identify Object

Table E.1 - Class Attributes

Attribute ID Access

Rule Name

DeviceNet Data Type

Data Value

1 Get Revision UINT 1.0 2 Get Max Instance UINT 1

Only valid when flash instance is supported.

Number of Instances: 1

Table E.2 – Instance Attributes

Attribute ID Access

Rule Name

DeviceNet Data Type

Data Value

1 Get Vendor ID UINT 1= RA 2 Get Device Type UINT 115=Rockwell Misc. 3 Get Product Code UINT 263=4010P1 option

264=4010P2 option 265=4010P3 option 266=4010P4 option 267=4010P5 option

4 Get Revision STRUCT of: Major Revision USINT 1 Minor Revision USINT 0

5 Get Status WORD Device status* 6 Get Serial Number UDINT Unique 32 bit number 7 Get Product Name

String length ASCII string

Structure of: USINT STRING [9]

21 “IntelliVAC Plus w/ 1IB” ~ “IntelliVAC Plus w/ 5IB”

8 Get state USINT 0 = Nonexistent 1 = Device Self Testing 2 = Standby 3 = Operational 4 = Major Recoverable Fault 5 = Major Unrecoverable Fault

9 Get Configuration Consistency value

UINT Unite value depending on output of the parameter checksum algorithm

10 Get/Set Heartbeat USING 0~255 (second)

E-2 DeviceNet Information

1503-UM054D-EN-P – March 2015

Table E.3 – Device Status

Bit No. Status Data Value

Bit 0 Owned 0=not owned1=owned (Group 2 allocated to master)

Bit 1 Reserved Always 0Bit 2 Configured 0= not configured

1=configured Bit 3 Reserved Always 0Bit 4-7 Vendor specific All 0Bit 8 Minor cfg fault 0=no fault

1=minor configuration fault Bit 9 Minor device fault 0=no fault

1=minor device fault Bit 10 Major cfg fault 0=no fault

1=major configuration fault Bit 11 Major device fault 0=no fault

1=major device fault Bit 12,13 Reserved Always 0Bit 14,15 Reserved Always 0

Note: The code build number is for internal reference only;

there shall be a corresponding frozen code package.

Table E.4 - Common Services

Service Code

Implementation for Service Name Description of Service

Class Instance

0E hex Yes Yes Get_Attribute_Single Returns the contents of the specified attribute.

10 hex No Yes Set_Attribute_Single Set the heartbeat value.05 hex No Yes Reset Invokes the Reset service

for the device.

DeviceNet Object


Attribute ID Access

Rule Name

DeviceNet Data Type

Data Value

1 Get Revision UINT 2


DeviceNet Information E-3

1503-UM054D-EN-P – March 2015


Attribute ID Access Rule Name DeviceNet Data Type

Data Value

1 Get/Set Node Address USINT 0…632 Get/Set Baud Rate USINT 0=125 K

1=250 K 2=500 K

5 Get/Special Allocation Information Allocation Byte Master’s Node Address

Structure of: BYTE USINT

Allocation byte* 63=master address 255=unallocated

6 Get/Set* Switch value changed, when set shall return NOT SETTABLE

BOOL 0=not changed1=changed

8 Get MAC_ID switch value USINT 0…63100 Get DeviceNet voltage USINT 0-24 101 Get IE power supply voltage USINT 0-15 102 Get Power selector BOOL 0=power from

DeviceNet 1=power from IB

103 Get Node address source BOOL 0= Rotary Switch1=DeviceNet

Table E.7 - Allocation Byte

Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0

N/a Ack_sup Cyclic COS N/a Strobe Poll Explicit

Note: Bit 3 is reserved for Multi cast poll


Service Code Implementation for

Service Name Class Instance

0E hex Yes Yes Get_Attribute_Single 10 hex No Yes Set_Attribute_Single 4Bhex No Yes Allocate_master/Slave_Connection_Set 4Chex No Yes Release_Master/Slave_Connection_Set


1503-UM054D-EN-P – March 2015

Explicit Connection

Table E.9 - Instance Attributes (predefined slave explicit connection)

Attribute ID

Access Rule Attribute Name

Data Type Data Value

1 Get state USINT 0=nonexistent 1=configured 3=established 4=time out

2 Get instance_type USINT 0=explicit message 3 Get transportClass_trigger BYTE 83hex, server, transport

class 3 4 Get produced_connection_id

CAN header field 11 bit message UINT 10xxxxxx011

xxxxxx=node address

5 Get consumed_connection_id CAN header field 11 bit message

UINT 10xxxxxx100 xxxxxx=node address

6 Get initial_comm._characteristics USINT 21hex 2=slave’s explicit message (produce, source) 1=master’s explicit request (consume, destination)

7 Get produced_connection_size UINT Max. 132 8 Get consumed_connection_size UINT Max. 132 9 Get/Set expected_packet_rate UINT 2500 ms (default), with

timer resolution of 10 ms 12 Get/Set watchdog_timeout_action USINT 1=auto delete

3=defer delete 13 Get produced_connection_path_length USINT 0 14 Get produced_connction_path EPATH Null 15 Get consumed_connection_path_length UINT 0 16 Get consumed_conection_path EPATH Null


1503-UM054D-EN-P – March 2015

Parameter Object

The parameter object and parameter object are all for mainly for 193-HIM to get online parameters.


Attribute ID

Access Rule

Name DeviceNet Data Type Data Value


2 Get Max instance UINT 24

8 Get Parameter Class Descriptor

WORD 0b Bit 0: Supports Parameter

Instances Bit 1: Supports Full Attributes Bit 2: Must do non-volatile

storage save command Bit 3: Params are stored in Non-

Volatile storage 9 Get Configuration

Assembly Instance

UINT 0

There is a set of instances reserved for IE plus module. The following instance attributes are implemented for all parameter attributes:

Table E.11 - Class Instances

Attribute ID

Access Rule

Attribute Name Data Type

1 Get/Set Value Specified in descriptor 2 Get Link path size USINT3 Get Link path Array of:

Byte EPATH

4 Get Descriptor WORD5 Get Data type EPATH6 Get Data size USINT7 Get Parameter name string Short string8 Get Unit string Short string9 Get Help string Short string10 Get Min value Specified in descriptor 11 Get Max value Specified in descriptor 12 Get Default value Specified in descriptor 13 Get Scaling multiplier UINT14 Get Scaling divisor UINT15 Get Scaling base UINT16 Get Scaling offset INT17 Get Multiplier Link UINT18 Get Divisor Link UINT19 Get Base Link UINT20 Get Offset Link UINT21 Get Decimal Precision USINT


1503-UM054D-EN-P – March 2015

Common Service

Table E.12 - Service Codes



0E hex Yes Yes Get_Attribute_Single 10 hex No Yes Set_Attribute_Single 0x01 No Yes Get_Attribute_All 0x4B No Yes Get_Enum_String

Here is the list of parameters with detail attribute values:

Table E.13 – Parameters with Detailed Attribute Values

Idx Group Name Parameter Index in this Group

1 Control IE Hardware input IE Hardware output Preload DLX program index Logic Mask DOP fault action DOP fault value DOP idle action DOP idle value Network input Network output Run status Ready Status

2 Communication Auto baud rate enable Produce assembly number Consumed assembly number Reset to default Produced size Consumed size Network output COS mask IE Status COS mask

3 Configuration Network override Communication override Time zone TDUV time source Drop out time source Communication loss action Reset Faults Altitude MC system locked

4 Diagnostic IE status word MC status word IB1~IB65 status word


1503-UM054D-EN-P – March 2015

Output (Consumed) Assembly and Layout

Output assembly instances attribute and format (produced by DeviceNet Master, consumed by IE)

IB OutA=close coil command

IB OutB=open coil command

Table E.14 – Output (Consumed) Assembly Instance – Commands Instance 1, 3 bytes

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 --- --- --- --- --- --- IE-Out B IE-Out A 1 CNB7 CNB6 CNB5 CNB4 CNB3 CNB2 CNB1 CNB0 2 CNB15

/Net Jog CNB14

/Net REV CNB13

/Net FWD CNB12

/Net Stop CNB11

/Net Start CNB10 CNB9 CNB8

Table E.15 – Output (Consumed) Assembly Instance – Outputs Instance 2, 1 byte


0 --- --- --- --- --- --- IE-Out B IE-Out A

Table E.16 – Output (Consumed) Assembly Instance – Commands Instance 3, 2 bytes


0 CNB7 CNB6 CNB5 CNB4 CNB3 CNB2 CNB1 CNB0 1 CNB15

/Net Jog CNB14

/Net REV CNB13

/Net FWD CNB12

/Net Stop CNB11



1503-UM054D-EN-P – March 2015

Input (Produced) Assembly and Layout

Table E.17 – Input assembly instances attribute and format (produced by EI, consumed by DeviceNet Master)

Instance 10, 7 bytes


0 IE-Input7 IE-Input6 IE-Input5 IE-Input4 IE-Input3 IE-Input2 IE-Input1 IE-Input01 IB3-Input1 IB3-Input0 IB2-Input2 IB2-Input1 IB2-Input0 IB1-Input2 IB1-Input1 IB1-Input02 --- IB5-Input2 IB5-Input1 IB5-Input0 IB4-Input2 IB3-Input1 IB4-Input0 IB3-Input23 PNB7

/Interim 5 PNB6

/Interim 4 PNB5

/Interim 3 PNB4

/Interim 2 PNB3

/Interim 1 PNB2 PNB1

PNB0

/Reset All Faults

4 PNB15 /Test

mode status

PNB14 /Normal

mode status

PNB13/Local mode

status

PNB12/Remote

mode status

PNB11/Isolation

SW status

PNB10 /Speed SW REV status

PNB9 /Speed SW FWD status

PNB8/Protection

Status 5 PNB23

/IB4-OutB PNB22

/IB4-OutA PNB21

/IB3-OutB PNB20

/IB3-OutA PNB19

/IB2-OutB PNB18

/IB2-OutA PNB17

/IB1-OutB PNB16

/IB1-OutA

6 PNB31 /Jog

PNB30 /REV

PNB29/FWD

PNB28/Stop

PNB27/Start

PNB26 /Stop status

PNB25 /IB5-OutB

PNB24/IB5-OutA

Table E.18 – Input assembly instances attribute and format (produced by EI, consumed by DeviceNet Master) Instance 11, 1 byte


0 IE-Input7 IE-Input6 IE-Input5 IE-Input4 IE-Input3 IE-Input2 IE-Input1 IE-Input0

Table E.19 – Input assembly instances attribute and format (produced by EI, consumed by DeviceNet Master) Instance 12, 4 bytes


0 PNB7 /Interim tag 5

PNB6 /Interim tag 4

PNB5/Interim tag 3

PNB4/Interim tag 2

PNB3/Interim tag 1

PNB2 PNB1 /Reset

Warning

PNB0/Reset All

1 PNB15 /Test mode status

PNB14 /Normal mode status

PNB13/Local mode status

PNB12/Remote

mode status

PNB11/Isolation SW status

PNB10 /Speed SW REV status

PNB9 /Speed SW

FWD status

PNB8/Protection

Status

2 PNB23 /IB4-OutB

PNB22 /IB4-OutA

PNB21/IB3-OutB

PNB20/IB3-OutA

PNB19/IB2-OutB

PNB18 /IB2-OutA

PNB17 /IB1-OutB

PNB16/IB1-OutA

3 PNB31 /Jog

PNB30 /REV

PNB29/FWD

PNB28/Stop

PNB27/Start

PNB26 /Stop status

PNB25 /IB5-OutB

PNB24/IB5-OutA

Table E.20 – Input assembly instances attribute and format (produced by EI, consumed by DeviceNet Master)

Instance 13, 4 bytes


0 IE-Input7 IE-Input6 IE-Input5 IE-Input4 IE-Input3 IE-Input2 IE-Input1 IE-Input01 IB3-Input1 IB3-Input0 IB2-Input2 IB2-Input1 IB2-Input0 IB1-Input2 IB1-Input1 IB1-Input02 --- IB5-Input2 IB5-Input1 IB5-Input0 IB4-Input2 IB3-Input1 IB4-Input0 IB3-Input2

3 --- --- --- --- --- --- --- ---


1503-UM054D-EN-P – March 2015

Important Notes:

*About PNBnn/IBx-Outy: this is IntelliVAC assembly’s unique feature: some produced network bits are used in 2 purposes, depends on the control mask and if there is DeviceLogix program:

If the control mask is mask local or mask network, these bits are normal PNB

If mask DeviceLogix and there is no DeviceLogix program, they are normal produced network data, when there is DeviceLogix program, they (the 10 IB-Out) are DeviceLogix result (same as same name in Consumed assembly) as long as they are bound, and the result will be applied to corresponding IB and feedback to CNB

** About PNBnn/network command: this is IntelliVAC assembly’s unique feature: the 5 network command (Jog, Rev, Fwd, Stop, Start) bits are used in 2 purpose, when they are not bound in DeviceLogix program, they are normal produced network data, when bound then they are DeviceLogix result (same as same name in Produced assembly) and will be applied to corresponding Consumed network bits.

*** About PNBnn/xxxStatus in Instance 10, byte4: they are status setting, which is used as DeviceLogix output, their value also could be referenced as input in DeviceLogix Status Input bits.

**** About Interim bits: this is IntelliVAC assembly’s unique feature: the 5 interim bits are used in DeviceLogix program and will be referenced as status bit, see Figure E.1.

Figure E.1 – Use of Interim Bit

DNI (IE) Object

Table E.21 – Class Attributes

Attribute ID

Access Rule Name DeviceNet Data Type Data Value




1503-UM054D-EN-P – March 2015


Attribute ID

Access Rule Attribute Name Data Type Default Value

Range

15 Get/Set Autobaud Enable BOOL 1 0=disabled1=enabled

16 Get/Set Consumed Assy USINT 10 1~3 17 Get/Set Produced Assy USINT 1 10 ~ 13 19 Get/Set Set To Defaults BOOL 0 0=no action

1=reset 23 Get I/O Produced Size USINT 8 1~8 24 Get I/O Consumed Size USINT 5 1~5 64 Get/Set Flash instance enable UINT 0 110 Get/Set PNB COS Mask DWORD 0 0 … 0xFFFFFFFF111 Get/Set Status COS Mask *** DWORD 0 0 … 0xFFFFFFFF112 Get/Set RTC Date Date 0 1972-1-1 ~ 2151-6-6113 Get/Set RTC Time Time 0 00:00:00.000

~ 23:59:59.999

114 Get/Set Preload DeviceLogix program index

USINT 0 0~5

115 Get Invalid DLX Program USINT 0/1 0=invalid 1=valid

116 Get Altitude USINT 0 0: -1000~0000 M 1: 0001~1000 M 2: 1001~2000 M 3: 2001~3000 M 4: 3001~4000 M 5: 4001~5000 M

117 Get/Set Time Zone USINT 0 0~31 represent GMT-12 ~ GMT+13 Hrs

118 Get/Set Control Mask* USINT 0-3 0=local 1=network 2=user customized priority

119 Get/Set Network command (Start, stop, FWD, REV, Jog)

BYTE 0 Xxx00000- xxx11111

120 Get Module Status1: Test_Mode 2: Normal_Mode 3: Local_Mode 4: Remote_Mode 5: Isolation_SW 6: Speed_REV 7: Speed_FWD 8: Protection

BYTE 0 0-FF

121 Get IB1 Status BOOL 0 0=bad, IB power lost1=good, IB power On

122 Get MC altitude set warning BOOL 0 1=Altitude Inconsistent0=Not Fault

123 Get/Set TDUV Time Source BOOL 0 0=from IB1=from IE

124 Get/Set Drop Out Time Source BOOL 0 0=from IB1=from IE


1503-UM054D-EN-P – March 2015

Table E.22 – Instance Attributes (cont.)

Attribute ID

Access Rule Attribute Name Data Type Default Value

Range

125 Get/Set Communication Loss Action BOOL 0 0=Hold 1=RESET detail

126 Get Ready Status BOOL 0 0=FALSE1=TRUE

127 Get/Set MC System Status UINT 0 128 Get/Set IE status word UINT 0 129 Get Running status BOOL 0 0=FALSE

1=TRUE

130 Get System locked BOOL 0 0=not active1=active

131 Get/Set Reset All BOOL 0 0=no action1=reset all fault and warning

Note *:

1. The Setting of Mask is only could be done in specific condition.

The setting of Customize priority is only could be done in specific condition if Mask=2

Note**: some bits are set to clear fault/warning

Note***: the status is: Byte 0, IE inputs, assembly 10, byte 0

Byte 1~2: IB inputs, assembly 10, byte 5~6

Byte 3; Status, assembly 10, byte 4




0E hex Yes Yes Get_Attribute_Single 10 hex No Yes Set_Attribute_Single

IntelliVAC Base Module Object

This is a vendor specific class defined for IntelliVAC base module.


Attribute ID Access Rule Name DeviceNet Data Type

Data Value

1 Get Revision UINT 1 2 Get Max instance UINT 1~5, depends on the product option

Number of Instances: 1~5, depends on the IB number


1503-UM054D-EN-P – March 2015

Table E.25 - Instance Attribute

Parameter No.

Control Parameter Access

Rule Type Description NV CCV

1 AUX Status Get BOOL 1=open 0=close

N N

2 CLOSE Status Get BOOL 0=not present 1=present

N N

3 OPEN Status Get BOOL 0=not present 1=present

N N

4 Close Coil Command Get/Set BOOL 1=Open 0=Close

N N

5 Trip Coil Command Get/Set BOOL 1=Close 0=Open

N N

6 Contactor Relay Status Get BOOL 0=open 1=close

N N

7 Module Relay Status Get BOOL 0=open 1=close

N N

8 Close Current Get LONG INT* 0~xx.xxx A N N9 Hold Current Get LONG INT* 0~xx.xxx A N N

10 Trip Current Get LONG INT* 0~xx.xxx A N N11 Line Voltage Get LONG INT* 0~xx.xxx V N N12 DC Bus Voltage Get LONG INT* 0~xx.xxx V N N13 Drop-out Time

(from IB or IE) Get/Set USINT 50~240 ms Y Y

14 Contactor Type (from IB) Get USINT 0=400A Mech. Latch 1=400A Elec. Held 2=800A Mech. Latch 3=800A Elec. Held 4~F=TBD

N N

15 TDUV Config (from IB) Get/Set BOOL 0=disable 1=enable

Y Y

16 Power-up Safety (from IB or IE) Get BOOL 0=enable 1=disable

N N

17 Learn Mode (from IB) Get BOOL 0=Off 1=On

N N

18 Pick-up Time Get USINT 0~255 ms N N19 Delay Restart Time Get/Set UINT 6(12) ~ 3600 Sec Y Y20 Delay Restart Wait Time Get UINT 0 ~ 3600 Sec N N21 Jog Time Get/Set USINT 0 ~ 30 Sec, default

12 Y Y

22 Jog Repetition Time Get/Set UINT* 0 ~ 60 second, default 6

Y Y

23 IB Invalid Command Get BOOL 0=not present 1=present

N N

24 IB Mechanical Latch Fail to Trip Get BOOL 0=not present 1=present

N N

25 Contactor Fails to Pick-Up Get BOOL 0=not present 1=present

N N

26 Contactor Drop-out during Hold Get BOOL 0=not present 1=present

N N

27 Contactor Fails To Drop Out Get BOOL 0=not present 1=present

N N

28 IB Module Not Healthy Get BOOL 0=not healthy 1=healthy

N N

29 Power-up with Contactor Closed Get BOOL 0=not present 1=present

N N

30 Power-up with Invalid DIP Switch Configuration

Get BOOL 0=not present 1=present

N N


1503-UM054D-EN-P – March 2015

Table E.25 - Instance Attribute (cont.)

Parameter No.



31 U/V with Close Command Present


N N

32 Master Counter (Operations) Get UDINT 0~16777215 Y N33 Reset Operations Since

Counter Get/Set BOOL 0/1 Y N

34** Operations Event (count value) Get UDINT 0~16777215 Y N35** Operations Event Since

(Date) Get Date YYYY-MM-DD Y N

36** Operations Event Since(Time)

Get Time HH-MM-SS.xxx Y N

37** Operations Since-1 Event (count value)

Get UDINT 0~16777215 Y N

38** Operations Event Since-1 (Date)

Get Date YYYY-MM-DD Y N

39** Operations Event Since-1 (Time)


40** Operations Since-2 Event (count value)

Get UDINT 0~16777215 Y N

41** Operations Event Since-2 (Date)

Get Date YYYY-MM-DD Y N

42** Operations Event Since-2(Time)


43 Average Operations per Time Unit

Get/Set USINT 0=Hour 1=Day 2=Week

Y N

44 Average Operations counter Get UDINT 0~16777215 Y N45 Line Undervoltage Close Get BOOL 0=not present

1=present N N

46 Line Overvoltage Get BOOL 0=not present 1=present

N N

47 Power Loss Get BOOL 0=not present 1=present

N N

48 Main Coil Open Get BOOL 0=not present 1=present

N N

49 Drop out time(from IB DIP) Get USINT 50/75/100/130/150/ 175/200/240

N N

50 TDUV Time Get/Set USINT* 0.2 ~ 2.00 N N51 Event Max Length Get SINT 100~500, depends on

the product option. N N

52 Event log present length Get USINT 0-500, depends on the product option.

Y N

53 Specific Event data Get Member

Struct ofUSINT USINT DATE

Time of Day

8 bytes Event Code Evnet Fault byte Date Time

Y N

54 Long Close Time Get BOOL 0=not present 1=present

N N

55 Extended Pick up Time Get BOOL 0=not present 1=present

N N

56 IB Contactor Not Healthy Get BOOL 0=not present 1=present

N N

57 Trip coil open Get BOOL 0=not present 1=present

N N


1503-UM054D-EN-P – March 2015

Table E.25 - Instance Attribute (cont.)

Parameter No.



58 TDUV base Time (from DIP)* Get USINT 0.2/0.5/1.0/2.0 N N59 Line Undervoltage Hold Get BOOL 0=not present

1=present N N

60 Contactor Long Drop Out Time Get BOOL 0=not present 1=present

N N

61 Coil Current trend*** Get LONG INT* 0~xx.xxx A N N62 IB module status**** Get/Set UINT N N63 Correct MC Termination

resistor@ Ibx Termination resistor


N N

64 IB revision Get LONG INT* XX.XX N N

Note*: In EDS its decimal position is 2, scaling to engineering unit, i.e, the data 100 will be scale to 1.00 in RSNetWorx parameter page.

Note**: These parameters keep the 3 latest events

Note***: The current trend is for electrically held contactor only, which provide a way for the IntelliCENTER software to display the current trend of contactor’s close transition state, this parameter will not be displayed in RSNetWorx’ parameter page.

Note****: Some bits are set to clear fault/warning.

Note: For IB1 this is correct MC termination resistor, for IB 2~5 this is IBx termination resistor.


Service Code

Implementation for Service Name

Class Instance 0E hex Yes Yes Get_Attribute_Single 10 hex No Yes Set_Attribute_Single 18hex No Yes Get_Member*

Note*: Only used for get the event log member.


1503-UM054D-EN-P – March 2015

PCP Object (Motor Control Center Object)

Class Attributes: None


Table E.27 – Instance Attribute

Attribute ID

Access Rule

Name Data Type Data Value

NV/CCV

1 Get/Set MCC number USINT 0 to 255 Y 2 Get/Set Vertical section number USINT 0 to 255 Y 3 Get/Set Starting section letter USINT 0 to 255 Y 4 Get/Set Space factor USINT 0 to 63 Y 5 Get/Set Cabinet width USINT 0 to 255 Y 6 Get/Set Controlled device USINT 0 to 255 Y 7 Get Number of device inputs USINT 8 Y 8 Get/Set Devices connected at input Array of USINT - Y 9 Get Number of device outputs Array of USINT 2 Y

10 Get/Set Device connected at outputs Array of USINT - Y

Table E.28 – Common Services



0E hex No Yes Get_Attribute_Single 10 hex No Yes Set_Attribute_Single 18 hex No Yes Get member 19 hex No Yes Set member


1503-UM054D-EN-P – March 2015

Data Table Layout

Table E.29 shows the data table layout.

Table E.29 – DeviceLogix Data Table Layout


NUMBER_OF_HARDWARE_OUTPUTS_BYTES (O~7) = 1 byte Byte 0 --- --- --- --- --- --- OutB OutA

NUMBER_OF_HARDWARE_INPUT_BYTES (8~f) =1 byte Byte 1 IE-In7 IE-IN6 IE-In5 IE-In4 IE-In3 IE-In2 IE-In1 IE-In0

NUMBER_OF_CONSUMED_NETWORK BYTES (10~1F) = 1 byte Byte 2 CNB7 CNB6 CNB5 CNB4 CNB3 CNB2 CNB1 CNB0Byte 3 CNB15

/Net Jog CNB14

/Net REV CNB13

/Net FWD CNB12

/Net Stop CNB11


NUMBER_OF_PRODUCED_NETWORK_BYTES (20~3F) = 4 bytes Byte 4 PNB7

/Interim 5 PNB6

/Interim 4 PNB5

/Interim 3 PNB4

/Interim 2 PNB3

/Interim 1 PNB2 PNB1 PNB0

/Reset All FaultByte 5 PNB15

/Test mode status

PNB14 /Normal

mode status

PNB13/Local mode

status

PNB12/Remote

mode status

PNB11/Isolation

status

PNB10/Speed SW REV status

PNB9 /Speed SW FWD status

PNB8/protection

status Byte 6 PNB23

/IB4-OutB PNB22

/IB4-OutA PNB21

/IB3-OutB PNB20

/IB3-OutA PNB19

/IB2-OutB PNB18

/IB2-OutA PNB17

/IB1-OutB PNB16

/IB1-OutA Byte 7 PNB31

/Jog tag PNB30

/REV tag PNB29

/FWD tag PNB28

/Stop tag PNB27

/Start tag PNB26

/Stop status tag

PNB25 /IB5-OutB

PNB24/IB5-OutA

NUMBER_OF_MISCELLANEOUS_BYTES (40~77) = 7 bytes Byte 8 IB3-In1 IB3-In0 IB2-In2 IB2-In1 IB2-In0 IB1-In2 IB1-In1 IB1-In0Byte 9 Stop Status IB5-In2 IB5-In1 IB5-In0 IB4-In2 IB4-In1 IB4-In0 IB3-In2Byte 10 Start Ready

Status* Interim 2 Interim 1 IO_CONXN_

IDLE IO_CONXN_

FLT IO_CONXN_

OK EXP_CONXN_

FLT EXP_CONXN_

OK Byte 11 Interim 5 Interim 4 Interim 3 Jog REV FWD Stop StartByte 12 Test mode

status Normal

mode status Local mode

status Remote

mode status Isolation SW

status Speed SW REV status

Speed SW FWD status

Protection status

Byte 13 IB4 OutB IB3 OutA IB3 OutB IB3 OutA IB2 OutB IB2 OutA IB1 OutB IB1 OutAByte 14 --- --- --- --- --- Fault

Status** IB5 Out B IB5 OutA

NUMBER_OF_FUNCTION_BLOCK_OUTPUT_BYTES (78~C7) = 10 bytes Byte 15 FB7 FB6 FB5 FB4 FB3 FB2 FB1 FB0Byte 16 FB15 FB14 FB13 FB12 FB11 FB10 FB9 FB8Byte 17 FB23 FB22 FB21 FB20 FB19 FB18 FB17 FB16Byte 18 FB31 FB30 FB29 FB28 FB27 FB26 FB25 FB24Byte 19 FB39 FB38 FB37 FB36 FB35 FB34 FB33 FB32Byte 20 FB47 FB46 FB45 FB44 FB43 FB42 FB41 FB40

NUMBER_OF_FUNCTION_BLOCK_OUTPUT_BYTES (78~C7) = 10 bytes Byte 21 FB55 FB54 FB53 FB52 FB51 FB50 FB49 FB48Byte 22 FB63 FB62 FB61 FB60 FB59 FB58 FB57 FB56Byte 23 FB71 FB70 FB69 FB68 FB67 FB66 FB65 FB64Byte 24 FB79 FB78 FB77 FB76 FB75 FB74 FB73 FB72


1503-UM054D-EN-P – March 2015

Table E.29 – DeviceLogix Data Table Layout (cont.)


NUMBER_OF_HARDWARE_INPUT_FAULT_BYTES (C8-FE) = 7 bytes Byte 25 IB1– Long

contactor drop out time

IB1 – Contactor drop out during hold

IB1 –Contactor fails to pick up

IB1 – Power up with contactor close (EH only)

IB1–Mechanical Latch Fail to Trip

IB1– Invalid Command Present

IB1 – Healthy Module & Contactor close

IB1 – Healthy Module & Contactor open

Byte 26 IB2– Power up with contactor close (EH only)

IB2 – Mechanical Latch Fail to Trip

IB2 –Invalid Command Present

IB2 – Healthy Module & Contactor Close

IB2 – Healthy Module & Contactor Open

IB1 –Undervoltage with close command present

IB1 – Power up w/ Invalid DIP Config.

IB1 – CPU Malfunction

Byte 27 IB3 – Healthy Module & Contactor Close

IB3 – Healthy Module & Contactor Open

IB2 – Undervoltage with close command present



IB2 – Long contactor drop out time

IB2 – Contactor drop out during hold

IB2 – Contactor fails to pick up

Byte 28 IB3 – Power up w/ Invalid DIP Config.



IB3 –Contactor Drop Out during hold

IB3 –Contactor fails to pick up

IB3 – Power up with Contactor close (EH only)

IB3 – Mechanical Latch Fail to Trip

IB3 – Invalid Command Present

Byte 29 IB4 – Contactor drop out during hold


IB4 – Power up with contactor close (EH only)

IB4 –Mechanical Latch fail to trip


IB4 – Healthy Module & Contactor Close



Byte 30 IB5 – Mechanical Latch Fail to Rip


IB5 – Healthy Module & Contactor close





IB4 –- Long contactor drop out time

Byte 31 XXX This bit can not be used

IB5 – Undervoltage with close command present






IB5 – Power up with Contactor close (EH only)

Note: *: Start Ready Status is the all status of Jog Restart **: Fault Bit is the IE and IB fault status


1503-UM054D-EN-P – March 2015

Appendix F

1503-UM054D-EN-P – March 2015

IntelliVAC Plus Firmware

Introduction In order to update the firmware of the IntelliVAC Plus module using DeviceNet you will need the following:

1. Personal computer equipped with a DeviceNet interface such as a 1784-PCD or 1770-KFD

2. IntelliVAC Plus Event Browser Software

3. A functioning DeviceNet network including 24VDC DeviceNet power supply

Browsing the Events:

Start the IntelliVAC Plus Event Browser Software Select a DeviceNet driver

Figure F.1 – DeviceNet Driver Selection

F-2 IntelliVAC Plus Firmware

1503-UM054D-EN-P – March 2015

Configure the selected DeviceNet driver

Figure F.2 – DeviceNet Drive Configuration

Set the MacID of the IntelliVAC Plus Select the Base Module Click ‘Update’ button, the events of the selected base module will

be shown in the list

Figure F.3 – IntelliVAC Plus Event Browser

Publication 1503-UM054D-EN-P - March 2015 Supersedes Publication 1503-UM054C-EN-P - June 2013 Copyright © 2015 Rockwell Automation, Inc. All rights reserved. Printed in Canada.

Rockwell Automation Support

Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support, you can find technical manuals, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools. You can also visit our Knowledgebase at http://www.rockwellautomation.com/knowledgebase for FAQs, technical information, support chat and forums, software updates, and to sign up for product notification updates.

For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnectSM support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/support/.

Installation Assistance

If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact Customer Support for initial help in getting your product up and running.

New Product Satisfaction Return

Rockwell Automation tests all of its products to help ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.

Documentation Feedback

Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.

United States or Canada 1.440.646.3434

Outside United States or Canada Use the Worldwide Locator at http://www.rockwellautomation.com/rockwellautomation/support/overview.page, or contact your local Rockwell Automation representative.

United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process.

Outside United States Please contact your local Rockwell Automation representative for the return procedure.

Medium Voltage Products, 135 Dundas Street, Cambridge, ON, N1R 5X1 Canada, Tel: (1) 519.740.4100, Fax: (1) 519.623.8930Online: www.ab.com/mvb

Rockwell Automation maintains current product environmental information on its website athttp://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.

http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf

http://www.rockwellautomation.com/support/

http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

http://www.rockwellautomation.com/literature/

http://www.rockwellautomation.com/locations/

http://www.rockwellautomation.com/support

http://www.rockwellautomation.com/knowledgebase

Documents

Catalog Number 1503 - RockwellAutomation.com · 2015-03-27 · 1 – Logical Mask 0 (Mask Local) ..... 9-2 2 – Logical Mask 1 (Mask ... Data Table Layout ... F-1 . viii Table of