Enhanced Diagnostic Monitor

User’s Guide

Triconex Enhanced Diagnostic Monitor

Version 2.10.0

Assembly Number 9700107-013

December 2014
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., now part of Schneider Electric.

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

Invensys, Foxboro, Foxboro Evo, Triconex, Tricon, Trident, and TriStation are trademarks of Invensys
Limited, its subsidiaries and affiliates. All other brands may be trademarks of their respective owners.

Document Number 9720107-013, Rev 0

Printed in the United States of America.
 Contents

Preface vii
New Features in Enhanced Diagnostic Monitor 2.10.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Summary of Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Product and Training Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
We Welcome Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Viewing User Access Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Creating and Managing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Changing the Security Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Adding User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Modifying User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Recommended Rules for Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Changing the Security Level for Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Changing Security Level Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Other Permissions Affecting User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Setting Up a Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Types of Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Identifying an Automatically Discovered Controller. . . . . . . . . . . . . . . . . . . . . . . . . . 35
Creating or Changing a Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Opening a Network Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Troubleshooting Connection Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuring the Connection Retry Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Enabling Secure Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

iv Contents

What Is a Certificate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Choosing the Certificate to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring Secure Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Customizing Your Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Showing or Hiding Window Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Moving, Docking, and Floating Window Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Maximizing, Restoring, and Resizing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 2 Monitoring Controller Hardware 63

System Overview and Module Status Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Tricon System Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Tricon Module Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Trident/Tri-GP System Overview Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Trident/Tri-GP Module Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Understanding External Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Locating and Correcting External Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Understanding Internal Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Locating Internal Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Clearing Faults on All Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Monitoring Output Voter Diagnostics (OVD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Monitoring Trident/Tri-GP SDO OVD and Supervision Status . . . . . . . . . . . . . . . . . . . . . 78
Displaying Firmware Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 3 Monitoring Controller Status 81

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Viewing Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Monitoring and Changing the Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Changing the Scan Time Using TriStation 1131 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Monitoring and Changing the Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Changing the Memory Allocation Using TriStation 1131 . . . . . . . . . . . . . . . . . . . . . . 87
Viewing Data in the Messages Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Viewing Program Execution Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Monitoring Communication Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Monitoring Tricon Communication Status Information . . . . . . . . . . . . . . . . . . . . . . . 92
Monitoring Trident or Tri-GP Communication Status Information . . . . . . . . . . . . 100
Saving Communication Status Information to a File . . . . . . . . . . . . . . . . . . . . . . . . . 108

Chapter 4 Collecting and Viewing Events 109

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Interpreting System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Event Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Event List Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Events Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Important Information About Event Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Interpreting the Board Address Display Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Interpreting and Changing the Tricon Board Address Display Format . . . . . . . . . 116
Interpreting the Trident or Tri-GP Board Address Display Format . . . . . . . . . . . . 118

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Contents v

Opening the Events and Events Summary Panes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Managing Event Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Creating Event Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Managing Event Log File Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Managing Free Disk Space for Event Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Starting and Stopping Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Starting Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Stopping Event Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Changing the Default Event Collection Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Changing the Default Event Log File Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Controlling Event Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Filtering the Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuring the Board Address Event Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Modifying the Event Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Viewing an Existing Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Locating and Closing Open Event Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Exporting an Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Exported .Dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Opening an Exported Event Log File in Microsoft Access . . . . . . . . . . . . . . . . . . . . 138
Generating Event and Alarm Data Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Generating Event Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Generating Alarm Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Exporting Report Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Appendix A Commands and Properties 145

Appendix B Security Guidelines 185

Workstation Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Appendix C Using Enhanced Diagnostic Monitor with System Manager 187

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Appendix D Command-Line Interface Parameters 193

Appendix E Tricon Chassis and Slot Reference 201

Appendix F Trident and Tri-GP Baseplate and Slot Reference 215

Appendix G Event Classes 219

Index 223

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

vi Contents

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Preface

The Triconex® Enhanced Diagnostic Monitor is a software program for monitoring the
hardware, communication, and application status of Tricon™, Trident™, and Triconex General
Purpose (Tri-GP) controllers.

New Features in Enhanced Diagnostic Monitor 2.10.0

Enhanced Diagnostic Monitor version 2.10.0 is a significant release with the following new
features:
• Support for up to 254 nodes in Tricon system versions 11.1 and later.
• Support for Enhanced Peer-to-Peer communication between nodes in Tricon system
versions 11.1 and later.
• Several other minor fixes and enhancements.
Note For more detailed information about the changes made in each Enhanced Diagnostic
Monitor 2.x release, see the Product Release Notice for Enhanced Diagnostic Monitor 2.x,
available on the Global Customer Support (GCS) website.

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. Describes the default configuration file.
• 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.
• Appendix A: Commands and Properties— Describes commands and properties in the
Enhanced Diagnostic Monitor.
• Appendix B: Security Guidelines — Provides information on the security concepts and
guidelines that are applicable to the Enhanced Diagnostic Monitor.
• Appendix C: Using Enhanced Diagnostic Monitor with System Manager— Describes
how to use the Enhanced Diagnostic Monitor with the Foxboro Evo™ Control Core
Services System Manager. Provides information about installing and configuring the

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

viii Preface

Enhanced Diagnostic Monitor for use with System Manager, and how to launch the
Enhanced Diagnostic Monitor from within System Manager.
• Appendix D: 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 E: 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 F: Trident and Tri-GP Baseplate and Slot Reference— A visual reference of
typical Trident/Tri-GP 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 G: Event Classes— Lists the event classes for Tricon, Trident, and Tri-GP
controllers, with a short description of the component each event class originates from.

Related Documents
• TriStation™ 1131 Libraries Reference
• TriStation 1131 Developer’s Guide
• TriStation 1131 + ArchestrA Integration Guide
• Communication Guide for Tricon 9-10 Systems
• Communication Guide for Trident Systems
• Communication Guide for Tri-GP Systems
• Product Release Notices for specific Tricon, Trident, Tri-GP, and TriStation 1131 versions

Product and Training Information

To obtain information about Triconex products and in-house and on-site training, see the
Invensys website or contact your regional customer center.

Website
http://iom.invensys.com

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Preface ix

Technical Support
Customers in the U.S. and Canada can obtain technical support from the 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

Website
http://support.ips.invensys.com/ (registration required)

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

x 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:
[email protected]
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 Global Customer Support (GCS) center. See
Technical Support on page ix for contact information.
Or, you can write to us at:
Attn: Technical Publications — Triconex
Invensys Systems, Inc.
26561 Rancho Parkway South
Lake Forest, CA 92630
USA
Thank you for your feedback.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 1
Getting Started

Steps for Diagnostic Monitoring 2

Installing the Enhanced Diagnostic Monitor 3
Starting the Enhanced Diagnostic Monitor 9
Creating and Managing Users 18
Setting Up a Network Configuration 32
Enabling Secure Communication 55
Customizing Your Workspace 60

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Installing the Enhanced Diagnostic Monitor 3

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
• Tri-GP versions 2.1.x 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 the .NET Framework 4.0 and one of the following Windows operating
systems:
— Windows 7 Professional/Enterprise (32-bit or 64-bit)
— Windows Server® 2008 R2 (64-bit)
Note During the installation process, setup will verify that all prerequisite
components are installed. If prerequisite components are missing, you will be
prompted to install them. For example, 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
• Free hard drive space
— For installing the Enhanced Diagnostic Monitor: 25 MB (for installation of the
program only; if you are intending to collect events, a larger hard drive may be
needed)

1. Please see the Product Release Notice for Enhanced Diagnostic Monitor 2.x, available on the Global
Customer Support (GCS) website, for detailed compatibility information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

4 Chapter 1 Getting Started

— For installing the prerequisites:

• SAP® Crystal Reports® runtime engine for .NET Framework: 250 MB
• .NET 4.0 Framework: 850 MB (2 GB recommended)
• Microsoft® Visual C++ 2012 Runtime Library: 15 MB
• Microsoft Visual C++ 7.1 Runtime Library: 1 MB
• MSXML 6: 5 MB
Note If you have installed the Microsoft Office Suite, MSXML 6 will be automatically
installed on your system.
• 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.
Notes The above operating system and hard disk space requirements are applicable to a
Virtual Machine (VM) instance as well. Microsoft Hyper-V® is the only virtualization
technology that has been tested by Invensys, and is supported for use with the Enhanced
Diagnostic Monitor.
For optimum display performance while using the Enhanced Diagnostic Monitor,
Invensys 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
The upgrade path for the Enhanced Diagnostic Monitor depends on which version is currently
installed.

Upgrading from Enhanced Diagnostic Monitor 1.x

If you currently have Enhanced Diagnostic Monitor 1.x installed on the diagnostic PC, you must
manually uninstall it before you install Enhanced Diagnostic Monitor 2.10.0. Existing user
information will be deleted, and you will need to reconfigure all user names, passwords, and
security levels in Enhanced Diagnostic Monitor 2.10.0.
Note If Enhanced Diagnostic Monitor versions 1.0 and 1.1 were both installed on the
diagnostic PC prior to installing Enhanced Diagnostic Monitor version 2.10.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 (versions 1.0 and 1.1) after
you have installed 2.x.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Installing the Enhanced Diagnostic Monitor 5

Upgrading from Enhanced Diagnostic Monitor 2.x

If you currently have Enhanced Diagnostic Monitor 2.x installed on the diagnostic PC, installing
Enhanced Diagnostic Monitor 2.10.0 will upgrade the existing 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 19 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 128.

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

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 the TriStation 1131 software.
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.
During the installation process, setup will verify that all prerequisite components are installed.
If prerequisite components are missing, you will be prompted to install them. For example, 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 4.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 Security Banner
message text. This is optional; the message text can also be modified at any time after
installation. If you are not sure if you want to change the text, leave the default text as-is
during installation. See Customizing the Security Banner Text on page 12 for more
information.

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

6 Chapter 1 Getting Started

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.
9 If prompted to install required prerequisite components, click Install Prerequisites.
Setup will automatically install all necessary prerequisites.
You must install all required prerequisite components before the Enhanced Diagnostic
Monitor setup can continue. For more information about a selected prerequisite,
double-click the prerequisite name.
Invensys recommends installing the Enhanced Diagnostic Monitor software in the
default destination folder, which is: C:\Program Files\Triconex\Enhanced
Diagnostic Monitor.
Note For systems running 64-bit versions of Windows, the default folder is:
C:\Program files(x86)\Triconex\Enhanced Diagnostic Monitor.
10 Continue to follow the InstallShield Wizard prompts.
11 To complete the installation, click Finish.
You are not required to restart your PC before running the 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 7 (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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Installing the Enhanced Diagnostic Monitor 7

Step 1: Obtain the DLC Protocol Installation Program

1 Contact Global Customer Support to obtain the dlc.exe file. (For contact information, see
Technical Support on page ix.)
2 Save the dlc.exe file to your local drive.
3 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 3 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: Obtain 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

8 Chapter 1 Getting Started

Uninstalling the Enhanced Diagnostic Monitor

This procedure explains how to uninstall the Enhanced Diagnostic Monitor.

Manually uninstalling the Enhanced Diagnostic Monitor version 2.10.0

CAUTION will delete all existing user names, passwords, and security levels.

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

Monitor, and want 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 2.10.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 in Windows
7 32-bit, or C:\Program files(x86)\Triconex\Enhanced Diagnostic
Monitor in Windows Server 2008 and Windows 7 64-bit), 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting the Enhanced Diagnostic Monitor 9

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 19 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.
Topics in this section include:
• 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 12
• Viewing User Access Logs on page 14

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 18 for more information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

10 Chapter 1 Getting Started

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.10.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.10.0.
The Windows Login dialog box appears.

2 Enter your Windows user name (including domain, if necessary) and password, and
click OK.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting the Enhanced Diagnostic Monitor 11

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.
The following error message This message appears when Enhanced Security is enabled,
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

12 Chapter 1 Getting Started

Problem Solution
The following error message This message appears when Enhanced Security is enabled,
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, or meet site-specific
needs.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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting the Enhanced Diagnostic Monitor 13

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 Global Customer Support for
assistance. For contact information, see Technical Support on page ix.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

14 Chapter 1 Getting Started

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.
Note For more information about the Enhanced Security option, see Changing the Security
Setting on page 19.
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).
Topics in this section include:
• Viewing the User Access Log In Windows Event Viewer on page 14
• Saving the User Access Log to a File on page 15
• Changing Event Logging Options on page 16
• Clearing the User Access Log on page 17

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting the Enhanced Diagnostic Monitor 15

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. See Viewing the User Access Log In Windows Event
Viewer on page 14.
2 On the Action menu, click Save Log File As.
3 In File name, enter a name for the archived log file.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

16 Chapter 1 Getting Started

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
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, 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting the Enhanced Diagnostic Monitor 17

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
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, 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

18 Chapter 1 Getting Started

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 Global Customer Support
for assistance. For contact information, see Technical Support on page ix.
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.
Topics in this section include:
• Changing the Security Setting on page 19
• Managing User Accounts on page 22
• Adding User Accounts on page 23
• Modifying User Accounts on page 25
• Recommended Rules for Passwords on page 26
• Changing the Security Level for Privileges on page 27
• Changing Security Level Names on page 30
• Other Permissions Affecting User Access on page 31

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 19

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
1 Make sure that all network node connections are closed.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

20 Chapter 1 Getting Started

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 22 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 22 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 21

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 26 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.

8 Click OK to save your changes.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

22 Chapter 1 Getting Started

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 27)
Even if you have the appropriate Enhanced Diagnostic Monitor user privileges, if you do not
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
1 Make sure that all network node connections are closed.
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.

3 Click the Users tab, and then perform one of these actions.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 23

Command Action
New To create a new user, click New. For further instructions, see
Adding User Accounts on page 23.
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 25.
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
1 Make sure that all network node connections are closed.
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.
3 Click New. The Add User dialog box appears.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

24 Chapter 1 Getting Started

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 26 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.

5 Click OK to save your changes.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 25

Modifying User Accounts

This procedure explains how to modify Enhanced Diagnostic Monitor user accounts, including
changing user names or passwords.

Procedure
1 Make sure that all network node connections are closed.
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.
3 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 26 for minimum requirements.
Verify Password Enter the changed password again for verification.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

26 Chapter 1 Getting Started

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.

5 Click OK to save your changes.

Recommended Rules for Passwords

Invensys recommends configuring your Windows domain authentication settings to support
the following minimum requirements for passwords:
• 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.
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. However, when Standard Security setting is enabled,
this level of password protection is not provided.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 27

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 Tricon, Trident,
and Tri-GP 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 76.
Module: Allows the user to collect system events when connected Levels 01—05
Collect system to a node (controller). Applies to Tricon, Trident, and
events Tri-GP controllers.
For more information, see Chapter 4, Collecting and
Viewing Events.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

28 Chapter 1 Getting Started

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 or UCM is installed in the Tricon controller, or a communication module (CM
or CIM) is installed in a Trident 2.x/3.x or Tri-GP 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 31.

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
communication module, they will be unable to perform the command. For more
information, see the TriStation 1131 Developer’s Guide.

Procedure
1 Make sure that all network node connections are closed.
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.
3 Click the Privileges tab.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 29

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).
6 Click OK to save your changes.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

30 Chapter 1 Getting Started

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
1 Make sure that all network node connections are closed.
2 On the Permissions menu, click Edit Users. The Permissions dialog box appears.
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

5 Click OK to save your changes.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Creating and Managing Users 31

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 TCM or UCM installed in your Tricon controller, or a communication
module installed in your Trident 2.x/3.x or Tri-GP 2.x/3.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/UCM, they will be unable to perform the command.
For more information on configuring the 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 Trident/Tri-GP 2.x and later communication
modules.
4. Selected TCM models, and the Trident/Tri-GP 2.x and later communication modules only. See the
TriStation 1131 Developer’s Guide for more information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

32 Chapter 1 Getting Started

Setting Up a Network Configuration

A network configuration is an XML file which includes the Tricon, Trident, and Tri-GP 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.
When you launch the Enhanced Diagnostic Monitor, a default network configuration file opens.
You can use this as a basis for creating your own network configuration, customized for the
controllers you want to monitor. This network configuration file is located in the path
C:\ProgramData\Triconex\Enhanced Diagnostic Monitor\Data.

If you have Trident/Tri-GP 3.0 and later controller(s) on your network, the Enhanced
Diagnostic Monitor will automatically discover them if a CIM is configured in the system. This
avoids the need to manually configure the connection to the controller(s).
This section describes how to configure a network connection. Topics include:
• Types of Network Configurations on page 32
• Identifying an Automatically Discovered Controller on page 35
• Creating or Changing a Network Configuration on page 36
• Opening a Network Node on page 49
• Troubleshooting Connection Problems on page 51
• Configuring the Connection Retry Settings on page 52

Types of Network Configurations

A network configuration can include Tricon, Trident, and/or Tri-GP 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 33

