Triconex Enhanced Diagnostic Monitor PDF

Triconex Enhanced Diagnostic Monitor
User’s Guide
Enhanced Diagnostic Monitor, Version 1.0
Assembly No. 9700107-001
April 2006
Information in this document is subject to change without notice. Companies, names and data used in
examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or
transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express
written permission of Triconex.
© 2006 Invensys Systems, Inc. All Rights Reserved.
Triconex, Tricon, Trident, TriStation 1131, TriStation MSW, and CEMPLE are trademarks of Invensys plc,
its subsidiaries and affiliates. All other brands may be trademarks of their respective owners.
Document No. 9720107-001

Printed in the United States of America.
Contents
Preface v
New Features in the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Summary of Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Product and Training Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
We Welcome Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Chapter 1 Getting Started 1

Installing the Enhanced Diagnostic Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installing the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Uninstalling the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installing the DLC Protocol on the Diagnostic PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Starting the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Creating and Managing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Adding and Modifying User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Changing the Security Level for Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Changing Security Level Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Other Permissions Affecting User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting Up a Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Types of Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating or Changing a Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Opening a Network Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2 Monitoring Controller Hardware 23

System Overview and Module Status Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Tricon System Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Tricon Module Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Trident System Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Trident Module Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Understanding External Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Locating and Correcting External Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Understanding Internal Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Locating Internal Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Clearing Faults on All Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

