Home

Spec Sheet - The Reynolds Company

1. E oO Oo a n 8 pin FT gt mini DIN connector 8 amp mini DIN ER connector e m S Bl JE Personal computer Personal computer PLC 5 20C PLC 5 40C 5 46C DH Link Processor DH Link 5 80C Processor 1785 UM022C EN P February 2008 1 20 Installing Your ControlNet PLC 5 Processor 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 When using this communication card 1784 KTX KTXD Use this cable 1784 CP13 1784 PCMK 1784 PCM6 1784 PCM5 with 1784 CP7 adapter 1784 PKTX PKTXD 1784 CP13 Personal computer 1785 UM022C EN P February 2008 Serial Channel To program the processor using Channel 0 configure the channel for RS 232C using DF1 point to point protocol PLC 5 40C 5 46C or 5 80 C Processor 99 O oO o 00 e All le J E PLC 5 20C Processor Personal computer If
2. PLC 5 40C 1784 PCC1 to PLC 5 NAP y port or any other NAP port m G pem e 3l 1770 15 Tap 4 choices cm fl eo Interface 1786 TPR E li Tap 4 choices ControlNet Network 4 1786 TPR A PLC 5 40C eee uoo a om x JS 1 i jeee jeee at QUE m UR deo ej E al a EE pE 1794 ACNR15 FLEX 1 0 Adapter 1747 15 Adapter 1771 ACNR15 Adapter A programming terminal connected through this cable is counted as a node and must have a unique address Redundant media not required Important 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 If you connect or disconnect the ControlNet 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 1785 UM022C EN P February 2008 1 22 Installing Your ControlNet PLC 5 Processor Selecting Appropriate Cables WARNING When used in a Class I Division 2 hazardous locati
3. s etia Duis Ufo de didi B 3 pda dad iui 4 sapor TETTE TTE B 11 D200 UR B 12 suo nv PTT B 13 wp Q B 15 Appendix C ControlNet 1 0 Transfer Instruction C 1 Message Instructions on a ControlNet Network C 1 Immediate Data 1 0 Instructions C 2 Instruction Timing and Memory Requirements C 2 1785 UM022C EN P February 2008 iv Table of Contents ControlNet PLC 5 Programmable Controllers ControlNet 1 0 Map Entry Status Words and Error Messages Fault Codes ControlNet Diagnostics File Layout 1785 UM022C EN P February 2008 Appendix D VO Map Entry Status D 1 SUME ae 4 Appendix E Clearing E 1 Additional Major Fault E 2 Appendix F Introduction Audience Preface 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 ControINet network When we refer to ControlNet PLC 5 programmable controllers or processors in this manual we mean the phase 1 5 programmable controllers e Catalog number 1785 L20C1
4. 1785 UM022C EN P February 2008 4 2 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 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 NR No response flag bit not used word 0 bit 09 NC No cache bit word 0 bit 10 ERR Error code word word 1 RLEN Requested length word word 2 DLEN Done length word word 3 DATA 0 through DATA 51 Remaining words words 4 through 55 1756 CNB i An 9e Os o o o o oo o oo o dg Jg tel rre P co e e E ControlBus ControlNet Link 1 ControlNet Link 2 1785 UM022C EN P February 2008 For more detailed information about writing ladder programs and using message instructions see your programming software documentation Mul
5. 1 2 Identifying ControlNet PLC 5 Processor Components 1 3 Before You Install the Programmable Controller 1 5 Install or Remove the 1 6 Setting the 1 0 Chassis Backplane Switches 1 9 Setting the 1 0 Chassis Configuration 9 1 10 Installing Keying Bands for the 1 10 Selecting the DH Station Address of Channel 1A 1 11 Specifying the Serial Interface of 0 1 12 Selecting the ControlNet Network Address of Channel 2 1 12 Inserting Removing the Processor into from the 1 0 Chassis 1 13 Installing a Remote 0 1 13 Installing 1 15 Connecting to a ControlNet Network 1 17 Connecting a Programming 1 19 DAF CODDECUDII V es ar DRE RE 1 19 Serial CNAME D 1 20 ControlNet 1 21 Selecting Appropriate 1 22 Serial 1 22 DH Programming 1 23 Remote TO 1 23 ControlNet Cables 1 23 Cha
6. 26 01 Start up protection after power loss when reset no protection When set processor sets major fault bit S 11 5 when powering up in run mode 5 26 02 Define the address of the local rack when reset local rack address is 0 When set local rack address is 1 26 03 Set complementary 1 0 series A only when reset complementary 1 0 is not enabled When set complementary 1 0 is enabled 26 04 Local block transfer compatibility bit when reset normal operation When set eliminates frequent checksum errors to certain BT modules 26 05 PLC 3 scanner compatibility bit when set 1 adapter channel response delayed by 1 ms when reset 0 operate in normal response time 26 06 Data table modification inhibit bit When set 1 user cannot edit the data table or modify forces while the processor keyswitch is in the RUN position You control this bit with your programming software S 26 07 through S 26 15 Reserved S 27 Rack control bits See also 5 7 5 32 5 33 5 34 and 5 35 e 27 0 7 1 0 rack inhibit bits for racks 0 7 e 5 27 8 15 1 0 rack reset bits for racks 0 7 5 28 Program watchdog setpoint 5 29 Fault routine file 5 30 STI setpoint 5 31 STI file number 5 32 Global status bits See also 5 7 5 27 5 33 5 34 and 5 35 e 32 0 7 rack fault bits for racks 10 17 octal e 32 8 15 unused Processor Status Fil
7. 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 about STIs see your programming software documentation A Major Fault with error code 200 and 201 means that the processor was unable to transmit the scheduled data it is configured to transmit This is typically caused by disturbances on the ControlNet channel because of missing terminators bad connectors or noisy conditions These disturbances may cause the processor to fall off the network while its trying to transmit its scheduled data If you consistently get these faults you may want to check and repair the cable This fault can also occur when the processor falls behind and did not have the scheduled data ready to send on time Depending on the requirements of the application you may consider adding a fault routine to the application to clear an occurrence of a Major Fault with error code 200 and 201 For detailed information about creating fault routines refer to chapter 16 of the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publicatio
8. Prevent Electrostatic Discharge ATTENTION This equipment is sensitive to electrostatic discharge which can cause internal damage and affect normal operation Follow these guidelines when you handle this equipment e touch a grounded object to discharge potential static wear an approved grounding wrist strap e do not touch connectors or pins on component boards e do not touch circuit components inside the equipment e if available use static safe workstation e when notin use store the equipment in appropriate static safe packaging 1785 UM022C EN P February 2008 Identifying ControlNet PLC 5 Processor Components Installing Your ControlNet PLC 5 Processor 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 1 0 Status Indicator Green Red al gt 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 2400
9. e Error code indicates the error when the ER bit is set Features As many as 32 ControlNet MSGs can be active at a time e Minor fault bit S 17 13 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 chapter 4 and Appendices C and F for more information 1 2 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 See Appendix D for a list of ControlNet error codes Using 1 0 Forcing Operations ControlNet I O forcing occurs in the same way as remote I O forcing in the ControlNet 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 DIF and DOF data is not supported For detailed information about forcing see your programming software documentation 1785 UM022C EN P February 2008 2 8 Planning to Use Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 Using Immediate Data Transfer Operations ControlNet Immediate Data I O tr
10. e aredundant owner connection can be made A listen only connection can only be made to the adapter if e an exclusive owner connection already exists or e aninput only connection already exists or e a redundant owner connection already exists If a redundant owner connection is made to the adapter e anexclusive owner connection will be rejected e aninput only connection can be made alisten only connection can be made e another identical redundant owner connection can be made Multiple Processors Can Control I O on the Same ControlNet Link A processor at any valid node address can control the outputs of a particular module or rack However only one processor can control the same outputs at any one time In the following figure the processor at node 1 can control the outputs of node 2 while the processor at node 3 controls the outputs of node 4 in x B E node 1 node 2 node 3 node 4 1785 UM022C EN P February 2008 2 14 Heartbeat Connection 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 e Network opti
11. 4 Blue 4 Blue LI 82W or 150W resistor WARNING 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 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 Connecting to a ControlNet Network Straight T tap 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 A e from trunk cable A to channel A on the processor and from trunk cable B to channel B on the processor Rockwell Automation recommends using channel for nonredundant media Installing Your ControlNet PLC 5 Processor 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 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 electri
12. Addressing Number of Words Reserved me 4 Slots 8 Slots 12 Slots 16 Slots 2 Slot 2 4 6 7 1 Slot 4 8 19 1 2 Slot 8 16 z The programming software reserves non ControlNet Remote I 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 37 for the PLC 5 20C15 processor 00 177 for the PLC 5 40C15 processor 00 177 for the PLC 5 46C15 processor 00 277 the PLC 5 80C15 processor The output image offset value in the I O map corresponds to the first slot of the referenced chassis 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 table 1 e if a chassis set for 1 slot addressing has an input image offset of 1 10 and an input module in slot 3 the word that corresponds to that input module would be 1 10 4 3 or I 13 1785 UM022C EN P February 2008 2 18 Planning to Use Your ControlNet PLC 5 Processor Supported ControlNet 1 0 Sizes The following table shows the maximum I O map entries allowed in the C
13. Now if you optimize the map table looks like this Input file Input size Output file Output size 1 010 2 0 010 6 By placing the input modules first you only have to map two input words to the chassis and do not lose any by having to pass over output modules The outputs only lose two words by passing over the inputs This example shows the first rule of module optimization First Rule of Module Optimization Planning to Use Your ControlNet PLC 5 Processor 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 Examine the following chassis ACN A 0 0 ps Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter A Analog Module PS Power Supply This chassis contains an analog module and a power supply Assume all analog modules on a ControlNet network are mapped to an integer table in the PLC 5 processor Power supplies do not require any I O image table Therefore the optimal configuration of this chassis is ACN 0101 PS Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter A Analog Module PS Power Supply Input file Input size Output file Output size 010 6 0 010 2 Since analog modules and power supplies do not need any I O image space you should place them to the ri
14. Source N12 175 IDI IMMEDIATE DATA INPUT Data file offset 232 Length 10 Destination N11 232 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 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 Using Selectable Timed Interrupts with a Program a ControlNet Network on page 4 9 Data Table N11 0 Private DIF Buffer N11 232 232 IDI copies from the private DIF buffer to the data table Inputs arrive from the ControlNet network 1785 UM022C EN P February 2008 4 8 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 1s stored The Length 24 identifies the number of words in the transfer or a logical address that sp
15. blinking being transferred to EEPROM Red Major fault e RSLogix 5 During RSLogix 5 download this is blinking download in normal operation wait for progress download to complete e Run time error If not during RSLogix 5 download Check major fault bit in status file S 11 for error definition Clear fault correct problem and return to run mode Alternating Processor in Normal operation if No action required allow flash Red and FLASH memory processor s FLASH update to complete Green programming mode memory is being reprogrammed Red Power cycle with Battery is low Properly replace or install battery steady problem battery disconnected or not see Chapter 1 for more installed information Red Fault with memory New processor Use programming software to steady loss clear and initialize memory e Invalid ControlNet Verify that ControlNet address network address Switch is not set to 0 Processor has Install battery to preserve failed internal failure diagnostics then power diagnostics down reseat processor and power up then reload your program If you are unable to reload your program replace the processor If you are able to reload your program and fault persists contact Technical Support at 440 646 6800 to diagnose the problem Off Processor is in Check power supply and program load or test connections mode or is not receiving power FORCE Amber SFC and or 1 0 forces Normal operation No action required stea
16. link device 1785 UM022C EN P Blue Shield amp Clear gt 1770 CD February 2008 PLC 5 40C 5 46C 5 80C Processor ided in the accessory kit Gu e 9 O PLC 5 20C Processor 82W or 150W resistor JE Terminate both ends of a remote 1 0 link Installing Your ControlNet PLC 5 Processor 1 15 WARNING 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 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 a DH Link Use 1770 CD cable to connect the processor to a DH link Follow these guidelines while installing DH communication links e not exceed these cable lengths trunk cable length 3 048 m approximately 10 000 cable ft drop cable length 30 4 m approximately 100 cable ft e do not connect more than 64 stations on a single DH link 1785 UM022C EN P February 2008 1 16 Installing Your ControlNet
17. you encounter fault code 88 be sure you followed proper design guidelines Specifically make sure you group together 1 4 racks and 1 2 racks of each logical rack Do not intersperse these with other rack numbers e if using complementary 1 0 addressing treat complementary rack addresses individually when grouping racks primary rack numbers are separate from complement rack numbers 90 Sidecar module extensive memory test failed Call your Rockwell Automation representative for service 91 Sidecar module undefined message type 92 Sidecar module requesting undefined pool 93 Sidecar module illegal maximum pool size 94 Sidecar module illegal ASCII message 95 Sidecar module reported fault which may be the result of a bad sidecar program or of a hardware failure 96 Sidecar module not physically connected to the PLC 5 processor 97 Sidecar module requested a pool size that is too small for PC command occurs at power up 98 Sidecar module first last 16 bytes RAM test failed 99 Sidecar module to processor data transfer faulted 100 Processor to sidecar module transfer failed 101 Sidecar module end of scan transfer failed 102 The file number specified for raw data transfer through the sidecar module is an illegal value 103 The element number specified for raw data transfer through the sidecar module is an illegal value 104 The size of the transfer requested through the sidecar module is an illegal size 105 The offset into the raw transfer seg
18. 1771 2 111 1771 P4 1771 2 111 1771 P4R 1771 5 3 1771 P4S 1771 2 13 1771 P5 1771 2 111 1771 P6R 1771 5 3 1771 P6S 1771 5 11 1771 P7 1771 5 56 1785 UM022C EN P February 2008 1 6 Installing Your ControlNet PLC 5 Processor Install or Replace the Battery 1785 UM022C EN P February 2008 A 3 0 volt lithium battery cat 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 DO NOT use any other type or size of battery Important In non hazardous environments it may be possible to replace the battery while the processor is powered so that your programs are maintained in memory You may lose your programs if you remove the battery when power is removed WARNING When you connect or disconnect the battery 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 For safety information on the handling of lithium batteries including handling and disposal of leaking batteries refer to Guidelines for Handling Lithium Batteries publication AG 5 4 Store batterie
19. 1784 PCC card PCMCIA based and your HMI or your HMI or and your HMI and your HMI or programming software programming software or programming software programming software PLC 5 40C 1784 PCC1 to PLC 5 NAP port or any other NAP port mm 20 mn 0 min 20 Serial connection s a 1 3 d 41770 KFC15 ccr i ee Interface Tap 4 choices TEE 1786 TPR 6i T Remote VO link Tap 4 choices Data Highway Plus link 1786 CIPR J CEST PLC 5 40C ControlNet Network ios a FM _ i 1794 ACNR15 1747 ACNR15 p Eee Flex 1 0 Adapter Adapter 1771 ACNR15 Adapter Example of a ControlNet Network with Redundant Media Personal computer Personal computer or with 1784 KTCX15 car
20. 5 60L e PLC 5 20E PLC 5 80 e PLC 5 30 e PLC 5 80C15 1A 1A e PLC 5 40 e PLC 5 80E e PLC 5 40C15 e PLC 5 46C15 e PLC 5 40E e PLC 5 20 e PLC 5 40L 1B 1B e PLC 5 20C15 PLC 5 60 e PLC 5 20E e PLC 5 60L e PLC 5 30 PLC 5 80 e PLC 5 40 PLC 5 80C15 e PLC 5 40C15 PLC 5 80E e PLC 5 46C15 e PLC 5 40E e PLC 5 20C15 PLC 5 46C15 2 2 e PLC 5 40C15 PLC 5 80C15 If they fit and are downloaded unchanged 1785 UM022C EN P February 2008 Planning to Use Your ControlNet PLC 5 Processor 2 35 Program files Can be run on a ControlNet for this process Archived from a On channel PLC 5 channel If they fit and are Messaging and 1 0 e PLC 5 11 e PLC 5 40L 1A 2 performed by the ControlNet network you continued e PLC 5 20 e PLC 5 46C15 must make these changes manually by e PLC 5 20015 e PLC 5 60 reprogramming e PLC 5 20E e PLC 5 60L e PLC 5 30 PLC 5 80 e PLC 5 40 PLC 5 80C15 e PLC 5 40C15 PLC 5 80E e PLC 5 40E e PLC 5 20 e PLC 5 40L 1B 2 e PLC 5 20C15 PLC 5 46C15 e PLC 5 20E PLC 5 60 e PLC 5 30 e PLC 5 60L e PLC 5 40 e PLC 5 80 e PLC 5 40C15 PLC 5 80C15 e PLC 5 40E e PLC 5 80E e PLC 5 40 PLC 5 80 2A or 2B 2 e PLC 5 60 1A or 1B performed by DH or remote 1 0 must make these changes manually by reprogramming e PLC 5 20E e PLC 5 60L 2 1A 1B performed by DH or remote 1 0 must e PLC 5 40E e PLC 5 80E make the
21. Foundation Fieldbus CN2FF networks 1756 CNBR ControlLogix ControlNet Bridge Allows the ControlNet processor remote access to Allen Bradley s family of 1756 CN2 1756 controllers via a ControlNet network PV 550 600 900 1000 1400 1000e Panel View ControlNet products with ControlNet comm option Allows the ControlNet processor remote access to Allen Bradley s PanelView ControlNet operator interfaces via a ControlNet network and 1400e 1203 CN1 Any scan port drive or device that Allows the ControlNet processor remote access to Allen Bradley s scan port communicates thru 1203 CN1 drives or devices that communicate through a 1203 CN1 via a ControlNet network 1336T AC Vector Drives with direct fiber ControlNet Allows the ControlNet processor remote access to Allen Bradley s AC Vector Drive 1395 Digital DC Drive connections and Digital DC drives via a ControlNet network 1785 UM022C EN P February 2008 2 32 Planning to Use Your ControlNet PLC 5 Processor Example of a ControlNet Network without Redundant Media Personal computer Personal computer or with 1784 KTCX15 card Personal computer La ptop computer with other serial device ISA based and with PCIC card PCl based
22. Interface HMI devices 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 The system specific amount reserves time of time for all for network scheduled maintenance operations Any time remaining is used for unscheduled operations Unscheduled messaging on a ControlNet network is non deterministic Your application and your configuration number of nodes application program NUT amount of scheduled bandwidth used etc determine how much time there 1s for unscheduled messaging Important The ControlNet network reserves time for at least one maximum sized unscheduled transfer per NUI Depending on how much time there is for unscheduled messaging every node may not have a chance to send unscheduled data every NUI 1785 UM022C EN P February 2008 Operation Non discrete 1 0 Data Transfer CIO Instructions Planning to Use Your ControlNet PLC 5 Processor Description Table 2 B ControlNet Unscheduled Data Transfer Operations Perform ladder initiated unscheduled non discrete 1 0 data transfers on a ControlNet network by using ControlNet 1 0 Transfer CIO instructions The d
23. Monitoring and Troubleshooting Your ControlNet System Processor Specifications Processor Status File ControlNet Instruction Set Table of Contents ControlNet PLC 5 Programmable Controllers iii Chapter 4 Using This Chapter 4 1 Using ControlNet Message Instructions 4 1 Multihop Messaging Via the MSG Instruction 4 2 Option to Close Communication Connection when MSG is Done 4 3 Understanding the ControlNet PLC 2 Compatibility File 4 3 Using the ControlNet 1 0 Transfer 4 3 Sending Continuous 4 5 1771 ControlNet Transfers in Plls and 515 4 5 Using ControlNet Immediate Data Input and Output Instructions 4 6 Using Selectable Timed Interrupts with a Program on a ControlNet 4 9 Recovering from Major Fault 200 and 201 4 9 Chapter 5 Using This CHAD disiri teto seie irii en 5 1 Using the General Status 5 1 Using the ControlNet Status 5 3 Using the DH RIO Status 5 5 Monitoring ControlNet Configuration and Status 5 6 Appendix A Appendix B DSO RE dd PP RT 1 won B 2
24. No 17865 12015 1785 140 15 1785 146 15 1785 18015 Pub No 1783 UMOO1A EN P Pub Date April 2008 Part No Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2 Completeness all necessary information is provided Technical Accuracy 1 2 all provided information is correct Clarity 1 2 all provided information is easy to understand Other Comments 3 How Can we add more information to help you procedure step illustration feature example guideline other explanation definition Can we be more accurate text illustration How can we make things clearer You can add additional comments on the back of this form Your Name Your Title Function Location Phone Would you like us to contact you regarding your comments No there is no need to contact me Yes please call me Yes please email me at Yes please contact me via Return this form to Rockwell Automation Technical Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Fax 440 646 3525 Publication CIG C0521D EN P July 2007 Email RADocumentComments ra rockwell com PLEASE FASTEN HERE DO NOT STAPLE Other Comments PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND POSTAGE WILL BE PAID BY THE
25. 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 ControINet documentation The types of modules that may be accommodated by the processor s 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 1771 modules you can also include explicit CIO instructions in your ladder logic program See Chapter 4 and Appendix C for more information The 1771 discrete rack must be owned by a processor before any non discrete connections scheduled or unscheduled can be established with the 1771 adapter The non discrete connections can be established by the owner processor and or non owner processors ATTENTION The Run Program mode for all modules in a 1771 chassis is controlled by the owning discrete rack connection You must consider this when configuring non discrete connections from other processors 1747 Modules ControlNet 1747 discrete I O data transfer mapping requires one map table entry per node ControlNet 1747 non discrete I O data transfer mapping requires one map table entry per module The ControlNet s
26. OK If bit xis set then the module in slot x is missing bad or is the wrong type 1794 Analog Write Clear 0 0 1794 Analog Read Write Clear 0 If bit xis clear then the module in slot x is OK If bit xis set then the module in slot x is missing bad or is the wrong type 1785 UM022C EN P February 2008 D 4 ControlNet 1 0 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 Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code VARIOUS VARIOUS CONFIGURATION DATA The ControlNet configuration is Reenter the map entry that is failing CORRUPTED corrupted Reenter the ladder instruction that is failing 1 0x0001 CONNECTION FAILED The ControlNet cable from the Fix and or reconnect the ControlNet originating node to the target node is cable broken or disconnected The target node is not powered Supply power to the target node The target s node number is greater Reconfigure the ControlNet network than SMAX so that the target s node number is less than or equal to SMAX 5 0x0005 UNKNOWN DESTINATION The slot addressed does not exist Use a rack with more slots ADDRESS Correct the 1 0 map table The map table is corrupted Reenter the 1
27. ON OFF ON OFF toward TOP E OFF Toggle pushed OFF OFF oN OFF OFF OFF OFF OFF oN OFF toward BOTTOM RS 422A UMP ON ON ON OFF OFF ON OFF OFF ON OFF RS 423 Selecting the ControlNet Network Address of Channel 2 For optimum throughput assign addresses to your ControlNet nodes in a sequential order starting with 01 1785 UM022C EN P February 2008 Select your processor s ControlNet network address by setting the two 10 digit rotary switches on the top of the processor 20 30 2 3 10 10 4 00 50 0 5 Network address 01 is shown 90 30 9 9 80 70 8 7 NET ADDRESS You can select from as many as 99 network addresses from 01 to 99 for a processor on a ControlNet link 0 is invalid Important Do not power up the processor if the processor s ControlNet network address is set to 0 If you do you will not be able to communicate with your processor and your ladder program will be lost even if you have a battery installed If this happens select a valid network address for the processor and cycle power Inserting Removing the Processor into from the 1 0 Chassis Card Guides Installing a Remote 1 0 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 e trunk cable length depends on the communication rate of the link see Tabl
28. Operates at 57 6K or 115 2K bit s and you do not require over 16 physical devices You can install a remote 1 0 link two ways trunk cable drop cable from the drop cable to the connector screw terminals on the remote 1 0 connectors of the processor daisy chain to the connector screw terminals on the remote 1 0 connectors of the processor and then to the remote 1 0 screw terminals of the next remote 1 0 device To connect remote 1 0 cable use the Phoenix MTSB2 5 3 ST 3 pin header connector prov 1 Run the 1770 CD cable from the processor to each remote 1 0 adapter module or processor in the remote 1 0 system 2 Connect the signal conductor with blue insulation to the 3 pin connector terminal labeled 1 on the processor and to each remote 1 0 adapter module or PLC 5 adapter in the remote 1 0 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 1 0 network cable to the chassis to relieve strain on the cable 6 Terminate the remote 1 0 link by connecting an external terminator resistor between the remote 1 0 terminals labeled 1 and 2 e 1770 CD To another 1 0 99m Blue p Shield 0 Clear
29. 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 communication link You can install a link two ways trunk cable drop cable from the drop cable to the connector screw terminals on the 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 5 3 ST 3 pin header connector provided in the accessory kit 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 1785 UM022C EN P February 2008 CoO ON PLC 5 400 5 46 PLC 520 or 5 80C processor processor HE i i Clear l lt a Shield Shield i lt a Clear m L 82W or 150W resistor
30. The corresponding data table file must exist and be large enough to accommodate the PLC 2 requests You can use a MOV instruction in the ladder program to update 8 73 The PLC 2 type MSG instructions error if the PLC 2 compatibility file on the target PLC 5 processor is invalid Condition Error Code Returned Corrective Action PLC 2 Compatibility file number is less than 3 or greater than 999 0x8000 Set 5 73 to a value between 3 and 999 inclusive between 3 and 999 but file does 0x8000 Create the data not exist table file referred by 5 73 between 3 999 exists but file is 0x5000 Increase the size of not large enough the data table file referred by S 73 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 Use your programming software to go to the instruction entry for ControlNet I O transfer block screen 1785 UM022C EN P February 2008 4 4 If you want to Do this change the command type Select one of the following 1771 READ reads input data from 1771 non discrete 1 0 module e 1771 WRITE writes output data to 1771 non discrete 1 0 module 1794 READ reads data from a 1794 1 0 module e 1794 WRITE writes data to a 1794 1 0 module e 1794 FAULT ACTION changes the action that a module takes when it faults 1794 IDLE ACTION changes the action that a m
31. UM022C EN P February 2008 Hardware Addressing 2 slot Any mix of 8 pt modules e 16 pt modules must be 1 0 pairs No 32 pt modules 1 slot Any mix of 8 or 16 pt modules e 32 pt modules must be 1 0 pairs 1 2 slot Any mix of 8 16 or 32 pt modules Communication Serial DH DH using 1785 KA Remote 1 0 ControlNet Wire Category 9 Relay Cartridge Wire Category 1 Location 1771 A1B A2B A3B A3B1 4 chassis left most slot Weight PLC 5 20C15 3 Ibs 3 oz 1 45 kg PLC 5 40C15 3 Ibs 2 oz 1 42 kg PLC 5 46C15 3 Ibs 2 oz 1 42 kg PLC 5 80C15 3 Ibs 2 oz 1 42 kg Keying Between 40 and 42 Between 54 and 56 Certifications when product is marked UL UL Listed Industrial Control Equipment CSA CSA Certified Process Control Equipment CSA CSA Certified Process Control Equipment for Class 1 Division 2 Group A B C D Hazardous Locations European Union 89 336 EEC EMC Directive compliant with EN 50081 2 Industrial Emissions EN 50082 2 Industrial Immunity European Union 73 23 EEC LVD Directive compliant with EN 61131 2 Programmable Controllers Australian Radiocommunications Act compliant with AS NZS 2064 Industrial Emissions C Tick The clock calendar will update appropriately each year The 1785 CHBM cannot be used with the 1785 5 60C processor The 1785 ME16 cannot be used with ControlNet PLC 5 processor
32. adjacent slots This allows you to set the density of the chassis to a lower value than the modules used in the chassis and then share the I O between the slots For example you can set a chassis to 2 slot addressing and then place 16 point modules in the chassis alternating input and output modules 1785 UM022C EN P February 2008 2 28 Planning to Use Your ControlNet PLC 5 Processor 2 slot addressing 16 point modules 2 slot addressing 16 point modules 1785 UM022C EN P February 2008 Example 1 Examine the following chassis ACN 0 0 0 0 Discrete Input Module 0 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 The first output module uses eight outputs from the first slot and eight outputs from the second slot and so on Given an 8 slot chassis in 2 slot addressing there are four words of inputs and four words of outputs used in this chassis On a ControlNet network you can map four words of inputs and four words of outputs to this chassis and no I O image space is wasted If you set the addressing mode to 1 slot addressing and use the methods described in the previous section you waste either four words of input or four words of output image table This method works extremely well for cases where there are equal numbers of input and
33. input file do not access the data until the PCSC new data bit has been set by the system When this bit is set to one it signifies that new data has been received and it is safe to read from your ControlNet data input file This data is not updated again until you clear this bit or until housekeeping occurs between program scans Never set this bit to one 4 PCSC Overflow This bit indicates that your program is not checking the PCSC new data bit often enough to use all processor control sample complete data that has arrived If the PCSC new data bit has not been cleared by the time a new data sample arrives the PCSC overflow bit is set and the new data is not copied to the ControlNet data input file You must clear this bit If you clear the PCSC New Data bit but not the PCSC overflow bit the ControlNet data input file is still updated when the next process control sample complete data is received Never set this bit to one 1785 UM022C EN P February 2008 Understanding Scheduled Connection Types 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 w
34. ladder program scan by either adding more logic or by increasing the Communications Time Slice S 77 Reduce the number or frequency of immediate ControlNet 1 0 ladder instructions that are performed 206 This error code is reserved Contact your local Rockwell Automation representative if you get this message 207 This error code is reserved Contact your local Rockwell Automation representative if you get this message 208 Too many pending ControlNet 1 0 connections Recoverable Delete one or more 1 0 map table entries and reaccept edits for the ControlNet configuration 230 System attempted transition to Run mode with processor in Invalid backup state Change from the Invalid backup state to the No Control backup state before transitioning into Run mode Refer to the Invalid backup state troubleshooting table later in this chapter 1785 UM022C EN P February 2008 Processor Status File This fault code 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 Reconf
35. ms 5 10 Minor fault word 1 See also 5 17 5 10 00 Battery is low replace 1 2 days 10 01 DH active node table has changed 5 10 02 STI delay too short interrupt program overlap 10 03 memory module transferred at power up Processor Status File B 3 This word of the status file Stores 5 10 04 Edits prevent SFC continuing data table size changed during program mode reset automatically in run mode 10 05 Invalid 1 0 status file 10 06 reserved 5 10 07 No more command blocks exist to execute block transfers 10 08 Not enough memory on the memory module to upload the program from the processor 10 09 No MCP is configured to run 5 10 10 not allowed 10 11 PII word number not in local rack 5 10 12 PII overlap 10 13 no command blocks exist to get PII 5 10 14 Arithmetic overflow 5 11 This word of the status file Stores 5 11 major fault word 11 00 Corrupted program file codes 10 19 See major fault codes S 12 11 01 Corrupted address in ladder program codes 20 29 See major fault codes S 12 11 02 Programming error codes 30 49 See major fault codes S 12 11 03 Processor detected an SFC fault codes 71 79 See major fault codes S 12 11 04 Processor detected an error when assembling a ladder program file code 70 duplicate LBLs found 11 05 Start up
36. o Scheduled data transfer occurs between the PLC 5 and the adapter module in the 1 0 chassis Data may Stay in the private memory buffer for up to 1 API 1 0 Chassis In the same manner Scheduled Data Private the 1 0 adapter has Transfer Memory Data Update scheduled 1 0 data Buffers lt transfer with 1 0 modules Adapter Module 1 0 Modules Input data is written from the 1 0 module to a private memory buffer on the adapter The new input data may stay in the private memory buffer for as long as it takes to complete the 1 0 chassis backplane update The frequency of I O chassis backplane updates depends on the adapter the type of scheduled data transfer rack or module connection and the number of different modules being updated Actual I O throughput times must be determined with real products to determine if the I O throughput times meet the requirements of the application 1785 UM022C EN P February 2008 2 4 Planning to Use Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 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 1 0 Data Performed in a deterministic and repeatable manner Transfer can be done asynchronous to and independent of the ladder logic as a rack or module program scan You configure all ControlNet discrete 1 0 c
37. output cards However in most cases there are not the same number of each module Example 2 Examine the following chassis ACN 0 0 X 0 X 0 Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter X Empty Slot In this case you can map two words of input and four words of output to the chassis and not waste any I O image table However you waste physical space note the two empty slots Look at the case where you have 14 input modules and two output modules If you use slot complementary you have to purchase an additional chassis and therefore an additional adapter and power supply since you can only put eight of the input modules in one chassis one module every other slot If you do not use slot complementary you can fit all the cards in one chassis and only sacrifice two output image table words With the slot complementary method you cannot just put any module anywhere If you wish to add an output module to the chassis shown above you cannot since there are no output slots available you have to start a new chassis 2 slot addressing 16 point modules 2 slot addressing 16 point modules 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 Method Tradeoffs optimize witho
38. output image table PLC 5 80C 192 words of input image table and 192 words of output image table The I O image table is used for all discrete I O connected to the PLC 5 processor regardless of where it is located local I O Remote I O ControlNet network Since the local chassis reserves a minimum of eight words of input and output a PLC 5 20C processor has a maximum of 24 words of inputs and 24 words of outputs available for the ControlNet network Some applications may find that the use of I O image space needs to be optimized to insure that the I O requirements can be met A node address on a ControlNet network does not directly map to a location in the I O image table like it does on a Remote I O network For example If you have an 8 slot chassis in 1 slot addressing and set the node address to two and If the node is on a Then Remote 1 0 network the inputs in that chassis automatically map to 020 1 027 if the node is on a remote 1 0 network ControlNet network you can map the inputs to any location available in the input image table and the outputs to any location available in the output image table The input and output locations can be in two totally different rack numbers For example you can specify I 024 as the input location and O 032 as the output location The only restriction is that you must map the input and output words contiguously If you mapped eight words of inputs you must map it t
39. protection fault The processor sets this major fault bit when powering up in Run mode if the user control bit S 26 1 is set 5 11 06 Peripheral device fault 11 07 User generated fault processor jumped to fault routine codes 0 9 See major fault codes S 12 11 08 Watchdog faulted 11 09 System configured wrong codes 80 82 84 88 200 208 See major fault codes S 12 11 10 Recoverable hardware error 11 11 MCP does not exist or is not a ladder or SFC file 1785 UM022C EN P February 2008 Processor Status File This word of the status file Stores 11 12 PII file does not exist or is not a ladder file 11 13 STI file does not exist or is not a ladder file 11 14 Fault routine does not exist or is not a ladder file 11 15 Faulted program file does not contain ladder logic 12 This word stores the following fault codes This fault code Indicates this fault And the fault is 00 09 Reserved for user defined fault codes Recoverable You can use user defined fault codes to identify different types of faults or error conditions in your program by generating your own recoverable fault To use these fault codes choose an input condition that decides whether to jump to a fault routine file then use the JSR instruction as the means to jump to the fault routine file To use the JSR instruction enter the fault code number 0 9 an immediate va
40. table protection file number 1785 UM022C EN P February 2008 B 14 Processor Status File 1785 UM022C EN P February 2008 This word of the status file Stores 5 64 The number of remote block transfer command blocks being used by channel pair 1A 1B 65 The number of remote block transfer command blocks being used by channel pair 2N 2B 5 66 Reserved 5 68 Installed memory card type The four most significant bits indicate memory card type Value Memory card type 0 No memory card installed 1 1785 ME16 installed 2 1785 ME32 installed 3 1785 ME64 installed 4 1785 ME100 installed 5 1785 CHBM installed 6 1785 RC installed 7 15 Reserved When the 1785 RC module is installed the eight least significant bits indicate the memory card s status Bit Is set when 3 the 1785 RC memory card is installed in the processor 2 contact is detected closed The bit resets when contact is detected open 1 the relay is driven open The bit resets when the relay is closed 0 120Vac is present on the memory card The bit resets when 120Vac is not present on the card When any other memory card is installed the bits are undefined 5 72 ControlNet node number of this processor 5 73 ControlNet PLC 2 compatibility file When a PLC 2 command is received from the ControlNet network the processor uses this file number The PLC 2 file number must be between 3 and 999 inclusive 5 74 Time in milliseconds
41. the ControlNet PLC 5 RSLogix 5 software creates a project rsp file on your personal computer when you save the project These two software packages are separate tools because RSNetWorx software is used to configure the entire ControlNet network and RSLogix 5 software is used to configure node specific information 1785 UM022C EN P February 2008 3 2 Understanding the ControlNet System Software 1785 UM022CEN P February 2008 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 Two interdependencies exist between RSNetWorx and RSLogix 5 software e the I O configuration utility invoked in RSLogix 5 software e ControlNet configuration information is created and saved in RSNetWorx software but is also saved and downloaded in RSLogix 5 software 1 0 Configuration Utility The I O configuration utility in RSLogix 5 software is used to simplify the configuration of intelligent I O modules It is important to understand the difference between I O configuration over remote I O vs I O configuration over ControlNet e over remote I O the information displayed and entered in the configuration applet is always read and written to the data table Thus all of the I O configuration functionality over remote I O is contained with the RSLogix 5 application over ControlNet the information displayed and entere
42. this bit is set The processor will also set the Data Invalid Bit and Connection Error Bit Clear this bit to allow the processor to attempt to open the associated connection Data Invalid Bit The processor sets this bit when data is not received from the associated target node The error code in second and third words of the ControlNet 1 0 status tells you why the data is invalid Also if either the Inhibit Bit or Immediate Inhibit Bit is set the Data Invalid Bit will be set The processor clears this bit when valid data is received from the associated target node In your program make sure that this bit is clear before you use the associated data Connection Error Bit The processor sets this bit when the associated connection is not made to the target node The error code in second and third words of the ControlNet 1 0 status tells you why the connection is not made Also if either the Inhibit Bit or Immediate Inhibit Bit is set the Connection Invalid Bit will be set The processor clears this bit when the associated connection is made to the target node Data Underrun This bit it set whenever the length of data received for the associated connection is smaller than expected The Data Invalid Bit will also set if the length of data received is less than the value configured in the Input Data Size field for the connection in RSNetworx Data Overrun This bit it set whenever the length of data received for the associa
43. to the originating node powered when the ControlNet and reconfigure the ControlNet network was configured network 797 Ox31D INVALID TARGET TAG The PLC 5C is requesting data from Change the PLC 5C 1 0 map entry to a ControlLogix tag that is not use the correct tag configured as a producer Reconfigure the tag in the ControlLogix processor to be a producer REDUNDANT CONNECTION Configuration for this redundant Change the PLC 5C 1 0 map and MISMATCH connection does not match the module configuration data to match configuration used by the Hot the Hot Backup partner Backup partner 798 Ox31E TAG IS ALREADY PRODUCED The PLC 5C is requesting data from In the ControlLogix processor THE MAXIMUM NUMBER OF a ControlLogix tag that is already increase the number of times this TIMES being produced the maximum tag can produce data number of times 65522 OxFFF2 CONFIGURATION FROM MAP The ControlNet cable from the Fix and or reconnect the ControlNet ENTRY FAILED originating node to the target node is cable broken or disconnected The target node is not powered Supply power to the target node The target slot is empty The target slot contains the wrong module type Insert the proper module in the correct slot of the target node An incorrect module or slot was entered in the map table Edit the 1 0 map table to show the correct module type and slot 1785 UM022C EN P February 2008 ControlNet 1 0
44. with other ControlNet nodes using scheduled or unscheduled peer to peer communication 1784 KTC15 KTCX15 KTCS ControlNet ISA Communication Cards Allows other computer platforms to communicate with the ControlNet network 1784 PCC ControlNet PCMCIA Communication Card Allows other computer platforms to communicate with the ControlNet network 1770 KFC15 ControlNet Serial Parallel Communication Connects a serial or parallel device to a ControlNet network KFCD15 Interface 1747 ACN15 1747 ControlNet SLC 1 0 Adapters Allows the ControlNet processor remote access to Allen Bradley s family of ACNR15 SLC designated 1 0 modules via a ControlNet network 1771 ACN15 1771 ControlNet 1 0 Adapters Allows the ControlNet processor remote access to Allen Bradley s family of ACNR15 1771 designated 1 0 modules via a ControlNet network 1784 PCIC PCICS ControlNet PCI Communication Cards Allows other computer platforms to communicate with the ControlNet network 1794 ACN15 1794 ControlNet FLEX 1 0 Adapters Allows the ControlNet processor remote access to Allen Bradley s family of ACNR15 1794 designated 1 0 modules via a ControlNet network 1797 ACN15 1797 ControlNet Ex 1 0 Adapter Allows the ControlNet processor remote access to Allen Bradley s family of 1797 designated 1 0 modules via a ControlNet network 1788 CN2DN 1788 ControlNet Linking Devices Allows the ControlNet processor to link to DeviceNet or
45. 0 and 201 4 9 Expected Network Packet Time 1771 non discrete 1 0 data transfer mapping 2 21 F fault codes E 1 fault codes 200 and 201 4 9 fault routines E 1 files configured with 1 0 map for scheduled 1 0 usage 2 18 Data Input 2 18 2 19 Data Output 2 18 2 19 Default Configuration 2 18 1 0 Status 2 18 2 35 D 1 1 0 status 2 18 processor status B 1 frame definition of P 2 front panel PLC 5 20C processor 1 3 PLC 5 40C processor 1 4 G global status bits racks 07 B 2 racks 1017 B 12 Publication 1785 UM022C EN P February 2008 4 Index l 1 0 ControlNet 2 1 automatic mapping 2 16 discrete 1 0 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 1 0 Status File 2 18 1 0 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 1 0 data transfer mapping 2 19 2 20 reserving rack space for remote 1 0 linked racks before mapping 2 16 scheduled data transfer 2 2 scheduled operations discrete 1 0 data transfer 2 4 non discrete 1 0 data transfer 2 4 peer to peer communication 2 4 unscheduled 1 0 datatransfer instructions 4 3 immediate data 1 0 instructions 4 6 Message instruction 2 7 4 1 C 1 non discrete 1 0 data transfers 2 6 C 1 non discrete 1 0 data transfer instructions 4 3 unscheduled data transfe
46. 0 map entry that is failing The target node of the MSG Edit the ladder program so that the instruction is not a processor or the correct target node is used target node of the CIO instruction is not the correct 1 0 adapter Replace the target node with the correct type of node 12 0x000C OBJECT IN WRONG STATE The target Scheduled Peer Output Clear the inhibit and immediate map entry is inhibited inhibit bits for the target Scheduled Peer Output map entry 14 0x000E ATTRIBUTE CANNOT BE SET A CIO instruction attempted to setan Insert a module that can have this attribute that cannot be set at the attribute set into the correct slot destination module For example a CIO tried to send safe state data to a Flex module that does not support safe state data Edit the ladder program so that it does not attempt to set this attribute 19 0x0013 NOT ENOUGH DATA The transfer length is zero Increase the transfer length The processor data table is too small Increase the size of the data table to to hold the data to be transferred accommodate the transfer length 21 0x0015 TOO MUCH DATA The transfer length is too large Decrease the transfer length 1785 UM022C EN P February 2008 ControlNet 1 0 Map Entry Status Words and Error Codes D 5 Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 38 0x0026 INVALID DESTINATION The map ta
47. 5 or PLC 5 20C e Catalog number 1785 L40C15 PLC 5 40C e Catalog number 1785 L46C15 or PLC 5 46C e Catalog number 1785 L80C15 or PLC 5 80C For detailed information about features that the ControlNet PLC 5 processors share with Ethernet and Enhanced processors see the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication 1785 6 5 12 The information in this manual is intended for engineers and technicians who are installing programming and maintaining a control system that includes a ControlNet PLC 5 programmable controller You should have a background in control system applications and a basic knowledge of e programmable real time control systems e the PLC 5 control system e your operation s required systems and applications 1785 UM022C EN P February 2008 Preface 2 Terminology Term Actual Packet Interval API Description the actual time it takes for the ControlNet network to update the requested data The largest binary multiple of the Network Update Time NUT smaller or equal to the Requested Packet Interval RPI For more information see Scheduled Data Transfer Operations on a ControlNet Network on page 2 2 ControlNet network communication architecture that allows the exchange of data between Allen Bradley Company Inc products and certified third party products ControlNet PLC 5 processors references PLC 5 20C PLC 5 40C PLC 5 46C and PLC 5 80C pro
48. ADDRESSEE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Notes Rockwell Automation Support www rockwellautomation com Rockwell Automation provides technical information on the Web to assist you in using its products At http support rockwellautomation com you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running United States 1 440 646 3434 Monday Friday 8am 5pm EST Outside United Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell Automation tests all of its products to ensure that they are fully operat
49. Channel 2 ControlNet Status Indicators Green Red lt Battery Status Indicator q lt _ lt ControlNet Network Access Port Status Indicator NAP RJ45 connector Green Red Channel 2 E ControlNet Redundant Media Ports XK Channel 0 BNC dedicated Serial Port 25 pin D shell supports standard EIA RS 232C and RS 423 is RS 422A compatible CD Use this port with ASCII or DF1 full duplex half duplex master and half duplex slave rotocols The port s default configuration supports Channel 1 Status Indicators Green Red y MUS DH Programming Terminal Connection to 1 gt DF1 point to point one stop bit 8 pin mini DIN parallel with 3 pin connectors 2400 bps BCC error check of Channel 1A use only when Channel 1A is e no parity handshaking configured for DH communications Memory Module Space Channel 1A 3 pin default is DH configurable for e remote 1 0 scanner e remote 1 0 adapter E e DH communication m gt gt e unused Battery Compartment Channel 1B 3 pin default is remote 1 0 scanner configurable for e remote 1 0 scanner e remote 1 0 adapter e DH communication Channel 0 is optically coupled provides high e unused electrical noise immunity and can be used with most RS 422A equipment as long as e termination resistors are not us
50. ControlNet PLC 5 Programmable Controllers User Manual Catalog Numbers 1785 120 15 1785 L40C15 1785 L46C15 1785 L80C15 Rockwell ALLEN BRADLEY ROCKWELL SOFTWARE Automation Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls publication SGI 1 1 avail able from your local Rockwell Automation sales office or online at http literature rockwellautomation com de scribes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons re sponsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages result ing from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many vari ables and requirements associated with any particular installation Rockwell Automation Inc cannot assume re sponsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circu
51. ER SUPPLY The default setting is N not using a o MODULE IN power supply module in the chassis B THE CHASSIS m Y N Y N E H D q L Important You cannot power a single 1 0 chassis with both a power supply module and an external Set Y when you install a power supply module in the chassis Installing Keying Bands for the Processor power supply Set N when you use an external power supply 1 0 Chassis Backplane Connector N 2 Install a keying band in the left most A slot between the following pins 10 13 Use these i 7 1 1 numbers 20 asa guide 17075 You receive plastic keying bands with each I O chassis Insert the keying bands as follows Kevi em ATTENTION A module inserted into a wrong slot PHA H could be damaged by improper voltages connected rn n RK 2 through the wiring arm Use keying bands to prevent RK 50 damage to the module 52 54 FT se 12062 1785 UM022C EN P February 2008 Installing Your ControlNet PLC 5 Processor 1 11 Selecting the Station To select the DH station address of Channel set the switches of Address of Channel 1A assembly SWI Side View of PLC 5 20C 5 40C 5 46C 5 80C Switch Assembly SW1 Toggle pushed To select Se
52. ISPR 11 Group 1 Class A ESD Immunity IEC 61000 4 2 4kV contact discharges Radiated RF Immunity IEC 61000 4 3 10V m 3V m Broadcast Bands with 1kHz sine wave 80 AM from 30MHz to 1000Mhz EFT B Immunity IEC 61000 4 4 2kV at 5kHz on communications ports Surge Transient Immunity 61000 4 5 2kV line earth CM on signal ports Conducted RF Immunity IEC 61000 4 6 10Vrms with 1kHz sine wave 80 AM from 150kHz to 30MHz Enclosure Type Rating None open style Time of Day Clock Calendar Maximum Variations at 60 C 5 min per month Typical Variations at 20 C 20s per month Timing Accuracy 1 program scan Available Cartridges 1785 CHBM ControlNet Hot Backup Cartridge required for each processor used in a hot backup system 1785 RC Relay Cartridge Battery Allen Bradley 1770 XYC Memory Modules 1785 ME32 1785 ME64 e 1785 M100 1 0 Modules Bulletin 1771 1 0 1794 1 0 1746 1 0 and 1791 1 0 including 8 16 32 pt and intelligent modules The clock calendar will update appropriately each year 2 The 1785 CHBM cannot be used with the 1785 5 60C processor 3 The 1785 ME16 cannot be used with ControlNet PLC 5 processors 4 For more information refer to publication 1770 4 1 Industrial Automation Wiring and Grounding Guidelines 5 See the Product Certification link at http www ab com for Declarations of Conformity Certificates and other certification details 1785
53. 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 e When Channel 0 is configured for RS 422A compatibility do not use terminating resistors anywhere on the link e 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 pier ae iB Use this cable communication card 1784 KTX KTXD e 1784 CP13 1784 PCMK e 1784 PCM6 e 1784 5 with 1784 CP7 adapter 1784 PKTX PKTXD e 1784 CP13 Remote 1 0 Cables Use 1770 CD or cable for remote I O See Inserting Removing the Processor into from the I O Chassis on page 1 13 for more information ControlNet Cables Several types of RG 6 quad shield cable may be appropriate for your ControlNet installation depending on the environmental factors associated with your application and installation site 1785 UM022C EN P February 2008 1 24 Installing Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 The following ControlNet cable system components are available from the Rockwell Automation Item Cat No ControlNet Coax Tool Kit 1786 CTK Coax Tap Kit Right angle T tap 1786 TPR Straight T tap 1786 TPS Right angle Y tap 1786 TPYR Straight Y tap 1786 TPYS Repeater
54. Map Entry Status Words and Error Codes D 9 Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 65523 OxFFF3 CONTROLNET TRANSFER The immediate CIO instruction could Edit the ladder program so that the QUEUE FULL not be executed because the queue number of active 1771 READ WRITE is full CIO instructions is equal to or less than the maximum of 32 65527 OxFFF7 MODULE TIMED OUT The target slot is empty Insert the proper module in the correct slot of the target node The target slot contains the wrong module type An incorrect module or slot was Edit the 1 0 map table to show the entered in the map table correct module type and slot 65529 OxFFF9 COMMUNICATION ERROR A communication error between the Make sure that the module is CAUSED LOSS OF DATA adapter and the module caused the properly seated in the correct slot of transfer to be aborted the target node Make sure that the adapter s power supply is providing the proper voltage The target slot contains the wrong module type Insert the proper module in the correct slot of the target node An incorrect module or slot was entered in the 1 0 map table Edit the 1 0 map table to show the correct module type and slot 1785 UM022C EN P February 2008 D 10 ControlNet 1 0 Map Entry Status Words and Error Codes Decimal Hex Code Error Message Exp
55. Net 1 0 Transfer Instruction Instruction Description CIO CNET 1 0 TRANSFER Control block CT21 50 ControlNet 1 0 Transfer CT 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 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 1 0 transfer instruction The Control Block CT21 50 contains status and instruction parameters You cannot use N integer control blocks on the ControlNet network For continuous CIOs condition the rung to be true for only scan Message Instructions on a ControlNet Network Instruction Description Message If the input conditions go from false to true the data is MSG MSG transferred according to the instruction parameters you set SEND RECEIVE MESSAGE when you enter the message instruction The Control Block Control block MG10 10 MG10 10 contains status and instruction parameters Status Bits You cannot use N integer control blocks on the ControlNet TO Time Out Bit EW Enabled Waiting Bit CO Continuous Bit ER Error Bit DN Done Bit ST Start Bit EN Enable Bit NC No Cache Bit network For continuous MSGs condition the rung to be true for only scan 1785 UM022C EN P February 2008 C 2 ControlNet Instruction Set Immediate Data 1 0 Instr
56. Note A value of 219 in word 23 indicates that the ControlNet network is not usable 1785 UM022C EN P February 2008 F 4 Notes 1785 UM022C EN P February 2008 Numerics 1747 modules discrete 1 0 data transfer mapping 2 20 1770 CD 1 15 1 23 1770 KFC Communication Interface 2 31 1771 modules discrete 1 0 data transfer mapping 2 20 1771 ACN and ACNR Contro Net 1 0 Adapters 2 31 1771 AF 1 14 1771 AS 1 1 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 5 1 20 1 23 1784 6 1 20 1 23 1784 PCMK 1 20 1 23 1786 BNC BNC Connector 1 24 1786 BNCJ BNC Connector 1 24 1786 BNCJI BNC Connector 1 24 1786 BNCP BNC Connector 1 24 1786 CP 1 21 1786 CP ControINet Network Access Cable 1 24 1786 CTK ControlNet Tool Kit 1 24 1786 RG6 Quad Shield Cable 1 24 1786 RPA Repeater 1 24 1786 TPR Tap 1 17 1 24 1786 TPS Tap 1 17 1 24 1786 TPVR Tap 1 24 1786 TPVS Tap 1 24 1786 TPYR Tap 1 17 1786 TPYS Tap 1 17 1786 XT BNC Terminator 1 24 1794 FLEX 1 0 data transfer mapping 2 20 1794 FLEX 1 0 data transfer mapping 2 20 1794 modules discrete 1 0 data transfer mapping 2 20 1794 ACN ControlNet FLEX 1 0 Adapter 2 31 6008 SQH1 SQH2 1 14 Index A automatic 1 0 mapping 2 16 battery compartment location of on PLC 5 20C 1 3 on PLC 5 40C 1 4 bat
57. 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 T O racks on non ControlNet channels This allows the 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 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 programming software for the different sizes and addressing modes of processor resident local I O Addressing Number of Words Reserved Mode 4 Slots 8 Slots 12 Slots 16 Slots 2 Slot 8 8 8 8 1 Slot 8 8 16 16 1 2 Slot 8 16 24 32 Important ControlNet I O cannot map into any part of a rack number used by the processor resident rack 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 Planning to Use Your ControlNet PLC 5 Processor configure non ControlNet Remote I O on your processor
58. a is updated during housekeeping regardless of the state of the new data bit If new data is received and the PCSC new data bit is already set then the PCSC overflow bit is set In this event your data table will not be updated Process control sample complete uses bits 2 3 and 4 of the first word of the ControlNet I O status file entry See Appendix D for more information about the ControlNet I O status file The input data must be mapped into the DIF PCSC is not enabled if the input data is mapped into the discrete input image table PCSC Overflow Bit PCSC New Data Bit PCSC Enable Bit First Word 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Bit Description 2 PCSC Enable When this bit is set the processor updates your ControlNet data input file when new data is received Process control sample complete can be dynamically enabled and disabled by your program during a program scan This can be done by setting and clearing the PCSC enable bit of the connection s entry in the ControlNet status file After this bit has been set the input data should not be read until the PCSC new data bit has been set by the processor 3 PCSC New Data This bit is set by the processor when the PCSC enable bit is set to one and new data has been copied to the ControlNet data input file To insure that you do not access this data while the processor is copying new data to the data
59. a rack with the correct number of slots 273 0x0111 INVALID RPI The target node cannot produce the Increase the requested packet data at or faster than the requested interval RPI entered in the map packet interval RPI entered in the table map table 275 0x0113 OUT OF CONNECTIONS The maximum number of Reduce the number of 1 0 connections to from this node has connections MSG instructions or been exceeded CIO instructions to from this node 276 0x0114 PRODUCT CODE MISMATCH The target node module does not Replace the target node module match the node module entered in with the correct node module the map table 277 0x0115 PRODUCT TYPE MISMATCH Correct the 1 0 map table 278 0x0116 REVISION MISMATCH The series revision of the target Replace the target node module node module does not match the series revision entered in the map table with the correct node module Correct the 1 0 map table 1785 UM022C EN P February 2008 D 6 ControlNet 1 0 Map Entry Status Words and Error Codes Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 279 0x0117 INVALID CONNECTION POINT The PLC 5C is requesting data from Change the PLC 5C I 0 map entry to a ControlLogix tag that does not use the correct tag exist Change or add the tag to the ControlLogix processor The PLC 5C does not support Verify that the PLC 5C is a Series F C
60. ace mode 22 7 0 Toggle bits 22 15 8 Channel status see following table 23 7 0 Media bits see following table 23 15 8 Keeper State 24 Reserved 25 39 Current number of open scheduled connections 40 always less than or equal to the number in Word 41 Current number of configured scheduled connections 41 Accumulated number of scheduled connection timeouts 42 Current number of active MSG instructions 43 always less than or equal to 32 Maximum number of simultaneously active MSG instructions 44 always less than or equal to 32 Accumulated number of MSG connection timeouts 45 Current number of active 1771 CIO instructions 46 always less than or equal to 32 Maximum number of simultaneously active 1771 CIO instructions 47 always less than or equal to 32 Accumulated number of 1771 CIO connection timeouts 48 Current number of active 1794 and CIP CIO instructions 49 always less than or equal to 8 Maximum number of simultaneously active 1794 and CIP CIO 50 instructions always less than or equal to 8 Accumulated number of 1794 and CIP CIO connection timeouts 51 Current number of open target Message Router connections 52 always less than or equal to 32 F3 1 Field Names File Offset word bits Maximum number of simultaneously open target Message 53 Router connections always less than or equal to 32 Accumulated number of target Message Router connection 54 timeouts Current number of used u
61. ansfers Immediate Data Input and Immediate Data Output IDO perform similarly to the Remote I O supported immediate I O transfers Immediate Input 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 Immediate Data Transfer Private Data Memory Table Buffers Data Update Files S c e 3 3 2 iA 3 ControlNet Data Transfer Program Scan m u p Scheduled Data Transfer DNE p Unscheduled Data Transfer Planning to Use Your ControlNet PLC 5 Processor 2 9 Table 2 C ControlNet Immediate Data Transfer Operations Instructions Description Immediate l 0 ControlNet and Remote 1 0 001 001 MOT In the case of an IIN the most recent copy of the specified input word secured in the last discrete 1 0 data transfer from the corresponding 1 0 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 1 0 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
62. apping 2 20 non redundant media 1 17 NUI P 2 2 5 NUT P 3 0 Option to Close Communication 4 3 owner definition of P 3 Publication 1785 UM022C EN P February 2008 6 Index P PCMCIA Communication Card 2 31 PCSC 2 9 considerations 2 11 PCSC enable bit 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 1 processor status file B 1 layout B 1 processor resident local 1 0 2 16 processors ControlNet PLC 5 programmable controllers P 1 programming a processor through Channel 0 1 20 programming software 3 1 programming terminal connecting 1 19 publications ControlNet cabling 1 25 ControlNet system 1 18 rack control bits racks 07 B 12 racks 1017 B 13 recovery fault codes 200 and 201 4 9 redundant media 1 17 definition of P 3 redundant media example 2 32 related ControlNet publications P 4 related PLC 5 publications P 4 Publication 1785 UM022C EN P February 2008 remote 1 0 cable lengths 1 13 nonControlNet 2 17 remote 1 0 status indicators 5 5 remote 1 0 immediate 1 0 transfers 2 8 4 8 repeater definition of P 3 replacing a non ControlNet remote 1 0 network with a Co
63. ary 2008 Chapter 4 Programming Your ControlNet System Using This Chapter Topic Page ControlNet message instructions 4 1 ControlNet 1 0 transfer instructions 4 3 ControlNet immediate data input and output instructions 4 6 Using Selectable Timed Interrupts STIs in a program on a 4 9 ControlNet network Recovering from Major Fault Codes 200 and 201 4 9 Using ControlNet You can use the Message MSQ instruction and the MG data type to Message Instructions send message commands over the ControlNet system within the local ControlNet link e PLC 5 TYPED WRITE e PLC 5 TYPED READ e PLC 3 WORD RANGE READ e PLC 3 WORD RANGE WRITE e PLC 2UNPROTECTED READ e PLC 2UNPROTECTED WRITE Use your programming software to go to the instruction entry for message block screen If you want to Do this change the command Select one of the following type PLC 5 TYPED WRITE t0 select a write operation to another PLC 5 processor e PLC 5 TYPED READ t0 select a read operation from another PLC 5 processor e PLC 3 WORD RANGE READ to select a write operation to another PLC 3 processor e PLC 3 WORD RANGE WRITE t0 select a read operation from another PLC 3 processor PLC 2 UNPROTECTED READ to select a write operation to another PLC 2 processor e PLC 2 UNPROTECTED WRITE to select a read operation from another PLC 2 processor enter a PLC 5 data Type the PLC 5 data table address table address
64. ary 2008 Fault Codes This fault code Indicates this fault Take this corrective action 205 ControlNet configuration exceeds processor resources e Reduce the number of ControlNet I O map table IMPORTANT Scheduled connections will be closed You must cycle entries Possible ways to do this include power save with RSNetWorx or download the program to reopen using a discrete rack connection instead of the connections multiple discrete module connections Because the configuration software is unable to accurately predict all the combining multiple 1 0 racks into a single resources that the processor will require to execute your ControlNet 1 0 rack configuration software based on the relative loading on the processor this fault code is used if the processor determines that your putting peer to peer data in contiguous configuration typically when you accept Channel 2 edits exceeds the blocks in the data table so that less send processor s available bandwidth and receive scheduled messages are Typical causes of this error code include required receiving data from the ControlNet network faster than the ControlNet Increase your Network Update Time and or PLC 5 processor can parse it increase the Requested Packet Intervals for scheduled data transfers in your I O map table e performing 1 0 updates too frequently o berf rmingi diate ControlNet 1 0 ladder instru
65. ata type for these transfers CT has the following information e Command 1771 READ 1771 WRITE 1794 READ 1794 WRITE 1794 FAULT ACTION 1794 IDLE ACTION 1794 CONFIG DATA 1794 SAFE STATE DATA CIP GENERIC Generic bi directional 1747 READ INPUT 1747 WRITE OUTPUT 1747 READ MO FILE 1747 WRITE MO FILE 1747 READ M1 FILE 1747 WRITE M1 FILE 1747 SAFE STATE DATA 1747 WRITE FLAGS 1747 CONFIG DATA reads data from a 1771 non discrete 1 0 module writes data to a 1771 non discrete 1 0 module reads data from a 1794 1 0 module writes data to a 1794 1 0 module 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 changes a module s safe state data sends user specified CIP service sends user specified CIP service which requires reply data reads data from SLC 1 0 module input file writes data to SLC 1 0 module output file reads data from SLC 1 0 module MO file writes data to SLC 1 0 module MO file reads data from SLC 1 0 module M1 file writes data to SLC 1 0 module M1 file change SLC 1 0 module safe state data change action SLC 1 0 module take when it faults and or goes to idle change SLC module s configuration 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 forces a
66. ator Color Probable Cause Recommended Action Off Internal diagnostics failed 1 Turn power off make sure ControlNet address and L is not 00 reseat processor then power up A B 2 Clear memory and reload your program 3 Replace EEPROM with new program 4 error replace the processor No power Check power supply Steady Red Faulted unit Cycle power or reset unit If fault persists contact your Rockwell Automation representative or distributor Flashing Normal operation if processor is in No action required Green FLASH memory program mode Flashing The processor s ControlNet address Configure the ControlNet network so that UMAX is at Red Green is above UMAX least as high as the processor s ControlNet address Set the processor s ControlNet address at or below UMAX Alternating Self test No action required Red Green Alternating Incorrect node configuration Check network address and other ControlNet Red Off configuration parameters 1785 UM022C EN P February 2008 Indicator Color Probable Cause Recommended Action Off Channel disabled No action required A r B Configure for ControlNet communication Steady Normal operation No action required Green Flashing Temporary errors Make sure that the processor is connected to the Green Off ControlNet network with an Allen Bradley tap Check media for broken cables loose connectors missing terminators etc Flashing Media fault Make sure
67. ayed unless that information has been imported into the RSNetWorx project xc file Understanding the ControlNet System Software 3 3 Under these circumstances consider the following guidelines e 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 e if you must configure an intelligent module over ControlNet via program logic you must then upload the online network configuration in RSNetWorx software to synchronize the contents of the data table with the RSNetWorx project xc file This will ensure that the I O configuration utility applet will contain current information the next time it is launched Uploading and Downloading Software Projects Considering that both RSLogix 5 and RSNetWorx software can upload and download the ControlNet configuration information you must make sure that both the RSLogix 5 project rsp file and the RSNetWorx project xc file contain the same ControlNet configuration information For example if outdated ControINet configuration information is present in the RSLogix 5 project rsp file a download of the RSLogix 5 project may download ControNet configuration information that does not match the current ControlNet network There are two reasons why the RSLogix 5 project xc fil
68. between iterations of the ControlNet subsystem diagnostics When this value exceeds 2000 the processor may major fault with error code 205 See Appendix E Fault Codes 75 Maximum amount of time in milliseconds between iterations of the ControlNet subsystem diagnostics 5 76 Number of slots processor resident local rack 0 Illegal 1 4 slots 2 12 slots 3 8 slots 4 16 slots 5 77 Communication time slice for communication housekeeping functions in ms 5 78 MCP 1 0 update disable bits Bit 0 for MCP A Bit 1 for MCP B etc 79 S127 Processor Status File B 15 This word of the status file Stores 5 79 MCP inhibit bits Bit 0 for MCP A Bit 1 for MCP B etc 5 80 5 127 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 1785 UM022C EN P February 2008 B 16 Processor Status File Notes 1785 UM022C EN P February 2008 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 Control
69. bit s no parity e one stop bit e BCC error check e no handshaking 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 Channel 1A 3 pin dedicated DH D 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 e the distance and transmission rate are reduced to comply with RS 423 requirements D 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 1B pin default is remote 1 0 scanner configurable for e remote 1 0 scanner e remote 1 0 adapter e DH communication e unused 1785 UM022C EN P February 2008 1 4 Installing Your ControlNet PLC 5 Processor Figure 1 2 PLC 5 40C 5 46C and 5 80C Processors Front Panel Red Processor RUN FAULT Status Indicator Green Red Force Status Indicator Amber Channel 0 Communication ACTIVE FAULT Keyswitch selects processor mode gt ControlNet 1 0 Status Indicator Green Red
70. ble is corrupted Reenter the 1 0 map entry that is ADDRESS SIZE failing The target node of the MSG Edit the ladder program so that the instruction is not a processor or the correct target node is used target node of the CIO instruction is not the correct 1 0 adapter Replace the target node with the correct type of node 256 0x0100 CONNECTION IN USE The connection at the target node is No action is required The already in use connection can be re established after the target node times out the old connection 262 0x0106 CONNECTION USED BY OTHER The originating node attempted to Delete or inhibit any other node s NODE use a connection that is already connection so that the preferred being used by another node node can establish the connection A non discrete connection is setup Replace the target module with the to a discrete module correct non discrete module Correct the 1 0 map table 263 0x0107 CONNECTION NOT FOUND The connection at the target node Make sure 1 0 map entries exist in does not exist the 1 0 map tables of both the originating and target nodes 265 0x0109 INVALID CONNECTION SIZE The originating node requested a Correct the connection size in the connection size that the target node map table If it is a listen only cannot accommodate connection make sure that the connection size is not larger that the Size of the controlling connection Set the addressing mode switches of the 1771 rack dip correctly Use
71. cal 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 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 Four taps are available from Rockwell Automation Right angle Y tap O Important ControlNet taps contain passive electronics and must be purchased from Rockwell Automation for the network to function properly After terminating your segments you connect your node to the network __ 19 Nonredundant Media eae Redundant Media 25 2 I e E EB 1 B ese i a yan 1 Frre adc w ieee 1785 UM022C EN P February 2008 1 18 Installing Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 For detailed information about planning and installing your ControlNet system 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 In
72. ces to poll the network for active devices monitor station diagnostics 1 itis highly recommended that you declare an extended ControlNet diagnostic file 63 words using RSNetWorx This file will allow you to monitor for noise via ladder and HMI query to monitor the overall health of scheduled connections words 40 and 41 and to monitor ControlNet buffer usage For information about using these software packages see the online help systems for RSNetWorx for ControlNet and RSLogix5 software Appendix A Processor Specifications Backplane Current 1785 L20C15 2 7A Q 5Vdc 1785 L40C15 L46C15 L80C15 3 3A 5Vdc Heat Dissipation 1785 L20C15 54 BTU hour 1785 L40C15 L46C15 L80C15 59 BTU Rour Operating Temperature IEC 60068 2 1 Test Ad Operating Cold IEC 60068 2 2 Test Bd Operating Dry Heat IEC 60068 2 14 Test Nb Operating Thermal Shock 0 60 C 32 140 Storage Temperature IEC 60068 2 1 Test Ab Un packaged Non operating Cold IEC 60068 2 2 Test Bc Un packaged Non operating Dry Heat IEC 60068 2 14 Test Na Un packaged Non operating Thermal Shock 40 to 85 C 40 to 185 F Relative Humidity IEC 60068 2 30 Test Db Un packaged Non operating Damp Heat 5 95 non condensing Vibration IEC60068 2 6 Test Fc Operating 2g 10 500Hz Shock IEC60068 2 27 1987 Test Ea Unpackaged shock ES 002 Operating 30g Non operating 50g Emissions C
73. cheduled I O data transfer mechanism makes it possible to map 1747 modules For a complete list of these modules refer to RSNetWorx for ControlNet documentation 1794 Modules ControlNet 1794 FLEX discrete I O data transfer mapping requires one map table entry per node ControlNet 1794 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 map 1794 modules For a complete list of these modules refer to RSNetWorx for ControlNet documentation Using 1 0 Mapping Techniques Planning to Use Your ControlNet PLC 5 Processor 2 21 Other ControINet 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 F Peer to Peer Communications Mapping Message Type Description Valid Sizes Receive Data From Scheduled Message 1 240 words Send Data Scheduled Message RPI Default 4 x NUT To communicate between any ControlNet PLC 5 processors on the ControlNet network you can include MSG instructions in your ladder logic program See Chapter 4 and Appendix C for more information Discrete I O interfaced to a PLC 5 p
74. ctions t e Increase your ladder program scan by either m d immediate ControlNe adder instructions too adding more logic or by increasing the Tequenty Communications Time Slice S 77 Reduce the number or frequency of immediate See S 74 and S 75 for more information ControlNet 1 0 ladder instructions that are performed 206 This error code is reserved Contact your local Rockwell Automation representative if you get this message 207 This error code is reserved Contact your local Rockwell Automation representative if you get this message 208 Too many pending ControlNet 1 0 connections Delete one or more 1 0 map table entries and reaccept edits for the ControlNet configuration 230 System attempted transition to Run mode with processor in Invalid Change from the Invalid backup state to the No backup state Control backup state before transitioning into Run mode Refer to the Invalid backup state troubleshooting table later in this chapter 231 Bypassed qualification may occur during race condition when both Transition the PLC 5 processors into Run mode processors attempt to go into Run mode at the same time 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 Reconfigure the ControlNet channel 234 Failed Qualification Refer to the qualification major faults troubleshooting
75. d Personal computer Laptop computer with other serial device ISA based and with PCIC card PCI based 1784 PCC card PCMCIA based and your HMI or your HMI or and your HMI and your HMI or programming software programming software or programming software programming software PLC 5 40C 1784 PCC1 to PLC 5 NAP Y port or any other NAP port min 70 min Ld 2 za S za L Serial connection 5j 1770 15 4 choices P fl il ce Interface 1786 TPR EI EM 4 choices 4 choices 1786 TPR 1786 TPR ControlNet Network A B 5 E PLC 5 40C eee MR I 1 Mr 1 n as je jia jeee joes an a n wa e jeee SEE ALLEE T 1794 ACNR15 Flex 1 0 Adapter 1747 ACNR15 Adapter 1771 ACNR15 Adapter 1785 UM022C EN P February 2008 Planning to Use Your ControlNet PLC 5 Processor 2 33 WARNING When used in 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 If the master keeper drops off the network the next lowest numbered processor takes over as the master keeper No user intervention is required Important ControlN
76. d in the configuration applet is read and written to both the data table and the RSNetWorx project xc file The I O configuration data must be read and written to the RSNetWorx project xc file so that the user can download the I O configuration data from RSNetWorx software If the RSNetWorx project xc file was not updated with the I O configuration edits done within the I O configuration utility the edits would be lost when that RSNetWorx project file was downloaded You must configure the association to the RSNetWorx project xc file in RSLogix 5 software so that RSLogix 5 software knows which RSNetWorx project xc file to access the I O configuration information You can do this within the Controller Properties window in RSLogix 5 software If you don t use the I O configuration utility to edit or monitor ControINet scheduled connections the association to the RSNetWorx project xc file in RSLogix 5 software is unnecessary Certain circumstances can cause the data table configuration information to differ from what is stored in the RSNetWorx project xc file This can occur when program logic is used to modify the contents of the data table for purposes of reconfiguring a module via a path other than the I O configuration utility If such on the fly reconfiguration is necessary for your application consider that subsequently launching the I O configuration utility applet will result in outdated information being displ
77. d maximum node UMAX the maximum ControlNet node number that can transmit and receive unscheduled data unscheduled transfers non deterministic data transfers through ladder initiated communication or programming devices 1785 UM022C EN P February 2008 Preface 4 Related PLC 5 Publications Related ControlNet Publications 1785 UM022C EN P February 2008 The 1785 PLC 5 programmable controller and ControlNet documentation is organized into manuals according to the tasks that you perform Publication Publication Number Enhanced and Ethernet PLC 5 Programmable Controllers User 1785 6 5 12 Manual ControlNet Cable System Planning and Installation Manual 1785 6 2 1 1785 PLC 5 Programmable Controllers Quick Reference 1785 7 1 For more information about 1785 PLC 5 programmable controllers contact your local Rockwell Automation sales office or distributor To view or order these publications online visit www literature rockwellautomation com For detailed information about different aspects of planning and installing your ControlNet network see the following publications Publication Publication Number ControlNet Coax Cable System Planning and Installation Manual 1786 6 2 1 ControlNet Network Access Cable Installation Instructions 1786 2 6 ControlNet System Overview 50001 ControlNet PLC 5 Hot Backup System User Manual 1785 UM024 ControlNet Fiber Plannin
78. dy enabled Amber SFC and or 1 0 forces blinking present but not enabled Off SFC and or 1 0 forces not present COMM Off No transmission on Normal operation if channel 0 channel is not being used Green Transmission on Normal operation if blinking channel 0 channel is being used 1785 UM022C EN P February 2008 VO 5 3 Using the ControlNet The ControINet status indicators inform you of the operational state Status Indicators of the ControINet network Indicator Color Description Probable Cause Recommended Action VO Off ControlNet 1 0 not Normal operation if No action required present or not Channel 2 not being used operating OO Steady All nodes configured Normal operation No action required Green in the ControlNet map m L table present and operating properly A B Flashing At least one node Cable s or connector s Repair or replace cable s or Green Off configured for the broken or not connected connector s and reconnect ControlNet network not present or not Destination module s bad Repair or replace module s operating properly or missing Node s not on network Connect node to network Flashing All nodes configured Cable s or connector s Repair or replace cable s or Red Off for ControlNet not broken or not connected connector s and reconnect present or not operating properly Nodes not on network Connect nodes to network Indic
79. e Table 1 A e 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 6K bit s MORE For more information about designing trunk cable drop cable configurations see the Data Highway Data Highway Plus Data Highway Il Data Highway 485 Cable Installation Manual publication 1770 6 2 2 Installing Your ControlNet PLC 5 Processor 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 Liftthe locking bar and the ejector tab Ejector 2 Slide the processor into the left most slot of the Tab 1 0 chassis 3 Press down on the ejector tab and then close the locking bar over the processor To remove a processor from the chassis Save processor memory Remove power to the processor resident chassis 1 2 3 Disconnect all cables from the processor s ports 4 Liftthe locking bar and the ejector tab and then slide the processor from the chassis Install a remote I O link using 1770 CD cable and either a daisy chain or trunk cable drop cable configurat
80. e B 13 This word of the status file Stores 5 33 Rack control bits See also 5 7 5 27 5 32 5 34 5 35 e 33 0 7 V O rack inhibit bits for racks 10 17 e 33 8 15 1 0 rack reset bits for racks 10 17 5 34 Global status bits See also 5 7 5 27 5 32 5 33 and 5 35 e 34 0 7 fault bits for racks 20 27 octal e 34 8 15 unused 5 35 Rack control bits See also 5 7 5 27 5 32 5 33 5 34 e 5 35 0 7 1 0 rack inhibit bits for racks 20 27 e 35 8 15 1 0 rack reset bits for racks 20 27 Important Setting inhibit bits in the processor status file S 27 95 33 or 8 35 does not update inhibit bits in the I O status file 36 S 78 This word of Stores the status file 5 36 8 45 Reserved 46 PII program file number 5 47 PII module group 48 PII bit mask 5 49 PII compare value 50 PII down count 5 51 PII changed bit 5 52 PII events since last interrupt 5 53 STI scan time in ms 54 STI maximum scan time in ms 55 PII last scan time in ms 56 PII maximum scan time in ms 5 57 User program checksum 58 Reserved 5 59 Extended local 1 0 channel discrete transfer scan in ms 60 Extended local 1 0 channel discrete maximum scan in ms 5 61 Extended local 1 0 channel block transfer scan in ms 5 62 1 0 channel maximum block transfer scan in ms 5 63 Protected processor data
81. e contains ControlNet configuration information e RSNetWorx tool can only download to the entire ControlNet network For example in an application where a single ControlNet PLC 5 needs to have its program downloaded RSNetWorx software will attempt to download all nodes on the ControlNet network This will be time consuming and require that all ControlNet PLC 5 processors on the ControlNet network be placed in PROGRAM mode e the RSLogix 5 software download can download everything to a ControlNet PLC 5 in a single download If the ControlNet configuration information was not contained within the RSLogix 5 project both an RSLogix 5 project download and an RSNetWorx project download would be required Verify that ControlNet PLC 5 Configuration Matches Network Information To make sure that the ControINet configuration information downloaded to the ControlNet PLC 5 processor matches the current ControlNet network information follow one of these procedures 1785 UM022C EN P February 2008 3 4 Understanding the ControlNet System Software 1785 UM022CEN P February 2008 Download from both RSNetWorx and RSLogix 5 software You can download the ControlNet configuration information from RSNetWorx software and the remaining controller information from RSLogix 5 software When downloading the project from RSLogix 5 software a dialog box appears and asks whether the ControlNet configuration information stored in the RSLogix 5 project sh
82. e out if you cycle power in RUN mode If this happens the CIO error bit is set To reset the error bit the CIO instruction rung condition must go from FALSE to TRUE See Chapter 4 and Appendices C and F for more information 1785 UM022C EN P February 2008 Planning to Use Your ControlNet PLC 5 Processor Operation Peer to peer Messaging MSG Instructions Description 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 The MG data type for the ControlNet instruction has the following information Command PLC 5 TYPED READ PLC 5 TYPED WRITE PLC 3 WORD RANGE READ PLC 3 WORD RANGE WRITE PLC 2 UNPROTECTED READ PLC 2 UNPROTECTED WRITE Data table address in source processor Size of message in elements e Network address of destination processor Data table address in destination processor Port number set to 2 for the ControlNet network Flags forces a message to time out EW indicates that the message is waiting for an open connection CO message is sent continuously in Run mode ER indicates that the message was terminated due to an error DN indicates that the message was sent without error ST indicates that the message was started EN indicates that the message instruction is enabled NC forces the connection to close when the message is done
83. ecifies 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 Using Selectable Timed Interrupts with a Program on a ControlNet Network on page 4 9 IDO IMMEDIATE DATA OUTPUT Data file offset 175 Length 24 Source N12 175 Data Table Private DOF Buffer N12 0 0 N12 175 175 a i IDO instruction Outputs transmitted copies from the to the ControlNet data table to the network on next private opportunity DOF buffer For more detailed information about writing ladder programs and programming ControlNet I O transfers using Immediate Input IIN and Immediate Output IOT instructions see your programming software documentation 1785 UM022C EN P February 2008 Using Selectable Timed Interrupts with a Program on a ControlNet Network Recovering from Major Fault 200 and 201 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 If an STI occurs while a normal ControlNet non discrete I O data transfer or a ControlNet Immediate Data I O instruction IDO or
84. ed ethe distance and transmission rate are reduced to comply with RS 423 requirements 1785 UM022C EN P February 2008 Installing Your ControlNet PLC 5 Processor 1 5 Before You Install the Before installing your ControlNet PLC 5 processor Programmable Controller 1 Check your processor package and make sure that you have the following ControlNet PLC 59 Programmable Controller Processor 1785 L20C15 LA0C15 L46C15 or L80C15 Contents of Tray Lithium Battery 1770 XYC DIN connector cover Terminating resistors 82 3 pin connectors Keys Battery cover with screw 1784 CP7 cable adapter for 1784 CP CP5 cables Terminating resistors 1500 ControlNet PLC 5 Programmable Controllers Quick Documentation Start publication number 1785 10 6 Identified by four colored bands brown green brown and gold 7 Two with a PLC 5 20C processor four with PLC 5 40C 5 46C and 5 80C processors Identified by four colored bands gray red black and gold If any items are missing or incorrect contact your local Rockwell Automation sales office or distributor 2 Install and connect a chassis and power supply Use the following table to find more information about completing these tasks Chassis Type Chassis Document Power Supply Power Supply Document 1771 A1B A2B A3B A3B1 MB 1771 2 210 1771 P1 1771 2 6 1771 P2 1771 2 7 1771 P3
85. ed 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 Immediate Inhibit Bit PCSC Overflow Bit PCSC New Data Bit PCSC Enable Bit First Word 07 06 05 04 03 02 01 00 Reset Reserved Bit Data Invalid Bit Data Data Overrun Underrun Run Mode Reserved Inhibit Bit Connection Error Bit 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Error Messages 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 For critical 1 0 points always condition your logic with bits 8 and 9 of the first ControlNet status word 1785 UM022C EN P February 2008 D 2 ControlNet 1 0 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 Inhibit Bit Set this bit to perform an orderly shutdown of the associated connection If the target node is a Contr
86. ed to start an SFC subchart that is already running 72 The processor tried to stop an SFC subchart that isn t running 73 The processor tried to start more than the allowed number of subcharts 74 SFC file error detected 75 The SFC has too many active functions 76 SFC step loops back to itself 77 The SFC references a step transition subchart or SC file that is missing empty or too small 78 The processor cannot continue to run the SFC after power loss 79 You tried to download an SFC to a processor that cannot run SFCs 80 You have an 1 0 configuration error Recoverable 81 You illegally set an 1 0 chassis backplane switch by setting both switch 4 and 5 on 82 Illegal cartridge type for selected operation This error also occurs if the processor doesn t have a memory module but the backplane switches are set for a memory module Make sure the backplane switches are correct set switch 6 ON and switch 7 OFF if the processor doesn t have a memory module 1785 UM022C EN P February 2008 Processor Status File B 7 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 1 0 buffer too much data for the processor to process If
87. emote 1 0 and Transmission Rate 57 6K bit s DH 115 2K bit s 230 4K bit s 1 0 Scan Time Typical 10 ms per rack 57 6K bit s 7 ms per rack 115 2K bit s 3 ms per rack 230K bit s Maximum Number of Remote 1 0 Racks 3 15 15 23 Maximum Number of Remote 1 0 Devices 12 60 60 92 Number of Ports Configurable for DH or Remote 1 0 1 2 2 2 Adapter or Scanner Number of Dedicated DH Ports 1 0 0 0 Number of Serial Ports 1 Number of Coprocessor Ports 1 Maximum Number of MCPs 16 The PLC 5 40C15 and 5 46C15 processors have a limit of 32K words per data table file The PLC 5 80C15 processor has a limit of 56K words per program file and 32 K words per data table file The PLC 5 80C processor has 64K words of total data 2 table space 3 For more information see the ControlNet Cable System Planning and Installation Manual publication 1786 6 2 1 1785 UM022C EN P February 2008 The following information applies when operating this equipment in hazardous locations 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 When combining products within a system the most adverse temperature code lowest T number may be used to help determine the overall temperature code of the system Combinations of equip
88. essor memory protection disabled ON Processor memory protection enabled D Regardless of this switch setting outputs are turned off when any of the following occurs processor detects a runtime error 1 0 chassis backplane fault occurs e you select Program or Test mode e 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 bit S 11 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 1785 UM022C EN P February 2008 1 10 Installing Your ControlNet PLC 5 Processor Setting the 1 0 Chassis Configuration Plug Set the I O chassis configuration plug as follows Y N 4 1 Locate the chassis configuration plug Q y between the two left most slots of the chassis 1 2 Set the 1 0 chassis configuration plug USINGA foe a I POW
89. et PLC 5 programmable controllers with firmware revision E B D C or C L are single keeper devices later releases are distributed keeper devices There are two rules you must follow when combining single keeper devices and distributed keeper devices on the same network e if there is a single keeper device at node 1 there can be no distributed keeper devices on the network e if there are distributed keeper devices on the network single keeper devices can also be allowed on the network However there cannot be a single keeper device at node 1 If you plan to have distributed keeper devices on the network we recommend that you flash upgrade the single keeper devices to be distributed keeper devices 1785 UM022C EN P February 2008 2 34 Converting from a Non ControlNet Remote 1 0 System to ControlNet 1 0 System Program files for this process Messaging and 1 0 Planning to Use Your ControlNet PLC 5 Processor 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 The software sets Channel 2 to the default ControlNet configuration Can be run on a ControlNet Archived from a On channel PLC 5 channel e PLC 5 11 e PLC 5 40L 0 0 e PLC 5 20 e PLC 5 60 e PLC 5 20C15 PLC
90. ete 1 0 Data Transfer Mapping 2 19 T771 MOUUBS uia na rero rap dene hoe eme dei 2 20 W747 MOJU S SR PIPER DUE Rud 2 20 1794 Modules 2 20 Other ControlNet Processors 2 21 Using 1 0 Mapping Techniques 2 21 Understanding Discrete 2 22 Optimizing the I O Image Table 2 23 Optimizing the 1 0 Image Table without Slot Complementary 2 23 SUMMA E TETTE TS TET ETT EQUOS 2 29 Using the ControlNet PLC 5 Processor in a ControlNet 1 0 System 2 31 Distributed Keeper 2 33 Converting from a Non ControlNet Remote 1 0 System to a ControlNet 1 0 System 2 34 Converting from ControlNet Phase 1 0 or 1 25 to ControlNet Phase 1 5 2 35 Understanding the ControlNet Chapter 3 System Software Configuring and Programming Your ControlNet System 3 1 Using ControlNet Message Instructions 3 1 I O Configuration Utility 3 2 Uploading and Downloading Software Projects 3 3 Using RSNetWorx to Perform Verification Activities 3 4 For More Information ud uuo irrite vere Dur inie 3 5 1785 UM022C EN P February 2008 Programming Your ControlNet System
91. etween logic scans i e during housekeeping Scheduled data transfer occurs between the PLC 5 and the adapter module in the 1 0 chassis Data may stay in the private memory buffer for up to 1 API o Output data is written from a private memory buffer on the adapter to the module The output data stays in the private memory buffer for as long as it takes the 1 0 chassis backplane update to occur Logic Scan Data Table Files Housekeeping Program Scan Data Update PLC 5 Programmable Controller 1785 UM022C EN P February 2008 i In the same manner i the 1 0 adapter has Male Scheduled Data scheduled Vo data Memory transfer Memory Data Update ith VO Buffers Buffers transfer with 1 modules Adapter Module VO Modules 1 0 Chassis In scheduled 1 0 data transfer updates occur between logic scans i e during housekeeping Input data from the private memory buffer is put Planning to Use Your ControlNet PLC 5 Processor 2 3 What Happens During Scheduled Input Data Transfer PLC 5 Programmable Controller Logic Scan Data Table Files Housekeeping Data Update Private Memory Buffers into the input image file New input data may stay in the private memory buffer up to 1 program scan or until the next housekeeping
92. f the fault before clearing it For example if a major fault is encountered that causes bit S 11 2 to be set which indicates a programming error do not use a routine to clear the fault until you correct your program The processor stores fault codes in word 12 of the processor status file S 12 The following table lists new major fault codes specific to the ControlNet processor This fault code Indicates this fault Take this corrective action 200 ControlNet scheduled output data missed Check your network for missing terminators or The processor is unable to transmit the scheduled data itis configured to other sources of electrical noise see the Industrial transmit Automation Wiring and Grounding Guidelines publication 1770 4 1 201 ControlNet input data missed Check your network for missing terminators or The processor is unable to process incoming data from the network other sources of electrical noise see the Industrial Automation Wiring and Grounding Guidelines publication 1770 4 1 202 This error code is reserved Contact your local Rockwell Automation representative if you get this message 203 This error code is reserved Contact your local Rockwell Automation representative if you get this message 204 Too many output connections per NUI Make scheduled outputs with short Requested Packet Intervals longer and reaccept edits for the ControlNet configuration 1785 UM022C EN P Febru
93. ff 32 on off on off off on 72 on off on off off off 33 off off on off off on 73 off off on off off off 34 on on off off off on 74 on on off off off off 35 off on off off off on 75 off on off off off off 36 on off off off off on 76 on off off off off off 37 off off off off off on 77 off off off off off off 1785 UM022C EN P February 2008 1 12 Installing Your ControlNet PLC 5 Processor Specifying the Serial Specify RS 232C RS 422A or RS 423 communication for Channel Interface of Channel 0 0 by setting the switches of assembly SW2 Bottom View of PLC 5 20C Processor Bottom View of PLC 5 40C 5 46C 5 80C Processor Switch Assembly SW2 Switch Assembly SW2 T QOOOOOQOO OOOOQOO O Front of processor OOQO GOOGOGOQGG Front of processor H OOO BEEBBBHERH OOOO EHHEHEEHEEH OO OOOO 1 23 4 5 6 7 8 9 10 1 2 3 4 5 6 7 8 9 10 Set Switches To Specify pn 1 2 3 4 5 6 7 8 9 10 Toggle pushed ON ON ON OFF OFF ON
94. for 1747 SAFE STATE DATA e 1for 1747 WRITE FLAGS 1 to 138 for 1747 CONFIG DATA enter the destination network address Type a number from 1 to 99 enter the destination slot number Type the number of the slot that holds the 1 0 device number from 0 to 15 1 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 accommodate up to 64 words 1785 UM022C EN P February 2008 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 DLEN Done length word word 3 FILE Transfer file number word 4 ELEM Transfer element number word 5 DATA 0 through DATA 15 Remaining words words 6 through 21 The CIP Generic and Generic Bi directional CIO command types allow you to enter any possible CIP command over the ControlNet network This allows the processor to send commands to devices not listed in the command type list or to send special CIP commands to devices Use of these command types requires specific details of the device to wh
95. ftware 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 Use the following software packages to configure and program your ControlNet system Use To RSNetWorx for ControlNet define ControlNet network parameters such as henceforth RSNetWorx network update time software media redundancy physical media configuration e maximum scheduled nodes e maximum unscheduled nodes e monitor 1 0 map entry status RSLogix 5 software enter user program files e create delete monitor data table files enter module configuration e enter channel 0 1A 1B and 3 configuration administer passwords and privileges RSLinx software provide the ControlNet network interfaces to poll the network for active devices monitor station diagnostics Additionally use e RSNetWorx software to configure the individual scheduled connections for the ControlNet PLC 5 RSNetWorx software creates a project xc file on your personal computer when you save the project RSNetWorx software writes to the Channel 2 configuration memory during an online save to the ControlNet PLC 5 e RSLogix 5 software to configure and program all other parameters within
96. fy during configuration Important If you want to force your discrete I O you must map it to the I O image table Non discrete I O Data Transfer Mapping ControlNet non discrete I O data can be stored in either the I O image table or the DIF DOF The ControlNet processor supports two distinct image files both are integer data table files that you specify e Data Input File DIF e 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 scan non discrete I O data asynchronously to the program scan Like discrete I O the data is presented synchronously to the processor and output buffers during housekeeping The DIF and DOF can be overlapped as in Figure 2 1 so that inputs from one device can be used as outputs to another device As a result of the overlap no ladder logic is required to copy the data If either the DIF or DOF size is greater than 1000 words then it will span multiple physical files The physical files comprising the DIF or DOF must be contiguous Figure 2 1 Data Input and Data Output Files N10 0 DIF N11 0 N10 999 DOF N11 249 N11 499 1785 UM022C EN P February 2008 2 20 Planning to Use Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 1771 Modules ControlNet 1771 discrete I
97. g Installation Guide CNET INOO1 Industrial Automation Wiring and Grounding Guidelines 1770 4 1 System Design for Control of Electrical Noise GMC RMO001 To view or order these publications online visit www literature rockwellautomation com or contact your local Rockwell Automation sales office or distributor Using This Chapter Installing Your ControlNet PLC 5 Processor Chapter 1 Topic 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 1 0 chassis backplane switches 1 11 Setting the 1 0 chassis configuration plug 1 10 Installing keying bands for the processor 1 10 Selecting the Data Highway Plus DH station address 1 11 of Channel 1A Specifying the serial interface for Channel 0 1 12 Selecting the ControlNet network address of Channel 2 1 12 Inserting removing the processor into from the 1 0 chassis 1 13 Installing a remote 1 0 link 1 13 Installing a DH link 1 15 Connecting to a ControlNet network 1 17 Connecting a programming terminal 1 19 Selecting appropriate cables 1 22 For detailed information about installing chassis and adapters see the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication 1785 6 5 12 1785 UM022C EN P February 2008 1 2 Installing Your ControlNet PLC 5 Processor
98. gative preset or accumulated value in a timer instruction Recoverable 35 You entered a negative time variable in a PID instruction 36 You entered an out of range setpoint in a PID instruction 37 You addressed an invalid module in a block transfer immediate input or immediate output instruction 38 You entered a RET instruction from a non subroutine file Non recoverable the fault routine will be 39 FOR instruction with missing NXT executed but cannot clear major fault bit 2 40 The control file is too small for the PID BTR BTW or MSG instruction Recoverable 1785 UM022C EN P February 2008 B 6 Processor Status File This fault code Indicates this fault And the fault is 41 NXT instruction with missing FOR Non recoverable 42 You tried to jump to a non existent label 43 File is not an SFC ROMPE 44 Error using SFR This error occurs if you tried to reset into a simultaneous path you specified a step reference number that is not found or is not tied to a step it is a transition the previous SFR to a different step is not complete 45 Invalid channel number entered Recoverable 46 Length operand of IDI or IDO instruction is greater than the maximum allowed 47 SFC action overlap An action was still active when the step became re activated Non recoverable 48 69 Reserved Recoverable 70 The processor detected duplicate labels 71 The processor tri
99. ght so that you don t have to waste any inputs or outputs passing over these modules This leads to the second important module placement rule of optimization 1785 UM022C EN P February 2008 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 Example 4 To understand how optimization with a ControlNet network preserves I O image space look at the following example system ACN 0 0 o PS 1 Discrete Input Module 0 Discrete Output Module Chassis 1 ACN ControlNet adapter A Analog Module PS Power Supply ACN 0 5 Chassis 2 ACN AJIA A AJA A PS Chassis 3 The following chart shows how a Remote I O system compares to one optimized with a ControlNet network Remote 1 0 ControlNet Network Input Output Input Output Chassis Address Size Address Size Address Size Address Size Total Used 24 3 racks 8 1 rack Remaining 0 16 2 racks 1785 UM022C EN P February 2008 If you install the system on a PLC 5 20C processor the Remote I O network option would be out of I O image space while the ControlNet network option would have used only one third of the available I O image space You must take into account future expansion when optimizing the I O Chassis 1 Chassis 2 Chassis 3 Pla
100. grammable controllers phase 1 5 connection opened communication path between two nodes on a ControlNet network DData Input File DIF integer file used by ControlNet PLC 5 processors to store discrete and non discrete input data The DIF cannot be forced Data Output File DOF integer file used by ControlNet PLC 5 processors to store discrete and non discrete output data The DOF cannot be forced discrete 1 0 data transfer type of data transfer in which single units of 1 0 have discrete relationships with values in the processor s data table uses the processor s input and output image tables and 0 files configured on a per node basis in the ControlNet 1 0 map table frame single data transfer on a ControlNet link drop cable cable that connects a ControlNet node to the trunk cable integral part of 1786 taps 1 0 map table table that you configure using the programming software to map data from an 1 0 chassis scanlist configuration and other devices on the ControlNet network to particular data table file addresses keeper device that stores and distributes ControlNet configuration data to all nodes on the network A minimum of one keeper device is required on each ControlNet network link collection of ControlNet nodes with unique network addresses in the range of 01 99 segments connected by repeaters make up a link links connected by bridges make up a network map table entry scanlist en
101. hanged in an area known to be non hazardous 1785 UM022C EN P February 2008 RISQUE D EXPLOSION AVERTISSMENT e Couper le courant ou s assurer que l environnement est class non dangereux avant de d brancher l quipement e Couper le courant ou s assurer que l environnement est class non dangereux avant de d brancher les connecteurs Fixer tous les connecteurs externes reli s cet quipe ment l aide de vis loquets coulissants connecteurs filet s ou autres moyens fournis avec ce produit e La substitution de composants peut rendre cet quipement inadapt une utilisation en environnement de Classe I Division 2 e S assurer que l environne ment est class non dangereux avant de changer les piles 0 5 2 Appendix B Processor Status File Processor statu s data is stored in data file 2 This word of Stores the status file 5 0 Arithmetic flags e bit 0 carry bit 1 overflow e bit 2 zero e bit 3 sign 1 Processor status and flags 5 1 00 RAM checksum is invalid at power up 5 1 01 Processor in run mode 1 02 Processor in test mode 1 03 Processor in program mode 1 04 Processor uploading to memory module 1 05 Processor in download mode 1 06 Processor has test edits enabled 1 07 Mode select switch in REMOTE position 1 08 Forces enabled 1 09 Forces present 1 10 Processor successfully uploaded t
102. he PLC 5 80C processor spanning four contiguous data table files This file is typically used for non discrete input data and peer to peer input Discrete input data may be mapped to DIF as well Data Output File DOF User specified integer data table file with a maximum of e 2000 words for the PLC 5 20C processor spanning two contiguous data table files e 3000 words for the PLC 5 40C processor spanning three contiguous data table files e 3000 words for the PLC 5 46C processor spanning three contiguous data table files e 4000 words for the PLC 5 80C processor spanning four contiguous data table files This file is typically used for non discrete output data and peer to peer output Discrete output data may be mapped to DOF as well Configuration File User specified integer data table file used to store non discrete 1 0 data transfer configuration data This configuration data is sent to the target device each time the connection is opened 1785 UM022C EN P February 2008 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 speci
103. ich the command is being sent For more detailed information about writing ladder programs see your programming software documentation Sending Continuous Messages If you use continuous mode message instructions do not toggle the rung condition unless the continuous message is done or errored Once enabled the continuous message will only stop under the following conditions e if a message error is detected e if you reset the message CO bit e if you set the TO status bit You can change the CO and TO bits through the message block configuration screen or with ladder logic 1785 UM022C EN P February 2008 4 6 Using ControlNet Immediate Data Input and Output Instructions 1785 UM022C EN P February 2008 1771 ControlNet Transfers in Plis 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 You can use two instructions for immediate data input and output on a ControlNet network Immediate Data Input IDI and Immediate Data Output IDO IDI IMMEDIATE DATA INPUT E Data file offset 232 Length 10 Destination N11 232 IDO IMMEDIATE DATA OUTPUT Data file offset 175 b Length 24
104. ies those products for information on their scheduled connection behavior Scheduled connection types made from the ControINet PLC 5 to I O adapters can be made either to some or all of the discrete I O on the adapter called a rack connection or to individual modules called a module connection 1785 UM022C EN P February 2008 2 12 Planning to Use Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 There are four general types of scheduled connections from the ControlNet PLC 5 to I O adapters e 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 e input only these scheduled connections only gather inputs from the I O adapters These scheduled connections do not require other scheduled connection types to be first established before its scheduled connection can be established e listen only these scheduled connections are similar to input only scheduled connections except that they require a different scheduled connection to be first established before its connection can be established redundant owner these scheduled connections are similar to exclusive owner scheduled connections because they both can control outputs and gather inputs The difference between them
105. iew 1786 2 9 ControlNet Fiber Planning and Installation Guide CNET IN001A EN P System Design for Control of Electrical Noise GMC RM001A EN P Industrial Automation Wiring and Grounding Guidelines 1770 4 1 Terminating Your ControlNet Coaxial Cable CNET DM001A EN C 1785 UM022C EN P February 2008 1 26 Installing Your ControlNet PLC 5 Processor Notes 1785 UM022C EN P February 2008 Using This Chapter Understanding ControlNet 1 0 Chapter 2 Planning to Use Your ControlNet PLC 5 Processor Topic Page Understanding ControlNet 1 0 2 1 Understanding Scheduled Connection Types 2 11 Understanding ControlNet 1 0 mapping 2 16 Using 1 0 Mapping Techniques 2 21 Using the ControlNet PLC 5 processor in a ControlNet 1 0 system 2 31 Converting from a non ControlNet remote 1 0 system to a 2 34 ControlNet 1 0 system Converting from ControlNet phase 1 0 or 1 25 to ControlNet 2 35 phase 1 5 To distinguish phase 1 5 ControlNet processors from earlier phase processors new catalog numbers were created for each of the phase 1 5 ControlNet processors 1785 L20C15 1785 L40C15 L46C15 and 1785 L80C15 You cannot mix phase 1 5 and earlier phase such as ATTENTION 1 0 and 1 25 products on the same ControlNet network The ControlNet system is designed to e provide high speed repeatable deterministic I O transmission e allow control and message information to co exist on the same physical media e
106. igure the ControlNet channel 234 Failed Qualification Refer to the qualification major faults troubleshooting table later in this chapter 235 Illegal invalid backup state Cycle power to the processor If the fault reoccurs contact Rockwell Automation Technical Support at 440 646 6800 236 Illegal No Control backup state Cycle power to the processor If the fault reoccurs contact Rockwell Automation Technical Support at 440 646 6800 237 Illegal Primary Secondary backup state Cycle power to the processor If the fault reoccurs contact Rockwell Automation Technical Support at 440 646 6800 238 Incompatible firmware revisions Install the same series and revision of firmware into both hot backup PLC 5 processors 239 ControlNet keeper mismatch Use RSNetworx to make the PLC 5 processor a valid keeper 1785 UM022C EN P February 2008 13 S 24 Processor Status File B 11 This word of the status file Stores 5 13 Program file where fault occurred 5 14 Rung number where fault occurred 5 15 VME status file 5 16 1 0 status File 5 17 Minor fault word 2 See also 5 10 17 00 BT queue full to remote 1 0 17 01 Queue full channel 1A maximum remote block transfers used 17 02 Queue full channel 1B maximum remote block transfers used 17 03 Queue full channel 2A maxi
107. ill not modify the new data and overflow bits while you clear them 2 Clear the PCSC new data and the PCSC overflow bits 3 Re enable process control sample complete by setting the connection s PCSC enable bit back to one Considerations When Using PCSC When using scheduled ControlNet 1 5 communications to analog I O such as map entries and you are using the PID instruction in the PLC 5 15 then you should do the following e the analog module must be set up to use RTS Real Time Sample mode e set your analog RPI Repetitive Packet Interval to be at least twice the RTS time e your ladder program needs to set the PCSC enable bit e your ladder program needs to use the PCSC done bit to condition the execution of the PID instruction e the PID loop update must equal RTS rate e your ladder program must use the PCSC overflow bit to take appropriate action on an overflow condition Scheduled connections are made to I O devices such as I O adapters and to peer to peer devices such as other controllers There are some common scheduled connection types made from the ControlNet PLC 5 to other Allen Bradley products that are detailed in the following section These scheduled connection types have certain behaviors and limitations that you must understand before configuring the connections The ControlNet PLC 5 can also make scheduled connections to products not manufactured by Allen Bradley Refer to the literature that accompan
108. in the module type correct slot of the target node An incorrect module or slot was Edit the 1 0 map table to show the entered in the map table correct module type and slot 65533 OxFFFD DATA TABLE TOO SMALL The processor data table is too small Increase the size of the data table to to hold the data to be transferred accommodate the transfer length 1785 UM022C EN P February 2008 ControlNet 1 0 Map Entry Status Words and Error Codes D 11 Notes 1785 UM022C EN P February 2008 D 12 ControlNet 1 0 Map Entry Status Words and Error Codes 1785 UM022C EN P February 2008 Clearing Faults Additional Major Fault Codes Fault Codes Appendix E Fault routines execute when a PLC 5 processor encounters a run time error major fault during program execution 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 Fault routines provide a means to either e systematically shut down a process or control operation e log and clear the fault and continue normal operation For more information about fault routines see Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication 1785 6 5 12 When a major fault occurs you need to clear faults before your process can continue ATTENTION Clearinga major fault does not correct the cause of the fault Be sure to examine the fault bit and correct the cause o
109. ing 5 1 5 3 status words 1 0 map entry D 1 T tap 1 21 connecting 1 17 definition of P 3 using 1 17 terminator Index 7 definition of P 3 troubleshooting ControlNet system 5 1 trunk cable definition of P 3 trunkcable section P 3 U UMAX definition P 3 Unscheduled Data Transfer definition 2 4 unscheduled data transfer operations 2 4 unscheduled maximum node definition P 3 unscheduled non discrete 1 0 data transfer 2 4 unscheduled transfers definition of P 3 upload download software projects 3 3 user control bits processor status file B 12 using ControlNet 1 0 Transfer CIO instructions 4 3 using ControlNet Immediate Data 1 0 instructions 4 6 using ControlNet Message MSG instructions 1 using the ControINet status indicators 5 3 using the general status indicators 5 1 using this manual conventions used P 4 intended audience for P 1 introduction to P 1 recommended preparation for P 1 V verification acitivities 3 4 verify keeper signature 3 4 verify scanner signature 3 4 Publication 1785 UM022C EN P February 2008 8 Index Publication 1785 UM022C EN P February 2008 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 or fax it back to us or email us at RADocumentComments ra rockwell com Pub Title Type ControlNet PLC 5 Programmable Controllers Cat
110. instruct 11 Bad user program checksum the processor to clear the Bad i fi fault and then resume 12 ad integer operand type restore new processor memory file scanning the program 13 Bad mixed mode operation type restore new processor memory file A fault routine executes 14 Not enough operands for instruction restore new processor memory file when any of these faults occur 15 Too many operands for instructions restore new processor memory file 16 Corrupted instruction probably due to restoring an incompatible processor memory file bad opcode 17 Can t find expression end restore new processor memory file 18 Missing end of edit zone restore new processor memory file 19 Download aborted 20 You entered too large an element number in an indirect address 21 You entered a negative element number in an indirect address 22 You tried to access a non existent program file 23 You used a negative file number you used a file number greater than the number of existing files or you tried to indirectly address files 0 1 or 2 24 You tried to indirectly address a file of the wrong type Recoverable 30 You tried to jump to one too many nested subroutine files Non recoverable E the fault routine will be 31 You did not enter enough subroutine parameters executed but cannot clear major fault bit 2 32 You jumped to an invalid non ladder file jor fault h 33 You entered a CAR routine file that is not 68000 code 34 You entered a ne
111. ion Verify that your system s 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 1 0 link using this communication rate Cannot exceed this cable length 57 6K bit s 3 048 m approximately 10 000 ft 115 2K bit s 230 4K bit s 1 524 m approximately 5 000 ft 762 m approximately 2 500 ft 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 1502 or 82Q terminator 1785 UM022C EN P February 2008 Installing Your ControlNet PLC 5 Processor The maximum number of logical rack Use this physical devices numbers that you resistor thatyoucanconnect can scan on the If your remote 1 0 link rating on the link is link is 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 820 32 16 6008 SQH1 SQH2 Adapters 1771 AS 1771 ASB Series A Only 1771 DCM Miscellaneous 1771 AF Connects to any device listed below Scanners 1771 SN 1772 SD SD2 1775 SR S4A S4B 6008 SQH1 SQH2 1500 16 16 Adapters 1771 AS 1771 ASB Series A Only 1771 DCM Miscellaneous 1771 AF
112. ional when shipped from the manufacturing facility However if your product is not functioning and needs to be returned follow these procedures United States Contact your distributor You must provide a Customer Support case number call the phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for the States return procedure Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1785 UM022C EN P February 2008 Supersedes Publication 1785 UM022B EN P February 2002 Copyright 2008 Rockwell Automation Inc All rights reserved Printed in the U S A
113. ir immediate inhibit bit set After the immediate inhibit takes place you may independently re enable each connection by clearing this bit ControlNet I O Status file Reset Bit all connections of a Scanner to Target Multicast ID group must have this bit set or cleared so that the target devices are put into the correct state The Reset Bit affects all connections for a given multicast ID group 1785 UM022C EN P February 2008 2 16 Planning to Use Your ControlNet PLC 5 Processor Understanding ControlNet 1 0 Mapping 1785 UM022C EN P February 2008 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 The map table is stored in the configuration section of memory and is not accessible by your application program Using your programming software you can automatically configure and map nodes attached to your ControlNet I O See Using I O Mapping Techniques in Chapter 2 for information about ControlNet automatic configuration and I O mapping Reserving Space for Non ControlNet 1 0 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
114. is that with redundant owner scheduled connections multiple ControlNet PLC 5 controllers can establish identical redundant connections Only one of the controllers that establish the redundant scheduled connection will own the outputs Redundant connections can only be used in a PLC 5 ControlNet Hot Backup system Refer to the PLC 5 ControlNet Hot Backup User Manual publication 1785 6 5 24 for more information on using redundant connections Allowable Scheduled Connection Type Combinations for I O Adapter Connections Only specific combinations of scheduled connection types are allowable RSNetWorx software will have a pull down list showing all allowable schedule connection types The following details about these combinations assume that different processors are making either rack connections to the same adapter or module connections to the same slot Important The 1771 ACN R15 requires a rack connection to be established before any module connections are accepted If an exclusive owner connection is made to the adapter e another exclusive owner connection will be rejected e aninput only connection can be made alisten only connection can be made e a redundant owner connection will be rejected Planning to Use Your ControlNet PLC 5 Processor 2 13 If an input only connection is made to the adapter e anexclusive owner connection can be made e another input only connection can be made alisten only connection can be made
115. ith RSNetWorx The ControlNet network was formed by joining two existing ControlNet networks Reconfigure the new ControlNet network by enabling and accepting edits with RSNetWorx 1785 UM022C EN P February 2008 D 8 ControlNet 1 0 Map Entry Status Words and Error Codes Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 774 0 0306 KEEPER NOT AVAILABLE The ControlNet cable from the Fix and or reconnect the ControlNet originating node to the keeper is cable broken or disconnected The keeper is not powered Supply power to at least one ControlNet processor No keeper exists on the ControlNet Add at least one ContolNet network processor to the network Reconfigure the ControlNet network by enabling and accepting edits with RSNetWorx 789 0x0315 INVALID PATH SEGMENT TYPE The map table is corrupted Reenter the 1 0 map entry that is failing The target node of the CIO Edit the ladder program so that the instruction is not the correct 1 0 correct target node is used adapter Replace the target node with the correct adapter 791 0x0317 INVALID SCHEDULE DATA The ControlNet cable from the Fix and or reconnect the ControlNet originating node to the programming cable and reconfigure the ControlNet terminal was broken or network disconnected when the ControlNet network was configured The originating node was not Supply power
116. its equip ment or software described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Auto mation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you identify a hazard avoid a hazard and recognize the consequence INA away Labels may be on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present PETE vam Labels may be on or inside the equipment for example a drive or motor to alert people that surfaces may reach dangerous temperatures Allen Bradley ControlLogix Data Highway Plus DH FLEX I O PLC 2 PLC 3 PLC 5 Rockwell Automation RSLinx RSLogix RSLogix 5000 RSLogix 5 RSNetWorx RSNetworx for ControlNet SLC and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their res
117. lanation Possible Cause s Possible Corrective Action s Code 65530 OxFFFA MODULE DECLARED INVALID A communication error between the Make sure that the module is LENGTH adapter and the module caused the properly seated in the correct slot of transfer to be aborted the target node Make sure that the adapter s power supply is providing the proper voltage The target slot contains the wrong Insert the proper module in the module type correct slot of the target node An incorrect module or slot was Edit the 1 0 map table to show the entered in the map table correct module type and slot 65531 OxFFFB INVALID READ DATA A communication error between the Make sure that the module is adapter and the module caused the properly seated in the correct slot of transfer to be aborted the target node Make sure that the adapter s power supply is providing the proper voltage The target slot contains the wrong Insert the proper module in the module type correct slot of the target node An incorrect module or slot was Edit the 1 0 map table to show the entered in the map table correct module type and slot 65532 OxFFFC INVALID WRITE DATA A communication error between the Make sure that the module is adapter and the module caused the properly seated in the correct slot of transfer to be aborted the target node Make sure that the adapter s power supply is providing the proper voltage The target slot contains the wrong Insert the proper module
118. later During the save operation RSNetWorx software gives you two options Optimize schedule for all connections RSNetWorx software recalculates the ControINet schedule for all the nodes on the ControlNet network The new schedule is downloaded to all the processors The processors close all of their existing connections and then reopen their connections according to the new schedule This option requires that all the processors be in Program mode Merge changes into existing schedule RSNetWorx software merges the pending changes into the current ControINet schedule The new schedule is only downloaded to those processors that are affected by the change Only those processors that are affected by the change have to be in Program mode other processors on the network can remain in Run mode and their connections remain open This option is only available if the current schedule can accommodate the pending changes and if the ControlNet network parameters such as NUT maximum scheduled address maximum unscheduled address or media redundancy do not change Important Performing a download via RSNetWorx software may require all the processors to be in Program mode For more information about using these software packages see the online help systems included with RSNetWorx for ControlNet and RSLogix 5 software 1785 UM022C EN P February 2008 3 6 Understanding the ControlNet System Software Notes 1785 UM022CEN P Febru
119. lue as the first input parameter of the instruction Any other input parameters are ignored even if you have an SBR instruction at the beginning of your fault routine file You cannot pass parameters to the fault routine file using JSR SBR instructions You do not have to use the user defined fault codes to generate your own fault If you program a JSR with no input parameters the processor will write a zero to the Fault Code field The purpose of using the user defined fault codes is to allow you to distinguish among different types of faults or error codes based on the 0 9 fault code numbers When the input condition is true the processor copies the fault code number entered as the first input parameter of the JSR instruction into word 12 of the processor status file S 12 which is the Fault Code field The processor sets a Major Fault S 11 7 User Generated Fault The processor then faults unless you clear the Major Fault word S 11 or the specific fault bit via ladder logic in the fault routine the fault routine can instruct the processor to clear the fault and then resume scanning the program A fault routine executes when any of these faults occur 1785 UM022C EN P February 2008 Processor Status File B 5 This fault code Indicates this fault And the fault is 10 Run time data table check failed Recoverable the fault routine can
120. make sure that I O data transfers are not affected by programming terminal message activity inter PLC processor message activity on the network 1785 UM022C EN P February 2008 2 2 Planning to Use Your ControlNet PLC 5 Processor Scheduled Data Transfer Operations on a ControlNet Network ControlNet scheduled data transfer on ControINet PLC 5 processor e 15 continuous e 15 asynchronous to the ladder logic program scan e occurs at the actual rate displayed in the Actual Packet Interval APD field on the programming software scanlist configuration screen in RSNetWorx for ControlNet software Important The Requested Packet Interval RPI rate requested for a connection establishes the data transfer rate on the ControINet network API is determined by RSNetWorx software when the schedule is built The API will always be the same or less than the RPI The API does not imply the actual I O throughput I O data is sent on the network every API regardless of whether the I O data has been refreshed with newer I O data I O throughput time may be slower due to delays caused by module update times processor scan times and adapter to I O module transfer times What Happens During Scheduled Output Data Transfer Data from the output image file is put into a private memory buffer New output data may stay in the data table files up to 1 program scan or until the next housekeeping In scheduled 1 0 data transfer updates occur b
121. map feature reserves the maximum size of inputs outputs It is up to you to manually change the sizes if desired If you optimize the chassis as shown the sizes adjust to the following Input file Input size Output file Output size 1 010 4 0 010 6 There are two input modules and four output modules in the chassis However you cannot set the sizes to two and four because the address you specify is the starting address of the chassis It identifies the address of the leftmost slot The size you specify determines how many slots in the chassis written to or read from In 1 slot addressing words equals slots The concept is the same for any addressing mode Words are read written from left to write In 1 2 slot addressing there are two words per slot In this example the first slot in the chassis is I 010 0 010 the second slot I 011 O 011 and so on The fifth slot is O 014 only You cannot place an input module in this slot since no input word is mapped to it The seventh slot has no I O image table mapped to it You cannot place a discrete input or output module in the last two slots since there is no I O image table allocated to it Example 2 Take another look at the chassis By moving the modules you can optimize this chassis further Move all the input modules to the left of the chassis ACN 0 0 0 0 X X Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter X Empty Slot
122. ment in your system are subject to investigation by the local Authority Having Jurisdiction at the time of installation Informations sur l utilisation de cet quipement en environnements dangereux Les produits marqu s CL I DIV 2 GP A B C D ne conviennent qu une utilisation en environnements de Classe I Division 2 Groupes A B C D dangereux et non dangereux Chaque produit est livr avec des marquages sur sa plaque d identification qui indiquent le code de temp rature pour les environnements dangereux Lorsque plusieurs produits sont combin s dans un syst me le code de temp rature le plus d favorable code de temp rature le plus faible peut tre utilis pour d terminer le code de temp rature global du syst me Les combinaisons d quipements dans le syst me sont sujettes inspection par les autorit s locales qualifi es au moment de l installation EXPLOSION HAZARD WARNING e Do not disconnect equipment unless power has been removed or the area is known to be nonhazardous e Do not disconnect connec tions to this equipment unless power has been removed or the area is known to be non hazardous Secure any external connections that mate to this equipment by using screws sliding latches threaded con nectors or other means pro vided with this product e Substitution of components may impair suitability for Class I Division 2 e If this product contains batter les they must only be c
123. ment of the sidecar module is an illegal value 106 Sidecar module transfer protection violation for PLC 5 26 5 46 and 5 86 processors only 200 ControlNet scheduled output data missed Recoverable The processor is unable to transmit the scheduled data it is configured to transmit Check your network for missing terminators or other sources of electrical noise see the Industrial Automation Wiring and Grounding Guidelines publication 1770 4 1 1785 UM022C EN P February 2008 This fault code 201 Processor Status File Indicates this fault ControlNet input data missed The processor is unable to process incoming data from the network And the fault is 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 203 ControlNet schedule transmit data overflow Recoverable Contact your local Rockwell Automation representative if you get this message 204 Too many output connections per NUI Recoverable Make scheduled outputs with short Requested Packet Intervals longer and reaccept edits for the ControlNet configuration 1785 UM022C EN P February 2008 Processor Status File B 9 This fault c
124. mization 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 e Device synchronization inputting data to all devices simultaneously improves synchronization between devices In the following example the ControlNet PLC 5 processor at node 2 is sending outputs to the adapter at node 3 Nodes 1 2 and 4 are all receiving the same input packet from node 3 Nodes 1 and 4 are considered listen only and are producing heartbeats to keep their connections to the adapter alive Heartbeat Connection ControlNet PLC 5 Processor Node 1 Point to Point Outputs ControlNet PLC 5 Processor Node 2 ControlNet Adapter Node 3 ControlNet PLC 5 Processor Node 4 1785 UM022C EN P February 2008 Multicast Inputs Understanding Multicast Outputs This feature enables the PLC 5 to simultaneously send the same output data to more that one target device To use this feature both the PLC 5 and the target devices must support multicast outputs Advantages of multicast outputs include e 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 e Device sy
125. mum remote block transfers used 17 04 Queue full channel 2B maximum remote block transfers used 17 05 No modem on serial port 17 06 e Remote 1 0 rack in local rack table or e Remote 1 0 rack is greater than the image size This fault can also be caused by the local rack if the local rack is set for octal density scan and the 1 0 image tables are smaller than 64 words 8 racks each 5 17 07 Firmware revision for channel pairs 1 1 or 2 2 does not match processor firmware revision 17 08 ASCII instruction error 5 17 09 Duplicate node address 5 17 10 DF1 master poll list error 5 17 11 Protected processor data table element violation 17 12 Protected processor file violation 17 13 Using all 32 ControlNet MSGs 17 14 Using all 32 ControlNet 1771 ClOs 17 15 Using all 8 1794 ControlNet FLEX 1 0 ClOs 5 18 Processor clock year 5 19 Processor clock month 5 20 Processor clock day 5 21 Processor clock hour 8 22 Processor clock minute 1785 UM022C EN P February 2008 B 12 Processor Status File 5 26 5 35 1785 UM022C EN P February 2008 This word of Stores the status file 5 23 Processor clock second 5 24 Indexed addressing offset 5 25 Reserved This word of Stores the status file 5 26 User control bits 5 26 00 Restart continuous SFC when reset processor restarts at first step SFC When set processor continues with active step after power loss or change to RUN
126. munication Your data table files and private buffers are synchronized during housekeeping which occurs between program scans During housekeeping the latest inputs are copied from the private memory buffers to the processor s input data table files file 1 and the DIF and the output data table files file 0 and the DOF are copied to the private output buffers In some instances however it is useful to have access to new input data as soon as it has been received without waiting for housekeeping to take place at the end of the program scan Process control sample complete enables you to do so for the following scheduled connection types e 1747 analog or module connection e 1771 analog or module connection e 1794 analog or module connection e receive scheduled message 1785 UM022C EN P February 2008 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 When process control sample complete is enabled for a connection and the processor is in RUN mode newly received data for that connection is immediately copied into your data table even if the processor is in the middle of a program scan and the PCSC new data bit is set in the connection s ControlNet I O status file entry This data will not be updated again during a program scan until you clear the PCSC new data bit The dat
127. n 1785 6 5 12 Note To monitor for ControlNet noise via ladder logic or HMI declare a ControlNet diagnostic file using RSNetWorx software Refer to Appendix F ControlNet Diagnostic File Layout for definitions You can also monitor for ControlNet noise via RSWho s station diagnostics in RSLinx 1785 UM022C EN P February 2008 4 10 Notes 1785 UM022C EN P February 2008 Using This Chapter Using the General Status Indicators BATT Ox PROC Chapter 5 Monitoring and Troubleshooting Your ControlNet System Topic Page Using the general status indicators 5 1 Using the ControlNet status indicators 5 3 Using the Data Highway Plus and Remote 1 0 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 Indicator Color Description Probable Cause Recommended Action BATT Red Battery low Battery low Replace battery within 10 days Off Battery is good Normal operation No action required FORCE COMM 1785 UM022C EN P February 2008 5 2 Indicator Color Description Probable Cause Recommended Action PROC Green Processor is in run Normal operation No action required steady mode and fully operational Green Processor memory is Normal operation No action required
128. n AG 5 4 Store batteries in a cool dry environment We recommend 25 C with 40 or 60 relative humidity You may store batteries up to 30 days between 45 85 C such as during transportation To avoid possible leakage do not ID store batteries above 60 C for more than 30 days 1785 UM022C EN P February 2008 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 Duration PLC 5 20C 60 C 173 days 346 days 70 hours 25 1 69 years 3 38 years 14 5 days PLC 5 40C 60 C 92 5 days 185 days 38 hours 25 1 25 years 2 5 years 10 8 days PLC 5 46C 60 C 92 5 days 185 days 38 hours 25 1 25 years 2 5 years 10 8 days PLC 5 80C 60 C 80 days 160 days 33 hours 25 1 18 years 2 36 years 10 days i 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 Dispose of a Battery If you need to dispose of a battery follow the procedures described in Guidelines for Handling Lithium Batteries pub no AG 5 4 Follow these precautions to prevent the battery from ATTENTION exploding An exploding battery exposes toxic corrosive and flammable chemicals and causes burns do not i
129. nchronization outputting data to all devices simultaneously improves synchronization between devices 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 The Scanner to Target Multicast ID of the Details Tab indicates to which multicast output group the connection belongs connections with the same Multicast ID will have their output data combined into a single transmission on the ControlNet network The processor will combine the output data into a single packet and simultaneously send it to all assigned connections that have the same Request Packet Interval Output Address in the PLC 5 data table Output Size You must determine if the output data being sent to each device of a multicast group is compatible with the application Using Multicast Outputs affects the ControINet I O Status file Immediate Inhibit bit and ControlNet I O Status file Reset bit functionality ControlNet I O Status file Immediate Bit since all connections in a Scanner to Target Multicast ID group share the same output data the Immediate Inhibit Bit will not take affect until all connections of that group have the
130. ncinerate or expose the battery to high temperatures e do not solder the battery or leads do not open puncture or crush the battery do not charge the battery do not short positive or negative terminals together 1785 UM022C EN P February 2008 Setting the 1 0 Chassis Backplane Switches Installing Your ControlNet PLC 5 Processor 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 1 Last State ON Outputs of this 1 0 chassis remain in their last state when a hardware failure occurs OFF Outputs of this 1 0 chassis are turned off when a hardware failure occurs P Always OFF Switches 1 5 Addressing ON OFF OFF 2 slot OFF OFF ON 1 slot ON OFF 1 2 slot ON ON Not allowed Switches EEPROM Transfer 6 7 OFF OFF EEPROM memory transfer to processor memory at powerup 2 ON ON EEPROM memory transfers to processor memory if processor memory not valid ON OFF EEPROM memory does not transfer to processor memory Switch Processor Memory Protection OFF Proc
131. nconnected clients 55 always less than or equal to 8 Maximum number of simultaneously used unconnected clients 56 always less than or equal to 8 Accumulated number of unconnected client timeouts 57 Current number of used unconnected servers 58 always less than or equal to 20 Maximum number of simultaneously used unconnected servers 59 always less than or equal to 20 Accumulated number of unconnected server timeouts 60 Accumulated number of dropped unconnected requests 61 Accumulated number of JITT overruns 62 1 The file offset in the user specified ControlNet diagnostics file For example if you specified N12 then the Buffer Errors would be located in N12 0 bits 15 00 The following table describes each bit in word 23 Channel status and Media bits of the diagnostic file Bit s Description Values 2 0 channel A LED state 000 off 001 green 5 3 channel B LED state 010 flashing green off 011 flashing red off 100 flashing red green 101 railroading red off 110 railroading red green 111 red 6 redundancy warning 0 normal 1 non selected channel is unusable 1 active channel 0 channel B active 1 channel A active 8 repeater mode 0 device set for normal mode 1 device set for repeater mode 9 channel A media mode 0 configured for Coaxial 1 configured for fiber 10 channel B media mode 0 configured for Coaxial 1 configured for fiber 15 11 reserved
132. nning to Use Your ControlNet PLC 5 Processor 2 27 Example 4 Examine the following system 0 0 0 0 0 Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter A Analog Module PS Power Supply X Empty Slot ACN ACN A 0 A X X A 1 ACN 0 0 Input file Input size Output file Output size Chassis 1 1 010 5 0 010 8 Chassis 2 1 015 8 0 020 3 Chassis 3 1 025 7 0 023 3 Assume you want to add an additional output module in one of the empty slots in the second chassis Only three words of output are mapped to the second chassis You have to change the output size in the second chassis to five to get to the first empty slot However this example started mapping the third chassis at O 023 If you try to set the second chassis size to five you get an overlap error because words O 023 and O 024 are being used in the third chassis You can always change the starting address of the third chassis but then you must change any references to the outputs in your program It may be better to start mapping the third chassis at O 027 to allow for output expansion You can add input modules in the empty slots without changing anything since there are already eight words of inputs mapped to the chassis Optimizing the I O Image Table with Slot Complementary Slot complementary makes use of the ability of a chassis to share inputs or outputs between
133. ntrolNet network 2 16 2 34 2 35 Requested Packet Interval definition P 3 reset bit D 2 RSLinx software 3 1 RSLogix software 3 1 RSNetWorx for ControlNet software 3 1 RSNetWorx to perform verification activities 3 4 S scan list configuration definition P 2 scan list entry definition P 2 scanner signature verification 3 4 scheduled connection types definition P 3 Scheduled Data Transfer definition 2 2 scheduled data transfer operations 2 2 2 4 scheduled maximum node definition P 3 scheduled peer to peer communication 2 4 scheduled peer to peer communications 2 21 scheduled peer to peer communications mapping 2 21 scheduled transfers definition of P 3 screens Instruction Entry for ControlNet 1 0 Transfer Block 4 3 Instruction Entry for Message Block 1 segment definition of P 3 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 1 0 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 1 0 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 1 0 description 2 18 status file processor B 1 status indicators location of on PLC 5 20C 1 3 on PLC 5 40C 1 4 PLC 5 5 1 us
134. o a location with eight words available In this example words I 024 I 033 must be available The ControlNet network also allows the size of the chassis to be set based on what is needed Using the previous example the chassis on the Remote I O network uses eight words of inputs and eight words of outputs regardless of what modules are actually in the chassis On the ControlNet network you can set the sizes to what is actually needed For example you can set the input size to six and the output size to three If no outputs are in the chassis you can set the output size to Zero Planning to Use Your ControlNet PLC 5 Processor 2 23 Optimizing the 1 0 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 The use of these techniques is not required they merely demonstrate methods which can be used to make maximum use of the available I O image table Proceed with caution when using these techniques Important You need to understand the ramifications of how you map the I O before proceeding as the method you use may make future expansion extremely difficult There are two methods to optimize the use of I O image table in a ControlNet PLC 5 processor e optimizing witho
135. o memory module 1 11 Performing online programming 5 112 Not defined 5 118 User program checksum calculated 5 114 Last scan of ladder SFC step 5 115 Processor running first program scan or the first scan of the next step in an SFC 5 2 Switch setting information 5 2 00 Channel 1A DH station number through 2 05 5 2 06 Channel 1A DH baud rate 0 57 6 kbps 1 2304 kbps 1785 UM022C EN P February 2008 B 2 Processor Status File 5 3 10 1785 UM022C EN P February 2008 This word of Stores the status file 5 2 07 Not defined 2 08 5 2 09 Last state 0 outputs are turned off 1 outputs retain last state 5 2 11 1 0 chassis addressing 5 2 12 bit12 bit 11 0 0 illegal 1 0 1 2 slot 0 1 1 slot 1 1 2 slot 2 13 Memory module transfer S 2 14 bit14 bit13 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 powerup 2 15 Processor memory protection 0 enabled 1 disable This word of the status file Stores 5 3 to 8 6 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 5 7 Global status bits See also 5 27 5 32 5 33 5 34 and 5 35 e 5 7 0 7 rack fault bits for racks 0 7 e 7 8 15 unused 5 8 Last program scan ms 5 9 Maximum program scan
136. ode Indicates this fault And the fault is 205 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 Because the configuration software is unable to accurately predict all the resources that the processor will require to execute your ControlNet configuration software based on the relative loading on the processor this fault code is used if the processor determines that your configuration typically when you accept Channel 2 edits exceeds the processor s available bandwidth Typical causes of this error code include e receiving data from the ControlNet network faster than the ControlNet PLC 5 processor can parse it e performing 1 0 updates too frequently e performing immediate ControlNet 1 0 ladder instructions too frequently See S 74 and S 75 for additional information Recoverable Reduce the number of ControlNet 1 0 map table entries Possible ways e using a discrete rack connection instead of multiple discrete module connections e combining multiple 1 0 racks into a single 1 0 rack e putting peer to peer data in contiguous blocks in the data table so that less send and receive scheduled messages are required Increase your Network Update Time and or increase the Requested Packet Intervals for scheduled data transfers in your 1 0 map table Increase your
137. odule takes when it is idle 1794 CONFIG DATA changes a module s configuration data GENERIC sends user specified CIP service 1794 CONFIG DATA changes a module s configuration data 1794 SAFE STATE DATA changes a module s safe state data CIP GENERIC sends user specified CIP service GENERIC BI DIRECTIONAL sends user specified CIP service which requires reply data 1747 READ INPUT reads data from SLC 1 0 module input file 1747 WRITE OUTPUT writes data to SLC 1 0 module output file 1747 READ FILE reads data from SLC 1 0 module MO file 1747 WRITE FILE writes data to SLC 1 0 module MO file 1747 READ MI FILE reads data from SLC 1 0 module M1 file e 1747 WRITE FILE writes data to SLC 1 0 module M1 file 1747 SAFE STATE change SLC 1 0 module safe state DATA data 1747 WRITE FLAGS change action SLC 1 0 module take when it faults and or goes to idle 1747 CONFIG DATA change SLC module configuration data enter a PLC 5 data table address Type the data table address enter the size in elements Type the number of elements 0 to 64 for 1771 READ or 1771 WRITE e 1 for 1794 FAULT ACTION or 1794 IDLE ACTION e 1 to 15 for 1794 CONFIG DATA or 1794 SAFE STATE DATA e 110 16 for 1794 READ or 1794 WRITE e 1 to 32 for 1747 READ INPUT or 1747 WRITE INPUT e 1 to 138 for 1747 READ MO FILE 1747 WRITE MO FILE 1747 READ M1 FILE 1747 WRITE M1 FILE e 1 to 138
138. olNet adapter the adapter will go into idle mode The processor will not attempt to reopen the connection as long as this bit is set The processor will also set the Data Invalid Bit and Connection Error Bit Clear this bit to allow the processor to attempt to open the associated connection PCSC Enable Bit Set this bit to enable Process Control Sample Complete for the associated 1 0 map entry Clear this bit to disable Process Control Sample Complete for the associated 1 0 map entry PCSC New Data Bit The processor sets this bit when the PCSC Enable Bit is set and new data arrives from the associated connection Clear this bit when you are finished processing the current sample of data PCSC Overflow Bit The processor sets this bit when the PCSC Enable Bit and the PCSC New Data Bits are set and new data arrives from the associated connection This means that PCSC data is arriving faster than your ladder program is processing it Clear this bit after you modify your ladder program to handle the incoming PCSC data Immediate Inhibit Bit Set this bit to immediately stop communicating on the associated connection This has the same effect as if you disconnected the target node from the ControlNet network If the target node is a ControlNet adapter and the adapter is setup for Processor Restart Lockout the adapter will go into Processor Restart Lockout mode The processor will not attempt to reopen the connection as long as
139. on this equipment must be mounted in a suitable enclosure with proper wiring method that complies with the governing electrical codes This section lists information about e serial cables e DH programming cables e remote I O cables e ControlNet cables For more information about cables see the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication 1785 6 5 12 Serial Cables You can make your own serial cables or purchase them from Rockwell Automation The side label of the processor shows the following table which lists Channel 0 serial port pin assignments Pin RS 232C RS 422A RS 423 Pin RS 232C RS 422A RS 423 1 C GND C GND C GND 14 NOT USED TXD OUT SEND COM 2 TXD OUT TXD OUT TXD OUT 15 3 RXD IN RXD IN RXD IN 16 NOT USED RXD IN REC COM 4 RTS OUT RTS OUT RTS OUT 17 5 CTS IN CTS IN CTS IN 18 6 DSR IN DSR IN DSR IN 19 NOT USED RTS 0UT NOT USED 7 SIG GND SIG GND SIG GND 20 DTR OUT DTR OUT DTR OUT 8 DCD IN DCD IN DCD IN 21 9 22 NOT USED DSRJN NOT USED 10 NOT USED DCD IN NOT USED 23 NOT USED DTR OUT NOT USED 11 24 12 25 13 NOT USED CTS IN NOT USED The shading indicates that the pin is reserved 1785 UM022C EN P February 2008 Installing Your ControlNet PLC 5 Processor 1 23 This processor s serial port can support these configurations Digital Interface Maximum Cable
140. onnection data transfers on a per node basis in the 1 0 map table scanlist configuration Non discrete 1 0 Data Handled with the same priority as discrete 1 0 data Transfer can be done transfer You can update analog data without using as a module block transfer instructions in ladder programs You do connection this by including non discrete 1 0 data transfer configurations in the 1 0 map table scanlist configuration This data is updated in the buffers and data table files between logic scans in the same manner as that used in discrete 1 0 data transfer Peer to peer Allows a ControlNet processor to communicate with Communication any other ControlNet processor on the ControlNet network with the same priority as that of the discrete and non discrete 1 0 data transfers discussed above While scheduled data transfer is asynchronous to program scanning all data is presented synchronously to and from the user data table during housekeeping 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 e unscheduled I O data transfers or when unscheduled messaging is event driven through ControlNet I O Transfer CIO instructions e peer to peer messaging through Message MSG instructions messaging from programming devices messaging from Human Machine
141. ontrolNet I O map table Table 2 D Maximum 1 0 Map Entries Processor Number of Number of DIF Number of DIF Number of DOF Number of DOF 5 Mappings Files Words Files Words PLC 5 20C15 64 2 2000 2 2000 PLC 5 40C15 96 3 3000 3 3000 PLC 5 46C15 96 3 3000 3 3000 PLC 5 80C15 128 4 4000 4 4000 Each map table entry corresponds to one transfer input only output only or both input and output of data between the ControlNet processor and an I O rack an I O module or another ControlNet processor Table 2 E Files That You Configure with the 1 0 Map for Scheduled 1 0 Usage File Description ControlNet Status File User specified integer data table file containing status information about this processor s scheduled 1 0 map table entries Each 1 0 map table entry has a status file offset field pointing to three status words associated with that entry Refer to Appendix D for more information on 1 0 map table entry status words ControlNet Diagnostics File User specified integer data table file containing diagnostics about the ControlNet network not required See Appendix F Data Input File DIF User specified integer data table file with a maximum of e 2000 words for the PLC 5 20C processor spanning two contiguous data table files e 3000 words for the PLC 5 40C processor spanning three contiguous data table files e 3000 words for the PLC 5 46C processor spanning three contiguous data table files e 4000 words for t
142. ontrolNet PLC 5 Processor 2 slot addressing 16 point modules 1785 UM022C EN P February 2008 However the overall system may be heavy on inputs and there are no concerns about the output image table In this case you may want to conserve the input image table for this chassis and arrange it as follows ACN 0 0 Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter When deciding when where and what type of optimization to use you have to balance e space limitations e additional costs extra chassis adapters etc e I O image table availability e future expansion Planning to Use Your ControlNet PLC 5 Processor 2 31 Using the ControlNet There can be multiple ControlNet PLC 5 processors updating I O PLC 5 Processor in a adapters on a ControINet network ControlNet 1 0 System any processor can own adapters on the network e processor is allowed to send CIO instructions to I O modules e additional processors can do scheduled transfers to any other processor on the ControlNet network by using peer to peer Catalog Number s 1785 L20C15 L40C15 L46C15 L80C15 communications through the scan configuration list The following table describes various ControlNet devices that you can add to your network For a complete listing contact your local Rockwell Automation sales office Device s ControlNet Programmable Controllers Function Communicate
143. ontrolNet hot backup Refer to PLC 5 40C or 5 80C publication 1785 6 5 24 for more information Verify that the 1785 CHBM Hot Backup module is properly installed The target node does not support Replace the target node with one ControlNet Hot Backup that supports ControlNet Hot Backup 280 0x0118 INVALID CONFIGURATION The target node module does not Replace the target node module FORMAT match the node module entered in with the correct node module the map table Verify that the target node module is powered up Correct the map table 281 0x0119 OWNER CONNECTION NOT The originating node attempted to Correct any connection errors OPEN open a listen only connection before associated with the owner the owner connection was opened connection The CIO instruction failed because In the I O map table add a discrete the 1771 discrete rack has no connection for the 1771 1 0 rack owner The ControlNet cable from the Fix and or reconnect the ControlNet controlling node to the target node is cable broken or disconnected The controlling node is not powered Supply power to the controlling node The target 1771 adapter is in Press the reset button on the target Processor Restart Lockout 1771 adapter Cycle power to the target 1771 adapter 282 0x011A OUT OF APPLICATION The maximum number of e lf this is an 1 0 connection reduce CONNECTIONS connections to from this node has the number of 1 0 connections been exceeded f this is a MSG inst
144. orx software even if no ControlNet configuration information changed for any ControlNet PLC 5 processor This is required because a network keeper signature is reevaluated every save and is unique for every save The network keeper signature is downloaded to every keeper capable device on the ControlNet network Using RSNetWorx Software to Perform Verification Activities After a Download or Save in RSNetWorx Software We recommend that you perform two verification activities following a download or save operation in RSNetWorx software Verify Keeper Signatures e Verify Scanner Signatures For More Information 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 If any scanners are invalid download the RSNetWorx project to the processors that indicate a scanner signature mismatch you may have to follow additional troubleshooting procedures in RSNetWorx software to correct the scanner signature mismatch Merge Save Functionality When you add or delete nodes or when you add modify or delete I O map table entries only those processors on the network whose ControlNet schedules need to change are required to be in Program mode This feature requires RSNetWorx for ControlNet software version 1 6 or
145. ould be downloaded With this approach you will want to keep the existing ControINet configuration that is currently on the ControlNet PLC 5 processor Download from RSLogix 5 Software Only You can download the entire program from RSLogix 5 software while keeping the ControlNet configuration information up to date When downloading the ControlNet configuration information from RSLogix 5 software 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 overwrite the existing ControlNet configuration that is currently on the ControlNet PLC 5 processor with the ControlNet configuration information that is stored in the RSLogix 5 project rsp file The ControlNet configuration information in RSLogix 5 software is kept up to date by uploading from the ControlNet PLC 5 processor and by saving a new RSLogix 5 project rsp file following every save performed in RSNetWorx software or following an RSNetWorx project download if a save was performed off line Important This approach simplifies the download to a single operation however it requires the maintenance of keeping the RSLogix 5 project rsp file up to date with the current ControINet network configuration information for every PLC 5 processor on the ControlNet network To do this you must perform the RSLogix 5 upload and save for each and every save performed in RSNetW
146. output update to the 1 0 chassis The actual change is not communicated until the next asynchronous 1 0 transfer Only 1 word of 1 0 data can be updated per instruction ControlNet Immediate Data 1 0 IDI IMMEDIATE DATA INPUT 7 Data file offset 232 _ Length 10 Destination N11 232 IDO IMMEDIATE DATA OUTPUT Data file offset 175 Length 24 Source N12 175 The ControlNet Immediate Data 1 0 instructions work in much the same way as the immediate 1 0 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 specify to the private memory buffer and sent on the next 1 0 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 Chapter 4 for more information on this and other aspects of using ControlNet IDI and IDO instructions Using Process Control Sample Complete Scheduled data transfers occur continuously and asynchronously to the program scan If a scheduled connection is an input then incoming data is copied to a private input buffer upon its receipt If a scheduled connection is an output then data from a private output buffer is transmitted during each scheduled com
147. pective companies Revised Information Software and Hardware Requirements 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 See the table in the Using the ControlNet PLC 5 Processor in a ControlNet I O System section on page 2 31 to see the revision to information about the ControlLogix ControlNet Bridge Use the following table to understand specific features that are only available with specific versions and releases of software and PLC 5 processors You need both of these And this PLC 5 processor If you want this feature versions of software ControlNet Series F RSLogix5 RSNetWorx Revision A or later Standard functionality 2 20rlater 1 8 or later all Hot Backup 1771 and FLEX 1 0 3 21 or later 1 8 or later PLC 5 40 or 5 80 Multicast Outputs 3 21 or later 3 0 or later PLC 5 20 5 40 or 5 80 SLC 1 0 also with Hot Backup 5 0 or later 3 0 or later PLC 5 40 or 5 80 1785 UM022C EN P February 2008 SOC ii Notes 1785 UM022C EN P February 2008 Installing Your ControlNet PLC 5 Processor Planning to Use Your ControlNet PLC 5 Processor Table of Contents Chapter 1 Using This CADE uu 2222 eese rir hb hehehe hb he 1 1 Prevent Electrostatic
148. pter 2 Using Tis Chapel ua cuu oe qaare ath Qe CE Voie ui end 2 1 Understanding ControlNet 0 2 1 Scheduled Data Transfer Operations on a ControlNet Network 2 2 Unscheduled Data Transfer Operations on a ControlNet Network 2 4 Using 1 0 Forcing Operations 2 7 Using Immediate Data Transfer Operations 2 8 Using Process Control Sample Complete 2 9 Clearing the PCSC New Data and PCSC Overflow Bits 2 11 Considerations When Using 5 2 11 Understanding Scheduled Connection Types 2 11 Allowable Scheduled Connection Type Combinations 2 12 Multiple Processors Can 0 2 13 1785 UM022C EN P February 2008 ii Table of Contents ControlNet PLC 5 Programmable Controllers Understanding Multicast Inputs 2 14 Understanding Multicast 2 14 Using Multicast 2 15 Understanding ControlNet 1 0 Mapping 2 16 Reserving Space for Non ControlNet 0 2 16 Processor Resident Local 1 0 2 16 Remote Ue se dd ed veoh we bx aote da dea E Reb e bacs 2 17 Supported ControlNet 1 0 Sizes 2 18 Discrete 1 0 Data Transfer 2 19 Non Discr
149. r Cable broken e Repair cable slowly DH No other nodes on network Red Remote 1 0 Hardware fault Hardware error e Turn power off then steady Scanner on Remote 1 0 Check that the Adapter software DH configurations match the hardware set up e Replace the processor Red Remote 1 0 Faulted adapters detected Cable not Repair cable blinking Scanner connected or rapidly or is broken slowly e Power off at Restore power to remote racks racks DH Bad communication on Duplicate node Correct station address DH detected Off Remote 1 0 Channel offline Channel is not Place channel online if Scanner being used needed Remote 1 0 Adapter DH 1785 UM022C EN P February 2008 5 6 Monitoring ControlNet Configuration and Status 1785 UM022C EN P February 2008 Use the following software packages to monitor ControlNet configuration and status information Use To RSNetWorx for ControlNet define ControlNet network parameters such as network update time media redundancy physical media configuration e maximum scheduled nodes e maximum unscheduled nodes e monitor 1 0 map entry status RSLogix5 e monitor ControlNet diagnostic file e enter user program files e create delete monitor data table files e enter module configuration e enter channel 0 1A 1B and 3 configuration administer passwords and privileges RSLinx to provide the ControlNet network interfa
150. r 2 4 unscheduled non discrete 1 0 data transfer 2 4 unscheduled operations messaging from programming Publication 1785 UM022C EN P February 2008 devices 2 4 non discrete 1 0 data transfer 2 4 peer to peer messaging 2 4 1 0 configuration utility 3 2 1 0 forcing 2 7 1 0 map table definition of P 2 1 0 map entry status words D 1 1 0 mapping techniques 2 21 1 0 status indicator 5 3 IDI 2 9 IDO 2 9 IIN 2 9 Immediate Data Input IDI instruction C 2 Immediate Data Output IDO instruction C 2 immediate data transfer operations 2 8 immediate 1 0 process 2 9 immediate inhibit bit D 2 Immediate Input IIN instruction 2 9 Immediate Output IOT instruction 2 9 indicators PLC 5 20C 1 3 PLC 5 40C 1 4 inhibit bit D 2 installed memory card type using status to determine B 14 installing keying bands for the processor 1 10 installing your processor checking your processor package 1 5 connecting a programming terminal 1 19 ControlNet connection 1 21 DH connection 1 19 serial channel 1 20 connecting to a ControlNet network 1 17 identifying the components of the processor 1 3 installing a DH link 1 15 installing a remote 1 0 link 1 13 installing keying bands for the processor 1 10 installing the processor in the chassis 1 13 locating additional information 1 1 removing the processor from the chassis 1 13 selecting cables ControlNet cables 1 23 DH programming 1 23 remote 1 0 1 23 serial 1 22 selecting the ControlNe
151. rocessor is typically mapped to the I O image table You can map discrete I O to the DIF and DOF but you lose the ability to force the I O if the DIF or DOF is used Each version of the PLC 5 processor has a specific amount of I O image table available and therefore a limit on the amount of I O that can be mapped to the I O image table Traditionally each slot in an I O chassis is assigned a location in the input image table and the output image table While this provides very easy mapping of I O to the image table it is not the most efficient way to use it For example if a slot contains an input module the corresponding location in the output image table goes unused With the introduction of the ControlNet network to the PLC 5 processor family new techniques are available to map discrete I O into the I O image table in a more efficient manner Input and output data can be mapped to offsets within the I O image tables and need not be the same size 1785 UM022C EN P February 2008 2 22 Planning to Use Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 Understanding Discrete Mapping Each version of a PLC 5 processor has a fixed amount of I O image space For example This processor Has PLC 5 20C 32 words of input image table and 32 words of output image table PLC 5 40C 128 words of input image table and 128 words of output image table PLC 5 46C 128 words of input image table and 128 words of
152. rolNet PLC 5 40C processor 1 4 ControlNet processor configuring your ControlNet system 3 1 installing 1 1 planning to use 2 1 programming your system 4 1 ControlNet publications P 4 ControlNet status processor ControlNet system cabling 1 23 configuring 3 1 changing a 1794 1 0 modules fault action 2 6 4 4 changing a 1794 1 0 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 2 31 ControlNet system software 3 1 ControlNet conserving resources 4 3 Converting ControlNet phase 1 0 or 1 25 to 1 5 2 35 non ControlNet to ControlNet system 2 34 Data Highway Plus status indicators 5 5 Data Input File definition P 2 description 2 18 2 19 data invalid bit D 2 Data Output File definition P 2 description 2 18 2 19 data overrrun D 2 data underrun D 2 Default Configuration File description 2 18 diagnostics file layout ControlNet F 1 DIF P 2 2 18 2 19 diganostics counters F 1 discrete 1 0 data transfer Index 3 definition of P 2 description 2 4 discrete 1 0 data transfer mapping 2 19 distributed keeper functionality 2 33 DOF P 2 2 18 2 19 download from RSLogix 5 3 3 download software projects 3 3 drop cable definition of P 2 E error codes D 4 error codes 20
153. rors 0 15 00 Last 8 Nodes from which bad packets were received 1 4 Good Frames Transmitted center significant byte 5 07 00 Good Frames Transmitted least significant byte 5 15 08 Good Frames Received least significant byte 6 07 00 Good Frames Transmitted most significant byte 6 15 08 Good Frames Received most significant byte 7 07 00 Good Frames Received center significant byte 7 15 08 Channel A Errors 8 07 00 Bad Received Frames 8 15 08 Aborted Frames Transmitted 9 07 00 Channel B Errors 9 15 08 NUI Overloads 10 07 00 Highwaters Out of Steps 10 15 08 Blockages 11 07 00 Slot Overloads 11 15 08 Aborted Frames Received 12 07 00 Non Concurrences 12 15 08 Frames with Duplicate Node Address Received 13 07 00 Lonely Occurrences 13 15 08 Collisions 14 07 00 Noise Hits 1415 08 Moderators from non lowmen 15 07 00 1785 UM022C EN P February 2008 F 2 1785 UM022C EN P February 2008 Field Names ale Offset word bits Node Address of current Moderator 15 15 08 Cannot Hear Moderator Occurrences i e Lonely 16 07 00 Network Parameter Mismatch Occurrences 16 15 08 Reserved 17 07 00 SM Commands Received from the wire 17 15 08 Reserved 18 07 00 Reserved 18 15 08 Fault Register Pre Reset 19 07 00 Reserved 19 15 08 Reserved 20 07 00 Fault Register Post Reset 20 15 08 Dirty bits 21 7 0 SMAC version number 21 15 8 Interf
154. ruction reduce the number of MSG instructions e f this is a CIO instruction reduce the number of CIO instructions 515 0x0203 CONNECTION TIMED OUT The ControlNet cable from the Fix and or reconnect the ControlNet originating node to the target node is broken or disconnected cable The target node is not powered Supply power to the target node 1785 UM022C EN P February 2008 ControlNet 1 0 Map Entry Status Words and Error Codes D 7 Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 516 0x0204 UNCONNECTED REQUEST The ControlNet cable from the Fix and or reconnect the ControlNet TIMED OUT originating node to the target node is cable broken or disconnected The target node is not powered Supply power to the target node The originator s and or the target s Reconfigure the ControlNet network node number is greater than UMAX sothatthe originator s and target s node numbers are less than or equal to UMAX The target node is too busy to Reduce the number of unconnected respond requests to the target node 769 0x0301 OUT OF BUFFER MEMORY The maximum number of e If this is 1 0 connection reduce connections to from this node has the number of 1 0 connections been exceeded f this is MSG instruction reduce the number of MSG instructions e If this is a CIO instruction reduce the number of CIO instr
155. s 2 4 unscheduled non discrete 1 0 data transfer 2 4 unscheduled operations Publication 1785 UM022C EN P February 2008 ControlNet 1 0 Transfer CIO instruction description C 1 ControlNet 1 0 Transfer CIO instructions description 2 6 features 2 6 1 0 transfer instructions programming 4 3 immediate data 1 0 instructions programming 4 6 ladder rung messages 2 4 messaging from programming devices 2 4 non discrete 1 0 data transfers 2 6 description C 1 features C 1 peer to peer messaging 2 4 2 7 peer to peer messaging instructions 4 1 programming C 1 ControlNet 1 0 automatic mapping 2 16 ControlNet I O mapping automatic 2 16 reserving rack space for remote 1 0 linked racks before mapping 2 16 understanding 2 16 discrete 1 0 data transfer mapping 2 19 mapping data transfers 2 18 non discrete 1 0 data transfer mapping 2 19 2 20 ControlNet 1 0 status file D 2 ControlNet 1 0 Transfer CIO instructions 2 4 2 6 4 3 C 1 ControlNet immediate data 1 0 instructions Immediate Data Input IDI C 2 Immediate Data Output IDO C 2 process C 2 ControlNet immediate data 1 0 instructions process 2 9 ControINet Immediate Data Input IDI instruction 2 9 ControlNet Immediate Data Output IDO instruction 2 9 ControlNet network definition of P 2 locating additional information P 4 ControlNet network examples 2 32 ControlNet PLC 5 configuration matches network information 3 3 ControlNet PLC 5 20C processor 1 3 Cont
156. s For more information refer to publication 1770 4 1 Industrial Automation Wiring and Grounding Guidelines See the Product Certification link at http www ab com for Declarations of Conformity Certificates and other certification details 1785 UM022C EN P February 2008 A 3 PLC 5 20C15 PLC 5 40C15 PLC 5 46C15 PLC 5 80C15 Maximum User Memory Words 16K 48K 48K 100K2 Maximum Total Any Mix 512 2048 2048 3072 1 0 Complimentary 512inand512 2048inand 2048inand 3072 in and out 2048 out 2048 out 3072 out Program Scan Time 0 5 ms per K word bit logic 2 ms per K word typical ControlNet 1 03 Transmission Rate 5M bit s Network Update Time NUT 2 100 ms user selectable Number of ControlNet Ports 1 redundant Maximum Number of Nodes per Link without a Repeater 48 with 250 m approx 820 ft cable length Maximum Number of Nodes per Link with Repeaters 99 Maximum Link Cable Length without a Repeater 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 Maximum Number of 1 0 Map Entries 64 96 96 128 Maximum DIF DOF Size 2000 words 3000 words 3000 words 4000 words Maximum Link Cable Length with Repeaters 6 000 m approximately 19 680 ft with 2 nodes 3 000 m approximately 9 840 ft typical R
157. s Repeater adapter 1786 RPA Copper 1786 RPCD Fiber short 1786 RPFS Fiber medium 1786 RPFM Fiber ring long 1786 RPFRL Fiber ring extra long 1786 RPFRXL Dummy load 1786 TCAP Fiberoptic Repeaters Low voltage dc 1786 RPA RG 6 Quad Shield Cable Standard PVC CM CL2 1786 RG6 ControlNet Network Access Cable 3 05 m 10 ft 1786 CP PC Card Cable for 1784 PCC 1784 PCC1 BNC Connectors Barrel plug to plug 1786 BNCP BNC RG 6 plug 1786 BNC Bullet jack to jack 1786 BNCJ Isolated bulkhead jack to 1786 BNCJI jack Terminators BNC 75O 1786 XT For a complete list of ControlNet cable system components that are available from Rockwell Automation and other sources see the ControlNet Cable System Component List publication AG 2 2 Planned availability March 2002 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 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 Overv
158. s in a cool dry environment We recommend 25 C with 40 or 60 relative humidity You may store batteries up to 30 days between 45 85 C such as during transportation To avoid possible leakage do not store batteries above 60 C for more than 30 days Installing Your ControlNet PLC 5 Processor 1 7 To install or replace the battery CN 1 Remove the battery from the shipping bag O 2 Remove the battery cover from the processor 3 Ifyou are replacing an existing battery detach the wired clip from the mating connector on the processor and remove the bat clip to the mating connector on the processor 5 Soe tery h 4 Connect the new or replacement battery by attaching the wired 5 Place the battery and tuck the wires inside the battery area on the processor Replace the battery cover Use a pencil or erasable pen to write the battery installation date on the battery cover K 7 N G VY N N 1 e Ve t S um When you connect disconnect the battery electrical arc can occur This could cause an 2 L7 SB explosion in hazardous location installations Be E i sure that power is removed or the area is nd is nonhazardous before proceeding e For safety information on the handling of lithium batteries including handling and disposal of leaking batteries refer to Guidelines for Handling Lithium Batteries publicatio
159. se changes manually by e PLC5 40L reprogramming 2 performed by the ControlNet network you must make these changes manually by reprogramming gt gt 1 These include processor files data table files and port configurations If you do not update the program the ControlNet processor will fault scheduled transfers or to unscheduled CIO instructions You must change block transfer instructions for the ControlNet system from the standard block transfer read BTR and block transfer write BTW instructions to You must edit non ControlNet PLC 5 programs containing references to the 1 0 Status File for use with 1 0 connected via the ControlNet network Information regarding ControlNet status is stored in a separate data file that you specify through the programming software If you do not update the program the data table locations corresponding to the missing 1 0 devices will not be updated Converting from ControlNet Phase 1 0 or 1 25 to ControlNet Phase 1 5 ControlNet phase 1 0 or 1 25 products will not work in a ControlNet 1 5 system To convert ControlNet phase 1 0 or 1 25 to ControlNet phase 1 5 contact your local Rockwell Automation sales office or distributor 1785 UM022C EN P February 2008 2 36 Planning to Use Your ControlNet PLC 5 Processor Notes 1785 UM022C EN P February 2008 Using This Chapter Configuring and Programming Your ControlNet System Chapter 3 Understanding the ControlNet System So
160. structions 1786 2 6 ControlNet Fiber Planning and Installation Guide CNET INOO1A EN P System Design for Control of Electrical Noise GMC RM001A EN P Industrial Automation Wiring and Grounding Guidelines 1770 4 1 Terminating Your ControlNet Coaxial Cables CD ROM CNET DM001A EN C To view or order these publications online visit http literature rockwellautomation com Installing Your ControlNet PLC 5 Processor 1 19 Connecting a You can connect a programming terminal to a ControlNet PLC 5 Programming Terminal processor via a e DH connection e serial channel e ControlNet connection 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 WARNING If you connect or disconnect the DH 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 DH Connection To attach a personal computer to a ControINet PLC 5 processor using a connection
161. t network address 1 12 selecting the DH station address of Channel 1A 1 11 setting the 1 0 chassis backplane switches 1 9 setting the 1 0 chassis configuration plug 1 10 specifying the serial interface of Channel 0 1 12 instructions ControlNet 1 0 Transfer CIO 2 6 C 1 how to use 4 3 when to use 2 20 2 35 ControlNet Immediate Data Input IDI 2 9 C 2 ow to use 4 6 ControlNet Immediate Data Output 100 2 9 C 2 how to use 4 6 ControlNet Message MSG how to use 4 1 Immediate Input IIN 2 9 Immediate Output IOT 2 9 Message MSG 2 7 how to use C 1 when to use 2 21 IOT 2 9 g K keeper definition P 2 keeper signature verification 3 4 keyswitch location of on PLC 5 20C 1 3 on PLC 5 40C 1 4 Index 5 L ladder rung messaging 2 4 link definition of P 2 major fault 200 and 201 4 9 major fault codes E 1 map table 2 16 maptable entries 2 16 maptable entry P 2 memory card type using status file to determine B 14 memory module space 1 3 1 4 merge save functionality 3 5 Message instructions 2 4 2 7 4 1 C 1 monitoring ControlNet system 5 1 MSGs 2 4 multicast 2 14 multicast inputs 2 14 multicast outputs 2 14 NAP P 2 Network Access Port definition of P 2 network address definition of P 2 network examples 2 32 Network Update Interval 2 5 definition of P 2 Network Update Time definition of P 3 node definition of P 3 non discrete 1 0 data transfer P 3 2 4 non discrete 1 0 data transfer m
162. table later in this chapter 235 Illegal invalid backup state Cycle power to the processor If the fault reoccurs contact Rockwell Automation Technical Support at 440 646 6800 236 Illegal No Control backup state Cycle power to the processor If the fault reoccurs contact Rockwell Automation Technical Support at 440 646 6800 237 Illegal Primary Secondary backup state Cycle power to the processor If the fault reoccurs contact Rockwell Automation Technical Support at 440 646 6800 238 Incompatible firmware revisions Install the same series and revision of firmware into both hot backup PLC 5 processors 239 ControlNet keeper mismatch Use RSNetworx to make the PLC 5 processor a valid keeper 1785 UM022C EN P February 2008 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 The layout of the ControlNet diagnostic file is described in the following table The processor updates this file once every second 1 Field Names HD Buffer Er
163. ted connection is larger than expected The Data Invalid Bit will not be set Run Mode This bit it set to give the Run Idle status of the target device for connections that support Run Idle notification such as Peer to Peer Receive Data connections 1785 UM022C EN P February 2008 ControlNet 1 0 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 ControlNet 1 0 Connection Type Bit 9 of First Word of 1 0 Status File Entry Connection Error Second Word of I 0 Status File Entry Third Word of 1 0 Status File Entry All Set 0 Error code see the Error Messages section Receive Data Clear 0 0 peer processor is in PROGRAM mode 1 peer processor is in RUN mode Send Data Clear 0 Number of peer listeners 1747 Discrete Clear If bit x is clear then the module in slot x is OK If bit xis set then the module in slot x is missing bad or is the wrong type 1747 Analog Clear 0 0 1771 Discrete Clear 0 0 1771 Analog Read Clear 0 Error code from read 1771 Analog Write Clear Error code from write 0 1771 Analog Read Write Clear Error code from write Error code from read 1794 Discrete Clear 0 If bit xis clear then the module in slot x is OK If bit xis set then the module in slot x is missing bad or is the wrong type 1794 Analog Read Clear 0 If bit xis clear then the module in slot x is
164. tery status 5 1 C cables remote 1 0 1 13 cabling 1 23 catalog numbers ControlNet PLC 5 processors P 1 Channel 1A 2 34 Channel 1B 2 34 05 2 4 clearing faults E 1 Closing ControlNet communication 4 3 communication time slice B 14 Communication Connection closing 4 3 communication connection closing 4 3 communication ports location of on PLC 5 20C 1 3 on PLC 5 40C 1 4 communication option to close 4 3 configuration software 5 1 configuration utility 5 2 connecting a programming terminal 1 19 connecting to a ControlNet network 1 17 connection definition of P 2 connection error bit D 2 Conserving ControlNet resources 4 3 ControlNet diagnostics counters F 1 diagnostics file layout F 1 Scheduled Data Transfer 2 2 ControlNet cabling 1 23 ControlNet communication closing 4 3 ControlNet diagnostics file layout F 1 Publication 1785 UM022C EN P February 2008 2 Index ControlNet 1 0 error messages D 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 1 0 Status File 2 18 1 0 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 1 0 data transfer 2 4 nondiscrete 1 0 data transfer 2 4 peer to peer communication 2 4 understanding 2 1 unscheduled data transfer operation
165. th 24 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 Source N12 175 the instruction to ensure data block integrity in the case of Selectable Timed Interrupts STIs See page 4 8 in the Using ControlNet Immediate Data Input and Output Instructions section Immediate 1 0 Execution Times Execution Time Ls Instruction Processor Words of Memory True False INN Immediate Input PLC 5 20 C15 389 11 2 PLC 5 40C15 5 46C15 and 5 80 15 347 IOT Immediate Output PLC 5 20 C15 323 14 5 x dis 6 7 x DOF 1 1 2 PLC 5 40C15 5 46C15 and 5 80C15 330 27 5 x dis 13 25 DOF IDI Immediate Data PLC 5 20 C15 538 0 65 x words 1 1 4 7 Input PLC 5 40C15 5 46C15 and 5 80C15 488 0 65 x words IDO Immediate Data PLC 5 20 C15 286 1 23 x words 14 5 x 14 4 7 Output DOF 6 7 x dis PLC 5 40C15 5 46C15 and 5 80C15 270 1 6 x words 27 5 x DOF 13 25 x dis words IDI or IDO transfer length dis Total number of ControlNet connections using the discrete Output image file DOF Total number of ControlNet connections using the Data Output File 1785 UM022C EN P February 2008 Appendix D ControlNet 1 0 Map Entry Status Words and Error Codes 1 0 Map Entry The ControlNet status file is an integer data table file that you specify Status Words and configure with the I O map for schedul
166. that the processor is connected to the Red Off ControlNet network with an Allen Bradley tap Check media for broken cables loose connectors missing terminators etc No other nodes present on network Add other nodes to the network Flashing Incorrect network configuration Cycle power or reset unit Red Green If fault persists contact your Rockwell Automation representative or distributor 1 Definition of terms alternating the two indicators alternate between the two defined states at the same time applies to both indicators viewed together the two indicators are always in opposite states out of phase e flashing the indicator alternates between the two defined states applies to each indicator viewed independent of the other if both indicators are flashing they flash together in phase steady indicator is on continuously in the defined state 1785 UM022C EN P February 2008 Using the DH RIO Status Indicators Indicator Color Channel Mode Description Probable Cause Recommended Action Green Remote 1 0 Active Remote 1 0 link all Normal No action required u steady Scanner adapter modules are operation A present and not faulted Remote 1 0 Communicating with Adapter scanner DH Processor is transmitting or receiving on DH link Green Remote 1 0 At least one adapter is Power off at e Restore power to the blinking Scanner faulted or has failed remote rack rack rapidly o
167. tihop Messaging Via the MSG Instruction You can use the MSG instruction to communicate from a processor on one ControlNet link to a processor on another ControlNet link via ControlBus using 1756 CNB ControlNet bridge modules You can also configure a ControlNet ladder MSG instruction to e a Data Highway Plus device by bridging across the 1756 CNB R and 1756 DHRIO modules e Ethernet device by bridging across the 1756 CNB R and 1756 ENET modules Refer to your programming software documentation for information about configuring multihop messages Using the ControlNet 1 0 Transfer Instruction 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 Understanding the ControlNet PLC 2 Compatibility File When a PLC 2 command is received from the ControlNet network the ControlNet PLC 5 processor uses the user specified file as the PLC 2 compatibility file All PLC 2 commands received from the ControlNet network use the same PLC 2 compatibility file The ControlNet PLC 5 processor uses the value stored in 8 73 of the processor status file as the PLC 2 compatibility file number The PLC 2 file number must be between 3 and 999 inclusive
168. transfer to time out EW indicates that the transfer is waiting for an open connection CO transfer is made continuously in Run mode indicates that the transfer was terminated due to an error DN indicates that the transfer was made without error ST indicates that the transfer was started EN indicates that the transfer instruction is enabled e Error code indicates the error when the ER bit is set 2 Done length indicates the number of words transferred Features As many as 32 1771 READ and or 1771 WRITE ClOs can be active at a time Minor fault bit 17 14 is set when 32 1771 READ and or 1771 WRITE ClOs are active at a time As many as a total of 8 1794 FLEX 1 0 and 1747 SLC 1 0 ClOs can be active at a time Minor fault bit 17 15 is set when 8 1794 FLEX 1 0 ClOs 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 tens of milliseconds Vo 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 If the SFC startover bit is set in the processor configuration file continuous ClOs may tim
169. try one entry in the 1 0 map table that you configure using the programming software to map data from one 1 0 chassis or other device on ControlNet to particular data table file addresses network access port NAP port that provides a temporary ControlNet network connection through an RJ45 connector network address node s address on the ControlNet network network update interval NUI single occurrence of the ControlNet Network Update Time NUT 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 1 0 data transfer type of data transfer in which blocks of data transferred to or from a single 1 0 module use integer input and output data table files that you specify scheduled transfers are configured in the ControlNet 1 0 map table unscheduled transfers make use of ControlNet 1 0 Transfer CIO instructions owner device that controls the outputs of an adapter processor any one of the ControlNet PLC 5 programmable controllers redundant media dual cable system that allows you to receive the best signal over a ControlNet network 1785 UM022C EN P February 2008 Preface 3 Term Description repeater two port active ph
170. tswitch To toward TOP OFF DH Station Number 1 through6 See below Toggle pushed Channel 1A DH Configuration 7 on bottom 57 6 kbps toward BOTTOM off top 230 4 kbps UH on DH Switch DH Switch Station Station Number 1 2 3 4 5 6 Number 1 2 3 4 5 6 0 on on on on on on 40 on on on on on off 1 off on on on on on 41 off on on on on off off on on on on 42 on off on on on off off off on on on on 43 off off on on on off 4 on on off on on on 44 on on off on on off 3 off he e on on on 45 off on off on on off on 0 0 on on on 46 on off off on on off 7 off off off on on on 47 off off off on on off 10 on on on off on on 50 on on on off on off 11 off on on off on on 51 off on on off on off 12 on off on off on on 52 on off on off on off 13 off off on off on on 53 off off on off on off 14 on on off off on on 54 on on off off on off 15 off on off off on on 55 off on off off on off 16 on off off off on on 56 on off off off on off 17 off off off off on on 57 off off off off on off 20 on on on on off on 60 on on on on off off 21 off on on on off on 61 off on on on off off 22 on off on on off on 62 on off on on off off 23 off off on on off on 63 off off on on off off 24 on on off on off on 64 on on off on off off 25 off on off on off on 65 off on off on off off 26 on off off on off on 66 on off off on off off 27 off off off on off on 67 off off off on off off 30 on on on off off on 70 on on on off off off 31 off on on off off on 71 off on on off off o
171. uctions Instruction Description Immediate Data If the input conditions are true an immediate data input is initiated that IDI Input updates the destination file from the private buffers before the next normal IMMEDIATE DATA INPUT IDI 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 Data file offset 232 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 Length 10 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 Destination N11 232 to ensure data block integrity in the case of Selectable Times Interrupts STIs See page 4 8 in the Using ControlNet IMmediate Data Input and Output Instructions section Immediate Data If the input conditions are true an immediate data output is initiated that IDO Output updates the private memory output buffers from the source file before the IMMEDIATE DATA OUTPUT IDO 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 Data file offset 175 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 Leng
172. uctions 770 0 0302 SCHEDULED BANDWIDTH NOT There are too many words Edit the 1 0 map table to reduce the AVAILABLE scheduled for transmission number of scheduled words The network update time NUT is Increase the network update time too small NUT The originator s and or the target s Reconfigure the ControlNet network node number is greater than SMAX so that the originator s and target s node numbers are less than or equal to SMAX 772 0 0304 NO SCHEDULED The ControlNet cable from the Fix and or reconnect the ControlNet CONFIGURATION originating node to the keeper was cable and reconfigure the ControlNet broken or disconnected when the network ControlNet network was configured The keeper was not powered when Supply power to the keeper and the ControlNet network was reconfigure the ControlNet network configured The originating and or target node is Edit the 1 0 map table of the not properly configured to send originating and or target nodes to scheduled data send scheduled data 773 0 0305 SCANNER SIGNATURE The ControlNet cable from the Fix and or reconnect the ControlNet MISMATCH originating node to the keeper was cable Reconfigure the ControlNet broken or disconnected when the ControlNet network was configured network by enabling and accepting edits with RSNetWorx The ControlNet processor was not configured on the current network Reconfigure the ControlNet network by enabling and accepting edits w
173. ut slot complementary e optimizing with slot complementary where you set the I O chassis backplane switches to a lower density than the modules you are actually using and then staggering the modules input output input output etc For example you can set the backplane switches to 2 slot addressing and then place 16 point I O modules in the rack input output input output etc See Configuring Complementary I O for PLC 5 Processors publication number 1785 6 8 3 for information about slot complementary I O Both methods make use of arranging the I O modules in the most efficient manner within the chassis In many cases the optimal solution for a system is a combination of both the methods Optimizing the I O Image Table without Slot Complementary The techniques used for I O image optimization are best illustrated using examples The following examples all assume 1 slot addressing for all chassis and that the local rack is using rack 0 image table 1 000 007 and O 000 007 Example 1 Examine the following chassis ACN 0 0 l 0 0 X X Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter X Empty Slot 1785 UM022C EN P February 2008 2 24 Planning to Use Your ControlNet PLC 5 Processor 1785 UM022C EN P February 2008 If you perform an automap on this system the map table appears like this Input file Input size Output file Output size 010 8 0 010 8 The auto
174. ut slot e allows optimization of 1 0 image table but complementary not to the extent if using slot complementary e does not waste chassis slots can put any module anywhere provided 1 0 table exists for that slot optimize with slot complementary allows complete optimization of the 1 0 image table e can waste chassis slots and require additional chassis e can only put modules in odd or even slots depending on the module type The best solution in most cases is to combine the two methods Examine the module requirements at any given chassis or location and see which method fits best You may find in some areas you have an equal number of input and output modules and slot complementary optimizing works well However you may find in other areas there are space limitations which require the use of the smallest possible chassis and therefore you cannot waste slots using slot complementary A final point to be aware of is that each system is unique and you must apply these techniques accordingly For example you may have the following chassis ACN 0 0 I Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter Using strict rules of optimization you might immediately arrange the chassis like this ACN 0 0 1 Discrete Input Module 0 Discrete Output Module ACN ControlNet adapter 1785 UM022C EN P February 2008 2 30 Planning to Use Your C
175. you connect or disconnect the serial 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 ATTENTION Do not connect the same communication card to both the NAP and a tap on the ControlNet network A Installing Your ControlNet PLC 5 Processor 1 21 ControlNet Connection You can connect programming devices to a ControlNet network through e the ControlNet network access cable 1786 CP e ControlNet 1784 cable e atap on a ControlNet network Examples of ControlNet Connection Types Personal computer Personal computer or other serial device and your HMI or programming software with 1784 KTCX15 card ISA based 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
176. ysical layer device that reconstructs and retransmits all traffic that it hears on one ControlNet segment to another segment Requested Packet Interval RPI the maximum time allowed for the ControlNet network to update requested data The RPI is user selectable on a per connection basis For more information see page 2 2 scheduled maximum node SMAX the maximum ControlNet node number that can transmit and receive scheduled data scheduled transfers deterministic and repeatable transfers that are continuous and asynchronous to the ladder logic program scan scheduled connection types rack connection scheduled connection made from the PLC 5C to 1 0 adapters to some or all of the discrete 1 0 on the adapter module connection scheduled connection made from the PLC 5C to 1 0 adapters to individual modules segment trunkline section of ControlNet network with terminators at each end a segment does not include repeaters segments connected by repeaters make up a link tap component that connects products to the ControlNet trunk cable a tap is required for each node and for each side of a repeater terminator 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 trunk cable bus or central part of the ControlNet cable system trunk cable section length of trunk cable between any two ControlNet taps unschedule

Spec Sheet - The Reynolds Company

Contents

Download Pdf Manuals

Related Search

Related Contents