Home

1756-UM528A-EN-P, ControlLogix Sequence of Events Module

1. Figure 1 1 7 id Indicators SOE INPUT Locking tab 3 ST 012345670 ST 8 9101012181415 K ki 8 Removable terminal Jumper block bar E a a fal e e D ay 8 I a a a S a eg e e qd o 9 Top and mee a Sar bottom o a i e Slots m o guides Connector tee e QD D pins for o eD e o keying 2 E e e the 5 j RTB 5 DL e e o OL e a o o o Z a p i nez Table 1 3 Physical Features on the ControlLogix Sequence of Events Module Physical Feature Backplane connector Description The backplane connector interface for the ControlLogix system connects the module to the ControlLogix backplane Connector pins input output power and grounding connections are made to the module through these pins with the use of an RTB or IFM Locking tab The locking tab anchors the RTB or IFM cable on the module maintaining wiring connections Slots for keying Mechanically keys the RTB to prevent inadvertently making the wrong wire connections to your module Status indicators Indicators display the status of communication module health and input output devices Use these indicators to help in troubleshooting Top and bottom guides Guides provide assistance in seat
2. lt Strain relief area 20859 M Installing the Sequence of Events Module 3 5 Spring Clamp RTB 1 Strip 7 16 inch 11mm maximum length of wire 2 Insert the screwdriver into the inner hole of the RTB 3 Insert the wire into the open terminal and remove the screwdriver Figure 3 6 a alfalfa ry fe fa fa FO FERE PEER lt Strain relief area Siim Recommendations for Wiring Your RTB Consider the following guidelines when wiring your RTB e Begin wiring the RTB at the bottom terminals and move up e Use a tie to secure the wires in the strain relief area of the RTB e The jumper bar part number is 97739201 Contact your local Rockwell Automation sales representative to order additional jumper bars if necessary e Order and use an extended depth housing Catalog number 1756 TBE for applications that require heavy gauge wiring For more information see page 3 8 Publication 1756 UM528A EN P April 2004 3 6 Installing the Sequence of Events Module Wiring the Sequence of Use Figure 3 7 to wire your Sequence of Events module Events Module A If you connect or disconnect wiring while the field side power is on an electrical arc can occur This could cause an explosion in hazardous location installations Be sure that powe
3. J 3 Module sends input 5 1 Input 2 transitions 2 Module timestamps data to the controller Controller tags H from OFF to ON the transition C Far Z lt Uata l es 4 0000000 4 Controller o m C 0000000 copies i feturning ime To 0107100 E i rmestamplT6 O1FOnl2 0000000 Fault relevant UTimestamp T6 On0fft 0000000 data from oO Ciaooo Data Separate array NewData controller 3 S TEventOverlow tags toa b ReturningUCTTime separate s J ooo TEventNumber array 0000000 I Timestamp 16 0ffOn 2 J J l Timestamp 16 0n0ff 2 2 42796 Your application determines what input data should be copied from the controller tags to a separate data structure Although you can copy all the input data to another array typically only the data from specific tags is copied Figure 6 4 shows an example of ladder logic in which the controller only moves OFF to ON timestamp data for inputs 0 to 3 from the controller tags to a separate data structure named myarray The data in the myarray structure is then moved to another array used to sort the data In this example 32 bits of each 64 bit timestamp are moved to the new array Figure 6 4 Ov Ov Move Move Move Source Local 2 l Timestamp 0 OffOn 0 Source Local 2 1 Timestamp 1 OffOn 0 Source Local2 1 Timestamp 2 OffOn 0 9
4. Figure 3 10 lt 144 73mm gt 5 698in 12 7mm gt lt 131 75mm gt 0 5in lt 3 18mm 0 125in 5 187in lt Rear Surface of ControlLogix Chassis Standard Depth Housing Extended Depth Housing o J k o 41682 IMPORTANT The depth from front of the module to the back of the chassis is as follows standard depth housing 147 91mm 5 823in extended depth housing 157 43mm 6 198in Publication 1756 UM528A EN P April 2004 3 10 Installing the Sequence of Events Module Installing the Removable Terminal Block ATTENTION Install the RTB onto the module to connect wiring Shock hazard exists If the RTB is installed onto the module while the field side power is applied the RTB will be electrically live Do not touch the RTB s terminals Failure to observe this caution may cause personal injury The RTB is designed to support Removal and Insertion Under Power RIUP However when you remove or insert an RTB with field side power applied unintended machine motion or loss of process control can occur Exercise extreme caution when using this feature It is recommended that field side power be removed before installing the RTB onto the module Before installing the RTB make certain e field side wiring of the RTB has been completed e the RTB housing is snapped into place on the RTB
5. Figure 7 3 Sequence of Events module aD ControlLogix controller ee err A o oo 1 Module stores data 2 Module produces Controller ontroller tags I in on board buffer current event data g i Fault 2 Loo o m Newa L j TEventOverlow z a 0710070 Current event 3 Controller icone o o 0100010 copies Benen fo oO 17100770 Fault re evant eRe O o _ 1010010 D t 1 EventsQueuedCount o o wH ie a data from 2 a 0000110 NewUata controller Separate array o o 1100107 EventOverlow aes eee EventNumber ae ea a CSTTimestamp 2 separate o 04 P UCTTimestamp 2 array ep eT T0010 EventPoint a 1110011 EventData o o ReturningUCTTime a 43811 EventsQueuedCount Figure 7 4 shows an example of ladder logic in which the controller only moves the input number I EventPoint and copies the CST timestamp I CSTTimestamp from the controller tags to a separate data structure named Fifo_ExtractDatal Index Figure 7 4 0 Move Source InputPoint sLocal 2 1 EventPoint gt 0 Dest Fifo_ExtractData Index Input_Point 0 Copy File Source CurrentCST sLocal 2 CSTTimestamp O Dest Fifo_ExtractData Index Event_Time 0 Length 2 UsingUCT sLocal2 ReturningUCTTime gt Fifo_ExtractData Index UsingUCT pii Publication 1756 UM528A EN P April 2004 43812 Sequence of Events module Using The Sequence of Events Module in FIFO Mode Acknowledging Latched
6. Status Offline Publication 1756 UM528A EN P April 2004 Configuring the Sequence of Events Module 4 9 Configuring Modules ina Remote Chassis A Right click on 1 0 Configuration B Select New Module oa Module Defined ControlLogix ControlNet Interface modules 1756 CNB or 1756 CNBR or the EtherNet IP Bridge module 1756 ENBT are 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 1 Add a communications module to the local chassis f RSLogix 5000 My_Sequence_of_Events_proje File Edit View Search Logic Communications Too alsia a sme lo Offline I E RUN A No Forces b aoe gt fi No Edits a H Redundancy Sa e Dj i Controller My_Sequence_of Event l A Controller Tags Controller Fault Handler G Power Up Handler B Tasks S E MainTask E3 amp MainProgram Unscheduled Programs 6 6 Motion Groups Ungrouped Axes Trends iJo Data Types ier User Defined p Strings oa Predefined EA New Module 2 Choose a communications module 1756 CNB 1756 CNBR or 1756 ENBT for the local chassis 3 Configure the communications module in the local chassis For more information on the ControlLogix ControlNet Interface modules see the Us
7. 2 0 159 12 1 160 5 Timestamp data 160 Timestamp Event ky Input F w 8 alo SJ Jol ol alolo of gt ogjo 2 2 2 2 gt golo o ojojo oo pan pao pa pan Pa pa Pa n o gt aonla cq Sjen S SIN Fo el i 0159 12 1 160 5 nput State Note that the timestamp data for event 1 has been deleted from the buffer The timestamp from the most recent transition overwrites the data in slot 1 and becomes the current event sent to the controller 43807 1 This table assumes the transition occurs on inputs that have Enable CST Capture enabled If Enable CST Capture is disabled the module does not timestamp transitions on that input and therefore Latch CST does not affect module behavior Publication 1756 UM528A EN P April 2004 7 8 Using The Sequence of Events Module in FIFO Mode IMPORTANT We suggest you monitor the I EventOverflow bits to make sure you are aware of when transitions were either not timestamped or when timestamp data was overwritten Use the Configuration tab in RSLogix 5000 to enable Latch CST as shown in the example below ial Module Properties Local 1 1756 IH16ISOE 1 1 r Input Filter Time Off g
8. clear only the falling edge timestamp e I TimestampI x OnOff e 1 clear only the rising edge timestamp e I TimestampI x OffOn e 2 clear both the falling and rising edge timestamps 2 Change the NewDataAck tag i e O NewDataAck to a rising edge i e set the tag 1 e If the bit 0 change the bit to 1 e If the bit 1 change the bit to 0 wait for at least one RPI and change the bit to 1 The corresponding I EventOverflow and I NewData tags are also cleared Clear all latched data for the Sequence of Events module This transition erases all timestamp data from the module clearing data from all inputs simultaneously Once the data is cleared the module timestamps the first transition in each direction for each input and sends the data to the controller assuming those inputs are configured with Enable CST Capture enabled in each direction To clear all data for the module transition the O ResetEvents tag to 1 If the bit 0 change the bit to 1 If the bit 1 change the bit to 0 wait for at least one RPI and change the bit to 1 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 Now the controller must clear the data from the Sequence of Even
9. with the following constraints e The modules operate in FIFO mode e The controller uses Standard Retrieval to retrieve timestamp data from multiple Sequence of Events modules e Sample of sorting multiple timestamps ST_BubbleSort ACD This project uses two Structured Text subtroutines The project is an example of easily sorting data Mriitttte lable E 1 only briefly describes the sample projects The projects have rung by rung descriptions to explain why the projects were written as they were We recommend you open the projects to see exactly how they were written and how to use them To access the sample projects see page E 2 Publication 1756 UM528A EN P April 2004 E 2 Using Sample RSLogix 5000 Projects with the Sequence of Events Module Accessing the The sample projects are available at the following locations Sample Projects e RSLogix 5000 CD that shipped with v13 e RSLogix 5000 software via the Vendor Sample Project PDF accessible through online help e Rockwell Automation Technical Support Knowledgebase available at http support rockwellautomation com Click on the Knowledgebase link Publication 1756 UM528A EN P April 2004 Glossary Absolute time Time represented in an easily understood format G 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 microseco
10. 3 of Events module you must perform the following steps Add the new module to your RSLogix 5000 project Accept the default configuration or change it to specific configuration for the module Edit configuration for a module when changes are needed Figure 4 1 shows an overview of the configuration process Figure 4 1 Click on the Next Button to Set Specific Configuration NEXT Select a e New module e Major Revision Configure the e Name Slot number Comm format Minor revision Keying choice Clic Use Series of Application Specific Screens Make custom configuration p gt gt choices here Publication 1756 UM528A EN P April 2004 Configuration complete Download configuration to owner controlle Reconfigure module as needed via series of screens or controller tags on the Finish Button to Default Configuration FINISH 41058 Configuring the Sequence of Events Module 4 3 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 9000 Project create a new module and write configuration You can use default configuration or write specific configuration for your application IMPORTANT You must be offline when you create a new modul
11. The 1 0 configuration portion of RSLogix5000 v13 or greater generates the configuration data for each RSLogix 5000 Sequence of Events module in the control system whether the module is located in a local or remote chassis A remote chassis also known as networked contains the Sequence of Events module but not the module s owner controller Remote chassis can be connected to the controller via a scheduled ControlNet or an EtherNet IP network Configuration data is transferred to the controller during the program download and subsequently transferred to the appropriate Sequence of Events modules Sequence of Events modules in the local chassis and modules in a remote chassis that is connected via the EtherNet IP network are ready to run as soon as the configuration data has been downloaded However you must run RSNetWorx for ControlNet to enable Sequence of Events modules in a scheduled ControlNet chassis Running RSNetWorx transfers configuration data to Sequence of Events modules on scheduled ControlNet and establishes a Network Update Time NUT for ControlNet that is compliant with the desired communications options specified for each module during configuration Anytime a controller references a Sequence of Events module in a scheduled ControlNet chassis you must run RSNetWorx to configure ControlNet Follow these general guidelines when configuring Sequence of Events modules 1 Configure all Sequence of Events modules for a given con
12. The module is capable of storing the data for up to 160 input transitions in its on board buffer at a single time However if you retrieve data from the buffer effectively i e retrieve the data before the module timestamps greater than 160 input transitions the module can timestamp an infinite number of input transitions We recommend you use this mode if you want to minimize propagation delay of new input data being reported to the controller For more information on propagation delay see page 2 4 Publication 1756 UM528A EN P April 2004 5 4 Using the Sequence of Events Module Features Use this pull down menu to choose a communication format Publication 1756 UM528A EN P April 2004 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 Module Properties Local 3 1756 IH16ISOE 1 1 ee x Type 1756 IH16ISOE16 Channel Isolated 125 Input Sequence of Events Vendor Allen Bradley Parent Local Name Sequence_of_Events_Module Slot fs a Description z z Comm Fore cst Per Point z CST FIFO Mode Revision Cancel lt B ck Next gt Finish gt gt Help IMPORTANT Once the module is created in your RSLogix 5000 project you cannot change the communicat
13. When the controller attempts to connect to and configure a Sequence of Events module e g after program download the module compares the following parameters before allowing the connection and configuration to be accepted e Vendor e Product Type e Product Code e Major Revision Change that affects the module s function or RSLogix 5000 interface e Minor Revision Change that does not affect the module s intended function or RSLogix 5000 interface The comparison is made between the keying information present in the module and the keying information in the controller s program preventing the inadvertent operation of a system with the wrong module in the wrong slot For example if you select Exact Match and a module with revision 1 2 is placed in a location configured for a module with revision 1 4 the controller does not make a connection to the new module because of the mismatched revisions Publication 1756 UM528A EN P April 2004 5 14 Using the Sequence of Events Module Features Table 5 4 Keying option Exact Match Table 5 4 describes the keying options available with your module Definition All of the parameters listed above must match or the inserted module will reject a connection to the controller Compatible Module The Compatible Match mode allows a Sequence of Events module to determine whether it can emulate the module defined in the configuration sent from the controller With Sequence of
14. e the RTB housing door is closed e the locking tab at the top of the module is unlocked 1 Align the top bottom and left side guides of the RTB with the guides on the module m _ 6 0 Sew EN Ey EN sah N N Se t oss N EN HES Eh W Top guide GZ ot ey AA P P LEG AWAAZZR Left side guides Bottom guide Publication 1756 UM528A EN P April 2004 20853 M 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 3 12 Installing the Sequence of Events Module Removing the Removable If you need to remove the module from the chassis you must first Terminal Block remove the RTB from the module Shock hazard exists If the RTB is removed from the module while the field side power is applied the module will be electrically live Do not touch the RTB s terminals Failure to observe this caution may cause personal injury The RTB is designed to support Removal and Insertion Under Power RIUP However when you remove or insert an RTB with field side pow
15. the module sends the data for that specific event as well as the status of all the other points on the module to the controller and at every subsequent RPI until the data is acknowledged e As subsequent events occur after the first the module timestamps the transition and records the data for that event in its on board buffer Use the Configuration tab in RSLogix 5000 to set Enable CST Capture as shown in the example below ial Module Properties Local 1 1756 IH16ISOE 1 1 ackplane a Input Filter Time Beset AUCST 5 Enable CST Capture Chatter Detectio Point Off gt On On gt Off Off gt On On gt Off No of Events Time o oa 0 v O 0 t 1 Vv m 0 C 2 M m E j Module Configuration Bits 3 E 0 4 M m 0 C I Latch CST 5 Vv m 0 t 6 Vv m 0 C 7 M o c 8 Vv CL 0 if 4 gt Status Offline Cancel Apply Help Publication 1756 UM528A EN P April 2004 7 10 Using The Sequence of Events Module in FIFO Mode Managing the Data in FIFO Mode Publication 1756 UM528A EN P April 2004 In FIFO Mode the Sequence of Events module sends input data for the current event to the controller immediately after the first input transition has been timestamped and at each RPI You must manage the data coming from the Sequence of Events module The following occurs in the process of the managing data coming from the Se
16. 0 modules including your Sequence of Events module Failure to do so may not prevent the application from working but may defeat the purpose of upgrading your modules revision levels Disable Keying The inserted module attempts to accept a connection to the controller regardless of its type Be extremely cautious when using the disable keying option if used incorrectly this ATTENTION ne option can lead to personal injury or death property damage or economic loss If keying is disabled a controller makes a connection with most modules of the same type as that used in the slot configuration For the ControlLogix Sequence of Events module if keying is disabled the controller will only make a connection to another Sequence of Events module A controller will NOT establish a connection if any of the following conditions exist even if keying is disabled e The slot is configured for one module type e g input module and a module of another type e g output module is inserted in the slot e The module inserted into the slot cannot accept some portion of the configuration For example if a Sequence of Events module is inserted into a slot configured for a diagnostic input module the controller cannot make a connection because the module will not accept process the diagnostic configuration 1 Minor revisions are incremented by single counts such that minor level 10 i major minor revision level 1 10 follo
17. 6 setting in RSLogix 5000 4 6 retrieving module identification information 1 5 retrieving module status 1 5 revision major 1 5 minor 1 5 RSLogix 5000 adding a module to a project 4 3 4 5 choosing a communications format 4 4 choosing an electronic keying method communications format choices 4 5 configuring 1756 SYNCH module C 3 configuring chatter detection 4 6 configuring the module 4 1 4 10 downloading configuration 4 7 editing configuration 4 7 4 8 electronic keying methods 4 5 enabling CST Capture 4 6 enabling Latch CST 4 6 fault reporting 8 4 inhibiting the module 4 6 setting input filter times 4 6 setting the minor revision 4 4 setting the RPI 4 6 troubleshooting the module 8 2 using module tags D 1 D 12 using with RSNetWorx for ControlNet 2 2 Index 3 RSNetWorx for ControlNet adding anew module to a remote chassis connected via ControlNet 2 2 Using with RSLogix 5000 2 2 S software using RSLogix 5000 2 2 using RSNetWorx for ControlNet 2 2 sorting data in CST Per Point mode 6 14 specifications 1756 IB16ISOE module A 1 1756 IH16ISOE module A 5 spring clamp RTB 3 5 status indicators 1 4 5 18 8 1 8 2 I O status 5 18 module status 5 18 T tasks event tasks 2 3 time master in synchronized chassis C 1 timestamping acknowledging latched timestamp data in CST Per Point mode 6 12 6 13 acknowledging latched timestamp data in FIFO mode 7 17 in CST Per Point mode 1 3 5 3 6 2 in FFIO mode 7 2 in
18. Be Gon he hae gen 6 14 Clearing All Data From the Module s Buffers At Once 6 14 Chapter Summary and Whats Nex fis crea a eS 6 14 Chapter 7 What This Chapter Contains 44 045 pove beet eh iew ys 7 1 Overview of the Mode ti des ote Ue hie lint Pant Heed 7 1 How Does the On Board Buffer Work in FIFO Mode 7 2 What the Typical Applications Where FIFO Mode is Used 7 4 Configuring the Module for FIFO Mode 7 4 Choosing a Communications Format 7 5 Using Latch CST in FIFO Mod cx occ va tien eid ao 7 6 Using Enable CST Capture in FIFO Mode 7 9 Managing the Data in FIFO Mode 624 ics ee vad ee peed 7 10 Retrieving Data in FIFO Mode 4 456c06 cea eae 7 10 Producing Current Event Data 5 65 4 ean oo eee hes 7 14 Copying Relevant Input Data to a Separate Data GUI CHT Si 5 4 Goons Wh cus pang Sdn SG Sag hs Gah yeep San Oe 7 15 Acknowledging Latched Timestamp Data 7 17 Clearing All Data From the Module s Buffers At Once 7 20 Changing Between Retrieval Methods 7 20 Chapter Summary and What s Next ss 0ys 54086 rs aana 7 20 Publication 1756 UM528A EN P April 2004 Table of Contents 4 Troubleshooting the Sequence of Events Module Specifications and Module Block Diagrams Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System Synchronizing CSTs Across Multiple Chassis Using Module Tags Using Sample
19. Configured Features that can be adjusted to make sure the module operates as efficiently as possible in your application e g input filter times e Other Inherent Module Features Features that cannot be changed but are still crucial to module functionality e g producer consumer model Using the Sequence of Events Module Features 5 3 Module Features That Table 5 2 lists features on the Sequence of Events module that can Can Be Configured emia wis Table 5 2 This feature is described on Two Operational Modes 5 3 Enable CST Capture 5 5 Chatter Detection 5 8 Software Configurable Input Filters 5 10 Latch CST 5 7 Electronic Keying 5 13 Module Inhibiting 5 15 Two Operational Modes The Sequence of Events module can operate in either of the modes described in Table 5 3 Table 5 3 Operational mode CST Per Point Mode Description The module produces timestamps for up to 2 input transitions per input one for OFF to ON transitions and another for ON to OFF transitions these timestamps can occur simultaneously This is the default setting when you add the module to an RSLogix 5000 project First In First Out FIFO Mode The module timestamps an unlimited number of input transitions regardless of direction i either OFF to ON or ON to OFF or input i the same input can transition many times and the module will timestamp every transition and stores them in an on board buffer
20. EN P April 2004 Configuring the Sequence of Events Module 4 7 Downloading Configuration A Click here to see the pull down menu B Click download Editing Configuration After you write configuration for your Sequence of Events module the module does not use this configuration until you download it to the owner controller The download transfers the entire program to the controller overwriting any existing program Download module configuration as shown below R RSLogix 5000 My_Sequence_of_Ev File Edit View Search Logic Communic alala 2 lelel ofc c Offline j F RUN i No Forces Go Online No Edits Upload Gun Controller Properties Depending on your application a variety of RSLogix 5000 screens may appear to choose a path to your ControlLogix controller and to verify the download Navigate those screens as best fits your application This completes the download process After you have set configuration for a module you can review and change your choices You can change configuration data and download it to the controller while online This is called dynamic reconfiguration Your freedom to change some configurable features though depends on whether the controller is in Remote Run Mode or Program Mode Miiietia Although you can change configuration while online you must go offline to add or delete modules from the project Publi
21. Events module offers two input filter settings one for OFF to ON transitions and one for ON to OFF transitions and is set on a module wide basis Publication 1756 UM528A EN P April 2004 2 2 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 However you should be aware of aspects in which the Sequence of Events module is similar to standard ControlLogix digital input modules For more information on these similarities see Table 2 3 Table 2 3 Ways that a Sequence of Events Module Behave Like Other ControlLogix Digital Input Modules Concept Description Ownership Every Sequence of Events module in the ControlLogix system must be owned by a Logix5000 controller This owner controller e stores configuration data for every module that it owns e can be local or remote in regard to the Sequence of Events module s position e sends the Sequence of Events module configuration data to define the module s behavior and begin operation with the control system This module does not support multiple owner controllers Using RSNetWorx and
22. Events modules the module can emulate older revisions The module will accept the configuration if the configuration s major minor revision is less than or equal to the physical module s revision For example if the configuration contains a major minor revision of 1 7 the module inserted into the slot must have a firmware revision of 1 7 or higher for a connection to be made When a module is inserted with a major minor revision that is less than the revision for which the slot is configured i e the module has a revision of 1 6 and the slot is configured for a module with revision 1 8 no connection is made between the controller and the 1 0 module We recommend using Compatible Match whenever possible Remember though with major revision changes the module only works to the level of the configuration At the time of this printing the Sequence of Events module uses a major revision of 1 3 However if a new major revision for the module is released consider this example If a slot is configured for a module with major minor revision of 1 7 and you insert a module with a major minor revision of 2 3 the module works at the 1 7 level with respect to module functions that are related to RSLogix 5000 such as interface changes Bug fixes that are affected by the module s firmware though would work at the 2 3 revision level If possible we recommend that you make sure configuration is updated to match the revision levels of all 1
23. FIFO mode 1 3 5 3 on board storage of timestamp data 1 2 using CST 1 1 1 3 using Enable CST Capture 2 6 2 7 5 5 5 6 triggering event tasks 2 3 troubleshooting module status indicators 1 4 status indicators 8 1 8 2 using RSLogix 5000 8 2 troubleshooting the module 8 1 8 4 U universal coordinated time UCT B 2 converting CST to UCT B 8 B 9 Publication 1756 UM528A EN P April 2004 4 Index WwW warnings preventing electrostatic discharge Preface 3 wiring connections recommendations for wiring RTB 3 5 using the cage clamp RTB 3 4 Publication 1756 UM528A EN P April 2004 using the interface module IFM 1 4 using the removable terminal block RTB 1 4 using the RTB 3 4 3 5 using the spring clamp RTB 3 5 wiring the module 3 6 How Are We Doing ANE Your comments on our technical publications will help us serve you better in the future Thank you for taking the time to provide us feedback wy You can complete this form and mail or fax it back to us or email us at RADocumentComments ra rockwell com Pub Title Type ControlLogix Sequence of Events Module Cat No 1756 IB16ISOE 24 48V dc Pub No 1756 UM528A EN P Pub Date April 2004 PartNo 957859 83 1756 IH16ISOE 125V de ees a Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2 3 How can we ma
24. Module Features 5 9 Use the Configuration tab in RSLogix 5000 to configure Chatter Detection as shown in the example below E Module Properties Local 1 1756 IH16ISOE 1 1 General Connection Module Info Configuration Backplane Chatter Detection I On gt Off No of Events F 5 r Input Filter Time Off gt On On Off r Module Configuration Bits Beset All CST A Type the number of events Range Is 2 127 events Use 0 to disable this feature I Latch CST B Type the time measured in milliseconds You can use up to 10 000 milliseconds X aft Status Offline Cancel Apply Help In this example if 5 events occur on input point 0 within any 20ms time frame the module considers the point to be chattering mM fen configuring Chatter Detection make sure the time divided by the number of events is greater than the module s input filter times For example in the example above the time 20ms divided by the number of events 5 4 For Chatter Detection to work properly in this case make sure your input filter lt 4ms Publication 1756 UM528A EN P April 2004 5 10 Using the Sequence of Events Module Features Publication 1756 UM528A EN P April 2004 Software Configurable Input Filters To account for hard contact bounce you can configure ON to OFF and OFF to ON input filter times in R
25. OFF and OFF to ON events The NewData tag must also be used to acknowledge the event s O NewDataAck x DINT Allows NewData bits in the Input word to function as intended NewData bits are set when a transition occurs and clear only after they are acknowledged via the NewDataAck bit Typically the following events occur e An event occurs on an input e The Sequence of Events module sets the NewData bit for the input where the event occurred e The controller records the new data e The controller acknowledges the new data by causing a 0 to 1 transition on the corresponding NewDataAck bit e The NewData bit clears e When another event occurs on the input the sequence begins at the top bullet in this list The controller must cause a 0 to 1 transition in this bit to acknowledge new data for an input in other words if the NewDataAck bit is 0 when new data is received the controller must change this bit to 1 to acknowledge the data If NewDataAck bit is 1 when new data is received the controller must change this bit to 0 and then to 1 to acknowledge the new data O PointToRetrieve INT Not used in this mode O ResetEvents BOOL Erases all recorded events when transitioned from 0 to 1 Resets most other fields to 0 as well O RetrieveByPoint BOOL Not used in this mode Publication 1756 UM528A EN P April 2004 Table D 4 Output Tags in CST Per Point Mode Tag name Type O UCTTime 2 DINT 2 O CSTTime 2 DINT 2 Table D 5 Con
26. P April 2004 Conductors Wire Size Category 22 to 14 AWG 0 324 to 2 08 sq mm stranded 3 64 inch 1 2mm insulation maximum 4 2 Screwdriver Blade Width for RTB 1 8 inch 3 2mm maximum Environmental Conditions Operational Temperature IEC 60068 2 1 Test Ad Operating Cold IEC 60068 2 2 Test Bd Operating Dry Heat IEC 60068 2 14 Test Nb Operating Thermal Shock 0 to 60 C 32 to 140 F Storage Temperature IEC 60068 2 1 Test Ab Un packaged Non operating Cold IEC 60068 2 2 Test Bb Un packaged Non operating Dry Heat IEC 60068 2 14 Test Na Un packaged Non operating Thermal Shock 40 to 85 C 40 to 185 F Relative Humidity IEC 60068 2 30 Test Db Un packaged Non operating Damp Heat 5 to 95 non condensing Vibration IEC 60068 2 6 Test Fc Operating 2g 10 500Hz Operating Shock IEC 60068 2 27 Test Ea Unpackaged Shock 30g Non operating Shock IEC 60068 2 27 Test Ea Unpackaged Shock 50g Emissions CISPR 11 Group 1 Class A ESD Immunity IEC 61000 4 2 6kV contact discharges 8kV air discharges Radiated RF Immunity IEC 61000 4 3 10V m with 1kHz sine wave 80 AM from 80MKHz to 1000MHz 10V m with 200Hz 50 Pulse 100 AM at 900Mhz 10V m with 200Hz 50 Pulse 100 AM at 1890Mhz Specifications and Module Block Diagrams A 3 EFT B Immunity IEC 61000 4 4 4kV at 2 5kHz on signal ports Surge Transient IEC
27. P April 2004 Table of Contents 2 Configuring the Sequence of Events Module Using the Sequence of Events Module Features Publication 1756 UM528A EN P April 2004 Chapter 4 What This Chapter Contains oy 24 ci eo oe eGiseae 4 1 Configuring Your I O Module 4 3s dcgdne ahh Ybor ees 4 1 RSLogix 5000 Configuration Software 4 1 Overview of the Configuration Process 4 2 Adding a New Module to Your RSLogix 5000 Project 4 3 Communications Format 44 665 45 nee saa ee 4 5 Electronic Keying 2 yoo bait gg Seat aed aw Bi ee ea 4 5 Using the Default Configuration 25 6 ec28 kei Fou SEG 4 6 Altering the Default Configuration 4 6 Downloading Configuration os wa e098 sO EN SR eS 4 7 Editing Configuration siii4 acca in cone eee KERR Oe 4 7 Configuring Modules in a Remote Chassis 4 9 Chapter Summary and What s Next 000 4 11 Chapter 5 What This Chapter Contains o aaa aaaeeeaa 5 1 Determining Module Compatibility 5 2 Module Features That Can Be Configured 5 3 Two Operational Modes ia cies tees ad ee da bls 5 3 Enable GST Capit ceca o a E ea ee ee 5 5 ACR Ss mingite gaS Ns E Rupee e E EEN Neo 5 7 Chatter ISTE CHO e nr iieaoe Bele a E aE E eM eae 5 8 Software Configurable Input Filters 5 10 Electronic Keyingi isir Sty ake 8 SN E A ee eS 5 13 Module Inhibiting on 0 9 Soe eee
28. Publication 1756 UM528A EN P April 2004 Sequence of Events module 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 been timestamped and at each RPI You must manage the data coming from the Sequence of Events module The following occurs in the process of the managing data coming from the Sequence of Events module in CST Per Point mode 1 The Sequence of Events module sends data to the controller 2 The controller copies the relevant portions of the input data to a separate array 3 At the user s discretion the controller clears latched timestamp data from the Sequence of Events module via the O EventAck and O NewData tags preparing the module to timestamp the next transition This process is described in the rest of this section Module Sends Data to the Controller Figure 6 2 shows an example of the Sequence of Events module sending data to the controller In the example the following occurs 1 Input 1 transitions from OFF to ON The input has Enable CST Capture enabled 2 The Sequence of Events module timestamps the transition 3 The module sends its input data including the transition timestamp from input 1 to the controller a D gt ControlLogix controller Figure 6 2 oO yA l 2
29. RSLogix 5000 Projects with the Sequence of Events Module Glossary Index Publication 1756 UM528A EN P April 2004 Chapter 8 What This Chapter Contains wav iene ox Hee eae ye 8 1 Using LED Status Indicators o an Sickanargey Seale ial bcd gs 8 1 Using RSLogix 5000 To Troubleshoot the Module 8 2 Determining Fault Type nanana aaaea 8 4 Chapter Summary and What s Next 05 8 4 Appendix A 1756 IB1G6ISOE Specifications 0 0 0 0 00 eee eee A 1 1756 IB16ISOE Module Block Diagram A 4 1756 IH16ISOE Specifications oc ccecddcieed Aye ks Pees A 5 1756 IH16ISOE Module Block Diagram A 8 Appendix B OVENI EW dee Aca ha pete el rh Gag 9b Sa Ue tf aa A thc peel de die deca las B 1 What is the 1756HP GPS Module i ve 4es eeew ee ess B 2 Correlating CST with UCT 4a t 5 Sones boeken BS B 2 Determining the Absolute First Fault Across Multiple Chassis B 4 How Does the ControlLogix Controller Retrieve Converted Value from the 1756HP GPS Module B 6 Converting Timestamps from CST Format to Universal Coordinated Time Format oasa aaa we aalia oh nadd ate wes B 8 Appendix C OVErVI EW ia as ieee EIO a OMA Sh RO OR nee eae C 1 Usinga Time Master nase parisa ie ga hem teak ae neuen C 1 Configuring 1756 SYNCH Modules in RSLogix 5000 C 3 Synchronizing Chassis in ControlLogix Redundancy Systems C 4 Related Synchlink Documentation aoaaa Sp as ho 8 eS C 5 A
30. Sequence of Events system see Appendix B The following are example typical applications for CST Per Point mode e Substation automation e Load shedding energy management e Emergency shutdown systems You configure the same general set of configurable features described in Chapter 5 whether you are using the Sequence of Events module in CST Per Point mode or FIFO mode However for some features the module behavior as dictated by the feature varies according to operational mode For example Latch CST impacts the Sequence of Events module behavior slightly differently in CST Per Point mode than in FIFO mode You should be aware of the impact the following configurable features have on module behavior in CST Per Point mode e Communications Format e Latch CST e Enable CST Capture e Universal Coordinated Time UCT Use this pull down menu to choose the CST Per Point communication format Using The Sequence of Events Module in CST Per Point Mode 6 5 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 To operate the Sequence of Events module in CST Per Point mode you must choose the CST Per Point communication format as shown below Paren Namene Descr
31. The maximum amount of time between broadcasts of I O data Run mode In this mode the following events occur e Controller program is executing e Inputs are actively producing data Service A system feature that is performed on user demand such as fuse reset or diagnostic latch reset System side Backplane side of the interface to the Sequence of Events module Tag A named area of the controller s memory where data is stored Time master Device either ControlLogix controller or 1756 SYNCH module that sets the CST time for a ControlLogix chassis and or SynchLink system Timestamping ControlLogix process that stamps a change in input data with a relative time reference of when that change occurred Universal Coordinated Time UCT World standard time format maintained by atomic clocks operated by government organizations around the world The 1756HP GPS module reports UTC as a 64 bit unsigned long integer representing the number of elapsed microseconds since 1 January 1972 Wall clock time WCT Gregorian time format In this format time is represented in year month day hour minute second and microsecond A absolute time determining across chassis B 4 B 5 agency certifications 5 19 ASIC delay 2 4 2 5 backplane connector 1 4 bandwidth conserving on ControlNet 2 7 block diagram 1756 IB16ISOE module A 4 1756 IH16ISOE A 8 C cage clamp RTB 3 4 chatter detection 5 8 5 9 configuring in RSLogix 500
32. The module can timestamp each transition with a unique CST with 25us resolution 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 You copy new data from the controller tags to a separate data structure for later sorting Once the data is copied to a separate data structure you may sort the data in the controller to determine the order of events Some of these typical events are described in greater detail in the rest of this chapter Publication 1756 UM528A EN P April 2004 6 4 Using The Sequence of Events Module in CST Per Point Mode What Are The Typical Applications Where CST Per Point Mode is Used Configuring the Module for CST Per Point Mode Publication 1756 UM528A EN P April 2004 CST Per Point mode is typically used in applications that need to determine relative first fault detection after an event cascade occurs The Sequence of Events module can provide unique timestamps for separate input transitions as long as they occur 25uUs apart you can sort the data resulting from an event cascade to determine where the first input transition occurred in the cascade You can also use the 1756HP GPS module to give the stored CST timestamps a real time reference For more information on how to integrate the 1756HP GPS module into your ControlLogix
33. 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 from the current event located in the 1 EventNumber tag to the module s EventAck tag G e O EventAck Figure 7 5 shows how to clear data for the current event from the 7 17 Sequence of Events module In this example the controller has copied relevant input data from the controller tags to a separate data structure The controller may use a COP or MOV instruction to copy the current event number to the Sequence of Events module s O EventAck tag and clear the data from the module s on board buffer ControlLogix controller Figure 7 5 i oa 1 Module stores data in on board buffer 2 Module produces 4 To clear the current event from the Sequence of Events module buffer the controller gI p Controller tags p tFauit l Data i TNewDaa EventOverlow 3 C
34. UM528A EN P April 2004 6 14 Using The Sequence of Events Module in CST Per Point Mode Sorting the Data Clearing All Data From the Module s Buffers At Once Chapter Summary and What s Next Publication 1756 UM528A EN P April 2004 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 If necessary you can reset the events in the Sequence of Events module in effect clearing all data from previously timestamped transitions In other words when all data is cleared from the module s buffers all of the module s input tags return to 0 To reset events in the module s buffer transition the O ResetEvents tag to 1 as described below e If the bit 0 change the bit to 1 e If the bit 1 change the bit to 0 wait for at least one RPI and change the bit to 1 Once the data is cleared the module begins timestamping input transitions again and storing them in its on board buffer In this chapter you read about using the Sequence of Events module s features Chapter 7 describes Using The Sequence of Events Module in FIFO Mode Chapter What This Chapter Contains Overview of the Mode Us
35. communication format as shown below H16ISOE 1 1 17561H16ISOE 16 Channel Isolated 125V Input Sequence of Events Allen Bradley i communication format Parent Local 3 gt in 3 i Name ihe Sequence_ot_Events_module Slot ig 3 Epee As Berar eee core Use this pull down menu to tmm tam csT FiFo Moe choose the CST FIFO Mode ie C51 FIFO Mode se Revision He Cancel lt Back Next gt se ae Publication 1756 UM528A EN P April 2004 7 6 Using The Sequence of Events Module in FIFO Mode Table 7 2 If Latch CST is Enabled 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 the following occurs The Sequence of Events module timestamps input transitions as they occur and stores the data for those transitions in its on board buffer If you fail to empty the buffer as described on page 7 10 faster than it is filled after 160 timestamped input transitions the module ignores additional transitions Once the Sequence of Events module buffer is filled the next input transition is not timestamped and the EventOverflow for the point where the transition occurred is set to one to inform the controller that events occurred but were not
36. e l P E a NoEdts a Battery OK Ly a eae Sete ea 7 H 1 0 Not Responding wl BY sf Favorites E S Controller SOE_Test_Program Controller Tags a Controller Fault Handler Power Up Handler B S Tasks 5 6 Maintask MainProgram Unscheduled Programs H E Motion Groups on I O Configuration fh 1 1756 IH16ISOE f 2 1756 18161 f 3 1756 0x81 Ungrouped pes Trends 5 8 Data Types Gi User Defined Gy Strings H Predefined i Madule Defined 6 1 0 Configuration Pi 1 1756 IH16150E fj 2 1756 18161 3 1756 oxar Status Fauted EE Cancel Apply Help i Warning signal The module in slot 1 has a communications fault Troubleshooting the Sequence of Events Module 8 3 e Message in a screen s status line Status line provides information on the module s fault and on the connection to the module e Notification in the Tag Editor General module faults are also reported in the Tag Editor Diagnostic faults are only reported in the Tag Editor tagNameCCi CSSC ie efface z RSLogix 5000 generates 1s in response to a module communication fault 2 1111_1111_1111_1111_1111_1111_1111_1111 2 0000_0000_0000_0000_0000_0000_0000_0000 2 0000_0000_0000_0000_0000_0000_0000_0000 2 0000_0000_0000_0000_0000_0000_0000_0000 a In this example a communication fault occurred between the controller and the Sequence of Events
37. e how the data is sent to the controller The next section briefly describes the two modes of operation available with the Sequence of Events module and how they impact the module s behavior Table 1 2 Operational mode CST Per Point Mode What is the ControlLogix Sequence of Events Module 1 3 Two Modes of Operation The Sequence of Events module can operate in either of the modes described in Table 1 2 Description The module timestamps up to 2 input transitions per input one for OFF to ON transitions and another for ON to OFF transitions First In First Out FIFO Mode What Else Does the Sequence of Event Module Do The module timestamps an unlimited number of input transitions regardless of direction i e either OFF to ON or ON to OFF or input i the same input can transition many times and the module will timestamp every transition and stores them in an on board buffer The module is capable of storing the data for up to 160 input transitions in its on board buffers at a single time However if you retrieve data from the buffers effectively the module will never miss an input transition regardless of how many occur You set the module s operational mode when you choose a communication format during initial module configuration Depending on operational mode RSLogix 5000 creates different tags for the Sequence of Events when it is added to a project For more information on each mode see Chap
38. latched For more information on Latch CST see page 5 7 C FilterOffOn SINT Sets the OFF to ON filter time for all 16 inputs Times are set in 1ms increments from Oms to 50ms 0 no filtering For more information on Software Configurable Input Filters see page 5 10 Publication 1756 UM528A EN P April 2004 D 8 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 Oms to 50ms 0 no filtering For more information on Software Configurable Input Filters see page 5 10 C CaptureOffOn x DINT Enables capturing OFF to ON events on a per point basis If disabled i e set to 0 that point will not record timestamp data for OFF to ON input transitions 0 CST Capture disabled for OFF to ON 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 1 CST Capture enabled default for OFF to ON input transitions For more information on Enable CST Capture see page 5 5 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
39. long as the transitions occur 25uUs apart 3 The controller retrieves data from the Sequence of Events module as described in the following steps a Immediately after the Sequence of Events module timestamps an input transition it records data in the first slot of its on board buffer and produces the data for the controller the data is the current event The module produces the data from the current event at every subsequent RPI until the controller clears it as described in step c b The controller copies the data from the controller tags to a separate data structure for later use c The controller acknowledges the current event in the Sequence of Events module s buffer by I EventNumber to O EventNumber d Once the current event is cleared from the Sequence of Events module s buffer data for the next transition stored in the buffer becomes the current event and the module begins producing this data for the controller as described in step a 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 e less than 160 input transitions worth of data is stored in the buffer Publication 1756 UM528A EN P April 2004 7 4 Using The Sequence of Events Module in FIFO Mode What the Typical Applications Where FIFO Mode is Used Configuring the Module for FIFO Mode Publication 1756 UM528A EN P April 2004 FIFO mode is intended for
40. modules have identical functionality except for the fact that they operate at different voltage levels Throughout this manual we use the term Sequence of Events module generically When you read the term it refers to both types of modules unless specifically noted This manual is intended for individuals who program ControlLogix control systems such as e software engineers e control engineers e application engineers To most efficiently use the Sequence of Events module you should be familiar with e ControlLogix controllers e ControlLogix ControlNet communication modules e RSLogix 5000 e RSNetWorx for ControlNet Publication 1756 UM528A EN P April 2004 Preface 2 What This Manual Contains Table Preface 2 lists the sections contained in this manual Related Documentation Publication 1756 UM528A EN P April 2004 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 Chapter 4 Configuring the Sequence of Events Module Chapter 5 Using the Sequence of Events Module Features Chapter 6 Using The Sequence of Events Module in CST Per Point Mode Chapter 7 Using The Sequence of Events Module in FIFO Mode Chapter 8 Troubleshooting the Sequence of Events Module Appendix A Specifications and Modu
41. ms 0 2 750 0 ms I Major Fault On Controller If Connection Fails While in Run Mode Module Fault Publication 1756 UM528A EN P April 2004 5 16 Using the Sequence of Events Module Features Other Inherent Module Features Publication 1756 UM528A EN P April 2004 Table 5 5 lists features on the Sequence of Events module that cannot be configured Table 5 5 This feature is described on Removal and Insertion Under Power RIUP 5 16 Module Fault Reporting 5 16 Fully Software Configurable 5 17 Producer Consumer Model 5 17 Status Indicator Information 5 18 Full Class Division 2 Compliance 5 19 Agency Certifications 5 19 Removal and Insertion Under Power RIUP The Sequence of Events module is designed to be installed or removed while chassis power is applied WARNING When you insert or remove the module while backplane power is on an electrical arc can occur This could cause an explosion in hazardous location installations Be sure that power is removed or the area is nonhazardous before proceeding Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance that can affect module operation Module Fault Reporting Your Sequence of Events module provides both a hardware and software indication when a module fault occurs The module s status indicator and RSLogix 5000 graphically di
42. offers several significant differences from other ControlLogix digital input modules including those described in Table 2 2 Description The Sequence of Events module produces significantly more data for its owner controller than standard ControlLogix digital input modules While other input modules only produce ON OFF and fault status the Sequence of Events module produces data such as ON OFF and fault status timestamp data indication of whether new data was produced for specific input points or if transitions were not timestamped Only one owner controller per module While multiple controllers can simultaneously own other digital input modules the Sequence of Events module only supports a single owner controller Rack optimized connections not supported The Sequence of Events module does not support Rack Optimized Connections from the owner controller Change of State COS functionality in Enable CST Capture feature The module does support Enable CST Capture a feature used to timestamp input transitions that is analogous to COS For more information on Enable CST Capture see page 2 6 No listen only connections Controllers cannot make listen only connections to the Sequence of Events module All connections between the module and its owner controller are direct connections Input filtering on a module wide basis Other digital input modules offer input filtering on a per group basis The Sequence of
43. onto the RTB until it stops IMPORTANT When keying your RTB and module you must begin with a wedge shaped tab in position 6 or 7 Figure 3 4 Wedge shaped Keying Tab Module side of RTB 20851 M Publication 1756 UM528A EN P April 2004 3 4 Installing the Sequence of Events Module Connecting Wiring Publication 1756 UM528A EN P April 2004 You can use an RTB or a Bulletin 1492 prewired Interface Module FM 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 Wiring the RTB You can use either of the following RTBs with your Sequence of Events module e Cage Clamp RTB Catalog number 1756 TBCH e Spring Clamp RTB Catalog number 1756 TBS6H Wire the RTB with a 1 8 inch 3 2mm maximum flat bladed screwdriver before installing it onto the module WARNING When you connect or disconnect the Removable Terminal Block RTB while field side power is on an electrical arc can occur This could cause an explosion in hazardous location installations Be sure that power is removed or that the area is nonhazardous before proceeding Cage Clamp RTB 1 Strip 3 8 inch 9 5mm maximum length of wire 2 Insert the wire into the open terminal 3 Turn the screw clockwise to close the terminal on the wire Figure 3 5
44. owner controller via an EtherNet IP network data is transferred to the owner controller in the following way e At the RPI or on an Enable CST Capture event the module multicasts data within its own chassis The 1756 ENBT module in the remote chassis immediately sends the module s data over the network to the owner controller as long as it has not sent data within a time frame that is 1 4 the value of the digital input module s RPI For example if a Sequence of Events module uses an RPI 100ms the 1756 ENBT module only sends module data immediately on receiving it if another data packet was not sent within the last 25ms In this chapter you read about how the Sequence of Events module operates in a ControlLogix system Chapter 3 explains the Installing the Sequence of Events Module Chapter 3 What This Chapter Contains Installing the Sequence of Events Module Installing the Sequence of Events Module This chapter describes how to install the Sequence of Events module Table 3 1 For information on See page Installing the Sequence of Events Module 3 1 Keying the Removable Terminal Block 3 3 Connecting Wiring 3 4 Assembling The Removable Terminal Block and the Housing 3 7 Choosing the Extended Depth Housing 3 8 Installing the Removable Terminal Block 3 10 Removing the Removable Terminal Block 3 12 Removing the Module from the Chassis 3 13 You can install or remove the module while cha
45. propagated via 1756 SYNCHS A 1756 SYNCH Gets CST from backplane and sends it to the other 1756 SYNCH modules Configure this 1756 SYNCH module as shown below Module Properties Local 2 1756 SYNCH A 2 1 _ Module s Role in Coordinated System Time CST Mastership JA Make SynchLink CST Master Curent Setting Details This module is a SynchLink CST Master It zy 0 rei __ relays time from the Chassis CST Master ho Ze shat A p Dependence k See i Paneer We Required ses Math EN S E A Synchlink ee 43743 1756 SYNCH Gets CST from 1756 SYNCH in local chassis and sets it on the backplane in Chassis 2 Configure this 1756 SYNCH module as shown below Module Properties Local 2 1756 SYNCH A 2 1 a Current Setting Details _ This module is the Chassis CST Master It requires SynchLink to relay time from the SynchLink CST Master to the chassis If no SynchLink is detected on power up orif N SynchLink is lost during normal operation this module will stop relaying time to th chassis cae M Make Chassis CST Master m Dependence On SynchLink K P Requiredeg Ne 3 S C Not Required This setting is This setting is recommended This setting is This Dependence on SynchLink setting is required because the In this case you must make required because the optional for the 1756 SYNCH module We module relays time sure the ControlLogix c
46. sinea reani el ak Rie E EE A 2 2 Propagating a Signal From Field Device to Backplane 2 4 Sequence of Events Module in a Local Chassis 2 6 Requested Packet Interval RPD 4 2 6 Enable GST Gapiiie coax oa a Goo Ae ok ee 2 6 Sequence of Events Module in a Remote Chassis 2 8 Remote Input Module Connected Via ControlNet 2 8 Remote Input Modules Connected Via EtherNet IP 2 10 Chapter Summary and What s Next 2 10 Chapter 3 What This Chapter Contains o a ic 86 skate ed hye 3 1 Installing the Sequence of Events Module 3 1 Keying the Removable Terminal Block 3 3 Connecting Wine sa pi6 b oS de eed a es oH HOR eS 3 4 Witing the RTB se ghia cette AG sp edt Badia vata de Sk Goa 3 4 Recommendations for Wiring Your RTB 3 5 Wiring the Sequence of Events Module 3 6 Assembling The Removable Terminal Block and the PIOUS Onis 4 ek FG aa ata KR ee eee O 3 7 Choosing the Extended Depth Housing 3 8 Recommendations for Using the Extended Depth Housing 4 9 acid 2 BE eal a dees 3 9 Cabinet Size Considerations With the Extended Depth Housing onana saasaa 3 9 Installing the Removable Terminal Block 3 10 Removing the Removable Terminal Block 3 12 Removing the Module from the Chassis 3 13 Chapter Summary and What s Next 4 can foe xeee ace es 3 14 Publication 1756 UM528A EN
47. synchronized U g U a ControlNet 8 8 _ 8 8 8 _ 8 8 _ 8 a ma Ae o og d of oe om d de o ma a a ag D mar a a dg bi a a l a a a pot F 43834 l SynchLink Weal 1 Chassis contains Each chassis contains Chassis containing 1756 CNB R e 1756 L55 controller version 13 x e Sequence of Events module module series D version 5 23 or Required because the e 1756 SYNCH module greater and remote 1 0 but no redundant controllers use version Sequence of Events or 1756 SYNCH 11 71 This controller is not e 1756 CNB R module series modules and not synchronized with required if you use version 13 D version 5 23 or greater the other remote chassis redundancy e Sequence of Events module e 1756 SYNCH module e 1756 CNB R module series D version 5 23 or greater Related SynchLink For more information on how to use the 1756 SYNCH module see Documentation e SynchLink Design Guide publication number 1756 TD008 e ControlLogix SynchLink Module User Manual publication number 1756 UM521 Publication 1756 UM528A EN P April 2004 C 6 Synchronizing CSTs Across Multiple Chassis Notes Publication 1756 UM528A EN P April 2004 Appendix D Fault and Status Reporting Between the Module and Controllers Module Fault Word Bit 31 Using Module Tags Sequence of Events modules multicast fault status data to the owner controller The module maintains a Module Fault Word the highest level of fault report
48. the Per point tags there is one bit per input For exa Publication 1756 UM528A EN P April 2004 mple bit 0 represents input 0 bit 7 represents input 7 and so on 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 2 The controller copies relevant input data from the current event to a separate data structure for later use 3 The controller clears the current event from the Sequence of Events module s on board buffer by acknowledging the data via the module s output word 4 When the current event is cleared the next event in the module s on board buffer becomes the new current event If no other events are present the event data will be 0 5 The Sequence of Events module produces the new current event as described in step 1 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 Publication 1756 UM528A EN P April 2004 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 retriev
49. timestamped The Sequence of Events module has timestamped and recorded enough input transitions since the controller last retrieved data that the on board buffer is full Input 3 transitions for OFF to ON Because Latch CST is enabled and the Sequence of Events module s on board buffer is full it does not timestamp the transition All data in the buffer remains the same and the module increments the EventOverflow tag Publication 1756 UM528A EN P April 2004 Timestamp Event Np l Input Input State Y L oln gt Timestamp data 1 ge 4 Ip o lol Jo ol ajoj aa eS Ny a o Kee e ele 5l Timestamp data 160 Timestamp Event oo oo oo o 0 L Input State The data in the buffer here matches the data in the buffer above 43806 Using The Sequence of Events Module in FIFO Mode 7 1 Table 7 2 If Latch CST is Disabled the following occurs 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
50. value is cleared if the module is reset as described on page 7 20 CSTTimestamp 2 Per point 64 bit CST timestamp in CST format for the current 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 UCTTimestamp 2 Per point 64 bit UCT timestamp in Universal Coordinated Time format for the event UCT is expressed as microseconds elapsed since 1 January 1972 Typically UCT format is only used in applications that also use the 1756HP GPS module For more information on the 1756HP GPS module see Appendix B 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 EventPoint Per point Input that recorded the event Values are 0 15 where 0 Input 0 1 Input 1 etc EventData Per point Indicates if input transitioned OFF or ON 0 input transitioned OFF 1 input transitioned ON ReturningUCTTime Modulewide Indicates if timestamps are in UCT format rather than CST Typically UCT format is only used in applications that also use the 1756HP GPS module For more information on the 1756HP GPS module see Appendix B 0 CST format only UCT timestamp 0 1 UCT format available also For more information on UCT format see Appendix B EventsQueuedCount Modulewide Number of events currently stored in the module s buffer that have not been read 1 With
51. your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for States return procedure www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1756 UM528A EN P April 2004 PN 957859 83 Copyright 2004 Rockwell Automation Inc All rights reserved Printed in the U S A
52. 0 Module Chapter 4 Configuring the Sequence of Events Module This chapter describes how to configure your Sequence of Events module Table 4 1 For information on See page Configuring Your I O Module 4 1 Overview of the Configuration Process 4 2 Adding a New Module to Your RSLogix 5000 Project 4 3 Using the Default Configuration 4 6 Altering the Default Configuration 4 6 Downloading Configuration 4 7 Editing Configuration 4 7 Configuring Modules in a Remote Chassis 4 9 You must configure your module upon installation The module will not work until it has been configured with at least the default configuration g This chapter focuses on configuring I O modules in a local chassis To configure I O modules in a remote chassis you must follow all the detailed procedures with two additional steps To see the additional steps see page 4 9 RSLogix 5000 Configuration Software You must use RSLogix 5000 version 13 to set configuration for your Sequence of Events 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 Publication 1756 UM528A EN P April 2004 4 2 Configuring the Sequence of Events Module Overview of the When you use the RSLogix 5000 software to configure a Sequence Configuration Process 1 2
53. 0 4 6 communication networks ControlNet 2 2 EtherNet IP 2 2 communications format 4 5 choosing in RSLogix 5000 4 4 CST FIFO mode 4 5 CST Per Point 4 5 in CST Per Point mode 6 5 in FIFO mode 7 5 compatible match in electronic keying 5 14 configuration tags in CST Per Point mode D 2 in FIFO mode D 7 configuring a ControlLogix system using RSLogix 5000 2 2 using RSNetWorx for ControlNet 2 2 configuring the module 4 1 4 10 downloading configuration 4 7 editing configuration 4 7 4 8 in a remote chassis 4 9 4 10 overview of the process 4 2 RSLogix 5000 4 1 connections 2 3 connector pins on the module 1 4 ControlLogix backplane 1 4 conserving bandwidth on ControlNet 2 7 ControlLogix redundancy synchronizing chassis in a redundant system C 4 C 5 Index coordinated system time CST 1 1 1 3 CST Per Point mode 1 3 4 5 5 3 6 1 6 14 input tags 6 9 6 10 managing data in this mode 6 8 6 13 sorting data 6 14 typical applications 6 4 current event 7 3 D delays ASIC 2 4 2 5 firmware scan time 2 4 2 5 hardware 2 4 2 5 input filters 2 4 2 5 disable keying in electronic keying 5 14 documentation for related products Preface 2 downloading configuration 4 7 E editing configuration 4 7 4 8 electronic keying 5 13 5 14 choosing in RSLogix 5000 4 4 compatible match 5 14 disable keying 5 14 exact match 5 14 electrostatic discharge preventing Preface 3 Enable CST Capture 2 6 2 7 4 6 5 5 5 6 in C
54. 110010 nput State AC O LJ oc 4 Q e ed oO ie imestamp Event o Input 110010 1 aa 1 0 nput State 43805 Using The Sequence of Events Module in FIFO Mode 7 3 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 mE The current event is the event for which the Sequence of Events module is currently producing data The current event is NOT the most recently timestamped input transition After the controller retrieves the current event data it acknowledges the data and clears it from the Sequence of Events module s on board buffers and the data from the next slot in the buffer becomes the current event i e the module produces this data for the controller In FIFO mode generally the following occurs 1 You configure the Sequence of Events module to operate in FIFO mode via the Communication Format selection 2 The Sequence of Events module timestamps each transition and stores the data in its on board buffer The module can timestamp each transition with a unique CST as
55. 16ISOE module at 24V dc in 25 C conditions the signal propagation delay is affected by e hardware delay to energize the module nominally 10uS on this module e user configurable input filter time 0 to 50ms e firmware scan time up to 25us e ASIC delay 175us FIFO mode 625us CST Per Point mode In the typical case scenario e filter time of Oms the module has a signal propagation delay of approximately 210us FIFO to 660us CST Per Point Publication 1756 UM528A EN P April 2004 2 6 How Does the Sequence of Events Module Operate in a ControlLogix System Sequence of Events Module in a Local Chassis Publication 1756 UM528A EN P April 2004 When a Sequence of Events module resides in the local chassis G e the same chassis as the owner controller the following two configuration parameters affect how and when an input module multicasts data e Requested Packet Interval RPD e Enable CST Capture Requested Packet Interval RPI This interval specifies the rate at which a module multicasts its data to the controller The time ranges from 250us to 750ms and is sent to the module with all other configuration parameters When the specified time frame elapses the module multicasts data This is also called a cyclic update Because each operational mode CST Per Point or FIFO generates a unique set of controller tags the operational mode determines exactly what data is sent to the controller at the RPI For more
56. 40 F Storage Temperature IEC 60068 2 1 Test Ab Un packaged Non operating Cold IEC 60068 2 2 Test Bb Un packaged Non operating Dry Heat IEC 60068 2 14 Test Na Un packaged Non operating Thermal Shock 40 to 85 C 40 to 185 F Relative Humidity IEC 60068 2 30 Test Db Un packaged Non operating Damp Heat 5 to 95 non condensing Vibration IEC 60068 2 6 Test Fc Operating 2g 10 500Hz Operating Shock IEC 60068 2 27 Test Ea Unpackaged Shock 30g Non operating Shock IEC 60068 2 27 Test Ea Unpackaged Shock 50g Emissions CISPR 11 Group 1 Class A ESD Immunity IEC 61000 4 2 6kV contact discharges 8kV air discharges Radiated RF Immunity IEC 61000 4 3 10V m with 1kHz sine wave 80 AM from 80MKHz to 1000MHz 10V m with 200Hz 50 Pulse 100 AM at 900Mhz 10V m with 200Hz 50 Pulse 100 AM at 1890Mhz Specifications and Module Block Diagrams A 7 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 Withstand 3kV Enclosure Type Rating None open style Agency Certification UL UL Listed Industrial Control Equipment when product is marked CSA CSA Certified Process Control Equipment CSA CSA Certified Process
57. 58502392 957820651 958231715 Dest myarray 0 Dest myarray 1 Dest myarray 2 958502392 957820651 958231715 MOV Move Source Local 2 Timestamp 3 OffOn 0 Ei 957013421 Dest myarray 3 957013421 Lets_Sort ons OP SR E ons Copy File Jump To Subroutine Source myarray 0 Routine Name Bubble_Sort Dest sorted_array 0 Length Publication 1756 UM528A EN P April 2004 6 12 Using The Sequence of Events Module in CST Per Point Mode Publication 1756 UM528A EN P April 2004 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 when you acknowledge data you Clear it from the Sequence of Events module To clear data from the Sequence of Events module you must acknowledge them via the module s output tags You can clear data in the following ways e Clear latched timestamp data for specific inputs As data is acknowledged it is cleared from the module and the module will once again timestamp the first new transition for the input in the cleared direction s To clear timestamp data for specific inputs you must complete the following steps 1 Write to the EventAck tag i e O EventAck in the input point s output word e 0
58. 6 UM528A EN P April 2004 7 20 Using The Sequence of Events Module in FIFO Mode Clearing All Data From the Module s Buffers At Once Changing Between Retrieval Methods Chapter Summary and What s Next Publication 1756 UM528A EN P April 2004 If necessary you can reset the events in the Sequence of Events module s on board buffers in effect clearing all data from previously timestamped transitions In other words when all data is cleared from the module s buffers all of the module s input tags return to 0 except data that is a live filtered view of the inputs To reset events in the module s buffer transition the O ResetEvents tag to 1 as described below e If the bit 0 change the bit to 1 e If the bit 1 change the bit to 0 wait for at least one RPI and change the bit to 1 Once the data is cleared the module begins timestamping input transitions normally and storing them in its on board buffer When using the Sequence of Events module in FIFO mode you may determine that you need to change retrieval methods You can change retrieval methods but keep the following in mind before doing so e The change will NOT take effect until all events are acknowledged cleared from the module s buffers e When you change retrieval methods dynamically the ideal way is to reset events in the module buffers as described above and immediately switch FIFO retrieval modes Make sure you do not need the data bein
59. 6 UM528A EN P April 2004 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 If not accounted for chatter can cause the module to timestamp invalid input transitions Typically chattering signals cause inputs to transition falsely many times in a relatively short period of time To configure Chatter Detection for an input you must define an acceptable number of input transitions within a specific time period e If the number of input transitions meets the number specified in the configured time period the module considers the point in chatter the input device defective and ignores the last transition G e clears any timestamp data for the transition from its buffer and all subsequent transitions while still chattering e If the number of events in the specific time is less than your defined number the input will not go into chatter and timestamps are produced for all transitions e If an input is chattering the corresponding fault bit for that input is set e Once a point is in chatter all transitions on that input are ignored until the point is no longer chattering an input is no longer chattering if the configured chatter time elapses and no new transitions occur on the input Using the Sequence of Events
60. 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 B8OMHz Oscillatory Surge Withstand IEEE C37 90 1 3kV Enclosure Type Rating None open style Agency Certification when product is marked UL UL Listed Industrial Control Equipment CSA CSA Certified Process Control Equipment CSA CSA Certified Process Control Equipment for Class Division 2 Group A B C D Hazardous Locations FM FM Approved Equipment for use in Class Division 2 Group A B C D Hazardous Locations cE European Union 89 336 EEC EMC Directive compliant with EN 50082 2 Industrial Immunity EN 61326 Meas Control Lab Industrial Requirements EN 61000 6 2 Industrial Immunity EN 61000 6 4 Industrial Emissions C Tick 3 Australian Radiocommunications Act compliant with AS NZS CISPR 11 Industrial Emissions EEx 3 European Union 94 9 EC ATEX Directive compliant with EN 50021 Potentially Explosive Atmospheres Protection n Zone 2 Maximum wire size will require extended housing 1756 TBE 2 Use this Conductor Category information for planning conductor routing Refer to Publication 1770 4 1 Industrial Automation Wiring and Grounding Guidelines 3 certification details See the Product Certification link at www ab com for Declarations of Conformity Certificates and other
61. 756HP GPS module records UCT CST pairs that allow the module to calculate a drift compensation between the two clocks to provide increased synchronization and accuracy Figure B 1 y D 1 1756HP GPS module receives UCT value from satellite f CST on backplane T T T 2 1756HP GPS module captures 2an CST value from backplane Fa ae Z Q On board table 3 1756HP GPS module l 7 7 UCTICST calculates an offset for drift D p i TENER p XXXX XXXX l l XXXX XXXX l S P00 XXXX aa 4 4 1756HP GPS module stores the values in on board table Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System B 3 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 Generally the following occurs in this case 1 The Sequence of Events module sends timestamps to the controller after an event cascade 2 The ControlLogix controller sends a message instruction to the 1756HP GPS module with a CST format timestamp you must use one MSG per timestamp 3 The 1756HP GPS module converts the CST format timestamp to UCT and Gregorian wall clock format 4 1756HP GPS module send the new value back to the controller delivering the value in whatever
62. Allen Bradley ControlLogix Sequence of Events Module 1756 IB16ISOE 24 48V dc 1756 IH16ISOE 125V de User Manual Rockwell Automation 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 ab com manuals gi describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable 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 The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circuits equipment or software described in this manua
63. CST Per Point mode e Typically Latch CST is enabled in CST Per Point mode The configuration of this feature described on page 6 6 determines whether the module timestamps only the first transition on an input or every transition on an input e If Latch CST is enabled the module timestamps only the initial transitions OFF to ON and ON to OFF for each input e Whenever an input transition is timestamped as a valid transition the module sends updated input data for all inputs to the controller immediately and at every subsequent RPI Use the Configuration tab in RSLogix 5000 to set Enable CST Capture as shown in the example below ial Module Properties Local 1 1756 IH16ISOE 1 1 r Input Filter Time Off gt On On Off r Module Configuration Bits Click the Configuration tab Beset All CST e Click on the individual boxes for each input point to enable CST Capture for that point o e Clear the individual boxes for wey each input point to disable CST Capture for that point ojo jojojojojojo You can also use these boxes to enable or disable all points simultaneously Status Offline Cancel Apply Help Publication 1756 UM528A EN P April 2004 6 8 Using The Sequence of Events Module in CST Per Point Mode Managing the Data in CST Per Point Mode 1 Input 2 transitions from OFF to ON 42793
64. Control Equipment for Class Division 2 Group A B C D Hazardous Locations ces European Union 89 336 EEC EMC Directive compliant with EN 50082 2 Industrial Immunity EN 61326 Meas Control Lab Industrial Requirements EN 61000 6 2 Industrial Immunity EN 61000 6 4 Industrial Emissions European Union 73 23 EEC LVD Directive compliant with EN 61131 2 Programmable Controllers C Tick 3 Australian Radiocommunications Act compliant with AS NZS CISPR 11 Industrial Emissions 1 2 3 Maximum wire size will require extended housing 1756 TBE Use this Conductor Category information for planning conductor routing Refer to Publication 1770 4 1 Industrial Automation Wiring and Grounding Guidelines See the Product Certification link at www ab com for Declarations of Conformity Certificates and other certification details Publication 1756 UM528A EN P April 2004 A 8 Specifications and Module Block Diagrams 1756 IH16ISOE Module Figure A 2 shows the Sequence of Events module block diagram Block Diagram Figure A2 Isolation Barrier 125V dc or 24 48V de input circuit Serial EEPROM 5V power m T BF532 ualport Blackfin OPTO RAM DSP Isolation odo TT WOH WHO Backplane ASIC c 0 0 i 125V dc or i 1 24 48V de h I s n c 24V power input cir
65. Local 1 1756 IH16ISOE 1 1 r Input Filter Time Off gt On On Off e Click on the individual boxes for os o each input point to enable CST Capture for that point ea 0 r Module Configuration Bits I Latch CST Click the Configuration tab Reset All CST On gt off e Clear the individual boxes for each input point to disable CST Capture for that point You can also use these boxes to enable or disable all points simultaneously Status Offline Cancel Apply Help mA The basic function of Enable CST Capture G e timestamp specific input transitions occurs whether the Sequence of Events module is used in CST Per Point mode or FIFO mode However how the module uses the data from each transition varies slightly depending on the mode in which the module is operating e For more information on how Enable CST Capture is used in CST Per Point mode see page 6 7 e For more information on how Enable CST Capture is used in FIFO mode see page 7 9 Publication 1756 UM528A EN P April 2004 Click this box to enable the Latch CST feature Unclick the box to disable the feature Using the Sequence of Events Module Features 5 7 Latch CST Latch CST can be used to prevent the Sequence of Events module from overwriting input data once it is timestamped e If Latch CST is enabled the module only timestamps a
66. Module timestamps 3 Module sends input the transition C data to the controller C C a co Cao E o e A oma oop LData A NewData EventOverlow ReturningUCTTime L 0000000 EventNumber me aneo0 Timestamp 16 OffOn 2 22 Timestamp 16 OnOff 2 2 Using The Sequence of Events Module in CST Per Point Mode 6 9 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 Fault Set on a Per Point or Modulewide basis Per point Description Indicates if a fault has occurred for the input 0 no fault 1 fault The fault can be chatter or communication fault as described below e Chatter The Sequence of Events module can detect chatter on individual inputs and will set the appropriate tag to 1 when chatter exists on an input For example if the module has detected chatter on input 4 Fau t 4 1 e Communication fault The controller sets this tag to 1 for all 32 bits if a communication fault occurs on the module This tag clears when the fault that causes the condition no longer exists Data Per point Status of the input point This data is filtered if the Input Filter feature is used on the module Thus an input change must pass through the filter before it is
67. Net ControlNet Many miles Remote chassis with Sequence of Events modules and 1756 SYNCH modules 43791 Publication 1756 UM528A EN P April 2004 B 6 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 Controller Retrieve Converted Value from the cascade it may send them to the 1756HP GPS via a message instruction for conversion to either the following formats 1756HP GPS Module e Wall clock time WCT Format that is easily understood Typically the controller requests a conversion to this format for display purposes e UCT This format is a 64 bit value in microseconds similar to CST except that UCT starts from 1 January 1972 It is most useful to sort data using this field prior to converting to WCT for display purposes To convert CST format timestamps to WCT you must 1 Add the 1756HP GPS module to your RSLogix 5000 project via the Generic Module profile For more information on how to configure the 1756HP GPS module in an RSLogix 5000 project see the 1756HP GPS module user manual available at http www hiprom com 2 Send a Message Instruction to the 1756HP GPS module that uses the configuration listed in Table B 1 Table B 1 Message Type CIPGeneric i i i lt 2 lt 7 7 3 CP ia Service Type Custom S
68. OFF timestamp data 0000000 OFF ON timestamp data npu oo 0000000 ON OFF timestamp data 0000000 OFF ON timestamp data Input 2 S Q L 0000000 ON OFF timestamp data J 0000000 OFF ON timestamp data Input 15 ge C 0000000 ON OFF timestamp data J J 0000000 OFF ON timestamp data Input 0 oo L 0000000 ON OFF timestamp data Input 1 og O 0101100 OFF ON timestamp data P P T ON OFF timestamp data 0000000 OFF ON timestamp data Input 2 DT 0000000 ON OFF timestamp data 3 m 0000000 OFF ON timestamp data Input 15 ee 0000000 ON OFF timestamp data 3 an ee r 0000000 OFF ON timestamp data 0000000 ON OFF timestamp data Input 1 oO 0101100 OFF ON timestamp data 0000000 ON OFF timestamp data Input 2 Oo c 0000000 OFF ON timestamp data 100101 ON OFF timestamp data Input 0 oO J 0000000 i monis o o ineo Qa mentary dat 43793 Using The Sequence of Events Module in CST Per Point Mode 6 3 When the Sequence of Events module operates in CST Per Point mode generally the following occurs 1 5 You configure the Sequence of Events module to operate in CST Per Point mode via the Communication Format selection The Sequence of Events module timestamps each transition for inputs that are Enable CST Capture enabled
69. Publication 1756 UM528A EN P April 2004 A 4 Specifications and Module Block Diagrams 1756 IB16ISOE Module Block Diagram 5V power Figure A 1 Serial EEPROM odo TT WOH WHO C o n n e c 24V power t o r 1 2V power IN 0 GND 0 D Backplane ASIC RAM Dualport Isolation Barrier 125V dc or 24 48V de input circuit OPTO Isolation 125V de or _ 24 48V de input circuit The 125V dc or 24 48Vdc input circuits are shown in greater t detail below 24 48Vdc input circuit Electronic current limit circuit 5V 5 Publication 1756 UM528A EN P April 2004 K T i 43836 ControlLogix Display backplane Interface Figure A 1 shows the Sequence of Events module block diagram oa amm O Fa O Sa Sa O a 43687 1756 IH16ISOE Specifications Specifications and Module Block Diagrams A 5 Number of Inputs 16 Individually isolated Module Location 1756 ControlLogix Chassis Backplane Current 275mA 5 1V de amp 2mA 24V de Backplane Power 1 3W Maximum Power Dissipation 5 5W 60 C Module Thermal Dissipation 17 22 BTU hr On State Voltage Range 90 140V de Nominal Input Voltage 125V de On State Current 1 15mA 90V de minimum 1 85mA 140V dc maximum Maximum Off State Current 0 3mA Maximum Off State Voltage 20
70. SLogix 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 Miatigtia oput filters are applied to all inputs on the Sequence of Events module You cannot apply input filters to individual inputs on the module When an input transition occurs the Sequence of Events module timestamps the transition on the initial edge of the transition and stores data for the transition on board the module then scans the input where the transition occurred every 25us for the length of the filter time setting to verify that the input remains in the new state i e remained OFF or ON e If the input remains in the new state for a time period equal to the filter time setting the module sends data for the transition to the controller e If the input changes state again i e returns to the original state before the length of time of the filter setting has elapsed the module continues to scan that input for up to 4x the filter setting During this continued scan period one of the following events occurs At some point in the time period that is 4x the length of the input filter setting the input returns to the transitioned state and remains there for a length of time equal to the filter setting In this case the module sends data from the transition to the controller The input does not remain in the transitioned state f
71. ST Per Point mode 6 7 in FIFO mode 7 9 event tasks 2 3 exact match in electronic keying 5 14 extended depth housing 3 8 3 9 cabinet size considerations 3 9 recommendations for use 3 9 extended depth housing RTB 3 5 F fault reporting 5 16 8 4 FIFO mode 1 3 4 5 5 3 7 1 7 20 input tags 7 11 7 12 managing data in this mode 7 10 7 19 typical applications 7 4 Publication 1756 UM528A EN P April 2004 2 Index H hardware delay 2 4 2 5 l inhibiting the module 4 6 5 15 input filters 5 10 5 12 input filter delay 2 4 2 5 setting filter times in RSLogix 5000 4 6 input tags in CST Per Point mode 6 9 6 10 D 4 in FIFO mode 7 11 7 12 D 9 installing the module 3 1 installing the RTB 3 10 3 11 interface module IFM 1 4 J jumper bar 1 4 3 5 K keying electronic 4 4 4 5 5 13 5 14 mechanical keying 1 4 3 3 L Latch CST 5 7 acknowledging latched timestamp data in CST Per Point mode 6 12 6 13 acknowledging latched timestamp data in FIFO mode 7 17 enabling in RSLogix 5000 4 6 in CST Per Point Mode 6 6 in FIFO mode 7 6 local chassis module behavior in local chassis 2 6 2 7 M major revision 1 5 5 13 mechanical keying 1 4 minor revision 1 5 5 13 setting in RSLogix 5000 4 4 module compatibility 5 2 module identification information 1 5 ASCII text string 1 5 major revision 1 5 minor revision 1 5 product code 1 5 Publication 1756 UM528A EN P April 2004 product type 1 5 s
72. V de Maximum Input Impedance 74 8kQ Input Delay Time OFF to ON ON to OFF Hardware Delay 10us nominal 20us maximum Firmware Scan 25s Input Filter Time User selectable time Oms to 50ms ASIC delay 175s FIFO 625us CST Per Point Hardware Delay 50us nominal 75us maximum Firmware Scan 25us Input Filter Time User selectable time Oms to 50ms ASIC delay 175s FIFO 625us CST Per Point Timestamp accuracy 100us Cyclic Update Time RPI User selectable 250us minimum 750ms maximum Reverse Polarity Protection Yes Isolation Voltage Inputs to backplane and Input to input 250V continuous RTB Screw Torque Cage clamp 4 4 inch pounds 0 4Nm maximum Module Keying Backplane Software configurable RTB Keying User defined mechanical keying RTB and Housing 36 Position RTB 1756 TBCH or TBS6H Publication 1756 UM528A EN P April 2004 A 6 Specifications and Module Block Diagrams Publication 1756 UM528A EN P April 2004 Conductors Wire Size Category 22 to 14 AWG 0 324 to 2 08 sq mm stranded 3 64 inch 1 2mm insulation maximum 4 2 Screwdriver Blade Width for RTB 1 8 inch 3 2mm maximum Environmental Conditions Operational Temperature IEC 60068 2 1 Test Ad Operating Cold IEC 60068 2 2 Test Bd Operating Dry Heat IEC 60068 2 14 Test Nb Operating Thermal Shock 0 to 60 C 32 to 1
73. amp 5 OffOn or Timestamp 5 OnOff has new data This tag only clears when the controller acknowledges the new data or all events on the module are reset For more information see page 7 17 EventOverflow Per point Set for an input when the module either e Does not timestamp an input transition The module has Latch CST enabled and the module s on board buffer contains 160 timestamps In this case the module does not have room in its on board buffer to store the timestamp from any additional transitions and does not timestamp those transitions or e Overwrites previously recorded timestamp data The module has Latch CST disabled and the on board buffer contains 160 events In this case the module continues to timestamp input transitions When the module records new transitions it records the data in its buffer and clears the timestamp data from the oldest transition of the 160 This value is cleared if the module is reset EventNumber Per event Running count of the timestamped input transitions this tag increments by one with each new event sent This value is cleared if the module is reset Publication 1756 UM528A EN P April 2004 D 10 Using Module Tags Table D 6 Input Tags in FIFO Mode Tag name Set on a Per Point or Description Modulewide basis CSTTimestamp 2 Per event 64 bit CST timestamp in CST format for the event This value is cleared after the data has bee
74. an ed 125 Input Seance of Events i ed Input Sequence of 5 16 Point 10 30 AC Input 1 l 6 Channel Isolated RTD Analog Input Events module 6 Channel Isolated Thermocouple Analog Input 6 Channel Isolated Thermocouple Analog Input Enhanced 7 a l 16 Point 10v 30V DC Input Source B Click OK 32 Point 10 30 DC Input Source ControlLogix5950 Controller ControlLogix5953 Controller ControlLogix5555 Controller ControlLogixSS60M03SE Controller ControlLogix5561 Controller ontrolLagix55 troller 4 Configure the module The first screen of the configuration wizard is shown below A Name the module B Select the module s slot number C Choose a Communications Format For more information see page 4 5 D Make sure the Minor Revision number matches your module s minor revision E Choose an Electronic Keying method For CST Per Point nn more information see page 5 13 compatible Module F If you are altering the default configuration click Next Go to page 4 6 G If you are using default configuration click Finish Go to page 4 6 Publication 1756 UM528A EN P April 2004 Configuring the Sequence of Events Module 4 5 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 communicat
75. ane Current 295mA 5 1V de amp 2mA 24V de Backplane Power 1 5W Maximum Power Dissipation 5 5W 60 C Module Thermal Dissipation 17 22 BTU hr On State Voltage Range 10 55V de Nominal Input Voltage 24V dc 48V de On State Current Minimum 2 0mA 9V de Nominal 4 5mA 24 31V de Maximum 5 1mA 48 55V de Maximum Off State Current 1 5mA Maximum Off State Voltage 5V de Maximum Input Impedance 10 8kQ 55V de Input Delay Time OFF to ON ON to OFF Hardware Delay 101s nominal 20us maximum Firmware Scan up to 25us Input Filter Time User selectable time Oms to 50ms ASIC delay 175s FIFO 625us CST Per Point Hardware Delay 251s nominal 50us maximum Firmware Scan 25s Input Filter Time User selectable time Oms to 50ms ASIC delay 175s FIFO 625us CST Per Point Timestamp accuracy 100us Cyclic Update Time RPI User selectable 250us minimum 750ms maximum Reverse Polarity Protection Yes Isolation Voltage Inputs to backplane Input to input 250V continuous 125V continuous RTB Screw Torque Cage clamp 4 4 inch pounds 0 4Nm maximum Module Keying Backplane Software configurable RTB Keying User defined mechanical keying RTB and Housing 36 Position RTB 1756 TBCH or TBSGH Publication 1756 UM528A EN P April 2004 A 2 Specifications and Module Block Diagrams Publication 1756 UM528A EN
76. ation on acknowledging data see page 6 12 When the Sequence of Events module overwrites data it sets the EventOverflow tag for that point to inform the controller that events have been overwritten 1 This table assumes the transition occurs on inputs that have Enable CST Capture enabled If Enable CST Capture is disabled the module does not timestamp transitions on that input and therefore Latch CST does not affect module behavior IMPORTANT We suggest you monitor the I EventOverflow bits to make sure you are aware of when transitions were either not timestamped or when timestamp data was overwritten Use the Configuration tab in RSLogix 5000 to enable Latch CST as shown in the example below E Module Properties Local 1 1756 IH16ISOE 1 1 Be xj r Input Filter Time Off gt On On Off EK os r Module Configuration Bits B Latch CST Ce ae Status Offline Cancel Apply Help Reset All CST Click this box to enable the Latch CST feature qaaa aannam Clear the box to disable the feature Publication 1756 UM528A EN P April 2004 Using The Sequence of Events Module in CST Per Point Mode 6 7 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
77. be SD BOK 5 15 Other Inherent Module Features 044 5 16 Removal and Insertion Under Power RIUP 5 16 Module Fault Reporting 0 0 0 0 eee 5 16 Fully Software Configurable 0 5 5 17 Producer Consumer Model 0 0005 5 17 Status Indicator Information 6 5 5 8fo as 4 28 848545 5 18 Full Class I Division 2 Compliance 5 19 Agency Certifications ss 6 0 sce Sed hcdica s Gigi 4b Gosh ptt dea ate 5 19 Chapter Summary and What s Next 0 5 19 Using The Sequence of Events Module in CST Per Point Mode Using The Sequence of Events Module in FIFO Mode Table of Contents 3 Chapter 6 What This Chapter Contains navi ce Heya eae 6 1 Overview of the Mode nunaa anaa 6 1 How Does the Module Store Timestamp Data in CST Per Point Mode oaan uaaa 6 2 What Are The Typical Applications Where CST Per Point Mode is OS 216 Pe Wee Ce ee Ee ee eR 6 4 Configuring the Module for CST Per Point Mode 6 4 Choosing a Communications Format 6 5 Using Latch CST in CST Per Point Mode 6 6 Using Enable CST Capture in CST Per Point Mode 6 7 Managing the Data in CST Per Point Mode 6 8 Module Sends Data to the Controller 6 8 Copying Relevant Input Data to a Separate Data Structure a ry SO tae Re A Ae ee eee 6 10 Acknowledging Latched Timestamp Data 6 12 Sorting the Data 4 th Geka he tds orton ee
78. can only store the data for up to 160 transitions in its on board storage buffers If you fail to empty the buffer as described on page 7 10 faster than it is filled after 160 timestamped input transitions the module overwrites the timestamp from the first transition in its on board buffer with data from the most recent transition If the Sequence of Events module overwrites data it sets the I EventOverflow bit to one for the point where a timestamp was previously recorded but has been deleted to inform the controller that events have been overwritten The Sequence of Events module has timestamped and recorded enough input transitions since the controller last retrieved data that the on board buffer is full Input 3 transitions for OFF to ON Because Latch CST is disabled the module timestamps the transition and records the data in slot 1 of its on board buffer In this case the oldest data i e data in slot 1 is automatically deleted from the module The module sets the EventOverflow tag for that point N I oo Timestamp Event a i i Input H N nput State H Timestamp data 1 Ir gt Jo o o alolo o gt gt oloj 9 alo qj Aolofajalajao qo 2o Hol Slo ala AalolH ofalolo qj ojoj op en SS co Ny S t o ojo oj e 2 2
79. cation 1756 UM528A EN P April 2004 4 8 Configuring the Sequence of Events Module The editing process begins on the main page of RSLogix 5000 fs RSLogix 5000 My_Sequence_of_Events_prd File Edit View Search Logic Communications T elated S sele lj Offline D m RUN No Forces b m 0K Eg E TN No Edits a E vo Redundancy Sal wj B Controller My_Sequence_of_Event Controller Tags Controller Fault Handler Power Up Handler Tasks a fa MainTask g MainProgram Unscheduled Programs 6 6 Motion Groups Ungrouped Axes Trends a Data Types amp User Defined Ga Strings Gi Predefined E Module Defined 6 8 1 0 Configuration A Right click on the module l S A 21113 ff New Module p erm g amp cu Ctri x Copy Ctrl C E Paste Ctrl y Delete Del B Select Properties Cross Reference Ctrl E 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 Make any necessary changes as shown in the example below E Module Properties Local 1 1756 IH16ISOE 1 1 x A Click the tab where you need to reconfigure the module Reset amp lCST Off gt On On Off In this example CST Capture was disabled for several input points M Latch CST B When the module is an reconfigured click OK TYAS lt 1
80. cations In this chapter you read about using the Sequence of Events module s features Chapter 6 describes the Using The Sequence of Events Module in CST Per Point Mode Publication 1756 UM528A EN P April 2004 5 20 Using the Sequence of Events Module Features Notes Publication 1756 UM528A EN P April 2004 Chapter 6 What This Chapter Contains Overview of the Mode Using The Sequence of Events Module in CST Per Point Mode This chapter describes how to use the Sequence of Events module in CST Per Point mode Table 6 1 For information on See page Overview of the Mode 6 1 What Are The Typical Applications Where CST Per Point Mode is 6 4 Used Configuring the Module for CST Per Point Mode 6 4 Managing the Data in CST Per Point Mode 6 8 Module Sends Data to the Controller 6 8 Copying Relevant Input Data to a Separate Data Structure 6 10 Acknowledging Latched Timestamp Data 6 12 Sorting the Data 6 14 Clearing All Data From the Module s Buffers At Once 6 14 In CST Per Point mode the Sequence of Events 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 Enable CST Capture enabled transition e g input 1 is configured so that Enable CST Capture is enabled for OFF to ON transitions and the input turns ON the module timestamps the transition with the current CST value on the backplane The
81. chnical information on the web to assist you in using our products At http support rockwellautomation com you Support 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 For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem with a hardware module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United States 1 440 646 3223 Monday Friday 8am 5pm EST Outside United Please contact your local Rockwell Automation representative for States any technical support issues New Product Satisfaction Return Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned United States Contact your distributor You must provide a Customer Support case number see phone number above to obtain one to
82. communication fault as described below e Chatter The Sequence of Events module can detect chatter on individual inputs and will set the appropriate tag to 1 when chatter exists on an input For example if the module has detected chatter on input 4 Fau t 4 1 e Communication fault The controller sets this tag to 1 for all 32 bits if a communication fault occurs on the module This tag clears when the fault that causes the condition no longer exists Data Per point Status of the input point This data is filtered if the Input Filter feature is used on the module Thus an input change must pass through the filter before it is seen in this tag 0 input is OFF 1 input is ON For example if input 3 is ON Data 3 1 NewData Per point Flag indicating if new timestamp data was detected on the input 0 no new timestamp data on the input 1 new timestamp data on the input since last acknowledged Because input data for all inputs is sent immediately after each timestamped transition and at each RPI this tag is useful to quickly determine on which input the transition occurred For example if the Sequence of Events module sends new input data to the owner controller and NewData 5 1 you know that at least one of the timestamps for input 5 i e Timestamp 5 OffOn or Timestamp 5 OnOff has new data This tag only clears when the controller acknowledges the new data or all events on the module are reset For more informat
83. copy relevant input data from the controller tags to a separate array in the controller s memory IMPORTANT When the Sequence of Events module sends current event data at the RPI it sends data for all the tags described in Table 7 3 on page 7 11 You typically will only need data from specific tags though We recommend you only copy data from those tags to a separate array For example if you only need data from the e event number C EventNumber x e CST timestamp 1 CSTTimestamp 2 e event point EventPoint x e event data EventData x tags for your application we recommend you only copy the data from those tags to a separate array Later you can combine data from multiple Sequence of Events modules and use a Sort routine to determine the order of events with relative time reference that occurred in a specific time period Publication 1756 UM528A EN P April 2004 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
84. cuit z t i The 125V de or t 0 H 24 48Vde input 0 r 1 2V power 1 circuits are r i i shown in greater v4 detail below 43687 125Vdc input circuit 5V IN 0 D D GND 0 es D ka 43835 ControlLogix Display backplane Interface Publication 1756 UM528A EN P April 2004 Overview Appendix B Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System 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 However each timestamp is captured in CST format a 64 bit number that has little meaning other than to indicate which transition occurred first The controller determines an order of transitions but not the real time of each transition The most significant benefits to using the 1756HP GPS module are e The 1756HP GPS module provides a real time reference for CSTs captured in the ControlLogix system e By using the 1756HP GPS module you can make sure geographically separated systems operate from a single time reference e The 1756HP GPS module can convert CST format timestamps to a real time reference IMPORTANT This appendix offers a brief description of how to use the 1756HP GPS module with the ControlLogix Sequence
85. ding on when the input transitions relative to the sample time e ASIC delay 25us Typically the Sequence of Events module can deliver a signal to the ControlLogix backplane within 275us in FIFO mode and 725us in CST Per Point mode after it was received at the removable terminal block RTB these 275us or 725us numbers represent a scenario where the hardware delay is at maximum levels but no input filter is used TIP For fastest propagation of a signal from a field device to the controller use the module in FIFO mode in a local chassis How Does the Sequence of Events Module Operate in a ControlLogix System 2 5 Figure 2 1 Digital signal CST captured here processor a Hardware Filter Scan ASIC delay delay Gre delay ri Signal applied l the RTB User configurable Up to 25us Typically Signal ae 0 50ms 175us FIFO sent to mode or backplane 625us CST Per Point 1756 IB16ISOE 1756 IH161SOE mode For OFF to ON e 10us nominal e 20us maximum For ON to OFF e 25us nominal e 50us maximum For OFF to ON e 10us nominal e 20us maximum For ON to OFF e 50us nominal e 75us maximum 42701 Many factors e g voltage operating temperature if the module is turning ON or OFF affect the signal propagation delay on a module But a nominal delay time can be estimated For example if you are turning ON a 1756 IB
86. dule 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 communication connection to a module Program mode In this mode the following events occur e Controller program is not executing e Inputs are still actively producing data Pulse per second Process by which the 1756HP GPS receives the UCT time reference from the navigation sattelites that are part of the GPS system Relative time Time format used when sorting timestamps in CST format In this case you cannot easily determine what the 64 bit timestamps represent but you can determine an order for the timestamps that will provide a relative reference for when a timestamped transition occurred Remote connection A connection where the controller establishes an individual connection with Sequence of Events modules in a remote chassis Removal and insertion under power RIUP ControlLogix feature that allows a user to install or remove a module or RTB while power is applied Publication 1756 UM528A EN P April 2004 Glossary 4 Publication 1756 UM528A EN P April 2004 Removable terminal block RTB Field wiring connector for Sequence of Events modules Requested packet interval RPI
87. dule in Remote Chassis with Data Coming At Least as Often as RPI l A A olNet Bridge module ControlNet Bridge module Sequence of Events module i Q e 9 Input data multicast in g p module s chassis at RPI i a Input data at least as often as RPI ControlNet 40947 Publication 1756 UM528A EN P April 2004 How Does the Sequence of Events Module Operate in a ControlLogix System 2 9 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 Best Case RPI Multicast Scenario In the Best Case scenario the module performs an RPI multicast with updated channel data just before the reserved network slot is made available In this case the owner controller receives the data almost immediately Worst Case RPI Multicast Scenario In the Worst Case scenario the module performs an RPI multicast just after the reserved network slot has passed In this case the owner controller does not receive data until the next a
88. dules reside in a remote chassis with respect to the location of the controller Some applications must be designed in such a way that a Sequence of Events module cannot reside in the controller s local chassis Yet the controller still needs the timestamp from when transitions occur on the remote module in terms it understands For the timestamp with the input data to make any sense to the controller the CSTs in the separate chassis must be synchronized In other words in this case any chassis that contain Sequence of Events module must synchronized via SynchLink Using a Time Master Each ControlLogix chassis can house a time master ControlLogix controller or 1756 SYNCH module a device that establishes the CST for a ControlLogix chassis In a single chassis scenario the ControlLogix controller typically serves as the time master When you require CST synchronization across multiple chassis you need a time master in each chassis and those masters must receive a single CST from a common source You can use ControlLogix SynchLink modules 1756 SYNCH to synchronize CSTs between ControlLogix chassis In the most basic terms the following occurs to synchronize time between chassis e You must use RSLogix 5000 v13 or greater You can synchronize CSTs between chassis with previous versions of RSLogix 5000 but those versions require a ControlLogix controller be located in each chassis This section describes synchronizing CSTs with
89. e 1 If necessary go offline s RSLogix 5000 Digital_IO 1756 File Edit View Search Logic Comm ele aaee If you are not offline use this RemProg ail Program Mode pull down menu to go offline No Forces No Edits Test Mode 0 E Upload Downoad Erocran fade Bun Mode mea kaats Go fio Faults cg Controler Properties 2 Add the Sequence of Events module to your RSLogix 5000 project f RSLogix 5000 My_Sequence_of_Events_projq File Edit View Search Logic Communications Toc lala S elel ol Offline D m RUN No Forces de aoe f im No Edits a E A J amp v0 Redundancy W9 m a Control Controller My_Sequence_of_Event ler Tags E Control Power Tasks Manta Trends Ga Strings A Right click on 1 0 Configuration B Select New Module H ie MainProgram i Unscheduled Programs 6 6 Motion Groups Ungrouped Axes 6 Data Types iar User Defined oe Predefined Ce Module Defined ller Fault Handler Up Handler sk PJ New Module Ctrl x Ctrl C E Paste Ctrl Publication 1756 UM528A EN P April 2004 4 4 Configuring the Sequence of Events Module 3 When the Select Module Type screen appears select the Sequence of Events module Select Module Type ie A Select the gt 756 IH161S0 6 Ch
90. e guidelines when you handle this equipment e Touch a grounded object to discharge potential Static e Wear an approved grounding wriststrap e Do not touch connectors or pins on component boards e Do not touch circuit components inside the equipment e If available use a static safe workstation When not in use store the equipment in appropriate static safe packaging Publication 1756 UM528A EN P April 2004 Preface 4 Environment and Enclosure Publication 1756 UM528A EN P April 2004 ATTENTION A This equipment is intended for use in a Pollution 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 Without appropriate precautions there may be potential difficulties ensuring electromagnetic compatibility in other environments due to conducted as well as radiated disturbance This equipment is supplied as open type equipment It must be mounted within an enclosure that is suitably designed for those specific environmental conditions that will be present and appropriately designed to prevent personal injury resulting from accessibility to live parts The interior of the enclosure must be accessible only by the use of a tool Subsequent sections of this publication may contain additiona
91. e it IMPORTANT Remember the current event is data that the module is currently producing from its on board buffer at each RPI For more information on how the Sequence of Events module produces data from its on board buffer see page 7 2 In the example the Sequence of Events module produces data from the current event for the controller Figure 7 2 Sequence of Events module a BD ControlLogix controller ee eee A _ _ ____ 1 Module stores data 2 Module produces YN ll in on board buffer E current event data SN 4 0710070 Current event L oo 7100110 oo 0100010 g o 100110 l Fault 0 0j Horon Ae ee OOOO NewData oo 1100101 EventOverlow eee EventNumber e 1 CSTTimestamp 2 oo 4 UCTTimestamp 2 eee al T0T770 EventPoint oe 1110011 EventData oo i ReturningUCTTime i EventsQueuedCount Publication 1756 UM528A EN P April 2004 43810 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 We recommend you use a COP or CPS instruction to programmatically
92. er applied unintended machine motion or loss of process control can occur Exercise extreme caution when using this feature It is recommended that field side power be removed before removing the module 1 Unlock the locking tab at the top of the module 2 Open the RTB door using the bottom tab 3 Hold the spot marked PULL HERE and pull the RTB off the module mae Do not wrap your fingers around the entire door A shock hazard exists 20855 M Publication 1756 UM528A EN P April 2004 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 lt GRAL LL LLA LLL LLLA 2 Pull module out of the chassis EEN EEN FEN BEIN BIS Publication 1756 UM528A EN P April 2004 3 14 Installing the Sequence of Events Module Chapter Summary and In this chapter you read about What s Next e installing the module e keying the RTB and IFM e connecting wiring e assembling the RTB and the housing e installing the RTB or IFM onto the module e removing the RTB from the module e removing the module from the chassis Chapter 4 explains Configuring the Sequence of Events Module Publication 1756 UM528A EN P April 2004 What This Chapter Contains Configuring Your 1
93. er to retrieve data For example if you want to retrieve the data for input 10 you must change this tag to 10 Retrieval Process Similar to Standard Retrieval After you make the output tag changes listed above the controller retrieves the data for each transition on the specified input in the order in which the transitions occur The steps to retrieve the data are the same as those described on page 7 13 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 out of the full 160 that contains data for a transition timestamped at the specified input For example if you are using Retrieval by Point to retrieve data for input 7 and the first transition that occurs on input 7 is the 5th transition the module timestamped the current event is located in slot 5 of the module s on board buffer as shown in Figure 7 6 Figure 7 6 Current event The module produces the data in this slot because the controller is using the Retrieve by Point method to retrieve data aol cn awn gt g 9jo 2 In this example e Q RetrieveByPoint 1 0 159 12 0 1 160 5 1 e 0 PointtoRetrieve 7 JoJ 43813 Publication 175
94. erational Modes 5 3 Enable CST Capture 5 5 Latch CST 5 7 Chatter Detection 5 8 Software Configurable Input Filters 5 10 Electronic Keying 5 13 Module Inhibiting 5 15 Removal and Insertion Under Power RIUP 5 16 Module Fault Reporting 5 16 Fully Software Configurable 5 17 Producer Consumer Model 5 17 Status Indicator Information 5 18 Full Class Division 2 Compliance 5 19 Agency Certifications 5 19 Publication 1756 UM528A EN P April 2004 5 2 Using the Sequence of Events Module Features Determining Module Compatibility Publication 1756 UM528A EN P April 2004 Primarily a Sequence of Events module is used to timestamp input data However additionally the module interfaces to sensing 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 Typical input devices include e auxiliary contacts e limit switches When designing a system using Sequence of Events modules you must consider e the voltage necessary for your application e whether you need a solid state device e current leakage e if your application should use sinking or sourcing wiring For more information on compatibility of other Rockwell Automation products to Sequence of Events modules see the I O Systems Overview publication CIG SO001 There are two types of features available on the Sequence of Events module e Module Features That Can Be
95. erial number 1 5 status 1 5 vendor ID 1 5 WHO service 1 5 module status retrieving 1 5 module status indicators 5 18 network update time NUT for ControlNet 2 2 0 operational mode FIFO mode 1 3 operational modes 5 3 5 4 CST Per Point mode 1 3 4 5 5 3 6 1 6 14 FIFO mode 4 5 5 3 7 1 7 20 output tags in CST Per Point mode D 6 in FIFO mode D 11 ownership 2 2 P preventing electrostatic discharge Preface 3 product identification catalog number 5 13 major revision 5 13 minor revision 5 13 product type 5 13 vendor 5 13 propagating signal from field device to backplane 2 4 2 5 related documentation Preface 2 remote chassis configuring the module in a remote chassis 4 9 4 10 module behavior in remote chassis 2 8 2 10 when chassis is connected via Con trolNet 2 8 2 10 when chassis is connected via Ether Net IP 2 10 scenarios for data transfer 2 9 removable terminal block RTB 1 4 assembling the RTB and housing 3 7 cabinet size consideration with the extended depth housing 3 9 connecting wiring 3 4 3 5 extended depth housing 3 5 3 8 3 9 installing 3 10 3 11 mechanically keying the RTB 3 3 recommendations for using the extended depth housing 3 9 recommendations for wiring RTB 3 5 removing 3 12 using the cage clamp RTB 3 4 using the spring clamp RTB 3 5 removal and insertion under power RIUP 3 1 5 16 removing the module 3 13 removing the RTB 3 12 requested packet interval RPI 2
96. ervice Code 32 hex Class 70 hex Instance 1 Attribute 1 hex Source Element Controller tag where the CST format timestamp is located Source Length 8 Destination Destination tag for reply data Publication 1756 UM528A EN P April 2004 Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System B 7 The screen below shows the Configuration tab for an example MSG Message Configuration GPSConvertCSTMsg Configuration Communication Tag Message Type CIP Generic kg Service Custom gt Source Element GPSConvertCST CST 7 Source Length fe Bytes GPSConvertCST Ye z New Tag Type Service pz 5 fro Code 32 Hex Class 70 Hex Instance 1 Attribute f1 Hex O Enable Enable Waiting Start Eror Code Extended Error Code Error Path Error Text Done Length 0 I Timed Out Cancel Apply Help Table B 2 shows the two formats in which a 1756HP GPS may return timestamp data Table B 2 Field Bytes Description Year 4 Gregorian year Month 4 Gregorian month Day 4 Gregorian day Hour 4 Gregorian hour Minute 4 Gregorian min Second 4 Gregorian sec Microsecond 4 Gregorian Sec UTC 8 Corresponding UCT value CST 8 Given CST value Publication 1756 UM528A EN P April 2004 B 8 Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System Convert
97. figuration Tags in FIFO Mode Tag name C LatchEvents Type BOOL Using Module Tags D 7 Description 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 the 1756HP GPS module one in UCT format and the other a corresponding CST format value to these tags When these tags are nonzero numbers the Sequence of Events module converts timestamps from CST format to UCT format before sending them to the controller Additionally ReturningUCTTime 1 Typically the following events occur e A 1756HP GPS module produces CST UCT Time pairs that are sent to the controller e The controller copies the pairs to the Sequence of Events module every pulse per second PPS We recommend you copy the pairs every PPS e The Sequence of Events module uses the streams of pairs to calculate UCT timestamps for input data including the use of calculating drift between the clocks If these tags 0 the Sequence of Events module sends timestamps in CST format and ReturningUCTTime 0 Tags Used in FIFO Mode Configuration Tags Table D 5 describes the configuration tags generated in RSLogix 5000 when you use the Sequence of Events module in FIFO Mode Description Latches events so that timestamp data from an input transition will not be overwritten until acknowledged 0 CST not latched default 1 CST
98. format the controller requested via the MSG configuration Figure B 2 Controller Sequence of 1756HP GPS Events module module mm oo 1 Timestamps sent in CST format to controller 7 Timestamp sent in CST format via MSG to 1756HP GPS Q O Timestamp converted from CST format to Gregorian and UCT format 3 A 4 Converted timestamp sent to controller Publication 1756 UM528A EN P April 2004 B 4 Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System Determining the Absolute First Fault Across Multiple Chassis Publication 1756 UM528A EN P April 2004 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 module in a local chassis However the greatest benefit of using the 1756HP GPS module comes when you need to determine the absolute first fault among devices connected to multiple Sequence of Events modules in remotely located chassis To determine absolute first fault among devices connected to multiple Sequence of Events modules in remotely located chassis you must first synchronize the chassis in other words you must make sure all the Sequence of Events modules are working from the sa
99. 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 1 0 status STLEDs Description This yellow display indicates the ON OFF state of the field device Module status OK LED The LED status This red green display indicates the module s communication module health status indicators used on the Sequence of Events module are shown in Figure 5 4 Figure 5 4 SOE INPUT T012345670 ST 8 9 10111213 1415 K 8 20945 For more information on how to use the Sequence of Events module s LED status indicators and RSLogix 5000 when troubleshooting your application see Chapter 8 Troubleshooting the Sequence of Events Module Chapter Summary and What s Next 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 IMPORTANT Modules should not be pulled under power nor should a powered RTB be removed in a Class I Division 2 environment Agency Certifications The Sequence of Events module is marked for any agency certifications e g UL CSA CE FM and C Tick it has obtained See the module s label for all agency certifi
100. g cleared from the module buffer prior to resetting events To change retrieval methods change the O RetrieveByPoint tag to the new method e To use the standard retrieval by time method O RetrieveByPoint 0 e To use the retrieval by point method O RetrieveByPoint 1 In this chapter you read about using the Sequence of Events module s features Chapter 8 describes the Troubleshooting the Sequence of Events Module What This Chapter Contains Using LED Status Indicators Chapter 8 Troubleshooting the Sequence of Events Module This chapter describes how to troubleshoot the Sequence of Events module Table 8 1 For information on See page Using LED Status Indicators 8 1 Using RSLogix 5000 To Troubleshoot the Module 8 2 Your Sequence of Events module has yellow indicators that show individual I O state and a bi colored red green indicator that shows module status with an OK Status indicators are located on the front of the module The LED status indicators used on the Sequence of Events module are shown in Figure 8 1 Figure 8 1 SOE INPUT 3 ST 012345670 ST 8 9 10111213 1415 K 20945 During power up an indicator test is done and the following occurs e OK indicator turns red for 1 second and then turns to flashing green if it has passed the self test e I O status indicators turn ON for a maximum of 2 seconds and then turn OFF Publ
101. he transition i 10000000 2 in CST format 2 Sends input data with the timestamp in CST format to the controller il Input 15 oo Bea LEN Module Sends Timestamp in UCT Format me The module is configured so that input 1 is Enable ll CST Capture enabled for OFF to ON transitions i 7110100 and to send timestamp data in UCT format In other words the controller copied timestamp data Input 0 oo L hi to the following tags Input 1 m 0101100 e 0 UCTTime nps 9 Q ioooo000 S e 0 CSTTime nut oo hroooo0n o as described on page B 8 7 1110100 When input 1 transitions from OFF to ON the 2 To controller module Input 15 P oooo000 3 in UCT format 1 Timestamps the transition 0000000 2 Converts the timestamp from CST to UCT __ Po format 3 Sends input data with the timestamp in UCT format to the controller Publication 1756 UM528A EN P April 2004 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 Appendix C Overview Synchronizing CSTs Across Multiple Chassis 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 You can synchronize CSTs between chassis synchronization is especially useful when Sequence of Events mo
102. hysical module and the module configured in the software to match Download The process of transferring the contents of a project on the workstation into the controller Electronic keying A feature where modules can be requested to perform an electronic check to make sure that the physical module is consistent with what was configured by the software Exact match An electronic keying protection mode that requires the physical module and the module configured in the software to match according to vendor catalog number major revision and minor revision First In First Out FIFO Operating mode on the Sequence of Events module in which the module timestamps an unlimited number of input transitions regardless of direction G e either OFF to ON or ON to OFF or input G e the same input can transition many times and the module will timestamp every transition and stores them in an on board buffer Global positioning system GPS A constellation of 24 radio navigation satellites that transmit signals used by GPS receivers to determine precise location position velocity and time solutions Inhibit A ControlLogix process that allows you to configure a Sequence of Events module but prevent it from communicating with the owner controller In this case the controller behaves as if the I O module does not exist at all Glossary 3 Interface module IFM A module that uses prewired cable to connect wiring to an I O mo
103. ication 1756 UM528A EN P April 2004 8 2 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 OK Steady green light The inputs are being multicast and in normal operating state None Flashing green light The module has passed internal diagnostics but is not multicasting inputs Configure the module with RSLogix 5000 Flashing red light One of the following e Previously established communication has timed out e A FLASH update is in progress e Check controller and chassis communication e Finish the update Steady red light An unrecoverable error has occurred on the module Replace the module 1 0 State Yellow Using RSLogix 5000 To Troubleshoot the Module Warning icon appears when a communications fault occurs or if the module is inhibited Publication 1756 UM528A EN P April 2004 The input is active None In addition to the LED status indicators on the module RSLogix 5000 alerts you to fault and other conditions in one of three ways e Warning signal on the main screen next to the module This occurs when the connection to the module is broken tions Tools Window Help alsa a dae AA lel I I e ae ess re hr t S Nera sonra a
104. if you want to avoid using buffer space on the Sequence of Events module for events in which you have no interest 1 CST Capture enabled default for ON to OFF input transitions For more information on Enable CST Capture see page 5 5 C ChatterEvents 16 SINT 16 Number of events required in ChatterTime 16 period to determine a chatter condition 0 Disable Chatter Detection 1 Illegal value The number of events must be greater than 1 The maximum value is 127 For more information on Chatter Detection see page 5 8 C ChatterTime 16 INT 16 Time period in milliseconds in which the number of events in the ChatterEvents tag must occur to declare a chatter condition For example if ChatterEvent 10 and ChatterTime 20 and 11 events occur on the point in a 20ms time period chatter is declared on the point When chatter is declared the input faults and no longer timestamps transitions that occur on the point When chatter ceases the input returns to normal operation The Sequence of Events module considers chatter to have ceased when the configured chatter time elapses with no transitions occurring on the input For more information on Chatter Detection see page 5 8 Publication 1756 UM528A EN P April 2004 D 4 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 I
105. ile Edit View Search Logic Communications Tools Wine alsa S sel olf _ Offline D E RUN E E Pail No Forces b Needs Ble ye aE Redundancy W9 D KDG B S Controller My_Sequence_of_Event Controller Tags Controller Fault Handler Power Up Handler a Tasks z fa MainTask amp MainProgram Unscheduled Programs Motion Groups Ungrouped Axes i Trends B 63 Data Types Ca User Defined ier Strings Gp Predefined Gi Module Defined 1 0 Configuration fi 1 1756 IH16I50E Local_Sequ a fil 2 1 1756 CNB E Local_Contro amp Cut Ctrl x Ba Copy Ctrl C E Paste trey Delete Del Cross Reference Ctri E Properties 8 Configure the new Sequence of Events module as described earlier in this chapter Configuring the Sequence of Events Module 4 11 Chapter Summary and In se chapter you read about configuring your Sequence of Events What s Next seer Chapter 5 describes Using the Sequence of Events Module Features Publication 1756 UM528A EN P April 2004 4 12 Configuring the Sequence of Events Module Notes Publication 1756 UM528A EN P April 2004 Chapter 5 Using the Sequence of Events Module Features What This Chapter This chapter describes the features available on the Sequence of Contains Events module Table 5 1 For information on See page Determining Module Compatibility 5 2 Two Op
106. information on which tags are generated in each operational mode and therefore what data is sent to the controller at each RPI see Appendix D Using Module Tags Enable CST Capture Enable CST Capture instructs the Sequence of Events module to capture the CST whenever specific input points transition You can use this feature to instruct the module to capture the CST when the inputs transition from e OFF to ON only e ON to OFF only or e both OFF to ON and ON to OFF How Does the Sequence of Events Module Operate in a ControlLogix System 2 7 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 Because the RPI and Enable CST Capture functions are asynchronous to the program scan it is possible for an input to change state during program scan execution The point must be buffered to prevent this Copy the input data from your input tags to another structure and use the data from there TIP IMPORTANT To minimize traffic and conserve bandwidth we recommend you use a larger RPI value if the Enable CST Capture option is used and the module is located in the same chassis as its owner All points on the Sequence of Events module have Enable Capture CST enabled by default for both ON to OFF and OFF to ON Additionally you must specify an RPI regard
107. ing 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 Tag Description Module Fault This word provides fault summary reporting It s tag name is Fault Word Each bit corresponds to an individual input e If a communication fault occurs on the Sequence of Events module all 32 bits in the Module Fault Word are set to 1 e If chatter is detected on any input points the bit corresponding to that point is set to 1 Figure D 1 Bit 0 42676 A communications fault sets all bits in the Module Fault Word Publication 1756 UM528A EN P April 2004 D 2 Using Module Tags Module Tag Names and Definitions The tags associated with the Sequence of Events module depends on the type of module and the Communications Format chosen during configuration For each operational mode there are three sets of tags e Configuration e Input e Output Tags Used in CST Point Per Mode Configuration Tags Table D 2 describes the configuration tags generated in RSLogix 5000 when you use the Sequence of Events module in CST Per Point Mode Table D 2 Configuration Tags in CST Per Point Mode Tag name Type Description C LatchEvents BOOL Latches events so that timestamp data from an input transition will not be overwritten un
108. ing ControlNet Communication Modules in Logix5000 Control Systems user manual publication CNET UMO01 For more information on the ControlLogix EtherNet IP Bridge module see the Using EtherNet IP Communication Modules in Logix5000 Control Systems user manual publication ENET UMO01 Publication 1756 UM528A EN P April 2004 4 10 Configuring the Sequence of Events Module A Right click on the local communication module B Select New Module A Right click on the remote communication module B Select New Module Publication 1756 UM528A EN P April 2004 4 Add a communications module to the remote chassis Events_project 1756 File Edit View Search Logic Communications Tools Windc alsia a see oof Offline f ERUN EJ Path No Forces Le aoe NoEdis Ble in a i Redundancy De D TFA Fa B S Controller My_Sequence_of_Event Controller Tags Controller Fault Handler 5 Power Up Handler 8 Tasks S S MainTask amp MainProgram Unscheduled Programs J Motion Groups i Ungrouped axes Gi Trends i e Data Types i User Defined Ga Strings i Predefined Gig Module Defined B 86 1 0 Configuration f 1 1756 IH16I50E Local_Sequ NB E Le 5 Select a communications module for the remote chassis 6 Configure the communications module in the remote chassis 7 Add a Sequence of Events module to the remote chassis RSLogix 5000 My_Sequence_of_Events_project 175 F
109. ing The Sequence of Events Module in FIFO Mode This chapter describes how to use the Sequence of Events module in FIFO mode Table 7 1 For information on See page OveviewoftheMode To vwa What the Typical Applications Where FIFO Mode is Used 7 4 Configuring the Module for FIFO Mode 7 4 Retrieving Data in FIFO Mode 7 10 Clearing All Data From the Module s Buffers At Once 7 20 Changing Between Retrieval Methods 7 20 In First In First Out FIFO mode the Sequence of Events module timestamps multiple input transitions on any CST Capture enabled inputs The module stores the timestamp data in an on board buffer that holds data for up to 160 unique transitions and their timestamps When an input transitions the module timestamps the event and records specific input data related to the transition The owner controller must retrieve the data 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 data for up to 160 timestamped transitions in its on board buffers if you manage the buffer effectively G e 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 Publication 1756 UM528A EN P April 2004 7 2 Using The Sequence of Events Module in FIFO Mode How Does the On Board Buffe
110. ing Timestamps By default the Sequence of Events module uses the CST to timestamp f CSTF tt input transitions in CST Per Point mode You can configure the rom orma 0 module to convert CST timestamps to UCT timestamps before sending Universal Coordinated the data to the owner controller Time Format To configure the Sequence of Events module to convert timestamps to UCT in CST Per Point mode you copy a pair of timestamps one in CST format and one in UCT format from the 1756HGPS module to the following tags in the Sequence of Events module s output word e O UCTTime e O CSTTime Miotiptia fhe O UCTTime and O CSTTime tags 0 the Sequence of Events module sends timestamp data to the controller in CST format If the O UCTTime and O CSTTime tags a nonzero number the Sequence of Events module sends timestamp data to the controller in UCT format Figure B 4 shows an example of a ladder logic rung that copies the timestamp pair from the 1756HP GPS module to the Sequence of Events module s output tags You need to do this for every Sequence of Events module in your system if you want the module to send timestamps in UTC format Figure B 4 GPS_SOEuseUTC 3 GPS PPS OneShots 0 8 E E tons PS Synchronous Copy File Source GPS UTC O Dest Local 1 0 UCTTime 0 Length 4 In this example the synchronous copy begins at the GPS UTC tag on the 1756HP GPS module and copies 4 DINTs because the Length 4 w
111. ing the RTB or IFM cable onto the module Jumper bar Publication 1756 UM528A EN P Device you can use to connect multiple points in non isolated wiring application as shown on page 3 6 April 2004 Using Module Identification and Status Information What is the ControlLogix Sequence of Events Module 1 5 Each Sequence of Events module maintains specific identification information that separates it from all other modules This information assists you in tracking all the components of your system For example you can track module identification information to be aware of exactly what modules are located in any ControlLogix chassis at any time While retrieving module identity you can also retrieve the module s status Each module maintains the information listed in Table 1 4 Table 1 4 Module Identification and Status Information Module Identification Description Product Type Module s product type Product Code Module s catalog number Major Revision Module s major revision number Minor Revision Module s minor revision number Status Module s status Returns the following information e Controller ownership if any e Whether module has been configured e Device Specific Status such as e Self Test Flash update in progress e Communications fault Not owned Internal fault need flash update e Run mode Minor recoverable fault e Minor unrecoverable fault Major recoverable fau
112. ion see page 7 17 EventOverflow Per point Set for an input when the module either e Does not timestamp an input transition The module has Latch CST enabled and the module s on board buffer contains 160 timestamps In this case the module does not have room in its on board buffer to store the timestamp from any additional events and does not timestamp new transitions or e Overwrites previously recorded timestamp data The module has Latch CST disabled and the on board buffer contains 160 events In this case the module continues to timestamp input events When the module records new transitions it records the data in its buffer and overwrites the timestamp data from the oldest transition of the 160 This value is cleared if the module is reset or when an event is acknowledged Publication 1756 UM528A EN P April 2004 7 12 Using The Sequence of Events Module in FIFO Mode Table 7 3 Input Tags in FIFO Mode Tag name Set ona Per Point or Description Modulewide basis EventNumber Per point Running count of the timestamped input transitions this tag increments by one with each new event The event number is the identifier that uniquely indicates which event the Sequence of Event module is returning to the controller When you copy this value to the O EventAck tag the Sequence of Events module begins producing the next event in its buffer as the next event becomes the current event This
113. ion frequency depends on module configuration and where in the control system that input module physically resides This is called the Producer Consumer model The Sequence of Events module produces the input data and the controller consumes the data All Sequence of Events module inputs are updated asynchronous to the controller s task execution In other words an input may be updated in the controller at any time during the controller s execution of the tasks it is configured to run The input device determines when the input is sent based on its configuration Triggering Event Tasks You can configure Sequence of Events modules to trigger an event task The event task offers ControlLogix controller users a task that executes a section of logic immediately when an event i receipt of new unseen data occurs Your Sequence of Events module can trigger event tasks When using a Sequence of Events module to trigger an event task remember these considerations e Only one input module can trigger a specific event task e The input module triggers the event task based on the Enable CST Capture configuration for the module The Enable CST Capture configuration defines which points prompt the module to produce data if they turn ON or OFF This production of data triggers the event task e Typically Enable CST Capture for only one point on the module If you Enable CST Capture for multiple points a task overlap of the event task ma
114. ions format without deleting the module from the project and recreating it For more information on using the Sequence of Events module in CST Per Point mode see Chapter 6 For more information on using the Sequence of Events module in FIFO mode see Chapter 7 Using the Sequence of Events Module Features 5 5 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 e OFF to ON only e ON to OFF only or e both OFF to ON and ON to OFF 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 IMPORTANT All points on the Sequence of Events module have Enable Capture CST enabled by default for both ON to OFF and OFF to ON transitions Additionally you must specify an RPI regardless of whether you use Enable Capture CST on any input points If a change does not occur within the RPI timeframes the module will still multicast data at the rate specified by the RPI Publication 1756 UM528A EN P April 2004 5 6 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 E Module Properties
115. ions format unless you delete and recreate the module Table 4 2 lists the communications formats used with input modules Table 4 2 If you want the Sequence of Events choose this communication format module to operate in this mode CST Per Point mode CST Per Point FIFO mode CST FIFO Mode For more information on the Sequence of Events module s operational modes see page 5 3 Electronic Keying 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 e Exact Match e Compatible Module e Disable Keying For more information on electronic keying see page 5 13 Publication 1756 UM528A EN P April 2004 4 6 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 configuration for your module in RSLogix 5000 Some of the screens that appear during this initial module configuration process are blank and are not shown here However those screens can be important during online monitoring To see these screens in use see Chapter 8 Troubleshooting the Sequence of Events Module Write specific configuration for your Sequence of Events module on
116. iption Publication 1756 UM528A EN P April 2004 6 6 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 Table 6 2 describes how Latch CST affects the module in CST Per Point mode Table 6 2 If Latch CST is the following occurs Enabled The Sequence of Events module timestamps two transitions for each input one for OFF to ON and one for ON to OFF If similar transitions occur on inputs where a transition has already been timestamped and the data was not yet acknowledged for more information on acknowledging data see page 6 12 the module does not timestamp the new transition When transitions occur that the Sequence of Events module does not timestamp the module sets the EventOverflow tag for that point to inform the controller that an input transitioned but a timestamp was not produced for the transition Typically Latch CST is enabled in CST Per Point mode Disabled The Sequence of Events module timestamps each transition for each input as it occurs In this case when multiple transitions occur in the same direction on the same input the module records the new timestamp data overwriting any previously recorded data which had yet to be acknowledged for more inform
117. iption Modulewide basis Fault Per point Indicates if a fault has occurred for the input 0 no fault 1 fault The fault can be chatter or communication fault as described below e Chatter The Sequence of Events module can detect chatter on individual inputs and will set the appropriate tag to 1 when chatter exists on an input For example if the module has detected chatter on input 4 Fau t 4 1 e Communication fault The controller sets this tag to 1 for all 32 bits if a communication fault occurs on the module This tag clears when the fault that causes the condition no longer exists Data Per point Status of the input point This data is filtered if the Input Filter feature is used on the module Thus an input change must pass through the filter before it is seen in this tag 0 input is OFF 1 input is ON For example if input 3 is ON Data 3 1 NewData Per point Flag indicating if new timestamp data was detected on the input 0 no new timestamp data on the input 1 new timestamp data on the input since last acknowledged Because input data for all inputs is sent immediately after each timestamped transition and at each RPI this tag is useful to quickly determine on which input the transition occurred For example if the Sequence of Events module sends new input data to the owner controller and NewData 5 1 you know that at least one of the timestamps for input 5 i e Timest
118. ix backplane A time master either a ControlLogix controller or 1756 SYNCH module generates the timer and sets it on the backplane All other modules in the chassis have access to the CST and adjust their time reference based on the backplane time reference Publication 1756 UM528A EN P April 2004 1 2 What is the ControlLogix Sequence of Events Module Publication 1756 UM528A EN P April 2004 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 You can propagate the same CST value across multiple chassis effectively making sure that modules in separate chassis use the same time reference in all their operations if necessary You can extend a single CST value across multiple chassis that are physically connected via 1756 SYNCH modules Additionally multiple ControlLogix systems even those that are geographically separated can use the 1756HP GPS module to share a common real time reference For more information on extending a single CST value across multiple chassis see Appendix C On Board Data Storage Once a CST timestamp is captured for an input transition the module s operational mode impacts how the module functions with respect to e what data is stored on board e how much data is stored for each input point
119. ke this publication more useful for you 2 3 Can we add more information to help you Completeness all necessary information procedure step illustration feature is provided Ae example guideline other explanation definition Technical Accuracy 1 Zn 3 Can we be more accurate all provided information is correct text illustration Clarity 1 2 3 How can we make things clearer all provided information is easy to understand Other Comments You can add additional comments on the back of this form Your Name Your Title Function Would you like us to contact you regarding your comments Location Phone ___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 ClG C0521C EN P May 2003 PN957859 83957782 91 Other Comments PLEASE FASTEN HERE DO NOT STAPLE PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Allen Bradley BELIANCE JB ELECTRIC SrA DOGE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Rockwell Automation Rockwell Automation provides te
120. l Throughout this manual we may use notes to make you aware of safety considerations Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you ATTENTION e identify a hazard e avoid a hazard e recognize the consequence Tava Labels may be located on or inside equipment to alert people that dangerous voltage may be present BURN HAZARD Labels may be located on or inside equipment to alert people that surfaces may be dangerous temperatures Purpose of This Manual Who Should Use This Manual Preface 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 Availability date 1756 IB16ISOE 16 point 10 50V dc module June 2004 1756 IH16ISOE 16 point 90 140V de April 2004 module mM The two types of Sequence of Events
121. l information regarding specific enclosure type ratings that are required to comply with certain product safety certifications See NEMA Standards publication 250 and IEC publication 60529 as applicable for explanations of the degrees of protection provided by different types of enclosure Also see the appropriate sections in this publication as well as the Allen Bradley publication 1770 4 1 Industrial Automation Wiring and Grounding Guidelines for additional installation requirements pertaining to this equipment What is the ControlLogix Sequence of Events Module How Does the Sequence of Events Module Operate in a ControlLogix System Installing the Sequence of Events Module Table of Contents Chapter 1 What This Chapter Contains beaded eee 1 1 What does Sequence of Events Module Do 1 1 Timestamping Using the Coordinated System Time CST 1 1 On Board Data Storage 23 aya rs eh ea A 1 2 Two Modes of Operation n sanaaa doe eee ds 1 3 What Else Does the Sequence of Event Module Do 1 3 Understanding the Module s Physical Features 1 4 Using Module Identification and Status Information 1 5 Chapter Summary and What s Next 1 6 Chapter 2 What This Chapter Contains 0000005 2 1 Differences Between Sequence of Events Module and Standard Digital I O o aana gan Beak Se ead 2 1 Similar Functionality to Standard ControlLogix DC Inpit Modules
122. le Block Diagrams Appendix B Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System Appendix C Using the Sequence of Events Module for Absolute First Fault Detection Appendix D Using Module Tags Appendix E Using Sample RSLogix 5000 Projects with the Sequence of Events Module Table Preface 3 lists related ControlLogix documentation that may assist you when using the Sequence of Events module Table Preface 3 Related Documentation Catalog Document title Publication number number 1756 A4 A7 ControlLogix Chassis Series B Installation 1756 IN080 A10 A13 A17 Instructions 1756 PA72 B ControlLogix Power Supply Installation 1756 5 67 PB72 B Instructions 1756 PA75 ControlLogix Power Supply Installation 1756 5 78 PB75 Instructions 1756 PH75 ControlLogix 125V DC 90 143V Power Supply 1756 IN589 1756 Series ControlLogix Module Installation Instructions Multiple 1756 IN Each module has separate installation numbers document 1756 CNB Using ControlNet Communication Modules in CNET UM001 CNBR Logix5000 Control Systems User Manual 1756 Lx ControlLogix System User Manual 1756 UM001 Preface 3 Preventing Electrostatic Discharge This module is sensitive to electrostatic discharge ATTENTION This equipment is sensitive to electrostatic discharge which can cause internal damage and affect normal operation Follow thes
123. le timestamps In CST Per Point mode this tag has lesser importance than in FIFO mode This value is cleared if the module is reset Timestamp 16 0ffOn 2 Per point Timestamp value in CST or UCT format with an input s OFF to ON transition This tag is a 16 x 2 32 bit array This value is cleared after the data has been acknowledged via the O EventAck and O NewData tags For more information on clearing timestamp data see page 6 12 Timestamp 16 OnOff 2 Per point Timestamp value in CST or UCT format with an input s ON to OFF transition This tag is a 16 x 2 32 bit array This value is cleared after the data has been acknowledged via the O EventAck and O NewData tags For more information on clearing timestamp data see page 6 12 1 With the Per point tags there is one bit per input For example bit 0 represents input 0 bit 7 represents input 7 and so on Publication 1756 UM528A EN P April 2004 D 6 Using Module Tags Table D 4 Output Tags in CST Per Point Mode 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 Tag name Type Description O EventAck DINT To acknowledge reset of event the controller writes back the EventNumber read to transition buffers in Queuing mode or to unlatch events in 16 point mode 0 acknowledging an ON to OFF event 1 acknowledging an OFF to ON event 2 acknowledging both ON to
124. less of whether you use Enable Capture CST on any input points The default RPI at module creation in an RSLogix 5000 project is 10ms Publication 1756 UM528A EN P April 2004 2 8 How Does the Sequence of Events Module Operate in a ControlLogix System Sequence of Events Module 1f your Sequence of Events module physically resides in a chassis in a Remote Chassis A Owner controller A Cont other than where the owner controller is e g 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 The RPI and Enable CST Capture behavior still define when the module multicasts data within its own chassis as described in the previous section but only the value of the RPI determines when the owner controller receives it over the network Remote Input Module Connected Via ControlNet When a Sequence of Events module resides in a remote chassis connected by a scheduled ControlNet network the RPI e instructs the module to multicast data in its own chassis at a specific interval e reserves a spot in the stream of data flowing across the ControlNet network The timing of this reserved spot may or may not coincide with the exact value of the RPI but the control system guarantees that the owner controller receives data at least as often as the specified RPI Figure 2 2 Sequence of Events Mo
125. lt Major unrecoverable fault Vendor ID Module manufacturer vendor for example Allen Bradley Serial Number Module serial number Length of ASCII Text String Number of characters in module s text string ASCII Text String Module s ASCII text string description IMPORTANT You must perform a WHO service to retrieve this information Publication 1756 UM528A EN P April 2004 1 6 What is the ControlLogix Sequence of Events Module Chapter Summary and In this chapter you read about what the ControlLogix Sequence of What s Next Events module is Chapter 2 explains How Does the Sequence of Events Module Operate in a ControlLogix System Publication 1756 UM528A EN P April 2004 Chapter 2 What This Chapter Contains Differences Between Sequence of Events Module and Standard Digital 1 0 Table 2 2 Difference Additional data produced for controller How Does the Sequence of Events Module Operate in a ControlLogix System This chapter describes how the Sequence of Events module operates in a ControlLogix system Table 2 1 For information on See page Ownership 2 2 Using RSNetWorx and RSLogix 5000 2 2 Propagating a Signal From Field Device to Backplane 2 4 Sequence of Events Module in a Local Chassis 2 6 Sequence of Events Module in a Remote Chassis 2 8 In many aspects the Sequence of Events module behaves the same as other ControlLogix digital input modules However the module
126. lter setting In this case the module considers the transition valid and sends the data timestamped at the original transition to the controller Figure 5 2 Input turns ON timestamp recorded Input turns OFF before 2ms have elapsed 4 Input turns ON and remains ON for at least 2ms in the time period that is 4x the input filter setting i e 8ms The module sends the timestamp recorded at the original transition point to the controller 43672 0 1 2 3 4 5 6 7 8 Time in milliseconds Publication 1756 UM528A EN P April 2004 5 12 Using the Sequence of Events Module Features e Scenario 3 The input turns ON but turns OFF before 2ms Cength of the input filter setting elapses In this case the Sequence of Events module continues to scan the input every 25us for 4x the length of the input filter setting G e for 8ms In those 8ms the input never remains ON for at least 2ms G e the input filter setting In this case the module considers the transition invalid and drops the data timestamped at the original transition Figure 5 3 Input turns OFF before In none of these time periods is 2ms have elapsed the input ON for at least 2ms After 8ms i e 4x the input filter setting the module drops the data recorded at the original transition If an RPI occurs during this 8ms the module sends the controller its current valid input data the data that s sent does not include data fro
127. m the transition describes in this graphic because the timestamp has not been validated Input turns ON timestamp 1 43671 3 4 5 6 et The next time the input turns ON the Time in milliseconds module records the transition as timestamp 1 Use the Configuration tab in RSLogix 5000 to configure Input Filters as shown in the example below fal Module Properties Local 1 1756 IH16ISOE 1 1 General Connection Module Info Configuration Backplane Chatter Detection Le m Input Filter Time Off gt On On Off a r Module Configuration Bits Beset Al CST Type the filter times or use the increase decrease arrows to configure the Input Filter Time is V Latch CST The Input Filter Time range is 0 o EE 2 EN 4 fag to 50ms 8 el KI Status Offline Cancel Apply Help TY lt 1 lt 1 o jojojojojojojo a o jojojojojojojo Publication 1756 UM528A EN P April 2004 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 e Exact Match e Compatible Module e Disable Keying
128. me time reference the CSTs in their respective chassis You can synchronize CSTs among multiple ControlLogix chassis via the ControlLogix SynchLink module This method can only be used if the chassis are located in close enough proximity to physically connect the chassis via SynchLink fiber For more information on using SynchLink to synchronize multiple ControlLogix chassis see Appendix C The 1756HP GPS modules in each system receive a common time from the satellite that can be correlated to CST format timestamps produced in each system to report an absolute time reference for both systems effectively synchronizing the chassis The 1756HP GPS module only allows conversion for 1 hour conversions to UCT should be done shortly after the event is received Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System B 5 In this example the following are required e The CST in each ControlLogix system must be synchronized across chassis e Each ControlLogix system must contain a 1756HP GPS module e Once the controllers in each system receive CST format timestamps they must send the timestamps to the 1756HP GPS modules in their respective chassis for conversion to UCT in wall clock format Figure B 3 ControlLogix system 1 x 222 EEE Local chassis with controller Sequen oon fees of Events modules 1756 SYNCH modules and 1756HP GPS modules SynchLink SynchLink Control
129. module so the controller automatically writes 1s for all bits in the word a a 4 gt Monitor Tags Publication 1756 UM528A EN P April 2004 8 4 Troubleshooting the Sequence of Events Module The fault type is listed here Chapter Summary and What s Next Publication 1756 UM528A EN P April 2004 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 W Module Properties Local 1 1756 IH16ISOE 1 1 General Connection Module Info Configuration Backplane Beequested Packet Interval RPI 100 4ms 02 7500 Serna T Inhibit Module Roary oe b T Major Fault On Controller If Connection Fails While in Run Mode 2 7i a hin Module Fault i Tpit Tn Sys 0204 Connection Request Error Connection request timed out ald on Suet aa aap Status Faulted a For a detailed listing of the possible faults their causes and suggested solutions see Module Faults in the online help In this chapter you learned about troubleshooting the module Appendix A lists the Sequence of Events module s Specifications and Module Block Diagrams Appendix A 1756 IB16ISOE Specifications Specifications and Module Block Diagrams Number of Inputs 16 Individually isolated Module Location 1756 ControlLogix Chassis Backpl
130. module produces data for the owner controller when the input filter and chatter detection criteria have been met and at subsequent RPIs Publication 1756 UM528A EN P April 2004 How Does the Module Store Timestamp Data in CST Per Point Mode The module is installed wired to input devices and ready to begin operation All inputs are configured to timestamp any transition that occurs At this point timestamp data for each input is 0 because no input transitions have occurred Note that only 8 bits of the 64 bit CST timestamp are shown Input 1 transitions from OFF to ON The module timestamps the transition the module sends the data to the owner controller not shown and also stores it locally Input 2 transitions from ON to OFF The module timestamps the transition the module sends the data to the owner controller not shown and also stores it locally Note that the module continues to store the timestamp for the OFF to ON transition on input 1 Publication 1756 UM528A EN P April 2004 Using The Sequence of Events Module in CST Per Point Mode With each timestamped transition the Sequence of Events module stores data for that point An overview of how the module stores timestamp data in CST Per Point mode is shown in Figure 6 1 Figure 6 1 ee onna Input 0 oo L 000000 OFF ON timestamp data L 0000000 ON
131. n acknowledged via the O EventAck tag For more information on clearing timestamp data see page 7 17 UCTTimestamp 2 Per event 64 bit UCT timestamp in Universal Coordinated Time format for the event UCT is expressed as microseconds elapsed since 1 January 1972 Typically UCT format is only used in applications that also use the 1756HP GPS module For more information on the 1756HP GPS module see Appendix B 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 EventPoint Per event Input that recorded the event Values are 0 15 where 0 Input 0 1 Input 1 etc EventData Per event Indicates if input transitioned OFF or ON 0 input transitioned OFF 1 input transitioned ON ReturningUCTTime Modulewide Indicates if timestamps are in UCT format rather than CST Typically UCT format is only used in applications that also use the 1756HP GPS module For more information on the 1756HP GPS module see Appendix B 0 CST format 1 UCT format For more information on UCT format see Appendix B EventsQueuedCount Modulewide Number of events currently stored in the module s buffer that have not been read 1 With the Per point tags there is one bit per input For exa Publication 1756 UM528A EN P April 2004 mple bit 0 represents input 0 bit 7 represents input 7 and so on Using Module Tags D 11 Output Tags Table D 7 describe
132. nd Communications format Format that defines the operational mode used on the Sequence of Events and consequently the type of information transferred between the module and its owner controller This format also defines the tags created for each the module Compatible match An electronic keying protection mode that requires that the physical module and the module configured in the software to match according to vendor and catalog number In this case the minor revision of the module must greater than or equal to that of the configured slot Connection The communication mechanism from the controller to another module in the control system ControlLogix backplane The backplane used by the 1756 chassis Coordinated system time CST Timer value which is kept synchronized for all modules within a single ControlBus chassis CST Per Point Operating mode on the Sequence of Events module in which the module timestamps up to 2 input transitions per input one for OFF to ON transitions and another for ON to OFF transitions Current event Event for which the Sequence of Events module is currently producing data Publication 1756 UM528A EN P April 2004 Glossary 2 Publication 1756 UM528A EN P April 2004 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 p
133. nput Tags in CST Per Point Mode Tag name Set ona Per Point or Description Modulewide basis Fault Per point Indicates if a fault has occurred for the input 0 no fault 1 fault The fault can be chatter or communication fault as described below e Chatter The Sequence of Events module can detect chatter on individual inputs and will set the appropriate tag to 1 when chatter exists on an input For example if the module has detected chatter on input 4 Fau t 4 1 e Communication fault The controller sets this tag to 1 for all 32 bits if a communication fault occurs on the module This tag clears when the fault that causes the condition no longer exists Data Per point Status of the input point This data is filtered if the Input Filter feature is used on the module Thus an input change must pass through the filter before it is seen in this tag 0 input is OFF 1 input is ON For example if input 3 is ON Data 3 1 NewData Per point Flag indicating if new timestamp data was detected on the input 0 no new timestamp data on the input 1 new timestamp data on the input since last acknowledged Because input data for all inputs is sent immediately after each timestamped transition and at each RPI this tag is useful to quickly determine on which input the transition occurred For example if the Sequence of Events module sends new input data to the owner controller and NewData 5 1 yo
134. o synchronize remote Sequence of Events modules you must either e Use version 13 redundancy across the system or e Use version 11 71 for the redundancy controllers and include a ControlLogix controller version 13 in one of the synchronized remote chassis as shown in the example In this case you must use two RSLogix 5000 projects one for the redundancy controllers programmed with RSLogix 5000 version 11 and one for the remote chassis controller programmed with RSLogix 5000 version 13 Publication 1756 UM528A EN P April 2004 Synchronizing CSTs Across Multiple Chassis C 5 Figure C 3 Each chassis contains e 1756 L55 controller version 11 71 y Primary chassis y Secondary chassis e 1757 SRM module Ol M La man e 1756 CNB R module series D afo version 5 23 or greater These chassis are NOT
135. odule in remote chassis other 1756 SYNCH modules chassis and sets it on the timestamps input data Publication 1756 UM528A EN P April 2004 backplane in Chassis 2 with the same CST as used by the controller in Chassis 1 Once the CST is synchronized between chassis as shown in Figure C 1 the modules in chassis 2 use the same CST as the modules in chassis 1 You can use 1756 SYNCH modules to synchronize CSTs for up to 257 ControlLogix chassis Synchronization of CSTs between ControlLogix chassis provides a common CST with no more than 5us drift between chassis Synchronizing CSTs Across Multiple Chassis C 3 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 Figure C 2 shows the example again but also show what the configuration for each 1756 SYNCH module needs to be Figure C 2 Chassis 1 0 o ooo I I in ooo Oi ooo ControlNet Chassis 2 mje ooo ooo foo CST
136. of Events module For more information on how to use the 1756HP GPS module see the 1756HP GPS module user manual available at http www hiprom com Publication 1756 UM528A EN P April 2004 B 2 Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System What is the 1756HP GPS Module Publication 1756 UM528A EN P April 2004 The 1756HP GPS module is an integrated GPS product that makes use of Global Positioning System GPS technology to derive accurate time that is synchronized with the atomic clocks located on the GPS satellites The 1756HP GPS module receives regular transmissions from GPS satellites that deliver time in the Universal Coordinated Time UCT format In addition to receiving UCT time the 1756HP GPS module also has access to time in CST format because the module resides in the ControlLogix chassis and can obtain the CST from the backplane Correlating CST with UCT As shown in Figure B 1 with every receipt of a UCT value from the satellite 1 the 1756HP GPS module captures the CST value from the ControlLogix backplane at that moment 2 calculates the necessary offset to account for drift 3 and then stores the values in its on board table 4 This correlation table provides a real time equivalent for any CST timestamp in the system The table holds one hour s worth of UCT CST times Because drift typically exists between the CST clock and the UCT clock the 1
137. ontroller estes 1 UCTTimestamp 2 copies LEventPoint LEventData relevant LReturningUCTTime d t f LEventsQueuedCount ata trom controller Separate array tags toa separate array lt T current event data pane d1100T0 Current event oo 1100110 oo 0100010 on 1100110 Fault 1010010 pa gt 1100110 Data oo forgot NewData oo 1100107 EventOverlow Ore EventNumber o CSTTimestamp 2 oO UCTTimestamp 2 as TUBER EventPoint 1110011 l EventData oO J ReturningUCTTime EventsQueuedCount copies the current event number EventNumber to the O EventAck tag COP 1 EventNumber O EventAck Once the current event data is cleared from the Sequence of Events module s buffer the module begins producing data for the next event in its buffer at each RPI because that event has become the current event At this point the process returns to Producing Current Event Data on page 7 14 Publication 1756 UM528A EN P April 2004 7 18 Using The Sequence of Events Module in FIFO Mode Publication 1756 UM528A EN P April 2004 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 in
138. ontroller module relays time recommend that when you are using the from its backplane to is configured as the Chassis from its backplane to 1756 SYNCH module with the Sequence of the SynchLink CST Master the SynchLink Events module you use the Required option For more information on how to configure the 1756 SYNCH module see ControlLogix SynchLink Module User Manual publication number 1756 UM521 Publication 1756 UM528A EN P April 2004 C 4 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 When synchronizing time in ControlLogix redundancy systems that also use Sequence of Events modules remember the following e A time master either ControlLogix controller or 1756 SYNCH module must reside in each synchronized chassis e All chassis containing Sequence of Events modules must also contain 1756 SYNCH modules that provide a common CST via SynchLink me At the time of this printing April 2004 ControlLogix Redundancy was only available with ControlLogix controllers version 11 71 T
139. or a time period equal to the filter setting at any point in the time period that is 4x the length of the input filter setting In this case the module does not consider the original transition valid and drops the timestamp See Figure 5 1 on page 5 11 for an example of how the Sequence of Events module s input filters operate Using the Sequence of Events Module Features 5 11 In the example a Sequence of Events module e is Enable CST Capture enabled for all of its points e 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 e Scenario 1 no bounce The input turns ON and remains for the full 2ms In this case the module considers the transition valid and sends the data recorded at the transition to the controller Figure 5 1 Input turns ON timestamp recorded Joine lt lt q _ Input remains ON for at least 2ms transition is considered valid and the timestamp is sent to the controller 43671 3 6 Time in milliseconds 4 5 7 8 e Scenario 2 The input turns ON but turns OFF before 2ms Cength of the input filter setting elapses In this case the Sequence of Events module continues to scan the input every 25us for 4x the length of the input filter setting G e for 8ms At some point in those 8ms the input turns ON again and remains for at least 2ms e the input fi
140. or input data including the use of calculating drift between the clocks If these tags 0 the Sequence of Events module sends timestamps in CST format and ReturningUCTTime 0 Appendix E 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 However you must use the data to perform such tasks as e detect relative first faults e determine absolute first faults e associate real time with CST formatted timestamps Table E 1 describes the sample projects Rockwell Automation offers Table E 1 Project Description GPS_withSOE ACD This project uses multiple user defined data types UDTs and one subroutine The project provides samples on how to manage and buffer information from a 1756HP GPS module Many of these messages are optional and dependent on how you implement your specific system The last rung of this routine provides the interface for communications between the ControlLogix Sequence of Events module and 1756HP GPS module so the Sequence of Events module will return UTC time instead of CST SOE_Module_FifoExtract ACD This project uses multiple user defined data types UDTs and subroutines The project is an example of extracting data from an Sequence of Events module system multiple modules
141. orth of data included in the 4 DINTs is not only the GPS UTC tag but also the GPS CST tag The timestamps are copied to the O UCTTime and O CSTTime tags in the Sequence of Events module s output tags The GPS PPS pulse per second bit is used to send new pairs once a second at the GPS satellite s tone Publication 1756 UM528A EN P April 2004 Integrating The HiProm GPS Module 1756HP GPS into a ControlLogix Sequence of Events Module System B 9 You do NOT need to copy the timestamp pair from the 1750HP GPS module to the Sequence of Events module s output tags if e you convert CST times to UTC manually via messaging to the 1756HP GPS module In this case you must message every timestamp from the Sequence of Events module or e you only need the relative time of events e g breaker one tripped 3ms after breaker 2 Figure B 5 shows the difference between using CST and UCT timestamps Figure B 5 w y Module Sends Timestamp in CST Format Ci 0107700 The module is configured so that input 1 is Enable 72 ag a L CST Capture enabled for OFF to ON transitions Input 0 oo peer D C When input 1 transitions from OFF to ON the Input 1 oO CHICO a module p gt To controller Input 2 oo 0000000 1 Timestamps t
142. ppendix D Fault and Status Reporting Between the Module Ind O a 01016 es peat a ee ee Oe ae ena D 1 Module Tag Names and Definitions D 2 Tags Used in CST Point Per Mode D 2 Tags Used in FIFO Mode 84 te EG OE Ee POF aed D 7 Appendix E OVENI EW w ils ak idee Ane phe Lod aa Aly a ae og Wace Be E 1 Accessing the Sample Projects 1 4 cae e34 ee Sila oe es E 2 What This Chapter Contains What does Sequence of Events Module Do Chapter 1 What is the ControlLogix Sequence of Events Module This chapter describes the ControlLogix Sequence of Events module Table 1 1 For information on See page What does Sequence of Events Module Do 1 1 What Else Does the Sequence of Event Module Do 1 3 Understanding the Module s Physical Features 1 4 Using Module Identification and Status Information 1 5 The ControlLogix Sequence of Events module is a DC input module that offers sub millisecond timestamping on a per point basis in addition to providing the basic ON OFF detection as found on other ControlLogix input modules Timestamping is a ControlLogix feature that registers a time reference to a change in input data In ControlLogix the time mechanism used for timestamping is the Coordinated System Time CST Timestamping Using the Coordinated System Time CST The Coordinated System Time CST is a 64 bit free running timer with microsecond us granularity on a ControlLog
143. put via the EventAck and NewDataAck output tags see page 6 12 This value is cleared if the module is reset Publication 1756 UM528A EN P April 2004 6 10 Table 6 3 Input Tags in CST Per Point Mode Using The Sequence of Events Module in CST Per Point Mode Tag name Set ona Per Point or Description Modulewide basis 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 EventNumber x Modulewide Running count of the timestamped transitions this tag increments by one with each new transition that the module timestamps In CST Per Point mode this tag has lesser importance than in FIFO mode This value is cleared if the module is reset as described on page 6 14 Timestamp 16 0ffOn 2 Per point Timestamp value in CST or UCT format with an input s OFF to ON transition This tag is a 16 x 2 32 bit array There is a 64 bit timestamp per point This value is cleared after the data has been acknowledged via the O EventAck and O NewData tags For more information on clearing timestamp data see page 6 12 Timestamp 16 OnOff 2 Per point Timestamp value in CST or UCT format with an input s ON to OFF transition This tag is a 16 x 2 32 bit array There is a 64 bit timestamp per point This value is cleared after the data has been acknowledged via the O EventAck and O NewData tags For more informa
144. puts The module also stores the data in its on board buffers as described on page 7 2 for up to 160 input transitions IMPORTANT Although the Sequence of Events module can still store the data for up to 160 timestamped transitions in its on board buffer when you use the Retrieval by Point method the module only stores up to 10 timestamps per input You must manage the module buffer effectively to make sure that the module timestamps all transitions on a specific input Consider the following example You are using Retrieve by Point to retrieve timestamp data from input 4 and 10 of the first 34 input transitions that the Sequence of Events module timestamps occur on input 4 If Latch CST is enabled for the module and you fail to clear any of the timestamp data for input 4 before the input transitions again the Sequence of Events module will not timestamp the next transition for input 4 even though there are 126 slots still available in the module s on board buffer 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 e O RetrieveByPoint 1 default value is 0 e O PointtoRetrieve input point for which you want the controll
145. quence of Events module in CST 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 At the user s discretion controller clears current data from the Sequence of Events module by copying the current event number EventNumber to the O EventAck tag preparing the module send data from the next current event This process is described in the rest of this section Retrieving Data in FIFO Mode In FIFO Mode the Sequence of Events module automatically sends the controller the data from the first timestamped transition in its buffer The controller must retrieve the data for the remaining timestamped transitions in the Sequence of Events module s buffers The controller can retrieve data in one of the following ways e Standard Retrieval By default the module uses this retrieval method which returns events in order of occurrence e Retrieval by Point Regardless of retrieval method the controller retrieves data in the format described in Table 7 3 on page 7 11 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 Fault Per point Indicates if a fault has occurred for the input 0 no fault 1 fault The fault can be chatter or
146. r Work in FIFO Mode The Sequence of Events module s on board buffer stores data for up to 160 timestamped transitions at one time For each transition specific information is recorded as shown below and described on page 7 10 The on board buffer has 160 slots to store timestamp information for input transitions As the transitions occur the module timestamps them and fills the 160 slots The first transition fills the first slot the second fills the second slot and so forth Figure 7 1 The module is installed wired to input devices and ready to begin operation At this point the module s on board buffer is empty because no input transitions have occurred Input 5 transitions from OFF to ON The module timestamps the transition and stores the data in this first slot of its on board buffer Input 1 transitions from ON to OFF The module timestamps the transition and stores the data in the next slot of its on board buffer Note that the data from the input 5 OFF to ON transition is still stored in the first slot of the module s on board buffer Publication 1756 UM528A EN P April 2004 _ Lai i a AA imestamp Event KAF Input oO C O nput State T 7 imestamp Event o iy Input Ce o9 0
147. r is removed or the area is nonhazardous before proceeding Figure 3 7 Isolated wiring Sink input wiring l DC 0 GND 0 2 1 INO o O oO _ 0C 0 DE 1 GND 1 a 43 g N 1 O O DC 1 GND 2 a 65 A N 2 7 GND 3 g 8 7 fe N 3 B Source input wiring GND 4 aD wa g N 4 Source input wiring q DC 5 O O O GND5 Qr o N5 c DC 5 DC 6 OO O GND4 D 413 G N6 DC 6 L GND 7 a 16 15 fa N 7 GND 8 G 317 EN N 8 Non isolated wiring GND 9 20 19 S N 9 Sink input wiring _ GND 10 Q 22 E N10 O O GND 11 g 24 23 ID N 11 O Oe Jumper bar a Z 3 O e Cut to length GND 12 q Te D N 12 O GND 13 g 28 27 o N 13 O O e GND 14 g 30 29 E N 14 O i O e GND 15 Q 2 a1 EN N15 O O DC O GND 15 g 34 33 a Not used ODC Not used D 36 35 a Not used 40167 M Daisy chain to other RTBs NOTES 1 All terminals with the same name are connected together on the module For example DC can be connected to either terminal marked GND 15 2 When you use the second GND 15 terminal to daisy chain to other RTBs always connect
148. s 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 To clear the current event data you must COP the current event number I EventNumber to this tag O NewDataAck x DINT Allows NewData bits in the Input word to function as intended NewData bits are set when a transition occurs and clear only after they are acknowledged via the NewDataAck bit Typically the following events occur e An event occurs on an input e The Sequence of Events module sets the NewData bit for the input where the event occurred e The controller records the new data e The controller acknowledges the new data by causing a 0 to 1 transition on the corresponding NewDataAck bit e The NewData bit clears e When another event occurs on the input the sequence begins at the top bullet in this list The controller must cause a 0 to 1 transition in this bit to acknowledge new data for an input in other words if the NewDataAck bit is 0 when new data is received the controller must change this bit to 1 to acknowledge the data If NewDataAck bit is 1 when new data is received the controller must change this bit to 0 and then to 1 to acknowledge the new data O PointToRetrieve NT Determines for which point the module returns events You can use this bit to quer
149. seen in this tag 0 input is OFF 1 input is ON For example if input 3 is ON Data 3 1 NewData Per point Flag indicating if new timestamp data was detected on the input 0 no new timestamp data on the input 1 new timestamp data on the input since last acknowledged Because input data for all inputs is sent immediately after each timestamped transition and at each RPI this tag is useful to quickly determine on which input the transition occurred For example if the Sequence of Events module sends new input data to the owner controller and NewData 5 1 you know that at least one of the timestamps for input 5 i e Timestamp 5 OffOn or I Timestamp 5 OnOff has new data This tag only clears when the controller acknowledges the new data or all events on the module are reset For more information see page 6 12 EventOverflow Per point Set for an input when the module either e Does not timestamp a transition on the input The module has Latch CST enabled and a similar transition has already been timestamped on this input but has not been cleared via the EventAck and NewDataAck output tags see page 6 12 or e Overwrites previously recorded timestamp data for the input The module has Latch CST disabled and multiple transitions occur on the input In this case timestamp data from new transitions are recorded before previously recorded transitions were cleared from the in
150. 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 received as described on page 6 12 and page 7 20 e If Latch CST is disabled the module timestamps every input transition and may overwrite previously recorded timestamp data if the controller does not acknowledge the data quickly enough This feature is set on a module wide basis and is enabled by default mM The bullets above provide a general description of how Latch CST works However there are slight differences between how the features affects module behavior in each operational mode e For more information on how Latch CST is used in CST Per Point mode see page 6 7 e For more information on how Latch CST is used in FIFO mode see page 7 9 Use the Configuration tab in RSLogix 5000 to enable Latch CST as shown in the example below E Module Properties Local 1 1756 IH16ISOE 1 1 General Connection Module Info p Backplane r Input Filter Time Reset All CST Off gt On On Off T On Off H od gt Module Configuration Bits pel Latch CST M O M O M O M m a M m M O M O M O ty J Status Offline Cancel Apply Help Publication 1756 UM528A EN P April 2004 5 8 Using the Sequence of Events Module Features Publication 175
151. splay each fault and include a fault message describing the nature of the fault This feature allows you to determine how the fault affects your module and what action you should take to resume normal operation For more information on how to use hardware and software indicators when a module fault occurs see Chapter 8 Troubleshooting the Sequence of Events Module 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 serial number revision information product code vendor identification error fault information e 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 Sequence of Events modules can produce data without having been polled by a controller first The module produces the data and the owner controller device consumes it Publication 1756 UM528A EN P April 2004 5 18 Using the Sequence of Events Module Features Publication 1756 UM528A EN P April 2004 Status Indicator Information Each Sequence of Events module has LED status indicators on the
152. ssis power is applied ATTENTION The module is designed to support Removal and Insertion Under Power RIUP However when you remove or insert an RTB with field side power applied unintended machine motion or loss of process control can occur Exercise extreme caution when using this feature Publication 1756 UM528A EN P April 2004 3 2 Installing the Sequence of Events Module 1 Align circuit board with top and bottom chassis guides Printed Circuit Board 20861 M 2 Slide module into chassis until module tabs click Figure 3 2 20862 M Publication 1756 UM528A EN P April 2004 Installing the Sequence of Events Module 3 3 Keying the Removable Key the RTB to prevent inadvertently connecting the incorrect RTB Terminal Block to your module When the RTB mounts onto the module keying 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 We recommend that you use a unique keying pattern for each slot in the chassis 1 Insert the U shaped band with the longer side near the terminals Push the band onto the module until it snaps in place Figure 3 3 U shaped Keying Band p 20850 M 2 Key the RTB in positions that correspond to unkeyed module positions Insert the wedge shaped tab on the RTB with the rounded edge first Push the tab
153. t On On Off l On gt Off H od r Module Configuration Bits pel Latch CST Click on this box to enable the Latch CST feature kakalaka FAM ojojojojojojojo Clear the box to disable the feature Status Offline Cancel Apply Help Publication 1756 UM528A EN P April 2004 Click the Configuration tab e Click on the individual boxes for each input point to enable CST Capture for that point e Clear the individual boxes for each input point to disable CST Capture for that point Using The Sequence of Events Module in FIFO Mode 7 9 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 e The module is capable of timestamping an unlimited number of transitions However at any one time the Sequence of Events module can store the data for up to 160 events in its on board buffer You must manage the buffer effectively e retrieve data to make sure no events are missed or overwritten e The controller must retrieve data associated with each input transition from the Sequence of Events module s on board buffers See Retrieving Data in FIFO Mode on page 7 10 to learn how to manage the module s on board storage buffer e When the first transition is timestamped
154. ter 6 Using The Sequence of Events Module in CST Per Point Mode and Chapter 7 Using The Sequence of Events Module in FIFO Mode The Sequence of Events module offers additional features that are common to ControlLogix digital input modules such as e Full software configuration via RSLogix 5000 e Removal and insertion under power e Full Class I Division Compliance e Agency Certifications e g UL and CSA To see a full description of all the features available on your Sequence of Events module see Chapter 5 Using the Sequence of Events Module Features Publication 1756 UM528A EN P April 2004 1 4 What is the ControlLogix Sequence of Events Module Understanding the Module s Physical Features ControlLogix modules mount in a ControlLogix chassis and use a Removable Terminal Block RTB or a Bulletin 1492 Interface Module cable that connects to an IFM to connect all field side wiring Before you use your module you should have already e installed and grounded a 1756 chassis and power supply To install these products refer to the publications listed in Table Preface 3 on page Preface 2 e ordered and received an RTB or IFM and its components for your application neither RTBs nor IFMs are included with your module purchase ia ences ControlLogix backplane
155. the Sequence of Events module for events in which you have no interest 1 CST Capture enabled default for ON to OFF input transitions For more information on Enable CST Capture see page 5 5 C ChatterEvents 16 SINT 16 Number of events required in ChatterTime 16 period to determine a chatter condition 0 Disable Chatter Detection 1 Illegal value The number of events must be greater than 1 The maximum value is 127 For more information on Chatter Detection see page 5 8 C ChatterTime 16 INT 16 Time period in milliseconds in which the number of events in the ChatterEvents tag must occur to declare a chatter condition For example if ChatterEvent 10 and ChatterTime 20 and 11 events occur on the point in a 20ms time period chatter is declared on the point When chatter is declared the input faults and no longer timestamps transitions that occur on the point When chatter ceases the input returns to normal operation The Sequence of Events module considers chatter to have ceased when the configured chatter time elapses with no transitions occurring on the input For more information on Chatter Detection see page 5 8 Publication 1756 UM528A EN P April 2004 Using Module Tags D 9 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 Descr
156. the daisy chain to the terminal directly connected to the supply wire as shown in the example above 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 Installing the Sequence of Events Module 3 7 Assembling The Removable Removable housing covers the wired RTB to protect wiring Terminal Block and the Housing connections when the RTB is seated on the module 1 Align the grooves at the bottom of each side of the housing with the side edges of the RTB Figure 3 8 Housing Groove Side edge of RTB RTB 20858 M 1756 TBCH RTB shown for reference 2 Slide the RTB into the housing until it snaps into place e additional wire routing space is required for your application use extended depth housing 1750 TBE Publication 1756 UM528A EN P April 2004 3 8 Installing the Sequence of Events Module Choosing the Extended Depth Housing Maximum Area 336mm There are two housing options you must consider when wiring your Sequence of Events module standard depth or extended depth 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 e
157. the following screens On this screen you can A Change the RPI For more information on the RPI see page 2 6 Module Properties Local 1 1756 IH16ISOE 1 1 Requested Packet Interval RPI B Inhibit the module For more eT Inhibit Module information on inhibiting the module Major Fault On Controller If Connection Fails While in Run Mode see page 5 19 Module Fault Sms 0 2 750 0 ms 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 Next until you see the screen below Cancel Finish gt gt TE On this screen you can A Enable CST Capture for each input point For more information on CST Capture see page 5 5 Module Properties Local 1 1756 IH16ISOE 1 1 Input Filter Time Off gt On On gt Off 4 pe j Module Configuration Bits F Latch CST Reset All CST B Configure Chatter Detection for each input point For more information on Chatter Detection see page 5 8 M x C Set the Input Filter Times For more information on Input Filters see page 5 10 WII lt qj xI Cancel lt Back Next gt D Click on the box to enable CST Latching For more information on CST Latching see page 5 7 E Click Finish Publication 1756 UM528A
158. til acknowledged 0 CST not latched default 1 CST latched For more information on Latch CST see page 5 7 C FilterOffOn SINT Sets the OFF to ON filter time for all 16 inputs Times are set in 1ms increments from Oms to 50ms 0 no filtering For more information on Software Configurable Input Filters see page 5 10 C FilterOnOff SINT Sets the ON to OFF filter time for all 16 inputs Times are set in 1ms increments from Oms to 50ms 0 no filtering For more information on Software Configurable Input Filters see page 5 10 C CaptureOffOn x DINT Enables capturing OFF to ON events on a per point basis If disabled i e set to 0 that Publication 1756 UM528A EN P April 2004 point will not record timestamp data for OFF to ON input transitions 0 CST Capture disabled for OFF to ON 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 1 CST Capture enabled default for OFF to ON input transitions For more information on Enable CST Capture see page 5 5 Using Module Tags D 3 Table D 2 Configuration Tags in CST Per Point Mode Tag name C CaptureOnOff Type DINT Description 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
159. tion on clearing timestamp data see page 6 12 1 This tag is a 32 bit tag The lower 16 bits represent the 16 inputs on the Sequence of Events module Copying Relevant Input Data to a Separate Data Structure When the Sequence of Events module sends input data to the controller the data is stored in the controller tags We recommend you use a COP or CPS instruction to programmatically copy new timestamp data from the controller tags to a separate array in the controllers memory Later you can combine timestamp data from multiple Sequence of Events modules and use a Sort routine to determine the order of events with relative time reference that occurred in a specific time period IMPORTANT When you copy relevant timestamp data from the controller tags to a separate data structure make sure you copy enough information for each timestamp that you can differentiate between timestamps for different inputs Publication 1756 UM528A EN P April 2004 Sequence of Events module 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 a D gt ControlLogix controller Figure 6 3
160. troller using RSLogix 5000 and download that information to the controller 2 If the module configuration data references a module in a remote chassis connected by scheduled ControlNet run RSNetWorx 3 After running RSNetWorx perform an online save of the RSLogix 5000 project so the configuration information that RSNetWorx sends to the controller is saved IMPORTANT You must run RSNetWorx whenever a new module is added to a scheduled ControlNet chassis When a module is permanently removed from a remote chassis we recommend that RSNetWorx be run to optimize the allocation of network bandwidth Publication 1756 UM528A EN P April 2004 How Does the Sequence of Events Module Operate in a ControlLogix System 2 3 Table 2 3 Ways that a Sequence of Events Module Behave Like Other ControlLogix Digital Input Modules Concept Making Connections Description ControlLogix controllers can make direct or rack connections to digital 1 0 modules The controller can only make a direct connection to the Sequence of Events module The controller cannot make rack connections to the Sequence of Events module Additionally the controller cannot make listen only connections to the Sequence of Events module A direct connection is a real time data transfer link between the controller and the device that occupies the slot that the configuration data references When module configuration data is downloaded to an owner controller the controller a
161. ts module In this example to clear data from the Sequence of Events module the controller writes the following to the Sequence of Events output word e O EventAck 2 1 e O NewDataAck 2 1 Figure 6 5 Sequence of Events module YN 1 Input 2 transitions l 2 Module timestamps 3 Module sends l Controller tags from OFF to ON the transition E input data to pe O E oo pm E the controller 4 Controller nt E i TRetamingUC Tim Po OTTO gg copies ieee y L o000000 Fault relevant Eest ee onon 2 0000000 oo Ltoooo000 Data data irom Separate array 7 NewData controller 7 EventOverlow tags toa ReturningUCTTime separate 0000000 EventNumber array Doon Timestamp 16 OffOn 2 2 pi Timestamp 16 0nOff 2 22 a wD ControlLogix controller FF 5 Controller clears data from input 2 on the Sequence of Events module O EventAck 2 1 O NewDataAck 2 1 If Latch CST is disabled the controller does not need to clear timestamp data In this case Sequence of Events module sends new data from subsequent transitions to the controller as soon as they occur The controller overwrites timestamp data from the last transition regardless of whether it saved the data or not 42793 Publication 1756
162. ttempts to establish a direct connection to each of the modules referenced by the data If a controller has configuration data referencing a slot in the control system the controller periodically checks for the presence of a device there When a device s presence is detected there the controller automatically sends the configuration data If the data is appropriate to the module found in the slot a connection is made and operation begins If the configuration data is not appropriate the data is rejected and an error message appears in the software In this case the configuration data can be inappropriate for any of a number of reasons For example a module s configuration data may be appropriate except for a mismatch in electronic keying The controller maintains and monitors its connection with a module Any break in the connection such as module faults or removal of the module from the chassis while under power causes the controller to set fault status bits in the data area associated with the module RSLogix 5000 monitors connection status to annunciate the modules failures Transmitting Data In the ControlLogix system a controller does not poll the Sequence of Events module to obtain input status When you configure a Sequence of Events module to capture a CST value for a specific transition the module produces data whenever that input transitions and also at a user configured rate The type of input data transmitted and transmiss
163. u know that at least one of the timestamps for input 5 i e Timestamp 5 OffOn or Timestamp 5 OnOff has new data This tag only clears when the controller acknowledges the new data or all events on the module are reset For more information see page 6 12 EventOverflow Per point Set for an input when the module either e Does not timestamp a transition on the input The module has Latch CST enabled and a similar transition has already been timestamped on this input but has not been cleared via the EventAck and NewDataAck output tags see page 6 12 or Overwrites previously recorded timestamp data for the input The module has Latch CST disabled and multiple transitions occur on the input In this case timestamp data from new transitions are recorded before previously recorded transitions were cleared from the input via the EventAck and NewDataAck output tags see page 6 12 This value is cleared if the module is reset Publication 1756 UM528A EN P April 2004 Table D 3 Input Tags in CST Per Point Mode Using Module Tags D 5 Tag name Set ona Per Point or Description Modulewide basis 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 EventNumber x Modulewide Running count of the timestamped transitions this tag increments by one with each new transition that the modu
164. use in applications where multiple transitions occur on multiple inputs in relatively rapid succession i e faster than the controller can acknowledge the data as the transitions occur Because of this intention the Sequence of Events module uses an on board buffer to store the data for up to 160 events The following are example typical applications for FIFO mode e Sequence monitoring e Process and machine optimization You configure the same general set of configurable features described in Chapter 5 whether you are using the Sequence of Events module in CST Per Point mode or FIFO mode However for some features the module behavior as dictated by the feature varies according to operational mode For example Latch CST impacts the Sequence of Events module behavior slightly differently in CST Per Point mode than in FIFO mode You should be aware of the impact the following configurable features have on module behavior in FIFO mode e Communications Format e Latch CST e Enable CST Capture Using The Sequence of Events Module in FIFO Mode 7 5 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 To operate the Sequence of Events module in FIFO mode you must choose the FIFO
165. v13 or greater e A 1756 SYNCH module is located in each chassis local and remote Publication 1756 UM528A EN P April 2004 C 2 Synchronizing CSTs Across Multiple Chassis e 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 e 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 e The 1756 SYNCH module in remote chassis receive the CSTs from the 1756 SYNCH module in the local chassis and use that time to set the CST on the backplane of the chassis where they reside e All the other modules in the remote chassis operate with a CST from the backplane that is synchronized with the CST in the controller s chassis Figure C 1 Chassis 1 Chassis 2 CST on backplane golon synchronized with Chassis fes B Age se ee I O O O O O O 7 Ea ControlNet KR CST propagated via Controller Sets CST 1756 SYNCH Gets CST from 1756 SYNCH Gets CST Sequence of events for local chassis backplane and sends it to the from 1756 SYNCH in local m
166. vailable network slot Mitta Enabling the Enable CST Capture feature on an input module in a remote chassis allows the module to multicast data at both the RPI rate and when the input changes state This helps to reduce the Worst Case time Table 2 4 summarizes the Best Case and Worst Case scenarios from the time an input changes state to the time the owner controller will receive the data Table 2 4 Best and Worst Case Scenarios For Remote Input Data Transfer Best case scenario Worst case scenario Enable CST Capture Backplane Network Twice the RPI disabled transfer times lt 1mS Enable CST Capture Backplane Network RPI enabled transfer times lt 1mS Publication 1756 UM528A EN P April 2004 2 10 How Does the Sequence of Events Module Operate in a ControlLogix System Chapter Summary and What s Next Publication 1756 UM528A EN P April 2004 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 NUT 5mS x20 x2t x22 x xa lx x28 hz Optimal 5ms 10mS 20mS 40mS 80mS 160mS 320mS 640mS RPI Values mS Remote Input Modules Connected Via EtherNet IP When the Sequence of Events module is connected to the
167. ws minor revision level 9 i e 1 9 Publication 1756 UM528A EN P April 2004 Click on this box to inhibit or uninhibit the module 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 e You write configuration for a Sequence of Events module but inhibit the module to prevent it from communicating with the owner controller In this case the owner controller does not establish a connection and configuration is not sent to the module until the connection is uninhibited The following examples are instances where you may need to use module inhibiting e You want to FLASH upgrade your module We recommend you a Inhibit the module b Perform the upgrade c Uninhibit the module e 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 in the proper slot You can inhibit your Sequence of Events module on the Connection tab in RSLogix 5000 as shown in the example below E Module Properties Local 1 1756 IH16ISOE 1 1 General Connection Module Into Configuration Backplane Requested Packet Interval RPI 10 024
168. xtended depth housing This housing does not come with an RTB You can use one of the housings listed in Table 3 2 Table 3 2 Use this with this RTB This combination allows up housing to this capacity of wires 1756 TBCH Cage clamp 336 sq mm 1756 TBS6H Spring clamp 36 position 1756 TBE Any RTB that uses heavy 628 sq mm gauge wiring Figure 3 9 shows the difference in terms of capacity between the housing options IMPORTANT The housings shown are used with a spring clamp RTB but the capacity for each remains the same regardless of RTB type Figure 3 9 Standard Depth Housing Extended Depth Housing Maximum Area 628mm 36 18AWG wires 23 14AWG wires Publication 1756 UM528A EN P April 2004 40 14AWG wires a4 30484 M Installing the Sequence of Events Module 3 9 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 e using gt 36 18AWG wires e using gt 23 14AWG wires Cabinet Size Considerations With the Extended Depth Housing When you use an extended depth housing 1756 TBE the module depth is increased The diagram below shows the difference in terms of depth between a Sequence of Events module using a standard depth housing and one using an extended depth housing
169. y events by point instead of just sequence O ResetEvents BOOL Erases all recorded events when transitioned from 0 to 1 O RetrieveByPoint BOOL Sets the retrieval mechanism for retrieving events 0 Retrieve events sequentially 1 Retrieve events on a per point basis In this case the module uses the PointtoRetrieve value to determine which input s events are retrieved Publication 1756 UM528A EN P April 2004 D 12 Using Module Tags Table D 7 Output Tags in FIFO Mode Tag name Type O UCTTime 2 DINT 2 O CSTTime 2 DINT 2 Publication 1756 UM528A EN P April 2004 Description 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 the 1756HP GPS module one in UCT format and the other a corresponding CST format value to these tags When these tags are nonzero numbers the Sequence of Events module converts timestamps from CST format to UCT format before sending them to the controller Additionally ReturningUCTTime 1 Typically the following events occur e A 1756HP GPS module produces CST UCT Time pairs that are sent to the controller e The controller copies the pairs to the Sequence of Events module every pulse per second PPS We recommend you copy the pairs every PPS e The Sequence of Events module uses the streams of pairs to calculate UCT timestamps f
170. y occur For more information on using Event tasks see the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Publication 1756 UM528A EN P April 2004 2 4 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 Field Device to Backplane Publication 1756 UM528A EN P April 2004 signal at the RTB and processes it internally before sending a signal to the ControlLogix backplane via the Requested Packet Interval RPD or at na Enable CST Capture occurrence However when you operate the Sequence of Events module you must account for signal propagation delays that exist during internal processing Some of these delays are inherent to the module and others can be controlled via the user defined module configuration During processing the following delays exist e hardware delay varies according to module type i e catalog number and input transition type G e OFF to ON ON to OFF mM The hardware delay is relatively consistent across inputs on a module and across modules in a chassis Therefore assuming the inputs and modules are used in similar environmental conditions and with similar voltages applied the hardware delay is a minor consideration affecting timestamping accuracy e input filter delay user configurable number from 0 to 50ms e firmware scan time up to 25us depen

1756-UM528A-EN-P, ControlLogix Sequence of Events Module

Contents

Download Pdf Manuals

Related Search

Related Contents