iv Contents
Monitoring Output Voter Diagnostics (OVD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Displaying Firmware Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 3 Monitoring Controller Status 39

Viewing Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Monitoring and Changing the Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Changing the Scan Time Using TriStation 1131 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Monitoring and Changing the Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Changing the Memory Allocation Using TriStation 1131 . . . . . . . . . . . . . . . . . . . . . . 43
Refreshing Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Viewing Data in the Messages Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Viewing Program Execution Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Collecting and Viewing Tricon System Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Interpreting Tricon System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Opening the Events and Events Summary Panes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Managing Tricon Event Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Starting Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Stopping Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Changing the Default Event Collection Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Filtering the Events List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Modifying the Event Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Viewing an Existing Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Exporting an Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Collecting Trident System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Appendix A Commands and Properties 65
Appendix B Converting Tricon Hexadecimal Board Addresses 91

Tricon v9 / v10 High-Density Conversion Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Hex to Chassis / Slot Conversion Tables—All High-Density Chassis . . . . . . . . . . . 93
High-Density Chassis Physical Slot Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Tricon v9 Low-Density Conversion Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Hex to Chassis / Slot Conversion Tables—Low-Density Main and RXM Chassis . 96
Hex to Chassis / Slot Conversion Tables—Low-Density Expansion Chassis . . . . . 97
Low-Density Chassis Physical Slot Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Index 101

Preface
The Triconex™ Enhanced Diagnostic Monitor is a software program for monitoring the
hardware and application status of Tricon and Trident controllers.
New Features in the Enhanced Diagnostic Monitor

The Enhanced Diagnostic Monitor v1.0 improves upon the previous version of Diagnostic
Monitor (v4.1) by adding several new features:
• Support for the Tricon Communication Module (TCM).
• Improved Tricon system event collection, including the ability to view events while
they are being collected, and export saved event log files to database (.dbf) files.
• User management, so that access to the Enhanced Diagnostic Monitor application can
be controlled via user IDs/passwords with assigned security levels.
Summary of Sections
• Chapter 1, Getting Started—Explains how to create and modify a network
configuration, and create and manage user accounts.
• Chapter 2, Monitoring Controller Hardware—Describes how to monitor module status,
interpret and correct faults, and monitor OVD status.
• Chapter 3, Monitoring Controller Status—Explains how to view current controller
status, including information about scan time, memory allocation, program execution,
and communications information. Also provides instructions for viewing and
collecting system events.
• Appendix A, Commands and Properties—Describes commands and properties in the
Enhanced Diagnostic Monitor.
• Appendix B, Converting Tricon Hexadecimal Board Addresses—Explains how to
convert the physical (chassis/slot) location of a module in a Tricon to its hexadecimal
board address.

vi Preface
Related Documents
• TriStation 1131 Libraries Reference
• TriStation 1131 Developer’s Guide
• Tricon and Trident Communication Guides
• Tricon and Trident Planning and Installation Guides
Product and Training Information

To obtain information about Triconex products and in-house and on-site training, see the
Triconex Web site or contact your regional customer center.
Web Site
http://www.triconex.com
Technical Support
Customers in the U.S. and Canada can obtain technical support from the Customer Satisfaction
Center (CSC) at the numbers below. International customers should contact their regional
support center.
Requests for support are prioritized as follows:
• Emergency requests are given the highest priority
• Requests from participants in the System Watch Agreement (SWA) and customers with
purchase order or charge card authorization are given next priority
• All other requests are handled on a time-available basis
If you require emergency or immediate response and are not an SWA participant, you may
incur a charge. Please have a purchase order or credit card available for billing.
Telephone
Toll-free number 866-746-6477, or
Toll number 508-549-2424 (outside U.S.)
Fax
Toll number 508-549-4999
Web Site
http://customernet.triconex.com (registration required)
E-mail
ips.csc@ips.invensys.com

Preface vii
We Welcome Your Comments

To help us improve future versions of Triconex documentation, we want to know about any
corrections, clarifications, or further information you would find useful. When you contact us,
please include the following information:
• The title and version of the guide you are referring to
• A brief description of the content you are referring to (for example, step-by-step
instructions that are incorrect, information that requires clarification or more details,
missing information that you would find helpful)
• Your suggestions for correcting or improving the documentation
• The version of the Triconex hardware or software you are using
• Your name, company name, job title, phone number, and e-mail address
Send e-mail to us at:
triconextechpubs@ips.invensys.com
Please keep in mind that this e-mail address is only for documentation feedback. If you have a
technical problem or question, please contact the Customer Satisfaction Center. See Technical
Support (page vi) for contact information.
Or, you can write us at:
Attn: Technical Publications
Triconex
15345 Barranca Parkway
Irvine, CA 92618
Thank you for your feedback.

viii Preface

1
Getting Started
Steps for Diagnostic Monitoring 2

Installing the Enhanced Diagnostic Monitor 3
Starting the Enhanced Diagnostic Monitor 7
Creating and Managing Users 8
Setting Up a Network Configuration 16

2 Chapter 1 Getting Started
Steps for Diagnostic Monitoring

This figure shows the main steps for using the Enhanced Diagnostic Monitor software to
monitor Triconex controllers on a network.
C reate User
Accounts
C reate A Network
C onfiguration
C onnect to C ontrollers
Monitor C ontroller Monitor C ontroller

Status Hardware
Monitor System &

Module Status Replace
Use TriStation 1131 to: Internal
Module
- Adjust Scan Time
Yes
- Allocate More Memory
Faults?
C ollect System
Events
No Repair Field
External
Devices
Yes
P roble m s?
No

Installing the Enhanced Diagnostic Monitor

This section explains how to install and uninstall the Enhanced Diagnostic Monitor.
The Enhanced Diagnostic Monitor is compatible with the following Triconex controllers:
• Tricon v9.51 and later
• Trident v1.2 and later
You do not need to keep any previous versions of Diagnostic Monitor installed on your system.
To ensure access to the most recently released hardware, you should install and use only the
latest version of the Enhanced Diagnostic Monitor.
Note Throughout this manual, the PC on which you install and use the Enhanced Diagnostic
Monitor is referred to as the diagnostic PC.
Topics include:
• System Requirements on page 3
• Installing the Enhanced Diagnostic Monitor on page 4
• Uninstalling the Enhanced Diagnostic Monitor on page 4
• Installing the DLC Protocol on the Diagnostic PC on page 5
System Requirements
The following are the minimum system requirements for the Enhanced Diagnostic Monitor:
• PC running Windows 2000 or XP
• Pentium 233 MHz with 128 MB RAM
• 25 MB free hard drive space (for installation of the application only; if you are
intending to collect events, a larger hard drive may be needed)
• CD-ROM drive
• Network adapter card
• SVGA monitor running at 1024 x 768 resolution with 64,000 colors
• DLC protocol installed (see Installing the DLC Protocol on the Diagnostic PC on page 5)
Note For optimum display performance while using Enhanced Diagnostic Monitor, Triconex
recommends using the “Normal” system font size. To change this setting, go to Start >
Control Panel, double-click Display, and then click the Appearance tab.

Installing the Enhanced Diagnostic Monitor

This procedure explains how to install the Enhanced Diagnostic Monitor software.
If you have previously installed Diagnostic Monitor version 4.1 or earlier, you do not need to
uninstall it before installing the Enhanced Diagnostic Monitor. Installing Enhanced Diagnostic
Monitor will not overwrite an existing Diagnostic Monitor v4.1 installation.
You do not need to install the Enhanced Diagnostic Monitor on the same PC as TriStation 1131.
Procedure
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.
If the installation starts automatically, go to step 8. Otherwise, go to the next step.
4 From the Start menu, click Settings, and then click Control Panel.
5 Double-click Add New Programs.
6 Click the CD or Floppy button, and then browse to locate the setup.exe file on the CD.
7 Double-click setup.exe to start the installation.
8 Follow the InstallShield Wizard instructions.
Triconex recommends installing the Enhanced Diagnostic Monitor software in the
default destination folder, which is: C:\Program Files\Triconex\Enhanced
Diagnostic Monitor 1.0.
Uninstalling the Enhanced Diagnostic Monitor

This procedure explains how to uninstall the Enhanced Diagnostic Monitor.
Procedure
1 Log on to Windows as an administrator or as a user with administrator privileges.
2 From the Start menu, click Settings, and then click Control Panel.
3 Double-click Add/Remove Programs, and select Triconex Enhanced Diagnostic
Monitor 1.0.
4 Click Change/Remove. Follow the on-screen instructions to confirm the deletion of the
selected application and all its components.
Note If you saved network configuration files or event log files in the default directory,
(C:\Program Files\Triconex\Enhanced Diagnostic Monitor 1.0), the
uninstall program does not remove them.
5 Click Yes or Yes to All if the Remove Shared File dialog box asks about removing unused
DLLs.
6 Click Finish to complete the uninstallation process.

Installing the DLC Protocol on the Diagnostic PC

These procedures explain how to install the DLC protocol on the diagnostic PC.
The DLC protocol is required for Trident MP connection, and for using Enhanced Diagnostic
Monitor on a Windows XP workstation.
Installing DLC on Windows 2000

1 On the Start menu, click Settings, then click Network and Dial-up Connections.
2 Right-click the network connection where you want to install the DLC protocol, then
click Properties.
3 Do one of the following:
• On the Networking tab, if the DLC protocol is checked on the list of installed
components, it means the protocol is installed and you are finished with this
procedure.
• If the DLC protocol is not checked, go to the next step to continue the installation.
4 Click Install, click Protocol, then click Add.
5 On the Select Network Protocol screen, click the DLC protocol on the Network Protocol
list, and then click OK.
6 Verify the check box for the DLC protocol is selected, and then click OK.
Installing DLC on Windows XP

Installing the DLC protocol on a Windows XP workstation is a 3-step process.
Note If you have already installed the DLC protocol on your workstation, you can configure
it to start automatically each time you start your workstation by changing a registry
value. Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Dlc, and
then change the Start value to 1.
Step 1: Download the DLC Protocol Installation Program

1 Open your Internet browser, and enter the following URL in the address field:
http://www.microsoft.com/downloads/
2 In the Search for a Download section, perform a search for “DLC Protocol” and then go
to the download page for the DLC protocol for Windows XP.
3 Follow the instructions on the download page to start the download process.
4 When prompted, save the dlc.exe file to your local drive.
5 When the download is complete, double-click the self-extracting dlc.exe file to unzip the
five DLC protocol files.
Save the files to a location on your local drive that will be easy to remember (for example,
C:\DLC).

Step 2: Modify the .Inf File

1 Go to the location where you saved the DLC protocol files in step 5 of the previous
section.
2 Right-click on NetDLC.inf, and select Open with from the shortcut menu that appears.
Then select Notepad from the Open with dialog box and click OK. The .inf file opens in
Notepad.
3 Scroll down until you see the following section:
4 Change the value for StartType from 3 to 1. This ensures that the DLC protocol will start
automatically each time you start your workstation.
5 Save the file and then exit Notepad.
Step 3: Configure the DLC Protocol Network Connection

1 Go to the location where you saved the DLC protocol files in Step 1: Download the DLC
Protocol Installation Program.
2 Double-click install.cmd to start the installation script.
3 On the Start menu, click Control Panel, and then double-click Network Connections.
4 Right-click the network connection where you want to install the protocol, then click
Properties.
5 On the General tab, click Install.
6 In the Select Network Component Type dialog box, click Protocol, and then click Add.
7 Click the DLC Protocol, and then click OK.
8 Once installation is complete, you can close the Network Connections dialog box.

Starting the Enhanced Diagnostic Monitor 7
Starting the Enhanced Diagnostic Monitor

A user name and password is required to open the Enhanced Diagnostic Monitor application.
There is no limit on the number of times you can attempt to enter your user name and password.
To start the Enhanced Diagnostic Monitor:

1 On the Start menu, select Programs > Triconex > Enhanced Diagnostic Monitor 1.0.
The Login dialog box appears.
2 Enter your user name and password, and click OK.

The default user name is MANAGER, with a password of PASSWORD.
You should change the default password to prevent unauthorized users from accessing
the Enhanced Diagnostic Monitor. For information on changing the default user
information, see Managing User Accounts on page 9.

Creating and Managing Users

This section explains how to manage user access to Enhanced Diagnostic Monitor operations.
Access is based on the security level assigned to the user, from the highest level (01) to the lowest
level (10).
Each level of security includes default settings for the operation privileges allowed for that level.
For example, the Site Manager level (02) includes privileges for operations associated with
adding and removing Enhanced Diagnostic Monitor users.
When the Enhanced Diagnostic Monitor is installed, a default level 01 user (MANAGER) and
password (PASSWORD) are created. To ensure unauthorized users do not access the
application, you should change the default level 01 user password, and create additional user
names and passwords before creating network configurations.
Note If you forget the password for your level 01 user, contact Triconex Customer Support for
assistance. For contact information, see Technical Support on page vi.
You cannot make changes to user accounts or access levels while a node is open, even if it is not
connected.
Topics include:
• Managing User Accounts on page 9
• Adding and Modifying User Accounts on page 10
• Changing the Security Level for Privileges on page 11
• Changing Security Level Names on page 14
• Other Permissions Affecting User Access on page 15

Managing User Accounts

This procedure explains how to manage user accounts, which includes creating, modifying, and
deleting an Enhanced Diagnostic Monitor user. Only users assigned to security levels 01, 02, or
03 can access the Permissions dialog box and view user access settings.
You also must have Add/Modify User privileges to add, modify, or delete user accounts. For
more information about privileges, see Changing the Security Level for Privileges on page 11.
Procedure
1 Make sure that all network node connections are closed.
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.
3 Perform one of these actions on the Users tab.
Command Action
New To create a new user, click New. For further instructions, see Adding and
Modifying User Accounts on page 10.
Modify To change a user’s information, select a user in the list, and then click Modify.
For instructions, see Adding and Modifying User Accounts on page 10.
Delete To delete a user, select a user in the list, and then click Delete.
The default level 01 user (MANAGER) can be deleted only if another level 01
user has already been created.
Note Unless you have level 01 access, you cannot add or delete users who have the same or
higher security level as yourself. For example, if you have level 02 access, you cannot
add or delete users with level 02 or 01 access, including yourself.
If you have security level 01 access, you can add or delete other level 01 users, but you
cannot delete yourself.

Adding and Modifying User Accounts

This procedure explains how to add or modify Enhanced Diagnostic Monitor user accounts,
including changing user IDs or passwords.
Procedure
• To add a user, click Add.
• To modify a user, click the user name, and then click Modify.
4 Specify these properties in the Modify User dialog box.
Property Action
Full Name Enter or change the name for the user.
Description Enter or change the description for the user.
Logon Name Enter or change the ID to be used to log on to the Enhanced Diagnostic
Monitor.
Password Enter or change the logon password.
Verify Password Enter the new or changed password again for verification.
Security Level Select the security level for this user. Level 01 is the highest; level 10 is
the lowest.
If you do not set the user’s security level to 01 when you first create the user,
you will not be able to modify the user to give him or her level 01 access
in the future. If you want to increase an existing user’s level to 01, you
must first delete the existing user and then create a new user.

Note Even if you are not changing the password, you must enter a password in the
Password and Verify Password fields to confirm the other changes to the user’s
information.
You should enter the user’s existing password in these fields. If you don’t know
the user’s password, you can enter a new password in these fields; just be sure to
tell the user their new password.
5 Click OK to save your changes.
Changing the Security Level for Privileges

This procedure explains how to change the security level required for privileges to Enhanced
Diagnostic Monitor operations. Each operation can be assigned one or more security levels,
from the highest level (01), to the lowest level (10).
Each security level includes a set of privileges for that level, which also includes the privileges
for lower levels. For example, if the operation is set to level 04, users with level 01, 02, and 03
privileges also have access to the operation.
Only users with level 01, 02, or 03 access (and that have also been assigned the Security: Change
level privileges privilege) can change security level privileges.
Enhanced Diagnostic Monitor privileges include the following:
Default
Privilege Description
Security Levels
Module: Allows the user to clear faults on a module, if they also Levels 01—05
Clear faults have read/write permissions to the module. Applies to
both Tricon and Trident controllers.
Note: Under normal operation, faults are cleared
automatically when the problem causing the fault
is fixed. The Clear Faults command should be used
only in rare circumstances when a fault is not
automatically cleared. As a result, permission to
use this command should be granted only when
needed.
For more information, see Clearing Faults on All Modules
on page 35.
Module: Allows the user to collect system events when connected Levels 01—05
Log system events to a node (controller). Applies to both Tricon and Trident
controllers.
For more information, see Collecting and Viewing Tricon
System Events on page 48 or Collecting Trident System
Events on page 64.

Default
Privilege Description
Security Levels
Security: Allows the user to perform the following user Levels 01—02
Add/modify users management functions:
• Create new users
• Modify existing users
• Delete existing users
• Change user passwords
Even if a user has this privilege, he or she must also have
a security level of 03 or higher to access the Permissions
dialog box.
Also, unless he or she is a level 01 user, a user can only
create, modify, or delete users at a lower security level
than their own.
Security: Change Allows the user to change the security level descriptions. Levels 01—02
level descriptions For example, changing the description of level 05 from
Project Programmer to Software Programmer.
Even if a user has this privilege, he or she must also have
a security level of 03 or higher to access the Permissions
dialog box.
Security: Change Allows the user to assign privileges to security levels. Levels 01—02
level privileges (For example, assigning level 03 users the add/modify
users privilege.)
Even if a user has this privilege, he or she must have a
security level of 03 or higher to access the Permissions
dialog box.
Note If a TCM is installed in the Tricon, access to the controller via the Enhanced Diagnostic
Monitor (using the TriStation protocol) can also be managed by the Port Write Enabled
property or the optional TCM client access list.
For example, even if a user has the correct security level privileges to perform a Clear All
Faults command, if they do not have Read/Write TriStation access through the TCM,
they will be unable to perform the command. For more information, see the TriStation
1131 Developer’s Guide.

Procedure
3 Click the Privileges tab.
4 Click the operation(s) whose security level you want to change.

• Press Shift and click to select multiple contiguous items.
• Press Ctrl and click to select multiple non-contiguous items.
5 Select the check box for the level of security to be assigned to the selected operation(s).
Note Because they cannot access the Permissions dialog box, users with security levels 04–10
cannot perform the following tasks: Security: Add/modify users, Security: Change level
descriptions, Security: Change level privileges.
Additionally, you cannot remove privileges from your own security level. For example, if
you are a level 03 user, you cannot remove privileges from security level 03.

Changing Security Level Names

This procedure explains how to change the names associated with security levels. If you change
a name on this tab, it is reflected on the other security tabs. Changing the name does not affect
the security level assignments.
Only users with level 01, 02, or 03 access can change security level names, as only these levels
can open the Permissions dialog box.
Procedure
3 Click the Level Names tab.
4 Enter the name to associate with each security level.

The default names are as follows:
Level Name Level Name

01 Corporate Manager 06 Maintenance Manager
02 Site Manager 07 Maintenance Engineer
03 Project Manager 08 Operations Manager
04 Project Engineer 09 Operator
05 Project Programmer 10 Level 10

Other Permissions Affecting User Access

In addition to the Enhanced Diagnostic Monitor’s access controls, the following items can affect
user access to Enhanced Diagnostic Monitor application files, and the ability to connect to a
controller and perform selected commands.
• If a network configuration file or event log file was created by a user with restricted or
administrator-level rights in Windows, other users may be unable to access that file.
Windows security file access rules apply to all Enhanced Diagnostic Monitor
application files.
Your network or system administrator can assist with changing the access rights for the
selected configuration file and/or file location.
• If you have a model 4351A or 4352A Tricon Communication Module (TCM) installed in
your Tricon system, access to the Tricon via the Enhanced Diagnostic Monitor (using
the TriStation protocol) can also be controlled by the Port Write Enabled property or the
optional TCM client access list.
For example, even if a user has the correct security level privileges to perform a Clear All
Faults command, if they do not have Read/Write TriStation access through the TCM,
they will be unable to perform the command.
For more information on configuring the TCM client access list, or enabling/disabling
the Port Write Enabled property, see the TriStation 1131 Developer’s Guide.

Setting Up a Network Configuration

A network configuration is an XML file which includes the Tricon and Trident controllers you
want to monitor. You can create network configurations for Ethernet networks, and for serial
links (for Tricon). You can add controllers (nodes) to a network configuration, and edit their
properties as often as needed. To begin monitoring controllers, you must connect the diagnostic
PC to the network and add each controller node to the network configuration.
This section describes how to configure a network connection. Topics include:
• Types of Network Configurations on page 16
• Creating or Changing a Network Configuration on page 18
• Opening a Network Node on page 20
Types of Network Configurations

A network configuration can include Tricon and/or Trident controllers on Ethernet networks,
and Tricon controllers on serial links.
Ethernet Network
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.
This figure shows a typical network of Triconex controllers which can be specified in a network
configuration for diagnostic monitoring.
Tricon Controller Trident Controller Tricon Controller

CM
PASS
PASS
PASS PASS PASS FAULT PASS PASS PASS FAULT
FAULT FAULT FAULT ACTIVE FAULT FAULT FAULT ACTIVE
NET 1
ACTIVE ACTIVE ACTIVE FIRM ACTIVE ACTIVE ACTIVE FIRM
115/230 VAC MAINT1 MAINT1

115/230 VAC
MAINT1 MAINT1 MAINT1 MAINT1
NET 1
MAINT2 MAINT2 NET 1
MAINT2 MAINT2 MAINT2 MAINT2
LINK
LINK
TX RX
TX RX
PASS
PASS
MP MP MP MP MP MP
NET 2
FAULT
NET 2
FAULT
ALARM C C C NET 2
ALARM C C C
TEMP LINK
TEMP NET 2
LINK
TX RX
BATT LOW BATT LOW TX RX
TS/TSAA TS/TSAA TS/TSAA TS/TSAA TS/TSAA TS/TSAA
(TCM) (TCM)
EF01 EF01 EF01 EF01 EF01 EF01
ABCD
ABCD
ABCD
ABCD
ABCD
ABCD
23
23
23
23
23
SERIAL 1
23
SERIAL 1
TX RX TX RX
NODE NODE NODE NODE NODE NODE
ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS
EF01 EF01 EF01 EF01 EF01 EF01
ABCD
ABCD
ABCD
ABCD
ABCD
ABCD
23
23
23
23
23
23
LINK LINK LINK LINK LINK LINK
TX TX TX TX TX TX
POWER MODULE RX RX RX SERIAL 2 POWER MODULE RX RX SERIAL 2

TX RX RX TX RX
MODEL 8310 MODEL 8310
NETWORK NETWORK NETWORK NETWORK NETWORK NETWORK

TX TX TX TX TX TX
RX RX RX RX RX RX
115/230 VAC 115/230 VAC
SERIAL 3 SERIAL 3
TX RX TX RX
PASS PASS
FAULT SERIAL SERIAL SERIAL FAULT SERIAL SERIAL SERIAL
ALARM COM TX COM TX COM TX

ALARM COM TX COM TX COM TX
COM RX COM RX
TEMP
COM RX
SERIAL 4
TEMP COM RX COM RX COM RX
SERIAL 4
TX RX TX RX
I/O TX I/O TX I/O TX I/O TX
BATT LOW BATT LOW I/O TX I/O TX
I/O RX I/O RX I/O RX I/O RX I/O RX I/O RX
DEBUG DEBUG
MP MP MP MP MP MP
3008 TCM TCM
POWER MODULE 3008 3008 POWER MODULE 3008 3008 3008
4351 4351
MODEL 8310 MODEL 8310
MP
Ethernet Network
To DCS
Diagnostic PC SOE PC OPC Server
Figure 1 Typical Configuration of Triconex Controllers on Ethernet Network

Serial Links
For Tricon, a network configuration can include controllers on serial links which use Modbus
communication. This figure shows Tricon controllers on a typical multi-point serial link.
Tricon Controller Tricon Controller
PASS PASS PASS

PASS
PASS PASS FAULT PASS PASS PASS FAULT

PASS FAULT FAULT
FAULT FAULT ACTIVE FAULT FAULT FAULT ACTIVE

FAULT ACTIVE ACTIVE
ACTIVE ACTIVE FIRM ACTIVE ACTIVE ACTIVE

ACTIVE FIRM FIRM FIRM
MAINT1 MAINT1 MAINT1 MAINT1 MAINT1

MAINT1
MAINT2 NET 1 NET 1 NET 1
MAINT2 NET 1 MAINT2 MAINT2 MAINT2
MAINT2 LINK
LINK LINK LINK
TX RX TX RX TX RX
TX RX
MP MP MP MP
C C C NET 2
C NET 2 NET 2
NET 2
LINK LINK
LINK LINK
TX RX TX RX
TX RX TX RX
To DCS
TS/TSAA
EF01
TS/TSAA
EF01
TS/TSAA
EF01
TS/TSAA
EF01
TS/TSAA
EF01
TS/TSAA
EF01
To DCS
ABCD
ABCD
ABCD
ABCD
ABCD
ABCD
23
23
23
23
23
23
SERIAL 1
SERIAL 1 SERIAL 1 SERIAL 1
TX RX
TX RX TX RX TX RX
NODE NODE
NODE NODE NODE NODE
ADDRESS ADDRESS
ADDRESS ADDRESS ADDRESS ADDRESS
EF01 EF01
EF01 EF01 EF01 EF01
ABCD
ABCD
ABCD
ABCD
ABCD
ABCD
23
23
23
23
23
23
LINK LINK LINK LINK LINK

LINK
TX TX TX TX TX
TX
RX SERIAL 2 RX
RX RX SERIAL 2 RX RX SERIAL 2 SERIAL 2
TX RX
TX RX TX RX TX RX
NETWORK NETWORK NETWORK NETWORK NETWORK

NETWORK
TX TX TX TX TX
TX
RX RX RX RX RX
RX
SERIAL 3
SERIAL 3 SERIAL 3 SERIAL 3
TX RX
TX RX TX RX TX RX
Serial Cable Serial Cable

SERIAL SERIAL SERIAL SERIAL SERIAL
SERIAL
COM TX COM TX COM TX COM TX COM TX

COM TX
COM RX COM RX COM RX COM RX COM RX

COM RX SERIAL 4
SERIAL 4 TX RX SERIAL 4 SERIAL 4
I/O TX TX RX I/O TX TX RX TX RX
I/O TX I/O TX I/O TX I/O TX
I/O RX I/O RX I/O RX I/O RX I/O RX

I/O RX
DEBUG
DEBUG
DEBUG DEBUG
MP MP MP MP MP MP
TCM TCM
3008 3008 3008 3008 3008 3008 TCM TCM
4351 4351
4351 4351
TCMs TCMs
Diagnostic PC
Figure 2 Typical Multi-Point Serial Network with Tricon Controllers
Notes When connecting the diagnostic PC to a Tricon Communication Module (TCM) via a
serial cable, you must connect the serial cable to Serial Port 4 on the TCM. This is the only
port enabled for serial communication via the TriStation protocol (used by Enhanced
Diagnostic Monitor).
For more detailed information and instructions on installing and configuring your
Triconex controller on a network, please see the appropriate Communication Guide for
your controller.
You cannot collect Tricon system events when the diagnostic PC is connected to the
controller via a serial link. For more information on collecting Tricon events, see
Collecting and Viewing Tricon System Events on page 48.

Creating or Changing a Network Configuration

This procedure explains how to create or change a network configuration of controllers. Before
you begin, gather the following information 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 (serial or network)
Each of these values can be found on the TriStation 1131 Communication screen. For more
detailed information, see the TriStation 1131 Developer’s Guide.
You cannot create a new network configuration, or open an existing network configuration, if a
network configuration is already open in the Enhanced Diagnostic Monitor.
Note A maximum of 31 nodes can be added to a network configuration. If 31 nodes already
exist in the configuration, you must delete a node before you can add a new node. To do
so, right-click the node you want to delete, and then click Delete.
Procedure
1 Verify that a network configuration is not currently open.
2 On the File menu, click New Network Configuration or Open Network Configuration.
The Network Nodes tree opens in the left pane.
3 Do either of these:
• To add a node, right-click Network Nodes at the top of the tree, and then click Add.
• To edit a node, right-click the node name on the tree, and then click Edit.
The Network Node Configuration dialog box appears.
4 Specify these properties in the Network Node Configuration dialog box.

These settings must match the settings on the TriStation 1131 Communication screen for
the application running in the controller.

Property Action
Controller Type Select Tricon or Trident.
Node Number Enter the node number of the controller.
Node Name Enter the node name of the controller.
Connection Type For Tricon, select one of these options:
• Network for an Ethernet (TCP/IP) connection
• Serial for a serial (Modbus) connection
For Trident, select one of these options:
• Main Processor for an Ethernet (DLC) connection
• Network for an Ethernet (TCP/IP) connection
IP Address For a Tricon serial connection, specify the IP address of the controller to
be monitored.
Serial Port For a Tricon serial connection, select the COM port on the diagnostic PC
which is connected to the controller.
MP Connection For a Trident Main Processor connection, select the main processor
which is connected to the diagnostic PC.
NIC Index For a Trident Main Processor connection, enter the index position of the
network interface card in the diagnostic PC.

6 Repeat steps 3–5 for each node you want to add or change.
7 On the File menu, click Save Network Configuration to save the XML file to the same
name and destination (to replace an existing configuration).
You can also save the file to a new name and destination by using the Save Network
Configuration As command on the File menu.

Opening a Network Node

This procedure explains how to open and connect to a node in a network configuration. You
must open a node before you can view diagnostic information and collect system events.
You can open and connect to multiple nodes at one time; however, you can collect Tricon system
events only from one node at a time. For more information, see Collecting and Viewing Tricon
System Events on page 48.
Before you begin, the diagnostic PC 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 (see Creating or Changing a Network Configuration on page 18).
Procedure
1 If a network configuration is not already open, on the File menu, click Open Network
Configuration.
2 Double-click the name of a node in the tree.
The node opens automatically, or requests a password if one was specified for the
application running on the controller.
3 If a password is requested, do one of the following:

• Enter the correct password, and click OK. If you don’t enter the correct password
after five attempts, you will be disconnected from the node.
• Click Ignore to connect to the node in read-only mode. For more information about
this mode, see Connecting in Read-Only Mode on page 21.
• Click Cancel to disconnect from the node.

Connecting in Read-Only Mode

A network node will connect in read-only mode under any of the following conditions:
• You enter a password that does not match the one specified for the application running
in the controller.
• You click Ignore in the Enter Password dialog box when prompted for the application
password.
• A TCM is installed in the Tricon and the TCM client access list has been enabled and
configured so that the IP address of the diagnostic PC has read-only access via the
TriStation protocol. For more information, see the TriStation 1131 Developer’s Guide.
• A TCM is installed in the Tricon and the Port Write Enabled property has been disabled
for the network port the diagnostic PC is connected to. For more information, see the
TriStation 1131 Developer’s Guide.
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 Tricon and Trident system events
• Viewing existing Tricon event log files
• Clearing module faults
Note When connected in read-only mode due to a TCM client access list permission (read-
only access via the TriStation protocol), you are allowed to collect system events for a
Tricon node. However, if the node is password-protected, you still must know the
correct password in order to collect events.
Troubleshooting Connection Problems

The following are common problems you may encounter while trying to connect to a node.
Problem Solution
You cannot connect to a node. Right-click the node name in the tree, and then click Edit in
the shortcut menu that appears. Examine the properties in the
Network Node Configuration dialog box, change any that are
incorrect, and then attempt to open the node again.
You cannot connect to a Tricon Verify in TriStation 1131 that the IP address of the diagnostic
node that has a TCM installed. PC has read-only or read/write access to the TCM via the
TriStation protocol.
If the TCM client access list has been configured so that the IP
address of the diagnostic PC is denied access to the TCM via
the TriStation protocol, you will be unable to open the node.
For more information, see the TriStation 1131 Developer’s
Guide.
You cannot connect to a Trident If the diagnostic PC is running Windows XP, you must install
node when Main Processor is the DLC protocol to be able to connect to a Trident MP. For
selected as the connection type. instructions, see Installing the DLC Protocol on the Diagnostic
PC on page 5.

Setting the Connection Retry Limit – Tricon Only

If a connection to a Tricon node is lost (for example, due to communication or hardware
problems), the Enhanced Diagnostic Monitor will automatically attempt to restore the connection.
You can control how many automatic attempts will be made to restore the lost connection. The
connection retry limit applies to all Tricon nodes in the network configuration.
You can also manually attempt to restore the connection by double-clicking the node name on
the tree again to re-open the node.
Procedure
1 In the Network Configuration tree, double-click the node you want to monitor.
You do not have to be actively connected to the controller, but the node must be open.
2 On the Tools menu, select Communication Options.
3 Select one of these properties:
Property Action
Unlimited Select this if you want the Enhanced Diagnostic Monitor to continue
trying to restore the connection indefinitely, until the connection is
successfully restored.
This is the default selection.
Limited Select this if you want the Enhanced Diagnostic Monitor to attempt to
restore the connection only for a pre-determined number of times,
regardless of whether the connection is restored.
Enter the number of connection attempts that should be made.
4 Click OK to save your changes and close the dialog box.

2
Monitoring Controller Hardware
Overview 24
System Overview and Module Status Windows 25
Understanding External Faults 31
Understanding Internal Faults 33
Clearing Faults on All Modules 35
Monitoring Output Voter Diagnostics (OVD) 36
Displaying Firmware Versions 37

24 Chapter 2 Monitoring Controller Hardware
Overview
The Enhanced Diagnostic Monitor allows you to identify alarms on Tricon chassis and Trident
IOPs, and faults on power supplies, modules, and points.
You can also monitor the OVD status of Tricon 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), see the maintenance guidelines
in the appropriate Planning and Installation Guide for your controller.

