9720107-006 Enhanced Diagnostic Monitor v2.4.0 Users Guide

Enhanced Diagnostic Monitor
User’s Guide
Triconex Enhanced Diagnostic Monitor

Version 2.4.0
9700107-006
April 2010
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 Invensys Systems, Inc.
© 2006–2010 by 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-006

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
We Welcome Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Chapter 1 Getting Started 1

Installing the Enhanced Diagnostic Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Upgrade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installing the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installing the DLC Protocol on the Diagnostic PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Uninstalling the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Starting the Enhanced Diagnostic Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Logging In for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Logging In When Standard Security Is Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Logging In When Enhanced Security Is Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Troubleshooting Login Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Customizing the Security Banner Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Viewing User Access Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating and Managing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Changing the Security Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Adding User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Modifying User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Recommended Rules for Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Changing the Security Level for Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Changing Security Level Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Other Permissions Affecting User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Setting Up a Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Types of Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Creating or Changing a Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Opening a Network Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Troubleshooting Connection Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring the Connection Retry Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Customizing Your Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Showing or Hiding Window Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Enhanced Diagnostic Monitor v2.4.0 User’s Guide

ii Contents
Moving, Docking, and Floating Window Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Maximizing, Restoring, and Resizing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 2 Monitoring Controller Hardware 51

System Overview and Module Status Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Tricon System Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Tricon Module Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Trident System Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Trident Module Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Understanding External Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Locating and Correcting External Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Understanding Internal Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Locating Internal Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Clearing Faults on All Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Monitoring Output Voter Diagnostics (OVD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Monitoring Trident SDO OVD and Supervision Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Displaying Firmware Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 3 Monitoring Controller Status 69

Viewing Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Monitoring and Changing the Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Changing the Scan Time Using TriStation 1131 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Monitoring and Changing the Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Changing the Memory Allocation Using TriStation 1131 . . . . . . . . . . . . . . . . . . . . . . 75
Viewing Data in the Messages Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Viewing Program Execution Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Monitoring Communication Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Monitoring Tricon Communication Status Information . . . . . . . . . . . . . . . . . . . . . . . 80
Monitoring Trident Communication Status Information . . . . . . . . . . . . . . . . . . . . . . 88
Saving Communication Status Information to a File . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Chapter 4 Collecting and Viewing Events 95

Interpreting System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Event Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Event List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Events Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Important Information About Event Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Interpreting the Board Address Display Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Interpreting and Changing the Tricon Board Address Display Format . . . . . . . . . 101
Interpreting the Trident Board Address Display Format . . . . . . . . . . . . . . . . . . . . . 102
Opening the Events and Events Summary Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Managing Event Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating Event Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Managing Event Log File Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Managing Free Disk Space for Event Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Starting and Stopping Event Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Starting Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Contents iii
Stopping Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Changing the Default Event Collection Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Controlling Event Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Filtering the Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configuring the Board Address Event Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Modifying the Event Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Viewing an Existing Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Locating and Closing Open Event Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Exporting an Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Exported .Dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Opening an Exported Event Log File in Microsoft Access . . . . . . . . . . . . . . . . . . . . 121
Generating Event and Alarm Data Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Generating Event Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Generating Alarm Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Exporting Report Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Appendix A Commands and Properties 127
Appendix B Command-Line Interface Parameters 163
Appendix C Tricon Chassis and Slot Reference 167
Appendix D Trident Baseplate and Slot Reference 179
Appendix E Tricon and Trident Event Classes 183
Index 187

iv Contents

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

The following are new features in Enhanced Diagnostic Monitor v2.4.0:
• Support for up to 63 Trident nodes.
• Improved security features include Windows user authentication, user access logs, and
more, per NERC Cyber Security standards.
• Improved reporting capabilities, including the ability to generate alarm and event data
reports that can be saved to a variety of file formats.
• Enhanced support for Tricon communication, including the ability to automatically
switch to a secondary network connection when the primary connection to a Tricon
controller is lost.
• Expanded event log visibility. Events that were previously viewable only by Invensys
Customer Support personnel are now visible in all event log files.
• Windows administrator privileges are no longer required to run the Enhanced
Diagnostic Monitor.
Note For more detailed information about the changes made in each Enhanced Diagnostic
Monitor v2.x release, see the Product Release Notice for Enhanced Diagnostic Monitor v2.x,
available on the Invensys Global Customer Support (GCS) Web site.
Summary of Sections
• Chapter 1, Getting Started—Explains how to create and modify a network
configuration, select a security setting, create and manage user accounts, and customize
your workspace.
• 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.
• Chapter 4, Collecting and Viewing Events—Provides instructions for viewing and
collecting system events. Describes how to generate event and alarm data reports.

vi Preface
• Appendix A, Commands and Properties—Describes commands and properties in the

Enhanced Diagnostic Monitor.
• Appendix B, Command-Line Interface Parameters—Explains how to use the
command-line interface to start the Enhanced Diagnostic Monitor and connect to a
specified controller.
• Appendix C, Tricon Chassis and Slot Reference—A visual reference of Tricon chassis
and slot locations. Use in combination with an event message board address to
determine the location of a module installed in a chassis.
• Appendix D, Trident Baseplate and Slot Reference—A visual reference of typical
Trident baseplate and slot locations. Use in combination with an event message board
address to determine the location of a module installed in an IOP.
• Appendix E, Tricon and Trident Event Classes—Lists the event classes for both Tricon
and Trident controllers, with a short description of the component each event class
originates from.
Related Documents
• TriStation 1131 Libraries Reference
• TriStation 1131 Developer’s Guide
• Communication Guide for Tricon v9-v10 Systems
• Communication Guide for Trident Systems
• Product Release Notices for specific Tricon, Trident, and TriStation 1131 versions
Product and Training Information

To obtain information about Triconex products and in-house and on-site training, see the
Invensys Operations Management Web site or contact your regional customer center.
Web Site
http://iom.invensys.com

Preface vii
Technical Support
Customers in the U.S. and Canada can obtain technical support from the Invensys Global
Customer Support (GCS) center 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://support.ips.invensys.com/ (registration required)
E-mail
iom.support@invensys.com

viii Preface
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@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 Invensys Global Customer Support (GCS)
center. See Technical Support on page vii for contact information.
Or, you can write to us at:
Attn: Technical Publications — Triconex
Invensys
15345 Barranca Parkway
Irvine, CA 92618
USA
Thank you for your feedback.

1
Getting Started
Steps for Diagnostic Monitoring 2

Installing the Enhanced Diagnostic Monitor 3
Starting the Enhanced Diagnostic Monitor 9
Creating and Managing Users 19
Setting Up a Network Configuration 33
Customizing Your Workspace 47

2 Chapter 1 Getting Started
Steps for Diagnostic Monitoring

This figure shows the main steps for using the Enhanced Diagnostic Monitor to supervise
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, and Replace
Use TriStation 1131 to: C ommunication Status Internal
Module
- Adjust Scan Time
Yes
- Allocate More Memory
Faults?
C ollect System
Events No Repair Field
External
Devices
Yes
P ro ble 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 controllers1:
• Tricon versions 9.51.x, 9.52.x, and 9.5.2 and later
• Trident versions 1.2 and later
The Enhanced Diagnostic Monitor is intended to be installed on a DCS operator workstation,
but can be installed on any PC located on the same network as the Triconex controller(s) you
will be monitoring.
Note Throughout this manual, the PC on which you install and use the Enhanced Diagnostic
Monitor is referred to as the diagnostic PC.
Topics in this section include:
• System Requirements on page 3
• Upgrade Information on page 4
• Installing the Enhanced Diagnostic Monitor on page 5
• Installing the DLC Protocol on the Diagnostic PC on page 6
• Uninstalling the Enhanced Diagnostic Monitor on page 8
System Requirements
The following are the minimum system requirements for the Enhanced Diagnostic Monitor:
• PC running Windows XP Professional, Windows Server 2003, or Windows Server 2008
(32-bit and 64-bit); and the .NET Framework 3.5
Note If the .NET Framework is not already installed, setup will install it for you before
installing Enhanced Diagnostic Monitor. See Installing the Enhanced Diagnostic
Monitor on page 5 for more information.
• 1 GHz processor with 512 MB RAM
• 25 MB free hard drive space (for installation of the program 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 32-bit color
• DLC protocol installed (for connecting to a Trident 1.x MP only; see Installing the DLC
Protocol on the Diagnostic PC on page 6)
The DLC protocol cannot be installed on 64-bit Windows systems.
1. Please see the Product Release Notice for Enhanced Diagnostic Monitor v2.x, available on the Invensys
Global Customer Support (GCS) Web site, for detailed compatibility information.

Note For optimum display performance while using the 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.
Upgrade Information
Installing Enhanced Diagnostic Monitor version 2.4.0 will upgrade an existing Enhanced
Diagnostic Monitor 1.x or 2.x installation. The previous version will be automatically
uninstalled, but all user information will be retained, so you will not need to reconfigure your
user names, passwords, and security levels. Additionally, Standard Security will be enabled by
default. See Changing the Security Setting on page 20 for more information.
Note During the upgrade process, all event filtering settings are reset to their default values.
You will need to reconfigure your event filtering settings on a per-node basis prior to
starting event collection. For instructions, see Filtering the Event List on page 111.
If Enhanced Diagnostic Monitor versions 1.0 and 1.1 were both installed on the
diagnostic PC prior to installing Enhanced Diagnostic Monitor 2.4.0, one of the shortcuts
to these versions will remain on the Start > All Programs menu, even though the
applications were uninstalled. To remove the shortcut from the menu, right-click on the
shortcut and select Delete. When asked to confirm the deletion, click Delete Shortcut.
Do not re-install older versions of the Enhanced Diagnostic Monitor (1.0 and 1.1) after you have
installed 2.x.
Upgrading from Diagnostic Monitor 4.1 or Earlier

If you have previously installed Triconex Diagnostic Monitor version 4.1 or earlier (as part of a
TriStation 1131 installation), you do not need to keep it installed on your system.
The Enhanced Diagnostic Monitor can be installed on the same PC as Diagnostic Monitor 4.1
and earlier. However, we do not recommend running the two programs simultaneously.2
2. If both programs are installed, and you attempt to start Diagnostic Monitor 4.1 but it does not open,
the Enhanced Diagnostic Monitor may already be open. In this case, close the Enhanced Diagnostic
Monitor, and then try starting Diagnostic Monitor again.

Installing the Enhanced Diagnostic Monitor

This procedure explains how to install the Enhanced Diagnostic Monitor software. You must
have Windows administrator privileges to install the Enhanced Diagnostic Monitor. You do not
need to install the Enhanced Diagnostic Monitor on the same PC as TriStation 1131.
Before you start the Enhanced Diagnostic Monitor installation, make sure you have installed the
latest service packs and critical updates for your version of Windows. To look for recent
updates, visit the Microsoft Windows Update website.
If the .NET Framework is not already installed, setup will install it for you before installing the
Enhanced Diagnostic Monitor. If necessary, setup will also install Windows Installer v4.5 prior
to installing the .NET Framework. Depending on your PC’s configuration, Windows Installer
and .NET Framework installation can take several minutes, and may require you to restart your
PC in order to complete the installation process.
If you receive any errors during the .NET Framework installation, contact your system
administrator for assistance.
Note During installation, you will be asked if you want to change the NERC Security Banner
message text. This is optional; the message text can also be modified at any time after
installation. If you aren’t sure if you want to change the text, leave the default text as-is
during installation. See Customizing the Security Banner Text on page 13 for more
information.
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 or Remove Programs, and then click Add New Programs.
6 Click CD or Floppy, 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.

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 only for connecting to a Trident 1.x MP.
Installing the DLC protocol on a Windows XP, Windows Server 2003, or Windows Server 2008
(32-bit only) workstation is a 3-step process.
The DLC protocol cannot be installed on Windows 64-bit systems. As a result, you cannot
connect to a Trident 1.x MP on a Windows 64-bit system.
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.

Uninstalling the Enhanced Diagnostic Monitor

This procedure explains how to uninstall the Enhanced Diagnostic Monitor.
Manually uninstalling the Enhanced Diagnostic Monitor 2.4.0 will delete

CAUTION all existing user names, passwords, and security levels.
If you are upgrading from version 2.0—2.3 of the Enhanced Diagnostic

Monitor, and wish to maintain your existing user information, do not
manually uninstall the existing version. Installing the new version will
automatically uninstall the existing version for you, while also preserving
your user information for use with the new version. For more
information, see Upgrade Information on page 4.
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 or Remove Programs, and select Enhanced Diagnostic Monitor v2.4.0.
4 Click Change/Remove. Follow the on-screen instructions to confirm the deletion of the
selected program 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), 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.

Starting the Enhanced Diagnostic Monitor

A user name and password is required to open the Enhanced Diagnostic Monitor. Depending
on the current security setting, you may need to log in using your Windows user name and
password. See Changing the Security Setting on page 20 for more information about security
settings.
• If Standard Security is enabled, there is no limit on the number of times you can
attempt to enter your user name and password. This is the default setting after
installation.
• If Enhanced Security is enabled, the number of times you can attempt to enter your user
name and password is determined by your Windows domain setting.
For example, if your Windows domain setting is limited to three login attempts, after
three unsuccessful attempts to log in to the Enhanced Diagnostic Monitor, your user
account will be locked out. If this occurs, ask your network administrator to reset your
Windows account.
Note Only one instance of the Enhanced Diagnostic Monitor (or Diagnostic Monitor 4.x) can
be open at any one time. Do not use the Windows Run As command in an attempt to
simultaneously run more than one instance of the Enhanced Diagnostic Monitor, as
doing so may corrupt essential program files.
• Logging In for the First Time on page 9
• Logging In When Standard Security Is Enabled on page 10
• Logging In When Enhanced Security Is Enabled on page 10
• Logging In for the First Time When Enhanced Security Is Enabled on page 11
• Customizing the Security Banner Text on page 13
• Viewing User Access Logs on page 15
Logging In for the First Time

The first time you log in to the Enhanced Diagnostic Monitor after installation, Standard
Security is enabled. Use the default user name (MANAGER) and password (PASSWORD) to log
in.
When you log in using the default password, you are required to change the password
immediately upon login. This is to prevent unauthorized users from accessing the Enhanced
Diagnostic Monitor.
For additional security, you should create additional user names and passwords—including at
least two different level 01 users—before creating network configurations, and not allow
multiple users to access the Enhanced Diagnostic Monitor using the default user information.
See Creating and Managing Users on page 19 for more information.

Logging In When Standard Security Is Enabled

When Standard Security is enabled, you must use your Enhanced Diagnostic Monitor user
name and password to log in.
Procedure
1 On the Start menu, select Programs > Triconex > Enhanced Diagnostic Monitor 2.4.0.
The Login dialog box appears.
2 Enter your user name and password, and click OK.
Logging In When Enhanced Security Is Enabled

When Enhanced Security is enabled, you must use your Windows user name and password to
log in. Your user information will be authenticated against Windows Active Directory, as well
as the Enhanced Diagnostic Monitor user list.
If you are having problems logging in using your Windows user information, see Logging In for
the First Time When Enhanced Security Is Enabled on page 11.
Procedure
1 On the Start menu, select Programs > Triconex > Enhanced Diagnostic Monitor 2.4.0.
The Windows Login dialog box appears.
2 Enter your Windows user name (including domain, if necessary) and password, and
click OK.

Logging In for the First Time When Enhanced Security Is Enabled

If you are a new user, the first time you log in to the Enhanced Diagnostic Monitor when
Enhanced Security is enabled, you may need to log in twice:
• First, you need to enter your Windows user name and password, to authenticate
against the Windows domain.
• If Windows authentication is successful, you then need to enter your Windows user
name and Enhanced Diagnostic Monitor password (NOT your Windows password), to
authenticate against the Enhanced Diagnostic Monitor user list.
If both authentications are successful, all subsequent logins will require you to enter only your
Windows user name and password to access the Enhanced Diagnostic Monitor.
Troubleshooting Login Problems

The following are common problems you may encounter when trying to log in to the Enhanced
Diagnostic Monitor.
Problem Solution
The following error message This message appears when Enhanced Security is enabled,
appears: and you clicked OK in the Login dialog box without entering
“The parameter is incorrect.” your Windows user name and/or password.
When you click OK in the error message box, the Login dialog
box will appear again. Be sure not to leave the user name
and/or password field blank.
appears: and you do one of the following in the Login dialog box:
“Logon failure: unknown user • Enter a Windows user name that has not been added to
name or bad password.” the Enhanced Diagnostic Monitor user list.
• Enter an incorrect password.
In this case, the Enhanced Diagnostic Monitor is unable to
authenticate your user information with Windows.
When you click OK in the error message box, the Login dialog
box will appear again. Verify that you are trying to log in with
the correct Windows user name (including domain, if
necessary) and password.
User names and passwords are case-sensitive. Verify that the
CAPS LOCK key is not on when you enter your user
information.

Problem Solution
appears: and you enter a Windows user name that has not been added
“You are not authorized to open to the Enhanced Diagnostic Monitor user list.
this application because your When you click OK in the error message box, the Login dialog
user name was not found in the box will appear again. Verify that you are trying to log in with
application’s user list.” the correct Windows user name and password.
User names and passwords are case-sensitive. Verify that the
CAPS LOCK key is not on when you enter your user
information.
The following error message This message appears when Enhanced Security is enabled and
appears: you are trying to log in using a Windows “Guest” account.
“Logon failure: the user has not Windows “Guest” accounts are used to provide access to a
been granted the requested computer when you do not have a Windows user account on
logon type at this computer.” that computer. In order for you to be able to log in to
Enhanced Diagnostic Monitor with a “Guest” account, ask
your network or system administrator to do the following:
• Remove the “Guest” user from the Windows Local
Security Policy “Deny access to this computer from the
network” list.
• Enable the “Accounts: Guest account status” option in the
Windows Local Security Policy security options list.

Customizing the Security Banner Text

Each time you start the Enhanced
Diagnostic Monitor, a security banner
appears, advising you of the appropriate
use of the Enhanced Diagnostic Monitor.
If you are an administrator managing
Enhanced Diagnostic Monitor installations
in your organization, you may want to
customize the security banner text to reflect
your corporate policy, meet site-specific
needs, or be in compliance with North
American Electric Reliability Corporation
(NERC) Cyber Security standards.
Note For more information about the
NERC’s Cyber Security standards, a
set of sound security practices that, if properly implemented, can assist in securing
critical infrastructure from cyber security threats, see www.nerc.com.
The security banner text must be individually customized in each Enhanced Diagnostic Monitor
installation. However, once you modify the security banner text once, you can simply copy and
paste the text from one PC to another. An easy way to do this would be to create a temporary
text file with the security banner text in it, and place that file on the network, or on a portable
flash drive. You can then copy and paste the text from the file.
Also, the same security banner text can be used for other Triconex products that use the security
banner functionality. For example, if your organization’s security banner text is the same for all
Triconex products, you can use the same text for TriStation 1131 as you do for the Enhanced
Diagnostic Monitor.
The security banner text can be changed during Enhanced Diagnostic Monitor installation, or at
any time after installation using the procedure provided in this section.
You must have administrator privileges to change the security banner text.
• If Standard Security is enabled, you must be logged in to Windows as a user with
administrator privileges.
• If Enhanced Security is enabled, you must be logged in to the Enhanced Diagnostic
Monitor as a Windows user with administrator privileges.
Procedure
1 Make sure that all network node connections are closed.
2 On the Edit menu, click Modify Banner Message.
If the Modify Banner Message menu item is not enabled, you are not logged in to
Windows or the Enhanced Diagnostic Monitor with administrator privileges.
The Modify Banner Message dialog box appears.

3 Edit the security banner text as needed, and then click OK. The security banner text can
be a maximum of 2,100 characters.
Note You cannot have a blank security banner message; if you delete the existing text,
but do not enter new text, the default security banner message (“This system is
for use by authorized Safety System personnel only.”) will be displayed.
The next time you start the Enhanced Diagnostic Monitor, the customized text will
appear in the security banner.
Note If you receive an “Unable to save changes to the banner message” error message when
you attempt to save the security banner text, you may not have read/write access to the
location where the message text is stored. Contact Invensys Global Customer Support
for assistance. For contact information, see Technical Support on page vii.

Viewing User Access Logs

When Enhanced Security is enabled, the Enhanced Diagnostic Monitor keeps a log of all user
login attempts, whether they are successful or not. These access logs are required for compliance
with NERC Cyber Security standards.
Note For more information about the Enhanced Security option, see Changing the Security
Setting on page 20.
The Enhanced Diagnostic Monitor uses the Windows System Events Log to store the following
information about user login and logoff attempts:
• Successful login using Windows user name and password
• Login failure due to an incorrect Windows user name and/or password
• Login attempt cancelled by the user
• Login failure due to the user forgetting to enter their Windows user name and/or
password (this is referred to as an “incorrect parameter” error)
• Successful logoff (when the user closes the Enhanced Diagnostic Monitor)
You can view this log to determine if an unauthorized user is attempting to log in to the
Enhanced Diagnostic Monitor. You can also use this log as a troubleshooting tool when helping
a user who is having login problems.
Note If you are logged into Windows using a “Guest” account, you will be unable to view the
Windows System Events Log. For more information, see Microsoft Knowledge Base
Article 842209 (http://support.microsoft.com/kb/842209).
• Viewing the User Access Log In Windows Event Viewer on page 15
• Saving the User Access Log to a File on page 16
• Changing Event Logging Options on page 17
• Clearing the User Access Log on page 18
Viewing the User Access Log In Windows Event Viewer

This procedure describes how to view Enhanced Diagnostic Monitor user access information in
the Windows System Events Log using the Windows Event Viewer. You must be logged on to
Windows as an administrator to perform this procedure.
Procedure
1 On the Start menu, click Control Panel, and then double-click Administrative Tools.
2 Double-click the Event Viewer icon. The Windows Event Viewer opens.
3 In the console tree, click Application. Event information appears in the details pane.

4 In the details pane, click the Source column header to sort the events by application.
5 Look for Enhanced Diagnostic Monitor as the source type.
6 To view detailed information about a specific event, double-click the event.
Saving the User Access Log to a File

This procedure describes how to save the user access event information to a file. You must be
logged on to Windows as an administrator to perform this procedure.
When you save a log file, the entire log is saved, regardless of filtering options. You cannot save
a log file with just the events related to the Enhanced Diagnostic Monitor. Also, the sort order is
not retained when logs are saved.
Procedure
1 In the Windows Event Viewer, display the event log with the user access information
that you want to save to a file.
2 On the Action menu, click Save Log File As.
3 In File name, enter a name for the archived log file.

4 In Save as type, select a file format, and then click Save.

• If you save the log in the default format, you can re-open it in the Windows Event
Viewer. Logs saved in this format (.evt) retain the binary data for each event.
• If you save a log in text (.txt) or comma-delimited (.csv) format, you can re-open the
log in other programs, such as word processing or spreadsheet programs. Logs
saved in text or comma-delimited format do not retain the binary data.
Changing Event Logging Options

Using the Windows Event Viewer, you can set the maximum size of the log and specify whether
events are overwritten or stored for a certain period of time.
The default logging policy is that if a log is full, the oldest events are deleted to make room for
new events. Invensys recommends that you change this setting to ensure that user login event
information is not lost.
This procedure describes how to change event logging options using the Windows Event
Viewer. You must be logged on to Windows as an administrator to perform this procedure.
Procedure
3 In the console tree, right-click Application. The Application Properties dialog box
appears.
4 Do one or both of the following:

• To increase the maximum size of the event log file, enter the desired value (in KB) in
the Maximum log size field
• Select Do not overwrite events (clear log file manually).
5 Click OK to save your changes.

Clearing the User Access Log

When the Windows System Events Log reaches its maximum size, you will see the following
error message in the Enhanced Diagnostic Monitor:
The event log file is full. You must manually clear all events from the event log file before
new entries can be added.
This procedure describes how to clear the event log file so that you can continue collecting user
login event information. You must be logged on to Windows as an administrator to perform this
procedure.
Note Clearing the log file will clear ALL application event information, not just events related
to the Enhanced Diagnostic Monitor. Invensys highly recommends saving the file prior
to clearing it.
Procedure
3 In the console tree, right-click Application, and then select Clear all events.
4 When prompted to save the log before clearing it, click Yes.
5 Select the location where you want to save the file to, and click Save.
The file is saved to your selected location, and the current log file is cleared.

Creating and Managing Users

This section explains how to manage user access to Enhanced Diagnostic Monitor operations.
Multiple levels of access control help prevent unauthorized access to the Enhanced Diagnostic
Monitor.
• The application-level security setting defines the type of authentication used to identify
users upon login. Choose the security setting that is right for your implementation:
— Standard Security uses a simple user name / password scheme. This is the default
setting.
— Enhanced Security adds another layer of protection against unauthorized access by
requiring Windows domain user authentication.
• User security levels define what operations a user can perform while using the
Enhanced Diagnostic Monitor. 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. You are required to change the default level 01 user
password the first time you log in.
Once you have logged in for the first time, you should immediately add at least one more level
01 user. This ensures that if you forget the password for the default level 01 user, you’ll still be
able to log in as the secondary level 01 user, and have the ability to add or modify users, or
change the security setting.
Note If you forget the passwords for all your level 01 users, contact Invensys Global Customer
Support for assistance. For contact information, see Technical Support on page vii.
You should create a user account for each person who will be using the Enhanced Diagnostic
Monitor before you begin creating network configurations, and not allow multiple users to
access the Enhanced Diagnostic Monitor using the default level 01 user information.
You cannot make changes to user accounts or access levels while a node is open, even if it is not
connected.
• Changing the Security Setting on page 20
• Managing User Accounts on page 23
• Adding User Accounts on page 24
• Modifying User Accounts on page 26
• Recommended Rules for Passwords on page 27
• Changing the Security Level for Privileges on page 28
• Changing Security Level Names on page 31
• Other Permissions Affecting User Access on page 32

Changing the Security Setting

The Enhanced Diagnostic Monitor uses one of two application-level security settings: Standard
or Enhanced. You should choose the security setting you want to use before you begin creating
user accounts. You must be a level 01 user to change the security setting.
The security setting defines the type of authentication used to identify users upon login:
• Standard Security: When selected, a user name and password is required to open the
Enhanced Diagnostic Monitor. No other user authentication is required.
This is the default setting. If you used a version of the Enhanced Diagnostic Monitor
previous to version 2.4.0, this security setting is the same as the user name / password
login scheme used in previous versions.
• Enhanced Security: When selected, Windows and Enhanced Diagnostic Monitor user
authentications are required to log in. The user name for each Enhanced Diagnostic
Monitor user must be the same as the user’s Windows user name.
If you change the security setting from Standard to Enhanced, make sure
CAUTION that at least one level 01 user has a valid Windows user name before
closing the Enhanced Diagnostic Monitor. Failure to do so will prevent
you from opening the Enhanced Diagnostic Monitor again and/or
changing the security setting back to Standard.
This procedure describes how to change the Enhanced Diagnostic Monitor’s security setting.
Procedure
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.
3 On the Security Setting tab, select the setting you want to use: Standard Security or
Enhanced Security.

Note If both options are unavailable, you are not a level 01 user. You must be a level
01 user to change the security setting.
4 Click OK, and then do one of the following:
• If you downgraded the security setting from Enhanced to Standard, this procedure
is complete. Go to Managing User Accounts on page 23 to edit users as needed.
• If you upgraded the security setting from Standard to Enhanced, go to the next step.
5 When prompted, enter your Windows user name and password, and then click OK.
6 Do one of the following:

• If your Windows user name was previously added to the Enhanced Diagnostic
Monitor user list, and the Enhanced Diagnostic Monitor was able to successfully
authenticate your Windows user name and password, this procedure is complete.
Go to Managing User Accounts on page 23 to edit users as needed.
• If this is the first time you have upgraded the security setting from Standard to
Enhanced, and the Enhanced Diagnostic Monitor was able to successfully
authenticate your Windows user name and password, the Add User dialog box
appears so you can add yourself as a Windows user to the Enhanced Diagnostic
Monitor user list. Go to the next step.

7 Specify these properties in the Add User dialog box.
Property Action
Full Name Enter or change the user’s full name (for example, John Smith).
Description Enter or change the description for the user (for example, their job
title or function).
User Name You cannot change the user name, because it must be the same as the
user’s Windows user name.
Password Enter the user’s password. This is NOT the same as the user’s
Windows password. You should select a different password, unique
to the user’s Enhanced Diagnostic Monitor account. See
Recommended Rules for Passwords on page 27 for minimum
requirements.
Verify Password Enter the new password again for verification.
Security Level You cannot change the security level. Enhanced Security requires at
least one level 01 Windows user.

Managing User Accounts

This procedure explains how to manage user accounts, which includes creating, modifying, and
deleting an Enhanced Diagnostic Monitor user.
To view and manage user account information (including adding, modifying, or deleting user
names and passwords), you must have the following user privileges:
• Windows administrator privileges
• Security level 01, 02, or 03
• Add/Modify User privileges (see Changing the Security Level for Privileges on
page 28)
Even if you have the appropriate Enhanced Diagnostic Monitor user privileges, if you don’t
have Windows administrator privileges, you will be unable to make changes to user account
information. See your network administrator for more information about obtaining Windows
administrator privileges.
Note If Enhanced Security is enabled, a quick way to prevent a user from accessing the
Enhanced Diagnostic Monitor is to add their Windows user account to the Windows
Local Security Policy “Deny access to this computer from the network” list.
Procedure
3 Click the Users tab, and then perform one of these actions.

Command Action
New To create a new user, click New. For further instructions, see
Adding User Accounts on page 24.
Modify To change a user’s information, select a user in the list, and then
click Modify. For instructions, see Modifying User Accounts on
page 26.
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.
If Enhanced Security has ever been enabled (even if it is not the
current security setting), you cannot delete the last level 01
Windows user.
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 User Accounts

This procedure explains how to add Enhanced Diagnostic Monitor user accounts.
Note When Enhanced Security is enabled, the first time a newly-added user logs in, they need
to log in twice for authentication purposes. See Logging In for the First Time When
Enhanced Security Is Enabled on page 11 for more information.
Procedure
3 Click New. The Add User dialog box appears.

4 Specify these properties:
Property Action
Full Name Enter the user’s full name (for example, John Smith).
Description Enter a description for the user (for example, their job title or
function).
User Name Enter the ID to be used to log in to the Enhanced Diagnostic Monitor.
• If you are using Standard Security, user names can have a
maximum of 16 alphanumeric characters; spaces and special
characters are not allowed.
• If you are using Enhanced Security, the user name must be the
same as the user’s Windows user name, including domain
information, if necessary.
Password Enter the user’s password.
If you are using Enhanced Security, this is not the same as the user’s
Windows password. You should select a different password, unique
to the user’s Enhanced Diagnostic Monitor account.
See Recommended Rules for Passwords on page 27 for minimum
requirements.
Verify Password Enter the new 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.
Enhanced Security requires at least one level 01 Windows user.

Modifying User Accounts

This procedure explains how to modify Enhanced Diagnostic Monitor user accounts, including
changing user names or passwords.
Procedure
3 Click the name of the user whose account information you want to change, and then
click Modify. The Modify User dialog box appears.
4 Specify these properties:
Property Action
Full Name Change the user’s.name.
Description Change the user’s description.
User Name Change the ID to be used to log in to the Enhanced Diagnostic
Monitor. User names can have a maximum of 16 alphanumeric
characters; spaces and special characters are not allowed.
If Enhanced Security is enabled, you cannot change the user name,
because it must be the same as the user’s Windows user name.
Password Change the user’s password. See Recommended Rules for Passwords
on page 27 for minimum requirements.
Verify Password Enter the changed password again for verification.

Property Action
Security Level Change the security level for this user. Level 01 is the highest; level 10
is the lowest.
If you did not set the user’s security level to 01 when you first created
the user, you cannot increase the user’s level to 01. To do so, you must
first delete the existing user and then create a new user.
If the user whose information you are modifying is the only level 01
Windows user, you cannot change the security level. Enhanced
Security requires at least one level 01 Windows user. To change this
user’s level, assign another Windows user to level 01, and then try
changing this user’s level again.
Recommended Rules for Passwords

Invensys recommends configuring your Windows domain authentication settings to support
the following minimum requirements for passwords, as set forth in the NERC Cyber Security
standards. Passwords should:
• Be a minimum of six (6) characters.
• Consist of a combination of alpha, numeric, and special characters. Special characters
include the following:
! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~
• Include at least one number.
• Include at least one letter.
• Include at least one lower-case letter AND one upper-case letter.
• Include at least one special character.
• Be changed at least annually, or more frequently based on risk.
These rules will NOT be validated by the Enhanced Diagnostic Monitor when you enter or
change the user’s password, so it is up to you to ensure user passwords meet these
requirements. Invensys recommends you check the latest NERC Cyber Security standards
(available at www.nerc.com) for all the latest applicable password requirements.
If Enhanced Security is enabled, Windows passwords will be used. As a result, these password
rules should be enforced at the Windows domain / Active Directory level. See your network
administrator for more information about how to enforce requirements for Windows
passwords.
Note When Enhanced Security is enabled, all Enhanced Diagnostic Monitor passwords are
protected from unauthorized read or copy access because they are stored and protected
by Windows security mechanisms. This meets the NERC Cyber Security standards
regarding password security. However, when Standard Security setting is enabled, this
level of password protection is not provided.

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 single module or on all None
Clear (module and modules in a system, if they also have read/write
all) faults permissions to the module. Applies to both Tricon and
Trident controllers.
You must explicitly assign this privilege to a security
level if you want a user to be able to clear faults. By
default, users are not given this privilege, regardless of
their security level.
Note: Under normal operation, faults are cleared
automatically when the problem causing the fault
is fixed. The Clear Faults and Clear All Faults
commands 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 64.
Module: Allows the user to collect system events when connected Levels 01—05
Collect system to a node (controller). Applies to both Tricon and Trident
events controllers.
For more information, see Chapter 4, Collecting and
Viewing Events.

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, or a CM is installed in a Trident 2.x controller, 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 client access list. For more
information, see Other Permissions Affecting User Access on page 32.
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 or
CM, 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 Permissions 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 Tricon Communication Module (TCM) installed in your Tricon controller,
or a Communication Module (CM) installed in your Trident 2.x controller, access to the
controller via the Enhanced Diagnostic Monitor (using the TriStation protocol) can also
be controlled by the Port Write Enabled property3 or the client access list4.
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 or
2.x CM, they will be unable to perform the command.
For more information on configuring the TCM or 2.x CM client access list, or
enabling/disabling the Port Write Enabled property, see the TriStation 1131 Developer’s
Guide.
3. Selected TCM models only. Not available on the 2.x CM.

4. Selected TCM models and the 2.x CM only. See the TriStation 1131 Developer’s Guide for more
information.

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. 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 33
• Creating or Changing a Network Configuration on page 36
• Opening a Network Node on page 42
• Troubleshooting Connection Problems on page 43
• Configuring the Connection Retry Settings on page 44
Types of Network Configurations

A network configuration can include Tricon and/or Trident controllers on Ethernet networks
or serial links.
For detailed information and instructions on installing and configuring your Triconex controller
on a network, please see the appropriate Communication Guide for your controller.
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)
E F 01 E F 01 E F 01 E F 01 E F 01
AB CD
E F 01
AB CD
AB CD
AB CD
AB CD
AB CD
23
23
23
23
23
23
SERIAL 1 SERIAL 1
TX RX TX RX
NODE NODE NODE NODE NODE NODE
ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS ADDRESS
E F 01 E F 01 E F 01 E F 01 E F 01
AB CD
E F 01
AB CD
AB CD
AB CD
AB CD
AB CD
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
MODEL 8310
TX RX
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
POWER MODULE 3008 3008 TCM
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
Configuring for Redundancy (Tricon or Trident 2.x)

Invensys recommends the following redundant communications configuration to ensure
maximum availability and avoid a single point of failure:
• Install two network interface cards (NICs) in your diagnostic PC, and two TCMs or
CMs in the controller (this achieves media redundancy).
• Connect the Ethernet port on the primary NIC to the Left TCM or CM. Configure this as
your primary connection to the controller.
• Connect the Ethernet port on the secondary NIC to the Right TCM or CM. Configure
this as your secondary connection to the controller.
If communications on the primary connection (the Left TCM or CM) fail, the Enhanced
Diagnostic Monitor can automatically switch to this secondary connection.
See Creating or Changing a Network Configuration on page 36 for detailed information on
configuring the network connection to the Tricon or Trident 2.x controller. Also, see
Configuring the Connection Retry Settings on page 44 for information on configuring the
automatic switch to the secondary connection.

Serial Links
For Tricon or Trident 2.x, 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

PASS FAULT FAULT FAULT
FAULT FAULT ACTIVE FAULT FAULT FAULT

FAULT ACTIVE ACTIVE ACTIVE
ACTIVE ACTIVE FIRM ACTIVE ACTIVE ACTIVE

ACTIVE FIRM FIRM FIRM
MAINT1 MAINT1 MAINT1 MAINT1 MAINT1

MAINT1
MAINT2 NET 1 NET 1
MAINT2 MAINT2 NET 1 MAINT2 MAINT2 MAINT2 NET 1
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
E F 01
TS/TSAA
TS/TSAA
E F 01
TS/TSAA TS/TSAA TS/TSAA
E F 01
To DCS
AB CD
E F 01 E F 01 E F 01
AB CD
AB CD
AB CD
AB CD
AB CD
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
E F 01 E F 01
E F 01
AB CD
E F 01 E F 01 E F 01
AB CD
AB CD
AB CD
AB CD
AB CD
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 I/O TX TX RX
I/O TX I/O TX I/O TX TX RX TX RX
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
3008 3008 3008 TCM
3008 3008 3008 TCM TCM
4351 4351
4351 4351
TCMs TCMs
Diagnostic PC
Figure 2 Typical Multi-Point Serial Network with Tricon Controllers
Note When connecting the diagnostic PC to a Tricon Communication Module (TCM) or an

EICM via a serial cable, you must connect the serial cable to Serial Port 4 on the TCM or
EICM. When connecting the diagnostic PC to a Trident 2.x CM via serial cable, you must
connect the serial cable to Serial Port 3 on the CM. These are the only ports enabled for
serial communication via the TriStation protocol (used by the Enhanced Diagnostic
Monitor).
Tricon system events can be collected from an EICM when the diagnostic PC is
connected to the controller via a serial connection; however, event collection will be
significantly slower than when collecting events via an Ethernet connection.
You cannot collect Tricon system events from a TCM or NCM when the diagnostic PC
is connected to the controller via a serial connection. For more information on collecting
events, see Chapter 4, Collecting and Viewing Events.

Creating or Changing a Network Configuration

This section 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 a network connection)
• Type of TriStation connection (serial or network)
• UDP port numbers (for a network connection)
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.
You can configure up to 63 Tricon or Trident controllers in a single network configuration.
Nodes 1-31 may be configured as Tricon or Trident controllers. Because a maximum of 31 Tricon
controllers are supported, nodes 32-63 may be configured as Trident controllers only.
For example, you can configure 25 Tricon controllers and 35 Trident controllers, for a total of 60
nodes. But you cannot configure 35 Tricon controllers and 35 Trident controllers, as this exceeds
both the overall 63-node limit, AND the 31-node Tricon limit.
Note If 63 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.
• Adding or Changing a Tricon Controller on page 36
• Adding or Changing a Trident Controller on page 39
Adding or Changing a Tricon Controller

This section describes how to add a new Tricon controller node, or make changes to an existing
Tricon controller node, in a network configuration.
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.
Node Number Enter the node number of the controller (1-31).
Node Name Enter the node name of the controller.
Connection Type Select one of these options:
• Network for an Ethernet (TCP/IP) connection
• Serial for a serial (Modbus) connection
Primary IP For a Network connection, specify the IP address of the controller
Address to be monitored. The default is 192.168.1.n, where n is the node
number of the controller.
Primary For a Network connection, specify the UDP port to use for the
TriStation UDP Enhanced Diagnostic Monitor connection (via the TriStation
Port Number protocol) to a Tricon with a TCM installed. The default is 1502.
This must be the same value as the TriStation UDP Port Number
property in the TriStation 1131 TCM Setup dialog box. For more
information, see the TriStation 1131 Developer’s Guide.
Required only for a connection to a Tricon node with a TCM
installed.

Property Action
Management Enhanced Diagnostic Monitor’s connection to TCM
UDP Port communication status information. The default is 1510.
Number This must be the same value as the Management UDP Port
Number property in the TriStation 1131 TCM Setup dialog box.
For more information, see the TriStation 1131 Developer’s Guide.
For more information about viewing a TCM’s communication
status, see Monitoring Communication Status Information on
page 79.
Serial Port For a Serial connection, select the COM port on the diagnostic PC
which is connected to the controller.
Note The Controller Type, Node Number, and Node Name cannot be changed while
the node is open, even if you are not actively connected to the controller.
5 If you want to configure a secondary network connection for use when the primary
network connection is lost, specify the following optional properties.
Note The secondary network connection settings are used to connect to the controller
only after the primary connection has been lost. See Configuring the Connection
Retry Settings on page 44.
Property Action
Secondary IP Address Specify the secondary IP address of the controller to be
monitored.
Secondary TriStation Specify the secondary UDP port to use for the Enhanced
UDP Port Number Diagnostic Monitor connection (via the TriStation protocol) to
a Tricon with a TCM installed. The default is 1502.
Secondary Management Specify the secondary UDP port to use for the Enhanced
UDP Port Number Diagnostic Monitor’s connection to TCM communication
status information. The default is 1510.
Note Secondary connection settings are available only for the Network connection
type. You cannot configure a secondary connection for a serial connection.
7 Repeat steps 3–6 for each node you want to add or change.
8 On the File menu, click Save Network Configuration to save the XML file to the same
name and location (to replace an existing configuration).
You can also save the file to a new name and location by using the Save Network
Configuration As command on the File menu.
Note You must have write access to the directory where you are trying to save the
network configuration file. If you don’t have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

Adding or Changing a Trident Controller

