732E EtherNet/IP ArmorBlock Supporting Sequence of Events Catalog Number 1732E-IB16M12SOEDR User Manual
Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Table of Contents Preface Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Common Techniques Used in this Manual. . . . . . . . . . . . . . . . . . . . . . vi Chapter 1 About 1732E ArmorBlock Modules Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Module Features. . . . . . . . . . . . . . . . . . . .
Table of Contents ii Chapter 5 Configure the Module for Your EtherNet/IP Network Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Gateway Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Subnet Mask. . . . . . .
Table of Contents iii Producer/Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Status Indicator Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Agency Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter 8 Using the Module Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents iv Connecting to an Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . 90 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Ethernet Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Duplicate IP address Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Configure Ethernet Communications on the ArmorBlock module . . 91 Configure Using RSLogix 5000 Software .
Preface Read this preface to familiarize yourself with the rest of the manual. It provides information concerning: • • • • Who Should Use this Manual who should use this manual the purpose of this manual related documentation conventions used in this manual Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use 1732 ArmorBlock EtherNet/IP with Diagnostics and CIPSync modules.
vi Preface Related Documentation The following documents contain additional information concerning Rockwell Automation products. To obtain a copy, contact your local Rockwell Automation office or distributor. Resource Description 1732 Ethernet/IP 16 Point ArmorBlock I/O Wiring Diagram, publication 1732E-WD001 Information on wiring the ArmorBlock EtherNet/IP module.
Chapter 1 About 1732E ArmorBlock Modules Overview Module Features This chapter is an overview of the 1732E ArmorBlock family of modules. You will need to understand the concepts discussed in this chapter to configure your module and use it in an EtherNet/IP control system. The following table lists where to find specific information in this chapter.
2 About 1732E ArmorBlock Modules Contact Rockwell Automation if you need software or firmware upgrades to use this equipment. Product Firmware Version / Software Release 1732E-IB16M12SOEDR Firmware rev. 1.6 or later 1756-EN2T or 1756-EN2TR module 2.3 (or later version of major revision 2) when using RSLogix 5000 v17 3.x version when using RSLogix 5000 v18 or later RSLogix 5000 software 17 or later RSLinx software 2.
About 1732E ArmorBlock Modules Specify the Requested Packet Interval (RPI) 3 The Requested Packet Interval (RPI) is the update rate specified for a particular piece of data on the network. This value specifies how often to produce the data for that device. For example, if you specify an RPI of 50 ms, it means that every 50 ms the device sends its data to the controller or the controller sends its data to the device. RPIs are only used for devices that exchange data.
4 About 1732E ArmorBlock Modules Notes: Publication 1732E-UM002A-EN-P - March 2010
2 Module Overview Overview EtherNet/IP Network Overview This chapter provides an overview of the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module. The module uses CIP Sync functionality to provide time stamping when an input event occurs.
6 Module Overview If the ring topology is used, theRing Master (not the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events) must be designated in the system, and it will determine the beacon rate and the timeout period. For more information on topologies, refer to publication ENET-AP005. The 1732E-IB16M12SOEDR module is a CIP Sync slave only device. There must be another module on the network that will function as a master clock.
Module Overview 7 CIP Sync Support CIP Sync supports the IEEE 1588-2008 synchronization standard. In this architecture, a grandmaster clock provides a master time reference for the system time. The 1732E-IB16M12SOEDR module is a CIP Sync slave only device. There must be another module on the network that will function as a master clock. The grandmaster could be: • a 1756 ControlLogix L6 or L7controller when using RSLogix 5000 software V18 or later.
8 Module Overview Introduction to Sequence of Events modules The 1732E-IB16M12SOEDR is an input module that offers sub-millisecond timestamping on a per point basis in addition to providing the basic ON/OFF detection. All input point event times are recorded and returned in a single buffer. The module returns two 64-bit timestamps for each input point, thus allowing: • ON and OFF events for each point to be displayed simultaneously in the input data.
Module Overview 9 High Performance Sequence of Events Applications in the Logix Architecture Sequence of Events (SOE) applications span a wide range of industry applications. Typically any event that needs to be compared against a second event can be classified as SOE.
10 Module Overview Common Time base for Alarming System logs user interaction as well as alarm events using common time reference. The power industry requires sub 1 ms accuracy on first fault across geographically dispersed architecture. High Speed Applications Packaging machines or sorters that have fast part cycles are often bottlenecked by controller scan times. By switching to a time based solution, you can remove many scan time critical components of the system.
3 Use the Module in an ArmorBlock System Introduction Differences Between Module and Standard I/O This chapter describes how the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module operates in an ArmorBlock system. Topic Page Differences Between Module and Standard I/O 11 Similar Functionality to Standard ArmorBlock 11 In many aspects, the module behaves the same as other ArmorBlock digital input modules.
12 Use the Module in an ArmorBlock System standard EtherNet/IP ArmorBlock I/O modules. In addition to the common features described in Chapter 1, the following table describes the similarities. Concept Description Ownership Every module in the ArmorBlock system must be owned by a Logix5000 controller. This owner-controller: • stores configuration data for every module that it owns. • sends the module configuration data to define the module’s behavior and begin operation with the control system.
Chapter 4 Install Your Module Overview This chapter shows you how to install and wire the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events. The only tools you require are a flat or Phillips head screwdriver and drill. Mount the Module To mount the module on a wall or panel, use the screw holes provided in the module. Refer to the drilling dimensions illustration to guide you in mounting the module. 43.25 mm (1.70 in.) 26.5 mm (1.04 in.) 65 mm (2.56 in.) 32.5 mm (1.28 in.) 179 mm (7.05 in.
14 Install Your Module Wire the Module The ArmorBlock EtherNet/IP family has 5-pin micro-style I/O connectors. We provide caps to cover the unused connectors on your module. Connect the quick-disconnect cord sets you selected for your module to the appropriate ports. I/O Connectors Refer to the pinout diagrams for the I/O connectors.
Install Your Module 15 Auxiliary Power Cable Attach the mini-style 4-pin connector to the mini-style 4-pin receptacle as shown below. Mini-style 4-Pin Male Receptacle 4 2 3 1 (View into receptacle) Pin 1 NC Pin 2 Sensor/MDL power+ Pin 3 Sensor/MDL powerPin 4 NC 44809 Auxiliary Power is based on a 4-pin connector system and is used to provide 24V DC power to I/O modules and other devices. Pins 3 and 4 are connected inside the module.
16 Install Your Module Notes: Publication 1732E-UM002A-EN-P - March 2010
5 Configure the Module for Your EtherNet/IP Network Introduction Before using the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events in an EtherNet/IP network, configure it with an IP address, subnet mask, and optional Gateway address. This chapter describes these configuration requirements and the procedures for providing them. Here are the ways you can do this: • Use the Rockwell BootP/DHCP utility, version 2.3 or greater, that ships with RSLogix 5000 or RSLinx software.
18 Configure the Module for Your EtherNet/IP Network If the module needs to be reset to factory defaults, set the switches on the module to the value 888 and then cycle power to the module. IMPORTANT If using the BootP/DHCP utility, you will need to know the Ethernet hardware address of your module. Rockwell assigns each module a unique 48-bit hardware address at the factory. The address is printed on a label on the side of your module. It consists of six hexadecimal digits separated by colons.
Configure the Module for Your EtherNet/IP Network 19 IP addresses are written as four decimal integers (0...255) separated by periods where each integer gives the value of one byte of the IP address. EXAMPLE For example, the 32-bit IP address: 10000000 00000001 00000000 00000001 is written as 128.1.0.1. Gateway Address This section applies to multi-network systems. If you have a single network system, skip to the next section. The gateway address is the default address of a network.
20 Configure the Module for Your EtherNet/IP Network Subnet Mask The subnet mask is used for splitting IP networks into a series of subgroups, or subnets. The mask is a binary pattern that is matched up with the IP address to turn part of the Host ID address field into a field for subnets. Take Network 2 (a Class B network) in the previous example and add another network.
Configure the Module for Your EtherNet/IP Network Set the Network Address 21 The I/O block ships with the rotary switches set to 999 and DHCP enabled. To change the network address, you can do one of the following: 1. Adjust the switches on the front of the module. 2. Use a Dynamic Host Configuration Protocol (DHCP) server, such as Rockwell Automation BootP/DHCP. 3. Retrieve the IP address from nonvolatile memory.
22 Configure the Module for Your EtherNet/IP Network installation CD. The module must have DHCP enabled (factory default and the network address switches set to an illegal value) to use the utility. To configure your module using the BootP/DHCP utility, perform the following steps: 1. Run the BootP/DHCP software. The BOOTP/DHCP Request History dialog appears showing the hardware addresses of devices issuing BootP/DHCP requests. 2. Double-click the hardware address of the device you want to configure.
Configure the Module for Your EtherNet/IP Network 23 The device is added to the Relation List, displaying the Ethernet Address (MAC) and corresponding IP Address, Hostname and Description (if applicable). When the IP address assignment is made, the address displays in the IP Address column in the Request History section. 4. To assign this configuration to the device, highlight the device in the Relation List panel and click Disable BOOTP/DHCP.
24 Configure the Module for Your EtherNet/IP Network Save the Relation List You can save the Relation List to use later. To save the Relation List do the following: 1. Select Save As... from the File menu. The Save As dialog box appears. 2. Select the folder you want to save the list to. 3. Enter a file name for the Relation List (for example, control system configuration) and click Save. If you want to see your saved file names in the Open dialog box, save your files using the default file type (*.
Configure the Module for Your EtherNet/IP Network 25 allows for dynamic allocation of network addresses and configurations to newly attached devices. Be aware that a DHCP server typically assigns a finite lease time to the offered IP address. When 50 percent of the leased time has expired, the module will attempt to renew its IP address with the DHCP server. The module could be assigned a different IP address, which would cause communicating with the ControlLogix controller to cease.
26 Configure the Module for Your EtherNet/IP Network Notes: Publication 1732E-UM002A-EN-P - March 2010
Chapter 6 Configure the Module Using RSLogix 5000 Introduction 27 This chapter guides you through the steps required to configure your 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events using RSLogix 5000 software. Note that the modules presented in this chapter are configured using RSLogix 5000 software, version 17 or later.
Configure the Module Using RSLogix 5000 Set Up the Hardware In this example, a ControlLogix chassis contains the Logix 5565 processor in slot 1 and a 1756-EN2T bridge module in slot 3. The 1732E ArmorBlock module is mounted remotely. Slot 0 1 2 3 Local Chassis Logix5565 Logix5565 Logix5565 Controller (slot 1) EtherNet/IP 1756-EN2T 28 1732E ArmorBlock Ethernet Module 192.168.1.20 LINK 1 LINK 2 1732E ArmorBlock Data 1756-EN2T 192.168.1.1 (slot 3) Switch 192.168.1.
Configure the Module Using RSLogix 5000 Create the Example Application 29 Perform the following steps to create the example application: 1. Perform the following steps to create the example application: 2. From the File menu, select New. The New Controller dialog opens. 3. Enter an appropriate name for the Controller, for example, ArmorBlock_IO_Controller. 4.
30 Configure the Module Using RSLogix 5000 Configure Your I/O Module You must configure your module upon installation. The module will not work until it has been configured with at least the default configuration. RSLogix 5000 Configuration Software You must use RSLogix 5000, version 17 or later to set configuration for your module. You have the option of accepting default configuration for your module or writing point level configuration specific to your application.
Configure the Module Using RSLogix 5000 31 Add the Local EtherNet/IP Bridge to the I/O Configuration 1. If necessary, go offline. If you are not offline, use this pull-down menu to go offline 2. Add the EtherNet/IP Bridge to your RSLogix 5000 project. A. Right-click on I/O Configuration. B.
32 Configure the Module Using RSLogix 5000 3. When the Select Module dialog appears, expand Communications and select the new module. Select the 1756-EN2T EtherNet/IP Bridge. A. Select the 1756-EN2T EtherNet/IP Bridge. B. Click OK. 4. The Select Major Revision dialog opens. Select Major Revision 2 or later. A. Select the number of major revision. B. Click OK. 5. Configure the bridge. The first screen of the configuration wizard opens. A. Name the bridge. B. Enter the IP address. C.
Configure the Module Using RSLogix 5000 33 Add the 1732E-IB16M12SOEDR as a child of the 1756-EN2T module 1. Right click the Ethernet folder that appears below the 1756-EN2T bridge you added to the I/O Configuration tree and select New Module. 2. When the Select Module dialog appears expand Digital. Select the 1732E-IB16M12SOEDR module. A. Select the 1732E-IB16M12SOEDR module. B. Click OK.
34 Configure the Module Using RSLogix 5000 You can either accept or change the default configuration as shown... A. Name the module. B. Enter the module’s IP address as shown. C. Make sure the Module Definition information matches this example. D. Click Change... to edit the Module Definition for your module before downloading the program to the controller. E. Click OK to accept the default configuration. Use the Default Configuration If you use the default configuration and click on OK, you are done.
Configure the Module Using RSLogix 5000 35 On this dialog, you can: A. Select the module series. B. Make sure the Major and Minor Revision numbers match your module’s revision. C. Choose and Electronic Keying method. For more information, see page 49. D. Select the Connection type. E. Select the Data Format. F. Click OK to return to theGeneral tab of the Module Properties dialog. From the Connection tab, you can: A. Change the RPI. For more information on the RPI, see page 3. B. Inhibit the module.
36 Configure the Module Using RSLogix 5000 This screen is grayed out unless you are online with the controller and module. On this screen, you can: A. Enable or disable external ports. B. Select Auto-negotiate on enabled ports. If Auto-negotiate is disabled then select the correct speed and duplex. C. Click Port Diagnostics to display the Port Diagnostics dialog. D. If you make changes in Step A or Step B then click Set.
Configure the Module Using RSLogix 5000 Download Your Configuration 37 After you write configuration for your module, the module does not use this configuration until you download it to the owner-controller. The download transfers the entire program to the controller, overwriting any existing program. Download module configuration as shown below.: A. Click here to see the pull-down menu. B. Click download.
38 Configure the Module Using RSLogix 5000 The General tab of the Module Properties dialog appears. Click on the tab of the page that you want to view or reconfigure and make any appropriate changes, as shown in the example. A. Click the tab where you need to reconfigure the module. In this example, Timestamp Capture was disabled for several input points. B. When the module is reconfigured, click OK.
Configure the Module Using RSLogix 5000 Configure RSLogix 5000 and the 1756-EN2T Communication Module for CIP Sync 39 If you are using RSLogix 5000 version 17, follow these steps to configure the 1756-EN2T communication module to be the PTP (CIP Sync) master clock. 1. In your web browser, go to the Rockwell Automation Sample Code Library at http://samplecode.rockwellautomation.com/idc/groups/public/docu ments/webassets/sc_home_page.hcst. The Search Our Sample Code Library page appears. 2.
40 Configure the Module Using RSLogix 5000 Notes: Publication 1732E-UM002A-EN-P - March 2010
Chapter 7 Module Features Introduction 41 This chapter describes the features available on 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events. The chapter contains the following main sections:.
42 Module Features Determine Module Compatibility Primarily, this module is used to interface to sensing devices and detect whether they are ON or OFF and to timestamp ON and OFF transitions. The module converts ON/OFF signals from user devices to appropriate logic level for use in the processor.
Module Features 43 Operational Mode The module operates only in Per Point Mode: Per Point Mode The module produces timestamps for up to 2 input transitions per input, one for OFF to ON transitions and another for ON to OFF transitions; these timestamps can occur simultaneously on separate inputs. Timestamp Capture Timestamp Capture instructs the module to timestamp specific input point transitions.
44 Module Features Use the Configuration tab in RSLogix 5000 to set Timestamp Capture, as shown in the example. Click the Configuration tab. • Click on the individual boxes for each input point to Timestamp Capture for that point. • Clear the individual boxes for each input point to disable Timestamp Capture for that point. You can also use these boxes to enable or disable all points simultaneously.
Module Features 45 Input Diagnostics As with other modules with diagnostics, the input connector’s Sensor Source Voltage (SSV), on Pin 1 of the input connectors, is protected from short circuits to ground as well as open wire conditions due to a missing sensor or to a cable disconnection. Short Circuit Protection Each connector with inputs is protected against short circuits to ground. The circuit automatically resets each connector individually and the SSV energizes once the short circuit is removed.
46 Module Features Use the Configuration tab in RSLogix 5000 to enable Open Wire Detection, as shown in the example. • Click on the individual boxes for each input point to enable Open Wire Detection for that point. • Clear the individual boxes for each input point to disable Open Wire Detection for that point. You can also select this box to enable or disable all points simultaneously.
Module Features 47 – At some point while still filtering the input, the input returns to the transitioned state and remains there until the module counts the number of 1 ms intervals equal to the filter setting. In this case, the module sends data from the transition to the controller. – The input does not remain in the transitioned state for a time period equal to the filter setting and the 1 ms counter decrements to zero.
48 Module Features • Scenario #2 – The input turns ON but turns OFF before 2 ms (length of the input filter setting) elapses. In this case, the module continues to scan the input every millisecond. At some point, less than 2 ms later, the input turns ON again and remains for 1 to 2 ms, the third ON sampled 1 ms interval (in this case at 6 ms). In this case, the module considers the transition valid and sends the data timestamped at the original transition to the controller.
Module Features 49 Use the Configuration tab in RSLogix 5000 software to configure Input Filters, as shown in the example below. Type the filter times or use the drop down menu to select the Input Filter Time. The Input Filter Time range is 0, 1, 2, 4, 8 or 16 ms. Communications Format The communications format determines what operational mode your module uses and, consequently, what tags RSLogix 5000 generates when configuration is complete.
50 Module Features When the controller attempts to connect to and configure a module (for example, after program download), the module compares the following parameters before allowing the connection and configuration to be accepted: • • • • Vendor Product Type Product Code Major Revision - Change that affects the module’s function or RSLogix 5000 interface • Minor Revision - Change that does not affect the module’s intended function or RSLogix 5000 interface The comparison is made between the keying inf
Module Features Keying option: Definition: Disable Keying The inserted module attempts to accept a connection to the controller regardless of its type. ATTENTION 51 Be extremely cautious when using the disable keying option; if used incorrectly, this option can lead to personal injury or death, property damage or economic loss. If keying is disabled, a controller makes a connection with most modules of the same type as that used in the configuration.
52 Module Features You can inhibit your module on the Connection tab in RSLogix 5000, as shown in the example. Click on this box to inhibit or uninhibit the module The following table lists features on the module that cannot be configured. This feature: is described on: Module Fault Reporting 52 Fully Software Configurable 52 Producer/Consumer Model 53 Status Indicator Information 53 Module Fault Reporting Your module provides both a hardware and software indication when a module fault occurs.
Module Features 53 You can also use the software to interrogate your module to retrieve: • • • • • • serial number revision information product code vendor identification error/fault information diagnostic counters. By eliminating such tasks as setting hardware switches and jumpers, the software makes module configuration easier and more reliable. Producer/Consumer Model By using the Producer/Consumer model, modules can produce data without having been polled by a controller first.
54 Module Features Notes: Publication 1732E-UM002A-EN-P - March 2010
Chapter 8 Using the Module Introduction Overview This chapter describes how to use the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module. The chapter contains the following main sections:.
56 Using the Module With each timestamped transition, the module stores data for that point. An overview of how the module stores timestamp data is shown in the following figure. How Does the Module Store Timestamp Data? The module is installed, wired to input devices and ready to begin operation. All inputs are configured to timestamp any transition that occurs.
Using the Module 57 3. You copy new data from the controller tags to a separate data structure for later sorting. 4. Acknowledge the timestamp, using output tags, so that the module can capture another timestamp on that input without losing any data. 5. Once the data is copied to a separate data structure, you may sort the data in the controller to determine the order of events. Some of these typical events are described in greater detail in the rest of this chapter.
58 Using the Module IMPORTANT We suggest you monitor the I.EventOverflow bits to make sure you are aware of when transitions were either not timestamped or when timestamp data was overwritten. Use the Configuration tab in RSLogix 5000 to enable Timestamp Latching, as shown in the example. Select this box to enable the Timestamp Latching feature. Deselect the box to disable the feature.
Using the Module 59 Click the Configuration tab. • Select the individual boxes for each input point to enable Timestamp Capture for that point. • Unselect the individual boxes for each input point to disable Timestamp Capture for that point. You can also use these boxes to enable or disable all points simultaneously.
60 Using the Module The module sends all of its input data to the controller the next RPI after an input transition has been timestamped and at each subsequent RPI. You must manage the data coming from the module. Manage the Data The following occurs in the process of the managing data coming from the module: 1. The module sends data to the controller. 2. The controller copies the relevant portions of the input data to separate array. 3.
Using the Module 61 The following table describes the data that is sent for each input. These tags are sent to the controller the next RPI after the module timestamps a transition on any input as well as all other RPIs. For detailed descriptions of the tags, refer to Appendix B. Tag Name Set on a Per Point or Modulewide Basis Description I.Fault Modulewide Indicates if a communication fault has occurred.
62 Using the Module Tag Name Set on a Per Point or Modulewide Basis Description I.EventOverflow Per point Set for an input when the module either: • Does not timestamp a transition on the input – The module has Timestamp Latching enabled and a similar transition has already been timestamped on this input but has not been cleared via the O.EventAck and O.NewDataAck output tags (see page 82).
Using the Module 63 Copy Relevant Input Data to a Separate Data Structure When the module sends input data to the controller, the data is stored in the controller tags. We recommend you use a COP or CPS instruction to programmatically copy new timestamp data from the controller tags to a separate array in the controller’s memory.
64 Using the Module structure is then moved to another array used to sort the data. In this example, 32 bits of each 64-bit timestamp are moved to the new array. Acknowledge Timestamp Latching Timestamp Data In most cases, Timestamp Latching is enabled.
Using the Module 65 b. Change the NewDataAck output tag (O.NewDataAck.x) to a rising edge (set the tag =1). This tag determines which inputs will be cleared (acknowledged). There are 16 bits (x = 0…15) that can be transitioned; each corresponding to an input. More than one bit can be transitioned at the same time. • If the bit = 0, change the bit to 1. • If the bit = 1, change the bit to 0, wait for at least one RPI, and change the bit to 1. The corresponding I.EventOverflow and I.
66 Using the Module • O.NewDataAck.2 = 1 1732E-IB16M12SOEDR 1. Input 2 transitions from OFF to ON. 2. Module timestamps the transition. ControlLogix controller 3. Module sends input data to the controller. I.Fault I.Data I.OpenWire I.ShortCircuit I.NewData I.EventOverflow I.EventNumber I.LocalClockOffset I.OffsetTimeStamp I.GrandMasterClockID I.Timestamp[16].OffOn[2] I.Timestamp[16].OnOff[2] I.SyncedToMaster Controller tags 4. Controller copies relevant data from controller tags to a separate array.
Using the Module Clear All Data From the Module’s Buffer At Once 67 If necessary, you can reset the events in the module, in effect clearing all data from previously timestamped transitions. In other words, when all data is cleared from the module’s buffers, all of the module’s input tags return to 0. To reset events in the module’s buffer, transition the O.ResetEvents tag to 1 as described below: • If the bit = 0, change the bit to 1.
68 Using the Module Timestamp Accuracy = +/- 40 µs.(1) Module Input Pin OFF->ON to Timestamp (Hardware + Firmware) Delay (µs) Ambient Temp ºC -20 25 60 10V DC 23 24 25 24V DC 18 19 19 30V DC 18 19 19 Voltage Module Input Pin ON->OFF to Timestamp (Hardware + Firmware) Delay (µs) Ambient Temp ºC -20 25 60 10V DC 59 75 84 24V DC 70 84 93 30V DC 71 85 94 Voltage Maximum input frequency (for each input) = 250 Hz 50% duty cycle.
Chapter 9 Interpret Status Indicators Introduction This chapter contains information about status indicators. This module has the following indicators: • Network, Module, and Link status indicators for EtherNet/IP • Auxiliary Power indicator • Individual I/O status indicators for inputs.
70 Interpret Status Indicators Indicator Status for Module Status Network status Off Network link status The device is not initialized or the module does not have an IP address. Flashing green The device has an IP address, but no CIP connections are established. Green The device is online, has an IP address, and CIP connections are established. Flashing red One or more connections have timed out. Red The module has detected that its IP address is already in use. Off No link established.
Chapter 10 Troubleshoot the Module Introduction This chapter describes how to troubleshoot the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events using RSLogix 5000. Troubleshoot the Module In addition to the Status Indicators on the module, RSLogix 5000 alerts you to fault and other conditions in one of three ways: • Warning signal on the main screen next to the module – This occurs when the connection to the module is broken.
72 Troubleshoot the Module • Notification in the Tag Monitor - General module faults are also reported in the Tag Monitor. Communication faults are reported in the input tags. OpenWire, ShortCircuit and EventOverflow faults are also reported in the input tag. RSLogix 5000 software generates 1s in response to a module communication fault. In this example, a communication fault occurred between the controller and the module, so the controller automatically writes 1s for all bits in the word.
Appendix A ArmorBlock 2 Port Ethernet Module Specifications Specifications ArmorBlock 2 Port Ethernet Module Input Specifications – 1732E-IB16M12SOEDR 73 Attributes Value Number of inputs 16 Input type Sink, 24V DC Voltage, off-state input, max 5V DC Voltage, on-state input, max 30V DC Voltage, on-state input, nom 24V DC Voltage, on-state input, min 11V DC Current, off-state input, max 1.
74 ArmorBlock 2 Port Ethernet Module Specifications ArmorBlock 2 Port Ethernet Module Input Specifications – 1732E-IB16M12SOEDR Attributes Value CIP Sync (PTP) clock Transparent clock, and slave only ordinary clock Status indicators Module Status - red/green Network Status - red/green Link Status - green/yellow Auxiliary Power - green I/O Status - yellow/red Dimensions (HxWxD), approx. 179 x 65 x 43.25 mm (7.05 x 2.56 x 1.70 in.) Weight, approx. 0.34 kg (0.
ArmorBlock 2 Port Ethernet Module Specifications 75 Environmental Specifications Attribute Value EFT/B immunity IEC 61000-4-4: ±4 kV @ 5 kHz on power ports ±3 kV @ 5 kHz on signal ports ±3 kV @ 5 kHz on communications ports Surge transient immunity IEC 61000-4-5: ±1 kV line-line(DM) and ±2 kV line-earth(CM) on power ports ±1 kV line-line(DM) and ±2 kV line-earth(CM) on signal ports ±2 kV line-earth(CM) on communications ports Conducted RF immunity IEC 61000-4-6: 10V rms with 1 kHz sine-wave 80% AM
76 ArmorBlock 2 Port Ethernet Module Specifications Notes: Publication 1732E-UM002A-EN-P - March 2010
Appendix B Module Tags Fault and Status Reporting Between the Module and Controllers The 1732E-IB16M12SOEDR sends fault/status data to the owner-controller. The module maintains a Module Fault Word, the highest level of fault reporting. The following table describes the tag that can be examined in ladder logic to indicate when a fault has occurred for your module: Tag Description Module Fault Word This word provides fault summary reporting. It’s tag name is Fault.
78 Module Tags Tags Used Configuration Tags The following table describes the configuration tags generated in RSLogix 5000 when you use your module. Configuration Tags Tag Name Type Description C.FilterOffOn INT Sets the OFF to ON filter time for all 16 inputs. Times are set in μs increments of 0, 1000 (default), 2000, 4000, 8000 and 16000 μs. 0 = no filtering For more information on Software Configurable Input Filters, see page 46. C.
Module Tags 79 Configuration Tags Tag Name Type Description C.CaptureOffOn.x INT Enables capturing OFF to ON events on a per point basis. If disabled (0), that point will not record timestamp data for OFF to ON input transitions. 0 = Capture disabled for OFF to ON input transitions 1 = Capture enabled (default) for OFF to ON input transitions This option is useful if you want to avoid reporting data on the module for events in which you have no interest. C.CaptureOnOff.
80 Module Tags Input Tags Tag Name Type Set on Per Description Point or Modulewide basis I.PtXX_YYShortCircuit BOOL Per point XX = even numbered input 0…14 YY = odd numbered input 1…15 A Short Circuit condition exists per I/O connector. For example, 00_01 or 14_15 0 = no fault 1 = short circuit For more information on Short Circuit Protection, see page 45. I.NewData INT Per point(1) Flag indicating if new timestamp data was detected on the input.
Module Tags 81 Input Tags Tag Name Type Set on Per Description Point or Modulewide basis I.OffsetTimeStamp DINT[2] Modulewide The time when the PTP message was received to cause the Local Clock Offset to update. This value is initially zero. The first timestamp occurs when the module synchronizes with the Grandmaster clock. I.GrandMasterClockID DINT[2] I.Timestamp[16].OffOn[2] DINT[2] Modulewide The I.D. number of the Grandmaster clock that the module is synchronized to.
82 Module Tags Output Tags The following table describes the output tags generated in RSLogix 5000. Output Tags Tag Name Type Description O.EventAck DINT For the bits selected in the O.NewDataAck tag, this tag selects which edge to acknowledge, On to Off, Off to On or both. 0 = acknowledging an ON to OFF event 1 = acknowledging an OFF to ON event 2 = acknowledging both ON to OFF and OFF to ON events The O.NewDataAck tag must also be used to acknowledge the event(s). O.NewDataAck.x INT Allows I.
Appendix C 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables Communicate with Your Module Read this section for information about how to communicate with your module. I/O messages are sent to (consumed) and received from (produced) the ArmorBlock I/O modules. These messages are mapped into the processor’s or scanner’s memory. The following table lists the assembly instances and connection points for the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events.
84 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables Produced Assembly Instance 118 88-95 IN 3 Off-On Time Stamp (64 bit) 96-103 IN 3 On-Off Time Stamp (64 bit) 104-111 IN 4 Off-On Time Stamp (64 bit) 112-119 IN 4 On-Off Time Stamp (64 bit) 120-127 IN 5 Off-On Time Stamp (64 bit) 128-135 IN 5 On-Off Time Stamp (64 bit) 136-143 IN 6 Off-On Time Stamp (64 bit) 144-151 IN 6 On-Off Time Stamp (64 bit) 152-159 IN 7 Off-On Time Stamp (64 bit) 160-167 IN 7 On-Off Time Stam
1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables 85 Produced Assembly Instance 118 272-279 IN 14 On-Off Time Stamp (64 bit) 280-287 IN 15 Off-On Time Stamp (64 bit) 288-295 IN 15 On-Off Time Stamp (64 bit) 296 Reserved Synced to Master Where: INOW = Input Open Wire INSC = Input Short Circuit NewData = New data, has been detected upon that input and an unread event is queued for that point. EventOV = Set whenever the module begins to lose events for that input pint.
86 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables All data listed in this assembly is in Little Endian format, LSB first, in increasing byte order to MSByte last.
1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables 87 Configuration Assembly Instance 110 16 Input / Status / CIP Sync Byte Bit 7 Bit 6 Bit 5 0 Bit 4 Bit 3 Bit 2 Reserved Reserved 2 Reserved 3 Reserved 4 Group 0 Input OFF_ON Delay Filter (Low Byte) 5 Group 0 Input OFF_ON Delay Filter (High Byte) 6 Group 0 Input ON_OFF Delay Filter (Low Byte) 7 Group 0 Input ON_OFF Delay Filter (High Byte) Enable IN OW 7 Enable IN OW 6 Enable IN OW 5 Enable IN OW 4 Bit 0 CRN 1
88 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables Notes: Publication 1732E-UM002A-EN-P - March 2010
Appendix D Connect to Networks via Ethernet Interface This appendix: • • • • • ArmorBlock Module and Ethernet Communication describes ArmorBlock module and Ethernet communication. describes Ethernet network connections and media. explains how to establish connections with the ArmorBlock module. lists Ethernet configuration parameters and procedures. describes configuration for subnet masks and gateways.
90 Connect to Networks via Ethernet Interface Ethernet Network Topology Ethernet Hub or Switch to PC Ethernet Card IMPORTANT RJ45 cable with D-coded M12 connector to ArmorBlock module The ArmorBlock module contains two 10/100Base-T, M12-D (4-pin) Ethernet connectors which connect to standard Ethernet hubs or switches via RJ-45 (8-pin) twisted-pair straight-through cable. It can also connect to another ArmorBlock module via a four wire twisted pair straight-through or cross-over cable.
Connect to Networks via Ethernet Interface Ethernet Connections 91 TCP/IP is the mechanism used to transport Ethernet messages. On top of TCP, the Ethernet/IP protocol is required to establish sessions and to send MSG commands. Connections can be initiated by either a client program (RSLinx application) or a processor. The client program or processor must first establish a connection to the ArmorBlock module to enable the ArmorBlock module to receive solicited messages from a client program or processor.
92 Connect to Networks via Ethernet Interface • set the IP address of the module using the modules network address switches. See Connecting to an Ethernet Network on page 90. The configuration parameters are shown in the Configuration Parameters table, and the configuration procedures follow. Configuration Parameters Parameter Description Default Status Hardware Address The ArmorBlock module Ethernet hardware address.
Connect to Networks via Ethernet Interface Configure Using Web Server 93 The 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module includes an embedded web server which allows viewing of module information, TCP/IP configuration, and diagnostic information. For more information on ArmorBlock module embedded web server capability, refer to Appendix E on page 95.
94 Connect to Networks via Ethernet Interface Notes: Publication 1732E-UM002A-EN-P - March 2010
Appendix E 1732E ArmorBlock I/O Embedded Web Server Introduction Rockwell Automation offers enhanced 1732E ArmorBlock I/O for your EtherNet/IP control systems so you can monitor data remotely via web pages. This chapter shows how you can use the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module’s web server.
96 1732E ArmorBlock I/O Embedded Web Server Access the Home Page of the Web Server From your web browser, enter the IP address of the 1732E ArmorBlock I/O module. The module displays its Home page. Specify the IP address of the module in the Address window of your web browser. This is the module’s Home page.
1732E ArmorBlock I/O Embedded Web Server Navigate the 1732E ArmorBlock I/O 97 You navigate the web server’s web pages by using the navigation panel on the left of the screen. There are also tabs across the top you can use to navigate the sections within folders Tabs across the top match the documents within a folder, as shown in the left navigation panel. Click folders to open and close additional levels of information. Click a document to display a web page showing specific information.
98 1732E ArmorBlock I/O Embedded Web Server Notes: Publication 1732E-UM002A-EN-P - March 2010
Glossary The following terms are used throughout this manual. Refer to the Allen-Bradley Industrial Automation Glossary, publication AG-7.1, for a complete guide to Allen-Bradley technical terms. 1588 IEEE1588-2008 is a protocol to synchronize independent clocks running on separate nodes of a distributed measurement and control system to a high degree of accuracy and precision. Provides accurate real-time (Real-World Time) or Universal Coordinated Time (UTC) synchronization.
100 Glossary send a message from the “producing” device in a system to the “consuming” devices. CIP Sync CIP Sync is a CIP implementation of the IEEE 1588 PTP protocol in which devices can bridge the PTP time across backplanes and on to other networks via EtherNet/IP ports. CIP Sync provides accurate real-time (Real-World Time) or Universal Coordinated Time (UTC) synchronization of controllers and devices connected over CIP networks. communication scan A part of the controller’s operating cycle.
Glossary 101 data table The part of processor memory that contains I/O values and files where data is monitored, manipulated, and changed for control purposes. download Data is transferred from a programming or storage device to another device. DNS Domain Name System. A system for converting host names and domain names into IP addresses on the Internet or on local networks that use the TCP/IP protocol. DTE Data Terminal Equipment. Equipment that is attached to a network to send or receive data, or both.
102 Glossary Gateway address The default address of a network or website. It provides a single domain name and point of entry to the site. half-duplex A communication link in which data transmission is limited to one direction at a time. hard disk A storage area in a personal computer that may be used to save processor files and reports for future use. high byte Bits 8...15 of a word. IANA Internet Assigned Numbers Authority.
Glossary 103 I/O Inputs and Outputs. Consists of input and output devices that provide and/or receive data from the controller. jump Change in normal sequence of program execution, by executing an instruction that alters the program counter (sometimes called a branch). In ladder programs a JUMP (JMP) instruction causes execution to jump to a labeled rung. ladder logic A program written in a format resembling a ladder-like diagram. The program is used by a programmable controller to control devices.
104 Glossary MCR Master Control Relay. A mandatory hard-wired relay that can be de-energized by any series-connected emergency stop switch. Whenever the MCR is de-energized, its contacts open to de-energize all application I/O devices. MCU Microcontroller. Microcontroller, an embedded microcomputer which handles most module functionality. Mini A family of sealed 7/8 inch connectors. Larger than the Micro style connector, the contacts are rated for 7...12 A and 600V.
Glossary 105 normally closed Contacts on a relay or switch that are closed when the relay is de-energized or the switch is deactivated; they are open when the relay is energized or the switch is activated. In ladder programming, a symbol that allows logic continuity (flow) if the referenced input is logic “0” when evaluated. normally open Contacts on a relay or switch that are open when the relay is de-energized or the switch is deactivated.
106 Glossary online Describes devices under direct communication. For example, when RSLogix 5000 is monitoring the program file in a controller. operating voltage For inputs, the voltage range needed for the input to be in the On state. For outputs, the allowable range of user-supplied voltage. output device A device, such as a pilot light or a motor starter coil, that is controlled by the controller. PTP Precision Time Protocol.
Glossary 107 protocol The packaging of information that is transmitted across a network. read To acquire data from a storage place. For example, the processor READs information from the input data file to solve the ladder program. relay An electrically operated device that mechanically switches electrical circuits. relay logic A representation of the program or other logic in a form normally used for relays. RPI Requested Packet Interval.
108 Glossary run mode This is an executing mode during which the controller scans or executes the ladder program, monitors input devices, energizes output devices, and acts on enabled I/O forces. rung Ladder logic is comprised of a set of rungs. A rung contains input and output instructions. During Run mode, the inputs on a rung are evaluated to be true or false. If a path of true logic exists, the outputs are made true. If all paths are false, the outputs are made false.
Glossary 109 sinking A term used to describe current flow between an I/O device and controller I/O circuit — typically, a sinking device or circuit provides a path to ground, low, or negative side of power supply. sourcing A term used to describe current flow between an I/O device and controller I/O circuit — typically, a sourcing device or circuit provides a path to the source, high, or positive side of power supply. status The condition of a circuit or system, represented as logic 0 (OFF) or 1 (ON).
110 Glossary recycling and minimize impact on the environment. Manufacturers will be responsible for taking back and recycling equipment. watchdog timer A timer that monitors a cyclical process and is cleared at the conclusion of each cycle. If the watchdog runs past its programmed time period, it causes a fault. workspace The main storage available for programs and data and allocated for working storage. write To copy data to a storage device.
Index Numerics 1588 99 protocol 99 standard 6 1732E ArmorBlock embedded web server 95 modules 1 navigate 97 overview 1 A access AOP help 72 data 95 module data 38 accuracy timestamp 68 acknowledge data 64 timestamp data 64 acknowledged timestamp 58 add module 30 additional data 11 Add-On Profile help 36 address 99 network 92 agency certifications 53 Ambient Temp 68 AOP help 36, 72 AOP help access 72 RSLogix 5000 72 application 99 ArmorBlock system 11 auto negotiation protocol 90 auxiliary power status indi
112 Index configuration process overview 30 Configuration tab 34, 36, 44, 46, 58, 59 configuration tab use 44, 58 configuration tags 78 configure 1732E EtherNet/IP ArmorBlock 27 1756-EN2T 39 ArmorBlock module 91 bridge 32 Ethernet communications 91 I/O 30 input filters 49 IP address 17 module 1, 27, 50 OFF to ON 46 ON to OFF 46 RSLogix 5000 39 subnet mask 17 using RSLogix 5000 92 using web server 93 your module 22 configure for CIP Sync 39 configuring the Ethernet channel 91 connecting to networks via Eth
Index Diagnostic Overview 97 dialog Module Properties 36 Port Diagnostics 72 Disable Keying 51 disabled Timestamp Latch 66 Timestamp Latching 44 DNS 101 download 101 configuration 37 download your configuration 37 DTE 101 duplicate IP address detection 91 Dynamic Host Configuration Protocol 17, 21, 24 dynamic reconfiguration 37 E edge falling 64 rising 64 edit configuration 37 Electronic Keying 35 electronic keying choosing in RSLogix 5000 32 embedded web server 93 1732E Armorblock 95 browser requirements
114 Index half-duplex 102 hard disk 102 hardware set up 28 high byte 102 home page web server 96 how to use 55 how to use 55 I I/O 103 configure 30 connectors 14 data 91 status indicators 69 IANA 102 implementation CIP 7 independent clocks synchronize 6, 99, 106 indicators status 71 information diagnostic 97 inhibiting module 51 INOW 85 input data 2, 8, 38, 43, 44, 56, 63 filter times 46 maximum frequency 68 transition 46, 64 input device 102 Input filters 46 input filters setting filter times in RSLogix
Index MCU 104 message-based protocol 2, 99 Mini 104 minor revision setting in RSLogix 5000 32 mnemonic 104 mode operational 49 Per Point 43 model networking 2 Producer/Consumer 2, 53 modem 104 modes 104 Module 1 module 1 1732E ArmorBlock 1 add new 30 compatibility 1, 42 configure 1, 27 data 95 fault reporting 52 features 1 inhibiting 51 interrogate 53 mount 13 overview 5, 55 reconfigure 38 Sequence of Events 8, 11 status indicators 69 stores data 56 use v using 55 Module Compatibility 42 module data access
116 Index O OFF to ON timestamp data 63 off-delay time 105 offline 105 offset 105 Offset Time Stamp 85 off-state leakage current 105 ON and OFF timestamp 42 on-board buffer 67 on-delay time 105 one-shot 105 online 106 Open Wire Detection enable 36 OpenWire fault 72 operating voltage 106 operation mode 43 operational mode 49 order of events 57, 66 output data 38 output device 106 output tag EventAck 64 Overview 1732E ArmorBlock 1 overview configuration process 30 EtherNet/IP network 5 module 5, 55 stores t
Index redundancy use 29 Related Documentation vi related documentation vi related publications vi relay 107 relay logic 107 relevant timestamp data 63 reserved bit 107 restore 107 retentive data 107 Ring network 89 rising edge 64 timestamp 64 Rockwell BootP/DHCP utility 21 RoHS 107 routes data 20 routine Sort 66 RPI 3, 55, 56, 58, 60, 63, 67, 107 RSLogix 5000 choosing an electronic keying method 32 enabling Diagnostic Latching 36 module data 38 setting input filter times 36 setting the minor revision 32 us
118 Index T tab Configuration 34, 36, 44, 46, 49, 58, 59 Connection 35, 52 General 35 Internet Protocol 72 Network 72 Port Configuration 35 Time Sync 72 tables data 83 TCP/UDP/IP protocol 1 terminal 109 throughput 109 Time Universal Coordinated 7 time stamping 5 time stamping 5, 109 Time Sync tab 72 Timestamp Latching 44 timestamp 7, 47, 55 64-bit 8 accuracy 68 acknowledge 57 acknowledged 58 capture 43 data 11, 44, 56 falling edge 64 individual 7 ON and OFF 42 recorded 7, 47, 48 rising edge 64 transition
Index sinking or sourcing wiring 42 small blade screwdriver 21 Sort routine 63, 66 the module 11 Timestamp Capture 43 using module 55 Timestamp Latching 57 119 Web Server home page 96 web server 96 log in 96 WEEE 109 workspace 110 write 110 W watchdog timer 110 Publication 1732E-UM002A-EN-P - March 2010
120 Index Notes: Publication 1732E-UM002A-EN-P - March 2010
How Are We Doing? Your comments on our technical publications will help us serve you better in the future. Thank you for taking the time to provide us feedback. You can complete this form and mail (or fax) it back to us or email us at RADocumentComments@ra.rockwell.com. Pub. Title/Type 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Cat. No. 1732E-IB16M12SOEDR Pub. No. 1732E-UM002A-EN-P Pub. Date March 2010 Part No. Please complete the sections below.
PLEASE FASTEN HERE (DO NOT STAPLE) PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
141 Publication 1732E-UM002A-EN-P - March 2010
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
