1785 Um523 - en P PDF

ControlNet PLC 5 Programmable Controllers
Cat. No. 1785 L20C, L40C
User Manual
product icon
Important User Information
Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes, and standards. The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based on the examples shown in this publication. Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation, and Maintenance of Solid-State Control (available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication. Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Allen-Bradley Company, Inc., is prohibited. Throughout this manual, we use notes to make you aware of safety considerations:
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage or economic loss.
Attention statements help you to: identify a hazard avoid the hazard recognize the consequences Important: Identifies information that is critical for successful application and understanding of the product.
Table of Contents
Using This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
i i i ii iii iii
Installing Your ControlNet PLC 5 Processor . . . . . . . . . . .

Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling the Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying ControlNet PLC 5 Processor Components . . . . . . . . . . Setting the I/O Chassis Backplane Switches . . . . . . . . . . . . . . . . . Setting the I/O Chassis Configuration Plug . . . . . . . . . . . . . . . . . . Installing Keying Bands for the Processor . . . . . . . . . . . . . . . . . . Installing and Disposing of the Processor Battery . . . . . . . . . . . . . Selecting the DH+ Station Address of Channel 1A . . . . . . . . . . . . . Specifying the Serial Interface of Channel 0 . . . . . . . . . . . . . . . . . Selecting the ControlNet Network Address of Channel 2 . . . . . . . . Inserting/Removing the Processor into/from the I/O Chassis . . . . . Installing a Remote I/O Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a DH+ Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to a ControlNet Network . . . . . . . . . . . . . . . . . . . . . . Connecting a Programming Terminal . . . . . . . . . . . . . . . . . . . . . Selecting Appropriate Cables . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11 12 13 14 16 17 17 18 1 10 1 11 1 11 1 12 1 12 1 14 1 15 1 16 1 18
Planning to Use Your ControlNet PLC 5 Processor . . . . . .

Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding ControlNet I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding ControlNet I/O Mapping . . . . . . . . . . . . . . . . . . . . Using the ControlNet PLC 5 Processor in a ControlNet I/O System . Converting from a Non ControlNet Remote I/O System to a ControlNet I/O System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21 21 27 2 13 2 15
ii
Table of Contents
Configuring Your ControlNet System . . . . . . . . . . . . . . . . .

Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Matching the Processor Configuration with the ControlNet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Local Rack Characteristics . . . . . . . . . . . . . . . . . . . . . . . Editing ControlNet Node Information . . . . . . . . . . . . . . . . . . . . . . Editing ControlNet I/O Mapping . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31 32 33 34 36
Programming Your ControlNet System . . . . . . . . . . . . . . .

Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ControlNet Message Instructions . . . . . . . . . . . . . . . . . . . . Using the ControlNet I/O Transfer Instruction . . . . . . . . . . . . . . . . Using ControlNet Immediate Data Input and Output Instructions . . . Using Selectable Timed Interrupts with a Program on a ControlNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41 42 44 46 47
Monitoring and Troubleshooting Your ControlNet System

Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the General Status Indicators . . . . . . . . . . . . . . . . . . . . . . Using the ControlNet Status Indicators . . . . . . . . . . . . . . . . . . . . . Using the 6200 Programming Software to Monitor ControlNet Configuration and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
51 52 53 55
Processor Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Status File . . . . . . . . . . . . . . . . . . . . . . . . . . . .

S:0 S:2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S:3 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S:11 S:12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S:12 S:16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S:17 S:27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S:28 S:61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S:62 S:127 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A1 B1
B1 B2 B3 B4 B5 B6 B7
ControlNet Instruction Set . . . . . . . . . . . . . . . . . . . . . . . . .

ControlNet I/O Transfer Instruction . . . . . . . . . . . . . . . . . . . . . . . . Message Instructions on a ControlNet Network . . . . . . . . . . . . . . . Immediate Data I/O Instructions . . . . . . . . . . . . . . . . . . . . . . . . . .
C1
C1 C1 C2
ControlNet I/O Map Entry Status Words and Error Messages D 1

I/O Map Entry Status Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D1 D2
Preface
Using This Manual
Introduction
This manual describes how to install your processor as well as how to plan for, configure, and use the features of a PLC-5/20Ct or PLC-5/40Ct programmable controller that are unique to the ControlNett network. For detailed information on features that the PLC-5/20C or PLC-5/40C programmable controllers share with the PLC-5/20t and -5/40t processors, see the Enhanced and Ethernet PLC-5 Programmable Controllers User Manual, publication 1785-6.5.12.
More
Audience
The information in this manual is intended for engineers and technicians who are installing, programming, and maintaining a control system that includes a PLC-5/20C or PLC-5/40C programmable controller. You should have a background in control-system applications and a basic knowledge of: programmable real-time control systems the PLC-5R control system your operations required systems and applications
Contents
If you want to read about: Installing your ControlNet PLC 5 processor Setting switches Installing communication links Planning to use your ControlNet PLC 5 processor Understanding ControlNet I/O Using a ControlNet PLC 5 processor Using the 6200 Programming Software to configure your ControlNet system Editing your ControlNet configuration Editing ControlNet I/O mapping Programming your ControlNet system Monitoring and troubleshooting your ControlNet system Using the status indicators Monitoring the 6200 Programming Software configuration and status screens Processor specifications Processor status file ControlNet instructions ControlNet I/O map table entry status words and error messages
Go to: Chapter 1
Chapter 2
Chapter 3
Chapter 4 Chapter 5
Appendix A Appendix B Appendix C Appendix D
Using This Manual
Preface
Terminology
Term ControlNet network connection discrete I/O data transfer
Description communication architecture that allows the exchange of data between Allen Bradley Company, Inc. products and certified third party products opened communication path between two nodes on a ControlNet network type of data transfer in which single units of I/O have discrete relationships with values in the processor's data table; uses the processor's input and output image tables (I and O files); configured on a per node basis in the ControlNet I/O map table single data transfer on a ControlNet link cable that connects a ControlNet node to the trunk cable; integral part of 1786 taps table that you configure using the programming software to map data from an I/O chassis and other devices on the ControlNet network to particular data table file addresses collection of ControlNet nodes with unique network addresses in the range of 01 107; segments connected by repeaters make up a link; links connected by bridges make up a network one entry in the I/O map table that you configure using the programming software to map data from one I/O chassis or other device on ControlNet to particular data table file addresses node with the highest network address that can use scheduled time on a ControlNet link node with the highest network address that can use unscheduled time on a ControlNet link port that provides a temporary ControlNet network connection through an RJ 45 connector node's address on the ControlNet network single occurrence of the ControlNet Network Update Time (NUT) repetitive time interval in which data can be sent on the ControlNet network port of a physical device connecting to the ControlNet network that requires a network address in order to function on the network; a link may contain a maximum of 107 nodes type of data transfer in which blocks of data transferred to or from I/O modules use integer input and output data table files that you specify; cannot use the processor's input and output image tables (I and O files); scheduled transfers are configured in the ControlNet I/O map table, unscheduled transfers make use of ControlNet I/O Transfer (CIO) instructions device that controls the outputs of an adapter dual cable system that allows you to receive the best signal over a ControlNet network two port active physical layer device that reconstructs and retransmits all traffic that it hears on one ControlNet segment to another segment deterministic and repeatable transfers that are continuous and asynchronous to the ladder logic program scan trunkline section of ControlNet network with terminators at each end; a segment does not include repeaters; segments connected by repeaters make up a link component that connects products to the ControlNet trunk cable; a tap is required for each node and for each side of a repeater 75W resistor mounted in a BNC plug placed on each end of a ControlNet segment to prevent reflections from occurring at the ends of the cable bus or central part of the ControlNet cable system length of trunk cable between any two ControlNet taps non deterministic data transfers through ladder initiated communication or programming devices
frame drop cable I/O map table link map table entry maximum scheduled node maximum unscheduled node network access port (NAP) network address network update interval (NUI) network update time (NUT) node non discrete I/O data transfer
owner redundant media repeater scheduled transfers segment tap terminator trunk cable trunk cable section unscheduled transfers
ii
Preface Using this Manual
Conventions
This icon
More
A series like this
Any Menu
indicates that the current topic is discussed further in the publication(s) referenced indicates a keystroke procedure for you to follow to get to the correct screen or to complete a task using software
Fx
Text that shows what a terminal displays is shown like this: Press a key Text in square brackets indicates an actual key that you pressi.e., [F1] Text describing information that you must provide is italicizedi.e., filename
Related Publications
The 1785 PLC-5 programmable-controller, 6200 programming-software, and ControlNet documentation is organized into manuals according to the tasks that you perform.
The manual that you are currently reading
PLC 5 Processor Documentation
1785 Enhanced PLC 5 Processor System Overview Overview of processor functionality, system benefits, and operating features 1785 2.36
Enhanced & Ethernet PLC 5 Programmable Controllers User Manual How to configure, program, and operate your processor 1785 6.5.12
ControlNet PLC 5 Programmable Controllers User Manual How to install, configure, program, operate, and maintain your processor for ControlNet communication 1785 6.5.14
ControlNet PLC 5 Programmable Controllers Quick Start How to install and use a ControlNet processor in a typical system 1785 7.4
1785 PLC 5 Programmable Controllers Quick Reference Quick access to switches, status bits, indicators, instructions, SW screens 1785 7.1
For more information on 1785 PLC-5 programmable controllers or the above publications, contact your local Allen-Bradley Company, Inc. sales office or distributor.
iii
Using This Manual
Preface
PLC 5 Programming Software Documentation
PLC 5 Programming Software Supplement ConttrolNet Support Using the software to configure and monitor a ControlNet network 6200 6.4.20
PLC 5 Programming Software Instruction Set Reference Instruction execution, parameters, status bits and examples 6200 6.4.11
PLC 5 Programming Software Programming Creating/managing files, saving/restoring files, importing/exporting files creating/editing SFCs, creating/editing ladder 6200 6.4.7
PLC 5 Programming Software Software Configuration and Maintenance Installing software, defining data table files, configuring processor, checking status, clearing faults 6200 6.4.6
PLC 5 Programming Software I/O Configuration Configuring intelligent I/O modules 6200 6.4.12
For more information on PLC-5 programming software or the above publications, contact your local Allen-Bradley Company, Inc. sales office or distributor. For detailed information on different aspects of planning and installing your ControlNet network, see the following publications:
ControlNet Documentation
Publication ControlNet Cable System Component List ControlNet Cable System Planning and Installation Manual ControlNet Coax Tap Installation Instructions ControlNet Network Access Cable Installation Instructions ControlNet Repeater Installation Instructions Industrial Automation Wiring and Grounding Guidelines Publication Number AG 2.2 1786 6.2.1 1786 2.3 1786 2.6 1786 2.7 1770 4.1
iv
Chapter
Installing Your ControlNet PLC 5 Processor
Using This Chapter
If you want to read about: Completing the preliminary setup Checking the contents of the processor package Handling the processor Identifying the processor channels/connectors Setting the I/O chassis backplane switches Setting the I/O chassis configuration plug Installing keying bands for the processor Installing and disposing of the processor battery Selecting the Data Highway Plust (DH+t) station address of Channel 1A Specifying the serial interface for Channel 0 Selecting the ControlNet network address of Channel 2 Inserting/removing the processor into/from the I/O chassis Installing a remote I/O link Installing a DH+ link Connecting to a ControlNet network Connecting a programming terminal Selecting appropriate cables
Go to page: 12 12 13 14 16 17 17 18 1 10 1 11 1 11 1 12 1 12 1 14 1 15 1 16 1 18
More
For detailed information on installing chassis and adapters, see the Enhanced and Ethernet PLC-5 Programmable Controllers User Manual, publication 1785-6.5.12.
1-1
Chapter 1
Before You Begin
Before installing your ControlNet PLC-5 processor: 1. Complete the following: determine the proper environment configure the proper grounding route the conductors properly For detailed information on completing these tasks, see the Enhanced and Ethernet PLC-5 Programmable Controllers User Manual, publication 1785-6.5.12. 2. Check your processor package, and make sure that you have the following:
Processor ControlNet PLC 5R Programmable Controller, 1785 L20C or L40C
More
Contents of Tray y
1 1 4 2 or 4 2 or 4 2 1 1
Lithium Battery, 1770 XYC DIN connector cover Terminating resistors 150W Terminating resistors 82Wz g 3 pin connectors Keys y Battery cover with screw 1784 CP7 cable adapter for 1784 CP, CP5 cables
Documentation
ControlNet PLC 5 Programmable Controllers User Manual, publication 1785 6.5.14 ControlNet PLC 5 Programmable Controllers Release Notes, publication 1785 6 5 14 RN1 6.5.14 CSA Hazardous Location Approval Supplemental Information, publication AG 4 1 4.1 Enhanced and Ethernet PLC 5 Programmable Controllers User Manual, 6.5.12 Manual publication 1785 6 5 12 Guidelines for Handling Lithium Batteries, publication AG 5.4 Industrial Automation Wiring and Grounding Guidelines, publication 1770 4.1
Identified by four colored bands: brown, green, brown, and gold Two with a PLC 5/20C processor, four with a PLC 5/40C processor z Identified by four colored bands: gray, red, black, and gold
If any items are missing or incorrect, contact your local Allen-Bradley Company, Inc. sales office or distributor.
1-2
Chapter 1
Handling the Processor
Your processor is shipped in a static-shielded container to guard against electrostatic damage. Electrostatic discharge can damage integrated circuits or semiconductors in the processor if you touch backplane connector pins. It can also damage the module when you set configuration plugs or switches inside the module. Avoid electrostatic damage by observing the following precautions. Remain in contact with an approved ground point while handling the modulewear a properly grounded wrist strap. Do not touch the backplane connector or connector pins.
Wrist strap
19897
When not in use, keep the module in its static-shielded container.
1-3
Chapter 1
Identifying ControlNet PLC 5 Processor Components
Figure 1.1 and Figure 1.2 show the front panels of the ControlNet PLC-5 processors.
Figure 1.1 PLC 5/20C Processor Front Panel
Keyswitch selects processor mode ControlNet I/O Status Indicator (Green/Red) Channel 2 ControlNet Status Indicators (Green/Red) ControlNet Network Access Port (NAP) RJ45 connector Channel 2 ControlNet Redundant Media Ports BNC; dedicated Channel 0 Serial Port 25 pin D shell; supports standard EIA RS 232C and RS 423; is RS 422A compatible Use this port with ASCII or DF1 full duplex, half duplex master, and half duplex slave protocols. The port's default configuration supports processor programming: DF1 point to point one stop bit BCC error check 2400 bit/s no handshaking no parity Channel 1 Status Indicators (Green/Red) DH+ Programming Terminal Connection to Channel 1A 8 pin mini DIN Channel 1A 3 pin; dedicated DH+
Battery Status Indicator (Red) Processor RUN/FAULT Status Indicator (Green/Red) Force Status Indicator (Amber) Channel 0 Communication ACTIVE/FAULT Status Indicator (Green/Red)
Memory Module Space
Battery Compartment
Channel 0 is optically coupled (provides high electrical noise immunity) and can be used with most RS 422A equipment as long as: termination resistors are not used the distance and transmission rate are reduced to comply with RS 423 requirements
Channel 1B 3 pin; default is remote I/O scanner; configurable for: remote I/O scanner remote I/O adapter DH+ communication unused
1-4
Chapter 1
Figure 1.2 PLC 5/40C Processor Front Panel
Keyswitch selects processor mode ControlNet I/O Status Indicator (Green/Red) Channel 2 ControlNet Status Indicators (Green/Red) ControlNet Network Access Port (NAP) RJ45 connector Channel 2 ControlNet Redundant Media Ports BNC; dedicated
Battery Status Indicator (Red) Processor RUN/FAULT Status Indicator (Green/Red) Force Status Indicator (Amber) Channel 0 Communication ACTIVE/FAULT Status Indicator (Green/Red)
Channel 1 Status Indicators (Green/Red) DH+ Programming Terminal Connection to Channel 1A 8 pin mini DIN, parallel with 3 pin connectors of Channel 1A; use only when Channel 1A is configured for DH+ communications Channel 1A 3 pin; default is DH+; configurable for: remote I/O scanner remote I/O adapter DH+ communication unused Channel 1B 3 pin; default is remote I/O scanner; configurable for: remote I/O scanner remote I/O adapter DH+ communication unused
Channel 0 Serial Port 25 pin D shell; supports standard EIA RS 232C and RS 423; is RS 422A compatible Use this port with ASCII or DF1 full duplex, half duplex master, and half duplex slave protocols. The port's default configuration supports processor programming: DF1 point to point 2400 bps no parity one stop bit BCC error check no handshaking
Memory Module Space
Battery Compartment
Channel 0 is optically coupled (provides high electrical noise immunity) and can be used with most RS 422A equipment as long as: termination resistors are not used the distance and transmission rate are reduced to comply with RS 423 requirements
1-5
Chapter 1
Setting the I/O Chassis Backplane Switches
Set the I/O chassis backplane switches using a ball-point pen to set each switch. Important: Do not use a pencil because the tip can break off and short the switch.
Switch 1 ON OFF Always OFF Switches 4 OFF OFF ON ON 5 OFF ON OFF ON Last State Outputs of this I/O chassis remain in their last state when a hardware failure occurs. Outputs of this I/O chassis are turned off when a hardware failure occurs.
O F F
O 1 N 2 3 4 5 6 7 8

Addressing 2 -slot 1 -slot 1/2 - slot Not allowed EEPROM Transfer
ON OFF
Switches 6 OFF ON ON Switch 8 OFF ON 7 OFF ON OFF
EEPROM memory transfer to processor memory at powerup. EEPROM memory transfers to processor memory if processor memory not valid. EEPROM memory does not transfer to processor memory.
Processor Memory Protection Processor memory protection disabled. Processor memory protection enabled.
Regardless of this switch setting, outputs are turned off when any of the following occurs: processor detects a runtime error an I/O chassis backplane fault occurs you select Program or Test mode you set a status file bit to reset a local rack If an EEPROM module is not installed and processor memory is valid, the processor's PROC indicator blinks and the processor sets S:11/9, bit 9 in the major fault status word. To clear this fault, change the processor from Program mode to Run mode and back to Program mode. If the processor's keyswitch is set in Remote, the processor enters Remote Run mode after it powers up and has its memory updated by the EEPROM module. A processor fault (solid red PROC LED) occurs if processor memory is not valid. You cannot clear processor memory when this switch is on.
19309
1-6
Chapter 1
Setting the I/O Chassis Configuration Plug
Set the I/O chassis configuration plug as follows:
Y N
1.
Locate the chassis configuration plug (between the two left most slots of the chassis). Set the I/O chassis configuration plug. The default setting is N (not using a power supply module in the chassis).
2. USING A POWER SUPPLY MODULE IN THE CHASSIS? Y N Y N
Set Y when you install a power supply module in the chassis.
Set N when you use an external power supply.
Important: You cannot power a single I/O chassis with both a power supply module and an external power supply.
17075
Installing Keying Bands for the Processor
You receive plastic keying bands with each I/O chassis. Insert the keying bands as follows:
I/O Chassis Backplane Connector
Keying Bands (1771 RK)
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50 52 54 56
Install a keying band in the left most slot between the following pins: Use these numbers as a guide. 40 and 42 54 and 56
ATTENTION: A module inserted into a wrong slot could be damaged by improper voltages connected through the wiring arm. Use keying bands to prevent damage to the module.
12062
1-7
Chapter 1
Installing and Disposing of the Processor Battery

More
The 1770-XYC battery ships with the processor and requires special handling. For more detailed information on installing and disposing of the battery, see the Allen-Bradley Guidelines for Lithium Battery Handling and Disposal, publication AG-5.4.
ATTENTION: To maintain CSA certification for hazardous areas, do not substitute any other battery for the 1770-XYC.
Installing or Removing the Processor Battery Tip

You can insert or remove the battery without powering down the processor. If you do not want to lose your program, make sure that the processor is powered on when removing the battery.
To install or remove the battery, follow these steps: 1. Remove the thumb screw on the processors battery cover, remove the cover, and locate the battery. Install or remove the battery:
2.
To install the battery, slide the battery side connector into the processor side connector until you hear them snap.
To remove the battery, press the lever on the battery side connector and slide the connectors apart.
19331
Battery side connector Processor side connector
3.
Replace the battery cover, and secure the battery cover with the thumb screw. On the battery cover, write the date that you installed the last new battery.
4.
1-8
Chapter 1
Replacing the Battery Tip

You can insert or remove the battery without powering down the processor. If you do not want to lose your program, make sure that the processor is powered when replacing the battery.
Replace the lithium battery every year or when the BATT status indicator is red. For estimated battery lifetimes, see the table below:
Worst Case Battery Life Estimates Power Off 100% Power Off 50% 218 days 1.7 years 105 days 1.3 years 1.17 years 3.34 years 207 days 2.57 years
Processor PLC 5/20C PLC 5/40C
Temperature 60C 25C 60C 25C
Battery Duration 3.7 days 15 days 40 hours 10.8 days
The battery status indicator (BATT) warns you when the battery is low. These durations are based on the battery supplying the only power to the processor power to the chassis is off once the status indicator first lights.
Disposing of the Battery

Do not dispose of lithium batteries in a general trash collection when their combined weight is greater than or equal to 0.5 gram. A single 1770-XYC battery contains 0.65 grams of lithium. Check your state and local regulations that deal with the disposal of lithium batteries.
ATTENTION: Follow these precautions: Do not incinerate or expose the battery to high temperatures. Do not solder the battery or leads; the battery could explode. Do not open, puncture, or crush the battery. The battery could explode or toxic, corrosive, and flammable chemicals could be exposed. Do not charge the battery. An explosion may result, or the cell may overheat and cause burns. Do not short positive and negative terminals together. The battery will heat up.
1-9
Chapter 1
Selecting the DH+ Station Address of Channel 1A
To select the DH+ station address of Channel 1A, set the switches of assembly SW1.
Side View of PLC 5/40C Processor Switch Assembly SW1
Always OFF
Toggle pushed toward TOP OFF Toggle pushed toward BOTTOM ON
To select: DH+ Station Number
Set switch: 1 through 6
To: (See below)
Switch 7 is not used set it to OFF
DH+ Station Number 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 20 21 22 23 24 25 26 27 30 31 32 33 34 35 36 37
Switch 1 on off on off on off on off on off on off on off on off on off on off on off on off on off on off on off on off 2 on on off off on on off off on on off off on on off off on on off off on on off off on on off off on on off off 3 on on on on off off off off on on on on off off off off on on on on off off off off on on on on off off off off 4 on on on on on on on on off off off off off off off off on on on on on on on on off off off off off off off off 5 on on on on on on on on on on on on on on on on off off off off off off off off off off off off off off off off 6 on on on on on on on on on on on on on on on on on on on on on on on on on on on on on on on on
DH+ Station Number 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 60 61 62 63 64 65 66 67 70 71 72 73 74 75 76 77
Switch 1 on off on off on off on off on off on off on off on off on off on off on off on off on off on off on off on off 2 on on off off on on off off on on off off on on off off on on off off on on off off on on off off on on off off 3 on on on on off off off off on on on on off off off off on on on on off off off off on on on on off off off off 4 on on on on on on on on off off off off off off off off on on on on on on on on off off off off off off off off 5 on on on on on on on on on on on on on on on on off off off off off off off off off off off off off off off off 6 off off off off off off off off off off off off off off off off off off off off off off off off off off off off off off off off
1-10
Chapter 1
Specifying the Serial Interface of Channel 0
Specify RS-232C, RS-422A, or RS-423 communication for Channel 0 by setting the switches of assembly SW2.
Bottom View of PLC 5/40C processor Switch Assembly SW2 Front of Processor
Bottom View of PLC 5/20C Processor Switch Assembly SW2 Front of Processor
10
10
To Specify:
Set Switches: 1 ON 2 ON 3 ON 4 OFF 5 OFF 6 ON 7 ON 8 OFF 9 ON 10 OFF
Toggle pushed toward TOP OFF Toggle pushed toward BOTTOM ON
RS 232C
RS 422A
OFF
OFF
ON
OFF
OFF OFF
OFF
OFF
ON
OFF
RS 423
ON
ON
ON
OFF
OFF
ON
OFF OFF
ON
OFF
Selecting the ControlNet Network Address of Channel 2
Select your processors ControlNet network address by setting the two 10-digit rotary switches on the top of the processor.
20 10 00 90 80 70 60 30 40 50 0 9 8 NET ADDRESS 7 6 1 2 3 4 5
Network address 01 is shown
Tip
For optimum throughput, assign addresses to your ControlNet nodes in a sequential order starting with 01 for the controlling processor.
You can select from as many as 99 network addresses (from 01 to 99) for a processor on a ControlNet link. 00 is invalid.
1-11
Chapter 1
Inserting/Removing the Processor into/from the I/O Chassis
To insert/remove the processor into/from the chassis, do the following:

ATTENTION: Make certain that power to the chassis is off before inserting or removing the processor.
Locking Bar Ejector Tab
To insert a processor into the chassis: 1. Lift the locking bar and the ejector tab. 2. Slide the processor into the left most slot of the I/O chassis. 3. Press down on the ejector tab, and then close the locking bar over the processor. To remove a processor from the chassis: 1. 2. 3. 4. Save processor memory. Remove power to the processor resident chassis. Disconnect all cables from the processor's ports. Lift the locking bar and the ejector tab, and then slide the processor from the chassis.
19898
Card Guides
Installing a Remote I/O Link

Trunk cable/drop cable considerations: When using a trunk cable/drop cable configuration, use 1770 SC station connectors and follow these cable length guidelines: trunk cable length depends on the communication rate of the link; see Table 1.A drop cable length 30.4 m (100 cable ft) maximum Important: When using a trunk cable/ drop cable configuration, set your communication rate to 57.6kK bit/s.
Install a remote I/O link using 1770-CD cable and either a daisy-chain or trunk-cable/drop-cable configuration. Verify that your systems design plans specify cable lengths within allowable measurements. Important: The maximum cable length for remote I/O depends on the transmission rate. Configure all devices on a remote I/O link to communicate at the same rate.
Table 1.A Correct Cable Length Based on Communication Rate
A remote I/O link using this communication rate: 57.6K bit/s 115.2K bit/s 230.4K bit/s Cannot exceed this cable length: 3,048 m (approximately 10,000 ft) 1,524 m (approximately 5,000 ft) 762 m (approximately 2,500 ft)
More
For more information about designing trunk cable/drop cable configurations, see the Data Highway/Data Highway Plus/Data Highway II/Data Highway 485 Cable Installation Manual, publication 1770 6.2.2.
For proper operation, terminate both ends of a remote I/O link by using the external resistors shipped with the programmable controller. Use either a 150W or 82W terminator.
1-12
Chapter 1
The maximum number of Use this resistor rating: physical devices that you can connect on the link is: logical rack numbers that you can scan on the link is:
If your remote I/O link: Operates at 230.4K bit/s Operates at 57.6K or 115.2K bit/s, and no devices listed below are linked Scanners 1771 SN; 1772 SD, SD2; 1775 SR, S4A, S4B; 6008 SQH1, SQH2 Adapters Miscellaneous 1771 AS; 1771 ASB (Series A Only); 1771 DCM 1771 AF
82W
32
16
Connects to any device listed below: Scanners 1771 SN; 1772 SD, SD2; 1775 SR, S4A, S4B; 6008 SQH1, SQH2 Adapters Miscellaneous 1771 AS; 1771 ASB (Series A Only); 1771 DCM 1771 AF
150W
16
16
Operates at 57.6K or 115.2K bit/s, and you do not require over 16 physical devices
You can install a remote I/O link two ways: trunk cable / drop cable from the drop cable to the connector screw terminals on the remote I/O connectors of the processor daisy chain to the connector screw terminals on the remote I/O connectors of the processor and then to the remote I/O screw terminals of the next remote I/O device To connect remote I/O cable: 1. Run the 1770 CD cable from the processor to each remote I/O adapter module or processor in the remote I/O system. 2. Connect the signal conductor with blue insulation to the 3 pin connector terminal labeled 1 on the processor and to each remote I/O adapter module (or PLC 5 adapter) in the remote I/O system. 3. Connect the shield drain wire to the center terminal of the 3 pin connector. 4. Connect the signal conductor with clear insulation to the 3 pin connector terminal labeled 2. 5. Tie wrap the remote I/O network cable to the chassis to relieve strain on the cable. 6. Terminate the remote I/O link by connecting an external terminator resistor between the remote I/O terminals labeled 1 and 2. 1770 CD To another I/O link device PLC 5/40C Processor Blue Shield Clear 1770 CD PLC 5/20C Processor
Blue Shield Clear
82 or 150 resistor Terminate both ends of a remote I/O link
1-13
Chapter 1
Installing a DH+ Link
Use 1770-CD cable to connect the processor to a DH+ link. Follow these guidelines while installing DH+ communication links: do not exceed these cable lengths: - trunk-cable length3,048 m (approximately 10,000 cable-ft) - drop-cable length30.4 m (approximately 100 cable-ft) do not connect more than 64 stations on a single DH+ link
Use the 3 pin connector on the processor to connect a DH+ link. The connector's port must be configured to support a DH+ communication link. You can install a DH+ link two ways: trunk cable/drop cable from the drop cable to the connector screw terminals on the DH+ connectors of the processor daisy chain to the connector screw terminals on the DH+ connectors of the processor To make connections: 1. Connect the signal conductor with clear insulation to the 3 pin connector terminal 1 at each end of each cable segment. 2. Connect the shield drain wire to the center terminal of the 3 pin connector at both ends of each cable segment. 3. Connect the signal conductor with blue insulation to the 3 pin connector terminal 2 at each end of each cable segment. Clear Shield Blue
PLC 5/40C Processor
PLC 5/20C Processor
More
For more information, see the Data Highway/Data Highway Plus/Data Highway II/Data Highway 485 Cable Installation Manual, publication 1770 6.2.2. 82W or 150W resistor
Clear Shield Blue
82 or 150W resistor
19339
1-14
Chapter 1
Connecting to a ControlNet Network
Connect a ControlNet PLC-5 processor to a ControlNet network via a tap with a 1-m (39.4-in) drop cable. Four taps are available from Allen-Bradley Company, Inc.:
Straight T tap Straight Y tap Right angle T tap Right angle Y tap
Tip
We recommend that you use a tap with a straight connector 1786 TPS or 1786 TPYS when you attach a ControlNet PLC 5 processor to a ControlNet network.
1786 TPS
1786 TPYS
1786 TPR
1786 TPYR
Important: ControlNet taps contain passive electronics and must be purchased from Allen-Bradley Company, Inc. for the network to function properly. After terminating your segments, you connect your node to the network.
Remove the tap's dust cap located on the straight or right angle connector) and set it aside. If your network supports: nonredundant media redundant media Connect the tap's straight or right angle connector: to the channel A connector on the processor channel B is not used from trunk cable A to channel A on the processor and from trunk cable B to channel B on the processor
BATT BATT
Nonredundant media A
CH 0
Redundant media A B
CH 0
Allen Bradley Company, Inc. recommends using channel A for nonredundant media.
More
For detailed information on planning and installing your ControlNet system, see the following publications:
Publication ControlNet Cable System Component List ControlNet Cable System Planning and Installation Manual ControlNet Coax Tap Installation Instructions ControlNet Network Access Cable Installation Instructions ControlNet Repeater Installation Instructions Industrial Automation Wiring and Grounding Guidelines Publication Number AG 2.2 1786 6.2.1 1786 2.3 1786 2.6 1786 2.7 1770 4.1
1-15
Chapter 1
Connecting a Programming Terminal
You can connect a programming terminal to a ControlNet PLC-5 processor via a: DH+ connection serial channel ControlNet connection
DH+ Connection
To attach a programming terminal to a ControlNet PLC 5 processor using a DH+ connection: If you use this card to access a DH+ link: 1784 PCMK 1784 KT, KT2 Use cable: G 1784 PCM6 G 1784 PCM5 with a 1784 CP7 adapter G 1784 CP6 G 1784 CP6 with a 1784 CP7 adapter G 1784 CP8 adapter 1784 CP13
1784 KTx, KTxD
BATT
CH 0
Programming Terminal DH+ Link
PLC 5/20C Processor
Programming Terminal DH+ Link
PLC 5/40C Processor
Serial Channel
To program the processor using Channel 0, configure the channel for RS 232C using DF1 point to point protocol.
If your programming terminal has a: 9 pin serial port 25 pin serial port
BATT
Use cable: 1784 CP10 1784 CP11
CH 0
Programming Terminal
Programming Terminal
PLC 5/20C Processor
PLC 5/40C Processor
1-16
Chapter 1
ControlNet Connection
!
ATTENTION: Do not connect the same communication card to both the NAP and a tap on the ControlNet network.
You can connect programming devices to a ControlNet network through: the ControlNet network access cable (1786-CP) a tap on a ControlNet network
Using 1784 KTC or KTCx communication card and NAP
BATT
Using 1784 KTCx communication card on coax media Programming Terminal
Programming Terminal 1784 KTC or KTCx 1786 CPy
BATT
1784 KTCx
CH 0
CH 0
ControlNet Network
PLC 5/40C (or 5/20C) Processor
ControlNet Network
PLC 5/40C (or 5/20C) Processor
Using 1770 KFC communication interface on coax media Programming Terminal Serial Connection
CH 0 BATT
Using 1770 KFC communication interface and NAP Programming Terminal Serial Connection 1770 KFC 1786 CPy
BATT
CH 0
1770 KFC PLC 5/40C (or 5/20C) Processor PLC 5/40C (or 5/20C) Processor
ControlNet Network
ControlNet Network
Shown with redundant media The network access cable (1786 CP) can be plugged into any ControlNet product's NAP to provide programming capability on the ControlNet network. A programming terminal connected through this cable is counted as a node and must have a unique address.
ATTENTION: Use the 1786-CP cable when connecting a programming terminal to the network through a NAP. Using a commercially available RJ-style cable could result in network failure.
1-17
Chapter 1
Selecting Appropriate Cables
This section lists information about: serial cables DH+ programming cables remote I/O cables ControlNet cables For more information about cables, see the Enhanced and Ethernet PLC-5 Programmable Controllers User Manual, publication 1785-6.5.12.
More
Serial Cables
You can make your own serial cables or purchase them from Allen-Bradley Company, Inc. The side label of the processor shows the following table, which lists Channel 0 (serial port) pin assignments.
Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 NOT USED CTS.IN NOT USED The shading indicates that the pin is reserved. NOT USED DCD.IN NOT USED RS 232C C.GND TXD.OUT RXD.IN RTS.OUT CTS.IN DSR.IN SIG.GND DCD.IN RS 422A C.GND TXD.OUT RXD.IN RTS.OUT+ CTS.IN+ DSR.IN SIG.GND DCD.IN RS 423 C.GND TXD.OUT RXD.IN RTS.OUT CTS.IN DSR.IN SIG.GND DCD.IN Pin 14 15 16 17 18 19 20 21 22 23 24 25 NOT USED NOT USED DSR.IN DTR.OUT NOT USED NOT USED NOT USED DTR.OUT RTS.OUT DTR.OUT NOT USED DTR.OUT NOT USED RXD.IN+ REC COM RS 232C NOT USED RS 422A TXD.OUT+ RS 423 SEND COM
This processors serial port can support these configurations:

Digital Interface RS 232C RS 422A (compatible) RS 423 Maximum Cable Length 15 m (approximately 50 ft) 61 m (approximately 200 ft) 61 m (approximately 200 ft)
1-18
Chapter 1
Important: Follow these guidelines: When Channel 0 is configured for RS-422A compatibility, do not use terminating resistors anywhere on the link. When Channel 0 is configured for RS-422A (compatible) and RS-423, do not go beyond 61 m (approximately 200 ft). This distance restriction is independent of the transmission rate.
DH+ Programming Cables

When using this communication card: 1784 KT, KT2 1784 KL, KL/B 1784 KTK1 1784 KTx, KTxD 1784 PCMK Use this cable: 1784 CP6 1784 CP with 1784 CP7 adapter 1784 CP8 adapter 1784 CP5 with 1784 CP7 adapter 1784 CP13 1784 PCM6 1784 PCM5 with 1784 CP7 adapter
Remote I/O Cables

Use 1770-CD or cable for remote I/O. See page 1-12 for more information.
ControlNet Cables
Several types of RG-6 quad-shield cable may be appropriate for your ControlNet installationdepending on the environmental factors associated with your application and installation site.
1-19
Chapter 1
The following ControlNet cable system components are available from the Allen-Bradley Company, Inc.:
Itemx ControlNet Coax Tool Kit Coax Tap Kit Right angle T tap Straight T tap Right angle Y tap Straight Y tap High voltage ac & dc Low voltage dc Standard PVC CM CL2 Barrel (plug to plug) BNC/RG 6 plug BNC Connectors Bullet (jack to jack) Isolated bulkhead (jack to jack) Terminators (BNC 75)
x
Cat. No. 1786 CTK 1786 TPR 1786 TPS 1786 TPYR 1786 TPYS 1786 RPT 1786 RPTD 1786 RG6 1786 CP 1786 BNCP 1786 BNC 1786 BNCJ 1786 BNCJI 1786 XT
Repeaters RG 6 Quad Shield Cable
ControlNet Network Access Cable 3.05 m (10 ft)
For a complete list of ControlNet cable system components that are available from Allen Bradley Company, Inc. and other sources, see the ControlNet Cable System Component List, publication AG 2.2.
Important: Install all wiring for your ControlNet system in accordance with the regulations contained in the National Electric Code (or applicable country codes), state codes, and applicable municipal codes. For detailed information on ControlNet cabling, see the following:
More
Publication ControlNet Cable System Component List ControlNet Cable System Planning and Installation Manual ControlNet Coax Tap Installation Instructions ControlNet Network Access Cable Installation Instructions ControlNet Repeater Installation Instructions Industrial Automation Wiring and Grounding Guidelines
Publication Number AG 2.2 1786 6.2.1 1786 2.3 1786 2.6 1786 2.7 1770 4.1
1-20
Chapter
Planning to Use Your ControlNet PLC 5 Processor
Using This Chapter
If you want to read about: Understanding ControlNet I/O Understanding ControlNet I/O mapping Using the ControlNet PLC 5 processor in a ControlNet I/O system Converting from a remote I/O system to a ControlNet I/O system
Go to page: 21 27 2 13 2 15
Understanding ControlNet I/O
The ControlNet system is designed to: provide high-speed, repeatable, deterministic I/O transmission allow control and message information to co-exist on the same physical media make sure that I/O data transfers are not affected by - programming-terminal message activity - inter-PLC processor message activity on the network
Scheduled Data Transfer Operations on a ControlNet Network

ControlNet scheduled data transfer on a PLC-5/20C or -5/40C processor: is continuous transmits asynchronous to the ladder-logic program scan occurs at the actual rate displayed on the 6200 Programming Software ControlNet I/O Mapping (Monitor) screen in the Act Net Pckt Time (ms)Actual Network Packet Timefield In scheduled discrete I/O data transfer, for example, between logic scansi.e., during housekeepingthe following updates occur: the gathered input image is moved from a private memory buffer to the processors input-image file for use during the next logic scan the data from the output-image file is put into a private memory buffer and is sent during the next scheduled communication
2-1
Chapter 2
A similar method is used for all scheduled data-transfer operations.
Scheduled Data Transfers
Housekeeping
Private Memory Buffers
Data Update
Data Table Files Logic Scan Program Scan
Scheduled Data Transfer
The following scheduled data-transfer operations are supported by the PLC-5/20C and -5/40C processors on a ControlNet network:
Table 2.A ControlNet Scheduled Data Transfer Operations
Operation Discrete I/O Data Transfer Description Performed in a deterministic and repeatable manner asynchronous to and independent of the ladder logic program scan. You configure all ControlNet discrete I/O data transfers on a per node basis in the I/O map table.x Handled with the same priority as discrete I/O data transfer. You can update analog data without using block transfer instructions in ladder programs. You do this by including non discrete I/O data transfer configurations in the I/O map table. This data is updated in the buffers and data table files between logic scans in the same manner as that used in discrete I/O data transfer.x Allows the controlling" processor at network address 01 to communicate with other ControlNet processors on the ControlNet network with the same priority as that of the discrete and non discrete I/O data transfers discussed above.x
Non discrete I/O Data Transfer
Peer to peer Communication
While scheduled data transfer is asynchronous to program scanning, all data is presented synchronously to the processor and output buffers during housekeeping.
2-2
Chapter 2
Unscheduled Data Transfer Operations on a ControlNet Network

The ControlNet network allows you to use unscheduled messaging when deterministic delivery is not required. Unscheduled operations include: unscheduled non-discrete I/O data transfersthrough ControlNet I/O Transfer (CIO) instructions peer-to-peer messagingthrough Message (MSG) instructions messaging from programming devices The ControlNet system places your scheduled transfers in the first part of each Network Update Interval (NUI), time is automatically reserved for network maintenance, and unscheduled transfers are performed during the time remaining in the interval.
One occurrence of the NUT is a NUI
You reserve a specific amount of time for all scheduled operations
The system reserves time for network maintenance
. . .

Any time remaining is used for unscheduled operations
. . .
Unscheduled messaging on a ControlNet network is non-deterministic. Your application and your configurationnumber of nodes, application program, NUT, etc.help determine how much time there is for unscheduled messaging. Important: The ControlNet network reserves time for at least one unscheduled transfer per NUI.
2-3
Chapter 2
Table 2.B ControlNet Unscheduled Data Transfer Operations

Operation Description Features As many as 32 1771 READ and/or 1771 WRITE CIOs can be active at a timex A minor fault is set when 32 1771 READ and/or 1771 WRITE CIOs are active at a time You cannot use CIO instructions to read or write blocks of data from or to 1794 Flex I/O modules; but you can use these instructions to configure 1794 features listed in the Description" column As many as 8 1794 Flex I/O CIOs can be active at a timex A minor fault is set when 8 1794 Flex I/O CIOs are active at a time Any transfer initiated from a Processor Input Interrupt (PII) or Selectable Timed Interrupt (STI) program suspends execution of the program scan until the transfer is completed Important: This can extend your program scan by ten's of ms. No transfer is initiated when the processor is in Program mode Transfers that have been running with the .CO bit set automatically restart on the Program to Run transition when the Continue Last step bit is set and the data table has not changed A transfer has a maximum size of 64 words Only the processor owner" of an adapter can send or receive transfers to or from any of that adapter's modules See pages 4 4 and C 1 for more information. As many as 32 ControlNet MSGs can be active at a timex A minor fault is set when 32 ControlNet MSGs are active at a time All messages have the same priority No message is initiated when the processor is in Program mode Messages that have been running with the .CO bit set automatically restart on the Program to Run transition when the Continue Last step bit is set and the data table has not changed Each message has a maximum size of 1000 elements See pages 4 2 and C 1 for more information. Non discrete Perform ladder initiated unscheduled non discrete I/O data transfers on a ControlNet network by using ControlNet I/O Transfer (CIO) instructions. I/O Data The data type for these transfers (CT) has the following information: Transfer Command: CIO 1771 READ reads data from a 1771 non discrete I/O module Instructions 1771 WRITE writes data to a 1771 non discrete I/O module 1794 FAULT ACTION 1794 IDLE ACTION 1794 CONFIG DATA changes the action a module takes when it faults changes the action a module takes when it is idle changes a module's configuration data
1794 SAFE STATE DATA changes a module's safe state data Data table address in source processor Size of message in words Network address of destination node Slot of destination module Port number set to 2 for the ControlNet network Flags: .TO forces a transfer to time out .EW .CO .ER .DN .ST indicates that the transfer is waiting for an open connection transfer is made continuously in Run mode indicates that the transfer was terminated due to an error indicates that the transfer was made without error indicates that the transfer was started
.EN indicates that the transfer instruction is enabled Error code indicates the error when the .ER bit is set Done length indicates the number of words transferred Peer to peer You can use ControlNet message (MSG) instructions and the data type MG to Messaging create unscheduled messages that are initiated by one ControlNet PLC 5 processor and sent to another ControlNet PLC 5 processor. The MG data type for the ControlNet instruction has the following information: MSG Instructions Command PLC 5 TYPED READ or PLC 5 TYPED WRITE Data table address in source processor Size of message in elements Network address of destination processor Data table address in destination processor Port number set to 2 for the ControlNet network Flags: .TO forces a message to time out .EW .CO .ER .DN .ST indicates that the message is waiting for an open connection message is sent continuously in Run mode indicates that the message was terminated due to an error indicates that the message was sent without error indicates that the message was started
.EN indicates that the message instruction is enabled Error code indicates the error when the .ER bit is set
2-4
Chapter 2
Operation
x
Description
Features
Because connections are opened and closed as needed, more can exist in a program as long as no more than this number are active at one time.
Using I/O Forcing Operations

ControlNet I/O forcing occurs in the same way as remote I/O forcing in the PLC-5/20 and -5/40 processors. The processor performs the forcing and transmits the forced data to the output- and input-image tables. You can force any discrete I/O data placed in the I/O image; however, forcing of non-discrete I/O data is not supported. For detailed information on forcing, see PLC-5 Programming Software Configuration and Maintenance, publication 6200-6.4.6.
More
Using Immediate Data Transfer Operations

ControlNet Immediate Data I/O transfersImmediate Data Input (IDI) and Immediate Data Output (IDO)perform similarly to the remote-I/O supported immediate I/O transfersImmediate Input (INN) and Immediate Output (IOT)which the ControlNet system also supports. The logic scan is temporarily interrupted while the most recent state of one discrete input or output word is read from or written to the private memory buffer.
2-5
Chapter 2
Table 2.C ControlNet Immediate Data Transfer Operations

Instructions Immediate I/O ControlNet and Remote I/O 001 ( IIN ) 001 ( IOT ) ControlNet Immediate Data I/O IDI IMMEDIATE DATA INPUT Data file offset 232 Length 10 Destination N11:232 IDO IMMEDIATE DATA OUTPUT Data file offset 175 Length 24 Source N12:175 Description In the case of an IIN, the most recent copy of the specified input word secured in the last discrete I/O data transfer from the corresponding I/O chassis is used. This value is moved from the private memory buffer to the working data table and is used in all subsequent ladder instructions. This data could be as old as the time taken since the last asynchronous I/O update, and it may not actually reflect the latest state of the input word. In the case of an IOT, the current state of the specified output word is copied to the private memory buffer and is used on the next output update to the I/O chassis. The actual change is not communicated until the next asynchronous I/O transfer. Only 1 word of I/O data can be updated per instruction. The ControlNet Immediate Data I/O instructions work in much the same way as the immediate I/O instructions. During an input instruction, the most recent data is copied from the private memory buffer to a data table address that you specify. In the case of an output instruction, the data is copied from an area that you specified to the private memory buffer and sent on the next I/O update. As many as 64 words can be transferred per instruction. Important: In most cases, you should set the Data file offset and the Source of an IDO or the Data file offset and the Destination of an IDI to the same address. See page 4 6 for more information on this and other aspects of using ControlNet IDI and IDO instructions.
2-6
Immediate Data Transfer Private Memory Buffers Data Table Files Logic Scan Program Scan
Data Update Housekeeping
ControlNet Data Transfer = NUI = Scheduled Data Transfer = Unscheduled Data Transfer
Chapter 2
Understanding ControlNet I/O Mapping
All scheduled data transfers must be mapped on a ControlNet network. You specify where I/O data is to be read from or written toi.e., mapped. You do this and establish the relationship between processors, I/O adapters, and data-table file addresses by creating and maintaining an I/O map table. An I/O map-table entry is required for each scheduled data transfer. The map table is stored in the configuration section of memory and is not accessible by your application program. Using the 6200 PLC-5 Programming Software, you can automatically configure and map nodes attached to your ControlNet I/O. See Chapter 3 for information on ControlNet automatic configuration and I/O mapping.
Reserving Space for Non ControlNet I/O

Non-ControlNet processor-resident local I/O and remote-I/O devices can only use fixed I/O image locations based on rack number for discrete I/O data transfer, while discrete I/O data transfer between ControlNet nodes can be mapped to any unused location in the I/O image tables. Before mapping your ControlNet I/O, therefore, you should configure any processor-resident local I/O and any remote I/O racks on non-ControlNet channels. This allows the 6200 PLC-5 Programming Software to reserve input- and output-image space for all non-ControlNet processor-resident local I/O and remote-I/O chassis.
Processor Resident Local I/O

If you first configure processor-resident local I/O on your processor, the 6200 PLC-5 Programming Software reserves processor-resident local chassis input- and output-image space starting at offset 0 in both files. The following table shows the default number of input and output words automatically reserved by the 6200 PLC-5 Programming Software for the different sizes and addressing modes of processor-resident local I/O:
Addressing Mode 2 Slot 1 Slot 1/2 Slot 4 Slots 8 8 8 Number of Words Reserved 8 Slots 12 Slots 16 Slots 8 8 8 8 16 16 16 24 32
Important: ControlNet I/O cannot map into any part of a rack number used by the processor-resident rack.
2-7
Chapter 2
Remote I/O
The following table shows the default number of input and output words reserved by the 6200 PLC-5 Programming Software for the different sizes and addressing modes of non-ControlNet remote I/O if you first configure non-ControlNet remote I/O on your processor:
Addressing Mode 2 Slot 1 Slot 1/2 Slot 4 Slots 2 4 8 Number of Words Reserved 8 Slots 12 Slots 16 Slots 4 6 8 8 12 16 16 24 32
The 6200 PLC-5 Programming Software reserves non-ControlNet remoteI/O output- and input-image space according to these guidelines: It does not overlap processor-resident local I/O reserved image space It addresses input- and output-image space offset in octal from - 00-37for the PLC-5/20C processor - 00-177for the PLC-5/40C processor The output-image offset value in the I/O map corresponds to the first slot of the referenced chassisi.e., in a 4-slot chassis set for 1-slot addressing, the corresponding output-image offset of O:10 would map the words O:10, O:11, O:12, and O:13 to slots 0, 1, 2, and 3 respectively The input-image offset corresponds to the first slot in the referenced rack, and the offset location of the input modules in that rack corresponds to the same offset in the image tablei.e., if a chassis set for 1-slot addressing has an input-image offset of I:10 and an input module in slot 3 (of 0-7), the word that corresponds to that input module would be I:10 + 3, or I:13
2-8
Chapter 2
Mapping ControlNet Data Transfer

The ControlNet I/O map table can contain up to 64 entries. Each maptable entry corresponds to one transfereither input or outputof data between the ControlNet processor and an I/O rack, an I/O module, or another ControlNet processor.
Table 2.D Number of ControlNet I/O Map Table Entries Required
Data Transfer Type 1771 Discrete I/O Data Transfer 1771 Non discrete I/O Data Transfer 1794 Discrete and Non discrete I/O Data Transfer ControlNet PLC 5 Peer to peer Communication Number of Entries Required 1 per adapter 1 or 2 per module 2 per adapter 1 per message
Table 2.E Files That You Configure with the I/O Map for Scheduled I/O Usage
File Status File Data Input File (DIF) Data Output File (DOF) Default Configuration File Description User specified integer data table file containing status information about all of the ControlNet network's scheduled I/O map table entries. Each entry has a status file offset field pointing to three status words associated with the entry. User specified integer data table file with a maximum of 1000 words. This space is used for both non discrete input data and peer to peer input over the ControlNet network. Scheduled peer to peer inputs can also use the input image file. User specified integer data table file with a maximum of 1000 words. This space is used for both non discrete output data and peer to peer output over the ControlNet network. Scheduled peer to peer outputs can also use the output image file. User specified integer data table file used to store non discrete I/O data transfer configuration data when the automatic mapping feature is used.
Table 2.F ControlNet I/O Map Table Entry Fields

Map Table Entry Field Node and Slot/Message Numbers Description This is the entry's network location, currently defined as node.slot/message. The node value is the ControlNet network address of the destination device. The slot/message value takes on different meanings with the different communication options: 1771 and 1794 discrete I/O data transfer the slot value does not apply because the mapping granularity is based on the physical chassis 1771 non discrete I/O data transfer 0 15, the slot number is always the physical slot location inside the 1771 chassis regardless of addressing mode within the chassis 1794 non discrete I/O data transfer 0 7, the slot number is always the physical location in the 1794 system peer to peer communication 1 16, the message number represents one of sixteen scheduled peer messages available per processor; and it must be the same for both processors involved Module/Message Type This allows you to specify the module type or peer to peer message type Peer Out or Peer In in offline and online programming. It also determines how the map table entries are configured for the different modules and peer to peer messages. You set this to the maximum time allowed for the network to update the requested data. This read only field displays the actual time it takes for the network to update the requested data.
Expected Network Packet Time (ENPT) Actual Network Packet Time (ANPT)
2-9
Chapter 2
Map Table Entry Field Input File and Size
Description This is the offset in the input file where the data is to be stored and the number of words to be received from the input device. For discrete I/O data transfer, the offset is into the input image table; for non discrete I/O data transfer or peer to peer communication with another ControlNet processor, the offset is into the Data Input File entered on the ControlNet configuration screen. Scheduled peer to peer inputs can also use the input image file. This is the offset in the output file where the data is located and the number of words of the output transfer. For discrete I/O data transfer, the offset is into the output image table; for non discrete I/O data transfer or peer to peer communication with another ControlNet processor, the offset is into the Data Output File (DOF) entered on the ControlNet configuration screen. Scheduled peer to peer outputs can also use the output image file. This is an offset in a status file that points to three words of information on the status of this map table entry. Used only in 1771 non discrete I/O data transfer and 1794 configurations, this is the offset in a configuration file where configuration information needed for this node is located and the size in words of the information.
Output File and Size
Status File Offset Configuration File and Size
Discrete I/O Data Transfer Mapping

Regardless of the type of I/Oe.g., 1771, 1794all ControlNet discrete I/O data is stored within the processors I/O image files according to the corresponding I/O map-table entry. Any status information transferred along with the I/O data is stored in a separate status file that you specify during configuration.
Non discrete I/O Data Transfer Mapping

All ControlNet non-discrete I/O data is stored in integer files that you specify in a ControlNet configuration screen. The ControlNet processor supports two distinct image files; both are integer data-table files that you specify: Data Input File (DIF) Data Output File (DOF) Each map-table entry for a non-discrete I/O data transfer defines an offset into the DIF or DOF where the data is stored. Using separate data-table files for non-discrete I/O data transfer allows the processor to present non-discrete I/O data in the same way as discrete I/O datacontinuously transmitted and asynchronous to the ladder-logic program scan.
1771 Modules
ControlNet 1771 discrete I/O data-transfer mapping requires one map-table entry per module. ControlNet 1771 non-discrete I/O data-transfer mapping requires one or two map-table entries per module, depending on the module type. The PLC-5/20C and -5/40C ControlNet non-discrete I/O data-transfer mechanism makes it possible to eliminate block-transfer programming to communicate with the 1771 modules listed in Table 2.G.
2-10
Chapter 2
Table 2.G 1771 Non discrete I/O Data Transfer Mapping

Descriptionxy 1771 CFM/A Configurable Flowmeter Module Default Default Entries Input per Module Size 2 41 Valid Input Size(s) 0 41 Default Output Size 60 Valid Output Sizes 0 4, 14, 24, 34, 44, 48, 52, 56, 60 0, 5, 10, 15, 20, 22 Default Config. Size 60 Valid Configuration Sizes 0 4, 14, 24, 34, 44, 48, 52, 56, 60 0, 5, 10, 15, 20, 22
Module Type
1771-CFM/A
1771-DE/A 1771-IE 1771-IF 1771-IFE/A 1771-IFE/B 1771-IJ 1771-IK 1771-IL/A 1771-IL/B 1771-IR/A 1771-IR/B 1771-IS 1771-IXE/A 1771-IXE/B 1771-IXHR/A 1771-OF 1771-OFE/A 1771-OFE/B N-Series/A 1771-QA 1771-QB 1771-QC 1771-SN 1771-VHSC/A
1771 DE/A Absolute Encoder Module 2 1771 IE Analog Input Module 1771 IF Analog Input Module 1771 IFE/A Analog Input Module 1771 IFE/B Analog Input Module 1771 IJ Encoder/Counter Module 1771 IK Encoder/Counter Module 1771 IL/A Isolated Analog Input Mod. 1771 IL/B Isolated Analog Input Mod. 1771 IR/A RTD Input Module 1771 IR/B RTD Input Module 1771 IS Multiplexer Input Module 1771 IXE/A Thermocouple/Millivolt Input Module 1771 IXE/B Thermocouple/Millivolt Input Module 1771 IXHR/A High resolution Thermocouple/Millivolt Input Module 1771 OF Analog Output Module 1771 OFE/A Analog Output Module 1771 OFE/B Analog Output Module 1771 N Series Analog Module 1771 QA Stepper Positioning Module 1771 QB Linear Positioning Module 1771 QC Servo Positioning Module 1771 SN Sub I/O Scanner Module 1771 VHSC Very High speed Counter Module 1 1 1 1 2 1 1 1 1 1 1 1 1 2 2 2 1 1 1 2 2
2 8 8 20 20 1 12 12 8 8 6 12 12 12 1 5 28 4 5 6 16 18
0, 2 18 1 64 5 20 5 22 0, 0 1 5 12 5 15 38 39 17 4 12 4 13 4 13 01 0, 0 5
20
20
37 37 3 03 3 19 19 14 14 27 27 27 4 13 4 60 1 5, 13 5 0, 2 9, 59 13 59
0, 3, 37 0, 3, 37, 39 03 0, 2, 19 0, 2, 19, 36, 37 0, 2, 8, 14 0, 2, 8, 14, 15 0, 1, 19, 27 0, 1, 19, 27, 28 0, 3, 19, 27, 28
0, 5, 0 5 13 0, 2 9, 59
0, 20 28 59 1 10 1 33 1 14 0, 7 63 0, 4 26 16 64
0, 7 63 0 2, 4, 12, 20, 64 24, 29, 34, 39, 44, 49, 54, 59, 64 0 64 1 0 2, 4, 12, 20, 24, 29, 34, 39, 44, 49, 54, 59, 64 0 64
1771-Generic
x y
1771 Generic Modulez
0 64
ENPT Default = 4 x NUT ENPT Range = 2 15000 ms z For newly released modules or modules that can have multiple configurations but only one configuration is being used, you can use the generic module type and specify the input and/or output sizes.
2-11
Chapter 2
The types of modules that may be accommodated by the processors scheduled non-discrete I/O data-transfer mechanism are typically those modules that require a one-time configuration and then continuously read or write. To communicate with the modules listed in Table 2.G as well as with other 1771 analog modules, you can also include explicit CIO instructions in your ladder-logic program. See pages 4-4 and C-1 for more information.
1794 Modules
ControlNet 1794 Flex I/O mapping requires two map-table entries per adapter. The ControlNet scheduled transfer mechanism makes it possible to map the 1794 modules listed in Table 2.H.
Table 2.H 1794 Flex I/O Data Transfer Mapping
Default Input Size 1 5 9 15 19 Valid Input Size(s) Default Output Size 4 2 Valid Output Size
Module Type
1794-OE4/A 1794-IE4XOE2/A 1794-IE8/A
x y
Descriptionxy 1794 OE4/A Analog Output Module 1794 IE4XOE2/A Analog I/O Module 1794 IE8/A Analog Input Module
ENPT Default = 4 x NUT ENPT Range = 2 15000 ms
Other ControlNet Processors

ControlNet scheduled peer-to-peer communications between ControlNet processors require one map-table entry per message. The PLC-5 processor at node 01, the controlling processor, must be included in each message. The ControlNet transfer mechanism makes it possible to map the scheduled peer-to-peer messages listed in Table 2.I.
Table 2.I Peer to Peer Communications Mapping
Message Type
Peer In Peer Out to __
x y
Descriptionxy Scheduled Peer In Scheduled Peer Out
Default Input Size 64
Valid Input Sizes 1 64
ENPT Default = 4 x NUT ENPT Range = 2 15000 ms
2-12
Chapter 2
To communicate between any ControlNet PLC-5 processors on the ControlNet network, you can include explicit MSG instructions in your ladder-logic program. See pages 4-2 and C-1 for more information.
Using the ControlNet PLC 5 Processor in a ControlNet I/O System
There can be only one PLC-5/20C or -5/40C processor updating I/O adapters on a ControlNet network. the PLC-5/20C or -5/40C processor updating the I/O adapters must be at network address 01this is the controlling processor only the controlling processor is allowed to send CIO instructions additional PLC-5/20C or -5/40C processors can do scheduled transfers to the PLC-5/20C or -5/40C processor at node 01 by using peer-to-peer communications through the map table, but they cannot directly communicate with or control the ControlNet remote I/O In addition to your controlling processor, you can attach the following ControlNet devices to your network:
Catalog Number(s) 1785 L20C, L40C
Device(s) PLC 5/20C and 5/40C Programmable Controllers
Function Communicate with other PLC 5/20C or 5/40C processors using scheduled or unscheduled peer to peer communication Allows other computer platforms to communicate with the ControlNet network; for programming only Allows other computer platforms to communicate with the ControlNet network; supports redundant media; for programming MMI Connects a serial or parallel device to a ControlNet network; supports redundant media Allows the PLC 5/20C or 5/40C processor remote access to Allen Bradley's family of 1771 designated I/O modules via a ControlNet network; nonredundant only Allows the PLC 5/20C or 5/40C processor remote access to Allen Bradley's family of 1771 designated I/O modules via a ControlNet network; supports redundant media Allows the PLC 5/20C or 5/40C processor remote access to Allen Bradley's family of 1794 designated I/O modules via a ControlNet network; nonredundant only
1784 KTC 1784 KTCx
ControlNet KTC Communication Card ControlNet KTCx Communication Card
1770 KFC 1771 ACN
ControlNet Serial/Parallel Communication Interface 1771 ControlNet I/O Adapter
1771 ACNR
1771 ControlNet I/O Adapter
1794 ACN
1794 ControlNet Flex I/O Adapter
2-13
Chapter 2
Personal Computer or Other Serial Device and ControlView or 6200 Series Programming Software
Personal Computer with 1784 KTCx Card and ControlView or 6200 Series Programming Software
Personal Computer with 1784 KTCx or 1784 KTC Card and ControlView or 6200 Series Programming Software
PLC 5/40C Controlling Processor
Serial Connection 1770 KFC Interface ControlNet Network
1794 ACN Flex I/O Adapter
Example of a ControlNet Network without Redundant Media
1771 ACN Adapter
Data Highway Plus Link Remote I/O Link
PLC 5/40C Processor in ControlNet Non controlling Mode
Personal Computer or Other Serial Device and ControlView or 6200 Series Programming Software
Personal Computer with 1784 KTCx Card and ControlView or 6200 Series Programming Software
Personal Computer with 1784 KTCx or 1784 KTC Card and ControlView or 6200 Series Programming Software
PLC 5/40C Controlling Processor
Serial Connection 1770 KFC Interface
ControlNet Network
Example of a ControlNet Network with Redundant Media
1771 ACNR Adapter
Data Highway Plus Link Remote I/O Link
PLC 5/40C Processor in ControlNet Non controlling Mode
See page 3-4 for more information on ControlNet node configuration.

2-14
Chapter 2
Converting from a Non ControlNet Remote I/O System to a ControlNet I/O System
When you download archived files to a PLC-5/20C or -5/40C processor, the 6200 PLC-5 Programming Software ignores Channel 2 configuration information from anything other than a ControlNet-processor program because Channel 2 is reserved for ControlNet communication on the PLC-5/20C and -5/40C processors. The software sets Channel 2 to the ControlNet default configuration.
Can be run on a PLC 5/20C or 5/40C channel: 0
Program filesx for this process:
Archived from a: PLC 5/11 PLC 5/20 PLC 5/20C PLC 5/20E PLC 5/30 PLC 5/40 PLC 5/40C PLC 5/20 PLC 5/20C PLC 5/20E PLC 5/30 PLC 5/40 PLC 5/40C PLC 5/11 PLC 5/20 PLC 5/20C PLC 5/20E PLC 5/30 PLC 5/40 PLC 5/40C PLC 5/20 PLC 5/20C PLC 5/20E PLC 5/30 PLC 5/40 PLC 5/40C PLC 5/40E PLC 5/40L PLC 5/60 PLC 5/60L PLC 5/80 PLC 5/80E PLC 5/40E PLC 5/40L PLC 5/60 PLC 5/60L PLC 5/80 PLC 5/80E PLC 5/40E PLC 5/40L PLC 5/60 PLC 5/60L PLC 5/80 PLC 5/80E PLC 5/40E PLC 5/40L PLC 5/60 PLC 5/60L PLC 5/80 PLC 5/80E
On channel: 0
If they fit and are:
1A
1A downloaded nchanged do nloaded unchanged
1B
1B
PLC 5/20C PLC 5/40C Messaging and I/O
1A
performed by the ControlNet network you must make these changes manually by reprogrammingyz{ 1B 2
PLC 5/40 PLC 5/60
PLC 5/80
2 2A or 2B 1A or 1B performed by DH+ or remote I/O you must make these changes manually by reprogramming|
2-15
Chapter 2
Program filesx for this process: I/O

x y
Archived from a: PLC 5/20E PLC 5/60L PLC 5/40E PLC 5/80E PLC5/40L
On channel: 2
Can be run on a PLC 5/20C or 5/40C channel: 1A or 1B 2
If they fit and are: performed by remote I/O you must make these changes manually by reprogramming| performed by the ControlNet network you must make these changes manually by reprogrammingz{|
These include processor files, data table files, and port configurations. If you do not update the program, the ControlNet processor will fault. z You must change block transfer instructions for the ControlNet system from the standard block transfer read (BTR) and block transfer write (BTW) instructions to scheduled transfers or to unscheduled CIO instructions. { You must edit non ControlNet PLC 5 programs containing references to the I/O Status File for use with I/O connected via the ControlNet network. Information regarding ControlNet status is stored in a separate data file that you specify through the 6200 PLC 5 Programming Software. | If you do not update the program, the data table locations corresponding to the missing" I/O devices will not be updated.
2-16
Chapter
Configuring Your ControlNet System
Using This Chapter
If you want to read about: Matching the processor configuration with the ControlNet configuration Defining local rack characteristics Editing the ControlNet node information Editing ControlNet I/O mapping Editing ControlNet 1794 I/O module action
Go to page: 32 33 34 36 3 10
ControlNet Configuration Edit Screens in the 6200 Programming Software

Channel Overview F5 Fx = Function Key
ControlNet Node Information (Edit) See Page 3 4

F2
F4
ControlNet I/O Mapping (Edit) See Page 3 6

F9
F2
ControlNet I/O Action (Edit) See Page 3 10
3-1
Chapter 3
Matching the Processor Configuration with the ControlNet Configuration

6200 Main Menu
Follow the steps on the left to go to the ControlNet Node Information (Monitor) screen. If the ControlNet information in the processor does not match that on the current ControlNet link, the software redisplays the Channel Overview screen with a new prompt and set of function keys.
Channel Overview
Online Program F1
or
Offline Program F3
Channel 0: Channel 1A: Channel 1B: Channel 2:
SYSTEM (POINT-TO-POINT) DH+ SCANNER MODE CONTROLNET
General Utility F7
Channel 3A:
UNUSED
Channel Overview F4
PROCESSOR CONFIGURATION IS INCONSISTENT WITH CURRENT CONTROLNET CONFIGURATION. Press F10 apply processor to CNet. > Rem Prog Forces:None 5/40C File CN Apply to Link F10
Move cursor to
Channel 2: CONTROLNET
If you want to: apply the processor configuration information to the current ControlNet link configuration, then go to the ControlNet Node Information (Monitor) screen return to the original Channel Overview screen
Do this: Press [F10]Apply to Link
Channel Configuration (Monitor) F5
Press [Esc]
3-2
Chapter 3
Defining Local Rack Characteristics
If you are programming offline, configuring Channel 2 for the first time, and entering an edit screen for the first timeor if you follow the steps on the leftthe software prompts you to select the number of slots in the local chassis and your addressing mode.
6200 Main Menu
ControlNet Node Information Channel 2 Configuration Diagnostics file: 0 Network Update Time(ms): 5 Coax Repeaters in Series: 1 Scheduled Bandwidth Usage: 0% Fiber Repeater Pai A Only Local Rack Characteristics 0 (for reserving I/O image space) Node Node Type Select number of slots: F3 F4 F5 F6 4 Slots 8 Slots 12 Slots 16 Slots Select addressing mode: F8 2slot F9 1slot F10 1/2slot
MONITOR NODE --
Offline Program F3
General Utility F7
Channel Overview F4
Press a function key, or ESC to exit. > Rem Prog Forces:None Accept 4 8 12 Edits Slots Slots Slots F1 F3 F4 F5
16 Slots F6
5/40C File CN 2 1 Slot Slot F8 F9
1/2 Slot F10
Move cursor to
If you have: 4 slots 8 slots 12 slots 16 slots 2 slot addressing 1 slot addressing 1/2 slot addressing
Press:
[F3] 4 Slots [F4] 8 Slots [F5] 12 Slots [F6] 16 Slots [F8] 2-Slot [F9] 1-Slot [F10] 1/2-Slot
If you want to: apply pending edits and o e ControlNet go to the Co o e Node Information (Edit) f screen
Do this: 1. Press [F1]Accept Edits The software prompts you to enter the node number of your processor 2. Type 2 T pe the node number of your ode be o processor 3. Press [Enter]
Define Local Rack F7
return to the Channel Overview screen O e e sc ee
Press [Esc]
3-3
Chapter 3
Editing ControlNet Node Information
Follow the steps on the left to go to the ControlNet Node Information (Edit) screen. Important: Only one user on a network can enter a processors ControlNet Node Information (Edit) screen at one time.
6200 Main Menu

ControlNet - Node Information Channel 2 Configuration EDIT NODE 1
Online Program F1
or
Offline Program F3
Diagnostics File: Coax Repeaters in Series: Fiber Repeater Pairs:
N12 1 0
Network Update Time(ms): 5 Scheduled Bandwidth Usage: 64% Media Redundancy Usage: A Only Maximum Scheduled Node: 10
General Utility F7
Node 1 2 3 4
Node Type PLC-5/40C 1771-ACN PLC-5/20C 1794-ACN
Series/Revision C/H A/A C/H A/A
Status ACTIVE ACTIVE ACTIVE ACTIVE
Channel Overview F4
Press a function key, page up or page down, or enter a value. > Rem Prog Forces:None 5/40C File CN Accept Map Move Copy Auto Delete Insert Delete Edits Edit Entry Entry Network List to List Item F1 F2 F3 F4 F5 F6 F7 F8
Select Option F10
Move cursor to
If you want to: specify and create a diagnostics file
Do this: 1. Move the cursor to the Diagnostics File field 2. Type an integer file number between N3 and N999 3. Press [Enter]
specify the number of coax repeaters in series that you are using in your ControlNet network
1. Move the cursor to the Coax Repeaters in Series field 2. Type a number from 0 through 5 3. Press [Enter] 1. Move the cursor to the Fiber Repeater Pairs field 2. Type 0, 1, or 2 3. Press [Enter] 1. Move the cursor to the appropriate Pair #x length (meters) field 2. Type a number between 100 and 25500 (the software rounds up to the nearest 100) 3. Press [Enter] 1. Move the cursor to the Network Update Time (ms) field 2. Type a number between 2 and 100 3. Press [Enter]
Node Edit F4
specify the number of pairs of fiber optic repeaters that you are using in your ControlNet network enter the length of fiber cable between repeaters for any fiber optic repeater pairs that you specify Important: The field(s) for fiber cable length only appear if the number of fiber optic repeater pairs is not zero. specify the NUT the repetitive time interval during which data can be sent over the ControlNet network Important: All nodes do not need to transmit each NUI; however, the NUT defines the minimum time during which a node can transfer scheduled data.
3-4
Chapter 3
If you want to: view the percent of scheduled bandwidth used in the worst case a percent that changes depending on the ControlNet configuration specify the redundancy characteristic for the ControlNet channel specify the node with the highest network address that can use scheduled time on the ControlNet link
Do this: See the Scheduled Bandwidth Usage field
1. Move the cursor to the Media Redundancy Usage field 2. Press [F10]Select Option to toggle to A/B, A Only, or B Only 1. Move the cursor to the Maximum Scheduled Node field 2. Type a number between 1 and 99 3. Press [Enter] 1. Move the cursor to the entry's Node Type field 2. Press [F10]Select Option to toggle to your selection; or enter a unique substring of the name of the new node type
change a node's type
change a node's series or revision change a node's status to active node is a working/ communicating node on the ControlNet network or inactive configuration and map ping for node are included in computation of NUT, etc.; but device is not actually connected to the network go to the ControlNet I/O Mapping (Edit) screen move a node description to an unused network address
1. Move the cursor to the entry's Series/Revision field 2. Press [F10]Select Option to toggle to your selection 1. Move the cursor to the entry's Status field 2. Press [F10]Select Option to toggle to Active or Inactive
1. Press [F2]Map Edit 2. Go to page 3 6 1. Move the cursor to one of the node's cursorable fields 2. Press [F3]Move Entry 3. Type the new network address 4. Press [Enter]
copy node information to a different network address
1. Move the cursor to one of the original node's cursorable fields 2. Press [F4]Copy Entry 3. Type the new network address 4. Press [Enter]
automatically add nodes connected to the channel to the node list if you are programming online delete all nodes from the list except for the processor that you are editing insert an entry or range of entries into the node list
Press [F5]Auto Network Press [F6]Delete List 1. Press [F7]Insert to List 2. Type a new network address or range of network addresses e.g., 5 10 3. Press [Enter]
delete an entry from the node list apply pending edits and return to the ControlNet Node Information (Monitor) screen return to the ControlNet Node Information (Monitor) screen without saving any pending edits
1. Move the cursor to one of the node's cursorable fields 2. Press [F8]Delete Item Press [F1]Accept Edits Press [Esc]
3-5
Chapter 3
Editing ControlNet I/O Mapping

6200 Main Menu
Follow the steps on the left to go to the ControlNet I/O Mapping (Edit) screen. Important: Only one user on a network can enter a processors ControlNet I/O Mapping (Edit) screen at one time. While you are editing the map-table entries on this screen or accepting pending edits, the screen may display the following message:
Maximum transmit size exceededadjustments necessary.
Online Program F1
or
Offline Program F3
General Utility F7
This indicates that you are attempting to configure a node to transmit more data per NUT than the node can support.
ControlNet - I/O Mapping Channel 2 Configuration EDIT NODE 1
Channel Overview F4
Status File: Data Input File: Data Output File: Dflt Config File:
N32 N34 N36 N38
Network Update Time(ms): 5 Sch BW(%): 64 ------ Processors ControlNet Resource Usage ---Map Entries PLC BW (%) DIF (%) DOF (%) 8 8 10 8 Exp Net Pckt Input Time(ms) File Size n/a 20 5 15 13 n/a 7 n/a n/a I:010 N34:0 N34:20 n/a N34:25 n/a n/a 8 20 5 n/a 24 Output File Size n/a N36:0 O:010 n/a N36:64 n/a n/a n/a 24 8 n/a 5 n/a n/a Status Offset Config File Size n/a n/a n/a N38:0 N36:64 n/a n/a n/a n/a n/a 37 13 n/a n/a
Node Mod/Msg Type S/M
Move cursor to
1 1 2 6 7
3 1
PLC-5/40C Peer Out to 3 1771-ACN 1771-IFE/A 1771-OFE/A PLC-5/20C Peer In
0 3 6 9 15
Press a function key, page up or page down, or enter a value. > Rem Prog Forces:None Display:Slot/Message 5/40C File CN Accept Select Node Auto Clear Insert Delete Edit Select Edits Display Edit Mapping * to List * Actions Option F1 F3 F4 F5 F6 F7 F8 F9 F10
Map Monitor F2
If you want to: specify and create the status file the file containing status information on all the ControlNet network's scheduled I/O map table entries specify and create the DIF the file used for both non discrete and peer to peer input data transfer over the ControlNet network specify and create the DOF the file used for both non discrete and peer to peer output data transfer over the ControlNet network specify and create the Default Configuration File the file used to store non discrete I/O data transfer and 1794 Flex I/O configuration information when the automatic mapping feature is used
Do this: 1. Move the cursor to the Status File field 2. Type an integer file number between N3 and N999 3. Press [Enter] 1. Move the cursor to the Data Input File field 2. Type an integer file number between N3 and N999 3. Press [Enter] 1. Move the cursor to the Data Output File field 2. Type an integer file number between N3 and N999 3. Press [Enter] 1. Move the cursor to the Dflt Config File field 2. Type an integer file number between N3 and N999 3. Press [Enter]
Map Edit F2
3-6
Chapter 3
If you want to: specify the NUT
Do this: 1. Move the cursor to the Network Update Time (ms) field 2. Type a number between 2 and 100 3. Press [Enter]
view the percent of scheduled bandwidth used in the worst case a percent that changes depending on the NUT and the completed map table entries view the number of scheduled I/O map table entries indicating data transfers between the scanning processor and other nodes view the percentage of bandwidth used for the ControlNet PLC 5 processor that you are using view the percentage of the DIF being used view the percentage of the DOF being used change a module or message's type
See the Scheduled Bandwidth Usage field
See the Map Entries field
See the PLC BW (%) field
See the DIF (%) field See the DOF (%) field 1. Move the cursor to the entry's Type field 2. Press [F10]Select Option to toggle to your selection; or enter a unique substring of the name of the new module or message type 1. Move the cursor to the entry's Exp Net Pckt Time (ms) field 2. Type a number between the NUT and 15000 3. Press [Enter]
change the ENPT for a module or message
manually enter the destination file for information received from a module or message e.g., a 1771 ACN, 1794 ACN, or Peer In
1. Move the cursor to the entry's Input File field If the item is a digital module, I:" is displayed If it is non discrete or peer to peer input, the DIF is displayed (Scheduled peer to peer inputs can also use the input image file) 2. For non discrete or peer to peer input, type an offset between 0 and 999; for discrete or peer to peer input, type an offset between 0 and the end of the input image
manually enter the amount of information received from a module or message e.g., a 1771 ACN, 1794 ACN, or Peer In manually enter the source file for information sent to a module or in a message e.g., a 1771 ACN, 1794 ACN, or Peer Out
3. Press [Enter] 1. Move the cursor to the entry's Input Size field 2. Type a value 3. Press [Enter] 1. Move the cursor to the entry's Output File field If the item is a digital module, O:" is displayed If it is non discrete or peer to peer output, the DOF is displayed (Scheduled peer to peer outputs can also use the output image file) 2. For non discrete or peer to peer output, type an offset between 0 and 999; for discrete or peer to peer output, type an offset between 0 and the end of the output image
manually enter the amount of information sent to a module or in a message e.g., a 1771 ACN, 1794 ACN, or Peer Out
3. Press [Enter] 1. Move the cursor to the entry's Output Size field 2. Type a value 3. Press [Enter]
3-7
Chapter 3
If you want to: view the offset into the status file that con tains the status information for a module or message (determined by the software) manually enter the file for storing the I/O configuration needed for a module e.g., a 1771 IFE or 1794 ACN Important: If a 1771 module uses the DOF, this must match. manually enter the amount of information to be stored in the I/O configuration file for a module e.g., a 1771 IFE select the display of slots, messages, or slots and messages in the list I/O cards configured in physical slots of a chassis and their physical slot numbers
Slot Display displays all the non digital
Do this: See the Status Offset field for the item
1. Move the cursor to the module's Config File field 2. Type an integer file number between N3 and N999 3. Press [Enter] 1. Move the cursor to the module's Config Size field 2. Type a valid value 3. Press [Enter] 1. Press [F3]Select Display 2. Press [F2]Slot Display or [F3]Message Display or [F4]Slot/Message
Message Display displays all the peer to peer messages configured between PLC processors and their message numbers Slot/Message displays all the above
go to the ControlNet Node Information (Edit) screen have the software automatically map into available data table space (I/O or DIF/DOF) modules and messages that are listed but not mapped
Press [F4]Node Edit 1. Press [F5]Auto Mapping 2. Select items to be mapped by pressing:
[F2]Select All to select all the items that are not mapped [F3]Toggle to select or unselect an item that is highlighted by the cursor [F4]Clear All to unselect any items that are selected [F8]Auto Module to have the software automatically scan configured nodes for slot
information if you are programming online For 1771 I/O, Auto Module determines the size of the chassis
For 1794 Flex I/O, Auto Module determines the size of the chassis and lists all the non discrete I/O data transfer modules in the chassis 3. Press [F10]Auto I/O Map clear the following information on a module or message: input file and offset output file and offset status offset config file and offset clear the following information about all modules and messages: input file and offset output file and offset status offset config file and offset 1. Move the cursor to the slot/message where you want to clear information 2. Press [F6]Clear * 3. Press [F8]Clear Item
1. Press [F6]Clear * 2. Press [F10]Clear List
3-8
Chapter 3
If you want to:
Do this: 2. Press [F7]Insert to List 3. Type the slot or message number (slot/message or node.slot/message) for a single new entry or range (slot/message slot/message or node.slot/message slot/message) for multiple new entries 4. Press [Enter]
insert an entry or range of entries into the list 1. Move the cursor to the node where you want to add a module or message
delete a module or message
1. Move the cursor to the item that you want to delete 2. Press [F8]Delete * 3. Press [F8]Delete Item
delete all modules and messages go to the ControlNet I/O Action screen Important: This option is not available if the display mode is set to Message Display on this screen by using [F3]Select Display. apply pending edits and return to the ControlNet I/O Mapping (Monitor) screen return to the ControlNet I/O Mapping (Monitor) screen without saving any pending edits
1. Press [F8]Delete * 2. Press [F10]Delete List 1. Move the cursor to the 1794 Flex I/O module entry who's actions you want to edit 2. Press [F9]Edit Actions
Press [F1]Accept Edits Press [Esc]
3-9
Chapter 3
Editing ControlNet 1794 I/O Module Action

6200 Main Menu
Follow the steps on the left to the ControlNet I/O Action (Edit) screen. Important: Only one user on a network can enter a processors ControlNet 1794 I/O Module Action screen at one time.
ControlNet I/O Action Channel 2 Configuration Node 4 1794ACN Fault Action Idle Action Fault Action From Idle Idle Idle Idle Idle Idle Idle Idle Idle EDIT NODE
Online Program F1
or
Offline Program F3
General Utility F7
Module Type Slot 0 1 2 3 4 5 6 7 1794Digital 1794IE8/A 1794OE4/A 1794IE4XOE2/A 1794Digital 1794Digital 1794Digital 1794Digital
Channel Overview F4
Reset Reset Safe Safe Reset Reset Reset Reset
Reset Reset Reset Reset Reset Reset Reset Reset
Move cursor to
Press a function key or cursor key. > Rem Prog Forces:None Accept Map Edits Edit F1 F2
5/40C File CN Toggle All F8
Toggle Entry F10
If you want to:
Do this:
Map Monitor F2
change a system's fault action 1. Move the cursor to the Fault Action column i.e., the action that it takes 2. Press [F8]Toggle All to toggle between: when it faults Reset to change all outputs to zero Hold Last to maintain all current output values Safe to change all outputs to user specified fail-safe values change a system's idle action i.e., the action that it takes when it becomes idle 1. Move the cursor to the Idle Action column 2. Press [F8]Toggle All to toggle between: Reset to change all outputs to zero Hold Last to maintain all current output values Safe to change all outputs to user specified fail-safe values
Map Edit F2
Move cursor to
a 1794 I/O entry
change a system's fault action 1. Move the cursor to the Fault Action From Idle column from idle i.e., the action that it takes when it faults from idle 2. Press [F8]Toggle All to toggle between: Idle to use the idle action Fault to use the fault action change a module's fault action 1. Move the cursor to the module's field Fault Action field i.e., the action that it takes 2. Press [F10]Toggle Entry to toggle between: when it faults Reset to change all outputs to zero Hold Last to maintain all current output values Safe to change all outputs to user specified fail-safe values
Edit Actions F9
3-10
Chapter 3
If you want to: change a module's idle action i.e., the action that it takes when it becomes idle
Do this: 1. Move the cursor to the module's Idle Action field 2. Press [F10]Toggle Entry to toggle between: Reset to change all outputs to zero Hold Last to maintain all current output values Safe to change all outputs to user specified fail-safe values
change a module's fault action 1. Move the cursor to the module's Fault Action From Idle field from idle i.e., the action that it takes when it faults from idle 2. Press [F10]Toggle Entry to toggle between: Idle to use the idle action Fault to use the fault action apply pending edits and return Press [F1]Accept Edits to the ControlNet I/O Mapping (Edit) screen go back to the ControlNet I/O Mapping (Edit) screen Press [F2]Map Edit or [Esc]
3-11
Chapter
Programming Your ControlNet System
Using This Chapter
If you want to read about using: ControlNet message instructions ControlNet I/O transfer instructions ControlNet immediate data input and output instructions Using Selectable Timed Interrupts (STIs) in a program on a ControlNet network
Go to page: 42 44 46 47
4-1
Chapter 4
Using ControlNet Message Instructions

Monitor File F8
You can use the existing MG data type to send two message commands over the ControlNet system within the local ControlNet linkPLC-5 TYPED WRITE and PLC-5 TYPED READ. Follow the steps on the left to go to the Instruction Entry for Message Block screen.
Instruction Entry for Message Block MG20:50
Edit F10
Communication Command: PLC-5 Data Table Address: Size in Elements:
PLC-5 TYPED WRITE N8:0 1
Insert Rung F4
Local ControlNet Node: Destination Data Table Address: Port Number: BLOCK SIZE = 56 WORDS
1 N11:0 2
Insert Instruction F4
Press a key to change a parameter or <ENTER> to accept parameters. > Rem Prog Forces:None Edits:None 5/40C File CN Command PLC-5 Size in Local Destin Port Type Address Elemnts Node Address Number F1 F2 F3 F8 F9 F10
Others F10
If you want to: change the command type
Do this: Press [F1]Command Type to toggle between: PLC-5 TYPED WRITE to select a write operation to another PLC 5 processor PLC-5 TYPED READ to select a read operation from another PLC 5 processor 1. Press [F2]PLC-5 Address 2. Type the PLC 5 data table address 3. Press [Enter] 1. Press [F3]Size in Elemnts 2. Type a number of elements from 1 to 1000 3. Press [Enter]
I/O Message F3
enter a PLC 5 data table address
Message F5
enter the size in elements
Enter message control block address using file type MG
enter the destination network address 1. Press [F8]Local Node 2. Type a number from 1 to 99 3. Press [Enter] enter a destination data table address 1. Press [F9]Destin Address 2. Type the destination data table address 3. Press [Enter]
Port Number F10
Type 2 and press
Enter
4-2
Chapter 4
6200 Main Menu
Follow the steps on the left to go to the Data Monitor for Message Control Block screen.
Online Program F1
or
Offline Program F3
Data Monitor for Message Control Block MG20:50 Communication Command: PLC-5 Data Table Address: Size in Elements: PLC-5 TYPED WRITE N8:0 ignore if timed-out: 1 to be retried: awaiting execution: continuous: error: message done: 1 message transmitting: N11:0 message enabled: 2
Cursor to file; or enter file number or name

Monitor File F8
Local ControlNet Node: Destination Data Table Address: Port Number: Error Code: 0000 (HEX)
0 0 0 0 0 0 0 0
TO NR EW CO ER DN ST EN
Cursor to MSG instruction

Data Monitor F8
Press a function key or enter a value. MG20:50.TO = Rem Prog Forces:None Data:Decimal Toggle Size in Specify Bit Elemnts Address F2 F3 F5
Addr:Decimal Next File F7
5/40C File CN Prev Next Prev File Element Element F8 F9 F10
The fields of the MG data type that you can directly address are: .TO .NR .EW .CO .ER .DN .ST .EN .ERR .RLEN Abort (Time out) control bit No response flag bitnot used Enabled-waiting flag bit Continuous control bit Errored flag bit Done flag bit Started flag bit Enabled flag bit Error-code word Requested length word word 0, bit 08 word 0, bit 09 word 0, bit 02 word 0, bit 03 word 0, bit 04 word 0, bit 05 word 0, bit 06 word 0, bit 07 word 1 word 2
More
For more detailed information on writing ladder programs and using message instructions, see the PLC-5 Programming Software Instruction Set Reference, publication 6200-6.4.11, and PLC-5 Programming Software Programming, publication 6200-6.4.7.
4-3
Chapter 4
Using the ControlNet I/O Transfer Instruction

6200 Main Menu
You can use the ControlNet I/O Transfer (CIO) instruction and the ControlNet Transfer (CT) data type to make ControlNet I/O transfers within the local ControlNet link. Follow the steps on the left to go to the Instruction Entry for ControlNet I/O Transfer Block screen.
Instruction Entry for ControlNet I/O Transfer Block CT21:50
Online Program F1
or
Offline Program F3
Communication Command: PLC-5 Data Table Address: Size in Elements: Elements Transmitted:
1771 WRITE N7:3 10 0

Monitor File F8
Local ControlNet Node: Slot Number: Port Number: BLOCK SIZE = 22 WORDS
1 0 2
Press a key to change a parameter or <ENTER> to accept parameters. > Rem Prog Forces:None Edits:None 5/40C File CN Command PLC-5 Size in Local Slot Type Address Elemnts Node Number F1 F2 F3 F8 F9
Edit F10
If you want to: change the command type
Do this: Press [F1]Command Type to toggle between: 1771 READ reads input data from 1771 non discrete I/O module 1771 WRITE writes output data to 1771 non discrete I/O module 1794 FAULT ACTION changes the action that a module takes when it faults 1794 IDLE ACTION changes the action that a module takes when it is idle 1794 CONFIG DATA changes a module's configuration data 1794 SAFE STATE DATA changes a module's safe state data 1. Press [F2]PLC-5 Address 2. Type the data table address 3. Press [Enter] 1. Press [F3]Size in Elemnts 2. Type the number of elements: 1 for 1794 FAULT ACTION or 1794 IDLE ACTION 1 to 15 for 1794 CONFIG DATA or 1794 SAFE STATE DATA 0x to 64 for 1771 READ or 1771 WRITE 3. Press [Enter] 1. Press [F8]Local Node 2. Type a number from 1 to 99 3. Press [Enter] 1. Press [F9]Slot Number 2. Type the number of the slot that holds the I/O device number from 0 to 15 3. Press [Enter]
Insert Rung F4
enter a PLC 5 data table address enter the size in elements
Others F10
I/O Message F3
enter the destination network address enter the destination slot number
CIO F8
x
If you enter a 0, the module determines the size of the transfer. In this case, you must make sure that your data table can accomodate up to 64 words.
Enter control block address using file type CT 4-4
Chapter 4
6200 Main Menu
Follow the steps on the left to go to the Data Monitor for ControlNet I/O Transfer Block screen.
Data Monitor for ControlNet I/O Transfer Block CT21:50 Communication Command: PLC-5 Data Table Address: Size in Elements: Elements Transmitted: 1771 Write N7:3 10 0
Online Program F1
or
Offline Program F3

Monitor File F8
Local ControlNet Node: Slot Number: Port Number: Error Code: 0000 (HEX)
1 0 2
ignore if timed-out: awaiting execution: continuous: error: transfer done: transfer started: transfer enabled:
0 0 0 0 0 0 0
TO EW CO ER DN ST EN
Cursor to CIO instruction

Data Monitor F8
Press a function key or enter a value. CT21:50.TO = Rem Prog Forces:None Data:Decimal Toggle Size in Specify Bit Elemnts Address F2 F3 F5
Addr:Decimal Next File F7
5/40C File CN Prev Next Prev File Element Element F8 F9 F10
The fields of the CT data type that you can directly address are: .TO .EW Abort (Time out) control bit Enabled-waiting flag bit Continuous control bit Errored flag bit Done flag bit Started flag bit Enabled flag bit Error-code word Requested length word Done length word Transfer file number Transfer element number word 0, bit 08 word 0, bit 02 word 0, bit 03 word 0, bit 04 word 0, bit 05 word 0, bit 06 word 0, bit 07 word 1 word 2 word 3 word 4 word 5
Monitor File F3
.CO .ER .DN .ST .EN .ERR .RLEN .DLEN .FILE .ELEM
More
For more detailed information on writing ladder programs, see the PLC-5 Programming Software Instruction Set Reference, publication 6200-6.4.11, and PLC-5 Programming Software Programming, publication 6200-6.4.7.
4-5
Chapter 4
Using ControlNet Immediate Data Input and Output Instructions

6200 Main Menu
You can use two instructions for immediate data input and output on a ControlNet networkImmediate Data Input (IDI) and Immediate Data Output (IDO). Follow the steps on the left to add IDI and IDO instructions to your program.
IDI IMMEDIATE DATA INPUT Data file offset Length Destination
Online Program F1
or
Offline Program F3
232 10 N11:232

Monitor File F8
[END OF FILE] Press a function key. (File 2: Rung 0) Rem Prog Forces:None Edits:None Change Config Return Program Documnt Search Mode Display to Menu Dirctry F1 F2 F3 F4 F5 F6
IDO IMMEDIATE DATA OUTPUT Data file offset Length Source
175 24
N12:175
Edit F10
5/40C File CN General Data Force Utility Monitor F7 F8 F9
Edit F10
Insert Rung F4
In the example above, an IDI is initiated that updates the destination file from the private buffer before the next normal input-image update. The Data File Offset (232) is the offset into the buffer where the data is stored. The Length (10) identifies the number of words in the transferit can be an immediate value ranging from 1 to 64 or a logical address that specifies the number of words to be transferred. The Destination (N11:232) is the destination of the words to be transferred. The Destination should be the matching data-table address in the DIF except when you use the instruction to ensure data-block integrity in the case of Selectable Timed Interrupts (STIs). See page 4-7. An IDO is initiated that updates the private memory output buffer from the source file before the next normal output- image update. The Data File Offset (175) is the offset into the buffer where the data is stored. The Length (24) identifies the number of words in the transfer or a logical address that specifies the number of words to be transferred. The Source (N12:175) is the source of the words to be transferred. The Source should be the matching data-table address in the DOF except when you use the instruction to ensure data-block integrity in the case of Selectable Timed Interrupts (STIs). See page 4-7.
Others F10
I/O Message F3
IDI F6
or
IDO F7
4-6
Chapter 4
More
For more detailed information on writing ladder programs, see the PLC-5 Programming Software Instruction Set Reference, publication 6200-6.4.11, and PLC-5 Programming Software Programming, publication 6200-6.4.7. For information on programming ControlNet I/O transfers using Immediate Input (INN) and Immediate Output (IOT) instructions, see the PLC-5 Programming Software Instruction Set Reference, publication 6200-6.4.11.
Using Selectable Timed Interrupts with a Program on a ControlNet Network
You must be careful when using Selectable Timed Interrupts (STIs) with a program on a ControlNet network. A Selectable Timed Interrupt (STI) periodically interrupts primary program execution in order to run a subprogram to completion. If an STI occurs while a normal ControlNet non-discrete I/O data transfer or a ControlNet Immediate Data I/O instruction (IDO or IDI) is in progress and they both operate on the same set of data, the integrity of that block of data is jeopardized. To ensure data-block integrity, write your STI routine so that it operates on its own copy of the data block that it needs. Use ControlNet Immediate Data I/O instructions (IDO and IDI) within your STI to copy the needed block of data out to and back from a temporary location that is different from that used by the normal data table. For detailed information on STIs, see PLC-5 Programming Software Configuration and Maintenance, publication 6200-6.4.6.
More
4-7
Chapter
Using This Chapter
If you want to read about: Using the general status indicators Using the ControlNet status indicators Monitoring the ControlNet configuration and status screens
See page: 52 53 55
5-1
Chapter 5
Using the General Status Indicators

Indicator BATT
BATT PROC FORCE COMM
The general status indicators inform you of the general operational state of the processor.
State Steady Red Off Steady Green Flashing Green Description Battery low Battery good Processor in Run mode and fully operational Processor memory being transferred to EEPROM Probable Cause(s) Battery low Normal operation Recommended Action(s) Replace battery within 10 days (typical) None
Normal operation
None 1. Check major fault bit in status file (S:11) for error definition
Flashing Red
Major fault
Run time error
2. Clear fault bit 3. Correct problem 4. Return to Run mode
PROC
Processor in FLASH Alternating Red memory programming and Green mode
Normal operation if processor's FLASH memory is being reprogrammed Processor FLASH memory checksum error Processor memory checksum error Memory module error
None
Contact your local A B representative for a field firmware update Clear memory and reload program Correct backplane switch settings, and/or insert correct memory module 1. Turn power off, reseat processor, then power up
Steady Red
Major fault Internal diagnostics failed
2. Clear memory and reload your program 3. Replace EEPROM with new program 4. If still an error, replace the processor
Off Steady Amber FORCE Flashing Amber Off
Processor in Program Load or Test mode SFC and/or I/O forces enabled SFC and/or I/O forces present but not enabled SFC and/or I/O forces not present No transmission on Channel 0 Transmission on Channel 0
Normal operation if mode correct
None
Normal operation None Normal operation if channel not being used Normal operation if channel being used
Off COMM Flashing Green
5-2
Chapter 5
Using the ControlNet Status Indicators

Indicator State Off
The ControlNet status indicators inform you of the operational state of the ControlNet network.
Description ControlNet I/O not present or not operating All nodes configured in the ControlNet map table present and operating properly At least one node configured for the ControlNet network not present or not operating properly All nodes configured for ControlNet not present or not operating properly Probable Cause(s) Normal operation if Channel 2 not being used Normal operation Cable(s) or connector(s) broken or not connected Destination module(s) bad or missing Node(s) not on network Cable(s) or connector(s) broken or not connected Nodes not on network Recommended Action(s) None
I/O
Steady Green
None Repair or replace cable(s) or connector(s), and reconnect Repair or replace module(s) Connect node to network Repair or replace cable(s) or connector(s), and reconnect Connect nodes to network
I/O
Flashing Green/Off
Flashing Red/Off
5-3
Chapter 5
Indicator
State Off
Probable Cause No power
Recommended Action(s) None Power up Cycle power or reset unit
and
Steady Red B Alternating Red/Green Alternating Red/Off Off Steady Green
Faulted unit
If fault persists, contact your Allen Bradley Company, Inc. representative or distributor None Check network address and other ControlNet configuration parameters None Configure for ControlNet communication None None Make sure that ControlNet is properly terminated Make sure the Configuration Manager node is present and workingy Check media for broken cables, loose connectors, missing terminators, etc. Add other nodes to the network Cycle power or reset unit
Self test Incorrect node configuration Channel disabled Normal operation Temporary errors Node is not configured to go online Media fault No other nodes present on network Incorrect network configuration
or
Flashing g Green/Off G /Off B Flashing Red/Off Flashing Red/Green
If fault persists, contact your Allen Bradley Company, Inc. representative or distributor
Definition of terms:
alternating the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together); flashing the indicator alternates between the two defined states (applies to each indicator viewed independent of the other); if both steady indicator is on continuously in the defined state
y The Configuration Manager node at node 01, the controlling processor
the two indicators are always in opposite states, out of phase indicators are flashing, they flash together, in phase
to all nodes on the ControlNet network.
is the node responsible for distributing ControlNet configuration data
5-4
Chapter 5
Using the 6200 Programming Software to Monitor ControlNet Configuration and Status
This section shows you how to use the ControlNet configuration monitor and status screens found in the 6200 PLC-5 Programming Software, release 5.1 or later.
ControlNet Configuration Monitor and Status Screens in the 6200 Programming Software
Channel Overview F5
ControlNet Node Information (Monitor) See Page 5 6

F2 F9 Fx = Function Key
F4
F4 F5
ControlNet I/O Mapping (Monitor) See Page 5 7

F6
F5
ControlNet View Times See Page 5 8

F9
F9
F6
ControlNet Map Entries Status See Page 5 9
F2
ControlNet I/O Action (Monitor) See Page 5 11
WHO F5
ControlNet Channel 2 Status See Page 5 12
ControlNet WHO ACTIVE Active Node Identification See Page 5 14

F5
F2 F6
ControlNet WHO ACTIVE Active Node Status See Page 5 16
ControlNet WHO ACTIVE Channel Status See Page 5 17

F5 F6
ControlNet WHO ACTIVE Network Status See Page 5 19
5-5
Chapter 5
Using the ControlNet Node Information (Monitor) Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet Node Information (Monitor) screen.
ControlNet - Node Information Channel 2 Configuration Diagnostics File: Coax Repeaters in Series: Fiber Repeater Pairs: N12 1 0 MONITOR NODE 1
Online Program F1
or
Offline Program F3
Network Update Time(ms): 5 Scheduled Bandwidth Usage: 64% Media Redundancy Usage: A Only Maximum Scheduled Node: 10
General Utility F7
Node 1 2 3 4
Node Type PLC-5/40C 1771-ACN PLC-5/20C 1794-ACN
Series/Revision C/H A/A C/H A/A
Status ACTIVE ACTIVE ACTIVE ACTIVE
Channel Overview F4
Press a function key, page up or page down, or enter a node. number. > Rem Prog Forces:None 5/40C File CN Map Node Define Chan 2 Monitor Edit LclRack Status F2 F4 F7 F9
Move cursor to
The ControlNet Node Information (Monitor) screen lists the nodes that you have entered for the ControlNet network; and it shows the node type, product series/revision, and status (active or inactive) that you have configured for each node.
If you want to: quickly position the cursor on a specific node in the list go to the ControlNet I/O Mapping (Monitor) screen go to the ControlNet Node Information (Edit) screen define the characteristics of the local chassis (for reserving I/O image space) Important: This option is not available if you are programming online. go to the ControlNet Channel 2 Status screen go to the Channel Overview screen Press [F9]Chan 2 Status Press [Esc] Press: 1. Type the node number and a period (.) e.g., 2. 2. Press [Enter] Press [F2]Map Monitor Press [F4]Node Edit Press [F7]Define LclRack
5-6
Chapter 5
Using the ControlNet I/O Mapping (Monitor) Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet I/O Mapping (Monitor) screen.
ControlNet I/O Mapping Channel 2 Configuration Status File: Data Input File: Data Output File: Dflt Config File: Node S/M 1 1 2 6 7 3 N32 N34 N36 N38 MONITOR NODE 1
Online Program F1
or
Offline Program F3
Network Update Time(ms): 5 Sch BW(%): 64 Processors ControlNet Resource Usage Map Entries PLC BW (%) DIF (%) DOF (%) 8 8 10 8 Output File Size n/a N36:0 O:010 n/a N36:64 n/a n/a n/a 64 8 n/a 5 n/a n/a Status Offset Config File Size n/a n/a n/a N38:0 N36:64 n/a n/a n/a n/a n/a 37 13 n/a n/a
General Utility F7
Mod/Msg Type
Act Net Pckt Input Time(ms) File Size n/a 20 5 10 10 n/a 5 n/a n/a I:010 N34:0 N34:20 n/a N34:25 n/a n/a 8 20 5 n/a 24
Channel Overview F4
PLC5/40C Peer Out to 3 1771ACN 1771IFE/A 1771OFE/A PLC5/20C Peer In
0 3 6 9 15
Press a function key, page up or page down, or enter a node.s/m number. > Rem Prog Forces:None Display:Slot/Message 5/40C File CN Map Select Node View Monitor Define I/O Monitor Edit Display Monitor Times Status LclRack Monitor Actions F2 F3 F4 F5 F6 F7 F8 F9
Move cursor to
If you want to: quickly position the cursor on a specific entry in the list
Do this: 1. Type the node number, a period (.), and the slot or message number of the entry e.g., 2.7 2. Press [Enter] Press [F2]Map Edit 1. Press [F3]Select Display 2. Press [F2]Slot Display or [F3]Message Display or
[F4]Slot/Message
go to the ControlNet I/O Mapping (Edit) screen select the display of slots, messages, or slots and messages in the list
Map Monitor F2
go to the ControlNet Node Information (Monitor) screen view the Actual Network Packet Time (ANPT) and Expected Network Packet Time (ENPT) instead of the input, output, status, and configuration information go to the ControlNet Map Entries Status screen define the characteristics of the local chassis Important: This option is not available if you are programming online. go to the I/O Configuration Monitor Utility go to the ControlNet I/O Action (Monitor) screen Important: This option is not available if the display mode is set to Message Display on this screen or the ControlNet View Times screen by using [F3]Select Display. return to the ControlNet Node Information (Monitor) screen
Press [F4]Node Monitor Press [F5]View Times
Press [F6]Monitor Status Press [F7]Define LclRack
1. Move your cursor to an analog entry 2. Press [F8]I/O Monitor 1. Move the cursor to the 1794 I/O module entry who's actions you want to monitor 2. Press [F9]Monitor Actions Press [Esc]
5-7
Chapter 5
Using the ControlNet View Times Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet View Times screen.
ControlNet View Times Channel 2 Configuration MONITOR NODE 1
Online Program F1
or
Offline Program F3
Status File: Data Input File: Data Output File: Dflt Config File: Node S/M
N32 N34 N36 N38
Network Update Time(ms): 5 Sch BW(%): 64 Processors ControlNet Resource Usage Map Entries PLC BW (%) DIF (%) DOF (%) 8 8 10 8
Mod/Msg Type
Act Net Pckt Exp Net Pckt Time(ms) Time(ms) n/a 20 5 10 10 n/a 5 n/a 20 5 15 13 n/a 7
General Utility F7
1 1 2 6 7 3 1
PLC5/20C Peer Out To 1771ACN 1771IFE/A 1771OFE/A PLC5/20C Peer In
Channel Overview F4
Press a function key, page up or page down, or enter a node.s/m number. > Rem Prog Forces:None Display:Slot/Message 5/40C File CN Map Select Node View Monitor I/O Monitor Edit Display Monitor Mapping Status Monitor Actions F2 F3 F4 F5 F6 F8 F9
Move cursor to
If you want to: quickly position the cursor on a specific entry in the list
Do this: 1. Type the node number, a period (.), and the slot or message number of the entry 2. Press [Enter] Look at the Act Net Pckt Time (ms) field for that entry Look at the Exp Net Pckt Time (ms) field for that entry Press [F2]Map Edit 1. Press [F3]Select Display 2. Press [F2]Slot Display or [F3]Message Display or
[F4]Slot/Message
see the ANPT for an entry the actual time it takes for the network to update the data see the ENPT for an entry the maximum time allowed for the network to update the data go to the ControlNet I/O Mapping (Edit) screen select the display of slots, messages, or slots and messages in the list
Map Monitor F2
View Times F5
go to the ControlNet Node Information (Monitor) screen toggle back to view input, output, status, and configuration information go to the ControlNet Map Entries Status screen go to the I/O Configuration Monitor Utility go to the ControlNet I/O Action (Monitor) screen
Press [F4]Node Monitor Press [F5]-View Mapping Press [F6]Monitor Status 1. Move your cursor to an analog entry 2. Press [F8]I/O Monitor
1. Move the cursor to the 1794 I/O module entry who's actions you want Important: This option is not available if the display mode is to monitor set to Message Display on this screen or the ControlNet I/O Mapping screen by using [F3]Select Display. 2. Press [F9]Monitor Actions return to the ControlNet Node Information (Monitor) screen Press [Esc]
5-8
Chapter 5
Using the ControlNet Map Entries Status Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet Map Entries Status screen.
ControlNet Map Entries Status Channel 2 Configuration Status File: Data Input File: Data Output File: Dflt Config File: Node S/M 1 1 2 6 7 7 3 N32 N34 N36 N38 MONITOR
Online Program F1
or
Offline Program F3
Network Update Time(ms): 5 Sch BW(%): 64 Processors ControlNet Resource Usage Map Entries PLC BW (%) DIF (%) DOF (%) 8 8 10 8 Status Status Offset Data Inhibit Valid Reset n/a YES YES YES YES YES n/a n/a 0 0 0 0 0 n/a n/a 0 0 0 0 0 n/a
General Utility F7
Mod/Msg Type
Channel Overview F4
PLC5/40C W Peer Out to 3 1771ACN R 1771IFE/A R 1771OFE/A W 1771OFE/A PLC5/20C
n/a SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS n/a
0 3 6 9 12
Page up or page down, or enter a value. > Rem Prog Forces:None Display:Slot/Message Select Display F3
5/40C File CN
Move cursor to
If you want to: select the display of slots, messages, or slots and messages in the list see whether an entry is a Read (R) or Write (W) operation view the current status of an entry
Do this: 1. Press [F3]Select Display 2. Press [F2]Slot Display or [F3]Message Display or [F4]Slot/Message Look at the field to the right of the S/M field for that entry Look at the Status field for that entry See Appendix D for a list of errors that may be displayed Look at the Status Offset field for that entry
Map Monitor F2
see where the three status words associated with an entry are located in the Status File see whether the data associated with an entry is valid or invalid
Look at the Data Valid field for that entry For all I/O modules except 1794: YES indicates that the status data for the slot are valid NO indicates that the status data for the slot are not valid For all 1794 I/O modules: Y indicates that the status data for the slot are valid N indicates that the status data for the slot are not valid X indicates that the slot is not configured For example, a 1794 I/O module field of YYXNNXYX indicates: the status data for slots 0, 1, and 6 are valid the status data for slots 3 and 4 are not valid slots 2, 5, and 7 are not configured 1. Move the cursor to the Inhibit field for that entry 2. Type a 1 3. Press [Enter]
Monitor Status F6
set the inhibit bit so that the processor will not attempt to establish a connection with the module or message
5-9
Chapter 5
If you want to:
Do this:
clear the inhibit bit so that the processor 1. Move the cursor to the Inhibit field for that entry will attempt to establish a connection with 2. Type a 0 the module or message 3. Press [Enter] set the reset bit so that the processor will set the output module or message's Run/Program command to Program mode clear the reset bit so that the processor will set the output module or message's Run/Program command to the processor's mode return to the ControlNet I/O Mapping (Monitor) screen 1. Move the cursor to the Reset field for that entry 2. Type a 1 3. Press [Enter] 1. Move the cursor to the Reset field for that entry 2. Type a 0 3. Press [Enter] Press [Esc]
5-10
Chapter 5
Using the ControlNet I/O Action (Monitor) Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet I/O Action (Monitor) screen.
Online Program F1
or
Offline Program F3
Node 4 1794ACN Module Type Slot
ControlNet I/O Action Channel 2 Configuration
MONITOR NODE 1
Fault Action
Idle Action
Fault Action From Idle Idle Idle Idle Idle Idle Idle Idle Idle
General Utility F7
0 1 2 3 4 5 6 7
1794Digital 1794IE8/A 1794OE4/A 1794IE4XOE2/A 1794Digital 1794Digital 1794Digital 1794Digital
Reset Reset Safe Safe Reset Reset Reset Reset
Reset Reset Reset Reset Reset Reset Reset Reset
Channel Overview F4
Press a function key. > Rem Prog Forces:None Map Monitor F2
Define LclRack F7
5/40C File CN Edit Actions F9
Move cursor to
If you want to:

Do this: Press [Esc]or [F2]Map Monitor Press [F7]Define LclRack
go to the ControlNet I/O Mapping (Monitor) screen define the characteristics of the local chassis Important: This option is not available if you are programming online. view a module's fault action i.e., the action that it takes when it faults
Map Monitor F2
Look at the module's field in the Fault Action column Reset changes all outputs to zero Hold Last maintains all current output values Safe changes all outputs to user specified fail-safe values Look at the module's field in the Idle Action column Reset changes all outputs to zero Hold Last maintains all current output values Safe changes all outputs to user specified fail safe values Look at the module's field in the Fault Action From Idle column Idle uses the idle action Fault uses the fault action Press [F9]Edit Actions
Move cursor to
a 1794 I/O entry
view a module's idle action i.e., the action that it takes when it becomes idle view a module's fault action from idle i.e., the action that it takes when it faults from idle go to the ControlNet I/O Action (Edit) screen
Monitor Actions F9
5-11
Chapter 5
Using the ControlNet Channel 2 Status Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet Channel 2 Status screen.
Online Program F1
or
Offline Program F3
Frames transmitted good: received good: total received: Network Capacity update time overload: Moderator Node: mismatch events: Misc out of step events: commands received: Press a function key. > Rem Prog Forces:None Clear Unlock Counter Counter F1 F2 0 0 0
ControlNet Channel 2 Status COUNTERS LOCKED media usage: A Only channel A errors: 0 channel B errors: n/a channel warnings: none
transmitted aborted: received aborted: received bad:
0 0 0
General Utility F7
0 1 0
blockage:
unheard occurrences:
Channel Overview F4
0 0
network silent: collisions:
0 0
noise detected:
5/40C File CN Chan 2 Config F9
Move cursor to
If you want to: clear all the ControlNet diagnostic counters
Do this: Press [F1]Clear Counter
toggle to lock all the counters on the screen (while they 1. Press [F2]Lock Counter continue to run in the background); then toggle back to 2. Press [F2]Unlock Counter unlock the counters so that they are updated continuously go to the ControlNet Node Information (Monitor) screen Press [F9]Chan 2 Config Press [Esc] go to the Channel Overview screen
Channel 2 Status F9
5-12
Chapter 5
This status field:

COUNTERS LOCKED
Word; Bits:x
Displays:y when the display of the counters stops changing the counters continue to run in the background; current values are continuously updated when COUNTERS LOCKED is not displayed the media redundancy characteristic for the ControlNet channel A/B, A Only, or B Only
media usage Frames transmitted good
6; 15 08 5; 07 00 5; 15 08 9; 07 00 7; 07 00 7; 15 08 6; 07 00 12; 07 00 8; 15 08 8; 07 00 9; 15 08 23; 07 06 10; 07 00 11; 07 00 15; 15 08 16; 15 08 16; 07 00
number of good frames transmitted
transmitted aborted received good
number of frames that could not be transmitted completely and were aborted during transmission number of good frames received on the active channel
received aborted received bad total received channel A errors
number of frames received that were aborted during transmission on the active channel number of unusable frames received on the active channel number of frames good and bad received on the active channel number of frames received on channel A that were unusable independent of the active channel channel selected for reception number of frames received on channel B that were unusable independent of the active channel channel selected for reception any channel that is receiving a low level of unusable frames i.e., frames containing data errors number of times that a NUI passes with no opportunity to transmit number of times that a NUI does not contain enough room to allow the transmission of a particular frame network address of the node that is transmitting the moderator frame always the lowest active network address number of times a moderator frame was received with network parameters different from those in the receiving node number of times a node can receive a frame from a lower network address but cannot receive a moderator number of times any event prevents a frame from being transmitted in the NUI in which it should be y p g t itt d transmitted number of times a node cannot hear any network activity for three consecutive NUIs number of times that a start of frame could not be detected number of station commands received directly from the network that bypass the node's host processor number of times that a node prevents the transmission of a frame because it would cause a collision to occur
channel B errors
channel warnings Network Capacity update time overload blockage
moderator node
mismatch events
unheard occurrences
Misc out of step events
10; 15 08 13; 15 08 14; 15 08 17; 15 08 14; 07 00
network silent
noise detected commands received
collisions
x y
In user specified Diagnostics File All counters display only the status of the node being examined
5-13
Chapter 5
Using the ControlNet WHO ACTIVE Active Node Identification Screen

Important: Keep the following in mind: ControlNet WHO screens are available only when your programming device is communicating through a 1784-KTC card, 1784-KTCx card, or 1770-KFC interface on the ControlNet network. When you view the WHO screens while your ControlNet system is operating, you affect the performance of unscheduled I/O operations.
6200 Main Menu
The ControlNet WHO ACTIVEActive Node Identification screen displays the active nodes up to the number of maximum unscheduled nodes. Follow the steps on the left to go to the ControlNet WHO ACTIVEActive Node Identification screen.
+ ControlNet WHO ACTIVE Active Node Identification + | 01 5/40C CN | | 02 1771-ACN | | 03 5/20C | | 04 1794-ACN | | 05 | | 06 | | 07 | | 08 | | 09 | | 10 | | 11 | | 12 | | 13 | | 14 | | 15 | + ESC exits [ WHO rate = 4 sec ][ Maximum Unscheduled Nodes = 15 ]+ Press a function key, or page up or page down. Net Channel A Status: Cable Good Net Channel B Status: Cable Inactive Online Node Channel Network Save Who Program Diags Diags Diags Config Rate F1 F2 F5 F6 F9 F10
WHO F5
WHO Active F5
If you want to: attach to the PLC 5 processor node of the highlighted entry go to the ControlNet WHO ACTIVE Active Node Status screen go to the ControlNet WHO ACTIVE Channel Status screen go to the ControlNet WHO ACTIVE Network Status screen save the current ControlNet WHO configuration as the permanent ControlNet WHO configuration enter a new ControlNet WHO rate go to the ControlNet WHO screen
Press:
[F1]Online Program [F2]Node Diags [F5]Channel Diags [F6]Network Diags [F9]Save Config [F10]WHO Rate [Esc]
5-14
Chapter 5
This field: Net Channel Status Line
Displays: the status of channel A and channel B Cable Good = channel is usable Cable WARN = channel is experiencing problems but still usable Cable FAULTED = channel is not usable Cable Inactive = channel unused (in non redundant network)
5-15
Chapter 5
Using the ControlNet WHO ACTIVE Active Node Status Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet WHO ACTIVE Active Node Status screen.
+ ControlNet WHO ACTIVE Active Node Status + | | |Frames media usage: A Only| | transmitted good: 0 transmitted aborted: 0 channel A errors: 0| | received good: 0 received aborted: 0 channel B errors: 0| | total received: 0 received bad: 0 channel warnings: none| | | |Network Capacity | | update time overload: 0 blockage: 0 | | | |Moderator Node: 1 | | mismatch events: 0 unheard occurrences 0 | | | |Misc | | out of step events: 0 network silent: 0 noise detected: 0| | commands received: 0 collisions: 0 | + ESC exits [ WHO rate = 4 sec ]+ Press a function key. Remote Program Clear Lock Counter Counter F2 F3 PLC5/40C Series C Revision A CNET Node 1 Save Who Config Rate F9 F10
WHO F5
WHO Active F5
Node Diagnostics F2
If you want to: clear all the ControlNet diagnostic counters toggle to lock all the counters on the screen (while they continue to run in the background); then toggle back to unlock the counters so that they are updated continuously
Do this: Press [F2]Clear Counter 1. Press [F3]Lock Counter 2. Press [F3]Unlock Counter
save the current ControlNet WHO configuration Press [F9]Save Config as the permanent ControlNet WHO configuration enter a new ControlNet WHO rate go to the ControlNet WHO ACTIVE Active Node Identification screen Press [F10]WHO Rate Press [Esc]
For descriptions of the status fields on the ControlNet WHO ACTIVE Active Node Status screen, see page 5-13.
5-16
Chapter 5
Using the ControlNet WHO ACTIVE Channel Status Screen

6200 Main Menu
Follow the steps on the left to go to the ControlNet WHO ACTIVE Channel Status screen.
+ ControlNet WHO ACTIVE Channel Status + | Node Active Channel A Channel B Bad frame received from node number | | Channel Status Status most recent to least recent | || | 01 A Good Inactive | | 02 A Good Inactive | | 03 A Good Inactive | | 04 A Good Inactive | | 05 | | 06 | | 07 | | 08 | | 09 | | 10 | | 11 | | 12 | + ESC exits [ WHO rate = 4 sec ][ Maximum Unscheduled Nodes = 12 ]+ Press a function key, or page up or page down.
WHO F5
WHO Active F5
Channel Diagnostics F5
Net Channel A Status: Cable Good
Net Channel B Status: Cable Inactive Network Save Who Diags Config Rate F6 F9 F10
If you want to: go to the ControlNet WHO ACTIVE Network Status screen save the current ControlNet WHO configuration as the permanent ControlNet WHO configuration enter a new ControlNet WHO update rate go to the ControlNet WHO ACTIVE Active Node Identification screen This field:
Node Active Channel Channel A Status
Press:
[F6]Network Diags [F9]Save Config [F10]WHO Rate [Esc]
Displays: a device's network address the channel that the node is using the status of the channel A for the specified node Good = channel A is receiving no unusable frames WARN = channel A is receiving a low level of unusable frames FAULTED = channel A is receiving a high level of unusable frames; it is not usable Inactive = channel A is not currently active
5-17
Appendix
A
0 to 60 C (32 140 F) 40 to 85 C ( 40 to 185 F) 5 to 95% (without condensation)
Processor Specifications
Heat Dissipation Environmental Conditions
54 BTU/hr Operating Temperature: Storage Temperature: Relative Humidity:
Shock and Vibration
Vibration Testing (operating and non operating): 1 g @ 10 to 500 Hz 0.012 inches peak to peak displacement Shock: Operating . . . . . . 30 g peak acceleration for 111 ms duration Non operating . . . . 50 g peak acceleration for 111 ms duration Maximum Variations at 60 C: Typical Variations at 20 C: Timing Accuracy: 1770 XYC 1785 ME16 1785 ME32 1785 ME64 1785 M100
Time of Day Clock/Calendar Battery Memory Modules
5 min per month 20 s per month

1 program scan
I/O Modules
Bulletin 1771 I/O, 1794 I/O, 1746 I/O, and 1791 I/O including 8 , 16 , 32 pt, and intelligent modules 2 slot Any mix of 8 pt modules 16 pt modules must be I/O pairs No 32 pt modules 1 slot y p Any mix of 8 or 16 pt modules 32 pt modules must be I/O pairs d l b i 1/2 slot Any mix of 8 ,16 , or 32 pt modules Serial DH+ DH using 1785 KA Remote I/O ControlNet 3 lbs, 2 oz (1.42 kg) 3 lbs, 3 oz (1.45 kg)
Hardware Addressing
Communication
Location Weight Keying Agency Certification (When product is marked)
1771 A1B, A2B, A3B, A3B1, A4B, AM1, AM2 chassis; left most slot PLC 5/40C: PLC 5/20C:
Between 40 and 42 Between 54 and 56 CSA Class I, Division 2, Groups A, B, C, D UL listed
A-1
Appendix A
Processor Specifications
PLC 5/20C Maximum User Memory Words Maximum Total I/O Program Scan Time Maximum Non discrete I/O Data Transfer Data Table Size Transmission Rate Network Update Time (NUT) Number of ControlNet Ports Number of Redundant Media ControlNet Ports Maximum Number of Nodes per Link without a Repeater ControlNet I/Oy Maximum Number of Nodes per Link with Repeaters Maximum Link Cable Length without a Repeater Maximum Link Cable Length with Repeaters Maximum Number of Repeaters in Series per Link Maximum Number of Segments in Series per Link Transmission Rate Any Mix Complimentary 16K 512 512 in and 512 out
PLC 5/40C 48Kx 2048 2048 in and 2048 out
0.5 ms per K word (bit logic) 2 ms per K word (typical) 1000 words in and 1000 words out 5M bit/s 2 100 ms (user selectable) 1 1 48 with 250 m (approx. 820 ft) cable length 107 1,000 m (approximately 3,280 ft) with 2 nodes 500 m (approximately 1,640 ft) with 32 nodes 250 m (approximately 820 ft) with 48 nodes 6,000 m (approximately 19,680 ft) with 2 nodes 3,000 m (approximately 9,840 ft) typical 5 6 57.6K bit/s 115.2K bit/s 230.4K bit/s 10 ms per rack @ 57.6K bit/s 7 ms per rack @ 115.2K bit/s 3 ms per rack @ 230K bit/s 4 12 1 1 1 1 16 3.0 A 2.7 A 6.2.1, for more information. 16 60 2 0
I/O Scan Time (Typical) Non ControlNet Remote I/O Maximum Number of Remote I/O Racks Maximum Number of Remote I/O Devices Number of Ports Configurable for DH+ or Remote I/O (Adapter or Scanner) Number of Dedicated DH+ Ports Number of Serial Ports Number of Coprocessor Ports Maximum Number of MCPs Backplane Current Load
x The PLC
Maximum Typical
y See the ControlNet Cable System Planning and Installation Manual, publication 1786
5/40C processor has a limit of 32K words per data table file.
A-2
Appendix
Processor Status File
Processor status data is stored in data-file 2.
S:0 S:2
This word of the status file: S:0
Stores: Arithmetic flags bit 0 = carry bit 1 = overflow bit 2 = zero bit 3 = sign Processor status and flags Bit Description 0 RAM checksum is invalid at power up 1 processor in Run mode 2 processor in Test mode 3 processor in Program mode 4 processor burning EEPROM 5 enabled download operation 6 enabled test edit mode 7 mode select switch in Remote position 8 forces enabled 9 forces present 10 processor successfully burned EEPROM 11 performing online programming 12 processor in Debug mode 13 user program checksum done 14 last scan of ladder or SFC step 15 processor started fist program scan or the first scan of the next step
in an SFC
S:1
S:2
Switch setting information bits 0-7 DH+ station number bit 11 12 are set based on the I/O chassis backplane switches bit 12 bit 11 = I/O chassis addressing 0 0 illegal 1 0 1/2 slot 0 1 1 slot 1 1 2 slot bit 13: 1 = load from EEPROM bit 14: 1 = RAM backup not configured bit 15: 1 = memory unprotected
B-1
Appendix B
S:3 10
This word of the status file: S:3 to S:6
Stores: Active Node table for channel 1A Word Bits DH+ Station # 3 0 15 00 17 4 0 15 20 37 5 0 15 40 57 6 0 15 60 77 Global status bits: low 8 bits rack fault bits for racks 0 7 high 8 bits rack queue full bits for racks 0 7 Last program scan (in ms) Maximum program scan (in ms) Minor fault (word 1) Bit Description 0 battery is missing or low (replace in 1 2 days) 1 DH+ table has changed (active node table) 2 STI delay too short, interrupt program overlap 3 EEPROM memory transfer at power up 4 edits prevent SFC continuing 5 invalid I/O status file 6 memory-cartridge battery low 7 no more command blocks exist 8 not enough memory on the memory module to upload the program from the processor 9 no MCP is configured to Run 10 MCP not allowed 11 PII word number not in local rack 12 PII overlap 13 no command blocks exist to get PII 14 arithmetic overflow 15 SFC action overlap
S:7
S:8 S:9 S:10
B-2
Appendix B
S:11 S:12
Stores: Major fault Bit Description 0 corrupted program file (codes 10 19) 1 corrupted address in ladder file (codes 10 29) 2 programming error (codes 30 49) 3 SFC fault (codes 71 79) 4 error while assembling program (code 70) 5 start up protection fault 6 peripheral device fault 7 jumped to fault routine (codes 0 9) 8 watchdog faulted 9 system configured wrong (codes 80 89) 10 recoverable hardware error 11 MCP does not exist or is not ladder or SFC file 12 PII does not exist or is not ladder 13 STI does not exist or is not ladder 14 fault routine does not exist or is not ladder 15 fault routine file is not a ladder file Fault codes Code Description 09 user defined 10 failed data table check 11 bad user program checksum 12 bad integer operand type 13 bad mixed mode operand type 14 not enough operands for instruction 15 too many operands for instruction 16 bad instruction found 17 no expression end 18 missing end of edit zone 19 download aborted 20 indirect address out of range (high) 21 indirect address out of range (low) 22 attempt to access undefined file 23 file number less than 0 or greater than number of defined files; or, indirect reference to file 0, 1, 2; or bad file number 24 indirect reference to wrong file type 30 subroutine jump nesting level exceeded 31 too few subroutine parameters 32 jump to non ladder file 33 CAR routine not 68000 code 34 bad timer parameters entered 35 bad PID delta time entered 36 PID setpoint out of range 37 invalid I/O specified in an immediate I/O instruction 38 invalid use of return instruction 39 FOR loop missing NXT 40 control file too small 41 NXT instruction with no FOR 42 jump target does not exist 43 file is not an SFC 44 error using SFR 45 invalid channel number entered 46 IDI or IDO instruction length operand too long ( > 64 words) 47 69 reserved
S:12
B-3
Appendix B
S:12 S:16
This word of the status file: S:12 (continued)
Stores: Fault codes Code Description 70 duplicate labels 71 SFC subchart is already executing 72 tried to stop an SFC that is not running 73 maximum number of SFC subcharts exceeded 74 SFC file error 75 SFC contains too many active steps 77 SFC references a step, transition, subchart, or SC file that is missing, empty, or too small 78 SFC could not continue after power loss 79 error in downloading an SFC to a processor that cannot run SFCs or this specific PLC processor does not support this enhanced SFC 80 I/O configuration error 81 illegal setting of I/O chassis backplane switch 82 illegal cartridge type 83 user watchdog fault 84 error in user configured adapter mode block transfers 85 bad cartridge 86 cartridge incompatible with host 87 rack overlap (includes any adapter channel) 88 scanner channels are overloading the remote I/O buffer; too much data for the processor to process 90 coprocessor extensive memory test failed 91 coprocessor undefined message type 92 coprocessor illegal pool index 93 coprocessor illegal maximum pool size 94 coprocessor illegal ASCII message 95 coprocessor reported fault 96 coprocessor present signal lost 97 coprocessor illegal minimum pool size 98 coprocessor first/last 16 bytes RAM test failed 99 coprocessor to processor data transfer faulted 100 processor to coprocessor transfer failed 101 coprocessor end of scan transfer failed 102 file number specified for raw data transfer through the coprocessor is an illegal value 103 element number specified for raw data transfer through the coprocessor is an illegal value 104 size of the transfer requested through the coprocessor is an illegal size 105 offset into the raw transfer segment of the coprocessor is an illegal value 106 coprocessor transfer protection violation 200 ControlNet output transfer missed 201 ControlNet input data missed 202 ControlNet diagnostic data missed 203 ControlNet scheduled transmit data overflow 204 ControlNet configuration too complex for the PLC 5 processor Program file where fault occurred Rung number where fault occurred VME status file I/O Status File
S:13 S:14 S:15 S:16
B-4
Appendix B
S:17 S:27
Stores: Minor fault (word 2) Bit Description 0 BT queue full to remote I/O 1 queue full channel 1A 2 queue full channel 1B 3 queue full channel 2A 4 queue full channel 2B 5 no modem on serial port 6 remote I/O rack in local rack table; or, remote I/O rack is greater than the image size 7 plug firmware revision does not match processor firmware revision 8 ASCII instruction error 9 duplicate network address 10 DF1 master poll list error 11 protected processor data table element violation 12 protected processor file violation 13 using all 32 ControlNet MSGs 14 using all 32 ControlNet 1771 READ and/or 1771 WRITE CIOs 15 using all 8 ControlNet Flex I/O CIOs Processor clock year Processor clock month Processor clock day Processor clock hour Processor clock minute Processor clock second Indexed addressing offset User control bits Bit Description 0 Restart/continuous SFC: when reset, processor restarts at first step in SFC. When set, processor continues with active step after power loss or change to Run 1 Start up protection after power loss: when reset, no protection. When set, processor executes fault routine at power up (sets word 11, bit 5). 2 Define the address of the local rack: when reset, local rack address is 0. When set, local rack address is 1. 3 Set complementary I/O: when reset, complementary I/O is not enabled. When set, complementary I/O is enabled. 4 Local block transfer compatibility bit: when reset, normal operation. When set, eliminates frequent checksum errors to certain BT modules. 5 When set (1), delay adapter channel response by 1 s for compatibility with PLC 3 scanners. When reset (0), operate in normal response time. Rack control bits: low 8 bits I/O rack inhibit bits for racks 0 7 high 8 bits I/O rack reset bits for racks 0 7
S:18 S:19 S:20 S:21 S:22 S:23 S:24 S:26
S:27
B-5
Appendix B
S:28 S:61
This word of the status file: S:28 S:29 S:30 S:31 S:32
Stores: Program watchdog setpoint Fault routine file STI setpoint STI file number Global status bits: low 8 bits rack fault bits for racks 10 17 (octal) high 8 bits rack queue full bits for racks 10 17 Rack control bits: low 8 bits I/O rack inhibit bits for racks 10 17 high 8 bits I/O rack reset bits for racks 10 17 Global status bits: low 8 bits rack fault bits for racks 20 27 (octal) high 8 bits rack queue full bits for racks 20 27 Rack control bits: low 8 bits I/O rack inhibit bits for racks 20 27 high 8 bits I/O rack reset bits for racks 20 27 PII program file number PII module group PII bit mask PII compare value PII down count PII changed bit PII events since last interrupt STI scan time (in ms) STI maximum scan time (in ms) PII last scan time (in ms) PII maximum scan time (in ms) User program checksum Extended local I/O channel discrete transfer scan (in ms) Extended local I/O channel discrete maximum scan (in ms) Extended local I/O channel block transfer scan (in ms)
S:33
S:34
S:35
S:46 S:47 S:48 S:49 S:50 S:51 S:52 S:53 S:54 S:55 S:56 S:57 S:59 S:60 S:61
B-6
Appendix B
S:62 S:127
This word of the status file: S:62 S:63 S:64 S:76
Stores: Extended I/O channel maximum block transfer scan (in ms) Protected processor data table protection file number Number of remote block transfer command blocks being used by channel pair 1A/1B Number of slots in processor resident local rack 0 1 2 3 4 Illegal 4 slots 12 slots 8 slots 16 slots
S:77 S:78
Communication time slice for communication housekeeping functions (in ms) MCP I/O update disable bits Bit 0 for MCP A Bit 1 for MCP B etc.
S:79
MCP inhibit bits Bit 0 for MCP A Bit 1 for MCP B etc.
S:80 S:127
MCP file number MCP scan time (in ms) MCP max scan time (in ms) The above sequence applies to each MCP; therefore, each MCP has 3 status words. For example, word 80: file number for MCP A word 81: scan time for MCP A word 82: maximum scan time for MCP A word 83: file number for MCP B word 84: scan time for MCP B etc.
B-7
Appendix
ControlNet Instruction Set
ControlNet I/O Transfer Instruction

Instruction CIO CNET I/O TRANSFER Control block CT21:50 ControlNet I/O Transfer CT Description If the input conditions go from false to true, the data is transferred according to the instruction parameters you set when you enter the ControlNet I/O transfer instruction. The Control Block (CT21:50) contains status and instruction parameters. ( g ) You cannot use N (integer) control blocks on the ControlNet network. C lN k For continuous CIOs, condition the rung to be true for only one scan.
Status Bits TO Time Out Bit EW Enabled Waiting Bit CO Continuous Bit ER Error Bit DN Done Bit ST Start Bit EN Enable Bit
Message Instructions on a ControlNet Network

Instruction Message MSG SEND/RECEIVE MESSAGE MSG Control block MG10:10 Status Bits TO Time Out Bit EW Enabled Waiting Bit CO Continuous Bit ER Error Bit DN Done Bit ST Start Bit EN Enable Bit Description If the input conditions go from false to true, the data is transferred according to the instruction parameters you set when you enter the message instruction. The Control Block (MG10:10) contains status and instruction parameters. You cannot use N (integer) control blocks on the ControlNet network. network For continuous MSGs, condition the rung to be true for only one scan.
C-1
Appendix C
ControlNet Instruction Set
Immediate Data I/O Instructions

Instruction IDI IMMEDIATE DATA INPUT Data file offset Length Destination 232 10 N11:232 Immediate Data Input IDI Description If the input conditions are true, an immediate data input is initiated that updates the destination file from the private buffers before the next normal input image update. The Data file offset (232) is where the data is stored. The Length (10) identifies the number of words in the transfer it can be an immediate value ranging from 1 to 64 or a logical address that specifies the number of words to be transferred. The Destination (N11:232) is the destination of the words to be transferred. The Destination should be the matching data table address in the DIF except when you use the instruction to ensure data block integrity in the case of Selectable Timed Interrupts (STIs). See page 4 7. If the input conditions are true, an immediate data output is initiated that updates the private memory output buffers from the source file before the next normal output image update. The Data file offset (175) is the offset into the buffer where the data is stored. The Length (24) identifies the number of words in the transfer it can be an immediate value ranging from 1 to 64 or a logical address that specifies the number of words to be transferred. The Source (N12:175) is the source of the words to be transferred. The Source should be the matching data table address in the DOF except when you use the instruction to ensure data block integrity in the case of Selectable Timed Interrupts (STIs). See page 4 7.
IDO IMMEDIATE DATA OUTPUT Data file offset Length Source 175 24 N12:175
Immediate Data Output IDO
More
For detailed information on the instruction set for programming PLC-5 processors, see the Enhanced and Ethernet PLC-5 Programmable Controllers User Manual, publication 1785-6.5.12, and the PLC-5 Programming Software Instruction Set Reference, publication 6200-6.4.11.
C-2
Appendix
ControlNet I/O Map Entry Status Words and Error Messages
I/O Map Entry Status Words
The ControlNet status file is an integer data-table file that you specify and configure with the I/O map for scheduled-I/O usage. It containing status information about all of the ControlNet networks scheduled I/O connections. Each I/O map-table entry has a status-file offset field pointing to three status words associated with the connection.
First Word
15 14 13 0 12 11 10 09 0 08 07 06 0 05 04 03 0 02 01 00 0
Reserved
Data Invalid Connection Error
Reset Reserved Inhibit
Second and Third Words

15 14 13 0 12 11 10 09 0 08 07 06 0 05 04 03 0 02 01 00 0
Error Messages 15 14 13 0 12 11 10 09 0 08 07 06 0 05 04 03 0 02 01 00 0
If these status words are for a 1794 Flex I/O module and there is no connection error, any 1's set in bits 00 through 07 of the third word indicate errors in the corresponding slots (numbered 0 through 7)
If these status words are for a Peer In or a Peer Out and there is no connection error, a 1 set in bit 00 of the third word indicates that the other (peer) processor is in Run mode
D-1
Appendix D
Error Messages
Decimal Code Various Hex. Code Various
The following is a list of ControlNet error codes, messages, possible causes, and possible corrective actions:
Error Message Explanation / Possible Cause(s) Possible Corrective Action(s)
CONFIGURATION DATA CORRUPTED
More than one configured and/or Re-configure map entryoverlapping programmed data transfer is trying map table locations to use the same location in the data or table Re-enter overlapping ladder instructions There are too many words scheduled for transmission The network update time (NUT) is too small The target node is not configured Reduce the number of words scheduled for transmission Increase the network update time (NUT) Correctly configure the target node as an active node on the ControlNet network and save your ControlNet configuration
0x0002
SCHED BANDWIDTH NOT AVAILABLE
18
0x0012
TARGET NODE NOT RESPONDING
The ControlNet cable to the target Fix and/or reconnect the ControlNet cable to node is broken and/or disconnected the target node No power is being received by the target node The target node is offline Supply power to the target node Correctly configure the target node as an active node on the ControlNet network and save your ControlNet configuration Correct the map table entry
20
0x0014
DEST SLOT/MSG NOT PRESENT
The slot number that you entered for an adapter is not in the valid range The number that you entered for an peer to peer message is not in the valid range The peer to peer message map table entry in the target node is inhibited
Clear the inhibit bit in the map table entry of the target node No action required connection can be re established after the target node times out the old connection
256
0x0100
CONNECTION IN USE
The connection that the originating node is trying to use is already in use
260
0x0104
NODE TYPE MISMATCH
You entered a node type in the map Correct the map table entry table that does not match the target or node Replace the target node with the node type entered in the map table The originating node attempted to open a connection that is already being used by another node The connection that the originating node is trying to close is already closed The originating node attempted to open a connection with a larger size than the target node can support Delete or inhibit any other node's connection so that the preferred node can open the connection No action required
262
0x0106
CONNECTION USED BY OTHER NODE
263
0x0107
CONNECTION ALREADY CLOSED
265
0x0109
INVALID CONNECTION SIZE
Reduce the size that is entered in the map table or Use a rack with a greater number of slots or Use a rack with higher density Correctly configure the target node as an active node on the ControlNet network and save your ControlNet configuration
272
0x0110
NODE NOT CONFIGURED
The target node is offline The target node is not configured
D-2
Appendix D ControlNet I/O Map Entry Status Words and Error Messages
Decimal Code 273
Hex. Code 0x0111
Error Message
EXP NET PCKT TIME INVALID
Explanation / Possible Cause(s)
Possible Corrective Action(s)
The target node cannot produce the Increase the expected net packet time data at or faster than the expected entered in the map table net packet time entered in the map table The ControlNet cable to the target Fix and/or reconnect the ControlNet cable to node is broken and/or disconnected the target node Supply power to the target node Correctly configure the target node as an active node on the ControlNet network and save your ControlNet configuration Press the reset button on the target adapter No action required
511
0x01FF
INVALID WHEN NODE IS IDLE
The originating node attempted to open a No power is being received by the data transfer connection before a node target node connection was opened ti d The target node is offline
The target adapter is in Processor Restart Lockout 513 0x0201

CONNECTION ALREADY CLOSED
The connection that the originating node is trying to close has not been opened by the target node The ControlNet cable to the target node has become broken and/or disconnected Power is no longer being received by the target node
515
0x0203
CONNECTION TIMED OUT
Fix and/or reconnect the ControlNet cable to the target node Supply power to the target node
65281
0xFF01
CONNECTION REJECTED
The ControlNet cable to the target Fix and/or reconnect the ControlNet cable to node is broken and/or disconnected the target node No power is being received by the target node The target node is offline Supply power to the target node Correctly configure the target node as an active node on the ControlNet network and save your ControlNet configuration Change your program so that it does not attempt to set the attribute Insert a module that can have this attribute set Increase the length of the transfer Increase the size of the data table to accommodate the transfer length Decrease the length of the transfer
65294
0xFF0E
ATTRIBUTE CANNOT BE SET
65299
0xFF13
NOT ENOUGH DATA
Your program attempted to set an attribute that cannot be set for a specific module e.g., a CIO instruction tried to send safe state data to a flex module that does not support safe state data The transfer length is zero The processor data table is too small
65301 65522
0xFF15 0xFFF2
TOO MUCH DATA CONFIG FROM MAP ENTRY FAILED
The transfer length is too large
The ControlNet cable to the target Fix and/or reconnect the ControlNet cable to node is broken and/or disconnected the target node No power is being received by the target node Supply power to the target node
The node or slot contains the wrong Insert the proper module in the correct slot of module type the target node An incorrect module type was entered in the map table 65523 0xFFF3
CONTROLNET TRANSFER QUEUE FULL The immediate CIO transfer could
Enter the correct module type in the map table entry
Keep the number of active 1771 READ not be executed because the queue and/or 1771 WRITE CIOs at or under the is full maximum of 32
D-3
Appendix D
Decimal Code 65527
Hex. Code 0xFFF7
Error Message
MODULE TIMED OUT
Explanation / Possible Cause(s)
Possible Corrective Action(s)
The node or slot contains the wrong Insert the proper module in the correct slot of module type the target node An incorrect module type was entered in the map table Enter the correct module type in the map table entry
65529
0xFFF9
COMM ERROR CAUSED LOSS OF DATA
A communication error between the Make sure that the proper module is properly module and adapter caused data to seated in the correct slot of the target node odu e a d adap e da a o be lost Make sure that the correct module type is entered in the map table entry module type the target node
65530
0xFFFA
MODULE DECLARED INVALID LENGTH The node or slot contains the wrong Insert the proper module in the correct slot of
An incorrect module type was entered in the map table 65531 0xFFFB
READ DATA INVALID
Enter the correct module type in the map table entry
The node or slot contains the wrong Insert the proper module in the correct slot of module type the target node An incorrect module type was entered in the map table Enter the correct module type in the map table entry
65532
0xFFFC
WRITE DATA INVALID
The node or slot contains the wrong Insert the proper module in the correct slot of module type the target node An incorrect module type was entered in the map table Enter the correct module type in the map table entry Increase the size of the data table to accommodate the transfer length
65533
0xFFFD
DATA TABLE TOO SMALL
The processor data table is too small
D-4
Allen Bradley Publication Problem Report

Pub. Name Cat. No. Check Problem(s) Type: Technical Accuracy Pub. No. Describe Problem(s): text Pub. Date
If you find a problem with our documentation, please complete and return this form.
Part No. Internal Use Only illustration
Completeness
What information is missing?
procedure/step example explanation
illustration guideline other
definition feature
info in manual (accessibility) info not in manual
Clarity
What is unclear?
Sequence
What is not in the right order?
Other Comments
Use back for more comments.
Your Name
Location/Phone Phone: (216)646 3166 FAX: (216)646 4320

PN 955107 82
Return to: Technical Communication, Allen Bradley Co., 1 Allen Bradley Drive, Mayfield Hts., OH 44124
Publication ICCG 5.21 August 1995
PLEASE FASTEN HERE (DO NOT STAPLE)
Other Comments
PLEASE FOLD HERE
NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH

POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705
PLEASE REMOVE
Index
Numbers
1770 CD, 1 14, 1 19 1770 KFC Communication Interface, 2 13 1770 KFC Communication Interface, 1 17 1771 Generic, 2 11 1771 N Series Analog Modules, 2 11 1771 AF, 1 13 1771 AS, 1 13 1771 DCM, 1 13 1771 IE, IF, and IFE Analog Input Modules, 2 11 1771 IL Isolated Analog Input Modules, 2 11 1771 IR RTD Input Modules, 2 11 1771 IS Multiplexer Input Modules, 2 11 1771 OF Analog Output Modules, 2 11 1771 OFE1, OFE2, and OFE3 Analog Output Modules, 2 11 1771 SN, 1 13 1771 ACN and ACNR ControlNet I/O Adapters, 2 13 1771 ASB, 1 13 1771 CFM Configurable Flowmeter Modules, 2 11, 2 12 1771 DE/A Absolute Encoder Modules, 2 11 1771 IJ and IK Encoder/Counter Modules, 2 11 1771 IXE Thermocouple/Millivolt Input Modules, 2 11 1771 IXHR High resolution Thermocouple/Millivolt Input Modules, 2 11 1771 QA Stepper Positioning Modules, 2 11 1771 QB Linear Positioning Modules, 2 11 1771 QC Servo Positioning Modules, 2 11 1771 VHSC Very High speed Counter Modules, 2 11 1772 SD, SD2, 1 13 1775 S4A, S4B, 1 13 1775 SR, 1 13 1784 CP10, 1 16 1784 CP8, 1 16, 1 19
1784 KL, 1 19 1784 KL/B, 1 19 1784 KTC Communication Card, 2 13 1784 CP, 1 16, 1 19 1784 CP11, 1 16 1784 CP13, 1 16, 1 19 1784 CP5, 1 19 1784 CP6, 1 16, 1 19 1784 CP7, 1 16, 1 19 1784 KT, KT2, 1 16, 1 19 1784 KTC Communication Card, 1 17 1784 KTCx Communication Card, 1 17, 2 13 1784 KTK1, 1 19 1784 KTx, 1 16, 1 19 1784 KTxD, 1 16, 1 19 1784 PCM5, 1 16, 1 19 1784 PCM6, 1 16, 1 19 1784 PCMK, 1 16, 1 19 1786 CP, 1 17 1786 BNC BNC Connector, 1 20 1786 BNCJ BNC Connector, 1 20 1786 BNCJI BNC Connector, 1 20 1786 BNCP BNC Connector, 1 20 1786 CP ControlNet Network Access Cable, 1 20 1786 CTK ControlNet Tool Kit, 1 20 1786 RG 6 Quad Shield Cable, 1 20 1786 RPT Repeater, 1 20 1786 RPTD Repeater, 1 20 1786 TPR Tap, 1 15, 1 20 1786 TPS Tap, 1 15, 1 20 1786 TPVR Tap, 1 20 1786 TPVS Tap, 1 20 1786 TPYR Tap, 1 15 1786 TPYS Tap, 1 15 1786 XT BNC Terminator, 1 20 1794 flex I/O data transfer mapping, 2 12 features, 2 12 number of map table entries required, 2 12
I2
Index
1794 ACN ControlNet Flex I/O Adapter, 2 13 1794 IE4XOE2/A Analog I/O Modules, 2 12 1794 IE8/A Analog Input Modules, 2 12 1794 OE4/A Analog Output Modules, 2 12 6008 SQH1, SQH2, 1 13
A
automatic I/O mapping, 2 7 avoiding electrostatic damage, 1 3
Misc collisions, 5 13 commands received, 5 13 network silent, 5 13 noise detected, 5 13 out of step events, 5 13 Network Capacity blockage, 5 13 mismatch events, 5 13 moderator node, 5 13 unheard occurrences, 5 13 update time overload, 5 13 CIOs. See ControlNet I/O Transfer instructions clock, processor, A 1 communication, specifications, A 1 communication ports, location of on PLC 5/20C, 1 4 on PLC 5/40C, 1 5 configuring your ControlNet system, where to go, 3 1 connecting a programming terminal, 1 16 connecting to a ControlNet network, 1 15 connection, definition of, ii ControlNet cabling, 1 19 ControlNet I/O error messages, D 2 features, 2 1 files configured with map Data Input File (DIF), 2 9, 2 10 Data Output File (DOF), 2 9, 2 10 Default Configuration File, 2 9 I/O Status File, 2 9 I/O forcing, 2 5 immediate data transfer operations, 2 5 map table creating, 2 7 entries, 2 7 map table entry configuration file, 2 10 module/message type, 2 9 mapping scheduled data transfers, 2 7 map table entry fields Expected Network Packet Time (ENPT), 2 9 Input File and Size, 2 10 Module/Message Type, 2 9 Node, 2 9 Output File and Size, 2 10 Slot/Message, 2 9 Status File Offset, 2 10 scheduled data transfer operations, 2 1 descriptions of, 2 2
B
battery, specifications, A 1 battery compartment, 1 4, 1 5 location of on PLC 5/20C, 1 4 on PLC 5/40C, 1 5 battery life, 1 9 battery status indicator, 1 4, 1 5
C
cables, remote I/O, 1 12 cabling, 1 19 certification, A 1 Channel 0, 1 4, 1 5 Channel 0 communication ACTIVE/FAULT status indicator, 1 4, 1 5 channel 1 status indicators, 1 5 Channel 1A, 1 4, 1 5, 2 15 Channel 1B, 1 4, 1 5, 2 15 Channel 2, 1 4, 1 5 Channel 2 ControlNet status indicators, 1 4, 1 5 Channel 2 Status screen, fields COUNTERS LOCKED, 5 13 Frames channel A errors, 5 13 channel B errors, 5 13 channel warnings, 5 13 received aborted, 5 13 received bad, 5 13 received good, 5 13 total received, 5 13 transmitted aborted, 5 13 transmitted good, 5 13 media usage, 5 13
Index
I3
scheduled discrete I/O data transfer, 2 1 scheduled operations discrete I/O data transfer, 2 2 non discrete I/O data transfer, 2 2 peer to peer communication, 2 2 understanding, 2 1 unscheduled data transfer operations, 23 unscheduled non discrete I/O data transfer, 2 3 unscheduled operations ControlNet I/O Transfer (CIO) instruction, description, C 1 ControlNet I/O Transfer (CIO) instructions description, 2 4 features, 2 4 I/O transfer instructions, programming, 44 immediate data I/O instructions, programming, 4 6 ladder rung messages, 2 3 messaging from programming devices, 23 non discrete I/O data transfer, description, 2 4 non discrete I/O data transfers description, C 1 features, 2 4, C 1 peer to peer messaging instructions, programming, 4 2, C 1 peer to peer messaging, 2 3 description, 2 4 features, 2 4 ControlNet I/O automatic mapping, 2 7 ControlNet I/O mapping automatic, 2 7 reserving rack space for remote I/O linked racks before mapping, 2 7 understanding, 2 7 discrete I/O data transfer mapping, 2 10 mapping data transfers, 2 9 non discrete I/O data transfer mapping, 2 10 modules that may be accommodated, 2 12 ControlNet I/O status indicator, 1 4, 1 5 ControlNet I/O Transfer (CIO) instructions, 2 3, 2 4, C 1 ControlNet immediate data I/O instructions Immediate Data Input (IDI), 2 6, C 2 Immediate Data Output (IDO), 2 6, C2 process, C 2
ControlNet immediate data I/O instructions, process, 2 6 ControlNet Immediate Data Input (IDI) instruction, 2 6 ControlNet Immediate Data Output (IDO) instruction, 2 6 ControlNet network definition of, ii locating additional information, iv ControlNet Network Access Port (NAP), 1 4, 1 5 ControlNet PLC 5/20C processor, identifying components of, 1 4 ControlNet PLC 5/40C processor, identifying components of, 1 5 ControlNet processor configuring your ControlNet system, 3 1 fault codes, B 4 installing, 1 1 planning to use, 2 1 programming your system, 4 1 ControlNet system cabling, 1 19 configuring, 3 1 automatically adding nodes to the node list, 3 5 automatically mapping modules and messages that are not mapped, 38 changing a 1794 I/O module's fault action, 2 4, 3 10, 4 4 changing a 1794 I/O module's fault action from idle, 3 11 changing a 1794 I/O module's idle action, 2 4, 3 11, 4 4 changing a 1794 system's fault action, 3 10 changing a 1794 system's fault action from idle, 3 10 changing a 1794 system's idle action, 3 10 changing a module or message's type, 37 changing a node's series or revision, 35 changing a node's status, 3 5 changing a node's type, 3 5 changing the Expected Network Packet Time (ENPT) for a module or message, 3 7 clearing information about a module or message, 3 8 clearing information about all modules and messages, 3 8
I4
Index
copying node information to a new address, 3 5 defining local rack characteristics, 3 3 deleting a module or message, 3 9 deleting a node from the node list, 35 deleting all modules and messages, 39 deleting all nodes from the node list, 35 editing 1794 I/O module action, 3 10 editing ControlNet I/O mapping, 3 6 editing node information, 3 4 editing the ControlNet node information configuration, 34 entering the length of cable between repeaters, 3 4 entering the number of coax repeaters, 34 entering the number of fiber optic repeaters, 3 4 inserting an entry at an unused slot or message address, 3 9 inserting nodes into the node list, 3 5 manually entering the amount of information received from a module or message, 3 7 manually entering the amount of information sent to a module or in a message, 3 7 manually entering the amount of information to be stored in the I/O configuration file for a module, 38 manually entering the destination file for information received from a module or message, 3 7 manually entering the file for storing the I/O configuration needed for a module, 3 8 manually entering the source file for information sent from a module or in a message, 3 7 matching the processor and ControlNet configurations, 3 2 moving a node description to a new address, 3 5 specifying the Data Input File (DIF), 36 specifying the Data Output File (DOF), 36 specifying the Default Configuration File, 3 6 specifying the Diagnostics File, 3 4 specifying the I/O Status File, 3 6 specifying the maximum scheduled node address, 3 5
specifying the Network Update Time (NUT), 3 4, 3 7 specifying the number of coax repeaters, 3 4 specifying the redundancy characteristic of the ControlNet media, 3 5 viewing the maximum percent of scheduled bandwidth, 3 5 viewing the number of scheduled I/O map table entries indicating data transfers to and from the processor, 3 7 viewing the percent of scheduled bandwidth used in the worst case, 37 viewing the percentage of the Data Input File (DIF) being used, 3 7 viewing the percentage of the Data Output File (DOF) being used, 37 configuring nodes, 2 7, 2 14 locating additional information, iii monitoring, 5 1 viewing a 1794 system's fault action, 5 11 viewing a 1794 system's fault action from idle, 5 11 viewing a 1794 system's idle action, 5 11 network maintenance, 2 3 network update cycle, what happens in, 23 scheduled operations, 2 3 selecting devices to connect, 2 13 setting the switches, 1 11 troubleshooting, 5 1 unscheduled operations, 2 3 using ControlNet PLC 5 processors in, 2 13 ControlNet WHO ACTIVE Network Status screen, fields Bad Frames Received, 5 19 Errors / 100,000 Frames Chan A, 5 19 Errors / 100,000 Frames Chan B, 5 19 Good Frames Received, 5 19 Node, 5 19 Total Errors Chan A, 5 19 Total Errors Chan B, 5 19
D
Data Input File description, 2 9, 2 10 specifying, 3 6
Index
I5
Data Output File description, 2 9, 2 10 specifying, 3 6 Default Configuration File description, 2 9 specifying, 3 6 defining local rack characteristics, 3 3 DH+, trunk cable/drop cable connection, 1 14 DH+ programming terminal connection (PTC), 1 4, 1 5 Diagnostics File, 5 13 DIF. See Data Input File discrete I/O data transfer definition of, ii description, 2 2 discrete I/O data transfers, number of map table entries required, 2 9 discrete I/O data transfer mapping, 2 10 disposing of the processor battery, 1 9 DOF. See Data Output File drop cable, definition of, ii
I/O status, 2 9 input, 2 10 input image, 2 1, 2 9, 2 10 output, 2 10 output image, 2 1, 2 10 processor status, B 1 force status indicator, 1 4, 1 5 frame, definition of, ii front panel PLC 5/20C processor, 1 4 PLC 5/40C processor, 1 5
H
handling the processor, 1 3 heat dissipation, specifications, A 1
I
I/O, ControlNet, 2 1 automatic mapping, 2 7 automatically mapping modules and messages that are not mapped, 38 changing a module or message's type, 37 changing the Expected Network Packet Time (ENPT) for a module or message, 3 7 clearing information about a module or message, 3 8 clearing information about all modules and messages, 3 8 deleting a module or message, 3 9 deleting all modules and messages, 3 9 discrete I/O data transfer mapping, 2 10 editing 1794 I/O module action, 3 10 editing mapping, 3 6 files configured with map Data Input File (DIF), 2 9, 2 10 Data Output File (DOF), 2 9, 2 10 Default Configuration File, 2 9 I/O Status File, 2 9 I/O forcing, 2 5 immediate data transfer, 2 5 inserting an I/O entry into the node list, 39 manually entering the amount of information received from a module or message, 3 7 manually entering the amount of information sent to a module or in a message, 3 7
E
ENPT. See Expected Network Packet Time environment, specifications, A 1 error codes, D 2 Expected Network Packet Time 1771 non discrete I/O data transfer mapping default, 2 11, 2 12 range, 2 11 1794 flex I/O data transfer mapping default, 2 12 range, 2 12 description, 2 9
F
fault codes, B 4 files configuration, 2 10 configured with I/O map for scheduled I/O usage, 2 9 Data Input, 2 9, 2 10, 3 6 Data Output, 2 9, 2 10, 3 6 Default Configuration, 2 9, 3 6 Diagnostics, 3 4, 5 13 I/O Status, 2 9, 2 10, 2 16, 3 6, D1
I6
Index
manually entering the amount of information to be stored in the I/O configuration file for a module, 3 8 manually entering the destination file for information received from a module or message, 3 7 manually entering the file for storing the I/O configuration needed for a module, 3 8 manually entering the source file for information sent to a module or in a message, 3 7 map table creating, 2 7 entries, 2 7 maximum number of entries, 2 9 map table entry configuration file, 2 10 module/message type, 2 9 mapping, 2 7 mapping data transfers, 2 9 map table entry fields Expected Network Packet Time (ENPT), 2 9 Input File and Size, 2 10 Module/Message Type, 2 9 Node, 2 9 Output File and Size, 2 10 Slot/Message, 2 9 Status File Offset, 2 10 non discrete I/O data transfer mapping, 2 10 modules that may be accommodated, 2 12 reserving rack space for remote I/O linked racks before mapping, 2 7 scheduled data transfer, 2 1 scheduled discrete I/O data transfer, 2 1 scheduled operations discrete I/O data transfer, 2 2 non discrete I/O data transfer, 2 2 peer to peer communication, 2 2 specifying the Data Input File (DIF), 3 6 specifying the Data Output File (DOF), 36 specifying the Default Configuration File, 36 specifying the I/O Status File, 3 6 specifying the Network Update Time (NUT), 3 7 unscheduled I/O data transfer instructions, 4 4 immediate data I/O instructions, 4 6 Message instruction, 2 4, 4 2, C 1 non discrete I/O data transfers, 2 4, C1 non discrete I/O data transfer instructions, 4 4
unscheduled data transfer, 2 3 unscheduled non discrete I/O data transfer, 2 3 unscheduled operations messaging from programming devices, 23 non discrete I/O data transfer, 2 3 peer to peer messaging, 2 3 viewing the number of scheduled I/O map table entries indicating data transfers to and from the processor, 37 viewing the percentage of the Data Input File (DIF) being used, 3 7 viewing the percentage of the Data Output File (DOF) being used, 3 7 I/O addressing, A 1 I/O forcing, 2 5 I/O map table, definition of, ii I/O map entry status words, D 1 I/O modules, specifications, A 1 I/O Status File, specifying, 3 6 I/O status indicator, 5 3 IDI. See ControlNet Immediate Data Input instruction IDO. See ControlNet Immediate Data Output instruction IIN. See Immediate Input instruction Immediate Data Input (IDI) instruction, C 2 Immediate Data Output (IDO) instruction, C2 immediate data transfer operations, 2 5 immediate I/O, process, 2 6 Immediate I/O instructions, 2 6 Immediate Input (IIN) instruction, 2 6 Immediate Output (IOT) instruction, 2 6 indicators PLC 5/20C, 1 4 PLC 5/40C, 1 5 installing keying bands for the processor, 17 installing the processor battery, 1 8 installing your processor checking your processor package, 1 2 connecting a programming terminal, 1 16 ControlNet connection, 1 17 DH+ connection, 1 16 serial channel, 1 16 connecting to a ControlNet network, 1 15
Index
I7
disposing of the battery, 1 9 handling the processor, 1 3 identifying the components of the processor, 1 4 installing a DH+ link, 1 14 installing a remote I/O link, 1 12 installing keying bands for the processor, 17 installing the battery, 1 8 installing the processor in the chassis, 1 12 locating additional information, 1 1 preparing for, 1 2 removing the processor from the chassis, 1 12 selecting cables ControlNet cables, 1 19 DH+ programming, 1 19 remote I/O, 1 19 serial, 1 18 selecting the ControlNet network address, 1 11 selecting the DH+ station address of Channel 1A, 1 10 setting the I/O chassis backplane switches, 1 6 setting the I/O chassis configuration plug, 17 specifying the serial interface of Channel 0, 1 11 where to go, 1 1 instructions ControlNet I/O Transfer (CIO), 2 4, C 1 how to use, 4 4 when to use, 2 12, 2 16 ControlNet Immediate Data Input (IDI), 2 6, C 2 how to use, 4 6 ControlNet Immediate Data Output (IDO), 2 6, C 2 how to use, 4 6 ControlNet Message (MSG), how to use, 42 Immediate Input (IIN), 2 6 Immediate Output (IOT), 2 6 Message (MSG), 2 4 how to use, C 1 when to use, 2 13 IOT. See Immediate Output instruction
L
ladder rung messaging, 2 3 link, definition of, ii
M
map table, 2 7 map table entries, 2 7 fields, 2 9 number required for data transfer types, 29 map table entry, definition of, ii maximum scheduled node, definition of, ii maximum unscheduled node, definition of, ii memory module space, 1 4, 1 5 memory modules, specifications, A 1 memory module space, location of on PLC 5/20C, 1 4 on PLC 5/40C, 1 5 Message instructions, 2 3, 2 4, C 1 monitoring ControlNet configuration and status screens, 5 5 MSGs. See Message instructions
N
NAP. See Network Access Port Network Access Port, 1 4, 1 5 definition of, ii when to use, 1 17 network address, definition of, ii Network Update Interval, 2 3, 3 4 definition of, ii Network Update Time, 3 4 definition of, ii specifying, 3 7 node, definition of, ii non discrete I/O data transfer definition of, ii description, 2 2 non discrete I/O data transfers, number of map table entries required, 2 9 non discrete I/O data transfer mapping, 2 10 1771 modules, 2 10 features, 2 11
K
keyswitch, location of on PLC 5/20C, 1 4 on PLC 5/40C, 1 5
I8
Index
number of map table entries required, 2 10 nonredundant media, 1 15 NUI. See Network Update Interval NUT. See Network Update Time
O
owner, definition of, ii
P
Peer In, 2 12 Peer Out, 2 12 planning to use your processor, where to go, 2 1 PLC 5 processors, locating additional information, iii PLC 5 programming software, locating additional information, iii processor connecting DH+ link, 1 14 front panel PLC 5/20C, 1 4 PLC 5/40C, 1 5 specifications backplane current load maximum, A 2 typical, A 2 battery, A 1 certification, A 1 clock/calendar, A 1 communication, A 1 ControlNet I/O maximum link cable length with repeaters, A 2 maximum link cable length without a repeater, A 2 maximum non discrete I/O data transfer data table size, A2 maximum number of nodes per link with repeaters, A 2 maximum number of nodes per link without a repeater, A 2 maximum number of repeaters in series per link, A 2 maximum number of segments in series per link, A 2 Network Update Time (NUT), A 2 number of ControlNet ports, A 2 number of redundant media ControlNet ports, A 2 transmission rate, A 2 environmental conditions, A 1
hardware addressing, A 1 heat dissipation, A 1 I/O modules, A 1 keying, A 1 location, A 1 maximum number of MCPs, A 2 maximum total I/O any mix, A 2 complimentary, A 2 maximum user memory words, A 2 memory modules, A 1 non ControlNet remote I/O I/O scan time, A 2 maximum number of devices, A 2 maximum number of ports configurable for DH+ or remote I/O, A 2 maximum number of racks, A 2 number of dedicated DH+ ports, A2 transmission rate, A 2 number of coprocessor ports, A 2 number of serial ports, A 2 program scan time, A 2 shock and vibration, A 1 weight, A 1 processor RUN/FAULT status indicator, 1 4, 1 5 processor status file, B 1 layout, B 1 processor resident local I/O, reserving space for, 2 7 programming a processor, through Channel 0, 1 16 programming terminal, connecting, 1 16 programming your ControlNet system, where to go, 4 1
R
redundant media, 1 15 definition of, ii remote I/O cable lengths, 1 12 non ControlNet, reserving space for, 2 8 remote I/O link, 2 15 remote I/O immediate I/O transfers, 2 5, 47 repeater, definition of, ii replacing a non ControlNet remote I/O network with a ControlNet network, 2 15 changing block transfer instructions, 2 16
Index
I9
changing I/O status files, 2 16 downloading archived files, 2 15 I/O performed on Channel 2 of PLC 5/40L processor, 2 16 messaging and I/O performed on Channels 1A and 1B, 2 15 messaging and I/O performed on Channels 2A and 2B of PLC 5/40B processor, 2 15 using automatic mapping, 2 7 replacing the processor battery, 1 9
terminating, 1 15 Selectable Timed Interrupts (STIs), using with ControlNet system, 4 7 selecting a ControlNet network address, 1 11 selecting the DH+ station address of Channel 1A, 1 10 setting the I/O chassis backplane switches, 16 addressing switches, 1 6 EEPROM transfer switches, 1 6 last state switch, 1 6 processor memory protection switch, 16 setting the I/O chassis configuration plug, 17 shock and vibration, specifications, A 1 specifying the serial interface of Channel 0, 1 11 status, layout for the processor, B 1 Status File, D 1 I/O, description, 2 9 status file, processor, B 1 status indicators location of on PLC 5/20C, 1 4 on PLC 5/40C, 1 5 using, 5 2, 5 3 status words, I/O map entry, D 1
S
scheduled data transfer operations, 2 1 descriptions of, 2 2 scheduled discrete I/O data transfer, process, 2 1 scheduled peer to peer communication description, 2 2 number of map table entries required, 29 scheduled peer to peer communications, number of map table entries required, 2 12 scheduled peer to peer communications mapping, 2 12 features, 2 12 scheduled transfers, definition of, ii screens Channel 2 Status, 5 12 Channel Overview, 3 2 Data Monitor for ControlNet I/O Transfer Block, 4 5 Data Monitor for Message Control Block, 43 I/O Action (Edit), 3 10 I/O Action (Monitor), 5 11 I/O Mapping (Edit), 3 6 I/O Mapping (Monitor), 5 7 Instruction Entry for ControlNet I/O Transfer Block, 4 4 Instruction Entry for Message Block, 4 2 Local Rack Characteristics, 3 3 Map Entries Status, 5 9 Node Information, 3 4 View Times (Monitor), 5 8 WHO ACTIVE--Network Status, 5 19 WHO ACTIVE Active Node Identification, 5 14 WHO ACTIVE Active Node Status, 5 16 WHO ACTIVE Channel Status, 5 17 segment definition of, ii
T
tap, 1 17 connecting, 1 15 definition of, ii using, 1 15 terminator, definition of, ii trunk cable, definition of, ii trunk cable section, definition of, ii trunk cable/drop cable connection, 1 14
U
unscheduled data transfer operations, 2 3 unscheduled non discrete I/O data transfer, 23 unscheduled transfers, definition of, ii using ControlNet I/O Transfer (CIO) instructions, 4 4
I10
Index
using ControlNet Immediate Data I/O instructions, 4 6 using ControlNet Message (MSG) instructions, 4 2 using the ControlNet Channel 2 Status screen, 5 12 using the ControlNet I/O Action (Monitor) screen, 5 11 using the ControlNet I/O Mapping (Monitor) screen, 5 7 using the ControlNet Map Entries Status screen, 5 9 using the ControlNet Node Information Channel 2 Configuration (Monitor) screen, 5 6 using the ControlNet status indicators, 5 3 using the ControlNet View Times (Monitor) screen, 5 8
using the ControlNet WHO ACTIVE Active Node Identification screen, 5 14 using the ControlNet WHO ACTIVE Active Node Status screen, 5 16 using the ControlNet WHO ACTIVE Channel Status screen, 5 17 using the ControlNet WHO ACTIVE Network Status screen, 5 19 using the general status indicators, 5 2 using this manual conventions used, iii intended audience for, i introduction to, i recommended preparation for, i related terminology, ii where to go, i
Allen Bradley, a Rockwell Automation Business, has been helping its customers improve productivity and quality for more than 90 years. We design, manufacture, and support a broad range of control and automation products worldwide. They include logic processors, power and motion control devices, man machine interfaces, sensors, and a variety of software. Rockwell is one of the world's leading technology companies.
Worldwide representation.
Algeria Argentina Australia Austria Bahrain Belgium Brazil Bulgaria Canada Chile China, PRC Colombia Costa Rica Croatia Cyprus Czech Republic Denmark Ecuador Egypt El Salvador Finland France Germany Greece Guatemala Honduras Hong Kong Hungary Iceland India Indonesia Ireland Israel Italyl Jamaica Japan Jordan Korea Kuwait Lebanon Malaysia Mexico Netherlands New Zealand Norway Pakistan Peru Philippines Poland Portugal Puerto Rico Qatar Romania Russia-CIS Saudi Arabia Singapore Slovakia Slovenia South Africa, Republic Spain Sweden Switzerland Taiwan Thailand Turkey United Arab Emirates United Kingdom United States Uruguay Venezuela Yugoslavia Allen Bradley Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 382 2000 Fax: (1) 414 382 4444
Publication 1785 6.5.14 September 1995
Copyright 1995 Allen Bradley Company, Inc. Printed in USA
PN 955116 44

1785 Um523 - en P PDF

Uploaded by

Copyright:

Available Formats

1785 Um523 - en P PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1785 Um523 - en P PDF

Uploaded by

Copyright:

Available Formats

ControlNet PLC 5 Programmable Controllers

Cat. No. 1785 L20C, L40C

Important User Information

Using This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing Your ControlNet PLC 5 Processor . . . . . . . . . . .

Planning to Use Your ControlNet PLC 5 Processor . . . . . .

Configuring Your ControlNet System . . . . . . . . . . . . . . . . .

Programming Your ControlNet System . . . . . . . . . . . . . . .

Monitoring and Troubleshooting Your ControlNet System

Processor Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Status File . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ControlNet Instruction Set . . . . . . . . . . . . . . . . . . . . . . . . .

ControlNet I/O Map Entry Status Words and Error Messages D 1

Using This Manual

Appendix A Appendix B Appendix C Appendix D

Using This Manual

Term ControlNet network connection discrete I/O data transfer

Preface Using this Manual

PLC 5 Processor Documentation

Using This Manual

PLC 5 Programming Software Documentation

Installing Your ControlNet PLC 5 Processor

Using This Chapter

Before You Begin

Installing Your ControlNet PLC 5 Processor

Handling the Processor

When not in use, keep the module in its static-shielded container.

Identifying ControlNet PLC 5 Processor Components

Memory Module Space

Installing Your ControlNet PLC 5 Processor

Figure 1.2 PLC 5/40C Processor Front Panel

Memory Module Space

Setting the I/O Chassis Backplane Switches

Addressing 2 -slot 1 -slot 1/2 - slot Not allowed EEPROM Transfer

Switches 6 OFF ON ON Switch 8 OFF ON 7 OFF ON OFF

Installing Your ControlNet PLC 5 Processor

Setting the I/O Chassis Configuration Plug

Set the I/O chassis configuration plug as follows:

2. USING A POWER SUPPLY MODULE IN THE CHASSIS? Y N Y N

Set Y when you install a power supply module in the chassis.

Set N when you use an external power supply.

Installing Keying Bands for the Processor

I/O Chassis Backplane Connector

Keying Bands (1771 RK)

Installing and Disposing of the Processor Battery

Installing or Removing the Processor Battery Tip

Battery side connector Processor side connector

Installing Your ControlNet PLC 5 Processor

Replacing the Battery Tip

Processor PLC 5/20C PLC 5/40C

Temperature 60C 25C 60C 25C

Battery Duration 3.7 days 15 days 40 hours 10.8 days

Disposing of the Battery

Selecting the DH+ Station Address of Channel 1A

Toggle pushed toward TOP OFF Toggle pushed toward BOTTOM ON

To select: DH+ Station Number

Set switch: 1 through 6

To: (See below)

Switch 7 is not used set it to OFF

DH+ Station Number 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 20 21 22 23 24 25 26 27 30 31 32 33 34 35 36 37