User Manual SmartGuard 600 Controllers Catalog Numbers 1752-L24BBB, 1752-L24BBBE
Important User Information Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
Summary of Changes The information below summarizes the changes to this manual since the last printing. 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 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Table of Contents Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Summary of Changes Table of Contents Preface Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Configuration Signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Reset (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Passwords (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set or Change a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forgotten Passwords . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Configure Safety I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Change an I/O Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Setting Up the Controller as a Safety Slave . . . . . . . . . . . . . . . . . . . . . . . . . 87 Create Safety Slave I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Use the Safety Generic Profile in RSLogix 5000 Software . . . . . . . .
Table of Contents Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Comment Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Programming Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Function Block Program. . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Viewing I/O Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 General Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Local Input Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Local Output Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Test Output or Muting Lamp Status . . . . . . . . . . . . . . .
Table of Contents Exclusive OR Truth Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exclusive NOR Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exclusive NOR Instruction Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . Exclusive NOR Instruction Truth Tables . . . . . . . . . . . . . . . . . . . . . . Routing Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Two-hand Control Function Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two-hand Control Function Block Optional Outputs . . . . . . . . . Two-hand Control Function Block Fault Present Output Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two-hand Control Function Block Parameters . . . . . . . . . . . . . . . . Two-hand Control Function Block Truth Table . . . . . . . . . . . . . . .
Table of Contents Appendix E Explicit Messages Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiving Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Response Format. . . . . . . . .
Preface Read this preface to familiarize yourself with the rest of the manual. It provides information concerning: • who should use this manual. • the purpose of this manual. • additional resources. • conventions used in this manual. Who Should Use This Manual Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use SmartGuard™ 600 controllers. You must have a basic understanding of electrical circuitry and familiarity with relay logic.
Preface Common Techniques Used in This Manual 14 These conventions are used throughout this manual: • Bulleted lists, such as this one, provide information, not procedural steps. • Numbered lists provide sequential steps or hierarchical information.
Chapter 1 Overview Introduction About the SmartGuard 600 Controller Topic Page About the SmartGuard 600 Controller 15 Safety Concept of the Controller 21 Additional Resource 21 The SmartGuard 600 controller (catalog numbers 1752-L24BBB and 1752L24BBBE) are programmable electronic systems featuring 16 digital inputs, 8 digital outputs, 4 test pulse sources, and connections for USB and DeviceNet™ communication. In addition, the 1752-L24BBBE controller offers EtherNet/IP connectivity.
Chapter 1 Overview Figure 1 - SmartGuard 600 Controller Safety Control System Example Programming 5 Safety Control Ethernet Switch Ethernet Network Standard Controller 4 SmartGuard Controller 1752-L24BBB SmartGuard Controller 1752-L24BBBE DeviceNet Network 16 2 1 3 Standard Slave RSNetWorx™ for DeviceNet Software DeviceNet Safety I/O Safety Slave Number Description 1 As a DeviceNet safety master, the SmartGuard 600 controller can control up to 32 Guard I/O modules.
Overview Chapter 1 Hardware The SmartGuard 600 controller (catalog numbers 1752-L24BBB and 1752L24BBBE) features 16 digital inputs, 8 digital outputs, 4 pulse test sources, and connections for USB and DeviceNet Safety protocol. In addition, the 1752L24BBBE controller offers EtherNet/IP connectivity.
Chapter 1 Overview SmartGuard 600 Controller (catalog number 1752-L24BBBE) Features 1 2 7 3 8 10 5 9 11 6 Number 18 4 12 7 Feature 1 Module status indicators 2 Alphanumeric display 3 Node address switches 4 Baud rate switches 5 USB port 6 DeviceNet communication connector 7 Terminal connectors 8 Input status indicators 9 Output status indicators 10 IP address display switch 11 Ethernet connector 12 Service switch Rockwell Automation Publication 1752-UM001E-EN-P - June 20
Overview Chapter 1 Safety Inputs The controller has 16 local safety inputs, which support the features described below. • Input circuit diagnosis — Test pulse sources can be used to monitor internal circuits, external devices, and external wiring. • Input on- and off-delays — You can set input time filters of 0…126 ms in multiples of the controller cycle time. Setting input on- and off-delays helps reduce the influence of chattering and external noise.
Chapter 1 Overview Communication The controller can act as a DeviceNet safety master or slave, as a DeviceNet standard slave, or as a standalone controller when DeviceNet communication is disabled. A single controller can function simultaneously as a safety master, safety slave, and standard slave. Explicit messages can be used to read controller status information. The user program can be configured to send explicit messages from the user program.
Overview Chapter 1 When the IP Address display switch is pressed for 1 second or longer, the display shows the EtherNet/IP address that is set. Errors detected by the controller are recorded in an error history log and an EtherNet/IP history log, along with the time the error occurred. (The time is shown as total operating time since the controller was powered up.
Chapter 1 Overview Notes: 22 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Introduction Topic Page General Safety Information 23 Understanding Node Addressing 25 Set the Node Address 26 Setting the Communication Rate 26 Mount the SmartGuard Controller 29 Grounding the SmartGuard Controller 30 Connecting a Power Supply 30 Wiring the SmartGuard 600 Controller 34 General Safety Information ATTENTION: Environment and Enclosure This equipment is intended for use in Pollution Degree 2 Industrial environm
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Table 1 - North American Hazardous Location Approval The following information applies when operating this equipment in hazardous locations Informations sur l’utilisation de cet équipement en environnements dangereux Products marked CL I, DIV 2, GP A, B, C, D are suitable for use in Class I Division 2 Groups A, B, C, D, Hazardous Locations and nonhazardous locations only.
Installing and Wiring the SmartGuard 600 Controller Chapter 2 ATTENTION: Serious injury may occur due to the loss of required safety function. · Do not use test outputs as safety outputs. · Do not use DeviceNet standard I/O data or explicit message data as safety data. · Do not use status indicators for safety operations. · Do not connect loads beyond the rated value to safety outputs or test outputs. · Wire the controller properly so that the 24V dc line does not accidentally touch the outputs.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Set the Node Address Set the node address before you mount the controller. IMPORTANT Turn off power to the controller before setting the node address or communication rate via the switches. Do not change the switch settings while the power supply is on. The controller will detect this as a change in the configuration and will switch to the ABORT mode.
Installing and Wiring the SmartGuard 600 Controller Chapter 2 If you choose to use a different communication rate, the length of the trunkline and types of cable determine which communication rates your application can support.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Set the communication rate by using the DIP switch on the front of the controller.
Installing and Wiring the SmartGuard 600 Controller Chapter 2 For detailed information on EtherNet/IP communication, refer to the EtherNet/ IP Performance and Application Solution, publication ENET-AP001. Attribute Value Number of CIP packets 2 Allowable Unit communication bandwidth 3000 pps(1) Explicit message communication 502 B(2) (1) PPS is packets Per second. It indicates the number of send or receive packets that can be processed per second.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Grounding the SmartGuard Controller ATTENTION: This product is grounded through the DIN rail to chassis ground. Use zinc plated yellow-chromate steel DIN rail to assure proper grounding. The use of other DIN rail materials (for example, aluminum or plastic) that can corrode, oxidize, or are poor conductors, can result in improper or intermittent grounding. Secure DIN rail to mounting surface approximately every 200 mm (7.8 in.
Installing and Wiring the SmartGuard 600 Controller TIP Chapter 2 The following Allen-Bradley 1606 power supplies are SELV- and PELVcompliant, and they meet the isolation and output hold-off time requirements of the SmartGuard 600 controller: · 1606-XLP30E · 1606-XLP72E · 1606-XLP50E · 1606-XLP95E · 1606-XLP50EZ · 1606-XLDNET4 · 1606-XLSDNET4 The SmartGuard controller has three V/G terminal pairs that require a power connection.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller 1. Wire the connector according to the colors on the connector. Wire No. Wire Color Connects to V+ Red V+ CAN H White CAN H Drain — Drain CAN L Blue CAN L V- Black V- 1 2 3 D D D D D 4 5 2. Attach the connector to the DeviceNet port. 3. Tighten the screws to 0.25…0.3 N•m (2.21…2.65 lb•in). For detailed DeviceNet connection information, refer to the DeviceNet Media Design Installation Guide, publication DNET-UM072.
Installing and Wiring the SmartGuard 600 Controller Chapter 2 Connecting to USB Port Connect the USB communication connector to your personal computer when you want to configure the network and controller by using RSNetWorx for DeviceNet software. Use a commercially available USB-A to USB-B male/male cable to make the connection. ATTENTION: To reduce the potential for electromagnetic interference, the USB cable length must be less than 3 m (10 ft).
Chapter 2 Installing and Wiring the SmartGuard 600 Controller standard Ethernet cable. When connecting the SmartGuard controller directly to your personal computer or a NIC card, use a cross-over (null modem) cable. ATTENTION: The cable length must be less then 100 m (328 ft) between hub and nodes. WARNING: If you connect or disconnect the Ethernet cable with power applied to this controller or any other device on this network, an electrical arc can occur.
Installing and Wiring the SmartGuard 600 Controller IN0…IN15 Chapter 2 Terminals for safety inputs. T0…T3 These are test output terminals that can provide pulse test sources for safety inputs IN0…IN15. T3 can also support wire off detection and burned out bulb detection for a load such as a muting lamp. OUT0…OUT7 Terminals for safety outputs. ATTENTION: If you connect or disconnect wiring while the field-side power is applied, an electrical arc can occur.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Figure 7 - Input Devices with PNP Semiconductor Outputs 4.5 mA Typical V1 24V dc Tx SmartGuard 600 Controller OSSDx INx 24V dc G1 GND Wire Output Devices ATTENTION: Serious injury may occur due to a loss of required safety functions. Do not connect loads beyond the rated value of safety or test outputs. Do not use test outputs as safety outputs. Wire the controller properly so that the 24V dc lines do not touch the safety or test outputs.
Installing and Wiring the SmartGuard 600 Controller Chapter 2 Wiring Examples Figure 9 - ESTOP I0 I2 I4 I6 I8 I10 I12 I14 I1 I3 I5 I7 I9 I11 I13 I15 KM1-NC KM2-NC 11 21 S2 S1 12 22 KM1 V1 G1 T0 T2 O0 O2 O4 O6 V2 G2 T1 T3 O1 O3 O5 O7 KM2 E2 E1 KM2 KM1 M E1 and E2: 24V dc Power Supplies S1: Emergency Stop Switch S2: Reset Switch (N.O.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Figure 11 - Two-hand Switch S1 1 I0 I2 I4 I6 I8 I1 0 I1 2 I1 4 I1 I3 I5 I7 I9 I1 1 I1 3 I1 5 KM 1 - N C T1 KM 2 - N C S1 2 KM 1 V1 G1 T0 T2 O0 O2 O4 O6 V2 G2 T1 T3 O1 O3 O5 O7 KM 2 T0 KM 2 E2 E1 KM 1 M E1 and E2: 24V dc Power Supplies S11 and S12: Two-hand Switches KM1 and KM2: Contactors Connect a 24V dc power supply to terminals V0 and G0, the power supply terminals for internal circuits.
Installing and Wiring the SmartGuard 600 Controller Chapter 2 Figure 13 - User Mode Switch S1 I0 I2 I4 I 6 I8 I1 0 I12 I14 I11 I13 I15 I1 I3 I5 I7 I9 V1 G 1 T0 T2 O0 O2 O4 O 6 V2 G 2 T1 T3 O1 O3 O5 O7 E2 E1 and E2: 24V dc Power Supplies S1: User Mode Switch E1 Connect a 24V dc power supply to terminals V0 and G0, the power supply terminals for internal circuits.
Chapter 2 Installing and Wiring the SmartGuard 600 Controller Notes: 40 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 3 Set Up Your DeviceNet Network Introduction Connecting a Computer to the DeviceNet Network Topic Page Connecting a Computer to the DeviceNet Network 41 Commission All Nodes 42 Browse the Network 44 Configuration Signature 44 Safety Reset (optional) 45 Setting Passwords (optional) 47 To access a network, either: • connect directly to the network. • connect to a different network and browse to the desired network via a linking device.
Chapter 3 Set Up Your DeviceNet Network 3. From the pull-down the list of Available Driver Types, add the driver for your network. Network Driver RS-232 RS-232 DF1 devices EtherNet/IP Ethernet devices DeviceNet DeviceNet drivers USB SmartGuard USB Driver 4. Configure the driver. The settings you make are dependent upon the network you choose and whether you are using a communication card or interface module. Make Sure the Driver Works 1.
Set Up Your DeviceNet Network Chapter 3 Follow these steps to use the Node Commissioning tool. 1. Within RSNetWorx for DeviceNet software, choose Tools>Node Commissioning. 2. Click Browse on the Node Commissioning dialog box to select a device by browsing the network. You can browse through the SmartGuard USB port or the Ethernet/IP port to reach the DeviceNet port. 3. Select the DeviceNet network in the left panel. 4. Select the device you want to commission in the right panel and click OK. 5.
Chapter 3 Set Up Your DeviceNet Network Browse the Network Follow these steps to browse the network. 1. Determine your connection type. If you are using this connection type Then DeviceNet network Go to step 2. USB Port Follow these steps to configure a path to the DeviceNet network. A. From the Network menu, choose Properties. B. On the DeviceNet dialog box, click Set Online Path. C. On the Browse for Network dialog box, select the desired path and click OK.
Set Up Your DeviceNet Network Chapter 3 The configuration signature is composed of an ID number, a date, and a time and is set automatically by RSNetWorx for DeviceNet software when a configuration update is applied to the device. The configuration signature is found on the Safety tab of the Device Properties dialog box. It is also displayed on the alphanumeric display, on character at a time, when the service switch is pressed.
Chapter 3 Set Up Your DeviceNet Network You can reset the attributes shown on the Reset Safety Device dialog box by checking their associated checkbox. Leaving an attribute checkbox blank preserves that attribute’s setting during the safety reset operation. 1. Open the Reset Safety Device dialog box by clicking on the device in the RSNetWorx for DeviceNet software graphic view and selecting Reset Safety Device from the Device menu. 2. Check the attributes you want to reset.
Set Up Your DeviceNet Network Setting Passwords (optional) Chapter 3 You can protect safety devices with a password to prevent changes to the configuration of the device by unauthorized personnel. When a password is set, the following operations require the password to be typed. • Download • Safety-configuration reset • Safety-lock • Safety-unlock Set or Change a Password Follow the steps below to set a password for a module. 1. Double-click the module to open the Device Properties dialog box. 2.
Chapter 3 Set Up Your DeviceNet Network Forgotten Passwords It is in the best interests of Rockwell Automation customers and partners that, where possible, user-defined configurations, programs, and intellectual property stored within a product remain protected from unauthorized disclosure and tampering. Definitive authorship or ownership of such user-defined content cannot be completely verified by Rockwell Automation.
Chapter 4 Set Up Your EtherNet/IP Network Introduction Connecting a Computer to the EtherNet/IP Network Topic Page Connecting a Computer to the EtherNet/IP Network 49 Connecting the SmartGuard 600 Controller to the EtherNet/IP Network 50 Bridging across Networks 56 To access the EtherNet/IP network, either: • connect directly to the network. • connect to a different network and browse to the desired network via a linking device.
Chapter 4 Set Up Your EtherNet/IP Network Configure a Driver for the Network 1. Start RSLinx software. For the RSLinx software to locate new devices on the EtherNet/IP network, the driver can be set up (browse the remote subnet option) to look for a specific IP address and mask. 2. Click Configure Driver. 3. From the Available Driver Types pull-down menu, choose the driver for your network.
Set Up Your EtherNet/IP Network Chapter 4 Setting the IP Address To configure the controller, define the IP address, subnet mask, and gateway. Table 4 - EtherNet/IP Parameters EtherNet/IP Parameter Description IP Address The IP address uniquely identifies the controller. The IP address is in the form xxx.xxx.xxx.xxx. where each xxx is a number between 0 and 255. The following reserved values cannot be used: ·127.0.0.1 ·0.0.0.0 ·255.255.255.
Chapter 4 Set Up Your EtherNet/IP Network • The processor broadcasts a BOOTP-request message containing its hardware address over the local network or subnet. • The BOOTP server compares the hardware address with the addresses in its look-up table. • The BOOTP server sends a message back to the processor with the IP address and other network information that corresponds to the hardware address it received.
Set Up Your EtherNet/IP Network Chapter 4 In the BOOTP Request History panel you will see the hardware addresses of devices issuing BOOTP requests. 2. Double-click the hardware address of the device you want to configure. You will see the New Entry pop-up window with the device's Ethernet Address (MAC). 3. Enter the IP Address (Hostname and Description are optional) that you want to assign to the device, and click OK.
Chapter 4 Set Up Your EtherNet/IP Network The device will be added to the Relation List, displaying the Ethernet Address (MAC) and corresponding IP Address, Subnet Mask, and Gateway (if applicable). Use RSLinx Software to Set the IP Address After you have used the BOOTP utility to initially set the IP address of a brand new SmartGuard 600 controller, you can then use RSLinx software to change the IP address.
Set Up Your EtherNet/IP Network Chapter 4 The RSWho dialog box appears. 4. Navigate in RSWho to the Ethernet network. 5. Right-click the SmartGuard controller and choose Module Configuration. TIP The module configuration option is also shown when viewing the SmartGuard controller from DeviceNet software, but the IP configuration is applied only when it is executed directly from the EtherNet/IP network. The Module Configuration dialog box appears.
Chapter 4 Set Up Your EtherNet/IP Network 6. Click the Port Configuration tab. 7. For Network Configuration Type, click Static to permanently assign this configuration to the port. IMPORTANT If you select Dynamic, on a power cycle, the controller clears the current IP configuration and resumes sending BOOTP requests. Refer to page 52 for more information. a. In the IP Address field, type the IP address. b. In the Network Mask field, type the network mask address. c.
Set Up Your EtherNet/IP Network Chapter 4 EtherNet/IP Network to a DeviceNet Network Here is a connection between the EtherNet/IP network and the DeviceNet network. The SmartGuard controller lets you use your personal computer that is connected to the EtherNet/IP network to configure the 1791DS module on the DeviceNet network by bridging through the SmartGuard controller. IMPORTANT The bridging capability of the SmartGuard controller is limited.
Chapter 4 Set Up Your EtherNet/IP Network Figure 16 - EtherNet/IP Bridge Linking to a DeviceNet Network EtherNet/IP Network DeviceNet Network DeviceNet Bridge in Same 1756 System EtherNet/IP Bridge in 1756 System 58 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Set Up Your EtherNet/IP Network Chapter 4 USB Port to the EtherNet/IP Network The SmartGuard controller supports bridging from the USB port to the EtherNet/IP network. However, we recommend not using this feature but rather connecting directly to the EtherNet/IP network to configure devices other than the SmartGuard controller. The SmartGuard controller can browse only on the Ethernet subnet that it is connected to.
Chapter 4 Set Up Your EtherNet/IP Network Notes: 60 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 5 Manage the Safety Network Number Introduction Topic Page Safety Network Number (SNN) Formats 61 Assignment of the Safety Network Number (SNN) 62 Set the Safety Network Number (SNN) in All Safety Nodes 63 Safety Network Number (SNN) Mismatch 65 Safety Network Number (SNN) and Node Address Changes 65 Each DeviceNet Safety device must be configured with a safety network number (SNN).
Chapter 5 Manage the Safety Network Number Time-based Safety Network Number (recommended) In the time-based format, the safety network number (SNN) represents the date and time at which the number was generated, according to the personal computer running RSNetWorx for DeviceNet software. Manual Safety Network Number (SNN) In the manual format, the SNN represents typed values from 1…9999 decimal.
Manage the Safety Network Number Chapter 5 Automatic (time-based) When a new safety device is added to the network configuration, a default SNN is automatically assigned via the configuration software, as follows. • If at least one safety device already exists in the DeviceNet network configuration, subsequent safety additions to that network configuration are assigned the same SNN as the lowest-addressed safety device.
Chapter 5 Manage the Safety Network Number Follow these steps if you need to set the SNN for a particular device. 1. Click the target device in the hardware graphic view and choose Set Safety Network Number from the Device menu. 2. Choose Time-based and click Generate, or choose Manual and fill in a decimal number from 1…9999. 3. Click OK. TIP You can use the copy and paste buttons on the Set Safety Network Number dialog box to copy and paste an SNN between devices and to make a record of the SNN. 4.
Manage the Safety Network Number Safety Network Number (SNN) Mismatch Chapter 5 RSNetWorx for DeviceNet software compares the offline SNN to the online SNN during each browse operation, one-shot or continuous, and during upload and download operations. If the SNNs do not match, RSNetWorx for DeviceNet software indicates an error with the SNN. The hardware graphic view displays the ! symbol over the safety device icon.
Chapter 5 Manage the Safety Network Number See Safety Reset (optional) on page 45 for more information on the Safety Reset function. TIP 66 After the safety reset, the node address can be changed in RSNetWorx for DeviceNet software by double-clicking the safety device’s node address in the graphic view. After changing the node address, rightclick the device and click Download to Device to restore the safety device’s SNN and configuration.
Chapter 6 Configure Local I/O Introduction Topic Configure Local Safety Inputs Page Configure Local Safety Inputs 67 Configure Local Test Outputs 71 Configure Local Safety Outputs 73 The controller has 16 local safety inputs that support the following features. • Input circuit diagnosis — Test pulse sources can be used to monitor internal circuits, external devices, and external wiring. • Input on- and off-delays — You can set input time filters of 0...
Chapter 6 Configure Local I/O 2. Select the Local Input/Test Output tab. 3. Set the Error Latch Time. The error latch time applies to all safety inputs and test outputs. It sets the time to latch the error state when an error occurs in an input or output. Even if the error is removed, the error state is always latched for the configured error latch time. The error latch time is set from 0…65530 ms in 10 ms increments. The default is 1000 ms. 4. Select a safety input terminal and click Edit. 5.
Configure Local I/O Chapter 6 6. Set the Channel Mode for the safety input. Channel Mode Description Not used The input channel is not connected to an external device. This is the default. Test pulse from test output Use this mode when you are achieving a Category 4 input circuit. This mode assumes that you have connected your input device to a Pulse Test Source, and then wired to this input terminal.
Chapter 6 Configure Local I/O 9. Specify an On Delay time and an Off Delay time. The valid range is 0…126 ms, but the delay time must be a multiple of the cycle time. IMPORTANT The optimum value for controller cycle time is automatically calculated based on the parameter settings and the application programs. Therefore, set the on- and off-delay times last.
Configure Local I/O Chapter 6 Automatic Adjustment of On- and Off-delay Times If parameters that affect the cycle time are changed after the on- and off-delays have been set, you may not be able to close the Controller Properties dialog box because of an error in the parameter settings. If this occurs, you can re-adjust the on-and off-delay times based on the cycle time by using the Adjust valid ON/ OFF delays with cycle time value button on the Local Input/Test Output tab.
Chapter 6 Configure Local I/O Follow these steps to configure a test output. 1. Right-click the SmartGuard controller and choose Properties. 2. Select the Local Input/Test Output tab. 3. Set the Error Latch Time. The error latch time applies to all safety inputs and test outputs. It sets the time to latch the error state when an error occurs in an input or output. Even if the error is removed, the error state is always latched for the configured error latch time.
Configure Local I/O Chapter 6 6. Type an I/O Comment. The I/O comment typed here is used as an I/O tag name in the Logic Editor. 7. Choose a Test Output Mode from the pull-down list. Configure Local Safety Outputs Test Output Mode Description Not used The corresponding Test Output is not used. Standard Output Choose this mode when connecting to the output from a muting lamp or programmable logic controller. This output is used as a monitor output.
Chapter 6 Configure Local I/O time. The error latch time is set from 0…65530 ms in 10 ms increments. The default is 1000 ms. 4. Select a safety output terminal and click Edit. 5. Type an I/O Comment. The I/O comment typed here is used as an I/O tag name in the Logic Editor. 6. Set the Channel Mode for the safety output. 74 Channel Mode Description Not used The output terminal is not connected to an output device. Safety A test pulse is not sent when the output is on.
Configure Local I/O Chapter 6 IMPORTANT If a safety pulse test is set, an off pulse signal (pulse width 580 µs) is output to diagnose the output circuit when the safety output turns on. Check the input response time of the control device to make sure this output pulse will not cause malfunctions. 7. Set the Dual Channel mode for the safety output. Setting Dual Channel mode enables an error to be detected if the two outputs from a user program are not equivalent.
Chapter 6 Configure Local I/O Notes: 76 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 7 Configure Your Controller for DeviceNet Communication Introduction The SmartGuard controller can function simultaneously as a safety master, safety slave, or standard slave.
Chapter 7 Configure Your Controller for DeviceNet Communication Figure 18 - SmartGuard Controller as the Safety Master SmartGuard Controller - Safety Originator Safety Connections CIP Safety I/O Modules Configure CIP Safety I/O Targets on the DeviceNet Network To configure your module, double-click the module in the graphic view or rightclick the module and choose Properties.
Configure Your Controller for DeviceNet Communication Chapter 7 Single Channel versus Dual-channel Equivalent or Dual-channel Complementary You can configure distributed I/O modules inputs for either Single- or Dualchannel mode. This tells the Guard I/O module whether to view the inputs individually (single-channel) or as input pairs (dual-channel).
Chapter 7 Configure Your Controller for DeviceNet Communication Download the Device Configurations Once you have configured the safety and standard I/O module parameters, download the configuration to the modules. To do this in RSNetWorx for DeviceNet software, from the Device menu, choose Download to Device. Configure Safety I/O Connections Safety I/O connections are used to exchange data automatically with the safety slaves without user programming.
Configure Your Controller for DeviceNet Communication Chapter 7 module will only accept the connection if the signature matches what is in the device. IMPORTANT If you do not choose Configuration signature must match, you are responsible for verifying the safety integrity of your system by some other means. 5. Review the Connection Reaction Time Limit. The Connection Reaction Time Limit is the maximum age of safety packets on the associated connection.
Chapter 7 Configure Your Controller for DeviceNet Communication • Timeout Multiplier – The Timeout Multiplier determines the number of RPIs to wait for a packet before declaring a connection timeout. This translates into the number of messages that may be lost before a connection error is declared. For example, a Timeout Multiplier of 1 indicates that messages must be received during every RPI interval.
Configure Your Controller for DeviceNet Communication Chapter 7 1. Highlight the I/O connection that you want to change or remove. 2. Click the ‘x’ button. This will let you remove an I/O connection. In this example, the next time you view your logic, an error message dialog box appears. 3. Click OK.
Chapter 7 Configure Your Controller for DeviceNet Communication 4. To locate invalid addresses, choose Function>Find Invalid Address or locate all red-flagged I/O tags and right-click on the red-flagged tag. The pull-down menu appears on the invalid tag. 5. Right-click the invalid tag. The Update IO Tag pull-down menu appears. The dialog box shows the tag error with the recommended tag.
Configure Your Controller for DeviceNet Communication Chapter 7 the tag was connected to originally. But you must verify and confirm that by double-clicking the suggested option. 6. If the recommended tag is correct, highlight the tag and click OK. If the recommended tag is not correct, double-click the line and a new dialog box appears that lets you select a replacement tag. You can also scroll for more options.
Chapter 7 Configure Your Controller for DeviceNet Communication 7. Click OK. ATTENTION: If multiple tags appear in the Update I/O Tag dialog box, all the tags must be accepted or alternatives picked before selecting OK. Otherwise the recommended I/O tag will be used. Refer to SmartGuard 600 Controllers Safety Reference Manual, publication 1752-RM001, for recommendations on setting up your safety system.
Configure Your Controller for DeviceNet Communication Setting Up the Controller as a Safety Slave Chapter 7 As a safety slave, the controller can perform safety I/O communication with a maximum of 4 connections, by using up to 16 bytes per connection. These connections can be either single-cast or multi-cast. However, for 1 multicast connection, the total number of masters that can be communicated with is 15.
Chapter 7 Configure Your Controller for DeviceNet Communication 2. Click the Safety Slave I/O tab. 3. Click New. 4. In the Edit Safety Slave I/O dialog box, click the I/O Type, either Safety Slave Input or Safety Slave Output. I/O Type Safety Data Direction Safety Slave Input SmartGuard controller safety slave —> safety master Safety Slave Output Safety master —> SmartGuard controller safety slave 5. To add status information for Safety Input types, check the appropriate Status checkbox.
Configure Your Controller for DeviceNet Communication Chapter 7 Safety Output types cannot include status data. You can only read status data; you cannot write to it. 6. To add local I/O monitor data for Safety Input types, check the appropriate Local I/O Monitor checkbox.
Chapter 7 Configure Your Controller for DeviceNet Communication b. Type a comment for each bit in the tag. The tag name comments typed here are displayed in the Logic Editor. c. Click OK. 11. Click OK again to return to the Safety Slave I/O tab. 12. Create additional safety slave input or output assemblies as required for your application by repeating steps 3…11. 13. To save your configuration, from the File menu, choose Save.
Configure Your Controller for DeviceNet Communication Chapter 7 4. On the Module Definition dialog box, set the parameters as shown. 5. On the Module Definition tab, click the Connection tab. 6. Set the safety input and output parameters by using the following tables.
Chapter 7 Configure Your Controller for DeviceNet Communication Table 7 - Output Assemblies When the safety slave output name is Set the generic profile input instance number to Set the generic profile output instance number to Safety Output 1 255 17 (for 0x11) Safety Output 2 255 18 (for 0x12) Safety Output 3 255 19 (for 0x13) Safety Output 4 255 20 (for 0x14) SmartGuard Controller to SmartGuard Controller Safety Interlocking Safety interlocking allows two SmartGuard controllers to share s
Configure Your Controller for DeviceNet Communication Chapter 7 2. On the Safety Connections tab of the other SmartGuard controller, the one that will be the safety master, right-click the SmartGuard controller and choose Add Connection. 3. From the Connection Name pull-down menu, choose the safety I/O assembly you want to use. 4. Click Add.
Chapter 7 Configure Your Controller for DeviceNet Communication Now the SmartGuard controller acting as the safety master will be able to read the other SmartGuard controller’s inputs, 0…7.
Configure Your Controller for DeviceNet Communication Setting Up the Controller as a DeviceNet Standard Slave Chapter 7 As a DeviceNet standard slave, the controller can perform standard I/O communication with 1 standard master for up to 2 connections, by using up to 16 bytes per connection (128 bytes for input data for EtherNet/IP communication). The SmartGuard controller can also respond to explicit standard messages.
Chapter 7 Configure Your Controller for DeviceNet Communication 4. Click New. 5. Click the I/O type: Poll, Bit-Strobe, COS, or Cyclic. Output data cannot use a bit-strobe connection type because bitstrobe data cannot be output from the standard master. Also, the maximum size for bitstrobe data input to the standard master is 8 bytes. COS and cyclic connections cannot be used at the same time. 6. To add status information for Input types, check the Status checkboxes (optional).
Configure Your Controller for DeviceNet Communication Chapter 7 7. To add local I/O monitor data for Input types, check the appropriate Local I/O Monitor checkbox. Tag Name Data Size Attribute Type Local Input Monitor 1 (Inputs 0…7) Byte Non-safety Local Input Monitor 2 (Inputs 8…15) Byte Non-safety Local Output Monitor (Outputs 0…7) Byte Non-safety Output types cannot include local I/O monitor data. You can read only input and output values; you cannot directly write to them. 8.
Chapter 7 Configure Your Controller for DeviceNet Communication 11. To create a tag name for each bit in an I/O assembly, follow these steps. a. Select the applicable assembly and click Edit Comment. b. Type a comment for each bit in the tag. The tag name comments typed here are displayed in the Logic Editor. c. Click OK. 12. Click OK again to return to the Slave I/O tab. 13. Create additional slave input or output assemblies as required for your application by repeating steps 4…12. 14.
Configure Your Controller for DeviceNet Communication Chapter 7 Adding the SmartGuard Standard Slave to the Standard Master’s Scanlist To make the standard slave I/O assemblies available to the standard master, add the SmartGuard standard-slave controller to the master’s scanlist. Refer to the user documentation for your standard master for information on configuring your specific device. Save your configuration in RSNetWorx for DeviceNet software by choosing File>Save.
Chapter 7 Configure Your Controller for DeviceNet Communication Reading and Writing to and from the SmartGuard Controller to a PanelView Plus Interface This section describes how to read and write from the SmartGuard controller and the PanelView™ Plus interface. The SmartGuard controller is a standard slave within this architecture. Refer to page 95 for more information.
Configure Your Controller for DeviceNet Communication Chapter 7 This configuration allows 32 bytes of input data (16 via polled and 16 via COS or Cyclic) and 16 bytes of output data via the polled connection. This configuration is described in greater detail in this chapter. Read BOOLs from the SmartGuard Controller and Display Them on the PanelView Plus Interface Follow this procedure to read BOOLs from the SmartGuard controller and display them on the PanelView Plus interface. 1.
Chapter 7 Configure Your Controller for DeviceNet Communication In this case, a single 4-byte tag has been created and will use a polled connection. These 4 bytes are read by the PanelView Plus interface. Even though you created a DWORD tag, you have access to all 32 bits of the DWORD within the SmartGuard editor. The sample SmartGuard code is controlling two of the 32 bits. The bolded tags in the taglist are used in code. 6. Download the configuration to the SmartGuard 600 controller.
Configure Your Controller for DeviceNet Communication Chapter 7 Configure the Scanlist of the PanelView Scanner Follow this procedure to configure the scanlist of the PanelView Plus DeviceNet scanner. 1. Click the Scanlist tab. 2. Click the right arrow to move the SmartGuard controller to the scanlist. 3. Click Edit I/O Parameters and verify it is configured as shown below. The example has a 4-byte polled connection that will be an input to the PanelView Plus interface.
Chapter 7 Configure Your Controller for DeviceNet Communication 4. Verify that the 4 bytes of input data are mapped as shown. 5. Right-click the PanelView Plus Interface in RSNetWorx software and choose Download to Device. Configure the RN10C DeviceNet Scanner Follow this procedure to configure the RN10C DeviceNet scanner. The shortcut in RSLinx Enterprise software should appear similar as shown. Note that the slot number of the RN10C scanner is 2. 1.
Configure Your Controller for DeviceNet Communication Chapter 7 3. From the appropriate pull-down menu, choose the Node Address, Slot in the Virtual Backplane, and Baud rate. The PanelView Plus interface is configured for DeviceNet node 7. The SmartGuard controller has the DIP switches set for auto-sensing (left/ left/left/right from top to bottom). Choose the the baud rate that is appropriate for your application. 4. Click the I/O Configuration tab. The following dialog box appears. 5.
Chapter 7 Configure Your Controller for DeviceNet Communication 7. Click OK. The I/O configuration appears. 8. Right-click 0-3 Bytes and choose Add Devices. The following dialog box appears.
Configure Your Controller for DeviceNet Communication Chapter 7 9. Set the Node number to match your SmartGuard controller. The node number is 2 in this example. 10. Click OK. The following dialog box appears. 11. Right-click 0-3 Bytes and choose Add Alias. The following dialog box appears. 12. Select the bolded data type (BOOL) and from the appropriate pull-down, choose the Start Byte, Array Count, and Start Bit. The values shown above represent bit 0 of the first byte. 13. Enter the Name. 14.
Chapter 7 Configure Your Controller for DeviceNet Communication The following dialog box appears. To add a second BOOL that represents bit 1 of the first byte, follow this procedure. 1. Right-click 0-3 Bytes and choose Add Alias. The following dialog box appears when BOOL data type is selected. 2. From the appropriate pull-down menu, choose the Start Byte, Array Count, and Start Bit. 3. Enter the Name. 4. Click OK.
Configure Your Controller for DeviceNet Communication Chapter 7 The following dialog box appears. 5. Click OK. The final step is to create the PanelView Plus graphic that reads the alias tags. This example will use two multistate indicators that read the two aliases. The tags for each of the multistate indicators can be browsed by using RSLinx Enterprise software. Select the tags as shown. Finally, you need to save your project, generate a Runtime file, and download it to the PanelView Plus interface.
Chapter 7 Configure Your Controller for DeviceNet Communication Read and Write from and to the SmartGuard Controller from the PanelView Plus Interface Concurrently This example shows how to use two maintained push buttons on a PanelView Plus screen to control two tags within the SmartGuard 600 controller. To accomplish this, a single byte of data is sent from the the PanelView Plus interface to the SmartGuard controller.
Configure Your Controller for DeviceNet Communication Chapter 7 The following dialog box appears. 4. Click the IN tab. 5. Enter the tag names that will be read by the PanelView Plus interface. 6. Click the OUT tab. 7. Enter the tag names that will be written to by the PanelView Plus interface.
Chapter 7 Configure Your Controller for DeviceNet Communication In this case, a polled connection with 4 bytes that can be read and 1 byte that can be written to will be used. You also have access to all the bits of the DWORD and BYTE within the SmartGuard editor. The sample SmartGuard code is using two bits in both buffers. The four bolded tags in the taglist are used in code.
Configure Your Controller for DeviceNet Communication Chapter 7 The Input tab is shown below and so the PV_to_SG tags are displayed. To view the SG_to_PV tags, click the Output tab. 8. Download the configuration to the SmartGuard 600 controller. Configure the Scanlist of the PanelView Scanner For the PanelView Plus DeviceNet scanner, you must configure the scan list. Follow this procedure to add the SmartGuard 600 controller to the Scan list. 1. Click the Scanlist tab. 2.
Chapter 7 Configure Your Controller for DeviceNet Communication The example has a polled connection that will read 4 bytes and write 1 byte between the SmartGuard controller and the PanelView Plus interface. Because the Automap on Add was checked, the following mapping occurred automatically. 4. Verify that the 4 bytes of input data and the single byte of output data are mapped as shown. 5.
Configure Your Controller for DeviceNet Communication Chapter 7 Configure the RN10C DeviceNet Scanner Follow this procedure to configure the RN10C DeviceNet scanner. The shortcut in RSLinx Enterprise software should appear similar as shown. Note that the slot number of the RN10C is 2. 1. Right-click the RN10C scanner and choose Properties. The following dialog box appears. 2. Enter the name of the scanner. 3.
Chapter 7 Configure Your Controller for DeviceNet Communication The following dialog box appears. The configuration of the input block is covered in the ‘How to Read BOOLs’ section of this document. Refer to that section to configure the data that will be read from the SmartGuard controller and displayed on the PanelView Plus interface.
Configure Your Controller for DeviceNet Communication Chapter 7 The following dialog box appears. 4. Right-click 0-0 Bytes and choose Add Devices. The following dialog box appears. 5. Set the Node number to match your SmartGuard controller. The node number is 2 in this example. 6. Click OK. The following Dialog box appears. 7. Right-click 0-0 Bytes and choose Add Alias.
Chapter 7 Configure Your Controller for DeviceNet Communication The following dialog box appears when the BOOL data type is selected. The values shown above represent bit 0 of the first byte. 8. From the appropriate pull-down menu, choose the Start Byte, Array Count, and Start Bit. 9. Enter the Name. 10. Enter the initial value of 0. 11. Click OK. The following dialog box appears. To add a second BOOL that represents bit 1 of the first byte, follow this procedure.
Configure Your Controller for DeviceNet Communication Chapter 7 1. Right-click 0-0 Bytes and choose Add Alias. 2. Select the BOOL data type and from the appropriate pull-down, choose the Start Byte, Array Count, and Start Bit. 3. Enter the Name. 4. Enter the initial value of 0. 5. Click OK. The following dialog box appears. 6. Click OK. The final step is to create the PanelView Plus graphic that reads the alias tags. This example will use 2 maintained buttons that read the 2 aliases.
Chapter 7 Configure Your Controller for DeviceNet Communication Figure 22 - PanelView Plus Graphic The tags for each of the maintained buttons can be browsed by using RSLinx Enterprise software. Select the tags as shown. Figure 23 - Browse the Tags for Maintained Buttons Finally, you need to save your project, generate a Runtime file, and download it to the PanelView Plus interface.
Configure Your Controller for DeviceNet Communication Chapter 7 The following edits occur in the SmartGuard slave I/O configuration.
Chapter 7 Configure Your Controller for DeviceNet Communication The following edits occur in the RN10C DeviceNet scanner configuration in RSNetWorx software. Figure 25 - RN10C DeviceNet Scanner Configuration Changes Maximum Connection Sizes This example has a polled connection with 16 bytes input and 16 bytes output. A second connection (cyclic) of 16 bytes input was added. The following show the changes required to support the configuration. The SmartGuard slave I/O configuration appears as shown.
Configure Your Controller for DeviceNet Communication Chapter 7 Figure 26 - SmartGuard Slave I/O Configuration The DeviceNet scanner connection properties appear as shown. Figure 27 - DeviceNet Scanner Configuration The FactoryTalk® to RSView® Enterprise software I/O configuration appears as shown.
Chapter 7 Configure Your Controller for DeviceNet Communication Figure 28 - FactoryTalk to RSView Enterprise Software I/O Configuration 124 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 8 Configure Your Controller for EtherNet/IP Communication Introduction The SmartGuard controller (catalog number 1752-L24BBBE) offers EtherNet/ IP connectivity.
Chapter 8 Configure Your Controller for EtherNet/IP Communication Configure Target I/O in RSNetWorx for DeviceNet Software Follow these steps to create standard EtherNet/IP target I/O assemblies. 1. In RSNetWorx for DeviceNet software, right-click the SmartGuard controller and choose properties. 2. Click the EtherNet/IP Target I/O tab. 3. Click New. The following dialog box appears.
Configure Your Controller for EtherNet/IP Communication Chapter 8 4. Under I/O type, click either Target Input or Target Output. Target Input means that this data is produced by the SmartGuard controller and read by the originating device. Target Output means that this data is produced by the originating device and is sent to the SmartGuard controller. If you have checked Target Input, you can include the following status information in the I/O assembly.
Chapter 8 Configure Your Controller for EtherNet/IP Communication d. Select the byte you would like to add. e. Click OK. f. Repeat steps a...e to add additional Routing I/O. 8. Under I/O Tag, click New to create an I/O tag. Multiple I/O tags can be defined in an I/O assembly. I/O tags up to 16 bytes can be defined in each I/O assembly. The I/O tags here can be used in the Logic Editor.
Configure Your Controller for EtherNet/IP Communication Chapter 8 10. Click OK. The following dialog box appears. 11. Create a tag name for each bit in an I/O assembly. a. Under I/O Tag, select the applicable assembly and click Edit Comment. b. Enter a comment for each bit in the tag. The tag name comments entered here are displayed in the Logic Editor. c. Click OK. 12. Click OK to return to the EtherNet/IP Target I/O tab.
Chapter 8 Configure Your Controller for EtherNet/IP Communication Set Up Your Controller as a Slave by Using RSLogix 5000 Software Generic Profile Once you have configured the data to be shared in the SmartGuard controller, you can now use the RSLogix 5000 software and the standard generic profile to exchange that data with a Logix controller. Follow these steps to connect to the controller. 1. Right-click the Ethernet network in the controller organizer and choose New Module. 2.
Configure Your Controller for EtherNet/IP Communication Chapter 8 This dialog box shows the instance values for an input/output connection. The table provides the instance values for an input/output connection and input only connection. Connection Type Input/Output Input only Instance Number Input (SmartGuard controller to controller) 100, 101 Output (controller to SmartGuard controller) 102, 103 Input 100, 101 Output 199 5. Click OK.
Chapter 8 Configure Your Controller for EtherNet/IP Communication Configure Communication between a Standard PanelView Terminal and a SmartGuard 600 Controller over an EtherNet/IP Network Follow these steps to configure a standard PanelView terminal to be able to communicate with a SmartGuard 600 controller over an EtherNet/IP network. 1. Open your PanelView application within PanelBuilder™ 32 software.
Configure Your Controller for EtherNet/IP Communication Chapter 8 1. Click Tag Editor in the application explorer. The application’s tag editor opens. 2. On the bottom of the tag editor, click the ENet-CIP tab. 3. Click Insert to add a new tag. 4. In the new tag cells, type the Tag Name, a Data Type, and Node Name (which matches the node name you defined for the SmartGuard controller in the Communications Setup). In this example, we chose DINT as the data type.
Chapter 8 Configure Your Controller for EtherNet/IP Communication For input assemblies, the CIP message codes include the following: • Service: 0xE - Get Single Attribute • Class: 4 • Instance: 100 or 101 (input 1 or input 2 respectively) • Attribute: 3 For output assemblies, the CIP message codes include the following: • Service: 0x10 - Set Single Attribute • Class: 4 • Instance: 102 or 103 (output 1 or output 2 respectively) • Attribute: 3 This example shows a CIP message code that accesses Input Assemb
Chapter 9 Set Controller Modes Introduction Set Automatic Execution Mode (optional) Topic Page Set Automatic Execution Mode (optional) 135 Set Standalone Communication Mode (optional) 136 Change Controller Mode 137 The controller can be configured for Normal mode or Automatic Execution mode. Set the Automatic Execution mode only after the system has been configured. The setting becomes effective after you have cycled power following a configuration download. Follow these steps to set the mode.
Chapter 9 Set Controller Modes 3. Choose either Normal Mode or Automatic Execution Mode. Mode Description Normal The controller starts in Idle mode when the power supply is turned on. You must use RSNetWorx for DeviceNet software to change to Execute mode by clicking Change Mode on the Mode/Cycle Time tab of the Controller Properties dialog box.
Set Controller Modes Chapter 9 4. Select the Mode/Cycle Time tab. 5. Choose Disable (Stand Alone Mode) and click OK. Change Controller Mode Follow these steps to change the controller mode. 1. Go online with the SmartGuard controller. 2. Right-click the controller and choose Properties. 3. Select the Mode/Cycle Time tab on the Controller Properties dialog box. 4. Click Change Mode. 5. Select the Idle or Execute radio button. 6. Click OK.
Chapter 9 Set Controller Modes Notes: 138 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 10 Create Your Application Program Introduction The Logic Editor Topic Page The Logic Editor 139 Programming Basics 140 Creating a Function Block Program 144 Edit Function Block Parameters 146 Find Function Blocks with Open Connections 148 Program on Multiple Pages 149 Save the Program 150 Update the Program 150 Monitor the Program Online 151 Program Execution Sequence 152 User-defined Function Blocks 152 Additional Resources 157 You program the SmartGuard 600 controll
Chapter 10 Create Your Application Program You can password-protect your application program to prevent unauthorized editing, verification, or printing of programs. To create a password, follow these steps. 1. On the Logic tab of the Controller Properties dialog box, check the Enable Password checkbox. 2. On the Change Password dialog box, type in the password in the New Password field. Passwords may contain up to six characters. 3. Re-type the password in the Confirm Password field. 4. Click OK.
Create Your Application Program Chapter 10 Logic Functions and Function Blocks A maximum of 254 logic functions and function blocks can be used.
Chapter 10 Create Your Application Program In the object list, I/O tags are displayed with symbols to indicate how they are configured.
Create Your Application Program Chapter 10 Output Tags Output tags reflect the status of outputs from these I/O areas: • The controller’s local terminals • Output area of safety slaves registered as communication partners • Output area reflected from safety master data • Output area reflected from standard master data In the object list, I/O tags are displayed with symbols to indicate how they are configured.
Chapter 10 Create Your Application Program I/O Comment Function The I/O comment is an optional name, consisting of up to 32 ASCII characters that can be registered in the controller for each I/O terminal by using RSNetWorx for DeviceNet software. These I/O comments can be used in the object list of the Logic Editor as I/O tags, simplifying programming.
Create Your Application Program Chapter 10 2. Select the tag you want to use, and drag and drop it into position on the workspace. You can select multiple I/O tags and position them at the same time. Figure 33 - Place Input Tags TIP Input and output tags that are used in the application program appear bolded in the object list. Add a Function Block Follow these steps to add a function block to the workspace. 1. Click the Function Block tab in the object list. 2.
Chapter 10 Create Your Application Program Figure 35 - Connect Tags to Function Blocks Edit Function Block Parameters You can edit function blocks by changing parameter settings, changing the number of inputs or outputs, adding optional I/O, and adding comments pertaining to your application. The parameters that can be edited depend upon the type of function block. To open the Function Block Properties dialog box, right-click the function block and choose Edit.
Create Your Application Program Chapter 10 Figure 37 - In/Out Setting Tab Number of Inputs The number of inputs for logic functions can be increased or the optional input to function blocks can be enabled. Number of Outputs The number of outputs for logic functions can be increased or the optional outputs, such as error outputs, from function blocks can be enabled.
Chapter 10 Create Your Application Program Figure 38 - Out point Tab Comments Choose the Comments tab to type a name for the function block or I/O signals. The names of I/O signals are not displayed in the workspace, but the name of the function block is displayed under the function block in the workspace. All names typed in this dialog box are printed when the application program is printed.
Create Your Application Program Chapter 10 Figure 40 - Function Block With Open Connections Open Connection To find all open connections in the Logic Editor, choose Edit>Search OpenConnection. The Open Connection dialog box shows all the function blocks with open connections. Double-click an item on the list to display the function block. Open connections are shown in red in the workspace.
Chapter 10 Create Your Application Program 3. Connect the jump address to the function block. 4. Select the page to which you want to connect the logic. 5. Right-click anywhere on the page and choose Select JumpAddress. 6. Select the jump address from the pull-down menu. 7. Connect the jump address to the function block. Save the Program Follow these steps to save your application program. 1. Choose File>Apply. The program is saved temporarily in RSNetWorx for DeviceNet software. 2.
Create Your Application Program Chapter 10 error occurs, start the Logic Editor and check the program, making any necessary modifications. Monitor the Program Online The I/O tag values and signal states of connections with function blocks can be monitored online in the Logic Editor. Make sure that RSNetWorx for DeviceNet software is connected to the network and that the controller being monitored is in Run mode before starting online program monitoring.
Chapter 10 Create Your Application Program Program Execution Sequence The order of execution of function blocks is automatically set by the Logic Editor and displayed in the right-hand corner of each function block. Figure 41 - Example Program In this example, the execution order is: 1. E-stop 2. Reset 3. External Device Monitoring (EDM) Jump addresses can be used in programs to create loopbacks.
Create Your Application Program Chapter 10 Create User-defined Function Blocks Follow these steps to create a user-defined function block. 1. Open the Logic Editor by right-clicking the controller, choosing Properties, and clicking Edit on the Logic tab. 2. Choose FunctionBlock>Create. 3. On the IOProperty dialog box, define the number of inputs and outputs for the function block. 4. Assign names to each input and output. 5. Click OK to open the Function Block Logic Editor. 6.
Chapter 10 Create Your Application Program 8. Add the new function block to your application logic. TIP If you wish to edit your user-defined function block, it cannot be used in the current application. If it is, the edit option is unavailable. IMPORTANT Always download programs with user-defined function blocks to the controller, check their configuration, and verify their operation before using them in an application.
Create Your Application Program Chapter 10 2. In the Function Block Editor, choose File>Change Password. 3. Type a password of up to six alphanumeric characters in the New Password field. 4. Re-type the password in the Confirm Password field. 5. Click OK. The user-defined function block cannot be edited or deleted without entering the password.
Chapter 10 Create Your Application Program 3. Validate the user-defined function block. a. In the object list of the Logic Editor, right-click the new function block and choose Validate. b. Click OK on the confirmation dialog box. The icon for the new function block changes from white to yellow to indicate that the function block has been validated. 4. Export the user-defined function block to a file. a. In the object list of the Logic Editor, click the saved user-defined function block. b.
Create Your Application Program Chapter 10 Precautions for Reusing User-defined Function Blocks This table indicates which actions require user-defined function block files and describes what happens if the action is attempted without the function block file.
Chapter 10 Create Your Application Program Notes: 158 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 11 Download and Verify Introduction Download the DeviceNet Network Configuration Topic Page Download the DeviceNet Network Configuration 159 Verifying Your DeviceNet Safety Configuration 161 Start the Safety Device Verification Wizard 161 Determine if Devices Can Be Verified 161 Select Devices to Verify 163 Review the Safety Device Verification Reports 164 Lock Safety Devices 166 View the Safety Device Verification Wizard Summary 167 Before you download, you must go online to
Chapter 11 Download and Verify Follow these steps to download the DeviceNet network configuration. 1. Go online by clicking the online icon. 2. Browse to the DeviceNet network and click OK at the prompt. During each browse operation, RSNetWorx for DeviceNet software reads the following attributes of each device.
Download and Verify Verifying Your DeviceNet Safety Configuration IMPORTANT Chapter 11 Before running the Safety Device Verification Wizard, you should browse and upload your network and test the safety devices and all of their safety functions on your network to verify that they are operating properly. You must fully test your application prior to safety-locking your devices.
Chapter 11 Download and Verify listing those devices and their current status, including a device icon overlaid with a status icon. Status Icon Overlay Description Missing The device is part of the network configuration, but was not found during the browse operation. Mismatch The device identity in the network configuration does not match the identity of the online device. Unknown The device is in the configuration, but has not been detected on the network yet.
Download and Verify Select Devices to Verify Chapter 11 Choose which devices to verify by using the checkboxes in the Verify column of the Verify Safety Device Configuration dialog box. You can select only the devices whose status is Ready to be verified. If the Show all safety devices checkbox is checked, the dialog box lists all of the safety devices on the network and shows their current status.
Chapter 11 Download and Verify Click Next to begin the upload and compare process. TIP Review the Safety Device Verification Reports 164 If you click Next without selecting a device to verify, the wizard checks whether any devices were verified or are ready to be locked in this execution of the wizard. If Then the wizard displays Devices were verified the Review dialog box listing those devices. Devices are ready to be safetylocked the Lock dialog box listing those devices.
Download and Verify Chapter 11 1. Click Review in the Report column to launch the device’s HTML report in your default browser. 2. Click Review All to generate an HTML verification report for all of the devices listed. TIP If a device’s status is Verify FAILED, more information is provided in the verification failure report. 3. Review and print the verification reports for your records.
Chapter 11 Download and Verify Lock Safety Devices IMPORTANT Before you lock your safety device configurations, you must perform all of the verification steps required for your application. 1. Choose which devices to safety-lock by checking the checkbox in the Lock column for each device that is ready to be safety-locked. 2. You must check the acknowledgement checkbox before the locking process can continue. 3. Click Next.
Download and Verify View the Safety Device Verification Wizard Summary Chapter 11 Before closing, the wizard displays a summary of all the safety devices that were safety-locked, the number of safety devices that still need to be safety-locked, and lets you display the verified and safety-locked state of all of the safety devices on the network. Click Finish to close the wizard.
Chapter 11 Download and Verify Notes: 168 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Chapter 12 Monitor Status and Handle Faults Introduction Status Indicators Topic Page Status Indicators 169 Alphanumeric Display 170 Monitoring I/O Power Supply Input 171 Monitoring I/O Maintenance Information 172 Viewing I/O Status Data 175 Controller Connection Status (safety slave function) 177 Error Categories 179 Error History Table 179 Error History Messages and Corrective Actions 183 Download Errors and Corrective Actions 185 Reset Errors and Corrective Actions 187 Mode C
Chapter 12 Monitor Status and Handle Faults Alphanumeric Display The controller’s alphanumeric display provides DeviceNet error codes, DeviceNet node address, and EtherNet/IP address information. Under normal operating conditions, the display shows the node address of the module, 00…63 in decimal format. If the controller is operating in a standalone configuration (not networked), the display shows ‘nd’. The display flashes when the controller is self-testing, configuring, or in Idle mode.
Monitor Status and Handle Faults Monitoring I/O Power Supply Input Chapter 12 You can monitor the I/O power supply input by using the alphanumeric display on the front of the controller, as well as the general status data in DeviceNet I/O communication. If an I/O terminal on the controller is set to anything other than Not Used, and the normal power supply voltage is not supplied, the alphanumeric display shows: • P4: The power supply for inputs (V1,G1) is out of range.
Chapter 12 Monitor Status and Handle Faults Monitoring I/O Maintenance Information You can configure a maintenance mode and alarm threshold for each local input, test output, and local output terminal by using the Maintenance tab of the Controller Properties dialog box in RSNetWorx for DeviceNet software. You can configure a terminal for either contact operation counter or total on-time monitoring.
Monitor Status and Handle Faults EXAMPLE Chapter 12 ATTENTION: Calculating Total On-time With 1.5 Second On Pulses ATTENTION: In this example, the bit is actually on for 1.5 s x 2 = 3 s, but the bit is on 4 times when status is checked, so the total on-time is measured as 4 s. Measured 1 Time/Second ON OFF 1.5 s Configure a Maintenance Monitoring Mode Follow these steps to configure contact operation counter mode for a terminal. 1.
Chapter 12 Monitor Status and Handle Faults 4. Select the desired terminal and click Edit. 5. On the Edit Maintenance Config dialog box, choose the Detection mode, either Count or Time. 6. Type an alarm threshold value for the specified Detection mode. Detection Mode Valid Range for Values Time 0…4,294,967,295 seconds Count 0…4,294,967,295 times 7. Click OK. 8. Click OK. When you are online with the controller, you can monitor the configured terminals by clicking Monitor on the Maintenance tab.
Monitor Status and Handle Faults Chapter 12 2. Click Clear on the Maintenance Monitor dialog box. Viewing I/O Status Data When the controller operates as a safety slave or a standard slave target, status information can be added to the first line of the transmit data. The information can be stored in a controller and used to establish a monitoring system.
Chapter 12 Monitor Status and Handle Faults General Status Data The general status flags are non-safety attributes that indicate system status. Table 14 - General Status Data Details Bit Name Description 0 Input Power Supply Voltage Status Flag Indicates the status of the power supply voltage for inputs. OFF: Normal power supply is on. ON: Power-supply voltage error or power supply is off. 1 Output Power Supply Voltage Status Flag Indicates the status of the power supply voltage for outputs.
Monitor Status and Handle Faults Chapter 12 Local Output Status When the bit is on, the status of the output is normal. When the bit is off, an error has been detected Table 16 - Local Safety-Output Terminal Status Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Terminal 7 Terminal 6 Terminal 5 Terminal 4 Terminal 3 Terminal 2 Terminal 1 Terminal 0 Test Output or Muting Lamp Status When the bit is on, the status of the test output is normal.
Chapter 12 178 Monitor Status and Handle Faults Code Status Corrective Action 01:0115 Device type Error The device data for the device in the RSNetWorx for DeviceNet configuration file and the physical device in the system does not match. Use the Safety Device Verification Wizard to check that the device in the system and the device in the configuration file match. If they do match, re-configure the connections to the safety master.
Monitor Status and Handle Faults Error Categories Chapter 12 Controller errors can be categorized into nonfatal errors, abort errors, and critical errors. Table 18 - Controller Error Categories Error History Table Error Category Description Non-fatal Errors An error that stops each local I/O or safety I/O connection terminal and places it in the safety state. The controller continues to operate in Run mode.
Chapter 12 Monitor Status and Handle Faults 2. Click the Error History tab. a. Click Save to save the error history data, which can also be saved in a separate CSV file. b. Click Clear to erase the error history saved in the controller. c. Click Update to refresh the error history information. Display the EtherNet/IP Error History Table for the 1752-L24BBBE Controller Follow these steps to display the error history in real time by using RSNetWorx for DeviceNet software while online with the controller.
Monitor Status and Handle Faults Chapter 12 2. Click the EtherNet/IP Error History tab. a. Click Save to save the error history data, which can also be saved in a separate CSV file. b. Click Clear to erase the error history saved in the controller. c. Click Update to refresh the error history information.
Chapter 12 Error Code Monitor Status and Handle Faults Error Detail Code 1st Byte 03D0 Ethernet Basic Setting (1) 01: Ethernet Setting error 7-segment Display 2nd Byte (1) 01: Checksum error F2<->n4 11: Inconsistent setting 12; Specified baud rate is not supported 02: TCP/IP Basic Setting error 01: Checksum error 11: Invalid IP address 12: Invalid subnet mask 13: Invalid default gateway address 14: Invalid primary name server 15: Invalid secondary name server 16: Invalid domain server 17: Inva
Monitor Status and Handle Faults Chapter 12 Use the error history messages to identify and correct errors. Error History Messages and Corrective Actions Table 19 - Controller System Failure Error Messages Message Description Corrective Action System Failure A system failure occurred. Replace the controller if a system failure occurs again after cycling power. Invalid Configuration The configuration is invalid. The current configuration differs from the original configuration.
Chapter 12 Monitor Status and Handle Faults Table 21 - DeviceNet Communication Error Messages Message Description Corrective Action EM Transmission Error (Destination Device Absence) Unable to transmit because the destination device is not on the network. Check the node address of the destination node and the node address of the transmission message. Make sure the power supply voltage for the destination node is set within the specification range.
Monitor Status and Handle Faults Chapter 12 Table 24 - Safety Input Error Messages Message Description Corrective Action External Test Signal Failure at Safety Input A failure has occurred in the external wiring at the safety input. Discrepancy Error at Safety Input A discrepancy exists between two inputs configured as Dual Channel. Make sure the input signal wire is not contacting the power source (positive side). Make sure the input signal wire does not have an earth fault.
Chapter 12 Monitor Status and Handle Faults Table 27 - RSNetWorx for DeviceNet Software Download Error Messages and Corrective Actions Message Description Corrective Action Cannot be executed in the current mode. A fatal error (abort) has occurred, and the MS indicator flashes red. Check the switches to see if they are set correctly. Otherwise, execute a reset to clear the configuration data. The device is locked. The configuration is locked and the LOCK status indicator is lit. Unlock the device.
Monitor Status and Handle Faults Chapter 12 Table 27 - RSNetWorx for DeviceNet Software Download Error Messages and Corrective Actions Message Description Corrective Action Could not open connection. A connection to the controller could not be created when downloading to the controller via the DeviceNet or EtherNet/IP network. 1. Make sure that power to the device has been turned on and try downloading the data again. 2. Change the operating mode of the safety master to Idle. 3.
Chapter 12 Monitor Status and Handle Faults Mode Change Errors and Corrective Actions The controller may return an error response when you change modes. Use the messages displayed in RSNetWorx for DeviceNet software to identify the error. Table 29 - RSNetWorx for DeviceNet Software Mode-Change Error Messages and Corrective Actions Message Description Corrective Action Cannot be executed in the current mode. 1. The device has not been configured. 2. A fatal error (abort) has occurred. 1.
Appendix A Controller Specifications Introduction Topic Page General Specifications 189 Environmental Specifications 191 Certifications 193 General Specifications Attribute 1752-L24BBB 1752-L24BBBE Dimensions (HxWxD), approx. 99.0(4)x 99.4 x 131.4 mm(5) (3.90(4) x 3.91 x 5.18(5) in.) 99.0(4) x 113.0 x 131.4(5) mm (3.90(4) x 4.48 x 5.18(5) in.) Weight, approx. 460 g (1.23 lb) 575 g (1.54 lb) DeviceNet current load, max 15 mA @ 24V DC Supply voltage(1) 20.4…26.
Appendix A Controller Specifications Attribute 1752-L24BBB Voltage, off-state input, max 5V DC Current, off-state input, max 1 mA Input current 4.5 mA Input impedance 2.6 kΩ Test output type Current sourcing Pulse test output current(3) 0.7 A Test output surge current 0.7 A Pulse test off-state voltage, max 1.2V Pulse test output leakage current, max 0.
Controller Specifications Attribute 1752-L24BBB 1752-L24BBBE CIP connections Not applicable 2 Auto negotiation Not applicable Supported Data rate Not applicable 10/100 Mbps Duplex Not applicable Full/half Allowable unit communication bandwidth Not applicable 3000 pps(6) Explicit message communication Not applicable 502 bytes(7) Appendix A Ethernet communication (1) V0/G0 for internal logic circuit; V1/G1 for external input devices and test outputs; V2/G2 for external output devices.
Appendix A Controller Specifications Attribute 1752-L24BBB 1752-L24BBBE Radiated RF immunity IEC 61000-4-3: IEC 61000-4-3: · 10 V/m with 1 kHz sinewave 80% AM from 80…1000 MHz · 10 V/m with 1 kHz sinewave 80% AM from 80…1000 MHz · 10 V/m with 1 kHz sinewave 80% AM from 1.4…2.0 GHz · 10 V/m with 1 kHz sinewave 80% AM from 1.4…2.
Controller Specifications Appendix A Certifications Certification(1) (when product is marked) Value c-UL-us UL Listed for Class I, Division 2 Group A,B,C,D Hazardous Locations, certified for US and Canada. See UL File E194810 CE European Union 2004/108/EEC EMC Directive, compliant with: · EN 61000-6-4; Industrial Emissions · EN 61131-2; Programmable Controllers (Clause 8, Zone A & B) · EN 61326-1; Meas./Control/Lab.
Appendix A Controller Specifications Notes: 194 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Appendix B Status Indicators Introduction Module Status Indicators Topic Page Module Status Indicators 195 Identifying Errors Using Module Status Indicators and Alphanumeric Display 199 Identifying EtherNet/IP Errors Using Status Indicators and Alphanumeric Display 202 Use these tables to interpret the color of the status indicators and take recommended actions where applicable. ATTENTION: Status indicators are not reliable indicators for safety functions.
Appendix B Status Indicators If your Module Status indicator is solid red (on), follow these steps. 1. Cycle the power supply. 2. Check external wiring. 3. Take corrective actions for noise. 4. Contact Rockwell Automation. If your Module Status indicator is flashing red and green, follow these steps. 1. Configure the switches properly. 2. Set the safety network number. 3. Reconfigure the device.
Status Indicators Appendix B If the Lock Configuration (Lock) indicator is It means Take this action Yellow, on A locked valid configuration exists. No action required. Yellow, flashing An unlocked valid configuration exists. Lock the configuration before operating the safety system. Off The configuration is invalid. Reconfigure the controller. If the USB Communication (Comm U) indicator is It means Take this action Yellow, flashing The controller is communicating. No action required.
Appendix B Status Indicators If the EtherNet/IP Status (NS E) indicator is It means Take this action Green, on The controller has at least one established connection (even to the message router). No action required. Red, flashing One or more of the connections in which this device is the target has timed out. This shall be left only if all timed out connections are reestablished or if the device is reset. Refer to the corrective action following this table.
Status Indicators Identifying Errors Using Module Status Indicators and Alphanumeric Display Appendix B Use these tables to interpret the color and status combinations of the status and alphanumeric display indicators and take corrective action where applicable. Table 30 - Critical Errors Indicators MS NS Alphanumeric Display Code Error Log Cause Corrective Action 1. 2. 3. 4. Off Off Off None Critical hardware fault. Noise level higher than expected. Cycle the power supply.
Appendix B Status Indicators Table 32 - Nonfatal Errors Indicators MS Alphanumeric Display(1) Code I/O Error Log Cause Corrective Action --- E2 --- Transmission Timeout DeviceNet Transmission timeout or nothing connected to the DeviceNet network. Red, flashing A0 --- Relevant Safety I/O communication stopped because of a Safety I/O communication error A safety I/O connection timed out, interrupting the relevant safety I/O connection.
Status Indicators Appendix B Table 32 - Nonfatal Errors Indicators MS --- --- Alphanumeric Display(1) Code P3 P3 Error Log Cause Corrective Action Target terminal red, on Paired terminal red, flashing Overcurrent Detected at Safety Output An overcurrent was detected at the safety output. 1. Make sure there is no overcurrent for the output. 2.
Appendix B Status Indicators Identifying EtherNet/IP Errors Using Status Indicators and Alphanumeric Display Use these tables to interpret the color and status combinations of the status and alphanumeric display indicators and take corrective action where applicable. For the 1752-L24BBBE controller, when the IP address display switch for 1 second or longer, the display shows the EtherNet/IP address that is set. The error code ‘n4’ is displayed if an error occurs in EtherNet/IP configuration.
Appendix C Logic Functions Command Reference Introduction NOT Instruction This appendix describes the logic functions used for programming. Topic Page NOT Instruction 203 AND Instruction 204 OR Instruction 206 Exclusive OR Instruction 209 Exclusive NOR Instruction 210 Routing Instruction 211 Reset Set Flip-flop (RS-FF) Instruction 211 Multi-connector Instruction 212 Comparator Instruction 213 The outcome is the inverse of the input.
Appendix C Logic Functions Command Reference AND Instruction The output is the logical AND of up to eight input conditions. The number of inputs can be set by using the In/Out Setting tab in the Function Block Properties dialog box. The default setting is two inputs. AND Instruction Diagram Input 1 Output 1 Input 2 AND Instruction Truth Tables In the truth table, 0 is off and 1 is on. Lowercase x is don’t care.
Logic Functions Command Reference Appendix C Table 37 - Truth Table for Four-input AND Evaluation Input 1 Input 2 Input 3 Input 4 Output 1 0 x x x 0 x 0 x x 0 x x 0 x 0 x x x 0 0 1 1 1 1 1 Table 38 - Truth Table for Five-input AND Evaluation Input 1 Input 2 Input 3 Input 4 Input 5 Output 1 0 x x x x 0 x 0 x x x 0 x x 0 x x 0 x x x 0 x 0 x x x x 0 0 1 1 1 1 1 1 Table 39 - Truth Table for Six-input AND Evaluation Input 1 Input 2 Input
Appendix C Logic Functions Command Reference Table 41 - Truth Table for Eight-input AND Evaluation OR Instruction Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Input 8 Output 1 0 x x x x x x x 0 x 0 x x x x x x 0 x x 0 x x x x x 0 x x x 0 x x x x 0 x x x x 0 x x x 0 x x x x x 0 x x 0 x x x x x x 0 x 0 x x x x x x x 0 0 1 1 1 1 1 1 1 1 1 The Output is the logical OR of up to eight input conditions.
Logic Functions Command Reference Appendix C Table 44 - Truth Table for Three-input OR Evaluation Input 1 Input 2 Input 3 Output 1 0 0 0 0 1 x x 1 x 1 x 1 x x 1 1 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014 207
Appendix C Logic Functions Command Reference Table 45 - Truth Table for Four-input OR Evaluation Input 1 Input 2 Input 3 Input 4 Output 1 0 0 0 0 0 1 x x x 1 x 1 x x 1 x x 1 x 1 x x x 1 1 Table 46 - Truth Table for Five-input OR Evaluation Input 1 Input 2 Input 3 Input 4 Input 5 Output 1 0 0 0 0 0 0 1 x x x x 1 x 1 x x x 1 x x 1 x x 1 x x x 1 x 1 x x x x 1 1 Table 47 - Truth Table for Six-input OR Evaluation 208 Input 1 Input 2 In
Logic Functions Command Reference Appendix C Table 48 - Truth Table for Seven-input OR Evaluation Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Output 1 0 0 0 0 0 0 0 0 1 x x x x x x 1 x 1 x x x x x 1 x x 1 x x x x 1 x x x 1 x x x 1 x x x x 1 x x 1 x x x x x 1 x 1 x x x x x x 1 1 Table 49 - Truth Table for Eight-input OR Evaluation Exclusive OR Instruction Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Inpu
Appendix C Logic Functions Command Reference Table C.1 Truth Table for Exclusive OR Evaluation Exclusive NOR Instruction Input 1 Input 2 Output 1 0 0 0 0 1 1 1 0 1 1 1 0 The output is an exclusive NOR of the input conditions. Exclusive NOR Instruction Diagram Input 1 Output 1 Input 2 Exclusive NOR Instruction Truth Tables In the truth table, 0 is off and 1 is on. Table C.
Logic Functions Command Reference Appendix C The Routing instruction routes one input signal to a maximum of eight output signals. It is used to output a signal to more than one physical address, such as an output tag. The number of outputs can be set by using the I/O Setting tab in the Function Block Properties dialog box. The default setting is one. Routing Instruction Routing Instruction Diagram Input 1 Output 1 Routing Instruction Truth Table In the truth table, 0 is off and 1 is on. Table C.
Appendix C Logic Functions Command Reference Reset Set FIip-flop Error Handling Use this table to diagnose and reset a discrepancy error condition in the RS Flipflop instruction. Table 4 - Error Detection and Reset for RS Flip-flop Instruction Error Condition Status When an Error Occurs Input and Reset are active simultaneously To Reset the Error Condition Output Enable Fault Present OFF (Safety State) ON Make one of the signals inactive.
Logic Functions Command Reference Appendix C Multi-connector Instruction Truth Table In the truth table, 0 is off and 1 is on.
Appendix C Logic Functions Command Reference Comparator Instruction Diagram 1 0 1 0 1 1 0 1 0 1 Input 1 Output 1 Default Connections Output 1 Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Input 8 Maximum I/O for Comparator Instruction Comparator Instruction Parameters Set these parameters for the Comparator instruction.
Logic Functions Command Reference Appendix C Comparator Instruction Truth Table In the truth table, 0 is off and 1 is on. CV is the comparison value. An X indicates that the status of the input (match or don’t match) is not applicable.
Appendix C Logic Functions Command Reference Comparator Instruction Timing Chart The horizontal dashed lines in the chart represent the comparison values (CV) for each input. 1. Output 1 turns on when all of the input signals match the comparison value. 2. Output 1 turns off when any of the input signals does not match the comparison value.
Appendix D Function Blocks Command Reference Introduction Reset Function Block This appendix describes the function blocks used for programming.
Appendix D Function Blocks Command Reference The Output Enable signal turns on if the Reset signal is correctly received while the Monitored Input condition to the Reset function block is on. This function block can be used to prevent the machine from automatically resetting when power to the controller is turned on, when the operating mode is changed from Idle mode to Run mode, or when a signal from a safety input device turns on. The Static Release and Reset Required Indication are optional outputs.
Function Blocks Command Reference Appendix D Reset Function Block Timing Charts Figure 45 - Low-High-Low Reset Signal Monitored Input Optional Input (N) Reset Output Enable Static Release Reset Required Indication Idle to Run Figure 46 - Rising Edge Reset Signal Monitored Input Optional Input (N) Reset Output Enable Static Release Reset Required Indication Idle to Run Restart Function Block Figure 47 - Restart Function Block Diagram Restart Output Enable Static Release Monitored Input Restart Req
Appendix D Function Blocks Command Reference The Output Enable signal turns on if the Restart signal is correctly received while the Monitored Input condition to the Restart function block is on. This function block can be used to prevent the machine from automatically restarting when the power to the controller is turned on, when the operating mode is changed, or when a signal from a safety input device turns on. Reset and Restart are functionally identical.
Function Blocks Command Reference Appendix D Restart Function Block Timing Charts Figure 48 - Low-High-Low Restart Signal Monitored Input Optional Input (N) Restart Output Enable Static Release Restart Required Indication Idle to Run Figure 49 - Rising Edge Restart Signal Monitored Input Optional Input (N) Restart Output Enable Static Release Restart Required Indication Emergency Stop (ESTOP) Idle to Run Figure 50 - ESTOP Function Block Diagram Input 1 (NC) Output Enable Input 1 (NC) Output Ena
Appendix D Function Blocks Command Reference Enable turns off if the inputs become inactive or if an error is detected for the function block. IMPORTANT A manual reset function is required for emergency stop applications. When using the Emergency Stop push button function block, you must also use the Reset function block. The Discrepancy Error output can be used when programming the ESTOP function block.
Function Blocks Command Reference Appendix D ESTOP Function Block Error Handling A discrepancy error is generated when one of the inputs is not in it’s correct state for longer than the Discrepancy Time. For example, in Dual Channel Equivalent mode, both inputs must be active (on) within the Discrepancy Time or an error occurs. Use this table to diagnose and reset a discrepancy error condition in the ESTOP function block.
Appendix D Function Blocks Command Reference The Light Curtain monitoring function block monitors a type-4 safety light curtain. The Output Enable signal turns on when the inputs from the safety light curtain being monitored are active. The Output Enable signal turns off if the inputs become inactive or if an error is detected for the function block. You can use a Discrepancy Error output when programming the LC function block.
Function Blocks Command Reference Appendix D Use this table to diagnose and reset a discrepancy error condition in the LC function block. Table 15 - Error Detection and Reset for LC Function Block Error Condition Discrepancy Error Status When an Error Occurs Output Enable OFF (Safety State) Fault Present ON To Reset the Error Condition Error Output Discrepancy Error Output: ON Remove the cause of the error and then either: 1. Make the inputs inactive and active again. 2.
Appendix D Function Blocks Command Reference Safety Gate Monitoring Function Block Optional Outputs Optional outputs may also be used in programming. To display these optional outputs, check the appropriate checkbox on the Out point tab of the Function Block Properties dialog box in the Logic Editor of RSNetWorx for DeviceNet software.
Function Blocks Command Reference Appendix D Safety Gate Monitoring Function Block Parameters Set these parameters for the Safety Gate Monitoring function block.
Appendix D Function Blocks Command Reference Table 18 - Truth Table for Dual Channel (2 Pairs) Safety Gate Monitoring Function Block Dual Channel Equivalent (2 Pairs) Dual Channel Complementary (2 Pairs) Input 1 (NC) Input 2 (NC) Input 3 (NC) Input 4 (NC) Output Enable Input 1 (NC) Input 2 (NC) Input 3 (NC) Input 4 (NC) Output Enable 1 0 0 1 0 1 0 0 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 1 0 1 0 1 1 0 1 1 0 0 0 1 1 0 0 0 1 1 0 1 0 1 1 0 1 0 1 1 1 0
Function Blocks Command Reference Appendix D Safety Gate Monitoring Function Block Timing Charts Figure 53 - Single Channel With Function Test Enabled Input 1 Function Test Signal Function Test Required Output Enable Function Test Error Fault Present Idle to Run Figure 54 - Dual Channel Equivalent With Function Test Disabled Input 1 (NC) Input 2 (NC) Output Enable Discrepancy Error Fault Present Idle to Run Discrepancy Time Discrepancy Time Figure 55 - Dual Channel Equivalent (2 Pairs) With Function T
Appendix D Function Blocks Command Reference Two-hand Control Function Block Figure 56 - Two-hand Control Function Block Diagrams Input 1 (pair 1 - NO) Input 2 (pair 1 - NC) Input 1 (pair 1 - NO) Input 2 (pair 1 - NC) Output Enable Input 3 (pair 2 - NO) Input 4 (pair 2 - NC) Output Enable ! ! Input 3 (pair 2 - NO) Input 4 (pair 2 - NC) Default Connections ! Discrepancy Error (pair 1) Discrepancy Error (pair 2) Fault Present Maximum I/O for Two-hand Control Function The Two-hand Control functi
Function Blocks Command Reference Appendix D (1) A discrepancy time check is not performed if 0 is set. Two-hand Control Function Block Truth Table In the truth table, 0 is off and 1 is on.
Appendix D Function Blocks Command Reference (1) The Output Enable signal will not turn ON if the synchronization time requirement is not met (that is, operation inputs for both hands must be completed within 500 ms), but this is not considered an error.
Function Blocks Command Reference Appendix D OFF-delay Timer Function Block Timing Chart Input Set Value Timer Value 0 Output Enable Idle to Run ON-delay Timer Function Block Figure 58 - ON-delay Timer Function Block Diagram ON Input Output Enable The ON-delay timer function block performs a timer operation for an ON-delay set in 10 ms increments. The range for this delay is 0 ms…300 seconds. The default setting is 0 ms.
Appendix D Function Blocks Command Reference ON-Delay Timer Function Block Timing Chart Input Set Value Timer Value 0 Output Enable Idle to Run User Mode Switch Function Block Figure 59 - User Mode Switch Function Block Diagram 7 6 8 1 5 4 2 3 Input 1 Output 1 Input 2 Output 2 7 6 Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Input 8 8 1 5 4 2 3 Output 1 Output 2 Output 3 Output 4 Output 5 Output 6 Output 7 Output 8 Fault Present ! Maximum Inputs for User Mode Switch Function Def
Function Blocks Command Reference Appendix D User Mode Switch Function Block Fault Present Output Setting The Fault Present output can also be used in programming. To enable this output, check the Use Fault Present checkbox on the In/Out Settings tab of the Function Block Properties dialog box. User Mode Switch Function Block Truth Table In the truth table, 0 is off and 1 is on.
Appendix D Function Blocks Command Reference User Mode Switch Function Block Timing Chart Input 1 Input 2 Input 3 Output 1 Output 2 Output 3 Fault Present Idle to RUN External Device Monitoring (EDM) 2 seconds 2 seconds 2 seconds Figure 60 - External Device Monitoring Function Block Diagram EDM Feedback ! Monitored Input EDM Error Output 1 EDM Feedback Monitored Input Output 2 Default Connections ! EDM Error Output 1 Output 2 Fault Present ! Maximum I/O for EDM Function The External Device
Function Blocks Command Reference Appendix D Block Properties dialog box in the Logic Editor of RSNetWorx for DeviceNet software. • EDM error • Output 2 EDM Function Block Fault Present Output Setting The Fault Present output can also be used in programming. To enable this output, check the Use Fault Present checkbox on the Out point tab of the Function Block Properties dialog box. EDM Function Block Parameter Set this parameter for the EDM function block.
Appendix D Function Blocks Command Reference EDM Function Block Timing Chart Monitored Input EDM Feedback Output 1 Output 2 EDM Error Fault Present Idle to Run Muting TEDM TEDM TEDM TEDM TEDM Figure 61 - Muting Function Block Diagrams AOPD Input 1 (NC) AOPD Input 2 (NC) Override Input 1 (NC) Override Input 2 (NC) AOPD Input 1 (NC) AOPD Input 2 (NC) Muting Signal 11 S11 Muting Signal 12 S12 Muting Signal 11 Muting Signal 12 Muting Signal 21 Muting Signal 22 Default Connections ! ! ! ! ! Out
Function Blocks Command Reference Appendix D Muting Function Block Parameters Set these parameters for the two-hand control function block. Table 28 - Muting Function Block Parameters Parameter Settings/Range Default Muting Mode ·Parallel muting with 2 sensors This pattern is suitable for applications at a conveyor entrance. Use this pattern when two retro-reflective photoelectric sensors are set up as muting sensors with intersecting detection zones.
Appendix D Function Blocks Command Reference Muting Function Block Fault Present Output Setting The Fault Present output can also be used in programming. To enable this output, check the Use Fault Present checkbox on the In/Out Setting tab of the Function Block Properties dialog box. Muting Function Block Error Handling Use this table to diagnose and reset error conditions in the Muting function block.
Function Blocks Command Reference Appendix D • while the muting sensors are off, two muting sensors detect an object in the correct sequence. • while the muting sensors are off, the synchronization times of the two muting sensors are within the normal range (not including the position detection setting). If an error occurs, an alarm output is generated. The sequence error signal goes on if there is an invalid sequence.
Appendix D Function Blocks Command Reference Figure 62 - Application Setup Sensor 12 Workpiece L Light Curtain Reflected Board V Reflected Board Sensor 11 D1 = d1 Sensor 12 is connected to Muting Signal 12. Sensor 11 is connected to Muting Signal 11. Muting Sequence In this example, the muting sequence is described below. 1. The light is not interrupted between sensors 11 and 12 and the light curtain, so the Output Enable signal is on. 2.
Function Blocks Command Reference Appendix D For the muting function to operate effectively, both formulas must be satisfied.
Appendix D Function Blocks Command Reference Figure 65 - Sequence Error AOPD Input 1 (NC) AOPD Input 2 (NC) Muting Signal 11 Muting Signal 12 Output Enable Muting Sequence Error Fault Present Example: Sequential Muting with Four Sensors (forward direction) In this example, four through-beam photoelectric sensors are set up as the muting sensors with intersecting detection zones.
Function Blocks Command Reference Appendix D Muting Sequence The muting sequence for this example is described below. 1. The light is not interrupted between sensors 11, 12, 21, and 22 and the light curtain, so the Output Enable signal is on. 2. As the workpiece moves to the right and sensors 11 and 12 go on in order, muting is enabled and the muting signal turns on. 3. As the workpiece continues to advance, the Output Enable signal is kept on even if the light curtain is obstructed. 4.
Appendix D Function Blocks Command Reference Sequential Muting (forward direction) Timing Chart Figure 67 - Normal Operation AOPD Input 1 (NC) AOPD Input 2 (NC) Muting Signal 11 Muting Signal 12 Muting Signal 21 Muting Signal 22 Output Enable Muting Fault Present Idle to Run Muting Time Synchronization Time Example: Sequential Muting with Four Sensors (both directions) In this example, four through-beam photoelectric sensors are set up as the muting sensors with intersecting detection zones.
Function Blocks Command Reference Appendix D Figure 68 - Application Setup Entrance Light Curtain Workpiece Sensor 11 Sensor 12 Sensor 21 Sensor 22 Sensor 11 Sensor 12 Sensor 21 Sensor 22 V L d2 D2 D3 Exit Light Curtain Sensor 11 Sensor 12 Sensor 21 Sensor 22 V Sensor 11 Sensor 12 Sensor 21 Workpiece Sensor 22 L d2 D2 D3 Sensor 11 is connected to Muting Signal 11. Sensor 12 is connected to Muting Signal 12. Sensor 21 is connected to Muting Signal 21.
Appendix D Function Blocks Command Reference Distance Settings When setting up this type of muting application, the distance settings must prevent a passing person from enabling the muting function, and the light curtain and muting sensors must be set up so that a workpiece passes by all of the muting sensors before the next workpiece arrives at the muting sensors.
Function Blocks Command Reference Appendix D Figure 70 - Time-difference Input Pattern 2: Exit Timing Chart AOPD Input 1 (NC) AOPD Input 2 (NC) Muting Signal 11 Muting Signal 12 Muting Signal 21 Muting Signal 22 Output Enable Muting Synchronization Time Muting Time Example: Position Detection In this example application, the workpiece is mounted on a machine turntable surrounded by a guard fence.
Appendix D Function Blocks Command Reference Configure the local input in the controller as dual channel complementary. Program Example Limit switches 1 and 2 connect to muting signal 11 of the muting function block using an Estop instruction. Limit switches 1 and 2 are set to dual channel complementary setting for local inputs to evaluate the input data from the two switches. Figure 72 - Program Logic Muting Sequence The muting sequence for this example is described below. 1.
Function Blocks Command Reference Appendix D Timing Chart Figure 73 - Normal Operation AOPD Input 1 (NC) AOPD Input 2 (NC) Muting Signal 11 Output Enable Muting Muting Time Example: Override Function The override function can turn on the safety output even though the lightinterruption signal of the light curtain is inactive. If a workpiece gets jammed during transit, the system cannot be returned to normal operation without forcibly removing the workpiece.
Appendix D Function Blocks Command Reference Override Sequence The override sequence in this example is described below. 1. The Output Enable signal is off. 2. When the override inputs turn on, the override function starts and the overriding signal turns on. As long as the override inputs are on, the muting status is forcibly enabled, and both the muting and Output Enable signals are on. 3.
Function Blocks Command Reference Appendix D Timing Chart The muting mode in the following charts is parallel muting with 2 sensors.
Appendix D Function Blocks Command Reference Figure 77 - Override Timeout During Override AOPD Input 1 (NC) AOPD Input 2 (NC) Override Input 1 (NO) Muting Signal 11 Muting Signal 12 Output Enable Muting Status Override Sequence Sequence Error Fault Present Max.
Function Blocks Command Reference Appendix D Enable Switch Function Block Parameters Set these parameters for the Enable Switch function block. Table 30 - Enable Switch Function Block Parameters Parameter Valid Range Default Setting Input Type Single Channel Dual Channel Equivalent Dual Channel Equivalent Discrepancy Time 0…30 s in 10 ms increments.(1) The discrepancy time must be equal to or greater than the cycle time of the controller.
Appendix D Function Blocks Command Reference Enable Switch Function Block Error Handling Use this table to diagnose and reset a discrepancy error in the Enable Switch function block. Table 31 - Error Detection and Reset for Enable Switch Function Block Error Condition Discrepancy error at input pair Status When an Error Occurs Output Enable OFF (safety state) Fault Present ON To Reset the Error Condition Error Output Discrepancy Error: ON Remove the cause of the error, then either: 1.
Function Blocks Command Reference Pulse Generator Appendix D Figure 81 - Pulse Generator Function Block Diagram Input Output Enable On Pulse Time: 500 ms The Pulse Generator function block generates an On/Off pulse output at the output enable signal while the function block’s input signal is on. The pulse’s on-time and off-time can be set independently between 10 ms and 3 seconds in 10 ms increments.
Appendix D Counter Function Blocks Command Reference Figure 83 - Counter Function Block Diagram Input Output Enable Reset The counter function block counts the input pulses at an input and turns on the Output Enable signal when the count reaches a preset value. You set this value by using RSNetWorx for DeviceNet software. When the input count reaches the preset value, the Output Enable signal turns on and is held on.
Function Blocks Command Reference Appendix D Count Type The count type can be set to down counter (decrementing) or up counter (incrementing). With a down counter, the preset value is the counter’s initial value and the counter decrements by one count each time an input pulse is detected. The Output Enable signal turns on when the count reaches zero. This function block’s preset value is stored in the function block’s internal work area, and can be monitored from a programming device.
Appendix D Function Blocks Command Reference Figure 86 - Manual Reset Up Counter Input 1 Input 2 Preset Value Count Output 1 Idle to Run Figure 87 - Manual Reset Down Counter Input 1 Input 2 Preset Value Count Output 1 Idle to Run 260 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Appendix E Explicit Messages Introduction Receiving Explicit Messages Topic Page Receiving Explicit Messages 261 Send Explicit Messages 264 Accessing Controller Parameters By Using DeviceNet Explicit Messages 265 Sending an explicit message from a standard DeviceNet master to the SmartGuard controller enables reading or writing any specified data or parameters of the SmartGuard controller. The controller performs according to a command sent from the master and returns a response.
Appendix E Explicit Messages The Instance ID is dependent upon the type of message. Table 34 - Instance ID Values Explicit Message Type Service Instance ID Read Local Input Area Read 0001 (hex) Read Local Output Area Read 0002 (hex) Read Safety Remote Input Area Read 0005 (hex) Read Safety Remote Output Area Read 0006 (hex) The command data includes the offset size, and data size. The offset size specifies the address from which to start reading.
Explicit Messages Appendix E Table 37 - Local Outputs and Test Outputs (2 bytes) Offset (bytes) Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Safety Output Terminal Number 7 Safety Output Terminal Number 6 Safety Output Terminal Number 5 Safety Output Terminal Number 4 Safety Output Terminal Number 3 Safety Output Terminal Number 2 Safety Output Terminal Number 1 Safety Output Terminal Number 0 Test Output Terminal Number 3 Test Output Terminal Number 2 Test Output Terminal Number
Appendix E Explicit Messages Send Explicit Messages A SmartGuard controller can send explicit messages from a user application program. User-registered messages are sent over the network when user-specified trigger conditions are met. This can be used to notify monitoring and control devices or as a method for specifying outputs to display devices. Up to 32 bytes of explicit message data can be sent.
Explicit Messages Appendix E Restrictions on Sending Explicit Messages Explicit messages are subject to the following restrictions. • One address can be set in the user program for the trigger address. • The SmartGuard controller’s internal I/O memory is sent as a response to an explicit message. Explicit messages can be sent from a user program in the controller, but internal information in the controller cannot be used as send message data.
Appendix E Explicit Messages Table 42 - Setting and Monitoring Safety Input Terminals Explicit Message Command Service Function Service Code Class ID Instance ID Attribute ID Read Reads the monitor mode of maintenance information for the input (1…16) specified by the Instance ID. 0E hex 3D hex 01 to 10 hex 65 hex Write Writes the monitor mode of maintenance information for the input (1…16) specified by the Instance ID.
Explicit Messages Appendix E Table 42 - Setting and Monitoring Safety Input Terminals Command Explicit Message Service Function Read Safety Input Error Information Cause Read Reads the cause for the 0E hex normal flag of the number (1…16) specified by the Instance ID being off (error).
Appendix E Explicit Messages Table 43 - Setting and Monitoring Safety Output Terminals Command Explicit Message Service Function Service Code Class ID Instance ID Attribute ID Read Monitor Status of Output Total On Time or Contact Operation Counter Read Reads the monitor status of the total on time or contact operation counter for the output (1…8) specified by the Instance ID.
Explicit Messages Appendix E Table 44 - Monitoring Test Output Terminals Explicit Message SV for Test Output Total On Time or Contact Operation Counter Command Service Function Service Code Class ID Read Reads the SV of the total on time or contact operation counter for the input (1…4) specified by the Instance ID. 0E hex 35B hex 01…04 hex Writes the SV of the total on time or contact operation counter for the input (1…4) specified by the Instance ID.
Appendix E Explicit Messages Notes: 270 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Appendix F Application and Configuration Examples Introduction Emergency Stop Application Topic Page Emergency Stop Application 271 Safety Gate Application with Automatic Reset 273 Dual Zone Safety Gate Application Using Emergency Stop Switch with Manual Reset 274 Safety Mat Application 276 Light Curtain Application 279 This example shows a dual channel emergency stop switch with manual reset.
Appendix F Application and Configuration Examples Figure 92 - Configuration Figure 93 - Programming Figure 94 - Timing Diagram Emergency Stop Button Pressed ESTOP 11 and 12 ESTOP 21 and 22 Emergency Stop Button Pressed More than 350 ms More than 350 ms Reset KM1 KM2 EDM Feedback Idle to Run 272 TEDM TEDM Rockwell Automation Publication 1752-UM001E-EN-P - June 2014 TEDM
Application and Configuration Examples Safety Gate Application with Automatic Reset Appendix F This example shows dual channel mode limit switches with automatic reset.
Appendix F Application and Configuration Examples Figure 97 - Programming Figure 98 - Timing Diagram Safety Gate Opened Safety Gate Closed S1 S2 KM1 KM2 EDM Feedback Idle to Run Dual Zone Safety Gate Application Using Emergency Stop Switch with Manual Reset 274 TEDM TEDM This example shows dual channel door switches with automatic reset and a dual channel emergency stop switch with manual reset.
Application and Configuration Examples Appendix F Figure 99 - Wiring Diagram E1 and E2: 24V dc Power Supplies S1: Emergency Stop Push Button S2: Reset Switch S3, S4, S5, and S6: Safety Limit Switch KM1, KM2, KM3, and KM4: Contactors S5 S3 S6 S4 KM1 S1 11 21 S2 12 22 KM2 I0 I2 I4 I6 I8 I10 I12 I14 I1 I3 I5 I7 I9 I11 I13 I15 KM3-NC M KM1-NC V1 G1 T0 T2 O0 O2 O4 O6 V2 G2 T1 T3 O1 O3 O5 O7 KM2-NC KM3 KM4 E2 E1 KM4-NC KM1 KM2 KM3 KM4 M Connect a 24V dc power s
Appendix F Application and Configuration Examples Figure 101 - Programming Figure 102 - Timing Diagram 350 ms min.
Application and Configuration Examples Appendix F Figure 103 - Wiring Diagram Black White MSR30RT/RTP + - MatGuard Mats S11 S21 S34 A1 Power Supply Control Circuit 14 A1 S12 A2 S22 Y2 14 24 24 Y32 Y32 White Black S2 E1 and E2: 24V dc Power Supplies S1: Reset Switch S2: Emergency Stop Push Button KM1 and KM2: Contactors I0 I2 I4 I6 I8 I10 I12 I14 I1 I3 I5 I7 I9 I11 I13 I15 V1 G1 T0 T2 O0 O2 O4 O6 V2 G2 T1 T3 O1 O3 O5 O7 S1 KM2 KM2-NC M E2 E1 KM1-NC K
Appendix F Application and Configuration Examples Figure 105 - Programming Figure 106 - Timing Diagram Emergency Stop Button (ESTOP) Pressed 350 ms min. 350 ms min.
Application and Configuration Examples Appendix F This example shows a dual channel safety light curtain with manual reset and dual channel emergency stop switch with manual reset.
Appendix F Application and Configuration Examples Figure 108 - Configuration Figure 109 - Programming 280 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Application and Configuration Examples Appendix F Figure 110 - Timing Diagram Emergency Stop Button (ESTOP) Pressed 350 ms min. 350 ms min.
Appendix F Application and Configuration Examples Notes: 282 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
Glossary The following terms and abbreviations are used throughout this manual. For definitions of terms not listed here, refer to the Allen-Bradley Industrial Automation Glossary, publication AG-7.1. assembly Internal data in a device gathered as one group to be accessed externally. busoff Status that occurs when the error rate is extremely high over a communication cable. An error is detected when the internal error counter exceeds a threshold value.
Glossary polled A type of standard I/O data communication in which a polled message solicits a response from a single, specified device on the network (a point-to-point transfer of data). probability of failure on demand The average probability of an operational system to fail to perform its design (PFD) function on demand. probability of failure per hour (PFH) The probability of an operational system to have a dangerous failure occur per hour.
Index A alphanumeric display identify errors 199 B baud rate see communication rate BOOTP set the IP address 51 use the Rockwell Utility 52 bridge 56 C CIP Safety I/O configuration signature 44 communication rate reset 46 configuration DeviceNet Safety target nodes 44 reset 46 safety parameters 78 standard parameters 79 verify 161-167 configuration signature 44 comparison 166 components 45 definition 44 mismatch 162 configure a driver 41, 50 connection reaction time limit 81 and network delay multiplier 8
Index missing device icon 162 multicast connections 80 muting lamp status data 177 N Network bridge 56 network delay multiplier 82 network status indicator flashing 196 node address 42 changes 65 reset 46 select 25 node commissioning 42-43 tool 42 O off-delay 67 on-delay 67 online button 160 output connection owners reset 46 overcurrent detection outputs 73 pulse test sources 71 P parameters tab 79 password protected operations 47 reset 46 set or change 47 valid characters 47 point-to-point 80 pulse tes
Index unknown device icon 162 upload and compare Safety Device Verification Wizard 164 V verification reports failure report 165 Safety Device Verification Wizard 165 verify DeviceNet Safety configuration 161-167 FAILED 164 select devices 163 verify failed 163 verify not supported 163 W welcome page 161 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014 287
Index 288 Rockwell Automation Publication 1752-UM001E-EN-P - June 2014
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 and application notes, sample code, and links to software service packs. You can also visit our Support Center at https://rockwellautomation.custhelp.com/ for software updates, support chats and forums, technical information, FAQs, and to sign up for product notification updates.
