Rockwell Automation Allen-Bradley ControlLogix 1756-IB16ISOE User Manual
  1. Manuals
  2. Brands
  3. Rockwell Automation Manuals
  4. Control Unit
  5. Allen-Bradley ControlLogix 1756-IB16ISOE
  6. User manual

Rockwell Automation Allen-Bradley ControlLogix 1756-IB16ISOE User Manual

Sequence of events module
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
ControlLogix
Sequence of Events
Module
1756-IB16ISOE (24/48V dc),
1756-IH16ISOE (125V dc)
User Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Allen-Bradley ControlLogix 1756-IB16ISOE and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Rockwell Automation Allen-Bradley ControlLogix 1756-IB16ISOE

Summary of Contents for Rockwell Automation Allen-Bradley ControlLogix 1756-IB16ISOE

  • Page 1 ControlLogix Sequence of Events Module 1756-IB16ISOE (24/48V dc), 1756-IH16ISOE (125V dc) User Manual...
  • Page 2 In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
  • Page 3 Preface Purpose of This Manual This manual describes how to use the ControlLogix Sequence of Events module in your ControlLogix application. With this manual, you can learn how to install, configure and troubleshoot the module. There are two types of ControlLogix Sequence of Events modules, as described in Table Preface.1: Table Preface.1 Catalog number:...
  • Page 4 Preface What This Manual Contains Table Preface.2 lists the sections contained in this manual: Table Preface.2 Section: Title: Chapter 1 What is the ControlLogix Sequence of Events Module? Chapter 2 How Does the Sequence of Events Module Operate in a ControlLogix System? Chapter 3 Installing the Sequence of Events Module...
  • Page 5 Preface Preventing Electrostatic This module is sensitive to electrostatic discharge. Discharge This equipment is sensitive to electrostatic discharge, ATTENTION which can cause internal damage and affect normal operation. Follow these guidelines when you handle this equipment: • Touch a grounded object to discharge potential static.
  • Page 6 Preface Environment and Enclosure This equipment is intended for use in a Pollution ATTENTION Degree 2 industrial environment, in overvoltage Category II applications (as defined in IEC publication 60664-1), at altitudes up to 2000 meters without derating. This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR Publication 11.

  • Page 7: Table Of Contents

    Table of Contents Chapter 1 What is the ControlLogix What This Chapter Contains ..... . . 1-1 What does Sequence of Events Module Do? ... . 1-1 Sequence of Events Module? Timestamping Using the Coordinated System Time (CST) 1-1 On-Board Data Storage .
  • Page 8 Table of Contents Chapter 4 Configuring the Sequence of What This Chapter Contains ..... . . 4-1 Configuring Your I/O Module ..... . 4-1 Events Module RSLogix 5000 Configuration Software .
  • Page 9 Table of Contents Chapter 6 Using The Sequence of Events What This Chapter Contains ..... . . 6-1 Overview of the Mode ......6-1 Module in CST Per Point Mode How Does the Module Store Timestamp Data in CST Per Point Mode? .
  • Page 10 Table of Contents Chapter 8 Troubleshooting the Sequence of What This Chapter Contains ..... . . 8-1 Using LED Status Indicators ......8-1 Events Module Using RSLogix 5000 To Troubleshoot the Module .

  • Page 11: What Does Sequence Of Events Module Do

    Chapter What is the ControlLogix Sequence of Events Module? What This Chapter Contains This chapter describes the ControlLogix Sequence of Events module. Table 1.1 For information on: See page: What does Sequence of Events Module Do? What Else Does the Sequence of Event Module Do? Understanding the Module’s Physical Features Using Module Identification and Status Information What does Sequence of...

  • Page 12: On-Board Data Storage

    What is the ControlLogix Sequence of Events Module? CST cannot easily translate to real-time but serves as a relative time reference. Each module in a chassis has access to this reference. The Sequence of Events module grabs the current CST value at the time of the input state change to timestamp the input data.

  • Page 13: Two Modes Of Operation

    What is the ControlLogix Sequence of Events Module? Two Modes of Operation The Sequence of Events module can operate in either of the modes described in Table 1.2: Table 1.2 Operational mode: Description: CST Per Point Mode The module timestamps up to 2 input transitions per input, one for OFF to ON transitions and another for ON to OFF transitions.

  • Page 14: Understanding The Module's Physical Features

    What is the ControlLogix Sequence of Events Module? Understanding the ControlLogix modules mount in a ControlLogix chassis and use a Removable Terminal Block (RTB), or a Bulletin 1492 Interface Module Module’s Physical Features cable that connects to an IFM, to connect all field-side wiring. Before you use your module, you should have already: •...

  • Page 15: Using Module Identification And Status Information

    What is the ControlLogix Sequence of Events Module? Using Module Each Sequence of Events module maintains specific identification information that separates it from all other modules. This information Identification and assists you in tracking all the components of your system. For Status Information example, you can track module identification information to be aware of exactly what modules are located in any ControlLogix chassis at...

  • Page 16: Chapter Summary And What's Next

    What is the ControlLogix Sequence of Events Module? Chapter Summary and In this chapter you read about what the ControlLogix Sequence of Events module is. Chapter 2 explains How Does the Sequence of What’s Next Events Module Operate in a ControlLogix System? Publication 1756-UM528A-EN-P - April 2004...

  • Page 17: What This Chapter Contains

    Chapter How Does the Sequence of Events Module Operate in a ControlLogix System? What This Chapter This chapter describes how the Sequence of Events module operates in a ControlLogix system. Contains Table 2.1 For information on: See page: Ownership Using RSNetWorx and RSLogix 5000 Propagating a Signal From Field Device to Backplane Sequence of Events Module in a Local Chassis Sequence of Events Module in a Remote Chassis...

  • Page 18: Similar Functionality To Standard Controllogix Dc Input Modules

    How Does the Sequence of Events Module Operate in a ControlLogix System? Similar Functionality to With respect to general module operation in a ControlLogix system, the Sequence of Events module operates similarly to other Standard ControlLogix DC ControlLogix digital input modules in many ways. This chapter Input Modules focuses on how the Sequence of Events module’s behavior differs from that of other ControlLogix digital input modules.
  • Page 19 How Does the Sequence of Events Module Operate in a ControlLogix System? Table 2.3 Ways that a Sequence of Events Module Behave Like Other ControlLogix Digital Input Modules Concept: Description: Making Connections ControlLogix controllers can make direct or rack connections to digital I/O modules. The controller can only make a direct connection to the Sequence of Events module.

  • Page 20: Propagating A Signal From Field Device To Backplane

    How Does the Sequence of Events Module Operate in a ControlLogix System? Propagating a Signal From As shown in Figure 2.1, the Sequence of Events module receives a signal at the RTB and processes it internally before sending a signal to Field Device to Backplane the ControlLogix backplane via the Requested Packet Interval (RPI) or at na Enable CST Capture occurrence.
  • Page 21 How Does the Sequence of Events Module Operate in a ControlLogix System? Figure 2.1 Digital signal CST captured here processor Filter Scan Hardware ASIC time delay delay delay Signal applied User configurable Up to 25µs Typically Signal at the RTB 0 - 50ms 175µs - FIFO sent to...

  • Page 22: Sequence Of Events Module In A Local Chassis

    How Does the Sequence of Events Module Operate in a ControlLogix System? Sequence of Events Module When a Sequence of Events module resides in the local chassis (i.e., the same chassis as the owner-controller), the following two in a Local Chassis configuration parameters affect how and when an input module multicasts data: •...
  • Page 23 How Does the Sequence of Events Module Operate in a ControlLogix System? When Enable CST Capture is enabled for specific points and transitions occur for those points, the Sequence of Events module not only captures the CST at the transition occurrence but also sends input data to the controller.

  • Page 24: Sequence Of Events Module In A Remote Chassis

    How Does the Sequence of Events Module Operate in a ControlLogix System? Sequence of Events Module If your Sequence of Events module physically resides in a chassis other than where the owner-controller is (e.g. a remote chassis in a Remote Chassis connected via ControlNet), the role of the RPI and the module’s Enable CST Capture behavior changes slightly with respect to getting data to the owner-controller.
  • Page 25 How Does the Sequence of Events Module Operate in a ControlLogix System? The “reserved” spot on the network and the module’s RPI are asynchronous to each other. This means there are Best and Worst Case scenarios as to when the owner-controller will receive updated channel data from the module in a remote chassis.

  • Page 26: Remote Input Modules Connected Via Ethernet/Ip

    2-10 How Does the Sequence of Events Module Operate in a ControlLogix System? When selecting values for the remotely located module’s RPI, system throughput is optimized when its RPI value is a power of 2 times the current NUT running on ControlNet. For example, Table 2.5 shows recommended RPI values for a system using a NUT of 5mS: Table 2.5 Recommended RPI Values for System Using NUT of 5mS...

  • Page 27: What This Chapter Contains

    Chapter Installing the Sequence of Events Module What This Chapter This chapter describes how to install the Sequence of Events module. Contains Table 3.1 For information on: See page: Installing the Sequence of Events Module Keying the Removable Terminal Block Connecting Wiring Assembling The Removable Terminal Block and the Housing Choosing the Extended-Depth Housing...
  • Page 28 Installing the Sequence of Events Module 1. Align circuit board with top and bottom chassis guides. Figure 3.1 Printed Circuit Board 20861-M 2. Slide module into chassis until module tabs ‘click’. Figure 3.2 Locking Tab 20862-M Publication 1756-UM528A-EN-P - April 2004...

  • Page 29: Keying The Removable Terminal Block

    Installing the Sequence of Events Module Keying the Removable Key the RTB to prevent inadvertently connecting the incorrect RTB to your module. When the RTB mounts onto the module, keying Terminal Block positions match up. For example, if you place a U-shaped keying band in position #4 on the module, you cannot place a wedge-shaped tab in #4 on the RTB or your RTB does not mount on the module.

  • Page 30: Connecting Wiring

    Installing the Sequence of Events Module Connecting Wiring You can use an RTB or a Bulletin 1492 prewired Interface Module (IFM) to connect wiring to your module. You must connect wires to the RTB. An IFM has been prewired before you received it. If you are using an IFM to connect wiring to the module, skip this section and go to page 3-7.

  • Page 31: Recommendations For Wiring Your Rtb

    • Use a tie to secure the wires in the strain relief area of the RTB. • The jumper bar part number is 97739201. Contact your local Rockwell Automation sales representative to order additional jumper bars, if necessary. • Order and use an extended-depth housing (Catalog number 1756-TBE) for applications that require heavy gauge wiring.

  • Page 32: Wiring The Sequence Of Events Module

    3. If separate power sources are used, do not exceed the specified isolation voltage. 4. Do not connect more than 2 wires to any single terminal. 5. The jumper bar part number is 97739201. Contact your local Rockwell Automation sales representative to order jumper bars, if necessary. Publication 1756-UM528A-EN-P - April 2004...

  • Page 33: Assembling The Removable Terminal Block And The Housing

    Installing the Sequence of Events Module Assembling The Removable Removable housing covers the wired RTB to protect wiring connections when the RTB is seated on the module. Terminal Block and the Housing 1. Align the grooves at the bottom of each side of the housing with the side edges of the RTB.

  • Page 34: Choosing The Extended-Depth Housing

    Installing the Sequence of Events Module Choosing the There are two housing options you must consider when wiring your Sequence of Events module–standard-depth or extended-depth. Extended-Depth Housing When you order an RTB for your module, you receive a standard-depth housing with the RTB. If your application uses heavy gauge wiring, you can order an extended-depth housing.

  • Page 35: Recommendations For Using The Extended-Depth Housing

    Installing the Sequence of Events Module Recommendations for Using the Extended-Depth Housing Consider the following recommendations when deciding to use an extended-depth housing on your Sequence of Events module. It is recommended you use the 1756-TBE when: • using >36 18AWG wires •...

  • Page 36: Installing The Removable Terminal Block

    3-10 Installing the Sequence of Events Module Installing the Removable Install the RTB onto the module to connect wiring. Terminal Block Shock hazard exists. If the RTB is installed onto ATTENTION the module while the field-side power is applied, the RTB will be electrically live. Do not touch the RTB’s terminals.
  • Page 37 Installing the Sequence of Events Module 3-11 2. Press quickly and evenly to seat the RTB on the module until the latches snap into place. Locking tab 20854-M 3. Slide the locking tab down to lock the RTB onto the module. Publication 1756-UM528A-EN-P - April 2004...

  • Page 38: Removing The Removable Terminal Block

    3-12 Installing the Sequence of Events Module Removing the Removable If you need to remove the module from the chassis, you must first remove the RTB from the module. Terminal Block Shock hazard exists. If the RTB is removed from ATTENTION the module while the field-side power is applied, the module will be electrically live.

  • Page 39: Removing The Module From The Chassis

    Installing the Sequence of Events Module 3-13 Removing the Module 1. Push in the top and bottom locking tabs. from the Chassis Locking tabs 20856-M 2. Pull module out of the chassis. 20857-M Publication 1756-UM528A-EN-P - April 2004...

  • Page 40: Chapter Summary And What's Next

    3-14 Installing the Sequence of Events Module Chapter Summary and In this chapter, you read about: What’s Next • installing the module. • keying the RTB and IFM. • connecting wiring. • assembling the RTB and the housing. • installing the RTB or IFM onto the module. •...

  • Page 41: Configuring Your I/O Module

    Chapter Configuring the Sequence of Events Module What This Chapter This chapter describes how to configure your Sequence of Events module. Contains Table 4.1 For information on: See page: Configuring Your I/O Module Overview of the Configuration Process Adding a New Module to Your RSLogix 5000 Project Using the Default Configuration Altering the Default Configuration Downloading Configuration...

  • Page 42: Overview Of The Configuration Process

    Configuring the Sequence of Events Module Overview of the When you use the RSLogix 5000 software to configure a Sequence of Events module, you must perform the following steps: Configuration Process 1. Add the new module to your RSLogix 5000 project. 2.

  • Page 43: Adding A New Module To Your Rslogix 5000 Project

    Configuring the Sequence of Events Module Adding a New Module to After you have started RSLogix 5000 and created a controller, you must add a new module to your project. The wizard allows you to Your RSLogix 5000 Project create a new module and write configuration. You can use default configuration or write specific configuration for your application.
  • Page 44 Configuring the Sequence of Events Module 3. When the Select Module Type screen appears, select the Sequence of Events module. A. Select the Sequence of Events module. B. Click OK. 4. Configure the module. The first screen of the configuration wizard is shown below.

  • Page 45: Communications Format

    Configuring the Sequence of Events Module Communications Format The communications format determines what operational mode your Sequence of Events module uses and, consequently, what tags RSLogix 5000 generates when configuration is complete. Once a module is created, you cannot change the communications format unless you delete and recreate the module.

  • Page 46: Using The Default Configuration

    Configuring the Sequence of Events Module Using the Default If you use the default configuration and click on Finish, you are done. Configuration Altering the Default If you click Next in step 4 on page 4-4, you can write specific configuration for your module in RSLogix 5000.

  • Page 47: Downloading Configuration

    Configuring the Sequence of Events Module Downloading After you write configuration for your Sequence of Events module, the module does not use this configuration until you download it to Configuration the owner-controller. The download transfers the entire program to the controller, overwriting any existing program. Download module configuration as shown below.
  • Page 48 Configuring the Sequence of Events Module The editing process begins on the main page of RSLogix 5000. A. Right-click on the module. B. Select Properties The General tab of the configuration wizard appears. Click on the tab of the page that you want to view or reconfigure and make any appropriate changes.

  • Page 49: Configuring Modules In A Remote Chassis

    Configuring the Sequence of Events Module Configuring Modules in a ControlLogix ControlNet Interface modules (1756-CNB or 1756-CNBR) or the EtherNet/IP Bridge module (1756-ENBT) are Remote Chassis required to communicate with Sequence of Events modules in a remote chassis. You must configure the communications module in the local chassis and the remote chassis before adding remote Sequence of Events modules to your project.
  • Page 50 4-10 Configuring the Sequence of Events Module 4. Add a communications module to the remote chassis. A. Right-click on the local communication module. B. Select New Module 5. Select a communications module for the remote chassis. 6. Configure the communications module in the remote chassis. 7.

  • Page 51: Chapter Summary And What's Next

    Configuring the Sequence of Events Module 4-11 Chapter Summary and In this chapter, you read about configuring your Sequence of Events module. What’s Next Chapter 5 describes Using the Sequence of Events Module Features. Publication 1756-UM528A-EN-P - April 2004...
  • Page 52 4-12 Configuring the Sequence of Events Module Notes: Publication 1756-UM528A-EN-P - April 2004...

  • Page 53: What This Chapter Contains

    Chapter Using the Sequence of Events Module Features What This Chapter This chapter describes the features available on the Sequence of Events module. Contains Table 5.1 For information on: See page: Determining Module Compatibility Two Operational Modes Enable CST Capture Latch CST Chatter Detection Software Configurable Input Filters...

  • Page 54: Determining Module Compatibility

    Using the Sequence of Events Module Features Determining Module Primarily, a Sequence of Events module is used to timestamp input data. However, additionally, the module interfaces to sensing Compatibility devices and detects whether they are ON or OFF. The module also converts ON/OFF signals from user devices to appropriate logic level for use in the processor.

  • Page 55: Module Features That Can Be Configured

    Using the Sequence of Events Module Features Module Features That Table 5.2 lists features on the Sequence of Events module that can be configured. Can Be Configured Table 5.2 This feature: is described on: Two Operational Modes Enable CST Capture Chatter Detection Software Configurable Input Filters 5-10...
  • Page 56 Using the Sequence of Events Module Features During initial module configuration, you must choose a communication format for the module. The communication format determines the mode in which your module operates. The example screen below shows how to choose your module’s communication format and, thus, operational mode.

  • Page 57: Enable Cst Capture

    Using the Sequence of Events Module Features Enable CST Capture Enable CST Capture instructs the Sequence of Events module to timestamp specific input points transitions. You can use this feature to instruct the module to capture the CST when the inputs transition from: •...
  • Page 58 Using the Sequence of Events Module Features Use the Configuration tab in RSLogix 5000 to set Enable CST Capture, as shown in the example below. Click the Configuration tab. • Click on the individual boxes for each input point to enable CST Capture for that point.

  • Page 59: Latch Cst

    Using the Sequence of Events Module Features Latch CST Latch CST can be used to prevent the Sequence of Events module from overwriting input data once it is timestamped. • If Latch CST is enabled, the module only timestamps a specific number of input transitions(e.g., the first transition in CST Per Point mode) and ignores future input transitions (at least until the controller clears the timestamp data already...

  • Page 60: Chatter Detection

    Using the Sequence of Events Module Features Chatter Detection To detect a faulty input device wired to the Sequence of Events module, the module can use Chatter Detection to detect a chattering signal from a device connected to one of its inputs (e.g., rapid transitions from a failed contact) and ignore the data.
  • Page 61 Using the Sequence of Events Module Features Use the Configuration tab in RSLogix 5000 to configure Chatter Detection, as shown in the example below. A. Type the number of events. Range is 2-127 events. Use 0 to disable this feature. B.

  • Page 62: Software Configurable Input Filters

    5-10 Using the Sequence of Events Module Features Software Configurable Input Filters To account for hard contact “bounce”, you can configure ON to OFF and OFF to ON input filter times in RSLogix 5000 for your Sequence of Events module. These filters define how long an input transition must remain in the new state before the module considers the transition valid.
  • Page 63 Using the Sequence of Events Module Features 5-11 In the example, a Sequence of Events module: • is Enable CST Capture-enabled for all of its points • uses a 2ms input filter setting for OFF to ON transitions Three possible scenarios can result after an input transitioning from OFF to ON in the given circumstances.
  • Page 64 5-12 Using the Sequence of Events Module Features • Scenario #3 – The input turns ON but turns OFF before 2ms (length of the input filter setting) elapses. In this case, the Sequence of Events module continues to scan the input every 25µs for 4x the length of the input filter setting (i.e., for 8ms).

  • Page 65: Electronic Keying

    Using the Sequence of Events Module Features 5-13 Electronic Keying Instead of plastic mechanical backplane keys, electronic keying allows the ControlLogix system to control what modules belong in the various slots of a configured system. During module configuration, you must choose one of the following keying options for your Sequence of Events module: •...
  • Page 66 5-14 Using the Sequence of Events Module Features Table 5.4 describes the keying options available with your module. Table 5.4 Keying option: Definition: Exact Match All of the parameters listed above must match or the inserted module will reject a connection to the controller.

  • Page 67: Module Inhibiting

    Using the Sequence of Events Module Features 5-15 Module Inhibiting With module inhibiting, you can indefinitely suspend a connection between an owner-controller and a Sequence of Events module. This process can occur in the following way: • You write configuration for a Sequence of Events module but inhibit the module to prevent it from communicating with the owner-controller.

  • Page 68: Other Inherent Module Features

    5-16 Using the Sequence of Events Module Features Other Inherent Table 5.5 lists features on the Sequence of Events module that cannot be configured. Module Features Table 5.5 This feature: is described on: Removal and Insertion Under Power (RIUP) 5-16 Module Fault Reporting 5-16 Fully Software Configurable...

  • Page 69: Fully Software Configurable

    Using the Sequence of Events Module Features 5-17 Fully Software Configurable RSLogix 5000 uses a custom, easily understood interface to write configuration. All module features are enabled or disabled through the I/O configuration portion of the software. You can also use the software to interrogate your Sequence of Events module to retrieve: •...

  • Page 70: Status Indicator Information

    5-18 Using the Sequence of Events Module Features Status Indicator Information Each Sequence of Events module has LED status indicators on the front of the module that allows you to check the module health and operational status. Table 5.6 describes the module’s LED status indicators: Table 5.6 Status:...

  • Page 71: Full Class I Division 2 Compliance

    Using the Sequence of Events Module Features 5-19 Full Class I Division 2 Compliance The Sequence of Events module maintains CSA Class I Division 2 system certification. This allows the ControlLogix system to be placed in an environment other than only a 100% hazard free. Modules should not be pulled under power, nor IMPORTANT should a powered RTB be removed, in a Class I...
  • Page 72 5-20 Using the Sequence of Events Module Features Notes: Publication 1756-UM528A-EN-P - April 2004...

  • Page 73: Using The Sequence Of Events

    Chapter Using The Sequence of Events Module in CST Per Point Mode What This Chapter This chapter describes how to use the Sequence of Events module in CST Per Point mode. Contains Table 6.1 For information on: See page: Overview of the Mode What Are The Typical Applications Where CST Per Point Mode is Used? Configuring the Module for CST Per Point Mode...

  • Page 74: How Does The Module Store Timestamp Data In Cst

    Using The Sequence of Events Module in CST Per Point Mode How Does the Module With each timestamped transition, the Sequence of Events module stores data for that point. An overview of how the module stores Store Timestamp Data in timestamp data in CST Per Point mode is shown in Figure 6.1: CST Per Point Mode? Figure 6.1...
  • Page 75 Using The Sequence of Events Module in CST Per Point Mode When the Sequence of Events module operates in CST Per Point mode, generally the following occurs: 1. You configure the Sequence of Events module to operate in CST Per Point mode via the Communication Format selection. 2.

  • Page 76: Per Point Mode

    Using The Sequence of Events Module in CST Per Point Mode What Are The Typical CST Per Point mode is typically used in applications that need to determine relative first fault detection after an event cascade occurs. Applications Where CST The Sequence of Events module can provide unique timestamps for Per Point Mode is Used? separate input transitions as long as they occur 25µs apart;...

  • Page 77: Choosing A Communications Format

    Using The Sequence of Events Module in CST Per Point Mode Choosing a Communications Format During initial module configuration, you must choose a communication format for the module. The communications format determines what operational mode your Sequence of Events module uses and, consequently, what tags RSLogix 5000 generates when configuration is complete.

  • Page 78: Using Latch Cst In Cst Per Point Mode

    Using The Sequence of Events Module in CST Per Point Mode Using Latch CST in CST Per Point Mode When enabled, Latch CST prevents the Sequence of Events module from overwriting recorded timestamp data once a transition occurs. This feature is set on a module-wide basis and is enabled by default.

  • Page 79: Using Enable Cst Capture In Cst Per Point Mode

    Using The Sequence of Events Module in CST Per Point Mode Using Enable CST Capture in CST Per Point Mode Regardless of operating mode, Enable CST Capture causes the Sequence of Events module to timestamp specific input transitions. However, keep the following in mind when using this feature in CST Per Point mode: •...

  • Page 80: Managing The Data In Cst Per Point Mode

    Using The Sequence of Events Module in CST Per Point Mode Managing the Data in CST In CST Per Point Mode, the Sequence of Events module sends all of its input data to the controller immediately after an input transition has Per Point Mode been timestamped and at each RPI.
  • Page 81 Using The Sequence of Events Module in CST Per Point Mode Table 6.3 describes the data that is sent for each input. These tags are sent to the controller immediately after the module timestamps a transition on any input and at each RPI. Table 6.3 Input Tags in CST Per Point Mode Tag name: Set on a Per Point or...

  • Page 82: Copying Relevant Input Data To A Separate Data Structure

    6-10 Using The Sequence of Events Module in CST Per Point Mode Table 6.3 Input Tags in CST Per Point Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.ReturningUCTTime Modulewide Indicates if timestamps are in UCT format rather than CST. 0 = CST format 1 = UCT format For more information on UCT format, see Appendix B.
  • Page 83 Using The Sequence of Events Module in CST Per Point Mode 6-11 Figure 6.3 shows when to use the COP instruction. In this example, the Sequence of Events 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.

  • Page 84: Acknowledging Latched Timestamp Data

    6-12 Using The Sequence of Events Module in CST Per Point Mode Acknowledging Latched Timestamp Data In most cases, Latch CST is enabled when the module operates in CST Per Point mode. 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;...
  • Page 85 Using The Sequence of Events Module in CST Per Point Mode 6-13 Figure 6.5 shows when to clear data from the Sequence of Events module. In this example, the Sequence of Events module sent input data to the controller, and the controller copied the relevant input data to a separate structure.

  • Page 86: Sorting The Data

    Eventually, you will need to determine the order of events that occurred in a cascade. You must use a Sort routine to determine the order of events. Rockwell Automation offers a sample sort routine that you can use to determine the order of events in an event cascade. For more information, see Appendix E, Using Sample RSLogix 5000 Projects with the Sequence of Events Module.

  • Page 87: Using The Sequence Of Events Module In Fifo Mode

    Chapter Using The Sequence of Events Module in FIFO Mode What This Chapter Contains This chapter describes how to use the Sequence of Events module in FIFO mode. Table 7.1 For information on: See page: Overview of the Mode What the Typical Applications Where FIFO Mode is Used? Configuring the Module for FIFO Mode Retrieving Data in FIFO Mode 7-10...

  • Page 88: How Does The On-Board Buffer Work In Fifo Mode

    Using The Sequence of Events Module in FIFO Mode How Does the On-Board The Sequence of Events module’s on-board buffer stores data for up to 160 timestamped transitions at one time. For each transition, Buffer Work in FIFO Mode? specific information is recorded, as shown below and described on page 7-10.
  • Page 89 Using The Sequence of Events Module in FIFO Mode Once data is stored on the module, the controller must retrieve it. Typically, the controller retrieves data from the first slot in the on-board buffer; the data in the first slot is also known as the current event.

  • Page 90: What The Typical Applications Where Fifo Mode Is Used

    Using The Sequence of Events Module in FIFO Mode What the Typical FIFO mode is intended for use in applications where multiple transitions occur on multiple inputs in relatively rapid succession (i.e., Applications Where FIFO faster than the controller can acknowledge the data as the transitions Mode is Used? occur).

  • Page 91: Choosing A Communications Format

    Using The Sequence of Events Module in FIFO Mode Choosing a Communications Format During initial module configuration, you must choose a communication format for the module. The communications format determines what operational mode your Sequence of Events module uses and, consequently, what tags RSLogix 5000 generates when configuration is complete.

  • Page 92: Using Latch Cst In Fifo Mode

    Using The Sequence of Events Module in FIFO Mode Using Latch CST in FIFO Mode When enabled, Latch CST prevents the Sequence of Events module from overwriting input data once it is timestamped. This feature is set on a module-wide basis and is enabled by default. Table 7.2 describes how Latch CST affects the module in FIFO mode.
  • Page 93 Using The Sequence of Events Module in FIFO Mode Table 7.2 If Latch CST is the following occurs Disabled The Sequence of Events module timestamps input transitions as they occur, and stores the data for those transitions in its on-board buffer. However, the module can only store the data for up to 160 transitions in its on-board storage buffers.
  • Page 94 Using The Sequence of Events Module in FIFO Mode We suggest you monitor the I.EventOverflow bits to IMPORTANT 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 Latch CST, as shown in the example below.

  • Page 95: Using Enable Cst Capture In Fifo Mode

    Using The Sequence of Events Module in FIFO Mode Using Enable CST Capture in FIFO Mode Regardless of operating mode, Enable CST Capture causes the Sequence of Events module to timestamp specific input transitions. However, keep the following in mind when using this feature in FIFO mode: •...

  • Page 96: Managing The Data In Fifo Mode

    7-10 Using The Sequence of Events Module in FIFO Mode Managing the Data in In FIFO Mode, the Sequence of Events module sends input data for the current event to the controller immediately after the first input FIFO Mode transition has been timestamped and at each RPI. You must manage the data coming from the Sequence of Events module.
  • Page 97 Using The Sequence of Events Module in FIFO Mode 7-11 Table 7.3 Input Tags in FIFO Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.Fault Indicates if a fault has occurred for the input. Per point 0 = no fault 1 = fault –...
  • Page 98 7-12 Using The Sequence of Events Module in FIFO Mode Table 7.3 Input Tags in FIFO Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.EventNumber Running count of the timestamped input transitions; this tag increments by one with Per point each new event.
  • Page 99 Using The Sequence of Events Module in FIFO Mode 7-13 Standard Retrieval In Standard Retrieval, the controller retrieves the data for each event in the order in which the events occurred. This retrieval method includes the following: 1. At each RPI, the Sequence of Events produces the current event in its on-board buffer.

  • Page 100: Producing Current Event Data

    7-14 Using The Sequence of Events Module in FIFO Mode Producing Current Event Data Figure 7.2 shows an example of the Sequence of Events module producing the current data for the controller to retrieve it. Remember, the current event is data that the IMPORTANT module is currently producing from its on-board buffer at each RPI.

  • Page 101: Copying Relevant Input Data To A Separate Data Structure

    Using The Sequence of Events Module in FIFO Mode 7-15 Copying Relevant Input Data to a Separate Data Structure At each RPI, the Sequence of Events module sends input data for the current event to the controller; the data is stored in the controller tags.
  • Page 102 7-16 Using The Sequence of Events Module in FIFO Mode Figure 7.3 shows when to use the COP or CPS instruction. In this example, the Sequence of Events module has produced current event data for the controller at the RPI. The controller copies the relevant input data from the controller tags to a separate data structure.

  • Page 103: Acknowledging Latched Timestamp Data

    Using The Sequence of Events Module in FIFO Mode 7-17 Acknowledging Latched Timestamp Data In FIFO mode, the Sequence of Events produces data for the current event data at each RPI until the data is acknowledged and, thus, cleared from the buffer. To clear data for the current event, and begin producing data for the next event in the Sequence of Events module’s on-board buffer when using Standard Retrieval, you must copy the event number...
  • Page 104 7-18 Using The Sequence of Events Module in FIFO Mode 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. The Sequence of Events module still timestamps input transitions for any events that occur on Enable CST Capture-enabled inputs.
  • Page 105 Using The Sequence of Events Module in FIFO Mode 7-19 Additional Module Settings Required with Retrieval by Point Method By default, the Sequence of Events module operates as if the controller will use Standard Retrieval to retrieve data. To use the Retrieval by Point method, you must change the following two tags in the module’s output word: •...

  • Page 106: Clearing All Data From The Module's Buffers At Once

    7-20 Using The Sequence of Events Module in FIFO Mode Clearing All Data From the If necessary, you can reset the events in the Sequence of Events module’s on-board buffers, in effect clearing all data from Module’s Buffers At Once previously timestamped transitions.

  • Page 107: What This Chapter Contains

    Chapter Troubleshooting the Sequence of Events Module What This Chapter This chapter describes how to troubleshoot the Sequence of Events module. Contains Table 8.1 For information on: See page: Using LED Status Indicators Using RSLogix 5000 To Troubleshoot the Module Using LED Status Your Sequence of Events module has yellow indicators that show individual I/O state and a bi-colored (red/green) indicator that...

  • Page 108: Using Rslogix 5000 To Troubleshoot The Module

    Troubleshooting the Sequence of Events Module Table 8.2 describes how to use the Sequence of Events module’s LED status indicators. Table 8.2 This indicator: With this display: Means: Take this action: Steady green light The inputs are being multicast and in normal None operating state.
  • Page 109 Troubleshooting the Sequence of Events Module • Message in a screen’s status line Status line provides information on the module’s fault and on the connection to the module • Notification in the Tag Editor - General module faults are also reported in the Tag Editor.

  • Page 110: Determining Fault Type

    Troubleshooting the Sequence of Events Module Determining Fault Type When you are monitoring a module’s configuration properties in RSLogix 5000 and receive a Communications fault message, the Connection page lists the type of fault. The fault type is listed here For a detailed listing of the possible faults, their causes and suggested solutions, see Module Faults in the online help.

  • Page 111: 1756-Ib16Isoe Specifications

    Appendix Specifications and Module Block Diagrams 1756-IB16ISOE Number of Inputs 16 (Individually isolated) Specifications Module Location 1756 ControlLogix Chassis Backplane Current 295mA @ 5.1V dc & 2mA @ 24V dc Backplane Power 1.5W Maximum Power Dissipation 5.5W @ 60 (Module) Thermal Dissipation 17.22 BTU/hr.
  • Page 112 Specifications and Module Block Diagrams Conductors Wire Size #22 to #14 AWG (0.324 to 2.08 sq. mm) stranded 3/64 inch (1.2mm) insulation maximum Category Screwdriver Blade Width for 1/8 inch (3.2mm) maximum Environmental Conditions Operational IEC 60068-2-1 (Test Ad, Operating Cold), Temperature IEC 60068-2-2 (Test Bd, Operating Dry Heat), IEC 60068-2-14 (Test Nb, Operating Thermal Shock):...
  • Page 113 Specifications and Module Block Diagrams EFT/B Immunity IEC 61000-4-4: ±4kV at 2.5kHz on signal ports Surge Transient IEC 61000-4-5: Immunity ±1kV line-line (DM) and ±2kV line-earth (CM) on signal ports Conducted RF Immunity IEC 61000-4-6: 10Vrms with 1kHz sine-wave 80%AM from 150kHz to 80MHz Oscillatory Surge IEEE C37.90.1:...

  • Page 114: 1756-Ib16Isoe Module Block Diagram

    Specifications and Module Block Diagrams 1756-IB16ISOE Module Figure A.1 shows the Sequence of Events module block diagram. Block Diagram Figure A.1 Isolation Barrier 125V dc or Serial 5V power FLASH SRAM 24/48V dc EEPROM input circuit BF532 Backplane Dualport OPTO Blackfin ASIC Isolation...

  • Page 115: 1756-Ih16Isoe Specifications

    Specifications and Module Block Diagrams 1756-IH16ISOE Number of Inputs 16 (Individually isolated) Specifications Module Location 1756 ControlLogix Chassis Backplane Current 275mA @ 5.1V dc & 2mA @ 24V dc Backplane Power 1.3W Maximum Power Dissipation 5.5W @ 60 (Module) Thermal Dissipation 17.22 BTU/hr.
  • Page 116 Specifications and Module Block Diagrams Conductors Wire Size #22 to #14 AWG (0.324 to 2.08 sq. mm) stranded 3/64 inch (1.2mm) insulation maximum Category Screwdriver Blade Width for 1/8 inch (3.2mm) maximum Environmental Conditions Operational IEC 60068-2-1 (Test Ad, Operating Cold), Temperature IEC 60068-2-2 (Test Bd, Operating Dry Heat), IEC 60068-2-14 (Test Nb, Operating Thermal Shock):...
  • Page 117 Specifications and Module Block Diagrams EFT/B Immunity IEC 61000-4-4: ±4kV at 2.5kHz on signal ports Surge Transient IEC 61000-4-5: Immunity ±1kV line-line (DM) and ±2kV line-earth (CM) on signal ports Conducted RF Immunity IEC 61000-4-6: 10Vrms with 1kHz sine-wave 80%AM from 150kHz to 80MHz Oscillatory Surge IEEE C37.90.1:...

  • Page 118: 1756-Ih16Isoe Module Block Diagram

    Specifications and Module Block Diagrams 1756-IH16ISOE Module Figure A.2 shows the Sequence of Events module block diagram. Block Diagram Figure A.2 Isolation Barrier 125V dc or Serial 5V power FLASH SRAM 24/48V dc EEPROM input circuit BF532 Backplane Dualport OPTO Blackfin ASIC Isolation...

  • Page 119: Appendix B Overview

    Appendix Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System Overview Up to this point in this manual, the ControlLogix Sequence of Events module is described as being used for Relative First Fault Detection. In Relative First Fault Detection, the controller sorts the timestamps sent by Sequence of Events module(s) to determine which transition occurred first in an event cascade.

  • Page 120: What Is The 1756Hp-Gps Module

    Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System What is the 1756HP-GPS The 1756HP-GPS module is an integrated GPS product that makes use of Global Positioning System (GPS) technology to derive accurate time Module? that is synchronized with the atomic clocks located on the GPS satellites.
  • Page 121 Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System Using a 1756HP-GPS module, you can convert the CST-format timestamps, received from a ControlLogix Sequence of Events module, into a Gregorian wall clock time (WCT) that is easily understood.

  • Page 122: Determining The Absolute First Fault Across Multiple Chassis

    Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System Determining the Absolute For simplicity’s sake, Figure B.2 shows a system that determines the absolute first fault of devices connected to a single Sequence of Events First Fault Across Multiple module in a local chassis.
  • Page 123 Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System In this example, the following are required: • The CST in each ControlLogix system must be synchronized across chassis. • Each ControlLogix system must contain a 1756HP-GPS module. •...

  • Page 124: How Does The Controllogix Controller Retrieve Converted Value From The 1756Hp-Gps Module

    Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System How Does the ControlLogix Once a ControlLogix controller receives the timestamps from an event cascade, it may send them to the 1756HP-GPS via a message Controller Retrieve instruction for conversion to either the following formats: Converted Value from the •...
  • Page 125 Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System The screen below shows the Configuration tab for an example MSG. Table B.2 shows the two formats in which a 1756HP-GPS may return timestamp data. Table B.2 Field Bytes Description...

  • Page 126: Converting Timestamps From Cst Format To Universal Coordinated Time Format

    Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System Converting Timestamps By default, the Sequence of Events module uses the CST to timestamp input transitions in CST Per Point mode. You can configure the from CST Format to module to convert CST timestamps to UCT timestamps before sending Universal Coordinated the data to the owner-controller.
  • Page 127 Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System You do NOT need to copy the timestamp pair from the 1756HP-GPS module to the Sequence of Events module’s output tags if: • you convert CST times to UTC manually via messaging to the 1756HP-GPS module.
  • Page 128 B-10 Integrating The HiProm GPS Module (1756HP-GPS) into a ControlLogix Sequence of Events Module System Notes: Publication 1756-UM528A-EN-P - April 2004...

  • Page 129: Appendix C Overview

    Appendix Synchronizing CSTs Across Multiple Chassis Overview While each ControlLogix chassis uses the CST on its backplane to serve as the single time reference for all modules in the chassis, the CSTs between separate chassis are different from each other by default.
  • Page 130 Synchronizing CSTs Across Multiple Chassis • The controller in the local chassis typically serves as the time master for its chassis; the 1756-SYNCH module in the local chassis can also serve as the time master. • The 1756-SYNCH module in the local chassis sends a common CST time reference to 1756-SYNCH modules in remote chassis over a fiber optic connection.

  • Page 131: Configuring 1756-Synch Modules In Rslogix 5000

    Synchronizing CSTs Across Multiple Chassis Configuring 1756-SYNCH Modules in RSLogix 5000 The SynchLink module can be configured for multiple mastership and slave roles with respect to the Coordinated System Time and the SynchLink. The 1756-SYNCH modules used in the example on page C-2 require specific configuration for the system to work.

  • Page 132: Synchronizing Chassis In Controllogix Redundancy Systems

    Synchronizing CSTs Across Multiple Chassis Synchronizing Chassis in When Sequence of Events modules are used in ControlLogix Redundancy systems, the chassis that contain the Sequence of ControlLogix Redundancy Events modules must be synchronized. Systems Figure C.3 on page C-5 shows an example ControlLogix redundancy system that uses Sequence of Events modules in some of its remote chassis to timestamp input transitions and 1756-SYNCH modules to synchronize CSTs among those remote chassis.

  • Page 133: Related Synchlink Documentation

    Synchronizing CSTs Across Multiple Chassis Figure C.3 Each chassis contains: • 1756-L55 controller, version 11.71 Primary chassis Secondary chassis • 1757-SRM module • 1756-CNB(R) module (series D, version 5.23 or greater) These chassis are NOT synchronized. ControlNet 43834 SynchLink Chassis contains: Each chassis contains: Chassis containing 1756-CNB(R) •...
  • Page 134 Synchronizing CSTs Across Multiple Chassis Notes: Publication 1756-UM528A-EN-P - April 2004...

  • Page 135: Fault And Status Reporting Between The Module And Controllers

    Appendix Using Module Tags Fault and Status Reporting Sequence of Events modules multicast fault/status data to the owner-controller. The module maintains a Module Fault Word, the Between the Module highest level of fault reporting. and Controllers Table D.1 describes the tag that can be examined in ladder logic to indicate when a fault has occurred for your Sequence of Events module: Table D.1...

  • Page 136: Module Tag Names And Definitions

    Using Module Tags Module Tag Names The tags associated with the Sequence of Events module depends on the type of module and the Communications Format chosen and Definitions during configuration. For each operational mode, there are three sets of tags: •...
  • Page 137 Using Module Tags Table D.2 Configuration Tags in CST Per Point Mode Tag name: Type: Description: C.CaptureOnOff DINT Enables capturing ON to OFF events on a per point basis. If disabled (i.e., set to 0), that point will not record timestamp data for ON to OFF input transitions. 0 = CST Capture disabled for ON to OFF input transitions - This option is useful if you want to avoid using buffer space on the Sequence of Events module for events in which you have no interest.
  • Page 138 Using Module Tags Input Tags Table D.3 describes the input tags generated in RSLogix 5000 when you use the Sequence of Events module in CST Per Point Mode. Table D.3 Input Tags in CST Per Point Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.Fault...
  • Page 139 Using Module Tags Table D.3 Input Tags in CST Per Point Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.ReturningUCTTime Modulewide Indicates if timestamps are in UCT format rather than CST. 0 = CST format 1 = UCT format For more information on UCT format, see Appendix B.
  • Page 140 Using Module Tags Output Tags Table D.4 describes the output tags generated in RSLogix 5000 when you use the Sequence of Events module in CST Per Point Mode. Table D.4 Output Tags in CST Per Point Mode Tag name: Type: Description: O.EventAck DINT...

  • Page 141: Tags Used In Fifo Mode

    Using Module Tags Table D.4 Output Tags in CST Per Point Mode Tag name: Type: Description: O.UCTTime[2] DINT [2] These tags are used to configure the Sequence of Events module to send timestamps to the controller in UCT format. In this case, you must copy a pair of timestamp values from O.CSTTime[2] DINT [2] the 1756HP-GPS module (one in UCT format and the other a corresponding CST format...
  • Page 142 Using Module Tags Table D.5 Configuration Tags in FIFO Mode Tag name: Type: Description: C.FilterOnOff SINT Sets the ON to OFF filter time for all 16 inputs. Times are set in 1ms increments from 0ms to 50ms. 0 = no filtering For more information on Software Configurable Input Filters, see page 5-10.
  • Page 143 Using Module Tags Input Tags Table D.6 describes the input tags generated in RSLogix 5000 when you use the Sequence of Events module in FIFO Mode. Table D.6 Input Tags in FIFO Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.Fault...
  • Page 144 D-10 Using Module Tags Table D.6 Input Tags in FIFO Mode Tag name: Set on a Per Point or Description: Modulewide basis: I.CSTTimestamp[2] Per event 64-bit CST timestamp in CST format for the event. This value is cleared after the data has been acknowledged via the O.EventAck tag. For more information on clearing timestamp data, see page 7-17.
  • Page 145 Using Module Tags D-11 Output Tags Table D.7 describes the output tags generated in RSLogix 5000 when you use the Sequence of Events module in FIFO Mode. Table D.7 Output Tags in FIFO Mode Tag name: Type: Description: O.EventAck.x DINT Clears the current event data from the Sequence of Events module.
  • Page 146 D-12 Using Module Tags Table D.7 Output Tags in FIFO Mode Tag name: Type: Description: O.UCTTime[2] DINT [2] These tags are used to configure the Sequence of Events module to send timestamps to the controller in UCT format. In this case, you must copy a pair of timestamp values from O.CSTTime[2] DINT [2] the 1756HP-GPS module (one in UCT format and the other a corresponding CST format...

  • Page 147: Appendix E Overview

    Using Sample RSLogix 5000 Projects with the Sequence of Events Module Overview Rockwell Automation offers several sample RSLogix 5000 projects to use with your Sequence of Events module. The module timestamps input transitions and provides that data to its owner-controller.

  • Page 148: Accessing The Sample Projects

    Sample Projects • RSLogix 5000 CD that shipped with v13 • RSLogix 5000 software via the Vendor Sample Project PDF accessible through online help • Rockwell Automation Technical Support Knowledgebase, available at: – http://support.rockwellautomation.com/ – Click on the Knowledgebase link.
  • Page 149 Glossary Absolute time Time represented in an easily understood format (i.e., Gregorian format). You must use the 1756HP-GPS module to convert timestamps to absolute time. In this format, time is represented in year, month, day, hour, minute, second and microsecond. Communications format Format that defines the operational mode used on the Sequence of Events and, consequently, the type of information transferred...
  • Page 150 Glossary Direct connection A connection where the controller establishes an individual connection with the Sequence of Events module. Disable keying An electronic keying protection mode that requires no attributes of the physical module and the module configured in the software to match Download The process of transferring the contents of a project on the...
  • Page 151 Glossary Interface module (IFM) A module that uses prewired cable to connect wiring to an I/O module Major revision A module revision that is updated any time there is a functional change to the module Minor revision A module revision that is updated any time there is a change to the module that does not affect its function or interface Owner-controller The controller that creates and stores the primary configuration and...
  • Page 152 Glossary Removable terminal block (RTB) Field wiring connector for Sequence of Events modules Requested packet interval (RPI) The maximum amount of time between broadcasts of I/O data Run mode In this mode, the following events occur: • Controller program is executing •...
  • Page 153 Index 1-1–1-3 coordinated system time (CST) 1-3, 4-5, 5-3, 6-1– CST Per Point mode absolute time 6-14 B-4–B-5 determining across chassis 6-9–6-10 input tags 5-19 agency certifications 6-8–6-13 managing data in this mode 2-4–2-5 ASIC delay 6-14 sorting data typical applications current event backplane connector bandwidth...
  • Page 154 Index product type serial number 2-4–2-5 hardware delay status vendor ID WHO service module status 4-6, 5-15 inhibiting the module retrieving 5-10–5-12 input filters 5-18 module status indicators 2-4–2-5 input filter delay setting filter times in RSLogix 5000 input tags 6-9–6-10, D-4 in CST Per Point mode network update time (NUT)
  • Page 155 Index removable terminal block (RTB) RSNetWorx for ControlNet assembling the RTB and housing adding a new module to a remote chassis cabinet size consideration with the connected via ControlNet extended-depth housing Using with RSLogix 5000 3-4–3-5 connecting wiring 3-5, 3-8–3-9 extended-depth housing 3-10–3-11 installing...
  • Page 156 Index using the interface module (IFM) using the removable terminal block (RTB) warnings preventing electrostatic discharge 3-4–3-5 using the RTB Preface-3 using the spring clamp RTB wiring connections wiring the module recommendations for wiring RTB using the cage clamp RTB Publication 1756-UM528A-EN-P - April 2004...
  • Page 157 ___No, there is no need to contact me ___Yes, please call me ___Yes, please e-mail me at _______________________ ___Yes, please contact me via _____________________ Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705 Fax: 440-646-3525 E-mail: RADocumentComments@ra.rockwell.com Publication CIG-CO521C-EN-P- May 2003...
  • Page 158 PLEASE FASTEN HERE (DO NOT STAPLE) Other Comments PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE 1 ALLEN-BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705...
  • Page 160 (see phone number above to obtain one) to your distributor in order to complete the return process. Outside United Please contact your local Rockwell Automation representative for States return procedure. Publication 1756-UM528A-EN-P - April 2004 PN 957859-83 Copyright © 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

This manual is also suitable for:

Allen-bradley controllogix 1756-ih16isoe

Table of Contents