This section describes how to add a new Trident controller node, or make changes to an existing
Trident controller node, in a network configuration.
Procedure
1 Verify that a network configuration is not currently open.
2 On the File menu, click New Network Configuration or Open Network Configuration.
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 Trident.
Node Number Enter the node number of the controller (1-63).
Node Name Enter the node name of the controller.
Connection Type Select one of these options:
• Main Processor 1.x for an Ethernet (DLC) connection to a Trident
1.x controller
• Network for an Ethernet (TCP/IP) connection
• Serial for a serial (Modbus) connection to a Trident 2.x controller

Property Action
Primary IP For a Network connection, specify the IP address of the controller to
Address be monitored. Each node has seven connection options:
• Left MP
• Middle MP
• Right MP
• Left CM - NET 1
• Left CM - NET 2
• Right CM - NET 1
• Right CM - NET 2
The default IP address is 192.168.255.n, where n is the node number
of the controller. The default IP address is for connection to the Left
MP only. You must use the default IP address the first time you
connect to the controller.
To use the default IP address, click the browse button, and in the
dialog box that appears, select the IP address for the node you are
configuring.
Note: The default IP address that initially appears (192.168.1.n)
cannot be used for Trident. You must browse for the correct
Trident default IP address as described above, or enter your
own IP address.
Your own IP addresses for other MP and CM modules

cannot be used for connecting to the controller until the
control program—with the IP address configuration—has
been downloaded to the controller at least once, using the
Download All command. For more information, see the
TriStation UDP Enhanced Diagnostic Monitor connection (via the TriStation
Port Number protocol) to a Trident 2.x with a CM installed. The default is 1502.
This must be the same value as the TriStation UDP Port Number
property in the TriStation 1131 CM Setup dialog box. For more
Required only for a connection to a Trident 2.x node with a CM
installed.
Management Enhanced Diagnostic Monitor’s connection to 2.x CM
UDP Port communication status information. The default is 1510.
Number This must be the same value as the Management UDP Port Number
property in the TriStation 1131 CM Setup dialog box. For more
For more information about viewing a 2.x CM’s communication
status, see Monitoring Communication Status Information on
page 79
Serial Port For a Trident v2.x Serial connection, select the COM port on the
diagnostic PC which is connected to the controller.

Property Action
MP Connection For a Trident 1.x Main Processor connection, select the main
processor which is connected to the diagnostic PC. The default is
Left.
NIC Index For a Trident 1.x Main Processor connection, enter the index position
of the network interface card in the diagnostic PC.
Note The Controller Type, Node Number, and Node Name cannot be changed while
the node is open, even if you are not actively connected to the controller.
5 If you want to configure a secondary network connection for use when the primary
network connection is lost, specify the following optional properties.
Note The secondary network connection settings are used to connect to the controller
only after the primary connection has been lost. See Configuring the Connection
Retry Settings on page 44.
Property Action
Secondary IP Address Specify the secondary IP address of the controller to be
monitored.
To use the default IP address, click the browse button, and
in the dialog box that appears select the node you are
configuring.
Secondary TriStation Specify the secondary UDP port to use for the Enhanced
UDP Port Number Diagnostic Monitor connection (via the TriStation protocol) to
a Trident 2.x with a CM installed. The default is 1502.
Secondary Management Specify the secondary UDP port to use for the Enhanced
UDP Port Number Diagnostic Monitor’s connection to 2.x CM communication
status information. The default is 1510.
Note Secondary connection settings are available only for the Network connection
type. You cannot configure a secondary connection for a serial or MP v1.x
connection.
7 Repeat steps 3–6 for each node you want to add or change.
8 On the File menu, click Save Network Configuration to save the XML file to the same
name and location (to replace an existing configuration).
You can also save the file to a new name and location by using the Save Network
Configuration As command on the File menu.
Note You must have write access to the directory where you are trying to save the
network configuration file. If you don’t have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

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 the same time; however, you can collect system
events only from one node at a time. For more information, see Chapter 4, Collecting and
Viewing Events.
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 36).
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 42.
• 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 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
• A CM is installed in the Trident 2.x and the CM 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.
When connected in read-only mode, you can only view system or module status. The following
operations are not allowed when connected in read-only mode:
• Collecting system events
• Clearing module faults
Note When connected in read-only mode due to a TCM or 2.x CM client access list permission
(read-only access via the TriStation protocol), you are allowed to collect system events
for a node. However, if the node is password-protected, you still must know the correct
password in order to collect events.
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
node that has a TCM installed. diagnostic PC has read-only or read/write access to the TCM
or or CM via the TriStation protocol. If the TCM or CM client
access list has been configured so that the IP address of
You cannot connect to a Trident the diagnostic PC is denied access to the TCM or CM via
2.x node that has a CM installed. the TriStation protocol, you will be unable to open the
node.
• Verify that the TriStation UDP Port Number configured
for the node matches the TriStation UDP Port Number
configured for the TCM or CM in TriStation 1131. If the
UDP port numbers are different, you will be unable to
connect to the node.
For more information about the TCM or CM access list, or the
UDP port number, see the TriStation 1131 Developer’s Guide.
You cannot connect to a Trident You must install the DLC protocol to be able to connect to a
1.x node when Main Processor is Trident 1.x MP. For instructions, see Installing the DLC
selected as the connection type. Protocol on the Diagnostic PC on page 6.

Configuring the Connection Retry Settings

This section describes how to configure the connection retry settings for Tricon and Trident
nodes.
If a connection to a 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 nodes in the network configuration.
You can also choose whether the Enhanced Diagnostic Monitor should switch to the secondary
connection (if configured), or if it should attempt to restore the primary connection.
Once the Enhanced Diagnostic Monitor has switched to the secondary connection, it will remain
connected until the secondary connection is lost. If the secondary connection is lost, the
Enhanced Diagnostic Monitor will attempt to restore the secondary connection either
indefinitely or for the number of times you define in the connection retry settings.
Note You can also manually attempt to restore the connection by double-clicking the node
name on the tree again to re-open the node.
The Enhanced Diagnostic Monitor displays messages in the Messages Pane for the following
connection-related occurrences:
• Connection lost, including the node number and the date / time the connection was
lost
• Connection restore attempts on the primary connection, including the node number,
date / time, IP address, and attempt number
• Connection restore attempts on the secondary connection, including the node number,
date / time, IP address, and attempt number
• Successful connection restoration, including the node number and the date / time the
connection was restored
Procedure
1 In the Network Configuration tree, double-click any node.
You do not have to be actively connected to the controller, but a node must be open.
2 On the Tools menu, select Communication Options.

3 Select what you want the Enhanced Diagnostic Monitor to do when the primary
connection is lost:
Property Description
Switch to Select this if you want the Enhanced Diagnostic Monitor to switch to
Secondary the secondary connection automatically when the primary connection
Connection has been lost.
You must have configured the secondary connection settings for the
node; see Creating or Changing a Network Configuration on page 36.
For a Trident 1.x node, or if the secondary settings for a Trident 2.x or
Tricon node have not been configured, the Enhanced Diagnostic
Monitor will not make any attempt to restore a lost connection. An
error message will appear in the Messages Pane if this occurs.
This is the default value.
Note: The Enhanced Diagnostic Monitor will switch to a secondary
connection only after the primary connection has been lost. It
will not switch to the secondary connection if the primary
connection has never successfully connected.
Restore Primary Select this if you want the Enhanced Diagnostic Monitor to attempt to
Connection restore only the primary connection.
Note The connection retry settings apply to all nodes in the network configuration. If
you have Trident 1.x nodes in your network configuration, we recommend
selecting Restore Primary Connection as the connection retry option to ensure
that the Enhanced Diagnostic Monitor will attempt to automatically restore a lost
connection. If you select Switch to Secondary Connection, and the connection to
a Trident 1.x node is lost, the Enhanced Diagnostic Monitor will not do anything,
requiring operator intervention to manually restore the connection.
4 Select how many times you want the Enhanced Diagnostic Monitor to attempt to restore
a lost connection:

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. The
default is 1.
If you don’t want the Enhanced Diagnostic Monitor to make any
connection attempts, enter 0 or leave the field blank.
5 Click OK to save your changes and close the dialog box.

Customizing Your Workspace

The Enhanced Diagnostic Monitor workspace can be easily customized to suit your needs. The
following are some of the ways you can change the workspace configuration:
• Showing or Hiding Window Panes on page 47
• Moving, Docking, and Floating Window Panes on page 48
• Maximizing, Restoring, and Resizing Windows on page 49
Note Changes you make to customize your workspace apply to your current session only. If
you close and re-open the Enhanced Diagnostic Monitor, your changes will not be
saved.
Showing or Hiding Window Panes

The Enhanced Diagnostic Monitor has two window panes that can be displayed or hidden
within the workspace.
• The Network Nodes Tree pane
• The Messages pane
Network
Nodes
Tree Pane
Messages
Pane

Showing or Hiding the Messages Pane

The Messages pane is hidden when you first open a node. To show or hide the Messages pane:
• On the View menu, click Messages, or click on the toolbar.

The Messages pane appears at the bottom of the Enhanced Diagnostic Monitor window.
See Viewing Data in the Messages Pane on page 76 for more information about the Messages
pane.
Showing or Hiding the Network Nodes Tree Pane

The Network Nodes Tree pane is hidden when you first open the Enhanced Diagnostic Monitor.
To show or hide the Network Nodes Tree pane:
• On the View menu, click Workspace, or click on the toolbar.

See Setting Up a Network Configuration on page 33 for more information about the Network
Nodes Tree pane.
Note The Network Nodes Tree pane appears automatically when you open a network
configuration file.
Moving, Docking, and Floating Window Panes

Both the Network Nodes Tree pane and the Messages pane can be moved and/or docked within
the workspace. By default, these panes are attached (docked) to the left side and bottom of the
workspace, respectively. You can move these to any location that is convenient for you.
• To move a window pane
Click the Drag Pane section (located in the top or left side of the
window pane) and then drag the window where you want it.
• To float a window pane
Click the Drag Pane section and then drag and drop the window at a random location in
the workspace.
• To dock a window pane
Docking a window means to attach it to an edge of the Enhanced Diagnostic Monitor
workspace. To do this, move the floating window pane by clicking in the title bar of the
window pane, drag it to the edge where you want to dock it, and then drop it.

Maximizing, Restoring, and Resizing Windows

The System Overview, Module Status, and Communication Status View windows can be
floating windows, or they can be maximized and expanded within the Enhanced Diagnostic
Monitor workspace.
If you only have one of these windows open, you may want to maximize the window to increase
its size and see more of the window at once.
• To maximize a window, click the button in the upper right corner of the window.
The window expands to fill the Enhanced Diagnostic Monitor workspace.
Maximized
Window
• To restore the window (make it a floating window), click the button in the upper
right corner of the window.
Floating
Window
See System Overview and Module Status Windows on page 53, and Monitoring
Communication Status Information on page 79, for more information about these windows.


2
Monitoring Controller Hardware
Overview 52
System Overview and Module Status Windows 53
Understanding External Faults 60
Understanding Internal Faults 62
Clearing Faults on All Modules 64
Monitoring Output Voter Diagnostics (OVD) 65
Monitoring Trident SDO OVD and Supervision Status 66
Displaying Firmware Versions 67

52 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, monitor the OVD and
supervision status of Trident supervised digital output modules, and display the firmware
version numbers for all types of modules.
For corrective actions (such as replacing a module with a spare), 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, a
module configuration window called the Module Status window, and a Communication Status
window. Multiple System Overview, Module Status, and/or Communication Status windows
can be open at once if you are connected to multiple nodes.
The System Overview and Module Status windows are refreshed continuously while you are
connected to and monitoring a controller.
Note When you start event collection, you can choose to stop refreshing information in the
System Overview window while events are being collected, speeding up the event
collection rate. (See Starting and Stopping Event Collection on page 107.) Once you stop
event collection, continuous controller status updates will automatically begin again.
For information about the Communication Status window, see Monitoring Communication
Status Information on page 79.
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.
System
Overview Tree Red icon for Green icon for
for selecting full chassis with chassis with
chassis display alarm on alarm off
The System Overview window can be a floating window or a maximized window. For more
information, see Customizing Your Workspace on page 47.

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 maximized window. For more information, see Customizing Your Workspace on page 47.
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.
The Module Status dialog box displays the following:
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.
Status Displays a message that describes the type of fault.
Point Faults Displays the number of each point with a fault condition.
Note When the Tricon is running in degraded (single or duplex) mode, faults occurring on the
channel (also known as a leg) of a module whose MP is missing will not be reported in
the Module Status dialog box. Additionally, the module’s status may be incorrectly
displayed in the System Overview window.
When an MP is missing, the Enhanced Diagnostic Monitor has no way to know about
faults happening on that channel of the controller. For example, if MP B is missing, faults
occurring on channel B of the modules in the system will not be reported in the
Enhanced Diagnostic Monitor. Once the missing MP is replaced, and the Tricon returns
to TMR mode, all faults on the missing MP will be correctly reported, and modules will
display correctly in the System Overview window.

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
The System Overview window can be a floating window or a maximized window. For more
information, see Customizing Your Workspace on page 47.
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.
The Module Status window—like the System Overview window—can be a floating window or
a maximized window. For more information, see Customizing Your Workspace on page 47.

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 and a Point Status tab (see Monitoring Trident SDO OVD and Supervision Status
on page 66 for more information about the Point Status tab).
For the main processors, the Module Status dialog box includes Left, Middle, and Right Module
tabs.
Each module 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

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.
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 button
in the Module Status dialog box. 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 button.
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 Invensys Global Customer Support (GCS) Center for
assistance. For contact information, see Technical Support on page vii.

Understanding External Faults 61
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 42.
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

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.

controller.

Understanding Internal Faults 63
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

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.
If you have not been assigned a user security level with the Clear (Module and All) Faults
privilege, you will be unable to clear faults on all modules. For more information, see Changing
the Security Level for Privileges on page 28.
Additionally, even if you have the appropriate user security level access, you also 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 42), 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, or a Trident 2.x with a CM installed, verify in TriStation
1131 that the IP address of the diagnostic PC has read/write access to the TCM or CM 2.x
via the TriStation protocol.
If the TCM or CM 2.x client access list has been configured so that the IP address of the
diagnostic PC has read-only access to the TCM or CM 2.x via the TriStation protocol, you
will be unable to clear all faults. For more information, see the TriStation 1131 Developer’s
Guide.

controller.
Procedure
1 Ensure that all faults have been identified and corrected, as described in Locating and
Correcting External Faults on page 61 and Locating Internal Faults on page 63.
2 For a Tricon, verify that the keyswitch is in the PROGRAM position by viewing the Key
Stop/Position property in the System Overview window.
If the keyswitch is not in the PROGRAM position, the Clear Faults on All Modules
command will be unavailable.
3 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) 65
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 and SDO modules in a controller.
Note While you can use the Enhanced Diagnostic Monitor to monitor the OVD status of SDO
points in the Trident (see Monitoring Trident SDO OVD and Supervision Status on
page 66), you cannot monitor the OVD status of DO points in the Trident. 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 Yellow
Label
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.

Monitoring Trident SDO OVD and Supervision Status

The Trident model 3411 Supervised Digital Output (SDO) module1 provides loop supervision
to field devices in fire and gas applications. 16 points are available; each point can be
independently configured.
This procedure explains how to monitor the supervision and output voter diagnostics (OVD)
status of Trident SDO modules and points.
Procedure
1 On the System Overview tree, expand a baseplate node, and then click a module to
display the Module Status window.
2 In the Module Status window, double-click an SDO module to open the Module Status
dialog box for the module.
3 Click the Point Status tab.
4 For each SDO point, review the following properties:
OVD The OVD status for the selected point. Can be
Running or Not Running.
Supervision The supervision status for the selected point. Can be
Running or Not Running.
1. The model 3411 SDO module is compatible only with Trident v2.1 and later systems. See the Planning
and Installation Guide for Trident v2 Systems for more information.

Displaying Firmware Versions 67
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 an Invensys Customer 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 76.
• 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 70
Viewing Controller Status 71
Monitoring and Changing the Scan Time 73
Monitoring and Changing the Memory Allocation 75
Viewing Data in the Messages Pane 76
Viewing Program Execution Times 78
Monitoring Communication Status Information 79

70 Chapter 3 Monitoring Controller Status
Overview
Controller status is monitored via the System Overview and Communication Status windows.
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 33.
• 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 33.
• Open the nodes you want to monitor. See Opening a Network Node on page 42.
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 71
Viewing Controller Status

This procedure explains how to view controller status in the System Overview window.
Information in the System Overview window is refreshed continuously while you are
connected to and monitoring a controller.
Note When you start event collection, you can choose to stop refreshing information in the
System Overview window while events are being collected, speeding up the event
collection rate. (See Starting and Stopping Event Collection on page 107.) Once you stop
event collection, continuous controller status updates will automatically begin again.
If you are connected to a Tricon node, a beep sounds once when a chassis alarm turns on.
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
Tricon/Trident Displays the system version of the connected controller.
Version Applicable to Tricon and Trident 2.x controllers only.
Note: The system version is not available for Trident 1.x
controllers. This property will display 0 when
connected to a Trident 1.x.
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.

Property Action
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 73).
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 73
Monitoring and Changing the Scan Time

Scan time is the time required by the controller to process the TriStation 1131 application on the
controller, which includes the following operations:
• Read inputs
• Execute the application
• Process communication messages (TriStation protocol, TSAA, Modbus, Peer-to-Peer,
etc.)
• Write outputs
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 from the input modules.
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.
• The requested scan time is the scan time specified in the
application running on the controller. This value is set in
the application’s TriStation 1131 project.
• The actual scan time is the actual length of time required
by the controller to complete the last scan. It is always equal
to or greater than the requested scan time.
Scan Surplus Displays the time that remains in a scan after the application
operations are completed.
A negative scan surplus means that scan overruns have
occurred, which can cause communication errors. To eliminate
scan overruns, increase the scan time.
To avoid communication errors, ensure the scan surplus is
positive.
Note If you chose to stop refreshing information in the System Overview window
during event collection, the scan time may not be up-to-date. (See Starting and
Stopping Event Collection on page 107.) Once you stop event collection, the scan
time will be updated.
4 If the poll time exceeds the scan time, or if the scan surplus is negative, use TriStation
1131 to adjust the scan time. See Changing the Scan Time Using TriStation 1131 on
page 74.

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 the 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 systems using model 3006/3007 Main Processors, the range is 20 to 500
milliseconds.
• For Tricon systems using model 3008 Main Processors, the range is 20 to 450
milliseconds.
• For Trident, the range is 10 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 75
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.

Viewing Data in the Messages Pane

The Messages pane displays information about diagnostic operations while you are connected
to a node. The Messages pane is hidden when you first open a node. To show or hide the
Messages pane, on the View menu, click Messages.
The Messages pane is a dockable window that can be moved anywhere within the Enhanced
Diagnostic Monitor workspace. See Customizing Your Workspace on page 47 for more
information.
Note System event information does not appear in the Messages pane. Event information is
displayed in the bottom pane of the System Overview, Module Status, or
Communication Status window. For more information, see Monitoring Communication
Status Information on page 79.
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.

Viewing Data in the Messages Pane 77
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 78.
Display Firmware Versions The firmware version numbers of all modules in a Tricon
Command chassis or Trident IOP. See Displaying Firmware Versions on
page 67.
Info: Event Filter Settings Reset to The Enhanced Diagnostic Monitor saves event log filtering
Default Values information in an XML file. If invalid information is found in
this file upon startup, all event log filtering settings are reset
to their default values in order to repair the XML file. In this
case, you will need to reconfigure any previously selected
event log filtering settings. See Filtering the Event List on
page 111.
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 43.
Error: Event Collection Stopped The maximum number of events was reached in the existing
event log file AND the hard drive that the event log file is
located on has 10% or less free space remaining. See
Maximum File Size on page 143.
Error: Unable to Create New Event The Enhanced Diagnostic Monitor was unable to create a new
Log File log file. Event collection was stopped. See Managing Event
Log Files on page 105.
Error: Unable to Write Events to the The event log file has become corrupted, or a problem with
Event Log File the hard drive is preventing the Enhanced Diagnostic
Monitor from being able to write to the selected file. Try
restarting the event collection session with a new event log
file. See Managing Event Log Files on page 105.
Info: Event Log File Full, New Log The maximum number of events was reached in the existing
File Created 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 143.
Error: Disk Space at 90% Capacity The hard drive that the event log file is located on has 10% or
less free space remaining. Event collection stops until free
space is increased. See Maximum File Size on page 143.
Warning: Disk Space at 80% The hard drive that the event log file is located on, or being
Capacity created on, has 20% or less free space remaining. See
Maximum File Size on page 143.
Note If the Messages pane is hidden when an error message is reported, Enhanced Diagnostic
Monitor will alert you to the error by automatically displaying the Messages pane.

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 Tricon controller with model 3006 Main Processors.
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 76.

Monitoring Communication Status Information

