User Manual 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules Catalog Numbers 1732E-IB8M8SOER, 1732E-OB8M8SR
Important User Information Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid-state equipment and hard-wired electromechanical devices.
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 • related documentation • 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 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules.
Common Techniques Used in this Manual iv The following 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. • Italic type is used for emphasis.
Summary of Changes This manual contains new and updated information. Changes throughout this revision are marked by change bars, as shown to the right of this paragraph. New and Updated Information This table contains the changes made to this revision.
vi Summary of Changes Notes: Publication 1732E-UM003B-EN-E - March 2014
Table of Contents Preface Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Common Techniques Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . iv Chapter 1 About ArmorBlock Modules Overview . . . . . . . . . .
viii Table of Contents Set the Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mount the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter Summary and What’s Next . . . . . . . . . . . . .
Table of Contents Producer/Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Indicator Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agency Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix 51 51 51 51 Chapter 8 Specific Features of the Introduction . . . . . . .
x Table of Contents Troubleshoot the Module Troubleshoot the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Determine Fault Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Chapter 12 Interpret Status Indicators Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1 About ArmorBlock Modules Overview This chapter is an overview of the 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 guides you where to find specific information in this chapter.
Chapter 1 About ArmorBlock Modules Product Firmware Version / Software Release 1756-EN2T, 1756-EN2TR, 1756-EN3TR 3.x version when using RSLogix 5000 v18 or later RSLogix 5000 software 18 or later RSLinx software 2.56 or later For a complete ControlLogix compatibility matrix, see publication IA-AT003. Use of the Common Industrial Protocol (CIP) The 1732E-IB8M8SOER and 1732E-OB8M8SR modules use the Common Industrial Protocol (CIP).
About ArmorBlock Modules Chapter 1 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. For example, a ControlLogix EtherNet/IP bridge module in the same chassis as the controller does not require an RPI because it is not a data-producing member of the system; it is used only as a bridge to remote modules.
Chapter 1 About ArmorBlock Modules Notes: 4 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Chapter 2 Module Overview and Features Overview This chapter provides an overview of the 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules, 1732E-IB8M8SOER and 1732E-OB8M8SR. The modules provide timestamping functionality when an input event occurs and allow for scheduling of outputs. Although primarily described in this manual as having CIP Sync functionality, both modules can be configured to function as standard I/O modules.
Chapter 2 Module Overview and Features EtherNet/IP Network Overview Functional Earth ground(1) EtherNet/IP D-Code M12 connector Link 1 status LED Module status LED EtherNet/IP D-Code M12 connector LINK1 LINK2 X10 X100 Node address switches M8 I/O connectors/ status indicators NET MOD Link 2 status LED Network status LED X1 Node address switches M8 I/O connectors Power status indicator Power connector Power connector 45766 (1) Functional Earth grounds the I/O block’s EtherNet/IP communica
Module Overview and Features Chapter 2 If the ring topology is used, the Ring Master (not the 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input or Scheduled Output) must be designated in the system, and determines the beacon rate and the timeout period. For more information on topologies, refer to publication ENET-AP005. The 1732E-IB8M8SOER and 1732E-OB8M8SR modules are CIP Sync slave only devices. There must be another module on the network that functions as a master clock.
Chapter 2 Module Overview and Features only devices. There must be another module on the network that will function as a master clock. The grandmaster could be: • a 1756 ControlLogix L6 or L7 controller when using RSLogix 5000 software v18 or later. • an Ethernet bridge that supports IEEE 1588 V2, or • a Symmetricom Grand Master GPS or equivalent. What is CIP Sync? CIP Sync is a CIP implementation of the IEEE 1588 PTP (Precision Time Protocol).
Module Overview and Features Chapter 2 All input point event times are recorded and returned in a single buffer. The module returns two 64-bit timestamps for each input, thus allowing: • ON and OFF events for each point to be displayed simultaneously in the input data. • ladder logic not being explicitly required to see events, although needed to archive events. • events to be kept in the controller memory during remote power loss thus eliminating data loss.
Chapter 2 Module Overview and Features • Used in SCADA applications to indicate pump failures or other discrete events • Used in motion control applications to increase control coordination. • Used in high speed applications • Used in Global Position Registration In today's environment, specifications for SOE applications typically require 1 ms or better resolution on timestamps. There are two types of SOE applications.
Module Overview and Features Chapter 2 Motion Control CIP Sync also provides a common time reference for distributed VFD drives, servos, and controllers throughout the system. This allows controllers to request axes, reach a pre-defined position at a known time reference, or run at a set speed using the same reference. Since all drives and controllers in the system have the same reference to time, the controller can issue simple requests for axes to reach target positions in a synchronized fashion.
Chapter 2 Module Overview and Features Individual schedules are created in the controller, stored in the output image table for the module, and sent over the backplane to the Scheduled Output module. The schedule specifies a sequence count, the output point to be associated with the schedule, the time at which an output value should be applied to the physical output point, and the value to be applied at the scheduled time. The I/O module receives and stores the schedule.
Module Overview and Features Chapter 2 By using time to schedule the output in advance,and identifying when the product will be at a known position, hitting the exact point when a part is in front of a reject station on a high speed packaging machine, can be controlled. Chapter Summary and What’s Next In this chapter, you were given an overview of the 1732E ArmorBlock EtherNet/ IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules modules.
Chapter 2 Module Overview and Features Notes: 14 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Chapter 3 Use the Modules in an ArmorBlock System Introduction This chapter describes how the 1732E ArmorBlock EtherNet/IP Dual Port 8Point Sequence of Events Input and Scheduled Output Modules modules operate in an ArmorBlock system. Differences Between Module and Standard I/O Topic Page Differences Between Module and Standard I/O 15 Similar Functionality to Standard ArmorBlock 15 In many aspects, the modules behave the same as any other ArmorBlock digital module.
Chapter 3 Use the Modules in an ArmorBlock System Concept Description Using RSLogix 5000 software The I/O configuration portion of RSLogix 5000 software, v18 or greater, generates the configuration data for each module. Configuration data is transferred to the controller during the program download and subsequently transferred to the appropriate modules. Modules are ready to run as soon as the configuration data has been downloaded.
Chapter 4 Install Your Module Overview Install the Module This chapter shows you how to install and wire the 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules modules. The only tools you require are a flat or Phillips head screwdriver and drill.
Chapter 4 Install Your Module 4. Line up the small notch on the switch with the number setting you wish to use. Valid settings range from 001…254. 5. Replace switch dust caps. Make sure not to over tighten. 6. Reapply power. 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. 37 (1.46) 16.2 (0.64) Millimeters (Inches) 19.8 (0.
Install Your Module Chapter 4 2. Drill the necessary holes for #6 (M3) pan head screws. 3. Mount the module using #6 (M3) screws. Mount the Module in High Vibration Areas If you mount the module in an area that is subject to shock or vibration, we recommend you use a flat and a lock washer to mount the module. Mount the flat and the lock washer as shown in the mounting illustration. Torque the mounting screws to 0.68 Nm (6 lb-in.).
Chapter 4 Install Your Module Pico-style 3-Pin Output Female Connector (View into connector) Pin 1 Sensor Source Voltage Pin 3 Return Pin 4 Output 43583 ATTENTION: Sensors/actuators power should not be supplied externally. Ethernet Connectors Refer to the pinout diagrams for the network connectors. 4 3 1 2 5 44808 (View into connector) Pin 1Tx+ Pin 2 Rx+ Pin 3 TxPin 4 RxPin 5 Shell .
Install Your Module Chapter 4 Micro-style 4-Pin Input Male Receptacle Male Input Female Output (View into receptacle) Pin 1 Auxiliary power+ Pin 2 Module power+ Pin 3 Module powerPin 4 Auxiliary power- 2 1 3 4 IMPORTANT 45764 2 3 1 4 45763 The maximum current that any pin on the power connectors can carry is 4 A. The power required by the module is based on a 4-pin micro-style connector system. The module receives its required power through the male connector on the left.
Chapter 4 Install Your Module The table Auxiliary Power Calculation shows the resulting Auxiliary Power current calculation for a system of four modules. The Auxiliary Power voltage is 24V DC in this example. As can be seen in the cell with value set in bold, the Auxiliary Power current through the first connector in the daisy-chain is 3.898A which is less than 4A, so this system is adequate. Auxiliary Power Calculation Module 1 Module 2 Module 3 Module 4 IAPDC 3.108A 2.772A 1.301A 0.
Chapter 5 Configure the Module for Your EtherNet/IP Network Introduction Before using the modules in an EtherNet/IP network, you need to configure them 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 Automation BootP/DHCP utility, version 2.3 or greater, that ships with RSLogix 5000 or RSLinx software.
Chapter 5 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 Automation 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.
Configure the Module for Your EtherNet/IP Network Chapter 5 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, go to the next section. The gateway address is the default address of a network.
Chapter 5 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 Chapter 5 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.
Chapter 5 Configure the Module for Your EtherNet/IP Network 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. The New Entry dialog appears showing the device’s Ethernet Address (MAC). 3. Enter the IP Address you want to assign to the device and click OK.
Configure the Module for Your EtherNet/IP Network Chapter 5 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.
Chapter 5 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.
Configure the Module for Your EtherNet/IP Network Chapter 5 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.
Chapter 5 Configure the Module for Your EtherNet/IP Network Notes: 32 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Chapter 6 Configure the Module Using RSLogix 5000 Software Introduction This chapter guides you through the steps required to configure your 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules modules using the RSLogix 5000 software. Note that the modules presented in this chapter are configured using RSLogix 5000 software, version 18 or later.
Configure the Module Using RSLogix 5000 Software Set Up the Hardware In this example, a ControlLogix chassis contains the Logix5565 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 EtherNet/IP 1732E ArmorBlock Ethernet Module 192.168.1.20 1756-EN2T Chapter 6 LINK1 LINK2 X10 MOD X100 NET X1 1732E ArmorBlock Data AUX POWER Logix5565 Controller (slot 1) 1756-EN2T 192.168.1.
Configure the Module Using RSLogix 5000 Software Create the Example Application Chapter 6 Perform the following steps to create the example application: 1. From the File menu, select New. The New Controller dialog opens. 2. Enter an appropriate name for the Controller, for example, ArmorBlock_IO_Controller. 3. Select the correct version, chassis type, and slot number of the controller, and the folder where you want to save the RSLogix 5000 software file (Create In). The Description is optional.
Chapter 6 Configure the Module Using RSLogix 5000 Software RSLogix 5000 Configuration Software You must use RSLogix 5000, version 18 or later, to configure your module. You have the option of accepting default configuration for your module or writing point-level configuration specific to your application. Both options are explained in detail, including views of software screens, in this chapter.
Configure the Module Using RSLogix 5000 Software Chapter 6 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 I/O Configuration. B. Select New Module. 3. Expand Communications and select the new module in the Select Module dialog that appears. Select the 1756-EN2T EtherNet/IP Bridge. A. Select the 1756-EN2T EtherNet/IP Bridge. B.
Chapter 6 Configure the Module Using RSLogix 5000 Software 4. The New Module dialog opens. Configure the bridge module as illustrated below. A. Name the bridge. B. Enter the IP address. C. Select slot 3 for the EtherNet/IP bridge. D. Make sure the Minor Revision number matches your module revision number. E. Choose an Electronic Keying method. For more information, see page 48. F. Click OK. The local 1756-EN2T communication module will communicate with the 1732E ArmorBlock module on EtherNet.
Configure the Module Using RSLogix 5000 Software TIP Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014 Chapter 6 If the 1732E-IB8M8SOER, 1732E-OB8M8SR modules are not listed in the digital section of the Select Module dialog you may need to download the Add-On Profile (AOP) for the 1732E ArmorBlock R 2-Port and install it as an add-on to RSLogix 5000. The AOP file can be downloaded from: support.rockwellautomation.com/controlflash/ LogixProfiler.
Chapter 6 Configure the Module Using RSLogix 5000 Software 3. The New Module dialog appears. Fill in the Module Properties information as shown, and then click OK. Module Properties Values Field Name Name IP address Electronic keying Connection Format Revision Timestamp Value TEST_1732EIB8M8SOER or TEST_1732EOB8M8SR 192.168.1.20 Compatible Module Data (This field does not exist for the 1732-EOB8M8SR module.) 1.1 Per Point You can either accept or change the default configuration as shown.
Configure the Module Using RSLogix 5000 Software Chapter 6 Use the Default Configuration If you use the default configuration and click OK, you are done. You can skip to Download Your Configuration on page 43 for instructions on how to download your default configuration to the controller. Change the Default Configuration If you click Change... in step D on page 40, you can change the Module Definition information.
Chapter 6 Configure the Module Using RSLogix 5000 Software From the Connection tab, you can: A. Change the RPI. B. Inhibit the module. For more information on Module Inhibiting, see page 49. C. Make sure a Major Fault occurs on the module’s owner-controller if there is a connection failure between the module and the controller. D. Click the Configuration tab to go to the next screen, or E. Click OK to close the Module Properties dialog and download your configuration.
Configure the Module Using RSLogix 5000 Software Chapter 6 1732E-OB8M8SR Configuration Tab For the 1732E-OB8M8SR, you can do the following through the Configuration tab: A. Set the Output State during Program Mode and Fault Mode for Points 0…7. B. Set the Fault Duration and Fault Final State for Points 0…7. Grayed out unless Hold Duration is something other than “Forever”. C. Click OK to close the Module Properties dialog and download your configuration, or D.
Chapter 6 Configure the Module Using RSLogix 5000 Software Your freedom to change some configurable features, though, depends on whether the controller is in Remote Run Mode or Program Mode. IMPORTANT Although you can change configuration while online, you must go offline to add or delete modules from the project. The editing process begins on the main page of RSLogix 5000 software: A. Right-click the module. B. Select Properties. The General tab of the Module Properties dialog appears.
Configure the Module Using RSLogix 5000 Software Chapter 6 The Port Configuration 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.
Chapter 6 Configure the Module Using RSLogix 5000 Software • For RSLogix 5000 programming instructions, refer to RSLogix 5000 Getting Results, publication no. 9399-RLD300GR. • For ControlLogix controller information, refer to ControlLogix System User Manual, publication no. 1756-UM001.
Chapter 7 Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules Introduction This chapter describes the features common to both the 1732E Sequence of Events Input and Scheduled Output modules.
Chapter 7 Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules The table describes the communication formats used with input modules. Data Return Electronic Keying Communication Format Module Module returns input data with CIPSync/PTP time input data the value of the system clock (from its local chassis) when the input data changes.
Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules Chapter 7 The following table describes the keying options available with your module. Keying option Definition Exact Match All of the parameters listed above must match or the inserted module rejects a connection to the controller. Compatible Module The Compatible Module mode allows the module to determine whether it can emulate the module defined in the configuration sent from the controller. Some modules can emulate older revisions.
Chapter 7 Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules a. Inhibit the module. b. Perform the upgrade. c. Uninhibit the module. • You are using a program that includes a module that you do not physically possess yet, but you do not want the controller to continually look for a module that does not exist yet. In this case, you can inhibit the module in your program until it physically resides on the network.
Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules Chapter 7 • 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. The module produces the data and the owner-controller device consumes it.
Chapter 7 Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules Notes: 52 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Chapter 8 Specific Features of the 1732E-IB8M8SOER Sequence of Events Input Module Introduction This chapter describes the features specific to the 1732E Sequence of Events Input module. Topic Page Determine Module Compatibility 53 Operational Modes 53 Timestamp Latching 54 Software Configurable Input Filters 55 Sync to Master 57 These features are configurable through the RSLogix 5000 software.
Chapter 8 Specific Features of the 1732E-IB8M8SOER Sequence of Events Input Module • FIFO – Each channel provides buffering of the timestamped input data for every input transition. A minimum of ten buffers is provided for every input channel (total twenty data buffers for every input to contain both OFF to ON and ON to OFF transition). The stored data is utilized on a first-in-first-out (FIFO) basis.
Specific Features of the 1732E-IB8M8SOER Sequence of Events Input Module Software Configurable Input Filters Chapter 8 To account for hard contact “bounce”, you can configure ON to OFF and OFF to ON input filter times in RSLogix 5000 software for your module. These filters define how long an input transition must remain in the new state before the module considers the transition valid. IMPORTANT Input filters are applied to all inputs on the module.
Chapter 8 Specific Features of the 1732E-IB8M8SOER Sequence of Events Input Module • Scenario #1 (no bounce) – The input turns ON and remains for the full 2 ms. In this case, the module considers the transition valid and sends the data recorded at the transition to the controller. Note the input was sampled as being on three different times: 0 ms, 1 ms and 2 ms.
Specific Features of the 1732E-IB8M8SOER Sequence of Events Input Module Chapter 8 • Scenario #3 – 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 until the 1 ms counter decrements to zero. The input never remains ON for at least 2 consecutive ms intervals, the third ON sampled 1 ms interval.
Chapter 8 Specific Features of the 1732E-IB8M8SOER Sequence of Events Input Module synchronized with a master clock. When disabled, the module operates normally whether it is synchronized with a master clock or not. The Sync to Master attribute is a read/writeable Boolean with a default value of 0 (master synchronization disabled). Chapter Summary and What’s Next 58 In this chapter, you learned about the features of the Sequence of Events Input module.
Chapter 9 Specific Features of the 1732E-OB8M8SR Scheduled Output Module Introduction This chapter describes the features specific to the 1732E Scheduled Output module. Topic Page Determine Module Compatibility 59 Operational Modes 60 Time-Scheduled Output Control 60 Time-Scheduled Output Control 60 Configurable Point-Level Output Fault States 61 Output State 62 These features can be configured through the RSLogix 5000 software.
Chapter 9 Specific Features of the 1732E-OB8M8SR Scheduled Output Module Operational Modes The 1732E-OB8M8SR output module has two modes of handling the individual output points: • Normal Output – The output behaves like a normal output point such that the module updates the output point upon receiving new I/O data from the client controller. • Scheduled Mode – The output module is updated at a specific scheduled time.
Specific Features of the 1732E-OB8M8SR Scheduled Output Module Configurable Point-Level Output Fault States Chapter 9 Individual outputs can be independently configured to unique fault states, either On, Off, or Hold in case of a communication failure or Program mode. IMPORTANT Whenever you inhibit an output module, it enters the Program mode and all outputs change to the state configured for the Program mode.
Chapter 9 Specific Features of the 1732E-OB8M8SR Scheduled Output Module 4. Specify Fault Duration. When active, Fault Duration has options of "Forever", "1 Second", "2 Seconds", "5 Seconds" or "10 Seconds". Default is "Forever" or 0. 5. Specify the Fault Final State. Note that this is grayed out unless Hold Duration is something other than “Forever”. When active, Fault Final State has the options, “Off ” and “On”. Default value is Off. 6.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Introduction This chapter describes how to use the Sequence of Events Input and Scheduled Output modules (1732E-IB8M8SOER, 1732E-OB8M8SR). This chapter has two main sections: • Use the 1732E-IB8M8SOER Sequence of Events Input Module on page 65-83 • Use the 1732E-OB8M8SR Scheduled Output Module on page 81-88 The following table includes the list of topics available in this chapter.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Overview The 1732E-IB8M8SOER module can be configured to timestamp two transitions per input, one in each direction (OFF to ON and ON to OFF). When specific points that are Timestamp Capture-enabled transition (for example, input 1 is configured so that Timestamp Capture is enabled for OFF to ON transitions and the input turns ON), the module timestamps the transition with the current system time value on the network.
Use the Sequence of Events Input and Scheduled Output Modules Use the Sequence of Events Input Module Chapter 10 The following section describes how to use the Sequence of Events Input module. How Does 1732E-IB8M8SOER Store Timestamp Data? With each timestamped transition, 1732E-IB8M8SOER stores data for that point. An overview of how the module stores timestamp data is shown in the following figure. The module is installed, wired to input devices and ready to begin operation.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules 2. The module sends all of its input data, including the new data from the most recent transition, to the controller immediately after timestamping the transition and passing the input filter to make sure the transition was valid. 3. You copy new data from the controller tags to a separate data structure for later sorting. 4.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 Use the Configuration tab in RSLogix 5000 software to enable Timestamp Latching on the 1732E-IB8M8SOER, as shown in the example. Select this box to enable the Timestamp Latching feature. De-select the box to disable the feature. Use Timestamp Capture Timestamp Capture causes the module to timestamp specific input transitions (Off to On and On to Off ).
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Use the Configuration tab in RSLogix 5000 software to set Timestamp Capture, as shown in the example below. 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.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 from the Sequence of Events module using one of the two methods described later in this chapter. IMPORTANT Keep in mind that, although the Sequence of Events module can store up to 256 events per input, if you manage the buffer effectively (that is, retrieve data in a timely fashion), the module can timestamp an infinite number of input transitions and the controller will be able to retrieve and use the data.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules 4. The Sequence of Events module timestamps input transitions and records the data in its on-board buffer as long as the buffer is not full. (The module stores up to 256 events per input.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 The following occurs in the process of the managing data coming from the Sequence of Events module in CIPSync/PTP Per Point mode: 1. The controller retrieves current event data from the Sequence of Events module in one of two retrieval methods. 2. The controller copies the relevant portions of the current event data to a separate array. 3.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules This process continues as long as the Sequence of Events module timestamps input transitions and the controller continues to retrieve the data for each transition. Retrieval by Point Retrieval by Point is similar to Standard Retrieval by time except that with this method, the controller only retrieves timestamp data for input transitions that occurred on a specific point.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 The only exception to the process is that in Retrieval by Point, the current event is not necessarily the data in the first slot of of the on-board buffer. Instead, the current event is the first slot (up to 256 events per input) that contains data for a transition timestamped at the specified input.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Module Sends Data to the Controller The following figure shows an example of the module sending data to the controller. In the example, the following occurs: 1. Input 1 transitions from OFF to ON. (The input has Timestamp Capture enabled). 2. The module timestamps the transition. 3. The module sends its input data, including the transition timestamp from input 1, to the controller. 1732E-IB8M8SOER 1.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 The following figure shows when to use the COP instruction. In this example, the module timestamped a transition on input 1 and is sending input data to the controller at each RPI. The controller copies input data from the controller tags to a separate data structure. ControlLogix controller 1732E-IB8M8SOER 1. Input 1 transitions from OFF to ON. 2. Module timestamps the transition. 3. Module sends input data to the controller. I.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Acknowledge Timestamp Latching Timestamp Data In most cases, Timestamp Latching is enabled. This means that once the module timestamps an input transition, the module will not timestamp another transition in the same direction on the same input until you acknowledge the data from the first timestamped transition; when you acknowledge data, you clear it from the module.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 relevant input data to a separate structure. Now, the controller must clear the data from the module. In this example, to clear data from the module, the controller writes the following to the Sequence of Events output word: • O.EventAck = 1 • O.NewDataAck.2 = 1 ControlLogix controller 1732E-IB8M8SOER 1. Input 2 transitions from OFF to ON. 5. Module timestamps the transition. 3. Module sends input data to the controller. I.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Visit the Rockwell Automation Sample Code Library at http:// samplecode.rockwellautomation.com/idc/groups/public/documents/webassets/ sc_home_page.hcst. Clear All Data From the Module Buffer At Once 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 buffers, all of the module input tags return to 0.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 Timestamp Accuracy = +/- 12.5 μs.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Per Point Mode of Operation The Per Point mode of operation provides a single On and Off timestamp for each input point on the module. The 1732E-IB8M8SOER module employs employs CIP Sync Per Point. Per Point operation begins with the selection of the appropriate Timestamp Format in RSLogix 5000 software.
Use the Sequence of Events Input and Scheduled Output Modules Use the Scheduled Output Module Chapter 10 The Motion Planner Output Cam (MAOC) instruction offers the functionality to set and reset output bits based on an axis position. Usage with MAOC Instruction When used with motion and the MAOC instruction values in the output image are controlled by the Motion Planner firmware in the controller, the Motion Planner triggers the data to be sent to the module.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Due to the limit of 16 schedules supported by the 1732E-OB8M8SR module, some constraints are applied to the number of events that can be processed every coarse update period. Only eight schedules are available each coarse update. This allows for two consecutive coarse updates in which each update contains eight output events.
Use the Sequence of Events Input and Scheduled Output Modules Chapter 10 Time Slot Information Topic Description Output Off Mask For normal outputs, the bit corresponding to the output bit of the Unlatch or Pulse Off event is set indicating that the output is to be turned off for these events. For inverted outputs, the bit corresponding to the output bit of the Latch or Pulse On event is set indicating that the output is to be turned off for these events.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules associated with a 1732E-OB8M8SR module by checking the module type stored in the driver table. Output Data Structure Field Size Description Value 4 bytes Data values for un-scheduled output bits. 0 = Off 1 = On Mask 4 bytes Selects which output bits are to be scheduled. The eight bits (0…7) can be scheduled.
Use the Sequence of Events Input and Scheduled Output Modules Chapter Summary and What’s Next Chapter 10 In this chapter, you learned how to use the modules. The next chapter describes interpreting the status indicators.
Chapter 10 Use the Sequence of Events Input and Scheduled Output Modules Notes: 86 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Chapter 11 Troubleshoot the Module This chapter describes how to troubleshoot the 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules modules using RSLogix 5000 software. Troubleshoot the Module In addition to the status indicators on the module, RSLogix 5000 software 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.
Chapter 11 Troubleshoot the Module · Message in a screen’s status line. Status line provides information on the module fault and on the connection to 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. RSLogix 5000 software generates 1 s in response to a module communication fault.
Troubleshoot the Module Chapter 11 Determine Fault Type When you are monitoring a module’s configuration properties in RSLogix 5000 software and receive a Communications fault message, the Connection page lists the type of fault. The fault type is listed here. Click Help for a detailed listing of the possible faults, their causes and suggested solutions. For a detailed listing of the possible faults, their causes and suggested solutions, see Module Faults in the RSLogix 5000 Software Online Help.
Chapter 11 Troubleshoot the Module Notes: 90 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Chapter 12 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.
Chapter 12 Interpret Status Indicators Indicator Status for Modules Indicator Status Description Module status Off No power applied to the device. Flashing red/green The module is performing POST (Power-On Self Test), which completes within 30 s. Green Device operating normally. Flashing red Module has experienced a recoverable fault. Red Unrecoverable fault – may require device replacement. Flashing green On 1732E-IB8M8SOER and 1732E-OB8M8SR: Device is not synchronized to master clock.
Appendix A Specifications Specifications The ArmorBlock Sequence of Events Input and Scheduled Sourcing Output modules (1732E-IB8M8SOER, 1732E-OB8M8SR) have the following specifications.
Appendix A Specifications Input Specifications – 1732E-IB8M8SOER Attributes Value On-state current, min 180 µA @ 11V DC On-state current, max 5.0 mA @ 30V DC Off-state current, max 90 µA @ 5V DC Voltage sensor source, max 30V DC Voltage sensor source, min 10V DC Input filter 0 ms (default), 2 ms, 4 ms, 8 ms, and 16 ms Output Specifications – 1732E-OB8M8SR Attributes Value Number of outputs 8 sourcing type On-state voltage 11V DC, min 24V DC, nom 30V DC, max On-state current 0.
Specifications Appendix A Environmental Specifications Attribute Value EFT/B immunity IEC 61000-4-4: ±3 kV at 5 kHz on power ports ±3 kV at 5 kHz on signal ports ±3 kV at 5 kHz on communication ports Surge transient immunity IEC 61000-4-5: ±2 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 shielded ports ±2 kV line-earth(CM) on communication ports Conducted RF immunity IEC 61000-4-6: 10V rms with 1 kHz sin
Appendix A Specifications Notes: 96 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
B Appendix Module Tags Fault and Status Reporting Between the Module and Controllers The 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules modules send fault/status data to the owner-controller. The module maintains a Module Fault Word, the highest level of fault reporting.
Appendix B Module Tags Configuration Tags – 1732E-IB8M8SOER Tag Name Type Description C.FilterOnOff INT Sets the ON to OFF filter time for all 8 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 55. C.LatchEvents BOOL Latches events so that an event will not be overwritten until acknowledged.
Module Tags Appendix B Input Tags – 1732E-IB8M8SOER Tag Name Type Set on Per Point or Modulewide basis Description I.EventOverflow SINT Per point Set for an input when the module either: · Does not timestamp a transition on the input – The module has Timestamp Latch 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 76).
Appendix B Module Tags Output Tags – 1732E-IB8M8SOER 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 SINT Allows I.NewData bits and I.
Module Tags Appendix B Configuration Tags – 1732E-OB8M8SR C.Pt00FaultMode…Pt07FaultMode BOOL The Pt0xFaultMode is used in conjunction with FaultValue to configure the state of output x (that is, Pt00FaultMode for output 0, Pt01FaultMode for output 1, Pt02FaultMode for output 2, and so on up to Pt07FaultMode for output 7) when a communications fault occurs. A value of 0 means that, in the case of a communications fault, the value in FaultValue will be used (Off or On).
Appendix B Module Tags Input Tags – 1732E-OB8M8SR Tag Name Type Description I.OffsetTimeStamp DINT[2] 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] The ID number of the Grandmaster clock that the module is synchronized to. I.TimeStamp DINT[2] Timestamp to be used with scheduled outputs and CIPSync/PTP.
Module Tags Appendix B Notes: Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014 103
Appendix B 104 Module Tags Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Appendix C 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 or scanner memory. The following table lists the assembly instances and connection points for the 1732E EtherNet/IP ArmorBlock Sequence of Events Input and Scheduled Sourcing Output Modules.
Appendix C Data Tables Configuration Assembly Instance 124 Data Structure (Configuration Header) Configuration Byte Bit 7 Bit 6 Bit 5 Bit 4 0 Reserved (Ignored) 1 Reserved (Ignored) 2 Reserved (Ignored) 3 Reserved (Ignored) CRN Configuration Revision Number Bit 3 Bit 2 Bit 1 Bit 0 CRN Assembly Instance 4 Data Structure Produced Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 In 7 In 6 In 5 In 4 In 3 In 2 In 1 In 0 Assembly Instance 34 Data Structure Consumed Byte
Data Tables Appendix C Produced Assembly Instance 157 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Reserved (Must be 0) 1 Reserved (Must be 0) 2 Reserved (Must be 0) 3 Reserved (Must be 0) 4 In 7 In 6 In 5 In 4 In 3 In 2 In 1 In 0 5 NewData7 NewData6 NewData5 NewData4 NewData3 NewData2 NewData1 NewData0 6 EventOv7 EventOv6 EventOv5 EventOv4 EventOv3 EventOv2 EventOv1 EventOv0 7 Pad 8…15 Local Clock Offset (64 bit) 16…23 Offs
Appendix C Data Tables Produced Assembly Instance 157 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Where: 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 point. Events may be lost when new events are either ignored or overwriting existing events which have yet to be acknowledged.
Data Tables Appendix C Produced Assembly Instance 158 Data Structure Consumed Byte Bit 7 Bit 6 72…75 Event Number 2 (32 bit) 76 Event Point 2 77 Reserved (Must be 0) 78…79 Pad (16 Bits) 80…87 Input Time Stamp 3 (64 bit) 88…91 Event Number 3 (32 bit) 92 Event Point 3 93 Reserved (Must be 0) 94…95 Pad (16 Bits) 96…103 Input Time Stamp 4 (64 bit) 104…107 Event Number 4 (32 bit) 108 Event Point 4 109 Reserved (Must be 0) 110…111 Pad (16 Bits) 112…119 Input Time Stamp 6 (64 bit)
Appendix C Data Tables Produced Assembly Instance 158 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 189 Reserved (Must be 0) 190…191 Pad (16 Bits) 192…195 Events Queued Count (32 Bits) 196 Reserved (Must be 0) Where: NewData – Set when new data has been detected upon that input and an unread event is queued for that point. Cleared when all the time stamps for that point have been acknowledged or if the corresponding NewDataAck bit transitions from 0…1.
Data Tables Appendix C Consumed Assembly Instance 159 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Where: FIFO Mode EventAck – The controller writes back the EventNumber read to transition buffers. All events with EventNumbers less than or equal to the EventAck will be acknowledged. If the RetreiveByPoint bit is set the PointToRetrieve attribute must also be used to specify the point to retrieve next.
Appendix C Data Tables Configuration Assembly Instance 171 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 8 ProgMode Ch7 ProgMode Ch6 ProgMode Ch5 ProgMode Ch4 ProgMode Ch3 ProgMode Ch2 ProgMode Ch1 ProgMode Ch0 9 Reserved (Ignored) 10 ProgVal Ch7 ProgVal Ch5 ProgVal Ch4 ProgVal Ch3 ProgVal Ch2 ProgVal Ch1 ProgVal Ch0 11 Reserved (Ignored) 12…15 Hold Last State Duration [0] 16…19 Hold Last State Duration [1] 20…23 Hold Last State Duration [2
Data Tables Appendix C Consumed Assembly Instance 174 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 10 Schedule[0].TimestampOffset 11 Schedule[1].ID 12…15 Schedule[1].SequenceNumber 16…19 Schedule[1].OutputPointSelect 20…23 Schedule[1].Data 24…27 Schedule[1]. TimestampOffset 28…31 Schedule[2].ID 32…35 Schedule[2].SequenceNumber 36…39 Schedule[2].OutputPointSelect 40…43 Schedule[2].Data 44…47 Schedule[2]. TimestampOffset 48 Schedule[3].ID 49 Schedule[3].
Appendix C Data Tables Consumed Assembly Instance 174 Data Structure 114 Consumed Byte Bit 7 Bit 6 Bit 5 89 Schedule[8].SequenceNumber 90 Schedule[8].OutputPointSelect 91 Schedule[8].Data 92…95 Schedule[8]. TimestampOffset 96 Schedule[9].ID 97 Schedule[9].SequenceNumber 98 Schedule[9].OutputPointSelect 99 Schedule[9].Data 100…103 Schedule[9]. TimestampOffset 104 Schedule[10].ID 105 Schedule[10].SequenceNumber 106 Schedule[10].OutputPointSelect 107 Schedule[10].
Data Tables Appendix C Consumed Assembly Instance 174 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 147 Schedule[15].Data 148…151 Schedule[15]. TimestampOffset Where: Data – Output Data to apply to unscheduled channels (those with a value of zero configured in ScheduleMask). ScheduleMask – Mask indicating which channels are scheduled. Per bit 0 = use Data value (normal output); 1 = use scheduled output. TimestampOffset – System Time to Local Time Offset.
Appendix C Data Tables Produced Assembly Instance 177 Data Structure 116 Consumed Byte Bit 7 Bit 6 Bit 5 62…63 Reserved 16 bits (Must be zero) 64 Schedule[4].State (8 bit) 65 Schedule[4].SequenceNumber (8 bit) 66…67 Reserved 16 bits (Must be zero) 68 Schedule[5].State (8 bit) 69 Schedule[5].SequenceNumber (8 bit) 70…71 Reserved 16 bits (Must be zero) 72 Schedule[6].State (8 bit) 73 Schedule[6].SequenceNumber (8 bit) 74…75 Reserved 16 bits (Must be zero) 76 Schedule[7].
Data Tables Appendix C Produced Assembly Instance 177 Data Structure Consumed Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Where: Data – Output echo data. SyncToMaster – When set, indicates the module has synced to a Valid Time Master. Sync Timeout – We had a Valid local CIP Sync Timemaster which has since timed out. LateScheduleCount – Indicates that a schedule request arrived at the module after the schedule time. The counter rolls over to 1 every 65,535 late updates.
Appendix C Data Tables Notes: 118 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Appendix D Connect to Networks via Ethernet Interface This appendix: • 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.
Appendix D Connect to Networks via Ethernet Interface IMPORTANT The ArmorBlock module contains two 10/100Base-T, M12-D (4pin) 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 Appendix D In order to exchange I/O data with another device on Ethernet, that device must first originate a connection with the ArmorBlock via TCP/IP. Once an I/O connection is established via TCP/IP the I/O data is exchanged via UDP/IP. Duplicate IP Address Detection The ArmorBlock module firmware supports duplicate IP address detection.
Appendix D Connect to Networks via Ethernet Interface Configuration Parameters Subnet Mask The ArmorBlock module subnet mask (in network byte order). The Subnet Mask is used to interpret IP addresses when the internet is divided into subnets. A Subnet Mask of all zeros indicates that no subnet mask has been configured. In this case, the controller assumes a Subnet Mask of 255.255.255.0.
Appendix E 1732E ArmorBlock Embedded Web Server Introduction Rockwell Automation offers enhanced 1732E ArmorBlock for your EtherNet/IP control systems so you can monitor data remotely via web pages. This chapter shows how you can use the 1732E ArmorBlock EtherNet/IP Dual Port 8-Point Sequence of Events Input and Scheduled Output Modules module’s web server.
Appendix E 1732E ArmorBlock Embedded Web Server Access the Home Page of the Web Server From your web browser, enter the IP address of the 1732E ArmorBlock module. The module displays its home page. Module home page Specify the IP address of the module in the Address field. Log On to the Web Server Many of the features of the 1732E ArmorBlock I/O require you to log on with appropriate access.
1732E ArmorBlock Embedded Web Server Appendix E Navigate the 1732E ArmorBlock I/O You navigate the web server 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.
Appendix E 1732E ArmorBlock Embedded Web Server Notes: 126 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Index Numerics 1588 standard 7 1732E ArmorBlock embedded web server 119 navigate 121 overview 1 1732E-IB8M8SOER 8, 59, 60, 61, 64, 75, 76, 88 configuration tags 94 data tables 101 input tags 94 output tags 96 tags 93, 94 1732E-OB8M8SR 59, 77, 78, 80, 88, 97 data tables 101 input tags 99 tags 93 1756-EN2T 2, 36 1756-EN2TR 2, 36 1756-EN3TR 2, 36 A access AOP help 85 data 119 module data 45 accuracy 75 timestamp 75 acknowledge data 72 timestamp data 72 add module 36 Add-On Profile help 42, 43 agency certifica
128 bridge 38 I/O 35 for CIP Sync 46 input filters 57 IP address 23 module 1, 33, 48 OFF to ON 55 ON to OFF 55 RSLogix 5000 46 subnet mask 23 your module 27 connection data 40 tab 42, 50 connectors I/O 19 network 20 consumer data 2 controller 65, 67, 68 controller tags use 45 ControlLogix 3, 70 conventions iv COP instruction 70 use 70 COS 2 CPS instruction 70 use 70 critical data 6 D data 71, 73 access 119 acknowledge 72 additional 15 configuration 15 connection 40 consumer 2 exchange 2, 3 input 2, 9, 45,
129 event latching 9 EventAck 69, 72, 73 output tag 72 EventNumber 65, 70, 71, 73 EventOverflow 62, 70, 71, 72, 73 exact match 48 F falling edge 72 timestamp 72 fault 71, 73, 83, 85 communication 84 connection page 85 general module 84 listings 85 module 50 notification 84 warning signal 83 FaultMode 97 feature Timestamp Latching 54 FIFO 65, 66, 67, 69 firmware 74, 75 delay 74 version 1 FLASH upgrade 49 Functional Earth 6, 18 G gateway address 25, 118 General tab 41, 44 GrandMasterClockID 70, 71, 73 H h
130 LocalClockOffset 70, 71, 73, 76 Logix5000 15 LVD 22 M manage data 69 manuals related iv MAOC 77, 79 master clock 8, 46 master/slave 2 maximum input frequency 75 message-based protocol 2 minor revision setting in RSLogix 5000 38 mode operational 47 Per Point 54 model networking 2 Producer/Consumer 2, 51 module 1, 87, 88 1732E ArmorBlock 1 add new 36 buffer 74 compatibility 1, 53 configure 1, 33 data 45, 119 definition 41 fault reporting 50 features 1 inhibiting 49 interrogate 50 mount 18 overview 5, 60
131 configuration process 36 EtherNet/IP network 6 module 5, 60 stores timestamp data 61 overwrite timestamp data 62 owner-controller 15 P PELV 22 Per Point 76 mode 54 Pin ON->OFF 75 point ID 80 point value 80 PointtoRetrieve 68 Port Configuration tab 42 Port Diagnostics dialog 85 POST 88 power 87 Precision Time Protocol 7, 8 primary name server 118 produce data 2, 51 Producer/Consumer model 2, 51 produces data 60 propagate signal 74 protocol Common Industrial 2, 7 Dynamic Host Configuration 23, 27, 30 In
132 output word 73 signal propagate 74 sinking or sourcing wiring use 53 software configuration 36 DHCP 30 software release 1 Sort routine 73 use 70, 73 standard I/O 15 standard retrieval 67 status indicator 50, 87, 88 auxiliary power 87 I/O 87 interpret 87 link 87 Link 1 88 Link 2 88 module 87 network 87, 88 power 88 store data 61 subnet mask 26, 118 configure 23 synchronize computer time 7 independent clocks 7 to grandmaster clock 46 SyncToMaster 70, 71, 73 system ArmorBlock 15 T tab Configuration 41, 4
133 individual 8 latching 54 ON and OFF 53 recorded 8, 56 rising edge 72 transition 70 timestamp latching default 62 disabled 54 enable 42, 54, 63 enabled 54 feature 54 using 62 TimeStampOffOn 70, 71, 73 TimeStampOnOff 70, 71, 73 time-transfer protocol 7 torque 19 transitions 61, 68 Transport Control Protocol 27 troubleshoot 83 1732E EtherNet/IP 83 U configuration tab 63 controller tags 45 COP instruction 70 CPS instruction 70 default configuration 36, 41 DHCP 30 DHCP server 23, 27 how to 59 module iii m
134 Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014
Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014 135
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