System Overview and Module Status Windows

For each controller, the Enhanced Diagnostic Monitor includes a System Overview window, and
a module configuration window called the Module Status window. Multiple System Overview
and/or Module Status windows can be open at once if you are connected to multiple nodes.
Tricon System Overview Window

The Tricon System Overview window displays an icon for each chassis in the configuration.
Healthy chassis are green; chassis that contain modules with faults are red.
Green icon for

chassis with
alarm off
Red icon for

chassis with
alarm on
System
Overview Tree
for selecting
full chassis
display
Selecting a Window Position

The System Overview window can be a floating window (as shown above), or it can be docked
and expanded within the Enhanced Diagnostic Monitor workspace (as shown on page 24). If
you only have one System Overview window open, you may want to dock the window to
increase its size and see more of the window at once.
• To dock the System Overview window, in the upper right corner of the window, click the
button. The window expands to fill the Enhanced Diagnostic Monitor workspace.
• To undock the System Overview window (make it a floating window), in the upper
right corner of the window, click the button.

Tricon Module Status Window

The Module Status window, accessible by clicking on a chassis in the System Overview tree,
shows the configuration and status of modules in a chassis.
The Module Status window—like the System Overview window—can be a floating window or
a docked window. For more information, see Selecting a Window Position on page 25.
Tricon Module Colors

The Module Status window uses these colors to represent the current state of each module.
Color Meaning
Yellow Module installed in the slot is not configured in the application currently running on
the controller. (Only displayed if a Download All is performed after a module is
installed.)
Blue Spare module is not installed in the slot.
Red Module configured in the application currently running on the controller is not
installed in the slot.
The module/slot colors are also described on the Legend tab of the Module Status dialog box
for each module.

Tricon Module Indicator Behavior

Module indicators in the Module Status window behave the same as module indicators on the
controller, with these exceptions:
• During power-up of a controller, the indicators in the Module Status window are Off
(gray).
• Blinking indicators blink more slowly in the Module Status window.
• Indicators that are blinking very quickly may appear static in the Module Status
window.
Tricon Module Status Dialog Box

For each module in a Tricon controller (including the power supplies and Main Processor
modules), the Module Status dialog box displays information about faults.
To open the Module Status dialog box, double-click on any module in the Module Status
window.
Tabs Description
Field Faults Displays load or fuse faults related to field inputs, terminations, wiring, or devices.
(Field faults are not applicable to Main Processors.)
Power Faults Displays faults related to missing field loads (power) or blown fuses; or power
problems which are internal to the controller.
Voter Faults Displays faults in the OVD (Output Voter Diagnostic) circuitry of a digital output
module.
Legend Describes what the colors mean for the slot and LED indicators.

Fault Information Areas

Each Module Status dialog box includes an area for the left module and the right module in a
slot. The module areas have properties which provide information about faults.
Property Description
Status Displays a message that describes the type of fault.
Point Faults Displays the number of each point with a fault condition.
Trident System Overview Window

The Trident System Overview window displays an icon for each IOP (input/output processor)
in the configuration. Healthy IOPs are green; IOPs with modules that have faults are red.
Tree for Red icon for IOP

selecting full with alarm on
IOP display
Trident Module Status Window

The Module Status window, accessible by clicking an IOP in the System Overview tree, shows
the setup of modules in an IOP.

Changing the Trident Module Status Window View

This procedure explains how to change the view of the modules in a Trident Module Status
window.
Procedure
1 Expand the System Overview tree and click a module to display the Module Status
window.
2 On the View menu, click Zoom, and then do one of the following:
• Click 200, 100, 75, or 50 percent.
• Click Custom, and then enter the desired percentage.
3 Click Zoom to Fit to size the elements to the window.
Trident Module Colors

The Module Status window uses these colors to represent the current state of each module.
Module 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/slot colors are also described on the Legend tab of the Module Status dialog box
for each module.
Trident Module Indicator Behavior

Module indicators in the Module Status window behave the same as module indicators on the
controller, with these exceptions:
• During power-up of a controller, the indicators in the Module Status window are Off
(gray).
• Blinking indicators blink more slowly in the Module Status window.
• Indicators that are blinking very quickly may appear static in the Module Status
window.

Trident Module Status Dialog Box

For an I/O or communication module, the Module Status dialog box includes Left and Right
Module tabs.
For the main processors, the Module Status dialog box includes Left, Middle, and Right Module
tabs.
Each tab in a Module Status dialog box provides the following information about faults.
Option Description
Current Faults Displays the current faults on a module, which can include internal faults and field
faults (external faults).
Fault History Displays all faults that have occurred during this session.
Field Faults Displays load or fuse faults related to field inputs, terminations, wiring, or devices.
(Field faults do not apply to main processors.)

Understanding External Faults 31
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 these indicators:
• For Tricon, the LOAD/FUSE indicator (if available) on the affected module turns
yellow.
• For Trident, the FIELD POWER indicator 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 in the Module Status dialog
box and examine the field inputs, field power supplies, terminations, wiring, and connected
devices.
A controller is subject to the following types of external faults.
Fault Type Description

Field Fault on Digital A load or fuse problem related to field terminations on the controller,
Output Point field wiring, or field devices.
Field Fault on Input Point A faulty power supply.
Power Fault For Tricon, a power fault refers to one of these conditions:
• The field load (power) for a point is missing.
• A point has a blown fuse.
• One of the power supplies is turned off.
For Trident, a power fault refers to the field power supplies that 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, or connected devices.
For detailed information about faults and module indicators, see the appropriate Planning and
Installation Guide for your controller.

Locating and Correcting External Faults

This procedure explains how to locate and correct external faults on a module. Before you begin,
the diagnostic PC must be connected to the network, and the node being monitored must be
open. For instructions, see Opening a Network Node on page 20.
For detailed information about fault conditions, see the appropriate Planning and Installation
Guide for your controller.
Procedure
1 In the System Overview tree, click System Overview to view the chassis or IOP alarm
icons.
2 If an alarm is on (red), open the Module Status window, and then double-click a module
with a yellow indicator.
3 In the Module Status dialog box, click these tabs to locate the fault details:
• For Tricon, click the Field Faults and Power Faults tabs.
• For Trident, on the Left Module and Right Module tabs, click the Current Faults
and Field Faults settings.
4 Examine the relevant field inputs, power supplies, terminations, wiring, and connected
devices, and then repair the faulty items.

Understanding Internal Faults 33
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, see the appropriate Planning and Installation Guide for your controller.
If you replace a module and the Fault indicator immediately turns red, you should read the
diagnostic messages in the Module Status dialog box 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 module with the fault,
which means 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 the following types of internal faults.
Fault Type Description

Minor A fault that is usually transient in nature and has no impact on system operation. An
example is a CRC error in one message. (Does not cause the Fault indicator to turn red.)
Major 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.
Voter 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.
Fatal 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 Internal Faults

This procedure explains how to locate internal faults on a module. Before you begin, the
diagnostic PC must be connected to the network, and the node being monitored must be open.
For detailed information about fault conditions, see the appropriate Planning and Installation
Procedure
1 In the System Overview tree, click System Overview to view the chassis or IOP alarm
icons.
2 If an alarm is on (red), open the Module Status window, and then double-click a module
with a red indicator.
3 In the Module Status dialog box, click these tabs to find the fault messages:
• For Tricon, click the Voter Faults tab.
• For Trident, on the Left Module and Right Module tabs, click the Current Faults
setting.

Clearing Faults on All Modules 35
Clearing Faults on All Modules

This procedure explains how to clear the faults on all modules in a controller. Before clearing
faults, you should identify the causes of the faults and correct them.
You must have read/write access to the controller to clear faults. If you are connected in read-
only mode (see Connecting in Read-Only Mode on page 21), you cannot clear faults.
Note If the Clear Faults on All Modules command is unavailable when connected to a Tricon
node that has a TCM installed, verify in TriStation 1131 that the IP address of the
diagnostic PC has read/write access to the TCM via the TriStation protocol.
If the TCM client access list has been configured so that the IP address of the diagnostic
PC has read-only access to the TCM via the TriStation protocol, you will be unable to
clear all faults. For more information, see the TriStation 1131 Developer’s Guide.
Normally, a fault is cleared automatically when the problem causing the