The Enhanced Diagnostic Monitor allows you to view and monitor real-time communication
status information, including network loading and traffic levels. Communication status
information is available for the following controllers:
• Tricon v10.3 or later controllers with a TCM installed
• Trident v2.0 or later controllers with a CM installed
Information that is actively being updated is shown in blue text in the Communication Status
window.
• When a zero (0) appears in the Value field, it means information is not available for the
selected item.
• When question marks (?) appear in the Value fields, it means either that the Enhanced
Diagnostic Monitor is unable to connect to the selected communication module, or that
communication to the selected communication module has been lost.
All counter values (such as number of messages, or number of errors) are cumulative, beginning
from when the communication module is powered on. Once the maximum value of
2,147,483,647 is reached, the counter will stop incrementing.
Note If a status value is a cumulative total (such as network CRC errors, or Peer-to-Peer
messages sent), it cannot be reset without physically removing the module from the slot.
When possible problems are detected in cumulative total values, Triconex recommends
reviewing the system event logs to determine when such problems occurred.
While monitoring communication status information, you can also:
• Actively collect system events (see Chapter 4, Collecting and Viewing Events).
• View continually updated controller status information (see Viewing Controller Status
on page 71).
However, the refresh rate for all functions will be reduced due to the increased system usage.
When you start event collection, you can choose to stop refreshing information in the
Communication Status window while events are being collected, speeding up the event
collection rate. (See Starting and Stopping Event Collection on page 107.) Once you stop event
collection, communication status updates will automatically begin again.
• Monitoring Tricon Communication Status Information on page 80
• Monitoring Trident Communication Status Information on page 88
• Saving Communication Status Information to a File on page 94

Monitoring Tricon Communication Status Information

Each TCM installed in the connected Tricon controller—up to four—can be monitored
separately, but not simultaneously. Communication status information is updated by the TCM
every second.
Note Communication status information is available only for model 4351B, 4352B, 4353, and
4354 TCMs installed in Tricon v10.3 and later systems. Model 4351, 4352, 4351A, and
4352A TCMs are not supported. OPC status information is available only for those
TCMs with an embedded OPC server (models 4353 and 4354).
• Viewing Tricon Communication Status Data on page 80
• Tricon Communication Status Information on page 83
Viewing Tricon Communication Status Data

This procedure describes how to connect to a Tricon controller and view communication status
information for a selected TCM.
Procedure
1 Connect to the node (controller) whose TCM communication status you want to view.
Note You must be connected to the node via a network connection. You cannot view
communication status information when connected to a node via a serial
connection. To change the connection type, see Creating or Changing a Network
Configuration on page 36.
2 In the System Overview tree, click Communication Status.
3 In the Communication Status window, select the TCM you want to view communication
status information for.
The module selection list includes only TCMs that are installed in the connected
controller. Modules installed in the left and right slots are listed individually, allowing
you to view status information for each slot separately.

Module
Selection
List
Status
List
Note The Communication Status window—like the System Overview window—can

be a floating window or a maximized window. For more information, see
Customizing Your Workspace on page 47.
4 In the status list, click the + next to the information node you want to view.
The section expands, displaying statistics for the selected node. For detailed descriptions
of each value contained in a node, see Tricon Communication Status Information on
page 83.
Only status information applicable to the selected module will be displayed. For
example, if the selected TCM does not support OPC, zeroes (0) will appear in the Value
column.
Note If you chose to stop refreshing communication status information during event
collection, the displayed status information may not be up-to-date. (See Starting
and Stopping Event Collection on page 107.) Once you stop event collection,
communication status information will begin updating again.

Troubleshooting Tricon Communication Status Connection Problems

The following are common problems you may encounter while trying to view TCM
communication status information.
Problem Solution
You don’t see the Module If the controller you are currently connected to does not support
Selection List in the communication status information, the Module Selection List will not
Communication Status appear in the Communication Status window.
window. Communication status information is available only for model 4351B,
4352B, 4353, and 4354 TCMs installed in Tricon v10.3 and later systems.
You cannot connect to the • Verify that you are connected to the node via a network connection.
selected TCM. Communication status information cannot be viewed when the
node is connected via a serial connection. For more information
about changing the network configuration type, see Adding or
Changing a Tricon Controller on page 36.
• Verify that the Management UDP Port Number configured for the
node matches the Management UDP Port Number configured for
the TCM in TriStation 1131. If the UDP port numbers are different,
you will be unable to view the communication status information.
For more information about the Management UDP port number,
see Adding or Changing a Tricon Controller on page 36.
The communication status • The connection to the controller has been lost. For additional
values have stopped troubleshooting tips, see Troubleshooting Connection Problems on
updating. page 43.
• You chose to stop refreshing communication status information
during event collection. (See Starting and Stopping Event
Collection on page 107.) Stop event collection to restart
communication status information updates.
All communication status The selected TCM is physically installed in the controller, but it has not
values are displayed as yet been configured in the downloaded application. Use TriStation 1131
question marks (?) instead to configure the TCM and then download the application to the
of actual values. controller.

Tricon Communication Status Information

The following tables provide detailed information about the communication status data
provided in each section.
Performance Status
Performance status information provides data about the overall performance of the TCM.
Percent idle The TCM’s current idle percentage, based on the previous 15 seconds.
Free memory The percentage of free memory available on the TCM.
Network Status
Network status information provides data about communications on each of the TCM’s
network ports—NET 1 and NET 2.
Link status Indicates the link status of the NET 1 or NET 2 port on the TCM.
• 1 = Link Up
• 0 = Link Down
If the port is not connected to a network, a question mark (?) is displayed.
Receiving Indicates that the TCM is receiving messages via the NET 1 or NET 2 port.
messages • 1 = RX OK
• 0 = RX Not OK
If the port is not connected to a network, a question mark (?) is displayed.
CRC errorsa The total number of CRC errors that have been detected on the NET 1 or
NET 2 port. Increases each time a message with a bad CRC is received.
Framing errors The total number of framing errors (excluding CRC errors) that have been
detected on the NET 1 or NET 2 port.
Collisionsb The total number of collisions that have been detected on the NET 1 or
NET 2 port.
Transmit errors The total number of transmit errors (excluding collisions) that have been
detected on the NET 1 or NET 2 port.
a. A Cyclic Redundancy Check (CRC) is a procedure used to check for errors in data transmission. A CRC
error occurs when the data being sent cannot be verified.
b. A collision occurs when one or more devices attempt to send data to the TCM at the same time. When
collisions are encountered, the TCM will send back a request to try sending the data again.

OPC Status
OPC status information provides data about the health and activity of the TCM’s embedded
OPC server. If the selected TCM does not have an embedded OPC server, all values in this
section appear as zeroes (0).
Number of active The current number of active OPC clients. Increases each time a new
clients OPC client connects; decreases each time an established OPC client
disconnects. A maximum of 10 clients can be connected to the OPC
server at any one time.
Number of The current number of OPC items currently subscribed to the OPC
subscribed DA Data Access (DA) server. Increases each time a new item is
subscribed; decreases each time an item is unsubscribed.
Number of writes DA The total number of OPC DA writes performed. Increases each time
a new OPC DA write occurs.
Number of updates The total number of DA points that have been updated. Increases
DA each time a new DA point is updated.
Number of DA The current number of DA groups that have been established.
groups Increases each time a new group is established; decreases each time
an established group is removed. A maximum of 100 DA groups
may be established.
Number of A&E The current number of client subscriptions to the OPC Alarms and
subscribed Events (A&E) server. Increases each time a new subscription is
made; decreases each time an existing subscription is unsubscribed.
Number of A&E The total number of A&E acknowledgements that have occurred.
acknowledgements Reserved for future use (not applicable to Tricon v10.3 systems).
Number of A&E The total number of A&E events that have occurred.
events
Number of disabled The current number of A&E disabled events. Increases each time an
A&E events A&E event is disabled; decreases when an event is re-enabled.
TSAA Status
TSAA status information provides data about the TSAA server running on the TCM.
Number of active clientsa The current number of active TSAA clients. Increases each
time a new TSAA client connects; decrements each time an
established TSAA client disconnects.
Number of CRC errors The total number of CRC errors received by the TSAA
server. Increases each time a message with a bad CRC is
received.
Number of messages received The total number of messages received by the TSAA
server.

Number of bad messages The total number of messages with a formatting error
received received by the TSAA server.
Number of write messages The total number of write commands received by the
received TSAA server.
Number of write messages The total number of write commands rejected by the TSAA
rejected server.
Seconds TSAA has been idlea The number of seconds the TSAA server has been idle. Idle
seconds are counted from the time of the last activity on
the TSAA server to the current time.
a. Even though the SOE Recorder uses TSAA to connect to the TCM, these variables will not update to
reflect the connection or disconnection, or seconds idle, of the SOE Recorder as a TSAA client.
Modbus TCP Status

Modbus TCP status information provides data about each of the TCM’s Modbus TCP ports.
Model 4351B and 4352B TCMs have 16 ports; model 4353 and 4354 TCMs have 4 ports.
Port Connected Provides the current connection status for the selected port.
• 1 = Modbus connection established
• 0 = Modbus connection does not exist.
Number of valid The total number of good messages that have been received by the
messages selected port. A good message is one received without an error.
Number of bad The total number of bad messages that have been received by the
illegal messages selected port. A bad message is one with an invalid Modbus function
code or a CRC error.
Number of rejects The total number of reject messages that have been sent or received by
received or sent the selected port.
Number of The number of seconds the selected port has been idle. Idle seconds are
seconds port has counted from the time of the last activity on the port to the current
been idle time.
Number of The total number of timeouts that have occurred on the selected port.
timeouts
Number of The total number of connection requests that have been received by the
connections selected port.
Number of The total number of Modbus TCP connections rejected by the selected
connections port.
rejected

Modbus Serial Status

Modbus Serial status information provides data about each of the TCM’s serial Modbus ports
(1–4).
Number of valid The total number of good messages that have been received by the
messages selected port. A good message is one received without an error.
Number of bad The total number of bad messages that have been received by the
illegal messages selected port. A bad message is one with an invalid Modbus function
code.
Number of CRC The total number of CRC errors that have been detected on the
errors selected port.
Number of rejects The total number of reject messages that have been sent or received by
received or sent the selected port.
Number of seconds The number of seconds the selected port has been idle. Idle seconds
port has been idle are counted from the time of the last activity on the port to the current
time.
Number of The total number of broadcast messages received by a selected port.
broadcasts received
Number of The total number of timeouts that have occurred on the selected
timeouts Modbus Master port.
Peer-to-Peer Status
Peer-to-Peer status information provides data about the Peer-to-Peer network established on
one or both of the TCM’s network ports (NET 1 and NET 2). 31 nodes are available on each port.
Number of CRC The total number of Peer-to-Peer CRC errors that have been detected
errors on NET 1 or NET 2.
Number of The total number of Peer-to-Peer messages that have been received on
messages received NET 1 or NET 2.
Number of The total number of Peer-to-Peer messages that have been sent from
messages sent NET 1 or NET 2.
Active (Per Node) Indicates that Peer-to-Peer communication with the selected node has
been successfully established on NET 1 or NET 2.
• 1 = Active
• 0 = Inactive
This value displays a zero (0) if Peer-to-Peer communication is not
configured for the selected node or port.

Timeout (Per Node) Indicates that Peer-to-Peer communication with the selected node has
timed out (no response within 30 seconds) on NET 1 or NET 2.
• 1 = Timeout has occurred
• 0 = No timeout (status OK).
This value displays a question mark (?) if Peer-to-Peer communication
is not configured for the selected node or port.
Printer Status
Printer status information provides data about the printer connected to the TCM’s printer port.
Printer is connected Provides the current connection status for the printer port.
• 1 = connection established
• 0 = connection does not exist
Number of bytes used The total number of bytes used in the print buffer. Set to zero
when the buffer is empty (no pending print jobs).
Number of bytes available The total number of bytes available for use in the print buffer.
Set to zero when the print buffer is full.
Number of connections The total number of connections to the printer port that have
been established.
TriStation Status
TriStation status information provides data about connections—network and serial—to the
TCM via the TriStation protocol.
Number of CRC errors The total number of CRC errors that have been detected on
the TriStation interface (serial or network).
Number of messages received The total number of messages received on the TriStation
interface (serial or network).
Number of active connections The current number of active connections to the TriStation
interface (serial or network). Increases when a new client
connects to the TriStation interface; decreases when an
established client disconnects.

Monitoring Trident Communication Status Information

Each CM installed in the connected Trident 2.x controller—up to two—can be monitored
separately, but not simultaneously. Communication status information is updated by the CM
every five seconds.
Note Communication status information is available only for Trident 2.x controllers.
• Viewing Trident Communication Status Data on page 88
• Trident Communication Status Information on page 90
Viewing Trident Communication Status Data

This procedure describes how to connect to a Trident controller and view communication status
information for a selected Trident 2.x CM.
Procedure
1 Connect to the node (controller) whose CM communication status you want to view.
Note You must be connected to the node via a network connection using the CM’s IP
address. You cannot view communication status information when connected to
a node via a serial connection, or when connected over the network via the MP’s
IP address. See Adding or Changing a Trident Controller on page 39 for more
information.
2 In the System Overview tree, click Communication Status.
3 In the Communication Status window, select the CM you want to view communication
status information for.
The module selection list includes only CMs that are installed in the connected
controller. Modules installed in the left and right slots are listed individually, allowing
you to view status information for each slot separately.
Module
Selection
List
Status
List

Note The Communication Status window—like the System Overview window—can

be a floating window or a maximized window. For more information, see
Customizing Your Workspace on page 47.
4 In the status list, click the + next to the information node you want to view.
The section expands, displaying statistics for the selected node. For detailed descriptions
of each value contained in a node, see Trident Communication Status Information on
page 90.
Note If you chose to stop refreshing communication status information during event
collection, the displayed status information may not be up-to-date. (See Starting
and Stopping Event Collection on page 107.) Once you stop event collection, the
communication status information will begin updating again.
Troubleshooting Trident Communication Status Connection Problems

The following are common problems you may encounter while trying to view Trident 2.x CM
communication status information.
Problem Solution
You don’t see the Module If the controller you are currently connected to does not
Selection List in the support communication status information, the Module
Communication Status window. Selection List will not appear in the Communication Status
window.
Communication status information is available only for
Trident v2.0 and later systems.
You cannot connect to the Do the following:
selected CM. • First, verify that you are connected to the node via a
network connection. Communication status information
cannot be viewed when the node is connected via a serial
connection.
• Next, verify that you are connected to the node via the
CM’s IP address, not the MP’s IP address. You must use
the Trident CM’s IP address as the primary or secondary
connection IP address in order to view communication
status information.
• Finally, verify that the Management UDP Port Number
configured for the node matches the Management UDP
Port Number configured for the CM in TriStation 1131. If
the UDP port numbers are different, you will be unable to
view the communication status information.
For more information about configuring the connection to the
Trident, see Adding or Changing a Trident Controller on
page 39.

Problem Solution
The communication status • The connection to the controller has been lost. For
values have stopped updating. additional troubleshooting tips, see Troubleshooting
Connection Problems on page 43.
• You chose to stop refreshing communication status
information during event collection. (See Starting and
Stopping Event Collection on page 107.) Stop event
collection to restart communication status information
updates.
All communication status values The selected CM is physically installed in the controller, but it
are displayed as question marks has not yet been configured in the downloaded application.
(?) instead of actual values. Use TriStation 1131 to configure the CM and then download
the application to the controller.
Trident Communication Status Information

The following tables provide detailed information about the communication status data
provided in each section.
Performance Status
Performance status information provides data about the overall performance of the CM.
Percent idle The CM’s current idle percentage, based on the previous 15 seconds.
Free memory The percentage of free memory available on the CM.
Network Status
Network status information provides data about communications on each of the CM’s network
ports—NET 1 and NET 2.
Link status Indicates the link status of the NET 1 or NET 2 port on the CM.
• 1 = Link Up
• 0 = Link Down.
If the port is not connected to a network, a question mark (?) is
displayed.
Receiving messages Indicates that the CM is receiving messages via the NET 1 or NET 2
port.
• 1 = RX OK
• 0 = RX Not OK.
If the port is not connected to a network, a question mark (?) is
displayed.

CRC errorsa The total number of CRC errors that have been detected on the NET
1 or NET 2 port. Increases each time a message with a bad CRC is
received.
Framing errors The total number of framing errors (excluding CRC errors) that
have been detected on the NET 1 or NET 2 port.
Collisionsb The total number of collisions that have been detected on the NET 1
or NET 2 port.
Transmit errors The total number of transmit errors (excluding collisions) that have
been detected on the NET 1 or NET 2 port.
a. A Cyclic Redundancy Check (CRC) is a procedure used to check for errors in data transmission. A CRC
error occurs when the data being sent cannot be verified.
b. A collision occurs when one or more devices attempt to send data to the CM at the same time. When
collisions are encountered, the CM will send back a request to try sending the data again.
TSAA Status
TSAA status information provides data about the TSAA server running on the CM.
Number of active clientsa The current number of active TSAA clients. Increases each
time a new TSAA client connects; decrements each time an
established TSAA client disconnects.
Number of CRC errors The total number of CRC errors received by the TSAA
server. Increases each time a message with a bad CRC is
received.
Number of messages received The total number of messages received by the TSAA server.
Number of bad messages The total number of messages with a formatting error
received received by the TSAA server.
Number of write messages The total number of write commands received by the TSAA
received server.
Number of write messages The total number of write commands rejected by the TSAA
rejected server.
Seconds TSAA has been idlea The number of seconds the TSAA server has been idle. Idle
seconds are counted from the time of the last activity on the
TSAA server to the current time.
a. Even though the SOE Recorder uses TSAA to connect to the CM, these variables will not update to
reflect the connection or disconnection, or seconds idle, of the SOE Recorder as a TSAA client.

Modbus TCP Status

Modbus TCP status information provides data about each of the CM’s four Modbus TCP ports.
Port Connected Provides the current connection status for the selected
port.
• 1 = Modbus connection established
• 0 = Modbus connection does not exist.
Number of valid messages The total number of good messages that have been
received by the selected port. A good message is one
received without an error.
Number of bad illegal messages The total number of bad messages that have been received
by the selected port. A bad message is one with an invalid
Modbus function code or a CRC error.
Number of rejects received or The total number of reject messages that have been sent or
sent received by the selected port.
Number of seconds port has The number of seconds the selected port has been idle. Idle
been idle seconds are counted from the time of the last activity on
the port to the current time.
Number of timeouts The total number of timeouts that have occurred on the
selected port.
Number of connections The total number of connection requests that have been
received by the selected port.
Number of connections rejected The total number of Modbus TCP connections rejected by
the selected port.
Modbus Serial Status

Modbus Serial status information provides data about each of the CM’s serial Modbus ports (1–
3).
Number of valid messages The total number of good messages that have been
received by the selected port. A good message is one
received without an error.
Number of bad illegal messages The total number of bad messages that have been received
by the selected port. A bad message is one with an invalid
Modbus function code.
Number of CRC errors The total number of CRC errors that have been detected
on the selected port.
Number of rejects received or The total number of reject messages that have been sent or
sent received by the selected port.

Number of seconds port has The number of seconds the selected port has been idle.
been idle Idle seconds are counted from the time of the last activity
on the port to the current time.
Number of broadcasts received The total number of broadcast messages received by a
selected port.
Number of timeouts The total number of timeouts that have occurred on the
selected Modbus Master port.
Peer-to-Peer Status
Peer-to-Peer status information provides data about the Peer-to-Peer network established on
one or both of the CM’s network ports (NET 1 and NET 2). 63 nodes are available on each port.
Number of CRC The total number of Peer-to-Peer CRC errors that have been
errors detected on NET 1 or NET 2.
Number of messages The total number of Peer-to-Peer messages that have been received
received on NET 1 or NET 2.
Number of messages The total number of Peer-to-Peer messages that have been sent from
sent NET 1 or NET 2.
Active (Per Node) Indicates that Peer-to-Peer communication with the selected node
has been successfully established on NET 1 or NET 2.
• 1 = Active
• 0 = Inactive
This value displays a zero (0) if Peer-to-Peer communication is not
configured for the selected node or port.
Timeout (Per Node) Indicates that Peer-to-Peer communication with the selected node
has timed out (no response within 30 seconds) on NET 1 or NET 2.
• 1 = Timeout has occurred
• 0 = No timeout (status OK)
This value displays a question mark (?) if Peer-to-Peer
communication is not configured for the selected node or port.
Printer Status
Printer status information provides data about the printer connected to the CM’s printer port.
Printer is connected Provides the current connection status for the printer port.
• 1 = connection established
• 0 = connection does not exist.

Number of bytes used The total number of bytes used in the print buffer. Set to zero
(0) when the buffer is empty (no pending print jobs).
Number of bytes available The total number of bytes available for use in the print buffer.
Set to zero (0) when the print buffer is full.
Number of connections The total number of connections to the printer port that have
been established.
TriStation Status
TriStation status information provides data about connections—network and serial—to the CM
via the TriStation protocol.
Number of CRC errors The total number of CRC errors that have been detected on
the TriStation interface (serial or network).
Number of messages received The total number of messages received on the TriStation
interface (serial or network).
Number of active connections The current number of active connections to the TriStation
interface (serial or network). Increases when a new client
connects to the TriStation interface; decreases when an
established client disconnects.
Saving Communication Status Information to a File

You can save a snapshot of the communication status data to a file for later review.
Procedure
1 Right-click anywhere in the communication status list and then select one of the
following:
• Copy All Items to Clipboard: Copies status information from all nodes in the
communication status list, even if the information is not currently visible in the
status list.
• Copy Selected Items to Clipboard: Copies only the currently selected item. If a node
is selected, status information from all child nodes is also copied. If a single status
item is selected, only that one value is copied.
Status information is copied to the clipboard in simple text format.
2 Open a new document in the application you want to paste the information into, such as
Notepad or Microsoft Word.
3 Press CTRL+V to paste the communication status information, and then format it as
necessary.