Tricon Controller Trident Controller Tricon Controller

CM or CIM

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

C C
MAINT2
C MAINT2 MAINT2
LINK
C C
MAINT2
C MAINT2 MAINT2
NET 1
LINK

NET 2
TX RX

NET 2
TX RX
PASS
PASS
FAULT
MP MP MP FAULT MP MP MP
ALARM ALARM
NET 2

TEMP LINK
TEMP NET 2
LINK
TX RX

BATT LOW BATT LOW TX RX

(TCM or
TS/TSAA TS/TSAA TS/TSAA TS/TSAA

(TCM or
TS/TSAA TS/TSAA
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
UCM)
LINK LINK LINK LINK LINK LINK

UCM)
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, Trident 2.x/3.x, or Tri-GP Controllers)

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
UCMs, CMs, or CIMs in the controller (this achieves media redundancy).
• Connect the Ethernet port on the primary NIC to the Left communication module.
Configure this as your primary connection to the controller.
• Connect the Ethernet port on the secondary NIC to the Right communication module.
Configure this as your secondary connection to the controller.

If communications on the primary connection (the Left communication module) 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 controller. Also, see Configuring the Connection
Retry Settings on page 52 for information on configuring the automatic switch to the secondary
connection.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

34 Chapter 1 Getting Started

Serial Links
For Tricon, Trident 2.x/3.x, or Tri-GP controllers, 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 TCM/UCM/EICM via a serial cable, you must
connect the serial cable to Serial Port 4 on the TCM or EICM, or Serial Port 2 on the UCM.
When connecting the diagnostic PC to a Trident 2.x/3.x or Tri-GP communication
module via serial cable, you must connect the serial cable to Serial Port 3 on the
communication module. 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, UCM 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 35

Identifying an Automatically Discovered Controller

The Enhanced Diagnostic Monitor can automatically discover Trident and Tri-GP 3.x
controllers with a CIM installed if either of the following criteria are met:
• The controller is located on the same subnet as the diagnostic PC, and the controller’s
node number (as configured in the MP) matches an available node number in the
network configuration.
• The controller is located on a different subnet as the diagnostic PC, and the controller is
using the default IP address (192.168.1.n, where n is the node number).
Note If the controller is not using the default IP address, it must be on the same subnet as the
diagnostic PC in order for the Enhanced Diagnostic Monitor to be able to automatically
discover the controller.
Every 2.5 minutes, the Enhanced Diagnostic Monitor refreshes
the network nodes list, polling the network for connected
controllers. When a controller is discovered, the Enhanced
Diagnostic Monitor automatically configures the controller’s
network connection by retrieving the following parameters from
the controller:
• Primary IP Address
• Primary TriStation UDP Port Number
• Primary Management UDP Port Number
Secondary connection parameters are not automatically
configured; if you want to configure secondary parameters for
the controller, follow the instructions provided in Adding or
Changing a Trident 3.x or Tri-GP 3.x Controller on page 44.
Automatically discovered controllers are highlighted green in
the Network Nodes tree, as shown at right. Once a controller has
been automatically discovered, double-click the node to connect
as described in Opening a Network Node on page 49.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

36 Chapter 1 Getting Started

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.
Note The Enhanced Diagnostic Monitor automatically discovers Trident 3.x/Tri-GP 3.x or
later controllers with a CIM installed, if they are available on the network the diagnostic
PC is connected to. You do not need to configure the connection to these controllers. See
Identifying an Automatically Discovered Controller on page 35 for more information.
You can use the default network configuration file as a basis for creating your own network
configuration, customized for the controllers you want to monitor.
If you are creating a network configuration for the first time, do one of the following:
• Using the default network configuration (EnDMConfig.xml) as a starting point, change
the connection information (node names, IP addresses, etc.) as needed to connect to the
controllers on your network. Each time you open the Enhanced Diagnostic Monitor, the
modified default network configuration file will open automatically.
• Create a new network configuration from scratch by selecting File > New Network
Configuration.
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 254 controllers in a single network configuration:
• Nodes 1–31 can be configured for Trident, Tri-GP, or Tricon controllers.
• Nodes 32–63 can be configured for Trident , Tri-GP, or Tricon 11.1 and later controllers.
• Nodes 64–254 can be configured for Tricon 11.1 and later controllers only.
For example, you can configure 25 Tricon 11.0 and earlier controllers and 35 Trident or Tri-GP
controllers, for a total of 60 nodes. But you cannot configure 35 Tricon 11.0 and earlier
controllers, 20 Trident controllers, and 15 Tri-GP controllers, as this exceeds both the overall
63-node limit for Trident or Tri-GP controllers, AND the 31-node limit for Tricon 11.0 and earlier
controllers.
Note If 254 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 37

Topics in this section include:

• Adding or Changing a Tricon Controller on page 37
• Adding or Changing a Trident 1.x/2.x or Tri-GP 2.x Controller on page 40
• Adding or Changing a Trident 3.x or Tri-GP 3.x Controller on page 44

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 Do one of the following:
• To modify the already opened default network configuration (EnDMConfig.xml) so
that it is customized for the controllers you want to monitor, go to step 2.
(preferred)
• To modify an existing network configuration, verify that a network configuration is
not currently open. Then, on the File menu, click Open Network Configuration and
select the file you want to modify.
• To create a new network configuration, verify that a network configuration is not
currently open, and then on the File menu, click New Network Configuration.
The Network Nodes tree opens in the left pane.
2 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.

3 Specify these properties in the Network Node Configuration dialog box.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

38 Chapter 1 Getting Started

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-254).
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 controller with a TCM or UCM installed. The
default is 1502.
This must be the same value as the TriStation UDP Port Number
property in the TriStation 1131 TCM/UCM 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/UCM installed.
Primary For a Network connection, specify the UDP port to use for the
Management Enhanced Diagnostic Monitor’s connection to TCM/UCM
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/UCM Setup dialog
box. For more information, see the TriStation 1131 Developer’s
Guide.
For more information about viewing the communication status of
a TCM/UCM, see Monitoring Communication Status
Information on page 91.
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.
4 If you want to configure a secondary network connection for use when the primary
network connection is lost, specify the following optional properties.

Property Action
Secondary IP Address Specify the secondary IP address of the controller to be
monitored.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 39

Property Action
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 controller with a TCM/UCM 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/UCM
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.
The secondary 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 52.
5 If you want to configure the default event log file directory, click the browse button
next to the Default Event Log File Directory property. In the dialog box that appears,
select the path where event log files will be saved. The default is
C:\ProgramData\Triconex\Enhanced Diagnostic Monitor\Data.
The path you specify here applies to all nodes.
You must have write access to this location. If you do not 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.
For more information about the event log files, see Collecting and Viewing Events on
page 109.
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.
6 Click OK to save your changes.
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 do not have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

40 Chapter 1 Getting Started

Adding or Changing a Trident 1.x/2.x or Tri-GP 2.x Controller

This section describes how to add a new Trident 1.x/2.x or Tri-GP 2.x controller node, or make
changes to an existing Trident 1.x/2.x or Tri-GP 2.x controller node, in a network configuration.

Procedure
1 Do one of the following:
• To modify the already opened default network configuration (EnDMConfig.xml) so
that it is customized for the controllers you want to monitor, go to step 2.
(preferred)
• To modify an existing network configuration, verify that a network configuration is
not currently open. Then, on the File menu, click Open Network Configuration and
select the file you want to modify.
• To create a new network configuration, verify that a network configuration is not
currently open, and then on the File menu, click New Network Configuration.
The Network Nodes tree opens in the left pane.
2 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.

3 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 or Tri-GP.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 41

Property Action
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 or Tri-GP
2.x controller
Use Secure Not applicable to Trident 1.x and Trident/Tri-GP 2.x controllers.
Communication Available only with Trident/Tri-GP 3.x controllers with a CIM
installed.
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 1.x/2.x or Tri-GP 2.x controllers.
You must browse for the correct 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 1131 Developer’s Guide.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

42 Chapter 1 Getting Started

Property Action
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 Trident 2.x or Tri-GP 2.x controller 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
information, see the TriStation 1131 Developer’s Guide.
Required only for a connection to a Trident 2.x or Tri-GP 2.x node
with a CM installed.
Primary For a Network connection, specify the UDP port to use for the
Management Enhanced Diagnostic Monitor’s connection to Trident 2.x/Tri-GP 2.x
UDP Port CM 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
information, see the TriStation 1131 Developer’s Guide.
For more information about viewing a Trident 2.x/Tri-GP 2.x CM’s
communication status, see Monitoring Communication Status
Information on page 91.
Serial Port For a Trident 2.x or Tri-GP 2.x Serial connection, select the COM port
on the diagnostic PC which is connected to the controller.
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.
4 If you want to configure a secondary network connection for use when the primary
network connection is lost, specify the following optional properties.

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 or Tri-GP 2.x controller 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 Trident 2.x/Tri-GP 2.x
CM communication status information. The default is 1510.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 43

Note Secondary connection settings are available only for the Network connection
type. You cannot configure a secondary connection for a serial or MP 1.x
connection.
The secondary 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 52.
5 If you want to configure the default event log file directory, click the browse button
next to the Default Event Log File Directory property. In the dialog box that appears,
select the path where event log files will be saved. The default is
C:\ProgramData\Triconex\Enhanced Diagnostic Monitor\Data.
The path you specify here applies to all nodes.
You must have write access to this location. If you do not 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.
For more information about the event log files, see Collecting and Viewing Events on
page 109.
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.
6 Click OK to save your changes.
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 do not have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

44 Chapter 1 Getting Started

Adding or Changing a Trident 3.x or Tri-GP 3.x Controller

This section describes how to add a new Trident 3.x or Tri-GP 3.x controller node, or make
changes to an existing controller node, in a network configuration.
If a CIM is installed, the Enhanced Diagnostic Monitor should automatically find the controller,
eliminating the need to configure the network connection. Since the Enhanced Diagnostic
Monitor is continuously polling the network, any changes to the network configuration should
be found automatically.
Note The following procedure is necessary only if any of the following are true:
• The diagnostic PC is on a separate subnet from the controller.
• A CM is installed in the controller.
• You want to enable secure communication with the controller.
• You want to configure secondary communication settings for this controller (see
Configuring the Connection Retry Settings on page 52).

Procedure
1 Do one of the following:
• To modify the already opened default network configuration (EnDMConfig.xml) so
that it is customized for the controllers you want to monitor, go to step 2.
(preferred)
• To modify an existing network configuration, verify that a network configuration is
not currently open. Then, on the File menu, click Open Network Configuration and
select the file you want to modify.
• To create a new network configuration, verify that a network configuration is not
currently open, and then on the File menu, click New Network Configuration.
The Network Nodes tree opens in the left pane.
2 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 45

3 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 or Tri-GP.
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:
• Network for an Ethernet (TCP/IP) connection
• Serial for a serial (Modbus) connection
Use Secure To enable secure communication with a controller with a CIM
Communication installed, select this check box.
Available only if a CIM is installed (not a CM), and with a network
connection, not a serial connection. For more information, see
Enabling Secure Communication on page 55.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

46 Chapter 1 Getting Started

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 or CIM - NET 1
• Left CM or CIM - NET 2
• Right CM or CIM - NET 1
• Right CM or CIM - 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. You must browse for the correct default IP
address as described above, or enter your own IP address.

Your own IP addresses for other MP, CM, or CIM 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 1131 Developer’s Guide.
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 the controller. The default is 1502.
This must be the same value as the TriStation UDP Port Number
property in the TriStation 1131 CM or CIM Setup dialog box. For
more information, see the TriStation 1131 Developer’s Guide.
Primary For a Network connection, specify the UDP port to use for the
Management Enhanced Diagnostic Monitor’s connection to CM or CIM
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 or CIM Setup dialog box. For
more information, see the TriStation 1131 Developer’s Guide.
For more information about viewing CM or CIM communication
status, see Monitoring Communication Status Information on
page 91.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 47

4 If you want to configure a secondary network connection for use when the primary
network connection is lost, specify the following optional properties.

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
the controller. The default is 1502.
Secondary Management Specify the secondary UDP port to use for the Enhanced
UDP Port Number Diagnostic Monitor’s connection to CM or CIM
communication status information. The default is 1510.

Note The secondary 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 52.
5 If you want to enable secure communication with this controller, specify the following
properties.

Property Action
Certificate Name Specifies the certificate name.
To search for a certificate, click the browse button, and in
the dialog box that appears, choose the type of certificate you
want to find (a certificate installed for the current user or a
certificate installed for the local machine). Then select the
desired certificate from the list of certificates that appears.
Certificate ID Specifies the unique certificate identification number. The
certificate ID is populated automatically from the certificate
properties.

Note The Use Secure Communication check box must be selected before you can select
a certificate. For more information, see Enabling Secure Communication on
page 55.
6 If you want to configure the default event log file directory, click the browse button
next to the Default Event Log File Directory property. In the dialog box that appears,
select the path where event log files will be saved. The default is
C:\ProgramData\Triconex\Enhanced Diagnostic Monitor\Data.
The path you specify here applies to all nodes.
You must have write access to this location. If you do not 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

48 Chapter 1 Getting Started

For more information about the event log files, see Collecting and Viewing Events on
page 109.
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.
7 Click OK to save your changes.
8 Repeat steps 3–7 for each node you want to add or change.
9 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 do not have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 49

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).
Note Nodes that have been automatically discovered are highlighted green in the tree. See
Identifying an Automatically Discovered Controller on page 35.

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 do not 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 50.
• Click Cancel to disconnect from the node.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

50 Chapter 1 Getting Started

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 or UCM is installed in the Tricon controller and the TCM or UCM 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 or UCM is installed in the Tricon controller and the Port Write Enabled
property has been disabled for the network port the diagnostic PC is connected to. For
more information, see the TriStation 1131 Developer’s Guide.
• A communication module is installed in the Trident 2.x/3.x or Tri-GP controller and
the 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, UCM, CM, or CIM 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 51

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 or UCM diagnostic PC has read-only or read/write access to the
installed. TCM, UCM, or CM via the TriStation protocol. If the
or TCM, UCM, or CM client access list has been configured
so that the IP address of the diagnostic PC is denied access
You cannot connect to a Trident to the TCM, UCM, or CM via the TriStation protocol, you
2.x/3.x or Tri-GP node that has a will be unable to open the node.
CM installed.
• Verify that the TriStation UDP Port Number configured
for the node matches the TriStation UDP Port Number
configured for the TCM, UCM, 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, UCM, 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.
The Enhanced Diagnostic Verify that the Trident 3.x or Tri-GP 3.x node:
Monitor cannot automatically • Is on the same network as the diagnostic PC
discover a Trident 3.x or Tri-GP
3.x node. • Has a CIM installed
• Has a node number configured in the controller’s MP that
matches an available node number in the network
configuration.
• Is successfully sending messages to the Enhanced
Diagnostic Monitor. If network communication errors
cause messages from the node to be lost, the Enhanced
Diagnostic Monitor will assume the node is no longer
available.
You cannot connect to a Trident Verify that the TriStation UDP Port Number configured for
3.x or Tri-GP 3.x node that has the node matches the TriStation UDP Port Number
been automatically discovered. configured for the CIM in TriStation 1131. If the UDP port
numbers are different, you will be unable to connect to the
node.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

52 Chapter 1 Getting Started

Configuring the Connection Retry Settings

This section describes how to configure the connection retry settings for all types of 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Setting Up a Network Configuration 53

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
Secondary switch to the secondary connection automatically when the
Connection primary 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
Tricon, Trident 2.x/3.x, or Tri-GP 2.x/3.x 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
Connection attempt to 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:

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

54 Chapter 1 Getting Started

Property Description
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 do not 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Enabling Secure Communication 55

Enabling Secure Communication

The Enhanced Diagnostic Monitor gives you the option to securely connect to Trident and
Tri-GP 3.x controllers with a CIM installed. When you are securely connected to a controller,
communication between the diagnostic PC and the controller is encrypted using a digital
certificate and a Secure Sockets Layer (SSL) connection.
Note For more detailed information about managing and using certificates, see the
Communication Guide for your controller, and the TriStation 1131 Developer’s Guide.
When deciding whether or not to use secure communication, you should assess the security
threats to your system within the context of the overall plant architecture, any applicable
standards, and your corporate practices. As a result of this security risk assessment, if you feel
that a higher level of security is needed to mitigate security threats, you should enable and use
secure communication.
Secure communication is enabled on a per-node basis.
Topics in this section include:
• What Is a Certificate? on page 55
• Choosing the Certificate to Use on page 56
• Configuring Secure Communication on page 57

What Is a Certificate?
A digital certificate is an electronic credential that ensures the identity of the certificate owner via
a pair of electronic keys (public and private) that are used to encrypt and sign information
digitally. Messages are encrypted with one key (public or private) and then decrypted with the
other key.