WARNING fault has been repaired, and there is no need to use the Clear Faults on All
Modules command. However, in rare circumstances the LED indicators
may show faults when there are no actual faults to repair. This is the only
situation in which you should use the Clear Faults on All Modules
command.
Clearing faults is a write operation, and can change the behavior of the
controller.
If you are in doubt about whether or not you should use this command,
please contact the Triconex Customer Satisfaction Center for assistance.
For contact information, see Technical Support on page vi.
Procedure
1 Ensure that all faults have been identified and corrected, as described in Locating and
Correcting External Faults on page 32 and Locating Internal Faults on page 34.
2 On the Commands menu, click Clear Faults on All Modules.
The Tricon chassis or Trident IOP alarm turns off (green), and the Fault indicators on the
modules with faults turn off (gray).

Monitoring Output Voter Diagnostics (OVD)

This section explains how to monitor the OVD status of digital output (DO) 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.
Note You cannot monitor the OVD status of DO points in the Trident using the Enhanced
Diagnostic Monitor. 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. For instructions, see the TriStation 1131 Libraries Reference and the TriStation
1131 Developer’s Guide.
Procedure for Tricon

1 On the System Overview tree, click a chassis.
2 In the Module Status window, view the OVD labels underneath the status indicators on
DO modules.
A green label means OVD is on for all points on the module. A yellow label means OVD
is off for all points on the module.
OVD Status
Green
Label
Yellow
Changing the OVD State

To change the OVD state, you must use commands in the Controller Panel of TriStation 1131 for
the downloaded application. For instructions, see the TriStation 1131 Developer’s Guide.

Displaying Firmware Versions 37
Displaying Firmware Versions

This procedure explains how to display the firmware version numbers of all modules in a
Tricon chassis or Trident IOP. Typically, you only need to know the firmware version numbers
when requested by a Triconex Technical Support Engineer for diagnostic purposes.
• 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.
For more information about the Messages pane, see Viewing Data in the Messages Pane
on page 45.
• 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.


3
Monitoring Controller Status
Overview 40
Viewing Controller Status 41
Monitoring and Changing the Scan Time 42
Monitoring and Changing the Memory Allocation 43
Refreshing Controller Status 44
Viewing Data in the Messages Pane 45
Viewing Program Execution Times 47
Collecting and Viewing Tricon System Events 48
Collecting Trident System Events 64

40 Chapter 3 Monitoring Controller Status
Overview
Controller status is monitored via the System Overview screen. Before you can monitor
controller status, you must complete these steps:
• Connect the diagnostic PC to the network. See Types of Network Configurations on
page 16.
• Create a network configuration which includes node specifications for the controllers
you want to monitor, or open an existing network configuration. See Setting Up a
Network Configuration on page 16.
• Open the nodes you want to monitor. See Opening a Network Node on page 20.
Note You can also access controller performance and project information using function
blocks in the TriStation 1131 standard libraries, and for Trident, using system attributes.
For more information, see the TriStation 1131 Libraries Reference.

Viewing Controller Status 41
Viewing Controller Status

This procedure explains how to view controller status in the System Overview window.
Procedure
1 Connect to the node (controller) you want to monitor.
2 In the System Overview tree, click System Overview.
3 View the performance and project information for the controller in the right pane.
Property Action
Project Displays the name and version number of the project (application)
currently running on the controller.
Calendar Displays the current time of the controller being monitored in the
day/date/hour/minute/second format.
Poll Time Displays the maximum time needed by the controller to obtain data
from the input modules.
Ensure the poll time does not exceed the scan time (see Monitoring
and Changing the Scan Time on page 42).
Maximum Memory Displays the maximum amount of memory the controller originally
made available to the TriStation project.
Free Memory Displays the amount of memory available for project expansion.
Key Stop/Position For Tricon, Key Stop indicates whether the STOP position on the
keyswitch is logically enabled or disabled for security purposes.
Position indicates the current physical setting of the keyswitch.
Status Displays the current state of the project running on the controller.
Scan Request/Actual Displays the requested scan time and the actual scan time.
Scan Surplus Displays the time that remains in a scan after the control functions
are completed.
To avoid communication errors, ensure the scan surplus is positive.

Monitoring and Changing the Scan Time

This procedure explains how to monitor the scan time in the System Overview window, and
then change the scan time using TriStation 1131.
Procedure
3 In the right pane, view these properties, which are related to the scan time.
Property Action
Poll Time Displays the maximum time needed by the controller to obtain data
You should ensure the poll time does not exceed the scan time.
Scan Request/Actual Displays the requested scan time and the actual scan time.
Scan Surplus Displays the time that remains in a scan after the control functions
are completed.
To avoid communication errors, ensure the scan surplus is positive.
4 If the poll time exceeds the scan time, or if the scan surplus is negative, use TriStation
1131 to adjust the scan time.
Changing the Scan Time Using TriStation 1131

Changes to the scan time must be made in the TriStation 1131 project. This procedure explains
how to set the scan time for a downloaded application running in the controller. For more
detailed information about determining the correct scan time and scan surplus, see the
TriStation 1131 Developer’s Guide.
Procedure
1 In TriStation 1131, open the project running on the controller you are monitoring.
2 On the Controller tree, double-click Controller Panel and then connect to the controller.
3 On the Commands menu, click Set Scan Time.
4 In the Set Scan Time dialog box, enter the scan time in milliseconds. The number must
be within the minimum to maximum range.
• For Tricon 3006/3007, the range is 20 to 500 milliseconds.
• For Tricon 3008, the range is 16 to 450 milliseconds.
• For Trident, the range is 18 to 450 milliseconds. The minimum must be equal to or
larger than the poll times.
Note To guarantee that the controller provides a predictable response time, the scan
time should always be set to a value greater than the I/O poll time (the
maximum time needed by the controller to obtain data from the input modules).

Monitoring and Changing the Memory Allocation 43
Monitoring and Changing the Memory Allocation

This procedure explains how to monitor the memory allocation of a controller in the System
Overview window, and then change the memory allocation using TriStation 1131.
Procedure
3 In the right pane, view these properties, which are related to memory allocation.
Property Action
Maximum Memory Displays the maximum amount of memory that the controller
originally made available to the TriStation project.
Free Memory Displays the amount of memory available for project expansion.
4 If you plan to make changes to the project that require more memory, use TriStation 1131
to allocate more memory and then perform a Download All.
Changing the Memory Allocation Using TriStation 1131

This section explains how to allocate memory, which includes specifying the memory used for
input, output, and memory points in the application.
Initially, the amount of memory for input and output points is determined by the number and
type of I/O modules configured in the TriStation project. The amount of memory for memory
points is set when a TriStation project is created. You can change these allocations at any time.
After an application has been downloaded to a controller, changes to

CAUTION memory allocation require a Download All.
Procedure
1 In TriStation 1131, open the project currently running on the controller you are
monitoring.
2 Expand the Controller tree, double-click Configuration, and then expand Memory
Allocation.
3 Double-click the type of point you want to change.
4 In the Item Properties dialog box that appears, move the slider up or down to change the
memory allocated for the selected point.
5 Repeat for all points to be changed.
6 Rebuild the application and then perform a Download All to apply the memory
allocation changes. For detailed instructions, see the TriStation 1131 Developer’s Guide.

Refreshing Controller Status

This procedure explains how to refresh the System Overview and Module Status windows
while you are connected to and monitoring a controller. You can refresh the information
occasionally or continuously.
• To refresh the System Overview and Module Status windows once, on the Commands
menu, click Refresh Panel.
• To continuously refresh the System Overview and Module Status windows, on the
Commands menu, click Continuous Refresh.
The windows are continually refreshed until you disconnect from the node or click
Continuous Refresh again to clear your selection.
Note If you are connected to a Tricon node, a beep sounds once when a chassis alarm turns on.
Refreshing Controller Status During Tricon Event Collection

You cannot change the refresh setting while you are actively collecting Tricon system events.
During event collection, Enhanced Diagnostic Monitor automatically enables continuous
refreshing—even if you had previously disabled it—so that you continue to receive updated
module status information in the System Overview or Module Status window while events are
being collected. Once event collection is stopped, the refresh setting will revert to your original
setting.

Viewing Data in the Messages Pane 45
Viewing Data in the Messages Pane

The Messages pane displays information about diagnostic operations while you are connected
to a node.
To show or hide the Messages pane, on the View menu, click Messages.
Note System event information does not appear in the Messages pane. Event information is
displayed in the bottom pane of the System Overview or Module Status window. For
more information, see Collecting and Viewing Tricon System Events on page 48.
Managing Data in the Messages Pane

You can manage the data in the Messages pane through these commands, which are accessible
by right-clicking anywhere in the pane.
Command Name Operation

Copy Command Copies selected messages, and places them on the clipboard.
Cut Command Cuts selected messages, and places them on the clipboard,
while also removing the messages from the Messages pane.
Find Command Finds specified text.
Print Command Prints the contents to a specified printer.
Save As Command Saves messages in a text file (.log).
Clear All Command Clears all messages.
Select All Command Selects all text, in preparation for a Copy or Cut operation.
Show Line Numbers Command Shows the number of each line of text.
Typical Diagnostic Messages

These commands or errors report messages or results in the Messages pane.
Command Name / Error Message Description

Display Execution Times Command The execution time of each program in the application that is
running on the controller. See Viewing Program Execution
Times on page 47.
Display Firmware Versions The firmware version numbers of all modules in a Tricon
Command chassis or Trident IOP. See Displaying Firmware Versions on
page 37.

Command Name / Error Message Description

Error: Connection to Controller Lost The connection to the selected controller has been lost.
Provides the name of the node, and the date / time the
connection was lost. If applicable, also provides information
about the date / time the connection was restored. See
Troubleshooting Connection Problems on page 21.
Error: Event Log File Full, New Log The maximum number of events was reached in the existing
File Created Tricon event log file. A new file has been created. Provides
the name and location of the new file. See Max Events Per Log
File on page 76.
Error: Disk Space at 90% Capacity The hard drive that the Tricon event log file is located on has
10% or less free space remaining. Event collection stops until
free space is increased, or a new log file on a different drive is
created. See Maximum File Size on page 77.
Warning: Disk Space at 80% The hard drive that the Tricon event log file is located on, or
Capacity being created on, has 20% or less free space remaining. See
Maximum File Size on page 77.

Viewing Program Execution Times 47
Viewing Program Execution Times

This procedure explains how to view the execution time of each program in the application that
is running on a controller.
Program execution times are important when performing scan time calculations. For more
information about calculating scan time, see the TriStation 1131 Developer’s Guide.
The programs are identified as Program 0, Program 1, and so on. Program 0 and Program 1 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.
Note Due to system limitations, you cannot display the execution times of programs running
on a model 3006 Tricon controller.
Procedure
2 On the Commands menu, click Display Execution Times.
The execution time for each program displays in the Messages pane.
3 To copy, print, or save the program execution time information, right-click anywhere in
the Messages pane, and then select the desired command from the shortcut menu that
appears.
For more information, see Viewing Data in the Messages Pane on page 45.

Collecting and Viewing Tricon System Events

This procedure explains how to collect and view Tricon system diagnostic events. Collecting
events provides you with real-time information about a fault or other error that is occurring on
your Tricon. Event collection also provides you with a history of errors that you can send to
Customer Support for assistance in troubleshooting problems.
System events are displayed in the bottom half of the System Overview and Module Status
windows, in the Events pane. Events are also saved to Tricon event log files (.tce). Summary
information about the event log file currently being viewed is displayed in the Events Summary
pane.
Events
Summary
Pane
Events
Pane
Topics include:
• Interpreting Tricon System Events on page 49
• Opening the Events and Events Summary Panes on page 51
• Starting Event Collection on page 55
• Stopping Event Collection on page 56
• Changing the Default Event Collection Settings on page 56
• Filtering the Events List on page 58
• Modifying the Event Exclusion List on page 60
• Viewing an Existing Event Log File on page 61
• Exporting an Event Log File on page 62

Interpreting Tricon System Events

During event collection, all Tricon system events are saved to the event log file, regardless of any
filters that have been configured. However, only those events matching your currently applied
filters are displayed in the Events pane.
To assist in troubleshooting problems, events that are viewable only by Triconex Customer
Support personnel are also collected and saved in the event log file.
Events are color-coded according to their severity, as follows:
Color Severity Description

Blue Information Message is for informational purposes only.
Green Warning A problem or error that does not require immediate
action.
Pink Fault Important information about a system-level fault
that has occurred on the Tricon system.
Red Degraded A fatal error that has caused the Tricon to run in a
degraded (Duplex or Single) mode. Immediate
action should be taken to return the Tricon to TMR
mode.
The following information is provided for each event in the Events pane:
Event Date The date the event occurred, in mm/dd/yyyy format.
Event Time The time the event occurred, in hh/mm/ss:mls format, where
hh is hours (in the 24-hour format), mm is minutes, ss is seconds
and mls is milliseconds.
Class Indicates the system component (firmware) where the event
originated from. For example, class “ETSX” indicates the event
originated from the Main Processor.
Code The unique message identifier. Each class of messages has a set
of unique message codes.
Leg The main processor leg the event occurred on. A, B, or C.
Board The address of the board the event occurred on, in hexadecimal
format. For information about converting board addresses from
hexadecimal values to chassis/slot numbers, see Appendix B,
Converting Tricon Hexadecimal Board Addresses.
Message The event message text. Double-click the message text to view a
longer description of the event, if available.
Note Events are sorted by date and time; the sort order cannot be changed.

The following information is provided in the Events Summary pane:
Event Log Status The current status of the event log being displayed in the
Events pane. Possible values are:
• Collecting Diagnostics—Collecting diagnostic
information about the connected controller.
• Collecting Firmware—Collecting information about
the connected controller’s firmware versions. See
Displaying Firmware Versions on page 37.
• Collecting Events—Actively collecting events from a
connected controller.
• Viewing Events—Viewing events in a previously
saved event log file.
• No Log File Open—Events are not actively being
collected or viewed.
Collected At Node The node number of the controller the events being
displayed were collected from.
Event File Name The full path and file name for the event log file being
displayed.
Events Matching Filter The number of events in the current event log file that
match the current filter settings.
Total Events The total number of events in the event log file. This may
be greater than the number of events matching the filter.
Begin Event Time The date and time of the first event in the event log file.
End Event Time The date and time of the last event in the event log file.
Important Information About Event Retention

