Home

1785-6.5.22, ControlNet PLC-5 Programmable Controllers, User

1. Programming Terminal Programming Terminal P3 F E OF 1784 KTCx15 tT e 1784 KTC15 or KTCx15 S H S C pr x of or PCC 1786 CP Ig r jess mm al jeee ControlNet 5 ControlNet network PLC 5 sse jses ControlNet jese eee Processor ControlNet network a By rocessor jeee w jeee Using 1770 KFC15 communication interface on coax media Using 1770 KFC15 communication interface and NAP Programming Terminal Programming Terminal D gramming termir o 1770 KFC15 o o0 o pal 1786 CP 60 ial Connection a Connection le 1770 KFC15 jeee 1 Keh jeee Contro Net jeee 1 aa I cool Contro Net ControlNet network sei ControlNet network PLC 5 rin aN rocessor N Jeee jit leee jesi oe jesaj Processor Shown with redundant media redundant media is not required The network access cable 1786 CP can be plugged into any ControlNet product s NAP to provide programming capability on the ControlNet network A programming terminal connected through this cable is counted as a node and must have a unique address 1785 6 5 22 F
2. een Leno 1786 CP mu o mI o nmi 10 1 E a Ol Serial connection i a lt 1770 KFC15 iil Xo Interface i ControlNet Network jeee al Hih Ea eee Ig E 2 O ap PEET TE EEFI t l 1794 ACN15 0 S E i Flex I O Adapter Example of a ControlNet Network without Redundant Media 1771 ACN15 Adapter Data Highway Plus link to PLC 5 40C Serial connection Personal computer or other serial device and your HMI or programming software E _ Personal computer with 1784 KTCx15 card and your HMI or programming software 3 Personal computer with 1784 KTCx15 1784 KTC15 or 1784 PCC card and your HMI or programming software 7 7 U gt 1786 CP it o i it o lt 7 1770 KFC15 a E EU ua Interface ControlNet Network eee Pm HM A jeee eee i I Cyan nial 2 W f 1794 ACNR15 Flex I O Adapter
3. eee Jsem Example of a ControlNet Network with Redundant Media 1771 ACNR15 PLC 5 40C Adapter 1785 6 5 22 February 1999 Converting from a Non ControlNet Remote I O System to a ControlNet 1 0 System Planning to Use Your ControlNet PLC 5 Processor 2 33 Distributed Keeper Functionality All ControINet 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 When you download archived files to a Control Net 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 ona Program files ControlNet for this process Archived from a On channel PLC 5 channel If they fit and are Messaging and 1 O PLC 5 11 PLC 5 40L 0 0 downloaded unchanged e PLC 5 20 PLC 5 60 PLC 5 20C PLC 5 60L e PLC 5 20E PLC 5 80 e PLC 5 30 PLC 5 80C 1A 1A e PLC 5 40 PLC
4. USINGA POWER SUPPLY The default setting is N not using a o MODULE IN power supply module in the chassis g THE CHASSIS h D q L Important You cannot power a single I O chassis with both a power supply module and an external power supply Set Y when you install Set N when you a power supply module use an external in the chassis power supply 17075 Installing Keying Bands You receive plastic keying bands with each I O chassis Insert the for the Processor keying bands as follows t 1 0 Chassis Install a keying band in the left most CORN slot between the following pins Backplane Connector N4 0 40 and 42 9 an i a es e 54 and 56 20 asa guide 24 26 28 Keyi el m ATTENTION A module inserted into a wrong slot NRE mii 1 AN could be damaged by improper voltages connected DTL RK Hn through the wiring arm Use keying bands to prevent 50 damage to the module 52 12062 1785 6 5 22 February 1999 1 8 Installing Your ControlNet PLC 5 Processor Installing and Disposing of the Processor Battery more You can insert or remove the battery without p powering down the processor If you do not want to lose your program make sure that the processor is powered on when removing the battery 1785 6 5 22 February 1999 The 1770 XYC battery ships with the processor and requires special handling For more
5. Allen Bradley ControlNet PLC 5 User Programmable Manual Controllers Cat Nos 1785 L20C15 p h 1 5 L40C15 L80C15 aS L 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 describes 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 responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation with respect to use of information circuits equipment or software described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell
6. 1785 6 5 22 February 1999 Clearing Faults y a ore Appendix E Fault Codes 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 Clearing a major fault does not correct the cause of the fault Be sure to examine the fault bit and correct the cause of 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 1785 6 5 22 February 1999 E 2 Additional Major Fault Codes Fault Codes 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 Co
7. Configuring Your Chapter 3 ControlNet System Programming Your Chapter 4 ControlNet System Using This Chapter ices anchited ae aaa dad Reade Using ControlNet Message Instructions cece eee Multihop Messaging Via the MSG Instruction Option to Close Communication Connection when MSG is Done 4 Understanding the ControlNet PLC 2 Compatibility File Using the ControlNet I O Transfer Instruction 000000 Sending Continuous MesSageS cece cece es 1771 ControlNet Transfers in Plls and STIS ccc cee eee es Using ControlNet Immediate Data Input and Output Instructions Using Selectable Timed Interrupts with a Program on a ControlNet Network 0 cece eee eee e eens Publication 1785 6 5 22 February 1999 Monitoring and Troubleshooting Your ControlNet System Processor Specifications Processor Status File ControlNet Instruction Set ControlNet I O Map Entry Status Words and Error Messages Fault Codes ControlNet Diagnostics File Layout Table of Contents ControlNet PLC 5 Programmable Controllers toc iii Chapter 5 Using This Chapter sasse noui rannan natma e inanan sta sonatas Using the General Status Indicators nnana cece eee ees Using the ControlNet Status Indicators 0c e aaea Using the DH RIO Status Indicators ccc cece eee eee Monitoring ControlNet Configuration and Status 00
8. If you find a problem with our documentation please complete and return this form Pub Name ControlNet PLC 5 Programmable Controllers User Manual Phase 1 5 Cat No 1785 L20C15 L40C15 L80C15 Pub No 1785 6 5 22 Pub Date February 1999 PartNo 955133 55 Check Problem s Type Describe Problem s Internal Use Only _ Technical Accuracy _ text C illustration __ Completeness _ procedure step _ illustration C definition L info in manual What information is missing example __ guideline _ feature accessibility L explanation L other _ info not in manual Clarity What is unclear L Sequence What is not in the right order L Other Comments Use back for more comments Your Name Location Phone Return to Marketing Communications Allen Bradley Co 1 Allen Bradley Drive Mayfield Hts OH 44124 6118Phone 440 646 3166 FAX 440 646 4320 Publication ICCG 5 21 August 1995 PN 955107 82 PLEASE FASTEN HERE DO NOT STAPLE Other Comments PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE OA Rockwell Automation Allen Bradley 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Reach us now at www rockwellauto
9. 1794 CONFIG DATA 1794 SAFE STATE DATA CIP GENERIC 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 I O module writes data to a 1794 I O 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 Data table address in source processor Size of message in words Network address of destination node Slot of destination module Port number set to 2 for the ControlNet network Flags TO forces a transfer to time out EW indicates that the transfer is waiting for an open connection CO transfer is made continuously in Run mode ER 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 Error code indicates the error when the ER bit is set 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 e Minor fault bit 17 14 is set when 32 1771 READ and or 1771 WRITE ClOs are active at a time e As many as 8 1794 Flex I O ClOs can be active at a time e Minor fault bit 17 15 is set when 8 1794 Flex 1 0 CIOs are active at a time
10. 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 6 5 22 February 1999 ControlNet I O Map Entry Status Words and Error Messages 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 so that the 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 an I O connection reduce connections to from this node has the number of I O connections been exceeded e If this is a MSG instruction reduce the number of MSG instructions e If this is a ClO instruction reduce the number of CIO instructions 770 0x0302 SCHEDULED BANDWIDTH NOT There are too many words Edit the I O map table to reduce the AVAILABLE scheduled f
11. Appendix A Appendix B S0 S2 eee ree eee S 36 S 78 eee eee eee Appendix C ControlNet I O Transfer Instruction Message Instructions on a ControlNet Network Immediate Data I O Instructions Instruction Timing and Memory Requirements 005 Appendix D I O Map Entry Status WordS 0 c ccc cece cece eee e eee en Error MESSAGES oe cee eect eee e eee n teen eee e eens Appendix E Clearing Faults 0 0 cece ccc eeceeeeeeeseeeevneenn eens Additional Major Fault Codes 0 0 cece cece eee Appendix F Publication 1785 6 5 22 February 1999 Using This Chapter Installing Your ControlNet PLC 5 Processor If you want to read about Completing the preliminary setup Chapter 1 S s go Q O ore Checking the contents of the processor package Handling the processor Identifying the processor channels connectors Setting the I O chassis backplane switches Setting the I O chassis configuration plug Installing keying bands for the processor Installing and disposing of the processor battery Selecting the Data Highway Plus DH station address of Channel 1A Specifying the serial interface for Channel 0 Selecting the ControlNet network address of Channel 2 Ty fh THT TP Pe Rey Py pay a pe ejj fee HT Ioj IA PN Py Pe Per PROT PM oO Inserting removing the processor into
12. Number of DOF Mappings Files Words Files Words PLC 5 20C 64 2 2000 2 2000 PLC 5 40C 96 3 3000 3 3000 PLC 5 80C 128 4 4000 4 4000 1785 6 5 22 February 1999 File ControlNet Status File Planning to Use Your ControlNet PLC 5 Processor 2 11 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 ControINet processor Table 2 E Files That You Configure with the I O Map for Scheduled I O Usage Description User specified integer data table file containing status information about this processor s scheduled I O map table entries Each I O 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 I O 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 2000 words for the PLC 5 20C processor spanning two contiguous data table files 3000 words for the PLC 5 40C processor spanning three contiguous data table files 4000 words for the PLC 5 80C processor spanning four contiguous data table files This file is typically used for non discrete input data and p
13. 2 slot e Any mix of 8 pt modules 16 pt modules must be 1 0 pairs No 32 pt modules 1 slot e Any mix of 8 or 16 pt modules 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 I O ControlNet Location 1771 A1B A2B A3B A3B1 A4B chassis left most slot Weight PLC 5 20C 3 Ibs 3 oz 1 45 kg PLC 5 40C 3 Ibs 2 oz 1 42 kg PLC 5 60C 3 Ibs 2 oz 1 42 kg PLC 5 80C 3 Ibs 2 oz 1 42 kg Keying Between 40 and 42 Between 54 and 56 Agency Certification e CSA certified When product is marked e CSA Class I Division 2 Groups A B C D certified UL listed CE marked for all applicable directives V N The clock calendar will update appropriately each year including the year 2000 The 1785 CHBM cannot be used with the 1785 5 60C processor The 1785 ME16 cannot be used with ControlNet PLC 5 processors 1785 6 5 22 February 1999 Processor Specifications PLC 5 20C PLC 5 40C PLC 5 60C PLC 5 80C Maximum User Memory Words 16K 48K 64K2 100K Maximum Total Any Mix 512 2048 3072 3072 1 0 Complimentary 512inand512 2048inand 3072inand 3072 in and out 2048 out 3072 out 3072 out Program Scan Time 0 5 ms per K word bit logic 2 ms per K word typical ControlNet 1 0 Transmission Rate 5M bit s Network Update Time NUT 2 1
14. ControlNet I O Transfer CIO instructions 2 3 2 5 ControlNet immediate data 1 0 instructions Immediate Data Input IDI C 2 Immediate Data Output IDO C 2 process ControlNet immediate data 1 0 instructions process 2 8 ControlNet Immediate Data Input IDI instruction ass sel Data Output IDO instruction 2 8 ControlNet network definition of p 2 locating additional information p 4 ControlNet Network Settings fields 2 12 ControlNet PLC5 20C processor 1 4 ControlNet PLC5 40C processor 1 5 ControlNet processor configuring your ControlNet system 3 1 installing 1 1 planning to use 2 1 programming your system 4 1 ControlNet system cabling 1 20 configuring 3 1 changing a 1794 I O module s fault action changing a 1794 I O modules fault idle action 2 5 4 4 configuring nodes 2 8 locating additional information p 4 monitoring 5 1 network maintenance 2 4 network update cycle what happens in 2 4 scheduled operations 2 4 selecting devices to connect 2 31 troubleshooting unscheduled operations using ControlNet PLC 5 processors in 2 31 ControlNet conserving resources 4 3 D Data Input File Index l 3 description 2 11 2 13 Data Output File description 2 11 2 13 Default Configuration File description 2 11 DIF 2 11 p 13 discrete O data transfer definition of p 2 description 2 3 discrete I O data transf
15. PLC 2 UNPROTECTED READ to select a write operation to another PLC 2 processor PLC 2 UNPROTECTED WRITE to select a read operation from another PLC 2 processor enter a PLC 5 data table address Type the PLC 5 data table address 1785 6 5 22 February 1999 4 2 Programming Your ControlNet System If you want to Do this enter the size in Type a number of elements from 1 to 1000 elements enter the destination Type a number from 1 to 99 network address 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 RE yore 1756 CNB 1756 CNB aol 4 Os O8 oo o
16. Status Address Offset This is an offset in the ControlNet status file that points to three words of information on the status of this map table entry Configuration Address and Size This is the offset in a configuration file where configuration data needed if any for this connection is located and the size in words of the data 1785 6 5 22 February 1999 The following table describes the ControlNet network settings Table 2 G ControlNet Network Settings Entry Fields Entry Field Description Network Name User specified name up to eight characters Network Update Time NUT This is the smallest user configurable repetitive time interval in milliseconds at which data can be sent on the ControlNet network This value must be between 2ms and 100ms inclusive This value does not have to be an integer Maximum Scheduled Node This is the highest node that can perform scheduled 1 0 on your ControlNet network This value must be between 1 and 99 inclusive Maximum Unscheduled This is the highest node that can perform unscheduled Node messaging on your ControlNet network This value must be between the Maximum Schedule Node value and 99 inclusive Planning to Use Your ControlNet PLC 5 Processor 2 13 Entry Field Description Media Redundancy Usage This indicates whether you are using e channel A only e channel B only e channels A and B Discrete I O Data Transfer Mapping Regardless
17. 1 ACN ControlNet adapter A Analog Module PS Power Supply X Empty Slot ACN A O A X X All Chassis 2 ACN 0 o Oo A Chassis 3 Input file Input size Outputfile Output size Chassis 1 1 010 5 0 010 8 Chassis 2 1 015 8 0 020 3 Chassis 3 025 7 0 023 3 1785 6 5 22 February 1999 2 28 Planning to Use Your ControlNet PLC 5 Processor 2 slot addressing 16 point modules 1785 6 5 22 February 1999 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 adjacent slots This allows you to set the density of the
18. 6 5 22 February 1999 Appendix F ControlNet Diagnostics File Layout When you specify a Control Diagnostic File in RSNetWorx for the ControlNet network the PLC 520C 5 40C or 5 80CC 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 RSLogixS5 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 Field Names File Offset word bits Buffer Errors 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 Receive
19. Analog Input Modules 2 15 1771 IR RTD Input Modules 1771 IS Multiplexer Input Modules 2 15 1771 IXE Thermocouple Millivolt Input Modules 1771 IXHR Highresolution Thermocouple M illivolt Input Modules 2 15 1771 OF Analog Output Modules 2 15 1771 OFE1 OFE2 and OFE3 Analog Output Modules 2 15 1771 QA Stepper Positioning Modules 2 15 1771 QB Linear Positioning Modules 1771 QC Servo Positioning Modules 2 15 2 16 1771 SN 1 13 1771 VHSC Very Highspeed Counter Modules 2 16 1772 SD SD2 1775 S4A S4B 1775 SRj 1 13 1784 CP 1 16 11 20 1784 CP13 1 16 1 20 1784 CP5 1 16 1 20 1784 CP6 1 16 1 20 1784 CP7 1 16 1 20 1784 CP8 1 16 1 20 1784 KL 1 16 f1 20 Index 1784 KL B 1 16 1 20 1784 KT KT2 1 16 1 20 1784 KTC Communication Card 2 31 1784 KTK1 1 16 1 20 1784 KTx 1 16 1 20 1784 KTxD 1 16 1 20 1784 PCC Communication Card 2 31 1784 PCM5 1 16 1 20 1784 PCM6 1 16 1 20 1784 PCMK 1786 BNC BNC Connector 1 21 1786 BNC BNC Connector 1 21 1 21 1786 BNC BNC Connector 1786 BNCP BNC Connector 1 21 1786 CP 1 18 1786 CP ControlNet Network Access Cable 1 21 1786 CTK ControlNet Tool Kit 1 21 1786 RG6 Quad Shield Cable 1786 RPA Repeater 1 21 1786 TPVS Tap 1 21 1786 TPYR Tap 1786 TPYS Tap 1 15 1786 XT BNC Terminator 1 21 179
20. B 6 Processor Status File This fault code Indicates this fault And the fault is 41 NXT instruction with missing FOR Non recoverable the fault routine will be 42 You tried to jump to a non existent label executed but cannot clear 43 File is not an SFC Malor fau bie 44 Error using SFR This error occurs if e 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 tried 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 I O configuration e
21. Guidelines 1770 4 1 1785 6 5 22 February 1999 1 16 Installing Your ControlNet PLC 5 Processor Connecting a You can connect a programming terminal to a Contro Net PLC 5 Programming Terminal processor via a e DH connection e serial channel e ControlNet connection DH Connection To attach a programming terminal to a ControlINet PLC 5 processor using a DH connection s f o o 00 o 00 q a A l 6 i ot Programming Terminal Programming Terminal PLC 5 20C PLC 5 40C 5 80C DH Link Processor DH Link Processor When ake this Use this cable communication card 1784 KT KT2 1784 CP6 1784 KL KL B 1784 CP with 1784 CP7 adapter 1784 CP8 adapter 1784 KTK1 1784 CP5 with 1784 CP7 adapter 1784 KTx KTxD 1784 CP13 1784 PCMK 1784 PCM6 1784 PCM5 with 1784 CP7 adapter 1785 6 5 22 February 1999 If your programming terminal has a 9 pin serial port 25 pin serial port Installing Your ControlNet PLC 5 Processor 1 17 Serial Channel To program the processor using Channel 0 configure the channel for RS 2
22. Your ControlNet PLC 5 Processor Instructions Immediate I O ControlNet and Remote 1 0 001 IN _ 001 0T _ Table 2 C ControlNet Immediate Data Transfer Operations Description 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 I O chassis is used This value is moved from the private memory buffer to the working data table and is used in all subsequent ladder instructions This data could be as old as the time taken since the last asynchronous O update and it may not actually reflect the latest state of the input word In the case of an IOT the current state of the specified output word is copied to the private memory buffer and is used on the next output update to the I O chassis The actual change is not communicated until the next asynchronous 1 0 transfer Only 1 word of I O data can be updated per instruction ControlNet Immediate Data 1 0 IDI IMMEDIATE DATA INPUT Data file offset 232 Length 10 Destination N11 232 IDO IMMEDIATE DATA OUTPUT Data file offset 175 Length 24 Source N12 175 The ControlNet Immediate Data 1 0 instructions work in much the same way as the immediate I O instructions During an input instruction the most recent data is copied from the private memory buffer to a data table address that you specify In the case of an output instruction the data is cop
23. Your ControlNet System 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 IDI is in progress and they both operate on the same set of data the integrity of that block of data is jeopardized To ensure data block integrity write your STI routine so that it operates on its own copy of the data block that it needs Use ControlNet Immediate Data I O instructions IDO and IDI within your STI to copy the needed block of data out to and back from a temporary location that is different from that used by the normal data table For detailed information about STIs see your programming software documentation 1785 6 5 22 February 1999 Using This Chapter Using the General Status Indicators BATT Chapter 5 Monitoring and Troubleshooting Your ControlNet System If you want to read about See page Using the general status indicators Using the ControlNet status indicators Monitoring the ControlNet configuration and status screens The general status indicators inform you of the general operational state of the processor Os Indicator Color Description Probable Cause Recommended A
24. and error messages Append HAEE Fault codes Append ControlNet diagnostics file layout Appendi 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 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 5 40C and 5 80C processors phase 1 5 connection opened communication path between two nodes on a ControlNet network Data 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 I O data transfer type of data transfer in which single units of I O have discrete relationships with values in the processor s data table uses the processor s input and output image tables I and O files configured on a per node basis in the ControlNet I O map table 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 O map table table that you c
25. angle T tap Right angle Y tap Q eN 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 If your Connect the tap s straight or network supports right angle connector Nonredundant media Redundant media S nonredundant media to the channel A connector on the A rail processor channel B is not used redundant media e from trunk cable A to channel A B j on the processor and le ee 7 e o I e from trunk cable B to channel B ud l on the processor Pate 1 Rockwell Automation recommends using channel A for aia jeson nonredundant media i For detailed information about planning and installing your a 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 Coax Tap Installation Instructions 1786 2 3 ControlNet Network Access Cable Installation Instructions 1786 2 6 ControlNet Repeater Installation Instructions 1786 2 7 Industrial Automation Wiring and Grounding
26. away Multiple multicast connections are allowed e exclusive owner where configuration data from all owners must agree New connections that do not match existing connection s configuration are rejected A second exclusive owner is not allowed e redundant owner where configuration data from all owners must agree New connections that do not match existing connection s configuration are rejected An exclusive output owner connection after redundant owner connections exist are not allowed These connection types are supported by the following e 1747 and 1771 connection types support exclusive owner and multicast for rack and module connections e 1794 connection types support exclusive owner redundant owner and multicast for rack and module connections Multiple redundant owners are allowed each device in the rack can be owned only once exclusively Peer to peer connection types support multicast for receive data connections Input Address and Size This is the offset in the input file where the data is to be stored and the number of words to be received from the input device Any connection type may be mapped to either the discrete input image table or the Data Input File DIF Output Address and Size This is the offset in the output file where the data is located and the number of words of the output transfer Any connection type may be mapped to either the discrete output image table or the Data Output File DOF
27. 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 plack integrity in the case of Selectable Times Interrupts STIs See pagg 4 8 IDO Data file offset Length Source IMMEDIATE DATA OUTPUT 175 24 N12 175 Immediate Data Output IDO If the input conditions are true an immediate data output is initiated that updates the private memory output buffers from the source file before the next normal output image update The Data file offset 175 is the offset into the buffer where the data is stored The Length 24 identifies the number of words in the transfer it can be an immediate value ranging from 1 to 64 or a logical address that specifies the number of words to be transferred The Source N12 175 is the source of the words to be transferred The Source should be the matching data table address in the DOF except when you use the instruction to ensure data block integrity in the case of Selectable Timed Interrupts STIs See pagg 4 8 Instruction Timing and Memory Requirements Time us Category Code Title integer Words of Memory True False Imm
28. e 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 e No transfer is initiated when the processor is in Program mode Transfers that have been running with the CO bit set automatically restart on the Program to Run transition when the Continue Last step bit is set and the data table has not changed A transfer has a maximum size of 64 words As long as an adapter is owned by a processor any processor within the ControlNet network can send or receive transfers to or from any of that adapter s modules If the SFC startover bit is set in the processor configuration file continuous ClOs may time 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 paged 4 3 find C 1 for more information 1785 6 5 22 February 1999 2 6 Planning to Use Your ControlNet PLC 5 Processor Operation Description Features Peer to peer Messaging MSG Instructions 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 t
29. 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 Repeaters High voltage ac amp dc 1786 RPT Low voltage dc 1786 RPTD 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 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 BNC jack Terminators BNC 75Q 1786 XT 1 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 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 1785 6 5 22 February 1999 1 22 Installing Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 ae mor For detailed information about ControlNet cabling see the following publications Publication Sri ControlNet Cable System Component List AG 2 2 ControlNet Cable System Planning and Installation Manual 1786 6 2 1 ControlNet C
30. planning and installing your Contro Net network see the following publications Publication Publication Number ControlNet Cable System Component List AG 2 2 ControlNet Coax Cable System Planning and Installation Manual 1786 6 2 1 ControlNet Coax Tap Installation Instructions 1786 2 3 ControlNet Network Access Cable Installation Instructions 1786 2 6 ControlNet Repeater Installation Instructions 1786 2 7 ControlNet System Overview 1786 2 12 ControlNet PLC 5 Hot Backup System User Manual 1785 6 5 24 Industrial Automation Wiring and Grounding Guidelines 1770 4 1 For more information about the above publications contact your local Rockwell Automation sales office or distributor Table of Contents Installing Your ControlNet Chapter 1 PLC 5 Processor Using This Chapter i334 ssh sshd sod sasdrordyosyosdao vows B fore Yo 03 0 rr eee meet CEPON OCET cre metre Handling the PROGOSSON ics 5 5 a x a8 sia Kea a a aaar aaa aaa aaa Compliance to European Union Directives 00 eaaa EMC DIAC iareoiia niitti iat AE E e Low Voltage Directive va ccccxcaxrcereK aks anne Identifying ControlNet PLC 5 Processor Components Setting the I O Chassis Backplane Switches aaan aaa Setting the I O Chassis Configuration Plug anaana Installing Keying Bands for the ProcesSOr cece eee aes Installing and Disposing of the Processor Battery 05 Inst
31. the ControlNet I O status file ControlNet I O Connection Bit 9 of First Word Second Word Third Word Type of I O Status File Entry of I O Status File Entry of I O Status File Entry Connection Error 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 xis clear then the module in slot xis OK If bit xis set then the module in slot x is missing bad or is the wrong type 1747 Analog Clear If bit xis clear then the module in slot xis OK If bit xis set then the module in slot x is missing bad or is the wrong type 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 1785 6 5 22 February 1999 D 4 ControlNet I O Map Entry Status Words and Error Messages ControlNet I O Connection Bit 9 of First Word Second Word Third Word Type of I O Status File Entry of I O Status File Entry of I O Status File Entry Connection Error 1794 Discrete Clear 0 If bit xis clear then the module in slot xis OK If bit x is set then the module in slot xis missing bad or is the wrong type 1794 Analog Read Clear 0 If bit xis clear then the module in slot xis OK If bit x is set th
32. to the network data table 1785 6 5 22 February 1999 4 8 Programming Your ControlNet System IDO IMMEDIATE DATA OUTPUT Data file offset 175 Length 24 Source N12 175 An IDO is initiated that updates the private memory output buffer from the source file before the next normal output image update The Data File Offset 175 is the offset into the buffer where the data is stored The Length 24 identifies the number of words in the transfer or a logical address that specifies the number of words to be transferred The Source N12 175 is the source of the words to be transferred The Source should be the matching data table address in the DOF except when you use the instruction to ensure data block integrity in the case of Selectable Timed Interrupts STIs See page 4 9 N12 0 Data Table more 1785 6 5 22 February 1999 N12 175 175 IDO instruction copies from the data table to the private DOF buffer Outputs transmitted to the ControlNet network on next opportunity For more detailed information about writing ladder programs and programming ControINet I O transfers using Immediate Input IN and Immediate Output IOT instructions see your programming software documentation Using Selectable Timed Interrupts with a Program on a ControlNet Network ore Programming
33. 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 ControlNet 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 et 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 I O map entry PCSC New Data Bit S 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 targe
34. 0 ot o Bj Bl E E ControlBus ControlNet Link 1 ControlNet Link 2 1785 6 5 22 February 1999 For more detailed information about writing ladder programs and using message instructions see your programming software documentation Multihop 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 aData Highway Plus device by bridging across the 1756 CNB R and 1756 DHRIO modules e an Ethernet device by bridging across the 1756 CNB R and 1756 ENET modules Refer to your programming software documentation for information about configuring multiphop messages Using the ControlNet 1 0 Transfer Instruction Programming Your ControlNet System 4 3 Option to Close Communication Connection when MSG is Done This feature allows you to configure the ControlNet ladder MSG instruction to close its communication connection when the message operation is done thus conserving ControlNet resources on low duty rate messages Do this by setting the NC configuration bit in the ladder MSG control file Understanding the ControlNet PLC 2 Compatibility File When a PLC 2 command is received from the ControlNet network the ControlINet PLC 5 processor uses the user specified file as the PLC 2
35. 00 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 I O Map Entries 64 96 128 128 Maximum DIF DOF Size 2000 words 3000 words 4000 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 Remote I O 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 23 23 Maximum Number of Remote 1 0 Devices 12 60 92 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 1 Rw nN The PLC 5 40C processor has a limit of 32K words per data table file The PLC 5 60C processor has a limit of 56K words per program file and 32 K words per data table file The PLC 5 80C processor has a limit of 56K words per program file and 32 K words per data table fi
36. 11 MCP does not exist or is not a ladder or SFC file 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 J SR instruction as the means to jump to the fault routine file To use the J SR instruction enter the fault code number 0 9 an immediate value 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 J SR SBR instructions You do not have to use the user defined fault codes to generate your own fault If you program a J SR 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 o
37. 12Slots 16 Slots 2 Slot 2 4 s 1 Slot 4 8 D F 1 2 Slot 8 16 J 5 1785 6 5 22 February 1999 2 10 Planning to Use Your ControlNet PLC 5 Processor The programming software reserves non ControlNet Remote I O output and input image space according to these guidelines e It does not overlap processor resident local I O reserved image space e It addresses input and output image space offset in octal from 00 37 for the PLC 5 20C processor 00 177 for the PLC 5 40C processor 00 277 for the PLC 5 80C processor e The output image offset value in the I O map corresponds to the first slot of the referenced chassis i 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 0 12 and O 13 to slots 0 1 2 and 3 respectively e 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 i 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 I 10 3 or 1 13 Mapping ControlNet Data Transfer The following table shows the maximum I O map entries allowed in the ControlNet I O map table Table 2 D Maximum I O Map Entries Processor Number of Number of DIF Number of DIF Number of DOF
38. 1D INVALID TARGET TAG The PLC 5C is requesting data from Change the PLC 5C I O 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 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 producted 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 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 I O map table to show the entered in the map table correct module type and slot 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 1785 6 5 22 February 1999 D 10 ControlNet I O Map Entry Status Words and Error Messages Decimal Hex Code Error Message Explanation Possible Cause s P
39. 32C using DF1 point to point protocol s A Use cable Os Os 1784 CP10 00 00 1784 CP11 a ae 9 j Programming Terminal Programming Terminal a J TR PLC 5 20C PLC 5 400 5 60C Processor 5 80C Processor 1785 6 5 22 February 1999 1 18 A Installing Your ControlNet PLC 5 Processor ATTENTION Do not connect the same communication card to both the NAP and a tap on the ControlNet network ControlNet Connection You can connect programming devices to a ControlNet network through e the ControlNet network access cable 1786 CP e atap ona ControlNet network Using 1784 KTCx15 communication card on coax media E Using 1784 KTC15 or KTCx15 or PCC communication card and NAP
40. 4 Flex I O datatransfer mapping 2 16 1794 Flex I O datatransfer mapping 2 16 1794 ACN ControlNet Flex I O Adapter 2 31 1794Generic Module 2 16 1794 IE4XOE2 A Analog I O Modules 2 16 1794 IE4X0E2 B Analog I O Modules 1794 IE8 A Analog Input Modules 2 17 1794 IE8 B Analog Input Modules 2 17 1794 IRS A RTD Input Module 2 17 1794 ITS A Thermocouple Millivolt Input Module 1794 OE4 A Analog Output Modules 2 17 1794 0E4 B Analog Output Modules Publication 1785 6 5 22 February 1999 l 2 Index 6008SQH1 SQH2 1 13 A Actual Packet Interval descri otion 2 12 API 2 12 automatic 1 0 mapping 2 8 avoiding electrostatic damage 1 3 B battery compartment location of on PLC5 20C1 4 on PLC5 40C 1 5 battery life 1 9 cables remote I O cabling 1 20 Channel 1A Channel 1B 2 33 Cl0s 2 3 Closing ControlNet communication 4 3 communication time slice communication connection closing 4 3 communication ports location of on PLC5 20C 1 4 on PLC5 40C 1 5 communication option to close 4 3 connecting a programming terminal 1 16 connecting to a ControlNet network connection definition of p 2 Conserving ControINet resources 4 3 ControlNet cabling ControlNet communication closing 4 3 ControlNet 1 0 error messa ges D 4 features 1 files configured with map Data Input File DIF 2 11 2 13 Data
41. 5 80E PLC 5 40C PLC 5 40E PLC 5 20 PLC 5 40L 1B 1B e PLC 5 20C PLC 5 60 PLC 5 20E PLC 5 60L e PLC 5 30 PLC 5 80 e PLC 5 40 PLC 5 80C PLC 5 40C PLC 5 80E PLC 5 40E e PLC 5 20C PLC 5 80C 2 2 e PLC 5 40C 1785 6 5 22 February 1999 2 34 Planning to Use Your ControlNet PLC 5 Processor Can berunona Program files ControlNet for this process Archived from a On channel PLC 5 channel If they fit and are Messaging and I O PLC 5 11 e PLC 5 40L 1A 2 performed by the ControlNet network you continued PLC 5 20 PLC 5 60 must make these changes manually by PLC 5 20C PLC 5 60L reprogramming PLC 5 20E PLC 5 80 PLC 5 30 PLC 5 80C PLC 5 40 PLC 5 80E PLC 5 40C PLC 5 40E PLC 5 20 e PLC 5 40L 1B 2 PLC 5 20C PLC 5 60 PLC 5 20E e PLC 5 60L PLC 5 30 PLC 5 80 PLC 5 40 PLC 5 80C PLC 5 40C PLC 5 80E e PLC 5 40E e PLC 5 40 PLC 5 80 2A or 2B 2 e PLC 5 60 1A or 1B performed by DH or remote I O you must make these changes manually by reprogramming PLC 5 20E e PLC 5 60L 2 1A or 1B performed by DH or remote I O you must e PLC 5 40E PLC 5 80E make these changes manually by PLC5 40L reprogramming gt 2 performed by the ControlNet network you must make these changes manually by reprogramming gt gt These include processor files data table files and port configurations If you do not update the program th
42. 85 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 nodeis 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 If this is an I O connection reduce CONNECTIONS connections to from this node has the number of I O connections been exceeded If this is a MSG instruction reduce the number of MSG instructions e If this is a ClO instruction reduce the number of CIO instructions
43. Automation is prohibited Throughout this manual we use notes to make you aware of safety considerations ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you e identify a hazard e avoid the hazard e recognize the consequences Important Identifies information that is especially important for successful application and understanding of the product Ethernet is a registered trademark of Intel Corporation Xerox Corporation and Digital Equipment Corporation ControlNet is a trademark of ControlNet International Data Highway Plus DH RSNetWorx FLEX I O PLC PLC 2 PLC 3 PLC 5 PLC 5 11 5 20 5 20C 5 26 5 30 5 40 5 46 5 40L 5 40C 5 60 5 60L 5 80 5 80C 5 86 5 20E 5 40E and 5 80E are trademarks of Rockwell Automation Allen Bradley is a trademark of Rockwell Automation a core business of Rockwell International Corporation New Information wore Summary of Changes Summary of Changes The information below summarizes the changes to the ControlNet PLC 5 Programmable Controllers User Manual To help you find new and updated information look for the revision bars as shown to the left of this paragraph The following table and paragraphs describe new features updated existing features and where to find this new information For This New Information See
44. ControlNet MSGs to DH and Ethernet Devices Chapter 4 ControlNet Unsolicited MSGs to RSLinx Option to Close Connection when MSG is Done Processor Specifications Appendif A 1 0 Map Entry Status Words Appendig D Error Messages ControlNet Diagnostics File Layout Append F ControlNet Hot Backup You can pair together two ControlNet processors either a PLC 5 40C or 5 80C and assign one of the processors as the primary controller and the other as a secondary backup controller The 1785 CHBM ControlINet Backup Cartridge is required for each processor For more information refer to the ControINet PLC 5 Hot Backup System User Manual publication 1785 6 5 24 Catalog Number 1785 L60C15 This release of the ControlNet PLC 5 Programmable Controllers does not include the 1785 L60C15 however only the new information in this user manual as highlighted above does not apply to the previous release of the 1785 L60C15 1785 6 5 22 February 1999 Preface Preface Introduction This manual describes how to install your processor and how to plan for configure and use the features of a PLC 5 20C PLC 5 40C or PLC 5 80C programmable controller that are unique to the ControlNet network When we refer to ControlNet processors in this manual we mean the phase 1 5 processors e 1785 L20C15 e 1785 L40C15 e 1785 L80C15 For detailed information about features that th
45. 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 I O 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 I O map table 263 0x0107 CONNECTION NOT FOUND The connection at the target node Make sure I O map entries exist in does not exist the I O 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 itis 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 a rack with the correct number of slots 273 0x0111 INVALID RPI The target node cannot produce the
46. INet documentation Table 2 H 1771 Non discrete I O Data Transfer Mapping Valid Valid Valid Input Output Configuration Module Type Description Sizes Sizes Sizes 1771 CFM 1771 CFM Configurable 0 41 0 4 14 24 0 4 14 24 34 Flowmeter Module 34 44 48 44 48 52 56 52 56 60 60 771 DB PLC Basic Module 0 64 0 64 0 64 771 DE 1771 DE Absolute Encoder Module 0 2 0 5 10 15 0 5 10 15 20 20 22 22 771 Generic 1771 Generic Module 0 64 0 64 0 64 771 IE 1771 IE Analog Input Module 1 8 771 IF 1771 IF Analog Input Module 1 64 771 IFE A 1771 IFE A Analog Input Module 5 20 0 3 37 771 IFE B 1771 IFE B Analog Input Module 5 22 0 3 37 39 771 IFE C 1771 IFE C Analog Input Module 5 22 0 3 37 39 771 IJ 1771 I Encoder Counter Module 0 1 0 3 0 3 771 IK 1771 IK Encoder Counter Module 0 1 0 3 0 3 771 IL A 1771 IL A Isolated Analog Input Mod 5 12 0 2 19 771 IL B 1771 IL B Isolated Analog Input Mod 5 15 0 2 19 36 37 771 IR A 1771 IR A RTD Input Module 3 8 0 2 8 14 771 IR B 1771 IR B RTD Input Module 3 9 0 2 8 14 15 771 18 1771 1 Multiplexer Input Module 1 7 771 IXE A 1771 XE A Thermocouple Millivolt 4 12 0 1 19 27 Input Module 771 IXE B 1771 XE B Thermocouple Millivolt 4 13 0 1 19 27 28 Input Module 771 IXHR 1771 IXHR High resolution 4 13 0 3 19 27 28 Thermocouple Millivolt Input Module 771 OF 1771 OF Analo
47. 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 I O 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 I O map table 278 0x0116 REVISION MISMATCH The series revision of the target Replace the target node module node module does not match the with the correct node module series revision entered in the map table Correct the I O map table 1785 6 5 22 February 1999 ControlNet I O Map Entry Status Words and Error Messages 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 O 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 ControlNet hot backup Refer to PLC 5 40C or 5 80C publication 1785 6 5 24 for more information Verify that the 17
48. Industrial Environment e EN 50082 2 EMC Generic Immunity Standard Part 2 Industrial Environment Low Voltage Directive This product is tested to meet Council Directive 73 23 EEC Low Voltage by applying the safety requirements of EN 61131 2 Equipment Requirements and Tests For specific information required by EN 61131 2 see the appropriate sections in this publication as well as the following Rockwell Automation publications e Industrial Automation Wiring and Grounding Guidelines For Noise Immunity publication 1770 4 1 e Guidelines For Handling Lithium Batteries publication AG 5 4 e Automation Systems Catalog This equipment is classified as open equipment and must be installed mounted in an enclosure as a means of providing safety protection 1785 6 5 22 February 1999 1 4 Installing Your ControlNet PLC 5 Processor Identifying ControlNet PLC 5 Figure 1 1 and F igure 1 2 show the front panels of the ControlNet Processor Components PLC 5 processors Figure 1 1 PLC 5 20C Processor Front Panel af Battery Status Indicator Red Keyswitch selects processor moe gt O Processor RUN FAULT Status Indicator sti 1 0 Status Indicator Green Red Force Status Indicator Channel 2 ControlNet Status Indicators Amber Green Red Channel 0 Communication ACTIVE ControlNet Network Acces
49. O adapter e DH communication e unused Channel 0 is optically coupled provides high electrical noise immunity and can be used with most RS 422A equipment as long as e termination resistors are not used e the distance and transmission rate are reduced to comply with RS 423 requirements 1785 6 5 22 February 1999 1 6 Installing Your ControlNet PLC 5 Processor Setting the 1 0 Chassis Set the I O chassis backplane switches using a ball point pen to set Backplane Switches each switch Important Do not use a pencil because the tip can break off and short the switch Switch i Last State ON Outputs of this I O chassis remain in their last state when a hardware failure occurs OFF Outputs of this I O chassis are turned off when a hardware failure occurs Always OFF Switches 7 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 ON ON EEPROM memory transfers to processor memory if processor memory not valid an ON OFF EEPROM memory does not transfer to process
50. Output File DOF 2 11 2 13 Default Configuration File 2 11 Publication 1785 6 5 22 February 1999 O Status File 2 11 0 forcing 2 6 immediate datatransfer operations 2 7 map table creating 2 8 entries 2 8 mapping scheduled data transfers 2 8 maptable entry maptable entry fields 2 11 2 12 scheduled datatransfer operations 2 2 2 3 scheduled discrete O data transfer 2 2 scheduled operations discrete I O data transfer non discrete I O data transfer peer to peer communication 2 3 understanding 2 1 unscheduled datatransfer operations 2 3 unscheduled nondiscrete 1 0 data transfer 2 3 unscheduled operations ControlNet I O Transfer CIO instruction description C 1 ControlNet I O Transfer CIO instructions description features 2 5 I O transfer instructions programming 4 3 immediate data 1 0 instructions programming 4 6 ladderrung messages 2 3 messaging from programming devices 2 3 nondiscrete I O data transfer 2 5 nondiscrete I O data transfers 2 5 description features peer to peer messaging 2 3 2 6 peer to peer messaging instructions 4 1 programming ControlNet I O automatic mapping 2 8 ControlNet I O mapping automatic 2 8 reserving rack space for remotel O linked racks before mapping 2 8 understanding 2 8 discrete 1 0 datatransfer mapping 2 13 mapping data transfers non discrete I O datatransfer mapping
51. PLC 5 Processor 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 trunk cable length depends on the communication rate of the link see Table Table 1 4 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 ll Data Highway 485 Cable Installation Manual publication 1770 6 2 2 1785 6 5 22 February 1999 To insert remove the processor into from the chassis do the following ATTENTION Make certain that power to the chassis is off before inserting or removing the processor Locking To insert a processor into the chassis Bar 1 Lift the locking bar and the ejector tab eas Ejector 2 Slide the processor into the left most slot of the F 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 ee 3 Disconnect all c
52. X 0 X 0 Discrete Input Module O 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 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 without slot e allows optimization of I O image table but complementary not to the extent if using slot complementary does not waste chassis slots can put any module anywhere provided 1 0 table exists for that slot optimize with slot complementary e allows complete optimization of th
53. a 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 6 5 22 February 1999 2 20 Planning to Use Your ControlNet PLC 5 Processor Clearing the PCSC New Data and PCSC Overflow Bits If it is crucial to maintain the integrity of the PCSC overflow bit while clearing the PCSC new data and overflow bits then do the following 1 Disable process control sample complete by setting the PCSC enable bit for the connection to zero When process control sample complete is disabled the system will not modify the new data and overflow bits while you clear them 2 Clear the PCSC new data and the PCSC overflow bits 3 Reenable process control sample complete by setting the connection s PCSC ena
54. able trunk cable bus or central part of the ControlNet cable system trunk cable section length of trunk cable between any two ControlNet taps unscheduled 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 This icon indicates that the current topic is MORE discussed further in the I publication s referenced 1785 6 5 22 February 1999 P 4 Preface Related PLC 5 Publications Related ControlNet Publications 1785 6 5 22 February 1999 The 1785 PLC 5 programmable controller and ControlNet documentation is organized into manuals according to the tasks that you perform Publication Publication Number Enhanced PLC 5 Processor System Overview 1785 2 36 Enhanced and Ethernet PLC 5 Programmable Controllers User 1785 6 5 12 Manual ControlNet PLC 5 Programmable Controllers User Manual 1785 6 5 22 ControlNet Cable system Planning and Installation Manual 1785 6 2 1 ControlNet PIC 5 Programmable Controllers Quick Start 1785 10 6 1785 PLC 5 Programmable Controllers Quick Reference 1785 7 1 For more information about 1785 PLC 5 programmable controllers or the above publications contact your local Rockwell Automation sales office or distributor For detailed information about different aspects of
55. ables from the processor s ports 4 Lift the locking bar and the ejector tab and then slide the processor from the chassis 19898 Install a remote I O link using 1770 CD cable and either a daisy chain or trunk cable drop cable configuration 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 4 Correct Cable Length Based on Communication Rate A remote I O 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 1 524 m approximately 5 000 ft 230 4K bit s 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 150Q or 82Q terminator Installing Your ControlNet PLC 5 Processor 1 13 The maximum number of logical rack Use this physical devices numbers that you resistor thatyou can connect 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 82Q 32 16 6008 SQH1 SQH2 Adapters 1771 AS 1771 ASB Series A Only 1771 DCM M
56. alling or Removing the Processor Battery 04 Replacing the Battery acter knee eee Rae RRR eo aR ae eg Disposing of the Battery ccc cece eee eee eens Selecting the DH Station Address of Channel 1A Specifying the Serial Interface of Channel0 000004 Selecting the ControlNet Network Address of Channel 2 Inserting Removing the Processor into from the I O Chassis Installing a Remote I O LINK 0 00 ccc eee cece teens Installing a DER LINK i died a elieie etter lind teed lei teed toda dele i Connecting to a ControlNet Network ccc cece eee eee Connecting a Programming Terminal nauuna aaeanoa DHH CONNECCION sarrosa sranna rara AA Serial CHANG vacwcavawe eee wa eae we see eee E ControlNet Connection 0 c cece cece Selecting Appropriate Cables 1 0 ccc cece eee eee Seral Cables anaa a A A I A E A DH Programming Cables 0 0 ccc cece ee eens Remote WO Cables naana CONMOINGECGDIGS 05sec taketh Peta Re ex anaia Planning to Use Your ControlNet Chapter 2 PLC 5 Processor Using This Chapter sea dete lcancie neg laxonct nnn eed nce neececa hea Sad Understanding ControlNet I 0 0c ccc cece cece eed Scheduled Data Transfer Operations on a ControlNet Network 2 2 Unscheduled Data Transfer Operations on a ControlNet Network 2 Using I O Forcing Operations s sears 5 dacacadacsearSrateatat a
57. assis 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 1 011 0 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 First Rule of Module Optimization Planning to Use Your ControlNet PLC 5 Processor 2 25 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 O Discrete Output Module ACN ControlNet adapter X Empty Slot 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 b
58. ata Highway II Data Highway 485 Cable Installation Manual publication 1770 6 2 2 1785 6 5 22 February 1999 Use 1770 CD cable to connect the processor to a DH link Follow these guidelines while installing DH communication links e do not exceed these cable lengths OOR trunk cable length 3 048 m approximately 10 000 cable ft drop cable length 30 4 m approximately 100 cable ft do not connect more than 64 stations on a single DH link 82w or 150w resistor Ke A 3 33 PLC 5 40C PLC 5 20C 5 60C or 5 80C Processor Processor E i lt Clear lt t Clear g a Shield lt a Shield i r Blue L F lt a Blue A 82w or 150w resistor 19339 Connecting to a ControlNet Network Remove the tap s dust cap located on the straight or right angle connector and set it aside Installing Your ControlNet PLC 5 Processor 1 15 Connect a ControlINet PLC 5 processor to a ControlNet network via a tap with a 1 m 39 4 in drop cable Four taps are available from Rockwell Automation Straight T tap Straight Y tap Right
59. ata 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 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 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 dat
60. ble bit back to one Understanding Multicast Inputs Information can be included in each ControINet processor s I O map table to indicate a multicast connection A processor will originate a connection to receive inputs from the adapter and a heartbeat connection to keep the connection alive when you specify a multicast connection Multicast is supported for the following types of connections e 1747 discrete input e 1747 non discrete input e 1771 discrete input e 1771 non discrete input e 1794 discrete input e 1794 non discrete input e scheduled peer output or send data In the following example the ControINet 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 Heartbeat Connection ControlNet PLC 5 Processor Node 1 Point to Point Outputs ControlNet PLC 5 ControlNet PLC 5 Processor oe Adapter Processor Node 2 Node 3 Node 4 1785 6 5 22 February 1999 Multicast Inputs Using I O Mapping Techniques Planning to Use Your ControlNet PLC 5 Processor 2 21 Merged 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 nee
61. ccept 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 performing I O updates too frequently performing immediate ControlNet I O ladder instructions too frequently Recoverable Reduce the number of ControlNet I O map table entries Possible ways using a discrete rack connection instead of multiple discrete module connections combining multiple 1 0 racks into a single I O 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 I O map table Increase your ladder program scan by either adding more logic or by increasing the Communications Time Slice 8 77 Reduce the number or frequency of immediate ControlNet I O 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 I O connections Recoverable Delete one or more I O map table entries and reaccept edits for the ControlN
62. ccor seatraca Using Immediate Data Transfer Operations 0005 Publication 1785 6 5 22 February 1999 toc ii Table of Contents ControlNet PLC 5 Programmable Controllers Understanding ControlNet I O Mapping cc eee eee Reserving Space for Non ControlNet O ccc cece ee ees Processor Resident Local 0 ccc cece cece eens POMOC One i cahs Geka raha Kakainearakakeeakadnnia Mapping ControlNet Data Transfer 000 e eee es Discrete I O Data Transfer Mapping cee eee eas Non discrete O Data Transfer Mapping Multiple Processors Can Control I O on the Same ControlNet Link 0545 bs saataasasasa aa 1771 Modules anuna 1794 Modules anuna Other ControlNet Processors eee eee eee eee eed Using Process Control Sample Complete naaa aaa Clearing the PCSC New Data and PCSC Overflow Bits Understanding Multicast Inputs aoaaa Merged Save Functionality aaa Using I O Mapping Techniques cce cece enaa Understanding Discrete Mapping sseeeeeeeeeeeed Optimizing the I O Image Table ccc eee eee eed Optimizing the I O Image Table without Slot Complementary Optimizing the I O Image Table with Slot Complementary Converting from a Non ControlNet Remote I O System to a ControlNet I O System cece eee eed Converting from ControlNet Phase 1 0 or 1 25 to ControlNet Phase 1 5 scenssesceaceane ace aan ace ace
63. 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 Example 1 Examine the following chassis ACN OJI 0 0 0 Discrete Input Module O Discrete Output Module ACN ControlNet adapter In this example the first input module uses eight inputs from the first slot and eight inputs from the second slot not used by the output module in the second slot 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 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 output cards However in most cases there are not the same number of each module 2 slot addressing 16 point modules Planning to Use Your ControlNet PLC 5 Processor 2 29 Example 2 Examine the following chassis ACN OJI 0
64. cks of data transferred to or from I O modules use integer input and output data table files that you specify scheduled transfers are configured in the ControlNet I O map table unscheduled transfers make use of ControlNet I O Transfer CIO instructions owner device that controls the outputs of an adapter redundant media dual cable system that allows you to receive the best signal over a ControlNet network repeater two port active physical 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 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 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 c
65. compatibility file All PLC 2 commands received from the ControlNet network use the same PLC 2 compatibility file The ControINet PLC 5 processor uses the value stored in S 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 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 S 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 S 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 S 73 between 3 and 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 6 5 22 February 1999 4 4 Programming Your ControlNet System 1785 6 5 22 February 1999 If you want to Do this change the command type Select one of the followi
66. ction BATT Red Battery low Battery low Replace battery within 10 days Off Battery is good Normal operation No action required FORCE COMM 1785 6 5 22 February 1999 5 2 Monitoring and Troubleshooting Your ControlNet System 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 blinking being transferred to EEPROM Red Major fault Run time error e Check major fault bit in status blinking file S 11 for error definition e Clear fault bit correct problem and return to run mode Alternatin Processor in Normal operation if No action required allow flash gRedand FLASH memory processor s FLASH update to complete Green programming mode memory is being reprogrammed Processor FLASH Contact your local A B memory checksum representative for a field firmware error update Red Major fault e Processor e Clear memory and reload steady memory has program checksum error e Check backplane switch settings Memory module and or insert correct memory error module Internal Power down reseat processor diagnostics have and power up then clear failed memory and reload your program Replace EEPROM with new program then if necessary replace the processor Off Processor is in Check power supply and program load or test connections mode or
67. cts processor mode y lt x Processor RUN FAULT Status Indicator ControlNet I O Status Indicator Green Red Green Red z Ox Force Status Indicator Channel 2 ControlNet Status Indicators Amber Green Red ControlNet Network Access Port NAP R 45 connector y Channel 0 Communication ACTIVE FAULT Status Indicator gt Green Red e os Channel 2 gt e gt ControlNet Redundant Media Ports e lt _ Channel 0 BNC dedicated Se Serial Port 25 pin D shell supports standard EIA rs paene 3 e RS 232C and RS 423 is RS 422A compatibleD Se 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 J er Pen a Pp DH Programming Terminal Connection to Chantel 1A 9 gt D DFI point to point one stop bit 8 pin mini DIN parallel with 3 pin connectors 08 e 2400 bps e BCC error check of Channel 1A use only when Channel 1A is e no parity e no handshaking configured for DH communications O Channel 1A z gt m Memory Module Space 3 pin default is DH configurable for 7 e remote I O scanner J e remote I O adapter 5 e DH communication m unused UEN lt Battery Compartment Channel 1B 3 pin default is remote I O scanner configurable for e remote I O scanner e remote I
68. d 13 07 00 Lonely Occurrences 13 15 08 1785 6 5 22 February 1999 F 2 ControlNet Diagnostics File Layout 1785 6 5 22 February 1999 Field Names File Offset word bits Collisions 14 07 00 Noise Hits 14 15 08 Moderators from non lowmen 15 07 00 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 Interface 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 Reserved 24 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 42 timeouts Current number of active MSG instructions 43 always less than or equal to 32 Maximum number of simultaneously active MSG 44 instructions 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 ac
69. d 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 Color Probable Cause Recommended Action Off Internal diagnostics failed 1 Turn power off make sure ControlNet address L and h is not 00 reseat processor then power up A B 2 Clear memory and reload your program 3 Replace EEPROM with new program 4 If still an 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 6 5 22 February 1999 5 4 Monitoring and Troubleshooting Your ControlNet System Indicator Color Probable Cause Recommended Action 7 7 Off Channel disabled No action required A or B Configure for ControlNet communication Steady Normal operation No action required Green Flashing Temporary er
70. d 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 More 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 if a message error is detected if you reset the message CO bit 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 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 PI or STI program file 1785 6 5 22 February 1999 4 6 Programm
71. d of Stores the status file 2 07 Not defined 2 08 2 09 Last state 0 outputs are turned off 1 outputs retain last state 2 11 I O chassis addressing 2 12 bitl2 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 sies S 3 to S 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 S 7 Global status bits See also 27 S 32 33 34 and 35 7 0 7 rack fault bits for racks 0 7 e 7 8 15 unused S 8 Last program scan in ms S 9 Maximum program scan in ms S 10 Minor fault word 1 See also S 17 S 10 00 Battery is low replace in 1 2 days S 10 01 DH active node table has changed S 10 02 STI delay too short interrupt program overlap S 10 03 memory module transferred at power up S Processor Status File B 3 This word of the status file sies S 10 04 Edits prevent SFC continuing data table size changed during program mode reset automatically in run mode S 10 05 nvalid 1 0 status file S 10 06 reserved S 10 07 No more command block
72. d to change are required to be in Program mode This feature requires RSNetWorx for ControINet version 1 6 or later During the save operation RSNetWorx gives you two options e Optimize schedule for all connections RSNetWorx recalculates the ControlNet schedule for all the nodes on the ControINet 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 e Merge changes into existing schedule RSNetWorx merges the pending changes into the current ControlNet 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 All 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 ControlINet network parameters such as NUT maximum scheduled address maximum unscheduled address or media redundancy do not change Performing a download via RSNetWorx still requires all the processors to be in Program mode Discrete I O interfaced to a PLC 5 processor is typically mapped to the I O image table in phase 1 0 it had to be mapped to the I O image table You can map discrete I O to the DIF and DOF but you lose
73. de within the chassis 1794 non discrete I O data transfer 0 7 the slot number is always the physical location in the 1794 rack e peer to peer communication 1 to the maximum number of I O map entries see Table 2 D on page 2 10 the message number must be the same for both processors involved Module Message Type This allows you to specify the module type or peer to peer message type Receive Data From or Send Data in offline and online programming It also determines how the map table entries are configured for the different modules and peer to peer messages Requested Packet Interval RPI Set this to the maximum time allowed for the network to update the requested data This value must be at least as large as the network update time NUT 1785 6 5 22 February 1999 2 12 Planning to Use Your ControlNet PLC 5 Processor Map Table Entry Field Description Actual Packet Interval API This read only field displays the actual time it takes for the network to update the requested data The API is the largest binary multiple of the Network Update Time smaller or equal to the RPI Connection Type This is the connection type The valid types are multicast where at least one owner connection must configure a device before any listeners can be accepted and at least one owner connection must be present at all times If all owner connections go away Communication to all multicast connections go
74. detailed information about installing and disposing of the battery see the Allen Bradley Guidelines for Lithium Battery Handling and Disposal publication AG 5 4 ATTENTION To maintain CSA certification for hazardous areas do not substitute any other battery for the 1770 XYC Installing or Removing the Processor Battery To install or remove the battery follow these steps 1 Remove the thumb screw on the processor s battery cover remove the cover and locate the battery 2 Install or remove the battery To install the battery slide the battery side connector into the processor side connector until you hear them snap p To remove the battery press the lever on the battery side connector and slide the connectors apart S P sas Battery side connector Processor side connector 3 Replace the battery cover and secure the battery cover with the thumb screw 4 On the battery cover write the date that you installed the last new battery gt You can insert or remove the battery without powering down the processor If you do not want to lose your program make sure that the processor is powered on when replacing the battery Installing Your ControlNet PLC 5 Processor 1 9 Replacing the Battery Replace the lithium battery every year or when the BATT status indicator is red For estimated battery lifetimes see the table below Worst Case Battery Life Estimates Processor Temperature Po
75. dicates 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 6 5 22 February 1999 Processor Status File B 9 This fault code 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 a
76. dule 1 4 2 1 RPI Default 4 x NUT 2 RPI Range 2 12 800 ms Other ControlNet Processors ControlNet scheduled peer to peer communications between ControlNet processors require one map table entry per message You can set up ControlNet peer to peer communications between any two processors on a ControlNet network The ControlNet transfer mechanism makes it possible to map the scheduled peer to peer messages listed in Table 2 J Table 2 Peer to Peer Communications Mapping Message Type Description Valid Sizes Receive Data Scheduled Message From 1 240 Send Data Scheduled Message RPI Default 4 x NUT 2 RPI Range 2 12 800 ms To communicate between any ControlNet PLC 5 processors on the ControlNet network you can include explicit MSG instructions in your ladder logic program See paged d llandC 1 4 1 and diC 1 ff or more information 1785 6 5 22 February 1999 2 18 Planning to Use Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 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 communication Your data table files and private buffers are synchronized during housekeeping
77. e 1 0 image table can waste chassis slots and require additional chassis can only put modules in odd or even slots depending on the module type 1785 6 5 22 February 1999 2 30 Planning to Use Your ControlNet PLC 5 Processor 2 slot addressing 16 point modules 2 slot addressing 16 point modules 2 slot addressing 16 point modules 1785 6 5 22 February 1999 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 Oo O Discrete Input Module O Discrete Output Module ACN ControlNet adapter Using strict rules of optimization you might immediately arrange the chassis like this ACN Ol O Discrete Input Module O Discrete Output Module ACN ControlNet adapter However the overall system may be heavy on inputs and there are no concerns about the output image table In this case you may wan
78. e ControlNet processor will fault You must change block transfer instructions for the ControlNet system from the standard block transfer read BTR and block transfer write BTW instructions to scheduled transfers or to unscheduled CIO instructions You must edit non ControlNet PLC 5 programs containing references to the 1 0 Status File for use with I O connected via the ControlNet network Information regarding ControlNet status is stored in a separate data file that you specify through the programming software If you do not update the program the data table locations corresponding to the missing 1 0 devices will not be updated V N Converting from ControlNet Phase To convert ControlNet phase 1 0 or 1 25 to ControlNet phase 1 5 1 0 or 1 25 to ControlNet Phase 1 5 contact your local Rockwell Automation sales office or distributor 1785 6 5 22 February 1999 y a MORE Chapter 3 Configuring Your ControlNet System Use the following software packages to configure your ControlNet system Use To RSNetWorx for ControlNet define ControlNet network parameters such as e network update time media redundancy e physical media configuration e maximum scheduled nodes e maximum unscheduled nodes monitor I O map entry status RSLogix5 enter user program files create delete monitor data table files enter module configuration e enter channel 0 1A 1B and 3 configuration e ad
79. e PLC 5 20C 5 40C More and 5 80C programmable controllers share with the PLC 5 20 5 40 5 80 processors see the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication 1785 6 5 12 Audience The information in this manual is intended for engineers and technicians who are installing programming and maintaining a control system that includes a PLC 5 20C 5 40C or 5 80C programmable controller You should have a background in control system applications and a basic knowledge of e programmable real time control systems the PLC 5 control system e your operation s required systems and applications Contents If you want to read about Go to Installing your ControlNet PLC 5 processor Chapter 1 Setting switches Installing communication links Planning to use your ControlNet PLC 5 processor Chaptef 2 Understanding ControlNet 1 0 Using a ControlNet PLC 5 processor Using programming software to configure your ControlNet system Chapter 3 Programming your ControlNet system Chaptel 4 Monitoring and troubleshooting your ControlNet system Chaptef 5 Using the status indicators Processor specifications Appendi A 1785 6 5 22 February 1999 Terminology Preface Term Actual Packet Interval API If you want to read about Go to Processor status file Append ControlNet instructions Append ControlNet I O map table entry status words
80. ebruary 1999 ATTENTION Use the 1786 CP cable when connecting a programming terminal to the network through a NAP Using a commercially available RJ style cable could result in network failure Selecting Appropriate Cables This section lists information about e serial cables e DHt programming cables e remote I O cables e ControlNet cables Installing Your ControlNet PLC 5 Processor 1 19 For more information about cables see the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication You can make your own serial cables or purchase them from 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 14 NOT USED TXD OUT SEND COM 15 16 NOT USED RXD IN REC COM 17 18 19 NOT USED RTS OUT NOT USED 20 DTR OUT DTR OUT DTR OUT 21 22 NOT USED DSR IN NOT USED 23 NOT USED DTR OUT NOT USED 24 25 ore 1785 6 5 12 Serial Cables Rockwell Automation Pin RS 232C RS 422A RS 423 1 C GND C GND C GND 2 TXD OUT TXD OUT TXD OUT 3 RXD IN RXD IN RXD IN 4 RTS OUT RTS OUTt RTS OUT 5 CTS IN CTS INt CTS IN 6 DSR IN DSR IN DSR IN 7 SIG GND SIG GND SIG GND 8 DCD IN DCD IN DCD IN 9 10 NOT USED DCD IN NOT USED 11 12 13 NOT USED CTS IN NOT USED The shading indicates that the pin
81. ediate 1 0 IDI Immediate Data 400 11 2 Input IDO Immediate Data 400 1 1 2 Output 1785 6 5 22 February 1999 Appendix D ControlNet I O Map Entry Status Words and Error Messages I O 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 scheduled I O usage It contains status information about all of the ControlNet network s scheduled T 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 CSC Overflow Bit CSC New Data Bit CSC Enable Bit First Word 08 Reset ine Reserved Bit Data Invalid Bit eee Reserved Inhibit Bit ___ Connection Error Bit System Bits User Bits Second and Third Words 15 14 13 12 1i 10 09 08 07 06 05 04 03 02 01 00 Error Messages 15 14 13 12 iLi 10 09 08 07 06 05 04 03 02 01 00 1785 6 5 22 February 1999 Bit Number 00 ControlNet I O Map Entry Status Words and Error Messages Description Reset Bit The following table explains the bits in the first word of the ControlNet I O status file Use 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
82. eer 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 2000 words for the PLC 5 20C processor spanning two contiguous data table files 3000 words for the PLC 5 40C processor spanning three contiguous data table files 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 I O data transfer configuration data This configuration data is sent to the target device each time the connection is opened Map Table Entry Field Node Table 2 F ControlNet I O Map Table Entry Fields Description This is the node s ControlNet network address Slot Symbol Message Numbers The slot message value takes on different meanings with the different communication options 1747 1771 and 1794 discrete I O data transfer the slot value does not apply because the mapping granularity is based on the physical chassis 1747 non discrete O data transfer 0 29 the slot number is always the physical slot location inside the 1746 chassis 1771 non discrete I O data transfer 0 15 the slot number is always the physical slot location inside the 1771 chassis regardless of addressing mo
83. en 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 x is clear then the module in slot x is OK If bit x is set then the module in slot x is missing bad or is the wrong type 178 5 6 5 22 February 1999 Error Messages ControlNet I O Map Entry Status Words and Error Messages D 5 The following is a list of ControlNet error codes messages possible causes and possible corrective actions 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 I O map table The map table is corrupted Reenter the I O map entry that is failing The target node of the MSG Edit the ladder program so that the instruct
84. er macpingy te disposing of the processor battery 1 9 por 2 1 1 drop cable definition of p 2 E error codes D 4 Expected Network Packet Time 1771 non discrete I O datatransfer mapping F files configuration 2 12 configured with I O map for scheduled I O usage O Status 1 0 status input 2 12 processor status frame definition of p 2 front panel PLC 5 20C processor 1 4 PLC 5 40C processor 1 5 G global status bits racks 07 B 2 racks 1017 B 11 Publication 1785 6 5 22 February 1999 l 4 Index H handling the processor 1 3 l 0 ControWet 2 1 automatic mapping 2 8 discrete I O data transfer mapping 2 13 files configured with map Data Input File DIF 2 11 2 13 Data Output File DOF 2 11 P 13 Default Configuration File 2 11 I O Status File I O forcing 2 6 immediate data transfer 2 7 map table creating 2 8 entries maximum number of entries 2 10 mapping 2 8 mapping data transfers 2 11 p 12 map table entry 2 12 map table entry fields non discrete I O datatransfer mapping 2 13 reserving rack space for remotel O linked racks before mapping 2 8 scheduled data transfer 2 2 scheduled discrete I O data transfer 2 2 scheduled operations discrete I O data transfer 2 3 non discrete I O data transfer 2 3 peer to peer communication unscheduled I O data transfer inst
85. ers 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 ClOs condition the rung to be true for only one scan Instruction MSG SEND RECEIVE MESSAGE Control block MG10 10 Message Instructions on a ControlNet Network Message MSG 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 NC No Cache Bit Description If the input conditions go from false to true the data is transferred according to the instruction parameters you set when you enter the message instruction The Control Block MG10 10 contains status and instruction parameters You cannot use N integer control blocks on the ControlNet network For continuous MSGs condition the rung to be true for only one scan 1785 6 5 22 February 1999 C 2 Immediate Data 1 0 Instructions Instruction IDI ControlNet Instruction Set Data file offset Length Destination IMMEDIATE DATA INPUT 232 10 N11 232 Immediate Data Input IDI Description If the input conditions are true an immediate data input is initiated that updates the destination file from the private buffers before the next normal input image update The Data file offset 232 is where the
86. et configuration 1785 6 5 22 February 1999 B 10 Processor Status File 13 24 1785 6 5 22 February 1999 This word of Stores the status file 13 Program file where fault occurred 14 Rung number where fault occurred 15 VME status file S 16 1 0 status File S 17 Minor fault word 2 See also S 10 17 00 BT queue full to remote 1 0 17 01 Queue full channel 1A maximum remote block transfers used S 17 02 Queue full channel 1B maximum remote block transfers used 17 03 Queue full channel 2A maximum remote block transfers used S 17 04 Queue full channel 2B maximum remote block transfers used 17 05 No modem on serial port 17 06 e Remote I O rack in local rack table or e Remote I O 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 I O image tables are smaller than 64 words 8 racks each 17 07 Firmware revision for channel pairs 1A 1B or 2A 2B does not match processor firmware revision 17 08 ASCII instruction error S 17 09 Duplicate node address 17 10 DF1 master poll list error 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 CIOs 18 Processor cloc
87. et 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 Planning to Use Your ControlNet PLC 5 Processor 2 9 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 configure non ControINet Remote I O on your processor Addressing Number of Words Reserved we 4Slots 8 Slots
88. f 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 T 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 I O network the inputs in that chassis automatically map to 020 1 027 if the node is on a remote I O 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 1 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 to 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 regardle
89. fers on a per node basis in the I O map table Non discrete I O Data Transfer Handled with the same priority as discrete I O data transfer You can update analog data without using block transfer instructions in ladder programs You do this by including non discrete I O data transfer configurations in the I O map table This data is updated in the buffers and data table files between logic scans in the same manner as that used in discrete I O data transfer Peer to peer Communication Allows a ControlNet processor to communicate with any other ControlNet processor on the ControlNet network with the same priority as that of the discrete and non discrete I O data transfers discussed above 1 While scheduled data transfer is asynchronous to program scanning all data is presented synchronously to the processor and output buffers 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 non discrete I O data transfers through ControlNet T O Transfer CIO instructions e peer to peer messaging through Message MSG instructions e messaging from programming devices 1785 6 5 22 February 1999 2 4 Planning to Use Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 The ControlNet system places your sched
90. from the I O chassis 1 12 Installing a remote 1 0 link Installing a DH link Connecting to a ControlNet network Connecting a programming terminal Selecting appropriate cables 1 19 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 6 5 22 February 1999 1 2 Installing Your ControlNet PLC 5 Processor Before You Begin 1785 6 5 22 February 1999 More Before installing your ControINet PLC 5 processor 1 Complete the following e determine the proper environment e configure the proper grounding e route the conductors properly For detailed information about completing these tasks see the Enhanced and Ethernet PLC 5 Programmable Controllers User Manual publication 1785 6 5 12 2 Check your processor package and make sure that you have the following ControlNet PLC 5 Programmable Controller Eipcesoe 1785 L20C15 L40C15 L60C15 or L80C15 N Contents of Tray 1 Lithium Battery 1770 XYC 1 DIN connector cover 4 Terminating resistors 1509 20or4 Terminating resistors 829 2or4 3 pin connectors 2 Keys 1 Battery cover with screw 1 1784 CP7 cable adapter for 1784 CP CP5 cables ControlNet PLC 5 Programmable Controllers Quick Documentation Start publication number 1785 10 6 Identified by four colored bands brown green brown and gold T
91. g Output Module 0 1 4 60 771 OFE 1771 OFE Analog Output Module 0 5 1 5 13 0 5 13 771 QA 1771 QA Stepper Positioning Module 1 10 771 OQB 1771 QB Linear Positioning Module 1 33 771 OC 1771 QC Servo Positioning Module 1 14 1785 6 5 22 February 1999 2 16 Planning to Use Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 Valid Valid Valid Input Output Configuration Module Type Description Sizes Sizes Sizes 1771 SN 1771 SN Sub I O Scanner Module 0 7 63 0 7 63 1771 VHSC 1771 VHSC Very High speed 0 4 26 0 2 4 12 0 2 4 12 20 Counter Module 20 24 29 24 29 34 39 34 39 44 44 49 54 59 49 54 59 64 64 N Series 1771 N Series Analog Module 0 0 2 9 59 0 2 9 59 20 28 1 RPI Default 4 x NUT 2 RPI Range 2 12 800 ms For newly released modules or modules that can have multiple configurations but only one configuration is being used you can use the generic module type and specify the input and or output sizes 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 the modules listed in Table 2 H fas well as with other 1771 analog modules you can also include explicit CIO instructions in your ladder logic program See pages 4 3 and C 1 for more information The 1771 discrete rack must be
92. he 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 1785 6 5 22 February 1999 F 4 ControlNet Diagnostics File Layout Bit s Description Values 7 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 1785 6 5 22 February 1999 Numerics 1203 FM1 A SCANport Module 2 16 1770 CD 1 14 f 20 1770 KFC Communication Interface 2 31 1771 Generic 1771 NSeries Analog Modules 1771 ACN and ACNR ControlNet I O Adapters 1771 AF 1 13 1771 AS 1 13 1771 ASB 1 13 1771 CFM Configurable Flowmeter Modules 2 15 2 16 2 17 1771 DCM 1771 DE A Absolute Encoder Modules 2 15 1771 IE IF and IFE Analog Input Modules 2 15 1771 l and IK Encoder Counter Modules 1771 IL Isolated
93. he 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 Network address of destination processor Data table address in destination processor Port number set to 2 for the ControlNet network Flags TO forces a message to time out EW 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 Error code indicates the error when the ER bit is set As many as 32 ControlNet MSGs can be active at a time inor fault bit S 17 13 is set when 32 ontrolNet 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 oz See paged 4 1 and C 1 for more information Because connections are opened and closed as
94. ied from an area that you specify to the private memory buffer and sent on the next I O update As many as 64 words can be transferred per instruction Important In most cases you should set the Data file offset and the Source of an IDO or the Data file offset and the Destination of an IDI to the same address See pagd 4 5 for more information on this and other aspects of using ControlNet IDI and IDO instructions Understanding ControlNet I O Mapping 1785 6 5 22 February 1999 All scheduled data transfers must be mapped on a ControlINet 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 on page 2 17 for information about ControINet automatic configuration and I O mapping Reserving Space for Non ControlNet I O Non ControlNet processor resident local I O and Remote I O devices can only use fixed I O image locations based on rack number for discrete I O data transfer while discrete I O data transfer between ControlN
95. ing Your ControlNet System Using ControlNet You can use two instructions for immediate data input and output on a Immediate Data Input and ControlNet network Immediate Data Input IDI and Immediate Output Instructions Pare Capa IDI IMMEDIATE DATA INPUT if Data file offset 232 Length 10 Destination N11 232 IDO IMMEDIATE DATA OUTPUT Data file offset 175 Length 24 Source N12 175 1785 6 5 22 February 1999 IDI IMMEDIATE DATA INPUT Data file offset 232 Length 10 Destination N11 232 Programming Your ControlNet System 4 7 In the previous example an IDI is initiated that updates the destination file from the private buffer before the next normal input image update The Data File Offset 232 is the offset into the buffer where the data is stored The Length 10 identifies the number of words in the transfer it can be an immediate value ranging from to 64 or a logical address that specifies the number of words to be transferred The Destination N11 232 is the destination of the words to be transferred The Destination should be the matching data table address in the DIF except when you use the instruction to ensure data block integrity in the case of Selectable Timed Interrupts STIs See page 4 9 N11 0 0 Data Table Private DIF Buffer N11 232 232 lt lt IDI copies from Inputs arrive from the private DIF the ControlNet buffer
96. ion is not a processor or the correct target node is used target node of the CIO instruction is not the correct I O adapter Replace the target node with the correct type of node 12 0x000C OBJ ECT 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 Ox000E 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 6 5 22 February 1999 D 6 ControlNet I O Map Entry Status Words and Error Messages Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 38 0x0026 INVALID DESTINATION The map table is corrupted Reenter the I O map entry that is ADDRESS SIZE failing The target node of the MSG
97. ion1 1 preparing for 1 2 removing the processor from the chassis 1 12 selecting cables ControlNet cables 1 20 DH programming 1 20 remote 1 0 1 20 serial 1 19 selecting the ControlNet network address 1 11 selecting the DH station address of Channel 1A setting the I O chassis backplane switches 1 6 setting the 1 0 chassis configuration plug 1 7 specifying the serial interface of Channel 0 instructions ControlNet I O Transfer CIO 2 5 C 1 how to use 4 3 when to use 2 16 2 34 ControlNet Immediate Data Input ID 2 8 c 2 how to use 4 6 ControlNet Immediate Data Output ID0 2 8 how to use 4 6 ControlNet Message MSG how to a Immediate Input maal Immediate Output IOT 2 8 Message MSG 2 how to use when to use oT 2 8 K keyswitch location of on PLC 5 20C 1 4 on PLC 5 40C 1 5 L ladder rung messaging 2 3 link definition of p 2 M map table 2 8 map table entries 2 8 2 11 map table entry p memory module Spa Message instructions MSGs 2 3 multicast 2 20 N NAP p 2 Network Access Port definition of p 2 2 32 6 4 1JC 1 Index l 5 when to use 1 18 network address definition ofp Network Update Interval 2 4 definition glial Network Update Time definition of p 2 node definition of p 2 non discrete I O data transfer non discrete I O datatransfer
98. is not receiving power FORCE Amber SFC and or I O forces Normal operation No action required steady 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 6 5 22 February 1999 Using the ControlNet Status Indicators Monitoring and Troubleshooting Your ControlNet System 5 3 yO 6 ia FL Indicator The ControlNet status indicators inform you of the operational state of the ControlNet network Indicator Color Description Probable Cause Recommended Action 0 Off ControlNet I O not Normal operation if No action required present or not Channel 2 not being used operating Steady All nodes configured Normal operation No action required Green in the ControlNet map table present and operating properly 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 Re
99. is reserved This processor s serial port can support these configurations Digital Interface RS 232C Maximum Cable Length 15 m approximately 50 ft RS 422A compatible 61 m approximately 200 ft RS 423 61 m approximately 200 ft 1785 6 5 22 February 1999 1 20 Installing Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 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 When using this pare Use this cable communication card 1784 CP6 1784 CP with 1784 CP7 adapter 1784 CP8 adapter 1784 KT KT2 1784 KL KL B 1784 KTK1 1784 CP5 with 1784 CP7 adapter 1784 KTx KTxD 1784 CP13 1784 PCMK 1784 PCM6 1784 PCMS5 with 1784 CP7 adapter Remote 1 0 Cables Use 1770 CD or cable for remote I O See page 1 12 for more information ControlNet Cables Several types of RG 6 quad shield cable may be appropriate for your ControlNet installation depending on the environmental factors associated with your application and installation site Installing Your ControlNet PLC 5 Processor 1 21 The following ControlNet cable system components are available
100. iscellaneous 1771 AF Connects to any device listed below Scanners 1771 SN 1772 SD SD2 1775 SR S4A S4B 6008 SQH1 SQH2 1502 16 16 Adapters 1771 AS 1771 ASB Series A Only 1771 DCM Miscellaneous 1771 AF 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 I O connectors of the processor e daisy chain to the connector screw terminals on the remote I O connectors of the processor and then to the remote I O screw terminals of the next remote I O device To connect remote I O cable 1 Run the 1770 CD cable from the processor to each remote I O adapter module or processor in the remote I O system 2 Connect the signal conductor with blue insulation to the 3 pin connector terminal labeled 1 on the processor and to each remote I O adapter module or PLC 5 adapter in the remote I O system 3 Connect the shield drain wire to the center terminal of the 3 pin connector 4 Connect the signal conductor with clear insulation to the 3 pin connector terminal labeled 2 5 Tie wrap the remote I O network cable to the chassis to relieve strain on the cable Gee OOB O Q 6 Terminate the remote 1 0 link by connecting an external ter
101. k year 19 Processor clock month S 20 Processor clock day S 21 Processor clock hour S 22 Processor clock minute Processor Status File B 11 This word of Stores the status file 23 Processor clock second S 24 Indexed addressing offset S 25 Reserved S 26 S 35 This word of Stores the status file S 26 User control bits S 26 00 Restart continuous SFC when reset processor restarts at first step in SFC When set processor continues with active step after power loss or change to RUN S 26 01 Start up protection after power loss when reset no protection When set processor sets major fault bit S 11 5 when powering up in run mode S 26 02 Define the address of the local rack when reset local rack address is 0 When set local rack address is 1 S 26 03 Set complementary I O series A only when reset complementary I O 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 S 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 sof
102. le The PLC 5 80C processor has 64K words of total data table space For more information see the ControlNet Cable System Planning and Installation Manual publication 1786 6 2 1 1785 6 5 22 February 1999 Appendix B Processor Status File S 0 2 Processor status data is stored in data file 2 This word of Stores the status file S 0 Arithmetic flags e bit 0 carry bit 1 overflow bit2 zero e bit3 sign 1 Processor status and flags 1 00 RAM checksum is invalid at power up 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 to memory module 1 11 Performing online programming 1 12 Not defined 1 13 User program checksum calculated 1 14 Last scan of ladder or SFC step 1 15 Processor running first program scan or the first scan of the next step in an SFC 2 Switch setting information 2 00 Channel 1A DH station number through 2 05 2 06 Channel 1A DH baud rate 0 57 6 kbps 1 230 4 kbps 1785 6 5 22 February 1999 B 2 Processor Status File S 3 10 1785 6 5 22 February 1999 This wor
103. ll 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 ControINet Increase your Network Update Time and or increase the Requested Packet Intervals for PLC 5 processor can parse it i scheduled data transfers in your I O map table performing I O updates too frequently Raha diate ControlNet 1 0 ladder instructions t e Increase your ladder program scan by either r aming immediate ControlNet I O ladder instructions too adding more logic or by increasing the requengy Communications Time SLice S 77 Reduce the number or frequency of immediate ControlNet I O 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 I O connections Delete one or more I O map table entries and reaccept edits for the ControlNet configuration 1785
104. lot 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 I O 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 I O 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 in the module type correct slot of the target node An incorrect module or slot was Edit the I O 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
105. mapping 2 14 2 15 nonredundant media 1 15 NUI p 2 2 4 NUT p 2 0 Option to Close Communication 4 3 owner definition off p 3 P PCMCIA Communication Card 2 31 Peer In 2 17 Peer Out 2 17 aoe PLC 5 programming so tware p 4 Process Control Sample Complete 2 18 processor front panel PLC5 20C 1 4 PLC5 40C 1 5 processor status file B 1 layout B 1 processor resident local 1 0 2 9 programming a processor through Channel 0 1 17 programming terminal connecting redundant media definition of p remote 1 O Publication 1785 6 5 22 February 1999 l 6 Index cable lengths 1 12 nonControlNet 2 9 remote O immediate 1 0 transfers 2 7 4 8 repeater definition ofj p 3 replacing a non ControlNet remote 1 0 network with a ControlNet network 2 8 12 33 2 34 replacing the processor battery 1 9 Requested Packet Interval 1771 non discrete I O datatransfer mapping 1794 Flex I O data transfer mapping 2 17 description 2 11 RPI 2 11 S scheduled data transfer operations 2 2 2 3 scheduled discrete I O data transfer process 2 2 scheduled peer to peer communication 2 3 scheduled peer to peer communications scheduled peer to peer communications mapping EA scheduled transfers definition off p 3 screens Instruction Entry for ControlNet I O Transfer Block 4 31 Instruction Entry for Message Block 4 1 segment defi
106. mation com Wherever you need us Rockwell Automation brings together leading brands in industrial automation including Allen Bradley controls Reliance Electric power transmission products Dodge mechanical power transmission components and Rockwell Software Rockwell Automation s unique flexible approach to helping customers achieve a competitive advantage is supported by thousands of authorized partners distributors and system integrators around the world Americas Headquarters 1201 South Second Street Milwaukee WI 53204 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Rockwell European Headquarters SA NV avenue Herrmann Debroux 46 1160 Brussels Belgium Tel 32 2 663 06 00 Fax 32 2 663 06 40 Asia Pacific Headquarters 27 F Citicorp Centre 18 Whitfield Road Causeway Bay Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Automation 1785 6 5 22 February 1999 PN 955133 55 Supersedes Publication 1785 6 5 22 J une 1997 1999 Rockwell International All Rights Reserved Printed in USA
107. minator resistor between the remote I O terminals labeled 1 and 2 PLC 5 20C Processor __ OO PLC 5 40C 5 60C 5 80C Processor 1770 CD Ble Ble lt Shield a o Shield gt a J C d To another I O Clear aE Clear a E resistor link device 1770 CD sg Terminate both ends of a remote 1 0 link 1785 6 5 22 February 1999 1 14 Installing Your ControlNet PLC 5 Processor Installing a DH Link Use the 3 pin connector on the processor to connect a DH link The connector s port must be configured to support a DH communication link You can install a DH link two ways trunk cable drop cable from the drop cable to the connector screw terminals on the DH connectors of the processor daisy chain to the connector screw terminals on the DH connectors of the processor To make connections 1 Connect the signal conductor with clear insulation to the 3 pin connector terminal 1 at each end of each cable segment 2 Connect the shield drain wire to the center terminal of the 3 pin connector at both ends of each cable segment 3 Connect the signal conductor with blue insulation to the 3 pin connector terminal 2 at each end of each cable segment 5 mor For more information see the Data Highway Data Highway Plus D
108. minister passwords and privileges For information about using these software packages see the online help systems for RSNetWorx for ControlNet and RSLogix5 software 1785 6 5 22 February 1999 3 2 Configuring Your ControlNet System Notes 1785 6 5 22 February 1999 Using This Chapter Using ControlNet Message Instructions Chapter 4 Programming Your ControlNet System If you want to read about using Go to page ControlNet message instructions ControlNet 1 0 transfer instructions ControlNet immediate data input and output instructions Using Selectable Timed Interrupts STIs in a program on a ControlNet network You can use the Message MSG instruction and the MG data type to send message commands over the ControlNet system within the local ControlNet link PLC 5 TYPED WRITE PLC 5 TYPED READ PLC 3 WORD RANGE READ PLC 3 WORD RANGE WRITE PLC 2 UNPROTECTED READ PLC 2 UNPROTECTED WRITE Use your programming software to go to the instruction entry for message block screen If you want to change the command type Do this Select one of the following PLC 5 TYPED WRITE to Select a write operation to another PLC 5 processor PLC 5 TYPED READ to Select a read operation from another PLC 5 processor PLC 3 WORD RANGE READ to select a write operation to another PLC 3 processor PLC 3 WORD RANGE WRITER to select a read operation from another PLC 3 processor
109. 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 segment 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 6 5 22 February 1999 B 8 This fault code 201 Processor Status File In
110. mputer 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 I O Adapters Allows the ControlNet processor remote access to Allen Bradley s family of ACNR15 SLC designated I O modules via a ControlNet network 1771 ACN15 1771 ControlNet I O Adapters Allows the ControlNet processor remote access to Allen Bradley s family of ACNR15 1771 designated 1 0 modules via a ControlNet network 1794 ACN15 1794 ControlNet Flex I O Adapters Allows the ControlNet processor remote access to Allen Bradley s family of ACNR15 1794 designated 1 0 modules via a ControlNet network There are other products available for information about these products contact your local Rockwell Automation sales office 1785 6 5 22 February 1999 2 32 Personal computer or other serial device and your HMI or programming software a Planning to Use Your ControlNet PLC 5 Processor Personal computer with 1784 KTCx15 card and your HMI or programming software ey Personal computer with 1784 KTCx15 1784 KTC15 or 1784 PCC card and your HMI or programming software
111. n 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 the fault routine will be 31 You did not enter enough subroutine parameters executed but cannot clear a 7 major fault bit 2 32 You jumped to an invalid non ladder file J 33 You entered a CAR routine file that is not 68000 code 34 You entered a negative 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 7 Se 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 6 5 22 February 1999
112. n processor resident local rack 0 Illegal 1 4 slots 2 12 slots 3 8 slots 4 16 slots S 77 Communication time slice for communication housekeeping functions in ms S 78 MCP I O update disable bits Bit 0 for MCP A Bit 1 for MCP B etc This word of Stores the status file S 79 MCP inhibit bits Bit 0 for MCP A Bit 1 for MCP B etc S 80 S 127 MCP file number MCP scan time in ms MCP max scan time in ms The above sequence applies to each MCP therefore each MCP has 3 status words For example word 80 file number for MCP A word 81 scan time for MCP A word 82 maximum scan time for MCP A word 83 file number for MCP B word 84 scan time for MCP B etc 1785 6 5 22 February 1999 Instruction ClO CNET I O TRANSFER Control block CT21 50 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 ControlNet I O Transfer Instruction ControlNet I O 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 Description If the input conditions go from false to true the data is transferred according to the instruction paramet
113. n 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 J SR instruction into word 12 of the processor status file 5 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 6 5 22 February 1999 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 instruct 11 Bad user program checksum the processor to clear the D Badi d fi fault and then resume 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 expressio
114. needed more can exist in a program as long as no more than this number are active at one time 2 See Appendix D for a list of ControlNet error codes Using I O 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 non discrete I O data is not supported For detailed information about forcing see your programming software documentation 1785 6 5 22 February 1999 Planning to Use Your ControlNet PLC 5 Processor 2 7 Using Immediate Data Transfer Operations ControlNet Immediate Data I O transfers Immediate Data Input IDI and Immediate Data Output IDO perform similarly to the Remote I O supported immediate I O transfers Immediate Input AIN and Immediate Output OT 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 lt Immediate Data Transfer gt Private Data Memory Table Buffers Data Update Files ControlNet Data Transfer Program Scan m yu 5 Scheduled Data Transfer lt Neca yee Bowes p Unscheduled Data Transfer 1785 6 5 22 February 1999 2 8 Planning to Use
115. ng 1771 READ reads input data from 1771 non discrete I O module 1771 WRITE writes output data to 1771 non discrete I O module 1794 READ reads data from a 1794 I O module 1794 WRITE writes data to a 1794 I O module 1794 FAULT ACTION Changes the action that a module takes when it faults 1794 IDLE ACTION Changes the action that a module takes when it is idle 1794 CONFIG DATA Changes a module s configuration data CIP GENERIC sends user specified CIP service enter a PLC 5 data table address Type the data table address enter the size in elements Type the number of elements s 1 for 1794 FAULT ACTION Of 1794 IDLE ACTION 1 to 15 fOr 1794 CONFIG DATA Of 1794 SAFE STATE DATA e o to 64 for 1771 READ Of 1771 WRITE 1t016for1794 READOr1794 WRITE 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 I O 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 Programming Your ControlNet System 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 Errore
116. nition of p 3 terminating Selectable Timed Interrupts STIs using with ControlNet system 4 9 selecting the DH station address of Channel 1A T 10 setting the I O chassis backplane switches 1 6 addressing switches 1 6 EEPROMtransfer switches 1 6 last state switch 1 6 processor memoryprotection switch setting the I O chassis configuration plug specifying the serial interface of Channel 0 1 11 status layout for the processor B 1 Status lel D 1 I O Publication 1785 6 5 22 February 1999 description 2 11 status file processor B 1 status indicators location of on caa cE on PLC5 40C1 5 using 5 1 5 3 status words I O map entry D 1 T tap 1 18 connecting definition of terminator definition of p 3 trunk cable definition of p 3 trunk cable secttor rp 3 U unscheduled data transfer operations 2 3 unscheduled non discrete 1 0 data transfer 2 3 unscheduled transfers definition of p 3 user control bits processor status file B 11 using ControlNet I O Transfer CIO instructions 4 3 using ControlNet Immediate Data 1 0 instructions using ControlNet Message MSG instructions 4 1 using the ControlNet status indicators using the general status indicators 5 1 using this manual conventions used p 3 intended wade ort introduction to recommended preparation for p 1 Allen Bradley wy Publication Problem Report
117. ntrolNet scheduled output data missed Check your network for missing terminators or The processor is unable to transmit the scheduled data it is 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 205 ControlNet configuration exceeds processor bandwidth 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 combining multiple 1 0 racks into a single the resources that the processor wi
118. oax Tap Installation Instructions 1786 2 3 ControlNet Network Access Cable Installation Instructions 1786 2 6 ControlNet Repeater Installation Instructions 1786 2 7 ControlNet System Overview 1786 2 9 Industrial Automation Wiring and Grounding Guidelines 1770 4 1 Chapter 2 Planning to Use Your ControlNet PLC 5 Processor Using This Chapter If you want to read about Go to page Understanding ControlNet 1 0 Understanding ControlNet 1 0 mapping Using I O Mapping Techniques Using the ControlNet PLC 5 processor in a ControlNet I O system Converting from a remote I O system to a ControlNet I O system Converting from ControlNet phase 1 0 or 1 25 to ControlNet 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 and 1785 L80C15 ATTENTION You cannot mix 1 5 and earlier phase products on the same ControlNet network Understanding The ControlNet system is designed to ControlNet I O e provide high speed repeatable deterministic I O transmission allow control and message information to co exist on the same physical media e make sure that I O data transfers are not affected by programming terminal message activity inter PLC processor message activity on the network 1785 6 5 22 February 1999 2 2 Planning to Use Your ControlNet PLC 5 Processor 1785 6 5 22 Febr
119. of the type of I O e g 1747 1771 1794 all ControlNet discrete I O data is stored within the processor according to the corresponding I O map table entry Discrete I O data can be stored in either the I O image table or the DIF DOF Any status information transferred along with the I O data is stored in a separate status file that you specify during configuration 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 ControINet 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 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 com
120. on x on 62 on off on on off off 3 is on on 2 on 63 off off on on off off 24 on on off on off on 64 a oi off an off off 25 off on off on off on 65 off on off a off off 26 on off off on off on 66 n off off on off off 21 off off off on off on 67 off off off on off off 30 on on on off off on 70 o on an off off off 31 off on on off off on 71 oft on on off off off 32 on off on off off on 7 off oh 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 5 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 6 5 22 February 1999 Specifying the Serial Interface of Channel 0 Installing Your ControlNet PLC 5 Processor 1 11 Specify RS 232C RS 422A or RS 423 communication for Channel 0 by setting the switches of assembly SW2 Bottom View of PLC 5 20C Processor Bottom View of PLC 5 40C 5 60C 5 80C processor S
121. onfigure using the programming software to map data from an I O chassis and other devices on the ControlNet network to particular data table file addresses 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 one entry in the I O map table that you configure using the programming software to map data from one I O chassis or other device on ControlNet to particular data table file addresses network access port NAP port that provides a temporary ControlNet network connection through an RJ 45 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 1785 6 5 22 February 1999 Conventions Preface P 3 Term Description non discrete I O data transfer type of data transfer in which blo
122. or memory a Switch l 3 g Processor Memory Protection Ei CT C g m Bi OFF Processor memory protection disabled _ ON Processor memory protection enabled Regardless of this switch setting outputs are turned off when any of the following occurs e processor detects a runtime error e an I O 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 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 6 5 22 February 1999 Installing Your ControlNet PLC 5 Processor 1 7 Setting the 1 0 Chassis Set the I O chassis configuration plug as follows Configuration Plug 1 Locate the chassis configuration plug i between the two left most slots of the chassis 2 Set the I O chassis configuration plug
123. or 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 7712 0x0304 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 I O map table of the not properly configured to send originating and or target nodes to scheduled data send scheduled data 773 0x0305 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 with RSNetWorx The ControlNet network was formed by joining two existing ControlNet networks Reconfigure the new Con
124. ossible Corrective Action s Code 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 I O map table to show the entered in the map table correct module type and slot 65529 OXFFF9 COM MUNICATION ERROR A communication error between the Make sure that the module is CAUSED LOSS OF DATA adapter and the module caused the transfer to be aborted properly seated in the correct slot of 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 I O map table Edit the I O map table to show the correct module type and slot 1785 6 5 22 February 1999 ControlNet I O Map Entry Status Words and Error Messages D 11 Decimal Hex Code Error Message Explanation 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 s
125. 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 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 the 1794 modules listed in Table 2 1 For a complete list refer to RSNetWorx for ControINet documentation Table 2 1 1794 Flex I O Data Transfer Mapping Valid Valid Valid Input Output Config Module Type Description Size s Size s Size s 1203 FM1 A 1203 FM1 A SCANport Module 6 5 5 1794 Generic 1794 Generic Module 1794 IE4X0E2 A 1794 IE4XOE2 A Analog I O Module 1 5 2 2 1794 IE4X0E2 B 1794 IE4XOE2 B Analog I O Module 1 5 2 2 Planning to Use Your ControlNet PLC 5 Processor 2 17 Valid Valid Valid Input Output Config Module Type Description Size s Size s Size s 1794 IE8 A 1794 E8 A Analog Input Module 1 9 0 1 1794 IE8 B 1794 E8 B Analog Input Module 1 9 0 1 1794 IR8 A 1794 R8 A RTD Input Module 2 11 4 1794 IT8 A 1794 IT8 A Thermocouple Millivolt 2 11 4 Input Module 1794 0E4 A 1794 0E4 A Analog Output Module 1 4 2 1794 0E4 B 1794 O0E4 B Analog Output Mo
126. peration 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 e Power off at e Restore power to the blinking Scanner faulted or has failed remote rack rack rapidly or Cable broken 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 e Repair cable blinking Scanner connected or rapidly or is broken slowly Power offat 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 6 5 22 February 1999 5 6 Monitoring and Troubleshooting Your ControlNet System Monitoring ControlNet Configuration and Status More 1785 6 5 22 February 1999 Use the following software packages to monitor ControINet configuration and status information Use RSNetWorx for ControlNet To define ControlNet network parameters such as e network update time media redundancy e physical media configuration e maximum scheduled nodes e ma
127. 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 Oo Oj O O X X Discrete Input Module O Discrete Output Module ACN ControlNet adapter X Empty Slot 1785 6 5 22 February 1999 2 24 Planning to Use Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 If you perform an automap on this system the map table appears like this Input file Input size Output file Output size 1 010 8 0 010 8 The automap feature reserves the maximum size of inputs and outputs It is up to you to manually change the sizes if desired If you optimize the chassis as shown the sizes adjust to the following Input file Input size Output file Output size 010 4 0 010 6 There are two input modules and four output modules in the ch
128. portant module placement rule of 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 T O image space look at the following example system AN 0 0 0 olo ol ps t Discrete Input Module O Discrete Output Module ACN ControlNet adapter A Analog Module PS Power Supply ACN OJ I I I PS ACN A AJA A A A A PS Planning to Use Your ControlNet PLC 5 Processor 2 27 The following chart shows how a Remote I O system compares to one optimized with a ControlNet network Remote I O ControlNet Network Input Output Input Output Chassis Address Size Address Size Address Size Address Size 1 010 8 0 010 8 1 010 1 0 010 7 2 020 8 0 010 8 1 011 7 0 017 3 030 8 0 030 8 n a 0 n a 0 Total Used 24 3 racks 24 3 racks 8 1 rack 8 Remaining 0 0 16 2 racks 16 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 Example 4 Examine the following system ACN Oo OJI 0 0 0 Discrete Input Module hassi O Discrete Output Module Chassis
129. prising the DIF or DOF must be contiguous 1785 6 5 22 February 1999 2 14 Planning to Use Your ControlNet PLC 5 Processor Figure 2 1 Data Input and Data Output Files N10 0 DIF N11 0 N10 999 DOF N11 249 N11 499 Multiple Processors Can Control I O on the Same ControlNet Link A processor at any valid node address can control all of the outputs of a particular rack of I O at one time However only one processor can control the discrete outputs in an I O rack at 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 U E D 2 i ll node 1 node 2 node 3 node 4 1785 6 5 22 February 1999 1771 Modules ControlNet 1771 discrete I O data transfer mapping requires one map table entry per node ControlNet 1771 non discrete I O data transfer mapping requires one map table entry per module Planning to Use Your ControlNet PLC 5 Processor The ControlNet scheduled I O data transfer mechanism makes it possible to eliminate block transfer programming to communicate with the 1771 modules listed in Table 2 H For a complete list refer to RSNetWorx for Contro
130. rors 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 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 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 e steady indicator is on continuously in the defined state 1785 6 5 22 February 1999 Using the DH RIO Status Indicators Monitoring and Troubleshooting Your ControlNet System 5 5 Indicator AorB Color Channel Mode Description Probable Cause Recommended Action Green Remote 1 0 Active Remote 1 0 link all Normal No action required steady Scanner adapter modules are o
131. rror Recoverable 81 You illegally set an I O 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 6 5 22 February 1999 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 I O buffer too much data for the processor to process If you encounter fault code 88 be sure you followed the design guidelines listed on page ___ 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 if using complementary I O 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
132. ructions 4 3 immediate data I O instructions non discrete I O data transfers 2 5 C 1 non discrete I O data transfer instruc tions 4 3 unscheduled data transfer 2 3 unscheduled nondiscrete O data transfer unscheduled operations messaging from programming devices 25 Publication 1785 6 5 22 February 1999 non discrete I O data transfer peer to peer messaging 2 3 I O forcing 2 6 O map table definition off p 2 I O mapentry status words D 1 I O status indicator 5 3 IDI 2 8 IDO IIN 2 8 Immediate Data Input IDI instruction C 2 Immediate Data Output IDO instruction immediate data transfer operations 2 7 immediate I O process 2 8 Immediate Input IIN instruction 2 8 Immediate Output IOT instruction 2 8 indicators aoa PLC5 40C 1 5 installing keying bands for the processor 1 7 installing the processor battery 1 8 installing your processor checking your processor package 1 2 connecting a programming terminal 1 16 ControlNet connection DH connection 1 16 serial channel 1 17 connecting to a ControlNet network 1 15 disposing of the battery handling the processor 1 3 identifying the components of the processor 1 4 installing a DH link installing a remote I O link 1 12 installing keying bands for the processor 1 7 installing the battery 1 8 installing the processor in the chassis 1 12 locating additional informat
133. s Port FAULT Status Indicator NAP RJ 45 connector Green Red Channel 2 ControlNet Redundant Media Ports BNC dedicated Channel 0 lt Memory Module Space Serial Port 25 pin D shell supports standard EIA RS 232C and RS 423 is RS 422A compatible D e Use this port with ASCII or DF1 full duplex s half duplex master and half duplex slave es protocols The port s default configuration supports Se processor programming e 3 e DF1 point to point one stop bit es 2400 bit s e BCC error check se no parity e no handshaking Channel 1 Status Indicators Green Red y gt O lt lt Battery Compartment DH Programming Terminal Connection to Channel 1A ge B08 8 pin mini DIN parallel with 3 pin 2 connectors of Channel 1A 5 4 lt _ _H Channel 1B Channel 1A gt k 3 pin default is remote I O scanner 3 pin dedicated DH configurable for remote I O scanner e remote I O adapter e DH communication Channel 0 is optically coupled provides high electrical eure noise immunity and can be used with most RS 422A equipment as long as e termination resistors are not used e the distance and transmission rate are reduced to comply with RS 423 requirements 1785 6 5 22 February 1999 Installing Your ControlNet PLC 5 Processor 1 5 Figure 1 2 PLC 5 40C 5 60C and 5 80C Processors Front Panel S Ox Battery Status Indicator Red Keyswitch sele
134. s exist to execute block transfers S 10 08 Not enough memory on the memory module to upload the program from the processor S 10 09 No MCP is configured to run S 10 10 MCP not allowed 10 11 Pil word number not in local rack 10 12 PII overlap 10 13 no command blocks exist to get PII 10 14 Arithmetic overflow 10 15 SFC lingering action overlap step was still active when step was reactivated 11 This word of the status file gares S 11 major fault word S 11 00 Corrupted program file codes 10 19 See major fault codes S 12 S 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 12 11 04 Processor detected an error when assembling a ladder program file code 70 duplicate LBLs found 11 05 Start up protection fault The processor sets this major fault bit when powering up in Run mode if the user control bit 26 1 is set 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 1785 6 5 22 February 1999 B 4 Processor Status File This word of the status file Stores 11
135. ss 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 without 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
136. t 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 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 1785 6 5 22 February 1999 ControlNet I O Map Entry Status Words and Error Messages D 3 The following table explains the second and third status words in
137. t the DH station address of Channel 1A set the switches of Address of Channel 1A assembly SW1 Side View of PLC 5 20C 5 40C 5 60C 5 80C Processor Switch Assembly SW1 S565865 W paar LLL LUDA LULL AADIL IA AUALILIL DUDA LUIL LLI Toggle pushed To select Setswitch To toward TOP OFF DH Station Number 1through6 See below Tege Channel 1A DH Configuration 7 on bottom 57 6 kbps toward BOTTOM off top 230 4 kbps 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 n on on on on 41 off on on on on off 2 a of on on on on 42 on off on on on off 0 k Be on on E 43 off off on on on off 5 or an H on on on 44 on on off on on off 0 l Bi on on on 45 off on off on on off 6 on o 2 on on on 46 on off off on on off 7 off off off on on on 47 off off off af on off 10 on on on off on on 50 an on Gh off on off 11 off on on off on on 5I off on on off on off 12 on off on off on on 52 oh off on off Sn off 13 off off on off on on 53 off off on off on off 14 on on off off on on 54 an ies off off ah off 15 off on off off on on 55 off n off off on off o a or on a on on 56 on off off off on off 0 i id 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 an oh on off off a A on
138. t to conserve the input image table for this chassis and arrange it as follows ACN I 1 0 0 Discrete Input Module O 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 ControINet PLC 5 processors updating I O PLC 5 Processorina adapters on a ControlNet network ControlNet 1 0 System e any processor can own adapters on the network e any processor is allowed to send CIO instructions as long as some processor on the ControlNet network owns the adapter e additional processors can do scheduled transfers to any other processor on the ControlNet network by using peer to peer communications through the I O map table You can attach the following ControlNet devices to your network Catalog Number s Device s Function 1785 L20C15 ControlNet Programmable Controllers Communicate with other ControlNet nodes using scheduled or unscheduled L40C15 L60C15 peer to peer communication L80C15 1784 KTC15 ControlNet ISA Communication Cards Allows other computer platforms to communicate with the ControlNet network KTCx15 KTCS 1784 PCC ControlNet PCMCIA Communication Card Allows other co
139. 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 1 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 1785 6 5 22 February 1999 2 22 Planning to Use Your ControlNet PLC 5 Processor 1785 6 5 22 February 1999 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 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 o
140. tive 1771 CIO 41 instructions always less than or equal to 32 ControlNet Diagnostics File Layout F 3 Field Names File Offset word bits Accumulated number of 1771 ClO connection timeouts 48 Current number of active 1794 and CIP ClO instructions 49 always less than or equal to 8 Maximum number of simultaneously active 1794 and 50 CIP CIO instructions always less than or equal to 8 Accumulated number of 1794 and CIP ClO connection 51 timeouts Current number of open target a Router 52 connections always less than or equal to 32 Maximum number of simultaneously open target 53 Message Router connections always less than or equal to 32 Accumulated number of target Message Router 54 connection timeouts Current number of used unconnected clients 55 always less than or equal to 8 Maximum number of simultaneously used 56 unconnected clients 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 59 unconnected servers always less than or equal to 20 Accumulated number of unconnected server timeouts 60 Accumulated number of dropped unconnected 61 requests Accumulated number of J ITT overruns 62 1 The file offset in the user specified ControlNet diagnostics file For example if you specified N12 then t
141. trolNet network by enabling and accepting edits with RSNetWorx 1785 6 5 22 February 1999 ControlNet I O Map Entry Status Words and Error Messages D 9 Decimal Hex Code Error Message Explanation Possible Cause s Possible Corrective Action s Code 774 0x0306 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 I O map entry that is failing The target node of the ClO 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 to the originating node powered when the ControlNet and reconfigure the ControlNet network was configured network 797 0x3
142. tware S 26 07 Reserved through S 26 15 S 27 Rack control bits See also S 7 32 33 5 34 and 35 e 27 0 7 I O rack inhibit bits for racks 0 7 27 8 15 I O rack reset bits for racks 0 7 S 28 Program watchdog setpoint S 29 Fault routine file S 30 STI setpoint 31 STI file number 32 Global status bits See also S 7 27 33 34 and S 35 32 0 7 rack fault bits for racks 10 17 octal e 32 8 15 unused 1785 6 5 22 February 1999 B 12 Processor Status File S 36 S 78 1785 6 5 22 February 1999 This word of Stores the status file 33 Rack control bits See also S 7 27 32 34 and 35 33 0 7 I O rack inhibit bits for racks 10 17 e 33 8 15 1 0 rack reset bits for racks 10 17 S 34 Global status bits See also 7 S 27 32 33 and 35 34 0 7 rack fault bits for racks 20 27 octal 34 8 15 unused 35 Rack control bits See also 7 27 32 33 and 34 35 0 7 35 8 15 I O rack inhibit bits for racks 20 27 1 0 rack reset bits for racks 20 27 Important Setting inhibit bits in the processor status file S 27 33 or 8 35 does not update inhibit bits in the I O status file This word of Stores the status file 36 45 Reserved S 46 PII program file number S 47 Pil module group S 48 PII bit mask S 49 Pil compare value S 50 PII do
143. uary 1999 Scheduled Data Transfer Operations on a ControlNet Network ControlNet scheduled data transfer on a ControINet PLC 5 processor e is continuous e is asynchronous to the ladder logic program scan e occurs at the actual rate displayed in the Actual Packet Interval field on the programming software ControlNet I O mapping monitor screen In scheduled discrete I O data transfer for example the following updates occur between logic scans i e during housekeeping e the input image is moved from a private memory buffer to the processor s input image file for use during the next logic scan e the data from the output image file is put into a private memory buffer and is sent during the next scheduled communication cycle A similar method is used for all scheduled data transfer operations Private lt _______ __ Data Memory Data Update Table Buffers gt Files Scheduled Deta Transfers Logic Scan Scheduled Data Transfer Program Scan Planning to Use Your ControlNet PLC 5 Processor 2 3 The following scheduled data transfer operations are supported by the ControlINet processors on a ControlNet network Table 2 A ControlNet Scheduled Data Transfer Operations Operation Description Discrete 1 0 Data Transfer Performed in a deterministic and repeatable manner asynchronous to and independent of the ladder logic program scan You configure all ControlNet discrete I O data trans
144. uled transfers in the first part of each Network Update Interval NUT 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 is 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 Operation Non discrete I O Data Transfer CIO Instructions Description Planning to Use Your ControlNet PLC 5 Processor 2 5 Table 2 B ControlNet Unscheduled Data Transfer Operations Perform ladder initiated unscheduled non discrete I O data transfers on a ControlNet network by using ControlNet I O Transfer CIO instructions The data type for these transfers CT has the following information Command 1771 READ 1771 WRITE 1794 READ 1794 WRITE 1794 FAULT ACTION 1794 IDLE ACTION
145. wer Off 100 Power Off50 Battery Duration PLC 5 20C 60 C 173 days 346 days 70 hours 25 C 1 69 years 3 38 years 14 5 days PLC 5 40C 60 C 92 5 days 185 days 38 hours 25 C 1 25 years 2 5 years 10 8 days PLC 5 80C 60 C 80 days 160 days 33 hours 25 C 1 18 years 2 36 years 10 days 1 The battery status indicator BATT warns you when the battery is low These durations are based on the battery supplying the only power to the processor power to the chassis is off once the status indicator first lights Disposing of the Battery Do not dispose of lithium batteries in a general trash collection when their combined weight is greater than or equal to 0 5 gram A single 1770 XYC battery contains 0 65 grams of lithium Check your state and local regulations that deal with the disposal of lithium batteries ATTENTION Follow these precautions e Do not incinerate or expose the battery to high temperatures e Do not solder the battery or leads the battery could explode e Do not open puncture or crush the battery The battery could explode or toxic corrosive and flammable chemicals could be exposed e Do not charge the battery An explosion may result or the cell may overheat and cause burns e Do not short positive and negative terminals together The battery will heat up 1785 6 5 22 February 1999 1 10 Installing Your ControlNet PLC 5 Processor Selecting the DH Station To selec
146. 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 receive scheduled message Planning to Use Your ControlNet PLC 5 Processor 2 19 You enable process control sample complete on a per connection basis by setting the PCSC enable bit in the connection s ControlNet 1 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 data is updated during housekeeping regardless of the state of the new data bit If new data is received and the PCSC new d
147. witch Assembly SW2 Switch Assembly SW2 Frontof SoSS2Q2 QQ Q Front of Processor QROQ0020Q0O000O SSSSSaSSES Processor OOO BESEGEE009 OO0CO OOO SSBEESSSH5 OO O E OOOO SS 1 2 3 4 5 6 8 9 10 1 2 3 4 5 6 7 8 9 1 Set Switches To Specify O a a 4 5 6 7 g 9o D OFF OFF OFF OFF m Toggle pushed e ON ON ON ON ON ON toward TOP OFF Toggle pushed OFF OFF ON OFF OFF OFF OFF OFF ON OFF toward BOTTOM RS 422A o 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 for the keeper processor gt Select your processor s ControlNet network address by setting the two 10 digit rotary switches on the top of the processor NET ADDRESS Network address 01 is shown You can select from as many as 99 network addresses from 01 to 99 for a processor on a ControlNet link 00 is invalid Important Do not power up the processor if the processor s ControlNet network address is set to 00 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 1785 6 5 22 February 1999 1 12 Installing Your ControlNet
148. wn count 51 PII changed bit 52 PII events since last interrupt 53 STI scan time in ms S 54 STI maximum scan time in ms S 55 PII last scan time in ms S 56 PII maximum scan time in ms S 57 User program checksum S 58 Reserved S 59 Extended local I O channel discrete transfer scan in ms S 60 Extended local I O channel discrete maximum scan in ms S 61 Extended local I O channel block transfer scan in ms S 62 Extended 1 O channel maximum block transfer scan in ms S 63 Protected processor data table protection file number 79 S127 Processor Status File B 13 This word of Stores the status file S 64 The number of remote block transfer command blocks being used by channel pair 14 1B S 65 The number of remote block transfer command blocks being used by channel pair 2A 2B S 66 Reserved S 72 ControlNet node number of this processor 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 S 74 Time in milliseconds between iterations of the ControlNet subsystem diagnostics When this value reaches 2000 the processor major faults with error code 205 See Appendix E Fault Codes 75 Maximum amount of time in milliseconds between iterations of the ControlNet subsystem diagnostics S 76 Number of slots i
149. wo with a PLC 5 20C processor four with PLC 5 40C and 5 80C processors i 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 Handling the Processor Wrist strap 19897 Compliance to European Union Directives Installing Your ControlNet PLC 5 Processor 1 3 Your processor is shipped in a static shielded container to guard against electrostatic damage Electrostatic discharge can damage integrated circuits or semiconductors in the processor if you touch backplane connector pins It can also damage the module when you set configuration plugs or switches inside the module Avoid electrostatic damage by observing the following precautions e Remain in contact with an approved ground point while handling the module wear a properly grounded wrist strap e Do not touch the backplane connector or connector pins e When not in use keep the module in its static shielded container If this product has the CE mark it is approved for installation within the European and EEA regions It has been designed and tested to meet the following directives EMC Directive This product is tested to meet Council Directive 89 336 EEC Electromagnetic Compatibility EMC and the following standards in whole or in part documented in a technical construction file e EN 50081 2 EMC Generic Emission Standard Part 2
150. ximum unscheduled nodes monitor I O map entry status RSLogix5 enter user program files create delete monitor data table files e enter module configuration e enter channel 0 1A 1B and 3 configuration e administer passwords and privileges 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 PLC 5 20C 2 7A PLC 5 40C 5 60C 5 80C 3 3A Heat Dissipation PLC 5 20C 54 BTU hour PLC 5 40C 5 60C 5 80C 59 BTU hour Environmental Conditions 0 to 60 C 32 140 F 40 to 85 C 40 to 185 F 5 to 95 without condensation Operating Temperature Storage Temperature Relative Humidity Shock Operating duration 30 g peak acceleration for 11 1 ms Non operating duration 50 g peak acceleration for 11 1 ms Vibration 1g 10 to 500 Hz 0 012 inches peak to peak displacement Time of Day Maximum Variations at 60 C 5 min per month Clock Calendar Typical Variations at 20 C Timing Accuracy 20 s per month 1 program scan Backup Cartridge 1785 CHBM ControlNet Hot Backup Cartridge required for each processor Battery 1770 XYC Memory Modules 1785 ME32 1785 ME64 e 1785 M100 1 0 Modules Bulletin 1771 1 0 1794 I O 1746 1 0 and 1791 I O including 8 16 32 pt and intelligent modules Hardware Addressing
151. y 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 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 Oj ps l Discrete Input Module O Discrete Output Module ACN ControlNet adapter A Analog Module PS Power Supply_ 1785 6 5 22 February 1999 2 26 Planning to Use Your ControlNet PLC 5 Processor Second Rule of Module Optimization 1785 6 5 22 February 1999 Chassis 1 Chassis 2 Chassis 3 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 O O A PS Discrete Input Module O Discrete Output Module ACN ControlNet adapter A Analog Module PS Power Supply Input file Input size Output file Output size 1 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 right so that you don t have to waste any inputs or outputs passing over these modules This leads to the second im

1785-6.5.22, ControlNet PLC-5 Programmable Controllers, User

Contents

Download Pdf Manuals

Related Search

Related Contents