How Does the Enhanced Diagnostic Monitor Use Certificates?

When secure communication is enabled, the Enhanced Diagnostic Monitor uses a certificate and
the SSL secure transmission protocol to connect to the controller. Use of secure communication
provides the following benefits:
• Verifies the identity of the diagnostic PC and the controller through the exchange and
validation of the certificate.
• Encrypts information exchanged between the diagnostic PC and the controller on a
secure channel.
• Ensures the integrity of the contents of messages that are exchanged between the
diagnostic PC and the controller, by ensuring the messages have not been altered
during transmission.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

56 Chapter 1 Getting Started

Choosing the Certificate to Use

The certificate used by the Enhanced Diagnostic Monitor for secure communication is located
in the Windows certificate store on the diagnostic PC. The certificate can be specific to the
currently logged-in user (a current user certificate), or it can be global to all users on the
diagnostic PC (a local machine certificate).
The selected certificate must be in PKCS12 format, and it must include its associated private key.
Additionally, when the certificate was added to the certificate store, the “Mark this key as
exportable” option must have been selected, so that the private key can be extracted. The
Enhanced Diagnostic Monitor will be unable to use the certificate to establish a secure
connection to the controller if the private key cannot be extracted.
If you are the only person who will be using the Enhanced Diagnostic Monitor to connect to the
controller, you can select a certificate from the current user certificate store. However, if
multiple users will be using the Enhanced Diagnostic Monitor to connect to the controller, you
should select a certificate from the local machine store, so that all users who log in to the
Enhanced Diagnostic Monitor can securely connect to the controller.
Note You must have Windows administrator permissions to access the local machine
certificate store and select a certificate. If you do not have administrator permissions,
contact your network administrator for assistance.

Using the Default Certificates

Invensys recommends using your organization’s personalized certificates and private keys for
secure communication between the Enhanced Diagnostic Monitor and the controller. However,
if you do not have your own certificates, or want to test the use of secure communication before
you generate your own certificates, you can use the default certificates.
Note TriStation 1131 4.10.0 and later includes a simple certificate generation tool that you can
use to generate personalized certificates for your organization. For more information,
see the TriStation 1131 Developer’s Guide.
When you install the Enhanced Diagnostic Monitor, the following default certificates are also
installed:
• ExampleClientCertificate.pfx
• ExampleServerCertificate.pfx
The default certificates are located in the following location: C:\Program
Data\Triconex\Enhanced Diagnostic Monitor\Data

Before you can use the default certificates with the Enhanced Diagnostic Monitor, you must
manually import them into the Windows certificate store on the diagnostic PC. When you add
a default certificate to the certificate store, ensure the “Mark this key as exportable” option is
selected, so that the private key can be extracted. For more information on importing certificates
into the Windows certificate store, refer to Windows Help.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Enabling Secure Communication 57

Configuring Secure Communication

This procedure describes how to configure secure communication for a Trident 3.x or Tri-GP 3.x
controller. Before beginning this procedure, the controller should already be added to the
network configuration. See Adding or Changing a Trident 3.x or Tri-GP 3.x Controller on
page 44 for instructions.
Note While configuring secure communication for a controller, you may encounter errors
relating to certificates that have expired. For assistance with troubleshooting such errors,
contact Global Customer Support (see Technical Support on page ix).

Procedure
1 Verify that a network configuration is not currently open.
2 On the File menu, click Open Network Configuration. The Network Nodes tree opens
in the left pane.
3 Right-click the node name of the controller you want to configure secure communication
for, and then click Edit. The Network Node Configuration dialog box appears.

4 Select the Use Secure Communication check box. The Secure Communication
Configuration section appears.

Secure
Communication
Configuration
Section

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

58 Chapter 1 Getting Started

5 Click the browse button to search for a certificate. The Select Windows Certificate
Store dialog box appears.

6 Select one of the following options and then click OK.

Property Action
Browse Certificates Installed Searches for certificates installed in the current user
for the Current User certificate store.
Browse Certificates installed Searches for certificates installed in the local machine
for the Local Machine certificate store. You must have Windows administrator
permissions to access the local machine certificate store
and select a certificate.

The list of available certificates in the certificate store you selected appears.

7 Select the certificate you want to use and then click OK.
Note To view detailed information about a certificate prior to selecting it, click the
corresponding link.
The Certificate Name and Certificate ID appears in the Network Node Configuration
dialog box.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Enabling Secure Communication 59

8 Click OK to save your changes.

9 Repeat steps 3–8 for each node you want to configure to use secure communication.
10 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 do not have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

60 Chapter 1 Getting Started

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 60
• Moving, Docking, and Floating Window Panes on page 61
• Maximizing, Restoring, and Resizing Windows on page 62
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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Customizing Your Workspace 61

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 88 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.

The Network Nodes tree opens in the left pane.

See Setting Up a Network Configuration on page 32 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

62 Chapter 1 Getting Started

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 65, and Monitoring
Communication Status Information on page 91, for more information about these windows.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 2
Monitoring Controller Hardware

Overview 64
System Overview and Module Status Windows 65
Understanding External Faults 72
Understanding Internal Faults 74
Clearing Faults on All Modules 76
Monitoring Output Voter Diagnostics (OVD) 77
Monitoring Trident/Tri-GP SDO OVD and Supervision Status 78
Displaying Firmware Versions 79

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

64 Chapter 2 Monitoring Controller Hardware

Overview
The Enhanced Diagnostic Monitor allows you to identify alarms on Tricon chassis and Trident
or Tri-GP 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 or Tri-GP supervised digital output modules, and display the
firmware version numbers for all types of modules.
For corrective actions (such as replacing a module with a spare), see the maintenance guidelines
in the appropriate Planning and Installation Guide for your controller.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 System Overview and Module Status Windows 65

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 123.) 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 91.

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 Green icon for Red icon for
for selecting full chassis with chassis with
chassis display alarm off alarm on

The System Overview window can be a floating window or a maximized window. For more
information, see Customizing Your Workspace on page 60.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

66 Chapter 2 Monitoring Controller Hardware

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 60.

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 System Overview and Module Status Windows 67

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

68 Chapter 2 Monitoring Controller Hardware

Fault Information Areas

Each Module Status dialog box includes an area for the left module and the right module in a
slot. The module areas have properties which provide information about faults.

Property Description
Status Displays a message that describes the type of fault.
Point Faults Displays the number of each point with a fault condition.

Note When the Tricon controller 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 system
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/Tri-GP System Overview Window

The Trident/Tri-GP 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 60.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 System Overview and Module Status Windows 69

Trident/Tri-GP 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 60.

Changing the Trident/Tri-GP Module Status Window View

This procedure explains how to change the view of the modules in a Trident/Tri-GP 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

70 Chapter 2 Monitoring Controller Hardware

Trident/Tri-GP 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/Tri-GP 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 System Overview and Module Status Windows 71

Trident/Tri-GP 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/Tri-GP SDO OVD and Supervision
Status on page 78 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.)

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

72 Chapter 2 Monitoring Controller Hardware

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 controllers, the LOAD/FUSE indicator (if available) on the affected module
turns yellow.
• For Trident or Tri-GP controllers, 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 controllers, 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 or Tri-GP controllers, 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 Global Customer Support (GCS) Center for assistance.
For contact information, see Technical Support on page ix.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Understanding External Faults 73

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 49.
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 controllers, click the Field Faults and Power Faults tabs.

• For Trident or Tri-GP controllers, 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

74 Chapter 2 Monitoring Controller Hardware

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.
Invensys 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.

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 Global Customer Support (GCS) Center for assistance.
For contact information, see Technical Support on page ix.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Understanding Internal Faults 75

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
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 red indicator.
3 In the Module Status dialog box, click these tabs to find the fault messages:
• For Tricon controllers, click the Voter Faults tab.

• For Trident or Tri-GP controllers, on the Left Module and Right Module tabs, click
the Current Faults setting.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

76 Chapter 2 Monitoring Controller Hardware

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 27.
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 50), 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 or UCM installed, or a Trident 2.x/3.x or Tri-GP node with a
communication module installed, verify in TriStation 1131 that the IP address of the
diagnostic PC has read/write access to the communication module via the TriStation
protocol.

If the client access list has been configured so that the IP address of the diagnostic PC has
read-only access to the communication module via the TriStation protocol, you will be
unable to clear all faults. For more information, see the TriStation 1131 Developer’s Guide.

Normally, a fault is cleared automatically when the problem causing the

WARNING fault has been repaired, and there is no need to use the Clear Faults 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 Global Customer Support (GCS) Center for assistance.
For contact information, see Technical Support on page ix.

Procedure
1 Ensure that all faults have been identified and corrected, as described in Locating and
Correcting External Faults on page 73 and Locating Internal Faults on page 75.
2 For a Tricon controller, 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/Tri-GP IOP alarm turns off (green), and the Fault
indicators on the modules with faults turn off (gray).

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Output Voter Diagnostics (OVD) 77

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 or Tri-GP controller (see Monitoring Trident/Tri-GP SDO OVD
and Supervision Status on page 78), you cannot monitor the OVD status of DO points in
the Trident or Tri-GP controller. To monitor the OVD state of DO points, you must use
the SYS_DO16_STATUS function block in conjunction with the UNPACK16 function
block, and view these function blocks in the Controller Panel of TriStation 1131 during
online execution. 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

78 Chapter 2 Monitoring Controller Hardware

Monitoring Trident/Tri-GP SDO OVD and Supervision

Status
The Trident model 34111 and Tri-GP model 3411S2 Supervised Digital Output (SDO) modules
provide loop supervision to field devices in fire and gas applications. 16 points are available;
each point can be independently configured.
This procedure explains how to monitor the supervision and output voter diagnostics (OVD)
status of Trident and Tri-GP 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:

Property Description
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 2.1 and later systems. See the Planning
and Installation Guide for Trident v2 Systems for more information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Displaying Firmware Versions 79

Displaying Firmware Versions

This procedure explains how to display the firmware version numbers of all modules in a
Tricon chassis or Trident/Tri-GP IOP. Typically, you only need to know the firmware version
numbers when requested by a 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 88.

• 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

80 Chapter 2 Monitoring Controller Hardware

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 3
Monitoring Controller Status

Overview 82
Viewing Controller Status 83
Monitoring and Changing the Scan Time 85
Monitoring and Changing the Memory Allocation 87
Viewing Data in the Messages Pane 88
Viewing Program Execution Times 90
Monitoring Communication Status Information 91

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

82 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 32.
• 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 32.
• Open the nodes you want to monitor. See Opening a Network Node on page 49.
Note You can also access controller performance and project information using function
blocks in the TriStation 1131 standard libraries, and for Trident or Tri-GP, using system
attributes. For more information, see the TriStation 1131 Libraries Reference.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Viewing Controller Status 83

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 123.) 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/Tri-GP Displays the system version of the connected controller.
Version Applicable to Tricon, Trident 2.x/3.x, and Tri-GP 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

84 Chapter 3 Monitoring Controller Status

Property Action
Calendar Displays the current time of the controller being monitored in
the day/date/hour/minute/second/time zone format.
Note: For Tricon, if the controller's time zone is changed
while the Enhanced Diagnostic Monitor is connected,
the updated time zone will be displayed only after
you disconnect, and then reconnect to the controller.
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 85).
Maximum Memory Displays the maximum amount of memory the controller
originally made available to the TriStation 1131 project.
Free Memory Displays the amount of memory available for project
expansion.
Key Stop/Position For Tricon controllers, 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring and Changing the Scan Time 85

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, Standard and
Enhanced Peer-to-Peer, and so on.)
• Write outputs
This procedure explains how to monitor the scan time in the System Overview window, and
then change the scan time using the TriStation 1131 software.

Procedure
1 Connect to the node (controller) you want to monitor.
2 In the System Overview tree, click System Overview.
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 123.) 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 86.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

86 Chapter 3 Monitoring Controller Status

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.
You must ensure that the requested scan time is always greater than the minimum scan time to
guarantee that the controller provides a deterministic response time. The minimum scan time is
a value that the controller calculates based on the hardware configuration defined in your
TriStation 1131 project and information obtained from the controller. The minimum scan time
is calculated as the greater of the following two values:
• Application Scan Time: The amount of time it takes the controller to execute all the
programs in the application running on the controller. The application scan time is
displayed in the Set Scan Time dialog box in TriStation 1131.
• Estimated I/O Poll Time: The maximum time needed by the controller to obtain data
from input modules. The estimated I/O poll time is displayed on the System Overview
window.
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 or 3009 Main Processors, the range is 20 to 450
milliseconds.
• For Trident and Tri-GP systems, the range is 10 to 450 milliseconds.
If the scan time that is set is less than the minimum scan time, a message appears,
prompting you to change the scan time to a recommended value. You must change the
scan time to at least the recommended value, as you will be unable to build or download
your application if the requested scan time is less than the minimum scan time.
5 Click OK to save your changes.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring and Changing the Memory Allocation 87

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
1 Connect to the node (controller) you want to monitor.
2 In the System Overview tree, click System Overview.
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 1131 project. The amount of memory for
memory points is set when a TriStation 1131 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

88 Chapter 3 Monitoring Controller Status

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 60 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 91.

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Viewing Data in the Messages Pane 89

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 90.
Display Firmware Versions The firmware version numbers of all modules in a Tricon
Command chassis or Trident/Tri-GP IOP. See Displaying Firmware
Versions on page 79.
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 128.
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 51.
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 163.
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 121.
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 121.
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 163.
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 163.
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 163.

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

90 Chapter 3 Monitoring Controller Status

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
1 Connect to the node (controller) you want to monitor.
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 88.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 91

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 10.3 or later controllers with a TCM installed
• Tricon 11.0 or later controllers with a UCM installed
• Trident 2.0 and later controllers with a CM installed
• Trident 3.0 controllers with a CIM installed
• Tri-GP 2.1.x and later controllers with a CM installed
• Tri-GP 3.0 controllers with a CIM 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, Invensys 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 83).
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 123.) Once you stop event
collection, communication status updates will automatically begin again.
Topics in this section include:
• Monitoring Tricon Communication Status Information on page 92
• Monitoring Trident or Tri-GP Communication Status Information on page 100
• Saving Communication Status Information to a File on page 108

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

92 Chapter 3 Monitoring Controller Status

Monitoring Tricon Communication Status Information

Each connected Tricon controller can have up to four TCMs or two UCMs that can be monitored
separately, but not simultaneously. Communication status information is updated by the
TCM/UCM every second.
Communication status information is available only for the following:
• Model 4351B, 4352B, 4353, and 4354 TCMs installed in Tricon 10.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).
• Model 4610 UCMs installed in Tricon 11.0 and later systems.
Topics in this section include:
• Viewing Tricon Communication Status Data on page 92
• Tricon Communication Status Information on page 95

Viewing Tricon Communication Status Data

This procedure describes how to connect to a Tricon controller and view communication status
information for a selected TCM or UCM.

Procedure
1 Connect to the node (controller) whose TCM/UCM 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/UCM you want to view
communication status information for.
The module selection list includes only TCMs/UCMs 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.
Note When the Enhanced Diagnostic Monitor is connected to a Tricon 11.1
controller via the UCM, the “Bad TMI Version number” error message appears
in the Messages pane. As this does not have any impact on the display of
communication status information, it can be safely ignored.
This error message does not appear when the Enhanced Diagnostic Monitor is
connected to a Tricon 11.1 controller via the TCM.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 93

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 60.
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 95.
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 123.) Once you stop event collection,
communication status information will begin updating again.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

94 Chapter 3 Monitoring Controller Status

Troubleshooting Tricon Communication Status Connection Problems

The following are common problems you may encounter while trying to view TCM or UCM
communication status information.

Problem Solution
You do not 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 10.3 and later systems.
Communication status information is also available for model 4610
UCMs installed in Tricon 11.0 and later systems.
You cannot connect to the • Verify that you are connected to the node via a network connection.
selected TCM/UCM. 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 37.
• Verify that the Management UDP Port Number configured for the
node matches the Management UDP Port Number configured for
the TCM/UCM 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 37.
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 51.
• You chose to stop refreshing communication status information
during event collection. (See Starting and Stopping Event
Collection on page 123.) Stop event collection to restart
communication status information updates.
All communication status The selected TCM/UCM is physically installed in the controller, but it
values are displayed as has not yet been configured in the downloaded application. Use
question marks (?) instead TriStation 1131 to configure the TCM/UCM and then download the
of actual values. application to the controller.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 95

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 or
UCM.

Property Description
Percent idle The current idle percentage of the TCM or UCM, based on the previous 15
seconds.
Free memory The percentage of free memory available on the TCM/UCM.

Network Status
Network status information provides data about communications on each of the TCM or UCM
network ports—NET 1 and NET 2.