If you are connecting to the Tricon through a Model 4351A/4352A TCM, all system events are
retained in the TCM’s internal buffer until its maximum size is reached. When the buffer is full,
the oldest events are purged to make room for new events. As a result, some events are retained
even after they have been collected by the Enhanced Diagnostic Monitor. When you disconnect
and then reconnect to the controller, and start another event collection session, some of the
events that were collected previously will be collected again.
If you are connecting to the Tricon through another communication module, such as a Model
4351/4352 TCM, an NCM, or an EICM, however, events are not retained in a buffer. Once
collected, the events are purged from the system. When you disconnect and then reconnect to
the controller, and start another event collection session, none of the previously connected
events will be available.
In all cases, if there has been a loss of power to the system, all events will be lost, regardless of
which communication module is installed in the Tricon.

Opening the Events and Events Summary Panes

When you first connect to a node, the Events and Events Summary panes are not visible in the
System Overview window. You can control which panes are visible in the System Overview and
Module Status windows by using your mouse to resize the window panes.
To open the Events Pane:

1 Connect to the node (controller) you want to collect events for.
• Dock the window (see Selecting a Window Position on page 25).
• Resize the window by using the mouse pointer to click and drag the bottom edge of
the window down until you see the Events pane.
Drag this
bottom edge
down until
Events pane
appears.
To open the Events Summary Pane:

1 Connect to the node (controller) you want to collect events for.
2 Open the Events pane as described above.
3 Use the mouse pointer to click and drag the top edge of the Events pane down until you
see the Events Summary pane.

Drag this edge

up to decrease
the size of the
System
Overview
window.
Drag this top

edge down until
Events
Summary pane
appears.
Note Click and drag the bottom edge of the System Overview or Module Status window up
to decrease the size of the System Overview or Module Status window and provide a
larger viewing area for the Events and Events Summary panes.

Managing Tricon Event Log Files

During event collection, Tricon system events are saved to a Tricon event log file (.tce).
An event log file can be in one of the following states:
State Description Events Summary Pane View

Empty No event or system information has • Collected at Node field is blank.
been saved to the file. • Total Events field is blank.
Diagnostics Only system diagnostic information • Collected at Node field = 0
Only was saved to the file; event collection • Total Events field = 0
was stopped before events were saved.
Full System diagnostic information and • Collected at Node field = the node
events were saved to the file during events were collected for
event collection. • Total Events field = the number of
The maximum number of events may events in the file (could be 0 if no
or may not have been reached. events were collected or events in file
do not match filtering settings)
When you start event collection, one of the following occurs:

• If an Empty event log file is already open, event collection starts immediately, using the
currently open file.
• If an event log file that is in the Diagnostics Only or Full states is already open, you are
asked to create a new file.
• If no event log file is open, you are asked to create a new file.
Creating Tricon Event Log Files

When prompted for a new event log file, you can create a new file by entering a file name and
location. You can also browse to locate an already existing file. If the existing file you select is in
the Diagnostics Only or Full state, any system information or events already saved in the file
will be overwritten.
Due to Windows restrictions, we recommend limiting the total path for event log files to less
than 250 characters (including file name and extension). File names should be less than 240
characters. This allows for the creation of auto-generated files when the maximum number of
events in an event log file is reached.
Managing Event Log File Size

The Max Events Per Log File property controls the maximum number of events that are saved
to a single Tricon event log file during event collection. It also controls the maximum size of an
event log file.
A maximum of 500,000 events can be saved in a single log file; you can lower this amount in
increments of 10,000. The default is 500,000 events. For instructions on changing the maximum
number of events, see Changing the Default Event Collection Settings on page 56.

When an event log file reaches the maximum number of events during event collection,
Enhanced Diagnostic Monitor automatically saves the file and opens a new file in the same
directory with _newx appended to the file name (where x is a number representing the file
count).
For example, if the maximum number of events is reached while collecting events in the event
log file events.tce, Enhanced Diagnostic Monitor will automatically create a new file with the
name events_new1.tce, and continue event collection using the new file. If that file also reaches
its maximum size, the next automatically created file will be named events_new2.tce.
When a new event log file is created, the following occurs:
• A message providing the new file name appears in the Messages pane.
• The list of events in the Events pane is cleared, and only events being saved to the new
file are displayed. This keeps the event list view manageable. Events from the old file
may be viewed by opening the event log file for viewing.
Managing Free Disk Space for Event Log Files

During event collection, there must be an adequate amount of free disk space on the drive where
the event log file is located. A warning message will appear when 80% of disk capacity has been
reached. When 90% capacity is reached, event collection will stop. If this occurs, you will need to
restart event collection, using a new event log file located on a drive with adequate disk space.

Starting Event Collection

After you have connected to a node, event collection does not begin automatically. You must
manually start event collection.
Events can be collected for only one Tricon node at a time; you cannot collect events for multiple
Tricon nodes simultaneously. Module and chassis status information for all open nodes
continues to be updated while event collection is taking place on a selected node.
You can collect events simultaneously on one Tricon node and one or more Trident nodes.
However, event collection on multiple nodes will cause a reduction in performance. The
module statuses for all open nodes will not be updated as frequently, and overall event
collection will be significantly slower.
For more information about collecting Trident system events, see Collecting Trident System
Events on page 64.
Note If the connection to the controller is lost during event collection, and Enhanced
Diagnostic Monitor is able to automatically restore the connection, a new event log file
will be created when event collection resumes. For more information about
automatically restoring a connection, see Setting the Connection Retry Limit – Tricon
Only on page 22.
In most cases, you cannot collect events when connected in read-only mode. For more
information, see Connecting in Read-Only Mode on page 21.
To start event collection:

1 Connect to the node (controller) you want to collect events from.
Note You must be connected to the node via a network connection. You cannot collect
events when connected to a node via a serial connection. To change the
connection type, see Creating or Changing a Network Configuration on page 18.
2 On the Events menu, click Start Collecting Events.
• If an Empty event log file was already open, system event collection begins.
• If you are prompted to select a new event log file, go to the next step.
• Browse to locate the file you want to write events to, and then click Save. If you
select an existing file, any events already saved in the file will be overwritten.
• Create a new event log file by entering a file name and location, and then click Save.
System event collection begins.
During event collection, events matching your filtering options appear in the Events pane, and
are continuously updated until event collection is stopped. To change the current filtering
options, see Filtering the Events List on page 58 and Modifying the Event Exclusion List on
page 60.
If you’ve started collecting events, but you don’t see the events list in the System Overview or
Module Status window, you need to open the Events pane. See Opening the Events and Events
Summary Panes on page 51.

Stopping Event Collection

Event collection will stop automatically under the following conditions:
• The connection to the node is lost
• The drive on which the event log file is located reaches 90% capacity
• You manually disconnect from the node
• You exit Enhanced Diagnostic Monitor
To manually stop event collection:

• On the Events menu, click Stop Collecting Events.
Changing the Default Event Collection Settings

Event collection settings can be customized to suit your needs at any time. These settings apply
to all Tricon nodes in the open network configuration.
Procedure
1 In the Network Configuration tree, double-click the node (controller) you want to
monitor.
You do not have to be actively connected to the node to change event collection settings,
but the System Overview or Module Status window for the node must be open.
2 On the Events menu, select Options. The Event Options dialog box appears.
3 Click the General Tricon Options tab.

4 Edit these properties.
Auto Scroll Defines the behavior of the event list during event
collection.
When selected, the event list automatically scrolls
vertically to keep the most recent events at the bottom of
the list visible.
When cleared, the event list view does not change. You
must manually use the vertical scroll bar to view the most
recent events.
The default is selected (auto scroll enabled).
Default Log File Directory Enter the path where event log files will be saved. The
default is:
C:\...My Documents\Triconex\Enhanced
Diagnostic Monitor 1.0\
Note: Due to Windows restrictions, we recommend
limiting the total path length for event log files to
less than 250 characters (including file name and
extension). This allows for the creation of auto-
generated files when the maximum number of
Max Events Per Log File Enter the maximum number of events to save to a single
log file, in increments of 10,000.
• The maximum value is 500,000.
• The minimum value is 10,000.
• The default value is 500,000.
The Maximum File Size property displays the estimated
maximum size1 of an event log file based on the selected
number of maximum events per file. This property is
read-only.
See Managing Event Log File Size on page 53 for more
information about how the Enhanced Diagnostic Monitor
handles event log files when they reach their maximum
size.
1. The actual file size may differ significantly from this estimate. View the properties for the event
log file after event collection to view the actual size.

The selected options are immediately implemented only for the node that is currently
active, or the event log file currently being viewed.
Note To apply the same settings to other nodes, you must repeat steps 1–3 for each node, and
then also do one of the following:
• Make a change on either the Tricon Event Filters tab or Tricon Event Exclusion tab.
• Change the Auto Scroll setting on the General Tricon Options tab.

Filtering the Events List

You can control which events are visible in the Events pane during event collection or while you
are viewing an event log file using the event filtering options.
Note Events that do not match your selected filtering options will not appear in the Events
pane during event collection or viewing, but will still be saved to the event log file, so
they can be viewed later if needed.
Procedure
monitor.
You do not have to be actively connected to the node to change event collection settings,
3 Edit these properties.
Start Time Enter the starting date and time for a filtered list of
events, in the month/day/year/hour/minute/second
format. If you aren’t using the 24-hour time format, be
sure to specify AM or PM.
The default value is 1/1/1970 12:00:01 AM.
End Time Enter the ending date and time for a filtered list of events,
in the month/day/year/hour/minute/second format. If
you aren’t using the 24-hour time format, be sure to
specify AM or PM.
The default value is 12/31/2037 11:59:59 PM.

Severity Select the severity level(s) of the system events you want
to see in the event list.
For example, if you only want to see Fault and Degraded
messages in the event list, clear the Information and
Warning check boxes, and select the Fault and Degraded
check boxes.
All severity levels are selected by default.
MP Leg Select the main processor legs whose system events you
want to see in the list (A, B, or C).
All legs are selected by default.
Board Address Enter the address of the specific board whose system
events you want to see in the event list. The address must
be entered in hexadecimal format; however, do not enter
the “0x” characters. Enter only the last two characters of
the board address.
• Enter a single board address, such as ff.
• Enter a range of board addresses, to view events for
all boards included in the range, such as 00-0a.
• Enter individual board addresses, separated by
commas, to view events for more than one board,
such as b3,f0,68.
• Enter a combination of individual board addresses
and ranges, such as b3,00-0a,68,c2.
If you want to see system events for all boards, enter
0-ff (this is a range from 0x00 to 0xff). This is the default
setting.
For instructions on converting chassis/slot locations to
hexadecimal addresses, see Appendix B, Converting
Tricon Hexadecimal Board Addresses.
Note Click Get Defaults to reset all properties to their default settings.
The filter options are immediately implemented only for the node that is currently
active, or the event log file currently being viewed.
Note To apply the same settings to other nodes, you must repeat steps 1–2 for each node, and
then also do one of the following:
• Make a change on either the Tricon Event Filters tab or Tricon Event Exclusion tab.
• Change the Auto Scroll setting on the General Tricon Options tab.

Modifying the Event Exclusion List

During event collection, you can choose to exclude specific event messages from the event list.
For example, if you don’t want to see event messages related to the position of the keyswitch,
you can exclude just those events from appearing in the event list.
Note Even if events are excluded from appearing in the list displayed in the Events pane,
those events will still be saved to the event log file, so they can be viewed later if needed.
Procedure
monitor.
You do not have to be actively connected to the node to change the event exclusion list,
3 Click the Tricon Event Exclusion tab.

4 Do one or both of the following:
• Add events to the exclusion list by clicking the event in the top list and then clicking
Exclude.
• Remove events from the exclusion list by clicking the event in the bottom list and
then clicking Include.
The event exclusion list is immediately implemented only for the node that is currently
active.

Viewing an Existing Event Log File

You can open an existing event log file without being actively connected to a node. This allows
you to review past events at any time, even when you cannot connect to a controller.
More than one existing event log file can be viewed at the same time, up to a maximum of 31
open event log files (only one event log file can be opened per node; 31 nodes are available).
You cannot open an event log file on a node that is actively collecting events. However, you do
not have to open the specific node on which an event log file was originally collected in order
to view it.
For example, if you open node 7 in the System Overview window, you can open an existing file
for any node, not just a node 7 event log file.
Procedure
1 In the Network Configuration tree, double-click a Tricon node that is not actively
collecting events.
You do not have to be actively connected to a node to view an existing event log file, but
the System Overview or Module Status window for a node must be open.
2 On the Events menu, select Open Event File.
3 Browse to locate the file you want to view, and then click Open.
The list of events saved in the event log file appears in the Events pane. Events are sorted
by date and time; the sort order cannot be changed.
Note If you don’t see the events list in the System Overview or Module Status window,
you need to open the Events pane. See Opening the Events and Events Summary
Panes on page 51.
4 Use the event filtering options to customize the event view to your specific needs. See
Filtering the Events List on page 58.

Exporting an Event Log File

Tricon event log files can be exported to the dBase IV file format (.dbf) so that the event log file
can be viewed in applications that support the .dbf file format, such as Microsoft Excel or
Microsoft Access.
Only a previously saved event log file that has been opened for viewing can be exported. You
cannot export an event log file that is actively collecting events.
Only the events that are currently being shown in the Events pane will be exported. To export
all viewable events in a file, be sure to remove all filtering options before exporting the file.
Procedure
1 In the Network Configuration tree, double-click a Tricon node that is not actively
collecting events.
You do not have to be actively connected to a node to view and export an existing event
log file, but the System Overview or Module Status window for a node must be open.
2 On the Events menu, select Open Event File.
3 Browse to locate the event log file you want to export, and then click Open.
The list of events saved in the file appears in the Events pane.
Note If you don’t see the events list in the System Overview or Module Status window,
you need to open the Events pane. See Opening the Events and Events Summary
Panes on page 51.
4 On the Events menu, select Export Event File.
5 Enter a file name and location for the exported file, and then click Save.
The file is exported and a message appears confirming the successful export.
Exported .Dbf File Format

The format of an event log file exported to .dbf is as follows:
Maximum Length
Column Name Format
(Number of Characters)
DATE Text 10
TIME Text 15
CLASS Text 5
CODE Text 5
LEG Text 1
BOARD Text 5
MESSAGE Text 255

Opening an Exported Tricon Event Log File in Microsoft Access

