Allen Bradley Data Highway II PLC-3 Communication Interface Module (Cat. No.
Table of Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1 Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Read This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . Precautionary Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What This Package Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequently Used Terms . . . . . . . . . . . . . . . . . . . . . . .
ii Table of Contents Operation and Troubleshooting . . . . . . . . . . . . . . . . . . . . . A 1 Appendix Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KP3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Exit Request Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting the KP3 . . . . . . . . . . . . . . . . .
Preface Preface Purpose of This Manual This manual describes the Allen–Bradley 1779–KP3, –KP3R Communication Interface Module and provides information on: the Data Highway II Network other Allen–Bradley communication interface modules the 1779–KP3, –KP3R hardware and firmware components installing and configuring the 1779–KP3, –KP3R Module connecting the 1779–KP3, –KP3R Module to the Data Highway II network installing a backup cable system programming the 1779–KP3, –KP3R Module Who Should Read This Man
Preface Frequently Used Terms To make this manual easier to read, we occasionally use abbreviated versions of some terms. You may see: Term/symbol: Meaning: DH the Allen–Bradley Data Highway network DHII the Allen–Bradley Data Highway II network DH+ The Allen–Bradley Data Highway Plus network. KP3 module or KP3 the 1779–KP3 communication interface module. Generally, we use ‘‘KP3” to refer to both types of modules; we specifically use KP3R when only referring to it.
Preface Related Publications The following table shows you where to read more about related Allen–Bradley products: Title: Publication Number: Data Highway II Local Area Network Overview 1779–2.10 Data Highway/Data Highway 1770–6.2.2 Plus/Data Highway II/Data Highway 485 Cable Planning and Installation Manual Data Highway II Asynchronous–device Interface 1779–6.5.1 Data Highway II Synchronous–device Interface 1779–6.5.2 Data Highway II PLC–2 Communication Interface Module 1779–6.5.
Chapter 1 Overview Chapter Objectives This chapter serves as an introduction to the Allen–Bradley Data Highway II PLC–3 Communication Interface Module and contains the following sections: Introducing the 1779–KP3 Data Highway II Overview Data Highway II Communication Allen–Bradley Communication Interface Modules This information is meant to provide you with a general overview of these topics.
Chapter 1 Overview Figure 1.1 Front Panel of the KP3 The following sections provide a brief overview of the Data Highway II environment and related concepts you should be familiar with before using the 1779–KP3 module. A Brief Look at Data Highway II Allen–Bradley Data Highway II is local area network designed for the plant environment that allows your intelligent devices to communicate with each other (figure 1.2). Figure 1.
Chapter 1 Overview The Data Highway II network offers: a transmission rate of one megabit per second high immunity to noise easy connection to control devices This network is meant for time–critical operations where the status or position of one device (e.g., PLC Programmable Controller, personal computer, etc.) may affect another device, or an entire production line. Data Highway II Cabling All communication on Data Highway II travels from one device to another through the trunkline (figure 1.3).
Chapter 1 Overview You also have the option of running redundant cabling. You can order Allen–Bradley Data Highway II interface modules with dual ports, which allows you to install a back–up cable system. Thus providing more security for your system if a failure occurs. See Chapter 2 for information on redundant cabling. Data Highway II Communication A device and its communication interface make up a node on the Data Highway II network (figure 1.4).
Chapter 1 Overview Figure 1.5 Data Highway II is a Physical Bus Network Node 16 Node 1 Node 31 Node 7 10995-I While the physical layout of the Data Highway II network is a bus, the method of access to the network is a logical ring. Nodes are allowed to communicate on the network while they posses the token. This token is passed around the ring according to the nodes’ addresses on the Data Highway II link.
Chapter 1 Overview Data Highway II communication interfaces operate at different modes that vary according the their relationship with the logical ring. The modes are: In–ring mode, which is when the interface is a fully operational member of the ring. It accepts messages, replies to them, and is ready to send them. Seeking–membership mode, which is when the interface is trying to become a member of the ring so that it can send messages.
Chapter 1 Overview Figure 1.8 Two Data Highway II Links Node C Node B Node A Data Highway II Link 1 KP5 Node D KP5 Data Highway II Link 2 Node E 10998-I Figure 1.8 shows two Data Highway II links. Notice that to ‘‘Node A”, ‘‘Node B” is on–link, and ‘‘Node D” is off–link. Data Highway II nodes consider other nodes ‘‘off–link” if, to communicate with them, the Data Highway II nodes have to cross a bridge. The link numbers become an important factor when you are addressing messages.
Chapter 1 Overview You can also connect a Data Highway Plus subnetwork to your Data Highway II network via one Allen–Bradley KP5 module. When you have a Data Highway Plus sub–network attached to your Data Highway II network, the nodes on Data Highway Plus are considered on–link to the nodes on Data Highway II. If you are sending a message instruction from a PLC–3 controller on Data Highway II to a PLC–5 controller on Data Highway Plus, you would use the same link number for both (figure 1.10). Figure 1.
Chapter 1 Overview Allen-Bradley Communication Interface Modules The following tables show the types of on–link and off–link connections that are possible and the type of Allen–Bradley Communication Interface Modules you need.
Chapter 1 Overview operation LEDs PASS– FAIL– TEST– KP3 Thumbwheel switch that distin guishes this KP3 from others in the same chassis. 1 G. IN–RING Y. SEEKING operation LEDs DUP ADDR BACKUP Two ports for providing optional PLC-3 backups. A BACKUP B operation LEDs ERROR Auxiliary Data Highway II port (not used) A C T I V I T Y BACKUP MODE SAT NORMAL EXIT COMP LED that indicates you have stopped communication to the net work.
Chapter 2 Installing the 1779-KP3 Communication Interface Chapter Objectives This chapter contains the information you need to install your 1779–KP3 Communication Interface module.
Chapter 2 Installing the 1779-KP3 Communication Interface You set these switches to select module options and protection/privilege options. Keep in mind that when the switch is down, it is on (closed); when it is up, it is off (open). Figure 2.2 shows an example setting; the white areas correspond to the movable part within each switch. Figure 2.2 Clarifying the Switch Positions Up = OFF Down = ON 1 2 3 4 5 6 7 8 Switch 3 is OFF, the rest are ON.
Chapter 2 Installing the 1779-KP3 Communication Interface Table 2.
Chapter 2 Installing the 1779-KP3 Communication Interface Table 2.
Chapter 2 Installing the 1779-KP3 Communication Interface Verify that both of the switches in this group are set to OFF (open). Figure 2.4 shows the position they should remain in. Figure 2.4 Correct Position of the MAC Switches (Front View) OFF = up 1 2 Mac Board 11004-I Important: Do not to change these switch settings if you have them. In the later (series B) versions of the KP3 MAC board, changes were made to the hardware, making the need for this MAC switch unnecessary.
Chapter 2 Installing the 1779-KP3 Communication Interface Use the three thumbwheel switches at the bottom of the front panel to set the Data Highway II node address for the KP3. You can use from 1 to 376 octal. For example, to select node address 123, set the thumbwheels as shown in figure 2.6. Figure 2.
Chapter 2 Installing the 1779-KP3 Communication Interface Use the LIST Option to Select Additional KP3 Parameters 3. Slide the module into the chassis slot, making sure it slides along the grove at the bottom of the slot. Press firmly until you feel it snap into the backplane. 4. Pull the interlock bar back into place. 5. Restore power to the chassis. 6. Use LIST to select additional KP3 options (see following section).
Chapter 2 Installing the 1779-KP3 Communication Interface 5. Enter the LIST function at the $ prompt by pressing the shift key and then the list key. You receive the SYSTEM–MODE menu: SYSTEM-MODE SCREEN 1. TEST MONITOR 2. RUN MONITOR 3. *PROGRAM LOAD 4. REMOTE ENABLE 5. SYSTEM STATUS 6. MODULE STATUS ENTER NEXT> 6. 11006-I Select the MODULE STATUS option by typing 6 . The MODULES menu appears, which lists all of the modules in the PLC–3 system by catalog number, including the KP3. 7.
Chapter 2 Installing the 1779-KP3 Communication Interface The Message Time-outs Menu When you choose option 1, you receive the Message Time-outs menu: KP3 1, MESSAGE TIMEOUTS 1 TIME CRITICAL TIMEOUT 2 SUPERVISORY TIMEOUT 3 THIRD-PARTY TIMEOUT ENTER NEXT > This option: allows you to: Minimum value: Maximum Value: Default Value1: 1 set the time-out for time-critical messages. 0.01 seconds 10.00 seconds .50 seconds 2 set the time-out for supervisory messages.
Chapter 2 Installing the 1779-KP3 Communication Interface token hold time is multiplied by the number you enter. For example, if you enter 2, the token hold time will double. You may want to increase the token hold time at the node if, for example, that node typically has more messages to send than other nodes. The Set Node Mode Menu When you select option 3 from the Data Highway II Interface menu, you receive the Set Node Mode menu.
Chapter 2 Installing the 1779-KP3 Communication Interface When the KP3 receives a message containing PLC–2–style addressing, it searches the input file list and reads to or writes from the input file specified for the node that sent the message. If the sending node is not in the list, the KP3 uses the octal address of the source node as the decimal input–file number.
Chapter 2 Installing the 1779-KP3 Communication Interface Connecting the KP3 to Data Highway II Once you have installed and configured the KP3 module, follow the procedure below to connect it to the highway. Important: If you are connecting a backup PLC–3 system to Data Highway II, remember that you must run at least 30 feet of trunkline cable between droplines to the primary and backup KP3 modules. 1. Locate the Data Highway II Port on the KP3 front panel.
Chapter 2 Installing the 1779-KP3 Communication Interface You can assign the same node address to more than one KP3 in the same PLC–3 chassis as long as the KP3s are communicating over different links. Important: You are not required to connect these separate links by Data Highway II bridges. How a PLC-3 Backup System Works on Data Highway II When we talk about a ‘‘backup” system, we a talking about having a primary PLC–3 on the network and a backup PLC–3.
Chapter 2 Installing the 1779-KP3 Communication Interface Installing a Back-up PLC-3 System on Data Highway II You can set up a PLC–3 backup system in three ways, using an: I/O Scanner–programmer Interface Module (1775–S4A), a PLC–3 I/O Scanner Communication Adapter Module (1775–S5) or a Memory Communication Module (1775–MX) without the KP3 S4A, S5, or MX with the KP3 S4A or S5 with an MX, and the KP3 The following sections discuss each of these possibilities.
Chapter 2 Installing the 1779-KP3 Communication Interface Figure 2.8 Backup Cabling With the KP3 Primary PLC-3 S4A KP3 1775-CBB Cable Backup PLC-3 KP3 Backup A Backup A Backup B Backup B S4A 1775-CBB or 1779-CBC Cable Important: Because of the various options for this cable, refer to the backup cable configuration information in the PLC–3 Backup Concepts Manual (publication 1775–6.3.1). 11008-I This method provides faster switchover of communications between primary and backup PLC–3s.
Chapter 2 Installing the 1779-KP3 Communication Interface Figure 2.9 Backup Cabling Using the SA4 and KP3 Modules in Detail S4A Backup KP3 Backup A KP3 Backup A Backup B S4A Pin 1 Backup B 1775-CBB or 1779-CBC Cable 1775-CBB or 1779-CBC Cable 1775-CBB Cable 11009-I Using an S4A or S5, an MX, and a KP3 You can provide backup PLC–3s by connecting the S4A (or S5) module to the KP3 module in both the primary and backup PLC–3s. Then connect each KP3 to the MX modules.
Chapter 2 Installing the 1779-KP3 Communication Interface Figure 2.10 Using an S4A, MX, and a KP3 for Running Backup Cabling 1775-CM Cable (2 feet) S4A KP3 Backup Backup A Pin 1 Backup B 1775-CBB or 1779-CBC Cable MX Pin 1 MX KP3 Pin 1 Backup A XMT XMT REC REC Pin 1 1775-CM Cable (2 feet) S4A Backup Pin 1 Pin 1 Backup B Pin 1 1775-CM Cable Assembly 1775-CBB or 1779-CBC Cable 11010-I Important: The 1775–CBB cable assembly has one end that you can configure.
Chapter 2 Installing the 1779-KP3 Communication Interface Backup Cable Wiring for Linking a KP3 to an S4A, S5, or MX The following diagram shows the recommended wiring for a backup cable linking a KP3 module to an S4A or MX module. Figure 2.
Chapter 2 Installing the 1779-KP3 Communication Interface Important: The 1775–CBB cable assembly has one end that you can configure. When making cables, note the location of the locking connector tab on the module to be certain of the correct connector position. The S4A and MX modules both have the locking tab on the opposite side in comparison to the KP3. The connection between the S4A and the KP3 module is a straight through cable in relation to pin 1 of the connectors.
Chapter 3 Programming Chapter Objectives This chapter contains information on programming your PLC–3 to communicate on the Data Highway II network. We will discuss the information you place in a PLC–3 message send instruction. The PLC–3 Message Send instruction itself is covered in greater detail in the PLC–3 Programmable Controller Programming Manual (publication 1775–6.4.1).
Chapter 3 Programming Qualifier: Use: TO to specify the destination of the data transfer. You must use TO when using either command and it must be followed an address (which must include a data table address and can include a remote node address). You can abbreviate as T. FROM to specify where you want to transfer data from. You can use FROM with either com mand, but if omitted, you must replace it with an integer constant.
Chapter 3 Programming Refer to the PLC–3 Programming manual (publication 1775–6.4.1) for more information on the PLC–3 Message Send Instruction. The following sections cover each command in more detail and give examples for usage. In the syntax examples that follow, we use angle brackets < > to indicate information that you will enter that is specific to your application. For example
in a command line indicates where you would add an address specific to your application.Chapter 3 Programming Where: is: TO the qualifier that specifies the destination of the data transfer; you can abbreviate as T. You must specify the TO qualifier and it must be followed by an address (which must include a data table address and can include a remote node address).
the destination address for the data you are moving.Chapter 3 Programming Using the TMOVE Command to Transfer Data Like the MOVE command, you use the TMOVE command to tell the KP3 to transfer a: bit word contiguous block of information Unlike the MOVE command, the TMOVE command can only be used to transfer data to and from a remote node. This data bypasses some message processing for faster communication between nodes, therefore you should use TMOVE for transferring small amounts of time–critical data.
Chapter 3 Programming Where: is: TO the qualifier that specifies the destination of the data transfer; you can abbreviate as T. You must specify the TO qualifier and it must be followed an address (which must include a data table address and can include a remote node address).
the destination address for the data you are moving. This is either a Data Highway II node address or programmable controller memory address (see section titled Addressing Techniques for addressing style information).Chapter 3 Programming See the section titled Programming Examples, at the end of this chapter, for more command examples. Syntax for the TMOVE Command With the FROM and NOSTATUS Qualifiers The syntax for the TMOVE command when using the FROM and NOSTATUS qualifiers is: TMOVE FROM
TO NOSTATUS or TMOVE TO FROM NOSTATUS Where: is: TMOVE the command that tells the KP3 to transfer data to or from a remote node.Chapter 3 Programming Syntax for the TMOVE Command With an Integer Constant and the NOSTATUS Qualifier The syntax for the TMOVE command when using an integer constant and the NOSTATUS qualifier is: TMOVE TO NOSTATUS or TMOVE TO NOSTATUS Where: is: TMOVE the command that tells the KP3 to transfer data to or from a remote node. what you use in place of the FROM qualifier.
Chapter 3 Programming You need to specify both of these to create a complete address. The general format is: : . <&> <, or / > Information on specifying link, node and user numbers is covered in the following section. Information on specifying addr (addresses) is covered in the section titled Addressing Memory. Addressing Data Highway II Nodes The order of the addressing Data Highway II nodes is: : .
Chapter 3 Programming The KP5 can also have more than one user. When using the KP5 as a Data Highway II/Data Highway Plus interface, you can use user numbers from 2 to 20 to identify Data Highway Plus devices. For example, the address of a PLC–5 (that has its node address switches set to 4) connected to a KP5 (with a node #20) that is connected to a Data Highway Link might look like: :20.04 (figure 3.2). Figure 3.
Chapter 3 Programming The following list shows the possible ways you form memory addresses: $ wordaddr $ wordaddr/bit $ wordaddr,size $ fileaddr:wordaddr $ fileaddr:wordaddr/bit $ fileaddr:wordaddr,size $ extaddr & imblock Important: The numbers you enter into the fields when addressing memory are interrupted as decimal (base 10) unless you indicate that they are octal (base 8). You can specify an octal number by starting it with a zero.
Chapter 3 Programming Addressing a Block of Words This section provides examples of addressing a block of words in each PLC–2, PLC–3, and PLC–5 memory. To Use this format: address a block of words in: Examples: PLC-2 memory $wordaddr,size $010,22 (specifies 22 words beginning with the address 010). The maximum number of words you can specify with the size parameter is 65,535 for MOVE command. For TMOVE, the maximum is 18 (if wordaddr is less than 127) and 17 (if wordaddr is greater than 127).
Chapter 3 Programming When another node reads the immediate–access block, it does not have to wait as long to receive a reply. Usually, the node that receives a command must wait to receive the token before it can reply to a command. With the immediate–access block, the node that receives the command can transmit a reply without having to wait to receive the token first. Thus the node that sent the command, receives a reply sooner.
Chapter 3 Programming Addressing a Bit Within a Word This section provides examples of addressing a bit within a word in each PLC–2, PLC–3, and PLC–5 memory. Programming Examples To use this format: address a bit within a word in: Examples: PLC-2 memory $wordaddr/bit $010/5 (specifies bit 5 of address 010) PLC-3 memory $fileaddr:wordaddr/bit or $extaddr/bit $B111:2/3 (specifies bit 3 of word 2 of binary file 111) $E3.1.8.111.0.2/3 (extended addressing) PLC-5 memory $extaddr/bit $E0.10.2.
Chapter 3 Programming The following table contains examples of using the MOVE command to move a block of words: To move data from: Command line example: Explanation: PLC-3 to PLC-2 MOVE FROM :66$010,1024 TO $B2:3 or M F :66$010,1024 T $B2:3 Transfers 1024 words beginning at word 010 at node 66 to word 3 of binary file 2. PLC-3 to PLC-2 MOVE FROM $B2:3,1024 TO :66$010 or M F $B2:3,1024 T :66$010 Transfers 1024 words beginning at word 3 of binary file 2 to word address 010 at node 66.
Chapter 3 Programming The following table contains examples of using the TMOVE command to move a word: To move data from: Command line example: Explanation: PLC-3 to PLC-2 TMOVE FROM :66$010 TO $B2:3 or TM F :66$010 T $B2:3 Transfers word 010 from node 66 to word 3 of binary file 2. PLC-3 to PLC-2 TMOVE FROM $B2:3 TO :66$010 or TM F $B2:3 T :66$010 Transfers word 3 of binary file 2 to word address 010 at node 66.
Chapter 3 Programming The following table contains examples of using the TMOVE command to move bit: To move data from: Command line example: Explanation: PLC-3 to PLC-2 TMOVE FROM :66$010/1 TO $B2:3/4 or TM F :66$010/1 T $B2:3/4 Transfers bit 1 of word 010 from node 66 to bit 4 of word 3 of binary file 2. PLC-3 to PLC-2 TMOVE FROM $B2:3/011 TO :66$010/015 or TM F $B2:3/011 T :66$010/015 Transfers bit 11 of word 3 from binary file 2 to bit 15 of word address 010 at node 66.
Chapter 3 Programming Examples 3 and 4 show how to use the TMOVE command to move immediate blocks. For both examples, assume there are two nodes, both KP3s. The local node is 010, and the remote node is 020.
Appendix A Operation and Troubleshooting Appendix Objectives This appendix contains information to aid in operating and troubleshooting your 1779–KP3 module. It covers the following topics: an overview of the KP3 module during operation LED indicators using the Exit Request switch troubleshooting the KP3 module KP3 Operation The following sections provide information on the way in which the KP3 operates. Power-up After the KP3 module is powered–up, it goes through self–diagnostic tests.
Appendix A Operation and Troubleshooting Turning-off the Module's Power Whenever you want to turn off the module’s power, press the EXIT REQ switch first. This exit request notifies other nodes you are leaving the ring, thus saving the other nodes time that they would otherwise lose by trying to pass the token to a node that they cannot find. LED Indicators The KP3 module has 16 LED indicators on its front panel; the KP3R has 20 (figure A.1). Figure A.
Appendix A Operation and Troubleshooting The following tables shows the diagnostic information each of the LEDs provide. We have spilt them into two categories: the host board and the MAC board. Table A.A LEDs Associated with the Host Board When this LED(s): does this: then: PASS goes ON green the host and MAC boards performed and passed self-diagnostic tests.
Appendix A Operation and Troubleshooting Table A.B LEDs Associated with the MAC Board When this LED(s): is: then: IN-RING ON green this node is a member of the logical ring on the Data Highway II link. SEEKING ON yellow this node is trying to become a member of the logical ring, or trying to build a logical ring in the case that a ring does not already exist.
Appendix A Operation and Troubleshooting Using the Exit Request Switch The interface has an EXIT REQ pushbutton switch on its front panel. When you press this switch, the interface sends out a signal to the other nodes of the Data Highway II link that it no longer wants to be included in the logical ring After exiting, the interface turns on the EXIT COMP LED. The other nodes will not attempt to pass the token to this node unit it is reset Use the EXIT REQ switch before turning off interface power.
Appendix B Error Codes Appendix Objectives This appendix contains the error codes associated with using the KP3 module.
Appendix B Error Codes Table B.A KP3 Error Codes B 2 Error Code (decimal): Error Code (Hex): Description: 100 64 A carriage return on a blank line. 101 65 A constant preceded by a # is bad. 103 68 A local node in message with a non-local link. 105 69 A number entered for link or node is bad. 108 6C Duplicate wild card operator used in a perform message. 109 6D User symbol or number is bad. 110 6E An illegal memory address preceded by a $.
Appendix B Error Codes Table B.B Link-layer Error Codes Error Code (decimal): Error Code (Hex): Description: 16 10 ACK - 0 to 255 bytes of data. 17 11 NAK - no memory. 18 12 NAK - offline. 19 13 NAK - inactive lsap. 20 14 NAK - illegal PDU format. (Internal checking for proper data format.) 21 15 NAK - high water mark hit. 24 18 Illegal ACK from remote node. 25 19 Illegal RDR reply size. 26 1A Attempted to transmit when not in ring. 27 1B Underrun transmitting packet.
Appendix B Error Codes Error Code (decimal): Error Code (Hex): Description: 47 2F No more tasks for outgoing messages. 251 OFB Illegal destination link value. 252 OFC The message timed-out by application timer. 253 OFD Response from wrong source node. 254 OFE Response TNS did not match. 255 OFF Application layer has been reset. Error Code (decimal): Error Code (Hex): Description: 49 31 Unused. 50 32 Cannot guarantee delivery, link layer timed-out or received a NAK.
Appendix B Error Codes Error Code (decimal): Error Code (Hex): Description: 135 87 Remote node's processor in program or program load mode. 136 88 Communication zone invalid at remote node's processor. 137 89 Remote node's interface device unable to buffer received command in memory. 139 8B Either remote node is in download mode, error in download command, or operation not allowed in upload or download mode. 146 92 Destination node fails to respond. Table B.
Appendix B Error Codes Error Code (decimal): Error Code (Hex): Description: 81 51 Illegal data type. 82 52 Bad parameter. Table B.G Time-critical Error Codes Error Code (decimal): Error Code (Hex): Description: 176 0B0 Base. 177 0B1 Host faulted. 178 0B2 No such address. 179 0B3 Over boundary. 180 0B4 Data table closed. 181 0B5 Area protected. 182 0B6 Bad or no address field. 183 0B7 Missing field. 184 0B8 Timed out. 185 0B9 In wrong mode.
Appendix B Error Codes Error Code (decimal): Error Code (Hex): Description: 213 D5 Program end before delimiter rung. 214 D6 ~XIC in update mode. 215 D7 No memory access yet. 216 D8 Own link ADDR expected in update cmd. 217 D9 No symbolic addressing yet. 218 DA Fault bits in non-dt regions. 219 DB Startbit not 10 to 17. 220 DC ~(XIC) in command rung. 221 DD ~GET (for remote address). 222 DE ~GET (for start address). 223 DF ~GET (for end address).
Appendix C Specifications Appendix Objectives This appendix contains the specifications related to the use of the 1779–KP3, –KP3R module. Specifications Refer to the following table for the KP3, KP3R module specifications. Description: Specification: Module function Interface the PLC-3 processor with Allen-Bradley Data Highway II. Location Single slot of chassis of multi-chassis PLC-3 or PLC-3/10 system.
Index Numbers 1770-T4 Industrial Terminal, using to access the LIST option, 2 7 1775-MX module, 2 14, 2 15, 2 16, 2 17, 2 18 1775-S4A, 2 14, 2 15, 2 16, 2 17, 2 18, 2 19 1775-S5, 2 14, 2 15, 2 16, 2 17, 2 18 1779-KFL, 1 4, 1 8, 1 9 1779-KFM, 1 4, 1 8, 1 9 1779-KP3 installation, 2 1, 2 6 overview of, 1 1 1779-KP5, 1 7, 1 8, 1 9 A Addresses, setting node addresses on Data Highway II, 2 6 Addressing a bit within a word, 3 14 a block of words, 3 12 a word, 3 11 Data Highway II nodes, 3 8, 3 9 for programmable
I–2 Index of the KP3 onto Data Highway II, 2 12 Integer constant, 3 2, 3 4, 3 5, 3 6, 3 8 K KP3. See 1779-KP3 L LED indicators, 1 1, A 2 Link, aaddress for the KP3, setting the, 2 6 Link numbers in addressing, 3 9 Links, 1 6 offlink, onlink, 1 6, 1 7, 1 8 LIST option, using, the, 2 7, 2 8, 2 9, 2 10, 2 11 Logical ring communication, 1 5 Data Highway II as, 1 5 M MAC board. See Circuit boards Memory addresses, possible forms, 3 11 Message instruction, for PLC-3.
Index using to transfer data, 3 5, 3 6, 3 7, 3 8 using with an integer constant, 3 6 Token, 1 5 Transferring Data. See Programming Troubleshooting, A 1, A 5 U User numbers in addressing, 3 9 V Variable word range length, specifying, 3 17 Vocabulary.
Allen Bradley, a Rockwell Automation Business, has been helping its customers improve pro ductivity and quality for more than 90 years. We design, manufacture and support a broad range of automation products worldwide. They include logic processors, power and motion control devices, operator interfaces, sensors and a variety of software. Rockwell is one of the worlds leading technology companies. Worldwide representation.