4
Collecting and Viewing Events
Overview 96
Interpreting System Events 97
Interpreting the Board Address Display Format 101
Opening the Events and Events Summary Panes 103
Managing Event Log Files 105
Starting and Stopping Event Collection 107
Changing the Default Event Collection Settings 109
Controlling Event Visibility 111
Viewing an Existing Event Log File 119
Exporting an Event Log File 120
Generating Event and Alarm Data Reports 122

96 Chapter 4 Collecting and Viewing Events
Overview
This section explains how to collect and view system diagnostic events. Collecting events
provides you with real-time information about a fault or other error that is occurring on your
controller. Event collection also provides you with a history of errors that you can send to
Customer Support for assistance in troubleshooting problems.
Events can be viewed as they are being collected, or you can save the collected events to a file
without viewing them. Events are saved to event log files (.tce or .tde). Summary information
about the event log file currently being viewed is displayed in the Events Summary pane.
If you choose to view system events as they are collected, events are also displayed in the bottom
half of the System Overview, Module Status, and Communication Status windows, in the
Events pane.
Events
Summary
Pane
Events
Pane
Before you can collect events, you must complete these steps:
• Connect the diagnostic PC to the network. See Types of Network Configurations on
page 33.
• Create a network configuration which includes node specifications for the controllers
whose events you want to collect, or open an existing network configuration. See
Setting Up a Network Configuration on page 33.
• Open the nodes you want to collect events for. See Opening a Network Node on
page 42.

Interpreting System Events

During event collection, all 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.
• Event Severity Levels on page 97
• Event List Information on page 98
• Events Summary Information on page 99
• Important Information About Event Retention on page 99
Event Severity Levels

Tricon 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.
Trident events are color-coded according to their severity, as follows:
Color Severity Description

Blue Information Message is for informational purposes only.
Green Minor A problem with a field device or field wiring, or a problem or
error that does not require immediate action.
Pink Major Important information about a system-level fault that has
occurred on the Trident system.
Black Dangerous A fault that could lead to loss of control of an output if a
second fault occurs on the same module. Also known as an
Output Voter fault. Applies only to output modules.
Red Fatal A fatal error that has caused the Trident to run in a degraded
(Duplex or Single) mode. Immediate action should be taken
to return the Trident to TMR mode.

Event List Information

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.
Note: The event time is saved in the time zone that is currently
configured on the diagnostic PC. Before collecting events, you
should be sure that the diagnostic PC’s time zone is the same as
the time zone in which the controller is located, to ensure
accurate reporting of event times. Also, if the diagnostic PC’s
time zone needs to be changed, stop event collection, change the
time zone, and then start event collection again. Time zone
changes made during event collection will not be reflected in the
current event log file.
Class Indicates the system component (firmware) where the event originated
from. For example, class “ETSX” indicates the event originated from the
Tricon Main Processor.
See Appendix E, Tricon and Trident Event Classes for more detailed
information.
Code The unique message identifier. Each class of messages has a set of unique
message codes.
Leg The main processor channel (leg) the event occurred on. A, B, or C.
Board The address of the board (module) the event occurred on. See
Interpreting the Board Address Display Format on page 101 for more
information about 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.

Events Summary Information

The following information is provided in the Events Summary pane:
Event Log The current status of the event log being displayed in the Events pane.
Status 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 67.
• 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 The node number of the controller the events being displayed were
Node collected from.
Event File The full path and file name for the event log file being displayed.
Name
Events The number of events in the current event log file that match the current
Matching Filter filter settings. Updated only when events are being viewed in the Events
Pane.
Total Events The total number of events in the event log file. This may be greater than
the number of events matching the filter. Updated only when events are
being viewed in the Events Pane.
Begin Event The date and time of the first event in the event log file.
Time
End Event Time The date and time of the last event in the event log file.
Event The status of the event collection session.
Collection • When events are actively being collected, no message is shown.
Status
• When the event collection session is open, but the controller is not
generating any events, the following message appears: “Event
collection in progress. Waiting for next event.”
Important Information About Event Retention

The following sections describe how and when events are retained in the controller’s buffer
during event collection.
Tricon Event Retention

If you are connecting to the Tricon through a TCM (except for models 4351 and 4352), 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.
However, if you are connecting to the Tricon through another communication module, such as
a model 4351/4352 TCM, an NCM, or an EICM, events are not retained in a buffer.
• Once collected, the events are purged from the system. Collected events that are not
saved to a file prior to exiting the Enhanced Diagnostic Monitor will be lost. You
cannot recover events that were collected, but not saved.
collection session, none of the previously collected events will be available.
In all cases, if there is a loss of power to the system, all events will be lost, regardless of which
communication module is installed in the Tricon.
Trident Event Retention

If you are connecting to a Trident 2.x via the CM or MP, all system events are retained in the
controller’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.
collection session, some of the events that were collected previously will be collected
again.
• If the connection to the controller is lost, events that occurred during the time the
Enhanced Diagnostic Monitor was not connected to the controller will be retrieved
once event collection resumes.
If you are collecting events from a Trident 1.x controller, system events are removed from the
controller’s internal buffer as they are collected. When you have finished collecting events, you
must save the event log file for the event collection session, as you will not be able to retrieve
those events again.
• Once collected, the events are purged from the system.
collection session, none of the previously connected events will be available.
• If the connection to the controller is lost, events that occurred during the time the
Enhanced Diagnostic Monitor was not connected to the controller cannot be retrieved.
In all cases, if there is a loss of power to the system, all events will be lost, regardless of which
Trident controller you are connected to.

Interpreting the Board Address Display Format 101
Interpreting the Board Address Display Format

The board address provided for each event in the event log file identifies the location of a
module installed in a Tricon or Trident controller. This section describes how to interpret the
board address display, which is different for Tricon and Trident controllers.
• Interpreting and Changing the Tricon Board Address Display Format on page 101
• Interpreting the Trident Board Address Display Format on page 102
Interpreting and Changing the Tricon Board Address Display Format

For Tricon, you can select how you want board addresses to be displayed in the event log files.
The board address display format can be changed as often as needed, and at any time during
event collection or event log viewing.
Note For information on choosing the modules whose events you want to see in the event list,
see Configuring the Tricon Board Address Event Filter on page 113.
Chassis.slot is the default format, and is recommended for most users because it is the easiest to
understand. In this format, board addresses are provided as decimal values, where the character
to the left of the decimal is the chassis number, and the characters to the right of the decimal is
the logical slot location. For example, the board address 2.4L refers to chassis 2, logical slot 4
Left.
The hexadecimal format is recommended only for advanced users. 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.
For a visual reference of Tricon chassis and slot locations, see Appendix C, Tricon Chassis and
Slot Reference.
Tricon Board Address Display Format Exceptions

• In some cases, board addresses are provided as physical slot locations, rather than
logical slot locations. Usually, this occurs when viewing event log files created with
previous versions of the Enhanced Diagnostic Monitor or Diagnostic Monitor.
Board addresses provided as physical slot locations use the following format: x.yP,
where x is the chassis number, y is the physical slot, and P indicates the address is a
physical slot board address. For example, a board address of 9.8P indicates a physical
address of chassis 9, slot 8.
• If a board address displays with a question mark (?) for the slot location (such as 1.?),
the Enhanced Diagnostic Monitor was unable to translate the board address because of
a mismatch between the physical chassis hardware and the chassis type downloaded in
the TriStation project.

Change the board address display format to hexadecimal, and then use the conversion
tables provided in Appendix C, Tricon Chassis and Slot Reference, to manually translate
the board address.
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 the board address
display format, but the System Overview, Module Status, or Communication Status
window for the node must be open.
2 On the View menu, select Event, and then select one of the following options.
Display Board Address in Select to display board addresses in hexadecimal format
Hex Mode Command for all chassis types.
Display Board Address in Select to display board addresses in chassis.slot format,
High-Density Mode for a high-density Tricon chassis. This is the default
CommandView menu > setting.
Event
Display Board Address in Select to display board addresses in chassis.slot format,
Low-Density Mode for a low-density or enhanced low-density Tricon
Command chassis.
Note Slot locations in low-density chassis are different than those in high-density
chassis. To ensure accurate reporting of board addresses, be sure to select the
chassis.slot format corresponding to your Tricon chassis type. For more
information about chassis types, see Appendix C, Tricon Chassis and Slot
Reference.
Interpreting the Trident Board Address Display Format

The board address provided for each event in the event log file identifies the location of a
module installed in a Trident IOP. You cannot change the board address display format for
Trident.
• For I/O modules, the format is IOP.baseplate.slot. In this format, board addresses are
provided as decimal values. For example, the board address 01.04.L refers to IOP 1,
baseplate 4, Left slot.
• For MP and CM modules, the format is MP.slot or CM.slot. For example, the board
address MP.M refers to the Middle MP, and the board address CM.R refers to the Right
CM.
For a visual reference of Trident baseplate and slot locations, see Appendix D, Trident Baseplate
and Slot Reference.
Note For information on choosing the modules whose events you want to see in the event list,
see Configuring the Trident Board Address Event Filter on page 115.

Opening the Events and Events Summary Panes 103
Opening the Events and Events Summary Panes

When you first connect to a node, the Events and Events Summary panes are not visible. You
can control which of these panes are visible in the System Overview, Module Status, and
Communication 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.
• Maximize the System Overview window (see Customizing Your Workspace on
page 47).
• 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.
4 Click and drag the bottom edge of the System Overview, Module Status, or
Communication Status window up to decrease the size of the window and provide a
larger viewing area for the Events and Events Summary panes.
Note See Customizing Your Workspace on page 47 for more information about customizing
the Enhanced Diagnostic Monitor workspace to suit your needs.

Managing Event Log Files 105
Managing Event Log Files

During event collection, system events are saved to either a Tricon event log file (.tce) or a
Trident event log file (.tde).
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 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.
Note You must have write access to the directory where you are trying to create the new event
log file. If you don’t have access to this directory, select a different location, or contact
your system administrator to obtain write access to the desired location.
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. Total paths longer than 260 characters are not permitted.

Managing Event Log File Size

The Max Events Per Log File property controls the maximum number of events that are saved
to a single 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 109.
When an event log file reaches the maximum number of events during event collection, the
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 Tricon events in the
event log file events.tce, the 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 and Stopping Event Collection 107
Starting and Stopping 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 or Trident node at a time; you cannot collect events
for multiple controller nodes simultaneously.
When you start event collection, you can choose whether or not communication, module, and
chassis status information should continue to be updated while event collection is taking place
on a selected node. Updating status information while collecting events reduces the refresh rate
for all functions due to the increased system usage, and event collection will be slower.
If the connection to the controller is lost during event collection, and the Enhanced Diagnostic
Monitor is able to automatically restore the connection (see Configuring the Connection Retry
Settings on page 44), events will be appended to the current event log file when event collection
resumes.
In most cases, you cannot collect events when connected in read-only mode. For more
information, see Connecting in Read-Only Mode on page 42.
You cannot start event collection if an existing event log file is open for viewing.
Note The Enhanced Diagnostic Monitor can collect 50,000 Tricon system events from a TCM
in approximately 10-20 minutes (depending on network traffic and connection speed).
However, when the diagnostic PC is connected to an EICM via a serial connection, event
collection will be significantly slower.
Starting Event Collection

This section describes how to manually start event collection.
Procedure
1 Close any open event log files. See Locating and Closing Open Event Log Files on
page 119.
2 Connect to the node (controller) you want to collect events from.
• For Tricon, you can be connected to the node via a network connection to the TCM
or NCM, or via a serial connection to the EICM.
• For Trident 2.x, you can be connected to the node via a network connection to the
MP or CM, or via a serial connection to the CM.
To change the connection type, see Creating or Changing a Network Configuration on
page 36.
3 On the Events menu, click Start Collecting Events.
If the Start Collecting Events command is unavailable, an event log file is still open.
Close the event log file and then repeat this step.
4 When prompted to select an event log file, do one of the following:

• 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.
Note You must have write access to the directory where you are trying to create or
save the event log file. If you don’t have access to this directory, select a different
location, or contact your system administrator to obtain write access to the
desired location.
5 When prompted to continue collecting communication and controller status
information while events are being collected, do one of the following:
• Click Yes if you want to continue collecting controller status information (in the
System Overview window) and communication status information (in the
Communication Status window) while collecting events. The refresh rate for all
functions will be reduced due to the increased system usage, and event collection
will be slower.
• Click No if you want to collect events only. Information in the System Overview
and Communication Status windows will not be updated while events are being
collected, increasing the rate of event collection. Once you stop event collection,
communication and controller status updates will automatically begin again.
System event collection begins. A progress bar appears at the bottom of the Enhanced
Diagnostic Monitor window to indicate that events are being retrieved.
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 Controlling Event Visibility on page 111 and Modifying the Event Exclusion List on
page 118.
If you’ve started collecting events, but you don’t see the event list in the window, you need to
open the Events pane. See Opening the Events and Events Summary Panes on page 103.
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 the Enhanced Diagnostic Monitor.
To manually stop event collection:

• On the Events menu, click Stop Collecting Events.

Changing the Default Event Collection Settings 109
Changing the Default Event Collection Settings

Event collection settings can be customized to suit your needs at any time. Each node in a
network configuration has its own set of event collection settings, so that you can have different
settings for different nodes. Changes made to the default settings apply only to the node
currently being viewed when you access the Event Options dialog box.
Procedure
change the default settings for.
You do not have to be actively connected to the node to change event collection settings,
but the System Overview, Module Status, or Communication 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/Trident 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). This setting applies
only when you choose to view events as they are being collected.

Default Log File Enter the path where event log files will be saved. The default is:
Directory C:\...My Documents\Triconex\Enhanced Diagnostic
Monitor 2.4.0\.
You must have write access to this location. If you don’t have write
access, you will be unable to save event log files to this location. If
necessary, contact your system administrator to obtain write access
to the desired location.
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 events in an event log file is reached.
Max Events Per Enter the maximum number of events to save to a single log file, in
Log File 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
size of an event log file based on the selected number of maximum
events per file. This property is read-only.
Note: The actual file size may differ significantly from this
estimate. View the Windows file properties for the event
log file after event collection to view the actual size.
See Managing Event Log File Size on page 106 for more
information about how the Enhanced Diagnostic Monitor handles
event log files when they reach their maximum 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–5 for each node, and
then also do one of the following:
• Make a change on either the Event Filters tab or Event Exclusion tab.
• Change the Auto Scroll setting on the General Tricon/Trident Options tab.

Controlling Event Visibility

This section describes how to use event filtering options and the event exclusion list to control
which events are visible in the Events pane. Event filters and the exclusion list are applicable
both during event collection and while you are viewing an event log file.
Topics include:
• Filtering the Event List on page 111
• Configuring the Board Address Event Filter on page 113
• Modifying the Event Exclusion List on page 118
Filtering the Event List

Events can be filtered by any combination of time, severity, MP leg, chassis/IOP, or
slot/baseplate.
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 most event collection
settings, but the System Overview, Module Status, or Communication Status window
for the node must be open.
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
Tricon 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 channels (legs) whose system events you want
to see in the list (A, B, or C).
All channels are selected by default.
Board Available only when events are actively being connected, or an existing
Address event log file is open for viewing.
Filter When selected, board address filtering is enabled, so that only events
from selected chassis/IOPs and slots/baseplates are included in the
event list.
Click Select to choose the chassis/IOPs and slots/baseplates whose
events you want to see in the event list, or to view the existing
chassis/IOP and slot/baseplate filtering settings. For detailed
instructions, see Configuring the Board Address Event Filter on
page 113.
When cleared, board address filtering is disabled, so that events from all
chassis/IOPs and slots/baseplates are included in the event list.
The default is cleared (board address filtering is disabled).
Note: Board address filtering settings are not saved, and must be
reconfigured for each new event collection session or each time
an existing event log file is opened.
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–3 for each node, and
then also do one of the following:
• Make a change on either the Event Filters tab or Event Exclusion tab.
• Change the Auto Scroll setting on the General Tricon/Trident Options tab.

Configuring the Board Address Event Filter

When you start an event collection session or open an existing event log file, all events from all
chassis/IOPs and slots/baseplates are included in the event list (the board address filter is
disabled). Once you have started event collection or opened an existing file, you can then choose
the specific chassis/IOPs and slots/baseplates whose system events you want to see in the event
list.
The board address filter applies only to the current event collection session, or the event log file
currently being viewed. Once you stop event collection and/or close the event log file, the board
address filter configuration is discarded. When you start a new event collection session, or open
another event log file, you will need to reconfigure the board address filter.
Note Even if you open an existing event log file that you previously configured a board
address filter for, the settings were not saved, and you will need to reconfigure the filter.
• Configuring the Tricon Board Address Event Filter on page 113
• Configuring the Trident Board Address Event Filter on page 115
Configuring the Tricon Board Address Event Filter

By default, all chassis and slots are selected for inclusion in the event list.
Procedure
monitor.
2 Start event collection, or open an existing event log file.
3 On the Events menu, select Options.
The Event Options dialog box appears.
4 Click the Tricon Event Filters tab.
5 Under Chassis and Slots, select the Board Address Filter check box.
6 Click Select. The Chassis and Slot Selection dialog box appears.
A blue ‘X’ appears in the check boxes of the chassis and slots whose system events will
be included in the event list. By default, all chassis and slots are selected.

Note The chassis and slot tree includes nodes only for the chassis that are configured
in the Tricon system that events are currently being collected from, or were
previously collected from (if you are viewing an existing log file). The number of
slots per chassis depends on whether the chassis is a low-density chassis or a
high-density chassis.
• To view all possible chassis in a system (15 chassis, with 16 slots per chassis),
regardless of whether or not they are (or were) configured in the actual system,
select the Select All check box. Clear the check box to return to the default chassis
and slot tree.
• To include a chassis or slot in the event filter, select the check box. Selecting a
chassis automatically selects all slots in the chassis.
• To exclude a chassis or slot from the event filter, clear the check box. Excluding a
chassis automatically excludes all slots in the chassis.
Note Clearing the Board Address Filter check box on the Tricon Event Filters tab disables
chassis and slot filtering, so that events from the modules in all chassis and slots are
included in the event list, regardless of the selections made in the Chassis and Slot
Selection dialog box. However, as long as you have not stopped event collection and/or
closed the event log file, your chassis and slots filter configuration is saved, so that you
can re-enable filtering without having to reconfigure your filter.

Tips for Tricon Chassis and Slot Filtering

• Select the Tricon check box to select all chassis and all slots at once.
• To view events for all slots in a selected chassis:
— Clear the Tricon check box. This automatically clears the check boxes for all chassis.
— Then, select the chassis check box for the chassis whose events you want to include.
All slots in the chassis are selected by default when you select the chassis check box.
For example, to view events for all slots in chassis 12, select the Chassis 12 check box.
• To view events for selected slots in a chassis:
— Clear the chassis check box. This clears the check boxes for all slots in that chassis.
— Expand the tree node for the selected chassis.
— Then, select the individual check boxes for the slots whose events you want to
include in the event list.
• Once you have selected the chassis and slots you want included, click Close to save
your changes and return to the Event Options dialog box.
Note To select how board addresses are displayed in the event list, see Configuring the Tricon
Board Address Event Filter on page 113. For chassis slot location diagrams, see
Appendix C, Tricon Chassis and Slot Reference.
Configuring the Trident Board Address Event Filter

By default, all IOPs and baseplates, in addition to all MPs and CMs, are selected for inclusion in
the event list.
Procedure
1 In the Network Configuration tree, double-click the Trident node (controller) you want
to monitor.
2 Start event collection, or open an existing event log file.
4 Click the Filters tab.
5 Under Address, select the Board Address Filter check box.
6 Click Select. The IOP and Baseplate Selection dialog box appears.
A blue ‘X’ appears in the check boxes of the IOPs and baseplates whose system events
will be included in the event list. By default, all IOPs and baseplates are selected.
A node for the main processors (MPs) and communication modules (CMs) in the Trident
system is also included, in addition to the IOP nodes.

Note The IOP and baseplate tree includes nodes only for the IOPs that are configured
in the Trident system that events are currently being collected from, or were
previously collected from (if you are viewing an existing log file).
• To include an IOP or baseplate in the event filter, select the check box. Selecting an
IOP automatically selects all baseplates in the chassis.
• To exclude an IOP or baseplate from the event filter, clear the check box. Excluding
a IOP automatically excludes all baseplates in the IOP.
Note Clearing the Board Address Filter check box on the Filters tab disables IOP and baseplate
filtering, so that events from the modules in all IOPs and baseplates are included in the
event list, regardless of the selections made in the IOP and Baseplate Selection dialog
box. However, as long as you have not stopped event collection and/or closed the event
log file, your IOPs and baseplates filter configuration is saved, so that you can re-enable
filtering without having to reconfigure your filter.

Tips for Trident IOP and Baseplate Filtering