If you will be opening the exported file in Microsoft Access 2000 or 2003, please note the
following:
• When naming the exported file, you must select a name that uses eight characters or
less. Or, rename the file as necessary after the export is complete.
• To open the file, first open Access, and then use the File > Open command to open the
.dbf file. Other methods of opening the file with Access will not work.
• When the file is opened in Access, a master database file (.mdb) with the same name
will be created. This file has links to the original .dbf file; if you rename or delete the
associated .dbf file, the master database file will no longer be able to find the data.

Collecting Trident System Events

This procedure explains how to collect Trident system diagnostic events in a Trident event log
file (.tde). This file can be sent to Triconex customer service for assistance in troubleshooting
problems.
Note You can collect events simultaneously on one or more Trident nodes and one Tricon
node. For more information about collecting Tricon system events, see Collecting and
Viewing Tricon System Events on page 48.
Procedure
1 In the Network Configuration tree, double-click the Trident node (controller) you want
to monitor.
2 On the Commands menu, click Collect System Events.
3 In the Save As dialog box, enter a file name for the event log file, and then click Save.
The correct extension (.tde) is automatically appended if you do not type it in.
4 Click OK.
Event collection begins. A maximum of 500,000 events are collected.
5 To stop event collection at any time, in the Collecting System Events dialog box, click
Stop.

A
Commands and Properties
This appendix provides descriptions of Enhanced Diagnostic Monitor commands and

properties.
Add Command
The Add command adds a node (controller) to a network configuration.
The default is Tricon controller type.
Applies To
Network configurations, nodes
Location
Network Node menu, or right-click on Network Nodes tree
Auto Scroll
The Auto Scroll property defines the behavior of the event list during event collection. When
selected, the event list automatically scrolls vertically to keep the most recent events visible.
When cleared, the event list view in the Events pane does not change. You must manually use
the vertical scroll bar to view the most recent events.
The default is selected (auto scroll enabled).
Applies To
Tricon events list
Locations
Events menu > Options command > Event Options dialog box > General Tricon Options tab
Set Events Options button > Event Options dialog box > General Tricon Options tab

66 Appendix A Commands and Properties
Board Address
The Board Address property specifies the address of the specific board whose system events
you want to see in the event list. The address must be entered in hexadecimal format; however,
do not enter the “0x” characters. Enter only the last two characters of the board address.
• Enter a single board address, such as ff.
• Enter a range of board addresses, to view events for all boards included in the range,
such as 00-0a.
• Enter individual board addresses, separated by commas, to view events for more than
one board, such as b3,f0,68.
• Enter a combination of individual board addresses and ranges, such as b3,00-
0a,68,c2.
If you want to see system events for all boards, enter 0-ff (this is a range from 0x00 to 0xff). This
is the default setting.
Applies To
Tricon events list, modules
Locations
Events menu > Options command > Event Options dialog box > Tricon Event Filters tab
Set Events Options button > Event Options dialog box > Tricon Event Filters tab
Calendar
The Calendar property displays the current time of the controller being monitored in the
day/date/hour/minute/second format.
Applies To
Controllers
Location
System Overview window
Clear All Command

The Clear All command clears all messages from the Messages pane.
Applies To
Message text
Location
View menu > Messages command > right-click in Messages pane

67
Clear Faults on All Modules Command

The Clear Faults on All Modules command clears the fault indicators on modules and the fault
flags in the Enhanced Diagnostic Monitor.
Before using this command, you should identify the causes of the faults and correct them. For
more information and an important warning, see Clearing Faults on All Modules on page 35.
Applies To
Modules, fault flags
Location
Commands menu
Close Event File Command

The Close Event File command closes the Tricon event log file currently being viewed.
This command is available only when an event log file is open for viewing. You cannot close an
event log file that is actively collecting events.
Applies To
Tricon events list
Location
Events menu
Close Network Configuration Command

The Close Network Configuration command closes an open network configuration.
Applies To
Location
Network Node menu
Collect System Events Command

The Collect System Events command collects Trident system events in a log file (.tde).
This command is available only when you are actively connected to a Trident node (controller).
Applies To
Trident, power supplies, modules, points, events list
Locations
Collect System Events button, or Commands menu

Communication Options Command

The Communication Options command allows you to control how many times the Enhanced
Diagnostic Monitor will attempt to restore the connection to a Tricon node when it is lost (for
example, due to communication or hardware problems). The connection retry limit applies to all
nodes in the network configuration.
Applies To
Tricon nodes
Location
Tools menu
Connect Command
The Connect command connects the diagnostic PC to a node (controller) in an Ethernet network
or a serial link (Tricon only).
Applies To
Network configurations, networks
Locations
Connect button, or Commands menu
Connection Type
The Connection Type property specifies the type of connection between a diagnostic PC and a
controller.
For Tricon, the settings are:
• Network for an Ethernet (TCP/IP) connection. This is the default.
• Serial for a serial (Modbus) connection.
For Trident, the settings are:
• Main Processor for an Ethernet (DLC) connection. This is the default.
• Network for an Ethernet (TCP/IP) connection.
Applies To
Nodes in a network configuration
Location
Network Nodes tree or menu > right-click a node > Add or Edit command > Network Node
Configuration dialog box

69
Continuous Refresh Command

When the Continuous Refresh command is selected, the System Overview and Module Status
windows are continually updated until you disconnect from the node or click Continuous
Refresh again to clear your selection.
The default is On.
You cannot change the refresh setting while you are actively collecting events. During event
collection, Enhanced Diagnostic Monitor automatically enables continuous refreshing—even if
you had previously disabled it—so that you continue to receive updated module status
information in the System Overview or Module Status window while events are being collected.
Once event collection is stopped, the refresh setting will revert to your original setting.
Applies To
Module Status window (Tricon)
Module Status window (Trident)
Locations
Continuous Refresh button, or Command menu
Controller Type
The Controller Type property allows you to specify a Tricon or Trident controller in a network
node configuration.
Applies To
Location
Copy Command
The Copy command copies selected messages from the Messages pane and places them on the
clipboard.
Applies To
Message text
Location

Current Faults
The Current Faults setting displays the current faults on the selected module, including internal
and external (field) faults.
Applies To
Faults on a Trident controller
Location
Trident Module Status window > double-click faulting module > Module Status dialog box >
Left, Middle, or Right Module tab
Cut Command
The Cut command removes all messages from the Messages pane and places them on the
clipboard, erasing the previous content.
Applies To
Message text
Location
Default Log File Directory

The Default Log File Directory property specifies the default path for Tricon event log files.
The default is: C:\...My Documents\Triconex\Enhanced Diagnostic Monitor 1.0\
Due to Windows restrictions, we recommend limiting the total path length for event log files to
less than 250 characters (including file name and extension). This allows for the creation of auto-
generated files when the maximum number of events in an event log file is reached.
Applies To
Tricon events list
Locations
Delete Command
The Delete command allows you to remove a node from a network configuration.
Applies To
Network Nodes tree, nodes, network configurations
Locations

71
Disconnect Command
The Disconnect command stops the diagnostic PC from communicating with the active node
(controller).
Applies To
Locations
Disconnect button, or Command menu
Display Execution Times Command

The Display Execution Times command displays the execution time for each program in the
application that is running on the controller. The execution times are visible in the Messages
pane.
The programs are identified as Program 0, Program 1, and so on. Program 0 and Program 1 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. For example, if
the execution list in a project contains three programs named GET_INPUTS, EVALUATE, and
WRITE_OUTPUTS, the displayed program execution list looks something like this:
Program 0 = 215 usec. //Scan initialization program provided by TriStation 1131
Program 1 = 50 usec. //Scan termination program provided by TriStation 1131
Program 2 = 137 usec.//User program GET_INPUTS
Program 3 = 180 usec.//User program EVALUATE
Program 4 = 58 usec. //User program WRITE_OUTPUTS
Applies To
Tricon and Trident controllers
Location
Commands menu
Display Firmware Versions Command

The Display Firmware Versions command displays the firmware version numbers of all
modules in a Tricon chassis or Trident IOP. The firmware versions are visible in the Messages
pane.
Typically, this command is used only if requested by a Triconex Customer Support Engineer for
diagnostic purposes.
Applies To
Tricon and Trident modules
Location
Commands menu

Edit Command
The Edit command allows you to edit a node using the Network Node Configuration dialog
box.
Applies To
Network Nodes tree, nodes
Locations
Edit Users Command

The Edit Users command opens the Permissions dialog box, which allows user accounts to be
created and modified.
Applies To
User security
Location
Permissions menu
End Time
The End Time property specifies the ending date and time for a filtered list of events, in the
month/day/year/hour/minute/second format. The default value is 12/31/2037 11:59:59 PM.
Applies To
Tricon events list
Locations
Exclude Command
The Exclude command moves the selected event messages that you do not want to see in the
event list during event collection to the list of excluded events. For example, if you don’t want
to see event messages related to the position of the keyswitch, you can exclude just those events
from appearing in the event list.
Also see Include Command on page 74.
Applies To
Tricon events list
Locations
Events menu > Options command > Event Options dialog box > Tricon Event Exclusion tab
Set Events Options button > Event Options dialog box > Tricon Event Exclusion tab

73
Exit Command
The Exit command closes the network configuration and exits the Enhanced Diagnostic Monitor.
Applies To
Network configurations, Enhanced Diagnostic Monitor
Location
File menu
Export Event File

The Export Event File command exports a Tricon event log file (.tce) to a dBase IV-compatible
(.dbf) file. Only the events that are currently being shown will be exported. To export all
viewable events in a file, be sure to remove all filtering options before exporting the file.
This command is available only when an event log file is open for viewing. You cannot export
an event log file that is actively collecting events.
Applies To
Tricon events list
Location
Events menu
Fault History
The Fault History setting displays all the faults that have occurred on a module during the
current session.
Applies To
Faults on a Trident controller
Location
Trident Module Status window > double-click faulting module > Module Status dialog box >
Left, Middle, or Right Module tab
Field Faults
The Field Faults setting displays load or fuse faults related to field inputs, field power,
terminations, wiring, or devices for a selected module. (Does not apply to main processors.)
Applies To
Faults on a controller
Location
Trident Module Status window > double-click module > Module Status dialog box > Left,
Middle, or Right Module tab
Tricon Module Status window > double-click module > Module Status dialog box > Field Faults tab

Find Command
The Find command finds specified text in the Messages pane.
Applies To
Message text
Location
Free Memory
The Free Memory property displays the amount of memory available for expansion of the
TriStation 1131 application running on the controller.
Applies To
Applications, controllers
Location
Include Command
The Include command moves events from the list of excluded events to the list of events you
want to see in the event list during event collection.
Also see Exclude Command on page 72.
Applies To
Tricon events list
Locations
Events menu > Options command > Event Options dialog box > Tricon Event Exclusion tab
Set Events Options button > Event Options dialog box > Tricon Event Exclusion tab
IP Address
The IP Address property specifies the unique 32-bit address of a Triconex controller on an
Ethernet network.
Applies To
Locations
Network Nodes tree > right-click a node > Add or Edit command > Network Node
Network Node menu > Add or Edit command > Network Node Configuration dialog box

75
Get Defaults
The Get Defaults property resets all properties on the Tricon Event Filters tab to their default
settings.
Applies To
Tricon events list
Locations
Key Stop/Position
For Tricon, the Key Stop/Position property indicates whether the STOP position on the
keyswitch is logically disabled for security purposes, and indicates the physical setting of the
keyswitch.
If the Key Stop property is set to DISABLED, the keyswitch is prohibited from halting an
application. If the Key Stop property is set to ENABLED, the keyswitch can be used to halt an
application.
The Position property indicates the current position of the keyswitch, which can be REMOTE,
PROGRAM, RUN, or STOP.
Applies To
Location
LED Indicators
The LED Indicators area in the Module Status dialog box describes the colors of module
indicators in the On and Off states, and the meaning of each color. The indicator colors have the
following meanings.
Color Module State

Blue For Trident, the programmable alarm is On.
Green Module is operating normally.
Gray Indicates Off state.
Red Module has an internal fault.
Yellow Module has a problem with field inputs, field power supplies, terminations, wiring, or
connected devices.
For more information about module indicators, see the appropriate Planning and Installation

Applies To
Modules in Module Status window
Location
Module Status window > double-click a module > Module Status dialog box > Legend tab
Left Module
The Left Module area in the Tricon Module Status dialog box describes faults that occur on a
Tricon module in the left slot position.
Applies To
Faulting modules
Location
Tricon Module Status window > double-click faulting module > Module Status dialog box >
Any tab
Limited
The Limited property allows you to define a specific limit to the number of times the Enhanced
Diagnostic Monitor will attempt to restore the connection to a Tricon node when it is lost (for
example, due to communication or hardware problems). The connection retry limit applies to
all Tricon nodes in the network configuration.
Applies To
Tricon nodes
Location
Tools menu > Communication Options
Max Events Per Log File

The Max Events Per Log File property controls the maximum number of events that are saved
to a single Tricon event log file during event collection. It also controls the maximum size of an
event log file.
A maximum of 500,000 events can be saved in a single log file; you can lower this amount in
increments of 10,000. The default is 500,000 events.
When an event log file reaches the maximum number of events during event collection, Enhanced
Diagnostic Monitor will automatically save the file and open a new file in the same directory with
_newx appended to the file name (where x is a number representing the file count).
For example, if the maximum number of events is reached while collecting events in the event
log file events.tce, Enhanced Diagnostic Monitor will automatically create a new file with the
name events_new1.tce, and continue event collection using the new file. If that file also reaches
its maximum size, the next automatically created file will be named events_new2.tce.

77
When a new event log file is created, the following occurs:

• A message providing the new file name will appear in the Messages pane.
• The list of events in the Events pane is cleared, and only events being saved to the new
file are displayed. This keeps the event list view manageable. Events from the old file
may be viewed by opening the event log file for viewing.
Applies To
Tricon events list
Locations
Maximum File Size

The Maximum File Size property displays the estimated maximum size of a Tricon event log file
based on the selected number of maximum events per file. This property is read-only. See Max
Events Per Log File on page 76 for more information.
Note The actual file size may differ significantly from the estimate. View the properties for the
event log file after event collection to view the actual file size.
Applies To
Tricon events list
Locations
Maximum Memory
The Maximum Memory property displays the maximum amount of memory that a controller
makes available for a TriStation application. The maximum amount varies with the type of
controller (Tricon or Trident) and the version number.
Applies To
Location
System Overview screen

Messages Command
The Messages command toggles to display or hide the Messages pane at the bottom of the
screen.
The default is On.
Applies To
Messages pane
Locations
Message View button, or View menu
Module Colors
For a Trident Module Status window, the Module Colors area describes the colors that represent
the current state of each module.
Slot Color Module State