Property Description
Link status Indicates the link status of the NET 1 or NET 2 port on the TCM/UCM.
• 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/UCM is receiving messages via the NET 1 or NET
messages 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 TCM/UCM at the same time.
When collisions are encountered, the TCM/UCM will send back a request to try sending the data again.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

96 Chapter 3 Monitoring Controller Status

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).

Property Description
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 10.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 or UCM.

Property Description
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.
This number does not include multicast connections,
because the communication module cannot detect how
many clients have joined the multicast group.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 97

Property Description
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/UCM, 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 or UCM’s Modbus TCP
ports. Model 4351B/4352B TCMs and model 4610 UCMs have 16 ports; model 4353 and 4354
TCMs have 4 ports.

Property Description
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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

98 Chapter 3 Monitoring Controller Status

Modbus Serial Status

Modbus Serial status information provides data about each of the TCM’s serial Modbus ports
(1–4) and UCM serial Modbus ports (1 and 2).

Property Description
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 (Standard and Enhanced) status information provides data about the Peer-to-Peer
network established on one or both of the following network ports:
• TCM on Tricon 11.0 or earlier controllers or UCM (NET 1 and NET 2)—31 nodes are
available on each port.
• TCM on Tricon 11.1 or later controllers (NET 1 and NET 2)—254 nodes are available on
each port.
• UCM on Tricon 11.1 or later controllers (NET 1 and NET 2)—31 nodes are available on
each port.

Property Description
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 99

Property Description
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 or UCM’s
printer port.

Property Description
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 or UCM via the TriStation protocol.

Property Description
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

100 Chapter 3 Monitoring Controller Status

Monitoring Trident or Tri-GP Communication Status Information

Each communication module (CM or CIM) installed in a connected Trident 2.x/3.x or Tri-GP
controller—up to two—can be monitored separately, but not simultaneously. Communication
status information is updated by the CM or CIM every five seconds.
Note Communication status information is not available for Trident 1.x controllers.
Topics in this section include:
• Viewing Trident or Tri-GP Communication Status Data on page 100
• Trident/Tri-GP Communication Status Information on page 103

Viewing Trident or Tri-GP Communication Status Data

This procedure describes how to connect to a Trident 2.x/3.x or Tri-GP controller and view
communication status information for a selected CM or CIM.

Procedure
1 Connect to the node (controller) whose communication status you want to view.
— For Trident 1.x/2.x and Tri-GP 2.x controllers, you must be connected to the
node via a network connection using the CM’s IP address. You cannot view
the communication status information when you are connected to a node via a
serial connection, or when connected over the network via the MP’s IP
address.
— For Trident 3.x and Tri-GP 3.x controllers, you must be connected to the node
via a network connection using the CM or CIM’s IP address, or the MP’s IP
address. If you have a CIM installed, you can also be connected to the node via
a serial connection. You cannot view the communication status information
for a CM when you are connected to a node via a serial connection.
Note See Setting Up a Network Configuration on page 32 for more information about
configuring the connection to a controller.
2 In the System Overview tree, click Communication Status.
3 In the Communication Status window, select the CM or CIM you want to view
communication status information for.
The module selection list includes only CMs and CIMs 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 101

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 60.
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/Tri-GP Communication Status
Information on page 103.
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 123.) Once you stop event collection, the
communication status information will begin updating again.

Troubleshooting Trident or Tri-GP Communication Status Connection Problems

The following are common problems you may encounter while trying to view Trident 2.x/3.x
or Tri-GP communication status information.

Problem Solution
You do not 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 2.x/3.x and Tri-GP systems; Trident 1.x systems are
not supported.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

102 Chapter 3 Monitoring Controller Status

Problem Solution
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 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 or Tri-GP controller, see Adding or Changing a
Trident 1.x/2.x or Tri-GP 2.x Controller on page 40.
You cannot connect to the • Verify that you are connected to the node via a network or
selected CIM. serial connection.
• Verify that the CIM module is physically installed and has
been configured in TriStation 1131.
For more information about configuring the connection to the
Trident or Tri-GP controller, see Adding or Changing a
Trident 3.x or Tri-GP 3.x Controller on page 44.
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 51.
• You chose to stop refreshing communication status
information during event collection. (See Starting and
Stopping Event Collection on page 123.) Stop event
collection to restart communication status information
updates.
All communication status values The selected CM or CIM is physically installed in the
are displayed as question marks controller, but it has not yet been configured in the
(?) instead of actual values. downloaded application. Use TriStation 1131 to configure the
CM or CIM and then download the application to the
controller.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 103

Trident/Tri-GP 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 or CIM.

Property Description
Percent idle The CM’s or CIM’s current idle percentage, based on the previous
15 seconds.
Free memory The percentage of free memory available on the CM or CIM.

Network Status
Network status information provides data about communications on each of the CM’s or CIM’s
network ports—NET 1 and NET 2.

Property Description
Link status Indicates the link status of the NET 1 or NET 2 port on the CM or
CIM.
• 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 or CIM 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 or CIM at the same time.
When collisions are encountered, the CM or CIM will send back a request to try sending the data again.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

104 Chapter 3 Monitoring Controller Status

OPC Status
OPC status information provides data about the health and activity of the CIM’s OPC UA
server. This information is not available for CMs, because they do not have an OPC UA server.

Property Description
Number of sessions The total number of active OPC client sessions on the OPC
UA server.
Number of subscriptions The total number of OPC items currently subscribed to the
OPC UA server.
Number of monitored items The total number of monitored items across all active OPC
client sessions.
Number of writes The total number of write commands on the OPC UA
server.
Number of active alarms The total number of alarms that are in active state on the
OPC UA server.
Number of alarm confirms The total number of alarms that are confirmed.
Number of alarm The total number of alarm acknowledgments that have
acknowledgements occurred on the OPC UA server.
Number of configured alarms The total number of alarms that are configured on the OPC
UA server.
Number of disabled alarms The total number of alarms that are in disabled state on the
OPC UA server.
Number of unacked alarms The total number of unacknowledged alarms available on
the OPC UA server.
Number of bypassed alarms The total number of bypassed devices/tagnames.
Number of bypasses The total number of connections that have been bypassed.

TSAA Status
TSAA status information provides data about the TSAA server running on the CM or CIM.

Property Description
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.
This number does not include multicast connections,
because the communication module cannot detect how
many clients have joined the multicast group.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 105

Property Description
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 or CIM, 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 or CIM’s four Modbus
TCP ports.

Property Description
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

106 Chapter 3 Monitoring Controller Status

Modbus Serial Status

Modbus Serial status information provides data about each of the CM’s or CIM’s serial Modbus
ports (1–3).

Property Description
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 (Standard and Enhanced) status information provides data about the Peer-to-Peer
network established on one or both of the CM’s or CIM’s network ports (NET 1 and NET 2). 63
nodes are available on each port.

Property Description
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Monitoring Communication Status Information 107

Property Description
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 or CIM’s
printer port.

Property Description
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
or CIM via the TriStation protocol.

Property Description
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

108 Chapter 3 Monitoring Controller Status

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 4
Collecting and Viewing Events

Overview 110
Interpreting System Events 111
Interpreting the Board Address Display Format 116
Opening the Events and Events Summary Panes 119
Managing Event Log Files 121
Starting and Stopping Event Collection 123
Changing the Default Event Collection Settings 125
Controlling Event Visibility 128
Viewing an Existing Event Log File 136
Exporting an Event Log File 137
Generating Event and Alarm Data Reports 139

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

110 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 32.
• 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 32.
• Open the nodes you want to collect events for. See Opening a Network Node on
page 49.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Interpreting System Events 111

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.
Topics in this section include:
• Event Severity Levels on page 111
• Event List Information on page 112
• Events Summary Information on page 113
• Important Information About Event Retention on page 114

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 system to run in a
degraded (Duplex or Single) mode. Immediate action should
be taken to return the Tricon system to TMR mode.

Trident and Tri-GP 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 or Tri-GP 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 or Tri-GP system to
run in a degraded (Duplex or Single) mode. Immediate action
should be taken to return the system to TMR mode.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

112 Chapter 4 Collecting and Viewing Events

Event List Information

The following information is provided for each event in the Events pane:

Property Description
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 GMT time zone, regardless of the
time zone that is selected for displaying events (see Changing the
Default Event Collection Settings on page 125).
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 G, 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 116 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Interpreting System Events 113

Events Summary Information

The following information is provided in the Events Summary pane:

Property Description
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 79.
• 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.
Displayed Time The time zone that event times are currently displayed in. See Changing
Zone the Default Event Collection Settings on page 125 for more information
about changing the displayed time zone.
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.”

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

114 Chapter 4 Collecting and Viewing Events

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 controller through a TCM (except for models 4351 and 4352)
or UCM, all system events are retained in the TCM’s/UCM’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 controller 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.
• When you disconnect and then reconnect to the controller, and start another event
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 controller.

Trident and Tri-GP Event Retention

If you are connecting to a Trident 2.x/3.x or Tri-GP controller via the communication module
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.
• When you disconnect and then reconnect to the controller, and start another event
collection session, some of the events that were collected previously will be collected
again.
• If 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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Interpreting System Events 115

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.
• When you disconnect and then reconnect to the controller, and start another event
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 or Tri-GP controller you are connected to.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

116 Chapter 4 Collecting and Viewing Events

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, Trident, or Tri-GP controller. This section describes how to
interpret the board address display, which is different for Tricon and Trident/Tri-GP
controllers.
Topics in this section include:
• Interpreting and Changing the Tricon Board Address Display Format on page 116
• Interpreting the Trident or Tri-GP Board Address Display Format on page 118

Interpreting and Changing the Tricon Board Address Display Format

For Tricon controllers, 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 130.
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 E, 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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Interpreting the Board Address Display Format 117

a mismatch between the physical chassis hardware and the chassis type downloaded in
the TriStation 1131 project.
Change the board address display format to hexadecimal, and then use the conversion
tables provided in Appendix E, 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.

Property Description
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 E, Tricon Chassis and Slot
Reference.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

118 Chapter 4 Collecting and Viewing Events

Interpreting the Trident or Tri-GP 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 or Tri-GP IOP. You cannot change the board address display
format for Trident or Tri-GP controllers.
• 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 communication modules (CM and CIM), the format is MP.slot, CM.slot, or
CIM.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 and Tri-GP baseplate and slot locations, see Appendix F,
Trident and Tri-GP 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 or Tri-GP Board Address Event Filter on page 132.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Opening the Events and Events Summary Panes 119

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.
2 Do one of the following:
• Maximize the System Overview window (see Customizing Your Workspace on
page 60).
• 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

120 Chapter 4 Collecting and Viewing Events

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 60 for more information about customizing
the Enhanced Diagnostic Monitor workspace to suit your needs.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Managing Event Log Files 121

Managing Event Log Files

During event collection, system events are saved to either a Tricon event log file (.tce) or a
Trident/Tri-GP 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 do not 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, Invensys recommends 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

122 Chapter 4 Collecting and Viewing Events

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 125.
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.
This file naming convention applies to the automatically generated event log files also.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting and Stopping Event Collection 123

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, Trident, or Tri-GP 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 52), 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 50.
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
or UCM 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 136.
2 Connect to the node (controller) you want to collect events from.
• For Tricon controllers, you can be connected to the node via a network connection
to the TCM, UCM or NCM, or via a serial connection to the EICM.
• For Trident 2.x/3.x or Tri-GP controllers, you can be connected to the node via a
network connection to the MP or communication module, or via a serial connection
to the communication module.
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:

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

124 Chapter 4 Collecting and Viewing Events

• 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 default directory where you are trying to
create or save the event log file. If you do not 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 128 and Modifying the Event Exclusion List on
page 135.
If you’ve started collecting events, but you do not see the event list in the window, you need to
open the Events pane. See Opening the Events and Events Summary Panes on page 119.

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Changing the Default Event Collection Settings 125

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
1 In the Network Configuration tree, double-click the node (controller) you want to
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 Options tab.

4 Edit these properties:

Property Description
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

126 Chapter 4 Collecting and Viewing Events

Property Description
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 122 for more
information about how the Enhanced Diagnostic Monitor handles
event log files when they reach their maximum size.
Time Zone Select the time zone you want to display event times in.
Event times can be displayed in one of the following time zones:
• The time zone of the PC that is collecting events (the diagnostic
PC). For example, if the diagnostic PC is using the Eastern
Standard (EST) time zone, event times will be displayed using
EST.
• The time zone of the controller the events are being collected
from. For example, if the controller where events are
originating from is using the Pacific Standard (PST) time zone,
event times will be displayed using PST.
• Greenwich Mean Time (GMT). Regardless of the time zone the
diagnostic PC or controller are using, event times are
displayed using GMT. For example, even if the controller is
using PST, event times will be converted to GMT when they
are displayed.
The default is GMT.
Note: Regardless of the time zone events are displayed in, all
events are saved to the events log file in GMT.

5 Click OK to save your changes.

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 Options tab.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Changing the Default Event Collection Settings 127

Changing the Default Event Log File Directory

This section describes how to change the default event log file directory. The default event log
file directory configuration applies to all nodes.

Procedure
1 On the File menu, click Open Network Configuration, and select the file you want to
change the default event log file directory for.
The Network Nodes tree opens in the left pane.
2 Right-click any node name on the tree, and then click Edit.
The Network Node Configuration dialog box appears.
3 Click the browse button next to the Default Event Log File Directory property. In the
dialog box that appears, select the path where event log files will be saved. The default
is C:\ProgramData\Triconex\Enhanced Diagnostic Monitor\Data.
You must have write access to this location. If you do not 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.
For more information about the event log files, see Collecting and Viewing Events on
page 109.
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.
4 Click OK to save your changes.
5 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 do not have access to this directory, save it to
another location, or contact your system administrator to obtain write access to
the desired location.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

128 Chapter 4 Collecting and Viewing Events

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 128
• Configuring the Board Address Event Filter on page 130
• Modifying the Event Exclusion List on page 135

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
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 most 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 Edit these properties.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Controlling Event Visibility 129

Property Description
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 130.
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.
4 Click OK to save your changes.
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 Options tab.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

130 Chapter 4 Collecting and Viewing Events

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.
Topics in this section include:
• Configuring the Tricon Board Address Event Filter on page 130
• Configuring the Trident or Tri-GP Board Address Event Filter on page 132

Configuring the Tricon Board Address Event Filter

By default, all chassis and slots are selected for inclusion in the event list.

Procedure
1 In the Network Configuration tree, double-click the node (controller) you want to
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Controlling Event Visibility 131

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.
7 Do one of the following:
• 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

132 Chapter 4 Collecting and Viewing Events

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 130. For chassis slot location diagrams, see
Appendix E, Tricon Chassis and Slot Reference.

Configuring the Trident or Tri-GP Board Address Event Filter

By default, all IOPs and baseplates, in addition to all MPs, CMs, and CIMs, are selected for
inclusion in the event list.

Procedure
1 In the Network Configuration tree, double-click the Trident or Tri-GP node (controller)
you want to 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 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 or CIMs) in
the Trident or Tri-GP system is also included, in addition to the IOP nodes.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Controlling Event Visibility 133

Note The IOP and baseplate tree includes nodes only for the IOPs that are configured
in the Trident or Tri-GP system that events are currently being collected from, or
were previously collected from (if you are viewing an existing log file).
7 Do one of the following:
• 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

134 Chapter 4 Collecting and Viewing Events

Tips for Trident or Tri-GP IOP and Baseplate Filtering

• Select the Trident or Tri-GP check box to select all IOPs and all baseplates, including all
MPs, CMs, and CIMs, at once.
• To view events for all baseplates in a selected IOP:
— Clear the Trident or Tri-GP check box. This automatically clears the check boxes for
all MPs/CMs/CIMs 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 F, Trident and Tri-GP
Baseplate and Slot Reference.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Controlling Event Visibility 135

Modifying the Event Exclusion List

During event collection, you can choose to exclude specific event messages from the event list.
For example, if you do not 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
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 event exclusion list,
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 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.
5 Click OK to save your changes.
The event exclusion list is immediately implemented only for the node that is currently
active.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

136 Chapter 4 Collecting and Viewing Events

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 254
open event log files (only one event log file can be opened per node; 254 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 124.
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 do not see the event list in the window, you need to open the Events pane.
See Opening the Events and Events Summary Panes on page 119.
5 Use the event filtering options to customize the event view to your specific needs. See
Controlling Event Visibility on page 128.

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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Exporting an Event Log File 137

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.
2 On the Events menu, select Open Event File.
3 Browse to locate the event log file you want to export, and then click Open.
The list of events saved in the file appears in the Events pane.
Note If you do not see the event list in the window, you need to open the Events pane.
See Opening the Events and Events Summary Panes on page 119.
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/Tri-GP) Text 5
MESSAGE Text 255

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

