Digital IO Module User Man-Allen Bradley

8/20/2019 Digital IO Module User Man-Allen Bradley

1/250

ControlLogixDigital I/O Modules

Input Modules

1756-IA16, -IA16I, -IA8D, -IB16,-IB16D, -IB16I, -IB32, -IC16, -IH16I,-IM16I, -IN16, -IV16, -IV32

Output Modules

1756-OA16, -OA16I, -OA8, -OA8D,-OA8E, -OB16D, -OB16E, -OB16I,-OB32, -OB8, -OB8EI, -OC8, -OH8I,-ON8, - OV16E, -OW16I, -OX8I

User Manual


2/250

Important User Information Because of the variety of uses for the products described in thispublication, those responsible for the application and use of this

control equipm ent m ust satisfy them selves that all necessary stepshave been taken to assure that each application and use m eets allperform ance and safety requirem ents, including any applicable law s,

regulations, codes and standards.

The illustrations, charts, sam ple program s and layout exam ples show n

in this guide are intended solely for purposes of exam ple. Since thereare m any variables and requirem ents associated w ith any particularinstallation, Allen-Bradley does not assum e responsibility or liability

(to include intellectual property liability) for actual use based uponthe exam ples show n in this publication.

Allen-Bradley publication SG I-1.1,Safety Gui delin es for theAppli cation , In stallati on and Mai n tenan ce of Solid-State Con trol

(available from your local Allen-Bradley office), describes som e

im portant differences betw een solid-state equipm ent and

electrom echanical devices that should be taken into considerationw hen applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in w holeor part, w ithout w ritten perm ission of Rockw ell Autom ation, is

prohibited.

Throughout this m anual w e use notes to m ake you aw are of safety

considerations:

Attention statem ents help you to:

• identify a hazard

• avoid a hazard

• recognize the consequences

Allen-Bradley is a tradem ark of Rockw ell Autom ation

ATTENTION

!

Identifies inform ation about practices or

circum stances that can lead to personal injury ordeath, property dam age or econom ic loss

IMPORTANTIdentifies inform ation that is critical for successfulapplication and understanding of the product.


3/250

European Communities (EC)Directive Compliance

If this product has the CE m ark it is approved for installation w ithinthe European U nion and EEA regions. It has been designed and

tested to m eet the follow ing directives.

EMC Directive

This product is tested to m eet the C ouncil D irective 89/336/ECElectrom agnetic C om patibility (EM C) by applying the follow ingstandards, in w hole or in part, docum ented in a technical

construction file:

• EN 50081-2 EM C — G eneric Em ission Standard, Part 2 —

Industrial Environm ent

• EN 50082-2 EM C — G eneric Im m unity Standard, Part 2 —

Industrial Environm ent

This product is intended for use in an industrial environm ent.

Low Voltage Directive

This product is tested to m eet Council D irective 73/23/EEC Low

Voltage, by applying the safety requirem ents of EN 61131-2

Program m able C ontrollers, Part 2 - Equipm ent Requirem ents and

Tests. For specific inform ation required by EN 61131-2, see the

appropriate sections in this publication, as w ell as the A llen-Bradleypublication Industrial Autom ation W iring and G rounding G uidelines

For N oise Im m unity, publication 1770-4.1.

O pen style devices m ust be provided w ith environm ental and safety

protection by proper m ounting in enclosures designed for specific

application conditions. See N EM A Standards publication 250 and IEC

publication 529, as applicable, for explanations of the degrees of

protection p rovided by different types of enclosure.


4/250

Rockwell AutomationSupport

Rockw ell Autom ation offers support services w orldw ide, w ith over 75sales/support offices, 512 authorized distributors and 260 authorized

system s integrators located throughout the U nited States alone, as w ellas Rockw ell A utom ation representatives in every m ajor country in thew orld.

Local Product Support

Contact your local Rockw ell Autom ation representative for:

• sales and order support

• product technical training

• w arranty support

• support service agreem ents

Technical Product Assistance

If you need to contact Rockw ell Autom ation for technical assistance,please review the troubleshooting inform ation first. If the problem

persists, then call your local Rockw ell A utom ation representative.

Your Questions or Comments on this Manual

If you find a problem w ith this m anual, please notify us of it on theenclosed Publication Problem Report.


5/250

1 Publication 1756-UM 058C-EN-P - M arch 2001

Summary of Changes

Introduction This release of this docum ent contains updated inform ation. Changesare designated by change bars in m argin, as show n to the left.

New and RevisedInformation

The table below lists the new and revised inform ation included in thisrelease of the C ontrolLogix digital I/O m odules user m anual.

Table Summary of Changes.1New and Revised Information

Information About New or Revised Location

Internal M odule Operations New Chapter 2

Connections Revised Chapter 2

Electronic Keying Revised Chapter 3

Chapter 4Output Data Echo Revised Chapter 3

Chapter 4

1756-IV16 M odule New Chapter 3Chapter 7

1756-IV32 M odule New Chapter 3Chapter 7

1756-OV16E M odule New Chapter 3Chapter 7

A ddi tional Index Term s Revised and N ew Index


6/250

Publication 1756-UM 058C-EN-P - M arch 2001

Summary of Changes 2

Notes:


7/250


Preface

About This User Manual

What This Preface Contains This preface describes how to use this m anual. The follow ing tabledescribes w hat this preface contains and its location.

Who Should UseThis Manual

You m ust be able to program and operate an Allen-BradleyControlLogix Logix5550 controller to efficiently use your digital I/Om odules.

W e assum e that you know how to do this in this m anual. If you do

not, refer to the Logix5550 C ontroller docum entation before you

attem pt to use this m odule.Table C lists related docum entation.

Purpose of This Manual This m anual describes how to install, configure, and troubleshootyour ControlLogix digital I/O m odule.

For information about: See page:

W ho Should Use This M anual Preface-1

Purpose of This M anual Preface-1

Related Terms Preface-2

Relat ed Product s and Docum ent at ion Pref ace-4


8/250


Preface 2

Related Terms This m anual uses the follow ing term s:

Table Preface.BRelated Terms

This term: Means:

Broadcast Data transmissions to all address or functions

Bumplessreconfiguration

A reconfiguration in which the real time data connection to themodule is not closed and reopened. Communications are neverinterrupted and configuration data is applied to the moduleimmediately. This works best in a single owner-controllersystem.

Change of state (COS) Any change in the ON or OFF state of a point on an I/O module

Communicationsformat

Format that defines the type of information transferredbetween an I/O module and its owner controller. This formatalso defines the tags created for each I/O module.

Compatible match An electronic keying protection mode that requires that thephysical module and the module configured in the software tomatch according to vendor and catalog number. In this case,the minor revision of the module must greater than or equal tothat of the configured slot.

Connection The communication mechanism from the controller to anothermodule in the control system

ControlBus The backplane used by the 1756 chassis

Coordinated systemtime (CST)

Timer value which is kept synchronized for all modules withina single ControlBus chassis

Direct connection An I/O connection where the controller establishes anindividual connection with I/O modules

Disable keying An electronic keying protection mode that requires noattributes of the physical module and the module configured inthe software to match

Download The process of transferring the contents of a project on theworkstation into the controller

Electronic keying A feature where modules can be requested to perform anelectronic check to make sure that the physical module isconsistent with what was configured by the software

Exact match An electronic keying protection mode that requires the physicalmodule and the module configured in the software to matchaccording to vendor, catalog number, major revision and minorrevision

Field side Interface between user field wiring and I/O module

Inhibit A ControlLogix process that allows you to configure anI/O module but prevent it from communicating with the ownercontroller. In this case, the controller behaves as if the I/Omodule does not exist at all

Interface module (IFM) A module that uses prewired cable to connect wiring toan I/O module

Listen-only connection An I/O connection where another controller owns/provides theconfiguration and data for the module


9/250


Preface 3

Major revision A module revision that is updated any time there is a functionalchange to the module

Minor revision A module revision that is updated any time there is a change tothe module that does not affect its function or interface

Multicast Data transmissions which reach a specific group of one ormore destinations

Multiple owners A configuration set-up where multiple owner controllers use exactly the same configuration information tosimultaneously own an input module

Network update time(NUT)

The smallest repetitive time interval in which the data can besent on a ControlNet network. The NUT ranges from 2ms to100ms

Owner controller The controller that creates and stores the primaryconfiguration and communication connection to a module

Program Mode Controller program is not executing.Inputs are still actively producing data.Outputs are not actively controlled and go to their configuredprogram mode

