Rockwell-automation 1770, D17706.5.16 Ref Mnl DF1 Protocol Command Instrukcja Użytkownika

ReferenceManualDF1 Protocol andCommand SetAllenBradley

Table of Contents vii1785LT (PLC5/15) and 6008LTV (PLC5 VME) Status Bytes 10-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785

7–13Communication CommandsPublication 17706.5.16 - October 1996open fileOpens a file in an SLC 500 processor. If the file is successfullyopened, a T

7–14 Communication CommandsPublication 17706.5.16 - October 1996physical write Downloads data into the PLC data table or program memory. Use this

7–15Communication CommandsPublication 17706.5.16 - October 1996protected bit write Sets or resets individual bits within limited areas of the PLC da

7–16 Communication CommandsPublication 17706.5.16 - October 1996protected typed file readReads data from an open file in a MicroLogix 1000 or an SLC

7–17Communication CommandsPublication 17706.5.16 - October 1996protected typed logical read with three address fields Reads data from a logical addre

7–18 Communication CommandsPublication 17706.5.16 - October 1996protected typed logical write with three address fields Writes data to a logical addr

7–19Communication CommandsPublication 17706.5.16 - October 1996protected write Writes words of data into limited areas of the PLC data tablememory.

7–20 Communication CommandsPublication 17706.5.16 - October 1996read link parameters Reads the DH485 parameter, Maximum Solicit Address. This parame

7–21Communication CommandsPublication 17706.5.16 - October 1996readmodifywrite N Sets or resets specified bits in specified words of data table me

7–22 Communication CommandsPublication 17706.5.16 - October 1996read section sizeReads the size of the section most fully addressed by the systemaddr

Table of ContentsviiiDownloading to an SLC 500 Processor 12-10. . . . . . . . . . . . . . Procedure 1  SLC 500, SLC 5/01 and SLC 5/02 Processors

7–23Communication CommandsPublication 17706.5.16 - October 1996restart request (restart)Terminates an upload or a download. The computer cannot issu

7–24 Communication CommandsPublication 17706.5.16 - October 1996return edit resource Returns the edit resource (sole access) of the processor when ed

7–25Communication CommandsPublication 17706.5.16 - October 1996set ENQs Sets the maximum number of ENQs that the asynchronous interfacemodule issues

7–26 Communication CommandsPublication 17706.5.16 - October 1996set CPU mode Sets the operating mode of the processor at the next I/O scan. The oper

7–27Communication CommandsPublication 17706.5.16 - October 1996set timeout Sets the maximum amount of time that the asynchronous interfacemodule wai

7–28 Communication CommandsPublication 17706.5.16 - October 1996shutdownAsks the interface module to initiate either a PLC-3 shutdown (if the compute

7–29Communication CommandsPublication 17706.5.16 - October 1996Data Type ID (Bits 47) Data Type Size (Bits 03)The following table contains a list o

7–30 Communication CommandsPublication 17706.5.16 - October 1996typed write (write block) Writes a block of data to the processor starting at the PLC

7–31Communication CommandsPublication 17706.5.16 - October 1996Important: The interface module at the receiving PLC nodeexecutes this command by firs

7–32 Communication CommandsPublication 17706.5.16 - October 1996unprotected write 1774-PLC, PLC-2, PLC-3, PLC-5Writes words of data into any area o

Preface17706.5.16  October, 1996About This ManualRead this preface to familiarize yourself with this manual. This preface includes information on:

7–33Communication CommandsPublication 17706.5.16 - October 1996upload all request (upload)Places a PLC-5 processor in Upload mode before uploading ac

7–34 Communication CommandsPublication 17706.5.16 - October 1996upload completedAfter uploading a complete system, use to return the processor to the

7–35Communication CommandsPublication 17706.5.16 - October 1996word range write (write block) Writes to a word or file starting at a specified addres

7–36 Communication CommandsPublication 17706.5.16 - October 1996The type/data parameter is a variable length field. The mostsignificant bit of each

7–37Communication CommandsPublication 17706.5.16 - October 1996Example 2: Type/data parameter for writing or reading integer dataThis example shows

7–38 Communication CommandsPublication 17706.5.16 - October 1996Important: There are also some limitations on the basic commands SLC 500 family nodes

7–39Communication CommandsPublication 17706.5.16 - October 1996You can map the SLC 500 CIF file to PLC-2 memory as shown inthe following example. Th

7–40 Communication CommandsPublication 17706.5.16 - October 1996Example: Reading the 18th and 19th bytes shown in the example on page 7-39These exam

Chapter 8Publication 17706.5.16 - October 1996Message Packet Status Codes(STS, EXT STS)Use this chapter to help interpret status codes that appear i

8–2 Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996The STS byte provides information about the execution or failure o

About This ManualP–217706.5.16  October, 1996This manual is divided into five units:Chapter 3, Using HalfduplexProtocol to Send andReceive Message

8–3Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996Remote STS Error CodesThe remote STS error code nibble contains err

8–4 Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996EXT STS Codes for CMD 0FHex Code Explanation0 Not used1 A field ha

8–5Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996DH485 EXT STS Codes Hex Code Explanation07H Insufficient memory mod

8–6 Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996Remote STS and EXT STS Codes from a PLC3 ProcessorA PLC-3 interfa

8–7Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996Command ExplanationSTS CodeEXT STS CodePLC/PLC2 read- 10•The requi

8–8 Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996Command ExplanationSTS CodeEXT STS CodePLC3 word write- 10•There

8–9Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996Command ExplanationSTS CodeEXT STS CodePLC3 physical reads- 10•The

8–10 Message Packet Status Codes (STS, EXT STS)Publication 17706.5.16 - October 1996Command ExplanationSTS CodeEXT STS CodePLC3 bit write- 10 More t

Module DiagnosticsDiagnostic Counters  Chapter 9Diagnostic Status Information  Chapter 10

Chapter 9Publication 17706.5.16 - October 1996Diagnostic CountersDiagnostic counters are bytes of information stored in RAM in eachmodule. The coun

About This Manual P–317706.5.16  October, 1996Term Definitionlocal node The node sending the commandnode The point at which devices, such as progra

9–2 Diagnostic CountersPublication 17706.5.16 - October 1996Reading diagnostic countersTo read diagnostic counters, you issue a diagnostic read comma

9–3Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1747KE DH485 9-31747L20, L30, L40, L511, L514, L524, L532ÀDH48

9–4 Diagnostic CountersPublication 17706.5.16 - October 19961747L541, L542, and L543 (SLC 5/04 processors) DH+Diagnostic CountersThis counter byte

9–5Diagnostic CountersPublication 17706.5.16 - October 19961747L541, L542, and L543 (SLC 5/03 and 5/04 processors)DH485 Diagnostic CountersThis co

9–6 Diagnostic CountersPublication 17706.5.16 - October 19961747L541, L542, and L543 (SLC 5/03 and SLC 5/04 processors)DF1 Diagnostic CountersThis

9–7Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1761L16AWA, L16BBB, L16BWB, L32AWA, L32BWA,DH485 9-71761 L16AWA,

9–8 Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1770 KF2DH 9-81770KF2DH+9-111770KF3 DH485 9-31770KFC DF1 9-131770

9–9Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of9Frames that were rejected because they were less th

9–10 Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of21, 22 Times the node attempted to send a message.

9–11Diagnostic CountersPublication 17706.5.16 - October 19961770KF2 and 1785KE DH+ and Asynchronous Link DiagnosticCountersThis counter byte Count

About This ManualP–417706.5.16  October, 1996 Allen-Bradley offers a wide range of interfaces for the DH, DH+,and DH485 networks, including:Catalo

9–12 Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of35, 36 Times node attempted to send a message.37,

9–13Diagnostic CountersPublication 17706.5.16 - October 19961770KFC DF1 Diagnostic CountersThis counter byte Counts the number of1 Total DF1 packets

9–14 Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1771KA, 1771KA2, and 1774KA DH 9-14, 9-151771KC DH 9-16, 9-18177

9–15Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of9 Frames that were rejected because the header was

9–16 Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of30 Replies lost because they could not be delivere

9–17Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of8 Times the receiver received a status frame instea

9–18 Diagnostic CountersPublication 17706.5.16 - October 1996This counter byte Counts the number of15 Duplicate frames received.A duplicate frame is

9–19Diagnostic CountersPublication 17706.5.16 - October 19961771KG,KGM Diagnostic CountersAsynchronous Link Diagnostic CountersThis counter byte Co

9–20 Diagnostic CountersPublication 17706.5.16 - October 1996Internal Event CountersThis counter byte Counts the number of35 Messages routed to RS23

9–21Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1775KAÀDH 9-211775S5, SR5 DH+ 9-21ÀPLC3 processors1775KA,S5,SR

About This Manual P–517706.5.16  October, 1996Communication, diagnostic, and driver softwareDH 6001-NET Network Communications Software (Series 600

9–22 Diagnostic CountersPublication 17706.5.16 - October 1996Asynchronous Link Counters (1775KA only)This counter byte Counts the number of29, 30 Co

9–23Diagnostic CountersPublication 17706.5.16 - October 19961775S5,SR5 DH+ Diagnostic CountersThis counter byte Counts the number of0, 1 Messages s

9–24 Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1779KP5 DH+ 9-241779KP5 DH+ Diagnostic CountersThis counter byte C

9–25Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1784KR DH485 9-31784KT, KT2 DH+ 9-251784KT and 1784KT2 DH+ Diagn

9–26 Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages1785KE DH+ 9-111785KA3 DH+ 9-281785KA DH 9-261785KA DH+ 9-271785

9–27Diagnostic CountersPublication 17706.5.16 - October 19961785KA DH+ Diagnostic CountersThis counter byte Counts the number of0 Times received ACK

9–28 Diagnostic CountersPublication 17706.5.16 - October 19961785KA3 DH+ Diagnostic CountersThis counter byte Counts the number of0 Received ACKs wi

9–29Diagnostic CountersPublication 17706.5.16 - October 19961785KA5 DH+ Diagnostic CountersThis counter byteCounts the number of➀01 Timeouts that ex

9–30 Diagnostic CountersPublication 17706.5.16 - October 19961785KA5 DH485 Diagnostic CountersThis counter byte Counts the number of0, 1 Total packe

9–31Diagnostic CountersPublication 17706.5.16 - October 1996Below are diagnostic counters for the channel 0 serial port. These counters vary dependi

Network BasicsNetwork Layers  Chapter 1

9–32 Diagnostic CountersPublication 17706.5.16 - October 19961785L20E, L40E, L40L, L60L, L80E DH+ Diagnostic CountersThis counter byte Counts th

9–33Diagnostic CountersPublication 17706.5.16 - October 1996Cat. Nos. Link Pages5250LP1, LP2, LP3, LP4À processorsDH+ 9-33ÀPLC5/250 processors52

Chapter 10Publication 17706.5.16 - October 1996Diagnostic Status InformationIn chapter 8, we showed you the diagnostic status message packetformat.

10–2 Diagnostic Status InformationPublication 17706.5.16 - October 1996For status information from these cat. nos. See page1747KE 10-21747L20, L30

10–3Diagnostic Status InformationPublication 17706.5.16 - October 19961747L20, L30, L40, L511, L514, L524 (SLC 500, SLC 5/01 andSLC 5/02 proces

10–4 Diagnostic Status InformationPublication 17706.5.16 - October 19961747L532, L541, L542, L543 (SLC 5/03 and SLC 5/04processors) Status Bytes

10–5Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits240 directory file corrupted1 not used = 027 prog

10–6 Diagnostic Status InformationPublication 17706.5.16 - October 19961761L16AWA, L16BBB, L16BWB, L32AWA, L32BWA,L32BWB (MicroLogix 1000 proce

10–7Diagnostic Status InformationPublication 17706.5.16 - October 19961770KF3 Status Bytes Bytes Bits Contents Description1 1 Mode/Status 00 (no mod

10–8 Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits 90 - 4Series and revision level of interface mod

Chapter 1Publication 17706.5.16 - October 1996Network LayersYour network is made up of several layers, including:Physical layer transmits bits betwe

10–9Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes Bits Contents Description1771KG Module (Series B)1 0 = second module; 1

10–10 Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits10 Settings of the option switches on the1771KG

10–11Diagnostic Status InformationPublication 17706.5.16 - October 1996For status information from these cat. nos. See page1773KA 10-111775KA, 1775

10–12 Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits90 - 4Module series and revision level0 = Revisi

10–13Diagnostic Status InformationPublication 17706.5.16 - October 19961775KA, S5 and SR5 Status Bytes Bytes Bits Contents Description10 - 1Operat

10–14 Diagnostic Status InformationPublication 17706.5.16 - October 19961779KP5 Status Bytes Bytes Bits Contents Description1 all 00 Not used2 all I

10–15Diagnostic Status InformationPublication 17706.5.16 - October 1996For status information from these cat. nos. See page1784KR 10-151784KT,KT2

10–16 Diagnostic Status InformationPublication 17706.5.16 - October 1996For status information from these cat. nos. See page1785KA 10-161785KA3 10-

10–17Diagnostic Status InformationPublication 17706.5.16 - October 19961785KA5 Status Bytes DH+ Status BytesBytes Bits Contents Description0 all mod

10–18 Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits3 - 4 all Octal address of the start of the PLC

1–2 Network LayersPublication 17706.5.16 - October 1996The physical layer is a set of cables and interface modules thatprovides a channel for communi

10–19Diagnostic Status InformationPublication 17706.5.16 - October 19961785KE Status Bytes Bytes Bits Contents Description1 all Operating status of

10–20 Diagnostic Status InformationPublication 17706.5.16 - October 19961785LT (PLC5/15) and 6008LTV (PLC5 VME) Status Bytes Bytes Bits Contents

10–21Diagnostic Status InformationPublication 17706.5.16 - October 19961785LT3 (PLC5/12) and 1785LT2 (PLC5/25) Status Bytes Bytes Bits Contents D

10–22 Diagnostic Status InformationPublication 17706.5.16 - October 19961785L11B, L20B, L20E, L30B, L40B, L40E, L40L, L60B,L60L Status Byte

10–23Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits19 all Debug mode = 0, OFF0 0, ON20 - 21 all Hold

10–24 Diagnostic Status InformationPublication 17706.5.16 - October 1996Bytes DescriptionContentsBits6 - 7 all Program Change Sequence Count 1 word8

ReferenceData Encoding  Chapter 11Uploading and Downloading with AB Processors Chapter 12PLC Addressing  Chapter 13Line Monitor Examples  Chapter

Chapter 11Publication 17706.5.16 - October 1996Data EncodingThis chapter provides:• definitions of numbering systems you can use in your application

11–2 Data EncodingPublication 17706.5.16 - October 1996In general, PLC processors store binary data (1s and 0s) in 16-bitgroups called words. If you

11–3Data EncodingPublication 17706.5.16 - October 1996BinaryThe binary numbering system is a simple method for computer andPLC applications because i

Because of the variety of uses for the products described in thispublication, those responsible for the application and use of thiscontrol equipment m

1–3Network LayersPublication 17706.5.16 - October 1996DH Link A DH link is a local area network (LAN) designed for factory-floorapplications. This l

11–4 Data EncodingPublication 17706.5.16 - October 1996Hexadecimal The hexadecimal (hex) numbering system is the most compact wayto represent binary

11–5Data EncodingPublication 17706.5.16 - October 1996 OctalThe octal number system is another easy way to represent binarydata. This system uses th

11–6 Data EncodingPublication 17706.5.16 - October 1996PLC processors store data in 16-bit (2-byte) words. The bits in thesewords are numbered (addr

11–7Data EncodingPublication 17706.5.16 - October 1996A 16-Bit Word in PLC Memory10 100101 1 1 0 1 1 00117 16 15 14 13 12 11 10 7 6 5 4 3 2 1 0Bit(Oc

Chapter 12Publication 17706.5.16 - October 1996Uploading and Downloadingwith AB ProcessorsRead this chapter to help you perform uploads from and do

12–2 Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996To make sure the program image is stable during an upload, the

12–3Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Uploading from a PLC5 ProcessorImportant: Uploads cannot be pe

12–4 Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Procedure 1 — PLC-5/15/B processors, revision E and earlier1.

12–5Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Procedure 2The processor can be in any mode while uploading.1.

12–6 Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Uploading from an SLC 500 Processor1. Open the directory to be

1–4 Network LayersPublication 17706.5.16 - October 1996Unlike a master/slave relationship, a floating master relationshipdoes not require the current

12–7Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Downloading to a PLC2 Processor1. Place the PLC-2 processor in

12–8 Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Downloading to a PLC3 Processor1. Determine if the destinatio

12–9Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Procedure 1 (PLC-5/15/B rev E and earlier)1. Place the PLC-5 pr

12–10 Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Procedure 21. Verify the processor type using diagnostic stat

12–11Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Procedure 1 — SLC 500, SLC 5/01 and SLC 5/02 Processors1. Dete

12–12 Uploading and Downloading with A-B ProcessorsPublication 17706.5.16 - October 1996Procedure 2 — SLC 5/03 and SLC 5/04 Processors1. Make sure th

Chapter 13Publication 17706.5.16 - October 1996PLC AddressingPLC processors support these types of addressing:Type of Addressing Descriptionlogical

13–2 PLC AddressingPublication 17706.5.16 - October 1996PLC-2 and 1774-PLC processors support logical and physicaladdressing:For information on See p

13–3PLC AddressingPublication 17706.5.16 - October 1996PLC2 Physical AddressingPLC-2 processors use physical addresses that are directly related tot

13–4 PLC AddressingPublication 17706.5.16 - October 1996PLC-3 family controllers support logical, physical, and symbolicaddressing.For information on

1–5Network LayersPublication 17706.5.16 - October 1996DH+ LinkA DH+ link is similar to a DH link, but is optimally used for smallernetworks consistin

13–5PLC AddressingPublication 17706.5.16 - October 1996PLC3 Logical AddressingPLC-3 processors use a form of logical addressing known asextended add

13–6 PLC AddressingPublication 17706.5.16 - October 1996Example: PLC3 logical binary addressing formatE3 1 8 260 0Data table area = level 10Context

13–7PLC AddressingPublication 17706.5.16 - October 1996PLC3 Physical AddressingPLC-3 processors use physical addresses that are related to logicalad

13–8 PLC AddressingPublication 17706.5.16 - October 1996PLC3 Symbolic AddressingSymbolic addressing uses ASCII symbols to represent a logicaladdress

13–9PLC AddressingPublication 17706.5.16 - October 1996PLC-5 processors support logical and physical addressing:For information on See pagelogical ad

13–10 PLC AddressingPublication 17706.5.16 - October 1996PLC5 Logical AddressingPLC-5 processors, like PLC-3 processors, use a form of logicaladdres

13–11PLC AddressingPublication 17706.5.16 - October 1996PLC-5 Logical Binary AddressingByte Contents1 the mask byteThis byte determines which four le

13–12 PLC AddressingPublication 17706.5.16 - October 1996PLC5 Logical Binary Address to Access the Address N7:30level 1 (value = 0); data table07301

13–13PLC AddressingPublication 17706.5.16 - October 1996PLC5 Memory (for use with figures on page 13-12 )level 1level 2 level 3 level 40 (data table

13–14 PLC AddressingPublication 17706.5.16 - October 1996Important: If the value of the mask or a level of the address isgreater than or equal to 255

1–6 Network LayersPublication 17706.5.16 - October 1996DH485 LinkA DH485 link is a low cost, peer-to-peer programming and data-acquisition link for a

13–15PLC AddressingPublication 17706.5.16 - October 1996PLC5/250 RM/LP Memory (for use with figures on page 13-14)level 1 level 2 level 3 level 4 le

13–16 PLC AddressingPublication 17706.5.16 - October 1996PLC5 Physical AddressingPLC-5 processors use physical addresses that are related to logical

13–17PLC AddressingPublication 17706.5.16 - October 1996PLC5 Floating PointPLC-5 type reads and type writes use the IEEE floating point. (This is t

Chapter 14Publication 17706.5.16 - October 1996Line Monitor ExamplesThis chapter contains line monitor examples for DF1 protocol. Each example show

14–2 Line Monitor ExamplesPublication 17706.5.16 - October 1996When monitoring half-duplex protocol in two-wire mode, you needto monitor only one lin

14–3Line Monitor ExamplesPublication 17706.5.16 - October 1996In the following example an unprotected read (CMD 01 hex) is sent:• from a computer con

14–4 Line Monitor ExamplesPublication 17706.5.16 - October 1996CommandField Value FunctionDLE STX (2 bytes) 10 02 Indicates the start of a messageDST

14–5Line Monitor ExamplesPublication 17706.5.16 - October 1996ReplyField Value FunctionDLE STX (2 bytes) 10 02 Indicates the start of the reply messa

14–6 Line Monitor ExamplesPublication 17706.5.16 - October 1996In this example three word range reads (CMD 0F, FNC 01) are sent:• from a computer con

14–7Line Monitor ExamplesPublication 17706.5.16 - October 1996CommandField Value FunctionDLE STX (2 bytes) 10 02 Indicates the start of a messageDST

1–7Network LayersPublication 17706.5.16 - October 1996Your DF1 links and network links (DH, DH+, and DH485) each usetwo layers of software to enable

14–8 Line Monitor ExamplesPublication 17706.5.16 - October 1996ReplyField Value FunctionDLE STX (2 bytes) 10 02 Indicates the start of the reply mess

Chapter 15Publication 17706.5.16  July 1996ASCII CodesASCII Hex Binary DecimalNUL00 00000000 0SOH 01 00000001 1STX 02 00000010 2ETX 03 00000011 3EO

15-2 ASCII CodesPublication 17706.5.16  July 1996ASCII Hex Binary DecimalR52 01010010 82S 53 01010011 83T 54 01010100 84U 55 01010101 85V 56 0101011

15-3ASCII CodesPublication 17706.5.16  July 1996ASCII Hex Binary DecimalAC 10101100 172AD 10101101 173AE 10101110 174AF 10101111 175B0 10110000 176B

Symbols**Empty**, P-1, P-2, P-4, P-5, 2-2, 2-3, 6-1, 6-2, 6-3, 7-1Numbers16-bit computer word, 11-716-bit PLC word, 11-71747,

IndexI–2Application layer, 1-7description of, 1-8Application layer protocol, 6-1Application program, how it sends andreceives messages, 6-2Ap

IndexI–3Data link layer protocols, 2-4Data type ID, 7-29Data type size, 7-29Decimal, 11-2DH+ diagnostic counters, 1747-L542, 9-4, 9-5, 9-

IndexI–4MManualpurpose, P-1who should read, P-1Master, 2-3Master packet, 5-2Messagepriority, 1-10reply, 1-9Message bytes, data bytes,

IndexI–5Protocol environmentdefinition, 4-3message characteristics, 4-4message sink, 4-3message source, 4-3transmitter operation, 4-5RRecei

AllenBradleyPublication Problem ReportIf you find a problem with our documentation, please complete and return this form.Pub. NameCat. No.Pub. No. Pu

1–8 Network LayersPublication 17706.5.16 - October 1996Application LayerThis layer controls and executes the actual commands specified inthe communic

Other CommentsPLEASE FOLD HERENO POSTAGE NECESSARY IF MAILED IN THE UNITED STATESBUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OHPOST

Publication 17706.5.16  July 1996AllenBradley, a Rockwell Automation Business, has been helping its customers improveproductivity and quality for m

1–9Network LayersPublication 17706.5.16 - October 1996MessagesSee Chapter 7, “Communication Commands,” for:• a description of the command messages fo

1–10 Network LayersPublication 17706.5.16 - October 1996Message PriorityYou specify the priority level for each DH command in the messagecommand code

1–11Network LayersPublication 17706.5.16 - October 1996Types of CommandsFrom your computer on a DF1 link to a node on a DH, DH+ orDH485 link, you can

ProtocolUnderstanding DF1 Protocol  Chapter 2Using Halfduplex Protocols to Send and ReceiveMessages  Chapter 3Using Fullduplex Protocols to Send a

Summary of ChangesPublication 17706.5.16 - October 1996What's Changed in ThisDocumentThis document contains important information concerning the

Chapter 2Publication 17706.5.16 - October 1996Understanding DF1 ProtocolIf you are connecting an interface module to a computer, you mustprogram the

2–2 Understanding DF1 ProtocolPublication 17706.5.16 - October 1996A link protocol is a set of programming rules for interpreting thesignals transmit

2–3Understanding DF1 ProtocolPublication 17706.5.16 - October 1996Using half-duplex protocolWhen you use half-duplex protocol, the intended environme

2–4 Understanding DF1 ProtocolPublication 17706.5.16 - October 1996Fullduplex ProtocolUse full-duplex protocol:• over a point-to-point link that all

2–5Understanding DF1 ProtocolPublication 17706.5.16 - October 1996Allen-Bradley interface modules send data serially over theRS-232-C/RS-422-A interf

2–6 Understanding DF1 ProtocolPublication 17706.5.16 - October 1996Both half-duplex and full-duplex protocols are character-oriented.They use the ASC

2–7Understanding DF1 ProtocolPublication 17706.5.16 - October 1996Table 2.C Halfduplex Transmission SymbolsSymbolType MeaningDLE SOH control symbolS

2–8 Understanding DF1 ProtocolPublication 17706.5.16 - October 1996Table 2.D Fullduplex Transmission SymbolsSymbolType MeaningDLE STX control symbol

Chapter 3Publication 17706.5.16 - October 1996Using Halfduplex Protocols toSend and Receive MessagesIn half-duplex protocol, devices share the same

3–2 Using Half-duplex Protocols to Send and Receive MessagesPublication 17706.5.16 - October 1996Half-duplex protocol:• is a multidrop protocol for o

What's Changed in This Document soc-i. . . . . . . . . . . . . . About This Document soc-i. . . . . . . . . . . . . . . . . . . . . . . . .

3–3Using Half-duplex Protocols to Send and Receive MessagesPublication 17706.5.16 - October 1996Each node on a multidrop link contains a software rou

3–4 Using Half-duplex Protocols to Send and Receive MessagesPublication 17706.5.16 - October 1996The following program describes the actions of the t

3–5Using Half-duplex Protocols to Send and Receive MessagesPublication 17706.5.16 - October 1996GETMESSAGE is defined asGET-CODEwhile it is data code

3–6 Using Half-duplex Protocols to Send and Receive MessagesPublication 17706.5.16 - October 1996The following flowchart shows the software logic for

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU ,GHDOO\ WKH GDWDOLQN OD\HU SURWRFRO LV QRW FRQFHUQH

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU )XOO 6LQNV:KHQ D QRGH WLPHV RXW WR D PHVVDJH FRPPDQG

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 6LQFH LQSXW VHQW WR WKH WUDQVFHLYHU FDQ RIWHQ EH DIIH

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU ,I DQ\ FRQWURO V\PERO RWKHU WKDQ D '/( (7; %&am

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU :KHQ D PHVVDJH LV WUDQVPLWWHG DIWHU UHFHLYLQJ D SROO

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 1RUPDO 0HVVDJH 7UDQVIHU,Q WKLV WUDQVIHU GDWD E\WHV

Table of ContentsiiUsing Halfduplex Protocols to Send and Receive Messages 3-1. . . . . . . . . . . . . . . . . . . . . . . Halfduplex Protocol Me

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 0HVVDJH 7UDQVIHU ZLWK $&. 'HVWUR\HG,Q WKLV

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 3ROO ZLWK 0HVVDJH 5HWXUQHG,Q WKLV WUDQVIHU WKH PDV

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 'XSOLFDWH 0HVVDJH 7UDQVPLVVLRQ,Q WKLV WUDQVIHU

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 0HVVDJH 6LQN )XOO &DVH ,Q WKLV WUDQVIHU WKH V

ï8VLQJ +DOIGXSOH[ 3URWRFROV WR 6HQG DQG 5HFHLYH 0HVVDJHV3XEOLFDWLRQ  ï 2FWREHU 0HVVDJH 6LQN )XOO &DVH ,Q WKLV WUDQVIHU WKH V

Chapter 4Publication 17706.5.16 - October 1996Using Fullduplex Protocol toSend and Receive MessagesIn full-duplex protocol, devices share the same

4–2 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996With full-duplex protocol, a link uses two physical c

4–3Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Figure 4.2 Software implementation of data pathsSoftwa

4–4 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Figure 4.3 shows the protocol environment for message

4–5Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996How the Transmitter OperatesThe following program desc

Table of Contents iiiDatalink Layer Message Frames 5-1. . . . . . . . . . . . . . . . Halfduplex Protocol Message Frames 5-2. . . . . . . . . .

4–6 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996The following flowcharts the software logic for imple

4–7Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996How the Receiver OperatesThe receiver must be capable

4–8 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996The following program describes the actions of the re

4–9Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996The following flowchart is the software logic for impl

4–10 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996These transfer diagrams show events that occur on va

4–11Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with NAKIn this transfer:• the trans

4–12 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with Timeout and ENQIn this transfe

4–13Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with ReTransmissionIn this transfer

4–14 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with Message Sink FullIn this trans

4–15Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with NAK on ReplyIn this transfer:•

Table of Contentsivecho 7-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . enable outputs 7-9. . . . . . . . . .

4–16 Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with Timeout and ENQ for the ReplyI

4–17Using Full-duplex Protocol to Send and Receive MessagesPublication 17706.5.16 - October 1996Message Transfer with Message Source Full on the Repl

Message PacketsDatalink Layer Message Frames  Chapter 5Application Layer Message Packets  Chapter 6Communication Commands  Chapter 7Message Packet

Chapter 5Publication 17706.5.16 - October 1996Datalink Layer MessageFramesIn the data-link layer of a message frame:• half-duplex protocol uses thr

5–2 Data-link Layer Message FramesPublication 17706.5.16 - October 1996Half-duplex protocol uses three types of transmissions:• polling frame• master

5–3Data-link Layer Message FramesPublication 17706.5.16 - October 1996Full-duplex protocol implements different message frames,depending on the netwo

5–4 Data-link Layer Message FramesPublication 17706.5.16 - October 1996At the end of each polling frame and each message frame, there is a one-byte B

5–5Data-link Layer Message FramesPublication 17706.5.16 - October 1996Full-duplex protocol exampleIf a message frame contained the data 08. 09, 06, 0

5–6 Data-link Layer Message FramesPublication 17706.5.16 - October 1996CRC FieldFor these protocolsYou calculate the CRC value➀fullduplex using the

5–7Data-link Layer Message FramesPublication 17706.5.16 - October 1996The full-duplex and half-duplex slave and master protocol examplesbelow provide

Table of Contents vword range read (read block) 7-34. . . . . . . . . . . . . . . . . . . . . . word range write (write block) 7-35. . . . . .

Chapter 6Publication 17706.5.16 - October 1996Application Layer MessagePacketsRead this chapter to help learn about the application layer for youras

6–2 Application Layer Message PacketsPublication 17706.5.16 - October 1996There are two types of application programs:• command initiators• command e

6–3Application Layer Message PacketsPublication 17706.5.16 - October 1996Most devices send and receive messages using this message packet format:DST

6–4 Application Layer Message PacketsPublication 17706.5.16 - October 1996DST and SRCForm the DST and SRC bytes of a reply message by interchangingth

6–5Application Layer Message PacketsPublication 17706.5.16 - October 1996CMD and FNCThese bytes work together to define the activity that is to beper

6–6 Application Layer Message PacketsPublication 17706.5.16 - October 1996STS and EXT STSThese bytes work together to indicate the status of the mess

6–7Application Layer Message PacketsPublication 17706.5.16 - October 1996TNSThe TNS (transaction) bytes contain a unique 16-bit transactionidentifier

6–8 Application Layer Message PacketsPublication 17706.5.16 - October 1996ADDRThe ADDR (address) bytes contain the byte address of a memorylocation i

Chapter 7Publication 17706.5.16 - October 1996Communication CommandsThis chapter contains the format you should use when sendingcommunication comman

7–2 Communication CommandsPublication 17706.5.16 - October 1996Use this table to locate commands you want to use. For additionalinformation on the c

Table of Contentsvi1775 Cat. Nos. 9-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1775KA,S5,SR5 DH Diagnostic Counters 9

7–3Communication CommandsPublication 17706.5.16 - October 1996Command PageProcessorsFNCCMDMicroLogix1000SLC500ÃSLC5/03SLC5/041774PLCPLC2 PLC3 PLC

7–4 Communication CommandsPublication 17706.5.16 - October 1996apply port configurationChanges the configuration of some or all ports. If there are

7–5Communication CommandsPublication 17706.5.16 - October 1996change modeMicroLogix 1000Changes the mode of the MicroLogix processor.FNC3ADST SRCSRC

7–6 Communication CommandsPublication 17706.5.16 - October 1996diagnostic status Reads a block of status information from an interface module. The

7–7Communication CommandsPublication 17706.5.16 - October 1996download all request (download) Places a PLC-5 processor in Download mode before downlo

7–8 Communication CommandsPublication 17706.5.16 - October 1996download request (download privilege)Used by a computer to inform an interface module

7–9Communication CommandsPublication 17706.5.16 - October 1996enable outputsReturns control of the outputs to the 1774-PLC ladder diagramprogram. Us

7–10 Communication CommandsPublication 17706.5.16 - October 1996enter upload mode Puts the PLC-2 processor in Upload mode. Use this command on aPLC

7–11Communication CommandsPublication 17706.5.16 - October 1996file write (write file)Writes data, starting at a file symbol or block address. This

7–12 Communication CommandsPublication 17706.5.16 - October 1996initialize memory Resets the processor’s memory to the default directory (the direct