138 Chapter 4 Collecting and Viewing Events

Opening an Exported Event Log File in Microsoft Access

If you will be opening the exported file in Microsoft Access 2010, 2007, 2003, or 2000, 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Generating Event and Alarm Data Reports 139

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 SAP 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.
Topics in this section include:
• Generating Event Data Reports on page 139
• Generating Alarm Data Reports on page 141
• Exporting Report Data on page 143

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 137.
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 143).

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.
2 On the Events menu, select Open Event File.
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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

140 Chapter 4 Collecting and Viewing Events

Note If you do not see the event list in the window, you need to open the Events pane.
See Opening the Events and Events Summary Panes on page 119.
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 128.
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 141 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 instructions,
Command see Exporting Report Data on page 143.
Refresh Click to refresh the display, which re-loads event data to the
Command report.
Size of View Select or type a percentage to change the size of the report view.
Command

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 143.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Generating Event and Alarm Data Reports 141

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 143).

Procedure
1 Connect to the node (controller) you want to collect alarm information for. See Opening
a Network Node on page 49 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 139 for more information.
3 Perform any of the following tasks in the report viewer.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

142 Chapter 4 Collecting and Viewing Events

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 143.
Refresh Click to refresh the display, which re-loads event data to
Command the report.
Size of View Select or type a percentage to change the size of the report
Command 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 143.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Generating Event and Alarm Data Reports 143

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 139 or Generating Alarm Data Reports on page 141.
The report opens automatically in the Crystal Reports viewer window.

2 On the report viewer toolbar, click the Export Report button . The Export Report
dialog box appears.

3 In the File name field, enter a name for the exported file.
If you do not enter .rpt as the file extension, it is automatically appended to the file name.
4 Click Save, and wait while the Enhanced Diagnostic Monitor completes exporting the
data to the new file.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

144 Chapter 4 Collecting and Viewing Events

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 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 Options tab
• Set Events Options button > Event Options dialog box > General Options tab

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

146 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

Browse Certificates Installed for the Current User/Local Machine

The Browse Certificates property searches for certificates installed on the diagnostic PC. You
can choose to search for certificates in either of the following Windows certificate stores:
• Current User: Contains certificates that are local to the currently logged-in user.
• Local Machine: Contains certificates that are local to the computer, not to a specific
user. You must have Windows administrator permissions to access and use local
machine certificates.

Applies To
Secure communication

Location
Network Node Configuration dialog box > browse for certificate > Select Windows Certificate
Store dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Calendar 147

Calendar
The Calendar property displays the current time of the controller being monitored in the
day/date/hour/minute/second/time zone format.
Note For Tricon, if the controller's time zone is changed while the Enhanced Diagnostic
Monitor is connected, the updated time zone will be displayed only after you
disconnect, and then reconnect to the controller.

Applies To
Controllers

Location
System Overview window

Certificate ID
The Certificate ID property displays the certificate’s unique identification number. The
Certificate ID is obtained automatically when you select the certificate you want to use.

Applies To
Secure communication

Location
Network Nodes tree or menu > right-click a node > Add or Edit command > Network Node
Configuration dialog box

Certificate Name
The Certificate Name property displays the name of the certificate. The Certificate Name is
obtained automatically when you select the certificate you want to use.

Applies To
Secure communication

Location
Network Nodes tree or menu > right-click a node > Add or Edit command > Network Node
Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

148 Appendix A Commands and Properties

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

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 76.
You must have the appropriate user security level to use this command. For more information,
see Changing the Security Level for Privileges on page 27.

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Close Network Configuration Command 149

Close Network Configuration Command

The Close Network Configuration command closes an open network configuration.

Applies To
Network configurations, nodes

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, Trident, and Tri-GP 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

150 Appendix A Commands and Properties

• 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/3.x controller.
For Tri-GP, the settings are:
• Network for an Ethernet (TCP/IP) connection.
• Serial for a serial (Modbus) connection to a Tri-GP 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

Controller Type
The Controller Type property allows you to specify a Tricon, Trident, or Tri-GP controller in a
network node configuration.

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

Copy Command
The Copy command copies selected messages from the Messages pane and places them on the
clipboard.

Applies To
Message text

Location
View menu > Messages command > right-click in Messages pane

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Copy All Items to Clipboard 151

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 or Tri-GP controller

Location
Trident or Tri-GP Module Status window > double-click faulting module > Module Status
dialog box > Left, Middle, or Right Module tab

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

152 Appendix A Commands and Properties

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
View menu > Messages command > right-click in Messages pane

Default Event Log File Directory

The Default Event Log File Directory property specifies the default path for event log files. This
path applies to all nodes.
The default is C:\ProgramData\Triconex\Enhanced Diagnostic Monitor\Data.
You must have write access to this location. If you do not 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
• Network Nodes tree or menu > right-click a node > Add or Edit command > Network
Node Configuration dialog box

Delete Command
The Delete command allows you to remove a node from a network configuration.

Applies To
Network Nodes tree, nodes, network configurations

Locations
Network Node menu, or right-click on Network Nodes tree

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Diagnostic Alarms Command 153

Diagnostic Alarms Command

The Diagnostic Alarms command generates an alarm data report from the currently connected
controller.

Applies To
Tricon, Trident, and Tri-GP controllers

Locations
Reports menu

Disconnect Command
The Disconnect command stops the diagnostic PC from communicating with the active node
(controller).

Applies To
Network configurations, nodes

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

154 Appendix A Commands and Properties

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. The Tricon board address display format can be changed as often as
needed, and at any time during event collection or event log viewing.

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.
The Tricon board address display format can be changed as often as needed, and at any time
during event collection or event log viewing.

Applies To
Tricon event list

Locations
View menu > Event

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Display Firmware Versions Command 155

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, Trident, and Tri-GP 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, Trident IOP, or Tri-GP IOP. The firmware versions are visible in
the Messages pane. Typically, this command is used only if requested by a Customer Support
Engineer for diagnostic purposes.

Applies To
Tricon, Trident, and Tri-GP 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
Network Node menu, or right-click on Network Nodes tree

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

156 Appendix A Commands and Properties

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
• Events menu > Options command > Event Options dialog box > Event Filters tab
• Set Events Options button > Event Options dialog box > Event Filters tab

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 178.

Applies To
User security

Location
Permissions menu > Edit Users > Permissions dialog box > Security Setting tab

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Events and Diagnostic Alarms Command 157

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, Trident, and Tri-GP 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 do not 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

Execute Debug Commands

The Execute Debug Commands command generates a data report for the currently connected
controller. This report (also known as a diagread file) contains information about the controller
such as the build number, communication status, and other diagnostic parameters that will
assist Customer Support in troubleshooting controller issues.
Available only when connected to a Trident 3.x or Tri-GP 3.x controller with a CIM installed.

Applies To
Trident/Tri-GP CIM

Location
Commands menu

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

158 Appendix A Commands and Properties

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 or Tri-GP controller

Location
Trident or Tri-GP 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.)

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Find Command 159

Applies To
Faults on a controller

Locations
• Trident or Tri-GP 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
View menu > Messages command > right-click in Messages pane

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
System Overview window

Get Defaults
The Get Defaults property resets all properties on the Event Filters tab to their default settings.

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

160 Appendix A Commands and Properties

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
• UCM: 192.168.0.<node number> for NET 1; 192.168.1.<node number> for NET 2
• Trident or Tri-GP MP: 192.168.255.<node number>, For Trident 2.x/3.x and Tri-GP
controllers, 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 169 and Secondary IP Address on page 173.

Applies To
Nodes in a network configuration

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Key Stop/Position 161

Key Stop/Position
For Tricon controllers, 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
System Overview window

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 or Tri-GP controllers, 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
Guide for your controller.

Applies To
Modules in Module Status window

Location
Module Status window > double-click a module > Module Status dialog box > Legend tab

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

162 Appendix A Commands and Properties

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,
Trident, or Tri-GP nodes in the network configuration.

Applies To
Tricon, Trident, and Tri-GP nodes

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, UCM, Trident 2.x/3.x, and Tri-GP
communication status information. The default value is 1510.
This must be the same value as the Management UDP Port Number property in the TCM, UCM,
CM, or CIM Setup dialog box in TriStation 1131. For more information, see the TriStation 1131
Developer’s Guide.

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Max Events Per Log File 163

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.
This file naming convention applies to the automatically generated event log files also.
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
• Events menu > Options command > Event Options dialog box > General Options tab
• Set Events Options button > Event Options dialog box > General Options 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 163.
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
• Events menu > Options command > Event Options dialog box > General Options tab
• Set Events Options button > Event Options dialog box > General Options tab

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

164 Appendix A Commands and Properties

Maximum Memory
The Maximum Memory property displays the maximum amount of memory that a controller
makes available for a TriStation 1131 application. The maximum amount varies with the type of
controller (Tricon, Trident, or Tri-GP) and the version number.

Applies To
Applications, controllers

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Module Colors 165

Module Colors
For a Trident or Tri-GP Module Status window, the Module Colors area describes the colors that
represent the current state of each module.

Slot Color Module State

Yellow Module installed in the slot is not configured in the project.
Blue Slot is currently selected.
Red Module configured in the project is not installed in the slot.
Gray Module is configured in the project and installed in the slot.

Applies To
Modules in Trident or Tri-GP Module Status window

Location
Trident or Tri-GP 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
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

166 Appendix A Commands and Properties

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
• Events menu > Options command > Event Options dialog box > Event Filters tab
• Set Events Options button > Event Options dialog box > Event Filters tab

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
Network configurations, nodes

Locations
New button or File menu

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 NIC Index 167

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
• Network Node menu > 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 TRINODE001 through TRINODE254.

Applies To
Nodes in a network configuration

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

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 or Tri-GP).
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–254 for Tricon controllers and 1-63 for Trident and Tri-GP controllers.

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

168 Appendix A Commands and Properties

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Poll Time 169

Poll Time
The Poll Time property displays the maximum time needed by the controller to obtain data
from the input modules.
The poll time must not exceed the scan time. If it does, the scan time must be increased. For
instructions, see Changing the Scan Time Using TriStation 1131 on page 86.

Applies To
Applications, controllers

Location
System Overview window

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 controllers, 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 or Tri-GP controllers, 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 160 and Secondary IP Address on page 173 for more information.

Applies To
Nodes in a network configuration

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

170 Appendix A Commands and Properties

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, UCM, Trident 2.x/3.x, and Tri-
GP 2.x/3.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, UCM,
CM, or CIM Setup dialog box in TriStation 1131. For more information, see the TriStation 1131
Developer’s Guide.
See also Secondary Management UDP Port Number on page 174.

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

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 one of the
following controllers:
• Tricon 10.3 and later controllers with a TCM installed
• Tricon 11.0 and later controllers with a UCM installed
• Trident 2.0 and later controllers with a CM installed
• Trident 3.0 controllers with a CIM installed
• Tri-GP 2.1.x and later controllers with a CM installed
• Tri-GP 3.0 controllers with a CIM installed
The default value is 1502. This must be the same value as the TriStation UDP Port Number
property in the TCM, UCM, CM, or CIM Setup dialog box in TriStation 1131. For more
information, see the TriStation 1131 Developer’s Guide.
See also Secondary TriStation UDP Port Number on page 174.

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Print Command 171

Print Command
The Print command prints the selected contents of the Messages pane to a specified printer.

Applies To
Message text

Location
View menu > Messages command > right-click in Messages pane

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
Applications, controllers

Location
System Overview window

Restore Primary Connection

The Restore Primary Connection property enables the Enhanced Diagnostic Monitor to
automatically attempt to restore the primary connection to a Tricon, Trident 2.x/3.x, or Tri-GP
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 179.

Applies To
Tricon, Trident, and Tri-GP nodes

Location
Tools menu > Communication Options

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

172 Appendix A Commands and Properties

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
View menu > Messages command > right-click in Messages pane

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Scan Request/Actual 173

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
System Overview window

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 86.

Applies To
Controllers, applications

Location
System Overview window

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 1.x connection.
For Tricon controllers, 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 or Tri-GP controllers, 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.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

174 Appendix A Commands and Properties

See IP Address on page 160 and Primary IP Address on page 169 for more information.

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

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 TCM, UCM, Trident 2.x/3.x,
and Tri-GP 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 170 for more
information.

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

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
one of the following controllers:
• Tricon 10.3 and later controllers with a TCM installed
• Tricon 11.0 and later controllers with a UCM installed
• Trident 2.0 and later controllers with a CM installed
• Trident 3.0 controllers with a CIM installed
• Tri-GP 2.1.x and later controllers with a CM installed
• Tri-GP 3.0 controllers with a CIM installed
The default value is 1502.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Select All Command 175

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 170 for more
information.

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

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
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

176 Appendix A Commands and Properties

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
• Events menu > Options command > Event Options dialog box > Event Filters tab
• Set Events Options button > Event Options dialog box > Event Filters tab

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Show Line Numbers Command 177

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

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 controllers, the spare module is not installed.
For Trident or Tri-GP controllers, the slot is currently selected.
Red A module configured in the project is not installed in the slot.
For Trident or Tri-GP controllers, if a slot is outlined in red, a module in
the slot has a fault.
Gray For Trident or Tri-GP controllers, 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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

178 Appendix A Commands and Properties

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 156.

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
• Events menu > Options command > Event Options dialog box > Event Filters tab
• Set Events Options button > Event Options dialog box > Event Filters tab

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Status 179

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
Applications, controllers

Location
System Overview window

Status Bar Command

The Status Bar command toggles to display or hide the Status Bar. The default is On.

Applies To
Enhanced Diagnostic Monitor view

Location
View menu

Stop Collecting Events Command

The Stop Collecting Events command stops 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 Tricon,
Trident 2.x/3.x, or Tri-GP 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 173.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

180 Appendix A Commands and Properties

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 171.

Applies To
Tricon, Trident, and Tri-GP nodes

Location
Tools menu > Communication Options

Time Zone
The Time Zone property sets the time zone in which event times will be displayed. Event times
can be displayed in one of the following time zones:
• The time zone of the PC that is collecting events (the diagnostic PC).
• The time zone of the controller the events are being collected from.
• Greenwich Mean Time (GMT).
The default is GMT.

Applies To
Event list

Locations
• Events menu > Options command > Event Options dialog box > General Options tab
• Set Events Options button > Event Options dialog box > General Options tab

Toolbar Command
The Toolbar command toggles to display or hide the toolbar at the top of the screen. The default
is On.

Applies To
Enhanced Diagnostic Monitor view

Location
View menu

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon Version 181

Tricon Version
The Tricon Version property displays the system version number of the connected controller.

Applies To
Tricon controllers

Location
System Overview window

Trident/Tri-GP System Version

The Trident/Tri-GP 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 controller.

Applies To
Trident 2.x/3.x and Tri-GP controllers

Location
System Overview window

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 one of the following
controllers:
• Tricon 10.3 and later controllers with a TCM installed
• Tricon 11.0 and later controllers with a UCM installed
• Trident 2.0 and later controllers with a CM installed
• Trident 3.0 controllers with a CIM installed
• Tri-GP 2.1.x and later controllers with a CM installed
• Tri-GP 3.0 controllers with a CIM installed
The default value is 1502.
This must be the same value as the TriStation UDP Port Number property in the TCM, UCM,
CM, or CIM Setup dialog box in TriStation 1131. For more information, see the TriStation 1131
Developer’s Guide.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

182 Appendix A Commands and Properties

Applies To
Network configuration, nodes

Locations
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

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
Tools menu > Communication Options

Use Secure Communication

The Use Secure Communication property enables secure communication between the selected
node and the diagnostic PC. Available only for Trident/Tri-GP 3.x and later controllers with a
CIM installed.

Applies To
Secure communication

Location
• Network Nodes tree > right-click a node > Add or Edit command > Network Node
Configuration dialog box
• Network Node menu > Add or Edit command > Network Node Configuration dialog box

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 View Certificate Command 183

View Certificate Command

The View Certificate command displays detailed information for the selected certificate, such as
the certificate name, ID, issuer, and expiration date.

Applies To
Secure communication

Location
• Network Node Configuration dialog box > browse for certificate > Select Windows
Certificate Store dialog box > Select Certificate dialog box

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
Enhanced Diagnostic Monitor view

Locations
Workspace View button or View menu

Zoom Command
For Trident and Tri-GP controllers, 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 and Tri-GP modules

Locations
Zoom button or View menu

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

184 Appendix A Commands and Properties

Zoom To Fit Command

For Trident and Tri-GP controllers, the Zoom To Fit command toggles between a large and
small view of the modules in the Module Status window.

Applies To
Trident and Tri-GP modules

Locations
Zoom to Fit button or View menu

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 B
Security Guidelines

This appendix provides information about security guidelines that help prevent unauthorized
access to the Triconex Enhanced Diagnostic Monitor. Be sure to thoroughly read and
understand these guidelines before you configure and use the Enhanced Diagnostic Monitor.
When using the Enhanced Diagnostic Monitor in your environment, you should assess the
security threats to your system within the context of the overall plant architecture, any
applicable standards, industry best practices, and your corporate practices. This section
contains guidelines for security file backups, access to controllers, networks, and project files.
Note Invensys highly recommends that you register with the Global Customer Support (GCS)
center to ensure that you receive the latest information (via e-mail) about any security
vulnerabilities that may be found in Triconex products. Also, if you discover a security
vulnerability in a Triconex product, please immediately contact the GCS center for
assistance and further instructions.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

186 Appendix B Security Guidelines

Workstation Security
To reduce the security risks associated with the PC you have installed the Enhanced Diagnostic
Monitor on, follow these guidelines:
• If you use a domain controller/Active Directory, follow Microsoft’s recommended
practices for security.
• Create separate Windows accounts for each user
• Manage user accounts per your organization’s corporate policy
• Implement strong user authentication practices, including password strength and
periodic password change requirements
• Periodically monitor the Windows accounts available on the workstation to ensure that
only the necessary personnel can log on to the workstation, with the appropriate level
of access. Inactive or unnecessary user accounts should be removed.
• Review the Windows Security Event Log to monitor log on and log off activity on all
workstations, and to detect attempted unauthorized activity.
• Disable unused USB ports.
• Use firewalls and other security devices or settings to limit access to the host network,
based on your security risk assessment.
• When using a firewall:
— Restrict communication to the expected ports, as per your network configuration.
Only open those ports that are necessary for network communication.
— Periodically monitor the firewall to ensure the configuration has not been changed,
and that the firewall status does not indicate communication has occurred on
unexpected ports.
• When using network switches:
— Close or disable unused network ports to prevent unauthorized connection of
network nodes or PLCs.
— Periodically monitor the switch to ensure the configuration has not been changed,
and that the switch status does not indicate communication has occurred on
unexpected ports.
• Install operating system patches and anti-virus software updates, as they are released,
on the workstation.
• If you want to remotely access the workstation(s) the Enhanced Diagnostic Monitor is
installed on, you should take care to evaluate and mitigate all security threats to the
necessary level per your organization's security policy, following industry best
practices and applicable standards.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 C
Using Enhanced Diagnostic Monitor with
System Manager

Overview 188
Starting Enhanced Diagnostic Monitor from System Manager 189
Using Enhanced Diagnostic Monitor from System Manager 191

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

188 Appendix C Using Enhanced Diagnostic Monitor with System Manager

Overview
System Manager is a distributed application for monitoring the health and performance of all
components of an I/A Series or Foxboro Evo Control Core Services system; it is also used for
managing network operations.
The integration of the Enhanced Diagnostic Monitor with System Manager enables you to
extract and view fault and alarm information for a Triconex controller from within System
Manager, without having to open another application such as FoxView. For example, when a
safety system has a fault, you can invoke the Enhanced Diagnostic Monitor from System
Manager and view detailed information about the safety system fault.
The Enhanced Diagnostic Monitor can be started from any I/A Series or Foxboro Evo Control
Core Services workstation.
To start the Enhanced Diagnostic Monitor directly from System Manager, it must be installed
on an I/A Series or Foxboro Evo Control Core Services workstation. For more information about
where to install the Enhanced Diagnostic Monitor, and how to configure it for use with System
Manager, see I/A Series System FDSI and SOE Workstation Drivers for Triconex User’s Guide
(B0700DF), available on the Global Customer Support (GCS) website.
Note System and node configuration must be done in the Enhanced Diagnostic Monitor
before it can be launched from System Manager.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Starting Enhanced Diagnostic Monitor from System Manager 189

Starting Enhanced Diagnostic Monitor from System

Manager
Before you begin, make sure that the Field Device System Integrator (FDSI) Triconex Integrator
driver is running in an FBM232 or FBM233, and that the Enhanced Diagnostic Monitor is
attached to an FDSI FBM. For more information, see System Manager (B0750AP), available on the
Global Customer Support (GCS) website.

Procedure
1 In System Manager, do one of the following:
• Click the FDSI device. From the Actions menu, click Equipment Change, and then
click Triconex Enhanced Diagnostic Monitor.

• Or, right-click the FDSI device, and select Triconex Enhanced Diagnostic Monitor.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

190 Appendix C Using Enhanced Diagnostic Monitor with System Manager

2 When prompted, enter your login information.

You will need to enter your Windows user name if Enhanced Security is configured, or
your Enhanced Diagnostic Monitor user name if Standard Security is configured. For
more information, see Starting the Enhanced Diagnostic Monitor on page 9.
The Enhanced Diagnostic Monitor for the configured node opens.

Note You can close the System Manager while continuing to use the Enhanced
Diagnostic Monitor.
3 When you are finished using the Enhanced Diagnostic Monitor, exit the application by
manually closing it.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Using Enhanced Diagnostic Monitor from System Manager 191

Using Enhanced Diagnostic Monitor from System

Manager
After the Enhanced Diagnostic Monitor is connected to the specific node, you can manually start
event collection. For more information about event collection, see Starting and Stopping Event
Collection on page 123.
There are some differences when using the Enhanced Diagnostic Monitor after starting it from
System Manager:
• You can open multiple instances of the Enhanced Diagnostic Monitor for more than one
node at a time; that is, you can open one instance per node. If you try to open the
application for a node that is already open, a new instance will not be opened; instead
that instance window will be brought to the front.
• You must configure the default event log file directory where event log files will be
saved in the Enhanced Diagnostic Monitor before starting it from System Manager. You
cannot configure the event log file directory in an Enhanced Diagnostic Monitor
instance that was started from System Manager. For more information about how to
configure the event log file directory, see Changing the Default Event Log File
Directory on page 127.
• The Enhanced Diagnostic Monitor connects to the Triconex node using the IP address,
node number, and controller type specified in the ECB201’s Device Name (DVNAME)
parameter in System Manager.
You can identify the node number from the IP address of the Triconex device, as
specified in the Device Name field of the System Manager window. For example, if the
IP address in Device Name is 192.168.1.3, the node number is 3. For more information
about IP addresses and node numbers, see Creating or Changing a Network
Configuration on page 36.
• The Network Nodes tree is hidden, and only the System Overview window is
displayed.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

192 Appendix C Using Enhanced Diagnostic Monitor with System Manager

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 D
Command-Line Interface Parameters

Overview 194
Command-Line Syntax 196

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

194 Appendix D 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 software).
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, most normal Enhanced Diagnostic Monitor commands are
available.
• When in read-only mode, only the current system status of the specified controller is
available.
The command-line interface is intended for viewing status and collecting events only, and not
for configuring network connections.

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 18 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.

Differences When Starting the Enhanced Diagnostic Monitor via the

Command-Line
There are some differences when the Enhanced Diagnostic Monitor is started via the command-
line interface in regular mode:
• Each instance of the Enhanced Diagnostic Monitor is invoked for one specific node. If
an instance for a specified node is already open, that instance will be brought to the
front. A duplicate instance will not be opened.
• The Network Nodes tree is hidden, and only the System Overview window is
displayed. Also, closing the System Overview window closes the application.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Overview 195

• Multiple instances of the Enhanced Diagnostic Monitor can be run simultaneously so

that you can collect events from several nodes at once.
• When you start event collection, you will not be prompted to create a new file, or select
an existing file; instead, an event log file for the specific node is automatically created in
the event log file directory specified in the command-line. If no path is specified, the file
is created in the default directory. For more information about the default path, see
Changing the Default Event Collection Settings on page 125.
• The default format of the event log file name is:
<Node#>_<NodeName>_<ControllerType>_<MM-DD-YYYY>_<HOUR>-<MIN>-<SEC>
Examples:
— For Tricon: 030_TRINODE30_TRICON_11-25-2013_20-51-01.tce
— For Trident/Tri-GP: 016_TRINODE16_TRIDENT_11-25-2013_20-50-43.tde
• The following commands are unavailable in the Enhanced Diagnostic Monitor when it
is started via the command-line:
— Add
— Delete
— Edit
— Open
— Edit Users
— New Network Configuration
— Open Network Configuration
— Save Network Configuration
— Save Network Configuration As
— Close Network Configuration
— Clear Faults on All Modules
— View Certificate
— Workspace

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

196 Appendix D Command-Line Interface Parameters

Command-Line Syntax
To open the Enhanced Diagnostic Monitor via the command-line interface, use the following
syntax:
EtcxDiag.exe -mode <value> -nodenumber <value> -controller <value>
-connectiontype <value> -primaryip <value> -primaryport <value>
-primarymgmtport <value> -secondaryip <value> -secondaryport <value>
-secondarymgmtport <value> -eventdir <value> -mpleg <value> -mpnic
<value> -comport <value>

The following is the syntax with the minimum required parameter:

EtcxDiag.exe -nodenumber <value>

The following rules apply:

• There must be a space between the parameter name and the value, and also between
the previous value and the next parameter.
• The default value applies for optional parameters when they are not specified in the
command-line syntax. For any parameters that are not specified, the Enhanced
Diagnostic Monitor reads them from the default configuration, and uses them to
initiate a connection.
• The default value applies for optional parameters when they are not specified in the
command-line syntax. For any parameters that are not specified, the Enhanced
Diagnostic Monitor reads them from the existing configuration, and uses them to
initiate a connection.
• If you have not modified the default configuration file, the recommended minimum
required parameters are:
— -nodenumber
— -controller
— -primaryip
— -connectiontype
The following table provides descriptions of each of the available parameters in the command-
line syntax:

Parameter Description Acceptable Values Mandatory? Default Value

-mode The desired • READONLY No REGULAR

operating mode. • REGULAR
See Overview on
page 194 for more
information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Command-Line Syntax 197

Parameter Description Acceptable Values Mandatory? Default Value

-nodenumber The node number •1 Yes Not
of the controller applicable
through
you want to
connect to. • 254
The range is 1–254
for Tricon nodes
and 1-63 for
Trident or Tri-GP
nodes.

-controller The type of • TRICON Yes, if a For node

controller you • TRIDENT network numbers 1-
want to connect configurati- 254: Tricon
• TRI-GP
to. on does not
already
exist.

-connectiontype The type of • NETWORK Yes, if a For Tricon

connection you • SERIAL network (nodes 1-254):
want to make to configurati- NETWORK
• MAIN_PROCESSOR_1x
the controller. on does not
See Types of already
Network exist.
Configurations on
page 32 for more
information.

-primaryip The primary IP Any valid IP address. Yes, if a For Tricon

address of the network (nodes 1-254):
controller you configurati- 192.168.1.n
want to connect on does not For Trident
to. already (nodes 32-63):
See Primary IP exist. 192.168.255.n
Address on
page 169 for more
information.

-primaryport The Primary •0 No 1502

TriStation UDP
through
port used for the
diagnostic PC’s • 65535
connection to the
controller.
See Primary
TriStation UDP
Port Number on
page 170 for more
information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

198 Appendix D Command-Line Interface Parameters

Parameter Description Acceptable Values Mandatory? Default Value

-primarymgmtport The Primary •0 No 1510
Management UDP
through
port number used
for the Enhanced • 65535
Diagnostic
Monitor’s
connection to the
Tricon
TCM/UCM,
Trident 2.x/3.x, or
Tri-GP 2.x/3.x
communication
status
information.
See Primary
Management UDP
Port Number on
page 170.
Note: This
paramet-
er is not
support-
ed for the
CIM.

-secondaryip The secondary IP Any valid IP address. No 0.0.0.0

address of the
controller you
want to connect
to.
See Secondary IP
Address on
page 173 for more
information.

-secondaryport The Secondary •0 No 1502

TriStation UDP
through
port used for the
diagnostic PC’s • 65535
connection to the
controller.
See Secondary
TriStation UDP
Port Number on
page 174 for more
information.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Command-Line Syntax 199

Parameter Description Acceptable Values Mandatory? Default Value

-secondarymgmtport The Secondary •0 No 1510
Management UDP
through
port number used
for the Enhanced • 65535
Diagnostic
Monitor’s
connection to the
Tricon
TCM/UCM,
Trident 2.x/3.x, or
Tri-GP 2.x/3.x
communication
status
information.
See Secondary
Management UDP
Port Number on
page 174.
Note: This
paramet-
er is not
support-
ed for the
CIM.

-eventdir The event log file Any valid path No Default data
directory where directory (See
event log files will Changing the
be saved. Default Event
Collection
Settings on
page 125.)

-mpleg The channel (leg) •0 No 0

of the Trident •1
Main Processor
•2
module that is
connected to the where 0=Left, 1=Middle, and
diagnostic PC. 2=Right
Applies to a
Trident 1.x Main
Processor
connection only.
-mpnic The index position •0 No 0
of the network through
interface card
•9
installed in the
diagnostic PC.
Applies to a
Trident 1.x Main
Processor
connection only.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

200 Appendix D Command-Line Interface Parameters

Parameter Description Acceptable Values Mandatory? Default Value

-comport The COM port on •0 No 0

the diagnostic PC •1
that is connected
•2
to the controller or
the network. •3
•4

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 E
Tricon Chassis and Slot Reference

Overview 202
Tricon Enhanced Performance Chassis Slot Locations 204
Tricon High-Density Chassis Slot Locations 206
Tricon Low-Density Chassis Slot Locations 210

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

202 Appendix E 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 1131 project.
Change the board address display format to hexadecimal, and then use the conversion
tables to manually translate the board address.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Overview 203

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).
• In the enhanced performance main chassis:
— The COM1 slot equals one logical slot.
— The COM2 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, COM, and COM1 slot equals one physical slot.
• Each I/O logical slot and COM2 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:

Chassis
System Use this diagram...
Type
Tricon 11
Enhanced Main Tricon Enhanced Performance Main Chassis Configuration on page 204
Performance
Tricon 11 Main and
Tricon High-Density Main / RXM Chassis Configuration on page 206
High- RXM
Density
Expansion Tricon High-Density Expansion Chassis Configuration on page 207
Tricon 10 Main and
Tricon High-Density Main / RXM Chassis Configuration on page 206
High- RXM
Density
Expansion Tricon High-Density Expansion Chassis Configuration on page 207
Tricon 10.4
or Later Tricon 9 Low-Density / Tricon 10.4 or Later Enhanced Low-Density
Expansion
Enhanced Expansion Chassis Configuration on page 211
Low-Density
Tricon 9 Main and
Tricon High-Density Main / RXM Chassis Configuration on page 206
High- RXM
Density
Expansion Tricon High-Density Expansion Chassis Configuration on page 207
Tricon 9 Main and
Tricon 9 Low-Density Main / RXM Chassis Configuration on page 210
Low-Density RXM
Tricon 9 Low-Density / Tricon 10.4 or Later Enhanced Low-Density
Expansion
Expansion Chassis Configuration on page 211

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

204 Appendix E Tricon Chassis and Slot Reference

Tricon Enhanced Performance Chassis Slot Locations

The following figure shows the location of each logical and physical slot—by number—in a
enhanced performance Tricon 11 main chassis.
The main chassis is number 1. Expansion chassis are numbered from 2 to 15. A Tricon 11 system
can use any of the following expansion chassis:
• Tricon high-density expansion chassis (see page 207)
• Tricon high-density RXM expansion chasis (see page 206)
• Tricon enhanced low-density expansion chassis (see page 211)
Note The enhanced performance main chassis can be used only with a Tricon 11 system.

Tricon Enhanced Performance Main Chassis Configuration

POWER A MP B C COM1 L COM2 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
ó LOCAL ó FAULT FAULT FAULT

ACTIVE ACTIVE ACTIVE

ALARMS ALARMS ALARMS

MAINT1 MAINT1 MAINT1
115/230 VAC
MAINT2 MAINT2 MAINT2

FIELD FIELD FIELD

TEMP TEMP TEMP

PASS
PROG PROG PROG
FAULT
MODE MODE MODE
ALARM
REMOTE REMOTE REMOTE
TEMP RUN RUN RUN
BATT LOW PROGM PROGM PROGM
B HALT HALT HALT

NODE NODE NODE

ADDRESS ADDRESS ADDRESS
44 55 66 44 55 66 44 55 66
33 33 33
77 8

77 8

77 8
00 1122

00 1122

00 1122
8 99 AA

8 99 AA

8 99 AA
FF

FF

FF

BB CC D E BB CC D E BB CC D E

456 456 456

3 3 3
7

7
012

012

012
89 A

89 A

89 A
F

BCDE BCDE BCDE

IOP IOP IOP

LINK SFP LINK SFP LINK SFP

TX RX TX RX TX RX

POWER MODULE
MODEL 8310

BUSES BUSES BUSES

115/230 VAC TX RX COM TX RX COM TX RX COM

TX RX IO TX RX IO TX RX IO

