Appendix A

Appendix A Enhanced Diagnostic Monitor 1 Internal



Appendix Contents of This Appendix 3 Steps for Diagnostic Monitoring.....................................................7 Installing and Starting the Enhanced Diagnostic Monitor...............7 Setting Up a Network Configuration..................................................8 Types of Network Configurations.....................................................8 Ethernet Network Configurations .....................................................8 Serial Links ......................................................................................9 Creating or Changing a Network Configuration ...............................9 Connecting a Node to a Network .......................................................9 Connecting in Read-Only Mode .........................................................9 Lab 1 : Setting Up a Network Configuration ............................... 11 Introduction .......................................................................................11 Objectives ..........................................................................................11 Lab Procedure ...................................................................................11 Install the Enhanced Diagnostic Monitor........................................11 Create or Change a Network Configuration ...................................11 Connect a Node to a Network........................................................12 Monitoring Controller Hardware .................................................. 14 Tri-GP System Overview Window....................................................14 Tri-GP Module Status Window .........................................................14 Module Colors................................................................................15 Tri-GP Module Status Dialog Box ....................................................16 Module Indicator Behavior ...............................................................17 Understanding External Faults ........................................................17 Locating and Correcting External Faults ........................................17 Understanding Internal Faults........................................................18 Locating and Correcting Internal Faults .........................................18 Clearing Faults on All Modules ......................................................19 Monitoring Output Voter Diagnostics (OVD) ..................................19 Monitoring Tri-GP SDO OVD and Supervision Status ...................19 Displaying Firmware Versions .........................................................19 Lab 2 : Monitoring Controller Hardware...................................... 20 Introduction .......................................................................................20 Lab Procedure ...................................................................................20 Change the Tri-GP Module Status Window View...........................20 Locate and Correct External Faults................................................20 Locate and Correct Internal Faults.................................................21 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 Clear Faults on All Modules ...........................................................22 Monitor Tri-GP SDO OVD and Supervision Status ........................22 Display Firmware Versions ............................................................23 Monitoring Controller Status........................................................ 24 Viewing Controller Status.................................................................24 Monitoring and Changing the Scan Time........................................25 Monitoring and Changing the Memory Allocation .........................25 Refreshing Controller Status ...........................................................25 Viewing Program Execution Times .................................................25 Collecting System Diagnostic Events .............................................26 Lab 3 : Monitoring Controller Status ........................................... 27 Introduction .......................................................................................27 Objectives ..........................................................................................27 Lab Procedure ...................................................................................27 View Controller Status....................................................................27 Monitor and Change the Scan Time ..............................................27 Monitor and Change the Memory Allocation ..................................28 Refresh Controller Status...............................................................28 View Program Execution Times.....................................................29 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 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 5 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal



Appendix Steps for Diagnostic Monitoring Figure 1 shows the main steps for using the Tristation 1131 Diagnostic Monitor software to monitor controllers on a network. Figure 1 – Steps for Diagnostic Monitoring Installing and Starting the Enhanced Diagnostic Monitor The Enhanced Diagnostic Monitor is intended to be installed on a Foxboro™ Distributed Control System (DCS) operator workstation, but can be installed on any WORKSTATION located on the same network as the Triconex controller(s) you will be monitoring. Before you start the Enhanced Diagnostic Monitor installation, make sure you have installed the latest service packs and critical updates for your version of Windows. To look for recent updates, visit the Microsoft Windows Update website. If the .NET Framework is not already installed, setup will install it for you before installing the Enhanced Diagnostic Monitor. If necessary, setup will also install Windows Installer v4.5 prior to installing the .NET Framework. Depending on your WORKSTATION’s configuration, Windows Installer and .NET Framework installation can take several minutes, and may require you to restart your WORKSTATION in order to complete the installation process. If you receive any errors during the .NET Framework installation, contact your system 7 administrator for assistance. 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 To start the Diagnostic Monitor, navigate to the Triconex shortcut, and then click Diagnostic Monitor. For installation instructions, refer to the TriStation 1131™ Developer’s Guide. Setting Up a Network Configuration A network configuration is an XML file which includes the Tri-GP controllers you want to monitor. You can create network configurations for Ethernet networks, and for serial links. You can add controllers to a network configuration, and edit their properties as often as needed. To begin monitoring controllers, you must connect the Diagnostic WORKSTATION to the network and open each controller in the network configuration. The topics included are: • • Connecting a Node to a Network • Types of Network Configurations • Creating or Changing a Network Configuration • Connecting a Node to a Network Types of Network Configurations A network configuration can include Triconex controllers on Ethernet networks and on serial links. Ethernet Network Configurations For Ethernet networks, a network configuration can include controllers on one network, or on multiple networks, assuming the networks are connected and set up for communication. Figure 2 shows a typical network of Triconex controllers, which can be specified in a network configuration for diagnostic monitoring. Figure 2 – Ethernet Network Configurations 8 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0

Appendix Serial Links For Tri-GP, a network configuration can include controllers on serial links, which use Modbus communication. Figure 3 shows Tricon controllers on a typical multi-point serial link. Figure 3 – Serial Links Creating or Changing a Network Configuration Create or change a network configuration of controllers to be monitored. Before starting, you should know the settings of the following properties for each controller to be included in the network configuration: • Node name and node number. • IP address (for an Ethernet connection). • Type of TriStation connection. • UDP port numbers (for a network connection). Connecting a Node to a Network Before you start connecting a node in a network configuration to a network, the Diagnostic WORKSTATION must be connected to a network or serial link with an appropriate cable. In addition, you must have created a network configuration and added node specifications to it. Connecting in Read-Only Mode A network node will connect in read-only mode under any of the following conditions: • You click Ignore in the Enter Password dialog box when prompted for the application password. 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 • A CM is installed in the Tri-GP controller and the CM client access list has been enabled and configured so that the IP address of the diagnostic WORKSTATION has read-only access via the TriStation protocol. When connected in read-only mode, you can only view system or module status. The following operations are not allowed when connected in read-only mode: • Collecting system events. • Clearing module faults. Note: When connected in read-only mode due to a Tri-GP CM client access list permission (read- only access via the TriStation protocol), you are allowed to collect system events for a node. However, if the node is password-protected, you still must know the correct password in order to collect events. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 10

Appendix Lab 1 : Setting Up a Network Configuration Introduction A network configuration is an XML file that includes the Tri-GP controllers you want to monitor. You can create network configurations for Ethernet networks, and for serial links. You can add controllers to a network configuration, and edit their properties as often as needed. To begin monitoring controllers, you must connect the Diagnostic WORKSTATION to the network and open each controller in the network configuration. Objectives After completing this lab, you will be able to: • Install the Enhanced Diagnostic Monitor. • Create or change a network configuration. • Connect a node to a network. Lab Procedure Install the Enhanced Diagnostic Monitor 1. Log on to Windows as an administrator or as a user with administrator privileges. 2. Close all open applications. 3. Insert the Enhanced Diagnostic Monitor 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. Create or Change a Network Configuration 1. On the File menu, click New Network Configuration or Open Network Configuration. 2. To add a node, right-click Network Nodes at the top of the tree, and then click Add. 3. To edit a node, right-click the node name on the tree, and then click Edit. 4. In the Controller Type drop-down list, click your controller type. 5. In the Node Number field, enter the node number of the controller. 6. In the Node Name field, enter the node name of the controller. 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 7. In the Connection Type drop-down list, configure the parameters as follows: • Network for an Ethernet (TCP/IP) connection. • Serial for a serial (Modbus) connection to a Tri-GP controller. 8. In the IP Address field, configure the IP address of the controller to be monitored. Note: The default IP address that initially appears (192.168.1.n) cannot be used for Tri-GP controllers. You must browse for the correct Tri-GP default IP address as described above, or enter your own IP address. 9. For a Network connection, specify the UDP port to use for the Enhanced Diagnostic Monitor connection (via the TriStation protocol) to a Tri-GP controller with a CM installed. The default is 1502. 10. For a Tri-GP Serial connection, select the COM port on the diagnostic WORKSTATION which is connected to the controller. 11. Repeat steps 2 −10 for each node you want to add or change. 12. On the File menu, click Save Network Configuration, and save the XML file to a new name and destination, or the same name and destination. Connect a Node to a Network 13. On the File menu, click Open Network Configuration. 14. Right-click the name of a node on the tree, and then click Open. The node connects automatically to the network, or requests a password if one was specified for the application running in the controller. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 12

Appendix Note: If the node cannot connect to the network, right-click the node, and then click the Edit. Examine the properties on the Network Node Configuration window, change any field that is incorrect, and then repeat step 14. 15. If the node disconnects from the network, click the node name on the tree, and then click Connect. 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 Monitoring Controller Hardware The Enhanced Diagnostic Monitor allows you to identify alarms on Tri-GP IOPs, and faults on power supplies, modules, and points. After correcting faults, you can clear them on a specific module or on all modules. In addition, monitor the OVD and supervision status of Tri-GP supervised digital output modules, and display the firmware version numbers for all types of modules. For corrective actions (such as replacing a module with a spare), refer to the maintenance guidelines in the Planning and Installation Guide. The topics included are: • Tri-GP Module Status Dialog Box • Module Indicator Behavior • Understanding External Faults • Locating and Correcting External Faults • Understanding Internal Faults • Locating and Correcting Internal Faults • Clearing Faults on All Modules • Monitoring Output Voter Diagnostics (OVD) • Displaying Firmware Versions Tri-GP System Overview Window The Tri-GP System Overview window, Figure 4, displays an icon for each IOP (input/output processor) in the configuration. Healthy IOPs are green; IOPs with modules that have faults are red. Figure 4 – Tri-GP System Overview Window Tri-GP Module Status Window The Module Status window, accessible through the Configuration tree, shows the setup of modules in an lOP, Figure 5. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 14

Appendix Figure 5 – Tri-GP Module Status Window Module Colors The IOP window uses these colors to represent the current state of each module, as shown in Table 1. Table 1 – Module Colors Slot Color Meaning Red Module configured in the project is not installed in the slot. Yellow Module installed in the slot is not configured in the project. Gray Module is configured in the project and installed in the slot. Blue Slot is currently selected. The module colors are described on the Legend tab of the Module Status window for each module, Figure 6. Figure 6 – Legend tab 15 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 Tri-GP Module Status Dialog Box For an I/O or communication module, the Module Status window includes Left Module and Right Module tabs, Figure 7. Figure 7 – Tri-GP Module Status Dialog Box For the Main Processors, the Module Status window includes the Left Module, Middle Module, and Right Module tabs, Figure 8. Figure 8 – Middle Module Each tab on a Module Status window provides this information about faults. Option Description Current Faults Displays the current faults on a module, which can include internal Fault History faults and field faults (external faults). Field Faults Displays all the faults that have occurred during this session. Displays load or fuse faults related to field inputs, terminations, wiring, or devices. (Field faults do not apply to Main Processors.) 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 16

Appendix Module Indicator Behavior Module indicators in the Module Status window behave the same as module indicators on the controller, with these exceptions: • During the power-up of a controller, the indicators in the Diagnostic Monitor are Off (gray). • Blinking indicators blink more slowly. • Indicators that are blinking very quickly may appear static in the Module Status window. Understanding External Faults An external fault is a problem with field inputs, field power supplies, terminations, wiring, or connected devices. Modules report external faults through the indicator named FIELD POWER on the affected module turns yellow. If the module has a power fault, the FIELD POWER and SYSTEM ALARM indicators on the main processors also turn on. If an external fault occurs, you should read the diagnostic messages on the Module Status window and examine the field inputs, field power supplies, terminations, wiring, and connected devices. For detailed information about faults and module indicators, refer to the Planning and Installation Guide. A controller is subject to these types of external faults, Table 2. Table 2 – Fault Description Fault Type Description Field Fault on Digital Output A load or fuse problem related to field terminations on Point the controller, field wiring, or field devices. Field Fault on Input Point Power Fault A faulty power supply. For Tri-GP, a power fault refers to the field power supplies, which are connected to a specific module. • Field Power Supply 1 has a problem • Field Power Supply 2 has a problem • There is a problem with field inputs, field power supplies, terminations, wiring, and connected devices. Locating and Correcting External Faults Before starting, the Diagnostic WORKSTATION must be connected to the network, and the node of interest must be open. For more information about fault conditions, refer to the Planning and Installation Guide. 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 Understanding Internal Faults Internal faults are failures in the internal circuitry of a module. If a module has an internal fault, its Fault indicator turns red. You should replace the module with a spare as soon as possible. For instructions, refer to the Planning and Installation Guide, Table 3. If you replace a module and the Fault indicator immediately turns red, you should read the diagnostic messages on the Module Status window and investigate the field inputs. If the inputs are changing rapidly, they may be causing the Fault indicator to turn On. An internal fault is usually isolated to one channel (A, B, or C) of the faulting module, which means that the other two channels can maintain full control. Depending on the specific fault, the module remains in TMR mode or degrades to dual mode. A controller is subject to these types of internal faults. Table 3 – Fault Type Fault Type Description Minor Major A fault that is usually transient in nature and has no Voter impact on system operation. An example is a CRC error in one message. (Does not cause the Fault Fatal indicator to turn red.) A fault that degrades system operation, but does not affect the correct voting of system inputs or outputs. An example is a fault that inhibits diagnostics on one or more channels. A fault that can occur on a Digital Output module only, if the OVD circuitry becomes defective. Examples are an output switch stuck high or stuck low. Voter faults on two channels of a single point may lead to loss of control of that point. A fault on channel A, B, or C of an I/O module which prevents the channel from reading at least one input point or controlling at least one output point. An example is loss of communication with one channel of an I/O module. The module continues to operate correctly using the remaining two channels. Depending on the specific fatal fault and module type, many modules continue to operate correctly with fatal faults on two channels. Triconex recommends replacing any module whose Fault indicator is red, unless the application allows the controller to run in dual or single mode for a specified time period before shutting down. Locating and Correcting Internal Faults Before starting this procedures, the Diagnostic WORKSTATION must be connected to the network, and the node of interest must be open. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 18

Appendix Clearing Faults on All Modules Use the proper procedures in this section to clear the faults on all modules in a controller. Monitoring Output Voter Diagnostics (OVD) This section explains how to monitor the OVD status of Digital Output modules and points. OVD verifies the ability of each digital output point to transition to the energized and de- energized states, and detects failures in the output voting mechanism. By default, OVD is enabled for all the DO modules in a controller. You can disable and enable OVD for individual Digital Output points. Note: Disabling OVD is a potentially dangerous action that should only be taken if nuisance alarms are occurring and other actions cannot be taken. A safety application may not disable OVD. Note: While you can use the Enhanced Diagnostic Monitor to monitor the OVD status of SDO points in the Tri-GP controller, you cannot monitor the OVD status of DO points in the Tri-GP controller. To monitor the OVD state of DO points, you must use the SYS_DO16_STATUS function block in conjunction with the UNPACK16 function block, and view these function blocks in the Controller Panel of TriStation 1131 during online execution. Monitoring Tri-GP SDO OVD and Supervision Status The Tri-GP model 3411S2 Supervised Digital Output (SDO) modules provide loop supervision to field devices in fire and gas applications. 16 points are available; each point can be independently configured. Displaying Firmware Versions To display the firmware version numbers of all modules in a Tri-GP IOP, you only need to know the firmware version numbers if requested by a Triconex Technical Support Engineer for diagnostic purposes. 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 Lab 2 : Monitoring Controller Hardware Introduction In this lab, you will monitor controller hardware. The Enhanced Diagnostic Monitor allows you to identify alarms on Tri-GP IOPs, and faults on power supplies, modules, and points. After correcting faults, you can clear them on a specific module, or on all modules. Note: For corrective actions (such as replacing a module with a spare), refer to the maintenance guidelines in the Planning and Installation Guide. Objectives After completing this lab, you will be able to: • Change the Tri-GP Module Status window view. • Locate and correct external faults. • Locate and correct internal faults. • Clear faults on all modules. Lab Procedure Change the Tri-GP Module Status Window View The following steps explain how to change your view of the modules in a Module Status window. 1. Expand the System Overview tree, and then click a module to display the Module Status window. 2. On the View menu, click Zoom, and then perform one of the following options: • Click 200, 100, 75, or 50 percent. • Click Custom, and then enter the desired percentage. • Click Zoom to fit to size the elements into the window. Locate and Correct External Faults 3. On the System Overview tree, click System Overview to view the Chassis or IOP alarm icons. 4. If an alarm is On (red), open the Chassis or IOP view, and then double-click a module with a yellow indicator. 5. On the Module Status window, click the following tabs to locate the fault details: • Tri-GP, on the Left Module and Right Module tabs, click Current Faults and Field Faults 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 20

Appendix 6. Examine the relevant field inputs, power supplies, terminations, wiring, and connected devices, and then repair the faulty items. 7. On the Module Status window, click Clear Faults, and then wait ten minutes to see if the yellow indicator turns on again. If it does, repeat step 5 and step 6. 8. When all the faults are corrected, on the Module Status window, click the tab that displays the faulting points, and then click Clear Faults. Locate and Correct Internal Faults The following steps explain how to locate, correct, and clear internal faults on a module. Before starting, you must connect the Diagnostic WORKSTATION to the network, and the node of interest must be open. 9. On the System Overview tree, click System Overview to view the Chassis or IOP alarm icons. 10. If an alarm is On (red), open the Chassis or IOP view, and then double- click a module with a red indicator. 11. On the Module Status window, click the following tabs to find the fault messages: • For Tri-GP, on the Left Module and Right Module tabs, click the Current Faults setting 12. On the Module Status window, click Clear Faults, and then wait ten minutes to see if the red indicator turns On again. If it does, replace the module. 13. If you replace a module and the Fault indicator immediately turns red, you should investigate the field inputs. Rapidly changing field inputs may be causing faults. 14. When all faults are corrected, on the Module Status window, click the tab that displays the fault information, and then click Clear Faults. 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 Note: For instructions, refer to the Planning and Installation Guide. Clear Faults on All Modules The following steps explain how to clear the faults on all modules in a controller. 15. Ensure that all faults have been identified and corrected. 16. On the Commands menu, click Clear Faults on All Modules. The Tri-GP IOP alarm turns off, and the Fault indicators on the faulting modules turn Off (gray) as well. Monitor Tri-GP SDO OVD and Supervision Status 17. On the System Overview tree, expand a baseplate node, and then click a module to display the Module Status window. 18. In the Module Status window, double-click an SDO module to open the Module Status dialog box for the module. 19. Click the Point Status tab. 20. For each SDO point, review the OVD status. The OVD status for the selected point can be Running or Not Running. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 22

Appendix 21. Review the Supervision status. The supervision status for the selected point can be Running or Not Running. Display Firmware Versions 22. On the Commands menu, click Display Firmware Versions. The list of module firmware version numbers appears in the Messages pane at the bottom of the Enhanced Diagnostic Monitor window. 23. To copy, print, or save the firmware version information, right-click anywhere in the Messages pane, and then select the desired command from the shortcut menu that appears. 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 Monitoring Controller Status The Enhanced Diagnostic Monitor allows you to monitor controller status on a System Overview window. Before starting, you must perform the following: • Create a network configuration, which includes node specifications for the controllers you want to monitor, or open an existing network configuration. • Connect the Diagnostic WORKSTATION to the network. • Open the nodes you want to monitor. Note: You can also access controller performance and project information using function blocks in the TriStation 1131 standard libraries and for Tri-GP, using system attributes. The topics included are: • Viewing Controller Status • Monitoring and Changing the Scan Time • Monitoring and Changing the Memory Allocation • Refreshing Controller Status • Viewing Program Execution Times • Collecting System Diagnostic Events Viewing Controller Status Use this option to view the controller status on a System Overview window. To correct scan time problems or allocate more memory, refer to the TriStation 1131™ Developer’s Guide. Table 4 lists the properties that appear on the System Overview window: Table 4 – Viewing Controller Status Property Description Project Calendar Displays the name and version number of the project (application) Poll Time being monitored. Maximum Memory Displays the current time of the controller being monitored in the Scan Request/ Actual day/ date/hour/minute/second format. Displays the maximum time a controller needs to obtain data from the input modules. Ensure the poll time does not exceed the scan time. Displays the maximum amount of memory that the controller originally made available to the TriStation project. Displays the requested scan time and the actual scan time. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 24