• Select the Trident check box to select all IOPs and all baseplates, including all MPs and
CMs, at once.
• To view events for all baseplates in a selected IOP:
— Clear the Trident check box. This automatically clears the check boxes for all
MPs/CMs and IOPs.
— Then, select the IOP check box for the IOP whose events you want to include. All
baseplates in the IOP are selected by default when you select the IOP check box.
For example, to view events for all baseplates in IOP 1, select the IOP 1 check box.
• To view events for selected baseplates in an IOP:
— Clear the IOP check box. This clears the check boxes for all baseplates in that IOP.
— Expand the tree node for the selected IOP.
— Then, select the individual check boxes for the baseplates whose events you want to
include in the event list.
• Once you have selected the IOPs and baseplates you want included, click Close to save
your changes and return to the Event Options dialog box.
Note For a typical baseplate and slot location diagram, see Appendix D, Trident Baseplate
and Slot Reference.

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,
but the System Overview, Module Status, or Communication Status window for the
node must be open.
3 Click the 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 119
Viewing an Existing Event Log File

The Enhanced Diagnostic Monitor allows you to open existing event log files from past event
collection sessions, so that you can review historical events as needed.
You can open an existing event log file without being actively connected to a node. This allows
you to review past events 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 63
open event log files (only one event log file can be opened per node; 63 nodes are available).
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.
If a node is actively collecting events, you cannot open an existing event log file, even on a
different node. You must stop event collection before you can open an existing event log file.
Procedure
1 If you are currently collecting events from a node, stop event collection. See Stopping
Event Collection on page 108.
2 In the Network Configuration tree, double-click any node.
You do not have to be actively connected to a node to view an existing event log file, but
the System Overview, Module Status, or Communication Status window for the node
must be open before you can continue.
3 On the Events menu, select Open Event File.
4 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 event list in the window, you need to open the Events pane.
See Opening the Events and Events Summary Panes on page 103.
5 Use the event filtering options to customize the event view to your specific needs. See
Controlling Event Visibility on page 111.
Locating and Closing Open Event Log Files

All open event log files must be closed before you can start a new event collection session.
Procedure
1 On the Window menu, select Cascade.
All open node windows are arranged for easy viewing.
2 Click on a node window, and then select Close Event File from the Events menu. You do
not need to close the node window.
3 Repeat step 2 for each node with an open event log file.

Exporting an Event Log File

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 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, Module Status, or Communication Status window for
a node must be open.
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.
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
SEVERITY Text 15
LEG Text 1
BOARD (Tricon) or LOGICAL (Trident) Text 5
MESSAGE Text 255

Exporting an Event Log File 121
Opening an Exported 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.

Generating Event and Alarm Data Reports

This section describes how to generate event and alarm data reports. Event data reports are
generated from previously saved event log files. Alarm data reports are generated from alarm
information obtained from the currently connected controller.
These reports are generated and displayed in the Crystal Reports viewer, which is installed with
the Enhanced Diagnostic Monitor. They can be printed and searched. You can also export the
report to a variety of formats, which can be saved to disk or sent to an email address.
• Generating Event Data Reports on page 122
• Generating Alarm Data Reports on page 124
• Exporting Report Data on page 126
Generating Event Data Reports

Event data reports can be generated only from a previously saved event log file that has been
opened for viewing. You cannot generate a report from 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 generate
a report from all events in a file, be sure to remove all filtering options before generating the
report.
Note Event data reports should be thought of as snapshots of a selected event log file. They
are not designed to be filtered or sorted. If you need filtering and/or sorting capabilities,
you should export the file instead of generating a report. See Exporting an Event Log File
on page 120.
When you generate a report, it is saved to a temporary location. Each time you generate the
same report type again, even from a different event log file, it will be saved in the same
temporary location, with the same file name, overwriting a previously generated report. If you
want to save the report for future viewing, you must export the report data to a file (see
Exporting Report Data on page 126).
The default event data report file names are:
• EventReport_Tricon
• EventReport_Trident
Procedure
1 In the Network Configuration tree, double-click a node that is not actively collecting
events.
You do not have to be actively connected to a node to generate an event data report, but
the System Overview, Module Status, or Communication Status window for a node
must be open.

3 Browse to locate the event log file you want to generate a report from, and then click
Open.
The list of events saved in the file appears in the Events pane.
4 Verify that the desired filtering settings are selected. To generate a report from all events
in a file, be sure to remove all filtering options. See Filtering the Event List on page 111.
5 On the Reports menu, select Events.
The report is generated and opens automatically in the Crystal Reports viewer window.
Note If you select Events and Diagnostic Alarms on the Reports menu, a single report
with both event data and alarm data will be generated. However, you must be
connected to a controller to generate a report with alarm data information. See
Generating Alarm Data Reports on page 124 for more information.
6 Perform any of the following tasks in the report viewer.
Command Action
Print Click to print the report being viewed.
Command
Export Report Click to export the report data to a file. For further
Command instructions, see Exporting Report Data on page 126.

Command Action
Refresh Click to refresh the display, which re-loads event data to
Command the report.
Size of view Type or select a percentage to change the size of the report
view.
Search Text Click to search for text in the report.
Command
7 To save the report for archival purposes or for future viewing, go to Exporting Report
Data on page 126.
Generating Alarm Data Reports

Alarm data reports are generated from the currently connected controller. They contain
information about the current overall system status, as well as the status of each configured
module.
Note An alarm data report should be thought of as a snapshot of the controller’s status at one
specific moment in time. It does not provide a history of the controller’s alarm status.
When you generate a report, it is saved to a temporary location. Each time you generate the
same report type again, even from a different controller, it will be saved in the same location,
with the same file name, overwriting a previously generated report. If you want to save the
report for future viewing, you must export the report data to a file (see Exporting Report Data
on page 126).
The default alarm data report file names are:
• DiagReport_Tricon
• DiagReport_Trident
Procedure
1 Connect to the node (controller) you want to collect alarm information for. See Opening
a Network Node on page 42 for detailed instructions.
2 On the Reports menu, select Diagnostic Alarm.
The report is generated and opens automatically in the Crystal Reports viewer window.

Note If you select Events and Diagnostic Alarms on the Reports menu, a single report
with both event data and alarm data will be generated. However, you must be
viewing an event log file to generate an event data report. See Generating Event
Data Reports on page 122 for more information.
3 Perform any of the following tasks in the report viewer.
Command Action
Print Click to print the report being viewed.
Command
Export Report Click to export the report data to a file. For further
Command instructions, see Exporting Report Data on page 126.
Refresh Click to refresh the display, which re-loads event data to
Command the report.
Size of view Type or select a percentage to change the size of the report
view.
Search Text Click to search for text in the report.
Command
4 To save the report for archival purposes or for future viewing, go to Exporting Report
Data on page 126.

Exporting Report Data

This procedure explains how to export report data. You can export a report to a variety of file
formats (including .pdf, .doc, and .xls), and can save the exported data to a disk or send it to
someone via email.
Procedure
1 Generate an event or alarm data report, as explained in Generating Event Data Reports
on page 122 or Generating Alarm Data Reports on page 124.
The report opens automatically in the Crystal Reports viewer window.
2 On the report viewer toolbar, click the Export Report button .
3 Specify these properties in the Export dialog box.
Property Action
Format Select the file format. The default is PDF.
Destination Select the destination as either Disk file or Microsoft Mail.
The default is Disk.
4 Click OK to continue.
Depending on the format, additional information—such as the characters to use to
separate and delimit a file—may be requested.

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.
This setting applies only when you choose to view events as they are being collected.
The default is selected (auto scroll enabled).
Applies To
Event list
Locations
• Events menu > Options command > Event Options dialog box > General Tricon/Trident
Options tab
• Set Events Options button > Event Options dialog box > General Tricon/Trident Options
tab

128 Appendix A Commands and Properties
Board Address Filter

The Board Address Filter property is an event filtering option that allows you to restrict the
visible event list to only those events that occur on the modules in the selected chassis/IOPs and
slots.
This property is available only when events are actively being connected, or an existing event
log file is open for viewing.
When enabled, events for modules in other chassis/IOPs and slots/baseplates will still be
collected, but only events occurring on the modules in the selected chassis/IOP will appear in
the event list.
When disabled, events for modules in all chassis/IOPs and slots/baseplates will appear in the
event list, regardless of the chassis/IOP and slot/baseplate filter configuration.
Board address filtering is disabled by default.
Applies To
Event list
Locations
• Events menu > Options command > Event Options dialog box > Event Filters tab
• Set Events Options button > Event Options dialog box > 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

129
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. This command is available only when the keyswitch
is in the PROGRAM position.
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 64.
You must have the appropriate user security level to use this command. For more information,
see Changing the Security Level for Privileges on page 28.
Applies To
Modules, fault flags
Location
Commands menu
Close Event File Command

The Close Event File command closes the 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
Event list
Location
Events menu
Close Network Configuration Command

The Close Network Configuration command closes an open network configuration.
Applies To
Location
Network Node 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 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.

It also allows you to choose whether the Enhanced Diagnostic Monitor should switch to the
secondary connection (if configured), or if it should attempt to restore the primary connection.
Applies To
Tricon and Trident 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.
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 1.x for an Ethernet (DLC) connection to a Trident 1.x controller. This is
the default.
• Network for an Ethernet (TCP/IP) connection.
• Serial for a serial (Modbus) connection to a Trident 2.x controller.
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

131
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
Copy All Items to Clipboard

The Copy All Items to Clipboard command copies all available communication status
information and places it on the clipboard.
Applies To
Communication status data
Location
Communication Status window > right-click in status list
Copy Selected Items to Clipboard

The Copy Selected Items to Clipboard command copies selected communication status
information and places it on the clipboard.
Applies To
Communication status data
Location
Communication Status window > right-click in status list

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 event log files.
The default is: C:\...My Documents\Triconex\Enhanced Diagnostic Monitor 2.4.0\
You must have write access to this location. If you don’t have write access, you will be unable
to save event log files to this location. If necessary, contact your system administrator to obtain
write access to the desired location.
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
Event list
Locations
Options tab
tab

133
Delete Command
The Delete command allows you to remove a node from a network configuration.
Applies To
Network Nodes tree, nodes, network configurations
Locations
Diagnostic Alarms Command

The Diagnostic Alarms command generates an alarm data report from the currently connected
controller.
Applies To
Tricon and Trident controllers
Locations
Reports menu
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 Board Address in Hex Mode Command

The Display Board Address in Hex Mode command changes the board address displayed in
Tricon event log files to the hexadecimal format.
The Tricon board address display format can be changed as often as needed, and at any time
during event collection or event log viewing.
The hexadecimal format is recommended only for advanced users. 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.

Applies To
Tricon event list
Locations
View menu > Event
Display Board Address in High-Density Mode Command

The Display Board Address in High-Density Mode command changes the board address
displayed in Tricon event log files to the chassis.slot format, for high-density chassis.
Slot locations in low-density chassis are different than those in high-density chassis. To ensure
accurate reporting of board addresses, be sure to select the chassis.slot format corresponding to
your Tricon chassis type.
Applies To
Tricon event list
Locations
View menu > Event
Display Board Address in Low-Density Mode Command

The Display Board Address in Low-Density Mode command changes the board address
displayed in Tricon event log files to the chassis.slot format, for low-density or enhanced low-
density chassis.
Slot locations in low-density chassis are different than those in high-density chassis. To ensure
accurate reporting of board addresses, be sure to select the chassis.slot format corresponding to
your Tricon chassis type.
Applies To
Tricon event list
Locations
View menu > Event

135
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 Invensys 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, and the security setting to be changed.
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
Event list
Locations
Enhanced Security
The Enhanced Security property sets the application-level security setting to Enhanced.
When selected, Windows and Enhanced Diagnostic Monitor user authentications are required
to log in.
See also Standard Security on page 157.
Applies To
User security
Location
Permissions menu > Edit Users > Permissions dialog box > Security Setting tab

137
Events Command
The Events command generates an event data report from the event log file currently being
viewed.
Applies To
Event list
Locations
Reports menu
Events and Diagnostic Alarms Command

The Events and Diagnostic Alarms command generates both an alarm data report from the
currently connected controller, and an event data report from the event log file currently being
viewed.
Applies To
Tricon and Trident controllers; event list
Locations
Reports menu
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.
Applies To
Event list
Locations
• Events menu > Options command > Event Options dialog box > Event Exclusion tab
• Set Events Options button > Event Options dialog box >Event Exclusion tab

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 an event log file (.tce or .tde) to a dBase IV-compatible
(.dbf) file that can be opened in applications such as Microsoft Excel or Access. 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
Event 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

139
Locations
• 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
Get Defaults
The Get Defaults property resets all properties on the Event Filters tab to their default settings.
Applies To
Event list
Locations

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.
Applies To
Event list
Locations
• Events menu > Options command > Event Options dialog box > Event Exclusion tab
• Set Events Options button > Event Options dialog box > Event Exclusion tab
IP Address
The IP Address property specifies a unique 32-bit address of a computer attached to a network.
A network uses IP addresses to route messages to their destinations. An IP address is formatted
as four numbers separated by periods, where each number can be zero to 255. An example is
1.160.10.240.
Every client and server in a network requires an IP address, which is either permanently or
dynamically assigned at startup. The defaults are as follows:
• ACM/NCM: 192.168.1.<node number>
• TCM: 192.168.0.<node number> for NET 1; 192.168.1.<node number> for NET 2
• Trident MP: 192.168.255.<node number>
For Trident 2.x, the default IP address is for connection to the Left MP only.
Note The highest and lowest IP addresses in a subnet (addresses where the last number is 0
or 255, such as 192.168.1.255) are reserved for broadcast messaging and cannot be used
as a valid IP address for a Triconex communication module.
See also Primary IP Address on page 149 and Secondary IP Address on page 153.
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

141
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
Applications, Tricon controllers
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 node when it is lost (for example,
due to communication or hardware problems). The connection retry limit applies to all Tricon
or Trident nodes in the network configuration.
Applies To
Location
Tools menu > Communication Options
Management UDP Port Number

The Management UDP Port Number property identifies the UDP port number used for the
Enhanced Diagnostic Monitor’s connection to TCM and CM 2.x communication status
information. The default value is 1510.
This must be the same value as the Management UDP Port Number property in the TCM or CM
Setup dialog box in TriStation 1131. For more information, see the TriStation 1131 Developer’s
Guide.
Applies To
Network configuration, nodes
Locations

143
Max Events Per Log File

The Max Events Per Log File property controls the maximum number of events that are saved
to a single 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, the
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 Tricon events in the
event log file events.tce, the 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 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
Event list
Locations
Options tab
tab
Maximum File Size

The Maximum File Size property displays the estimated maximum size of an event log file
based on the selected number of maximum events per file. This property is read-only. For more
information, see Max Events Per Log File on page 143.
Note The actual file size may differ significantly from the estimate. View the Windows file
properties for the event log file after event collection to view the actual file size.
Applies To
Event list

Locations
Options tab
tab
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
Modify Banner Message Command

The Modify Banner Message command allows you to customize the security banner that
appears each time you start the Enhanced Diagnostic Monitor.
Applies To
User security
Location
Edit menu
Module Colors
For a Trident Module Status window, the Module Colors area describes the colors that represent
the current state of each module.

145
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
MP Connection
The MP Connection property specifies which Trident 1.x 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 1.x nodes in a network configuration
Locations
• Network Nodes tree > right-click a Trident 1.x node > Add or Edit command > Network
Node Configuration dialog box
MP Leg
The MP Leg property is an event filtering option that allows you to restrict the visible event list
to only those events that occur on the selected main processor channels (legs)—A, B, or C. If only

one channel is selected, events for the other two channels will still be collected, but only events
matching the selected channel will appear in the event list.
All three channels are selected by default.
Applies To
Event list
Locations
New Event File Command

The New Event File command creates a new event log file (.tce or .tde). 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
events in an event log file is reached.
Applies To
Event 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

147
NIC Index
The NIC Index property specifies the index position of the network interface card in the
diagnostic PC.
Applies To
Trident 1.x network configuration, nodes
Locations
• Network Nodes tree > right-click a Trident 1.x node > Add or Edit command > Network
Node Configuration dialog box
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 Tricon and 1-63 for Trident.
Applies To
Location

Open Command
The Open command opens a node (controller) in 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 event log file (.tce or .tde) for viewing. This
command is available only when events are not actively being collected on any node. You must
stop event collection before you can open an existing event log file.
Applies To
Event 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

149
Poll Time
The Poll Time property displays the maximum time needed by the controller to obtain data
from the input modules.
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 74.
Applies To
Location
Primary IP Address
The primary IP address of the controller to be monitored. The Enhanced Diagnostic Monitor
uses this address to make the initial connection to the controller.
• For Tricon, this is the IP address of the communication module installed in the
controller. The default is 192.168.1.n, where n is the node number of the controller.
• For Trident, this is the IP address of one of the following, depending on how you are
connecting to the controller:
— The Left, Middle, or Right Main Processor module
— NET 1 on the communication module
— NET 2 on the communication module
The default is 192.168.255.n, for the Left MP, where n is the node number of the
controller.
If the connection to the primary IP address is lost, the Enhanced Diagnostic Monitor can switch
to a secondary IP address, if configured.
See IP Address on page 140 and Secondary IP Address on page 153 for more information.
Applies To
Locations

Primary Management UDP Port Number

The Primary Management UDP Port Number property identifies the primary UDP port number
used for the Enhanced Diagnostic Monitor’s connection to TCM and CM 2.x communication
status information. The default value is 1510.
This must be the same value as the Management UDP Port Number property in the TCM or CM
Guide.
See also Secondary Management UDP Port Number on page 154.
Applies To
Locations
Primary TriStation UDP Port Number

The Primary TriStation UDP Port Number property identifies the primary UDP port number
used for the Enhanced Diagnostic Monitor connection (via the TriStation protocol) to a Tricon
with a TCM installed, or a Trident 2.x with a CM installed. The default value is 1502.
This must be the same value as the TriStation UDP Port Number property in the TCM or CM
Guide.
See also Secondary TriStation UDP Port Number on page 154.
Applies To
Locations

151
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
Restore Primary Connection

The Restore Primary Connection property enables the Enhanced Diagnostic Monitor to
automatically attempt to restore the primary connection to a Trident 2.x or Tricon node when it
is lost (for example, due to communication or hardware problems). The default value is cleared.
Applies to all nodes in the network configuration.
See also Switch to Secondary Connection on page 159.
Applies To
Location

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

153
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 74.
Applies To
Controllers, applications
Location
Secondary IP Address
The secondary IP address of the controller to be monitored. The secondary connection settings
are used to connect to the controller only when the primary connection has been lost.
Note Secondary connection settings are available only for the Network connection type. You
cannot configure a secondary connection for a serial or Trident MP v1.x connection.
For Tricon, this is the IP address of a communication module installed in the controller. The
default is 192.168.1.n, where n is the node number of the controller.
For Trident, the IP address can be one of the following, depending on how you are connecting
to the controller:
• The Left, Middle, or Right Main Processor module
• NET 1 on the communication module
• NET 2 on the communication module
There is no default value.

See IP Address on page 140 and Primary IP Address on page 149 for more information.
Applies To
Locations
Secondary Management UDP Port Number

The Secondary Management UDP Port Number property identifies the secondary UDP port
number used for the Enhanced Diagnostic Monitor’s connection to Trident CM 2.x or Tricon
TCM communication status information. The default value is 1510.
The secondary connection settings are used to connect to the controller only when the primary
connection has been lost. See Primary Management UDP Port Number on page 150 for more
information.
Applies To
Locations
Secondary TriStation UDP Port Number

The Secondary TriStation UDP Port Number property identifies the secondary UDP port
number used for the Enhanced Diagnostic Monitor connection (via the TriStation protocol) to a
Tricon TCM or a Trident 2.x with a CM installed. The default value is 1502.
The secondary connection settings are used to connect to the controller only when the primary
connection has been lost. See Primary TriStation UDP Port Number on page 150 for more
information.
Applies To
Locations

155
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
Serial Port
The Serial Port property specifies which COM port on a diagnostic PC is connected to a
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, controllers
Locations
Set Event Options

The Set Event Options command allows you to customize event collection settings to suit your
needs. Changes apply only to the node being viewed when you select this command.
Applies To
Event 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 system events you want to see in the
event list. All severity levels are selected by default.
For example, if you only want to see Fault and Degraded messages in the Tricon event list, clear
the Information and Warning check boxes, and select the Fault and Degraded check boxes.

Applies To
Event list
Locations
Show All
The Show All property displays all possible chassis and slots for a Tricon system in the Chassis
and Slot Filtering dialog box, regardless of whether or not they are (or were) configured in the
actual system the events being viewed are being (or were) collected from.
By default, the chassis and slot tree includes nodes only for the chassis that are configured in the
Tricon system that events are currently being collected from, or were previously collected from
(if you are viewing an existing log file). The number of slots per chassis depends on whether the
chassis is a low-density chassis or a high-density chassis.
When selected, 15 chassis nodes with 16 slots each are displayed in the Chassis and Slot Filtering
dialog box. When cleared, only the actual chassis and slots are displayed in the tree. The default
is cleared.
Applies To
Tricon event list
Locations
• Events menu > Options command > Event Options dialog box > Tricon Event Filters tab >
Chassis and Slot Selection dialog box
• Set Events Options button > Event Options dialog box > Tricon Event Filters tab > Chassis
and Slot Selection dialog box
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