PASS ECOM ECOM ECOM

FAULT L R L R L R
S2 S2 S2
ALARM S3 S3 S3
TEMP S4 S4 S4

BATT LOW S5 S5 S5
USB USB USB
TX RX TX RX TX RX
C

MP MP MP
POWER MODULE 3009 3009 3009
MODEL 8310

Physical Slot
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Numbers
A Keyswitch with Chassis Number
B, C Redundant Power Modules
1–16 Physical Slots

Tricon Enhanced Performance Main 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 COM1 10 4R 16 7R
5 COM2L 11 5L
6 COM2R 12 5R

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon Enhanced Performance Chassis Slot Locations 205

Hex to Chassis / Slot Conversion Tables—Enhanced Performance Main

Chassis
The following tables provide the hex and decimal equivalents for chassis and slot numbers in
an enhanced performance main 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 COM1 or empty
4 4 4 5 COM2L
5 5 5 6 COM2R
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 an enhanced
performance main chassis:

Hex Board Physical Logical

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

206 Appendix E Tricon Chassis and Slot Reference

Tricon High-Density Chassis Slot Locations

The following figures show the location of each logical and physical slot—by number—in a
high-density Tricon 9, 10, or 11 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 High-Density 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
ó LOCAL ó FAULT FAULT FAULT

ACTIVE ACTIVE ACTIVE

ALARMS ALARMS ALARMS

MAINT1 MAINT1 MAINT1
115/230 VAC
MAINT2 MAINT2 MAINT2

FIELD FIELD FIELD

TEMP TEMP TEMP

PASS
PROG PROG PROG
FAULT
MODE MODE MODE
ALARM
REMOTE REMOTE REMOTE
TEMP RUN RUN RUN
BATT LOW PROGM PROGM PROGM
B HALT HALT HALT

NODE NODE NODE

ADDRESS ADDRESS ADDRESS
44 55 66 44 55 66 44 55 66
33 33 33
77 8

77 8

77 8
00 1122

00 1122

00 1122
8 99 AA

8 99 AA

8 99 AA
FF

FF

FF

BB CC D E BB CC D E BB CC D E

456 456 456

3 3 3
7

7
012

012

012
89 A

89 A

89 A
F

BCDE BCDE BCDE

IOP IOP IOP

LINK SFP LINK SFP LINK SFP

TX RX TX RX TX RX

POWER MODULE
MODEL 8310

BUSES BUSES BUSES

115/230 VAC TX RX COM TX RX COM TX RX COM

TX RX IO TX RX IO TX RX IO

PASS ECOM ECOM ECOM

FAULT L R L R L R
S2 S2 S2
ALARM S3 S3 S3
TEMP S4 S4 S4

BATT LOW S5 S5 S5
USB USB USB
TX RX TX RX TX RX
C

MP MP MP
POWER MODULE 3009 3009 3009
MODEL 8310

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Physical Slot
Numbers
A Keyswitch with Chassis Number
B, C Redundant Power Modules
1–16 Physical Slots

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon High-Density Chassis Slot Locations 207

Tricon High-Density 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

Tricon High-Density 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

1–16 Physical Slots

Tricon High-Density 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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

208 Appendix E Tricon Chassis and Slot Reference

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon High-Density Chassis Slot Locations 209

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

The following tables provide the hex and decimal equivalents for chassis and slot numbers in a
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

Sample Hex to Chassis / Slot Conversions

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

Hex Board Physical Logical

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

210 Appendix E Tricon Chassis and Slot Reference

Tricon Low-Density Chassis Slot Locations

The following figures show the location of each logical and physical slot—by number—in the
Tricon 9 low-density main chassis and the Tricon 9/10.4 or later low-density expansion chassis.
An RXM chassis has the same physical configuration as a main chassis.
Termination modules are installed in the un-numbered slots. Each termination module is
associated with the two modules to the right of the un-numbered slot.
Note For a Tricon 10 system, only an enhanced low-density chassis can be installed, and then
only as an expansion chassis in a 10.4 or later system. Its physical slot locations are the
same as the Tricon 9 low-density expansion chassis.
The main chassis is number 1. Expansion chassis are numbered from 2 to 15.
Tricon 9 Low-Density Main / RXM Chassis Configuration

120 VAC/DC PASS PASS PASS

4AMP FAULT FAULT FAULT
PASS 125V AO AO AO AO
ACTIVE ACTIVE ACTIVE
FAULT
MAINT1 MAINT1 MAINT1
ALARM
MAINT2 MAINT2 MAINT2
TEMP
SLOW
BATT LOW BLOW
POWER MODULE

+
ALARM

COM
C

L
INPUT POWER

N
+ HART MUX HART MUX HART MUX HART MUX

MODEL 8300A PWR PWR PWR PWR

FAULT FAULT FAULT FAULT

HOST HOST HOST HOST

HART HART HART HART

120 VAC/DC
4AMP
PASS 125V
FAULT
ALARM

Physical Slot
TEMP
SLOW
BATT LOW BLOW
1 2 3 5 6 7 8 9 10 11 12
B POWER MODULE
4832-TR 4832-TR 4832-TR 4832-TR Numbers
+ TRICONEX TRICONEX TRICONEX TRICONEX
ALARM

COM 2071H 2071H 2071H 2071H

COM RX COM RX COM RX

COM TX COM TX COM TX

L
I/O RX I/O RX I/O RX
INPUT POWER

IN
IN

IN

IN
B
B

I/O TX I/O TX I/O TX

N
A
A

A
B
B

+
A
A

MODEL 8300A
OUT
OUT

OUT

OUT

HART RS-485 HART RS-485 HART RS-485 HART RS-485

1
REMOTE RUN
EMP EMP EMP HART AO HART AO HART AO HART AO
2870H 2870H 2870H 2870H
PROGRAM 3006 3006 3006
A
STOP
ó LOCAL ó

A Keyswitch with Chassis Number

B, C Redundant Power Modules
1–12 Physical Slots

Tricon 9 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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon Low-Density Chassis Slot Locations 211

Tricon 9 Low-Density / Tricon 10.4 or Later Enhanced Low-Density Expansion Chassis

Configuration

POWER 1 L
1
R 2 L
2
R 3 L 3 R 4 L 4 R 5 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
B, C Redundant Power Modules
3–12 Physical Slots

Tricon 9 Low-Density / Tricon 10.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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

212 Appendix E Tricon Chassis and Slot Reference

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

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

Hex Chassis Hex Physical Logical

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

Sample Hex to Chassis / Slot Conversions

The following are some sample hexadecimal board address conversions for a low-density main
or RXM chassis:

Hex Board Physical Logical

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon Low-Density Chassis Slot Locations 213

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

Low-Density Expansion Chassis
The following tables provide the hex and decimal equivalents for chassis and slot numbers in a
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

Sample Hex to Chassis / Slot Conversions

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

Hex Board Physical Logical

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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

214 Appendix E Tricon Chassis and Slot Reference

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 F
Trident and Tri-GP Baseplate and Slot
Reference

Overview 216
Trident and Tri-GP Baseplate and Physical Slot Locations 217

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

216 Appendix F Trident and Tri-GP Baseplate and Slot Reference

Overview
The Enhanced Diagnostic Monitor displays the board address associated with a Trident or Tri-
GP system event message as a decimal value in the format IOP.baseplate.slot, MP.slot, CM.slot or
CIM.slot, depending on the module the event is associated with.
This appendix provides a visual reference for typical Trident and Tri-GP baseplate and slot
locations.

What Is a Board Address?

A board address identifies the location of a module installed in a Trident or Tri-GP IOP. 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 (CM or CIM), the format is CM.slot or CIM.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 or Tri-GP 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, CM,
and CIM 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 or Tri-GP controller.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Trident and Tri-GP Baseplate and Physical Slot Locations 217

Trident and Tri-GP Baseplate and Physical Slot

Locations
The following figure and corresponding table show the location of each baseplate and physical
slot in a typical Trident or Tri-GP IOP configuration. Baseplates are numbered from 1 to 32.

EM

1
CM or CIM 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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

218 Appendix F Trident and Tri-GP Baseplate and Slot Reference

Label Baseplate Board Address

1 CM or CIM CM.L or CIM.L
2 CM.R or CIM.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

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 G
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,
Trident, and Tri-GP systems.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

220 Appendix G 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.
UTSX 39 Event messages from the Model 3009 Main Processor.
IOCCOM 33 Event messages from IOC/COMM.
CNMIO 34 Common event messages from Model 3720/3721 AI and 3625/3625A DO
modules.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Tricon Event Classes 221

Class Code Description

NGAI 35 Event messages from Model 3720 or 3721 Analog Input modules.
NGDO 36 Event messages from Model 3625/3625A Digital Output modules.
TCM 37 Event messages from Tricon Communication Modules (TCMs).
UCM 6 Event messages from Unified Communication Modules (UCMs).
BPAO 38 Event messages from Bipolar Analog Output (BPAO) modules.

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

222 Appendix G Event Classes

Trident and Tri-GP Event Classes

Class Code Description
CMN 0 Event messages that are common to all modules in the system.
TSX 1 Event messages from the System Executive on the 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 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/3.x or Tri-GP Communication Module (CM).
CIM 15 Event messages from the Trident 3.x or Tri-GP 3.x Communications Integration
Module (CIM).

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Index

A B
A&E status information, OPC 96 bad password error 11
access logs, user banner text, security 12–13
clearing 17 baseplate
exporting 15 addresses 118
options 16 configurations 217
saving 15 locations physical 216
viewing 14
black, event message color 111
Access, viewing events in 138
blue, event message color 111
ACM event retention 114
Board Address Filter property 129, 146
active alarms, OPC UA 104
board addresses
active clients defined
OPC 96 Tricon 202
TSAA 96, 104 Trident 216
active status, Peer-to-Peer 99, 106 Tri-GP 216
actual scan time 85 display format, Tricon
changing 116
Add command 145
exceptions 116, 202
Add/modify users privilege 28 filtering by 129–130
adding P indicator in, Tricon 116, 202
nodes 36 question mark in, Tricon 116, 202
Tricon node 37 Tricon enhanced performance 205
Trident 1.x/2.x node 40 Tricon high-density 208
Trident 3.x node 44 Tricon low-density 210, 212
Tri-GP 2.x node 40 broadcasts received, Modbus Serial 98, 106
Tri-GP 3.x node 44
Browse Certificates property 58, 146
users 22
bypassed devices, OPC UA 104
addresses, board
see board addresses bytes
CM/CIM print buffer 107
addresses, hexadecimal 202–213
TCM/UCM print buffer 99
admin user, Windows 5, 8, 12, 14
alarm data reports 141 C
alarm status, OPC UA 104 Calendar property 84, 147
application scan time 86 capacity, disk 122
attempts, login 9 Certificate ID property 47, 147
authentication, user 11, 19, 186 Certificate Name property 47, 147
Auto Scroll property 125, 145 certificate store, Windows 56
auto-discovery certificates
requirements for 35 choosing 56
troubleshooting 51 configuring 57
default 56

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

224 Index

described 55 on individual modules 72, 74

error troubleshooting 57 clearing user access logs 17
use of 55
client access list
changing CM/CIM 28, 31
board address format, Tricon 116 TCM/UCM 28, 31
default event log file directory 127 troubleshooting 51
default network configuration 36
Close Event File command 148
default password 9, 18
memory allocation 87 Close Network Configuration command 149
network configuration 36, 37, 40, 44 CM
OVD state 77 client access list 28
passwords, user 23, 25 communication status 100, 107
scan time 86 connecting via serial link 34
security level connection, troubleshooting 51
names 30 Modbus TCP ports 105
privileges 27 read-only mode 50
security setting 19 redundancy with 33
chassis and slot event filter 130 unable to connect to 51
unable to view communication status 101
chassis and slot locations, Tricon 202
CM.slot board addresses 118, 216
chassis configurations
Tricon enhanced performance 204 code, event message 112
Tricon high-density 206 Collect System Events privilege 27
Tricon low-density 210 collecting system events 110–138
chassis icons collisions
Tricon 65 CM/CIM 103
Trident/Tri-GP 68 TCM/UCM 95
chassis numbers colors
Tricon enhanced performance 204, 205 event messages 111
Tricon high-density 206, 208, 209 modules, Tricon 66
Tricon low-density 210, 212, 213 modules, Trident/Tri-GP 70
chassis.slot board addresses 116, 202 command-line interface 194–200
CIM Communication Options command 52, 149
adding a controller 46
communication status information
auto-discovery 32, 35, 36
counter values 91
client access list 28
definitions 91
communication status 100, 107
Modbus Serial status
connecting via serial link 34
Tricon 98
connection, troubleshooting 51
Trident/Tri-GP 106
Modbus TCP ports 105
Modbus TCP status
read-only mode 50
Tricon 97
redundancy with 33
Trident/Tri-GP 105
troubleshooting 102
Network status
unable to connect to 51
Tricon 95
unable to view communication status 101
Trident/Tri-GP 103
CIM.slot board addresses 118 OPC status
class, event message 112, 219 CIM 104
Clear All command 148 TCM 96
overview
Clear Faults on All Modules command 148
Tricon 92
Clear Faults privilege 27, 76 Trident/Tri-GP 100
clearing faults Peer-to-Peer status
on all modules 76 Tricon 98

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Index 225

Trident/Tri-GP 106 TCM/UCM printer 99

Performance status TriStation interface 99, 107
Tricon 95 controller
Trident/Tri-GP 103 auto-discovery of 35
Printer status connecting to 49
Tricon 99 status, viewing 82–83
Trident/Tri-GP 107 time zone 126
refresh rate 92 see also nodes
saving to file 108 see also Tri-GP
Tricon, viewing 92 see also Tricon
Trident/Tri-GP, viewing 100 see also Trident
TriStation status
Controller Type property 38, 40, 45, 150
Tricon 99
Trident/Tri-GP 107 converting hexadecimal addresses 202
troubleshooting Copy All Items to Clipboard command 151
Tricon 94 Copy command 150
Trident/Tri-GP 101
Copy Selected Items to Clipboard command 151
TSAA status
Tricon 96 correcting faults 73, 75
Trident/Tri-GP 104 counter values, communication status 91
Communication Status View window CRC errors
changing position of 62 CM/CIM 103
Tricon 92 Modbus Serial 98, 106
Trident/Tri-GP 100 Peer-to-Peer 98, 106
compatibility 3 TCM/UCM 95
TriStation interface 99, 107
configured alarms, OPC UA 104
TSAA 96, 104
configuring
creating
secure communication 57
network configuration 36, 37, 40, 44
Tricon node 37
reports 139–141
Trident 1.x/2.x node 40
user 22
Trident 3.x node 44
Tri-GP 2.x node 40 Crystal Reports 139
Tri-GP 3.x node 44 Current Faults property 71, 151
Connect command 149 current user certificate 56
connection customer support ix
auto-discovery 35 customizing the workspace 60
communication status 92, 100
Cut command 152
error messages 52
Ethernet 32
lost 52, 89 D
Modbus 34 DA groups, OPC 96
read-only 50 date, event message 112
redundant 33
retry limit 52 .dbf file 137
serial 34 default
switch to secondary 52 certificates 56
to controller 49 event collection settings 125
troubleshooting 51, 94, 101 event log file directory 39, 43, 47, 127, 152
Connection Type property 38, 41, 45, 149 events per file 122
IP address
connections ACM/NCM 160
CM/CIM printer 107 Tricon 38, 160
Modbus TCP 97, 105 Trident 41, 46, 160

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

226 Index

Tri-GP 41, 46, 160 enabling

network configuration 36 secure communication 47
network configuration file path 32 enabling secure communication 55
password 9
End Time property 129, 156
security banner text 13
security level names 30 Enhanced Diagnostic Monitor
security level privileges 27 command-line interface 194–200
security setting 19 compatibility 3
user 9–22 installing 5
login password 49
Default Event Log File Directory property 39, 43, 47,
security guidelines for 185
127, 152
starting 9
degraded mode, reporting faults in 68 starting from System Manager 189
Delete command 152 starting via command-line interface 194
deleting users 22 steps for using 2
System Manager, integrating 188–191
Diagnostic Alarms command 141, 153
system requirements 3
Diagnostic Monitor v4.x 4 uninstalling 8
diagnostic PC, time zone 126 upgrading 4
diagnostic reports 141 enhanced low-density Tricon 210, 213
digital certificates enhanced performance Tricon 205
see certificates Enhanced Security
directory, event log file 39, 43, 47, 127, 152 changing to 19
disabled A&E events, OPC 96 defined 18
login 10, 11
disabled alarms, OPC UA 104
login attempts 9
Disconnect command 153
Enhanced Security property 156
disk space
error messages
for event log files 122
connection retry 52
for installation 3
general 89
warnings 89
login 11
Display Board Address in Hex Mode command 117, security banner text, saving 13
153
estimated poll time 86
Display Board Address in High-Density Mode
Ethernet network configuration 32
command 117, 154
event analysis
Display Board Address in Low-Density Mode
generating reports 139
command 117, 154
event classes 219, 222
Display Execution Times command 90, 154
event collection
Display Firmware Versions command 79, 155
filtering 128
DLC protocol, installing 6 options 125
docking windows 61 performance 123
domain authentication, Windows 10, 11, 19 progress bar 123
settings 125–135
speed of 123
E starting 123
Edit command 155 status of 113
Edit Users command 155 stopping 124
EICM event data reports 139
collecting events from 5 event exclusion list 135
connecting via serial link 34 event log files
event collection speed 123 closing 148
event retention 114

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Index 227

