Appendix C

Appendix C Sequence of Events Recorder 1 Internal



Appendix Contents of This Appendix 3 Functionality Overview ....................................................................9 Installing Triconex SOE Recorder ...................................................10 Installing SOE Recorder ................................................................10 Uninstalling SOE Recorder ............................................................10 SOE Setup in TriStation 1131........................................................11 Assigning Event Variables to SOE Blocks......................................12 Specifying a Trip Variable ..............................................................12 Using the SOE Function Blocks .................................................. 13 Programming Notes ..........................................................................13 SOESTRT (SOE Start) ..................................................................13 SOESTOP (SOE Stop) ..................................................................14 SOECLR (SOE Clear)....................................................................15 SOESTAT (SOE Statistics)............................................................16 Lab 1 : Setting SOE in TriStation 1131 ........................................ 17 Introduction .......................................................................................17 Objectives ..........................................................................................17 Lab Procedure ...................................................................................17 Install SOE Recorder .....................................................................17 Uninstall SOE Recorder.................................................................17 Configure SOE...............................................................................18 Define SOE Block Properties.........................................................18 Assign Event Variables to SOE Blocks ..........................................19 Specify a Trip Variable ...................................................................20 SOE Recorder Setup ..................................................................... 21 Copying the SOE Definition File ......................................................21 Specifying Display Options..............................................................21 Specifying Periodic Snapshots........................................................22 Specifying Shift Snapshots..............................................................22 Specifying Auto Snapshot Options .................................................22 Specifying an Event File Folder .......................................................22 Specifying Controllers for Retrieval ................................................22 Specifying Automatic Export of Event Data ...................................23 Lab 2 : Setting SOE Recorder ...................................................... 24 Introduction .......................................................................................24 Objectives ..........................................................................................24 Lab Procedure ...................................................................................24 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Copy the SOE Definition File .........................................................24 Specify Display Options .................................................................24 Specify Periodic Snapshots ...........................................................26 Specify Shift Snapshots .................................................................26 Specify Auto Snapshot Options .....................................................26 Specify an Event File Folder ..........................................................27 Specify Controllers for Retrieval ....................................................28 Specify Automatic Export of Event Data ........................................28 SOE Recorder Event Retrieval ..................................................... 29 Setting Up Event Retrieval ...............................................................29 Starting Events Retrieval..................................................................29 Ending Event Retrieval .....................................................................29 Lab 3 : Retrieving SOE Recorder Event ...................................... 30 Introduction .......................................................................................30 Objectives ..........................................................................................30 Lab Procedure ...................................................................................30 Set Up Event Retrieval...................................................................30 Start Event Retrieval ......................................................................31 End Event Retrieval .......................................................................31 4 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Functionality Overview The Triconex Sequence of Events (SOE) Recorder software, Figure 1, allows you to retrieve event data from as many as 63 Triconex controllers on a network (up to 16 controllers simultaneously). This event data can be used to identify the causes of shutdowns, define corrective actions and procedures for preventive maintenance, and solve other process-control problems. Understanding the sequence of events that leads to unsafe process conditions and possible shutdowns may be essential to the safety application. For Triconex controllers, an event is the state change (transition) of a Boolean variable from True to False or from False to True. A Triconex controller can collect events and record the date, time, state, and variable name of each event in SOE blocks that reside in the controller’s memory. This figure shows how Triconex controllers, a TriStation 1131 application, and SOE Recorder interact to provide sequence-of-events functionality. Figure 1 – Triconex Sequence of Events (SOE) Recorder To enable event data to be detected by the controller, you must define the event variables and SOE blocks in the TriStation application. In addition, the application must include SOE function blocks that start event collection. After you download an SOE-enabled project to the controller, TriStation creates an SOE definition file that contains the SOE block definitions. To retrieve events with SOE Recorder, you must connect the SOE workstation to a communication port on a Triconex controller. (You can also retrieve events from a Triconex controller with an SOE program on a non-Triconex external device.) You must use TriStation to set the IP address of the controller and you must specify the address in SOE Recorder. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix SOE Recorder can simultaneously retrieve event data from as many as 32 networked controllers, assuming that IP addressing has been done correctly. SOE Recorder queries all the controllers on the network to determine which TriStation applications include SOE blocks. If a project includes one or more SOE blocks, SOE Recorder opens the appropriate SOE definition file and begins retrieving events from the associated controller. SOE Recorder accumulates events in an event file until a trip occurs or the maximum allowable number of events occurs. SOE Recorder can also save snapshots for periods that you specify, such as snapshots that reflect each shift of a plant’s operation. During event retrieval, you can manually save an intermediate snapshot of event data at any time. SOE Recorder also allows you to export event data, either manually or automatically, to dBASEIV or ASCII text files. A report engine and standard report are also included. While the TriStation application is running, SOE Recorder allows you to analyze events online as it retrieves them from the controllers. To analyze the event data, SOE Recorder includes tools for: • Finding events and copying them to other Windows applications. • Filtering and sorting saved event data. • Specifying the display of point properties for event data. • Viewing the properties of individual events. You can also save snapshots of events that cover specific periods of time before or after trips have occurred. In addition, a report engine and a standard report are included so you can generate reports and export event data, either manually or automatically, to dBASEIV or ASCII text files. Installing Triconex SOE Recorder To install SOE Recorder, you must be logged into Windows as a user with administrator privileges. If you do not have administrator privileges, contact your network administrator for assistance. Installing SOE Recorder If the .NET Framework is not already installed, setup will install it for you before installing SOE Recorder. Depending on your workstation's configuration, .NET Framework installation can take several minutes, and may require you to restart your workstation in order to complete the installation process. During installation, you will be asked if you want to change the NERC Security Banner message text. This is optional; the message text can also be modified at any time after installation. If you aren’t sure if you want to change the text, leave the default text as-is during installation. Uninstalling SOE Recorder If you have installed a previous version of SOE Recorder, you must uninstall it before installing a new version. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 10 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix SOE Setup in TriStation 1131 This section explains how to set up sequence of events collection in a TriStation 1131 application. Events can be retrieved from a Triconex controller by using the SOE Recorder software. For more information, Refer to the SOE Recorder User’s Guide. The topics included are: • SOE Configuration • Defining SOE Block Properties • Assigning Event Variables to SOE Blocks • Specifying a Trip Variable SOE Configuration The SOE Configuration window displays the SOE blocks that have been configured. Defining SOE Block Properties Defining SOE block properties is related to the general task of controller configuration and can be completed at the same time. You can define SOE blocks to provide continuous event information to external devices on a network, or you can define them for limited operation when your controller is not on a network. Table 1 lists properties of the SOE Block Definition tab: Table 1 – SOE Block Definition Property Description SOE Block Type History: Used to monitor current events. First Out: Used to retrieve events that started a trip. External: Used when an external device, such as a DCS or a workstation running SOE Recorder, is continually retrieving events. Modified External: Used for event retrieval with the SMM. Blocks 1 through 14 can use any combination of History, First Out, and External block types. Blocks 15 and 16 can use only the Modified External block type. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 11 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Property Description SOE Block Name The SOE Block Name field is used to enter a title for the block. If you SOE Buffer Size do not enter a block name, a default name will be assigned automatically. SOE Block Collection Type The buffer stores the event entries, each containing an 8-byte time stamp and one or more 8-byte data entries. SOE Block Collection Mode Enter the number of events to be stored in this block. The maximum number is 20,000 events (320,000 bytes); the default is 0. The maximum buffer size across all blocks is 60,000 events (1 MB). Select the event collection behavior type for the block. • Select Automatic if you want the block’s events to be automatically collected by an instance of SOE Recorder running in Primary, Redundant, or Custom mode. • Select Manual if you want the block’s events to be collected by an external DCS or an instance of SOE Recorder running in Custom mode. Select the collection mode for the block. • Select Primary if you want the block’s events to be collected by an instance of SOE Recorder running in Primary mode or an instance of SOE Recorder running in Custom mode when the blocks are selected for collection. • Select Redundant if you want the block to be a copy of an existing Primary block, and then select the Primary block you want this block to be a copy of. Assigning Event Variables to SOE Blocks Tagnames (event variables) to an SOE block are required if you are using sequence of events in an application. Tagnames must be aliased memory and/or input tagnames of type BOOL: • Discrete physical input points. • Discrete memory read-only aliased variables. • Discrete memory read/write aliased variables. Discrete output points cannot be assigned to an SOE block. Tagname states can be displayed with names and colors that you define. You can designate one tagname in a TriStation 1131 application as the trip variable that notifies the operator when a trip occurs. Specifying a Trip Variable In an application used for safety shutdown, a trip variable is an aliased tagname whose state transition causes SOE Recorder to automatically create a trip snapshot. An application can have one trip variable, but it can apply to all blocks. If an application 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 12 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix requires several variables related to trip conditions, these variables must be evaluated in combination to determine the final state of the trip variable. Using the SOE Function Blocks This section describes the function blocks that are used in an application to control and verify event collection for SOE blocks. The start function block (SOESTRT) must be used to identify the SOE blocks to be used for event collection. The other SOE function blocks are optional. • SOESTRT (SOE Start) : Starts event collection for a specified SOE block (required) • SOESTOP (SOE Stop) : Stops event collection for a specified SOE block (optional) • SOECLR (SOE Clear) :Checks status of a specified SOE block (optional) • SOESTAT (SOE Statistics) : Clears a specified SOE block (optional) Programming Notes To properly execute the SOESTRT, SOESTOP and SOECLR function blocks, a program should turn the CI input On for only one scan. If you leave CI on for more than one scan, SOE Recorder generates another event for every scan. For more information, refer to the sample projects on the TriStation CD. If you are programming with the Structured Text (ST) language, you must use conditional statements to execute SOESTRT, SOESTOP, and SOECLR. For more information, refer to the TriStation 1131 Libraries Reference. SOESTRT (SOE Start) The SOESTRT function block starts event collection for the designated block. The MPs write an SOESTRT time-stamp entry to the buffer and change the state of the designated block from not started or stopped to collecting. The MPs use these initial values as the basis for comparison during subsequent scans. If the SOESTRT operation is successful, the returned status is 1, which indicates the block is collecting data. This function block must be executed for each SOE block from which you want to collect events. Note: The SOESTRT function block is executed for only one scan, which means the resulting STAT output is only valid for that scan. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 13 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Input Parameters Name Data Type Description CI BOOL Enables SOESTRT. BLOCK DINT The block number (1–16). Output Parameters Name Data Type Description CO BOOL True if SOESTRT executes successfully. STAT DINT Status: • 0 = The block is not started or not configured with data type and size. • 1 = The block is collecting data. • 2 = The block is stopped or cleared. • 3 = The block is full. SOESTOP (SOE Stop) The SOESTOP function block stops event collection for the designated block, writes an SOESTOP time stamp into the buffer, and changes the state of the block from collecting to stopped. No further events are collected until the next SOESTRT function block is executed. If the SOESTOP operation is successful, the returned status is 2, indicating that event collection is stopped. This function block is not required, but is recommended following each start function block. Note: The SOESTOP function block is executed for only one scan, which means the resulting STAT output is only valid for that scan. Input Parameters Name Data Type Description CI BOOL Enables SOESTOP. BLOCK DINT The block number (1–16). 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 14 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Output Parameters Name Data Type Description CO BOOL True if SOESTOP executes successfully. STAT DINT Status: • 0 = The block is not started or not configured with data type and size. • 1 = The block is collecting data. • 2 = The block is stopped or cleared. • 3 = The block is full. SOECLR (SOE Clear) The SOECLR function block clears the buffer of the designated SOE block, removes all entries from the block, and writes an SOECLR time stamp into the buffer. You must stop event collection using the stop function block before clearing the block. If the SOECLR operation is successful, the status is 2, indicating the block has been cleared. If event collection was not stopped before the SOECLR operation was attempted, the status is 0, 1 or 3. This function block is optional. Note: The SOECLR function block is executed for only one scan, which means the resulting STAT output is only valid for that scan. Input Parameters Name Data Type Description CI BOOL Enables SOECLR. BLOCK DINT The block number (1–16). Output Parameters Name Data Type Description CO BOOL True if SOECLR executes successfully. STAT DINT Status: • 0 = The block is not started or not configured with data type and size. • 1 = The block is collecting data. • 2 = The block is stopped or cleared. • 3 = The block is full. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 15 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix SOESTAT (SOE Statistics) The SOESTAT function block returns the status of the designated SOE block, the number of eight- byte entries that are used, and the number of eight-byte entries that are free. This function block is optional. Input Parameters Name Data Type Description CI BOOL Enables SOESTAT BLOCK DINT The block number (1–16). Output Parameters Name Data Type Description CO BOOL True if SOESTAT executes successfully. STAT DINT Status: FREE DINT • 0 = The block is not started or not configured with USED DINT data type and size. • 1 = The block is collecting data. • 2 = The block is stopped or cleared. • 3 = The block is full. The number of unused 8-byte entries in the block. The number of unused 8-byte entries in the block. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 16 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Lab 1 : Setting SOE in TriStation 1131 Introduction In this lab, you will set up sequence of events collection in a TriStation 1131 application. Events can be retrieved from a Triconex controller by using the SOE Recorder software. Objectives After completing this lab, you will be able to: • Install SOE Recorder. • Uninstall SOE Recorder. • Configure SOE. • Define SOE block properties. • Assign event variables to SOE blocks. • Specify a Trip variable. Lab Procedure Install SOE Recorder 1. Log on to Windows as an administrator or as a user with administrator privileges. 2. Close all open applications. 3. Insert the SOE Recorder CD in the CD-ROM drive. 4. If the installation starts automatically, go to step 8. Otherwise, go to the next step. 5. On the Start menu, click Settings | Control Panel. 6. Double-click Add or Remove Programs, and then click Add New Programs. 7. Click CD or Floppy, and then browse to locate the setup.exe file on the CD. 8. Double-click setup.exe to start the installation. 9. Follow the InstallShield Wizard instructions. Schneider Electric recommends installing the SOE Recorder software in the default destination folder, which is: C:\\Program Files\\Triconex\\TcxSoe. Note: For Windows 7 64-bit or Windows 2008 Server R2 64-bit, the default folder is: C:\\Program files(x86)\\Triconex\\TcxSoe. Uninstall SOE Recorder 10. Log on to Windows as an administrator or as a user with administrator privileges. 11. On the Start menu, click Settings | Control Panel. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 17 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix 12. Double-click Add or Remove Programs, and select Triconex Sequence of Events Recorder. 13. Click Change/Remove. Follow the on-screen instructions to confirm the deletion of the selected application and all its components 14. If you saved configuration files or event log files in the default directory, (C:\\Documents and Settings\\All Users\\Application Data\\Triconex\\TcxSoe in Windows XP Professional and Windows Server 2003, and C:\\ProgramData\\Triconex\\TcxSoe in Windows Server 2008 and Windows 7), the uninstall program does not remove them. 15. Click Yes or Yes to All if the Remove Shared File dialog box asks about removing unused DLLs. 16. Click Finish to complete the uninstallation process. Configure SOE The following steps explain how to display the SOE Configuration screen, which displays the SOE blocks that have been configured. 17. Expand the Application tree, double-click Implementation, and then click SOE Configuration. Define SOE Block Properties The following steps explain how to define the properties of an SOE block, which is required if you are using sequence of events in an application. Defining SOE block properties is related to the general task of controller configuration and can be completed at the same time. You can define SOE blocks to provide continuous event information to external devices on a network, or you can define them for limited operation when your controller is not on a network. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 18 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix 18. In TriStation 1131, open the project for the application in which you want to enable SOE. 19. Expand the Application tree, and then double-click Implementation. 20. Expand the SOE Configuration tree, and double-click a block number. 21. On the SOE Block Definition tab, in the SOE Block Type drop-down list, click the block type you want. 22. In the SOE Block Name field, enter a title for the block. 23. In the SOE Buffer Size field, enter a the SOE buffer size you want. 24. Click Apply to save the settings. 25. Repeat steps 20 − 24 for all the blocks to be configured. Assign Event Variables to SOE Blocks The following steps explain how to assign tagnames (event variables) to an SOE block, which is required if using sequence of events in an application. Note: Before you can assign event variables, you must define SOE block properties. 26. Click the Application tree, and then double-click Implementation. 27. Expand SOE Configuration, and then click a block number. 28. Double-click the Tagname (event variable) to be assigned, and then check the block numbers to assign event variables. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 19 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix 29. To assign other event variables to SOE blocks, repeat step 28. 30. After assigning all the event variables, save the project so the tagnames are available when specifying a trip variable. Specify a Trip Variable The following steps explain how to designate a trip variable, which is optional if you are using sequence of events in an application. In an application used for safety shutdown, a trip variable is an aliased tagname whose state transition causes SOE Recorder to automatically create a trip snapshot. An application can have one trip variable, but it can apply to all blocks. If an application requires several variables related to trip conditions, these variables must be evaluated in combination to determine the final state of the trip variable. Note: You must define at least one SOE block and assign an event variable to the block. 31. In TriStation 1131, open the project for the application in which you want to enable SOE. 32. Click the Application tree, and double-click Implementation. 33. Double-click SOE Configuration. The Item Properties dialog box appears. 34. On the SOE Trip Variable tab, in the Trip Tagname drop-down list, click the Trip Tagname you want. 35. In the Trip State drop-down list, set the Trip State by clicking True or False. 36. In the Time After Trip field, set the suitable time. 37. In the Time Before Trip field, set the suitable time. Note: The minimum time is two minutes; the maximum time is ten minutes. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 20 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix SOE Recorder Setup This section explains the steps required to set up SOE Recorder so you can retrieve and view event information. You can use the default settings for event retrieval or customize the options that are listed in the table. Table 2 – SOE Recorder Setup Options Description Display options for event Specifies the column display settings. files Periodic snapshots Specifies a snapshot based on a time period. Auto snapshots Specifies a snapshot based on a trip event or a maximum number of events. Event File Directory Specifies where to store the event files. Auto export to a journal file Automatically exports events to a file. TCP/IP network addresses Specifies TCP/IP addresses for controllers. The topics included are: • Copying the SOE Definition File • Specifying Display Options • Specifying Periodic Snapshots • Specifying Shift Snapshots • Specifying Auto Snapshot Options • Specifying an Event File Folder • Specifying Controllers for Retrieval • Specifying Automatic Export of Event Data Copying the SOE Definition File The SOE definition file contains SOE block definitions and point properties for the tagnames assigned to the SOE blocks. This file is generated on the TriStation workstation when you download your application to the controller. You must copy the file to the SOE Recorder’s SoeConfig directory before SOE Recorder can begin retrieving events. Specifying Display Options By default, all 10 columns of event information are displayed in the order indicated on the screen. You can change these settings before or during event retrieval, or when viewing a saved events file. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 21 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix When you create an events file, the current column display settings are automatically applied to the next file you create unless you change the settings. Adjustments you make to column widths while an events file is open are saved when you close the file. Specifying Periodic Snapshots A periodic snapshot is a file of all the events that are generated during a specific time period. Daily, weekly, and monthly snapshots can be generated, as well as a shift snapshot. A shift snapshot is based on specific time periods you designate for up to four weekday shifts and four weekend shifts. Periodic snapshot filenames include the date and time of the snapshot and one of the following file extensions: • _D.SED for daily snapshot. • _W.SED for weekly snapshot. • _M.SED for monthly snapshot. • _S.SED for shift snapshot. Specifying Shift Snapshots A shift snapshot retrieves events based on time periods you specify, which can include up to three weekday shifts and three weekend shifts. The name that SOE Recorder gives to a shift snapshot is the SED file name, concatenated with the date and time of the snapshot, and the extension _S.SED. Specifying Auto Snapshot Options An auto snapshot is a file of events that is saved automatically when a trip occurs or when a specified number of events occurs. You can have snapshots taken when either or both situations occur. Specifying an Event File Folder The Event File Folder property allows you to specify the folder used to store event files. The default events file directory is found in the following locations: • Windows XP Professional and Windows Server 2003: C:\\Documents and Settings\\<yourusername>\\My Documents\\Triconex\\Triconex Sequence of Events Recorder 4.2.0. • Windows 7 and Windows Server 2008: C:\\Users\\<yourusername>\\Documents \\Triconex\\Triconex Sequence of Events Recorder 4.2.0. Specifying Controllers for Retrieval To specify IP addresses, you must specify the IP address of each Triconex controller from which you want to retrieve events. If you are using one Triconex controller and one workstation running SOE Recorder, specifying a default address supplied by TriStation and 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 22 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix SOE Recorder is sufficient. If you want SOE Recorder to retrieve events from multiple controllers on a network, you must specify the IP addresses that are used by the controllers on the network. Specifying Automatic Export of Event Data You can enable this option before or after you begin retrieving events to specify the automatic export of event data to a dBASE IV or ASCII journal file. Event data are exported to the specified file every 30 seconds. To export events, SOE Recorder must have exclusive access to the journal file. If another application accesses the file for several minutes, SOE Recorder waits until the file is free to resume the export activity. If you do not specify a file name, SOE Recorder uses the name JOURNAL. If you don’t specify a path, SOE Recorder uses the SoeData directory under the directory where you installed the SOE Recorder executable. If you move a journal file from the original directory, SOE Recorder automatically creates a new journal file in the directory of origin. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 23 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Lab 2 : Setting SOE Recorder Introduction In this lab, you will set up SOE Recorder so that you can retrieve and view event information. Objectives After completing this lab, you will be able to: • Copy the SOE definition file. • Specify display options. • Specify periodic snapshots. • Specify shift snapshots. • Specify auto snapshot options. • Specify an event file folder. • Specify controllers for retrieval. Lab Procedure Copy the SOE Definition File Ensure that an SOE-enabled application is downloaded to each Triconex controller that will be collecting events. 1. On the TriStation workstation, go to the folder where your TriStation 1131 projects are stored, and locate the SOE definition file. The file name includes the first eight characters of the TriStation 1131 project name, the major version number, the minor version number, and a time code. For example: SOE_EX_9_0_33F4CE47.SOE The name of the file is displayed in the TriStation 1131 Message Bar when the application is downloaded to the controller. 2. Copy the SOE definition file to the SoeConfig folder on the SOE Recorder workstation. The default location is: C:\\Documents and Settings\\All Users\\Application Data\\Triconex\\TcxSoe\\SoeConfig in Windows XP Professional and Windows Server 2003, and C:\\ProgramData\\Triconex\\TcxSoe\\SoeConfig in Windows Server 2008 and Windows 7. 3. Repeat steps 1 − 2 for each controller that will be collecting events. Specify Display Options 24 4. From the Tools menu, click Options. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix 5. In the Options dialog box, click the Display tab. 6. On the Display tab, use the Column property to check or uncheck the column name to include or remove it from the display. 7. Use the Move property by clicking Up or Down to organize the columns. 8. Check the Auto Scroll option if you want event data to scroll continuously during live event retrieval. Note: This option is only available during live event retrieval, not with saved event files. 9. Click OK to save your changes. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 25 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Specify Periodic Snapshots 10. From the Tools menu, click Options, and then click the Mode tab. 11. Click the desired period for snapshots. Specify Shift Snapshots The name that SOE Recorder gives to a shift snapshot is the SED file name, concatenated with the date and time of the snapshot, and the extension _S.SED. 12. From the Tools menu, click Options, and then click the Mode tab. 13. Click Shift Snapshot, and then enter the start and stop times for Shift Definitions. Specify Auto Snapshot Options 14. From the Tools menu, click Options, and then click the Mode tab. 15. On the Mode tab, check the on-Trip Events check box to save a snapshot when a trip occurs. 16. Check the on Max Events check box to save a snapshot when a specified number of events occurs. Note: If you click the on Max Events options, enter the maximum number of events in the Maximum Number per Events field (up to 100,000) to retrieve. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 26 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix Specify an Event File Folder 17. On the Tools menu, click Options, and then click the Mode tab. 18. On the Mode tab, in the Event File Folder area, browse to the desired folder, and then click OK. 19. Click OK to save your changes. 27 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Specify Controllers for Retrieval 20. On the Tools menu, click Options, and then click the Communications tab. 21. Click the Trinode number for the desired controller, and then click Modify. 22. Change the Node Name if desired, enter the TCP/IP Address, and then click OK. Specify Automatic Export of Event Data 23. From the Tools menu, click Options, and then click the Auto Export tab. 24. To enable the option, check the Auto Export to a journal file check box. 25. On the Auto Export tab, click one of the Select journal file format options to export event data to a dBASE IV or ASCII Delimited Text journal file automatically. 26. In the Specify the absolute path for the Journal file field, specify the path for your journal file, including a file name. Note: To ensure that any dBASE IV application can open this file, you should limit the file name to eight characters. 27. Click OK to save your changes. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 28 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix SOE Recorder Event Retrieval This section describes how to retrieve events from one or more controllers. When you create a new event file, SOE Recorder looks for controllers that are connected to the network. If the controller is connected and the SOE definition file matches the SOE definition in the SoeConfig directory, you can retrieve events from it. The topics included are: • Setting Up Event Retrieval • Starting Events Retrieval • Ending Event Retrieval Setting Up Event Retrieval Before you start setting up event retrieval, make sure that the following tasks are performed: • The SOE definition file is copied from the TriStation application folder to the SoeConfig folder. • IP addresses are specified for the controllers from which you are going to retrieve events. • The options for event retrieval are set. Starting Events Retrieval Use the Begin Event Retrieval property to start SOE Recorder events retrieval. Ending Event Retrieval Use the End Event Retrieval property to turn off the SOE Recorder event retrieval process. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 29 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Lab 3 : Retrieving SOE Recorder Event Introduction This lab explains how to retrieve events from one or more controllers. Objectives After completing this, you will be able to: • Setup event retrieval. • Start event retrieval. • End event retrieval. Lab Procedure Set Up Event Retrieval 1. In SOE Recorder, on the File menu, click New Primary, New Redundant, or New Custom. One of the following happens: • For New Primary or New Redundant, the Create New SED File dialog box appears. • For New Custom, you are prompted to select a custom configuration file. If you have previously created a custom configuration file, select it. If not, create one. 2. In the File name field, enter a name for the sequence of events data file, and then click Create. Note: If you do not enter SED as the file extension, it is automatically appended to the file name. The SOE Retrieve dialog box appears, that lists the names of controllers (nodes) that are connected to your network. Note: If a controller is not on the list, it might not be connected to the network or the SOE definition file, it might be missing from the SoeConfig directory. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 Schneider Electric Proprietary and Confidential Information 30 © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix 3. To specify a controller for event retrieval, click the check box next to the node name. You can click only those nodes that have a file name in the SOE Configuration File column. Note: If the status is No response in the Status column, it means SOE Recorder could not connect to the node. If the status is No SOE Data, it means SOE Recorder is connected to the node, but no SOE blocks have been configured. Start Event Retrieval 4. On the Command menu, click Begin Event Retrieval or click the Begin Event Retrieval icon. SOE Recorder displays events in the event file as they are retrieved from the controller. If the Auto Scroll option is checked, the list automatically scrolls as events occur. Event retrieval continues until you click End Event Retrieval or at the end of a snapshot period. End Event Retrieval The following step explains how to turn off event retrieval. 5. On the Command menu, click End Event Retrieval, or click the End Event Retrieval icon. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 31 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Action Plan List skills you learned in this course that you can use on the job. 1. ______________________________________________________________________ 2. ______________________________________________________________________ 3. ______________________________________________________________________ 4. ______________________________________________________________________ 5. ______________________________________________________________________ 6. ______________________________________________________________________ 7. ______________________________________________________________________ 8. ______________________________________________________________________ 9. ______________________________________________________________________ 10. _____________________________________________________________________ 11. _______________________________ ______________________________________ 12. _____________________________________________________________________ 13. _____________________________________________________________________ 14. _____________________________________________________________________ 15. _____________________________________________________________________ 16. _____________________________________________________________________ 17. _____________________________________________________________________ 18. _____________________________________________________________________ 19. _____________________________________________________________________ 20. _____________________________________________________________________ 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 32 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved

Appendix 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 33 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal