advertisement
MicroLogix 1500 Programmable Controllers User Manual
DF1 Half-Duplex Protocol
DF1 Half-Duplex protocol provides a multi-drop single master/multiple slave network. DF1 Half-Duplex protocol supports data transparency (American National
Standards Institute ANSI - X3.28-1976 specification subcategory D1). In contrast to
DF1 Full-Duplex, communication takes place in one direction at a time. You can use the RS-232 port on the MicroLogix 1500 as both a Half-Duplex programming port, and a Half-Duplex peer-to-peer messaging port.
DF1 Half-Duplex Operation
The master device initiates all communication by “polling” each slave device. The slave device may only transmit message packets when it is polled by the master. It is the master’s responsibility to poll each slave on a regular and sequential basis to allow slave devices an opportunity to communicate. During a polling sequence, the master polls a slave either repeatedly until the slave indicates that it has no more message packets to transmit or just one time per polling sequence, depending on how the master is configured.
An additional feature of the DF1 Half-Duplex protocol is that it is possible for a slave device to enable a MSG instruction in its ladder program to send or request data to/ from another slave. When the initiating slave is polled, the MSG instruction is sent to the master. The master recognizes that the message is not intended for it, but for another slave, so the master immediately forwards the message to the intended slave.
This slave-to-slave transfer is a function of the master device and is also used by programming software to upload and download programs to processors on the DF1
Half-Duplex link.
The MicroLogix 1500 can only act as a slave device. A device that can act as a master is required. Several Allen-Bradley products support DF1 Half-Duplex master protocol. They include the SLC 5/03™ and higher, and enhanced PLC-5
®
processors.
Rockwell Software WINtelligent LINX™ and RSLinx (version 2.x and higher) also support DF1 Half-Duplex master protocol.
DF1 Half-Duplex supports up to 255 devices (address 0 to 254) with address 255 reserved for master broadcasts. The MicroLogix 1500 supports broadcast reception but cannot initiate a broadcast command. The MicroLogix 1500 supports Half-
Duplex modems using RTS/CTS hardware handshaking.
D-4
Understanding the Communication Protocols
When the system driver is DF1 Half-Duplex Slave, the following parameters can be changed:
Table 25-2: DF1 Half-Duplex Configuration Parameters
Parameter
Baud Rate
Options
300, 600, 1200, 2400, 4800, 9600, 19.2K, 38.4K
Parity
Source ID (Node
Address)
Control Line none, even
0 to 254 decimal no handshaking, Half-Duplex modem handshaking
1200 none
1
Default
Error Detection
EOT Suppression
Duplicate Packet
(Message) Detect
CRC, BCC enabled, disabled
When EOT Suppression is enabled, the slave does not respond when polled if no message is queued. This saves modem transmission power when there is no message to transmit.
enabled, disabled
Detects and eliminates duplicate responses to a message. Duplicate packets may be sent under noisy communication conditions if the sender’s Message Retries are not set to 0.
Poll Timeout (x20 ms) 0 to 65535 (can be set in 20 ms increments)
Poll Timeout only applies when a slave device initiates a MSG instruction. It is the amount of time that the slave device waits for a poll from the master device. If the slave device does not receive a poll within the Poll Timeout, a MSG instruction error is generated, and the ladder program needs to requeue the MSG instruction. If you are using a MSG instruction, it is recommended that a Poll Timeout value of zero not be used. Poll Timeout is disabled when set to zero.
RTS Off Delay (x20 ms)
RTS Send Delay (x20 ms)
0 to 65535 (can be set in 20 ms increments)
Specifies the delay time between when the last serial character is sent to the modem and when RTS is deactivated. Gives the modem extra time to transmit the last character of a packet.
0 to 65535 (can be set in 20 ms increments)
Specifies the time delay between setting RTS until checking for the CTS response. For use with modems that are not ready to respond with CTS immediately upon receipt of RTS.
Message Retries
Pre Transmit Delay
(x1 ms)
0 to 255
Specifies the number of times a slave device attempts to resend a message packet when it does not receive an ACK from the master device. For use in noisy environments where message packets may become corrupted in transmission.
0 to 65535 (can be set in 1 ms increments)
• When the Control Line is set to no handshaking, this is the delay time before transmission. Required for 1761-NET-AIC physical Half-Duplex networks. The 1761-
NET-AIC needs delay time to change from transmit to receive mode.
• When the Control Line is set to DF1 Half-Duplex Modem, this is the minimum time delay between receiving the last character of a packet and the RTS assertion.
no handshaking
CRC disabled enabled
50
0
0
3
0
D-5
MicroLogix 1500 Programmable Controllers User Manual
Rockwell Software WINtelligent LINX,
RSLinx 2.0 (or higher), SLC 5/03, SLC
5/04, and SLC 5/05, or PLC-5 processors configured for DF1 Half-
Duplex Master.
RS-232 (DF1 Protocol)
MicroLogix 1500
Programmable
Controller
SLC 5/03 Processor
Modular Controller
MicroLogix 1500
Programmable Controllers
SLC 500 Fixed I/O
Controller with 1747-KE
Interface Module
Note:
It is recommended that isolation (1761-NET-AIC) be provided between the
MicroLogix 1500 and the modem.
Considerations When Communicating as a DF1 Slave on a Multi-drop Link
When communication is between either your programming software and a
MicroLogix 1500 Programmable Controller or between two MicroLogix 1500
Programmable Controllers via a slave-to-slave connection on a larger multi-drop link, the devices depend on a DF1 Master to give each of them polling permission to transmit in a timely manner. As the number of slaves increases on the link (up to 254), the time between when your programming software or the MicroLogix 1500
Controller is polled also increases. This increase in time may become larger if you are using low baud rates.
As these time periods grow, the following values may need to be changed to avoid loss of communication:
• programming software: increase poll timeout and reply timeout values
• MicroLogix 1500 Programmable Controller: increase poll timeout
D-6
Understanding the Communication Protocols
Ownership Timeout
When a program download sequence is started by a software package to download a ladder logic program to a MicroLogix 1500 controller, the software takes “program ownership” of the processor. Program ownership prevents other devices from reading from or writing to the processor while the download is in process. Once the download is completed, the programming software returns the program ownership to the controller, so other devices can communicate with it again.
The controller clears the program ownership if no supported commands are received from the owner within the timeout period. If the program ownership were not cleared after a download sequence interruption, the processor would not accept commands from any other device because it would assume another device still had program ownership.
Important:
If a download sequence is interrupted, due to electromagnetic interference or other events, discontinue communications to the controller for the ownership timeout period and then restart the program download. The ownership timeout period is 60 seconds.
After the timeout, you can re-establish communications with the processor and try the program download again. The only other way to remove program ownership is to cycle power on the processor.
D-7
MicroLogix 1500 Programmable Controllers User Manual
Using Modems with MicroLogix 1500 Programmable Controllers
The types of modems that you can use with MicroLogix 1500 controllers include dialup phone modems, leased-line modems, radio modems and line drivers.
For point-to-point Full-Duplex modem connections that do not require any modem handshaking signals to operate, use DF1 Full-Duplex protocol. For point-to-point
Full-Duplex modem connections that require RTS/CTS handshaking, use DF1 Full-
Duplex protocol.
For multi-drop modem connections, or for point-to-point modem connections that require RTS/CTS handshaking, use DF1 Half-Duplex slave protocol. In this case, one
(and only one) of the other devices must be configured for DF1 Half-Duplex master protocol.
Important:
Never attempt to use DH485 protocol through modems under any circumstance.
Note:
All MicroLogix 1500 controllers support RTS/CTS modem handshaking when configured for DF1 Full-Duplex protocol with the control line parameter set to Full-Duplex Modem Handshaking or DF1 Half-Duplex slave protocol with the control line parameter set to “Half-Duplex Modem”.
No other modem handshaking lines (i.e. Data Set Ready, Carrier Detect and
Data Terminal Ready) are supported by any MicroLogix 1500 controllers.
Dial-Up Phone Modems
Dial-up phone line modems support point-to-point Full-Duplex communications.
Normally a MicroLogix 1500 controller, on the receiving end of the dial-up connection, will be configured for DF1 Full-Duplex protocol with the control line parameter set for Full-Duplex modem. The modem connected to the MicroLogix
1500 controller must support auto-answer. The MicroLogix 1500 has no means to cause its modem to initiate or disconnect a phone call, so this must be done from the site of the remote modem.
D-8
Understanding the Communication Protocols
Leased-Line Modems
Leased-line modems are used with dedicated phone lines that are typically leased from the local phone company. The dedicated lines may be in a point-to-point topology supporting Full-Duplex communications between two modems or in a multi-drop topology supporting Half-Duplex communications between three or more modems. In the point-to-point topology, configure the MicroLogix 1500 controllers for DF1 Full-Duplex protocol. In the multi-drop topology, configure the MicroLogix
1500 controllers for DF1 Half-Duplex slave protocol with the control line parameter set to “Half-Duplex Modem”.
Radio Modems
Radio modems may be implemented in a point-to-point topology supporting either
Half-Duplex or Full-Duplex communications, or in a multi-drop topology supporting
Half-Duplex communications between three or more modems. In the point-to-point topology using Full-Duplex radio modems, configure the MicroLogix 1500 controllers for DF1 Full-Duplex protocol. In the point-to-point topology using Half-
Duplex radio modems, or multi-drop topology using Half-Duplex radio modems, configure the MicroLogix 1500 controllers for DF1 Half-Duplex slave protocol. If these radio modems require RTS/CTS handshaking, configure the control line parameter to “Half-Duplex Modem”.
Line Drivers
Line drivers, also called short-haul “modems”, do not actually modulate the serial data, but rather condition the electrical signals to operate reliably over long transmission distances (up to several miles). Allen-Bradley’s AIC+ Advanced
Interface Converter is a line driver that converts an RS-232 electrical signal into an
RS485 electrical signal, increasing the signal transmission distance from 50 to 4000 feet.
In a point-to-point line driver topology, configure the MicroLogix 1500 controller for
DF1 Full-Duplex protocol. In a multi-drop line driver topology, configure the
MicroLogix 1500 controllers for DF1 Half-Duplex slave protocol. If the line drivers that are used require RTS/CTS handshaking, configure the Control Line parameter to
Half-Duplex Modem.
D-9
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 4 Who Should Use this Manual
- 4 Purpose of this Manual
- 6 Common Techniques Used in this Manual
- 6 Allen-Bradley Support
- 16 Hardware Overview
- 17 Component Descriptions
- 20 Communication Options
- 22 Agency Certifications
- 23 Compliance to European Union Directives
- 24 General Considerations
- 25 Safety Considerations
- 27 Power Considerations
- 29 Preventing Excessive Heat
- 29 Master Control Relay
- 34 Base Unit Mounting Dimensions
- 34 Controller Spacing
- 35 Mounting the Controller
- 39 Installing Controller Components
- 48 Wire Requirements
- 51 Using Surge Suppressors
- 54 Grounding the Controller
- 55 Wiring Diagrams
- 55 Sinking and Sourcing Circuits
- 61 Controller I/O Wiring
- 64 Default Communication Configuration
- 65 Using the Communications Toggle Push Button
- 66 Connecting to the RS-232 Port
- 71 Connecting to a DH485 Network
- 75 Connecting the AIC+
- 83 DeviceNet Communications
- 85 Embedded I/O
- 85 Expansion I/O
- 86 I/O Configuration
- 87 I/O Forcing
- 88 Input Filtering
- 89 Latching Inputs
- 93 Controller Memory
- 96 Data Files
- 97 Protecting Data Files During Download
- 100 Password Protection
- 101 Clearing the Controller Memory
- 102 Allow Future Access Setting (OEM Lock)
- 103 Function Files
- 110 Trim Pot Operation
- 112 Data Access Tool (DAT)
- 112 DAT Keypad and Indicator Light Functions
- 114 Power-Up Operation
- 115 DAT Function File
- 122 F1 and F2 Functions
- 123 Working Screen Operation
- 123 Non-Existent Elements
- 123 Controller Faults
- 124 Error Conditions
- 126 Real Time Clock Operation
- 129 Memory Module Operation
- 135 High Speed Counter (HSC) Function File
- 137 High Speed Counter Function File Sub-Elements Summary
- 138 HSC Function File Sub-Elements
- 162 HSL - High Speed Counter Load
- 164 RAC - Reset Accumulated Value
- 166 PTO - Pulse Train Output Instruction
- 166 Pulse Train Output Function
- 171 Pulse Train Outputs (PTO) Function File
- 172 Pulse Train Output Function File Sub-Elements Summary
- 185 PWM - Pulse Width Modulation Instruction
- 185 PWM Function
- 186 Pulse Width Modulated (PWM) Function File
- 187 Pulse Width Modulated Function File Elements Summary
- 192 Instruction Set
- 193 Using the Instruction Descriptions
- 199 XIC - Examine if Closed XIO - Examine if Open
- 201 OTE - Output Energize
- 202 OTL - Output Latch OTU - Output Unlatch
- 204 ONS - One Shot
- 205 OSR - One Shot Rising OSF - One Shot Falling
- 208 Timer Instructions Overview
- 211 TON - Timer, On-Delay
- 212 TOF - Timer, Off-Delay
- 213 RTO - Retentive Timer On
- 217 CTU - Count Up CTD - Count Down
- 218 RES - Reset
- 221 Using the Compare Instructions
- 222 EQU - Equal NEQ - Not Equal
- 223 GRT - Greater Than LES - Less Than
- 224 GEQ - Greater Than or Equal To LEQ - Less Than or Equal To
- 225 MEQ - Mask Compare for Equal
- 227 LIM - Limit Test
- 231 Using the Math Instructions
- 232 Updates to Math Status Bits
- 233 ADD - Add SUB - Subtract
- 234 MUL - Multiply DIV - Divide
- 235 NEG - Negate
- 235 CLR - Clear
- 236 SCL - Scale
- 237 SCP - Scale with Parameters
- 239 SQR - Square Root
- 241 Using Decode and Encode Instructions
- 242 DCD - Decode 4 to 1-of-16
- 243 ENC - Encode 1-of-16 to 4
- 245 FRD - Convert from Binary Coded Decimal (BCD)
- 249 TOD - Convert to Binary Coded Decimal (BCD)
- 252 Using Logical Instructions
- 253 Updates to Math Status Bits
- 254 AND - Bit-Wise AND
- 255 OR - Logical OR
- 256 XOR - Exclusive OR
- 257 NOT - Logical NOT
- 259 MOV - Move
- 261 MVM - Masked Move
- 265 COP - Copy File
- 266 FLL - Fill File
- 268 BSL - Bit Shift Left
- 270 BSR - Bit Shift Right
- 272 FFL - First In, First Out (FIFO) Load
- 275 FFU - First In, First Out (FIFO) Unload
- 278 LFL - Last In, First Out (LIFO) Load
- 281 LFU - Last In, First Out (LIFO) Unload
- 285 SQC- Sequencer Compare
- 289 SQO- Sequencer Output
- 293 SQL - Sequencer Load
- 297 JMP - Jump to Label
- 297 LBL - Label
- 298 JSR - Jump to Subroutine
- 298 SBR - Subroutine Label
- 299 RET - Return from Subroutine
- 299 SUS - Suspend
- 300 TND - Temporary End
- 300 END - Program End
- 301 MCR - Master Control Reset
- 305 IIM - Immediate Input with Mask
- 307 IOM - Immediate Output with Mask
- 309 REF- I/O Refresh
- 310 Information About Using Interrupts
- 316 User Interrupt Instructions
- 316 INT - Interrupt Subroutine
- 317 STS - Selectable Timed Start
- 318 UID - User Interrupt Disable
- 319 UIE - User Interrupt Enable
- 321 UIF - User Interrupt Flush
- 322 Using the Selectable Timed Interrupt (STI) Function File
- 328 Using the Event Input Interrupt (EII) Function File
- 334 The PID Concept
- 335 The PID Equation
- 336 PD Data File
- 338 Input Parameters
- 340 Output Parameters
- 343 Tuning Parameters
- 352 Runtime Errors
- 354 Analog I/O Scaling
- 355 Application Notes
- 365 MicroLogix 1500 Messaging Overview
- 377 Remote Messages
- 381 MSG Instruction Error Codes
- 384 Timing Diagram for MicroLogix 1500 MSG Instruction
- 387 Service Communications (SVC)
- 390 Examples: Ladder Logic
- 391 Using Local Messaging
- 397 Using Remote Messaging
- 400 Example 2 - Passthru via DH485 Channel 0 of the SLC 5/04 Processor
- 403 Example - Passthu using Two 1785-KA5s
- 414 Controller Dimensions
- 415 Compact I/O Dimensions
- 415 Transistor Output Transient Pulses
- 416 MicroLogix 1500 Replacement Kits
- 417 Lithium Battery (1747-BA)
- 421 Replacement Doors
- 423 Replacement Terminal Blocks
- 425 Understanding the Controller LED Status
- 427 Controller Error Recovery Model
- 428 Identifying Controller Faults
- 437 Calling Allen-Bradley for Assistance
- 438 RS-232 Communication Interface
- 439 DF1 Full-Duplex Protocol
- 441 DF1 Half-Duplex Protocol
- 447 DH485 Communication Protocol
- 458 System Loading Limitations
- 461 System Loading Worksheet
- 463 Calculating Heat Dissipation
- 464 Programming Instructions Memory Usage and Execution Time
- 471 Scan Time Worksheet
- 472 Status File Overview
- 474 Status File Details