.dbf format 137 Exit command 158

default directory for 39, 43, 47, 127, 152 Export Event File command 137, 158
displaying 110
exporting
exporting 137–138
communication status data 108
filtering view 128
event log files 137–138
free disk space for 122
reports 143
generating reports from 139
user access logs 15
managing 121
opening 136, 168 external faults 72–73
size, default 122
status of 113 F
viewing 136 fatal faults 74
see also events
Fault History property 71
event message class 112
Fault History setting 158
event message code 112
fault information, Tricon 68
event retention 114
faults
Event Viewer, Windows 14 clearing
events on all modules 76
collecting 123 on individual modules 72, 74
collection settings 125 privileges for 27
color-coding 111 external 72–73
excluding from list 135 in degraded mode 68
exporting 137–138 internal 74–75
filtering view of 128 types of 72, 74
interpreting 111 field faults 72
loss of 114
maximum per file 122, 126, 163 Field Faults property 71, 158
retention of 114 Field Faults tab 67
severity levels 111, 129 FIELD POWER indicator, Trident/Tri-GP 72
speed of collection 123 file access rules 31
time zone, saved 126
file format, exported event log 137
viewing during collection 123
see also event log files filtering events 128
Events and Diagnostic Alarms command 141, 157 Find command 159
Events command 139, 156 firewalls, using 186
events file firmware versions 79, 155
generating reports from 139 floating windows 61
Events pane format
filtering view in 128 .dbf files 137
information in 112 board addresses 116, 118
opening 119 framing errors
Events Summary pane CM/CIM 103
information in 113 TCM/UCM 95
opening 119 free disk space
ExampleClientCertificate.pfx 56 required for installation 3
ExampleServerCertificate.pfx 56 required for log files 122
Exclude command 157 free memory
exclusion list 135 CM/CIM 103
TCM/UCM 95
Execute Debug Commands command 157
Free Memory property 84, 159
execution times, program 90, 154

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

228 Index

G K
GCS ix Key Stop/Position property 84, 161
generating reports 139 keyswitch, Tricon 84
Get Defaults property 159
Global Client Support ix L
GMT 126 LED Indicators area 161
green LEDs, module 67, 70
event message color 111 Left Module area 162
node color in tree 49 Limited property 54, 162
Guest account, Windows 12, 14 link status
CM/CIM 103
H TCM/UCM 95
hardware monitoring 64 LOAD/FUSE indicator, Tricon 72
hexadecimal board addresses local machine certificate 56
changing format 116 log files, event
defined 202 see event log files
Tricon enhanced performance 205
logging in 9–11
Tricon high-density 208
Tricon low-density 212 logical slots
defined, Tricon 203
hiding window panes 60
enhanced performance chassis, Tricon 204
high-density Tricon 208, 209 high-density chassis, Tricon 206
Tricon low-density 210
I login
icons access logs, viewing 14
chassis 65 attempts, number of 9
IOP 68 Enhanced Security 10, 11
ignoring password 49 error messages 11
first time 9, 11
Include command 160
password 9
incorrect parameter error 11 Standard Security 10
indicators troubleshooting 11
fault 72, 74 user name 23, 25
module 67, 70 Windows Guest user 12
installation 5 lost connection 52, 89
installing DLC protocol 6 low-density Tricon 116, 210, 212, 213
internal faults 74–75
Invensys contact information viii M
IOP and baseplate event filter 130 major faults 74
IOP icons 68 Management UDP Port Number property 162
IOP.baseplate.slot board addresses 118, 216 managing event log files 121
IP address Max Events Per Log File property 122, 126, 163
default, Tricon 38 maximizing windows 62
default, Trident 41, 46 maximum event log file size 122
default, Tri-GP 41, 46
Maximum File Size property 126, 163
defaults 160
primary 169 Maximum Memory property 84, 164
secondary 173 memory allocation 87
IP Address property 160 memory statistics 84

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Index 229

message text, event 112 N

messages names
Modbus Serial 98, 106 security level 30
received user 23, 25
Modbus TCP 97, 105
NCM event retention 114
Peer-to-Peer 98, 106
TriStation interface 99, 107 .NET Framework 3, 5
TSAA 97, 104 network configuration
sent, Peer-to-Peer 98, 106 auto-discovery 35
Messages command 164 creating 36
default 36
Messages pane 61, 79, 88, 90 opening 49, 168
Microsoft Access 138 types 32
minimum scan time 86 using Modbus 34
minor faults 74 Network Nodes tree
Modbus communication 34 showing or hiding 61
Modbus Serial status network status
CM/CIM 106 CM/CIM 103
Tricon TCM/UCM 98 TCM/UCM 95
Modbus TCP status network switches, using 186
CM/CIM 105 New Event File command 166
Tricon TCM/UCM 97 new event log files 166
modes, command-line interface 194 New Network Configuration command 166
Modify Banner Message command 12, 13, 164 NIC Index property 42, 167
module colors 66, 70, 165 Node Name property 38, 41, 45, 167
module indicators 67, 70 Node Number property 38, 41, 45, 167
Module Status command 165 nodes
Module Status dialog box 67, 71 adding to network configuration 36
Module Status window connecting to 49
changing position of 62 connection problems 51
Tricon 66 editing 36
Trident/Tri-GP 69 event collection settings 125
maximum number 36
monitored items, OPC UA 104
read-only connection 50
monitoring
not authorized error 12
communication status
Tricon 92 numbers, chassis
Trident/Tri-GP 100 Tricon enhanced performance 204, 205
controller Tricon high-density 206, 208, 209
hardware 64 Tricon low-density 210, 212, 213
status 83
memory allocation 87 O
OVD 77, 78 OPC status
scan time 85 CIM 104
moving windows 61 TCM 96
MP Connection property 42, 165 Open command 168
MP Leg property 129, 166 Open Event File command 168
MP.slot board addresses 118, 216 Open Network Configuration command 168
opening Events panes 119
options

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

230 Index

event collection 125 printer status

user access logs 16 CM/CIM 107
output voter fault 111 Tricon TCM/UCM 99
OVD 77, 78 printing
reports 140, 142
P private key, certificate 55
parameters, command-line 196 privileges, user 27
parameters, mandatory 196 program execution times 90
passwords progress bar, event collection 123
default 9, 18 Project property 171
forgotten 18 project status 84
login errors 11 protocol, DLC 6
rules for 26
TriStation 1131 project 49 public key
user 23, 25 certificate 55
Windows 10, 11, 19, 23
Peer-to-Peer status R
CM/CIM 106 read-only mode 50, 194
Tricon TCM/UCM 98 receiving messages status
percent idle CM/CIM 103
CM/CIM 103 TCM/UCM 95
TCM/UCM 95 red, event message color 111
performance status redundant communications 33
CM/CIM 103
refresh rate 65, 92, 100
TCM/UCM 95
refreshing report view 140, 142
performance, event collection 123
regular mode, command-line 194
physical baseplate locations, Trident/Tri-GP 216
rejects
physical slot location board addresses
Modbus Serial 98, 106
Tricon 116, 202
Modbus TCP 97, 105
physical slots
reports
enhanced performance chassis, Tricon 204
alarm data, generating 141
high-density chassis, Tricon 206
event data, generating 139
Tricon defined 203
exporting 143
Tricon low-density 210
file names 139, 141
Trident 217
printing 140, 142
Tri-GP 217
refreshing 140, 142
pink, event message color 111 saving 143
point faults 68, 168 searching 140, 142
Point Status tab 71 requested scan time 85
poll time 85, 86 requirements
Poll Time property 84, 169 disk space 3, 122
system 3
port connected status, Modbus TCP 97, 105
resizing windows 62
Port Write Enabled property 31, 50
Restore Primary Connection property 53, 171
power faults 67, 72
restoring
Primary IP Address property 169
lost connection 52
Primary Management UDP Port Number property 170 windows 62
Primary TriStation UDP Port Number property 170 retention, event 114
Print command 171 retry limit, connection 52

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Index 231

Right Module area 172 default privileges 27

rules, passwords 26 names, changing 30
overview 18
S security setting
changing 19
Save As command 172 default 19
Save Network Configuration As command 172 defined 18
Save Network Configuration commands 172 Select All command 175
saving serial connection
communication status data 108 event collection speed 123
reports 143 serial link 34
user access logs 15
Serial Port property 38, 42, 46, 175
Scan Request/Actual property 84, 173
sessions, OPC UA 104
scan surplus 85
Set Event Options command 176
Scan Surplus property 84, 173
severity levels, event 111, 129
scan time 84, 85, 86
Severity property 129, 176
SDO
OVD status 78 Show All property 176
supervision status 78 Show Line Numbers command 177
searching showing window panes 60
in reports 140, 142 size of event log files 122
Secondary IP Address property 173 slot colors
Secondary Management UDP Port Number Tricon 66
property 174 Trident/Tri-GP 70
secondary network connection Slot Colors area 177
configuring, Tricon 38 slot number, Tricon 203
configuring, Trident/Tri-GP 42, 46 slots, chassis 203–210
retry settings for 52
SSL protocol 55
Secondary TriStation UDP Port Number property 174
Standard Security
seconds idle changing to 19
Modbus Serial 98, 106 defined 18
Modbus TCP 97, 105 login 10
TSAA 97, 105 login attempts 9
secure communication Standard Security property 178
certificate for, choosing 56
certificate for, default 56 Start Collecting Events command 178
configuring 57 Start Time property 129, 178
enabling 47 starting
overview 55 Enhanced Diagnostic Monitor 9, 194
use of 55 Enhanced Diagnostic Monitor from System
security banner Manager 189
changing during installation 5 event collection 123, 178
customizing 12 status
default text 13 communication, Tricon 92, 99
error while saving 13 communication, Trident/Tri-GP 100, 107
security guidelines 185–186 controller
security levels viewing 82–83
assigning privileges to 27 event collection 113
assigning to user 23, 25 event log file 113, 121
client access list 28 OPC 96, 104

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

232 Index

OVD 77, 78 Time Zone property 180

project 84 time zone, selecting 126
system, reports 141
time, event message 112, 126
Status Bar command 179
timeout status, Peer-to-Peer 99, 107
Status property 179
timeouts
Stop Collecting Events command 179 Modbus Serial 98, 106
stopping event collection 124, 179 Modbus TCP 97, 105
subscribed DA, OPC 96 Toolbar command 180
subscriptions, OPC UA 104 training viii
supervision status, SDO 78 transmit errors
surplus, scan 85 CM/CIM 103
TCM/UCM 95
Switch to Secondary Connection property 53, 179
Tricon
syntax, command-line 196
adding node 37
SYSTEM ALARM indicator, Trident/Tri-GP 72 communication status 92, 99
system events configuring node 37
collecting 110–138 connection, Ethernet 33
collection settings 125 default IP address 38
color-coding 111 enhanced performance chassis configurations 204
exclusion list 135 event classes 220
exporting 137–138 event collection 110–138
filtering view of 128 event exclusion list 135
interpreting 111 event log files 121, 136–138
loss of 114 high-density chassis configurations 206
maximum per file 122, 126, 163 IP address 38
retention of 114 keyswitch 84
severity levels 111, 129 low-density chassis configurations 210
see also event log files low-density display format 116
System Manager 188–191 module colors 66
Module Status dialog box 67
System Overview tree 65
Module Status window 66
System Overview window 62, 65, 68 monitoring OVD 77
system requirements 3 nodes, maximum 36
system version 83 OPC status 96
secondary network connection 38
status reports 141
T supported versions 3
.tce files 121 system events 110, 111
TCM System Overview window 65
client access list 28, 31 system version 83
communication status 92, 99 see also event log files
connecting via serial link 34 see also TCM
connection, troubleshooting 51 see also UCM
event collection speed 123 Tricon Version property 83, 181
event retention 114
Trident
Modbus TCP ports 97
adding 1.x/2.x node 40
read-only mode 50
adding 3.x node 44
redundancy with 33
auto-discovery of 35
unable to connect to 51
baseplate locations, physical 216
unable to view communication status 94
board addresses 118
.tde files 121 client access list 28, 31
technical support ix communication status 100, 107

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

 Index 233

configuring 1.x/2.x node 40 Module Status window 69

configuring 3.x node 44 monitoring OVD 77, 78
connection, Ethernet 33 monitoring SDO supervision 78
connection, serial 34 nodes, maximum 36
default IP address 41, 46 OPC status 104
event classes 222 SDO module 78
event collection 110–138 secondary network connection 42, 46
event exclusion list 135 status reports 141
event log files 121, 136–138 supported versions 3
event retention 114 SYSTEM ALARM indicator 72
IOP icons 68 system events 110, 111
IP address 41, 46 System Overview window 68
module colors 70 system version 83
Module Status dialog box 71 see also CIM
Module Status window 69 see also CM
monitoring OVD 77, 78 see also event log files
monitoring SDO supervision 78 Tri-GP System Version property 83
nodes, maximum 36
TriStation 1131
OPC status 104
application password 49
SDO module 78
status
secondary network connection 42, 46
CM/CIM 107
status reports 141
TCM/UCM 99
supported versions 3
SYSTEM ALARM indicator 72 TriStation UDP Port Number property 51, 181
system events 110, 111 troubleshooting
System Overview window 68 certificate errors 57
system version 83 CIM, connection to 102
unable to connect to 51 communciation status problems
see also CIM Tricon 94
see also CM Trident/Tri-GP 101
see also event log files connection problems 51
Trident System Version property 83, 181 connection retry limit 52
error messages 89
Tri-GP
login problems 11
adding 2.x node 40
passwords, forgotten 18
adding 3.x node 44
auto-discovery of 35 TSAA status
baseplate locations, physical 216 CM/CIM 104
board addresses 118 TCM/UCM 96
client access list 28, 31
communication status 100, 107 U
configuring 2.x node 40 UCM
configuring 3.x node 44 client access list 28, 31
connection, Ethernet 33 communication status 92, 99
connection, serial 34 connecting via serial link 34
default IP address 41, 46 connection, troubleshooting 51
event classes 222 event collection speed 123
event collection 110–138 event retention 114
event exclusion list 135 Modbus TCP ports 97
event log files 121, 136–138 read-only mode 50
event retention 114 redundancy with 33
IOP icons 68 unable to connect to 51
IP address 41, 46 unable to view communication status 94
module colors 70
UDP ports
Module Status dialog box 71

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

234 Index

Management 162, 170, 174 W

TriStation 170, 174, 181
warning messages 89
uninstallation 8
web site, Invensys viii
unknown user name error 11
window panes 60, 61
Unlimited property 54, 182
window position, selecting 62
update rate window view, Trident/Tri-GP 69
see refresh rate
Windows
updates DA, OPC 96 administrator privileges 5, 8, 12, 14
upgrading 4, 8 domain authentication 10, 11, 19, 26
Use Secure Communication property 41, 45, 182 file access rules 31
user access logs 14–17 Guest account, using 12, 14
passwords, rules for 26
user accounts supported versions 3
Windows 186 user accounts for 186
user name user name 10, 11, 19, 23
Windows 10, 11, 19, 23
windows
users resizing 62
access 31 Windows certificate store 56
authentication of 19
creating 18 Windows Event Viewer 14
default 9, 23, 25 Workspace command 183
deleting 22 workspace, customizing 60
managing 18–31 workstation security 186
modifying 23, 25
names 23, 25 write messages, TSAA 97, 105
passwords 23, 25 writes DA, OPC 96
privileges 27 writes, OPC UA 104
security level, selecting 23, 25
X
V XML configuration file, defined 32
version
controllers, supported 3
Z
firmware 79, 155
project 83 Zoom command 69, 183
system 83 Zoom to Fit command 69, 184
View Certificate Command property 183
viewing
controller status 82–83
event log files 136
events during collection 123
events in Access 138
Events panes 119
firmware versions 79
memory statistics 87
program execution times 90
scan time 85
Tricon communication status information 92
Trident/Tri-GP communication status
information 100
voter faults 67, 74

Enhanced Diagnostic Monitor 2.10.0 User’s Guide

Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
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
Website: http://support.ips.invensys.com