157
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
Standard Security
The Standard Security property sets the application-level security setting to Standard. When
selected, a user name and password is required to open the Enhanced Diagnostic Monitor. No
other user authentication is required.
This is the default setting.
See also Enhanced Security on page 136.
Applies To
User security
Location
Permissions menu > Edit Users > Permissions dialog box > Security Setting tab
Start Collecting Events Command

The Start Collecting Events command collects system events in a log file (.tce or .tde). 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 node (controller). If an
existing event log file is open for viewing, this command is unavailable. You must close any
open event log files before starting event collection.

Applies To
Controllers, power supplies, modules, points
Locations
Collect System Events button or Events menu
Start Time
The Start Time property specifies the starting date and time for a filtered list of system events,
in the month/day/year/hour/minute/second format. The default value is 1/1/1970 12:00:01
AM.
Applies To
Event 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

159
Stop Collecting Events Command

The Stop Collecting Events command stops 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
Switch to Secondary Connection

The Switch to Secondary Connection property enables the Enhanced Diagnostic Monitor to
switch to the secondary connection automatically when the primary connection to a Trident 2.x
or Tricon node is lost (for example, due to communication or hardware problems). The default
value is selected.
You also must configure the secondary connection settings for the node. See Secondary IP
Address on page 153.
Note The Enhanced Diagnostic Monitor will switch to a secondary connection only after the
primary connection has been lost. It will not switch to the secondary connection if the
primary connection has never successfully connected.
Applies to all nodes in the network configuration.
See also Restore Primary Connection on page 151.
Applies To
Location
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

Tricon Version
The Tricon Version property displays the system version number of the connected controller.
Applies To
Tricon controllers
Location
Trident System Version

The Trident System Version property displays the system version number of the connected
controller.
Not available for Trident 1.x controllers. This property will display 0 when connected to a
Trident 1.x.
Applies To
Trident 2.x controllers
Location
TriStation UDP Port Number

The TriStation UDP Port Number property identifies the UDP port number used for the
Enhanced Diagnostic Monitor connection (via the TriStation protocol) to a Tricon with a TCM
installed, or a Trident 2.x with a CM installed. The default value is 1502.
This must be the same value as the TriStation UDP Port Number property in the TCM or CM
Guide.
Applies To
Locations

161
Unlimited
The Unlimited property enables the Enhanced Diagnostic Monitor to automatically attempt to
restore the connection to a 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
Nodes
Location
Workspace Command
The Workspace command toggles the display of the Network Configuration tree, 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
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
Command-Line Interface Parameters
Overview 164
Command-Line Syntax 165

164 Appendix B Command-Line Interface Parameters
Overview
The Enhanced Diagnostic Monitor can also be launched via a command-line interface. This
allows you to open the Enhanced Diagnostic Monitor application from scripts running in other
control applications (such as the Foxboro I/A Series).
Note The Enhanced Diagnostic Monitor must be installed on the PC that the command-line or
script is being run on.
When launched using the command-line interface, there are two Enhanced Diagnostic Monitor
operating modes: regular, and read-only.
• When in regular mode, all normal Enhanced Diagnostic Monitor commands are
available.
• When in read-only mode, only the current system status of the specified controller is
available.
Connecting in Read-Only Mode

When the Enhanced Diagnostic Monitor is started via the command-line interface in read-only
mode, the following limitations apply:
• You are logged in as a guest user with the lowest level of access privileges. See Creating
and Managing Users on page 19 for more information about user security levels.
• You are not required to enter a user name and password to access the Enhanced
Diagnostic Monitor.
• The Enhanced Diagnostic Monitor automatically attempts to connect to the node
specified in the command line.
— If the connection is successful, the System Overview window for the specified node
appears. No other commands are available.
— If the connection is unsuccessful, an error message appears and you must exit the
application.

165
Command-Line Syntax
To open the Enhanced Diagnostic Monitor via the command-line interface, use the following
syntax:
EtcxDiag -mode <value> -node <value> -platform <value> -connection <value>
-address <value> -UDPport <value> -TMIport <value> -mpleg <value> -nic
<value> -SerialPort <value>
The following rules apply:

• Parameters you are not using for connection do not need to be included.
For example, if you are connecting in read-only mode to Trident 2.x node 31 via the serial
port, your command-line would look like this:
EtcxDiag -mode READONLY -node 31 -platform TRIDENT -connection SERIAL -
SerialPort 2
• There must be a space between the parameter name and the value, and also between
the previous value and the next parameter.
The following table provides descriptions of each of the available parameters in the command-
line syntax:
Required in
Parameter Description Acceptable Values Read-only
Mode?
-mode The desired operating mode. • READONLY Yes
See Overview on page 164 for • REGULAR
more information.
-node The node number of the •1 Yes
controller you want to connect
to. through
The range is 1–31 for Tricon and • 63
1-63 for Trident.
-platform The type of controller you want • TRICON Yes
to connect to. • TRIDENT
-connection The type of connection you • NETWORK Yes
want to make to the controller. • SERIAL
See Types of Network • MAIN_PROCESSOR_1x
Configurations on page 33 for
more information.
-address The IP address of the controller Any valid IP address. Yes, if
you want to connect to. connection
See IP Address on page 140 for type is
more information. NETWORK.

166 Appendix B Command-Line Interface Parameters
Required in
Parameter Description Acceptable Values Read-only
Mode?
-UDPport The TriStation UDP port used • 1500 Yes, if
for the diagnostic PCs • 1502 connection
connection to the controller. type is
• 1503 NETWORK.
See TriStation UDP Port
Number on page 160 for more • 1504
information. • 1510
-TMIport The Management UDP port • 1500 Yes, if
number used for the Enhanced • 1502 connection
Diagnostic Monitor’s type is
connection to the Tricon TCM or • 1503 NETWORK.
Trident 2.x CM communication • 1504
status information. • 1510
See Management UDP Port • 1511
Number on page 142.
-mpleg The channel (leg) of the Trident •0 Yes, if
main processor module that is •1 connection
connected to the diagnostic PC. type is MAIN_
•2 PROCESSOR_
Applies to a Trident 1.x Main
Processor connection only. where 0=Left, 1=Middle, and 1x.
2=Right
-nic The index position of the •0 Yes, if
network interface card installed through connection
in the diagnostic PC. type is MAIN_
•9 PROCESSOR_
Applies to a Trident 1.x Main
Processor connection only. 1x.
-SerialPort The COM port on the diagnostic •0 Yes, if

PC that is connected to the •1 connection
controller or the network. type is
•2 SERIAL.
•3
•4
Note When connecting in regular mode, only the -mode parameter is required.

C
Tricon Chassis and Slot Reference
Overview 168
Tricon v9 / v10 High-Density Chassis Slot Locations 170
Tricon v9 / v10 Low-Density Chassis Slot Locations 174

168 Appendix C Tricon Chassis and Slot Reference
Overview
The Enhanced Diagnostic Monitor displays the board address associated with a Tricon system
event message as either a hexadecimal value, or as a decimal value in the format chassis.slot,
depending on the display mode you have selected.
This appendix describes how to convert board addresses from the hexadecimal values to their
equivalent chassis and slot numbers, and provides a visual reference for Tricon chassis and slot
locations.
What Is a Board Address?

A board address identifies the location of a module installed in a Tricon chassis. You can select
how board addresses are displayed in event lists.
• Chassis.slot is the default format, and is recommended for most users because it is the
easiest to understand. In this format, board addresses are provided as decimal values.
— The character to the left of the decimal is the chassis number
— The characters to the right of the decimal is the logical slot number.
For example, the board address 2.3R refers to chassis 2, logical slot 3 Right.
• The hexadecimal format is recommended only for advanced users. 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.
Board Address Display Format Exceptions

• In some cases, board addresses are provided as physical slot locations, rather than
logical slot locations. Usually, this occurs when viewing event log files created with
previous versions of the Enhanced Diagnostic Monitor or Diagnostic Monitor.
Board addresses provided as physical slot locations use the following format: x.yP,
where x is the chassis number, y is the physical slot, and P indicates the address is a
physical slot board address. For example, a board address of 9.8P indicates a physical
address of chassis 9, slot 8.
• If a board address displays with a question mark (?) for the slot location (such as 1.?),
the Enhanced Diagnostic Monitor was unable to translate the board address because of
a mismatch between the physical chassis hardware and the chassis type downloaded in
the TriStation project.
Change the board address display format to hexadecimal, and then use the conversion
tables to manually translate the board address.

169
What Is a Slot Number?

In most cases, the slot number refers to the logical slot, not the physical slot.
• Each MP and COM slot equals one logical slot.
• Each I/O logical slot has two physical slots–Left (L) and Right (R).
However, if the board address is provided in the physical slot location format (indicated by a P
at the end of the address, such as 1.5P), the slot number refers to the physical slot.
• Each MP and COM slot equals one physical slot.
• Each I/O logical slot equals two physical slots.
Which Chassis Diagrams Should You Refer To?

Be sure to use the correct reference diagram for your Tricon system and chassis type:
Tricon Chassis
Use this diagram...
System Type
v10 Main and Tricon v9 and v10 Main / RXM Chassis Configuration on
High-Density RXM page 170
Expansion Tricon v9 and v10 Expansion Chassis Configuration on page 171
v10.4 or Later Tricon v9 Low-Density / Tricon v10.4 or Later Enhanced Low-
Enhanced Expansion Density Expansion Chassis Configuration on page 175
Low Density
v9 Main and Tricon v9 and v10 Main / RXM Chassis Configuration on
High-Density RXM page 170
Expansion Tricon v9 and v10 Expansion Chassis Configuration on page 171
v9 Main and Tricon v9 Low-Density Main / RXM Chassis Configuration on
Low-Density RXM page 174
Tricon v9 Low-Density / Tricon v10.4 or Later Enhanced Low-
Expansion
Density Expansion Chassis Configuration on page 175

Tricon v9 / v10 High-Density Chassis Slot Locations

The following figures show the location of each logical and physical slot—by number—in a
high-density Tricon v9 or v10 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 Logical Slot

Numbers
1
REMOTE RUN
PROGRAM
A 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 Physical Slot
ALARM
TEMP
COM RX COM RX COM RX Numbers
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 Main / RXM Chassis Physical and Logical Slot Equivalents
Physical Logical Physical Logical Physical Logical

Slot Slot Slot Slot Slot Slot
1 MP A or RXM A 7 3L 13 6L
2 MP B or RXM B 8 3R 14 6R
3 MP C or RXM C 9 4L 15 7L
4 COM 10 4R 16 7R
5 2L 11 5L
6 2R 12 5R

171
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 Logical Slot

Numbers
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
Physical Slot
MODEL 8310
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Numbers
A, B Redundant Power Modules

Tricon v9 and v10 Expansion Chassis Physical and Logical Slot Equivalents
Physical Logical Physical Logical Physical Logical

Slot Slot Slot Slot Slot Slot
1 1L 7 4L 13 7L
2 1R 8 4R 14 7R
3 2L 9 5L 15 8L
4 2R 10 5R 16 8R
5 3L 11 6L
6 3R 12 6R

Hex to Chassis / Slot Conversion Tables—High-Density Main and RXM Chassis

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

(3rd Character) (4th Character) 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 3 4 COM or empty
4 4 4 5 2L
5 5 5 6 2R
6 6 6 7 3L
7 7 7 8 3R
8 8 8 9 4L
9 9 9 10 4R
a 10 a 11 5L
b 11 b 12 5R
c 12 c 13 6L
d 13 d 14 6R
e 14 e 15 7L
f 15 f 16 7R
Sample Hex to Chassis / Slot Conversions

The following are some sample hexadecimal board address conversions for a high-density main
or RXM chassis:
Hex Board Physical Logical

Chassis
Address Slot Slot
0xb3 11 4 COM
0xf0 15 1 MP A
0x68 6 9 4L
0x0f 1 16 7R
0xca 12 11 5L

173
Hex to Chassis / Slot Conversion Tables—High-Density Expansion Chassis

high-density expansion chassis.
Hex Chassis Hex Physical Logical Slot

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

The following are some sample hexadecimal board address conversions for a high-density
expansion chassis:

Chassis
Address Slot Slot
0xb3 11 4 2R
0xf0 15 1 1L
0x68 6 9 5L
0x2f 2 16 8R
0xca 12 11 6L

Tricon v9 / v10 Low-Density Chassis Slot Locations

The following figures show the location of each logical and physical slot—by number—in the
Tricon v9 low-density main chassis and the Tricon v9/v10 low-density expansion chassis. An
RXM chassis has the same physical configuration as a main chassis.
Note For a Tricon v10 system, only an enhanced low-density chassis can be installed, and then
only as an expansion chassis in a v10.4 or later system. Its physical slot locations are the
same as the Tricon v9 low-density expansion chassis.
The main chassis is number 1. Expansion chassis are numbered from 2 to 15.
Tricon v9 Low-Density Main / RXM Chassis Configuration
POWER A MP B C L
1
R L
2
R L 3 R L 4 R Logical Slot
Numbers
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 Physical Slot
COM RX COM RX COM RX
Numbers
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
PROGRAM 3006 3006 3006
A
STOP
ó LOCAL ó
A Keyswitch with Chassis Number

Tricon v9 Low-Density Main / RXM Chassis Physical and Logical Slot Equivalents
Physical Slot Logical Slot Physical Slot Logical Slot

1 MP A or RXM A 8 2R
2 MP B or RXM B 9 3L
3 MP C or RXM C 10 3R
5 1L 11 4L
6 1R 12 4R
7 2L

175
Tricon v9 Low-Density / Tricon v10.4 or Later Enhanced Low-Density Expansion Chassis

Configuration
POWER L
1
R L
2
R L 3 R L 4 R L
5
R Logical Slot
Numbers
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 Physical Slot
A 2 Numbers
A Chassis Number
Tricon v9 Low-Density / Tricon v10.4 or Later Enhanced Low-Density Expansion Chassis

Physical and Logical Slot Equivalents
Physical Slot Logical Physical Slot Logical

Slot Slot
3 1L 8 3R
4 1R 9 4L
5 2L 10 4R
6 2R 11 5L
7 3L 12 5R

Hex to Chassis / Slot Conversion Tables—Low-Density Main and RXM Chassis

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:

Chassis
Address Slot Slot
0xb4 11 5 1L
0xf0 15 1 MP A
0x68 6 9 3L
0x02 1 3 MP C
0xca 12 11 4L

177
Hex to Chassis / Slot Conversion Tables—Low-Density or Enhanced Low-

Density Expansion Chassis
low-density or enhanced 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 or
enhanced low-density expansion chassis:

Chassis
Address Slot Slot
0xb3 11 4 1R
0xf2 15 3 1L
0x68 6 9 4L
0x0b 1 12 5R
0xca 12 11 5L


D
Trident Baseplate and Slot Reference
Overview 180
Trident Baseplate and Physical Slot Locations 181

180 Appendix D Trident Baseplate and Slot Reference
Overview
The Enhanced Diagnostic Monitor displays the board address associated with a Trident system
event message as a decimal value in the format IOP.baseplate.slot, MP.slot, or CM.slot, depending
on the module the event is associated with.
This appendix provides a visual reference for typical Trident baseplate and slot locations.
What Is a Board Address?

A board address identifies the location of a module installed in a Trident chassis. Board
addresses are provided as decimal values.
• For I/O modules, the format is IOP.baseplate.slot.
— The character to the left of the first decimal is the IOP number.
— The character to the right of the first decimal are the baseplate number.
— The characters to the right of the second decimal is the slot location (Left or Right).
For example, the board address 01.05.R refers to IOP 1, baseplate 5, Right slot.
• For Main Processor modules, the format is MP.slot.
— The character to the right of the decimal is the slot location (Left, Middle, or Right).
For example, the board address MP.M refers to the Main Processor module in the
Middle position.
• For communication modules, the format is CM.slot.
— The character to the right of the decimal is the slot location (Left or Right).
For example, the board address CM.R refers to the communication module in the Right
position.
A Note About Physical Baseplate Locations

When you install your Trident baseplates and modules on the IOP rails, you can put them in
any order you like, with only a few restrictions regarding the location of the MP and CM
baseplates.
As long as the address plug on the module matches the module type configured in your
application (as defined in TriStation 1131), the physical location of the baseplates and modules
is unimportant.
As a result, depending on your configuration, your baseplate numbering may not be in
numerical order. For example, baseplate 04 may be located above baseplate 03. The figure and
baseplate locations in the next section should be considered as a suggested installation
configuration only.
Be sure to double-check your own physical baseplate locations and module configuration in
TriStation 1131 to correctly match the board addresses reported by the Enhanced Diagnostic
Monitor to your Trident controller.

181
Trident Baseplate and Physical Slot Locations

The following figure and corresponding table show the location of each baseplate and physical
slot in a typical Trident IOP configuration. Baseplates are numbered from 1 to 32.
EM
1
CM 10
2
11 AI
6
3 5
MP 12
4
11
DI
13
0
6
AI 14
7
6 DO
2
15
8
DI 16
9
0 RO
EM
17
9

182 Appendix D Trident Baseplate and Slot Reference
Label Baseplate Board Address

1 CM CM.L
2 CM.R
3 MP MP.L
4 MP.M
5 MP.R
6 01 01.01.L
7 01.01.R
8 02 01.02.L
9 01.02.R
10 03 01.03.L
11 01.03.R
12 04 01.04.L
13 01.04.R
14 05 01.05.L
15 01.05.R
16 06 01.06.L
17 01.06.R

E
Tricon and Trident Event Classes
Each event collected by the Enhanced Diagnostic Monitor has an event class that indicates the
system component (firmware) where the event originated from. For example, class “ETSX”
indicates the event originated from the Tricon Main Processor.
This appendix describes each event class and its corresponding system component for Tricon
and Trident systems.

184 Appendix E Tricon and Trident Event Classes
Tricon Event Classes
Class Code Description

CMN 0 Event messages that are common to all modules in the system.
TSX 1 Event messages from the Model 3006 Main Processor.
IOC 2 Event messages from IOC.
COMM 3 Event messages from COMM.
ICX 4 Event messages from ICX.
HCX 5 Event messages from HCX.
DCM 7 Event messages from DCMX.
NIAI 8 Event messages from NIAI.
AIO 9 Event messages from AIO.
DO 11 Event messages from digital output modules (DO).
EAO 12 Event messages from EAO.
EDI 13 Event messages from EDI.
EDO 14 Event messages from EDO.
EIAI 15 Event messages from EIAI.
ESDO 17 Event messages from ESDO.
HDI 18 Event messages from HDI.
LAI 19 Event messages from LAI.
AOPI 20 Event messages from analog output (AO) or pulse input (PI) modules.
SDO 22 Event messages from SDO.
TC 23 Event messages from TC.
RXM 24 Event messages from RXM chassis.
GC 25 Event messages from the glitch catcher.
CP 26 Event messages from the control program running on the controller.
TSDO 27 Event messages from TSDO.
DDO 28 Event messages from DDO.
SDI 29 Event messages from SDI.
ACM 30 Event messages from Advanced Communication Modules (ACMs).
ETSX 32 Event messages from the Model 3008 Main Processor.
IOCCOM 33 Event messages from IOC/COMM.
CNMIO 34 Common event messages from Model 3720/3721 AI and 3625 DO modules.
NGAI 35 Event messages from Model 3720 or 3721 Analog Input modules.
NGDO 36 Event messages from Model 3625 Digital Output modules.

185

TCM 37 Event messages from Tricon Communication Modules (TCMs).
SCAO 38 Event messages from Servo Controller Analog Output (SCAO) modules.
Trident Event Classes

CMN 0 Event messages that are common to all modules in the system.
TSX 1 Event messages from the System Executive on the Trident Main Processor.
CP 2 Event messages from the control program running on the controller.
LCM 3 Event messages from the Trident 1.x Communication Module (CM).
LIOX 4 Event messages from the I/O Executive on the Trident Main Processor.
DI 5 Event messages from digital input (DI) or high-resolution digital input (HRDI)
modules.
DO 6 Event messages from digital output (DO) or supervised digital output (SDO)
modules.
AI 7 Event messages from analog input (AI) modules.
RO 8 Event messages from relay output (RO) modules.
IO 9 Common event messages from I/O modules.
AO 10 Event messages from analog output (AO) modules.
PI 11 Event messages from pulse input (PI) or enhanced pulse input (EPI) modules.
TCM 14 Event messages from the Trident 2.x Communication Module (CM).

186 Appendix E Tricon and Trident Event Classes

Index
A board addresses
defined
A&E status information, OPC 84
Tricon 168
access logs, user Trident 180
clearing 18 display format, Tricon
exporting 16 changing 101
options 17 exceptions 101, 168
saving 16 filtering by 112–113
viewing 15 P indicator in, Tricon 101, 168
Access, viewing events in 121 question mark in, Tricon 101, 168
ACM event retention 99 Tricon high-density 172
active clients Tricon low-density 174, 176
OPC 84 broadcasts received, Modbus Serial 86, 93
TSAA 84, 91 bytes
active status, Peer-to-Peer 86, 93 TCM print buffer 87
Trident 2.x CM print buffer 94
actual scan time 73
Add command 127
C
Add/modify users privilege 29
Calendar property 71, 128
adding
nodes 36 capacity, disk 106
Tricon node 36 changing
Trident node 39 board address format, Tricon 101
users 23 default password 9, 19
addresses, board, see board addresses memory allocation 75
network configuration 36
addresses, hexadecimal 168–177
OVD state 65
admin user, Windows 5, 8, 13, 15 passwords, user 24, 26
alarm data reports 124 scan time 74
attempts, login 9 security level
names 31
authentication, user 11, 20
privileges 28
Auto Scroll property 109, 127 security setting 20
chassis and slot event filter 113
B chassis and slot locations, Tricon 168
bad password error 11 chassis configurations
banner text, security 13–14 Tricon high-density 170
baseplate Tricon low-density 174
addresses 102 chassis icons
configurations 181 Tricon 53
locations physical 180 Trident 57
black, event message color 97 chassis numbers
blue, event message color 97 Tricon high-density 170, 172, 173
Board Address Filter property 112, 128 Tricon low-density 174, 176, 177

188 Index
chassis.slot board addresses 101, 168 communication status information (continued)

class, event message 98, 183 overview
Tricon 80
Clear All command 128
Trident 88
Clear Faults on All Modules command 129 Peer-to-Peer status
Clear Faults privilege 28, 64 Tricon 86
clearing faults Trident 93
on all modules 64 Performance status
on individual modules 60, 62 Tricon 83
Trident 90
clearing user access logs 18
Printer status
client access list Tricon 87
TCM 29, 32, 43 Trident 93
Trident 2.x CM 29 refresh rate 80
Trident 2.x CM 32, 43 saving to file 94
Close Event File command 129 Tricon, viewing 80
Close Network Configuration command 129 Trident, viewing 88
TriStation status
CM, Trident 2.x
Tricon 87
client access list 29, 43
Trident 94
communication status 88–94
troubleshooting
connecting via serial link 35
Tricon 82
Modbus TCP ports 92
Trident 89
read-only mode 42
TSAA status
redundancy with 34
Tricon 84
unable to connect to 43
Trident 91
unable to view communication status 89
Communication Status View window
CM.slot board addresses 102, 180
changing position of 49
code, event message 98 Tricon 80
Collect System Events privilege 28 Trident 88
collecting system events 96–121 compatibility 3
collisions configuring
TCM 83 Tricon node 36
Trident 2.x CM 91 Trident node 39
colors Connect command 130
event messages 97 connection
modules, Tricon 54 communication status 80, 88
modules, Trident 58 error messages 44
command-line interface 164–165 Ethernet 33
Communication Options command 44, 129 lost 44, 77
Modbus 35
communication status information
read-only 42
counter values 79
redundant 34
definitions 79
retry limit 44
Modbus Serial status
serial 35
Tricon 86
switch to secondary 44
Trident 92
to controller 42
Modbus TCP status
troubleshooting 43, 82, 89
Tricon 85
Trident 92 Connection Type property 37, 39, 130
Network status connections
Tricon 83 Modbus TCP 85, 92
Trident 90 TCM printer 87
OPC status 84 Trident 2.x CM printer 94

Index 189
connections (continued) default (continued)

TriStation interface 87, 94 security level privileges 28
controller security setting 20
see also nodes user 9–23
see also Tricon Default Log File Directory property 110, 132
see also Trident degraded mode, reporting faults in 56
connecting to 42
Delete command 133
status, viewing 70–71
deleting users 23
Controller Type property 37, 39, 131
Diagnostic Alarms command 124, 133
converting hexadecimal addresses 168
Diagnostic Monitor v4.x 4
Copy All Items to Clipboard command 131
diagnostic reports 124
Copy command 131
directory, log file 110, 132
Copy Selected Items to Clipboard command 131
disabled A&E events, OPC 84
correcting faults 61, 63
Disconnect command 133
counter values, communication status 79
disk space
CRC errors
for event log files 106
Modbus Serial 86, 92
for installation 3
Peer-to-Peer 86, 93
warnings 77
TCM 83
Trident 2.x CM 91 Display Board Address in Hex Mode command 102,
TriStation interface 87, 94 133
TSAA 84, 91 Display Board Address in High-Density Mode
creating command 102, 134
event log file 105 Display Board Address in Low-Density Mode
network configuration 36 command 102, 134
reports 122–125 Display Execution Times command 78, 135
user 23
Display Firmware Versions command 67, 135
Crystal Reports 122
DLC protocol, installing 6
Current Faults property 59, 132
docking windows 48
customer support vii
domain authentication, Windows 10, 11, 20
customizing the workspace 47
Cut command 132 E
Cyber Security, NERC 13, 15, 27 Edit command 135
Edit Users command 136
D
EICM
DA groups, OPC 84 collecting events from 4
date, event message 98 connecting via serial link 35
.dbf file 120 event collection speed 107
event retention 99
default
event collection settings 109 End Time property 112, 136
events per file 106 Enhanced Diagnostic Monitor
IP address compatibility 3
ACM/NCM 140 installing 5
Tricon 37, 140 login password 42
Trident 40, 140 starting 9
log file directory 110 steps for using 2
password 9 system requirements 3
security banner text 14 uninstalling 8
security level names 31 upgrading 4

190 Index
enhanced low-density Tricon 174, 177 events (continued)

Enhanced Security collection settings 109
changing to 20 color-coding 97
defined 19 excluding from list 118
login 10, 11 exporting 120–121
login attempts 9 filtering view of 111
interpreting 97
Enhanced Security property 136
loss of 99
error messages maximum per file 106, 110, 143
connection retry 44 retention of 99
general 77 severity levels 97, 112
login 11 speed of collection 107
security banner text, saving 14 viewing during collection 107
Ethernet network configuration 33 Events and Diagnostic Alarms command 124, 137
event analysis, generating reports 122 Events command 122, 137
event classes 183–185 events file, generating reports from 122
event collection Events pane
filtering 111 filtering view in 111
options 109 information in 98
performance 107 opening 103
progress bar 107
Events Summary pane
settings 109–118
information in 99
speed of 107
opening 103
starting 107
status of 99 Exclude command 137
stopping 108 exclusion list 118
event data reports 122 execution times, program 78, 135
event exclusion list 118 Exit command 138
event log files Export Event File command 120, 138
see also events exporting
access to 105 communication status data 94
closing 129 event log files 120–121
creating 105 reports 126
.dbf format 120 user access logs 16
default directory for 110, 132
external faults 60–61
displaying 96
exporting 120–121
filtering view 111 F
free disk space for 106 fatal faults 62
generating reports from 122 Fault History property 59
managing 105
opening 119, 148 Fault History setting 138
size, default 106 fault information, Tricon 56
status of 99 faults
viewing 119 clearing
event message class 98 on all modules 64
on individual modules 60, 62
event message code 98
privileges for 28
event retention 99, 100 external 60–61
Event Viewer, Windows 15 in degraded mode 56
events internal 62–63
see also event log files types of 60, 62
collecting 107 field faults 60

Index 191
Field Faults property 59, 138 indicators

Field Faults tab 55 fault 60, 62
module 55, 58
FIELD POWER indicator, Trident 60
installation 5
file access rules 32
installing DLC protocol 6
file format, exported event log 120
internal faults 62–63
filtering events 111
Invensys contact information vi
Find command 139
IOM GCS vii
firmware versions 67, 135
IOP and baseplate event filter 113
floating windows 48
IOP icons 57
format
.dbf files 120 IOP.baseplate.slot board addresses 102, 180
board addresses 101, 102 IP address
framing errors default, Tricon 37
TCM 83 default, Trident 40
Trident 2.x CM 91 defaults 140
primary 149
free disk space
secondary 153
required for installation 3
required for log files 106 IP Address property 37, 38, 40, 41, 140
free memory
TCM 83 K
Trident 2.x CM 90 Key Stop/Position property 72, 141
Free Memory property 72, 139 keyswitch, Tricon 72
G L
generating reports 122 LED Indicators area 141
Get Defaults property 139 LEDs, module 55, 58
Global Client Support vii Left Module area 142
green, event message color 97 Limited property 46, 142
Guest account, Windows 12, 15 link status
TCM 83
H Trident 2.x CM 90
hardware monitoring 52 LOAD/FUSE indicator, Tricon 60
hexadecimal board addresses log files, event, see event log files
changing format 101 logging in 9–11
defined 168 logical slots
Tricon high-density 172 defined, Tricon 169
Tricon low-density 176 high-density chassis, Tricon 170
hiding window panes 47 Tricon low-density 174
high-density Tricon 172, 173 login
access logs, viewing 15
I attempts, number of 9
Enhanced Security 10, 11
icons
error messages 11
chassis 53
first time 9, 11
IOP 57
password 9
ignoring password 42 Standard Security 10
Include command 140 troubleshooting 11
incorrect parameter error 11 user name 24, 26

192 Index
login (continued) monitoring

Windows Guest user 12 communication status
lost connection 44, 77 Tricon 80
Trident 88
low-density Tricon 101, 174, 176, 177
controller
hardware 52
M status 71
major faults 62 memory allocation 75
Management UDP Port Number property 38, 82, 89, OVD 65, 66
142 scan time 73
managing event log files 105 moving windows 48
Max Events Per Log File property 106, 110, 143 MP Connection property 41, 145
maximizing windows 49 MP Leg property 112, 145
maximum event log file size 106 MP.slot board addresses 102, 180
Maximum File Size property 110, 143
N
Maximum Memory property 72, 144
names
memory allocation 75
security level 31
memory statistics 72 user 24, 26
message text, event 98 naming event log files 105
messages NCM event retention 99
NERC
received
password rules 27
Modbus TCP 85, 92
security banner text 5, 13
Peer-to-Peer 86, 93
user access logs 15–18
TriStation interface 87, 94
TSAA 84, 91 .NET Framework 3, 5
sent, Peer-to-Peer 86, 93 network configuration
Messages command 144 creating 36
opening 42, 148
Messages pane 48, 67, 76, 78
types 33
Microsoft Access 121 using Modbus 35
minor faults 62 Network Nodes tree, showing or hiding 48
Modbus communication 35 network status
Modbus Serial status TCM 83
Tricon TCM 86 Trident 2.xCM 90
Trident 2.x CM 92 New Event File command 146
Modbus TCP status new event log files 105, 146
Tricon TCM 85
New Network Configuration command 146
Trident 2.x CM 92
NIC Index property 41, 147
modes, command-line interface 164
Node Name property 37, 39, 147
Modify Banner Message command 13, 14, 144
Node Number property 37, 39, 147
module colors 54, 58, 144
nodes
module indicators 55, 58
adding to network configuration 36
Module Status command 145 connecting to 42
Module Status dialog box 55 connection problems 43
Module Status window editing 36
changing position of 49 event collection settings 109
Tricon 54 maximum number 36
Trident 57 read-only connection 42

Index 193
not authorized error 12 port connected status, Modbus TCP 85, 92

numbers, chassis Port Write Enabled property 32, 42
Tricon high-density 170, 172, 173 power faults 55, 60
Tricon low-density 174, 176, 177
Primary IP Address property 149
Primary Management UDP Port Number property 40,
O 150
OPC status, TCM 84 Primary TriStation UDP Port Number property 40, 150
Open command 148
Print command 151
Open Event File command 148
printer status
Open Network Configuration command 148 Tricon TCM 87
opening Events panes 103 Trident 2.x CM 93
options printing, reports 123, 125
event collection 109 privileges, user 28
user access logs 17
program execution times 78
output voter fault 97
progress bar, event collection 107
OVD 65, 66
Project property 151
project status 72
P
protocol, DLC 6
parameters, command-line 165
passwords R
default 9, 19
forgotten 19 read-only mode 42, 164
login errors 11 receiving messages status
rules for 27 TCM 83
TriStation project 42 Trident 2.x CM 90
user 24, 26 red, event message color 97
Windows 10, 11, 20, 24
redundant communications 34
Peer-to-Peer status
refresh rate 53, 80, 88
Tricon TCM 86
Trident 2.x CM 93 refreshing report view 124, 125
percent idle regular mode, command-line 164
TCM 83 rejects
Trident 2.x CM 90 Modbus Serial 86, 92
performance status Modbus TCP 85, 92
TCM 83 reports
Trident 2.x CM 90 alarm data, generating 124
performance, event collection 107 event data, generating 122
exporting 126
physical baseplate locations, Trident 180
file names 122, 124
physical slot location board addresses, Tricon 101, 168 printing 123, 125
physical slots refreshing 124, 125
high-density chassis, Tricon 170 saving 126
Tricon defined 169 searching 124, 125
Tricon low-density 174 requested scan time 73
Trident 181
requirements
pink, event message color 97 disk space 3, 106
point faults 56, 148 system 3
poll time 73, 74 resizing windows 49
Poll Time property 72, 149 Restore Primary Connection property 45, 151

194 Index
restoring security setting

lost connection 44 changing 20
windows 49 default 20
retention, event 99, 100 defined 19
retry limit, connection 44 Select All command 155
Right Module area 152 serial connection, event collection speed 107
rules, passwords 27 serial link 35
Serial Port property 38, 40, 155
S Set Event Options command 155
Save As command 152 severity levels, event 97, 112
Save Network Configuration As command 152 Severity property 112, 155
Save Network Configuration commands 152 Show All property 156
saving Show Line Numbers command 156
communication status data 94 showing window panes 47
reports 126
size of event log files 106
user access logs 16
slot colors
Scan Request/Actual property 72, 153
Tricon 54
scan surplus 73 Trident 58
Scan Surplus property 72, 153 Slot Colors area 157
scan time 72, 73, 74 slot number, Tricon 169
SDO slots, chassis 169–174
OVD status 66
Standard Security
supervision status 66
changing to 20
searching, in reports 124, 125 defined 19
Secondary IP Address property 153 login 10
Secondary Management UDP Port Number login attempts 9
property 38, 41, 154 Standard Security property 157
secondary network connection Start Collecting Events command 157
configuring, Tricon 38 Start Time property 112, 158
configuring, Trident 41
starting
retry settings for 44
Enhanced Diagnostic Monitor 9
Secondary TriStation UDP Port Number property 38, event collection 107, 157
41, 154 status
seconds idle communication, Tricon 80–87
Modbus Serial 86, 93 communication, Trident 88–94
Modbus TCP 85, 92 controller, viewing 70–71
TSAA 85, 91 event collection 99
security banner event log file 99, 105
changing during installation 5 OVD 65, 66
customizing 13 project 72
default text 14 system, reports 124
error while saving 14 Status Bar command 158
security levels Status property 158
assigning privileges to 28
Stop Collecting Events command 159
assigning to user 24, 26
client access list 29 stopping event collection 108, 159
default privileges 28 subscribed DA, OPC 84
names, changing 31 supervision status, SDO 66
overview 19

Index 195
surplus, scan 73 Tricon (continued)

Switch to Secondary Connection property 45, 159 see also TCM
adding node 36
syntax, command-line 165
communication status 80–87
SYSTEM ALARM indicator, Trident 60 configuring node 36
system events connection, Ethernet 34
see also event log files default IP address 37
collecting 96–121 event classes 184
collection settings 109 event collection 96–121
color-coding 97 event exclusion list 118
exclusion list 118 event log files 105, 119–121
exporting 120–121 high-density chassis configurations 170
filtering view of 111 IP address 37
interpreting 97 keyswitch 72
loss of 99, 100 low-density chassis configurations 174
maximum per file 106, 110, 143 low-density display format 101
retention of 99, 100 module colors 54
severity levels 97, 112 Module Status dialog box 55
System Overview tree 53 Module Status window 54
monitoring OVD 65
System Overview window 49, 53, 57
nodes, maximum 36
system requirements 3 secondary network connection 38
system version 71 status reports 124
supported versions 3
T system events 96, 97
System Overview window 53
.tce files 105 system version 71
TCM Tricon Version property 71, 160
client access list 29, 32, 43
communication status 80–87 Trident
connecting via serial link 35 see also CM, Trident 2.x
event collection speed 107 see also event log files
event retention 99 adding node 39
Modbus TCP ports 85 baseplate locations, physical 180
read-only mode 42 board addresses 102
redundancy with 34 CM client access list 29, 32
unable to connect to 43 communication status 88–94
unable to view communication status 82 configuring node 39
connection, Ethernet 34
.tde files 105
connection, serial 35
technical support vii default IP address 40
time, event message 98 event classes 185
timeout status, Peer-to-Peer 87, 93 event collection 96–121
event exclusion list 118
timeouts event log files 105, 119–121
event retention 100
Modbus TCP 85, 92 IOP icons 57
Toolbar command 159 IP address 40
training vi module colors 58
transmit errors Module Status window 57
TCM 83 monitoring OVD 65, 66
Trident 2.x CM 91 monitoring SDO supervision 66
nodes, maximum 36
Tricon
SDO module 66
see also event log files
secondary network connection 41

196 Index
Trident (continued) users (continued)

status reports 124 privileges 28
supported versions 3 security level, selecting 24, 26
SYSTEM ALARM indicator 60
system events 96, 97 V
System Overview window 57
system version 71 version
unable to connect to 43 controllers, supported 3
firmware 67, 135
Trident System Version property 71, 160 project 71
TriStation system 71
application password 42 viewing
status controller status 70–71
TCM 87 event log files 119
Trident 2.x CM 94 events during collection 107
TriStation UDP Port Number property 37, 43, 160 events in Access 121
troubleshooting Events panes 103
communication status problems firmware versions 67
Tricon 82 memory statistics 75
Trident 89 program execution times 78
connection problems 43 scan time 73
connection retry limit 44 Tricon communication status information 80
error messages 77 Trident communication status information 88
login problems 11 voter faults 55, 62
passwords, forgotten 19
TSAA status W
TCM 84
warning messages 77
Trident 2.x CM 91
web site, Invensys vi
U window panes 47, 48
window position, selecting 49
UDP ports
Management 38, 40, 41, 82, 89, 142, 150, 154 Windows
TriStation 37, 38, 40, 41, 150, 154, 160 administrator privileges 5, 8, 13, 15
domain authentication 10, 11, 20, 27
uninstallation 8
file access rules 32
unknown user name error 11 Guest account, using 12, 15
Unlimited property 46, 161 passwords, rules for 27
update rate, see refresh rate supported versions 3
updates DA, OPC 84 user name 10, 11, 20, 24
upgrading 4, 8 windows, resizing 49

Windows Event Viewer 15
user access logs 15–18
Workspace command 161
user name, Windows 10, 11, 20, 24
workspace, customizing 47
users
access 32 write messages, TSAA 85, 91
authentication of 20 writes DA, OPC 84
creating 19
default 9, 24, 26 X
deleting 23
managing 19–32 XML configuration file, defined 33
modifying 24, 26
names 24, 26 Z
passwords 24, 26 Zoom command 161

Index 197
Zoom to Fit command 162

198 Index

Invensys Operations Management
5601 Granite Parkway Suite 1000
Plano, TX 75024
United States of America
http://iom.invensys.com
Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Email: iom.support@invensys.com
Website: http://support.ips.invensys.com

9720107-006 Enhanced Diagnostic Monitor v2.4.0 Users Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9720107-006 Enhanced Diagnostic Monitor v2.4.0 Users Guide

Uploaded by

Copyright:

Available Formats

Enhanced Diagnostic Monitor

Triconex Enhanced Diagnostic Monitor

© 2006–2010 by Invensys Systems, Inc. All rights reserved.

Document No. 9720107-006

Chapter 1 Getting Started 1

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Moving, Docking, and Floating Window Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 2 Monitoring Controller Hardware 51

Chapter 3 Monitoring Controller Status 69

Chapter 4 Collecting and Viewing Events 95

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Stopping Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Appendix A Commands and Properties 127

Appendix B Command-Line Interface Parameters 163

Appendix C Tricon Chassis and Slot Reference 167

Appendix D Trident Baseplate and Slot Reference 179

Appendix E Tricon and Trident Event Classes 183

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

New Features in the Enhanced Diagnostic Monitor

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

• Appendix A, Commands and Properties—Describes commands and properties in the

Product and Training Information

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

We Welcome Your Comments

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Steps for Diagnostic Monitoring 2

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Steps for Diagnostic Monitoring

Monitor C ontroller Monitor C ontroller

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Installing the Enhanced Diagnostic Monitor

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Upgrading from Diagnostic Monitor 4.1 or Earlier

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Installing the Enhanced Diagnostic Monitor

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Installing the DLC Protocol on the Diagnostic PC

Step 1: Download the DLC Protocol Installation Program

Step 2: Modify the .Inf File

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

5 Save the file and then exit Notepad.

Step 3: Configure the DLC Protocol Network Connection

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Uninstalling the Enhanced Diagnostic Monitor

Manually uninstalling the Enhanced Diagnostic Monitor 2.4.0 will delete

If you are upgrading from version 2.0—2.3 of the Enhanced Diagnostic

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Starting the Enhanced Diagnostic Monitor

Logging In for the First Time

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Logging In When Standard Security Is Enabled

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

Logging In When Enhanced Security Is Enabled

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Logging In for the First Time When Enhanced Security Is Enabled

Troubleshooting Login Problems

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Customizing the Security Banner Text

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Enhanced Diagnostic Monitor v2.4.0 User’s Guide

Viewing User Access Logs