Rack connection An I/O connection where the 1756-CNB module collects digitalI/O words into a rack image to conserve ControlNetconnections and bandwidth

Rack optimization A communications format in which the 1756-CNB modulecollects all digital I/O words in the remote chassis and sendsthem to controller as a single rack image

Remote connection An I/O connection where the controller establishes anindividual connection with I/O modules in a remote chassis

Removal and insertionunder power (RIUP)

ControlLogix feature that allows a user to install or remove amodule or RTB while power is applied

Removable TerminalBlock (RTB)

Field wiring connector for I/O modules

Requested packetinterval (RPI)

The maximum amount of time between broadcasts of I/O data

Run mode Controller program is executingInputs are actively producing data.Outputs are actively controlled

Service A system feature that is performed on user demand, such asfuse reset or diagnostic latch reset

System side Backplane side of the interface to the I/O module

Tag A named area of the controller’s memory where data is stored

Timestamping ControlLogix process that stamps a change in input data with arelative time reference of when that change occurred

Table Preface.BRelated Terms


10/250


Preface 4

Related Products andDocumentation

The follow ing table lists related ControlLogix products anddocum entation:

If you need m ore inform ation on these products, contact your local

Allen-Bradley integrator or sales office for assistance. For m oreinform ation on the docum entation, refer to the Allen-B radleyPublication Index, publication SD 499.

Table Preface.CRelated Documentation

Catalognumber:

Document title: Pub. number:

1756-A4,-A7, -A10,-A13

Co nt ro lLo gi x Ch as si s In st al la ti on In st ru ct io ns 1 75 6-IN 08 0B

1756-PA72,-PB72

ControlLogix Power Supply Installat ion Instructi ons 1756-5.67

1756-PA75,-PB75

ControlLogix Power Supply Installat ion Instructi ons 1756-5.78

1756-Series ControlLogix M odule Instal lat ion Instruct ions(Each module has separate installation document .)

M ultiple 1756-INnumbers

1756-Series Cont rolLogix System User M anual 1756-UM 001

1 75 6-Se ri es Co nt ro lLo gi x A na lo g I/ O M o d ul es U se r M a n ua l 1 75 6- 6.5 .9

1756-CNB,-CNBR

ControlLogix ControlNet Interface M odule UserManual

1756-6.5.3

1756-DHRIO ControlLogix Data Highway Plus Communicat ionInterface M odule User M anual

1756-6.5.14

1756-ENET ControlLogix Ethernet Communicat ion Inter faceM odule User Manual

1756-UM051


11/250

i Publication 1756-UM 058C-EN-P - M arch 2001

Table of Contents

Chapter 1

What Are ControlLogix Digital I/O

Modules?

W hat This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 1-1W hat are C ontrolLogix D igital I/O M odules?. . . . . . . . . . . . 1-1U sing an I/O M odule in the ControlLogix System . . . . . . . . 1-2

Features of the C ontrolLogix D igital I/O M odules . . . . . 1-4U sing M odule Identification and Status Inform ation . . . . . . 1-5Preventing Electrostatic D ischarge . . . . . . . . . . . . . . . . . . . 1-6Rem oval and Insertion U nder Pow er . . . . . . . . . . . . . . . . . 1-6Chapter Sum m ary and W hat’s N ext . . . . . . . . . . . . . . . . . . 1-6

Chapter 2

Digital I/O Operation in the

ControlLogix System

W hat This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 2-1

O w nership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

U sing RSN etW orx and RSLogix 5000 . . . . . . . . . . . . . . . . . 2-2

I/O M odules in Local Chassis. . . . . . . . . . . . . . . . . . . . 2-2I/O M odules in Rem ote Chassis . . . . . . . . . . . . . . . . . . 2-3

Internal M odule O perations. . . . . . . . . . . . . . . . . . . . . . . . 2-4

Input M odules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

O utput M odules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

D irect Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Rack Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Suggestions for Rack Connection U sage . . . . . . . . . . . . 2-8

Input M odule O peration . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Input M odules in a Local Chassis. . . . . . . . . . . . . . . . . . . . 2-10

Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . 2-10Change of State (CO S). . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Input M odules in a Rem ote Chassis . . . . . . . . . . . . . . . . . . 2-11

Best Case RPI M ulticast Scenario. . . . . . . . . . . . . . . . . . 2-12

W orst Case RPI M ulticast Scenario . . . . . . . . . . . . . . . . 2-13

O utput M odule O peration . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

O utput M odules in a Local Chassis . . . . . . . . . . . . . . . . . . 2-14O utput M odules in a Rem ote Chassis. . . . . . . . . . . . . . . . . 2-15

Best Case RPI M ulticast Scenario. . . . . . . . . . . . . . . . . . 2-16

W orst Case RPI M ulticast Scenario . . . . . . . . . . . . . . . . 2-16

Listen-O nly M ode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

M ultiple O w ners of Input M odules . . . . . . . . . . . . . . . . . . 2-18Configuration Changes in an Input M odulew ith M ultiple O w ners . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Chapter Sum m ary and W hat’s N ext . . . . . . . . . . . . . . . . . . 2-20


12/250


Table of Contents ii

Chapter 3

ControlLogix Standard Digital I/O

Module Features

W hat This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 3-1D eterm ining Input M odule Com patibility . . . . . . . . . . . . . . 3-1D eterm ining O utput M odule C om patibility. . . . . . . . . . . . . 3-2

U sing Features Com m on to ControlLogix StandardD igital I/O M odules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Rem oval and Insertion U nder Pow er (RIU P). . . . . . . . . 3-3M odule Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . 3-3Fully Softw are Configurable . . . . . . . . . . . . . . . . . . . . . 3-3Electronic K eying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4U sing the System Clock to Tim estam p Inputs andSchedule O utputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Producer/Consum er M odel. . . . . . . . . . . . . . . . . . . . . . 3-9LED Status Inform ation. . . . . . . . . . . . . . . . . . . . . . . . . 3-10Full Class I D ivision 2 Com pliance . . . . . . . . . . . . . . . . 3-10

CE/CSA /U L/FM Agency Approvals . . . . . . . . . . . . . . . . 3-11U sing Features Specific to Standard Input M odules. . . . . . . 3-11

D ata Transfer on Either Change of State or Cyclic Tim e. 3-11Softw are Configurable Filter Tim es. . . . . . . . . . . . . . . . 3-11Isolated and N on-Isolated Varieties of M odules. . . . . . . 3-12M ultiple Point D ensities . . . . . . . . . . . . . . . . . . . . . . . . 3-12

U sing Features Specific to Standard O utput M odules . . . . . 3-12Configurable Point-Level O utput Fault States. . . . . . . . . 3-12O utput D ata Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Field W iring O ptions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14M ultiple Point D ensities . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Fusing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Field Pow er Loss D etection . . . . . . . . . . . . . . . . . . . . . 3-17D iagnostic Latch of Inform ation . . . . . . . . . . . . . . . . . . 3-17

Fault and Status Reporting B etw een Input M odulesand Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Fault and Status Reporting B etw een O utput M odulesand Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Chapter Sum m ary and W hat’s N ext . . . . . . . . . . . . . . . . . . 3-21

Chapter 4

ControlLogix Diagnostic

Digital I/O Module Features


D eterm ining D iagnostic Input M odule Com patibility. . . . . . 4-1

D eterm ining D iagnostic O utput M odule Com patibility . . . . 4-2

U sing Features Com m on to ControlLogix D iagnostic

D igital I/O M odules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Rem oval and Insertion U nder Pow er (RIU P). . . . . . . . . 4-3

M odule Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Fully Softw are Configurable . . . . . . . . . . . . . . . . . . . . . 4-3

Electronic K eying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4


13/250


Table of Contents iii

Tim estam ping Inputs and Scheduling O utputs. . . . . . . . 4-7Producer/Consum er M odel. . . . . . . . . . . . . . . . . . . . . . 4-9LED Status Inform ation. . . . . . . . . . . . . . . . . . . . . . . . . 4-10Full Class I D ivision 2 Com pliance . . . . . . . . . . . . . . . . 4-10

CE/CSA /U L/FM Agency Approvals . . . . . . . . . . . . . . . . 4-11D iagnostic Latch of Inform ation . . . . . . . . . . . . . . . . . . 4-11D iagnostic Tim estam p . . . . . . . . . . . . . . . . . . . . . . . . . 4-118 Point AC/16 Point D C . . . . . . . . . . . . . . . . . . . . . . . . 4-12Point Level Fault Reporting . . . . . . . . . . . . . . . . . . . . . 4-12