Appendix Property Description Free Memory Status Displays the amount of memory available for project expansion. Scan Surplus Displays the current state of the application running in a controller. Displays the time that remains in a scan after the control functions are completed. Monitoring and Changing the Scan Time Scan time is the time required by the controller to process the TriStation 1131 application on the controller, which includes the following operations: • Read inputs. • Execute the application. • Process communication messages (TriStation protocol, TSAA, Modbus, Peer-to- Peer, and so on). • Write outputs. Monitoring and Changing the Memory Allocation Use the TriStation 1131 to monitor the memory allocation of a controller in the System Overview window, and then change the memory allocation. Refreshing Controller Status You can refresh the System Overview and Hardware Configuration windows while you are monitoring a controller. You can also refresh the information occasionally or continuously. Viewing Program Execution Times The programs are identified as Program 0, Program1, and so on. The first and the last programs are provided by TriStation 1131 to initialize and terminate the scan. The other programs are the programs specified in the program execution list in the TriStation 1131 project. 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 Collecting System Diagnostic Events As shown in Figure 9,Events can be viewed as they are being collected, or you can save the collected events to a file without viewing them. Events are saved to event log files (.tce or .tde). Summary information about the event log file currently being viewed is displayed in the Events Summary pane. If you choose to view system events as they are collected, events are also displayed in the bottom half of the System Overview, Module Status, and Communication Status windows, in the Events pane. Figure 9 – Events View Before you can collect events, you must complete these steps: • Connect the diagnostic WORKSTATION to the network. • Create a network configuration which includes node specifications for the controllers whose events you want to collect, or open an existing network configuration. • Open the nodes you want to collect events for. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 26

Appendix Lab 3 : Monitoring Controller Status Introduction This lab explains how to use the Diagnostic Monitor to monitor controller status on a System Overview window. Before starting, you must perform these steps: • Create a network configuration, which includes node specifications for the controllers you want to monitor or open an existing network configuration. • Connect the Diagnostic WORKSTATION to the network. • Open the nodes you want to monitor. Objectives After completing this lab, you will be able to: • View controller status. • Monitor and change the scan time. • Monitor and change the memory allocation. • Refresh controller status. • View program execution times. • Collect System Diagnostic events. Lab Procedure View Controller Status The following steps explain how to view controller status on a System Overview window. For more information about correcting scan time problems or allocating more memory, refer to the TriStation 1131™ Developer’s Guide. 1. On the Network Nodes tree, double-click the node you want to monitor. 2. Click System Overview on the Controller tree. 3. View the performance and project information on the right pane. Monitor and Change the Scan Time The following steps explain how to monitor the scan time in the System Overview window, and then change the scan time using TriStation 1131. 4. On the Network Nodes tree, double-click the node of interest. 5. Click System Overview on the Controller tree. 6. On the right pane, view the following properties, which are related to the scan time. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 27 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal

Appendix Property Action Poll Time Displays the maximum time needed by a controller to obtain data Scan Request/Actual from the input modules. Scan Surplus You should ensure the poll time does not exceed the scan time. Displays the requested scan time and the actual scan time. Displays the time that remains in a scan after the control functions are completed. To avoid communication errors, ensure the scan surplus is positive. 7. If the poll time exceeds the scan time or the scan surplus is negative, use the Controller Panel in the TriStation 1131 project to adjust the scan time. Note: If the poll time exceeds the scan time or the scan surplus is negative, use the Controller Panel in the TriStation 1131 project to adjust the scan time. Monitor and Change the Memory Allocation The following steps explain how to monitor the memory allocation of a controller in the System Overview window, and then change the memory allocation using TriStation 1131. 8. On the Network Nodes tree, double-click the node of interest. 9. Click System Overview on the Controller tree. 10. On the right pane, view the following properties related to the memory allocation. Property Action Maximum Memory Displays the maximum amount of memory that the controller Free Memory originally made available to the TriStation project. Displays the amount of memory available for project expansion. 11. If you plan to make changes to the application that require more memory, use the Configuration tree in the TriStation project to allocate more memory, and then do a Download All. Note: For instructions, refer to the TriStation 1131 Developer’s Guide. Refresh Controller Status The following steps explain how to refresh the System Overview and Hardware Configuration windows while you are monitoring a controller. You can refresh the information occasionally or continuously: 12. On the Network Nodes tree, double-click the node (controller) desired. 13. To refresh the System Overview and Hardware Configuration windows once, on the Commands menu, click Refresh Panel. 14. To continuously refresh the System Overview and Hardware Configuration, on the Commands menu, click Continuous Refresh. 8602 Triconex General Purpose (Tri-GP) Configuration and Implementation A.0 28

Appendix View Program Execution Times 15. On the Network Nodes tree, double-click the node (controller) of interest. 16. On the Commands menu, click Display Execution Times. The execution time for each program displays in the Messages pane. 17. To copy, print, or save the program execution information, place the cursor in the Diagnostic Message Window, right-click, and then click the desired commands. 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 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 9 Schneider Electric Proprietary and Confidential Information © 2021 Schneider Electric Systems USA, Inc. All Rights Reserved Internal