Yellow Module installed in the slot is not configured in the project.
Blue Slot is currently selected.
Red Module configured in the project is not installed in the slot.
Gray Module is configured in the project and installed in the slot.
Applies To
Modules in Trident Module Status window
Location
Trident Module Status window > double-click a module > Module Status dialog box > Legend tab
Module Status Command

The Module Status command displays the Module Status dialog box for the selected module.
Applies To
Modules
Locations
Module Status View button, or View menu

79
MP Connection
The MP Connection property specifies which Trident main processor module in a controller is
connected to a TriStation PC. MP Connection settings are Left, Middle, and Right. The default
setting is Left.
Applies To
Trident nodes in a network configuration
Locations
Network Nodes tree > right-click a Trident node > Add or Edit command > Network Node
MP Leg
The MP Leg property is a Tricon event filtering option that allows you to restrict the visible
events list to only those events that occur on the selected main processor legs (A, B, or C). If only
one leg is selected, events for the other two legs will still be collected, but only events matching
the selected leg will appear in the events list.
All three legs are selected by default.
Applies To
Tricon events list
Locations
New Event File Command

The New Event File command creates a new Tricon event log file (.tce). Once created, events can
be saved to the file during event collection.
Due to Windows limitations, we recommend limiting the total path for event log files to less
than 250 characters (including file name and extension). File names should be less than 240
characters. This allows for the creation of auto-generated files when the maximum number of
Applies To
Tricon events list
Locations
New Event File button, or Events menu

New Network Configuration Command

The New Network Configuration command creates a Network Nodes tree in the left pane of the
Enhanced Diagnostic Monitor. Once created, you can save the configured nodes in the tree to
an XML file.
Applies To
Locations
New button, or File menu
NIC Index
The NIC Index property specifies the index position of the network interface card in the
diagnostic PC.
Applies To
Trident network configuration, nodes
Locations
Network Nodes tree > right-click a Trident node > Add or Edit command > Network Node
Node Name
The Node Name property specifies the name for a Triconex controller, which can be a default
name or a user-defined name.
The default names are TRINODE01 through TRINODE31.
Applies To
Locations
Node Number
The Node Number property specifies a number for a Triconex controller, which must be the
same as on the switch setting (Tricon) or the address plug (Trident).
The node number must be unique within the network configuration; you cannot have two
nodes with the same number in a single network configuration.
The range is 1–31 for both Tricon and Trident.

81
Applies To
Location
Open Command
The Open command opens a node (controller) on the Network Nodes tree for monitoring.
Applies To
Network Nodes tree, nodes
Locations
Network Nodes tree > right-click a node, or Network Node menu
Open Event File Command

The Open Event File command opens an existing Tricon event log file (.tce) for viewing. This
command is available only when events are not actively being collected on the selected node.
Applies To
Tricon events list
Locations
Open Event File button, or Events menu
Open Network Configuration Command

The Open Network Configuration command opens an existing network configuration (XML) file.
Applies To
Network configurations, controllers
Locations
Open button, or Network Node menu
Point Faults
For a selected Tricon module, the Point Faults area in the Module Status dialog box lists the
number of each point with a fault condition.
Applies To
Faulting modules
Location
Faulting module in Tricon configuration > Module Status dialog box > Field Faults, Power
Faults, or Voter Faults tabs

Poll Time
The Poll Time property displays the maximum time needed by the controller to obtain data
The poll time should not exceed the scan time. If it does, the scan time should be increased. For
instructions, see Changing the Scan Time Using TriStation 1131 on page 42.
Applies To
Location
Print Command
The Print command prints the selected contents of the Messages pane to a specified printer.
Applies To
Message text
Location
Project
The Project property displays the name and version number of the project (application) running
on a controller. The version number is incremented each time the application is downloaded.
Applies To
Location
Refresh Panel Command

The Refresh Panel command updates the System Overview and Module Status windows only
once. If Continuous Refresh was on, selecting this command will turn it off.
See also Continuous Refresh Command on page 69.
Applies To
Module Status
Locations
Refresh Panel button, or Commands menu

83
Right Module
The Right Module area in the Module Status dialog box describes faults that occur on a Tricon
module in the right slot position.
Applies To
Faulting modules
Location
Tricon Module Status window > double-click faulting module > Module Status dialog box >
Any tab
Save As Command
The Save As command saves messages from the Messages pane to a text file.
Applies To
Message text
Location
Save Network Configuration Command

The Save Network Configuration command saves an XML network configuration file in a
specified folder.
Applies To
Network configurations
Locations
Save button, File menu, or right-click Network Nodes on tree
Save Network Configuration As Command

The Save Network Configuration As command saves an XML network configuration file under
a different name or folder.
Applies To
Network configurations
Locations
File menu, or right-click on Network Configuration tree

Scan Request/Actual
The Scan Request/Actual property displays the requested scan time and the actual scan time of
the current controller. The requested scan time is the time specified in the project.
The actual scan time is the actual length of time required by the controller to complete the last
scan. The actual scan time is equal to or greater than the requested scan time.
Applies To
Controllers, applications
Location
Scan Surplus
The Scan Surplus property displays, for the current controller, the time that remains in a scan
after reading inputs, executing the application, processing messages, and writing outputs.
A negative scan surplus means that scan overruns have occurred, which can cause
communication errors.
To eliminate scan overruns, you should increase the scan time. For instructions, see Changing
the Scan Time Using TriStation 1131 on page 42.
Applies To
Controllers, applications
Location
Select All Command

The Select All command selects all text in the Messages pane, in preparation for a Copy or Cut
operation.
Applies To
Message text
Location
View menu > Messages command > right-click in the Messages pane

85
Serial Port
The Serial Port property specifies which COM port on a diagnostic PC is connected to a Tricon
controller or a network. Visible only when “Serial” is selected as the connection type.
Serial Port settings are COM1, COM2, COM3, and COM4.
The default setting is COM1.
Applies To
Diagnostic PC, Tricon controllers
Locations
Set Event Options

The Set Event Options command allows you to customize event collection settings to suit your
needs. These settings apply to all Tricon nodes.
Applies To
Tricon events list
Locations
Events menu > Options command > Event Options dialog box
Set Event Options button > Event Options dialog box
Severity
The Severity property specifies the severity level(s) of the Tricon system events you want to see
in the event list.
For example, if you only want to see Fault and Degraded messages in the event list, clear the
Information and Warning check boxes, and select the Fault and Degraded check boxes.
All severity levels are selected by default.
Applies To
Event list
Locations

Show Line Numbers Command

The Show Line Numbers command shows the number of each line of text in the Messages pane.
Applies To
Message text
Location
View menu > Messages command > Right-click in Messages pane
Slot Colors
The Slot Colors area in the Module Status dialog box describes the colors that represent the
current state of each module in the Module Status window.
Slot Color Module State

Yellow A module installed in the slot is not configured in the project.
Blue For Tricon, the spare module is not installed.
For Trident, the slot is currently selected.
Red A module configured in the project is not installed in the slot.
For Trident, if a slot is outlined in red, a module in the slot has a fault.
Gray For Trident, a module is installed in the slot and configured in the project.
Applies To
Module Status window
Location
Module Status window > double-click a module > Module Status dialog box > Legend tab
Start Collecting Events Command

The Start Collecting Events command collects Tricon system events in a log file (.tce). If a blank
log file is not already open, you will be prompted to select a location and name for a new file.
This command is available only when you are actively connected to a Tricon node (controller)
via a network connection. You cannot collect events when connected via a serial connection.
Applies To
Controllers, power supplies, modules, points
Locations
Collect System Events button, or Events menu

87
Start Time
The Start Time property specifies the starting date and time for a filtered list of Tricon system
events, in the month/day/year/hour/minute/second format.
The default value is 1/1/1970 12:00:01 AM.
Applies To
Tricon events list
Locations
Status
The Status property displays the current state of the application running on a controller.
Possible states are OFFLINE, IDLE, RUNNING, HALTED, and PAUSED.
Applies To
Location
Status Bar Command

The Status Bar command toggles to display or hide the Status Bar.
The default is On.
Applies To
Enhanced Diagnostic Monitor view
Location
View menu
Stop Collecting Events Command

The Stop Collecting Events command stops Tricon event collection. This command is available
only when you are actively collecting events.
Applies To
Controllers, power supplies, modules, points
Locations
Stop Collecting Events button, or Events menu

Toolbar Command
The Toolbar command toggles to display or hide the toolbar at the top of the screen. The default
is On.
Applies To
Location
View menu
Unlimited
The Unlimited property enables the Enhanced Diagnostic Monitor to automatically attempt to
restore the connection to a Tricon node when it is lost (for example, due to communication or
hardware problems). Attempts to restore the connection will continue indefinitely until the
connection is successfully restored. The connection retry limit applies to all nodes in the
network configuration.
Applies To
Tricon nodes
Location
Tools menu > Communication Options
Workspace Command
The Workspace command toggles the display of the Network Configuration tree on the left side
of the Enhanced Diagnostic Monitor window, increasing or decreasing the size of the
workspace on the right side of the window. The default is On (Network Configuration tree is
displayed).
Applies To
Locations
Workspace View button, or View menu

89
Zoom Command
For Trident, the Zoom command enlarges or shrinks your view of the modules in the Module
Status window. The standard settings are 50%, 75%, 100%, and 200%. You can also enter a
percentage or click Zoom To Fit to toggle between a large and small view.
Applies To
Trident modules
Locations
Zoom button, or View menu
Zoom To Fit Command

For Trident, the Zoom To Fit command toggles between a large and small view of the modules
in the Module Status window.
Applies To
Trident modules
Locations
Zoom to Fit button, or View menu


B
Converting Tricon Hexadecimal Board
Addresses
Overview 92
Tricon v9 / v10 High-Density Conversion Information 93
Tricon v9 Low-Density Conversion Information 96

92 Appendix B Converting Tricon Hexadecimal Board Addresses
Overview
The Enhanced Diagnostic Monitor displays the board address associated with a Tricon system
event message as a hexadecimal value. This appendix describes how to convert board addresses
from the hexadecimal values to their equivalent chassis and slot numbers.
What Is a Hexadecimal Board Address?

A hexadecimal board address consists of four characters, for example, 0xb3.
• The first two characters indicate that the value is hexadecimal.
• The third character is the chassis number, in hex format.
• The fourth character is the slot number, in hex format.
What Is a Slot Number?

The slot number refers to the physical slot, not the logical slot.
• Each MP and COM slot equals one physical slot.
• Each I/O logical slot equals two physical slots.
Which Conversion Tables Should You Use?

Be sure to use the correct conversion tables for your Tricon system and chassis type:
Tricon System Chassis Type Use these tables...

v10 High-Density All Hex to Chassis / Slot Conversion Tables—All High-Density
Chassis on page 93
v9 High-Density All Hex to Chassis / Slot Conversion Tables—All High-Density
Chassis on page 93
v9 Low-Density Main and RXM Hex to Chassis / Slot Conversion Tables—Low-Density Main
and RXM Chassis on page 96
v9 Low-Density Expansion Hex to Chassis / Slot Conversion Tables—Low-Density
Expansion Chassis on page 97

Tricon v9 / v10 High-Density Conversion Information

The tables and figures in this section apply to high-density chassis Tricon v9 and v10 systems.
Hex to Chassis / Slot Conversion Tables—All High-Density Chassis

The following tables provide the hex and decimal equivalents for high-density chassis and slot
numbers.
Hex Chassis Hex Slot

(3rd Character) (4th Character)
0 1 0 1
1 1 1 2
2 2 2 3
3 3 3 4
4 4 4 5
5 5 5 6
6 6 6 7
7 7 7 8
8 8 8 9
9 9 9 10
a 10 a 11
b 11 b 12
c 12 c 13
d 13 d 14
e 14 e 15
f 15 f 16
Sample Hex to Chassis / Slot Conversions

The following are some sample hexadecimal board address conversions for high-density
chassis:
Hex Board
Chassis Slot
Address
0xb3 11 4
0xf0 15 1
0x68 6 9
0x0f 1 16
0xca 12 11

High-Density Chassis Physical Slot Locations

The following figures show the location of each physical slot—by number—in a high-density
Tricon main and expansion chassis. An RXM chassis has the same physical configuration as a
main chassis.
The main chassis is number 1. Expansion chassis are numbered from 2 to 15.
Tricon v9 and v10 Main / RXM Chassis Configuration
POWER A MP B C COM L 2 R L 3 R L 4 R L 5 R L 6 R L 7 R
1
REMOTE RUN
A
PROGRAM
PASS PASS PASS
STOP
FAULT FAULT FAULT
ó LOCAL ó
ACTIVE ACTIVE ACTIVE
MAINT1 MAINT1 MAINT1

115/230 VAC
PASS
FAULT
ALARM
TEMP
BATT LOW
B
POWER MODULE
MODEL 8310
115/230 VAC
PASS
FAULT
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ALARM
COM RX COM RX COM RX
TEMP
COM TX COM TX COM TX
BATT LOW
I/O RX I/O RX I/O RX
C I/O TX I/O TX I/O TX
POWER MODULE EMP EMP EMP

MODEL 8310 3006 3006 3006
A Keyswitch with Chassis Number

B, C Redundant Power Modules
1–16 Physical Slots

Tricon v9 and v10 Expansion Chassis Configuration
POWER L 1 R L 2 R L 3 R L 4 R L 5 R L 6 R L 7 R L 8 R
2A
115/230 VAC
PASS
FAULT
ALARM
TEMP
BATT LOW
POWER MODULE
MODEL 8310
115/230 VAC
PASS
FAULT
ALARM
TEMP
BATT LOW
POWER MODULE
MODEL 8310
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
A, B Redundant Power Modules


Tricon v9 Low-Density Conversion Information

The tables and figures in this section apply only to the low-density Tricon v9 system. Note that
the slot conversion table for an expansion chassis is different than that of a main or RXM chassis.
Hex to Chassis / Slot Conversion Tables—Low-Density Main and RXM

Chassis
The following tables provide the hex and decimal equivalents for chassis and slot numbers in a
low-density main or RXM chassis.
Hex Chassis Hex Physical Logical

(3rd Character) (4th Character) Slot Slot
0 1 0 1 MP A or RXM A
1 1 1 2 MP B or RXM B
2 2 2 3 MP C or RXM C
3 3 4 5 1L
4 4 5 6 1R
5 5 6 7 2L
6 6 7 8 2R
7 7 8 9 3L
8 8 9 10 3R
9 9 a 11 4L
a 10 b 12 4R
b 11
c 12
d 13
e 14
f 15