U sing Features Specific to D iagnostic Input M odules . . . . . 4-14D ata Transfer on Either Change of State or Cyclic Tim e. 4-14Softw are Configurable Filter Tim es. . . . . . . . . . . . . . . . 4-14Isolated and N on-Isolated Varieties of M odules. . . . . . . 4-14M ultiple Point D ensities . . . . . . . . . . . . . . . . . . . . . . . . 4-15O pen W ire D etection . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Field Pow er Loss D etection . . . . . . . . . . . . . . . . . . . . . 4-16D iagnostic Change of State for Input M odules. . . . . . . . 4-16U sing Features Specific to D iagnostic O utput M odules . . . . 4-17

Configurable Point-Level O utput Fault States. . . . . . . . . 4-17O utput D ata Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Field W iring O ptions . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19M ultiple Point D ensities . . . . . . . . . . . . . . . . . . . . . . . . 4-19Fusing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20N o Load D etection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Field Side O utput Verification. . . . . . . . . . . . . . . . . . . . 4-22Pulse Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Point Level Electronic Fusing . . . . . . . . . . . . . . . . . . . . 4-24Field Pow er Loss D etection . . . . . . . . . . . . . . . . . . . . . 4-24D iagnostic Change of State for O utput M odules . . . . . . 4-25

Fault and Status Reporting B etw een Input M odulesand Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Fault and Status Reporting B etw een O utput M odulesand Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27Chapter Sum m ary and W hat’s N ext . . . . . . . . . . . . . . . . . . 4-29

Chapter 5

Installing the ControlLogix

I/OModule


Installing the ControlLogix I/O M odule . . . . . . . . . . . . . . . 5-1Keying the Rem ovable Term inal Block. . . . . . . . . . . . . . . . 5-2

Connecting W iring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Assem bling Rem ovable Term inal Block and the H ousing . . 5-7

Choosing the Extended-D epth H ousing . . . . . . . . . . . . . . . 5-8Installing the Rem ovable Term inal Block . . . . . . . . . . . . . . 5-10

Rem oving the Rem ovable Term inal Block . . . . . . . . . . . . . 5-12

Rem oving the M odule from the Chassis . . . . . . . . . . . . . . . 5-13



14/250


Table of Contents iv

Chapter 6

Configuring Your ControlLogix

Digital I/O Modules

W hat This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 6-1Configuring Y our I/O M odule . . . . . . . . . . . . . . . . . . . . . . 6-2

RSLogix 5000 Configuration Softw are . . . . . . . . . . . . . . 6-2

O verview of the Configuration Process . . . . . . . . . . . . . . . 6-2Creating a N ew M odule. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Com m unications Form at. . . . . . . . . . . . . . . . . . . . . . . . 6-6Electronic K eying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

U sing the D efault Configuration. . . . . . . . . . . . . . . . . . . . . 6-10Altering the D efault Configuration . . . . . . . . . . . . . . . . . . . 6-10Configuring a Standard Input M odule . . . . . . . . . . . . . . . . 6-12Configuring a Standard O utput M odule . . . . . . . . . . . . . . . 6-13Configuring a D iagnostic Input M odule . . . . . . . . . . . . . . . 6-14Configuring a D iagnostic O utput M odule . . . . . . . . . . . . . . 6-15Editing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

Reconfiguring M odule Param eters in Rem ote Run M ode . . . 6-17Reconfiguring M odule Param eters in Program M ode. . . . . . 6-18Configuring I/O M odules in a Rem ote Chassis . . . . . . . . . . 6-19Input O nline Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21O utput O nline Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22View ing and Changing M odule Tags . . . . . . . . . . . . . . . . . 6-23Chapter Sum m ary and W hat’s N ext . . . . . . . . . . . . . . . . . . 6-24

Chapter 7

Module-Specific Information W hat This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 7-11756-IA 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

1756-IA 16I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41756-IA8D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61756-IB 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

1756-IB16D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

1756-IB16I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

1756-IB32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

1756-IC16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

1756-IH 16I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-181756-IM 16I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

1756-IN 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

1756-IV16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

1756-IV32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

1756-O A16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

1756-O A16I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30

1756-O A8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32

1756-O A8D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34

1756-O A8E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36

1756-O B16D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38

1756-O B16E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40


15/250


Table of Contents v

1756-O B16I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-421756-O B32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-441756-O B8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-461756-O B8EI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48

1756-O C8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-501756-O H 8I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-521756-O N 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-541756-O V16E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-561756-O W 16I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-581756-O X8I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60Chapter Sum m ary and W hat’s N ext . . . . . . . . . . . . . . . . . . 7-62

Chapter 8

Troubleshooting Your Module W hat This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 8-1U sing Indicators to Troubleshoot Y our M odule . . . . . . . . . 8-1

LED indicators for input m odules . . . . . . . . . . . . . . . . . 8-1LED indicators for output m odules . . . . . . . . . . . . . . . . 8-2

U sing RSLogix 5000 to Troubleshoot Y our M odule . . . . . . . 8-4

D eterm ining Fault Type . . . . . . . . . . . . . . . . . . . . . . . . 8-5


Appendix A

Using Software

Configuration Tags

M odule Tag N am es and D efinitions. . . . . . . . . . . . . . . . . . A-3

Standard Input M odule Tags. . . . . . . . . . . . . . . . . . . . . A-3

Standard O utput M odule Tags . . . . . . . . . . . . . . . . . . . A-4

D iagnostic Input M odule Tags . . . . . . . . . . . . . . . . . . . A-6

D iagnostic O utput M odule Tags . . . . . . . . . . . . . . . . . . A-8

Accessing the Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11

Changing C onfiguration Through the Tags. . . . . . . . . . . . A-12

M odule-w ide Configurable Features . . . . . . . . . . . . . . A-12

Point-by-Point Configurable Features . . . . . . . . . . . . . A-13

D ow nloading N ew Configuration D ata

From the Tag Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Sam ple Series of Tags . . . . . . . . . . . . . . . . . . . . . . . . A-15

Appendix B

Using Ladder Logic U sing M essage Instructions . . . . . . . . . . . . . . . . . . . . . . . . B-1Processing Real-Tim e Control and M odule Services. . . . B-2

O ne Service Perform ed Per Instruction . . . . . . . . . . . . . B-2

Creating a N ew Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Enter M essage Configuration . . . . . . . . . . . . . . . . . . . . B-4

U sing Tim estam ped Inputs and Scheduled O utputs. . . B-10Resetting a Fuse, Perform ing the Pulse Test

and Resetting Latched D iagnostics . . . . . . . . . . . . . . . B-13


16/250


Table of Contents vi

Perform ing a W H O to Retrieve M odule Identificationand Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14U sing Tags in Ladder Logic . . . . . . . . . . . . . . . . . . . . B-16

Appendix CPower Supply Sizing Chart

Appendix D

Driving Motor Starters with

ControlLogix Digital I/O Modules

D eterm ining the M axim um N um ber of M otor Starters . . D -2

Index


17/250


Chapter 1

What Are ControlLogix Digital I/O Modules?

What This Chapter Contains This chapter describes the ControlLogix digital m odules and w hat youm ust know and do before you begin to use them .

What are ControlLogixDigital I/O Modules?

ControlLogix digital I/O m odules are input/output m odules thatprovide O N /O FF detection and actuation.

U sing the producer/consum er netw ork m odel, they can produce

inform ation w hen needed w hile providing additional systemfunctions.

The follow ing is a list of the features available on ControlLogix digital

I/O m odules that allow greater system applicability.

• Rem oval and insertion under pow er (RIU P) - This system featureallow s you to rem ove and insert m odules and RTB w hile pow eris applied. For m ore inform ation on RIU P, see page 1-6.

• Producer/consum er com m unications - These com m unications

are an intelligent data exchange betw een m odules and othersystem devices in w hich each m odule produces data w ithouthaving been polled.

• System tim estam p of data - A 64-bit system clock places atim estam p on the transfer of data betw een the m odule and itsow ner-controller w ithin the local chassis.

• M odule level fault reporting and field side diagnostic detection

• Class I D ivision 2, U L, CSA , FM and CE Agency C ertification


W h at a re Co nt ro lLog ix Di gi ta l I/ O M o dul es? 1 -1

Using an I/O M odule in the ControlLogixSystem

1-2

Types of Cont rolLogix Di git al I/ O M o dul es 1-2

Features of the ControlLogix Digital I/OModules

1-4

Prevent ing Electrostat ic Discharge 1-6

Removal and Insert ion Under Pow er 1-6

Chapter Summary and W hat ’s Next 1-6


18/250


1-2 Wh at Are ControlLogix Digital I/O M odules?

Using an I/O Module intheControlLogix System

ControlLogix m odules m ount in a C ontrolLogix chassis and use aRem ovable Term inal Block (RTB) or a B ulletin 1492 Interface M odulecable that connects to an IFM to connect all field-side w iring.

Before you install and use your m odule you should have already:

• installed and grounded a 1756 chassis and pow er supply. Toinstall these products, refer to the publications listed in

Table 1.A.

• ordered and received an R TB or IFM and its com ponents foryour application.

Table 1.AChassis and Power Supply Documentation

Catalognumber:

Document title: Pub. number:

1756-A4, -A7,-A10, -A13

Co nt ro lLo gi x Ch as si s In st al la ti on In st ru ct io ns 1 75 6-IN 08 0B

1756-PA72,-PB72

ControlLogix Pow er Supply Instal lat ion Instruct ions 1756-5.67

1756-PA75,-PB75

ControlLogix Power Supply Installat ion Instructio ns 1756-5.78

IMPORTANT RTBs and IFM s are not included w ith yourm odule purchase.

Table 1.BTypes of ControlLogix Digital I/O Modules

CatalogNumber:

Description: RTB:

1756-IA16 79-132V ac 16 pt . input module 20 pin

1756-IA16I 79-132V ac 16 pt . isolated input module 36 pin

1756-IA8D 79-132V ac 8pt . diagnost ic input module 20 pin

1756-IB16 10-31V dc 16 pt . input module 20 pin

1756-IB16D 10-30V dc diagnost ic input module 36 pin

1756-IB16I 10-30V dc 16 pt . isolated input module 36 pin

1756-IB32 10-31V dc 32 pt . input module 36 pin

1756-IC16 30-60V dc 16 pt . input module 20 pin

1756-IH16I 90-146V dc 16 pt . isolated input module 36 pin

1756-IM 16I 159-265V ac 16 pt . isolated input module 36 pin

1756-IN16 10-30V ac 16 pt . input module 20 pin

1756-IV16 10-31V dc 16 pt . sourcing current input module 20 pin

1756-IV32 10-31V dc 32 pt . sourcing current input module 36 pin


19/250


W hat Are ControlLogix Digital I/ O M odules? 1-3

1756-OA16 74-265V ac 16 pt . output module 20 pin1756-OA16I 74-265V ac 16 pt . isolated output module 36 pin

1756-OA8 74-265V ac 16 pt . output module 20 pin

1756-OA8D 74-132V ac 8 pt . diagnost ic output module 20 pin

1756-OA8E 74-132V ac 8 pt . e-fused output module 20 pin

1756-OB16D 19-30V dc 16 pt . diagnost ic out put module 36 pin

1756-OB16E 10-31V dc 16 pt . e-fused output module 20 pin

1756-OB16I 10-30V dc 16 pt . isolated output module 36 pin

1756-OB32 10-31V dc 32 pt . output module 36 pin

1756-OB8 10-30V dc 8 pt . output module 20 pin1756-OB8EI 10-30V dc 8 pt . e-fused isolated output module 36 pin

1756-OC8 30-60V dc 8 pt . output module 20 pin

1756-OH8I 90-146V dc 8 pt . isolat ed output module 36 pin

1756-ON8 10-30V ac 8 pt . output module 20 pin

1 75 6-OV1 6E 1 0- 31 V d c 1 6 p t. e- fu se d s in ki ng cu rre ntoutput module

20 pin

1756-OW 16I 10-265V 16 pt . isolated relay output module 36 pin

1 75 6-OX8 I 1 0- 26 5V, 5 -1 50 V d c 8 p t. i so la te d r el ay no rm al lyopen, normally closed output module

36 pin

Table 1.BTypes of ControlLogix Digital I/O Modules

CatalogNumber:

Description: RTB:


20/250



Features of the ControlLogix Digital I/O Modules

ControlBus connector - The backplane connector interface for theControlLogix system connects the m odule to the ControlBus

backplane.

Connectors pins - Input/output, pow er and grounding connectionsare m ade to the m odule through these pins w ith the use of an R TB orIFM .

Locking tab - The locking tab anchors the RTB or IFM cable on them odule, m aintaining w iring connections.

Slots for keying - M echanically keys the RTB to preventinadvertently m aking the w rong w ire connections to your m odule.

Status indicators - Indicators display the status of com m unication,m odule health and input/output devices. U se these indicators to helpin troubleshooting.

Top and bottom guides - G uides provide assistance in seating theRTB or IFM cable onto the m odule.

40200-M

DC OUTPUT

ST O

K 0 1 2 3 4 5 6 7

ControlLogix I/O Module

Indicators Locking tab

Removable Terminal Block

Slots for

keying theRTB

Connector pinsTop an d

bottom

guides

ControlBusConnector


21/250


W hat Are ControlLogix Digital I/ O M odules? 1-5

Using ModuleIdentification and StatusInformation

Each ControlLogix I/O m odule m aintains specific identificationinform ation that separates it from all other m odules. This inform ationassists you in tracking all the com ponents of your system .

For exam ple, you can track m odule identification inform ation to be

aw are of exactly w hat m odules are located in any C ontrolLogix rack atany tim e. W hile retrieving m odule identity, you can also retrieve them odule’s status.

Each m odule m aintains the follow ing inform ation:

Table 1.CModule Identification and Status Information

Module Ident if icat ion: Descr iption:

Product Type Module’s product type, such as Digital I/O orAnalog I/O module

Catalog Code Module’s catalog number

Major Revision Module’s major revision number

Minor Revision Module’s minor revision number

Status Module’s status. Returns the following information:

• Controller ownership (if any)

• Whether module has been configured

• Device Specific Status, such as:

–Self-Test

–Flash update in progress

–Communications fault

–Not owned (outputs in prog. mode)

–Internal fault (need flash update)

–Run mode

–Program mode (output mods only)

• Minor recoverable fault

• Minor unrecoverable fault

• Major recoverable fault

• Major unrecoverable fault

Vendor ID Module manufacturer vendor, for example Allen-Bradley

Serial Number Module serial number

Length of ASCII Text String Number of characters in module’s text string

ASCII Text String Number of characters in module’s text string

IMPORTANT You m ust perform a W H O service to retrieve thisinform ation. For m ore inform ation on how to

retrieve m odule identification inform ation, seeAppendix B .


22/250



Preventing ElectrostaticDischarge

This m odule is sensitive to electrostatic discharge.

Removal and InsertionUnder Power

These m odules are designed to be installed or rem oved w hile chassispow er is applied.

Chapter Summary andWhat’s Next

In this chapter you learned about:

• w hat ControlLogix digital I/O m odules are.

• types of ControlLogix digital I/O m odules.

M ove on to C hapter 2,D igital I/O O peration in the ControlLogixSystem .

ATTENTION

!

Electrostatic discharge can dam ageintegrated circuits or sem iconductors if you touch

backplane connector pins. Follow these guidelinesw hen you handle the m odule:

• Touch a grounded object to discharge staticpotential

• W ear an approved w rist-strap grounding device

• D o not touch the backplane connector orconnector pins

• D o not touch circuit com ponents inside them odule

• If available, use a static-safe w ork station

• W hen not in use, keep the m odule in itsstatic-shield box

ATTENTION

!

W hen you insert or rem ove a m odule w hilebackplane pow er is applied, an electrical arc m ayoccur. An electrical arc can cause personal injury orproperty dam age by:

• sending an erroneous signal to your system ’s

field devices causing unintended m achine

m otion or loss of process control.

• causing an explosion in a hazardous

environm ent.

Repeated electrical arcing causes excessive w ear to

contacts on both the m odule and its m ating

connectors. W orn contacts m ay create electrical

resistance that can affect m odule operation.


23/250


Chapter 2

Digital I/O Operation in theControlLogix System

What This Chapter Contains This chapter describes how digital I/O m odules w ork w ithin theControlLogix system .


Ow nership 2-2

Using RSNetW orx and RSLogix 5000 2-2

Internal M odule Operat ions 2-4

Direct Connect ions 2-6

Input M odule Operat ion 2-9

