ControlNet PLC-5 Programmable Controllers Catalog Numbers 1785-L20C15, -L40C15, -L46C15, -L80C15 User Manual
Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of these products 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.
ATTENTION ! Environment and Enclosure This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage Category II applications (as defined in IEC publication 60664-1), at altitudes up to 2000 meters without derating. This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR Publication 11.
Rockwell Automation Support Before you contact Rockwell Automation for technical assistance, we suggest you please review the troubleshooting information contained in this publication first. If the problem persists, call your local Rockwell Automation representative or contact Rockwell Automation in one of the following ways: Phone Internet United States/Canada 1.440.646.5800 Outside United States/Canada You can access the phone number for your country via the Internet: 1. Go to http://www.ab.com 2.
Summary of Changes Summary of Changes The information below summarizes the changes to the ControlNet PLC-5 Programmable Controllers User Manual. To help you find new and updated information, look for the revision bars as shown to the left of this paragraph. New Information The following table highlights new information and where its located in this manual. The following paragraphs describe software requirements product enhancements.
soc-ii Notes 1785-UM022B-EN-P - February 2002
Table of Contents Installing Your ControlNet PLC-5 Processor Chapter 1 Planning to Use Your ControlNet PLC-5 Processor Chapter 2 Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Prevent Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Identifying ControlNet PLC-5 Processor Components . . . . . . . . . . . . . 1-3 Before You Install the Programmable Controller . . . . . . . . . . . . . . . . .
ii Table of Contents – ControlNet PLC-5 Programmable Controllers Understanding Multicast Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Understanding Multicast Outputs . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Using Multicast Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 Understanding ControlNet I/O Mapping . . . . . . . . . . . . . . . . . . . . . . 2-16 Reserving Space for Non-ControlNet I/O. . . . . . . . . . . . . . . . . . . .
Table of Contents – ControlNet PLC-5 Programmable Controllers Programming Your ControlNet System Chapter 4 Monitoring and Troubleshooting Your ControlNet System Chapter 5 Processor Specifications Appendix A Processor Status File Appendix B iii Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Using ControlNet Message Instructions . . . . . . . . . . . . . . . . . . . . . . . 4-1 Multihop Messaging Via the MSG Instruction . . . . . . . . . . . . . .
iv Table of Contents – ControlNet PLC-5 Programmable Controllers ControlNet I/O Map-Entry Status Words and Error Messages Appendix D Fault Codes Appendix E I/O Map-Entry Status Words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4 Clearing Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 Additional Major Fault Codes . . . . . . . . . .
Preface Preface Introduction This manual describes how to install your programmable controller and how to plan for, configure, and use the features of a 1785-L20C15, 1785-L40C15, 1785-L46C15 or 1785-L80C15 programmable controller that are unique to the ControlNet™ network. When we refer to ControlNet PLC-5 programmable controllers (or “processors”) in this manual, we mean the phase 1.
P-2 Preface If you want to read about: Go to: Monitoring and troubleshooting your ControlNet system Using the status indicators Chapter 5 Processor specifications Appendix A Processor status file Appendix B ControlNet instructions Appendix C ControlNet I/O map table entry status words and error messages Appendix D Fault codes Appendix E ControlNet diagnostics file layout Appendix F Terminology Term Description Actual Packet Interval (API) the actual time it takes for the ControlNet netw
Preface Term P-3 Description network update time (NUT) smallest repetitive time interval in which data can be sent on the ControlNet network node 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 99 nodes non-discrete I/O data transfer type of data transfer in which blocks of data transferred to or from a single I/O module use integer input and output data table files that you specify;
P-4 Preface Related PLC-5 Publications The 1785 PLC-5 programmable-controller and ControlNet documentation is organized into manuals according to the tasks that you perform: Publication Publication Number Enhanced PLC-5 Processor System Overview 1785-2.36 Enhanced and Ethernet PLC-5 Programmable Controllers User Manual 1785-6.5.12 ControlNet PLC-5 Programmable Controllers User Manual 1785-UM022B-EN-P ControlNet Cable System Planning and Installation Manual 1785-6.2.
Chapter 1 Installing Your ControlNet PLC-5 Processor Using This Chapter If you want to read about: Go to page: Preventing Electrostatic Discharge 1-2 Identifying the processor components 1-3 What to do before you begin installation 1-5 Installing and disposing of the processor battery 1-6 Setting the I/O chassis backplane switches 1-11 Setting the I/O chassis configuration plug 1-10 Installing keying bands for the processor 1-10 Selecting the Data Highway Plus™ (DH+™) station address of Ch
1-2 Installing Your ControlNet PLC-5 Processor Prevent Electrostatic Discharge This equipment is sensitive to electrostatic discharge which can cause internal damage and affect normal operation.
Installing Your ControlNet PLC-5 Processor Identifying ControlNet PLC-5 Processor Components 1-3 Figure 1.1 and Figure 1.2 show the front panels of the ControlNet PLC-5 processors. Figure 1.
1-4 Installing Your ControlNet PLC-5 Processor Figure 1.
Installing Your ControlNet PLC-5 Processor Before You Install the Programmable Controller 1-5 Before installing your ControlNet PLC-5 processor: 1.
1-6 Installing Your ControlNet PLC-5 Processor Install or Replace the Battery A 3.0 volt lithium battery (cat. no. 1770-XYC) is included with your processor. If the LED on the front of the processor indicates BATT, it means that the battery must be replaced. You must use an exact replacement battery (cat. no. 1770-XYC). ATTENTION ! Lithium battery requirements: • do not short, recharge, heat above 85° C, disassemble or expose contents to water • use only the 1770-XYC battery in the processor.
Installing Your ControlNet PLC-5 Processor 1-7 To install or replace the battery: 1. Remove the battery from the shipping bag. 2. Remove the battery cover from the processor. 3. If you are replacing an existing battery, detach the wired clip from the mating connector on the processor and remove the battery. 4. Connect the new or replacement battery by attaching the wired clip to the mating connector on the processor. 5. Place the battery and tuck the wires inside the battery area on the processor. 6.
1-8 Installing Your ControlNet PLC-5 Processor Estimated Battery Lifetimes Worst-Case Battery-Life Estimates Processor Temperature Power Off 100% Power Off 50% Battery Duration1 60° C 173 days 346 days 70 hours 25° C 1.69 years 3.38 years 14.5 days 60° C 92.5 days 185 days 38 hours 25° C 1.25 years 2.5 years 10.8 days 60° C 92.5 days 185 days 38 hours 25° C 1.25 years 2.5 years 10.8 days 60° C 80 days 160 days 33 hours 25° C 1.18 years 2.
Installing Your ControlNet PLC-5 Processor Setting the I/O Chassis Backplane Switches 1-9 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 Last State 1 O N O F F ON Outputs of this I/O chassis remain in their last state when a hardware failure occurs. OFF Outputs of this I/O chassis are turned off when a hardware failure occurs.
1-10 Installing Your ControlNet PLC-5 Processor 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). 2. Set the I/O chassis configuration plug. USING A POWER-SUPPLY MODULE IN THE CHASSIS? Y N The default setting is N (not using a power-supply module in the chassis).
Installing Your ControlNet PLC-5 Processor Selecting the DH+ Station Address of Channel 1A 1-11 To select the DH+ station address of Channel 1A, set the switches of assembly SW1.
1-12 Installing Your ControlNet PLC-5 Processor 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.
Installing Your ControlNet PLC-5 Processor Inserting/Removing the Processor into/from the I/O Chassis 1-13 To insert/remove the processor into/from the chassis, do the following: WARNING ! If you insert or remove the processor while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding. To insert a processor into the chassis: Locking Bar 1.
1-14 Installing Your ControlNet PLC-5 Processor The maximum number of Use this resistor rating: If your remote I/O link: Operates at 230.4K bit/s Operates at 57.6K or 115.
Installing Your ControlNet PLC-5 Processor WARNING ! WARNING ! Installing a DH+ Link 1-15 If you connect or disconnect the 1770-CD cable with power applied to this processor or the device on the other end of the cable, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
1-16 Installing Your ControlNet PLC-5 Processor 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, use the Phoenix connector MTSB2.
Installing Your ControlNet PLC-5 Processor Connecting to a ControlNet Network 1-17 Connect a ControlNet PLC-5 processor to a ControlNet network via a tap with a 1-m (39.4-in) drop cable. WARNING ! WARNING ! If you connect or disconnect the ControlNet tap cable with power applied to this processor or the device on the other end of the cable, an electrical arc can occur. This could cause an explosion in hazardous location installations.
1-18 Installing Your ControlNet PLC-5 Processor For detailed information about planning and installing your ControlNet system, see the following publications: Publication ControlNet Cable System Component List AG-2.2 ControlNet Cable System Planning and Installation Manual 1786-6.2.1 ControlNet Network Access Cable Installation Instructions 1786-2.
Installing Your ControlNet PLC-5 Processor Connecting a Programming Terminal 1-19 You can connect a programming terminal to a ControlNet PLC-5 processor via a: • DH+ connection • serial channel • ControlNet connection WARNING ! WARNING ! When used in a Class I, Division 2, hazardous location, this equipment must be mounted in a suitable enclosure with proper wiring method that complies with the governing electrical codes.
1-20 Installing Your ControlNet PLC-5 Processor When using this communication card: Use this cable: 1784-KTX, KTXD • 1784-CP13 1784-PCMK • 1784-PCM6 • 1784-PCM5 with 1784-CP7 adapter 1784-PKTX, -PKTXD • 1784-CP13 Serial Channel To program the processor using Channel 0, configure the channel for RS-232C using DF1 point-to-point protocol. If your personal computer has a 9-pin serial port, use the 1784-CP10 cable. If your personal computer has a 25-pin serial port, use the 1784-CP11 cable.
Installing Your ControlNet PLC-5 Processor 1-21 ControlNet Connection ! ATTENTION: Do not connect the same communication card to both the NAP and a tap on the ControlNet network.
1-22 Installing Your ControlNet PLC-5 Processor WARNING ! Selecting Appropriate Cables When used in a Class I, Division 2, hazardous location, this equipment must be mounted in a suitable enclosure with proper wiring method that complies with the governing electrical codes.
Installing Your ControlNet PLC-5 Processor 1-23 This processor’s serial port can support these configurations: Digital Interface Maximum Cable Length RS-232C 15 m (approximately 50 ft) RS-422A (compatible) 61 m (approximately 200 ft) RS-423 61 m (approximately 200 ft) Important: Follow these guidelines: • When Channel 0 is configured for RS-422A compatibility, do not use terminating resistors anywhere on the link.
1-24 Installing Your ControlNet PLC-5 Processor The following ControlNet cable system components are available from the Rockwell Automation: Item1 Cat. No.
Installing Your ControlNet PLC-5 Processor 1-25 For detailed information about ControlNet cabling, see the following publications: Publication Publication Number ControlNet Cable System Component List AG-2.2 ControlNet Cable System Planning and Installation Manual 1786-6.2.1 ControlNet Network Access Cable Installation Instructions 1786-2.6 ControlNet System Overview 1786-2.
1-26 Installing Your ControlNet PLC-5 Processor Notes 1785-UM022B-EN-P - February 2002
Chapter 2 Planning to Use Your ControlNet PLC-5 Processor Using This Chapter If you want to read about: Go to page: Understanding ControlNet I/O 2-1 Understanding Scheduled Connection Types 2-11 Understanding ControlNet I/O mapping 2-16 Using I/O Mapping Techniques 2-21 Using the ControlNet PLC-5 processor in a ControlNet I/O system 2-31 Converting from a non-ControlNet remote I/O system to a ControlNet I/O system 2-34 Converting from ControlNet phase 1.0 or 1.25 to ControlNet phase 1.
2-2 Planning to Use Your ControlNet PLC-5 Processor Scheduled Data-Transfer Operations on a ControlNet Network ControlNet scheduled data transfer on a ControlNet PLC-5 processor: • is continuous • is asynchronous to the ladder-logic program scan • occurs at the actual rate displayed in the Actual Packet Interval (API) field on the programming software scanlist configuration screen in RSNetWorx for ControlNet Important: The Requested Packet Interval (RPI) rate requested for a connection establishes t
Planning to Use Your ControlNet PLC-5 Processor 2-3 What Happens During Scheduled Input Data Transfer PLC-5 Programmable Controller In scheduled I/O data transfer, updates occur between logic scans (i.e.
2-4 Planning to Use Your ControlNet PLC-5 Processor The following scheduled data-transfer operations are supported by the ControlNet processors on a ControlNet network: Table 2.A ControlNet Scheduled Data-Transfer Operations Operation Description Discrete I/O Data Transfer (can be done as a rack or module connection) Performed in a deterministic and repeatable manner asynchronous to and independent of the ladder-logic program scan.
Planning to Use Your ControlNet PLC-5 Processor 2-5 The ControlNet system places your scheduled transfers in the first part of each Network Update Interval (NUI). Time is automatically reserved for network maintenance. 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 . . .
2-6 Planning to Use Your ControlNet PLC-5 Processor Table 2.B ControlNet Unscheduled Data-Transfer Operations Operation Description Features Non-discrete I/O Data Transfer Perform ladder-initiated unscheduled non-discrete I/O data transfers on a ControlNet network by using ControlNet I/O Transfer (CIO) instructions.
Planning to Use Your ControlNet PLC-5 Processor 2-7 Operation Description Features Peer-to-peer Messaging You can use ControlNet message (MSG) instructions and the data-type MG to create unscheduled messages that are initiated by one ControlNet PLC-5 processor and sent to another ControlNet PLC-5 processor.
2-8 Planning to Use Your ControlNet PLC-5 Processor Using Immediate Data-Transfer Operations ControlNet Immediate Data I/O transfers—Immediate Data Input (IDI) and Immediate Data Output (IDO)—perform similarly to the Remote-I/O supported immediate I/O transfers—Immediate Input (IIN) and Immediate Output (IOT)—which the ControlNet system also supports. The logic scan is temporarily interrupted while the most recent state of up to 64 words is read from or written to the private memory buffer.
Planning to Use Your ControlNet PLC-5 Processor 2-9 Table 2.
2-10 Planning to Use Your ControlNet PLC-5 Processor You enable process control sample complete on a per connection basis by setting the PCSC enable bit in the connection’s ControlNet I/O status file entry.
Planning to Use Your ControlNet PLC-5 Processor 2-11 Clearing the PCSC New Data and PCSC Overflow Bits If it is crucial to maintain the integrity of the PCSC overflow bit after new data has arrived while clearing the PCSC new data and overflow bits. Then do the following: 1. Disable process control sample complete by setting the PCSC enable bit for the connection to zero. When process control sample complete is disabled, the system will not modify the new data and overflow bits while you clear them. 2.
2-12 Planning to Use Your ControlNet PLC-5 Processor There are four general types of scheduled connections from the ControlNet PLC-5 to I/O adapters: • exclusive owner - these scheduled connections indicate the PLC-5 has exclusive ownership of the outputs. These scheduled connections can also gather inputs from the device. There cannot be more than one exclusive owner connection made to either the rack connection or module connection at a time.
Planning to Use Your ControlNet PLC-5 Processor 2-13 If an input only connection is made to the adapter: • an exclusive owner connection can be made • another input only connection can be made • a listen only connection can be made • a redundant owner connection can be made A listen only connection can only be made to the adapter if: • an exclusive owner connection already exists, or • an input only connection already exists, or • a redundant owner connection already exists If a redundant ow
2-14 Planning to Use Your ControlNet PLC-5 Processor Understanding Multicast Inputs This feature enables input devices to send the same data to multiple processors simultaneously. Advantages of multicast inputs include: • Network optimization - reduces network usage since data is sent only once simultaneously to all connections. This reduction may allow more complex scheduled connection configurations or improved unscheduled connection performance.
Planning to Use Your ControlNet PLC-5 Processor 2-15 Using Multicast Outputs To use multicast outputs, you must first configure each Multicast Output connection in RSNetworx 3.0: 1. In the Details Tab of Connection Properties dialog, change the Scanner to Target Network Connection to Multicast. You cannot modify this field for any device that does not support multicast outputs. 2. The Scanner to Target Multicast ID of the Details Tab indicates to which multicast output group the connection belongs.
2-16 Planning to Use Your ControlNet PLC-5 Processor 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 to—i.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.
Planning to Use Your ControlNet PLC-5 Processor 2-17 Remote I/O The following table shows the default number of input and output words reserved by the 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 Number of Words Reserved 4 Slots 8 Slots 12 Slots 16 Slots 2 Slot 2 4 6 8 1 Slot 4 8 12 16 1/2 Slot 8 16 24 32 The programming software reserves non-ControlNet
2-18 Planning to Use Your ControlNet PLC-5 Processor Supported ControlNet I/O Sizes The following table shows the maximum I/O map entries allowed in the ControlNet I/O map table: Table 2.
Planning to Use Your ControlNet PLC-5 Processor 2-19 Discrete I/O Data-Transfer Mapping Regardless of the type of I/O—e.g., 1747, 1771, 1794—all ControlNet discrete I/O data is stored within the processor according to the corresponding I/O map-table entry. Discrete I/O data can be stored in either the I/O image table or the DIF/DOF. Any status information transferred along with the I/O data is stored in a separate status file that you specify during configuration.
2-20 Planning to Use Your ControlNet PLC-5 Processor 1771 Modules ControlNet 1771 discrete I/O data-transfer mapping requires one map-table entry per node. ControlNet 1771 non-discrete I/O data-transfer mapping requires one map-table entry per module. The ControlNet scheduled I/O data-transfer mechanism makes it possible to eliminate block-transfer programming to communicate with the 1771 modules. For a complete list of these modules, refer to RSNetWorx for ControlNet documentation.
Planning to Use Your ControlNet PLC-5 Processor 2-21 Other ControlNet Processors ControlNet scheduled peer-to-peer communications between ControlNet processors require one map-table entry per message. You can set up ControlNet peer-to-peer communications between any two processors on a ControlNet network. The ControlNet transfer mechanism makes it possible to map the scheduled peer-to-peer messages listed in the following table. Table 2.
2-22 Planning to Use Your ControlNet PLC-5 Processor Understanding Discrete Mapping Each version of a PLC-5 processor has a fixed amount of I/O image space.
Planning to Use Your ControlNet PLC-5 Processor 2-23 Optimizing the I/O Image Table You may find that you are close to the I/O image table limits in a PLC-5 processor and need to optimize the use of the I/O image table in order to insure that the application will fit in the processor. This section discusses techniques that make optimal use of the I/O image table available in a PLC-5 processor.
2-24 Planning to Use Your ControlNet PLC-5 Processor If you perform an automap on this system, the map table appears like this: Input file Input size Output file Output size I:010 8 O:010 8 The automap feature reserves the maximum size of inputs and outputs. It is up to you to manually change the sizes if desired.
Planning to Use Your ControlNet PLC-5 Processor First Rule of Module Optimization 2-25 When placing discrete modules, put the type (input or output) you have the least of to the left in the chassis. Example 3 Some chassis may contain analog modules, communication cards, or power supplies.
2-26 Planning to Use Your ControlNet PLC-5 Processor Second Rule of Module Optimization Place modules that do not require I/O image table space to the right in the chassis.
Planning to Use Your ControlNet PLC-5 Processor 2-27 Example 4 Examine the following system: ACN I O O I I ACN I A O A X O O I I O O X A I I I A O I = Discrete Input Module O = Discrete Output Module ACN = ControlNet adapter A = Analog Module PS = Power Supply X = Empty Slot Chassis 1 Chassis 2 ACN O Chassis 3 Input file Input size Output file Output size Chassis 1 I:010 5 O:010 8 Chassis 2 I:015 8 O:020 3 Chassis 3 I:025 7 O:023 3 Assume you want to add a
2-28 Planning to Use Your ControlNet PLC-5 Processor Example 1 Examine the following chassis: ACN I O I O I O I O 2-slot addressing 16-point modules I = Discrete Input Module O = Discrete Output Module ACN = ControlNet adapter In this example the first input module uses eight inputs from the first slot and eight inputs from the second slot (not used by the output module in the second slot).
Planning to Use Your ControlNet PLC-5 Processor 2-29 Summary There are two methods to optimize the use of I/O image table in a ControlNet PLC-5 processor. There are tradeoffs in using each method which are summarized in the following table.
2-30 Planning to Use Your ControlNet PLC-5 Processor However, the overall system may be heavy on inputs, and there are no concerns about the output image table.
Planning to Use Your ControlNet PLC-5 Processor Using the ControlNet PLC-5 Processor in a ControlNet I/O System 2-31 There can be multiple ControlNet PLC-5 processors updating I/O adapters on a ControlNet network.
2-32 Planning to Use Your ControlNet PLC-5 Processor Example of a ControlNet Network without Redundant Media Personal computer with 1784-KTCX15 card (ISA-based) and your HMI or programming software Personal computer or other serial device and your HMI or programming software Personal computer with PCIC card (PCI-based) and your HMI or programming software Laptop computer with 1784-PCC card (PCMCIA-based) and your HMI or programming software PLC-5/40C 1784-PCC1 to PLC-5 (NAP port or any other NAP port
Planning to Use Your ControlNet PLC-5 Processor WARNING ! 2-33 When used in a Class I, Division 2, hazardous location, this equipment must be mounted in a suitable enclosure with proper wiring method that complies with the governing electrical codes. Distributed Keeper Functionality All ControlNet processors now keep the ControlNet configuration. The processor with the lowest node address acts as the master keeper, while the other processors serve as backups.
2-34 Planning to Use Your ControlNet PLC-5 Processor Converting from a Non-ControlNet Remote I/O System to a ControlNet I/O System Program files1 for this process: Messaging and I/O When you download archived files to a ControlNet PLC-5 processor, the 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 ControlNet processors.
Planning to Use Your ControlNet PLC-5 Processor Program files1 for this process: Messaging and I/O continued 1 2 3 4 5 Archived from a: On channel: Can be run on a ControlNet PLC-5 channel: • • • • • • • • PLC-5/11 PLC-5/20 PLC-5/20C15 PLC-5/20E PLC-5/30 PLC-5/40 PLC-5/40C15 PLC-5/40E • • • • • • • PLC-5/40L PLC-5/46C15 PLC-5/60 PLC-5/60L PLC-5/80 PLC-5/80C15 PLC-5/80E 1A 2 • • • • • • • PLC-5/20 PLC-5/20C15 PLC-5/20E PLC-5/30 PLC-5/40 PLC-5/40C15 PLC-5/40E • • • • • • • PLC-5/40L PLC-5/46C15
2-36 Planning to Use Your ControlNet PLC-5 Processor Notes 1785-UM022B-EN-P - February 2002
Chapter 3 Understanding the ControlNet System Software Using This Chapter This chapter describes the configuration and programming software that you use with your ControlNet PLC-5 processor and specific details about their maintenance. Although the software packages are separate tools, they have specific interdependencies that must be met in order to keep projects synchronized between one another.
3-2 Understanding the ControlNet System Software Also, the ControlNet network requires that the entire network be configured at one time to make sure all scheduled connections are performed at their configured packet rates.
Understanding the ControlNet System Software 3-3 Under these circumstances, consider the following guidelines: • when configuring intelligent modules over ControlNet, any configuration changes should be performed via a module’s respective applet in the I/O configuration utility. This will ensure that the edits are written to both the data table and the RSNetWorx project (.xc) file.
3-4 Understanding the ControlNet System Software When downloading the project from RSLogix 5, a dialog box appears and asks whether the ControlNet configuration information stored in the RSLogix 5 project should be downloaded. With this approach, you will want to keep the existing ControlNet configuration that is currently on the ControlNet PLC-5 processor. Download from RSLogix 5 Only You can download the entire program from RSLogix 5 while keeping the ControlNet configuration information up to date.
Understanding the ControlNet System Software 3-5 To verify keeper signatures: 1. In Network menu, choose Keeper Status 2. If any keepers are invalid, select the node(s) and click Update Keeper To verify scanner signatures: 1. In Network menu, choose Scanner Signature Status 2.
3-6 Understanding the ControlNet System Software Notes 1785-UM022B-EN-P - February 2002
Chapter 4 Programming Your ControlNet System Using This Chapter If you want to read about using: Using ControlNet Message Instructions Go to page: ControlNet message instructions 4-1 ControlNet I/O transfer instructions 4-3 ControlNet immediate data input and output instructions 4-6 Using Selectable Timed Interrupts (STIs) in a program on a ControlNet network 4-9 Recovering from Major Fault Codes 200 and 201 4-9 You can use the Message (MSG) instruction and the MG data type to send message co
4-2 Programming Your ControlNet System If you want to: Do this: enter the size in elements Type a number of elements from 1 to 1000. enter the destination network address Type a number from 1 to 99. enter a destination data table address Type the destination data table address. The fields of the MG data type that you can directly address are: Field Definition Location .EW Enabled-waiting flag bit word 0, bit 02 .CO Continuous control bit word 0, bit 03 .
Programming Your ControlNet System 4-3 Option to Close Communication Connection when MSG is Done This feature allows you to configure the ControlNet ladder MSG instruction to close its communication connection when the message operation is done - thus conserving ControlNet resources on low duty rate messages. Do this by setting the .NC configuration bit in the ladder MSG control file.
4-4 Programming Your ControlNet System If you want to: Do this: change the command type Select one of the following: • 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 READ - reads data from a 1794 I/O module • 1794 WRITE - writes data to a 1794 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 CONF
Programming Your ControlNet System 4-5 The fields of the CT data type that you can directly address are: Field Definition Location .EW Enabled-waiting flag bit word 0, bit 02 .CO Continuous control bit word 0, bit 03 .ER Errored flag bit word 0, bit 04 .DN Done flag bit word 0, bit 05 .ST Started flag bit word 0, bit 06 .EN Enabled flag bit word 0, bit 07 .TO Abort (Time out) control bit word 0, bit 08 .ERR Error-code word word 1 .RLEN Requested length word word 2 .
4-6 Programming Your ControlNet System 1771 ControlNet Transfers in PIIs and STIs When a 1771 Read or 1771 Write CIO instruction is encountered in a PII or STI, the processor resumes execution of lower priority ladder programs (main logic programs) until the CIO is completed. If you want the PII or STI to run to completion before returning to your main logic program, place the CIO instruction inside of a UID/UIE pair in your PII or STI program file.
Programming Your ControlNet System 4-7 In the previous example, 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 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.
4-8 Programming Your ControlNet System 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.
Programming Your ControlNet System Using Selectable Timed Interrupts with a Program on a ControlNet Network 4-9 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.
4-10 Programming Your ControlNet System Notes 1785-UM022B-EN-P - February 2002
Chapter 5 Monitoring and Troubleshooting Your ControlNet System Using This Chapter Using the General Status Indicators If you want to read about: See page: Using the general status indicators 5-1 Using the ControlNet status indicators 5-3 Using the Data Highway Plus and Remote I/O Status Indicators 5-5 Monitoring the ControlNet configuration and status 5-5 Using the DH+/RIO Status Indicators 5-6 The general status indicators inform you of the general operational state of the processor.
5-2 Monitoring and Troubleshooting Your ControlNet System Indicator Color Description Probable Cause Recommended Action PROC Green (steady) Processor is in run mode and fully operational Normal operation No action required Green (blinking) Processor memory is being transferred to EEPROM Normal operation No action required Red (blinking) Major fault • RSLogix 5 download in progress • Run-time error During RSLogix 5 download, this is normal operation - wait for download to complete.
Monitoring and Troubleshooting Your ControlNet System Using the ControlNet Status Indicators The ControlNet status indicators inform you of the operational state of the ControlNet network.
5-4 Monitoring and Troubleshooting Your ControlNet System Indicator A or Color1 Probable Cause Recommended Action Off Channel disabled No action required Configure for ControlNet communication B Steady Green Normal operation No action required Flashing Green/Off Temporary errors Make sure that the processor is connected to the ControlNet network with an Allen-Bradley tap. Check media for broken cables, loose connectors, missing terminators, etc.
Monitoring and Troubleshooting Your ControlNet System 5-5 Using the DH+/RIO Status Indicators Indicator A or Color Channel Mode Description Probable Cause Recommended Action Green (steady) Remote I/O Scanner Active Remote I/O link, all adapter modules are present and not faulted Normal operation No action required Remote I/O Adapter Communicating with scanner DH+ Processor is transmitting or receiving on DH+ link Remote I/O Scanner At least one adapter is faulted or has failed • Power o
5-6 Monitoring and Troubleshooting Your ControlNet System Monitoring ControlNet Configuration and Status Use the following software packages to monitor ControlNet configuration and status information.
Appendix A Processor Specifications Backplane Current Heat Dissipation Operating Temperature Storage Temperature Relative Humidity Vibration Shock Emissions ESD Immunity Radiated RF Immunity EFT/B Immunity Surge Transient Immunity Conducted RF Immunity Enclosure Type Rating Time-of-Day Clock/Calendar1 Available Cartridges Battery Memory Modules3 I/O Modules 1 2 3 4 5 1785-L20C15: 2.7A @ 5Vdc 1785-L40C15, -L46C15, -L80C15: 3.
A-2 Processor Specifications Hardware Addressing Communication Location Weight Keying Certifications (when product is marked) 1 2 3 4 5 2-slot • Any mix of 8-pt modules • 16-pt modules must be I/O pairs • No 32-pt modules 1-slot • Any mix of 8- or 16-pt modules • 32-pt modules must be I/O pairs 1/2-slot—Any mix of 8-,16-, or 32-pt modules • Serial • DH+ • DH using 1785-KA • Remote I/O • ControlNet • Relay Cartridge Wire Category 24 Wire Category 14 1771-A1B, -A2B, A3B, -A3B1, -A4B chassis; left-mo
Processor Specifications Maximum User Memory Words Maximum Total I/O Any Mix Complimentary PLC-5/20C15 16K 512 512 in and 512 out Program Scan Time ControlNet I/O3 Transmission Rate Network Update Time (NUT) Number of ControlNet Ports Maximum Number of Nodes per Link without a Repeater Maximum Number of Nodes per Link with Repeaters Maximum Link Cable Length without a Repeater Maximum Number of I/O Map Entries Maximum DIF/DOF Size Maximum Link Cable Length with Repeaters Remote I/O and DH+ Transmissi
A-4 Processor Specifications The following information applies when operating this equipment in hazardous locations: Informations sur l’utilisation de cet équipement en environnements dangereux : Products marked “CL I, DIV 2, GP A, B, C, D” are suitable for use in Class I Division 2 Groups A, B, C, D, Hazardous Locations and nonhazardous locations only. Each product is supplied with markings on the rating nameplate indicating the hazardous location temperature code.
Appendix B Processor Status File S:0 - S:2 Processor status data is stored in data-file 2.
B-2 Processor Status File This word of the status file: Stores: S:2/07 S:2/08 Not defined S:2/09 Last state 0 outputs are turned off 1 outputs retain last state S:2/11 S:2/12 I/O chassis addressing bit 12 bit 11 0 0 illegal 1 0 1/2-slot 0 1 1-slot 1 1 2-slot S:2/13 S:2/14 Memory module transfer bit 13 bit 14 0 0 memory module transfers to processor memory if processor memory is not valid 0 1 memory module does not transfer to processor memory 1 1 memory module transfers to processor memory at pow
Processor Status File This word of the status file: B-3 Stores: S:10/04 Edits prevent SFC continuing; data table size changed during program mode; reset automatically in run mode S:10/05 Invalid I/O status file S:10/06 reserved S:10/07 No more command blocks exist to execute block-transfers S:10/08 Not enough memory on the memory module to upload the program from the processor S:10/09 No MCP is configured to run S:10/10 MCP not allowed S:10/11 PII word number not in local rack S:10/12 P
B-4 Processor Status File This word of the status file: S:12 This fault code: 00-09 Stores: S:11/12 PII file does not exist or is not a ladder file S:11/13 STI file does not exist or is not a ladder file S:11/14 Fault routine does not exist or is not a ladder file S:11/15 Faulted program file does not contain ladder logic This word stores the following fault codes: Indicates this fault: And the fault is: Reserved for user-defined fault codes.
Processor Status File B-5 This fault code: Indicates this fault: And the fault is: 10 Run-time data table check failed 11 Bad user program checksum 12 Bad integer operand type, restore new processor memory file Recoverable: the fault routine can instruct the processor to clear the fault and then resume scanning the program.
B-6 Processor Status File This fault code: Indicates this fault: And the fault is: 41 NXT instruction with missing FOR 42 You tried to jump to a non-existent label 43 File is not an SFC Non-recoverable the fault routine will be executed but cannot clear major fault bit 2. 44 Error using SFR.
Processor Status File This fault code: Indicates this fault: And the fault is: 83 User watchdog fault Recoverable 84 Error in user-configured adapter mode block-transfer 85 Memory module bad 86 Memory module is incompatible with host 87 Scanner rack list overlap 88 Scanner channels are overloading the remote I/O buffer; too much data for the processor to process. If you encounter fault code 88, be sure you followed the design guidelines listed on page ___.
B-8 This fault code: Processor Status File Indicates this fault: And the fault is: 201 ControlNet input data missed. The processor is unable to process incoming data from the network. Recoverable Check your network for missing terminators or other sources of electrical noise (see the Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1). 202 ControlNet diagnostic data missed. Recoverable Contact your local Rockwell Automation representative if you get this message.
Processor Status File This fault code: 205 B-9 Indicates this fault: And the fault is: ControlNet configuration exceeds processor bandwidth. IMPORTANT: Scheduled connections will be closed. You must cycle power, save with RSNetWorx, or download the program to reopen the connections.
B-10 This fault code: Processor Status File Indicates this fault: And the fault is: 231 Bypassed qualification (may occur during race condition when both processors attempt to go into Run mode at the same time). Transition the PLC-5 processors into Run mode one at a time. 232 Both processors attempted to be primaries. Check all media for broken cables, loose connectors, missing terminators, etc. 233 ControlNet configuration invalid on transition into Run mode.
Processor Status File B-11 S:13-S:24 This word of the status file: Stores: S:13 Program file where fault occurred S:14 Rung number where fault occurred S:15 VME status file S:16 I/O status File S:17 Minor fault (word 2) See also S:10.
B-12 Processor Status File This word of the status file: Stores: S:23 Processor clock second S:24 Indexed addressing offset S:25 Reserved S:26-S:35 This word of the status file: S:26 1785-UM022B-EN-P - February 2002 Stores: User control bits S:26/00 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 S:26/01 Start-up protection after power loss: when reset, no protection.
Processor Status File This word of the status file: Stores: S:33 Rack control bits: (See also S:7, S:27, S:32, S:34, and S:35) • S:33/0-7 I/O rack inhibit bits for racks 10-17 • S:33/8-15 I/O rack reset bits for racks 10-17 S:34 Global status bits: (See also S:7, S:27, S:32, S:33, and S:35) • S:34/0-7 rack fault bits for racks 20-27 (octal) • S:34/8-15 unused S:35 Rack control bits: (See also S:7, S:27, S:32, S:33, and S:34) • S:35/0-7 I/O rack inhibit bits for racks 20-27 • S:35/8-15 I/O rack reset
B-14 Processor Status File 1785-UM022B-EN-P - February 2002 This word of the status file: Stores: S:64 The number of remote block-transfer command blocks being used by channel pair 1A/1B. S:65 The number of remote block-transfer command blocks being used by channel pair 2A/2B. S:66 Reserved. S:68 Installed memory card type.
Processor Status File B-15 S:79-S127 This word of the status file: Stores: 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-16 Processor Status File Notes 1785-UM022B-EN-P - February 2002
Appendix C ControlNet Instruction Set For detailed information about 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 Instruction Set Reference, publication 1785-6.1.
C-2 ControlNet Instruction Set Immediate Data I/O Instructions Instruction Description IDI IMMEDIATE DATA INPUT Data file offset Immediate Data Output IDO 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.
Appendix D ControlNet I/O Map-Entry Status Words and Error Codes 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 contains status information about all of the ControlNet network’s 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.
D-2 ControlNet I/O Map-Entry Status Words and Error Codes The following table explains the bits in the first word of the ControlNet I/O status file: Bit Number Description Use 00 Reset Bit Set this bit to put the associated connection into PROGRAM mode, even if the processor is in Run mode. Clear this bit to set the mode of the associated connection according to the processor’s mode. This bit has no effect for 1771 block transfer modules.
ControlNet I/O Map-Entry Status Words and Error Codes D-3 The following table explains the second and third status words in the ControlNet I/O status file.
D-4 ControlNet I/O Map-Entry Status Words and Error Codes Error Codes The following is a list of ControlNet error codes, messages, possible causes, and possible corrective actions. These errors can originate in either the PLC-5 programmable controller or the target device: Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) VARIOUS VARIOUS CONFIGURATION DATA CORRUPTED The ControlNet configuration is corrupted. Reenter the map entry that is failing.
ControlNet I/O Map-Entry Status Words and Error Codes Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) 38 0x0026 INVALID DESTINATION ADDRESS SIZE The map table is corrupted. Reenter the I/O map entry that is failing. The target node of the MSG instruction is not a processor or the target node of the CIO instruction is not the correct I/O adapter. Edit the ladder program so that the correct target node is used.
D-6 ControlNet I/O Map-Entry Status Words and Error Codes Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) 279 0x0117 INVALID CONNECTION POINT The PLC-5C is requesting data from a ControlLogix tag that does not exist. Change the PLC-5C I/O map entry to use the correct tag. Change or add the tag to the ControlLogix processor. 280 0x0118 INVALID CONFIGURATION FORMAT The PLC-5C does not support ControlNet hot backup. Refer to publication 1785-6.5.
ControlNet I/O Map-Entry Status Words and Error Codes Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) 516 0x0204 UNCONNECTED REQUEST TIMED OUT The ControlNet cable from the originating node to the target node is broken or disconnected. Fix and/or reconnect the ControlNet cable. The target node is not powered. Supply power to the target node. The originator’s and/or the target’s node number is greater than UMAX.
D-8 ControlNet I/O Map-Entry Status Words and Error Codes Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) 774 0x0306 KEEPER NOT AVAILABLE The ControlNet cable from the originating node to the keeper is broken or disconnected. Fix and/or reconnect the ControlNet cable. The keeper is not powered. Supply power to at least one ControlNet processor. No keeper exists on the ControlNet network. Add at least one ContolNet processor to the network.
ControlNet I/O Map-Entry Status Words and Error Codes Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) 65523 0xFFF3 CONTROLNET TRANSFER QUEUE FULL The immediate CIO instruction could not be executed because the queue is full. Edit the ladder program so that the number of active 1771 READ/WRITE CIO instructions is equal to or less than the maximum of 32. 65527 0xFFF7 MODULE TIMED OUT The target slot is empty.
D-10 ControlNet I/O Map-Entry Status Words and Error Codes Decimal Code Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s) 65530 0xFFFA MODULE DECLARED INVALID LENGTH A communication error between the adapter and the module caused the transfer to be aborted. Make sure that the module is properly seated in the correct slot of the target node. Make sure that the adapter’s power supply is providing the proper voltage.
Appendix E Fault Codes Fault routines execute when a PLC-5 processor encounters a run-time error (major fault) during program execution. 3. A fault routine processes the major fault bit found in S:11 and determines the course of program execution based on the fault bit present.
E-2 Fault Codes This fault code: Indicates this fault: Take this corrective action: 205 ControlNet configuration exceeds processor resources. IMPORTANT: Scheduled connections will be closed. You must cycle power, save with RSNetWorx, or download the program to reopen the connections.
Appendix F ControlNet Diagnostics File Layout When you specify a Control Diagnostic File in RSNetWorx for the ControlNet network, the PLC-520C, -5/40C, -5/46C or -5/80C processor copies the 40 words of diagnostic counters into the specified integer file. Twenty-three additional diagnostic counters are available in the ControlNet diagnostic file. To access these counters, you must first use RSLogix5 to increase the size of the ControlNet diagnostic integer file to 63 words.
F-2 ControlNet Diagnostics File Layout 1785-UM022B-EN-P - February 2002 Field Names File Offset1 (word;bits) Node Address of current Moderator 15;15-08 Cannot Hear Moderator Occurrences (i.e.
ControlNet Diagnostics File Layout F-3 Field Names File Offset1 (word;bits) Maximum number of simultaneously open target Message Router connections (always less than or equal to 32) 53 Accumulated number of target Message Router connection timeouts 54 Current number of used unconnected clients (always less than or equal to 8) 55 Maximum number of simultaneously used unconnected clients (always less than or equal to 8) 56 Accumulated number of unconnected client timeouts 57 Current number of us
F-4 ControlNet Diagnostics File Layout Notes 1785-UM022B-EN-P - February 2002
Index Numerics 1747 modules discrete I/O data transfer mapping 2-20 1770-CD 1-15, 1-23 1770-KFC Communication Interface 2-31 1771 modules discrete I/O data transfer mapping 2-20 1771-ACN and -ACNR ControlNet I/O Adapters 2-31 1771-AF 1-14 1771-AS 1-14 1771-ASB 1-14 1771-DCM 1-14 1771-SN 1-14 1772-SD, -SD2 1-14 1775-S4A, -S4B 1-14 1775-SR 1-14 1784-CP13 1-20, 1-23 1784-KTC Communication Card 2-31 1784-KTx 1-20, 1-23 1784-KTxD 1-20, 1-23 1784-PCC Communication Card 2-31 1784-PCM5 1-20, 1-23 1784-PCM6 1-20, 1-
2 Index ControlNet I/O error messages D-4 features 2-1 files configured with map Data Input File (DIF) 2-18, 2-19 Data Output File (DOF) 2-18, 2-19 Default Configuration File 2-18 I/O Status File 2-18 I/O forcing 2-7 immediate data transfer operations 2-8 map table creating 2-16 entries 2-16 mapping scheduled data transfers 2-16 scheduled data transfer operations 2-2, 2-4 scheduled operations discrete I/O data transfer 2-4 nondiscrete I/O data transfer 2-4 peer-to-peer communication 2-4 understanding 2-1
Index ControlNet system cabling 1-23 configuring 3-1 changing a 1794 I/O modules fault action 2-6, 4-4 changing a 1794 I/O modules idle action 2-6, 4-4 configuring nodes 2-16 locating additional information P-4 monitoring 5-1 network maintenance 2-5 network update cycle what happens in 2-5 scheduled operations 2-5 selecting devices to connect 2-31 troubleshooting 5-1 unscheduled operations 2-5 using ControlNet PLC5 processors in 3 definition of P-2 description 2-4 discrete I/O data transfer mapping 2-19
4 Index I I/O ControlNet 2-1 automatic mapping 2-16 discrete I/O data transfer mapping 2-19 files configured with map Data Input File (DIF) 2-18, 2-19 Data Output File (DOF) 2-18, 2-19 Default Configuration File 2-18 I/O Status File 2-18 I/O forcing 2-7 immediate data transfer 2-8 map table creating 2-16 entries 2-16 maximum number of entries 2-18 mapping 2-16 mapping data transfers 2-18 non-discrete I/O data transfer mapping 2-19, 2-20 reserving rack space for remote I/O linked racks before mapping 2-16
Index locating additional information 1-1 removing the processor from the chassis 1-13 selecting cables ControlNet cables 1-23 DH+ programming 1-23 remote I/O 1-23 serial 1-22 selecting the ControlNet network address 1-12 selecting the DH+ station address of Channel 1A 1-11 setting the I/O chassis backplane switches 1-9 setting the I/O chassis configuration plug 1-10 specifying the serial interface of Channel 0 1-12 instructions ControlNet I/O Transfer (CIO) 2-6, C-1 how to use 4-3 when to use 2-20, 2-35
6 Index P PCMCIA Communication Card 2-31 PCSC 2-9 considerations 2-11 PCSC enable bit D-2 PCSC new data bit D-2 PCSC overflow bit D-2 Peer In 2-21 Peer Out 2-21 performing verification activities 3-4 PLC-5 using in a ControlNet system 2-31 PLC-5 catalog numbers P-1 PLC-5 processors P-4 PLC-5 programming software P-4 PLC-5 publications P-4 Process Control Sample Complete 2-9 processor definition P-3 front panel PLC-5/20C 1-3 PLC-5/40C 1-4 specifications A-1 processor status file B-1 layout B-1 processor re
Index terminating 1-17 Selectable Timed Interrupts (STIs) using with ControlNet system 4-9 selecting the DH+ station address of Channel 1A 1-11 setting the I/O chassis backplane switches 1-9 addressing switches 1-9 EEPROM transfer switches 1-9 last state switch 1-9 processor memory protection switch 1-9 setting the I/O chassis configuration plug 1-10 SMAX definition P-3 Software 3-1 specifications PLC-5 A-1 specifying the serial interface of Channel 0 1-12 status layout for the processor B-1 Status File D
8 Index Publication 1785-UM022B-EN-P - February 2002
How Are We Doing? Your comments on our technical publications will help us serve you better in the future. Thank you for taking the time to provide us feedback. You can complete this form and mail it back to us, visit us online at www.ab.com/manuals, or email us at RADocumentComments@ra.rockwell.com Pub. Title/Type ControlNet PLC-5 Programmable Controllers User Manual Cat. No. 1785-L20 to -L80C15 Pub. No. 1785-UM022B-EN-P Pub. Date February 2002 Part No. 957345-75 Please complete the sections below.
PLEASE FASTEN HERE (DO NOT STAPLE) PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
Publication 1785-UM022B-EN-P - February 2002 13 Supersedes Publication 1785-6.5.22 - February 1999 PN 957345-75 Copyright © 2002 Rockwell Automation. All rights reserved. Printed in the U.S.A.
