GuardPLC Controller Systems Bulletin 1753, 1754, 1755 User Manual
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 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Summary of Changes The information below summarizes the changes to this manual since the last publication. To help you find new and updated information in this release of the manual, we have included change bars as shown to the right of this paragraph.
Summary of Changes Notes: 4 Publication 1753-UM001C-EN-P - March 2010
Table of Contents Preface Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . 17 Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Chapter 1 Overview of Safety Controllers Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Concept . . . . . . . . . . . . . . . . . . . . . . . . Response to Faults . . . . . . . . . . . . . . . . . . . Safe States . . .
Table of Contents Chapter 3 General Wiring Considerations Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prevent Electrostatic Discharge . . . . . . . . . . . . . . . . . . . Power Supply Considerations . . . . . . . . . . . . . . . . . . . . Ground the Equipment . . . . . . . . . . . . . . . . . . . . . . . . . Considerations for Grounding All Controllers . . . . . . GuardPLC 1200 Controller . . . . . . . . . . . . . . . . . . . .
Table of Contents Wire the 1755-OF8 Analog Output Module. . . . . . . . . . . . . . 66 Wire the 1755-HSC Counter Modules . . . . . . . . . . . . . . . . . . 68 Chapter 6 Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . Safety-related Digital Inputs . . . . . . . . . . . . . . . Safety-related Digital Outputs . . . . . . . . . . . . . Power Supply Connections . . . . . . . . . . . . . . . Wire the 1753-IB16 Input Module . . . . . . . . .
Table of Contents Chapter 9 Wire the 1753-IF8XOF4 Analog I/O Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Safety-related Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . 95 Module Voltage Measurement. Current Measurement . Terminal Connections Standard Analog Outputs. Terminal Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 14 Use the Control Panel to Monitor Status Introduction . . . . . . . . . . . . . . . . . . . . Resource State Tab . . . . . . . . . . . . . . . Safety Parameters Tab . . . . . . . . . . . . . Statistics Tab . . . . . . . . . . . . . . . . . . . . P2P (Peer-to-Peer) State Tab . . . . . . . . Distributed I/O Tab. . . . . . . . . . . . . . . HH (High-level High-speed) State Tab . Environment Data Tab . . . . . . . . . . . . OS Tab . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Network Configuration . . . . . . . . . . . . . . . . . . . . HH Protocol Parameters . . . . . . . . . . . . . . . . . . . Token Group ID . . . . . . . . . . . . . . . . . . . . . . Protocol Mode . . . . . . . . . . . . . . . . . . . . . . . . Link Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . Response Time . . . . . . . . . . . . . . . . . . . . . . . Token Cycle Time . . . . . . . . . . . . . . . . . . . . . Token Alive Timeout . . . . . . . . . . . . . . . . . . .
Table of Contents Configure Peer-to-peer Communication . . . . . . . . . Define Controller Connections . . . . . . . . . . . . . Assign HH-Network . . . . . . . . . . . . . . . . . . . . . Choose a Peer-to-peer Profile . . . . . . . . . . . . . . Define Peer-to-peer Parameters . . . . . . . . . . . . Define The Signals to Exchange Between Each Controller Connection . . . . . . . . . . . . . . . . . . . Compile and Download . . . . . . . . . . . . . . . . . . . . Compile Logic . . . . . . . . . . . . . . .
Table of Contents Chapter 19 Use GuardPLC Controller as an Adapter Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the GuardPLC Controller as an Adapter . . . . . . . Configure the Adapter Input Assembly . . . . . . . . . . . . . Configure the Adapter Output Assembly . . . . . . . . . . . . Connect Signals to the Adapter Assemblies . . . . . . . . . . Open a Class 1 Connection from a Logix Controller to the GuardPLC Controller . . . . . . . . . . . . . . . . .
Table of Contents Configure Connections in RSNetWorx for EtherNet/IP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open a Connection to a Logix Controller . . . . . . . . . . . . . Create a Producing Data Tag . . . . . . . . . . . . . . . . . . . Configure Connections from the GuardPLC Controller to the Logix Controller . . . . . . . . . . . . . . . . . . . . . . . . Save the Connection Configuration in the GuardPLC Controller . . . . . . . . . . . . . . . . . . . . . .
Table of Contents GuardPLC 2000 Controller . . . . . . . . . . . . . GuardPLC 2000 Distributed I/O Modules . . 1755-IB24XOB16 Digital I/O Module . . 1755-IF8 Analog Input Module . . . . . . . 1755-OF8 Analog Output Module . . . . . 1755-HSC High Speed Counter Module. GuardPLC 2000 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Appendix C Wiring Examples Introduction . . . . . . . . . . . . . . . . . . . . . . . . . GuardPLC 1600 Controller . . . . . . . . . . . . . . . GuardPLC 1800 Controller . . . . . . . . . . . . . . . 1753-IB16 Modules . . . . . . . . . . . . . . . . . . . . 1753-OB16 Modules . . . . . . . . . . . . . . . . . . . 1753-IB20XOB8 Module . . . . . . . . . . . . . . . . 1753-IB8XOB8 Modules . . . . . . . . . . . . . . . . 1753-IB16XOB8 Modules. . . . . . . . . . . . . . . . 1753-OW8 Modules. .
Table of Contents 16 Publication 1753-UM001C-EN-P - March 2010
Preface Who Should Use This Manual Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use GuardPLC controllers. Personnel responsible for installation, programming, operation, and troubleshooting of safety-related controllers must be familiar with relevant safety standards for programmable electronic systems (PES). Purpose of This Manual The manual only briefly describes the safety concept of the GuardPLC family of controllers.
Preface Preface Resource Description Using RSLogix Guard PLUS! Software with GuardPLC Controllers Programming Manual, publication 1753-PM001 Provides procedural information for programming GuardPLC Controller Systems Using RSLogix Guard PLUS! Programming Software GuardPLC Controller Systems Safety Reference Manual, publication 1753-RM002 Contains in-depth information on the safety concept of GuardPLC controller systems, including the DeviceNet Safety Scanner for GuardPLC Controller.
Chapter 1 Overview of Safety Controllers Introduction Safety Concept Topic Page Safety Concept 19 Safe States 21 GuardPLC System Hardware 21 Communication Capabilities 27 GuardPLC controllers feature a fail-safe CPU according to IEC 61508 (SIL 3) and ISO 13849-1 (PLe/Cat. 4). Faults that cause loss of safety function are detected within the safety time you specify.
Chapter 1 Overview of Safety Controllers Response to Faults Type of I/O Error Controller Behavior Permanent If an error occurs at an I/O point, only this I/O point is considered faulty and not the entire module. In case of faulty input points, ‘0’ is assumed to be the safe value. Faulty output channels are de-energized. If it is not possible to de-energize a single point, the entire module is considered to be faulty, the entire module is de-energized, and the corresponding error status is set.
Overview of Safety Controllers Safe States Chapter 1 Inputs The safe state of an input is indicated by a 0 signal being passed to the user program logic. When a fault occurs, the inputs are switched off (0). Outputs An output is in the safe state when it is de-energized. In the event of a fault, all outputs are switched off. This includes faults in Ethernet communication.
Chapter 1 Overview of Safety Controllers GuardPLC 1600 and GuardPLC 1800 System GuardPLC 1600 Controller RJ-45 Ethernet Ports (on Top of Controller) Digital Outputs Voltage Supply Connection RS-485 Serial Ports (See Page 23) Digital Inputs RJ-45 Ethernet Ports (on Bottom of Controller) GuardPLC 1800 Controller RJ-45 Ethernet Ports (on Top of Controller) Digital Outputs Voltage Supply Connection Digital Inputs RS-485 Serial Ports High Speed Counter (See Page 23) RJ-45 Ethernet Ports (on Bottom o
Overview of Safety Controllers Chapter 1 Three ports are located on the front of the controller, providing these non-safety-related communication options.
Chapter 1 Overview of Safety Controllers GuardPLC 1753 Digital I/O Modules 1753-OB16 Module 1753-IB16 Module Digital Inputs Voltage Supply Connection L- L- L+ L+ Voltage Supply Connection 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 LS+ 1 2 3 4 L- LS+ 5 6 7 8 L- LS+ 9 10 11 12 L- Digital Outputs 13 14 15 16 17 18 1 2 3 4 5 6 24V DC D1 D1 Digital Outputs Voltage Supply Connection 7 8 9 10 11 12 1 2 3 4 5 6 D1 L- L- L+ 7 8 9 10 11 12 L+ L- L- 24V DC
Overview of Safety Controllers Chapter 1 1753 Relay Output and Analog I/O Modules 1753-OW8 Module Relay Outputs Voltage Supply Connection 1 L- L- L+ 24V DC L+ 2 3 DO 1 4 5 DO 2 1753-IF8XOF4 Module Safety Analog Inputs Voltage Supply Connection 6 7 DO 3 8 L- L- DO 4 L+ L+ 24V DC 24 V DC 1753-IF8XOF4 8 Analog Inputs 4 Analog Outputs RUN ERROR PROG 1753-OW8 FORCE 8 Digital Outputs FAULT AI AI T1 I1 L- T2 I2 L- AI T3 I3 L- T4 I4 7 9 L- T5 I5 AO O1 AI L- T6 I6 L- T7
Chapter 1 Overview of Safety Controllers GuardPLC 2000 Controller, Power Supply, and I/O Modules GuardPLC 2000 I/O Modules GuardPLC 2000 Power Supply GuardPLC 2000 Controller 1755PB720 1755L1 RUN STOP PROG Ethernet Port FAULT FORCE GuardPLC 2000 1755IB24XOB16 1755IB24XOB16 RUN ERR RUN RUN ERR 1755IF8 ERR RUN ERR 1755OF8 RUN ERR 1755HSC 1755HSC RUN ERR RUN ERR 1 LS+ 1 I1+ 1 O1+ 1 C- 1 C- 2 I1 2 I1 2 I- 2 O1- 2 A1 2 A1 3 I2 3 I2 3 I2+ 3 O2+ 3 B1 3 B1 4
Overview of Safety Controllers Chapter 1 1755-OF8 Analog Output Module The 1755-OF8 analog output module provides eight outputs, galvanically isolated in groups of 2 (that is, 2 outputs per power supply). They are electrically isolated from the processor system. Each analog output can operate as a current source or a voltage source. 1755-HSC High Speed Counter Module The 1755-HSC counter module provides two counters and four digital outputs. They are electrically isolated from the processor system.
Chapter 1 Overview of Safety Controllers GuardPLC Ethernet Networking Example Star Configuration 1 2 3 4 5 6 L- L- L+ Daisy-chain (Line) Configuration 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 DO L- 1 2 3 4 L- DO L- 7 8 9 10 L- L+ 24V DC (2A) (2A) 24 V DC To Programming Terminal RUN ERROR PROG FORCE FAULT 1753-IB20OXB8 20 DC Inputs 8 DC Outputs OSL To Programming Terminal BL D1 LS+ 1 2 3 4 L- D1 LS+ 5 6 7 8 L- 13 14 15 16 17 18 D1 LS+ 9 10 11 12 L- D1 LS+ 13 14 15 16 L- D1 LS+ 17
Overview of Safety Controllers Chapter 1 High-speed Safety Protocol GuardPLC 1600 and 1800 controllers support High-speed Safety Protocol (HSP), which allows them to connect to the DeviceNet safety network via the 1753-DNSI DeviceNet Safety Scanner. Refer to the DeviceNet Safety Scanner for GuardPLC Controllers User Manual, publication 1753-UM002, for more information.
Chapter 1 Overview of Safety Controllers OPC Server The GuardPLC 1600, GuardPLC 1800, series C GuardPLC 1200, and series C GuardPLC 2000 controllers are OPC clients. An OPC server, catalog number 1753-OPC, is available from Rockwell Automation and lets personal computer applications read and write data to and from the GuardPLC controller (non-safety-related communication only).
Chapter 2 Installation Introduction General Safety Topic Page General Safety 31 Mount the Equipment 32 Communication Connections 38 Reset Pushbutton 43 Open style devices must be provided with environmental and safety protection by proper mounting in enclosures designed for specific application conditions. See NEMA Standards 250 and IEC 60529, as applicable, for explanations of the degrees of protection provided by different types of enclosure.
Chapter 2 Installation Mount the Equipment GuardPLC 1200 Controller The GuardPLC 1200 controller can be either snapped onto a DIN rail or mounted to a back panel by using bolts. DIN rail mounting is the easiest way to attach the controller and should be used wherever possible. IMPORTANT For cooling reasons: • the GuardPLC 1200 controller must be mounted horizontally with the Ethernet socket facing down. • a location where air flows freely or use an additional cooling fan.
Installation Chapter 2 Back Panel ATTENTION Do not bend the controller. Bending the controller will damage it. Use the four brackets on the GuardPLC 1200 controller to mount it onto a back panel. Top Brackets Use the following to mount the controller.
Chapter 2 Installation GuardPLC 1600 and GaurdPLC 1800 controllers and I/O cannot be panel-mounted. Mount these controllers and distributed I/O to a DIN rail by following the steps below. 1. Hook the top slot over the DIN rail. 2. Insert a flathead screwdriver into the gap between the housing and the latch and pull the latch downward. (1) Top Slot (3) DIN Rail (2) Latch 3. Hold the latch down as you push the housing back onto the DIN rail. 4. Release the latch to lock the device onto the rail.
Installation Chapter 2 IMPORTANT • The chassis must be installed without any modules inserted. • Disconnect the supply voltage before mounting the chassis. • The chassis must be vertically mounted with the cooling fans on the lower side. • Do not obstruct ventilation openings. • Provide a gap of at least 100 mm (3.94 in.) above and below the device and at least 20 mm (0.79 in.) horizontally between devices. Modules are shown for illustration only.
Chapter 2 Installation GuardPLC 2000 Controller, I/O, and Power Supply Mount the GuardPLC 2000 chassis prior to installing the controller, I/O, and power supply. IMPORTANT Disconnect the power supply, 1755-PB720, from the 24V DC supply voltage before you insert any I/O modules. 1. Before you insert the device, you must detach the grounding grill. To do this, remove the grounding grill screws. grounding grill screws 2. Remove the lower panel of the chassis and disconnect the fans. 3.
Installation Chapter 2 6. Secure the device with the screws on the top and bottom of the device (see the figure below).
Chapter 2 Installation Communication Connections Connections for safety and non-safety related communication for GuardPLC controllers and distributed I/O modules are described in the following sections. GuardPLC 1200 Controller The GuardPLC 1200 controller has an ASCII serial port for non-safety-related communication and an Ethernet port for safety-related communication. Connect the ASCII port to any RS-232 device that has the capability to send ASCII command strings to the controller.
Installation Chapter 2 GuardPLC 1600 and GuardPLC 1800 Controllers Connections for safety- and non-safety-related communication are described in the following sections. Connections for Safety-Related Communication The controller has four 10/100BaseT, RJ-45 connectors to provide communication via the GuardPLC Ethernet network to other GuardPLC controllers, distributed I/O, and RSLogix Guard PLUS! software. These connectors also provide communication via an EtherNet/IP network to other Ethernet devices.
Chapter 2 Installation See Chapter 16 for information on peer-to-peer communication or Chapter 18 for information on EtherNet/IP communication. Connections for Non-Safety-Related communication Three 9-pin Min-D connectors are located on the front of the controller, providing these communication options.
Installation Chapter 2 The pin assignment of the Min-D connectors is shown in the table below.
Chapter 2 Installation GuardPLC 2000 Controller Connections for safety- and non-safety-related communication are described in the following sections. Connections for Safety-Related Communication To configure/program the GuardPLC system, the controller must be connected on an Ethernet network to the RSLogix Guard PLUS! programming terminal. The GuardPLC Ethernet network also provides for peer-to-peer communication to distributed I/O and to other controllers.
Installation Reset Pushbutton Chapter 2 GuardPLC 1600 and 1800 controllers and distributed I/O are equipped with a reset pushbutton. Reset via the pushbutton is necessary if you: • forget the password to go online via the programming software. • are unable to determine the IP address and SRS of the controller. The pushbutton is accessible through a small round hole at the top of the housing, approximately 4…5 cm (1.6…2.0 in.) from the left rim and recessed approximately 9.5 mm (0.375 in.).
Chapter 2 Installation Notes: 44 Publication 1753-UM001C-EN-P - March 2010
Chapter 3 General Wiring Considerations Introduction Prevent Electrostatic Discharge Topic Page Prevent Electrostatic Discharge 45 Power Supply Considerations 45 Ground the Equipment 46 Terminal Connections 47 Shield-contact Plate Connections 48 Detailed Wiring Information 48 ATTENTION Electrostatic discharge can damage integrated circuits or semiconductors. Follow these guidelines when you handle the module.
Chapter 3 General Wiring Considerations The 24V DC voltage supply must feature galvanic isolation because inputs and outputs are not electrically isolated from the internal processor.(1) To comply with CE Low Voltage Directives (LVD), you must use either an NEC Class 2, a Safety Extra Low Voltage (SELV) or a Protective Extra Low Voltage (PELV) power supply to power the GuardPLC controller or I/O module. A SELV supply cannot exceed 30V rms, 42.
General Wiring Considerations Chapter 3 GuardPLC 1600 and GuardPLC 1800 Controllers and Distributed I/O The I/O module is functionally grounded through its DIN rail connection. A protective earth ground connection is required and is provided by a separate grounding screw, located on the upper left of the housing and marked with the grounding symbol . ATTENTION This product is grounded through the DIN rail to chassis ground. Use zinc plated yellow-chromate steel DIN rail to assure proper grounding.
Chapter 3 General Wiring Considerations Shield-contact Plate Connections Shielded cabling is fed in from below so that the shielding can be connected to the shield-contact plate by using a clip. Remove about 2 cm (0.79 in.) of the outer cable insulation so that the mesh is exposed at the point where the cable is clipped to the plate. Position the clip over the uninsulated cable shielding and push it into the slots of the shield contact plate until it fits firmly in place, as shown below.
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Introduction Power Supply Connections Topic Page Power Supply Connections 49 Safety-related Digital Inputs 50 Safety-related Digital Outputs 51 Safety-related Analog Inputs 51 High-speed Counters 52 Wire the GuardPLC 1600 Controller 53 Wire the GuardPLC 1800 Controller 54 Wire the GuardPLC 1200 Controller 58 Power supply connections for GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 controllers are described i
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers GuardPLC 1200 Controller Both L+ and L- terminals must be used in parallel to allow the maximum current of 8 A. (Each terminal maximum is 4 A so both are required for 8 A.) If the power supply has only one (+) lead, a short bridge jumper must be installed between L+(1) and L+(2). TIP Safety-related Digital Inputs The GuardPLC 1200 controller requires approximately 0.5 A to operate. The remaining 7.
Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Safety-related Digital Outputs Chapter 4 The status of digital outputs is indicated via status indicators when the controller or module is in Run mode. GuardPLC outputs are rated to either 0.5 A or 1.0 A at an ambient temperature of 60 °C (140 °F). At an ambient temperature of 50 °C (122 °F), outputs rated at 1.0 A increase to 2.0 A. If an overload occurs, the affected outputs are turned off.
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers High-speed Counters The GuardPLC 1200 and 1800 controllers feature inputs for high-speed counting up to a maximum of 100 kHz. These counters are 24-bit, and are configurable for either 5V or 24V DC. The counters can be used as a counter or as a decoder for 3-bit Gray Code inputs. As a counter, input A is the counter input, input B is the counter direction input, and input Z is used for a reset.
Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Wire the GuardPLC 1600 Controller Chapter 4 Input and output terminal connections for the GuardPLC 1600 controller are described below.
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Safety-related Digital Output Terminals 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 DO L- 1 2 3 4 L(2 A) DO L- 5 6 7 8 L(2 A) Digital outputs are connected to these terminals. Wire the GuardPLC 1800 Controller Terminal Number Designation Function Current 1 L- Reference pole — 2 1 Digital output 1 0.5 A 3 2 Digital output 2 0.5 A 4 3 Digital output 3 0.
Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Chapter 4 Safety-related Digital Input Terminals 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 DI LS+ 1 2 3 4 5 6 7 8 L- DI LS+ 9 10 11 12 13 14 15 16 L- DI LS+ 17 18 19 20 21 22 23 24 L- Digital inputs are connected to these terminals.
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Safety-related Digital Output Terminals DO 1 2 3 4 5 6 7 8 9 10 1 2 3 4 5 6 7 8 9 10 L- 1 2 3 4 5 (2 A) 6 7 8 L(2 A) Digital outputs are connected to these terminals. Terminal Designation Number Function Current 1 L- Reference pole — 2 1 Digital output 1 0.5 A 3 2 Digital output 2 0.5 A 4 3 Digital output 3 0.5 A 5 4 Digital output 4 (for increased load) 2.
Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Chapter 4 The analog inputs are connected to these terminals.
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Safety-related High-speed Counter Terminals HSC A1 B1 Z1 L- A2 B2 Z2 65 69 66 67 68 70 L- 71 72 Counters are connected to these terminals.
Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers Terminal Number Designation Function 1 Not Used None 2 I1 Digital input 1 3 I2 Digital input 2 4 I3 Digital input 3 5 I4 Digital input 4 6 I5 Digital input 5 7 I6 Digital input 6 8 I7 Digital input 7 9 I8 Digital input 8 10 I9 Digital input 9 11 I10 Digital input 10 12 I11 Digital input 11 13 I12 Digital input 12 14 I13 Digital input 13 15 I14 Digital input 14 16 I15 Digital input 15 17 I16
Chapter 4 Wire GuardPLC 1600, GuardPLC 1800, and GuardPLC 1200 Controllers L+(1) L+(2) O1+ O2+ O3+ O4+ O5+ O6+ O7+ O8+ A1 B1 Z1 2 1 4 3 6 5 8 7 10 9 12 11 14 13 16 15 18 17 20 19 22 21 24 23 26 25 L-(1) L-(2) PA O1- O2- O3- O4- O5- O6- O7- O8- A2 B2 60 Terminal Number Designation Function 1 L- 24V DC return path 2 L+ 24V DC power input 3 L- 24V DC return path 4 L+ 24V DC power input 5 PA Functional ground I28 27 Z2 29 I- 6 O1+ Digital output 1 7 O1-
Chapter 5 Wire the GuardPLC 2000 Controller and I/O Introduction Safety-related Digital Inputs Topic Page Safety-related Digital Inputs 61 Safety-related Digital Outputs 62 Safety-Related Analog Inputs (1755-IF8) 62 High-speed Counter Module (1755-HSC) 63 Safety-related Analog Output Module (1755-OF8) 64 Current Draw 64 Wire the 1755-IB24XOB16 Digital I/O Module 65 Wire the 1755-IF8 Analog Input Module 66 Wire the 1755-OF8 Analog Output Module 66 Wire the 1755-HSC Counter Modules 6
Chapter 5 Wire the GuardPLC 2000 Controller and I/O Safety-related Digital Outputs The status of digital outputs is indicated via status indicators when the controller or module is in Run mode. GuardPLC 2000 controller outputs are rated at 2 A per point, but the total load of all 16 outputs on a single module must not exceed 8 A. If an overload occurs, the affected outputs are turned off.
Wire the GuardPLC 2000 Controller and I/O Chapter 5 Unused analog inputs must be short-circuited. Place wire jumpers to ground on any inputs that are not used. 10 11 12 13 14 15 16 17 18 I5+/1II6+/2II7+/3II8+/4I- Wire Jumper 1755-IF8 High-speed Counter Module (1755-HSC) The 1755-HSC module features inputs for high-speed counting up to 1 MHz. These counters are 24-bit, and are configurable for either 5V or 24V DC. The counters can be used as a counter or as a decoder for 3-bit Gray Code inputs.
Chapter 5 Wire the GuardPLC 2000 Controller and I/O Safety-related Analog Output Module (1755-OF8) Current Draw The 1755-OF8 module uses analog outputs to transfer analog values from the user program into outputs ranging from ±10V DC and 0…20 mA. The relationship between the value in the user program and the output value is linear and is displayed in this table. Logic Value Output Voltage Output Current 0 0.00V 0.0 mA 1000 10.00V 20.0 mA -1000 -10.
Wire the GuardPLC 2000 Controller and I/O Wire the 1755-IB24XOB16 Digital I/O Module Chapter 5 This module is a combination I/O module featuring 24 safety-related digital inputs and 16 safety-related digital outputs. • Inputs: The sockets with pins 2…9, 11…18, and 20…27 provide the 24 digital inputs I1…I24. Pins 1, 10, and 19 are the common positive poles (LS+). Each group of 8 inputs has current limits of 100 mA. • Outputs: The sockets with pins 29…36 and 38…45 provide the 16 digital outputs O1…O16.
Chapter 5 Wire the GuardPLC 2000 Controller and I/O Wire the 1755-IF8 Analog Input Module This module features 8 single-ended analog inputs or 4 differential analog inputs. Two-wire or four-wire transmitters can be used. The devices cannot be powered from the GuardPLC module. An external power supply is required for all analog transmitters. Single-ended transmitters connect between the Ix+ and I- terminals. For example: pins 1 and 2, 3 and 4, 5 and 6.
Wire the GuardPLC 2000 Controller and I/O Chapter 5 There are 4 reference poles for the 8 outputs. A pair of outputs share a reference pole as shown below. These outputs Share these Reference Poles 1 and 2 O1- and O2- 3 and 4 O3- and O4- 5 and 6 O5- and O6- 7 and 8 O7- and O8- Each group of 2 outputs is electrically isolated from the others.
Chapter 5 Wire the GuardPLC 2000 Controller and I/O Wire the 1755-HSC Counter Modules This module contains 2 high-speed counters and 4 digital outputs. Although the 4 digital outputs are located on the 1755-HSC module, they cannot be driven by counter presets. The 4 digital outputs are driven by software, just as on the 1755-IB24XOB16 module. The nominal current per output is limited to ≤ 0.5 A. Currents > 0.5 A are regarded as overload.
Chapter 6 Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Introduction Safety-related Digital Inputs Topic Page Safety-related Digital Inputs 69 Safety-related Digital Outputs 70 Power Supply Connections 70 Wire the 1753-IB16 Input Module 71 Wire the 1753-OB16 Output Module 73 Wire the 1753-IB20XOB8 Combination Module 75 The status of digital inputs is indicated via status indicators when the module is in Run mode.
Chapter 6 Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Safety-related Digital Outputs The status of digital outputs is indicated via status indicators when the module is in RUN mode. GuardPLC outputs are rated to either 0.5 A or 1.0 A at an ambient temperature of 60 °C (140 °F). At an ambient temperature of 50 °C (122 °F), outputs rated at 1.0 A increase to 2.0 A. If an overload occurs, the affected outputs are turned off.
Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Wire the 1753-IB16 Input Module Chapter 6 The 1753-IB16 input module features 16 digital inputs and 4 pulse test sources. Safety-related Digital Inputs DI LS+ 1 2 3 4 L- DI LS+ 5 6 7 8 L- DI LS+ 9 10 11 12 L- DI LS+ 13 14 15 16 L- 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Digital inputs are connected to these terminals.
Chapter 6 Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Pulse Test Sources The 1753-IB16 input module is equipped with four pulse test sources that can be software-configured for pulse testing of safety inputs, if required. Due to minimal current capacity, these pulse test sources cannot be used as outputs if they are not configured as pulse test sources. ATTENTION Pulse test sources must not be used as safety-related outputs.
Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Chapter 6 Wire the 1753-OB16 Output Operating Voltage Considerations Module The 1753-OB16 output module has a total current capacity (16 A) higher than the terminal block current limitation (10 A). Therefore, it features two separate operating voltage supply connections if more than 10 A is used by the module. The two output groups are shown below. Each group has a current capacity of 8 A.
Chapter 6 Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules The digital outputs are connected to these terminals.
Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Wire the 1753-IB20XOB8 Combination Module Chapter 6 The remote I/O module features 20 digital inputs and 8 digital outputs whose status is indicate via status indicators.
Chapter 6 Wire 1753-IB16, 1753-OB16, and 1753-IB20XOB8 Modules Safety-related Digital Outputs 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 DO L- 1 2 3 4 L(2A) DO L- 5 6 7 8 L(2A) The digital outputs are connected to these terminals. 76 Terminal Number Designation Function Current 1 L- Reference pole — 2 1 Digital output 1 0.5 A 3 2 Digital output 2 0.5 A 4 3 Digital output 3 0.5 A 2.
Chapter 7 Wire and Configure the 1753-IB8XOB8 Module Introduction Topic Page Safety-related Digital Inputs 77 Safety-related Digital Outputs 78 Pulse Test Sources 81 The module features 8 digital inputs, 8 positive-switching digital outputs, 2 negative-switching digital outputs, and 2 pulsed outputs. Safety-related Digital Inputs The status of the module’s 8 digital inputs is indicated via status indicators when the controller or module is in Run mode.
Chapter 7 Wire and Configure the 1753-IB8XOB8 Module Terminal Connections LS+ 1 2 3 4 LDI LS+ 5 6 7 8 LDI 19 20 21 22 23 24 25 26 27 28 29 30 19 20 21 22 23 24 25 26 27 28 29 30 See the wire size and terminal torques specifications on page 290. Digital inputs are connected to these terminals.
Wire and Configure the 1753-IB8XOB8 Module Chapter 7 negative-switching outputs. The total output current of the module is limited to 8 A and is generated from the 24V of the system. If configured for two-pole operation, the positive-switching output DO4 operates with the negative-switching output DO4- and the positive-switching output DO8 operates with the negative-switching output DO8-.
Chapter 7 Wire and Configure the 1753-IB8XOB8 Module Terminal Connections 1 2 3 4 5 6 1 2 3 4 5 6 DO PO L- 1 2 4- 8- S+ 13 14 15 16 17 18 7 8 9 10 11 12 7 8 9 10 11 12 13 14 15 16 17 18 DO L- 1 2 3 4 L- DO L- 5 6 7 8 L- See the wire size and terminal torques specifications on page 290. Digital outputs are connected to these terminals.
Wire and Configure the 1753-IB8XOB8 Module Chapter 7 S+ DO 8- DO 4- L- DO 4 DO 3 DO 2 DO 1 L- 1-pole Connection Examples Inductive loads can be connected without a protection diode on the load. However, Rockwell Automation strongly recommends that a protection diode be fitted directly to the load to suppress any interference voltage.
Chapter 7 Wire and Configure the 1753-IB8XOB8 Module Notes: 82 Publication 1753-UM001C-EN-P - March 2010
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module Introduction Topic Page Safety-related Digital Inputs 83 Safety-related Digital Outputs 86 Monitor for Line Short Line Break 91 Pulse Test Sources 93 The module features 16 digital inputs, 8 two-pole (8 positive-switching and 8 negative-switching) digital outputs, and 2 pulsed outputs. Safety-related Digital Inputs The status of digital inputs is indicated via status indicators when the module is in Run mode.
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module supply is read and the supply is switched off if an overcurrent condition occurs. This supply is protected by a current limiting device.
Wire and Configure the 1753-IB16XOB8 Module Chapter 8 Terminal Connections LS+ LS+ 1 2 3 4 L- L- 33 34 35 36 37 38 39 40 41 42 LS+ LS+ 5 6 7 8 L- L- 43 44 45 46 47 48 49 50 51 52 LS+ LS+ 9 10 11 12 L- L- 53 54 55 56 57 58 59 60 61 62 LS+ LS+ 13 14 15 16 L- L- 63 64 65 66 67 68 69 70 71 72 See the wire size and terminal torques specifications on page 290. Digital inputs are connected to these terminals.
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module Safety-related Digital Outputs Terminal Number Designation Function 63 LS+ Sensor supply for inputs 13…16 40 mA buffered/1 A unbuffered 64 LS+ Sensor supply for inputs 13…16 40 mA buffered/1 A unbuffered 65 13 Digital input 13 66 14 Digital input 14 67 15 Digital input 15 68 16 Digital input 16 69 L- Reference pole 70 L- Reference pole 71 Ground Shield 72 Ground Shield The module has 8 digital output pairs, each with a
Wire and Configure the 1753-IB16XOB8 Module Chapter 8 1-Pole Connection For 1-pole applications, all 8 positive-switching and all 8 negative-switching outputs are available, for a total of 16 outputs. If you are using a positive-switching output, connect the other side of the output to S-. If you are using a negative-switching output, connect the other side of the output to S+. Line monitoring with a 1-pole connection is not possible.
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module 2-Pole Connection If the outputs are configured for 2-pole operation, 8 outputs are available. Each of the 8 outputs switch both L+ and L-. 2-pole outputs (without line monitoring) are wired to both the positive-switch and negative-switch of a single channel, 2+ and 2- for example. 2+ 2- IMPORTANT ATTENTION ATTENTION The corresponding channels for 2-pole connections must be configured for 2-pole operation by using the system variable DO[xx].
Wire and Configure the 1753-IB16XOB8 Module Chapter 8 3-pole Connection With Line Monitoring Two 2-pole channels can support dual-channel devices with only a single reference connection. If line monitoring is required, the channels must be configured in pairs, using the system parameter DO[xx][xx].in pairs. There are four pairs allowed: channels 1 and 2, channels 3 and 4, channels 5 and 6, and channels 7 and 8.
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module Terminal Connections See the wire size and terminal torques specifications on page 290. Digital outputs are connected to these terminals.
Wire and Configure the 1753-IB16XOB8 Module Monitor for Line Short Line Break Chapter 8 The Line Short Line Break (LSLB) monitoring measures the impedance of a load and allows the modules to detect the following faults, when LSLB monitoring is configured by using the system variable DO[xx].
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module Line Monitoring with Reduced Voltage for Resistive, Capacitive Loads For line monitoring, a 10V signal is switched on in the output circuit for the duration of the monitoring time. This kind of line monitoring is designed for resistive or resistive-capacitive loads. There is no short-circuit detection for these types of loads. To configure this type of line monitoring: • • • • set a DO.LSLB period and DO.LSLB time. set the output DO[xx].
Wire and Configure the 1753-IB16XOB8 Module Chapter 8 Required Signals for Line Monitoring Line monitoring must be configured by using these system signals for 1753-IB16XOB8 modules on the Outputs tab of the digital outputs Signal Connections dialog box in RSLogix Guard PLUS! software. Name Description Setting DO.LSLB period The time between steps in Line Short Line Break (LSLB) monitoring Values in one second increments from 1…100. DO.
Chapter 8 Wire and Configure the 1753-IB16XOB8 Module Pulse test sources are connected to these terminals. Terminal Number Designation Function 25 1 Pulse test source 1 26 1 Pulse test source 1 27 1 Pulse test source 1 28 1 Pulse test source 1 29 2 Pulse test source 2 30 2 Pulse test source 2 31 2 Pulse test source 2 32 2 Pulse test source 2 All PO1 terminals are internally connected and all PO2 terminals are internally connected.
Chapter 9 Wire the 1753-IF8XOF4 Analog I/O Module Introduction Topic Page Safety-related Analog Inputs 95 Standard Analog Outputs 97 The 1753-IF8XOF4 module features 8 safety analog inputs and 4 standard analog outputs. Safety-related Analog Inputs These input values are available. Input Channels Polarity Current or Voltage Range Safety Accuracy 8 unipolar 0…+10V 0…2000 2% 0…20 mA / 4…20 mA 0…1000(1) 0…2000(2) (1) With external 250 Ω shunt. (2) With external 500 Ω shunt.
Chapter 9 Wire the 1753-IF8XOF4 Analog I/O Module Terminal Connections Analog cabling should be no more than 300 m (984 ft) in length and must be shielded, twisted-pair cables for each measurement input. The shields must be connected at one end. IMPORTANT Short-circuit unused input channels to the reference pole by connecting wire jumpers.
Wire the 1753-IF8XOF4 Analog I/O Module Standard Analog Outputs Chapter 9 Terminal Number Designation Function 19 T7 Sensor supply 7 20 I7 Analog input 7 21 L- Reference pole input 7 22 T8 Sensor supply 8 23 I8 Analog input 8 24 L- Reference pole input 8 The module has 4 analog outputs, which are not safety-rated outputs. However, in the event of an internal error, they can be shut down safely through configuration via the user program.
Chapter 9 Wire the 1753-IF8XOF4 Analog I/O Module Terminal Connections AO 01 + - 02 03 04 + - + - + - 25 26 27 28 29 30 31 32 See the wire size and terminal torques specifications on page 292. Analog outputs (AO) are connected to these terminals.
Chapter 10 Wire the 1753-OW8 Relay Output Module Introduction Safety-related Relay Outputs Topic Page Safety-related Relay Outputs 99 Terminal Connections 99 Voltage Supply Considerations 100 The module has 8 isolated relay outputs whose status is indicated via status indicators. An output is in a safety state when it is de-energized. When a fault occurs, all outputs are switched off. Errors in one or more channels are indicated by the FAULT status indicator.
Chapter 10 Wire the 1753-OW8 Relay Output Module Terminal Number Designation Relay Output 7 DO4 Contact 4, terminal A 8 9 Contact 4, terminal B DO5 Contact 5, terminal A 10 11 Contact 5, terminal B DO6 Contact 6, terminal A 12 13 Contact 6, terminal B DO7 Contact 7, terminal A 14 15 Contact 7, terminal B DO8 Contact 8, terminal A 16 Contact 8, terminal B The output contacts are connected in pairs via terminal connectors (numbered terminals).
Chapter 11 Pulse Testing Introduction Topic Page Response to OS Configurable Faults 102 Wire for OS Configurable Line Control 103 Input Configuration for Pulse Testing 105 Pulse testing is a high-frequency diagnostic test that can detect wiring faults on input devices before demand is placed on the safety system. There are two ways to generate a pulse test in the GuardPLC family of products.
Chapter 11 Pulse Testing Consider the following when choosing a method of pulse testing: • The certified function block lets the pulse test source (output) and safety input to be on different physical nodes. The OS configured pulse test assumes that the source and input are local to the same physical controller or I/O module. • The certified function block has a pulse test fault output that can be used for status inside the user program.
Pulse Testing Wire for OS Configurable Line Control Chapter 11 GuardPLC 1600 Controller and 1753-IB20XOB8 Module Up to 8 digital outputs (DO1 to DO8) can be configured as pulsed outputs. The example below shows 2 outputs, configured as pulse test outputs, connected to the digital inputs (DI) of the same system. As a result, the connections to the digital inputs (DI) are monitored. The pulse outputs must begin at DO[01] and must be sequential.
Chapter 11 Pulse Testing 1753-IB16, 1753-IB8XOB8, and 1753-IB16XOB8 Modules The 1753-IB16 module has four digital pulse test sources (PO). The 1753-IB8XOB8 and 1753-IB16XOB8 modules have two digital pulse test sources. The example below shows 2 pulse test sources connected to the digital inputs (DI) of the same system. As a result, the connections to the digital inputs (DI) are monitored..
Pulse Testing Input Configuration for Pulse Testing Chapter 11 Set up these signals by using the Outputs tab of the digital inputs Signal Connections dialogbox in RSLogix Guard PLUS! software.
Chapter 11 Pulse Testing Notes: 106 Publication 1753-UM001C-EN-P - March 2010
Chapter 12 High-Speed Counters Introduction This chapter covers using counters in these systems: • GuardPLC 1200 controllers • GuardPLC 1800 controllers • GuardPLC 2000 controllers using a 1755-HSC module Counter/Decoder Modes Topic Page Counter/Decoder Modes 107 Understand Counter Module Configuration 109 The counters can be used in these operating modes: • Counter mode • Decoder mode The two counters can be used in different modes at the same time.
Chapter 12 High-Speed Counters Counter Mode Inputs Pins Functions A1, A2 counting input for pulses (high-signals) with falling edge of the pulses B1, B2 counting direction input, incrementing the counter with low-signal, decrementing the counter with high-signal Z1, Z2 resets inputs Resets can be made with a short high-signal. A continuous high-signal blocks the counter. Resets can also be made by the controller program.
High-Speed Counters Understand Counter Module Configuration Chapter 12 The high-speed counters can be configured for three counting modes: Counter mode with manual direction, Counter mode with direction and reset, and Decoder mode (Gray codes). Counter Mode/Manual Direction The simplest mode of operation is pulse counting with manual direction. It can be used, for example, in connection with a light barrier where counting events are to be recorded. The direction of counting is determined by the routine.
Chapter 12 High-Speed Counters Counter Mode/Direction and Reset In pulse counting with direction and reset, the state of input B is evaluated in addition to counter input A. When the B input has a low signal while the counter recognizes a negative pulse edge at its A input, the value of the counter is incremented by 1. When there is a high signal at the B input, the counter is decremented by 1. The counter is released or reset via the Z input.
High-Speed Counters Chapter 12 Decoder Mode/Gray Codes The Gray code is a binary code where the code differs by only one bit with two neighboring numbers. Gray codes are useful in mechanical encoders, because a slight change in location affects only one bit. The controller uses a Gray code (4 bits for a GuardPLC 2000 controller or 3 bits for GuardPLC 1200 and 1800 controllers) that has this structure. Step Gray Code (GuardPLC 2000) Gray Code (GuardPLC 1200, 1600, and 1800) Cnt[0x].
Chapter 12 High-Speed Counters To enable the Gray code decoder to work correctly, configure these parameters in the routine. 112 Parameter Setting Cnt[0x].5/24V Mode true for 24V or false for 5V The adjusted level also applies to inputs B and Z. You must configure this parameter with a constant. Cnt[0x].Auto Advance Sense this setting has no function on the gray code (set to false) Cnt[0x].Direction this setting has no function on the gray code (set to false) Cnt[0x].Gray Code true Cnt[0x].
Chapter 13 Controller Configuration and Modes of Operation Introduction Topic Page Controller Modes 113 Controller Configuration 117 Routine Modes 120 Load a Configuration and Routine (in Stop Mode only) 121 Test Mode of the Routine 122 The GuardPLC operating system is stored permanently in the memory of the controller. The operating system is designed to make sure that all tasks of the controller are performed in a safety-related way.
Chapter 13 Controller Configuration and Modes of Operation To put the controller in Run mode: • set the Autostart switch of the both controller and the routine. • manually choose Run mode from the programming software. If you stop the controller, it transitions from Run to Stop and interrupts the execution of the routine. The outputs of the routine and the I/O modules are reset to safe values.
Controller Configuration and Modes of Operation Chapter 13 Controller Modes BOOT Yes INIT INIT OK? Yes No Hardware/Software Errors Restart? No FAILURE_STOP STOP Hardware/Software Errors? No No Yes Hardware/Software Errors START? Yes RUN Hardware/Software Errors? Yes No No Stop Command? Yes Publication 1753-UM001C-EN-P - March 2010 115
Chapter 13 Controller Configuration and Modes of Operation Recover From a Failure_Stop If the controller is in Failure_Stop, you must restart the controller, following the steps below. 1. If the controller is not online, you must go online first. a. In the Hardware Management window, from the Online menu, choose Control Panel . b. Type the Administrator username and password on the login dialog box. TIP You can use the [Ctrl]+[A] shortcut to enter the default username (Administrator) and password. 2.
Controller Configuration and Modes of Operation Chapter 13 If a routine has already been loaded in the controller when Failure_Stop occurs, the controller goes to Stop/Valid_Configuration after booting. If Autostart Enable is activated, the routine starts up automatically. If a routine has not been loaded in the controller when Failure_Stop occurs, the controller goes to Stop/Invalid_Configuration after booting.
Chapter 13 Controller Configuration and Modes of Operation 4. Set the controller parameters based on the information the table below. IMPORTANT The safety time you specify must meet the needs of the controlled process. See the GuardPLC Controller Systems Safety Reference Manual, publication 1753-RM002. For this parameter Specify System ID (SRS) the system ID of the controller. The system ID is a component of the SRS (System, Rack, Slot), and can be in the range of 2…65535.
Controller Configuration and Modes of Operation Chapter 13 You can set these switches. This switch Specifies Default Main Enable whether CPU switches can be changed while the controller is executing. On/Enabled If Main Enable is disabled, you cannot change the settings of the other 7 switches (described below) while the controller is in operation (routine in Run). Autostart whether the controller automatically starts up after restarting the controller or applying power to the controller.
Chapter 13 Controller Configuration and Modes of Operation Routine Modes The controller runs only one routine. The following table and flowchart summarize the routine modes. Mode Description Run_Run The controller is in the Run mode. • The routine is executed cyclically by the controller. • Input data are processed in the routine. • Output data of the routine are operated. Run_Freeze The controller is in the Run mode. • The routine is not executed. • No input data are processed.
Controller Configuration and Modes of Operation Chapter 13 Routine Modes Load Routine Yes STOP Error in Routine? Yes Restart Routine? No FAILURE_STOP No No Routine start? Yes Freeze enabled? Yes RUN_FREEZE No RUN_RUN Error in Routine? Yes No No Routine stop? Yes Load a Configuration and Routine (in Stop Mode only) You can load a controller configuration and routine when: • the controller is in Stop mode. • the controller Loading Allowed switch is set.
Chapter 13 Controller Configuration and Modes of Operation The configuration and the routine are loaded together into the controller. Loading a new configuration and a new routine automatically deletes all previously loaded objects, even if the new objects are faulty. IMPORTANT Configuration changes take effect only if you re-generate code before downloading to the controller.
Chapter 14 Use the Control Panel to Monitor Status Introduction 123Publication 1753-UM001C-EN-P - March 2010 The Control Panel is your window into the online functionality of the controller. Use the tabs to modify or monitor controller status.
Chapter 14 Use the Control Panel to Monitor Status Resource State Tab This field Displays CPU State The current state of the controller. Possible states are Init, Run, Stop/Valid_Configuration, Stop/Invalid_Configuration, and Failure_Stop. See Controller Modes on page 113. COM State State of the communication portion of the controller. Possible states are Run, Stop, and OS_Loading. Program Name The routine name. The name assigned by the user to the routine. The default name is ‘Routine.
Use the Control Panel to Monitor Status Chapter 14 Safety Parameters Tab This field Displays CPU configuration CRC Cyclic redundancy check (CRC) option for the configuration in the CPU (in hexadecimal notation). This identifies the configuration loaded in the controller. System ID The system ID. Safety Time [ms] The safety time in milliseconds. Watchdog Time [ms] The watchdog time in milliseconds. Main Enable Whether controller switches can be changed while the controller is executing.
Chapter 14 Use the Control Panel to Monitor Status Statistics Tab This field Displays Cycle Time [ms] average The average cycle time (in milliseconds) of the last 50 cycles. Cycle Time [ms] last The cycle time (in milliseconds) of the last cycle. Cycle Time [ms] min The fastest cycle time (in milliseconds). Cycle Time [ms] max The slowest cycle time (in milliseconds). If this value exceeds the Watchdog Time, the controller goes to Failure_Stop. Com.
Use the Control Panel to Monitor Status Chapter 14 P2P (Peer-to-Peer) State Tab This field Displays Resource The name of the controller. System ID The network ID of the controller. State The status of the communication. RspT (last, avg, The Measured ResponseTime for a message from PES1 → PES2 → PES1, based on the network hardware, CPU cycle min, max) time, and Peer-to-Peer profile. This parameter will be optimized later.
Chapter 14 Use the Control Panel to Monitor Status Distributed I/O Tab This field Displays Resource The name of the module. System.Rack The System.Rack ID of the module. State The status of the I/O module: • Run • Stop/Valid_Configuration • Error_Stop • not connected • Stop/Invalid_Configuration HH (High-level High-speed) State Tab 128 This field Displays Bus Cycle Time The time in milliseconds for a Token cycle. The value is 0, if Token Passing is off (any Cleanroom profile).
Use the Control Panel to Monitor Status Chapter 14 Environment Data Tab This tab displays status messages in hexadecimal form for Temperature State, Power Supply State, Fan State, and Relay State. See Programming Controller Data on page 305 for an explanation of the error bits. OS Tab This field Displays Serial Number The serial number of the communication module of the controller. CPU OS The version of the operating system and the cyclic redundancy check of the operating system (in hexadecimal).
Chapter 14 Use the Control Panel to Monitor Status HSP Protocol Tab This field Displays Name The Name of the controller Controller Id The SRS of the controller Controller Receive Timeout The time limit, within which a message from the scanner must be answered Controller Resend Timeout The length of time the controller waits for an acknowledgement of a message before it resend the message Scanner Id HSP Signature A unique number that ensures that the controller’s configuration data matches the
Use the Control Panel to Monitor Status Chapter 14 EIP Protocol Tab This Field Displays Peer IP IP address of communication partner Peer Status Status of Peers, either Run or Idle. If peer does not provide run idle information, nothing can be displayed! Connection Type Displays the Connection Type, Originator or Target, that the controller acts as in this connection. Connection State The status of connection. • 1 = Connecting Configuring – In the process of opening a new connection.
Chapter 14 Use the Control Panel to Monitor Status Use the Multi Control Panel The Multi Control Panel lets you connect the programming terminal to more than one controller in the project in one window and to perform actions such as downloads, controller starts, invoking the force editor, and so forth simultaneously. 1. Open the Multi Control Panel by choosing Online>Multi Control Panel. When the Multi Control Panel is opened for the first time, it does not contain any controllers. 2.
Use the Control Panel to Monitor Status Chapter 14 The Multi Control Panel displays this controller information. This field Displays Name the controller name System.Rack the controller ID CPU State the status of the controller CPU, such as Run, Stop, Stop/Valid Configuration, Stop/Invalid Configuration, and so forth. CPU Configuration CRC the checksum (cyclic redundancy check) of the CPU configuration, displayed in hexadecimal. Avg. Cycle Time the average CPU cycle time in milliseconds.
Chapter 14 Use the Control Panel to Monitor Status These commands can be carried out by using the Multi Control Panel buttons in the button bar. Multi Control Panel Buttons Button Command Connect Connects the programming software to the selected controller(s) after loss of communication or manual disconnect. After manual disconnect, a new login with password is required. Disconnect Disconnects the programming software from the selected controller(s).
Use the Control Panel to Monitor Status Control Panel Resource Menu Chapter 14 To modify the safety settings of the controller, choose Safety from the control panel’s Resource menu . IMPORTANT Any settings you change via the Resource menu are directly updated in the controller and are saved in the project. Menu Item Description Check Consistency Compares the program running in the controller with the program you are editing in RSLogix Guard PLUS! software.
Chapter 14 Use the Control Panel to Monitor Status Control Panel Extra Menu Use the Extra menu of the Control Panel to modify communication settings and change controller operation. You must have Administrator access to use most of these menu options as indicated in the table below. Menu Item Description Set Date/Time Sets the controller clock, if Set Main Enable is activated. Enter the date as mm/dd/yy and the time as hh:mm. Change System ID (SRS) Changes the system ID (SRS) of the controller.
Use the Control Panel to Monitor Status Menu Item Description Set Backplane Type Restores backplane information. Chapter 14 The individual modules (CPU, COM, I/O) are linked to each other over the backplane. The controller requires this information to be able to conduct hardware tests. If the EEPROM that stores the backplane information loses its contents, use this menu option to write the backplane type back into the EEPROM. You must have Administrator access to be able to set the backplane type.
Chapter 14 Use the Control Panel to Monitor Status Notes: 138 Publication 1753-UM001C-EN-P - March 2010
Chapter 15 Diagnostics Introduction View Controller Diagnostics Topic Page View Controller Diagnostics 139 GuardPLC 1200 Controller Status Indicators 142 GuardPLC 1600 and GuardPLC 1800 Controllers and GuardPLC Distributed I/O 143 GuardPLC 2000 Controller Status Indicators 145 1755-IB24XOB16 Module Status Indicators 147 1755-IF8 Analog Input Module Status Indicators 148 1755-OF8 Analog Output Module Status Indicators 149 1755-HSC Combination High-speed Counter and Output Module Status I
Chapter 15 Diagnostics To display the diagnostics window, follow these steps. 1. Select the Resource and, from the Online menu, choose Diagnostics. If the Control Panel is already open, you do not have to login. Otherwise, the software asks you to log in. 2. After you successfully log in, the software displays the controller diagnostics. This field Displays Level whether the entry is Info, Warning, or Error. Date the date and time the entry was recorded.
Diagnostics Chapter 15 Choose Online or Offline Diagnostics When you start the diagnostics window, Diag. Online is automatically activated. This signals that you want all diagnostics data transferred from the controller to the diagnostics buffer in RSLogix Guard PLUS! software. As long as Diag. Online is active, new diagnostic data is transferred to this buffer as it becomes available and if the filter you selected applies. Diag. Offline disconnects communication with the controller.
Chapter 15 Diagnostics GuardPLC 1200 Controller Status Indicators The GuardPLC 1200 controller has these status indicators. PLC 1200 Indicator State Description INput On Digital input channels are high (10 … 30V DC). Off Digital input channels are off. On Digital output channels are high. Off Digital output channels are off. On This is the normal status of the controller. OUTput RUN A routine, which has been loaded into the controller, is executed.
Diagnostics Indicator State Description FAULT On The routine logic has caused an error. Chapter 15 The controller configuration is faulty. The upload of a new operating system was not successful and the operating system is corrupted. Flashing An error has occurred during a Flash ROM write cycle. One or more I/O errors have occurred. COMMunication Off None of the above errors have been detected.
Chapter 15 Diagnostics Indicator State Description PROGress On The upload of a new controller configuration is in progress. Flashing The upload of a new operating system into the Flash ROM is in progress. FORCE FAULT Off No upload of controller configuration or operating system in progress. On The controller is executing a routine (Run) and Force mode is activated by the user.
Diagnostics GuardPLC 2000 Controller Status Indicators Chapter 15 The GuardPLC 2000 controller has status indicators for: • • • • module, both the program and the communication. controller and the system hardware. routine. Ethernet communication to the programming terminal. Controller Indicators 1755L1 Indicator Status Description RUN This is the normal status of the controller (Run or Stop mode). The controller carries out communication and performs software tests.
Chapter 15 Diagnostics Routine Indicators 1755L1 RUN ERR RUN STOP Indicator Status Description RUN On The routine is in Run or Freeze. Off The routine is in Failure_Stop. STOP On The routine is in Stop or Failure_Stop. PROG On The download of a new controller configuration is in progress. Flashing The download of a new operating system into the flash ROM is in progress. Off No download of controller configuration or operating system is in progress.
Diagnostics Chapter 15 Serial Communication Indicators Indicator Status Description FB1 On Field bus no. 1 is active FB2 On Field bus no. 2 is active (serial interface module) FB1 FB2 IMPORTANT 1755-IB24XOB16 Module Status Indicators The 1755-IB24XOB16 digital combination input and output module (AB-DIO) has status indicators for: • power supply. • module status. • I/O status.
Chapter 15 Diagnostics I/O Status Status Explanation On (yellow) • Input is high • Output is energized Off • Input is low • Output is de-energized While the system is in Run mode, ERR is indicated continuously for both a module and a channel error. Depending on the type of error, the module switches off only a faulty output channel, but the operation of the other outputs continues, or all the output channels are switched off. The inputs are always in operation.
Diagnostics 1755-OF8 Analog Output Module Status Indicators Chapter 15 The 1755-OF8 analog output module (AB-AO) has status indicators for: • power supply. • module status. 1755OF8 Indicator Status Description RUN ON (green) The module has the correct operating voltage (24V DC). OFF The module has no power. ERR ON (red) If the system is in Stop mode, one or more of the inputs or outputs is faulty or the module is faulty.
Chapter 15 Diagnostics Power Supply and Module Status Indicator Status Description RUN On (green) The module has the correct operating voltage (24V DC). Off The module has no power. On (red) If the system is in Stop mode, one or more of the inputs or outputs is faulty or the module is faulty. ERR Use the RSLogix Guard PLUS! software to verify the location of the fault.
Chapter 16 Peer-to-peer Communication Overview Introduction Peer-to-peer Communication Basics Topic Page Peer-to-peer Communication Basics 151 Networking Limitations 152 Network Configuration 153 HH Protocol Parameters 153 Peer-to-peer Protocol Parameters 157 HH Network Profiles 161 Peer-to-Peer Network Profiles 168 Peer-to-peer communication is used for data exchange between two or more controllers and distributed I/O on a GuardPLC Ethernet network.
Chapter 16 Peer-to-peer Communication Overview As seen in the figure below, both the HH and the peer-to-peer protocols are vital for safe Ethernet Communication. HH protocol can be considered the wire or transport media through which messages are passed. Peer-to-peer (P2P) is the protocol that runs on the wire, making sure that the messages are transmitted over the HH connection within the watchdog time. P2P is the mechanism that qualifies the GuardPLC Ethernet network as a safety network.
Peer-to-peer Communication Overview Network Configuration Chapter 16 Communication between GuardPLC controllers can be established via different kinds of Ethernet topologies. Both the HH protocol and the peer-to-peer protocol can be adapted to the network in use, to allow smooth and efficient data transfer. You configure the HH protocol and the peer-to-peer protocol by setting parameters, either manually or with the help of network profiles.
Chapter 16 Peer-to-peer Communication Overview Token Group ID The Token Group ID is the numerical identifier for a token group. Each token group must have its unique Token Group ID. Protocol Mode Choose either Normal or RAW protocol mode. Normal In Normal mode, software token passing is ON, meaning that access to the Ethernet network is controlled via token passing. Only the controller that holds the token is allowed to access the network.
Peer-to-peer Communication Overview Chapter 16 Data transfer is faster than in Normal Mode and message collisions are prevented by the switching and full-duplex mode ports. This mode is recommended for networks, where full-duplex (recommended) LAN-switches are used exclusively, or the switches integrated into the GuardPLC 1600 and 1800 controllers can be used. Link Mode Choose either TCS Direct or TCS TOKCYC.
Chapter 16 Peer-to-peer Communication Overview The Token Cycle Time depends on the number of controllers in a token group and can be read on the HH Status tab of the Control Panel. Token Alive Timeout The current holder of the token must send a token alive message to the Primary(1) controller within this time period or the Primary assumes the token is bad. If the token alive message is missing, a new token is created by the Primary.
Peer-to-peer Communication Overview Peer-to-peer Protocol Parameters Chapter 16 All peer-to-peer protocol parameters are displayed in the Peer-to-Peer Editor. With the exception of the ResponseTime and the ReceiveTMO, which have to be configured by the user, all other peer-to-peer protocol parameters are automatically preset with the selection of a peer-to-peer profile. See Configure Peer-to-peer Communication on page 184 for detailed instructions on how to configure the peer-to-peer protocol.
Chapter 16 Peer-to-peer Communication Overview The ResponseTime is the sum of the following variables, described in the table below. ResponseTime = TGR1 + T1 + TGR2 + T3+ T2 Response Time Variables Variable Definition TGR1 Message delay between two PES: CPU1 → COM1 → network → COM2 → CPU2 T1 Time on CPU2 to process all protocol stacks: T1 = CycleTime(CPU2) x n2 where n2 is the number of cycles needed on CPU2 to process all protocol stacks.
Peer-to-peer Communication Overview Chapter 16 If the Receive]TMO is not ≥ 2 x ResponseTime (minimum), the availability of the Peer-to-Peer connection is guaranteed only in a collision- and noise-free network. However, this does not result in a safety problem for the CPU. TIP The maximum permissible value for ReceiveTMO depends upon the application and is set in the Peer-to-Peer Editor along with the expected maximum ResponseTime and the profile.
Chapter 16 Peer-to-peer Communication Overview Production Rate (ProdRate) ProdRate is the minimum time interval between two data messages. The purpose of ProdRate is to limit the amount of data to a magnitude that can be transported to the recipient without overloading a (slow) communication channel. This results in an even load on the communication channel and avoids the reception of outdated data.
Peer-to-peer Communication Overview Chapter 16 The Worst-case ReactionTime TR is process-dependent and has to be coordinated with the approving board. In the Peer-to-Peer Editor, the Worst-case ReactionTime can be read in the Worst Case column. HH Network Profiles Two HH network profiles are used to configure the appropriate set of parameters for the network in use. The profiles, described below, can be chosen in the properties of the HH Network token group.
Chapter 16 Peer-to-peer Communication Overview The minimum network requirements are outlined this table. Minimum Ethernet Network Requirements for Profile I Requirement Definition Fast 100 Mbps technology (100-Base TX) Switched Fast Ethernet (full-duplex recommended) LAN switches or integrated switches (GuardPLC 1600/1800 controller) required. Cleanroom No loss of data due to traffic overload, harsh environmental conditions, or network defects.
Peer-to-peer Communication Overview Chapter 16 Example of HH Network Profile I Topology Token Group 1 GuardPLC 2000 GuardPLC 2000 GuardPLC 2000 Controllers GuardPLC 1200 Controller GuardPLC 1200 Controller GuardPLC 1200 Controller GuardPLC 2000 Controller GuardPLC 2000 Token Group 2 GuardPLC 1600 Controllers with Integrated Ethernet Switch Controllers GuardPLC 1200 Controller 100 Mbps LAN Switch GuardPLC 1800 Controller with Integrated Ethernet Switch Fiber Optic Cable Programming Terminal T
Chapter 16 Peer-to-peer Communication Overview Profile II: Medium This profile provides medium-speed data throughput and covers approximately 4% of all application cases. It is appropriate for applications where timing is not a critical factor. With the Medium profile, network media access within a token group and communication with external token groups is controlled by token passing. These external token groups must also run Medium profiles.
Peer-to-peer Communication Overview Chapter 16 Each token group handles its token passing individually, depending on user settings, CPU cycle times, network topology, and so forth. This means that for two (or more) token groups, which are exchanging data, Token passing is not synchronized, resulting in a loss of messages between the Token Groups. IMPORTANT To minimize loss of messages, only one controller in a token group is allowed to exchange data with exactly one controller in a second token group.
Chapter 16 Peer-to-peer Communication Overview In this network topology, only one controller in Token Group 1 is allowed to exchange data with one controller in Token Group 2. If Token Group 2 needs data from different controllers in Token Group 1, the “talking” controller in Token Group 1 must collect the data.
Peer-to-peer Communication Overview Chapter 16 HH Network Profile II Configuration Topology Token Group 1 GuardPLC 2000 Token Group 2 GuardPLC 2000 controllers GuardPLC 2000 3 1 GuardPLC 1200 controller 2 GuardPLC 2000 Token Group 3 GuardPLC 9 2000 controllers GuardPLC 2000 7 5 GuardPLC 2000 GuardPLC 2000 11 GuardPLC 1200 controller 6 4 8 10 Mbit Hub Buffer Amp 10 Mbit Hub Programming Terminal 12 10 10 Mbit Hub Twisted Pair Cable, max 100 m Buffer Amp 10 Mbit Switch Fiber Optic Ca
Chapter 16 Peer-to-peer Communication Overview Peer-to-Peer Network Profiles Due to the variety of parameters, manual network configuration is very complex and requires extensive knowledge of the parameters and how they influence one another. To simplify the setup, RSLogix Guard PLUS! software provides six Peer-to-Peer profiles, which can be selected by the user, depending upon application requirements and the capabilities of the network.
Peer-to-peer Communication Overview Chapter 16 Peer-to-Peer Profile I: Fast & Cleanroom This profile provides the fastest data throughput for applications that require fast data update rates. It is also best for applications that require the shortest feasible Worst-Case ReactionTime.
Chapter 16 Peer-to-peer Communication Overview Peer-to-Peer Profile II: Fast & Noisy This profile provides fast data throughput for applications that require fast data update rates. It is good for applications that require the shortest feasible Worst-Case Reaction Time where minor loss of messages can be corrected.
Peer-to-peer Communication Overview Chapter 16 Peer-to-Peer Profile III: Medium & Cleanroom This profile provides medium data throughput for applications where only a moderate data update rate is required and where the Worst Case Reaction Time is not a critical factor. It is well-suited for virtual private networks (VPN), where data exchange is slow due to safety devices (firewalls, encoding/decoding), but error-free. TIP Normally use the profile Medium & Noisy (see page 172).
Chapter 16 Peer-to-peer Communication Overview Peer-to-Peer Profile IV: Medium & Noisy The Medium and Noisy profile provides medium data throughput for applications where only a moderate data update rate is required. It is good for applications where the Worst Case ReactionTime is not a critical factor. Minor loss of messages can be corrected. Medium & Noisy Characteristics 10 MBit (10 Base T) or 100 Mbit technology (100 Base TX) or network with both 10 MBit and 100 Medium or Fast MBit components.
Peer-to-peer Communication Overview Chapter 16 Peer-to-Peer Profile V: Slow & Cleanroom This profile provides low data throughput for applications where only a low data update rate is required from remote controllers, via communication paths, whose conditions cannot be predicted by the user. TIP Normally use the profile Slow & Noisy (see page 174).
Chapter 16 Peer-to-peer Communication Overview Peer-to-Peer Profile IV: Slow & Noisy This profile provides low data throughput for applications where only low data update rates are required. It is primarily for data exchange via poor quality telephone lines or distorted radio links.
Chapter 17 Configure Peer-to-Peer Communication Introduction Topic Page Considerations for Using Peer-to-peer 175 Set Peer-to-Peer Controller Properties 176 Create a Peer-to-peer Network 178 Design the Logic 180 Configure Peer-to-peer Communication 184 Compile and Download 189 Network Optimizing 190 Using peer-to-peer communication, you can exchange signals between controllers by dragging signals onto pages that create controller-to-controller connections.
Chapter 17 Configure Peer-to-Peer Communication Set Peer-to-Peer Controller Properties Right-click Resource and choose Properties to set the timing parameters and switches according to the requirements of your application. The Communication Time Slice and Code Generation Version settings are needed for peer-to-peer network parameterization.
Configure Peer-to-Peer Communication Chapter 17 The time actually needed for communication adds to the CPU cycle time. A short Communication Time Slice limits the communication time to a low value. This prevents the CPU cycle time from being noticeably influenced by network occurrences. Although a Communication Time Slice well above the minimum value may result in cycle time on the local machine slowing down a bit if network traffic is heavy, it is not necessarily negative.
Chapter 17 Configure Peer-to-Peer Communication Code Generator Version To compile the logic correctly for your type of controller, set Code Generator Version to three (3) for RSLogix Guard PLUS! software. Set to version two (2) for RSLogix Guard software. Create a Peer-to-peer Network To create a peer-to-peer network, right-click the project in the Hardware Management window and choose New>HH-Network. You can right-click HH-Network and Rename the entry, if desired.
Configure Peer-to-Peer Communication Chapter 17 Add Controllers to Token Group(s) A controller must be a member of only one token group. To add a controller to a token group, follow these steps. 1. Expand the HH-Network, right-click a token group, and choose Node Editor. The Node Editor is empty when you open it for the first time. 2. Click a controller in the tree view and drag and drop it in the Node Editor. Configure Token Group(s) 1. Right-click the token group and choose Properties. 2.
Chapter 17 Configure Peer-to-Peer Communication IMPORTANT Design the Logic You must choose identical profiles for token groups that you want to interconnect. If Link Mode (External) does not match, communication between token groups is impossible. Create Peer-to-peer Signals Signals are transferred among controllers over the peer-to-peer network. Consider the following when creating signals: • You can create as many signals as you need in the logic for all controllers. • You can add signals anytime.
Configure Peer-to-Peer Communication Chapter 17 Use Peer-to-peer System Signals The status of the peer-to-peer communication as well as some timing parameters can be evaluated in the user program by means of system signals. Furthermore, the user program can control how a peer-to-peer connection is setup. Input System Signals These system signals can be used as inputs for the application: • Connection State.
Chapter 17 Configure Peer-to-Peer Communication Output System Signal Using the output system Connection Control signal, the user program can control how the peer-to-peer connection is setup. Connection Control Values Value Setting Description 0x0000 Autoconnect After loss of peer-to-peer communication, the controller tries to re-establish communication in the next CPU cycle. This is the standard mode of operation.
Configure Peer-to-Peer Communication Chapter 17 network, via Peer-to-Peer, from Robot A to Robot B, which uses it as an input.
Chapter 17 Configure Peer-to-Peer Communication Configure Peer-to-peer Communication As discussed in the following sections, you configure peer-to-peer communication by: • • • • • defining controller connections. assigning the HH-Network. choosing a peer-to-peer profile. defining peer-to-peer parameters. defining process signals for exchange. Define Controller Connections To define all of the controllers each controller can communicate with, follow these steps. 1.
Configure Peer-to-Peer Communication Chapter 17 This example shows how the three Peer-to-Peer Editors would appear if connections existed between all three controllers. Assign HH-Network Peer-to-peer communication requires the HH-Network, which must be entered in the Peer-to-Peer Editor. To assign the HH-Network, click the HH-Network in the tree view and drag and drop it in the Network column of the Peer-to-Peer Editor. The return path is automatically updated with the HH-Network.
Chapter 17 Configure Peer-to-Peer Communication Choose a Peer-to-peer Profile 1. Click in the Profile column and choose one of the profiles. Make sure that the profile is suitable for your network topology and matches the HH profile. See page 161 for a detailed description of all the profiles. 2. Click outside the table or press the Return key to activate the selection. The profile of the return path is automatically updated with the new profile.
Configure Peer-to-Peer Communication Chapter 17 on page 157), ReceiveTMO must be calculated and set manually by overwriting the default value in the Peer-to-Peer Editor.
Chapter 17 Configure Peer-to-Peer Communication 3. Open the Signal Editor by choosing Editor from the Signals menu. 4. Click Connect Process Signals in the Peer-to-Peer Editor. 5. Arrange the Signal Editor and the Peer-to-Peer (P2P) Process Signals dialog boxes side by side. When you open it for the first time, the P2P Process Signals dialog box is empty. 6. Using the tabs below the button bar of the P2P Process Signals, choose the direction of data exchange.
Configure Peer-to-Peer Communication Chapter 17 8. Change the direction of data exchange with the tab and define the return signals. The illustration below shows the signals that RobotB sends to RobotA. Compile and Download Compile Logic If changes, such as adding or deleting a tag, are made to a connection between two controllers, the code must be recompiled for both controllers.
Chapter 17 Configure Peer-to-Peer Communication 3. Click Download to start the simultaneous download for all selected controllers. The Action column shows the command that is currently executed or a short status message. In the example below, the downloads have completed successfully. 4. After successful download, the CPU Status is Stop/Valid Configuration. 5. Select all controllers again if necessary, and click Coldstart to start the application.
Configure Peer-to-Peer Communication Chapter 17 Check Routine Timing 1. In the Multi Control Panel, select all controllers and click Control Panel. 2. In the Control Panels of each controller, click the Statistics tab. 3. Write down the maximum Cycle Time for each controller. 4. Write down the maximum Com. Time Slice for each controller. IMPORTANT Before you continue to optimize settings, make sure that Number of Time Slices (see above) is not greater than 1.
Chapter 17 Configure Peer-to-Peer Communication Reconfigure Watchdog Time To optimize the Watchdog Time to the lowest possible value, you must know the maximum CPU cycle time. Cycle Time max., as displayed on the Statistics tab of the Control Panel, is the value that occurred so far, but is not necessarily the maximum value that can occur depending on network and process conditions. If the maximum Cycle Time cannot be estimated, run the project for several hours and under as many conditions as possible.
Configure Peer-to-Peer Communication Chapter 17 4. For all controllers in your project, re-adjust the Watchdog Times to their individual optimum values. After these modifications, you must re-compile the TIP project with the Code Generator and download the routines in the controllers again. 5. Start the project and let it run for a while. 6. If you encounter controller errors due to a Watchdog Time that is too short, increase the Watchdog Time. Otherwise, continue with the network optimization.
Chapter 17 Configure Peer-to-Peer Communication Check Peer-to-peer Status In the Control Panel, click the P2P Status tab. The P2P Status displays the following information. Parameter Description Resource Name of the controller System.Rack Network ID of the controller State Status of the communication RspT (last, avg, Measured ResponseTime for a message from PES1 → PES2 → PES1, based on the network hardware, CPU cycle time, min, max) and Peer-to-Peer profile.
Configure Peer-to-Peer Communication Chapter 17 Reconfigure ResponseTime The ResponseTime initially configured in Define Peer-to-peer Parameters on page 186 was derived from theoretical considerations and was chosen conservatively, to start the network running. The ResponseTime actually needed is usually much smaller than the theoretical value and can be optimized to improve network performance. To optimize the ResponseTime, follow these steps. 1.
Chapter 17 Configure Peer-to-Peer Communication 5. Note the larger of the two values. The example on page 195 shows RespT avg for Robot A → Robot B (11 ms) and Robot B → Robot A (10 ms). 6. Compare the RspT max of two linked controllers for the forward and return paths. Note down the larger of the two values. The example on page 195 shows RspT max for Robot A → Robot B (19 ms) and Robot B → Robot A (20 ms). 7. In the P2P State tab, check the entries for Resends and EarlyMsgs. a.
Configure Peer-to-Peer Communication Chapter 17 Reconfigure Receive Timeout 1. Set the new ReceiveTMO to: 2 x ResponseTime. 2. The Worst Case Reaction Time is optimized and displayed in the Peer-to-Peer Editor (see above). 3. Compile the project. 4. Download the routines in the controllers again. 5. Start and test your application.
Chapter 17 Configure Peer-to-Peer Communication Notes: 198 Publication 1753-UM001C-EN-P - March 2010
Chapter 18 Introduction to EtherNet/IP Communication Introduction EtherNet/IP Communication Overview Topic Page EtherNet/IP Communication Overview 199 Add EtherNet/IP Protocol to the Resource 203 View the Controller IP Settings 204 Configuring Communication Between the Controller and a PanelView PLUS Terminal 205 EtherNet Industrial Protocol (EtherNet/IP) is an open networking standard communication protocol.
Chapter 18 Introduction to EtherNet/IP Communication The GuardPLC controller can be used as a Class 1 adapter, a Class 3 adapter, or as an unconnected adapter to communicate to Logix controllers, PLC-5 or SLC 5/05 controllers, or PanelView Standard terminals. See Chapter 19 for information on using the GuardPLC controller as an adapter. Class 1 Connections GuardPLC assemblies may have various sizes and have signals of different types associated with them.
Introduction to EtherNet/IP Communication Chapter 18 GuardPLC Controller as a Scanner The scanner data memory is divided into input and output buffers of assemblies. The input area is used for signals received from the target (consumed data). The output area is used for signals transmitted to the target (produced signals). Each I/O assembly must have a corresponding signal connection. Signal connections are configured by using RSLogix Guard PLUS! software.
Chapter 18 Introduction to EtherNet/IP Communication Data Limits IMPORTANT In addition to the Ethernet/IP protocol, other protocols (for example, PROFIBUS-DP, TCP S/R, and others) can also be executed on a GuardPLC controller at the same time. A total of 16284 bytes of data can be transmitted and received per GuardPLC controller. These 16284 bytes can be arbitrarily divided between the protocols.
Introduction to EtherNet/IP Communication Chapter 18 Signal Connections It is your responsibility to allocate assemblies to be of the desired connection size. You do this by assigning signals, created in the Signal Editor, to the scanner buffers or adapter assemblies. For more information on creating signals by using the Signal Editor, refer to the Using RSLogix Guard PLUS! Software with GuardPLC Controllers Programming Manual, publication 1756-PM001.
Chapter 18 Introduction to EtherNet/IP Communication RSLogix Guard PLUS! software creates an EtherNet/IP branch under the Protocols folder where it adds the scanner and the adapter assemblies. Scanner defines the GuardPLC controller’s scanner I/O space, which consists of two buffers: one to store input data and one to store output data. The controller’s adapter input assembly, [120]IN_120, contains data that is produced by the GuardPLC controller.
Introduction to EtherNet/IP Communication Chapter 18 Parameter Description IP address The IP address uniquely identifies the module. The IP address is in the form xxx.xxx.xxx.xxx where each xxx is a number between 0…255. These are reserved values you cannot use: • 127.0.0.1 • 0.0.0.0 • 255.255.255.255 subnet mask Subnet addressing is an extension of the IP address scheme that allows a site to use a single network ID for multiple physical networks.
Chapter 18 Introduction to EtherNet/IP Communication Set Up FactoryTalk View Studio Machine Edition Software Follow these steps to setup FactoryTalk View Studio Machine Edition software. 1. Open FactoryTalk View Studio software. 2. Add the RSLinx Enterprise server to your application. 3. On the Communications tab, verify that RSLinx Enterprise software can browse and locate the GuardPLC controller.
Introduction to EtherNet/IP Communication Chapter 18 4. To add a shortcut for the GuardPLC controller to your application, double-click Communication Setup under the RSLinx Enterprise Server. 5. On the Design (Local) tab, select the GuardPLC controller. 6. On the Device Shortcuts pane, click Add and type a name for the shortcut.
Chapter 18 Introduction to EtherNet/IP Communication Add Ethernet/IP Protocol to Your Project Next, you need to add the Ethernet/IP protocol to your project in RSLogix Guard PLUS software. Follow these steps. 1. In the Hardware Management window of RSLogix Guard PLUS software, right-click Protocols and choose Add Ethernet/IP. By default, the software creates one input assembly (120) and one output assembly (121). Input and output are referenced to the scanner.
Introduction to EtherNet/IP Communication Chapter 18 Read Integers from the Controller and Display Them on the PanelView Plus Terminal This example uses input assembly 120 and shows how two integers can be read by the PanelView Plus terminal. Two INT tags, fromGuard_INT1 and fromGuard_INT2, were used in the controller as shown. The names, tag01 and tag02, in the input assembly window could be any names unique to the GuardPLC controller. The offsets must be renumbered by using the New Offsets tab.
Chapter 18 Introduction to EtherNet/IP Communication N120:0 corresponds to the first INT tag in the GuardPLC assembly 120. N120:1 corresponds to the second INT tag in the GuardPLC assembly 120. Read BOOLs from the GuardPLC Controller and Display Them on the PanelView Plus Terminal This example uses input assembly 122. Two BOOL tags, fromGuard_BOOL1 and fromGuard_BOOL2, were used in the controller as shown.
Introduction to EtherNet/IP Communication Chapter 18 The multistate indicator objects shown below read the two BOOLs from the GuardPLC controller. Tags B122:0 and B122:1 were used to match the input assembly used in the GuardPLC controller. The GuardPLC controller does not use the ‘B’; it is required for FactoryTalk View software. B122:0.0 corresponds to the first BOOL tag in the GuardPLC assembly 122. B122:0.8 corresponds to the second BOOL tag in the GuardPLC assembly 122.
Chapter 18 Introduction to EtherNet/IP Communication Writing Integers to the GuardPLC Controller from the PanelView Plus Terminal This example uses output assembly 121 and shows how two integers can be written by the PanelView Plus terminal. Two INT tags, toGuard_INT1 and toGuard_INT2, were used in the controller as shown. The numeric input objects write the two integers to the GuardPLC controller. Tags N121:0 and N121:1 were used to match the output assembly used in the GuardPLC controller.
Introduction to EtherNet/IP Communication Chapter 18 N121:0 corresponds to the first INT tag in the GuardPLC assembly 121. N121:1 corresponds to the second INT tag in the GuardPLC assembly 121. Writing BOOLs to the GuardPLC Controller from the PanelView Plus Terminal This example uses output assembly 123. Two BOOLs are written by the PanelView Plus terminal to the controller. Four BOOL tags, toGuard_BOOL1 and toGuard_BOOL2 and two dummy tags, were used in the controller as shown on the following page.
Chapter 18 Introduction to EtherNet/IP Communication These momentary pushbutton objects write the two integers to the GuardPLC controller. Tags N123:0 and N123:1 were used to match the output assembly used in the GuardPLC controller. The GuardPLC controller does not use the ‘N’; it is required for FactoryTalk View software. N123:0 corresponds to the first two BOOL tags in the GuardPLC assembly 123. The first tag changes between 0 and 1; the second is the dummy tag.
Chapter 19 Use GuardPLC Controller as an Adapter Introduction Topic Page Configure the GuardPLC Controller as an Adapter 215 Open a Class 1 Connection from a Logix Controller to the GuardPLC Controller 219 Open a Class 3 Connection from a Logix Controller 228 Use a GuardPLC Controller as an Unconnected Adapter 235 Use Unconnected PCCC Messaging from a PLC-5 or SLC 5/05 Controller 235 Use Unconnected CIP Messaging from a PanelView Standard Terminal Configure the GuardPLC Controller as an Adapter
Chapter 19 Use GuardPLC Controller as an Adapter 3. Type the name for the input assembly in the Name field. The Assembly ID can be any number from 120…183. All Assembly IDs under the same EtherNet/IP folder must be unique. If the Run/Idle header box is checked, the assembly uses a Run/Idle header. This four-byte header contains Run/Idle information about the GuardPLC controller that can be used in the scanner’s application logic.
Use GuardPLC Controller as an Adapter Chapter 19 2. Modify the default output assembly properties, if desired, by right-clicking the output assembly and choosing Properties. 3. Type the name for the output assembly in the Name field. The Assembly ID can be any number from 120…183. All Assembly IDs under the same EtherNet/IP folder must be unique. If the Run/Idle header box is checked, the assembly uses a Run/Idle header. The default is checked. Typically, output assemblies always use the Run/Idle header.
Chapter 19 Use GuardPLC Controller as an Adapter The example below shows the Signal Connections dialog box for an input assembly. Signals created in the Signal Editor are assigned to connections to the Output tab for the input assembly. 2. Drag the signals from the Signal Editor to the Signal Connections tab. 3. After assigning the signals, either assign the offsets manually or click New Offsets and choose Renumber at the Renumber Offsets prompt. The offsets are byte offsets.
Use GuardPLC Controller as an Adapter Open a Class 1 Connection from a Logix Controller to the GuardPLC Controller Chapter 19 The following example demonstrates making a connection to a Logix controller, specifically a ControlLogix controller, with a 1756-ENBT or 1756-ENET module to a GuardPLC controller. You can also open connections to CompactLogix controllers. In a Class 1 connection, data is cyclically exchanged based on a time interval (RPI).
Chapter 19 Use GuardPLC Controller as an Adapter 4. Choose Generic Ethernet Module from the list and click OK. 5. Type the connection name in the Name field. 6. Type the IP address of the GuardPLC controller in the IP Address field. 7. Enter the Configuration Assembly Instance as 1 and its size as 0 because the configuration data instance will not be used by the GuardPLC controller.
Use GuardPLC Controller as an Adapter Chapter 19 Exclusive Owner To establish an exclusive owner connection, follow these steps. 1. Choose Data — SINT in the Comm Format Field. 2. Type the GuardPLC controller’s Input Assembly instance number in the Input Assembly Instance field. 3. Type the size of the Input Assembly in the Input Size field. IMPORTANT This entry must exactly match the size of the input assembly, or the GuardPLC adapter controller will return an error.
Chapter 19 Use GuardPLC Controller as an Adapter 6. Click Next and type the desired packet rate for this connection in milliseconds. 7. Click Finish. Input Only Connections When you use input only connections, you can create more than one Class 1 scanner connection to the GuardPLC controller, specifying the same input assembly instance. The GuardPLC controller specifies the same multicast address for input data to all scanners asking for the same input assembly instance.
Use GuardPLC Controller as an Adapter Chapter 19 To open an input only connection, follow these steps. 1. Choose Input Data — SINT in the Comm Format field. 2. Type the GuardPLC controller’s Input Assembly instance number in the Input Assembly Instance field. 3. Type the size of the input assembly in bytes in the Input Size field. IMPORTANT This entry must exactly match the size of the input assembly, or the GuardPLC adapter controller will return an error.
Chapter 19 Use GuardPLC Controller as an Adapter To establish a listen only connection, follow these steps. 1. Choose Input Data — SINT in the Comm Format field. 2. Type the input assembly instance number in the Input Assembly Instance field. 3. Type the size of the input assembly in bytes in the Input Size field. IMPORTANT This entry must exactly match the size of the input assembly, or the GuardPLC adapter controller will return an error.
Use GuardPLC Controller as an Adapter Chapter 19 Download and Go Online Download new changes to the Logix controller and go online. Double-click the new connection icon under I/O Configuration. If the connection is established successfully, RSLogix 5000 software displays the status as Running in the Module Properties dialog box. If an error occurred, it is displayed in the Module Fault field of the Connection tab of the Module Properties dialog box.
Chapter 19 Use GuardPLC Controller as an Adapter Monitor Connection Status To monitor the status of your connections, follow these steps. 1. Go online with the GuardPLC controller by using RSLogix Guard PLUS! software. 2. Switch to the EIP tab of the Control Panel and click the Connection Status tab. You can view the connection’s EtherNet/IP statistics, described in the table below.
Use GuardPLC Controller as an Adapter Chapter 19 Use the Force Editor to Test the Connection You can use the Force Editor in the RSLogix Guard PLUS! software and the I/O controller tags in RSLogix 5000 software to test the connection between the GuardPLC controller and the Logix controller. Under normal operating conditions, the GuardPLC application program will change and update the data being read and update the data being read by the Logix controller.
Chapter 19 Use GuardPLC Controller as an Adapter Remove or Inhibit a Connection You can remove a connection in RSLogix 5000 software by going offline, right-clicking the connection icon, and choosing Delete. Download to apply the changes. You can also Inhibit a connection in Run mode, by double-clicking the connection icon and checking the Inhibit box on the Connection tab.
Use GuardPLC Controller as an Adapter Chapter 19 Create a Project for the Logix Controller 1. In RSLogix 5000 software, create a new project for the Logix controller. 2. Add the Ethernet adapter module to the I/O Configuration. a. Right-click I/O Configuration and choose New Module. b. In the Select Module Type dialog box, choose the 1756-ENBT or 1756-ENET module type and click OK. c. In the Module Properties dialog box, enter the IP address and the slot number of the module. d. Click Finish.
Chapter 19 Use GuardPLC Controller as an Adapter 5. Add a ReadBuffer tag with type DINT[3] and a WriteBuffer tag with type SINT[4]. These types correspond directly to the signal types of the GuardPLC adapter assemblies. When explicit CIP messaging is used to read and write assemblies, the tag being written to or read from must be of the same or larger size than the assembly size in the GuardPLC controller.
Use GuardPLC Controller as an Adapter Chapter 19 4. Configure the message parameters as follows. a. Set Service Type to Get Attribute Single. b. Set Class to 4 (assembly) c. Set Instance to 120. This is the assembly instance number that will be read from. d. Set Attribute to 3 (assembly data). e. Set Destination to ReadBuffer. 5. Switch to the Communication tab and enter this text in the Path field: ENBT,2,. Here, 2 is the EtherNet/IP port of the 1756-ENBT module.
Chapter 19 Use GuardPLC Controller as an Adapter 6. Check the Connected and then the Cache Connections boxes. The Connected option ensures that messages are sent over a Class 3 connection, not as unconnected ones. Cache Connections is the default option. If it is checked, the connection is opened the first time the controller is in Run mode and the rung condition is true. In this example, the rung condition is true when Enable value is true and the timer has expired (DN flag is set).
Use GuardPLC Controller as an Adapter Chapter 19 This Class 3 example uses the Cache Connections option. A connection with this flag is opened when the controller switches to Run mode and the rung condition is true. In our example, the rung condition is true when Enable value is true and the timer has expired (DN flag is set). When the rung condition is False, the connection remains open. If the Enable tag is changed to false, the connection still remains open.
Chapter 19 Use GuardPLC Controller as an Adapter 2. Set the WriteBuffer display type to Hex. Enter 16#12, 16#34, 16#ab, 16#cd in the WriteBuffer. 3. Set the ReadBuffer type to Decimal. The ReadBuffer is set to Decimal because RSLogix Guard PLUS! software displays DINT types in decimal format only. 4. Configure the Force Editor menu in RSLogix Guard PLUS! software to display all signals for assemblies IN_120 and OUT_121. 5. Set signals for the IN_120 assembly to values 12345678, 13572468, 98765432. 6.
Use GuardPLC Controller as an Adapter Use a GuardPLC Controller as an Unconnected Adapter Chapter 19 Using the GuardPLC controller as an unconnected adapter is similar to using it as a Class 3 adapter. In both cases, an explicit message is sent from the client to the GuardPLC controller, addressing one of the built-in objects, including Identity, Assembly, PCCC, Connection Configuration, Port, TCP/IP and Ethernet Link.
Chapter 19 Use GuardPLC Controller as an Adapter Refer to the Enhanced and Ethernet PLC-5 Programmable Controllers User Manual, publication 1785-UM012, or to the SLC 500 Modular Hardware Style User Manual, publication 1747-UM011, for more information on configuring these controllers for Ethernet communication. You will also need RSLogix 5 programming software to configure the PLC-5 controller or RSLogix 500 programming software to configure the SLC 5/05 controller.
Use GuardPLC Controller as an Adapter Chapter 19 Configure an EtherNet/IP Driver If you are going to program the PLC-5 or SLC 5/05 controller via the EtherNet/IP network, you must configure an EtherNet/IP driver in RSLinx software to allow your PC to communicate with the PLC-5 or SLC 5/05 controller. 1. Start RSLinx software. 2. Click the Configure Drivers button. 3. From the Available Driver Types pull-down menu, choose the Ethernet/IP Driver. 4. Click Add New. 5.
Chapter 19 Use GuardPLC Controller as an Adapter 3. Enter a name for the processor and choose the EtherNet/IP driver as shown below. PLC-5 Controller SLC 5/05 Controller 4. If your controller is a PLC-5 controller, configure the controller. a. Expand the Project in the project tree, right-click Controller, and choose Properties.
Use GuardPLC Controller as an Adapter Chapter 19 b. On the Controller Communications tab, choose the EtherNet/IP communication driver you configured in RSLinx software and click OK. Add a Message Instruction to Your Application Program Logic 1. To allocate a MSG instruction control block, right-click Data Files and choose New > Message. PLC-5 Controller SLC 5/05 Controller For the SLC 5/05 controller, the number of elements must be at least 93.
Chapter 19 Use GuardPLC Controller as an Adapter The MSG control block appears in the project tree under Data Files. PLC-5 Message Control Block 2. Insert a MSG instruction rung and assign it to a MSG instruction control block. SLC 5/05 Controller PLC-5 Controller 3. For an SLC 5/05 controller, edit the instruction parameters in the as described below. Parameter Setting Read/Write Choose either Read or Write.
Use GuardPLC Controller as an Adapter Chapter 19 5. Configure the This Controller parameters. SLC 5/05 Controller PLC-5 Controller Parameter PLC-5 Controller Settings Communication Command Choose PLC-5 Typed Read or PLC-5 Typed Write Choose either PLC5 Read or PLC5 Write. Data Table Address Enter the source file address for a write or the destination file address for a read. Enter the source file address for a write or the destination file address for a read.
Chapter 19 Use GuardPLC Controller as an Adapter 6. Configure the Target Device (the GuardPLC controller) parameters. Parameter PLC-5 Controller Settings SLC 5/05 Controller Settings Data Table Address This is the GuardPLC assembly object. Enter the text name of the GuardPLC assembly proceeded by a $ and enclosed in double quotes. For example, "$BLK_120:8:W". This is the GuardPLC assembly object. Enter the text name of the GuardPLC assembly proceeded by a $ and enclosed in double quotes.
Use GuardPLC Controller as an Adapter Chapter 19 9. Enter the IP address of the GuardPLC controller. SLC 5/05 Controller PLC-5 Controller Use Unconnected CIP Messaging from a PanelView Standard Terminal Use the Generic CIP message profile to configure the PanelView Standard terminal to exchange data with the GuardPLC controller. Both devices must be connected to the EtherNet/IP network. You will need PanelBuilder32 software, version 3.82.xx or later, to configure the PanelView Standard terminal.
Chapter 19 Use GuardPLC Controller as an Adapter 5. Save and download your application. These steps are described in more detail beginning on page 244. For more information on PanelView Standard terminals and using PanelBuilder32 software, refer to the following: • PanelView Standard Operator Terminals User Manual, publication 2711-UM014. • PanelBuilder32 Application Development Software for PanelView Standard Terminals Quick Start, publication 2711-QS003.
Use GuardPLC Controller as an Adapter Chapter 19 Configure the PanelView Terminal for EtherNet/IP Communication Follow these steps to configure the PanelView terminal. 1. Double-click the Comms. Setup button on the Application Settings dialog box. 2. When the Communications Setup - Ethernet dialog box opens, press the Insert key. 3. Choose Generic CIP from the Node Type list.
Chapter 19 Use GuardPLC Controller as an Adapter 4. Enter the GuardPLC controller’s Node Name and it’s EtherNet/IP address. 5. Leave the Path field blank. 6. Click OK. Configure a Write Operation The example below configures the PanelView Standard terminal to perform a write operation to set the preset value of a tag located in the GuardPLC controller’s target output assembly (OUT_120). 1. From the Objects menu, choose Numeric Entry > Cursor Point. 2.
Use GuardPLC Controller as an Adapter Chapter 19 7. Configure the tag as shown below. Parameter Setting Messaging Type CIP Node Name Enter the name of the GuardPLC controller that will receive the command. Service Code Choose Set Attribute Single to indicate that this is a write operation. Class Code Enter 4, for an assembly object. Instance Number Enter 120 to indicate the GuardPLC target output assembly that was created for the PanelView Standard terminal to write to.
Chapter 19 Use GuardPLC Controller as an Adapter 3. Double-click the object to open the Properties dialog box. 4. Enter the desired Field Width and Decimal Point display information. 5. Enter a name for the Read Tag. 6. Click the Edit Tag button to open the Tag Form dialog box. 7. Configure the tag as shown below. 248 Parameter Setting Messaging Type CIP Node Name Enter the name of the GuardPLC controller that will receive the command.
Chapter 20 Use the GuardPLC Controller as a Scanner Introduction Prepare the GuardPLC Controller for Class 1 Scanner Connections Topic Page Prepare the GuardPLC Controller for Class 1 Scanner Connections 249 Configure the EtherNet/IP Driver 252 Configure Connections in RSNetWorx for EtherNet/IP Software 254 Open a Connection to a Logix Controller 260 Save the Connection Configuration in the GuardPLC Controller 262 Remove the Connection Configuration 263 Make sure the GuardPLC controller re
Chapter 20 Use the GuardPLC Controller as a Scanner Connect the Scanner Signals 1. Right-click Scanner and choose Connect Signals from the context menu to open the Signal Connections dialog box. 2. Assign signals created in the Signal Editor by dragging them to either the Input or Output tab on the Connect Signals dialog box. The Input tab contains all signals to be received from the target. The Output tab contains all signals to be transmitted to the target. 3.
Use the GuardPLC Controller as a Scanner Chapter 20 Also make sure that the data to be written or read does not cross data type boundaries or try to use only a portion of the signal. In the example above, you must assign 1 WORD or 1 INT signal, or 2 BYTE signals to the output assembly and 6 BYTES, or 3 WORDs, or 3 INT signals to the input tab. If any I/O module uses an odd number of bytes, then you must use only BYTE data type signals. For example, the 1734-IB4 module requires 2.
Chapter 20 Use the GuardPLC Controller as a Scanner 4. Assign the signal to the Disable scanner signal in the signal connections dialog box by dragging and dropping it in the Signal field. If this signal is TRUE, scanner functionality on the controller is disabled. If this signal is FALSE, scanner functionality is enabled. Configure the EtherNet/IP Driver 1. Start RSLinx software. 2. Click the Configure Driver button. 3.
Use the GuardPLC Controller as a Scanner Chapter 20 5. In the Configure Drivers dialog box, leave Browse Local Subnet checked and click OK. TIP The controllers will be recognized automatically if they are in the same subnet. If the controller type or name is unidentified, you must install the correct EDS file. EDS files are available on the RSLogix Guard PLUS! software CD or at http://support.rockwellautomation.com.
Chapter 20 Use the GuardPLC Controller as a Scanner Configure Connections in RSNetWorx for EtherNet/IP Software Before starting RSNetWorx for EtherNet/IP software and configuring the GuardPLC controller’s scanlist, make sure the GuardPLC controller is in the STOP/VALID CONFIGURATION state, or RSNetWorx for EtherNet/IP software will generate an error. 1. Start RSNetWorx for EtherNet/IP software. 2. To create a new configuration, from the File menu, choose New. 3.
Use the GuardPLC Controller as a Scanner Chapter 20 4. Right-click the GuardPLC controller icon in the graphic view and choose Scanlist Configuration to open the Scanlist Configuration dialog box. The GuardPLC controller is highlighted in the Scanlist Configuration dialog box to show that it is the scanner in this configuration.
Chapter 20 Use the GuardPLC Controller as a Scanner 5. Right-click the target I/O module in the Scanlist Configuration dialog box and choose Insert Connection. TIP 256 If the controller is in the RUN mode, a warning message appears, instructing you to put the scanner into the STOP/VALID CONFIGURATION mode before you attempt to add connections.
Use the GuardPLC Controller as a Scanner Chapter 20 6. Configure the Connection Properties for the I/O module, using the Connection tab on the Connection Properties dialog box. In a produce/consume system, modules multicast data, meaning that multiple modules can receive the same data at the same time from a single module. When you choose Connection Name, in this dialog box, you must choose whether to establish an owner or listen-only relationship with the module.
Chapter 20 Use the GuardPLC Controller as a Scanner Property Description Input Size Input size is the length of the data sent from the I/O module (target) to the GuardPLC controller (scanner). The value in this field is predetermined by the module type and cannot be changed. Output Size Output size is the length of the data sent from the GuardPLC controller (scanner) to the I/O module (target). The value in this field is predetermined by the module type and cannot be changed.
Use the GuardPLC Controller as a Scanner Chapter 20 9. In RSLogix Guard PLUS! software, put the GuardPLC controller into RUN mode. The configuration is now complete and the I/O modules should be working under the control of the GuardPLC controller. 10. To view the status of the connection in RSNetWorx for EtherNet/IP software, click the Connection Status tab. Every connection in the GuardPLC controller is listed on this screen. Any non-working connections are also listed. 11.
Chapter 20 Use the GuardPLC Controller as a Scanner Open a Connection to a Logix Controller The GuardPLC controller can establish a connection to a ControlLogix or CompactLogix controller and read the data over this connection. The data must be stored in the producing data tag in the Logix controller. The data exchange is one-sided, from the Logix controller to the GuardPLC controller.
Use the GuardPLC Controller as a Scanner Chapter 20 For more information on configuring Logix controllers, refer to Logix5000 Controllers Quick Start, publication 1756-QS001. Configure Connections from the GuardPLC Controller to the Logix Controller 1. In RSNetWorx for EtherNet/IP software, right-click the GuardPLC scanner controller in the graphic view and choose Scanlist Configuration. 2. Right-click the target Logix controller in the Scanlist Configuration dialog box and choose Insert Connection. 3.
Chapter 20 Use the GuardPLC Controller as a Scanner Save the Connection Configuration in the GuardPLC Controller Up to this point, only the configuration has been downloaded to the GuardPLC controller. The offline project currently contains only the assigned signal connections.
Use the GuardPLC Controller as a Scanner Remove the Connection Configuration Chapter 20 You can also remove a connection configuration from a project. 1. Click the RSNetWorx Configuration under the EtherNet/IP Scanner branch and press the Delete key. RSLogix Guard PLUS! software removes the RSNetWorx Configuration branch. 2. Right-click the controller Resource and choose Code Generation to save the change to the project.
Chapter 20 Use the GuardPLC Controller as a Scanner Notes: 264 Publication 1753-UM001C-EN-P - March 2010
Chapter 21 Communicate with ASCII Devices Introduction Connect the Controller to an ASCII Device Topic Page Connect the Controller to an ASCII Device 265 Configure the ASCII Serial Port 268 Connect Signals 269 ASCII Protocol 270 For the sole purpose of sending the status of the signals from the GuardPLC controller to an external device, you can connect an intelligent ASCII device to the GuardPLC controller’s serial port.
Chapter 21 Communicate with ASCII Devices D-shell connector. This mini-DIN connector is not commercially available, so you cannot make this cable. The pin assignment of the ASCII Serial port is shown below.
Communicate with ASCII Devices Chapter 21 Connect to a GuardPLC 2000 Controller 1755PB720 1755L1 RUN STOP PROG FAULT FORCE GuardPLC 2000 1755IB24XOB16 1755IB24XOB16 RUN ERR RUN RUN ERR 1755IF8 ERR RUN ERR 1755OF8 RUN ERR 1755HSC 1755HSC RUN ERR RUN ERR 1 LS+ 1 I1+ 1 O1+ 1 C- 1 C- 2 I1 2 I1 2 I- 2 O1- 2 A1 2 A1 3 I2 3 I2 3 I2+ 3 O2+ 3 B1 3 B1 4 I3 4 I3 4 I- 4 O2- 4 Z1 4 Z1 5 I4 5 I4 5 I3+ 5 O3+ 5 C1 5 C1 6 I5 6 I5 6 I- 6
Chapter 21 Communicate with ASCII Devices Configure the ASCII Serial Port You must either create a new project or open an existing project before you can configure ASCII communication. Once the software opens a project, it automatically displays the Hardware Management window, from which you configure the ASCII port. 1. Right-click Protocols and choose New>ASCII. 2. Right-click the ASCII icon and choose Properties. For this field Specify Slave Address the slave address (1…65535) of the controller.
Communicate with ASCII Devices Connect Signals Chapter 21 Only ASCII output signals are sent from the controller. You connect signals to the ASCII outputs to determine which signal values you want to send from the controller to the connected ASCII device. 1. Expand Protocols, right-click the ASCII icon and choose Connect Signals.
Chapter 21 Communicate with ASCII Devices The offset in the ASCII output section is numbered based on bytes. In the example, the first signal uses bytes 0, 1, 2, and 3. The second signal uses bytes 4 and 5. However, when you request these signals in the command string (see ASCII Master - Request below), the first signal is always 0, the second signal is always 1, the third signal is always 2, and so forth. TIP The output section automatically sorts the name field based on alphanumerical order.
Communicate with ASCII Devices Chapter 21 For example, this string requests the first two variables from the slave. Start Sign Destination Source Function Code Start Address Number of Variables End Sign ^ 15 01 R 00000 002 & ASCII Slave - Controller Response If the controller receives a request from an ASCII master, it responds in this format (each character is one byte).
Chapter 21 Communicate with ASCII Devices For example, this string replies to the master request for the first two variables from the slave. Start Sign Destination Source Function Code Start Address Number of Variables Number of Data Characters End Sign ^ 01 15 r 00000 002 0005 & 4/123 Every data field in the message is separated with a slash ( / ). The slash also counts as a character when counting the total number of characters in the data string.
Communicate with ASCII Devices Chapter 21 Data Type Formats Follow these formats for sending different data types.
Chapter 21 Communicate with ASCII Devices Notes: 274 Publication 1753-UM001C-EN-P - March 2010
Chapter 22 Communicate with Modbus and Profibus Devices Introduction Modbus RTU Slave Protocol Topic Page Modbus RTU Slave Protocol 275 Connect the Controller to a Modbus Device 276 Configure the Modbus Serial Port 276 Connect Signals 277 Profibus DP Slave Protocol 279 Connect the Controller to a Profibus DP Device 279 Configure the Profibus DP Serial Port 280 Connect Signals 280 Configure the Profibus Master 282 Modbus is available only on GuardPLC 1600 or 1800 controllers.
Chapter 22 Communicate with Modbus and Profibus Devices Connect the Controller to a Modbus Device 3 (—) (—) L- 4 L+ Signal Function 1 --- --- 2 RP 5V, decoupled with diodes 3 RxD/TxD-A Receive/Transmit data A 4 CNTR-A Control Signal A 5 DGND Data reference potential 6 VP 5V, positive pole of supply voltage 7 --- --- 8 RxD/TxD-B Receive/Transmit data B 9 CNTR-B Control Signal B L+ 24V DC RS-485 ASCII MODBUS COMM3 COMM2 COMM1 RS-485 GuardPLC Ethernet 10/100 BaseT
Communicate with Modbus and Profibus Devices Chapter 22 2. Expand Protocols, right-click the Modbus Slave icon, and choose Properties. For this field Specify Slave Address the slave address (1…247) of the controller. The Modbus protocol of the controller supports only a direct point-to-point connection between the master and slave. The controller is always configured as slave.
Chapter 22 Communicate with Modbus and Profibus Devices Follow these steps to connect signals. 1. Expand Protocols, right-click the Modbus Slave icon, and choose Connect Signals. If you want to Click this tab create a new signal New Connected Signal renumber offsets sequentially for all signals New Offsets delete the selected signal Delete Connected Signal 2. Edit the signals you want to receive or send. • Use the Inputs tab to determine which values to read into the controller.
Communicate with Modbus and Profibus Devices Profibus DP Slave Protocol Chapter 22 Profibus DP Slave protocol is available only via the GuardPLC 1600 and 1800 controller’s COMM1 port. This connection is two-way non-safety-related communication from the controller (slave) to the master device. You cannot program the controller by using this port.
Chapter 22 Communicate with Modbus and Profibus Devices Configure the Profibus DP Serial Port You must either create a new project or open an existing project before you can configure Profibus DP communication. Once the software opens a project, it automatically displays the Hardware Management window, from which you configure the Profibus port. 1. Right-click Protocols and choose New>Profibus dp Slave. 2. Expand Protocols, right-click the Profibus dp Slave icon, and choose Properties.
Communicate with Modbus and Profibus Devices Chapter 22 Inputs are signals sent from the Profibus master to the controller (slave). Outputs are signals sent from the controller (slave) to the master. 1. Expand Protocols, right-click the Profibus-dp Slave icon, and choose Connect Signals. If you want to Click this tab create a new signal New Connected Signal renumber offsets sequentially for all signals New Offsets delete the selected signal Delete Connected Signal 2.
Chapter 22 Communicate with Modbus and Profibus Devices 3. Click New Offsets to automatically calculate the offsets for the new signals. IMPORTANT Due to the offsets of the system variables, the offset of the first input signal must begin with 12. The offset for the first output signal begins with 0. The Profibus ID for the first input signal is 0.
Appendix A Specifications GuardPLC 1200 Controller Attribute 1754-L28BBB Controller User Memory 500 KB application code memory 500 KB application data memory Digital Inputs Number of inputs 20 (not electrically isolated from each other, isolated from the backplane) Nominal input voltage 24V DC On-state voltage 10V DC…30V DC On-state current 2 mA @ 10V DC, 13 mA @ 30V DC Off-state voltage, max 5V DC (max) Off-state current, max 1.
Appendix A Specifications Attribute 1754-L28BBB Power Supply Supply Voltage (L+) 24V DC Supply voltage range 20.4V DC…28.8V DC (10 ms buffer), ripple ≤ 15% Power rating, max 8 A (1 A to run the controller, 7 A for inputs and outputs) Environmental Conditions Temperature, operating 0… 60 °C (32…140°F) Temperature, storage -40…85 °C (-40…185°F) without back-up battery Mechanical Dimensions Width x height x depth 160 mm x 112 mm x 90 mm (6.3 in. x 4.41 in. x 3.54 in.) Weight 680 g (1.
Specifications Attribute Appendix A 1753-L28BBBM and 1753-L28BBBP Digital Inputs Number of inputs 20 (not electrically isolated) Voltage, on-state 15V … 30V DC Current consumption, on-state ≥ 2 mA @ 15V 7.5 mA @ 30V Voltage, off-state, max 5V DC Current consumption, off-state, max 1.5 mA (1 mA @ 5V) Switching point, typical 7.5V Supply 5 x 20V / 100 mA @ 24V short-circuit proof Digital Outputs Number of Outputs 8 (not electrically isolated) Output voltage range 18.4V … 26.
Appendix A Specifications Attribute 1753-L28BBBM and 1753-L28BBBP Certifications (when product is marked) c-UL-us UL Listed Industrial Control Equipment, certified for US and Canada CE European Union 89/336/EEC EMC Directive, compliant with: • EN 61000-6-4; Industrial Emissions • EN 50082-2; Industrial Immunity • EN 61326; Meas./Control/Lab.
Specifications Attribute Appendix A 1753-L32BBBM-8A and 1753-L32BBBP-8A Digital Outputs Number of outputs 8 (not electrically isolated) Output voltage range ≥ L+ minus 2V Output current Channels 1…3 and 5…7: 0.5 A @ 60 °C (140 °F) Channels 4 and 8: 1 A @ 60 °C (140 °F); 2 A @ 50 °C (122 °C) Surge current per channel 1 A for 10 ms @ 1 Hz (Channels 1…3 and 5…7) 4 A for 10 ms @ 1 Hz (Channels 4 and 8) Current load, min 2 mA per channel Internal voltage drop, max 2.
Appendix A Specifications Attribute 1753-L32BBBM-8A and 1753-L32BBBP-8A Transmitter supplies 25.37 … 28.24V / ≤ 46 mA, short-circuit proof Safety accuracy ± 2% Environmental Conditions Temperature, operating 0…60 °C (32 …140 °F) Temperature, storage -40…85 °C (-40…185 °F) Mechanical Dimensions Width 257 mm (10.1 in.) including housing screws Height 114 mm (4.49 in.) including latch Depth 66 mm (2.60 in.) including grounding screw 80 mm (3.15 in.) including shield plate Weight 1.2 kg (2.
Specifications Attribute Appendix A 1753-IB16 Digital Inputs Number of inputs 16 (not electrically isolated) 1 Signal Voltage: 15V … 30V DC, Current consumption: ≥ 2 mA @ 15V 0 Signal Voltage, max: 5V DC Current consumption, max: 1.5 mA (1 mA @ 5V) Switching point typically 7.5V Switching time typically 250 μs Sensor supply 4 x 19.
Appendix A Specifications 1753 Combination I/O Modules Attribute 1753-IB8XOB8 1753-IB16XOB8 1753-IB20XOB8 General GuardPLC Ethernet interfaces 2 x RJ-45, 10/100BaseT (with 100 Mbps) with integrated switch Operating voltage 24V DC, -15% … +20%, wss 15% from a power supply with protective separation, conforming to IEC 61131-2 requirements Response time ≥ 10 ms Battery backup none Current consumption 8 A max (with max load), idle current 0.
Specifications Attribute 1753-IB8XOB8 Internal voltage drop, max 2V @ 2 A 1753-IB16XOB8 1753-IB20XOB8 8A 7A Appendix A Leakage current (with 0 maximum 1 mA @ 2V signal) Total output current, max 7A Response to overload shut down of the concerned output with cyclic reconnecting Pulse Test Sources Number of pulse test sources 2 (not electrically isolated) 2 (not electrically isolated) Not applicable Output voltage range L+ minus 4V Not applicable Output current 60 mA Not applicable Cur
Appendix A Specifications 1753-IF8XOF4 Analog Combination Module Attribute GuardPLC Ethernet interfaces Operating voltage Response time Battery backup Current consumption Wiring category Wire size Terminal block torque Analog Inputs Number of inputs Input signal range, nom Input signal range, service Shunt resistor, external Impedance, analog input Analog input signal, source impedance Input resolution Effective resolution Sensor supply Accuracy Safety accuracy Calibration error zero point Calibration e
Specifications Analog Outputs Number of outputs Output signal range Appendix A 4 (not electrically isolated) non-safety with common safety switch off 4…20 mA nominal 0…20 mA full range 12 bits 600 Ω max ±1% ±1% resolution of software Impedance, current output Calibration error zero point Calibration error terminal point Channel error ±1% Temperature error zero ±1%/10 K point Temperature error terminal ±1%/10 K point Linearity error ±1% Environmental Conditions Temperature, operating 0…60 °C (32…140 °F)
Appendix A Specifications 1753-OW8 Relay Output Module Attribute 1753-OW8 Response Time ≥ 10 ms GuardPLC Ethernet Interfaces 2 x RJ-45, 10/100BaseT (with 100 Mbps) with integrated switch Operating voltage 24V DC, -15%…20%, wss ≤15% from a power supply with protective separation conforming to IEC 61131-2 requirements Current consumption 0.
Specifications Shock, operating 15 g Relative humidity 10 … 95% noncondensing Emissions Group 1, Class A ESD immunity 6 kV contact discharges 8 kV air discharges Appendix A Radiated RF immunity 10V/m with 1kHz sine-wave 80% AM from 80 MHz…2000 MHz EFT/B immunity ±2 kV @ 5 kHz on power ports ±1 kV @ 5 kHz on signal ports ±1 kV @ 5 kHz on communication ports Surge transient immunity ±500V line-line (DM) and ±500V line-earth (CM) on DC power ports ±1 kV line-earth (CM) on signal ports ±1 kV line-e
Appendix A Specifications 1753-OB16 Output Module Attribute 1753-OB16 General GuardPLC Ethernet interfaces 2 x RJ-45, 10/100Base T (with 100 Mbps) with integrated switch Operating voltage 24V DC, -15% … +20%, wss 15% from a power supply with protective separation, conforming to IEC 61131-2 requirements Response time ≥ 10 ms Battery backup none Current consumption approximately 0.
Specifications Attribute Appendix A 1753-OB16 Certifications (when product is marked) c-UL-us UL Listed Industrial Control Equipment, certified for US and Canada CE European Union 89/336/EEC EMC Directive, compliant with: • EN 61000-6-4; Industrial Emissions • EN 50082-2; Industrial Immunity • EN 61326; Meas./Control/Lab.
Appendix A Specifications Attribute 1755-L1 Certifications (when product is marked) UL UL Listed Industrial Control Equipment CE European Union 89/336/EEC EMC Directive, compliant with: • EN 61000-6-4; Industrial Emissions • EN 50082-2; Industrial Immunity • EN 61326; Meas./Control/Lab.
Specifications Attribute Appendix A 1755-IB24XOB16 General Specifications Current consumption 0.3 A / 3.3V DC 0.5 A / 24V DC (Idle current to run module) Operating voltage 24V DC, -15 … +20%, ripple ≤ 15% Temperature, operating 0…60 °C (32…140 °F) Temperature, storage -40…85 °C (-40…185 °F) Weight 260 g (0.
Appendix A Specifications Attribute 1755-IF8 Maximum common mode voltage to I- ±13V DC Current consumption 150 mA / 3.3V DC 400 mA / 24V DC Temperature, operating 0…60 °C (32…140 °F) Temperature, storage -40…85 °C (-40…185 °F) Weight 240 g (0.53 lb) Certifications (when product is marked) UL UL Listed Industrial Control Equipment CE European Union 89/336/EEC EMC Directive, compliant with: • EN 61000-6-4; Industrial Emissions • EN 50082-2; Industrial Immunity • EN 61326; Meas./Control/Lab.
Specifications Attribute 1755-OF8 Weight 280 g (0.53 lb) Appendix A Certifications (when product is marked) UL UL Listed Industrial Control Equipment CE European Union 89/336/EEC EMC Directive, compliant with: • EN 61000-6-4; Industrial Emissions • EN 50082-2; Industrial Immunity • EN 61326; Meas./Control/Lab.
Appendix A Specifications 1755-HSC High Speed Counter Module Attribute 1755-HSC Number of counters 2 Input voltage 5V or 24V Input current ≤ 3 mA Input signal frequency 0…1 MHz Trigger with falling edge Edge steepness 1V/μs Input cables ≤ 500 m @ 100 kHz, shielded, twisted Input resistance 3.7 kΩ Resolution 24 bit (value range 0… 6,777,215) Accuracy of time basis 0.2% Quantity of outputs 4 digital Output load ≤0.
Specifications GuardPLC 2000 Power Supply Appendix A Attribute 1755-PB720 Supply voltage 24V DC Supply voltage range 20.4V DC…28.8V DC (10 ms buffer), ripple ≤15% External fusing 30 A(1) / IEC (This module has no overcurrent protection.) Outputs 3.3V DC/10 A, 5V DC/2 A Temperature, operating 0…60 °C (32…140 °F) Temperature, storage -40…60 °C (-40…140 °F) with battery -40…85 °C (-40…185 °F) without battery Weight 820 g (1.
Appendix A Specifications Notes: 304 Publication 1753-UM001C-EN-P - March 2010
Appendix B System Signal Variables Introduction Programming Controller Data Topic Page Programming Controller Data 305 I/O Variables 307 The controller supports system variables that you can configure. The system variables are defined as: • SAFE: the controller can use this information in safety-related functions. • NON-SAFE: additional information that safety functions must not rely on. These are the system variables.
Appendix B System Signal Variables Read/Write Description(1) System Variable Unit/Value Force Time milliseconds Read Remaining running time during forcing; 0 if Force is inactive. [DINT] NON-SAFE Power Supply 0-255 GuardPLC 1200 and GuardPLC 2000 Controllers 0 = normal 1 = error of input power supply 24 VDC 2 = error of battery 4 = module error of power supply 5 V 8 = module error of power supply 3.3 V 16 = 5 V undervoltage 32 = 5 V overvoltage 64 = 3.3 V undervoltage 128 = 3.
System Signal Variables I/O Variables Appendix B Depending upon the type of controller, the various GuardPLC controllers support variables for digital and analog I/O parameters that you can configure or monitor. Digital I/O Module Variables (AB-DIO) for GuardPLC 1200 and 2000 Controllers The GuardPLC 1200 and 2000 controllers support these digital I/O parameters. I/O Data Read/Write Description Board.SRS Read System.Rack.Slot Board.Type Read Module type Board.
Appendix B System Signal Variables I/O Data DO.State (1) DO[0x].State(1)(2) DO[0x].Value(1) DI.State DI[xy].State(3) DI[xy].
System Signal Variables Appendix B Analog Input Module Variables (AB-AI) for GuardPLC 2000 Controller The GuardPLC 2000 controller supports these analog input parameters. I/O Data Read/Write Description AI.Mode Write Mode for all channels of the analog input module AI.
Appendix B System Signal Variables I/O Data AI[0x].State (1) AI[0x].
System Signal Variables Appendix B Analog Output Module Variables (AB-AO) for GuardPLC 2000 Controller The GuardPLC 2000 controller supports these analog output parameters I/O Data Read/Write Description AO.State Read Error mask for all analog outputs AO[0x].Mode (1) AO[0x].State AO[0x].
Appendix B System Signal Variables I/O Data Read/Write Description Write Output value of analog output channels Voltage mode: -10V…10V = -1000…1000 Current mode: 0 mA…20 mA = 0…1000 for values between -1000… 0, the output current is 0 mA Board.SRS Read System.Rack.Slot Board.Type Read Module type AO[0x].Value (1) Board.
System Signal Variables I/O Data Read/Write Description Board.State Read Error mask for the module Cnt.
Appendix B System Signal Variables I/O Data Cnt[0x].GrayCode (1) Read/Write Description Read/Write Gray code mode of counter 1 or 2 0 Pulse 1 Gray Cnt[0x].Halt(1) Read/Write currently not used Cnt[0x].Reset(1) Read/Write Reset for counter 1 or 2 Cnt[0x].State(1) Cnt[0x].
System Signal Variables I/O Data (2) DO[0y].State DO[0x].Value(2) Read/Write Description Read Error mask for counter outputs 1…4 Write 0x01 Error in output channel 0x02 Output channel switched off due to overcurrent 0x04 Error during readback of the output channel 0x08 Faulty initialization after counter reset Appendix B Output value of counter outputs 1…4 (These 4 outputs cannot be driven by counter presets. They are driven by user software only.
Appendix B System Signal Variables I/O Data Read/Write Description Module.Error.
System Signal Variables I/O Data Read/Write Description DI.
Appendix B System Signal Variables Digital Output Module Variables for GuardPLC 1600/1800 Controllers, 1753-IB20XOB8 Modules, and 1753-OB16 Modules The GuardPLC 1600 and GuardPLC 1800 controllers, 1753-IB20XOB8 modules, and 1753-OB16 modules support these digital output parameters. I/O Data Read/Write Description DO.Error Code Read Error mask for all digital outputs DO[xx].
System Signal Variables Appendix B Digital Output Parameters for 1753-IB8XOB8 Modules In addition to the output parameters in the table on page 318, the GuardPLC 1753-IB8XOB8 module features these digital output parameters. I/O Data Read/ Description Write L+ Switching Outputs L- Switching Outputs DO1.Error Code DO2.
Appendix B System Signal Variables I/O Data L+ Switching Outputs L- Switching Outputs — DO2[xx].2 Pole used — Switch-on delay Read/ Write Description Write Configures the channel for 2 pole operation. Write 0 channel DO2[xx] is not used for 2-pole operation.
System Signal Variables I/O Data Read/Write Description DO[xx].+Error Code(1) DO[xx].
Appendix B System Signal Variables Digital Relay Output Parameters for 1753-OW8 Modules The 1753-OW8 module supports these digital output parameters. I/O Data Read/Write Description DO.Error Code Read Error mask for all digital outputs DO[xx].
System Signal Variables Appendix B Analog Input Signals for 1753-IF8XOF4 Modules The 1753-IF8XOF4 module supports these analog input signals. I/O Data Read/Write Description Module.SRS Read Slot number (System.Rack.Slot) Module.Type Read Module type: 0x001E Module.Error.Code Read Error mask for the module AI.
Appendix B System Signal Variables I/O Data AI[xx].Error Code (1) Read/Write Description Read Error code of analog input channels 0x01 Error in the analog input module 0x02 Limit value underflow/overflow 0x04 A/D converter faulty; measuring values not valid 0x08 Measured value not within safety accuracy 0x10 Measured value overflow 0x20 Channel not in operation 0x40 Address error of both A/D converters AI[xx].Value Read Analog value of each channel [INT] from 0…2000 (0V…10V).
System Signal Variables Appendix B Analog Output Signals for 1753-IF8XOF4 Modules The 1753-IF8XOF4 module supports these analog output signals. I/O Data Read/Write Description Module.SRS Read Slot number (System.Rack.Slot) Module.Type Read Module type: 0x Module.Error.Code0069 Read Error mask for the module AO.Error Code AO[xx].Error Code(1) AO[xx].
Appendix B System Signal Variables Counter Module Variables for GuardPLC 1800 Controllers The GuardPLC 1800 controllers support these counter parameters. I/O Data Read/Write Description Module.SRS Read Slot number (System.Rack.Slot) Module.Type Read Module type 0x0003 Module.Error.Code Cnt.Error Code Cnt[0x].
System Signal Variables I/O Data Cnt[0x].Time Overflow Cnt[0x].Direction(1) Cnt[0x].Auto Advance Sense(1) Cnt[0x].Reset(1) Cnt[0x].5/24V Mode(1) Cnt[0x].Gray Code(1) (1) Read/Write Description Read Overflow indication for the time stamp of the counters Read/Write Read/Write Read/Write Read/Write Read/Write True 24-bit overflow since last measurement False No 24-bit overflow since last measurement Appendix B Counting direction of the counter (only if Cnt[0x].
Appendix B System Signal Variables Digital (Analog) Input Variables for the GuardPLC 1800 Controller The digital inputs on the GuardPLC 1800 controller are actually analog inputs with these configurable parameters. I/O Data Read/Write Description Module.SRS Read Slot number (System.Rack.Slot) Module.Type Read Module type Module.Error.Code AI.
System Signal Variables I/O Data Read/Write Description AI[xx].Error Code DI[xx].Error Code Read Read Error mask for analog input channels (1…8) Error mask for digital input channels (9…32) 0x01 Error in input module 0x02 Measured values invalid 0x04 A/D converter faulty 0x08 Measured value not within the safety accuracy 0x10 Measured value overflow 0x20 Channel not in operation 0x40 Address error of both A/D converters 0x80 Configuration of hysteresis faulty AI[xx].
Appendix B System Signal Variables Notes: 330 Publication 1753-UM001C-EN-P - March 2010
Appendix C Wiring Examples Introduction Topic Page GuardPLC 1600 Controller 332 GuardPLC 1800 Controller 333 1753-IB16 Modules 334 1753-OB16 Modules 335 1753-IB20XOB8 Module 336 1753-IB8XOB8 Modules 337 1753-IB16XOB8 Modules 338 1753-OW8 Modules 339 1753-IF8XOF4 Modules 340 GuardPLC 1200 Controller 341 1755-IB24XO16 Digital Input/Output Modules 342 1755-IF8 Analog Input Modules 343 1755-OF8 Analog Output Modules 343 1755-HSC High Speed Counter Module 344 IMPORTANT The wirin
Appendix C Wiring Examples GuardPLC 1600 Controller 24V DC Power Supply 24V DC Power Supply + + COM COM A1 A2 CH1 CH2 Safety Relay 3 (—) (—) 4 PE L- L- L+ A1 A2 CH1 CH2 Safety Relay 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 Pulse-Tested Safety Input L+ DO L- 1 2 3 4 L- 24V DC DO L- 5 6 7 8 L- (2A) (2A) RS-485 MODBUS ASCII/HSP COMM3 COMM2 COMM1 24 V DC RUN Dry Contact ERROR PROG FORCE FAULT 1753-L28BBBM 20 DC Inputs 8 DC Outputs OSL BL D1 L
Wiring Examples Appendix C GuardPLC 1800 Controller Light Curtain/ Safety Input + COM 24V DC Power Supply + Light Curtain/ Safety Input + Dry Contact + COM COM COM 24V DC Power Supply Pulse Tested Safety Input 3 (—) PE (—) L- 4 L+ L+ 24V DC 1 2 3 4 5 6 7 8 9 10 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 DO L- 1 2 3 4 5 6 7 8 L- DI LS+ 1 2 3 4 5 6 7 8 L- DI LS+ 1 2 3 4 5 6 7 8 L- DI LS+ 1 2 3 4
Appendix C Wiring Examples 1753-IB16 Modules 24V DC Power Supply + + + COM COM COM PE L- L- L+ L+ 24V DC Power Supply 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 LS+ 1 2 3 4 L- LS+ 5 6 7 8 L- LS+ 9 10 11 12 L- D1 D1 D1 13 14 15 16 17 18 24V DC 24 V DC RUN ERROR PROG FORCE FAULT 1753-IB16 16 DC Inputs 4 Pulse Test Sources OSL BL LS+ 13 14 15 16 L- PO PULSE TEST L- 1 2 3 4 L- 19 20 21 22 23 24 25 26 27 28 29 30 19 20 21 22 23 24 25 26 27 28 29 30
Wiring Examples Appendix C 1753-OB16 Modules 24V DC Power Supply 24V DC Power Supply + + COM A1 A2 Safety Relay COM CH1 PE L- L- L+ 24V DC 1 2 3 4 5 6 1 2 3 4 5 6 L+ L- L- L+ 24V DC DO L- 1 2 3 4 L- CH2 7 8 9 10 11 12 7 8 9 10 11 12 L+ DO L- 5 6 7 8 L- 24 V DC RUN ERROR PROG FORCE FAULT 1753-OB16 16 DC Outputs OSL BL DO L- 9 10 11 12 L- DO L- 13 14 15 16 L- 13 14 15 16 17 18 19 20 21 22 23 24 13 14 15 16 17 18 19 20 21 22 23 24 GuardPLC Ethernet 10/100 BaseT 1 (—) 24V
Appendix C Wiring Examples 1753-IB20XOB8 Module 24V DC Power Supply 24V DC Power Supply + + COM COM A1 A2 Safety Relay CH1 PE L- L- L+ CH2 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 A1 A2 CH1 CH2 Safety Relay L+ 24V DC DO L- 1 2 3 4 L- DO L- 5 6 7 8 L- (2A) (2A) 24 V DC RUN ERROR PROG FORCE FAULT 1753-IB20OXB8 20 DC Inputs 8 DC Outputs OSL BL D1 LS+ 1 2 3 4 L- D1 LS+ 5 6 7 8 L- D1 LS+ 9 10 11 12 L- D1 LS+ 13 14 15 16 L- Pulse-Tested Safety Input D1 LS+ 17 18
Wiring Examples Appendix C 1753-IB8XOB8 Modules - + Load - + Load Contactor Contactor 24V DC COM Power Supply Load 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 L- 1 2 4- 8- S+ DO- L- 1 2 3 4+LDO (2A) L- 5 6 7 8+LDO (2A) PE L+ L+ L-L- L-L- L+ L+ 24V DC DC 24V PO PULSE TEST 24 V DC RUN ERROR PROG FORCE FAULT 1753-IB8XOB8 8 DC Inputs 8 DC Outputs OSL BL D1 LS+ 1 2 3 4 L- DI LS+ 5 6 7 8 L- 19 20 21 22 23 24 25 26 27 28 29 30 GuardPLC Ethernet 10/100 BaseT 1( ) ( ) 2 COM + COM 24V
Appendix C Wiring Examples 1753-IB16XOB8 Modules - + - Load + Load 24V DCCOM Power + Supply 1 PE L- L- L+ L+ L- LL+ L+ 24V DC 2 3 4 5 6 7 8 S+ S+ S+ S+ S- S- S- S- 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 1- 1+ 2- 2+ 3- 3+ 4- 4+ DO 5- 5+ 6- 6+ 7- 7+ 8- 8+ DO 25 26 27 28 29 30 31 32 1 1 1 1 2 2 2 2 24V DC PO PULSE TEST - DO + 1 24 V DC RUN 2 ERROR 3 PROG 4 FORCE 5 FAULT 6 OSL 7 BL 8 LS+ LS+ 1 2 3 4 1753-IB16 OXB8 16 DC Inputs 8 DC Outputs L- L- LS+ LS+ 5 6 7 8 L-
Wiring Examples Appendix C 1753-OW8 Modules Load L2 or DC- L1 or DC+ 1 PE L- L- L+ 24V DC L+ 2 3 DO 1 4 5 DO 2 6 7 DO 3 8 DO 4 1753-OW8 8 Digital Outputs L1 or DC+ DO5 9 L1 or DC+ Publication 1753-UM001C-EN-P - March 2010 DO6 10 11 Load 12 DO7 13 14 DO8 15 16 L2 or DC- 339
Appendix C Wiring Examples 1753-IF8XOF4 Modules PE L- L- L+ L+ 24V DC 24 V DC 1753-IF8XOF4 8 Analog Inputs 4 Analog Outputs RUN ERROR PROG FORCE FAULT AI AI T1 I1 L- T2 I2 L- AI T3 I3 L- T4 I4 7 9 L- T5 I5 AO O1 AI L- T6 I6 L- T7 I7 L- T8 I8 L- + - O2 + - O3 + - O4 + - OSL BL 1 2 3 4 5 6 8 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 STD ANALOG OUTPUTS GuardPLC Ethernet 10/100 BaseT 1 <—> <—> 2 * * 4-wire device with power source fr
Wiring Examples Appendix C GuardPLC 1200 Controller A1 A2 Safety Relay + CH1 CH2 COM 24V DC Power Supply A B Z A1 A2 Safety Relay CH1 CH2 L+(1) L+(2) O1+ O2+ O3+ O4+ O5+ O6+ O7+ O8+ A1 B1 Z1 2 24V DC Power Supply 4 6 8 10 12 14 16 24V DC Power COM Supply + 18 20 22 24 I- 26 28 + COM 1 3 5 7 9 11 13 15 17 19 21 23 25 27 L-(1) L-(2) PA O1- O2- O3- O4- O5- O6- O7- O8- A2 B2 29 Z2 I- Pulse-Tested Safety Input PE B Z A Dry Contact Dry Contact Not Used I2 + 1
Appendix C Wiring Examples 1755-IB24XO16 Digital Input/Output Modules 1755IB24XOB16 RUN ERR 1 2 3 4 5 6 7 8 9 LS+ I1 I2 I3 I4 I5 I6 I7 I8 10 11 12 13 14 15 16 17 18 LS+ I9 I10 I11 I12 I13 I14 I15 I16 19 20 21 22 23 24 25 26 27 LS+ I17 I18 I19 I20 I21 I22 I23 I24 28 29 30 31 32 33 34 35 36 L- 37 38 39 40 41 42 43 44 45 LO9 O10 O11 O12 O13 O14 O15 O16 Dry Contact Same power supply used by GuardPLC CPU + COM Pulse Tested Safety Input O1 O2 O3 O4 O5 O6 O7 O8 A1 A2 Safety Relay CH1 342 24V D
Wiring Examples Appendix C 1755-IF8 Analog Input Modules 10K Ω (current devices) 500 Ω (voltage devices) 1755IF8 10K Ω RUN ERR - + external + power supply COM 1 2 3 4 5 6 7 8 9 2-wire transmitters 10 11 12 13 14 15 16 17 18 I1+ II2+ II3+ II4+ I- + – singleended voltage + – external power supply + – singleended current + – external power supply differential voltage + – 500 Ω I5+/1II6+/2II7+/3II8+/4I- + – external power supply 4-wire analog devices 1755-OF8 Analog Output Modules 17
Appendix C Wiring Examples 1755-HSC High Speed Counter Module 1755HSC RUN ERR 1 2 3 4 5 6 7 8 9 CA1 B1 Z1 C1 CCCC- 10 11 12 13 14 15 16 17 18 CA2 B2 Z2 C2 CCCC- 19 20 21 22 23 24 25 26 27 344 A1 B1 + Z1 – + COM Same power supply used by GuardPLC CPU A1 B1 + Z1 – L1 2 3 4 LLLL- + COM A1 24V DC Power Supply 24V DC Power Supply A2 Safety Relay CH1 CH2 Publication 1753-UM001C-EN-P - March 2010
Appendix D Replacing the Back-up Battery The following procedures apply only to GuardPLC 1200 controllers and GuardPLC 2000 power supplies. Other GuardPLC controllers and I/O modules are not equipped with back-up batteries. ATTENTION A risk of fire or chemical burn exists if the battery is not handled properly. Do not crush, puncture, disassemble, or short external contacts, or expose the battery to temperatures higher than 60 °C (140 °F).
Appendix D Replacing the Back-up Battery GuardPLC 1200 Controllers Replace the back-up battery on your GuardPLC 1200 controller every two years. The battery case is located on the left-hand side of the cabinet (see drawing below). The battery must be replaced together with the case. Replacements are available from Rockwell Automation under part number 1754-BAT. Follow these steps to replace the battery.
Replacing the Back-up Battery GuardPLC 2000 Power Supply Appendix D Replace the back-up battery every four years. Replacement batteries are available from Rockwell Automation (1755-BAT). Follow these steps to replace the battery. ATTENTION Make sure that the GuardPLC 2000 controller is powered on. Replacing the back-up battery while the controller is off causes a reset. All data including the clock settings will be lost. 1. Remove the lid by removing the two screws. – 2.
Appendix D Replacing the Back-up Battery Notes: 348 Publication 1753-UM001C-EN-P - March 2010
Index Numerics 1753-CBLDN 40 1753-DNSI 40 1754-BAT replacement 346 1755-BAT replacement 347 1755-HSC status indicators 149 1755-IF8 status indicators 148 1755-OF8 status indicators 149 1-pole connection 1753-IB16XOB8 87 1753-IB8XOB8 example 81 1753-IB8XOB8 operation 78 2-pole connection 1753-IB16XOB8 88 1753-IB8XOB8 configuration 79 1753-IB8XOB8 example 81 1753-IB8XOB8 operation 79 3-pole connection 1753-IB16XOB8 89 A acknowledge timeout 159 adapter input assembly 215 output assembly 216 adapter assemblies
Index D data initialization 217 data types 273 decoder mode 111 inputs 108 DeviceNet Safety Scanner for GuardPLC See 1753-DNSI.
Index link mode 155 link mode (extern) 156 listen only connection 223, 257 Logix controllers as scanners 218 Class 1 connections 219-228 Class 3 connections 228-234 related publications 230 M manuals, related 18 Modbus configuring 276 connecting 276 overview 29 protocol 279 signals 277 modes controllers 113 routines 120 monitoring diagnostics 139 See also line monitoring.
Index S Safe States inputs 21 outputs 21 safety concept 19 scanlist configuration 254-259 scanner connect to Logix controller 260-261 disable function 251 input buffer 249 output buffer 249 remove connection configuration 263 save connection configuration 262 scanner signals connect 250 secondary controller 156 secondary interval 156 serial port 268 signals ASCII 269 counter data 312 I/O data 307 Modbus 277 Profibus DP 280 system variables 305 SLC 5/05 controllers PCCC messaging 235-243 related publication
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
GuardPLC Controller Systems User Manual