Input M odules in a Local Chassis 2-10

Requested Packet Interval (RPI) 2-10

Change of State (COS) 2-10

Input M odules in a Remote Chassis 2-11

Output M odule Operat ion 2-14

Output M odules in a Local Chassis 2-14

Output M odules in a Remote Chassis 2-15

Listen-Only M ode 2-17

M ult iple Ow ners of Input M odules 2-18

Configuration Changes in an Input M odulew ith Mult iple Ow ners

2-19

Rack Connect ions 2-7

Suggest ions for Rack Connect ion Usage 2-8



24/250


2-2 Digital I/ O Operation in the ControlLogix System

Ownership Every I/O m odule in the C ontrolLogix system m ust be ow ned by aLogix5550 Controller. This ow ner-controller:

• stores configuration data for every m odule that it ow ns.

•can be local or rem ote in regard to the I/O m odule’s position.

• sends the I/O m odule configuration data to define the m odule’s

behavior and begin operation w ith the control system .

Each C ontrolLogix I/O m odule m ust continuously m aintain

com m unication w ith its ow ner to operate norm ally.

Typically, each m odule in the system w ill have only 1 ow ner. Input

m odules can have m ore than 1 ow ner. O utput m odules, how ever, are

lim ited to a single ow ner.

For m ore inform ation on the increased flexibility provided by m ultiple

ow ners and the ram ifications of using m ultiple ow ners, see page 2-13.

Using RSNetWorx andRSLogix 5000

The I/O configuration portion of RSLogix5000 generates the

configuration data for each I/O m odule in the control system , w hether

the m odule is located in a local or rem ote chassis. A rem ote chassis,

also know n as netw orked, contains the I/O m odule but not the

m odule’s ow ner controller.

Configuration data is transferred to the controller during the program

dow nload and subsequently transferred to the appropriate I/O

m odules.

I/O Modules in Local Chassis

I/O m odules in the sam e chassis as the controller are ready to run as

soon as the configuration data has been dow nloaded.


25/250


Digital I/O Operation in the ControlLogix System 2-3

I/O Modules in Remote Chassis

You m ust run RSN etW orx to enable I/O m odules in the netw orked

chassis. Running RSN etW orx transfers configuration data to netw orked

m odules and establishes a N etw ork U pdate Tim e (N U T) forControlN et. The N U T is com pliant w ith the desired com m unicationsoptions specified for each m odule during configuration.

Follow these guidelines w hen configuring I/O m odules:

1. Configure all I/O m odules for a given controller using RSLogix5000 and dow nload that inform ation to the controller.

2. If the I/O configuration data references a m odule in a rem otechassis, run RSN etW orx.

IMPORTANT If you are not using I/O m odules in a netw orkedchassis, running RSN etW orx is not necessary.H ow ever, anytim e a controller references an I/Om odule in a netw orked chassis, you m ust runRSN etW orx to configure ControlN et.

IMPORTANT RSN etW orx must be run w henever a new m odule isadded to a netw orked chassis. W hen a m odule isperm anently rem oved from a rem ote chassis, w e

recom m end that N etw orx be run to optim ize the

allocation of netw ork bandw idth.


26/250



Internal Module Operations Signal propogation delays exist w ith ControlLogix I/O m odules thatm ust be accounted for w hen operating them . Som e of these delays areuser selectable, and som e are inherent to the m odule hardw are. Forexam ple, there is a sm all delay (typically less than 1m S) betw eenw hen a signal is applied at the RTB of a ControlLogix input m odule

and w hen a signal is sent to the system over the C ontrolBus (Thistypical tim e reflects a filter tim e choice of 0m S for a D C input.).

This section offers a graphical explanation of the tim e lim itations w ithControlLogix I/O m odules.

Input Modules

As show n below , ControlLogix input m odules receive a signal at the

RTB and process it internally (i.e. hardw are delay, filter delay, ASICdelay) before sending a signal to the C ontrolBus via the RequestedPacket Interval (RPI) or at the Change of State (CO S).

Hardw are delay Fi l ter delay ASIC delay

42701

User conf igurable 200µS scanSignal applied

at t he RTB

Signal sent to

ControlBus

Varies betw een

modules and

appl ication

configuration

EXAMPLE M any factors (e.g. m odule type, voltage,tem perature, if the m odule is turning O N or O FF)affect the signal propogation delay on a m odule. Buta typical delay tim e can be estim ated.

For exam ple, if you are turning O N a 1756-IB16

m odule, the signal propogation delay is affected by:

• hardw are delay to energize the m odule (typically

200µS on this m odule)

• user-configurable filter tim e (0, 1, or 2m S)

• ASIC scan (200µS)

In the best case scenario (i.e. filter tim e of 0m S),the 1756-IB16 m odule has a 400µS signalpropogation delay at 24V dc in 25°C.

These tim es are not guaranteed. W e list m axim um

delay tim es for each m odule in the specificatons.


27/250



Output Modules

ControlLogix output m odules receive a signal from the controller and

process it internally (i.e. ASIC delay and hardw are delay) before

sending a signal to the output device via the RTB.

Hardware delayASIC delay

42702

Typically 10µS

Signal sent from

RTB output poi nt

Signal received

from control ler

Varies betw een

modules and

appl ication

configuration

EXAMPLE As previously stated, m any factors (e.g. m odule type,voltage, tem perature, if the m odule is turning O N orO FF) affect the signal propogation delay on am odule. But a typical delay tim e can be estim ated.

For exam ple, if you are turning O N a 1756-O B16Em odule, the signal propogation delay is affected by:

• hardw are delay to energize the m odule (typically

200µS on this m odule)• ASIC scan (10µS)

In the best case scenario, the 1756-O B16E m odule

has a 210µS signal propogation delay at 24V dc in24°C.

These tim es are not guaranteed. W e list m axim um

delay tim es for each m odule in the specificatons.


28/250



Connections A connection is the data transfer link betw een a controller and thedevice that occupies the slot that the configuration data references, inthis case, the I/O m odule. There are tw o types of connections:

• D irect Connections

• Rack Connections

The follow ing sections describe each type of connection.See

Table 2.A on page 2-9 for differences betw een connection types. Thetable also lists the advantages and disadvantages of each type.

Direct Connections

A direct connection is a real-tim e data transfer link betw een the

controller and the device that occupies the slot that the configurationdata references. W hen m odule configuration data is dow nloaded to anow ner-controller, the controller attem pts to establish a directconnection to each of the m odules referenced by the data.

If a controller has configuration data referencing a slot in the controlsystem , the controller periodically checks for the presence of a devicethere. W hen a device’s presence is detected there, the controller

autom atically sends the configuration data.

If the data is appropriate to the m odule found in the slot, a connection

is m ade and operation begins. If the configuration data is not

appropriate, the data is rejected and an error m essage displays in thesoftw are. In this case, the configuration data can be inappropriate for

any of a num ber of reasons. For exam ple, a m odule’s configuration

data m ay be appropriate except for a m ism atch in electronic keying

that prevents norm al operation.

The controller m aintains and m onitors its connection w ith a m odule.

Any break in the connection, such as m odule faults or rem oval of the

m odule from the chassis w hile under pow er, causes the controller to

set fault status bits in the data area associated w ith the m odule. The

RSLogix 5000 softw are m onitors this data area to annunciate the

m odules’failures.

IMPORTANTW hile a Logix5550 controller allow s up to 250

bidirectional connections, each individual I/O

m odule allow s 16 bidirectional connections.


29/250



Rack Connections

W hen a digital I/O m odule is located in a rem ote chassis (w ith respect

to its ow ner), you m ay selectrack optimization or listen-only rack

optimization in the Com m unications Form at field during initialm odule configuration. This depends on the bridge m odule(1756-CN B) configuration. If the CN B is selected for Listen-O nly rackoption, then the I/O m odule only allow s the Listen-O nly rack option.

A rack connection econom izes connection usage betw een the ow nerand digital I/O in the rem ote chassis. Rather than having several directconnections w ith individual RPI values, the ow ner has a single rackconnection w ith a single RPI value. That RPI value accom m odates alldigital I/O m odules in the rack connection.

The input (or data echo) inform ation is lim ited to general faults and

data. N o additional status (e.g. diagnostic) is available.

IMPORTANT Because rack connections are only applicable inapplications that use a rem ote chassis, you m ustconfigure the Com m unications Form at for both therem ote I/O m odule and the rem ote 1756-CN Bm odule.

M ake sure you configure both m odules for Rack

O ptim ization. If you choose a differentCom m unications Form at for each, the controllerm akes tw o connections to the sam e chassis (one foreach form at) and the sam e data travels acrossControlN et.

If you use Rack O ptim ization for both m odules, youpreserve bandw idth and configure your system tooperate m ore efficiently.

IMPORTANT Each controller can only establish 255 connections,in any com bination of direct or rack. In other w ords,you can use a rack connection betw een an ow nercontroller and m ultiple rem ote I/O m odules w hile

sim ultaneously using a direct connection betw eenthat sam e controller and any other I/O m odules inthe sam e rem ote chassis.


30/250



In this exam ple, the ow ner is still com m unicating w ith all I/O in therem ote chassis but has used only one connection. The data from allthree m odules is sent together sim ultaneously at the RPI. This optionelim inates the need for three separate connections.

Suggestions for Rack Connection Usage

W e recom m end that you use a rack connection for applications

in w hich:

• standard digital I/O m odules are used.

• non-fused digital output m odules are used.

• your ow ner controller is running low on connections.

Using a Rack Connection with I/O in a Remote Chassis

Local chassis Remote chassis

INPUT

INPUT

OUTPU

T

Rack connection fo r all

I/O in remote chassis

ControlNet 41021

Ow ner control ler ControlN et Bridge module Cont rolNet Bridge module

IMPORTANT Rack connections are only available to digital I/Om odules. Although analog m odules can only usedirect connections, the system can m ake both directand rack connections to the sam e chassis.

IMPORTANT D o not use a rack connection for diagnostic I/Om odules or fused output m odules. D iagnostic and

fused output data w ill not be transferred over a rackconnection. This defeats the purpose of using thosem odules.

Also rem em ber, w hile a Logix5550 controller allow sup to 250 bidirectional connections, each individualI/O m odule allow s 16 bidirectional connections.


31/250



Table 2.A lists the differences betw een connection types and theadvantages/disadvantages of each.

Input Module Operation In traditional I/O system s, controllers poll input m odules to obtaintheir input status. D igital input m odules in the C ontrolLogix systemare not polled by a controller. Instead, the m odules m ulticast their

data either upon Change of State or periodically. The frequencydepends on the options chosen during configuration and w here in thecontrol system that input m odule physically resides.

An input m odule’s behavior varies depending upon w hether it

operates in the local chassis or in a rem ote chassis. The follow ing

sections detail the differences in data transfers betw een these set-ups.

Table 2.ADifferences Between Direct and Rack Connections

Connection Type Advantages Disadvantages

Direct connect ions Al l input and data echoinformation is transferred,including diagnosticinformation and fusing data.

W ith more data transferringover ControlNet, yoursystem does not operate asefficiently as w ith rackconnections.

Rack connect ions Connect ion usage iseconomi zed. Theow ner-controller has asingle RPI value.

Input and data echoinformation is l imited togeneral faults and data.

IMPORTANT This is called the Producer/Consum er m odel. Theinput m odule is the producer of input data and the

controller is the consum er of the data.


32/250


2-10 Digital I/O Operation in the ControlLogix System

Input Modules ina Local Chassis

W hen a m odule resides in the sam e chassis as the ow ner controller,the follow ing tw o configuration param eters w ill affect how and w henan input m odule m ulticasts data:

• Requested Packet Interval (RPI)

• Change of State (CO S)

Requested Packet Interval (RPI)

This interval specifies the rate at w hich a m odule m ulticasts its data.The tim e ranges from 200 m icroseconds to 750 m illiseconds and issent to the m odule w ith all other configuration param eters. W hen the

specified tim e fram e elapses, the m odule w ill m ulticast data. This isalso called a cyclic update.

Change of State (COS)

This param eter instructs the m odule to transfer data w henever aspecified input point transitions from O N to O FF or O FF to O N .

CO S selection occurs on a per-point basis, but all m odule data ism ulticast w hen any point enabled for CO S changes state. CO S is m oreefficient than RPI because it m ulticasts data only w hen a changeoccurs.

IMPORTANT The m odule CO S feature defaults to both O N to O FFand O FF to O N enabled.

IMPORTANT You m ust specify an RPI regardless of w hether youenable C O S. If a change does not occur w ithin theRPI tim efram e, the m odule w ill still m ulticast data atthe rate specified by the RPI.


33/250



For exam ple, if an input is changing state consistently every 2 secondsand the RPI is set at 750m S, the data transfer w ill look like this:

Because the RPI and CO S functions are asynchronous to the programscan, it is possible for an input to change state during program scanexecution. The point m ust be “buffered”to prevent this. Copy the

input data from your input tags to another structure and use the datafrom there.

Input Modules ina Remote Chassis

If an input m odule physically resides in a chassis other than w here the

ow ner controller is (i.e. a rem ote chassis connected via C ontrolN et),

the role of the RPI and the m odule’s CO S behavior changes slightly

w ith respect to getting data to the ow ner.

The RPI and CO S behavior still define w hen the m odule w ill m ulticast

data within its own chassis (as described in the previous section),but only the value of the RPI determ ines w hen the ow ner controller

w ill receive it over the netw ork.

41381

= COS multicast

= RPI multicast

250 500 750

1 Sec

1250 1500 1750

2 Sec 3 Sec

2250 2500 2750 3250

TIP To m inim ize traffic and conserve bandw idth, w erecom m end you use a larger RPI value if the CO S

option is used and the m odule is located in the sam e

chassis as its ow ner.


34/250



W hen an RPI value is specified for an input m odule in a rem otechassis, in addition to instructing the m odule to m ulticast data w ithinits ow n chassis, the RPI also “reserves”a spot in the stream of data

flow ing across the C ontrolN et netw ork.

The tim ing of this “reserved”spot m ay or m ay not coincide w ith theexact value of the RPI, but the control system w ill guarantee that the

ow ner-controller w ill receive data at least as often as the specifiedRPI.

The “reserved”spot on the netw ork and the m odule’s RPI are

asynchronous to each other. This m eans there are B est and W orst Case

scenarios as to w hen the ow ner controller w ill receive updated

channel data from the m odule in a netw orked chassis.

Best Case RPI Multicast Scenario

In the B est Case scenario, the m odule perform s an RPI m ulticast w ith

updated channel data just before the “reserved”netw ork slot is m ade

available. In this case, the rem otely located ow ner receives the data

alm ost im m ediately.

40947ControlNet

Input Module in Remote Chassis with Data Coming At Least as Often as RPI

Input data multicast in

module’s chassis at RPI

Input data a t least as of ten as RPI

Ow ner cont rol ler ControlN et Bridge module Input moduleControlNet Bridge module


35/250



Worst Case RPI Multicast Scenario

In the W orst Case scenario, the m odule perform s an RPI m ulticastjust after the “reserved”netw ork slot has passed. In this case, the

ow ner-controller w ill not receive data until the next availablenetw ork slot.

Table 2.B sum m arizes the B est Case and W orst Case scenarios, from

the tim e an input changes state to the tim e the ow ner-controller w ill

receive the data:

W hen selecting values for the rem otely located m odule’s RPI, system

throughput is optim ized w hen its RPI value is a pow er of 2 tim es the

current N U T running on ControlN et.

For exam ple,Table 2.C show s recom m ended RPI values for a system

using a N U T of 5m S:

IMPORTANT Enabling the CO S feature on an input m odule in arem ote chassis allow s the m odule to m ulticast data at

both the RPI rate and w hen the input changes state.

This helps to reduce the Worst Case time.

Table 2.B

Best and Worst Case Scenarios For Remote Input Data Transfer

Best case scenario Worst case scenario