The following are some sample hexadecimal board address conversions for a low-density main
or RXM chassis:
Hex Board
Chassis Slot
Address
0xb4 11 5
0xf0 15 1
0x68 6 9
0x02 1 3
0xca 12 11

Hex to Chassis / Slot Conversion Tables—Low-Density Expansion Chassis

The following tables provide the hex and decimal equivalents for chassis and slot numbers in a
low-density expansion chassis.
Hex Chassis Hex Physical Logical

(3rd Character) (4th Character) Slot Slot
0 1 2 3 1L
1 1 3 4 1R
2 2 4 5 2L
3 3 5 6 2R
4 4 6 7 3L
5 5 7 8 3R
6 6 8 9 4L
7 7 9 10 4R
8 8 a 11 5L
9 9 b 12 5R
a 10
b 11
c 12
d 13
e 14
f 15

The following are some sample hexadecimal board address conversions for a low-density
expansion chassis:
Hex Board
Chassis Slot
Address
0xb3 11 4
0xf2 15 3
0x68 6 9
0x0b 1 12
0xca 12 11

Low-Density Chassis Physical Slot Locations

The following figures show the location of each physical slot—by number—in the Tricon
low-density main and expansion chassis. An RXM chassis has the same physical configuration
as a main chassis.
The main chassis is number 1. Expansion chassis are numbered from 2 to 15.
Tricon v9 Low-Density Main / RXM Chassis Configuration
POWER MP 1 2 3 4
A B C L R L R L R L R
115/230 VAC PASS PASS PASS
FAULT FAULT FAULT
ACTIVE ACTIVE ACTIVE

PASS
FAULT
ALARM
TEMP
BATT LOW
POWER MODULE
MODEL 8310
115/230 VAC
PASS
FAULT
ALARM
TEMP
BATT LOW
B 1 2 3 5 6 7 8 9 10 11 12
COM RX COM RX COM RX
COM TX COM TX COM TX
I/O RX I/O RX I/O RX
I/O TX I/O TX I/O TX
POWER MODULE
MODEL 8310
1
REMOTE RUN
EMP EMP EMP
3006 3006 3006
A
PROGRAM
STOP
ó LOCAL ó
A Keyswitch with Chassis Number


Tricon v9 Low-Density Expansion Chassis Configuration
POWER 1 2 3 4 5
L R L R L R L R L R
115/230 VAC
PASS
FAULT
ALARM
TEMP
BATT LOW
POWER MODULE
MODEL 8310
115/230 VAC
PASS
FAULT
ALARM
TEMP
BATT LOW
B
POWER MODULE
MODEL 8310
3 4 5 6 7 8 9 10 11 12
A 2
A Chassis Number


Index
A Clear Faults privilege 11

Access, viewing events in 63 clearing faults, on all modules 35
ACM event retention 50 client access list, TCM 12, 15, 21
Add command 65 Close Event File command 67
Add/modify users privilege 12 Close Network Configuration command 67
adding code, event message 49
nodes 18 Collect System Events command 67
users 9 collecting system events
addresses, hexadecimal 92–98 Tricon 48–63
Auto Scroll property 57, 65 Trident 64
colors
B event messages 49
modules, Tricon 26
blue, event message color 49
modules, Trident 29
Board Address property 59, 66
Communication Options command 22, 68
board addresses, hexadecimal
compatibility 3
defined 92
Connect command 68
Tricon High-Density 93
Tricon Low-Density 96 connection
Ethernet 16
lost 22, 46
C Modbus 17
Calendar property 41, 66 read-only 21
capacity, disk 54 retry limit 22
changing serial 17
memory allocation 43 to controller 20
network configuration 18 troubleshooting 21
OVD state 36 Connection Type property 19, 68
passwords, user 10 Continuous Refresh command 44, 69
scan time 42 controller
security level connecting to 20
names 14 status
privileges 11 refreshing 44
chassis configurations viewing 40–41
Tricon High-Density 94 see also nodes
Tricon Low-Density 98 see also Tricon
chassis icons see also Trident
Tricon 25 Controller Type property 69
Trident 28 converting hexadecimal addresses 92
chassis numbers Copy command 69
Tricon High-Density 93
correcting faults 32, 34
Tricon Low-Density 96, 97
creating
class, event message 49
event log file 53
Clear All command 66 network configuration 18
Clear Faults on All Modules command 67 user 9

102 Index
Current Faults property 30, 70 event log files, Tricon

customer support vi closing 67
Cut command 70 creating 53
.dbf format 62
default directory for 57, 70
D
displaying 48
date, event message 49 exporting 62–63
.dbf file 62 filtering view 58
default free disk space for 54
event collection settings 56 managing 53
events per file 53 opening 61, 81
log file directory 57 size, default 53
password 7 status of 50
security level names 14 viewing 61
security level privileges 11 see also events, Tricon
user 7–9 event log files, Trident 64
Default Log File Directory property 57, 70 event message class 49
Delete command 70 event message code 49
deleting users 9 event retention 50
directory, log file 57, 70 Events pane
Disconnect command 71 filtering view in 58
disk space information in 49
for event log files 54 opening 51
for installation 3 Events Summary pane
Display Execution Times command 47, 71 information in 49
Display Firmware Versions command 37, 71 opening 51
DLC protocol, installing on diagnostic PC 5 events, Tricon
collecting 55
E collection settings 56
Edit command 72 color-coding 49
excluding from list 60
Edit Users command 72
exporting 62–63
EICM event retention 50
filtering view of 58
End Time property 58, 72
interpreting 49
Enhanced Diagnostic Monitor loss of 50
compatibility 3 maximum per file 53, 57, 76
installing 4 retention of 50
logon password 20 severity levels 49, 59
new features v see also event log files, Tricon
starting 7
events, Trident 64
steps for using 2
Exclude command 72
system requirements 3
uninstalling 4 exclusion list 60
error messages 46 execution times, program 47, 71
Exit command 73
Ethernet network configuration 16
event collection, Tricon Export Event File command 62, 73
filtering 58 exporting Tricon event log files 62–63
options 56 external faults 31–32
refreshing status during 44
settings 56–60 F
starting 55 fatal faults 33
stopping 56 Fault History property 30
event collection, Trident 64 Fault History setting 73
event exclusion list 60 fault information, Tricon 28

Index 103
faults L
clearing LED Indicators area 75
on all modules 35 LEDs, module 27, 29
privileges for 11
Left Module area 76
external 31–32
Limited property 22, 76
internal 33–34
LOAD/FUSE indicator, Tricon 31
types of 31, 33
log files, Trident event 64
field faults 31
log files, Tricon event, see event log files, Tricon
Field Faults property 30, 73
Log System Events privilege 11
Field Faults tab 27
logging in 7
FIELD POWER indicator, Trident 31
logical slots 92
file access rules 15
logon
file format, exported event log 62
name 10
filtering, events 58
password 7
Find command 74
lost connection 22, 46
firmware versions 37, 71
Low-Density Tricon 96, 97
format, .dbf files 62
free disk space
required for installation 3 M
required for log files 54 major faults 33
Free Memory property 41, 74 managing event log files 53
Max Events Per Log File property 53, 57, 76
G maximum event log file size 53
Maximum File Size property 57, 77
Get Defaults property 75
Maximum Memory property 41, 77
green, event message color 49
memory allocation 43
memory statistics 41
H
message text, event 49
hardware monitoring 24
Messages command 78
hexadecimal board addresses
Messages pane 37, 45, 47
defined 92
Tricon High-Density 93 Microsoft Access 63
Tricon Low-Density 96 minor faults 33
High-Density Tricon 93 Modbus communication 17
module colors 26, 29, 78
module indicators 27, 29
I
Module Status command 78
icons, chassis 25, 28
Module Status dialog box 27, 30
ignoring password 20
Module Status window
Include command 74
changing position of 25
indicators
Tricon 26
fault 31
Trident 28, 29
module 27, 29
monitoring
indicators, fault 33
controller
installation 4 hardware 24
installing DLC protocol 5 status 41
internal faults 33–34 memory allocation 43
IOP icons 28 OVD 36
IP Address property 19, 74 scan time 42
MP Connection property 19, 79
K MP Leg property 59, 79
Key Stop/Position property 41, 75
keyswitch, Tricon 41

104 Index
N privileges, user 11
names program execution times 47
security level 14 Project property 82
user 10 project status 41
naming event log files 53 protocol, DLC 5
NCM event retention 50
network configuration R
creating 18 read-only mode 21
opening 20, 81 red, event message color 49
types 16 Refresh Panel command 82
using Modbus 17
refreshing controller status 44
New Event File command 79
requirements
new event log files 53, 79
disk space 3, 54
new features v system 3
New Network Configuration command 80 restoring lost connection 22
NIC Index property 19, 80 retention, event 50
Node Name property 80 retry limit, connection 22
Node Number property 19, 80 Right Module area 83
nodes
adding to network configuration 18
connecting to 20
S
connection problems 21 Save As command 83
editing 18 Save Network Configuration commands 83
maximum number 18 Scan Request/Actual property 41, 84
read-only connection 21 Scan Surplus property 41, 84
numbers, chassis scan time 41, 42
Tricon High-Density 93 security levels
Tricon Low-Density 96, 97 assigning privileges to 11
assigning to user 10
O default privileges 11
names, changing 14
Open command 81
overview 8
Open Event File command 81
TCM client access list 12
Open Network Configuration command 81
Select All command 84
opening Events panes 51
serial link 17
options, event collection 56
Serial Port property 19, 85
OVD 36
Set Event Options command 85
severity levels, event 49, 59
P Severity property 59, 85
passwords Show Line Numbers command 86
default 7, 8
size of event log files 53
forgotten 8
slot colors
TriStation project 20
Tricon 26
user 10
Trident 29
physical slots, chassis 92, 94, 98
Slot Colors area 86
pink, event message color 49
slots, chassis 92–98
point faults 28, 81
Start Collecting Events command 86
poll time 42
Start Time property 58, 87
Poll Time property 41, 82
starting
Port Write Enabled property 15, 21
Enhanced Diagnostic Monitor 7
power faults 27, 31 event collection, Tricon 55, 86
Print command 82 event collection, Trident 64

Index 105
status Tricon (continued)

controller Module Status dialog box 27
refreshing 44 Module Status window 26
viewing 40–41 monitoring OVD 36
event log file 50, 53 supported versions 3
OVD 36 system events 48, 49
project 41 System Overview window 25
Status Bar command 87 see also event log files, Tricon
Status property 87 Triconex contact information vi
Stop Collecting Events command 87 Trident
stopping event collection collecting events 64
Tricon 56, 87 event log file 64
Trident 64 IOP icons 28
SYSTEM ALARM indicator, Trident 31 module colors 29
system events, Tricon Module Status dialog box 30
collecting 48–63 Module Status window 28
collection settings 56 monitoring OVD 36
color-coding 49 supported versions 3
exclusion list 60 SYSTEM ALARM indicator 31
exporting 62–63 System Overview window 28
filtering view of 58 TriStation, application password 20
interpreting 49 troubleshooting
loss of 50 connection problems 21
maximum per file 53, 57, 76 connection retry limit 22
retention of 50 error messages 46
severity levels 49, 59 passwords, forgotten 8
see also event log files, Tricon
system events, Trident 64 U
System Overview tree 25 uninstallation 4
System Overview window 25, 28 Unlimited property 22, 88
system requirements 3 users
access 15
T creating 8
.tce files 53, 64 default 7, 10
deleting 9
TCM
managing 8–15
clearing faults on 35
client access list 12, 15, 21 modifying 10
names 10
connecting via serial link 17
passwords 10
event retention 50
privileges 11
read-only mode 21
security level, selecting 10
unable to connect to 21
technical support vi
time, event message 49 V
Toolbar command 88 version
training vi controllers, supported 3
Tricon firmware 37, 71
event collection 48–63 project 41
event exclusion list 60 viewing
event log files 53, 61–63 controller status 40–41
High-Density chassis configurations 94 event log files, Tricon 61
keyswitch 41 events in Access 63
Low-Density chassis configurations 98 Events panes 51
module colors 26 events, Trident 64

106 Index
viewing (continued)
firmware versions 37
memory statistics 43
program execution times 47
scan time 42
voter faults 27, 33
W
warning messages 46
web site, Triconex vi
window position, selecting 25
window view, Trident 29
Windows file access rules 15
Workspace command 88
X
XML configuration file, defined 16
Z
Zoom command 29, 89
Zoom to Fit command 29, 89

Triconex Enhanced Diagnostic Monitor PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Triconex Enhanced Diagnostic Monitor PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Triconex Enhanced Diagnostic Monitor

© 2006 Invensys Systems, Inc. All Rights Reserved.

Document No. 9720107-001

Chapter 1 Getting Started 1

Chapter 2 Monitoring Controller Hardware 23

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Monitoring Output Voter Diagnostics (OVD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 3 Monitoring Controller Status 39

Appendix A Commands and Properties 65

Appendix B Converting Tricon Hexadecimal Board Addresses 91

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

New Features in the Enhanced Diagnostic Monitor

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Product and Training Information

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

We Welcome Your Comments

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Steps for Diagnostic Monitoring 2

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Steps for Diagnostic Monitoring

Monitor C ontroller Monitor C ontroller

Monitor System &

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Installing the Enhanced Diagnostic Monitor

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Installing the Enhanced Diagnostic Monitor

Uninstalling the Enhanced Diagnostic Monitor

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Installing the DLC Protocol on the Diagnostic PC

Installing DLC on Windows 2000

Installing DLC on Windows XP

Step 1: Download the DLC Protocol Installation Program

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Step 2: Modify the .Inf File

Step 3: Configure the DLC Protocol Network Connection

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Starting the Enhanced Diagnostic Monitor

To start the Enhanced Diagnostic Monitor:

2 Enter your user name and password, and click OK.

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Creating and Managing Users

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Managing User Accounts

3 Perform one of these actions on the Users tab.

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Adding and Modifying User Accounts

4 Specify these properties in the Modify User dialog box.

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Changing the Security Level for Privileges

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

4 Click the operation(s) whose security level you want to change.

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Changing Security Level Names

4 Enter the name to associate with each security level.

Level Name Level Name

5 Click OK to save your changes.

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Other Permissions Affecting User Access

Triconex Enhanced Diagnostic Monitor v1.0 User’s Guide

Setting Up a Network Configuration

Types of Network Configurations