COS disa bled Backplane/Networktransfer times (


36/250



Output Module Operation An ow ner controller sends output data to an output m odule w heneither one of tw o things occur:

• at the end of every one of its program scans (local chassis only)

and/or• at the rate specified in the m odule’s RPI

W hen an output m odule physically resides in a rem ote chassis (w ith

respect to the ow ner-controller), the ow ner-controller sends data to

the output m odule only at the RPI rate specified for the m odule.U pdates are not perform ed at the end of the ow ner-controller’s

program scan.

W henever the m odule receives data from the controller, it im m ediately

m ulticasts the output com m ands it received to the rest of the system .

The actual output data is echoed by the output m odule as input data

and m ulticast back out onto the netw ork. This is called Output DataEcho. The O utput D ata Echo also m ay contain fault and diagnosticinform ation, depending on the m odule type.

Output Modules ina Local Chassis

W hen you specify an RPI value for a digital output m odule, you

instruct the ow ner-controller w hen to broadcast the output data to them odule. If the m odule resides in the sam e chassis as the

ow ner-controller, the m odule receives the data alm ost im m ediately

after the ow ner-controller sent it (backplane transfer tim es are sm all).

D epending on the value of the RPI, w ith respect to the length of the

program scan, the output m odule can receive and “echo”data

m ultiple tim es during one program scan.

IMPORTANT In this Producer/Consum er m odel, the outputm odule is the Consum er of the controller’s output

data and the Producer of the data echo.

40949

Data sent from owner at the end of

every program scan a nd the RPI

Ow ner control ler Output module


37/250



Output Modules ina Remote Chassis

If an output m odule physically resides in a chassis other than that ofthe ow ner controller (i.e. a rem ote chassis connected via C ontrolN et),the ow ner controller sends data to the output m odule only at the RPIrate specified. U pdates are not perform ed at the end of thecontroller’s program scan.

In addition, the role of the RPI for a rem ote output m odule changes

slightly, w ith respect to getting data from the ow ner-controller.

W hen an RPI value is specified for an output m odule in a rem ote

chassis, in addition to instructing the ow ner-controller to m ulticast the

output data w ithin its ow n chassis, the RPI also “reserves”a spot in

the stream of data flow ing across the ControlN et netw ork.

The tim ing of this “reserved”spot m ay or m ay not coincide w ith the

exact value of the RPI, but the control system w ill guarantee that the

output m odule w ill receive dataat least as often

as the specified RPI.

The “reserved”spot on the netw ork and w hen the controller sends the

output data are asynchronous to each other. This m eans there are B est

and W orst Case scenarios as to w hen the ow ner controller w ill receive

updated channel data from the m odule in a netw orked chassis.

42675ControlNet

Output Module in Remote Chassis with Data Coming At Least as Often as RPI

Immediate backplane

transfers to module

Output data at least as oft en as RPI

Data sent from owner

at m odule’s RPI only

Ow ner control ler ControlN et Bridge module Output moduleControlNet Bridge module


38/250



Best Case RPI Multicast Scenario

In the Best Case scenario, the ow ner-controller sends the output datajust before the “reserved”netw ork slot is m ade available. In this case,

the rem otely located output m odule receives the data alm ostim m ediately.

Worst Case RPI Multicast Scenario

In the W orst Case scenario, the ow ner-controller sends the output data

just after the “reserved”netw ork slot has passed. In this case, the

output m odule does not receive data until the next available

netw ork slot.

Table 2.D show s the B est Case and W orst Case tim es for output data

sent from a controller to reach the output m odule:

Table 2.D

Best and Worst Case Times for Remote Output Data Transfer

Best case time Worst case time

Backplane/Networktransfer times (


39/250



Listen-Only Mode Any controller in the system can listen to the data from any I/Om odule (e.g. input data, “echoed”output data, or “echoed”diagnostic

inform ation) even if the controller does not ow n the m odule (i.e. it

does not have to hold the m odule’s configuration data to listen to the

m odule).

D uring the I/O configuration process, you can specify one of several

‘Listen’m odes in the C om m unication Form at field. For m ore

inform ation on Com m unication Form at, see page 6-6.

Choosing a ‘Listen’m ode option allow s the controller and m odule to

establish com m unications w ithout the controller sending any

configuration data. In this instance, another controller ow ns the

m odule being listened to.

IMPORTANT In the Listen-O nly m ode, controllers w ill continue to

receive data m ulticast from the I/O m odule as longas the connection betw een the ow ner and I/O

m odule is m aintained.

If the connection betw een ow ner and m odule is

broken, the m odule stops m ulticasting data and

connections to all ‘Listening controllers’are also

broken.


40/250



Multiple Ownersof Input Modules

Because ‘Listening controllers’lose their connections to m odules

w hen com m unications w ith the ow ner stop, the ControlLogix system

w ill allow you to define m ore than one ow ner for input m odules.

In the exam ple below , Controller A and Controller B have both been

configured to be the ow ner of the input m odule.

As soon as a controller receives its user program , it w ill try to establisha connection w ith the input m odule. W hichever controller’s

configuration data arrives first establishes a connection. W hen the

second controller’s data arrives, the m odule com pares it to its current

configuration data (the data received and accepted from the first

controller).

If the configuration data sent by the second controller m atches the

data sent by the first controller, that connection is also accepted. If any

param eter of the second configuration data is different from the first,

the m odule rejects the connection and the user is inform ed by an

error in the softw are or program atically via a ladder logic program .

The advantage of m ultiple ow ners over a ‘Listen m ode’connection is

that now either of the controllers can break the connection to the

m odule and the m odule w ill continue to operate and m ulticast data to

the system because of the connection m aintained by the other

controller.

IMPORTANT O nly input m odules can have m ultiple ow ners. Ifm ultiple ow ners are connected to the sam e inputm odule, they must maintain identicalconfiguration for that m odule.

Multiple Owners with Identical Configuration Data

Input ModuleConfigurationDataXxxxx

Xxxxx

Xxxxx


Xxxxx

Xxxxx

41056

Initial Configuration Initial ConfigurationController A Cont roller BInput

Con A Con B


41/250



Configuration Changes inan Input Module withMultiple Owners

You m ust be careful w hen changing an input m odule’s configuration

data in a m ultiple ow ner scenario. W hen the configuration data is

changed in one of the ow ners, for exam ple, Controller A, and sent to

the m odule, that configuration data is accepted as the new

configuration for the m odule. Controller B w ill continue to listen,

unaw are that any changes have been m ade in the m odule’s behavior.

To prevent other ow ners from receiving potentially erroneous data,

as described above, the follow ing stepsmust be followed w henchanging a m odule’s configuration in a m ultiple ow ner scenario

w hen online:

1. M ake the appropriate configuration data changes in the softw areand apply them .

W hen you apply new configuration data, the softw are alerts you

to inhibit the m odule (recom m ended if your are using amultiple controller system) or perform a bumpless reconfiguration (recom m ended if your are using a singlecontroller system). For a com plete explanation of a bum plessreconfiguration, see page P-2.

Multiple Owners with Changed Configuration Data in a Single Controller

41057Controller B is unaw are of changes made by Controller A


Zzzzz

Xxxxx


Xxxxx

Xxxxx

Initial Configuration Initial ConfigurationCont rol ler A Cont rol ler BInput

Con A Con B


42/250



2. Repeat step 1 for all ow ner controllers, m aking the exact samechanges in all controllers.

3. D isable the Inhibit box in each ow ner’s configuration, if youenabled this box in step 1.

Chapter Summary andWhat’s Next

In this chapter you learned about:

• ow nership and connections

• direct connections

• rack connections

• input m odule operation

• output m odule operation

M ove to Chapter 3,ControlLogix Standard D igital I/O M odule

Features.

IMPORTANT If all ow ner controllers have exactly the sam econfiguration after you have m ade changes, all thecontrollers w ill reestablish com m unication w ith theinput m odule.

If m ultiple controllers have different configuration

after you have m ade changes, only one controller(the first one to send changes to the m odule) w illreestablish com m unications w ith the input m odule.


43/250


Chapter 3

ControlLogix Standard Digital I/OModule Features

What This Chapter Contains This chapter describes devices com patible w ith ControlLogix I/O andfeatures that are specific to various m odules.

Determining InputModule Compatibility

ControlLogix digital input m odules interface to sensing devices anddetect w hether they are O N or O FF.

ControlLogix input m odules convert ac or dc O N /O FF signals from

user devices to appropriate logic level for use w ithin the processor.Typical input devices include:

• proxim ity sw itches

• lim it sw itches

• selector sw itches• float sw itches

• pushbutton sw itches


Determining Input M odule Compat ibil i t y 3-1

Det erm ining Out put M o dule Com pat ibil it y 3-2

Using Features Common to ControlLogix

Standard Digital I/O M odules

3-3

Using Features Specific to Standard InputModules

3-11

Using Features Specific to Standard OutputModules

3-12

Fault and Stat us Reporting Betw een InputM odules and Controllers

3-18

Fault and Status Reporting Betw een OutputM odules and Controller

3-19



44/250


3-2 ControlLogix Standard Digital I/O M odule Features

W hen designing a system using ControlLogix input m odules, youm ust consider:

• the voltage necessary for your application

•w hether you need a solid state device

• current leakage

• if your application should use sinking or sourcing w iring.

For m ore inform ation on com patibility of other Allen-BradleyCom pany products to C ontrolLogix input m odules, see the I/OSystem s O verview , publication CIG -2.1.

Determining Output

Module Compatibility

ControlLogix output m odules m ay be used to drive a variety of outputdevices. Typical output devices com patible w ith the C ontrolLogix

outputs include:

• m otor starters

• solenoids

• indicators

W hen designing a system :

• m ake sure that the C ontrolLogix outputs can supply thenecessary surge and continuous current for proper operation.

• m ake sure that the surge and continuous current are notexceeded. D am age to the m odule could result.

W hen sizing output loads, check the docum entation supplied w ith theoutput device for the surge and continuous current needed to operatethe device.

The ControlLogix outputs are capable of directly driving the

ControlLogix inputs. The exceptions are the ac and dc diagnosticinput m odules. W hen diagnostics are used a shunt resistor is requiredfor leakage current.

For m ore inform ation specifically on the com patibility of m otorstarters to ControlLogix output m odules, see Appendix D .

For m ore inform ation on com patibility of other Allen-BradleyCom pany products to C ontrolLogix output m odules, see the I/OSystem s O verview , publication CIG -2.1.


45/250


ControlLogix Standard Digital I/ O Modul e Features 3-3

Using Features Common toControlLogix StandardDigital I/O Modules

The follow ing features are com m on to all ControlLogix standarddigital I/O m odules:

Removal and Insertion Under Power (RIUP)

All ControlLogix I/O m odules m ay be inserted and rem oved from the

chassis w hile pow er is applied. This feature allow s greater availabilityof the overall control system because, w hile the m odule is beingrem oved or inserted, there is no additional disruption to the rest of thecontrolled process.

Module Fault Reporting

ControlLogix digital I/O m odules provide both hardw are and softw areindication w hen a m odule fault has occurred. Each m odule’s LED fault

indicator and RSLogix 5000 w ill graphically display this fault and

include a fault m essage describing the nature of the fault.

This feature allow s you to determ ine how your m odule has been

affected and w hat action should be taken to resum e norm al operation.

Fully Software Configurable

The RSLogix 5000 softw are uses a custom , easily understood interface

to w rite configuration. All m odule features are enabled or disabled

through the I/O configuration portion of the softw are.

You can also use the softw are to interrogate any m odule in the system

to retrieve

• serial num ber

• revision inform ation

• catalog num ber

• vendor identification

• error/fault inform ation

• diagnostic counters.

By elim inating such tasks as setting hardw are sw itches and jum pers,

the softw are m akes m odule configuration easier and m ore reliable.


46/250



Electronic Keying

Instead of plastic m echanical backplane keys, electronic keying allow s

the ControlLogix system to control w hat m odules belong in the

various slots of a configured system .

D uring m odule configuration, you m ust choose one of the follow ingkeying options for your I/O m odule:

• Exact M atch

• Com patible M atch

• D isable Keying

The options above are described later in this section.

W hen the controller attem pts to connect to and configure an I/Om odule (e.g. after program dow nload), the m odule com pares thefollow ing param eters before allow ing the connection andconfiguration to be accepted:

• Vendor

• Product Type

• Catalog N um ber

• M ajor Revision - Change that affects the m odule’s function or

RSLogix 5000 interface

• M inor Revision - Change that does not affects the m odule’s

function or RSLogix 5000 interface

The com parison is m ade betw een the keying inform ation p resent in

the I/O m odule and the keying inform ation in the controller’s

program . This feature can prevent the inadvertent operation of a

control system w ith the w rong m odule in the w rong slot.

Exact M atch

All of the param eters listed above m ust m atch or the inserted m odule

w ill reject a connection to the controller.


47/250



Compatible M atch

The C om patible M atch m ode allow s an I/O m odule to determ inew hether it can em ulate the m odule defined in the configuration sentfrom the controller.

W ith ControlLogix digital I/O m odules, the m odule can em ulate olderrevisions. The m odule w ill accept the configuration if theconfiguration’s m ajor.m inor revision is less than or equal to the

physical m odule’s revision.

For exam ple, if the configuration contains a m ajor.m inor revision of

2.7, the m odule inserted into the slot m ust have a firm w are revision of

2.7 or higher for a connection to be m ade.

TIP

W e recom m end using C om patible M atch w henever

possible. Rem em ber, though, the m odule w ill onlyw ork to the level of the configuration.

For exam ple, if a slot is configured for a m odule w ith

m ajor.m inor revision of 2.7 and you insert a m odule

w ith a m ajor.m inor revision of 3.1, the m odule w orks

at the 2.7 level despite having been previously

upgraded.

If possible, w e suggest you m ake sure configuration

is updated to m atch the revision levels of all I/O

m odules. Failure to do so m ay not prevent the

application from w orking but m ay defeat the

purpose of upgrading your m odules’revision levels.


48/250



Disable Keying

The inserted m odule attem pts to accept a connection to the controllerregardless of its type.

If keying is disabled, a controller m akes a connection w ith m ost

m odules of the sam e type as that used in the slot configuration. Forexam ple, if a slot is configured for a 1756-IA16I (standard input

m odule), and a 1756-IB16 (standard input m odule) is inserted into theslot, the controller established a connection because keying isdisabled.

A controller w ill not establish a connection if any of the follow ingconditions exist, even if keying is disabled:

• The slot is configured for one m odule type (e.g. input m odule)and a m odule of another type (e.g. output m odule) is inserted inthe slot.

• The m odule inserted into the slot cannot accept som e portion of

the configuration. For exam ple, if a standard input m odule isinserted into a slot configured for a diagnostic input m odule, thecontroller cannot m ake a connection because the m odulecannot accept/process the diagnostic configuration.

ATTENTION

!

B e extrem ely cautious w hen using the disablekeying option; if used incorrectly, this option canlead to personal injury or death, property dam ageor econom ic loss.


49/250



Using the SystemClock to Timestamp Inputs andSchedule Outputs

Controllers generate a 64-bit Coordinated System Tim e (CST) for their

respective chassis. The CST is a chassis-specific tim e that is notsynchronized w ith, or in any w ay connected to, the tim e generatedover ControlN et to establish a N U T, as described in Chapter 2.

You can configure your digital input m odules to access the C ST andtimestamp input data w ith a relative tim e reference (i.e. the value ofthe C ST) of w hen that input data changes state.

Timestamping for a Sequence of Events

The C ST can be used to establish a sequence of events occurring at aparticular input m odule point by tim estam ping the input data. To

determ ine a sequence of events, you m ust:

• Set the input m odule’s com m unications form at to: CST

Tim estam ped Input D ata

• Enable Change of state for the input point w here a sequencew ill occur (D isable CO S for all other points on the m odule)

IMPORTANT Because only one CST value is returned to thecontroller w hen any input point changes state, it is

recom m ended that you use tim estam ping on only

one inp ut point per m odule.

TIP If you decide to configure m ultiple input points forCO S, your m odule generates a unique C ST each tim e

any of those input points change state, as long as the

changes do not occur w ithin 500µS of each other.

If m ultiple input points configured for CO S change

state w ithin 500µs of each other, a single CST value

is generated for all, m aking it appear that they

changed at exactly the sam e tim e.


50/250



Timestamping In Conjunction w ith Scheduled Outputs

Tim estam ping can be used in conjunction w ith the scheduledoutputs feature so that after input data changes state and a tim estam poccurs, an output point w ill actuate at som e configured tim e in thefuture. You can schedule outputs up to 16 seconds into the future.

W hen you use tim estam ping of inputs and scheduled outputs, youm ust:

• choose a C om m unications Form at for each input and outputm odule that allow s tim estam ping. For m ore inform ation on

choosing a Com m unications Form at, see C hapter 6.

• have a controller in the sam e rack as both I/O m odules

• disable C hange of State for all input points on the input m oduleexcept the point being tim estam ped

TIP For scheduled outputs to w ork m ost effectively,rem em ber the follow ing:

• The tim e to schedule outputs to transition in thefuture m ust account for any controller, backplane

and netw ork delays.

• The I/O m odules m ust reside in the sam e rack asthe tim em aster.

For a detailed exam ple of how to w rite ladder logicto use these features, see A ppendix B.

8/20/2019 Digital IO Module Us

Digital IO Module User Man-Allen Bradley

Documents

Transcript of Digital IO Module User Man-Allen Bradley