Comunication Guide, Tricon v9÷v10

Tricon Version 910 Systems
Communication Guide
for Tricon v9v10 Systems
Assembly No. 9700088-001
December 2005
Information in this document is subject to change without notice. Companies, names and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Triconex. 2005 Invensys Systems, Inc. All Rights Reserved. Triconex, Tricon, Trident, TriStation 1131, TriStation MSW, and CEMPLE are trademarks of Invensys plc, its subsidiaries and affiliates. All other brands may be trademarks of their respective owners.
Document No. 9720088-004 Printed in the United States of America.
Contents
Preface
xi
Summary of Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii Product and Training Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii We Welcome Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1
Introduction
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 TriStation Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Client/Server Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Peer-to-Peer Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Modbus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Triconex Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Trimble GPS Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Centronics Interface for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Network Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Module Capabilities and Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2
Communication Hardware
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Triconex Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Serial Cables and Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Network Hardware Accessory Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Ethernet Twisted-Pair Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Chassis and Module Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Connecting Ethernet Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Converting from 10Base2 to Faster Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Redundant Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 PC Redundancy for TriStation and SOE Recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Testing for Hardware Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 3
TriStation Communication
17
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Communication Cables and Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Network Connection to TriStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Communication Guide for Tricon v9v10 Systems
iv
Contents
Installing a NIC Card in a TriStation PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Installing DLC or TCP/IP Protocol on a TriStation PC . . . . . . . . . . . . . . . . . . . . . . . . 21 Installing the TriStation 1131 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Using ACM Switches to Set the Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Using NCM Switches to Set the Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Changing the Node Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Directly Connecting an ACM or NCM Network Port to a TriStation PC . . . . . . . . 31 Connecting a TCM Network Port to a TriStation PC Using a Router or Hub . . . . . 32 Connecting a Tricon Network Port Using a Media Converter . . . . . . . . . . . . . . . . . . 33 Configuring the TriStation Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Serial Connection to TriStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Connecting a Tricon Serial Port to a TriStation PC . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Configuring a Tricon Serial Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Changing the TriStation Port Used with EICM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Controlling Access to the TCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 What Are TCM Resources? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 How Is Access Controlled? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 What Are Access Levels? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Configuring the Access List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 4
Client/Server Communication
47
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Configuring Ethernet Ports in TriStation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Configuring an NCM NET 2 (Ethernet) Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Configuring a TCM Ethernet Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Setting the IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 DDE Server for Triconex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Triconex DDE Server System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Installing the Triconex DDE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Configuring the DDE Server Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Configuration Requirements for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Requesting Data with a DDE Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Requesting Network Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Monitoring Responses from the Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 DDE Server Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 OPC Server for Triconex. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Configuring the OPC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Redundant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Adjusting System Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Other OPC Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Chapter 5
Peer-to-Peer Communication
75
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Peer-to-Peer Data Transfer Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Contents
Estimating Memory for Peer-to-Peer Data Transfer Time. . . . . . . . . . . . . . . . . . . . . . 78 Configuring Peer-to-Peer Ports in TriStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Allocating Peer-to-Peer Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Using Send and Receive Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Send and Receive Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Sample Send and Receive Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Restrictions on Data Transmission Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Monitoring Peer-to-Peer Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Status of Communication Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Status of NET 1 Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Examples of Peer-to-Peer Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Example 1: Fast Send to One Triconex Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Example 2: Sending Data Every Second to One Node . . . . . . . . . . . . . . . . . . . . . . . . . 88 Example 3: Controlled Use of SEND/RECEIVE Function Blocks . . . . . . . . . . . . . . . 88 Example 4: Using SEND/RECEIVE Function Blocks for Safety-Critical Data. . . . . 89
Chapter 6
Modbus Communication
91
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Physical Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Physical Media Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Multi-Point Connection Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Hardware Handshake Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Valid Modbus Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring Ports for Modbus in TriStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Setting EICM Switches for Serial Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Configuring EICM Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuring TCM Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Configuring TCM Modbus TCP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Setting Signal Delays for Hardware Handshake (EICM Only) . . . . . . . . . . . . . . . . 105 Programming for Triconex Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Processing of Modbus Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Function Blocks for Communicating with Non-Triconex Slaves . . . . . . . . . . . . . . . 107 Function Blocks for Communicating with Trident Slaves. . . . . . . . . . . . . . . . . . . . . 108 Function Blocks for Communicating with Tricon Slaves . . . . . . . . . . . . . . . . . . . . . 108 Sample Modbus Read Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Sample Modbus Write Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Programming for Triconex Slaves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Assigning Alias Numbers to Tagnames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 How Tricon Transmits REAL Values With Special Alias Numbers . . . . . . . . . . . . 112 Tricon Special Alias Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 How REAL Numbers are Scaled to Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Scaling REAL Values to Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Sample Modbus Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
vi
Contents
Chapter 7
Related Communication Features
119
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Tricon Write Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Tagnames and Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 System Aliases for Tricon Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Master Node in a Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Master Node in a Peer-to-Peer Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Time Adjustments from External Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 GPS Time Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Combination Schemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Setting the Controller Clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Configuring Time Synchronization Properties on the ACM, NCM, or NCMG. . . 127 Using a Tricon TCM to Synchronize Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Printing from a Tricon Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Effect of Printing on Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Devices for Tricon Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Installing Printer Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Connecting a Tricon EICM Port to a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Configuring a Tricon EICM Port for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Connecting a TCM to Printing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Connecting a TCM to Printing Devices Using a Hub . . . . . . . . . . . . . . . . . . . . . . . . 142 Configuring a Tricon TCM Printer Port for Printing . . . . . . . . . . . . . . . . . . . . . . . . . 143 About Function Blocks for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Appendix A TCM Capabilities
145
TCM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Message Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 TCM Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 TCM Communication Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Protocols Supported by TCM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Appendix B NCM and NCMG Capabilities
155
NCM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Message Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Communication Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Protocols Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Appendix C EICM Capabilities
161
EICM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Message Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Contents
vii
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Serial Port Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Parallel Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Port Numbers and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 EICM Communication Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Protocols Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Appendix D TSAA Protocol
169
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Byte Ordering in Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Symbol Table Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 TSAA Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 TRICON_DATA (Type 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 TRICON_DATA_REQ (Type 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 WRITE_TRICON_DATA (Type 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 WRITE_TRICON_DATA_RSP (Type 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 READ_TRICON_CLOCK (Type 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 READ_TRICON_CLOCK_RSP (Type 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 SET_TRICON_CLOCK (Type 7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 SET_TRICON_CLOCK_RSP (Type 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 ADJUST_TRICON_CLOCK (Type 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 ADJUST_TRICON_CLOCK_RSP (Type 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 READ_TRICON_DATA (Type 11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 READ_TRICON_RSP (Type 12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 TRICON_SOE_REQ (Type 13). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 TRICON_SOE_RSP (Type 14) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 TRICON_CPSTATUS_REQ (Type 15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 TRICON_CPSTATUS_RSP (Type 16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 TRICON_SOE_DATAAVAIL (Type 17) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 TRICON_GET_SYMBOL_REQ (Type 22, Trident Only) . . . . . . . . . . . . . . . . . . . . . . 193 TRICON_GET_SYMBOL_RSP (Type 23, Trident Only) . . . . . . . . . . . . . . . . . . . . . . 194 Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Performance Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Appendix E Modbus Protocol
203
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Message Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Determining Message Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Modbus Functions and Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Modbus Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Communication Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
viii
Contents
Function Names and Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Modbus Message Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Sample Query and Response Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Modbus Message Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Modbus Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Read Coil Status Function (Function 01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Read Input Status (Function 02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Read Holding Registers (Function Code 03) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Read Input Registers (Function Code 04) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Force Single Coil (Function Code 05) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Preset Single Register (Function Code 06) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Read Exception Status (Function Code 07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Loop-Back Diagnostic Test (Function 08) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Force Multiple Coils (Function Code 15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Preset Multiple Registers (Function Code 16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Transmission Errors and Exception Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Transmission Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Exception Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Exception Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Exception Response Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Appendix F Tricon System Aliases
227
Overview of Tricon Aliases and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Tricon Modbus Alias Ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 System Variables Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Main Processor Status Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 EICM Status Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Chassis Upper Power Supply Fault Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Chassis Lower Power Supply Fault Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Chassis Requires Maintenance Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Chassis Has Active Board with Fault Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Slot Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Aliases for ACM, NCM, and TCM Network Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Aliases for System-Wide Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Appendix G TCM Model 4351/4352 Configuration
287
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Configuring TCM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Configuring TCM Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Configuring TCM Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Configuring TCM Peer-To-Peer Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Configuring TCM Modbus TCP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Using a Tricon TCM to Synchronize Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Configuring GPS Time Synchronization on the TCM . . . . . . . . . . . . . . . . . . . . . . . . 298
Contents
ix
Configuring SNTP Time Synchronization on the TCM . . . . . . . . . . . . . . . . . . . . . . . 300 Configuring Triconex Time Synchronization on the TCM . . . . . . . . . . . . . . . . . . . . 302 Configuring a Tricon TCM Printer Port for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Glossary Index
305 315
Contents
Preface
This guide describes communication features available with Tricon version 10 and later systems, including how to install and configure communication modules. In this guide, Triconex controllers refers to Tricon and Trident controllers.
Summary of Sections
Chapter 1, Introduction Describes the types of communication available with a Triconex controller and the capabilities of its communication modules. Chapter 2, Communication Hardware Discusses the hardware used to enable Triconex controllers for communication with each other and with external devices. Chapter 3, TriStation Communication Explains how to connect a TriStation PC to a Triconex controller and specify write access to points. Chapter 4, Client/Server Communication Explains how to configure and use client/server communication, including OPC Server and DDE Server client. Chapter 5, Peer-to-Peer Communication Explains how to set up controllers for communication in a Peer-to-Peer network. Chapter 6, Modbus Communication Explains how to set up a controller for communication as a Modbus master, slave, or both. Chapter 7, Related Communication Features Describes the time synchronization and printing features of a Tricon controller. Appendix A, TCM Capabilities Describes TCM operation and physical communication interfaces. Appendix B, NCM and NCMG Capabilities Describes NCM operation and physical communication interfaces. Appendix C, EICM Capabilities Describes EICM operation and physical communication interfaces. Appendix D, TSAA Protocol Provides a programmers reference for TSAA, a Triconex protocol used for client/server applications. Appendix E, Modbus Protocol Provides detailed information about the Modbus protocol that can be used by Triconex network and serial ports. Appendix F, Tricon System Aliases Describes the system aliases available with the Tricon controller. Appendix G, TCM Model 4351/4352 Configuration Explains how to configure the older model 4351 or 4352 Tricon Communication Module. Glossary Provides definitions of terms used in this guide.
xii
Preface
Related Documentation
These Triconex guides contain related information: Planning and Installation Guide for Tricon v9v10 Systems Developers Guides for TriStation 1131 Safety Considerations Guide for Tricon Systems SOE Recorder Users Guide
Product and Training Information

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

To help us improve future versions of Triconex documentation, we want to know about any corrections, clarifications, or further information you would find useful. When you contact us, please include the following information: The title and version of the guide you are referring to A brief description of the content you are referring to (for example, step-by-step instructions that are incorrect, information that requires clarification or more details, missing information that you would find helpful) Your suggestions for correcting or improving the documentation The version of the Triconex hardware or software you are using Your name, company name, job title, phone number, and e-mail address
Send e-mail to us at: triconextechpubs@ips.invensys.com Please keep in mind that this e-mail address is only for documentation feedback. If you have a technical problem or question, please contact the Customer Satisfaction Center. See Technical Support (page xii) for contact information. Or, you can write us at: Attn: Technical Publications Triconex 15345 Barranca Parkway Irvine, CA 92618 Thank you for your feedback.
xiv
Preface
1
Introduction
Overview Module Capabilities and Usage 2 5
Chapter 1
Introduction
Overview
Tricon controllers can communicate with other Triconex controllers and with external devices through these communication modules: Tricon Communication Module (TCM) Advanced Communication Module (ACM) Enhanced Intelligent Communication Module (EICM) Network Communication Module (NCM) Network Communication Module with GPS Interface (NCMG)
For guidelines on using Triconex communication protocols in safety-critical applications, see the Safety Considerations Guide.
The TriStation protocol enables communication between a TriStation PC and a Triconex
controller. A TriStation PC can be connected to a Triconex controller through an Ethernet port on the ACM, NCM, or TCM, or through a serial port on the EICM or TCM. TriStation 1131 Developers Workbench is used to develop and monitor applications which run in a Triconex controller. The TriStation 1131 software is compliant with Part 3 of the IEC 61131 International Standard for Programmable Controllers. For more information about using the TriStation software, see the TriStation 1131 Developers Guide.
PC. OPC Server and DDE Server use TSAA protocol to exchange data with Triconex controllers. TSAA protocol can also be used to write custom programs for accessing Triconex points.
The TSAA protocol allows client/server communication between a Triconex controller and a
Triconex OPC Server

OPC Server is a client/server application, available from Triconex or Matrikon, which allows OPC clients to read and write to Triconex program variables. OPC is a standard set of nonproprietary interfaces used to develop client/server programs. For more information, see OPC Server for Triconex (page 69).
Triconex DDE Server

DDE Server is a client/server application that allows DDE clients to read and write to Triconex program variables. Using DDE Server, any Windows application that supports DDE protocol, such as Microsoft Excel, can access Triconex variables. For more information, see DDE Server for Triconex (page 60).
Overview
The Triconex proprietary Peer-to-Peer protocol allows multiple Triconex controllers in a closed network to exchange safety-critical data. The controllers exchange data by using Send and Receive function blocks in their TriStation applications. The controllers can synchronize their time with the master node (the one with the lowest node number) or with an external device, such as a DCS. For the TCM, Peer-to-Peer communication can use DLC or UDP/IP protocols.
Modbus is an industry-standard master/slave protocol that is traditionally used for energy management, transfer line control, pipeline monitoring, and other industrial processes. A Tricon controller with an EICM or TCM can operate as a Modbus master or slave. A DCS typically acts as the master while the Triconex controller acts as a slave. The master can also be an operator workstation or other device that is programmed to support Modbus devices. The ability to be a master or slave is avaliable on each port. The Tricon controller includes serial ports on the EICM or TCM that enable communication with Modbus devices. The serial ports on the EICM or TCM can be configured for use as Modbus masters or slaves. The NET 1 or NET 2 port on the TCM can be configured for use as a Modbus master or slave for communication over TCP.
Triconex Time Synchronization

The Time Synchronization protocol allows networks of Triconex controllers to be synchronized with each other, and optionally, with external devices. Triconex controllers on a network are typically synchronized with the master node (the controller with the lowest node number). If desired, the master node can accept time adjustments from an external device, such as a Foxboro DCS or an OPC client, so that the external device time prevails for all Triconex controllers on the network. Triconex Time Synchronization can be used with external devices that use TSAA or Modbus protocol. If networked controllers are collecting event data for system maintenance and shutdown analysis, Triconex Time Synchronization must be used to ensure accurate time-stamping of events. For the TCM, Time Synchronization can use the DLC or UDP/IP protocols. For controllers using NCMs for Triconex Time Synchronization, communication is limited to the link layer (DLC) protocol. For controllers using TCM, link layer or UDP/IP communication are available to allow greater networking capability.
Trimble GPS Time Synchronization

A Tricon controller with an NCMG or TCM can receive time adjustments from a Global Positioning System (GPS) by using the Trimble Acutime 2000 Synchronization Kit. The kit must be connected to an RS-232 port on the NCMG or TCM for communication using the Trimble Standard Interface Protocol.
Chapter 1
Introduction
If a controller includes an NCMG or TCM, it can act as a master node in a network of Triconex controllers and can accept GPS time adjustments to synchronize all Triconex controllers on the network with GPS time.
Centronics Interface for Printing

A Tricon controller can send brief ASCII text messages to a printer that is connected to a parallel port on the EICM. These messages are typically used for alarms, status, and maintenance. You must use a printer which is compatible with the Centronics interface on the EICM parallel port.
Network Printing
A Tricon controller can send brief ASCII text messages to a printer by means of a print server connected to an Ethernet port on the TCM. These messages are typically used for alarms, status, and maintenance. The printing devices you can use with a Tricon controller include an HP JetDirect-compatible print server and a networked printer through a router or hub.
Module Capabilities and Usage
Module Capabilities and Usage

This table lists the types of communication that can be done using ports on the Tricon communication modules.
Type of Communication Modbus Master or Slave (RTU or ASCII) Modbus Master or Slave (TCP) Peer-to-Peer (DLC) Communication Peer-to-Peer (UDP/IP) Communication Printing using a Parallel Port Printing using an Ethernet Port Triconex Time Synchronization via DLC Triconex Time Synchronization via UDP/IP SNTP Triconex Time Synchronization Time Synchronization (Trimble GPS) TriStation via a Serial Port TriStation via an Ethernet Port TSAA Client/Server Communication ACM 1 NET 2 NET 2 NET 2 NET 2 EICM 4 serial ports 1 parallel port 1 port NCM, NCMG NET 1 NET 1 1 port (NCMG) NET 2 NET 2 TCM 4 serial ports NET 1, NET 2 NET 1 NET 1, NET 2 NET 1, NET 2 NET 1 NET 1, NET 2 NET 1, NET 2 Port 1 Port 4 NET 1, NET 2 NET 1, NET 2
1. means this communication type is not available with this module.
Chapter 1
Introduction
2
Overview Triconex Products Chassis and Module Selection Connecting Ethernet Devices Redundant Devices Printing 8 8 10 11 13 15
Chapter 2
Overview
This chapter describes Triconex products and other devices that must be purchased to enable a Triconex controller for communication. Typical configurations include redundant modules, cables, and workstations, but can include other devices. Triconex supplies some communication cables, but does not supply PCs, hubs, routers, media converters, or printers. You must purchase these devices from manufacturers such as Black Box Network Services and Hewlett-Packard. If the system requires an Ethernet hub or router, it should operate at 10 or 100 megabits per second, or be auto-negotiable for either speed. Most hubs do not require configuration and do not have IP addresses. If you are using a managed hub, follow the manufacturers instructions for installation and configuration. If you need assistance with selecting communication hardware, please contact your network administrator or Information Technology department.
Triconex Products
This section describes the communication products available from Triconex. Note If you are installing a TCM with fiber connectors (model 4352 or 4352A), you will need to provide your own fiber-optic cable(s). You cannot purchase a fiber-optic cable from Triconex. The fiber cable should be a multimode 62.5/125 um cable which complies with the ANSI/TIA/EIA-568-B.3 standards.
Serial Cables and Adapter

Triconex serial cables are used to connect a serial port on the EICM or TCM to the TriStation PC. The standard length for serial cables is 20 feet (6 meters), but you can order other lengths if necessary. The xx in the part number indicates that you can specify another cable length. For connections to Modbus masters or slaves, use a cable based on the requirements of the Modbus device.
Accessory Serial cable with two 9-pin connectors Serial cable with one 25-pin connector and one 9-pin connector DB-25-pin to DB-9-pin adapter 1. xx indicates the cable can be ordered in various cable lengths. Part Number 1600080-0xx1 4000016-0xx 1420102-001
Triconex Products
Network Hardware Accessory Kit

The Network Hardware Accessory Kit (model 7600-3) can be used for these connections: ACM or NCM Ethernet connection to TriStation PC. NCM Peer-to-Peer connection. Media or protocol converter connected to a faster Ethernet network.
NET 2 ports on communication modules other than the TCM must use 10Base2 coaxial cables, but these cables can be connected to media converters which allow the Tricon to communicate with other Ethernet media. For more information, see Connecting Ethernet Devices (page 11). The accessory kit includes:
Accessory One 3Com network interface card (model 3C503). (Not required with Peer-to-Peer ports. One 10Base2 coaxial cable (Can be ordered separately as 1600010-006.) Two BNC T-connectors Two 50-ohm terminators with straps Model Number 7600-3
Ethernet Twisted-Pair Cable

A twisted-pair cable can be used to connect a TriStation PC with RJ-45 connectors to an Ethernet network. In this configuration, the NET 1 or NET 2 port on the TCM Model 4351 or 4351A (which uses an RJ-45 connector) is connected to the TriStation PC through a router or hub, using a straight-through cable. The NET 2 port on an NCM or ACM (which uses a BNC connector) is connected to the network through a media converter. The twisted-pair cable is a Category 5 shielded cable which complies with the 10BaseT and 100BaseTX standards. The standard length for twisted-pair cables is 20 feet (6 meters), but you can order other lengths if needed.
Accessory Twisted-pair cable Part Number 1600045-020
10
Chapter 2
Chassis and Module Selection

A Tricon controller must have a Main Chassis and can have up to 14 Expansion or RXM Chassis. These rules apply to the selection of communication modules for a Tricon controller: A TriStation PC must be connected to an ACM, NCM, EICM, or TCM, which means that one of these modules must be included in each Tricon configuration. Each Tricon controller includes one logical slot for ACM, EICM, or NCM modules, which can include a module in the left and right position. Each Tricon controller includes two logical slots for the TCM, each of which can include a module in the left and right position, for a total of four modules. The COM slot can be configured for a TCM, NCM, or EICM only. You cannot install an NCM and a TCM in the same Tricon system. You also cannot install an EICM and a TCM in the same system. Aditionally, you cannot install model 4351A/4352A TCMs and 4351/4352 TCMs in the same system, even if they are installed in different chassis. All types of communication modules must be housed in the Main Chassis or in Chassis 2. If communication modules are housed in Chassis 2, this chassis must be connected directly to the Main Chassis using I/O Comm Cables (model 9001) rather than standard I/O Bus Cables. Chassis 2 can be an I/O Expansion Chassis or a Primary RXM Chassis.
For detailed guidelines on chassis configuration and power limitations, see the Tricon Planning and Installation Guide.
Connecting Ethernet Devices
11
Connecting Ethernet Devices

NET 2 Ethernet ports on the ACM and NCM have BNC connectors that require 10Base2 coaxial cables, limiting data transmission speed to 10 megabits per second. For this type of connection, Triconex provides a Network Hardware Accessory Kit which includes a 10Base2 coaxial cable, BNC T-connectors, and 50-ohm terminators for unused connectors. For more information, see Ethernet Twisted-Pair Cable (page 9).
N M M C M PPP M ABC 1
Figure 1
Ethernet Connection Between Tricon with NCM or ACM and TriStation PC
You must use or terminate the BNC connectors on all ACM or NCM NET 2 ports in the Tricon controller. To terminate an unused BNC connector, you can attach a T-connector with 50-ohm terminators on each end to produce a 25-ohm parallel resistance. If necessary, ask your network administrator about other termination methods. Depending on which model you have, NET 1 or NET 2 Ethernet ports on the TCM have RJ-45 or fiber MTRJ Ethernet connectors that can be connected via a hub or router on the Ethernet network to the TriStation PC.
To Ethernet Network Network Adapter Card with RJ-45 or MTRJ Connector
62.5/125 um Multimode Fiber Cable or 10BaseT / 100BaseT Twisted-Pair Cable 62.5/125 um Multimode Fiber Cable or 10BaseT / 100BaseT Twisted-Pair Cable
Tricon Controller
M M M P P P A B C
T C M 1
RJ-45 or MTRJ Connector on NET 1 or NET 2
RJ-45 or MTRJ Connector
Ethernet Router or Hub
TriStation PC
Figure 2
Ethernet Connection Between Tricon with TCM and TriStation PC
12
Chapter 2
Converting from 10Base2 to Faster Media

If an ACM or NCM needs to communicate with a 10BaseT, 100BaseTX, or faster Ethernet device, you can connect it to a media converter which is connected to faster devices or a faster network.
Procedure
1 2 3 4 5 To each end of a 10Base2 cable, attach a BNC T-connector and a terminator. Attach one of the T-connectors to a BNC connector on a communication module NET 2 port. Attach the other T-connector to a BNC connector on the media converter. Attach one end of the twisted-pair cable to an RJ-45 connector on the media converter. Attach the other end of the twisted-pair cable to an RJ-45 connector on a compatible Ethernet device.
MMM P P P A B C
N C M 1
Figure 3
Using a Media Converter for Ethernet Connections
Redundant Devices
13
Redundant Devices
To ensure continuous operation of a Triconex system if a hardware failure occurs, you can create a redundant configuration. Redundant devices can include modules, workstations, cables, hubs, media converters, printers, and power sources. A redundant device operates in parallel with a primary device so that, if the primary device fails, the redundant device is easily or automatically placed into service. A typical configuration includes two NCM or TCM modules with redundant cables connected to one port on each module. The redundant modules protect against internal faults, and the redundant cables protect against cable breakage. To protect against network failures, you can connect a primary workstation to one network and a redundant workstation to another network, as shown in this figure.
N N M M M P P P A B C C C M M 1 2 M M M P P P A B C
N N C C M M 1 2
Figure 4
Sample Redundant Device Configuration
14
Chapter 2
PC Redundancy for TriStation and SOE Recorder

For TriStation and SOE Recorder, you can maintain redundant PCs and place them into service manually if the primary workstations fail. An efficient practice is to install the necessary programs on the PCs in advance. For TriStation, you should install the TriStation 1131 software and store a backup copy of the project on the redundant workstation. For SOE, you should install and configure the SOE Recorder software on the redundant workstation.
Testing for Hardware Failures

A redundancy scheme is effective only if the primary and redundant devices are connected and operational. Routing the redundant cables over different paths through the facility reduces the possibility of cable damage. To test for hardware failures, you must use the TR_PEER_STATUS and TR_PORT_STATUS function blocks in the TriStation application. These Triconex communication products provide another layer of redundancy testing: The Peer-to-Peer and Time Synchronization protocols transmit messages over both the primary and redundant networks at all times, discarding duplicate messages when both networks are operational. The OPC Server and DDE Server programs communicate with the Triconex controller over the primary network and switch to the redundant network if the primary device fails.
If you are using Modbus protocol or a customized TSAA application, you must develop the additional layer of redundancy testing on your own.
Printing
15
Printing
The Tricon controller supports two types of printing, depending on which communication module is installed: The EICM supports Centronics-compatible printing through port 5. The TCM supports printing to network-attached printers through NET 1 or NET 2.
The Tricon TCM also supports JetDirect-compatible print servers connected to Centronicscompatible printers. The print server must be specified for the JetDirect print protocol and speeds of 10 or 100 megabits per second. Triconex has tested and can recommend the following Hewlett-Packard print servers: HP JetDirect Ex Plus HP JetDirect 500X Series, model J3265A
This figure depicts a typical configuration that includes a print server.
HP JetDirect-Compatible Print Server Centronics-Compatible Printer Ethernet Hub

Standard Printer Cable Ethernet Cable Ethernet Cable
Tricon Controller
MMM P P P A B C
T C M 1
RJ-45 or Fiber Connector on NET 1 or NET 2
Other Network Connections
Figure 5
Tricon TCM Connection to Printer via Hub and Print Server
For more information, see Printing from a Tricon Controller (page 137).
16
Chapter 2
3
Overview Communication Cables and Accessories Network Connection to TriStation Serial Connection to TriStation Controlling Access to the TCM 18 19 20 37 41
18
Chapter 3
Overview
This chapter describes the tasks required to connect a TriStation PC to a Tricon controller. TriStation 1131 must be used to program and operate the controller, and to establish the controller address on an Ethernet network. TriStation can also be used to monitor applications that are running on Tricon controllers. The TCM supports three concurrent TriStation connections.
Connection Tasks
1 Set up a PC with the required hardware and communication protocols. This includes installing a network adapter card and TCP/IP protocol if you plan to connect the TriStation PC to an Ethernet port on an ACM, NCM, or TCM module. Install the TriStation software on a PC using the setup program provided by Triconex. Physically connect the TriStation PC via the following means: To a serial port on the EICM or TCM. To the NET 2 Ethernet port on the ACM or NCM. To the NET 1 or NET 2 Ethernet port on the TCM.
2 3
If using Ethernet, you can connect the PC via a router or hub to an Ethernet port, or to a media converter that is connected to the Ethernet port. A router or hub is not required if you do not need to connect any additional devices besides the TCM and the PC. To connect the TriStation PC to the Tricon controller with a TCM Model 4351 or 4351A via Ethernet, you must install a network adapter card with an RJ-45 connector in the PC and use a twisted-pair cable. You also need to use a router or hub between the Tricon and the PC. To connect the TriStation PC to the Tricon controller with a TCM Model 4352 or 4352A via Ethernet, you must install a network adapter card with an MTRJ fiber connector in the PC and use a multimode fiber cable. You also need to use a router or hub between the Tricon and the PC. To directly connect the TriStation PC to the Tricon controller with an ACM or NCM, you must install a network adapter card with a BNC connector in the PC and use a 10Base2 coaxial cable. If the network adapter card does not have a BNC connector, you must use an appropriate cable and a media converter. You can buy communication cables from Triconex or from other manufacturers. You must buy media converters from other manufacturers. 4 Note 5 Set the node number of the controller using the rotary switches on the ACM or NCM. The physical node number must match the node number that you set in the TriStation project. The TCM uses the node number set on the MP Front Panel. You need to physically set the switches to the desired node number on the TCM. After the physical connection tasks are completed, you must logically configure the connection in the TriStation project. This includes specifying which port the communication cable is connected to and the address of the Tricon controller.
After completing the physical and logical connection tasks, you can download, run, and monitor the TriStation application.
Communication Cables and Accessories
19
Communication Cables and Accessories

The TriStation PC can be connected to an ACM, NCM, or TCM Ethernet port, or to an EICM or TCM serial port. These communication cables and accessories are available from Triconex. For more information, see Triconex Products on page 8.
WARNING
Accessory Serial Cable
In hazardous indoor locations, apparatus used with Triconex communication modules must be FM certified for Class I, Division II.
Part/Model 4000015-0xx 4000016-0xx 1420102-001 7600-3 Description Used for an EICM connection to a TriStation PC. Used for a TCM connection to a TriStation PC. Needed for an EICM connection if the PC has a DB-9-pin connector. Used for an ACM or NCM Ethernet connection to a TriStation PC. Includes NIC card, 10Base2 cable, BNC T-connectors, and terminators. Used with an ACM, NCM, or Ethernet connection to TriStation PC on networks that are faster than 10Base2. This cable is always used for TCM model 4351 or 4351A.
25-pin to 9-pin adapter Network Hardware Accessory Kit (10Base2) Twisted-Pair Cable (10BaseT or 100BaseTX)
1600045-020
Note
If you are installing a TCM with fiber connectors (model 4352 or 4352A), you will need to provide your own fiber-optic cable(s). You cannot purchase a fiber-optic cable from Triconex. The fiber cable should be a multimode 62.5/125 um cable which complies with the ANSI/TIA/EIA-568-B.3 standards.
20
Chapter 3
Network Connection to TriStation

This section explains how to make a network connection between a ACM, NCM, or TCM communication module and a TriStation PC. This can be a direct connection from the communication module to the PC, or a connection through a router, hub, or media converter. A router or hub is not required if you do not need to connect any additional devices besides the TCM and the PC. You cannot use both an NCM and TCM module in a Tricon controller. To set up the connection, you must install a network interface card and TCP/IP protocol on the PC, set the node number of the controller, connect the PC to a network port on the communication module, and configure the connection in the TriStation 1131 project. This section includes procedures for each of these tasks.
CAUTION
Topics include: Note
The node setting (on the ACM or NCM module or the 3008 MP Front Panel) must match the node number specified in the TriStation project. See the Tricon Planning and Installation Guide for instructions on changing the MP node setting.
Installing a NIC Card in a TriStation PC on page 21 Installing DLC or TCP/IP Protocol on a TriStation PC on page 21 Installing the TriStation 1131 Software on page 24 Using ACM Switches to Set the Node Number on page 26 Using NCM Switches to Set the Node Number on page 28 Changing the Node Number on page 30 Directly Connecting an ACM or NCM Network Port to a TriStation PC on page 31 Connecting a TCM Network Port to a TriStation PC Using a Router or Hub on page 32 Connecting a Tricon Network Port Using a Media Converter on page 33 Configuring the TriStation Network Connection on page 35 If you are connecting the TCM or EICM to the TriStation PC via serial port, see Serial Connection to TriStation on page 37.
21
Installing a NIC Card in a TriStation PC

This procedure explains how to install a network interface card (NIC) in a TriStation 1131 PC to be connected to a Tricon ACM, NCM, or TCM.
Procedure
1 2 Install the network interface card by following the manufacturers instructions. Do not change the factory default settings on the NIC card. To connect a TCM to the TriStation PC, do one of the following: If the network interface card has an RJ-45 connector, you can connect it to the NET 1 or NET 2 port on the TCM (model 4351 or 4351A) via a router or hub using a patch cable. If the network interface card has a MTRJ (fiber) connector, you can connect it to the NET 1 or NET 2 port on the TCM (model 4352 or 4352A) via a router or hub using a patch cable. If the network interface card does not have the appropriate connector for your TCM model, connect the network interface card to a media converter that is connected to the NET 1 or NET 2 port.
Note 3
See Appendix A, TCM Capabilities for more information about the differences between the TCM model 4351 or 4351A (copper) and model 4352 or 4352A (fiber). To connect an ACM or NCM to the TriStation PC, do one of the following: If the network interface card has a BNC connector, you can connect it directly to the NET 2 port. If the network interface card does not have a BNC connector, connect the network interface card to a media converter that is connected to the NET 2 port.
Run the diagnostics provided with the network interface card according to the manufacturers instructions.
Installing DLC or TCP/IP Protocol on a TriStation PC

These procedures explain how to install DLC or TCP/IP protocol on a TriStation PC. These procedures are applicable only when connecting to a Trident system. The DLC protocol is required for using TriStation on a Windows XP workstation. The TCP/IP protocol is required for Tricon ACM, NCM, and TCM connection.
Installing TCP/IP or DLC on Windows 2000

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

1 2 3 On the Start menu, click Control Panel, and then double-click Network Connections. Right-click the network connection where you want to install the protocol, then click Properties. Do one of the following: On the General tab, if the TCP/IP protocol is checked on the list of installed components, it means the protocol is installed and you are finished with this procedure. If the TCP/IP protocol is not checked, go to the next step to continue the installation.
4 5 6
On the General tab, click Install. In the Select Network Component Type dialog box, click Protocol, and then click Add. Click the TCP/IP protocol, and then click OK.
Installing DLC on Windows XP

Installing the DLC protocol on a Windows XP workstation is a 3-step process. Note If you have already installed the DLC protocol on your workstation, you can configure it to start automatically each time you start your workstation by changing a registry value. Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Dlc, and then change the Start value to 1.
Step 1: Downloading the DLC Protocol Installation Program 1 2 3 4 Open your Internet browser, and enter the following URL in the address field: http://www.microsoft.com/downloads/ In the Search for a Download section, perform a search for DLC Protocol and then go to the download page for the DLC protocol for Windows XP. Follow the instructions on the download page to start the download process. When prompted, save the dlc.exe file to your local drive.
23
When the download is complete, double-click the self-extracting dlc.exe file to unzip the five DLC protocol files. Save the files to a location on your local drive that will be easy to remember (for example, C:\DLC).
Step 2: Modifying the .INF File 1 2 Go to the location where you saved the DLC protocol files in step 4 of the previous section. 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. Scroll down until you see the following section:
4 5
Change the value for StartType from 3 to 1. This ensures that the DLC protocol will start automatically each time you start your workstation. Save the file and then exit Notepad.
Step 3: Configuring the DLC Protocol Network Connection

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

The NCM, ACM, or TCM network connection must be configured in your TriStation project. This section explains how to install the TriStation 1131 software, and how to verify that the software is correctly installed. Please see the TriStation 1131 Developers Guide for more detailed installation instructions, including upgrade requirements and uninstallation instructions. Topics include: Note System Requirements on page 24 Installing the TriStation 1131 Software on page 24 Verifying the TriStation 1131 Installation on page 25 The following procedures assume use of TriStation 1131 v4.1 or higher. If you are using another version of TriStation 1131, please refer to the documentation for the version you are using for detailed installation instructions.
System Requirements
The following are the minimum system requirements for TriStation 1131, v4.1 or higher: PC running Windows 2000 or XP Pentium 233 MHz with 128 MB RAM 125 MB free hard drive space CD-ROM drive Network adapter card SVGA monitor running at 1024 x 768 resolution with 64,000 colors DLC protocol installed (see Installing DLC or TCP/IP Protocol on a TriStation PC on page 21)
Installing the TriStation 1131 Software

This procedure explains how to install the TriStation 1131 software. The setup program provided by Triconex installs all the components of the TriStation 1131 Developers Workbench on your PC. If you purchased the optional CEMPLE software, it is installed at the same time. Note If you are installing the TriStation 1131 software on a Windows XP workstation, you must also install the DLC protocol. Without this protocol installed, you will be unable to open a new or existing project in TriStation. See Installing DLC or TCP/IP Protocol on a TriStation PC on page 21 for detailed instructions.
The TriStation 1131 software must be installed on a local drive. Do NOT install and run TriStation 1131 on a network server.
25
Procedure
1 2 3 4 5 6 7 8 Log on as an administrator or as a user with administrator privileges. Close all open applications. Insert the TriStation 1131 CD in the CD-ROM drive. If the installation starts automatically, go to step 8. Otherwise, go to the next step. From the Start menu, click Settings, and then click Control Panel. Double-click Add New Programs. Click the CD or Floppy button, and then browse to locate the setup.exe file on the CD. Double-click setup.exe to start the installation. Follow the InstallShield Wizard instructions. Triconex recommends installing the TriStation 1131 software in the default destination folder, which is: C:\Program Files\Triconex\TriStation 1131 4.1. 9 10 To restart your PC after the installation has finished, click Yes. You are not required to restart your PC before running the TriStation 1131 software. To complete the installation, click Finish.
Verifying the TriStation 1131 Installation

This procedure explains how to verify the TriStation 1131 software is correctly installed and that associated files are not corrupted. After installing the software and before downloading an application to the controller, you should run the TriStation 1131 Install Check program. The Install Check software is copied to your hard drive when you install the TriStation 1131 software. Note Running TS1131 Install Check is required for safety applications. For more information, see the Safety Considerations Guide.
Procedure
1 From the Start menu, select Programs, Triconex, and then Install Check 4.1. Click Run. Click Display Details and verify that the program is validated by viewing each item in the list, as shown in the example at right.
2 3
26
Chapter 3
Using ACM Switches to Set the Node Number

This procedure explains how to set the node number of a Tricon controller by using rotary switches on an ACM. The node number uniquely identifies a controller on a network and is typically determined during network planning. The node number must be physically set on the ACM module during installation and must match the node setting on the MP front panel and the configuration setting in the TriStation project. The default (factory-configured) setting is for node number 1, which is the top switch set to 0 (zero) and the bottom switch set to 1.
CAUTION
Procedure
1
The node setting for the MP, ACM, and TriStation configuration must match.
If needed, remove the module from the chassis. This figure shows the default node setting, which is 1.
Figure 6
Setting the Node Number on the ACM Front Panel
Set the switches to identify the node number, which can be 1 to 31. If a Tricon controller includes two ACMs, you must set the switches on both modules to the same node number.
27
This table identifies the switch settings for nodes 1 to 31.

Node Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Top Switch 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Bottom Switch 1 2 3 4 5 6 7 8 9 A B C D E F 0 Node Number 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Top Switch 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Bottom Switch 1 2 3 4 5 6 7 8 9 A B C D E F
Set the top switch and the bottom switch on the front panel of the ACM to the hexadecimal values you selected.
28
Chapter 3
Using NCM Switches to Set the Node Number

This procedure explains how to set the node number of a Tricon controller by using rotary switches on an NCM. The node number uniquely identifies a controller on a network and is typically determined during network planning. The node number must be physically set on the NCM during installation and must match the node setting on the MP front panel and the configuration setting in the TriStation project. The default (factory-configured) setting is for node number 1, which is switch 1 set to 1 and switch 2 set to zero. Note Older NCMs have eight rotary switches, using hexadecimal notation. Newer NCMs have only two switches, using the numbers 0 15. The node setting for the MP, NCM, and TriStation configuration must match.
CAUTION
Procedure
1
If needed, remove the module from the chassis. This figure shows the default (factoryconfigured) node setting, which is 1.
C A 8 6
C A 8 6
C A 8 6
C A 8 6
C A 8 6
C A 8 6
C A 8 6
Figure 7
Setting the Node Number on the NCM Top Panel (Older Version)
Set the switches to identify the node number, which can be 1 to 31. If a Tricon controller includes two NCMs, you must set the switches on both modules to the same node number.
29
This table identifies the switch settings for nodes 1 to 31.

Node Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Switch 1 1 2 3 4 5 6 7 8 9 A/101 B /111 C/121 D/131 E/141 F/151 0 Switch 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Node Number 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Switch 1 1 2 3 4 5 6 7 8 9 A/101 B /111 C /121 D /131 E /141 F /151 Switch 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1. If you have an older NCM (with eight switches), use the hexadecimal value (A, B, C, etc). If you have a newer NCM (with two switches), use the numerical value (10, 11, 12, etc).
3 4
Set switches 1 and 2 on the top of the NCM to the values you selected. If you have an older NCM, verify that switches 3 through 8 are set to zero because they are unused.
30
Chapter 3
Changing the Node Number

These procedures explain how to change the node number of an ACM, NCM, or TCM after the TriStation application has been downloaded. Typically a node number is changed only during unplanned expansion or reconfiguration of an existing Ethernet network. Changing the node number requires a shutdown of the controlled process and another Download All.
CAUTION
Procedure
1 2 3 4 5 6 7 8 9
The node setting for the MP, ACM or NCM, and TriStation configuration must match.
Prepare for a complete shutdown. Remove all three MPs and all ACMs, NCMs, or TCMs from their respective slots. Change the node number switches on the MP modules. Wait for approximately 60 seconds, and then re-install the MPs. Change the node number switches on the ACMs, NCMs, or TCMs. Re-install the ACMs, NCMs, or TCMs. In TriStation, go to the TriStation Communication screen. Specify the node name, node number, and IP address. Wait for the Pass indicators on the MPs and on the ACMs, NCMs, or TCMs to illuminate. In TriStation, on the Commands menu, click Download All.
31
Directly Connecting an ACM or NCM Network Port to a TriStation PC

This procedure explains how to directly connect an ACM or NCM to a TriStation PC if the network interface card in the PC has a BNC connector. The connection requires a 10Base2 coaxial cable. Triconex provides an accessory kit that includes a 10Base2 coaxial cable, BNC T-connectors, and 50-ohm terminators for unused connectors (see page 9).
Procedure
1 2 3 To each end of a 10Base2 cable, attach a BNC T-connector and a terminator. Attach one of the T-connectors to a BNC connector on NET 2 of the communication module. An NCM is used as an example in the following figure. Attach the other T-connector to the BNC connector on the network interface card in the TriStation PC.
Figure 8
Directly Connecting an ACM or NCM to a TriStation PC
4 5
Terminate the BNC connectors on all communication modules that are installed in the Tricon controller. To terminate an unused BNC connector, you can attach a T-connector with 50-ohm terminators on each end to produce a 25-ohm parallel resistance. Ask your network administrator for information about other termination methods.
32
Chapter 3
Connecting a TCM Network Port to a TriStation PC Using a Router or Hub

This procedure explains how to connect a TCM to a TriStation PC if the network interface card in the PC has an RJ-45 connector or a MTRJ fiber connector. You must use an Ethernet router or hub between the Tricon and the TriStation PC. The RJ-45 connection requires twisted-pair straight-through cables. The fiber connection requires 62.5/125 um multimode fiber cables. See Triconex Products on page 8 for more information about the required cables and how they may be purchased from Triconex.
Procedure
1 2 3 4 Attach one end of the first cable to the NET 1 or NET 2 port on the TCM. Attach the other end of the first cable to the connector on the Ethernet router or hub. Attach one end of the second cable to the connector on the network interface card in the TriStation PC. Attach the other end of the second cable to the connector on the router or hub.
To Ethernet Network Network Adapter Card with RJ-45 or MTRJ Connector
62.5/125 um Multimode Fiber Cable or 10BaseT / 100BaseT Twisted-Pair Cable 62.5/125 um Multimode Fiber Cable or 10BaseT / 100BaseT Twisted-Pair Cable
Tricon Controller
M M M P P P A B C
T C M 1
RJ-45 or MTRJ Connector on NET 1 or NET 2
Ethernet Router or Hub
TriStation PC
Figure 9
Connecting a TCM (Copper or Fiber) to a TriStation PC Using a Router or Hub
Notes If the correct cable is connected to the TCM and the TCM is installed in a powered Tricon chassis, the green LED indicator turns on. If the LED indicator is not on, there is a problem with the physical cable connection. If the network ports on model 4352 or 4352A TCMs do not resume after a power restart, you may have an interface problem with the router or hub. Triconex recommends that you momentarily disconnect both ends of the fiber cable from the TCM and the router or hub, and then reconnect to allow the fiber network to resume proper communication.
33
Connecting a Tricon Network Port Using a Media Converter

This procedure explains how to connect an ACM, NCM, or TCM to a TriStation PC if the network interface card in the PC requires a media converter because it does not have the appropriate connector. The connection to an ACM or NCM requires a 10Base2 cable, a media converter, and another appropriate cable, such as a twisted-pair cable. The connection to a TCM (model 4352 or 4352A - fiber) requires a 62.5/125 um multimode fiber cable, a media converter, and another appropriate cable, such as a twisted-pair cable.
Procedure for Connecting an ACM or NCM

1 2 3 To each end of a 10Base2 cable, attach a BNC T-connector and a terminator. Attach one of the T-connectors to a BNC connector on the NET 2 port. Attach the other T-connector to a BNC connector on the media converter. For the TriStation PC, you can use a 10BaseT or 100BaseTX twisted-pair cable for faster communication. 4 5 Attach one end of the twisted-pair cable to an RJ-45 connector on the network interface card in the TriStation 1131 PC. Attach the other end of the twisted-pair cable to an RJ-45 connector on the media converter.
Figure 10
Connecting an ACM or NCM to the TriStation PC Using a Media Converter
34
Chapter 3
Procedure for Connecting a TCM (Model 4352 or 4352A- Fiber)

1 2 3 4 Attach one end of the fiber cable to the NET 1 or NET 2 port on the TCM. Connect one end of the twisted-pair cable to the RJ-45 connector on the network interface card in the TriStation PC. Attach the other end of the twisted-pair cable to an RJ-45 connector on the media converter. Attach the other end of the fiber cable to a MTRJ fiber connector on the media converter.
To Ethernet Network
Tricon Controller
Network Adapter Card with RJ-45 Connector
M M M P P P A B C
MTRJ Connector on NET 1 or NET 2

T C M
62.5/125 um Multimode Fiber Cable
10BaseT or 100BaseT Twisted-Pair Cable
MTRJ Connector Media or Protocol Converter
RJ-45 Connector
TriStation PC
Figure 11 Converter
Connecting a TCM (Model 4352 or 4352A - Fiber) to the TriStation PC Using a Media
Notes If the correct cable is connected to the TCM and the TCM is installed in a powered Tricon chassis, the green LED indicator turns on. If the LED indicator is not on, there is a problem with the physical cable connection. If the network ports on model 4352 or 4352A TCMs do not resume after a power restart, you may have an interface problem with the media converter. Triconex recommends that you momentarily disconnect both ends of the fiber cable from the TCM and the media converter, and then reconnect to allow the fiber network to resume proper communication.
35
Configuring the TriStation Network Connection

This procedure explains how to configure an ACM, NCM, or TCM network connection to a TriStation PC.
Before You Begin

Before beginning this procedure, you must determine which IP address to use for the communication module. Typically, you can get an IP address from your network administrator or Information Technology department.
Procedure
1 2 In TriStation 1131, expand the Controller tree, and double-click Configuration. On the Configuration tree, click TriStation Communication.
3 Note
Specify these properties on the TriStation Communication screen. The data displayed on the screen is used by TriStation only to connect to a Tricon communication port. The data that you enter will not be downloaded to the Tricon controller.
Property Network Connection Node Number Action Select the Network Connection check box. For the ACM and NCM, enter the number represented on the rotary switches. For TCM, enter the number represented by the Network Node Address setting on the MP front panel.
36
Chapter 3
Property Node Name IP Address
Action Enter a name containing eight or fewer characters to identify the Tricon controller. Enter the physical address of the controller on the network.
4 5 6
On the Configuration tree, click the chassis that contains the ACM, NCM, or TCM. Double-click the module to open the Properties dialog box, and then click Setup. Specify these properties on the ACM, NCM, or TCM Network Setup screen.
Property Installed (NCM and TCM) Used (ACM) IP Address If using a default IP address, leave blank. If not, enter the IP address that identifies the controller on the network. This must be the same IP address entered on the TriStation Communication screen. IP Subnet Mask If using a default IP Subnet Mask, leave blank. For ACM or TCM, get the subnet mask from your network administrator. For NCM, do not change the default setting (eight zeroes). Action Select this property for all installed modules.
Click OK.
Serial Connection to TriStation
37

This section explains how to make a direct (point-to-point) serial connection between a Tricon EICM or TCM and a TriStation PC. You cannot use both an EICM and TCM module in the same Tricon system. By default, both the EICM and the TCM use port 4 for the TriStation connection. Triconex strongly recommends you use the default setting. If port 4 on the EICM fails, port 1, 2, or 3 can be used by changing settings on the module switch block. If port 4 on the TCM fails, you can connect to TriStation using the NET 1 or NET 2 port; see Configuring the TriStation Network Connection on page 35. Topics include: Connecting a Tricon Serial Port to a TriStation PC on page 37 Configuring a Tricon Serial Connection on page 38 Changing the TriStation Port Used with EICM on page 39
Connecting a Tricon Serial Port to a TriStation PC

This procedure explains how to connect an EICM or TCM serial port to a TriStation PC. Triconex provides a serial cable that has a 9-pin connector on each end. If the COM port on the PC has a 25-pin connector, you can use a Triconex 25-pin to 9-pin adapter. If you need other parts, you can purchase them from another manufacturer.
Procedure
1 2 Connect one end of the serial cable to a serial port on the EICM or TCM. This is typically port 4. Connect the other end of the serial cable to a COM port on the TriStation PC. The COM port is typically numbered COM1, COM2, COM3, or COM4.
Figure 12
Connecting a Tricon Serial Port to the TriStation PC
38
Chapter 3
Configuring a Tricon Serial Connection

This procedure explains how to configure an EICM or TCM serial port that is connected to a TriStation PC.
Procedure
1 In TriStation, expand the Controller tree, double-click Configuration, and then click TriStation Communication.
2 Note
Specify these properties on the TriStation Communication screen. The data displayed on the screen is used by TriStation only to connect to a Tricon communication port. The data that you enter will not be downloaded to the Tricon controller.
Property Serial Connection Node Name Action Select this check box. Enter the name of the Tricon controller. You can use a default name, or enter your own user-defined name. The default names are TRINODE01 through TRINODE31. Select the COM port on the TriStation PC to which the serial cable is connected. Specify the data transmission speed. Settings include 115200, 57600, 38400, 19200, 9600, 4800, 2400, or 1200. The default is 9600.
Serial Port Baud Rate
39
3 4
On the Configuration tree, expand Hardware Allocation, double-click EICM or TCM, and then click Setup. Specify these properties in the EICM or Enhanced TCM Setup dialog box.
Property Port Action Select the port that the TriStation PC is attached to. The default TriStation connection is port 4. For TCM, you must select port 4, as this is the only serial port supported for TriStation connection. Protocol Select TriStation. In the TCM Setup dialog box, this selection is on the Serial Ports tab.
Click OK.
Changing the TriStation Port Used with EICM

This procedure explains how to change the port used for the EICM to TriStation serial connection, which should only be done if there is a hardware failure on port 4. If port 4 fails, you can use port 1, 2, or 3 by setting switches on the EICM. By default, all the switches are set to Off. This means that the default setup is for a TriStation connection to port 4 using a RS-232 interface. In addition to changing the TriStation port, you can set the interface for the port. The default setting for ports 1 through 4 is for RS-232. To use RS-422 (point-to-point) or RS-485 (multi-point), the switch must be turned On.
Procedure
1 2 Remove the EICM from its slot in the Tricon chassis. Figure 13 shows the default settings for port 4. Use Figure 14 to set the switches for the TriStation port. Switches 7 and 8 determine the port used for the TriStation connection. Switches 1, 2, 3, and 4 specify the RS interface for the port. If the switch is Off, the port uses RS-232; if On, the port uses RS-422 (point-to-point) or RS-485 (multi-point). 3 Replace the EICM in its slot. You can now connect the serial cable from the EICM port to the TriStation PC.
40
Chapter 3
Switches 7 and 8 are set to Off, specifying Port 4 for TriStation. O N

1 2 3 4 5 6 7 8
Port 1
Port 2
Port 3
Port 4
Port 5
Figure 13
EICM Switch Block Set to Use Port 4 for TriStation Serial Connection
Figure 14
Using Switches to Change the Port Selection for EICM Serial Connection to TriStation
Controlling Access to the TCM
41

The model 4351A and 4352A Tricon Communication Modules (TCMs) give you the ability to control who can access TCM resources through the modules network ports, and the level of access each user has.
What Are TCM Resources?

A resource is any service or information provided by the TCM through the supported communications protocols. Examples of these resources include: Access to the controller via TriStation (ability to perform a Download Change or Download All) Access to Tricon diagnostic information via Diagnostic Monitor Access to information provided in applications such as SOE Recorder or DDE Server that use the TSAA protocol Access to applications that use the TSAA protocol
How Is Access Controlled?

Access is controlled via client IP addresses. You can control access for a single IP address (one client), or for a group of IP addresses (a group of clients). If you want to group clients into a single access list entry, they must be physically separated in a sub-network, and a subnet mask must be used to group them in the access list. A subnet mask of 255.255.255.255 restricts an access list entry so that it applies only to the specific IP address identified in the entry. A subnet mask of 255.255.255.0 applies an access list entry to any client on the same subnet as the IP address identified in the entry. Other subnet masks may also be used, depending on your network structure. For example, if you want two clients with IP addresses of 192.168.1.134 and 192.168.1.65 to share the same access permissions, and there are no other clients on the same subnet, you can group them in the access list by setting the IP address for a single entry as 192.168.1.x and the subnet mask to 255.255.255.0. For each IP address or group of IP addresses, you can set the access level, the protocols the client can use to access the TCM, and the network ports the client can use to access the TCM.
What Are Access Levels?

There are three levels of access: Deny Access: Prevents all access to resources provided by the TCM. Connections to the Tricon are not allowed. Read Only: Allows client to connect to the Tricon and view information provided via the TCM. Does not allow the client to change any settings or perform certain commands.
42
Chapter 3
Read/Write: Full access. Allows client to view information provided by the TCM, change settings, and perform all commands (including Download Change or Download All for TriStation). This access level should only be provided to trusted clients.
Access levels are configured by adding entries to the Client Access List. A maximum of 10 entries can be provided in the access list. The same access level is applied to all selected protocols in a single access list entry. If you want to provide different access levels for a selected client depending on which protocol they are using, you will need to create two separate entries in the access list, one for each protocol. Access levels apply to all users using the PC assigned the IP address entered in the access list. This means if multiple users are using the same PC, they will all have the same access rights. For example, every user using TriStation on a PC with a particular IP address would have the same access rights to the TCM. Individual user access should be controlled via workstation security; TCM access is controlled only at the IP address level.
CAUTION
Once you enable TCM client access control by selecting the Enable Access List check box, you must configure at least one client with TriStation Read/Write access. Failure to do so will prevent you from connecting to the Tricon again after your next download, and you will be unable to make any further changes to the application running on the controller, including changes to the TCM access control list. If all TriStation clients are accidentally locked out of Read/Write access, you can connect via a TriStation serial connection to reconfigure the access list. See Configuring a Tricon Serial Connection on page 38.
Note
If you choose not to enable access list control, you can still manage read/write access to specific ports using the Port Write Enabled property.
Sample Access List and Resulting Access Control

The following table is a sample access list, with the access control scenarios that would result if it was enabled on the TCM.
Sample TCM Access Control List

Entry 1 IP Address 206.216.1.12 Subnet Mask 255.255.255.0 Protocol TriStation Network NET 2 Access Level Read/Write Resulting Access Control Scenario A client with an IP address of 206.216.1.12 (or any client on the same subnet) attempting to access the TCM using the TriStation protocol on NET 2 would be granted Read/Write access. A client with an IP address of 206.216.1.12 (or any client on the same subnet) attempting to access the TCM using the TSAA protocol on NET 2 would be granted Read Only access. A client with an IP address of 192.168.1.05 attempting to access the TCM using the TriStation protocol on NET 1 or NET 2 would be denied access. A client with an IP address of 192.168.1.09 attempting to access the TCM using TSAA on NET 1 or NET 2 would be denied access. A client with an IP address of 192.168.1.05 (or any client on the same subnet) attempting to access the TCM using TSAA on NET 1 would be granted Read Only access. A client with an IP address of 192.168.1.05 (or any client on the same subnet) attempting to access the TCM using the TriStation protocol on NET 2 would be granted Read Only access. 1 A client with an IP address of 192.168.1.09 (or any client on the same subnet) attempting to access the TCM using the TriStation protocol on NET 1 would be granted Read/Write access. Access is denied for all IP addresses not included in entries 17, using any protocol on NET 1 or NET 2. None
206.216.1.12
255.255.255.0
TSAA
NET 2
Read Only
192.168.1.05
255.255.255.255
TriStation
NET 1 NET 2 NET 1 NET 2 NET 1
Deny Access
192.168.1.09
255.255.255.255
TSAA
Deny Access
192.168.1.05
255.255.255.0
TSAA
Read Only
6 Communication Guide for Tricon v9v10 Systems
192.168.1.05
255.255.255.0
TriStation
NET 2
Read Only
192.168.1.09
255.255.255.0
TriStation
NET 1
Read/Write
8 9
0.0.0.0 NULL
0.0.0.0 NULL
All NULL
All NULL
Deny Access NULL
1. If a client with the specific IP address of 192.168.1.05 attempts to access the TCM using the TriStation protocol on NET 2, the TCM will deny access. This is because the TCM evaluates the access control list beginning from the top, and continuing through the list until it encounters an entry that applies to the IP address requesting access. In this case, entry 3 specifically denies access to a client with the IP address of 192.168.1.05, so the TCM will deny access and not evaluate the list any further.
43
44
Chapter 3
Configuring the Access List

This section describes how to enable access control on the TCM and configure the access list for your selected clients. This applies only to model 4351A and 4352A TCMs; it does not apply to model 4351 or 4352 TCMs. When configuring the access list, take care to organize your entries so that the most specific are at the top, and the least specific are at the bottom. The last entry in the list should be used to define the access level for unspecified clients. The TCM evaluates the access control list from top (Entry 1) to bottom (Entry 10). The first match that the TCM makes (between the clients network parameters and those listed in an access list entry) determines which entry is used to authorize or deny access. If no match is found, the TCM automatically denies all access. Once you have enabled access control and configured the access list, you must perform a Download Change for the access control to take effect. Note After a Download Change or Download All has been performed so that access control on the TCM is enabled, all existing connections will remain connected, even if the clients access has been changed to Read Only or Deny Access. The new access levels will not take effect until the client disconnects and attempts to reconnect.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Access List tab.
45
Specify these properties.

Property Slot Selection Action Select the slot where the TCM module you want to configure an access list for is installed. In most cases, you should create identical access lists for the modules in both slots. Enable Access List Click to enable access control for this TCM. If cleared, access control will be disabled and all users can access TCM resources. The default is cleared. Click on the entry for the client you want to configure or change. Specify the IP address of the client that you want to allow, restrict, or deny access to the TCM. Can be used in conjunction with the Client IP Subnet Mask property to create groups of IP addresses with the same access levels. Client IP Subnet Mask This property allows you to group IP addresses, so that you can create a single entry in the client access list for all IP addresses on the subnet. If needed, enter the IP address for the subnet. The default is 255.255.255.0. Permission Click the level of access to the TCM you want to provide for the selected client. If the application includes safety-critical outputs, you should not set this property to Read/Write.
Client Access List Client IP Address
46
Chapter 3
Property Client Protocols Network
Action Select the protocol(s) that the selected client can use to access the TCM. The OPC protocol is not currently supported. Select the network(s) on which the selected client can access the TCM.
5 6
Click Update Client Entry to save the settings for the selected client. Repeat steps 4 and 5 for each client to be included in the access list. Note If necessary, click Reset Client Entry to reset the settings for the selected client to the default, unconfigured state. Click Reset All to reset all entries in the access list to the default, unconfigured state.
7 8
If a TCM is installed in the right slot, repeat steps 4 through 6 for that module. In most cases, you should configure identical access lists for the modules in both slots. Click OK to save your changes.
4
Overview Configuring Ethernet Ports in TriStation DDE Server for Triconex OPC Server for Triconex 48 50 60 69
48
Chapter 4
Overview
Client/server communication with Triconex controllers can be done by using the DDE Server and OPC Server applications, which use the Triconex System Access Application (TSAA) protocol. For most process control networks, using DDE Server or OPC Server is the best solution. TSAA protocol can also be used to write custom applications for accessing Triconex data, such as these: Control (read/write) applications for operators that need read access to Triconex status and write access to Triconex data. Monitor (read-only) applications such as a sequential events recorder or a status display that collects and records Triconex data.
For detailed protocol information, see Appendix D, TSAA Protocol.
Figure 15
Sample Tricon System Configuration
Applications that use TSAA to exchange information with a Triconex controller require a Tricon ACM, NCM, or TCM. You can install a maximum of two ACM and four NCM modules or four TCM modules in a controller. You can physically connect one Ethernet port on each ACM or NCM to an Ethernet network; you can connect one or more Ethernet ports for each TCM. Through one Ethernet port, the controller can communicate with multiple devices on a network, such as a TriStation PC, a print server, and a client PC.
Overview
49
The Ethernet port on the ACM and NCM is called NET 2 and it operates at 10 megabits per second. If you connect the ACM or NCM to a network that is faster than 10 megabits per second, you must use a media converter with appropriate cables. Ethernet ports on the TCM are called NET 1 and NET 2. The NET 1 and NET 2 ports can operate at 10 or 100 megabits per second. The data transmission rate of the device or network you connect determines which port and cabling you must use. Most Ethernet devices and networks operate at 100 megabits per second, so connecting one to a Tricon controller with a TCM usually means you must use Fast Ethernet (100BaseTX) cabling. Each Ethernet port must be configured in the TriStation project, which means you must specify the mode, access privilege, port type and speed, IP address, and time synchronization properties. Part of physically connecting an ACM, NCM, or TCM port to a network is to set the IP address of the port. The most convenient methods are to use the Triconex default address or a Reverse ARP server (for NCM only). Other ways are discussed in this chapter. A Tricon controller with a TCM installed on an Ethernet network can communicate with devices on other networks if you specify the IP address of the default gateway or other routes in the TriStation project. Specifying the default gateway is often sufficient, but you can specify multiple other routes if necessary. Another task is to specify whether external devices are to have access to the application running on the Triconex controller. There are many levels of access, including allowing general write access while protecting specific points from write access through configuration settings. For more information, see Tricon Write Access on page 121.
50
Chapter 4
Configuring Ethernet Ports in TriStation

This section explains how to specify the logical configuration of Ethernet ports in TriStation 1131. Procedures for setting the IP address are also included. For an Ethernet connection, a NET 2 port on an ACM or NCM must be used. Tricon supports NET 2 connections using ACM or NCM modules, but not both. For example, if you are using a NET 2 port on an NCM for an Ethernet connection, you cannot use the NET 2 port on the ACM. You must use a TCM to connect a Tricon to an open network through an Ethernet connection. An open network is an Ethernet network to which Triconex controllers and many types of Ethernet devices can be connected, including routers and gateways to other networks. You cannot use a TCM in the same controller as an NCM. A closed network is designed for maximum safety and includes only Triconex devices. To configure a closed network port, see Chapter 5, Peer-to-Peer Communication. This section includes: Note Configuring an ACM NET 2 (Ethernet) Port on page 51 Configuring an NCM NET 2 (Ethernet) Port on page 52 Configuring a TCM Ethernet Port on page 54 Setting the IP Address on page 56 The following procedures assume use of TriStation 1131 v4.1 or higher. If you are using another version of TriStation 1131, please refer to the documentation for the version you are using for detailed instructions on configuring the Ethernet ports.
51
Configuring an ACM NET 2 (Ethernet) Port

This procedure explains how to specify the logical configuration for an ACM Ethernet port.
Procedure
1 2 In TriStation, expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the ACM slot, and then click Setup.
Specify these properties on the ACM Setup screen.

Property Redundant Mode Used/Not Used Action Select the check box to specify that a redundant module is installed. Select Used to specify the slots that have an installed ACM module. To enable the right slot, select the Redundant Mode check box (above). Privilege Specify Read/Write to allow external devices connected to the NET 2 port to read and write tagnames. The default is Read Only. If set to Read Only, external devices cannot write to any tagnames no matter what other write access controls are used. This setting protects safety-critical tagnames from writes by external devices on an Ethernet network. If set to Read/Write, external devices can write to tagnames depending on the settings of other write access controls. This property must be used in conjunction with other write access controls. For more information, see Tricon Write Access on page 121.
52
Chapter 4
Property IP Address
Action If the network configuration allows, use a Triconex default address. If using a default IP address, leave blank. If not, enter the IP address that identifies the controller on the network. This must be the same IP address as entered on the TriStation Communication screen. If necessary, get an address from your network administrator or Information Technology department. If you have two ACM modules in a slot, you can give each module a different IP address and connect it to a different Ethernet network or device. For more information, see Setting the IP Address on page 56.
IP Subnet Mask Default Gateway IP Address Time Synchronization
If the controller is on a subnet, enter the subnet address. If needed, enter the IP address of the gateway to which the Tricon controller is connected. Typically, this information is available from a network administrator. Select NET 2 to enable time synchronization with the Tricon Master controller in a Peer-to-Peer network. Select None if no time synchronization will be performed through this module. For more information, see Time Synchronization on page 123.
Click OK.
Configuring an NCM NET 2 (Ethernet) Port

This procedure explains how to configure the logical configuration for an NCM NET 2 Ethernet port.
Procedure
1 2 In TriStation, expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the NCM slot, and then click Setup.
53
Specify these properties in the NCM Setup dialog box.

Property Installed/Not Installed Action Select to indicate which slots have modules installed. Available for the right slot only when the module is installed in a redundant (non-COM) slot. Specify Read/Write to allow external devices connected to the NET 2 port to read and write tagnames. The default is Read. If set to Read, external devices cannot write to any tagnames no matter what other write access controls are used. This setting protects safety-critical tagnames from writes by external devices on an Ethernet network. If set to Read/Write, external devices can write to tagnames depending on the settings of other write access controls. This property must be used in conjunction with other write access controls. For more information, see Tricon Write Access on page 121. IP Address Enter the IP address for the NCM. If the network configuration allows, use a Triconex default address. If using a default IP address, leave blank. If not, enter the IP address that identifies the controller on the network. This must be the same IP address as entered on the TriStation Communication screen. If necessary, get an address from your network administrator or Information Technology department. If you have two NCM modules in a slot, you can give each module a different IP address and connect it to a different Ethernet network or device. For more information, see Setting the IP Address on page 56. Global Positioning System Installed Time Synchronization Select the check box to synchronize time with a GPS. The default is cleared. Select the check box to synchronize time with the Tricon master node on a Peer-to-Peer network. The default is cleared. In a network of Triconex controllers which are synchronized with the master node, the master node can be synchronized with an external device such as an OPC client or the GPS. For more information, see Time Synchronization on page 123.
Privilege
Click OK.
54
Chapter 4
Configuring a TCM Ethernet Port

This procedure explains how to specify the logical configuration for a TCM Ethernet port. To configure a network port on the TCM for the Peer-to-Peer communication mode, see Chapter 5, Peer-to-Peer Communication. Note The following procedure applies only to model 4351A and 4352A TCMs. If you have an older model 4351 or 4352 TCM installed in your system, see Appendix G, TCM Model 4351/4352 Configuration.
Procedure
1 2 In TriStation, expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears.
Specify these properties on the Network tab.

Property Slot Selection Not Installed, Installed Action Select the slot where the TCM module you want to configure is installed. Click Installed to enable configuration of the module. Clicking Not Installed resets all options to their default state and makes them unavailable for configuration. The default is Not Installed.
55
Property Transceiver Mode
Action Select the communication mode. The default is Auto-Negotiate. If you have a model 4352A TCM with fiber connectors, you must select 100 Mbps as the communication mode. The 4352A module cannot connect at 10 Mbps.
IP Address
Enter the IP Address for the port. NET 1 and NET 2 cannot use the same IP address. The default values are: NET 1: 192.168.0.x NET 2: 192.168.1.x where x is the node number.
IP Subnet Mask Default Gateway IP Address TriStation Port Number TSAA Port Number Port Write Enabled
If needed, enter the IP address for the subnet. The default is 255.255.255.0. If needed, enter the IP address for the default gateway. The default is 0.0.0.0. Enter the UDP port to use for the TriStation connection. The default is 1502. Enter the UDP port to use for TSAA connections, including DDE Server, SOE Recorder, and OPC Server. The default is 1500. Select this check box if you want to allow TSAA writes to this port. Applies to all TSAA connections on this port. The default is cleared (the port is read-only).
4 Note
Click OK. Changes to TCM IP addresses are not effective until the existing connection is closed and a new connection is opened. Once a connection is opened, it remains open until you close it, even if the IP address is changed via a download change operation.
56
Chapter 4
Setting the IP Address

To enable a Triconex controller for communication with network devices, you must set the IP addresses of ACM, NCM, and TCM modules on the network. If the network configuration permits the use of Triconex default IP addresses, the addresses are set on the network when you download the TriStation application, assuming that the correct node number and default IP addresses have been specified in the configuration. If you cannot use default IP addresses, there are other ways to set the IP addresses of ACM, NCM, and TCM modules on a network. These methods involve asking your network administrator for the intended IP addresses. The easiest way is to use a Reverse ARP (RARP) server on the subnet that has been configured in advance with the intended addresses. Other ways entail connecting the TriStation PC to an EICM or TCM serial port, specifying IP addresses in the TriStation project, downloading the TriStation application, then reconfiguring the physical connection. All the procedures for setting the IP address are based on the assumption that the controller includes at least one ACM, NCM, or TCM module with an Ethernet port connected to a network. To use the procedures, you should know how to: Connect the Triconex controller to a network Connect the TriStation PC to the controller Configure the TriStation project with the node number of the controller and the IP address
For more information, see Chapter 3, TriStation Communication. Note Typically, Triconex controllers are located on their own subnet which is connected to a larger network such as a DCS. Your network administrator can set up the subnet for compatibility with the Triconex default IP addresses and can program any routers that lie between the DCS and the Triconex subnet with addressing information about the Triconex controllers.
Using the Default IP Address for TriStation Communication

This procedure explains how to use the default IP address for network communication between a controller and a TriStation PC.
Procedure
1 2 3 4 5 Connect the controller to the network using the NET 1 or NET 2 port on the TCM. On the ACM or NCM, use the NET 2 port. Power up the controller. Connect the TriStation PC to the network, or directly to a port. In the TriStation project, expand the Controller tree, double-click Configuration, and then click TriStation Communication. On the TriStation Communication screen, verify the IP Address is: 192.168.1.1 (Tricon ACM, NCM, or TCM)
57
If the controller includes two communication modules, the default address applies to both modules. Note 6 7 The left and right modules in ACM, NCM, or TCM slots use the same 48-bit physical MAC address and cannot be connected to the same network.
On the Controller tree, click Configuration. Expand Hardware Allocation, click the slot where the communication module is installed, and then click Setup. If a communication module is not installed, insert a communication module, and then click Setup.
8 9 10 11 12 13 14
In the Setup dialog box, enter the same IP address specified on the TriStation Communication screen. If the controller includes a redundant communication module, enter the same IP address for the other slot. On the Controller tree, click the Controller Panel. From the Commands menu, click Connect. Wait about 40 seconds for the module to reset and become active. When the module is active, the Active indicator is green. On the Commands menu, click Download All to download the TriStation 1131 project to the controller. On the TriStation PC, from the Start menu, click the MS-DOS Command Prompt. Type the command ping followed by the IP address to be tested. For example, for an IP address of 206.32.216.43, enter this:
ping 206.32.216.43
If the network connection is made, the reply includes the IP address followed by byte and time information. If the connection is not okay, the reply is Request timed out. Note If you receive a Request timed out reply, check your network cable and port connections to verify they are securely connected, verify your configuration settings are correct, and then retry the ping command.
58
Chapter 4
Setting an IP Address Using a RARP Server

This procedure explains how to set the IP address of a communication module using a RARP server on the local network. To use this procedure, the network administrator must program the RARP server with the intended IP address for the controller. If this is not possible, use another method to set the IP address.
Procedure
1 2 3 4 Give the network administrator the MAC address, which is 40-00-00-00-00. Ask the network administrator for the IP address that is to be used for the controller. Connect the controller to the network through a network port on the communication module. Power up the controller. During initialization, the communication module sends a request to the RARP server for an IP address that has been mapped to its own 48-bit MAC address. Note 5 6 The left and right modules in ACM or NCM slots use the same 48-bit physical MAC address and cannot be connected to the same network. On the TriStation PC, from the Start menu, click the MS-DOS Command Prompt. Enter the command ping followed by the IP address to be tested. For example, for an IP address of 206.32.216.43, enter this:
ping 206.32.216.43
If the network connection is made, the reply includes the IP address followed by byte and time information. If the connection is not okay, the reply is Request timed out. Note If you receive a Request timed out reply, check your network cable and port connections to verify they are securely connected, verify your configuration settings are correct, and then retry the ping command. Connect the TriStation PC to the network, or directly to a network port on the communication module. In the TriStation project, expand the Controller tree, click Configuration, and then click TriStation Communication. On the TriStation Communication screen, specify the Node Number of the controller and the intended IP address. On the Commands menu, click Connect. Wait until the connection is made. On the Commands menu, click Download All to download the TriStation project to the controller.
7 8 9 10 11
59
Setting an IP Address Using an EICM or TCM

This procedure explains how to set the IP address of the Triconex controller by initially connecting the TriStation PC to an EICM or TCM serial port, and downloading the TriStation project. After the address is set, you can disconnect the TriStation PC from the EICM or TCM serial port, and reconnect it to an Ethernet port on the ACM, NCM, or TCM.
Procedure
1 2 3 4 Ask the network administrator for the IP address to be used for the ACM, NCM, or TCM. Connect the TriStation PC to a serial port on the EICM or TCM. Connect the controller to the network using the NET 1 or NET 2 port on the TCM. On the ACM or NCM, use the NET 2 port. In the TriStation project, configure the following: 5 6 7 8 9 The EICM or TCM serial port and Ethernet ports The node number and node name of the controller The intended IP address
Power up the controller. On the Controller tree, click Controller Panel. On the Command menu, click Connect To. On the Connect To screen, select the Serial Port option and the COM port to which the TriStation cable is connected. Connect to the Triconex controller and download the TriStation project. The ACM, NCM, or TCM initializes (resets) and accepts the IP address that you specify in the TriStation project.
10 11
On the TriStation PC, from the Start menu, click the MS-DOS Command Prompt. Enter the command ping followed by the IP address to be tested. For example, for an IP address of 206.32.216.43, enter this:
ping 206.32.216.43
If the network connection is made, the reply includes the IP address followed by byte and time information. If the connection is not okay, the reply is Request timed out. Note If you receive a Request timed out reply, check your network cable and port connections to verify they are securely connected, verify your configuration settings are correct, and then retry the ping command. If the IP address is set, you can disconnect the TriStation PC from the EICM or TCM serial port, and connect it to an Ethernet port or to the network.
12
60
Chapter 4
DDE Server for Triconex

This section explains how to use the Triconex DDE Server software to communicate between Triconex controllers and DDE clients on an Ethernet network. Triconex DDE Server is a Windows application that enables DDE-compliant clients to request data and, if allowed, to change data in a Triconex application. A client can request data about input and output variables, memory variables, and system attributes. Client applications use DDE protocol to communicate with a DDE server. Any Windows application that supports DDE protocolsuch as Microsoft Excelcan use Triconex DDE Server. Triconex DDE Server communicates with one or more Triconex controllers through the TSAA (Triconex System Access Application) protocol. To return data to clients, the DDE Server uses DDE protocol. The DDE Server PC must be connected to an Ethernet port on a Triconex controller. For Tricon controllers, the NCM, ACM, or TCM can be used. For Trident controllers, the CM can be used. This figure depicts the communication protocols used with Triconex DDE Server.
Figure 16
Triconex DDE Server Protocols
Triconex DDE Server System Requirements

The following are the minimum system requirements for a PC running Triconex DDE Server: Microsoft Windows NT version 4.0 (Service Pack 5), or Windows 2000 Pentium III 128 MB RAM CD-ROM drive 125 MB free space on the hard drive Network interface card (also referred to as network adapter card)
61
Installing the Triconex DDE Server

The setup program provided by Triconex installs all the necessary components of the Triconex DDE Server on a Windows 2000 or NT PC. To install DDE Server, you must be logged on to Windows as an Administrator or you must have the privileges of an Administrator.
Installing on Windows 2000

1 2 3 4 5 6 If a previous version is installed, uninstall it. Close all open applications. Insert the Triconex DDE Server CD in the CD-ROM drive. Browse the CD contents to locate the Windows2000 folder. Double-click setup.exe to start the installation. Follow the InstallShield Wizard instructions.
Installing on Windows NT
1 2 3 4 5 If a previous version is installed, uninstall it. Close all open applications. Browse the CD contents to locate the WindowsNT folder. Double-click setup.exe to start the installation. Follow the InstallShield Wizard instructions. 6 If the installation is successful, a message advises you to click Finish. You are finished with the installation procedure. If the installation requires Factory Suite 2000 components, a message appears and the DDE Server setup is closed. Continue to step 6 in this procedure.
Go to the FS2000 folder (under the WindowsNT folder) and double-click SETUP.bat. You may see a warning about the Windows service pack installed on your PC. Click OK to continue installing the Factory Suite 2000 components.
Follow the installation instructions. You may also be asked if you want to install Adobe Acrobat 3.0, which is an older version of the product. Click Cancel to not install this version, and then click OK. Go back to the WindowsNT folder and double-click the setup.exe program to restart the DDE Server installation. Click Finish to complete the installation. You may be required to reboot your PC.
8 9
62
Chapter 4
Configuring the DDE Server Application

When you configure the DDE Server application, you specify communication properties used by a Triconex controller (also called a host or node) to communicate with DDE clients. These properties allow DDE clients to identify which controller to communicate with and what communication protocol to use. If you plan to use a redundant DDE network, you need to use DDE Server PCs and install redundant communication modules in the controller. For more information, see Configuration Requirements for Redundancy on page 65. You can also modify or delete the configuration of a Triconex controller. Before modifying a configuration, make sure it is not being used by a DDE client. If you delete a configuration, the associated controller can no longer be accessed by a DDE client. To allow a DDE client to change the values of Triconex variables, you must enable write access by setting controls in the TriStation application.
Specifying the Triconex Host Configuration

This procedure explains how to specify host information for the Triconex controller, which must be done before a DDE client can access data from the controller.
Procedure
1 2 3 From the Start menu, select Programs, then Triconex, then Triconex DDE Server. The DDE Server main window appears. From the File menu, click Configure. The Configuring Host Information screen appears. Do one of the following: Select an existing node and click Modify. Click Add to add a host.
The Host Name Configuration screen appears.
63
Specify the following properties:

Property Host Name Action Enter the user-defined name for the controller. This name must be unique for each controller. (It is used by the DDE client application to request data from the controller.) The default names are TRINODE01 (for node 1) through TRINODE31 (for node 31). Node Number Enter the Triconex node number. This number must be unique for each controller. It also must match the physical switch settings on the MP Front Panel, the ACM or NCM (if installed), and the node number specified in the TriStation project. The default values are 1 to 31. Redundant Identifies whether there are redundant paths to the controller. Select this check box if the physical configuration is redundant. This means that two network interface cards must be connected to network ports on two communication modules. For Tricon, the NET 2 port on two ACMs or two NCMs. Note: The redundant paths can be configured through the NET 1 and NET 2 ports on one TCM. For Trident, the NET 1 or NET 2 port on two CM modules The default is not redundant. For more information, see Configuration Requirements for Redundancy on page 65. Time Sync Identifies whether a Triconex node (host) is to be synchronized with the clock on the DDE Server PC. If there is more than one Triconex controller in a network, select the master node for synchronization with the DDE Server PC clock. The master node can then synchronize the time of the other Triconex controllers. For time-critical applications, Triconex does not recommend selecting the Time Sync property because PCs are not generally a reliable source for time synchronization. The default is not synchronized. Poll Time Identifies how often the Triconex controller refreshes the data stored as aliases. The polling interval must be greater than the scan time of the controller. For more information on aliases, see Appendix F, Tricon System Aliases. The default is 1,000 milliseconds (one second).
64
Chapter 4
Property Use 802.2
Action Select this check box if the 802.2 protocol is used to communicate with the DDE client. If you configure a node to use 802.2 protocol, you must also configure the server properties. For more information, see Configuring Server Properties for 802.2 Protocol on page 64. These configuration rules apply to the 802.2 protocol: For Tricon v7.x and v8.x nodes, you must use the 802.2 protocol. For Tricon v9.x or 10.x nodes with ACMs or NCMs, you can use either the 802.2 protocol or the TCP/IP protocol. For v10 nodes with TCMs, you cannot use the 802.2 protocol. You must use the TCP/IP protocol. The default is clearedmeaning the TCP/IP protocol is used.
First Adapter
Enter the number of the first network adapter (interface) card in the primary PC. Available only if the Use 802.2 check box is selected. You can have multiple Ethernet adapters in your DDE PC. One is typical; two are needed for redundancy. The first adapter number is usually zero (0).
2nd Adapter
Enter the number of the second network adapter (interface) card in the redundant PC. Available only if the Use 802.2 and Redundant check boxes are selected. The second adapter number is usually one (1). Enter the IP address of the primary communication module in the Triconex controller. You must specify this property if the Use 802.2 check box is cleared. Enter the IP address of the redundant communication module in the Triconex controller. You cannot specify a redundant IP address if the Use 802.2 check box is selected. Select whether the host is a Tricon or a Trident controller.
IP Address
Redundant (IP Address) Device Type
Configuring Server Properties for 802.2 Protocol

This procedure explains how to configure the server properties, which must be specified if the Use 802.2 property is specified for any of the hosts (controllers). Note TCMs are not compatible with the 802.2 protocol.
Procedure
1 On the Host Name Configuration screen, click Server. The Configuring Host Information screen appears.
65
Specify the following properties:

Property Server Poll Rate (MS) Action Enter the rate in milliseconds at which DDE Server updates clients such as Microsoft Excel or Wonderware InTouch applications. Must be greater than 20 milliseconds and less than 1,000 milliseconds. Enter the size of the buffer (in bytes). This depends on the number of Triconex controllers using 802.2 protocol. For each host using 802.2 protocol, a minimum of 50,000 bytes for each host must be specified. For example, if three hosts use 802.2 protocol, the buffer must be set to 150,000 bytes. The default is 100,000. LLC SAP (Server Access Point) Enter the address for the DDE Server on the PC. This must be a unique address. The default is 4.
LLC Buffer Size
Testing a TCP/IP Connection

This procedure explains how to determine if the network connection is valid, which can be done after configuring the Triconex hosts. You might want to test the IP addresses of the network adapter card in the client PC, and the Triconex communication module(s).
Procedure
1 2 On any PC connected to the network, from the Start menu, click the MS-DOS Command Prompt. Type the word ping followed by the IP address to be tested. For example, for an IP address of 206.32.216.43, enter this:
ping 206.32.216.43
If the network connection is made, the reply includes the IP address followed by byte and time information. If the connection is not okay, the reply is Request Timed Out.
Configuration Requirements for Redundancy

For Tricon controllers, a redundant network can be configured using either TCP/IP protocol or 802.2 protocol. Typically, hardware setup is done before software configuration. The following hardware is required: For Tricon, two NCMs, two ACMs, or two TCMs in one or more Tricon controllers. For the DDE client PC, two network adapter cards.
Configuring Redundancy With TCP/IP Protocol

This procedure explains how to configure network redundancy when using TCP/IP protocol, which can be used with Tricon version 9 and later controllers that are using TriStation 1131.
66
Chapter 4
The configuration procedure involves setting IP addresses. If the network topology permits, use the Triconex default addresses. If not, get the IP addresses from your network administrator. If the DDE Server PC is not on the same subnet as the Triconex controller, you must specify the destination address during Ethernet port configuration.
Procedure
1 2 Install two network adapter cards and the TCP/IP protocol (see page 21) on the DDE Server PC. On the DDE Server PC, use Windows NT/2000 procedures to set the IP addresses of the network adapter cards. A sample IP address is: 206.32.216.x (where x = 1 to 254) 3 4 Connect the network adapter cards on the DDE Server PC to Ethernet ports on the primary and redundant Triconex communication modules. In TriStation, set the IP addresses for the primary and redundant communication modules. A sample IP address is 206.32.64.y where y is the node number. The node number is set with physical switches on the NCM, ACM or MP front panel (for TCM). 5 From the DDE server application, configure each Triconex node with a host name. You must use the same IP address for the node configuration in DDE Server that is used in TriStation.
Configuring Redundancy With 802.2 Protocol

This procedure explains how to configure network redundancy when using 802.2 protocol, which can be used with Tricon version 7 and later controllers. The 802.2 protocol is only available for Tricon controllers. Note TCMs are not compatible with the 802.2 protocol.
Procedure
1 2 3 4 Install two network adapter cards and the DLC protocol (see page 21) on each network card on your DDE PC. Connect the first network adapter card in the DDE Server PC to the left NCM or ACM. Connect the second network adapter card to the right NCM or ACM. In the DDE Server application, select the Redundant and Use 802.2 check boxes (see page 62). When these properties are selected, it is not necessary to configure IP addresses. Set the First Adapter property to 0 (zero) and the 2nd Adapter property to 1 (one).
67
Requesting Data with a DDE Client Application

When you use a DDE client application to request data, you identify the DDE Server application to use, the Triconex controller to be accessed, and the data to be accessed. This information is referred to as the DDE address. Each DDE client application uses a three-part DDE address format, but might use slightly different syntax. The DDE address format is as follows: Application + Topic + Item
DDE Address Application Topic Description Identifies the Triconex DDE Server application name, which is TR1DDE. Identifies the node name for a Triconex controller as configured in the DDE Server application. The default node names for controllers 1-31 are TRINODE01 through TRINODE31. For more information on defining nodes, see Specifying the Triconex Host Configuration on page 62. Item Identifies the alias number for the requested Triconex variable. You can identify one or more items. For more information on aliases, see the TriStation 1131 Developers Guide.
Save the address you have specified in the DDE client application and start the DDE Server application. Both the client and server applications must be running concurrently to request or exchange data. The DDE server sends the request to the Triconex controller, then returns the data to the DDE client application. As an example, the following address could be entered in a blank cell of a Microsoft Excel worksheet to request the value for alias 40001 in TRINODE02: =TR1DDE|TRINODE02!40001 Although you can run only one DDE Server application at a time, you can run as many DDE client applications as allowed by the virtual memory available on your PC.
Requesting Network Status

To find out whether the network ports on a Triconex controller are receiving data, enter either of the following commands in any client application using the following format.
=tr1dde|TRINODE01!STATUS =tr1dde|TRINODE01!RSTATUS Reads network status Reads redundant network status
For details on syntax for the DDE address, see the users manual for the client application you are using.
68
Chapter 4
Monitoring Responses from the Controller

The Triconex DDE Server allows you to monitor responses from the Triconex controller which can include alert entries as well as log entries that indicate a successful response. The entries are logged in the order in which they occur. To view the most current entries, scroll to the bottom of the list. If you select the Stats command on the Dump menu, older entries might appear at the bottom of the list, as shown in this screen.
Changing View Options

To keep the DDE Server main window on top of all other windows, select the Always on Top command on the View menu. A check mark next to the command means it is selected.
DDE Server Menu Commands

The DDE Server menus include these commands:
Command Configure... Exit Always on Top Stats Triconex DDE Server Help About Triconex DDE Server Menu File File View Dump Help Help Description Opens the Configure Host Information screen and allows you to configure up to 31 controllers for use with the DDE Server application. Closes the DDE Server application. Keeps the DDE Server main window on top of other windows. Displays statistics for all Triconex controllers. Opens the online Help for the DDE Server application. Displays the current version number of the DDE Server application and registered owner information.
OPC Server for Triconex
69

The Triconex OPC Server is a Windows application which allows OPC clients to have read and write access to Triconex program variables. OPC is a standard set of non-proprietary interfaces used to develop client/server applications. The OPC Server PC must be connected to an Ethernet port on a Triconex controller. For Tricon, the NET 2 port on the ACM or NCM must be used; on the TCM, use the NET 1 or NET 2 port. For Trident, the NET 1 or NET 2 port on the CM must be used. OPC Server is configured by exporting an XML configuration file from a TriStation project and opening that file in the OPC Server software. After OPC Server is configured, the OPC client can ask the OPC Server to get data from a Triconex controller. This figure depicts the communication protocols used with the Triconex OPC Server.
Figure 17
Communication Protocols Used with Triconex OPC Server
You can include TriStation configurations for multiple networked controllers in one XML file by using the same file name when exporting each configuration. The information from each TriStation configuration is appended to the file. In OPC Server, you can edit the properties of aliases, tagnames, and other aspects of the configuration. If you change the name of the configuration or alias, a new entry is created in the XML configuration file. If you change properties related to the entry, but do not change the configuration or alias name, those properties are changed for the entry. The Triconex OPC Server is available from Triconex and Matrikon. For more information on the Triconex OPC Server and OPC client applications, see the Matrikon OPC Web site at www.matrikonopc.com.
70
Chapter 4
Configuring the OPC Server

This procedure explains how to configure the OPC Server with alias information from a TriStation project. With TriStation 1131 version 3.1 and later, alias information can be exported to an XML file and then imported to the OPC Server. To use OPC Server with TriStation versions earlier than v3.1, alias information must be manually entered to the OPC Server.
Exporting the Configuration File From TriStation

1 2 3 4 In TriStation, assign all aliases to be accessed by OPC Server. To allow an OPC client to change the values of Triconex variables, enable write access in the TriStation application. From TriStation, complete the application and download it to the controller. Export the XML configuration file by exporting the tagnames (points). Select the file type as Matrikon OPC XML Data Files (*.XML). Name the file using the XML extension, using a maximum of eight characters. If you include multiple configurations, use the same file name each time you use the export command.
Configuring OPC Server

1 If not already done, install OPC Server and start it. Refer to the installation instructions provided by Matrikon for detailed installation information. When OPC Server is loaded, a gray Triconex icon appears on the status bar. 2 Open the XML configuration file by right-clicking the Triconex icon from the status bar and selecting Configure. The OPC Server for Triconex PLCs window appears. 3 From the File menu, select Open, then select the XML file you exported from TriStation. As the file loads, statistics are displayed. When finished, you can display Server Configuration and Alias Configuration information. 4 Select a node from the Current Configuration pane to view Server Configuration information. This following screen shows the Server Configuration information. You can make changes to these properties by entering the changes and clicking Apply.
71
Click node to display Server Configuration
Specify the properties of the Left and Right ACM, NCM, or TCM on tab 1 and tab 2
Under Protocol Settings, specify the TCP/IP address and other Triconex communication module properties on tab 1. If the controller includes two communication modules, specify the properties of the left module and the right module on tabs 1 and 2. Do not use tabs 3 through 7.
Select a node under Alias Configuration in the Current Configuration pane to view alias information. To make changes to an alias, double-click the alias row. The Edit Alias dialog box appears, as shown in this following figure.
72
Chapter 4
The Name column displays tagnames
The Item Path column displays the node, bin, and memory offset
Click node to display Alias Configuration
Double-click alias row to edit an alias
7 8
Repeat steps 8 through 11 for each node configuration included in the XML file. If you made changes to any of the configurations and want to keep them, save the configuration file.
Configuring the OPC Client

1 2 To use the OPC Server to get data from a Triconex controller, install an OPC client application. (Matrikon sells OPC client applications.) In the OPC client application, you can specify the tagnames or aliases of the data to be accessed. A sample tagname is DO_02, as shown in the preceding screen. The location of the data is described as node: bin: offset in the Item Path column for the Alias Configuration.
73
Redundant Configuration
OPC Server can be configured for dual redundancy by using two OPC Server PCs. Each PC must include two Ethernet interface cards, which must be connected to one Triconex communication module on the primary network and one Triconex communication module on the redundant network. You must specify the properties of the redundant Triconex communication modules in the OPC Server Configuration dialog box (see page 70). See Redundant Devices on page 13 for a sample redundant configuration including OPC Server.
Adjusting System Time

An OPC client can use the Device Clock tagname to read or write the system time of a Triconex controller. The Device Clock tagname is derived from Triconex status information in the OPC Server Configuration. For more information, see Time Synchronization on page 123. See also the documentation for the OPC client software. Before you can use the Device Clock tagname to adjust the system time of a Triconex controller, you must configure the TriStation project to allow write access by external devices on an open network. See the TriStation 1131 Developers Guide for more information.
Other OPC Products

For users of OPC Server, two additional OPC products are available from Triconex and Matrikon: the OPC Data Manager and the OPC Redundancy Broker.
OPC Data Manager

The OPC Data Manager (ODM) is an application that transfers data from one OPC server to another. ODM is useful for sharing data between two or more control systems, such as a Triconex controller and a DCS. Traditional OPC-enabled systems share data by implementing one application as an OPC client, and another as an OPC server. If two applications are servers instead of clients, they cannot exchange data. ODM solves this problem by acting as a doubleheaded or thin OPC client to both servers. It requests data from one OPC server and immediately sends it to the other OPC server. ODM includes these features: Support for both COM and DCOM architectures Support for DDE and OPC message protocols Operation as a Windows service or a normal application Real-time data monitoring Extensive error tracking and management
For more information, see the MatrikonOPC Data Manager Users Manual or the Matrikon OPC Web site at www.matrikonopc.com.
74
Chapter 4
OPC Redundancy Broker

The OPC Redundancy Broker (ORB) is a messaging application designed for systems that must use redundant devices to ensure high reliability. ORB constantly monitors the primary OPC server and redirects communication to the standby OPC server when a failure is detected. ORB can integrate with any OPC compliant client/server configuration and can be retrofitted to existing configurations. ORB includes these features: Intuitive configuration and monitoring features Choice of hot, cold, or warm fail-over for each OPC server Automatic fail-over notification by e-mail, fax, log file, or pager Extensive error tracking and diagnostic capabilities
For more information, see the MatrikonOPC Redundancy Broker Users Manual or the Matrikon OPC Web site at www.matrikonopc.com.
5
Overview Peer-to-Peer Data Transfer Time Configuring Peer-to-Peer Ports in TriStation Allocating Peer-to-Peer Memory Using Send and Receive Function Blocks Restrictions on Data Transmission Speed Monitoring Peer-to-Peer Communication Examples of Peer-to-Peer Applications 76 78 80 83 84 86 87 88
76
Chapter 5
Overview
Triconex Peer-to-Peer protocol is designed to allow multiple Tricon and Trident controllers in a closed network to exchange safety-critical data. (If you plan to implement a complex Peer-toPeer network, please contact Triconex Technical Support.) To enable Peer-to-Peer communication, you must connect each controller to an Ethernet network by using a NET 1 (Ethernet) port on the NCM or TCM. The controllers exchange data by using Send and Receive function blocks in their TriStation applications.
NN M M CC M P PP M M ABC 1 2
Figure 18
Simple Triconex Peer-to-Peer Network Configuration
To configure a TriStation application for Peer-to-Peer communication, you must: Configure the physical port connection for Peer-to-Peer mode Allocate memory for Send and Receive function blocks Add Send and Receive function blocks to the TriStation application Observe restrictions on data transmission speed
In addition, Triconex recommends that you calculate the data transfer time to determine whether the control algorithms will operate correctly. A TriStation application must use a specific Send function block to send data to a matching Receive function block in another TriStation application. Each Send function block has a parameter that identifies the Receive function block to which it sends data. Each Receive function block has a parameter that identifies the Send function block from which it receives data. The Send and Receive function blocks can transfer data with BOOL, DINT, or REAL data types. Some function blocks transfer 20 data values, and others transfer 32 data values. For detailed information about the available Send and Receive function blocks, see the TriStation Libraries Reference. Peer-to-Peer communication speed for Tricon controllers is 10 megabits per second with an NCM installed, and 10 or 100 megabits per second with a TCM installed. Trident controllers
Overview
77
communication speed is 10 or 100 megabits per second. If your network includes a Tricon with a TCM and a Trident, you can run the entire network at 100 megabits per second. If your network includes a Tricon with an NCM and a Trident, you can run the entire network at 10 megabits per second, or you can use a hub that converts messages from 10 to 100 megabits per second when they are transferred from the Tricon to the Trident. In this scenario, Triconex suggests using the NET 1 port on both Tricon and Trident communication modules, because 10 megabits per second is the only speed available on NET 1. With this setup, NET 2 is available for faster communication with external devices on an Ethernet network. For more information, see Restrictions on Data Transmission Speed on page 86. For monitoring Peer-to-Peer data exchange, TriStation provides function blocks and system aliases to track network communication paths and verify whether the Ethernet ports are receiving data from other controllers. The sample programs described in this chapter are available on the TriStation CD. These programs show how to send data at high speed and under controlled conditions, and how to measure the maximum data transfer time. Note With a TCM installed in your Tricon, you can also perform time synchronization over the Peer-to-Peer network using the NET 1 or NET 2 port. See Time Synchronization on page 123 for more information.
78
Chapter 5
Peer-to-Peer Data Transfer Time

In a Peer-to-Peer application, data transfer time includes the time required to initiate a send operation, send the message over the network, and have the message read by the receiving node. Additional time (at least two scans) is required for a sending node to get an acknowledgment from the MPs that the message has been acted on. These time periods are a function of the following parameters of the sending and receiving controllers: Scan time Configuration size Number of bytes for aliased variables Number of Send function blocks, Receive function blocks, printing function blocks, and Modbus master function blocks Number of controllers on the Peer-to-Peer network
Send function blocks require multiple scans to transfer data from the sending controller to the receiving controller. The number of send operations initiated in a scan is limited to five. The number of pending send operations is limited to 10. A typical data transfer time (based on a typical scan time) is 1 to 2 seconds, and the time-out limit for a Peer-to-Peer send (including three retries) is 5 seconds. Consequently, the processtolerance time of the receiving controller must be greater than 5 seconds. Process-tolerance time is the maximum length of time that can elapse before your control algorithms fail to operate correctly. If these limitations are not acceptable, further analysis of your process is required.
Estimating Memory for Peer-to-Peer Data Transfer Time

This procedure explains how to estimate memory for Peer-to-Peer data transfer time between a pair of Triconex controllers. The more memory allocated for aliased points, the slower the transfer time.
Procedure
1 2 3 In TriStation, open the project for the application running on the sending controller. Expand the Controller tree, and double-click Configuration. On the Configuration tree, click Memory Allocation. Find the bytes allocated for BOOL, DINT, and REAL points: On the Configuration tree, click Memory Points, Input Points, or Output Points. Double-click the graphic for the point type. Add the number of bytes allocated for all BOOL input, output, and aliased memory points. Enter the number in step 1 of the following worksheet. Do the same for DINT and REAL points and enter the results in step 1.
Repeat steps 13 for the receiving controller, and enter the numbers in step 3 of the following worksheet. Follow the instructions on the worksheet to estimate the transfer time.
Peer-to-Peer Data Transfer Time
79
Steps 1. Enter the number of bytes for each point type on the sending controller and divide or multiply as indicated. Add the results.
Point Type BOOL DINT REAL
Allocated Bytes _________ _________ _________
Operation 8= x4= x4=
Result _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________ _________
Total bytes of aliased points TBS = 2. Multiply the total bytes sending (TBS) from step 1 by 0.01 3. Enter the number of bytes for each point type on the receiving controller and divide or multiply as indicated. Add the results. BOOL DINT REAL _________ _________ _________ TS = 8= x4= x4=
Total bytes of aliased points TBR = 4. Multiply the total bytes receiving (TBR) from step 3 by 0.01 5. Get the scan time of the sending node in milliseconds by viewing the Scan Time in the Execution List. 6. Get the scan time of the receiving node in milliseconds by viewing the Scan Period in the Execution List. 7. Multiply the larger of TS or SS by 2. 8. Multiply the larger of TR or SR by 2. 9. Add the results of step 7 and 8 to get the data transfer time 10. If the number of pending send requests in the application is greater than 10, divide the number of send requests by 10. 11. Multiply the results of steps 9 and 10 to get the adjusted data transfer time. Adjusted DT DT= TR = SS = SR =
_________ _________ _________
12. Compare the adjusted DT to the process-tolerance time to determine if it is acceptable.
80
Chapter 5
Configuring Peer-to-Peer Ports in TriStation

These procedures explain how to configure an Ethernet port on the Tricon NCM or TCM for communication with other Triconex controllers on a Peer-to-Peer network.
Configuring Peer-to-Peer on the NCM

1 2 In TriStation, open your project and then expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the NCM slot, and then click Setup.
Specify these properties in the NCM Setup dialog box.

Property Installed/Not Installed Action Select to indicate which slots have modules installed. Available for the right slot only when the module is installed in a redundant (non-COM) slot. The NET 1 port on an NCM is pre-configured for Peer-to-Peer communication, and operates at 10 megabits per second. Global Positioning System Installed Time Synchronization Select the check box to synchronize time with a GPS, only if the NCMG acts as the master node. The default is cleared. Select the check box to synchronize time with the Tricon master node. The default is cleared. If this controller is the master node, you should still select this check box to use time synchronization.
Click OK.
Configuring Peer-to-Peer Ports in TriStation
81
Configuring Peer-to-Peer on the TCM

TCM supports Peer-to-Peer networking which allows routing of messages between different networks through routers. Note The following procedure applies only to model 4351A and 4352A TCMs. If you have an older model 4351 or 4352 TCM installed in your system, see Appendix G, TCM Model 4351/4352 Configuration. In TriStation, open your project and then expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. 3 Click the Peer-to-Peer tab.
1 2
4 5
Under Slot Selection, select the module (slot) you want to configure Peer-to-Peer ports for. Select a node (controller), and specify these properties.
Property Destination UDP Port Action Enter the UDP port number for each controller to be communicated with on the Peer-to-Peer network. This must be the same number that the controller uses as its UDP Base Port Number. Click the network that the selected node is connected to. The default is NET 1. Enter the IP address for the controller.
Network IP Address
82
Chapter 5
6 7 Note 8
Click Update to apply the new settings for the selected node. Repeat steps 4 through 6 for each node to be included in the network. If necessary, click Reset All to reset all node settings for the selected slot to their default, unconfigured state. Once all nodes have been configured, specify these properties (applicable to all nodes on the Peer-to-Peer network).
Property UDP Base Port Number Action For each network port, enter the UDP base port number for the controller. Enter 0 to disable Peer-to-Peer over UDP/IP on the network. The default is 1503 on NET 1 (meaning Peer-to-Peer is enabled on NET 1) and 0 on NET 2 (meaning Peer-to-Peer is disabled on NET 2). UDP port numbers must be unique. Enable Communication with Tricon V8 and V9 Peer-to-Peer Systems Select the check box to enable communication with Tricon version 8 and 9 systems. The default is cleared. Available only for a module installed in the left slot.
Click OK.
Allocating Peer-to-Peer Memory
83
Allocating Peer-to-Peer Memory

This procedure explains how to allocate memory for Peer-to-Peer functions, which is based on the maximum number of Send and Receive numbers you specify. To save memory and minimize scan time, you should use the lowest possible numbers. The maximum number does not have to be the same for Sends and Receives. For example, a TriStation application might need to send messages to three applications, but need to receive messages from only one application. A change in Peer-to-Peer allocation requires a Download All.
Procedure
1 2 In TriStation, open your project, expand the Application tree, double-click Implementation, and then click Peer-to-Peer Configuration. Set these properties by clicking the up and down arrows. 3 Maximum Number of Peer-to-Peer Sends Maximum Number of Peer-to-Peer Receives
If you want to change the settings for an application running on the controller, you must build the application and perform a Download All.
84
Chapter 5
Using Send and Receive Function Blocks

A TriStation application must use a specific Send function block to send data of a certain type to a matching Receive function block in another TriStation application. Each Send function block has a parameter that identifies the Receive function block to which it sends data. Each Receive function block has a parameter that identifies the Send function block from which it receives data.
Send and Receive Function Blocks

The Send and Receive function blocks that you can include in a TriStation application have data types of BOOL, DINT, and REAL. The following function blocks are available:
Send Function Blocks TR_USEND_BOOL TR_USEND_DINT TR_USEND_REAL TR_USEND_BOOL_32 TR_USEND_DINT_32 TR_USEND_REAL_32 Receive Function Blocks TR_URCV_BOOL TR_URCV_DINT TR_URCV_REAL TR_URCV_BOOL_32 TR_URCV_DINT_32 TR_URCV_REAL_32
The _32 ending means that the function block can send 32 data values. Function block names that do not include the _32 ending can send 20 data values. All Send function blocksand all Receive function blockshave the same parameters, except for the data transfer parameters which are BOOL, DINT, or REAL. For detailed descriptions, see the TriStation Libraries Reference.
Sample Send and Receive Pair

This figure depicts a sample pair of Send and Receive function blocks. A Send function block in one TriStation application is sending input values from the field over a Peer-to-Peer network to a matching Receive function block in another TriStation application. The Recvid and Sendid parameters are used to cross-reference the Send and Receive function blocks. The Recvnode and Sendnode parameters are used to cross-reference the sending and receiving nodes (TriStation applications). For more information, see PEER_EX4_RCV_FBD (for receiving Node #3) on page 90.
Using Send and Receive Function Blocks
85
1 2
2 1
Figure 19
Sample Pair of Send and Receive Function Blocks in a Peer-to-Peer Application
86
Chapter 5
Restrictions on Data Transmission Speed

Tricon controllers with an NCM installed perform Peer-to-Peer communication at 10 megabits per second. Trident controllers and Tricon controllers with a TCM installed can perform Peerto-Peer communication at 10 or 100 megabits per second. Peer-to-Peer communication can be performed across the entire network at 100 megabits per second if your network satisfies one of the following conditions: includes only Tricon controllers with TCMs installed. includes only Trident controllers. includes only Tricon controllers with TCMs installed AND Trident controllers.
If your network includes a Tricon with an NCM and a Trident controller, you must choose either of the following solutions.
Solution Run the entire network at 10 megabits Description Data exchange among Triconex controllers can be effectively done at a rate of 10 megabits per second. Triconex suggests using the NET 1 port on both Trident and Tricon communication modules, because 10 megabits per second is the only speed available on the NCM NET 1 port. With this setup, NET 2 is available for faster communication with external devices on an Ethernet network. The data rate can be converted when messages are transferred from a Tricon controller with an NCM to a Trident controller. A typical method is to connect the Tricon and Trident controllers to a hub which can convert from 10 to 100 megabits. For Trident controllers, another method is to use MAU connections, which can convert from 10 to 100 megabits, to CM ports.
Convert messages from 10 to 100 megabits
Monitoring Peer-to-Peer Communication
87
Monitoring Peer-to-Peer Communication

TriStation provides function blocks for monitoring the status of Peer-to-Peer communication paths (routes between NCM or TCM modules on the network) and the status of NET 1 ports on the NCM or TCM. For detailed information, see the TriStation Libraries Reference.
Status of Communication Paths

For controllers with NCM modules installed, the Peer-to-Peer network can communicate over one or two paths, depending on whether each controller contains one or two NCM modules. If there are two paths (two NCM modules), then both are used simultaneously to exchange Peerto-Peer data. For controllers with TCM modules installed, the Peer-to-Peer network can communicate over one, two, three, or four paths, depending on the number of TCM modules installed. If there are four paths (four TCM modules), then all are used simultaneously to exchange Peer-to-Peer data. The failure of one path does not affect Peer-to-Peer communication. To monitor the paths, use the TR_PEER_STATUS function block in the TriStation application. Path status is updated every 30 seconds.
Status of NET 1 Ports

You can determine whether the NET 1 ports on an NCM or TCM are receiving Peer-to-Peer data by using the TR_PORT_STATUS function block in the TriStation application. This figure depicts the FBD representation of a TR_PORT_STATUS function block.
88
Chapter 5
Examples of Peer-to-Peer Applications

Triconex Peer-to-Peer function blocks are designed to transfer limited amounts of data between two applications. Therefore you should use these function blocks sparingly in your applications. Ideally, you should control the execution of each SEND function block in such a way that each SEND is initiated only when the acknowledgment for the last SEND is received and new data is available for sending. You can do this through effective use of the SENDFLG parameter in the SEND function block and the STATUS output of the SEND function block, as shown in Examples 3 and 4. The examples described below can be found in the Expeer.pt2 project included as part of the TriStation 1131 installation.
Example 1: Fast Send to One Triconex Node

This example shows how to send data as fast as possible from node #2 to node #3. Scan time in both controllers is set to 100 milliseconds. The example uses the following project elements: PEER_EX1_SEND_FBD (for sending node #2) PEER_EX1_RCV_FBD (for receiving node #3)
Example 2: Sending Data Every Second to One Node

This example shows how to send data every second from node #2 to node #3. Scan time in both controllers is set to 100 milliseconds. The example uses the following project elements: PEER_EX2_SEND_FBD (for sending node #2) PEER_EX2_RCV_FBD (for receiving node #3)
Example 3: Controlled Use of SEND/RECEIVE Function Blocks

This example shows how to use SEND/RECEIVE function blocks correctly, in a controlled way, so that a limited amount of important data can be transferred between two applications when new data is ready to be sent. This example uses the following project elements: PEER_EX3_SEND_FBD (for sending node #2) PEER_EX3_RCV_FBD (for receiving node #3)
Examples of Peer-to-Peer Applications
89
Example 4: Using SEND/RECEIVE Function Blocks for Safety-Critical Data

This example shows how to use SEND/RECEIVE function blocks for transferring a limited amount of safety-critical data between the two applications as fast as possible. It also shows how to measure the actual maximum time for transferring data from the sending node to the receiving node. Because this is safety-critical data, each controller must use two NCMs or TCMs and two Peerto-Peer networks. However, this is for availability reasons only, and is not necessary if you have already included in your safety logic that a loss of communications will cause a shutdown of the process under safety control.
Sending Node #1 Parameters:

Scan time (SS) = 150 milliseconds Number of aliased variables in bytes = 2000 Time to transfer alias data over the communication bus in milliseconds (TS) = (2000/20000) * 1000 = 100 milliseconds The sending controller has only one SEND function block in the application, meeting the requirement to have five or fewer SEND function blocks. The sendflag is on in the SEND function block so that, as soon as the last SEND is acknowledged by the receiving controller, the sending controller initiates another SEND.
Receiving Node #3 Parameters:

Scan time (SR) = 200 milliseconds Number of aliased variables in bytes = 5000 Time to transfer aliased data over the communication bus in milliseconds (TR) = (5000/20000) * 1000 = 250 milliseconds Process tolerance time = 4 seconds Estimated data transfer time = 2 * 150 + 2 * 250 = 800 milliseconds.
If the sending controller does not receive acknowledgment from the receiving controller in one second, it automatically retries the last TR_USEND message. Because of network collisions, communication bus loading, etc., the sending controller occasionally has to retry once to get the message to the receiving node. This is why the general rule for data transfer time is one to two seconds, even though the estimated time is 800 milliseconds. The receiving node has a network to measure the actual time so you can validate the assumed two-second maximum transfer time. Since the process-tolerance time of the receiving node is four seconds, the maximum time-out limit is set to two seconds (half the process-tolerance time). The receiving node should receive at least one data transfer within the maximum timeout limit. Using this criteria meets the basic requirement for using peer-to-peer communication to transfer safety-critical data.
90
Chapter 5
This example packs 32 BOOL values into a DWORD and sends the DWORD and a diagnostic variable to a receiving node as fast as possible by setting the sendflag parameter to 1 all the time. The diagnostic variable is incremented every time a new SEND is initiated. The receiving node checks the diagnostic variable to verify that it has changed from the previous value received. The receiving node also determines whether it has received at least one data transfer within the process-tolerance time. If not, the application takes appropriate action, such as using the last data received or using default data to make safety-critical decisions. This example uses the following project elements: PEER_EX4_SEND_FBD (for sending Node #1) PEER_EX4_RCV_FBD (for receiving Node #3)
6
Overview Physical Features Configuring Ports for Modbus in TriStation 92 93 97
Programming for Triconex Masters 106 Programming for Triconex Slaves 111 Sample Modbus Programs 118
92
Chapter 6
Overview
Modbus is an industry-standard master/slave communication protocol that is traditionally used for energy management, transfer line control, pipeline monitoring, and other industrial processes. A Tricon controller with a TCM can operate as a Modbus master or slave; a controller with an EICM can operate as a Modbus master, slave, or both. A DCS typically acts as the master, while the Tricon acts as a slave. The master can also be an operator workstation or other device that is programmed to support Modbus devices. The Tricon controller has serial ports on the EICM or TCM that provide options for communication with a Modbus devices. Each serial port can operate in a point-to-point configuration with a single Modbus device, or in a multi-point configuration with several Modbus devices connected to a serial link. For an example, see Configuration Options on page 93. The TCM also supports Modbus over TCP through the NET 1 or NET 2 Ethernet port. Each serial port on the EICM or TCM can be configured as a master or slave. Serial ports on the EICM can also be configured as a combination master/slave. The Ethernet ports on the TCM can be configured as a master or slave, with up to 32 Modbus masters or slaves per Tricon system. A Tricon serial port can act as a master, slave, or combination master/slave with these physical features: Point-to-point or multi-point network topology RS-232, RS-422, or RS-485 communication interface 2-wire (half duplex) or 4-wire (full duplex) cables Hardware handshake with or without signal delays Note Signal delays are not available on TCMs.
For an EICM or TCM port configured as a master, the associated TriStation application can use Modbus Read and Write function blocks to communicate with slave devices, including other Triconex controllers. Programs in external Modbus master devices can directly access point values in a Triconex controller if the points have aliases and if write access controls are correctly applied. A TriStation application normally uses alphanumeric names to identify Triconex points (program variables). Numeric identifiers called aliases must also be used to make the point values accessible to external Modbus devices. An alias has five digits that define its data type and hardware address in the controller. Function blocks allow you to monitor the communication status of each EICM serial port. The status information includes the number and kinds of messages received and sent and milliseconds since the last message was received. The sample programs described in this chapter are included on the TriStation CD. These programs show how to use the Modbus Read and Write function blocks for transmitting aliased data, how to set time-out and retry values for Modbus communication, and how to control the flow of data from slave to master. For detailed information, see Appendix E, Modbus Protocol
Physical Features
93
Physical Features
When connecting a Tricon EICM or TCM serial port to one or more Modbus devices, you can select from these physical features.
Feature Network Topology Option Point-to-point Multi-point RS-232 RS-422 RS-485 Cable Type 2-wire 4-wire Hardware Handshake Default Signal delay Use for Connection to one Modbus device Connection to multiple Modbus devices. One master with up to 32 slaves. Maximum speed across distances up to 50 ft (15 m) Distances up to 4,000 ft (1,220 m), point-to-point only Distances up to 4,000 ft (1,220 m) Half-duplex data transmission Full-duplex data transmission Devices that do not require signal delays Devices with slow throughput, other limitations (EICM only)
Communication Interface
Configuration Options
A Tricon TCM or EICM port can operate in a point-to-point connection with a single Modbus device, or in a multi-point serial link with several Modbus devices.
Point-to-Point Connection
This figure shows a point-to-point connection, which is a direct connection between devices.
Figure 20
Modbus Point-to-Point Connection
94
Chapter 6
Multi-Point Connection
This figure shows a multi-point connection, which allows connections between several devices.
Figure 21
Modbus Multi-Point Connection
Physical Media Rules

These rules apply to the communication interfaces and cables you can use with TCM or EICM serial ports: RS-232 can be used only for point-to-point connections across distances up to 50 feet (15 meters). At higher baud rates, the maximum recommended distance is reduced. RS-422 can be used only for point-to-point connections across distances up to 4,000 feet (1,220 meters) RS-485 can be used: for point-to-point connections or multi-point serial links with 2-wire or 4-wire cables across distances up to 4,000 feet (1,220 meters) on a multi-point serial link for one master with up to 32 slaves
Multi-Point Connection Considerations

This section includes considerations for using RS-422 multi-point connections, which are also referred to as RS-485 with more than two connections. Also included is information on how the wires are identified and used. You should ensure that the connection includes the following: Mandatory pull-up/pull-down resistors A signal ground reference wire (optional, but highly advised)
The RS-422 and RS-485 standards do not define a connector pin-out, but do define each differential twisted-pair wire as Wire A and Wire B. Some RS-422 and RS-485 suppliers rename these as Wire + and Wire -. This means you cannot always rely on the name to identify the polarity of the signal.
Physical Features
95
To determine the polarity:

1 2 For both the Triconex controller and DCS, ensure the send channel is on. On the Triconex controller side, measure the signal ground to SDA and SDB. The SDA will be less than 1 volt. The SDB will be greater than 2.5 volts. 3 On the DCS side, measure the send channel. If the channel is less than 1 volt, it is the A channel. If the channel is greater than 2.5 volts, it is the B channel. 4 Use the following tables to determine whether the polarity is typical or reversed. This table identifies a typical conversion with wires defined as A and B, or + and -:
Triconex SDA = Send Data A SDB = Send Data B RDA = Receive Data A RDB = Receive Data B = = = = Other Suppliers TX+ = Transmit Data, Positive Polarity TX- = Transmit Data, Negative Polarity RX+ = Transmit Data, Positive Polarity RX- = Transmit Data, Negative Polarity
This table identifies a reverse polarity conversion:

Triconex SDA = Send Data A SDB = Send Data B RDA = Receive Data A RDB = Receive Data B = = = = Other Suppliers TX- = Transmit Data, Negative Polarity TX+ = Transmit Data, Positive Polarity RX- = Transmit Data, Negative Polarity RX+ = Transmit Data, Positive Polarity
96
Chapter 6
Hardware Handshake Rules

Hardware handshake refers to signals transmitted back and forth between two stations to coordinate the timing of data transmission. These rules apply to the use of hardware handshake with Modbus devices: Generally, hardware handshake can be used with the RS-232 or RS-485 communication interface. With a 2-wire cable, you must use hardware handshake. For a point-to-point configuration, you should use hardware handshake only if the connected Modbus device requires it. For a multi-point configuration that uses 4-wire cables, typically the slaves use hardware handshake but the master does not.
Valid Modbus Configurations

A valid configuration of Modbus devices must use one of these combinations of physical features.
Valid Configuration Combination 1 Combination 2 Combination 3 Combination 4 Combination 5 Network Topology Point-to-Point Point-to-Point Point-to-Point Multi-Point Multi-Point Communication Interface RS-232 RS-485 RS-485 RS-485 RS-485 Physical Media Not applicable 2-wire 4-wire 2-wire 4-wire Hardware Handshake Optional Required Optional Required Optional
Configuring Ports for Modbus in TriStation
97

This section explains how to configure ports for Modbus communication on the EICM or TCM, which includes specifying EICM or TCM properties in TriStation. The properties you specify in TriStation must match the physical properties of the Modbus device it is connected to. This section includes: Note Setting EICM Switches for Serial Ports on page 97 Configuring EICM Serial Ports on page 98 Configuring TCM Serial Ports on page 101 Configuring TCM Modbus TCP Ports on page 103 Setting Signal Delays for Hardware Handshake (EICM Only) on page 105 The following procedures assume use of TriStation 1131 v4.1 or higher. If you are using another version of TriStation 1131, please refer to the documentation for the version you are using for detailed instructions on configuring the module ports for Modbus.
Setting EICM Switches for Serial Ports

This procedure explains how to specify the communication interface for each port, which determines whether the port uses RS-232 or RS-422/RS-485. This procedure should be performed before installing an EICM in the Tricon chassis. The factory default setting is all switches Off.
Procedure
1 Remove the EICM module, if needed. Figure 22 depicts the EICM module and switch block. 2 Set switches as needed. 3 To use RS-232, the switch must be set to Off. To use RS-422 or RS-485, the switch must be set to On.
Replace the EICM in its slot.
Figure 22
Using EICM Switches to Configure Port Communication Interfaces
98
Chapter 6
Configuring EICM Serial Ports

This procedure explains how to configure ports on a Tricon EICM for connection to an external device using Modbus protocol (master, slave, and master/slave) You can install an EICM module in either chassis 1 or the first expansion chassis.
Procedure
1 2 In TriStation, open your project and then expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the EICM slot, and then click Setup.
Specify these properties in the EICM Setup dialog box.

Property Port Selection Protocol Modbus Slave Address Action For Modbus communication, select ports 14 (left slot) or 69 (right slot). Select the specific Modbus protocol. Each serial port connected to a Modbus master device must have a separate Modbus slave address. Enter the number of the slave address, which can be 1247. Only available with Modbus slave and Modbus slave/master protocols. If the EICM serial port acts as a Modbus master, the slave address is specified in the Modbus Read and Write function blocks. See Programming for Triconex Masters on page 106. Baud Rate Select the rate, which must be the same as other slaves on the network. The default is 9600. The total rate for all four ports must be less than or equal to 57,600. Data Bits Set as needed; must be the same as other Modbus slaves. Modbus slave can use 7 or 8 bits. Modbus master and master/slave must use 8 bits.
99
Property Stop Bits Parity
Action Select either 1 Bit or 2 Bits to specify whether to send 1 or 2 bits to indicate that the transmission of a byte of data is complete. Must use the same setting as other Modbus slaves. Specifies whether to use parity checking, which is a way to detect data communication errors, on the transmitted data. Odd and Even parity counts the number of 1 bits in a one-byte data item then sets the parity bit (9th bit) to 0 or 1 to result in an Odd or Even total number of 1 bits. Mark and Space parity (also called high/low parity) set the parity bit to 1 or 0 regardless of the number of 1 bits in the data item. Settings include: Odd sets the parity bit to 0 or 1 to make the total number of 1 bits odd. (Default value) Even sets the parity bit to 0 or 1 to make the total number of 1 bits even. Mark sets the parity bit to 1 for each data item. Space sets the parity bit to 0 for each data item. None deletes the parity bit.
Handshake
Specifies whether to use signals to establish a valid connection. With hardware handshake, a separate wire sends a signal when the receiving device is ready to receive the signal, which ensures that a device transmits data only when the other device is ready to receive it. Switch settings determine whether handshaking is allowed. Select Hardware if the physical hardware is using any of these configurations: Any 2-wire configuration (required) A multi-point configuration that uses the RS-485 transceiver mode (required) A point-to-point configuration that uses an external modem with RS-232 transceiver mode (optional) The default is None. To delay the timing of Modbus data transmission, see Setting Signal Delays on a Tricon EICM on page 105.
100
Chapter 6
Property Modbus (Minimum and Maximum) Range
Action Identifies the range of five-digit numbers that can be assigned to a point. The leftmost digit identifies the data type and the other digits identify the hardware address in the controller. Set minimum between 0 and 32767; maximum between 1 and 32767. Honeywell DHP uses 0 to 9,999. The Modbus Range operates in conjunction with the Minimum and Maximum values on the Tricon EICM serial ports to scale values of REAL points. For more information, see How REAL Numbers are Scaled to Integers on page 114. For a listing of aliases, see Tricon Modbus Alias Ranges on page 228.
Click OK.
Configuring Ports for Modbus in TriStation 101
Configuring TCM Serial Ports

This procedure explains how to configure serial ports for Modbus communication on a Tricon TCM. Note The following procedure applies only to model 4351A and 4352A TCMs. If you have an older model 4351 or 4352 TCM installed in your system, see Appendix G, TCM Model 4351/4352 Configuration.
Procedure
1 2 3 In TriStation, open your project and then expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Serial Ports tab.

Property Port Selection Port Write Enabled Action Click the port to be configured. Ports can be configured only for a slot with an installed module. Available only if Modbus Slave (ASCII or RTU) is selected as the communication protocol. Select this check box if you want to allow Modbus writes to this slave port. The default is cleared (the port is read-only).
102
Chapter 6
Property Protocol
Action Select the communication protocol for the port: All ports can use Modbus Master, Modbus Slave ASCII, Modbus Slave RTU. Only port 1 can use GPS. This port is automatically configured for GPS when you enable time synchronization. Only port 4 can use TriStation.
Modbus Slave Address Baud Rate Data Bits Stop Bits Parity Transceiver Mode Handshake Termination Options FP Ordering Modbus (Minimum and Maximum) Range Master Logical Port
If you selected Modbus Slave RTU or ASCII, enter the number of the Modbus slave device. The default is 1. Enter the communication rate for the port. The default is 9600. Select 8 or 7 bits. The default is 8. Available only with Modbus Slave ASCII. Select 1 or 2 bits. The default is 1 bit. Select the type of parity for the port. The default is Odd. Select RS-485 or RS-232. The default is RS232. On port 4 when TriStation is selected as the protocol, RS-485 is not available. Select None or Hardware; the default is None. Select the type of termination used with cables. Only available with RS-485 Transceiver Mode. The default is None. Select the order to be used with floating point numbers. The default is Low 16 Bits First. Enter the minimum and maximum values to be used for the Modbus data range. The default minimum is 0. The default maximum is 32,767. Enter the port number that the TCM will use in Modbus Master functions to access the port. Only available for Modbus Master.
5 Note
Click OK. Even if port 4 is set to Not Configured (the default value), it can still be used to connect to the Tricon via TriStation. This is useful when you are unable to connect via a network connection.
Configuring TCM Modbus TCP Ports

This procedure explains how to configure Modbus TCP ports on a Tricon TCM, which enables Modbus communication through network ports. Note The following procedure applies only to model 4351A and 4352A TCMs. If you have an older model 4351 or 4352 TCM installed in your system, see Appendix G, TCM Model 4351/4352 Configuration.
Procedure
1 2 3 In TriStation, open your project, and then expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Modbus TCP tab.
4 5
Under Slot Selection, select the module (slot) you want to configure Modbus TCP ports for. Select a port and specify these properties.
Property Protocol Port Write Enabled Action Select the communication protocol for the port. Options include Modbus TCP Master and Modbus TCP Slave Net. Available only if Modbus TCP Slave is selected as the communication protocol. Select this check box if you want to allow Modbus writes to this slave port. The default is cleared (the port is read-only).
104
Chapter 6
Property Master Logical Port TCP Port Network IP Address
Action Enter the number of the Modbus Master node. Available only with Modbus TCP Master protocol. Enter the number for the TCP port. The default is 502. Click the network that the selected port is connected to. The default is NET 2. If the port uses Modbus Master protocol, enter the IP address of the slave node. If the port uses Modbus Slave protocol, enter either of these: To accept communication from any Modbus Master, leave the IP address as 0.0.0.0. To accept communication only from a defined Modbus Master, enter the specific master IP address.
FP Ordering Modbus (Minimum and Maximum) Range
Select the ordering to use for floating point numbers. The default is Low 16 Bits First. Enter the minimum and maximum for the Modbus data range. Available only with Modbus TCP Slave Net.
Click OK.
Setting Signal Delays for Hardware Handshake (EICM Only)

For Modbus devices that use hardware handshake, setting CTS and RTS signals can delay the timing of data transmissions, a method for ensuring that devices are ready to receive data. The RTS (Request to Send) signal opens and closes the data transmission channel. The RTS predelay setting specifies the number of milliseconds to wait before the data is transmitted. The CTS (Clear to Send) signal indicates the transmitting station that it is ready to receive data. The CTS Pre-delay setting specifies the number of milliseconds to keep the channel open after data is transmitted. The following is a sample timing figure.
Figure 23
Sample Signal Timing Delays for Modbus Communication
Setting Signal Delays on a Tricon EICM

Signal delays are set by using the MBWRITE function blocks in a program.
Procedure
1 2 3 Set the Handshake property to Hardware on the Tricon EICM Setup screen. Add an MBWRITE function block for each type of delay (CTS and RTS) you want to specify. Specify these parameters in the function block.
Parameter Alias Port Station D01 Action For CTS, enter 40001. For RTS, enter 40004. Enter the EICM port number. Enter the slave station address. Enter the delay in milliseconds; 0 to 10,000.
The settings can be from 0 to 10,000 milliseconds; the default is 0.
106
Chapter 6
Programming for Triconex Masters

If you configure a serial port on a Triconex controller as a Modbus master, the TriStation application can use Modbus Read and Write function blocks to communicate with slave devices, including other Triconex controllers. The following Read and Write function blocks are available.
MBREAD_BOOL MBREAD_DINT MBREAD_REAL MBREAD_REAL_TRD MBWRITE_BOOL MBWRITE_DINT MBWRITE_REAL MBWRITE_REAL_TRD
Read and Write function blocks of types BOOL and DINT can transmit 32 data values. Read and Write function blocks of type REAL can transmit 25 data values. Triconex controllers use BOOL, 32-bit DINT (double integer) and 32-bit REAL numbers, whereas traditional Modbus protocol supports only Booleans and 16-bit integers. For this reason, TriStation includes function blocks which convert REAL values to integers and integers to REAL values. The sections beginning on page 107 provide guidelines for use of these function blocks. For detailed information on function blocks, see the TriStation Libraries Reference. For examples, see Sample Modbus Programs on page 118.
Processing of Modbus Function Blocks

During each scan, a Triconex controller initiates up to five Modbus read or write operations for each Modbus master port. Each Modbus master port is limited to 10 outstanding requests for a Modbus operation. A Modbus operation might require up to six scans to complete. When a Modbus operation is completed, the controller initiates the next pending request for a Modbus operation. For example, with a single Modbus master port and a TriStation application that uses 12 MBREAD function blocks and no MBWRITE or MBCTRL function blocks, the controller initiates the first five Modbus reads during the first scan. During the second scan, the controller initiates the sixth through tenth Modbus reads. When a Modbus read is completed, the controller initiates the 11th Modbus read. When the next Modbus read is completed, the controller initiates the 12th Modbus read. As each Modbus read is completed, the controller initiates the next pending request for a Modbus read. For more information, see Appendix E, Modbus Protocol.
107
Function Blocks for Communicating with Non-Triconex Slaves

These function blocks can be used when a Triconex master interfaces with a non-Triconex slave device.
Data Type in Slave Boolean Integer Function Block in Triconex Master MBWRITE_BOOL MBREAD_BOOL MBREAD_DINT MBWRITE_DINT Although the DINT data type uses signed 32-bit integers, only the least significant 16 bits are transferred. Values should be limited to the range of zero through 32,767. REAL values are read from the slave as two 16-bit consecutive aliases and concatenated to form a 32-bit REAL value (see Example 2). 32-bit REAL values to be written to the slave are first split into two 16-bit values which are written to two consecutive aliases (see Example 1). Application Notes Values are True (1) and False (0).
Real
MBREAD_REAL_TRD MBWRITE_REAL_TRD
Figure 24
Modbus Function Block Examples Communicating with Non-Triconex Slaves
108
Chapter 6
Function Blocks for Communicating with Trident Slaves

These function blocks can be used when a Triconex master communicates with a Trident slave.
Data Type in Slave BOOL DINT Function Block in Triconex Master MBWRITE_BOOL MBREAD_BOOL MBREAD_DINT MBWRITE_DINT Although the DINT data type uses signed 32-bit integers, only the least significant 16 bits are transferred. Values should be limited to the range of zero through 32,767. Each REAL aliased variable in the Trident slave must have scaling disabled in the Min/Max screen. Application Notes Values are True (1) and False (0).
REAL
MBREAD_REAL_TRD MBWRITE_REAL_TRD
Function Blocks for Communicating with Tricon Slaves

These function blocks can be used when a Triconex master communicates with a Tricon slave.
Data Type in Slave BOOL DINT Function Block in Triconex Master MBWRITE_BOOL MBREAD_BOOL MBREAD_DINT MBWRITE_DINT Although the DINT data type uses signed 32-bit integers, only the least significant 16 bits are transferred. Values should be limited to the range of zero through 32,767. The SPECIAL parameter on each of these function blocks should be set to False. Application Notes Values are True (1) and False (0).
REAL
MBREAD_REAL MBWRITE_REAL
109
Sample Modbus Read Function Block

This figure shows a sample Modbus Read function block in a TriStation application that includes programming for serial port 1 (as indicated by the Port parameter). The function block is reading values from Slave Station 2 (as indicated by the Station parameter) through serial port 1 and storing the values in local variables.
32
Figure 25
Sample TriStation Modbus Read Function Block
110
Chapter 6
Sample Modbus Write Function Block

This figure shows a sample Modbus Write function block in a TriStation application that includes programming for serial port 1 (as indicated by the Port parameter). The function block is writing values to Slave Station 2 (as indicated by the Station parameter) through serial port 1.
Figure 26
Sample TriStation Modbus Write Function Block
Programming for Triconex Slaves
111

If you configure a serial port on the Tricon controller as a Modbus slave, aliases must be assigned to tagnames that will be accessed by the external Modbus master. Triconex controllers support BOOL, 32-bit DINT (double integer) and 32-bit REAL numbers, whereas traditional Modbus protocol supports only Booleans and 16-bit integers. This means that DINT and REAL values from a Triconex controller are transmitted as follows: For DINT tagnames in a Triconex slave, the Triconex controller transfers only the least significant 16 bits. For REAL tagnames in a Tricon slave, you specify whether to use a special alias, which maps a 32-bit REAL number to two 16-bit REAL integers, or to scale the REAL number to a 16-bit integer.
Assigning Alias Numbers to Tagnames

This procedure explains how to assign an alias number for input, output, and memory points.
Procedure
1 In TriStation, open your project and then open a tagname by doing either of these: 2 On the Tagname Declarations tree, double-click a tagname. Double-click a tagname on a logic sheet, and then click the Declaration button.
Click the Point Assignment tab.
112
Chapter 6
Specify these properties on the Point Assignment tab. Note Change all the defaults to user after the aliases have been established. If default is selected, the alias is selected automatically from the available ranges. If you decide to make additional changes to tagname properties later, and the available alias range has changed, the default alias selection can result in alias getting changed again.
Action For memory points, specify either Read Aliased, or Read/Write Aliased. (Input and output points can only be Read Aliased.) For aliased memory points, specify either User alias or Default alias. If User alias, enter a number within the range, and then click Apply. If the User alias number is valid, the default alias number is changed for the memory address. For input and output points, the physical address must be specified before an alias number can be assigned. The memory address is displayed once you click Apply. It cannot be changed. Select the check box to allow the point to be written to multiple times in a scan. The default is cleared.
Property Alias Type Alias Number
Physical Address Memory Address Enable Multiple Writes
Note
When you select Default alias as the alias number for memory point tagnames, these aliases can be automatically reassigned under certain circumstances. For example, if another tagname using the Default alias setting is deleted, the next time you build the application, TriStation will re-use the alias number of the deleted tagname. You can avoid this behavior by always using the User alias setting to define your own alias numbers and keep control of assigned aliases.
To set the alias number, click Apply. To cancel your changes and restore the original settings, click Restore before clicking Apply. Once you click Apply, you cannot revert to the original settings.
How Tricon Transmits REAL Values With Special Alias Numbers

This section explains how the Tricon controller transmits REAL values for tagnames by using special alias numbers which map one 32-bit REAL value into two 16-bit Modbus integers. One Modbus integer is mapped to the 16 most significant bits and the other Modbus integer is mapped to the 16 least significant bits in the REAL number. The Modbus master can also read and write values by using a scaled value in an alias number.
Reading REAL Values

Figure 27 shows a Modbus master reading a REAL value from two consecutive special aliases which correspond to a REAL alias. The Tricon controller splits the 32-bit REAL value into two 16-bit integers and places them in the special aliases to be read by the Modbus master.
113
Figure 27
Modbus Master Reading REAL Values from the Tricon
Writing REAL Values

Figure 28 shows a Modbus master writing a REAL value to the Tricon controller by transmitting two 16-bit integer values to two consecutive special aliases. The controller concatenates the two 16-bit integers to form a 32-bit REAL value.
Figure 28
Modbus Master Writing REAL Values to the Tricon
114
Chapter 6
Tricon Special Alias Numbers

This table lists the special alias numbers used for read and write operations with REAL tagnames. The Most and Least columns refer to the most significant and least significant bits.
Variable Type Aliases Most Input Real, Read Only 32001 32002 . . . 32120 Memory Real, Read Only 33001 33002 . . . 34000 Memory Real, Read/Write 41001 41002 . . . 42000 34001 34003 . . . 34239 35001 35003 . . . 36999 42001 42003 . . . 43999 Special Aliases Least 34002 34004 . . . 34240 35002 35004 . . . 37000 42002 42004 . . . 44000 . . . . . . . . . - or - or . . . - or - or - or . . . - or Most 44001 44003 . . . 44239 45001 45003 . . . 46999 Least 44002 44004 . . . 44240 45002 45004 . . . 47000
How REAL Numbers are Scaled to Integers

This section explains how 32-bit REAL scaled numbers are transmitted in Modbus protocol, which uses 16-bit integers. If a REAL value is scaled, these operations occur: When a Modbus master writes a 16-bit integer to a Triconex slave, the controller scales the integer to a 32-bit REAL number before using it in the TriStation application. When a Modbus master reads a 32-bit REAL variable from a Triconex slave, the controller scales the REAL variable to a 16-bit integer before transmitting it.
Scaled REAL numbers use a formula that includes the value of the tagname, the Minimum Value (Min Span) and Maximum Value (Max Span) for the tagname, and the Modbus minimum (Modbus Min) and maximum (Modbus Max) range set for the Modbus Range property.
115
Scaling Integer Values to REAL Values

Figure 29 shows how a Modbus master writes an integer value to the Triconex controller, where it is scaled to a REAL value.
Figure 29
How Triconex Controller Scales a Integer Value to a REAL Value
Scaling an integer to a REAL value uses this formula:

(MaxSpan MinSpan) Real Value = ------------------------------------------------------------------------ (Modbus Value Modbus Min) + Minspan (Modbus Max Modbus Min)
Figure 30 shows how scaling is done. Values above the Max Span or below the Min Span are clamped to the respective limit. The same principle applies to values outside the Modbus range.
Figure 30
Scaling an Integer Value to a REAL Value
To avoid division by zero, do not set Modbus Max equal to Modbus Minthe REAL value result is undefined. For the Trident or Tricon v9.6 and later controllers, the result is one of the floating point standard special numbers: NAN (not a number: -1.#IND) or infinity (1.#INF).
116
Chapter 6
Scaling REAL Values to Integer Values

Figure 31 shows how a Modbus master reads a REAL value which has been scaled to an integer.
Figure 31
How the Modbus Master Reads a REAL Value Scaled to an Integer Value
Scaling a REAL value to an integer value uses this formula:

(Modbus Max Modbus Min) Modbus Value = ------------------------------------------------------------------------ (Real Value MinSpan) + ModbusMin (Maxspan MinSpan)
Figure 32 shows how scaling is done. Values above the Max Span or below the Min Span are clamped to the respective limit. The same principle applies to values outside the Modbus range.
Figure 32
Scaling a REAL Value to an Integer Value
To avoid division by zero, do not set Max Span equal to Min Spanthe resulting Modbus value is undefined. Typically, for a Triconex controller, the result is -1.
117
Scaling REAL Values to Integers

This procedure explains how to scale a REAL value to an integer. Scaling may be needed to transmit numbers through Modbus protocol, which uses 16-bit integer numbers. Numbers are scaled by using minimum (Min Span) and maximum (Max Span) values for the point and minimum and maximum values for the Modbus Range.
Procedure
1 In TriStation, open your project and then open a tagname by doing either of these: 2 On the Tagname Declarations tree, double-click a tagname. Double-click a tagname on a logic sheet, and then click the Declaration button.
Click the Scaling tab.
Specify these properties on the Scaling tab.

Property Minimum Value (Min Span) Maximum Value (Max Span) Precision Disable Scaling Action Enter the minimum value to be used to scale the REAL number to an integer; must be less than the maximum value. The default is -32768.0. Enter the maximum value to be used to scale the REAL number to an integer; must be more than the minimum value. The default is 32767.0. Enter the number of decimal points to be used. The default is blank. To allow scaling of REAL numbers to integers, do not select this check box. Scaling cannot be disabled on the Tricon. The default is cleared.
Click Apply to save your changes.
118
Chapter 6
Sample Modbus Programs

Sample Modbus projects are included on the TriStation CD. These programs show how to use the Modbus Read and Write function blocks for transmitting aliased data, how to set time-out and retry values for Modbus communication, and how to control the flow of data from slave to master.
Reading and Writing DINT Data

These programs show how to read and write N values of type DINT from Port P, Station S, starting at specified aliases. MB_EX1_READ_DINT_FBD MB_EX4_WRITE_DINT_FBD
Reading and Writing REAL Data

These programs show how to read and write N values of type REAL from Port P, Station S, starting at specified aliases. MB_EX2_READ_REAL_FBD MB_EX5_WRITE_REAL
Reading and Writing BOOL Data

These programs show how to read and write N values of type BOOL from Port P, Station S, starting at specified aliases. MB_EX3_READ_BOOL_FBD MB_EX6_WRITE_BOOL
Setting Time-Out and Retry Values

The MB_EX7_CONTROL program shows how to use the MBCTRL function block to set timeout and retry values for the communications initiated by a Modbus master port.
Controlling the Flow of Data

The MB_EX8_FLOW_CONTROL program shows how to control the flow of data from a Modbus slave to a Modbus master.
Counting Values and Verifying Outputs

These programs count the number of errors, reads and writes, time-outs, and other values; and verify the consistency of outputs. MB_READ_TEST MB_WRITE_TEST
7
Overview 120 Tricon Write Access 121 Tagnames and Aliases 122 Time Synchronization 123 Printing from a Tricon Controller 137
120
Chapter 7
Overview
This chapter describes the time synchronization and printing features that can be used with Triconex controllers. Time Synchronization protocol allows networks of Tricon and Trident controllers to be synchronized with each other, and optionally, with external devices. In addition, a Tricon controller with an NCMG or TCM module can receive time adjustments from the Global Positioning System (GPS) by using the Trimble Acutime 2000 Synchronization Kit. A Tricon controller can send brief ASCII text messages to a printer that is connected to a parallel port on an EICM. The printer must be compatible with the Centronics interface provided by the EICM parallel port. Network printing protocol allows a Tricon controller to print messages by means of a print server connected to an Ethernet port on the TCM. The print server must be compatible with the JetDirect network printing protocol, and the printer must be compatible with the print server. An Ethernet hub might also be needed. For both types of printing, a TriStation application must include print function blocks to send messages to a printer.
Tricon Write Access
121
Tricon Write Access

Write access for external devices can be allowed or restricted for memory and output points by using keyswitch settings, configuration settings, and program logic in a TriStation application. External devices cannot write to input points but can read input, memory, and output points if allowed. For procedures on allowing and restricting access, see the TriStation Developers Guide. The following types of read and write access are possible: Input, output, and memory points can be read by any external device that can communicate with a Tricon controller. Write access to input points is not allowed from any external device. Write access to an output or memory point is allowed or restricted based on the system, communication, application, and point settings.
This table describes write access to Tricon points from external devices.
Property or Feature Tricon keyswitch Description A system setting that determines write access to output and memory points unless overruled by the GATENB function block in the application. Restricts write access when set to the Run position. Allows write access when set to the Remote or Program position. GATENB A Tricon function block that programmatically allows write access to a specified range of aliased memory points when the keyswitch is in the Run position. A Tricon function block that programmatically restricts remote write access for all ranges of aliased memory points that were previously enabled by GATENB. A system setting on the Operating Parameters screen that determines write access to output points. When selected, external devices cannot write to output points, no matter what other settings are made. A Tricon ACM and NCM module setting that determines whether network devices using DDE, OPC, or TSAA communication have write access to output points and read/write aliased memory points. For Tricon ACM, the default it Read. For Tricon NCM, the default is Read/Write. The Tricon TCM, EICM, HIM, and SMM modules do not have this property. Prohibit Writes A Tricon SMM module setting that determines whether Honeywell devices have write access to output points and read/write aliased memory points. The default is cleared, which means write access is allowed. A tagname setting that determines whether the output and memory point is assigned a Read or Read/Write alias number. For output points, all alias numbers are Read/Write. For memory points, alias numbers can be Read or Read/Write.
GATDIS
Disable Remote Changes to Outputs Privilege
Point Assignment
122
Chapter 7
Tagnames and Aliases

This section describes tagnames, which is the word commonly used when referring to input points (sensors) and output points (final elements). In TriStation 1131, tagnames are references to physical tagnames (labels) on the connected field devices or to memory points which are locations in the controller memory. In IEC terminology, tagnames are called global variables. For Modbus or DDE communication, tagnames must be assigned an alias number that allows read or read/write access. An alias number is a five-digit identifier which defines the data type and location of a point in the controller memory. See Assigning Alias Numbers to Tagnames on page 111. For Peer-to-Peer, OPC, or TSAA applications, tagnames can be accessed by the tagname. For more information about tagnames and aliases, see the TriStation Developers Guide.
Protocol or Application Modbus Master Modbus Slave Peer-to-Peer (Triconex) OPC Server, OPC Data Manager, and OPC Redundancy Broker DDE Server User-Written TSAA Application Access by Tagname Access by Alias
System Aliases for Tricon Status

TriStation includes predefined system aliases which external devices can read to obtain Tricon status information. The system aliases provide information about the Tricon chassis, slots, Main Processors, communication modules, and system performance. For more information, see Appendix F, Tricon System Aliases.
Time Synchronization
123
If you have multiple Triconex controllers on an Ethernet network, you can synchronize their time with: The master node (the controller with the lowest node number) An external device, such as an OPC client, that writes time values to a TriStation application A Global Positioning System (GPS) A combination of the master node and an external device or a GPS An SNTP server over NET 1 or NET 2 (with TCM only)
These sections provide more information about these strategies and instructions for setting the Triconex controller clock and setting time synchronization properties on the communication modules.
Master Node in a Network

In a network of Triconex controllers, the master node determines the time for all controllers that are synchronized with it. The master node is the controller with the lowest node number. For example, in a network of five controllers which have node numbers 1, 2, 3, 4, and 5, node 1 is the master node. If node 1 goes down, node 2 becomes the master node. When node 1 comes back online, it again becomes the master node. In a typical Triconex network, the controllers are synchronized with the master node within plus or minus 25 milliseconds. When a controller is synchronized with the master node, it rejects time adjustment attempts from all other sources. You must use Ethernet ports on ACM, NCM, or TCM modules to synchronize Tricon controllers in a network with the master node. For instructions, see Configuring Time Synchronization Properties on the ACM, NCM, or NCMG on page 127 or Using a Tricon TCM to Synchronize Time on page 131. If you plan to synchronize ACM modules with the master node, contact Triconex Technical Support for assistance.
CAUTION
In a network of Triconex controllers, all controllers with low node numbers should be configured for time synchronization. If a Triconex controller becomes the master node but is not configured for time synchronization, none of the controllers in the network can be synchronized.
124
Chapter 7
Master Node in a Peer-to-Peer Network

In a Peer-to-Peer network of Triconex controllers, the master node determines the time for all controllers that are synchronized with it. Node status is broadcast every 10 seconds; a node is considered active if a status message has been received the node within the last 30 seconds Up to 31 nodes can be present in a Peer-to-Peer network. The master node is the controller with the lowest node number. For example, in a network of five controllers which have node numbers 1, 2, 3, 4, and 5, node 1 is the master node. If node 1 goes down, node 2 becomes the master node. When node 1 comes back online, it again becomes the master node. In a typical Triconex Peer-to-Peer network, the controllers are synchronized with the master node within plus or minus 25 milliseconds. Time synchronization in a Peer-to-Peer network is performed via the UDP/IP protocol (NET 1 or NET 2) or DLC (NET 1 only) on TCM. GPS time synchronization can also be used in a Peer-to-Peer network, so that all controllers on the network are synchronized with a GPS instead of the master node. You can use the NET 1 or NET 2 ports on the TCM to synchronize Tricon controllers in a Peerto-Peer network. For instructions, see Using a Tricon TCM to Synchronize Time on page 131.
Time Adjustments from External Devices

A Triconex controller can receive time adjustments from external devices such as a DCS or an OPC client. When the OPC Server application is used, the OPC client can adjust the Triconex clock using the Device Clock tagname which is derived from Triconex system status information in the OPC Server Configuration. For more information, see the users manual for the OPC client application you are using. The Foxboro DCS is the only external device that can send time adjustments to the Tricon controller through the ACM. This is done through the NET 2 port on the ACM with external DDE server. For instructions, see the ACM Users Guide. On the TCM, time adjustments are done through the UDP/IP protocol (NET 1 or NET 2) or DLC protocol (NET 1 only). On the NCM, time adjustments are done through NET 1. Another way for an external device to adjust the Triconex controller clock is to write aliased data to the TIMESET or TIMEADJ function blocks in the TriStation application. This can be done though an Ethernet port or a serial port. If you need assistance with the specialized programming that is required, please contact Triconex Technical Support. To allow an external device to adjust the Triconex clock, you must configure an ACM, NCM, or TCM for time synchronization, and you must configure the TriStation application to allow write access. For instructions, see these sections: Configuring Time Synchronization Properties on the ACM, NCM, or NCMG on page 127 Using a Tricon TCM to Synchronize Time on page 131 Tricon Write Access on page 121
125
GPS Time Adjustments

A Tricon controller with a TCM or NCMG (for GPS Interface) can receive time adjustments from the Global Positioning System (GPS) by using the Trimble Acutime 2000 Synchronization Kit. This kit is available from Triconex or Trimble. To use the kit, you must connect it to a serial port on the TCM or NCMG for communication. In the TriStation project, you must configure the TCM or NCMG for GPS time synchronization. For instructions on installing the Acutime 2000 kit, see the Acutime 2000 Synchronization Kit User Guide. For additional information about the Acutime 2000 kit, go to www.trimble.com. When a TCM or NCMG is connected to an Acutime 2000 kit, the Tricon clock is adjusted to within 5 milliseconds of the GPS time. Since the GPS time uses the universal GMT time zone, time adjustments in the Tricon only use the minutes, seconds, and milliseconds portion of the GPS time, and assume that the local time zone is correctly indicating the current Tricon time. Local time zones vary by one-hour or half-hour increments. For example, if the current Tricon time is 14:25 and the GPS time received is 17:58, Tricon time is adjusted to 14:28. Therefore, in order to assure correct times when using GPS time adjustment, it is essential that the Tricon clock be set to within 10 minutes of the correct local time. For instructions, see Setting the Controller Clock on page 127.
Redundant Configuration
The GPS feature can be used in a redundant configuration which requires two TCM or NCMG modules and two Acutime 2000 Synchronization Kits. Typically, the left (primary) TCM or NCMG adjusts the time. The right (redundant) TCM or NCMG begins to adjust the time if the left TCM or NCMG detects a problem with its Acutime kit or if communication with the left module fails. Several types of faults can cause the Tricon to switch control to the redundant TCM or NCMG module. For example, each TCM or NCMG module requests an event timestamp from the Acutime kit every 10 seconds. If the event is not received within 5 seconds, the Tricon assumes there is a failure in the TCM, NCMG or the Acutime kit and switches control to the redundant TCM or NCMG module. For more information, see the Acutime 2000 Synchronization Kit User Guide.
126
Chapter 7
Figure 33
TCM/NCMG GPS Configuration Using Trimble Acutime 2000 Synchronization Kit
Combination Schemes
In a typical configuration, Triconex controllers on a network are synchronized with the master node. In addition, the master node can accept time adjustments from an external device so that the external time prevails for all controllers on the network. Examples of external time sources are an OPC client and a GPS.
Guidelines for Networks

These guidelines apply to Triconex controllers in a network whose time is synchronized with an external device: Every controller to be synchronized must have its Ethernet port configured for time synchronization, including the master node. If a controller is synchronized with the master node, it rejects time adjustment attempts from all other sources. In a redundant network of Triconex controllers that each have two NCM or TCM modules installed, you can implement redundant time synchronization by selecting the time synchronization property for both NCM or TCM modules in TriStation. In a network of Triconex controllers, all controllers with low node numbers should be configured for time synchronization. If a controller becomes the master node but is not configured, none of the controllers can be synchronized.
CAUTION
127
Setting the Controller Clock

This procedure explains how to set the Triconex controller clock to the correct local time, which is important if you are using time synchronization strategy. When an application is downloaded and run, the controller automatically sets the clock to the PC time. You can reset the clock at any time while the application is running, without having to download again. The need for accuracy depends on the application.
Procedure
1 2 3 4 5 6 On the TriStation PC, right-click the time icon in the message bar or open the Date/Time dialog box from the Control Panel. Ensure the PC is set to the correct local time. In TriStation, open the TriStation project that is running in the controller. On the Configuration tree, double-click the Controller Panel. On the Commands menu, click Connect, and then click Set Calendar Clock. Click Yes when asked whether to set the calendar clock to the current configuration. If the node is currently synched to a master node, the set time will be rejected. The Triconex clock is now set to the TriStation PC time, that is, to the correct local time. Use the Diagnostic Panel to verify the time adjustment.
Configuring Time Synchronization Properties on the ACM, NCM, or NCMG

This procedure explains how to configure Triconex controllers in a network for time synchronization with the master node or an external device. To do so, you can use the NET 2 port on the ACM; use the NET 1 port on the NCM or NCMG.
Configuring Time Synchronization on an ACM

1 2 In TriStation, open your project, and then expand the Configuration tree, double-click Configuration, and expand Hardware Allocation. Double-click the ACM slot, and then click Setup.
128
Chapter 7
Specify these properties on the ACM Setup screen.

Property Privilege Time Synchronization Action For synchronization on NET 2, specify Read/Write. The default is Read. Select On NET 1... to allow time synchronization with a Foxboro I/A DCS. Select On NET 2... to enable time synchronization with the Tricon Master node (controller).
Click OK.
129
Configuring Time Synchronization on an NCM

1 2 In TriStation, open your project and then expand the Configuration tree, double-click Configuration, and expand Hardware Allocation. Double-click the NCM slot, and then click Setup.
3 4
Select the On NET 1 enable time synchronization with Tricon Master Node check box. Click OK.
Configuring Time Synchronization on an NCMG

1 2 In TriStation, open your project and then expand the Configuration tree, double-click Configuration, and expand Hardware Allocation. Double-click the NCMG slot, and then click Setup.
130
Chapter 7
Specify these properties on the NCM Setup screen.

Property Global Positioning System Installed Action Select this check box to enable time synchronization through the GPS. If selected, other controllers can also be synchronized to the Tricon master controller. Time Synchronization For a network of Triconex controllers, select the On NET 1 enable time synchronization with the Tricon Master Node check box.
Click OK.
131
Using a Tricon TCM to Synchronize Time

The information in this section explains how to enable time synchronization on a TCM. Time synchronization can be enabled using the following protocols: GPS SNTP Triconex Time Synchronization via DLC (NET 1 only) or UDP/IP (NET 1 or NET 2) on a Peer-to-Peer network
In a redundant network of Triconex controllers that each have two TCMs installed, you can implement redundant time synchronization by configuring time synchronization for both TCM modules (both left and right slots). Time synchronization can be enabled only for a single logical slot. If the TCM is installed in the COM slot, you configure time synchronization only for the left slot (there is no redundancy when installed in the COM slot). Note The following procedures apply only to model 4351A and 4352A TCMs. If you have an older model 4351 or 4352 TCM installed in your system, please go to Appendix G, TCM Model 4351/4352 Configuration.
Topics include: Configuring GPS Time Synchronization on the TCM on page 131 Configuring SNTP Time Synchronization on the TCM on page 133 Configuring Triconex Time Synchronization on the TCM on page 135
Configuring GPS Time Synchronization on the TCM

This procedure explains how to configure a TCM to enable time synchronization through the Global Positioning System (GPS) by using the Trimble Acutime 2000 Synchronization Kit.
CAUTION
To ensure the accuracy of GPS time adjustments, the Tricon clock must be set to within 10 minutes of the correct local time.
If the TCM is in a Peer-to-Peer network, it can also be used as the master node for time synchronization of other controllers on the network. In this configuration, the master node TCM synchronizes time with the GPS, and any slave nodes on the Peer-to-Peer network synchronize their time with the master TCM. In this way, all nodes on the Peer-to-Peer network are synchronized with GPS time. If the TCM is acting as a slave node on a Peer-to-Peer network, it cannot be configured for GPS time synchronization. Slave nodes synchronize their time only to the master node on the Peerto-Peer network, and reject all other time change requests. GPS time synchronization uses Serial Port 1 on the TCM.
132
Chapter 7
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Time Sync tab.
4 5
Under Slot Selection, click Left Slot. You must configure the module in the left slot first. Under Time Synchronization Configuration, select GPS. If you previously configured Port 1 to use a Modbus protocol, selecting GPS will reset Port 1 to use the GPS protocol.
(Optional) If you have a redundant TCM installed in the right slot, under Slot Selection, click Right Slot, and then select GPS Redundant. Note The module in the right slot can be configured only if it has been installed and if the module in the left slot has already been configured for GPS time synchronization.
Click OK to save your changes.
Enabling the TCM as a Master Node for Triconex Time Synchronization (Optional)
If you also want the TCM to be able to act as a master node for time sychronization of other controllers on a Peer-to-Peer network (using Triconex Time Synchronization) do the following: 1 2 In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box.
133
Configuring SNTP Time Synchronization on the TCM

This procedure explains how to configure a TCM time synchronization to an SNTP server. If the TCM is in a Peer-to-Peer network, it can also be used as the master node for time synchronization of other controllers on the network. In this configuration, the master node TCM synchronizes time with the SNTP server, and any slave nodes on the Peer-to-Peer network synchronize their time with the master TCM. In this way, all nodes on the Peer-to-Peer network are synchronized with SNTP time. If the TCM is acting as a slave node on a Peer-to-Peer network, it cannot be configured for SNTP time synchronization. Slave nodes synchronize their time only to the master node on the Peerto-Peer network, and reject all other time change requests.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Time Sync tab.
4 5
Under Slot Selection, click Left Slot. You must configure the module in the left slot first. Select these properties.
Property Time Synchronization Configuration SNTP Master Network SNTP Master IP Address Action Select SNTP. The default is None. Click the network the SNTP server is located on. Enter the IP address of the SNTP server to synchronize time with.
134
Chapter 7
(Optional) If you have a redundant TCM installed in the right slot, under Slot Selection, click Right Slot, and then select these properties.
Property Time Synchronization Configuration SNTP Master Network SNTP Master IP Address Action Select SNTP Redundant. Click the network the SNTP server is located on. This can be different than the master network selected for the left slot. Enter the IP address of the SNTP server to synchronize time with.
Note
The module in the right slot can be configured only if it has been installed and if the module in the left slot has already been configured for SNTP time synchronization.
If you also want the TCM to be able to act as a master node for time sychronization of other controllers on a Peer-to-Peer network (using Triconex Time Synchronization) do the following: 1 2 In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box.
135
Configuring Triconex Time Synchronization on the TCM

In a Peer-to-Peer network, Triconex Time Synchronization can be used to synchronize time across controllers on a network. The controller with the lowest node number serves as the master node. The master node can also synchronize its time with a GPS or an SNTP server. In this configuration, the master node synchronizes time with the GPS, and any slave nodes on the Peer-to-Peer network synchronize their time with the master node. In this way, all nodes on the Peer-to-Peer network are synchronized with GPS or SNTP time. Note Currently, when a Trident controller is on a Peer-to-Peer network using Triconex Time Synchronization, with a Tricon TCM acting as a master node, the Trident will not correctly synchronize its time to the master node.
Configuring a Master Node

This procedure describes how to configure the TCM as a master node on the Peer-to-Peer network when GPS or SNTP time synchronization is not being used. If you want the master node to synchronize to a GPS or SNTP server, use the procedures in the these sections: Configuring GPS Time Synchronization on the TCM on page 131 Configuring SNTP Time Synchronization on the TCM on page 133
Procedure
1 2 3 4 5 6 7 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Time Sync tab. Under Time Synchronization Configuration, select None. Click OK to save your changes. In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box. This allows the controller to participate as a master node in time synchronization across the Peer-to-Peer network.
Configuring a Slave Node

This procedure describes how to configure the TCM as a slave node on the Peer-to-Peer network.
Procedure
1 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation.
136
Chapter 7
2 3
Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Time Sync tab.
4 5
Under Slot Selection, click Left Slot. You must configure the module in the left slot first. Specify these properties.
Property Time Synchronization Configuration Peer-to-Peer Master Network Action Select Peer-to-Peer. The default is None. Click the network you want to enable Triconex Time Synchronization for. The default is NET 2.This property applies to the modules installed in both the left and right slots simultaneously.
Note 6 7 8
If you have a redundant TCM installed in the right slot, Time Synchronization Configuration is automatically set to Peer-to-Peer and cannot be changed.
Click OK to save your changes. In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box. This allows the controller to participateas a master node or a slave nodein time synchronization across the Peer-to-Peer network.
Printing from a Tricon Controller 137
Printing from a Tricon Controller

A Tricon controller can print brief ASCII text messages if a communication port is connected to a printer and the TriStation application includes standard print function blocks. Print messages are typically used for alarms, status, and maintenance. A sample alarm message might include the name of an analog input point, its time stamp and value, and a statement that the value is out of range. If the Tricon system includes numerous controllers or is connected to a DCS, alarms are typically displayed on an operator workstation. To print from a Tricon controller with a TCM, you must connect a TCM Ethernet port to a print server that is connected to a printer, configure these devices in the TriStation project, and use print function blocks in the TriStation application. To print from a Tricon controller with an EICM, you must connect an EICM parallel port to a Centronics-compatible printer, configure the port in the TriStation project, and use print function blocks in the TriStation application. Topics include: Effect of Printing on Scan Time on page 137 Devices for Tricon Printing on page 138 Installing Printer Devices on page 138 Connecting a Tricon EICM Port to a Printer on page 139 Configuring a Tricon EICM Port for Printing on page 140 Connecting a TCM to Printing Devices on page 141 Connecting a TCM to Printing Devices Using a Hub on page 142 Configuring a Tricon TCM Printer Port for Printing on page 143 About Function Blocks for Printing on page 144
Effect of Printing on Scan Time

Each time a message is printed, the print function blocks in the TriStation application are executed and the scan time increases. Typically, the print function blocks are subject to conditional execution, which means they are not executed every scan. When you set the scan time in TriStation, make sure it includes the execution time for all conditional statements in the application. If the scan time is not long enough, the execution of all conditional statements (when the conditions are True) could result in scan-time overruns. You can minimize this problem by limiting the amount of printer output. An alternative is to use a PC event logger such as the Triconex SOE Recorder. For more information, see the SOE Recorder Users Guide.
138
Chapter 7
Devices for Tricon Printing

The devices required to print from a Tricon depend on the module you are connecting to the printer.
Printing with an EICM

You must use a Centronics-compatible printer with a Tricon controller with an EICM installed. The printer can be connected using a standard PC printer cable. The maximum cable length is 15 to 20 feet (5 to 6 meters), depending on the quality of the cable. For pin-out information, see the Tricon Planning and Installation Guide.
Printing with a TCM

At a minimum, the printing devices you can use with a Tricon controller with a TCM installed are an HP JetDirect-compatible print server and a line printer for ASCII text. You can also use a router or a hub.
Print Server and Cables

A print server that is connected to a Tricon TCM must use the HP JetDirect print protocol and operate at speeds of 10 or 100 megabits per second. Standard communication cables are suitable for this connection. You can purchase communication cables from other manufacturers. You must purchase print servers elsewhere because Triconex does not supply them. Black-box cables and HewlettPackard print servers are examples of dependable network printing devices. Triconex has tested these Hewlett-Packard print servers and can recommend them. HP JetDirect Ex Plus HP JetDirect 500X Series, model J3265A
Printers
You must select a printer that is compatible with your print server. The TCM prints ASCII text only, which does not include formatting or graphics, so a Centronics-compatible printer is adequate. Laser printers are also suitable.
Installing Printer Devices

Most printers and print servers require configuration with an install program on a workstation or other device. For each device, follow the instructions provided by the manufacturer, and run the diagnostic routine if one is included with the package. To print from a Triconex controller, the printer driver that comes with the printer package is not needed. The TriStation project must identify the EICM parallel port to which the printer cable is connected, or, if using a TCM, the target printer, and the print server, using the TCM Setup dialog box, as explained in the following sections.
Connecting a Tricon EICM Port to a Printer

This procedure explains how to set up a Centronics-compatible printer and connect it directly to a Tricon EICM parallel port. You can use a standard PC printer cable with a maximum cable length of 5 to 6 meters (15 to 20 feet), depending on the quality of the cable
Procedure
1 2 3 If the printer package has an installation program, copy the program to the TriStation PC. Follow the instructions, and run the diagnostic routine, if available. You do not need the printer driver that may have come with the package. Connect one end of the cable to the printer, and connect the other end to port 5 or 10 on the EICM. (Other EICM ports cannot be used for printing.)
Figure 34
Connecting an EICM to a Centronics-Compatible Printer
Go to the next section to configure the EICM port for printing.
140
Chapter 7
Configuring a Tricon EICM Port for Printing

This procedure explains how to configure a Tricon EICM port that is connected to a Centronicscompatible printer.
Procedure
1 2 In TriStation, open your project, expand the Controller tree, and double-click Configuration. On the Configuration tree under Hardware Allocation, double-click EICM, and then click Setup.
Specify these properties on the EICM Setup screen.

Property Port Selection Protocol Rows Columns Action Select Port 5 or Port 10. Other ports cannot be used for printing. Select Printer from the Protocol list. Enter the number of lines (rows) to be displayed on a page. Enter the number of characters per line.
Click OK.
Connecting a TCM to Printing Devices

This procedure explains how to directly connect a TCM to an HP JetDirect-compatible print server and printer. You can use standard communication cables for these connections.
Procedure
1 2 3 4 If the print server and printer packages have installation programs, install them on the TriStation PC. Follow the instructions, and run the diagnostic routines if available. You do not need the printer drivers that came with the packages. Record the IP address of the print server. You will need the IP address when configuring the TCM printer. Connect the printer to the print server, and connect the print server to a TCM Ethernet port (NET 1 or NET 2).
T M M C M PP P M ABC 1
Figure 35
Connecting a Tricon TCM to a Printer and Print Server
142
Chapter 7
Connecting a TCM to Printing Devices Using a Hub

This procedure explains how to connect a TCM to an HP JetDirect-compatible print server and printer by using a hub. You can use standard communication cables for these connections. You do not need to install the printer drivers that may have come with the print server and printer packages.
Procedure
1 2 3 4 If the print server and printer packages have installation programs, install them on the TriStation PC. Follow the instructions that came with the packages, and run the diagnostic routines, if available. Record the IP address of the print server. You will need the IP address when configuring the TCM printer. Connect the printer to the print server, and connect the print server to a hub. Connect the hub to a TCM Ethernet port (NET 1 or NET 2).
T M M M C PP P M ABC 1
Figure 36
Connecting the Tricon TCM to a Printer Server and Printer Using a Hub
Configuring a Tricon TCM Printer Port for Printing

This procedure explains how to configure a Tricon TCM port that is connected to a Centronicscompatible printer. You do not need the printer driver that may have come with the printer package. Note The following procedure applies only to model 4351A and 4352A TCMs. If you have an older model 4351 or 4352 TCM installed in your system, see Appendix G, TCM Model 4351/4352 Configuration.
Procedure
1 2 3 In TriStation, open your project, expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The Enhanced TCM Setup dialog box appears. Click the Printer tab.
Specify these properties for the module installed in the Left Slot.
Property Printer Number Line Width TCP Port Action Enter the number for the printer; can only be 5 or 10. The default is 0, meaning a printer is not configured. Enter the number of characters to be printed on a line. The default is 80 characters. Enter the number of the TCP port for the print server. The default is 9100 for an HP printer.
144
Chapter 7
Property Network IP Address
Action Click the network that the print server is connected to. The default is NET 2. Enter the IP address of the print server.
5 6
If a module is also installed in the Right Slot, repeat step 4 for that module. Click OK.
About Function Blocks for Printing

A TriStation application must use print function blocks to send messages to a printer. Each print function block has a PRINTER parameter which specifies the port number where the printer cable is connected. For a Tricon EICM or TCM port, the PRINTER parameter must be 5 for a left EICM or TCM port, or 10 for a right EICM or TCM port. (Other EICM or TCM ports cannot be used for printing.) The PRINTER parameter must be the same number as is defined in TriStation. Each time a message is printed, the print function blocks in the TriStation application are executed and the scan time increases This table lists the print function blocks in the TriconLibrary.
Print Function Block PRINT_BOOL PRINT_CDT PRINT_CRLF PRINT_CTOD PRINT_DINT PRINT_REAL PRINT_STRING PRINTR_FLUSH Purpose Prints a three-character field containing either Off or On. Prints the current date and time. Prints a new line (carriage return and line feed). Prints the current time of day. Prints a DINT value. Prints a REAL value. Prints a string of text. Clears the print buffer.
A
TCM Capabilities
TCM Operation 146 Physical Description 148
146
Appendix A
TCM Capabilities
TCM Operation
The TCM (Tricon Communication Module) is an optional module for the Tricon controller which supports multiple message protocols and physical media types. Ports on the TCM can communicate with TriStation, other Tricon or Trident controllers, Ethernet devices, and Modbus master and slave devices. The Tricon controller supports two slots of TCMs, which means there can be a maximum of four TCMs in a system. The TCMs operate independently. Each TCM can be connected to a separate network, or they can be used in a redundant configuration.
Message Handling
This figure depicts how message handling works. The TCM ports communicate with the three MP modules by means of the Comm Bus. A message received by a TCM port is passed to all three MP modules over the Comm Bus. The TriBus votes on the message before sending it to the MP modules for processing, and sends the response back to the Comm Bus after processing is complete. The Comm Bus then forwards the response to the TCM port.
Figure 37
TCM Message Handling
The TCM and MP modules handle message types as follows.
TCM Operation
147
TriStation, Peer-to-Peer, and Time Synchronization Messages

1 2 3 Receives the message and transmits it to the MP modules over the Comm Bus. Votes the message request with other MP modules over TriBus. Receives the message from the Comm Bus, processes the message and transmits a response.
Modbus and TSAA Read Queries

1 2 3 Receives the read query. Gets the requested alias from the Comm Bus voted data pool. Transmits the response.
Modbus and TSAA Write Commands

1 2 3 Receives the write request and transmits it to the MP modules over the Comm Bus. Votes the write request with the other MP modules over TriBus. Receives the message from the Comm Bus, processes the message, and transmits a write confirmation response.
Typical Message Response Time

Because most messages (excluding Modbus and TSAA read queries) require TriBus voting, typical message response times require three or more scans to complete.
148
Appendix A
TCM Capabilities
Physical Description
There are two types of TCMs: Copper (model 4351, 4351A, 4353) Fiber (model 4352, 4352A, 4354).
PASS FAULT ACTIVE
The Copper TCM uses RJ-45 network ports; the Fiber TCM uses multi-mode fiber-optic network ports. Note Model 4351, 4351A, 4352, 4352A, 4353, and 4354 TCMs cannot be mixed in the same logical slot. Additionally, model 4351A/4352A TCMs and 4351/4352 TCMs cannot be mixed in the same system, even if they are installed in different chassis
FIRM
NET 1 LINK
Net 1Copper (4351, 4351A, 4353) or Fiber (4352, 4352A, 4354)
TX RX
NET 2 LINK
Net 2Copper (4351, 4351A, 4353) or Fiber (4352, 4352A, 4354)
TX RX
The TCM includes these ports: Four RS-232/RS-485 serial ports, each of which are TriStation-configurable for Modbus master or slave, Trimble GPS, and TriStation Two 10/100 Mbps Ethernet ports (model 4351, 4351A, 4353) or two 10/100 Mbps fiber-optic MTRJ Ethernet ports (model 4352, 4352A, 4354) One RS-232 debug port (for Triconex use only)
SERIAL 1 TX RX
Serial Port #1 for GPS or Modbus interface
SERIAL 2 TX RX
Serial Port #2 for Modbus interface
SERIAL 3 TX RX
Serial Port #3 for Modbus interface
The TCM front panel also includes status and communication indicators. For information about the communication indicators, see TCM Communication Indicators on page 152. For information about the other indicators, see the Tricon Planning and Installation Guide.
Serial Port #4 for TriStation or Modbus interface
SERIAL 4 TX RX
DEBUG
Debug Port for Triconex use
TCM
435x
Figure 38
TCM Front Panel
149
TCM Ports
Serial Ports
A TCM provides four optically isolated RS-232/RS-485 serial ports which are TriStationconfigurable for point-to-point or multi-point serial connections. Transmission rates up to 115.2 kilobits per second per port can be selected. When the port is in RS-485 mode, there is software configurable termination for the port; see Configuring TCM Serial Ports on page 101.
Specifications
Feature Serial (Modbus) ports Description 4 optically-isolated RS-232/RS-485 ports, configurable from TriStation. The termination for RS-485 ports can be configured from TriStation. DB-9-pin PE standard, shielded, located on front panel 50 ft (15 m) 100 (30 m) to 4,000 ft (1.2 km), depending on baud rate 115200, 57600, 38400, 19200, 9600, 4800, 2400, 1200. Modbus Master or Slave, ASCII and RTU modes, optional parity, 1 stop bit Trimble GPS Serial TriStation Galvanic isolation Status indicator: Module status Status indicator: Port activity 500 VDC Pass, Fault, Active TX (Transmit) 1 per port RX (Receive) 1 per port
Connector RS-232 maximum cable length RS-485 maximum cable length Supported transmission rates (bps) Protocols supported
150
Appendix A
TCM Capabilities
Network Ports
A TCM provides two Ethernet ports with RJ-45 sockets for connection to twisted-pair cables. NET 1 and NET 2 are 10BaseT/100BaseTX connectors which can operate at 10 or 100 megabits per second.
Specifications
Feature Network ports 10/100BaseTX connector 10/100BaseTX maximum cable length Application protocols Description Two 10/100BaseT Ethernet ports RJ-45 standard, shielded, located on front panel 100 m using category 5 shielded twisted-pair cable Network-connected TCP/IP printer Simple Network Time Protocol (SNTP) Triconex Time Synchronization (UDP/IP) Triconex Time Synchronization (DLC) on NET 1 only GPS Modbus Triconex Peer-to-Peer (UDP/IP) Triconex Peer-to-Peer (DLC) on NET 1 only TriStation TSAA Network protocols Maximum Peer-to-Peer Nodes1 Galvanic isolation Status indicator: Module status Status indicator: Port activity TCP/IP, SNTP, ICMP, UDP/IP 31 500 VDC Pass, Fault, Active TX (Transmit) 1 per port RX (Receive) 1 per port 1. Contact Triconex for application guidelines and potential performance limitations.
151
Debug Port
The TCM includes one RS-232 serial port at the bottom of the module. This port is intended for Triconex use as a Debug port. For more information, contact Triconex Technical Support.
Specifications
Parameter Type Connector Baud rate Protocol Description RS-232 C DB9 9600 ASCII 8-bit 1 stop bit No parity Galvanic Isolation 500 VDC
152
Appendix A
TCM Capabilities
TCM Communication Indicators

The TCM communication indicators identify the type of communication occurring on the Tricon controller. The TX light indicates the TCM is transmitting a message and the RX light indicates the TCM is receiving a message. This symbol ( ) means the indicator is not important for this condition.
Serial 1-4 RX/TX Green blinking Link NET 1 RX/TX Link NET 2 RX/TX Description Normal response. TCM is communicating with the attached Modbus master/slave device. TCM is communicating with an Ethernet device through the NET 1 port. The port has a valid electrical connection to an Ethernet device but there is no communication. This can be cause by no communication being issued to and from the port, or a port configuration setup error. The port does not have a valid electrical connection to an Ethernet device. This typically indicates a cable problem. TCM is communicating with TriStation or with an Ethernet device through the NET 2 port
Green steady Green steady
Green blinking Not blinking or rarely blinking
Green steady
Not blinking or rarely blinking
No light
No light Green steady
Green blinking
153
Protocols Supported by TCM Ports

This table lists the protocols supported on TCM ports for models 4351, 4351A, 4352, 4352A, 4353, and 4354.
Protocol TriStation TSAA (UDP/IP) Peer-to-Peer (UDP/IP) Peer-to-Peer (DLC) Modbus Slave (ASCII or RTU) Modbus Master (RTU) Modbus Master or Slave (TCP) GPS Time Synchronization Triconex Time Synchronization via DLC Triconex Time Synchronization via UDP/IP SNTP Triconex Time Synchronization Network Printing using Jet Direct Network Ports (Models 4351 and 4352) NET 2 NET 2 NET 1 NET 1 1 NET 2 NET 1 NET 1 NET 2 NET 2 Network Ports (Models 4351A, 4352A, 4353, and 4354) NET 1, NET 2 NET 1, NET 2 NET 1, NET 2 NET 1 NET 1, NET 2 NET 1 NET 1, NET 2 NET 1, NET 2 NET 1, NET 2 Serial Ports (All Models) Port 4 Any port Any port Port 1
1. means protocol is not available on this port.
For summary information about the protocols, see Chapter 1, Introduction.
154
Appendix A
TCM Capabilities
B
NCM and NCMG Capabilities
NCM Operation 156 Physical Description 158
156
Appendix B
NCM Operation
The Network Communication Module (NCM) and Network Communication Module GPS (NCMG) are optional modules for the Tricon controller that can communicate with other Triconex controllers, with external devices on Ethernet networks, and with a Global Positioning System (GPS). The NCM and NCMG support several Triconex protocols and applications and client/server applications from other manufacturers. The NCM provides two BNC connectors as ports with these capabilities: NET 1 supports Peer-to-Peer protocol for safety networks comprised of Triconex controllers only. NET 2 supports open communication with external devices on an Ethernet network. These devices can include PCs which are running Triconex applications such as TriStation, SOE Recorder, OPC Server, and DDE Server, or user-written applications.
The NCMG also provides an RS-232 serial port which can be connected to the Trimble Acutime 2000 Synchronization Kit for GPS time synchronization. The Tricon controller supports two NCM modules or NCMG modules in one logical slot, or one of these modules in the COM slot. If two modules are in one slot, they function independently, not as hot spares. Each module can be connected to a separate network, or both can be used in a redundant configuration. For more information, see Redundant Devices (page 13). The NCM and NCMG are compatible with the Ethernet (IEEE 802.3) communication interface and operate at communication speeds up to 10 megabits per second. The modules connect with external host devices by means of 10Base2 coaxial cabling at typical distances up to 607 feet (185 meters). Distances up to 2.5 miles (4,000 meters) are possible using repeaters and standard (thick-net or fiber-optic) cabling. The Main Processors typically refresh data on the NCM and NCMG once per scan. Note Throughout this section, the name NCM represents both the NCM and the NCMG modules.
Message Processing
Figure 39 depicts how NCM ports communicate with all three MP modules by means of the Comm Bus. A message received by a NCM port is passed to all three MP modules over the Comm Bus. The TriBus votes on the message before sending it to the MP modules for processing, and returns the response to the Comm Bus after processing is complete. The Comm Bus then forwards the response to the NCM port.
NCM Operation
157
Figure 39
NCM Communication with MPs
The NCM processes messages as described in these sections.
TriStation, Peer-to-Peer, and Time Synchronization Messages

1 2 3 Receives the message and transmits it to the MP modules over the Comm Bus. Votes the message request with other MP modules over TriBus. Receives the message from the Comm Bus, processes the message, and transmits a response.
TSAA Read Queries

TSAA Write Commands

1 2 3 Receives the write request, transmits it to the MP modules over the Comm Bus. Votes the write request with the other MP modules over TriBus. Receives the message from the Comm Bus, processes the message, and transmits a write confirmation response.

Because most messages (except TSAA read queries) require TriBus voting, typical message response times require three or more scans to complete. For more information, contact Triconex Technical Support.
158
Appendix B
An NCM includes two Ethernet ports which operate at 10 megabits per second. An NCMG also includes an RS-232 serial port for communication with a GPS interface.
Figure 40
NCM and NCMG Front Panels
159
Specifications
These specifications apply to both the NCM and NCMG, except for the serial port which is functional on the NCMG only.
Feature Ethernet ports External transceiver ports Serial port Galvanic isolation Protocols supported Maximum Peer-to-Peer Nodes1 Communication speed Status indicators Module status Port activity Logic power Pass, Fault, Active TX (Transmit) 1 per port RX (Receive) 1 per port < 20 W Specification Two BNC connectors that require 10Base2 coaxial cables Reserved One RS-232 connector for GPS time synchronization Maximum cable length is 15 m (50 ft) 500 VDC (applies to Ethernet and serial ports) See Protocols Supported (page 160). 31 10 megabits per second
1. Contact Triconex for application guidelines and potential performance limitations.
Communication Indicators
The NCM and NCMG have yellow TX (transmit) and RX (receive) indicators for the NET 1 and NET 2 Ethernet ports and for the COMM serial port. TX blinks each time an NCM port transmits a message and RX blinks each time an NCM port receives a message from an external device. If a TX indicator stops blinking, the NCM module or the controller could have a problem. If an RX indicator stops blinking, the external device could have a problem.
NET 1 RX/TX Yellow blinking NET 2 RX/TX Yellow blinking COMM RX/TX 1 Description Normal response. The Ethernet port is communicating with an Ethernet device or TriStation. Yellow blinking Normal response. The COMM serial port is communicating with the Trimble Acutime 2000 Synchronization Kit.
1. This symbol ( ) means the indicator is not important for this condition.
160
Appendix B
Protocols Supported
Ports on the NCM and NCMG support these protocols.
Supported Protocols TriStation TSAA Client/Server Peer-to-Peer Triconex Time Synchronization Trimble GPS Time Synchronization NET 1 Ethernet (NCM and NCMG) NET 2 Ethernet (NCM and NCMG) COMM Serial (NCMG Only)
For summary information about the protocols, see Chapter 1, Introduction.
C
EICM Capabilities
EICM Operation 162 Physical Description 165
162
Appendix C
EICM Capabilities
EICM Operation
The Enhanced Intelligent Communication Module (EICM) enables communication with these devices: Modbus masters and slaves Other Triconex controllers TriStation PC Centronics-compatible printers
Each EICM has four serial ports and one parallel port which can operate concurrently. The four serial ports are uniquely addressed and can be used for Modbus or TriStation communication. Modbus communication can be performed in either RTU or ASCII mode. The parallel port provides a Centronics interface to a printer. A Tricon controller supports up to two EICM modules which must reside in one logical slot. This arrangement provides a total of eight serial ports and two printer ports. The hot-spare feature is not available for the EICM. However, you can connect redundant devices to ports on two EICM modules in the same logical slot. For more information, see Redundant Devices on page 13. Each EICM supports an aggregate data rate of 57.6 kilobits per second, that is, the total data rate for all four ports must be less than or equal to 57.6 kilobits per second. Each EICM port provides 500 VDC isolation between the external signals and Tricon logic ground. Any standard Modbus device can communicate with the Tricon controller by means of the EICM, provided that aliases are assigned to the program variables.
EICM Operation
163
Message Processing
This figure depicts EICM modules communicating with the Main Processors by means of the triplicated Comm Bus. The Comm Bus has three channels (one for each MP) which are connected to each EICM module.
Figure 41
EICM Communication with MPs
A message received by an EICM port is passed to all three MPs over the Comm Bus. The TriBus votes on the message before sending it to the MP modules for processing, and returns the response to the Comm Bus after processing is complete. The Comm Bus then forwards the response to the EICM port. The EICM processes messages as described in the following sections.
TriStation Messages
1 2 3 Receives the message and transmits it to the MP modules over the Comm Bus. Votes the message request with other MP modules over TriBus. Receives the message from the Comm Bus, processes the message and transmits a response.
Modbus Read Queries

164
Appendix C
EICM Capabilities
Modbus Write Commands

1 2 3 Receives the write request, transmits it to the MP modules over the Comm Bus. Votes the write request with the other MP modules over TriBus. Receives the message from the Comm Bus, processes the message and transmits a write confirmation response.

Because all messages except Modbus read queries require Tribus voting, typical message response times require three or more scans to complete. For more information, see Determining Message Response Time on page 205 or contact Triconex Technical Support.
165
Each EICM includes four serial ports and one parallel port with indicators that blink when data is being transmitted and received.
Figure 42
EICM Front Panel
166
Appendix C
EICM Capabilities
Serial Port Specifications

An EICM has four serial ports which can be connected to Modbus master or slave devices in point-to-point or multi-point configurations. Each serial port provides a DB-25-pin male connector. For each port, you must set a switch on the side of the EICM module to specify whether the communication interface uses RS-232, or RS-422/RS-485. For instructions, see Setting EICM Switches for Serial Ports on page 97.
Feature Physical features Connectors RS-232 maximum cable length RS-422/RS-485 maximum cable length Data transmission rates Protocols Galvanic isolation Logic power Specification RS-232, RS-422 or RS-485 communication interface Other options are configurable from TriStation. Male DB-25-pin, DTE standard, shielded 50 ft (15 m) 4,520 ft (1.2 km) 19200, 9600, 4800, 2400, or 1200 kilobits per second Master, slave, or master/slave RTU or ASCII mode 500 VDC < 10 W
Parallel Port Specifications

An EICM module has one parallel port which can be connected to a Centronics-compatible printer. The port is galvanically isolated to 500 VDC and provides a female 25-pin D series connector for use with a standard printing cable. The maximum cable length is 15 to 20 feet (5 to 6 meters), depending on the quality of the cable.
Port Numbers and Connections

For configuration in TriStation, EICM ports in a left and right logical slot have these port numbers and can be connected to these devices. Ports 4 and 9 are the defaults for TriStation connection, although Ports 1 through 3 and Ports 6 through 8 can also be used for TriStation.
Left Slot 01 02 03 04 05 Right Slot 06 07 08 09 10 Parallel Centronics-compatible parallel printer Serial Modbus Device or TriStation Type of Port Connection
167
EICM Communication Indicators

The EICM has a yellow TX and RX indicator for each serial port. TX blinks each time an EICM port transmits a message and RX blinks each time an EICM port receives a message from an external Modbus device or TriStation. If a TX indicator stops blinking, the EICM module or the controller could have a problem. If an RX indicator stops blinking, the external Modbus device or TriStation could have a problem.
Serial 1 RX/TX Yellow blinking Serial 2 RX/TX Yellow blinking Serial 3 RX/TX Yellow blinking Serial 4 RX/TX Yellow blinking Description Normal response. EICM is communicating with a Modbus device or TriStation.
Protocols Supported
EICM ports can use these protocols.
Protocol TriStation Modbus Slave Modbus Master Modbus Master/Slave Parallel Printing Serial Ports Printer Ports
For summary information about the protocols, see Chapter 1, Introduction
168
Appendix C
EICM Capabilities
D
TSAA Protocol
Overview 170 TSAA Messages 172 Performance Considerations 197 Response Codes 201
170
Appendix D
TSAA Protocol
Overview
Triconex System Access Application (TSAA) protocol is a messaging protocol which provides message formats used in application programs that read and write data to Triconex controllers. TSAA is based on a client/server model which allows a client to request information from an external device using a server application. These communication modules can be used with TSAA communication: Tricon ACM, Tricon NCM, Tricon TCM, and Trident CM. You can use TSAA to develop these types of applications: Control (Read/Write) Applications, such as an operator interface station, that require access to the status of the Triconex controller and the ability to write data to the controller. Monitor (Read-Only) Applications, such as SOE Recorder, that receive data from the controller.
Byte Ordering in Messages

The following table identifies the type of ordering used in the message fields.
Message Field Frame Header Data CRC Description Big-endian order for both Tricon and Trident. Little-endian order for Tricon; big-endian order for Trident. Little-endian for both Tricon and Trident.
If the controller and PC use different ordering types, the application might need to convert data to the appropriate order.
Little-Endian Order
In little-endian ordering, the data is ordered from right to left with the least significant bits or bytes to the right.
Bit Ordering for Bit Fields

Bit 31 ... Bit 3 Bit 2 Bit 1 Bit 0
Byte Ordering for 16-Bit Variables

Byte 1 Byte 0

Byte 3 Byte 2 Byte 1 Byte 0
Overview
171
Big-Endian Order
In big-endian ordering, the data is ordered from the left to right with the least significant bits or bytes to the left.
Bit Ordering for Bit Fields

Bit 0 Bit 1 Bit 2 Bit 3 ... Bit 31

Byte 0 Byte 1

Byte 0 Byte1 Byte 2 Byte 3
Symbol Table Information

The symbol table includes information about TriStation 1131 variables, Modbus alias numbers, bin numbers, and offset. This information is required when data is read or written to the controller. The symbol table is downloaded to the controller with the TriStation 1131 application. Symbol table information can be retrieved in these ways: For Tricon and Trident, by exporting the information from TriStation 1131. For more information, see the Export Points command in the TriStation 1131 Developers Guide. For Trident only, by retrieving the information from the controller with the TSAA message TRICON_GET_SYMBOL_REQ.
172
Appendix D
TSAA Protocol
TSAA Messages
A TSAA message is a request made by a client, or a response made by the Triconex controller. This section describes the format of TSAA messages and the available types of messages. In this section, the words frame and message mean the same thinga unit of data that is transmitted through a network.
CAUTION
Message Format
UDP protocol is the only supported protocol. The Tricon NCM and Trident CM use UDP port 1500 for all TSAA communication. Using any other port may cause problems.
Each TSAA message uses a format which includes these fields: A frame header which identifies the message (big-endian order) A data area which contains the frame message (little-endian order for Tricon; big-endian for Trident) A 32-bit Cyclic Redundancy Check (CRC) (little-endian order for Tricon and Trident)
Data Area variable length CRC 4 bytes
Frame Header 8 bytes
Note
Unless otherwise specified, fields in messages are unsigned.
Frame Header
The frame header in a TSAA message includes these fields.
Type 1 byte nodeNumber 1 byte seqNum 1 byte version 1 byte flag 1 byte id 1 byte length 2 bytes
TSAA Messages
173
Type
The Type field in the frame header identifies the message type. These types of TSAA messages are available.
Request from Client Triconex Controller Response
Type
Message Type TRICON_DATA TRICON_DATA_REQ WRITE_TRICON_DATA
Description Returns data in response to a type 2 message. Requests data from the TriStation application. Requests the controller to write to memory and output variables in the TriStation application. Responds to a request to write to memory and output variables by a type 3 message. Requests the current time on the controller clock. Returns the current time on the controller clock in response to a type 5 message. Requests setting of the controller clock. Responds to a request to set the clock made by a type 7 message. Requests controller to adjust clock forward or backward. Responds to a request to adjust the clock made by a type 9 message. Requests data (memory, input, or output variables) to be read from the TriStation application. Returns variable data in response to a type 11 message. Requests SOE (sequence of events) data from the controller. Returns SOE data in response to a type 13 message. Requests the TriStation application name and version number. For Triconex internal use only.
1 2
WRITE_TRICON_DATA_RSP
READ_TRICON_CLOCK READ_TRICON_CLOCK_RSP
7 8 9
SET_TRICON_CLOCK SET_TRICON_CLOCK_RSP ADJUST_TRICON_CLOCK ADJUST_TRICON_CLOCK_RSP
10
11
READ_TRICON_DATA
12 13 14
READ_TRICON_RSP TRICON_SOE_REQ TRICON_SOE_RSP TRICON_CPSTATUS_REQ
15
174
Appendix D
TSAA Protocol
Type
Message Type TRICON_CPSTATUS_RSP
Description Returns program information in response to a type 15 message. For Triconex internal use only. Sends a message to the client when SOE data is available. The message is sent when SOE data is put into an empty SOE block and every 10 seconds while there is data available in any block. Requests part of a symbol table from the controller. For Trident only. Sends part of a symbol table as requested by a type 22 message. For Trident only.
Request from Client
Triconex Controller Response
16 TRICON_SOE_DATAAVAIL 17
TRICON_GET_SYMBOL_REQ 22 TRICON_GET_SYMBOL_RSP 23
nodeNumber
The nodeNumber field identifies the destination node number for the message, which is the node number for the Triconex controller.
seqNum
The seqNum field identifies the number of the message in a multiple-message response. This field can help determine if there are missing messages.
version
The version field identifies the version number of the protocol used by the sender: For Tricon, the number must be 0. For Trident, the number must be 1.
flag
The flag field is a bit field that indicates the position of the frame in a multi-frame message, or that the message is a single frame.
Flag 0x00 0x01 0x01 Frame Position mid-frame of a multi-frame message first frame of a multi-frame message last frame of a multi-frame message
TSAA Messages
175
Flag 0x03
Frame Position single frame message
id
The id field assigns a number to a request and associated response. If a client makes periodic requests of the same message type and wants to associate them with the responses, this field can be used to assign an identifier. The request and response use the same identifier.
length
The length field identifies the length of the frame excluding the CRC32 field.
TRICON_DATA (Type 1)
A TRICON_DATA message replies to a request for data made by a TRICON_DATA_REQ (type 2) message. If the client sends a data request at least once every two minutes, the controller continues sending data responses at the interval specified by the request.
CAUTION
If more than one client sends a TRICON_DATA_REQ to a controller, the controller response changes to a UDP broadcast which is sent to all the clients. If the client connects on a port other than 1500, broadcast data may be lost when a second client sends a data request.
This message includes these fields.

Frame_Hdr 8 bytes Data_Hdr variable length Bin (1) Header varies Bin (2) Header... varies CRC 4 bytes
Data_Hdr
The Data_Hdr field includes these fields.
numberOfBlocks 2 bytes rfu 2 bytes reserved SymbolTableVersion 4 bytes (Trident only)
numberOfBlocks
The numberOfBlocks field identifies the number of blocks in the data portion of the message.
SymbolTableVersion (Trident Only)

The SymbolTableVersion field identifies the TriStation application version. If the version is 1.0, this is 0x00010000. This field is only available for Trident controllers.
176
Appendix D
TSAA Protocol
Bin Headers
A TRICON_DATA (Type 1) message can have multiple bin headers followed by bin data. Each bin header includes these fields.
bin 1 byte rfu 1 byte reserved totalLength 2 bytes offset 2 bytes length 2 bytes BinTime 8 bytes (Trident only)
bin
The bin field identifies which bin holds the message data, using a numeric value to represent the variable type and data type. This table identifies Tricon and Trident bin information.
Bin 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Data Type BOOL BOOL BOOL BOOL DINT DINT REAL REAL BOOL DINT DINT DINT REAL Variable Type Output Memory Input Memory Input Memory Input Memory System status System status Output Memory Memory Message Type Read/Write Read/Write Read Read Read Read Read Read Read Read Read/Write Read/Write Read/Write Tricon Range 00001 - 02000 02001 - 04000 10001 - 12000 12001 - 14000 30001 - 31000 31001 - 32000 32001 - 32120 33001 - 34000 14001 - 19999 39631 - 39999 40001 - 40250 40251 - 41000 41001 - 42000 Trident Range 00001 - 09999 00001 - 09999 10001 - 19999 10001 - 19999 30001 - 39999 30001 - 39999 30001 - 39999 30001 - 39999 10001 - 19999 30001 - 39999 40001 - 49999 40001 - 49999 40001 - 49999 Bin Size 2048 2016 4096 2016 1024 1000 120 1000 5999 369 512 750 1000
Not applicable (Number of bins)
totalLength
The totalLength field indicates the length of the bin.
offset
The offset field identifies the starting position of the requested data in the bin. For discrete data types, the offset is the number of bits. For integer and real data types, the offset is the number of 32-bit words.
TSAA Messages
177
length
The length field contains the length of the data returned in the message.
binTime (Trident only)

The binTime field identifies the time stamp associated with the bin data in microseconds since January 1, 1970. This field is only available to Trident controllers.
TRICON_DATA_REQ (Type 2)
A TRICON_DATA_REQ message requests one or more bins of data from a Triconex controller. The controller responds with a TRICON_DATA (type 1) message. If the client sends a data request at least once every two minutes, the controller continues sending data responses at the interval specified by the request. The data request message is designed for applications that require all of the data in one or more bins. After the request is sent, the controller continuously sends data responses to the client at specified intervals. The client cannot stop the controller from sending data, but the controller will stop sending data if a data request is not received again within two minutes. If you use TCP protocol (or UDP protocol with connect and disconnect functions), you must leave the connection open for a minimum of two minutes after sending this request. If the application requires specifying the range of data, use READ_TRICON_DATA (type 11). This message includes these fields.
Frame_Hdr 8 bytes Data_Req_Hdr variable length CRC 4 bytes
Data_Req_Hdr
The Data_Req_Hdr field contains these fields.
binsRequested 2 bytes reqTime 2 bytes
binsRequested
The binsRequested field is a binary mask that identifies which bins of data the Triconex controller should send. If the request includes an invalid bin number, the response is a bin header with no data.
Binary Mask 0x1fff Description Masks all bins
178
Appendix D
TSAA Protocol
Binary Mask 0x0001 0x0002 0x0004 0x0008 0x0010 0x0020 0x0040 0x0080 0x0100 (Tricon only) 0x0200 (Tricon only) 0x0400 0x0800 0x1000
Description Masks discrete output Masks read/write discrete memory Masks discrete input Masks read-only discrete memory Masks analog input Masks read-only integer memory Masks real input Masks read-only real memory Masks discrete system status Masks integer system status Masks analog output Masks read/write integer memory Masks read/write real memory
reqTime
The reqTime field indicates the time in milliseconds between broadcasts of the requested bins. For example, a value of 1,000 causes a Triconex controller to broadcast the data once per second. If this value is zero (0), the controller broadcasts the data each time the ACM, NCM, or TCM (Tricon) or CM (Trident) is updated.
WRITE_TRICON_DATA (Type 3)
A WRITE_TRICON_DATA message requests the Triconex controller to write data to output and memory variables in the TriStation application. These conditions must be met for the controller to accept this request: The variables must be defined as read/write. For Tricon, the keyswitch must be in the Program or Remote position. For Trident, the Remote mode must be enabled by setting a system attribute. The TriStation configuration setting (Disable Remote Changes to Outputs) which was downloaded to the controller must allow remote changes. (This setting only affects changes to discrete outputs and analog outputs.) The TriStation configuration for the ACM, NCM, or TCM (Tricon) and CM (Trident) must be configured as read/write.
If the controller cannot write the data, it sends a reject response code. For more information, see Response Codes (page 201).
TSAA Messages
179
This message includes these fields.

Frame_Hdr 8 bytes Write_Hdr 4 bytes Write_Data varies ... Write_Data varies CRC 4 bytes
Write_Hdr
The Write_Hdr contains these fields.
numberOfBlocks 2 bytes rfu 2 bytes reserved
numberOfBlocks
The numberOfBlocks field indicates the number of write data blocks for the message type.
Write_Data
The Write_Data field includes these fields.
binNumber 1 byte rfu 3 bytes reserved offset 2 bytes numberOfValues 3 bytes Values varies
binNumber
The binNumber field indicates the number of the bin to be changed.
offset
numberOfValues
The numberOfValues field indicates the number of variables to be written starting at the specified offset.
Values
The Values field contains the values for the variables to be changed. Discrete variables require one byte each for the new value (0 or 1).
180
Appendix D
TSAA Protocol
WRITE_TRICON_DATA_RSP (Type 4)
A WRITE_TRICON_DATA_RSP message replies with a success or failure code to a request to write data sent by a WRITE_TRICON_DATA (type 3) message. This message includes these fields.
Frame_Hdr 8 bytes responseCode 1 byte subReason 1 byte rfu 2 bytes reserved CRC 4 bytes
responseCode
The responseCode field indicates the success or failure of the request. A value of zero (0) indicates the request was successfully completed. For more information, see Response Codes (page 201).
subReason
The subReason field contains additional information about the failure of the request.
READ_TRICON_CLOCK (Type 5)
A READ_TRICON_CLOCK message requests the current time on the Triconex controller. The controller responds with READ_TRICON_CLOCK_RSP (type 6) which sends the current time to the client. There are no fields specific to this message.
Frame_Hdr 8 bytes CRC 4 bytes
READ_TRICON_CLOCK_RSP (Type 6)
A READ_TRICON_CLOCK_RSP message sends the current controller time to the client in response to a READ_TRICON_CLOCK (type 5) request. This message includes these fields.
Frame_Hdr 8 bytes Read_Clock_Resp 12 bytes CRC 4 bytes
Read_Clock_Rsp
The Read_Clock_Rsp field includes these fields.
TSAA Messages
181
responseCode 1 byte
subReason 1 byte
rfu 2 bytes reserved
relSec 4 bytes
milliSec 2 bytes
rfu2 2 bytes
ResponseCode
subReason
relSec
The relSec field indicates the current Triconex system time expressed in relative seconds. For Tricon, relative seconds are seconds past 00:00 January 1, 1970 based on local time. For Trident, relative seconds are seconds past 1970 based on universal time (Greenwich Mean Time). (2000 is the earliest date and 2050 is the latest date.)
milliSec
The milliSec field indicates the millisecond portion of the Triconex system time.
SET_TRICON_CLOCK (Type 7)
A SET_TRICON_CLOCK message requests the time to be set on the Triconex controller. The controller responds with a SET_TRICON_CLOCK_RSP (type 8) message. These conditions must be met for the controller to accept this request: For Tricon, the keyswitch must be in Program mode. For Trident, the operational mode must be set to Program.
For Tricon only, the controller does not allow an application or an external device to set the time continuously. At least five minutes must pass before the controller responds to a SET_TRICON_CLOCK message. If the application sends this message before five minutes pass, the message is rejected. This message includes these fields.
Frame_Hdr 8 bytes Set_Clock 8 bytes CRC 4 bytes
182
Appendix D
TSAA Protocol
Set_Clock
The Set_Clock field includes these fields.
relSec 4 bytes milliSec 2 bytes rfu 2 bytes reserved
relSec
The relSec field contains the controller system time expressed in relative seconds. For Tricon, relative seconds are seconds past 00:00 January 1, 1970 based on local time. For Trident, relative seconds are seconds past 1970 based on universal time (Greenwich Mean Time). (2000 is the earliest date and 2050 is the latest date.)
milliSec
The milliSec field contains the millisecond portion of the system time.
SET_TRICON_CLOCK_RSP (Type 8)
A SET_TRICON_CLOCK_RSP message replies with a success or failure code to a SET_TRICON_CLOCK (type 7) message. This message includes these fields.
Frame_Hdr 8 bytes Set_Clock_Rsp 4 bytes CRC 4 bytes
Set_Clock_Rsp
The Set_Clock_Rsp field contains these fields.
responseCode 1 byte subReason 1 byte rfu 2 bytes reserved
responseCode
subReason
TSAA Messages
183
ADJUST_TRICON_CLOCK (Type 9)
An ADJUST_TRICON_CLOCK message requests the time to be adjusted on the Triconex controller either forward or backward. The controller responds with an ADJUST_TRICON_CLOCK_RSP (type 10) message. These conditions must be met for the controller to accept this request: For Tricon, the keyswitch must be in Program mode. For Trident, the operational mode must be set to Program.
For Tricon only, the controller does not allow an application or an external device to set the time continuously. At least five minutes must pass before the controller will respond to a SET_TRICON_CLOCK message. If the application program sends this message before five minutes pass, the message is rejected. This message includes these fields.
Frame_Hdr 8 bytes Adjust_Clock 8 bytes CRC 4 bytes
Adjust_Clock
The Adjust_Clock field includes these fields.
AdjustSeconds 4 bytes signed AdjustMilliseconds 4 bytes signed
AdjustSeconds
The AdjustSeconds field contains the number of seconds to adjust the controller clock either forward or backward.
AdjustMilliseconds
The AdjustMilliseconds field contains the number of milliseconds to adjust the controller clock either forward or backward.
184
Appendix D
TSAA Protocol
ADJUST_TRICON_CLOCK_RSP (Type 10)

An ADJUST_TRICON_CLOCK_RSP message replies with a success or failure code to an ADJUST_TRICON_CLOCK (type 9) message. This message includes these fields.
Frame_Hdr 8 bytes Adjust_Clock_Rsp 4 bytes CRC 4 bytes
Adjust_Clock_Rsp
The Adjust_Clock_Rsp field contains these fields.
responseCode 1 byte subReason 1 byte rfu 2 bytes reserved
responseCode
subReason
READ_TRICON_DATA (Type 11)

A READ_TRICON_DATA message requests variable data from the Triconex controller. The controller responds with the requested data using one or more READ_TRICON_RSP (type 12) messages depending on the amount of data requested. This message includes these fields.
Frame_Hdr 8 bytes Read_Hdr 4 bytes Read_Data 6 bytes CRC 4 bytes
Read_Hdr
The Read_Hdr field includes these fields.
numberOfBlocks 2 bytes rfu 2 bytes reserved
TSAA Messages
185
numberOfBlocks
The numberOfBlocks field indicates the number of Read_Data blocks for this message.
Read_Data
The Read_Data field includes these fields.
binNumber 1 byte rfu 3 bytes reserved offset 2 bytes numberOfValues 2 bytes
binNumber
The binNumber field contains the number of the bin to be read.
offset
If the numberOfValues field is zero (0), this field is ignored.
numberOfValues
The numberOfValues field contains the number of variables to be read from the bin. If the number is zero (0), all of the data in the bin is returned.
READ_TRICON_RSP (Type 12)

A READ_TRICON_RSP message responds to a request to read data on the controller made by a READ_TRICON_DATA (type 11) message. The controller sends one or more of these messages depending on the amount of data requested. This message includes these fields.
Frame_Hdr 8 bytes Read_Rsp_Hdr Read_Rsp_Hdr 4 bytes Read_Data_Rsp 12 bytes Data varies ... CRC 4 bytes
The Read_Rsp_Hdr field includes these fields.

responseCode 1 byte subReason 1 byte numberOfBlocks 2 bytes
186
Appendix D
TSAA Protocol
responseCode
subReason
numberOfBlocks
The numberOfBlocks field indicates the number of Read_Data_Rsp blocks in the message.
Read_Data_Rsp
The Read_Data_Rsp field includes these fields.
binNumber 1 byte rfu 1 byte reserved offset 2 bytes relSec 4 bytes milliSec 2 bytes numberOfValues 2 bytes
binNumber
The binNumber field contains the number of the bin to be read.
offset
The offset field contains the number of variables from the beginning of the bin. For discrete data types, the offset is the number of bits. For integer and real data types, the offset is the number of 32-bit words.
relSec and milliSec

The relSec field contains the controller time stamp for bin data expressed in relative seconds. The milliSec field contains the millisecond portion of the controller time stamp. For Tricon, relative seconds are seconds past 00:00 January 1, 1970 based on local time. For Trident, relative seconds are seconds past 1970 based on universal time (Greenwich Mean Time). (2000 is the earliest date and 2050 is the latest date.)
numberOfValues
The numberOfValues field indicates the number of variables that are read starting at the specified offset.
TSAA Messages
187
Data
The Data field contains data from the bin. For Tricon, the data is ordered in little-endian format. For Trident, the data is ordered in big-endian format.
For more information about Trident data, see Symbol Table Information (page 171).
TRICON_SOE_REQ (Type 13)

A TRICON_SOE_REQ message requests the Triconex controller to send event data collected in an SOE block. The controller responds with a TRICON_SOE_RSP (type 14) message. This message includes these fields.
Frame_Hdr 8 bytes Soe_Req 16 bytes CRC 4 bytes
Soe_Req
The Soe_Req field includes these fields.
soeNumber 1 byte firstFlag 1 byte ackFlag 1 byte rfu1 1 byte reserved getIndex 2 bytes rfu2 2 bytes wrapCount 4 bytes generation 4 bytes
soeNumber
The soeNumber field contains the SOE block number which can be 1 to 16. (SOE blocks are configured in TriStation.)
firstFlag
The firstFlag field indicates whether this is the first data request for this SOE block. This value should be set to one (1) for the first request. For all subsequent requests, it should be set it to zero (0).
ackFlag
The ackFlag field indicates whether the last TRICON_SOE_RSP message was received correctly. If the message was received correctly, set the field to one (1). If not, set it to zero (0).
getIndex
The getIndex field is a pointer into the SOE data block that indicates the start of the data being requested.
188
Appendix D
TSAA Protocol
wrapCount
The wrapCount field indicates the number of times the buffer has been filled since the last time the TriStation application issued an SOECLR command for this block.
generation
The generation field indicates the number of times the TriStation application has issued the SOECLR command.
TRICON_SOE_RSP (Type 14)

A TRICON_SOE_RSP message responds to a TRICON_SOE_REQ (type 13) request by sending data from the SOE block. The values for the getIndex, wrapCount, and generation fields may not match the numbers requested because their values change depending on how frequently you request data and whether events are occurring. This message includes these fields.
Frame_Hdr 8 bytes Soe_Rsp 16 bytes Entry 8 bytes Entry 8 bytes ... CRC 4 bytes
Soe_Rsp
The Soe_Rsp field includes these fields.
soe Number 1 byte response Code 1 byte sub Reason 1 byte rfu 1 byte numberOf Entries 2 byte next Index 2 bytes wrap Count 4 bytes generation 4 bytes
soeNumber
The soeNumber field indicates the number of the SOE block.
responseCode
subReason
The subReason field identifies the subcode for the request, which is used for debugging problems.
TSAA Messages
189
numberOfEntries
The numberOfEntries field indicates the number of entries in the response. There are two types of entry: time stamp and event data. For more information, see entry (SOE Data Entry) (page 189) and entry (SOE Time Stamp) (page 190).
getIndex
The getIndex field is a pointer into the SOE data block and is the beginning of the transferred data stream.
nextIndex
The nextIndex field is a pointer into the SOE data block that indicates the start of the data being requested.
wrapCount
The wrapCount field indicates the number of times the buffer has been filled since the last time the TriStation application issued an SOECLR command for this block.
generation
The generation field indicates the number of times the TriStation application has issued the SOECLR command.
entry (SOE Data Entry)

The entry field for an SOE data entry includes these fields.
offset 16 bits dataType 3 bits bin 5 bits type 3 bits soeNumber 3 bits value 32 bits
offset
The offset field contains the number of variables from the beginning of the bin. For discrete data types, the offset is the number of bits. For integer and real data types, the offset is the number of 32-bit words.
dataType
The type field identifies the data type of the SOE entry with a numeric value.
Data Type BOOL (Discrete) DINT (Integer) REAL (Analog) Value 0 1 2
190
Appendix D
TSAA Protocol
bin
The bin field identifies which bin holds the message data, using a numeric value to represent the variable type and data type.
Bin 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Data Type BOOL BOOL BOOL BOOL DINT DINT REAL REAL BOOL DINT DINT DINT REAL Variable Type Output Memory Input Memory Input Memory Input Memory System status System status Output Memory Memory Message Type Read/Write Read/Write Read Read Read Read Read Read Read Read Read/Write Read/Write Read/Write Tricon Range 00001 - 02000 02001 - 04000 10001 - 12000 12001 - 14000 30001 - 31000 31001 - 32000 32001 - 32120 33001 - 34000 14001 - 19999 39631 - 39999 40001 - 40250 40251 - 41000 41001 - 42000 Trident Range 00001 - 09999 00001 - 09999 10001 - 19999 10001 - 19999 30001 - 39999 30001 - 39999 30001 - 39999 30001 - 39999 10001 - 19999 30001 - 39999 40001 - 49999 40001 - 49999 40001 - 49999 Bin Size 2048 2016 4096 2016 1024 1000 120 1000 5999 369 512 750 1000
Not applicable (Number of bins)
type
The type field indicates whether the entry is an SOE time stamp or an SOE data entry. If 1, the entry is a time stamp. If 2, the entry is a data entry.
soeNumber
The soeNumber field identifies the SOE block number.
value
The value field contains the value of the aliased variable. If On, it is 0x00000001; if Off, it is 0x00000000.
entry (SOE Time Stamp)

The entry fields for an SOE time stamp include these fields.
TSAA Messages
191
microseconds 20 bits
reason 4 bits
type 3 bits
soeNumber 5 bits
seconds 32 bits
microseconds
The microseconds field contains the microseconds part of the time stamp which can be from 0 to 999,999.
reason
The reason field indicates the reason a time stamp entry was made. The reasons are described in this table.
Value 1 2 3 4 Reason SOESTRT command processed. SOESTOP command processed or buffer full for First Out block. SOECLR command processed. Event has been detected. It can be collected from the Entry field of the TRICON_SOE_RSP message.
type
The type field indicates whether the entry is an SOE time stamp or an SOE data entry. If 1, the entry is a time stamp. If 2, the entry is a data entry.
soeNumber
The soeNumber field identifies the SOE block number.
second
The second field contains the seconds part of the time stamp which can be from 0 to 59.
TRICON_CPSTATUS_REQ (Type 15)

A TRICON_CPSTATUS_REQ message requests the TriStation application name and version number from the Triconex controller. This message does not require any data. The controller responds with a TRICON_CPSTATUS_RSP (type 16) message. This message type is for Triconex internal use only.
192
Appendix D
TSAA Protocol
TRICON_CPSTATUS_RSP (Type 16)

A TRICON_CPSTATUS_RSP message replies to the request for TriStation application name and version number made by a TRICON_CPSTATUS_REQ (type 15) message. This message type is for Triconex internal use only.
TRICON_SOE_DATAAVAIL (Type 17)

A TRICON_SOE_DATAAVAIL message sends a message to the client when SOE data is available. The message is sent when SOE data is put into an empty SOE block and every 10 seconds while there is data available in any block. This is a broadcast message. This message includes these fields.
Frame_Hdr 8 bytes SoeDataAvail 16 bytes CRC 4 bytes
SoeDataAvail
The SoeDataAvail field includes these fields.
putIndex 2 bytes firstIndex 2 bytes size 2 bytes state 1 byte rfu 1 byte reserved wrapCount 4 bytes generation 4 bytes
putIndex
The putIndex field contains a pointer to the last data available in the SOE data block.
firstIndex
The firstIndex field contains a pointer to the beginning of the available data in the SOE data block.
size
The size field contains the number of entries in the block. The block size is specified in TriStation.
state
The state field contains a number representing the status of the SOE block. The states include: 0 1 2 Block is not defined or block is not started. Block is collecting. Block is stopped or cleared.
TSAA Messages
193
Block is full.
wrapCount
The wrapCount field contains the number of times the buffer has been filled since the last time the TriStation application issued an SOECLR command for this block.
generation
The generation field contains the number of times the TriStation application has issued the SOECLR command.
TRICON_GET_SYMBOL_REQ (Type 22, Trident Only)

A TRICON_GET_SYMBOL_REQ message requests a part of the symbol table from the Trident controller. When the controller receives this message, it sends a TRICON_GET_SYMBOL_RSP (type 23) message to the client. This message type is only available for Trident controllers. The symbol table can be large, up to 1.2 megabytes, which means you may have to download the table in parts and then assemble the table on the client. The client can then parse the symbol table (after correcting endian) and extract all the relevant information related to a symbol. This message includes these fields.
Frame_Hdr 8 bytes Tricon_Get_Symbol 12 bytes CRC 4 bytes
Tricon_Get_Symbol
The Tricon_Get_Symbol field includes these fields.
totalSize 4 bytes offset 4 bytes CRC 4 bytes
totalSize
The totalSize field must be set to zero (0).
offset
The offset field identifies the starting position of the requested data in the symbol table. For discrete data types, the offset is the number of bits. For integer and real data types, the offset is the number of 32-bit words.
194
Appendix D
TSAA Protocol
TRICON_GET_SYMBOL_RSP (Type 23, Trident Only)

A TRICON_GET_SYMBOL_RSP message sends symbol table data requested by a TRICON_GET_SYMBOL_REQ (type 22) message. This message type is not available to Tricon controllers. To find the starting address for a tagname, use this equation:
Location of tag name = Starting_Address_of_Symbol_Table + x + (y x Tricon_Symbol_Table::numberOfEntries) + Tricon_Symbol_Entry::nameOffset
where x=size of Tricon_Symbol_Table and y=size of Tricon_Symbol_Entry This message includes these fields.
Frame_Hdr 8 bytes Symbol_Table _Rsp 20 bytes Tricon_Symbol _Table 12 bytes Tricon_Symbol _Entry each 12 bytes Symbol_names variable sizenull terminated ASCII strings Check sum 4 bytes
Symbol_Table_Rsp
The Symbol_Table_Rsp field includes these fields.
responseCode 1 byte subReason 1 byte rfu 2 bytes reserved totalSize 4 bytes offset 4 bytes length 4 bytes symbolVersion 4 bytes
responseCode The responseCode field indicates the success or failure of the request. A value of zero (0) indicates the request was successfully completed. For more information, see Response Codes (page 201). subReason The subReason field identifies the sub code for the request. Used for debugging. totalSize The totalSize field identifies the total size of the symbol table. offset The offset field identifies the starting position of the requested data in the symbol table. For discrete data types, the offset is the number of bits. For integer and real data types, the offset is the number of 32-bit words.
TSAA Messages
195
Length The Length field contains the length of the data returned. symbolVersion The symbolVersion field contains the version of the symbol table which is the same TriStation application version. After conversion to little endian format on the client PC, this is a 32-bit number with this format: MMMMnnn: where MMMM is the 16-bit major version number and nnnn is the TriStation application minor version number.
Tricon_Symbol_Table
The Tricon_Symbol_Table field includes these fields.
numberOfEntries 4 bytes String Offset 4 bytes reserved Checksum 4 bytes reserved
numberOfEntries
The number of Tricon_Symbol_Entry structures in the table.
String Offset
Reserved.
Checksum
Reserved.
Tricon_Symbol_Entry
The Tricon_Symbol_Entry field includes these fields.
nameOffset 4 bytes Bin Number 1 byte rfu 1 byte reserved Bin Offset 2 bytes No conversion 1 byte Modbus Station 1 byte Alias 2 bytes
nameOffset
The nameOffset field identifies the starting position of the name string for this entry.
Bin Number
The Bin Number identifies the bin number of the entry.
196
Appendix D
TSAA Protocol
Bin Offset
The Bin Offset field identifies the starting position of the entry in the bin.
No Conversion
Reserved for Triconex use.
Modbus Station
Reserved for Triconex use.
Alias
The Alias field identifies the alias number for the entry.
Performance Considerations
197
This section describes factors affecting the performance of TSAA communication, which is measured in terms of the Triconex controllers response to a clients read and write requests. These actions occur with TSAA messages: Read requests are directly processed by the communication module. The communication module returns data from bins which mirror the bins stored on the MPs. This data is updated by the MPs via the Communication Bus at the end of each scan, during the period referred to as the scan surplus. Write requests pass through the communication module and are processed by the MPs TSX operating system. If the data items are aliased read/write variables and remote access is enabled, the MPs update data in its bins and communicate the updates to the application running on the controller and to the communication module. The communication module then responds with a success or failure message to the client.
This figure shows the path of read and write messages.
Figure 43
Message Flow Between Triconex Controller and Client
198
Appendix D
TSAA Protocol
Performance Factors
Factors which affect performance include: communication bus speed, the amount of aliased data and scan time, and network speed and loading. Read requests are typically processed in 10 to 50 milliseconds because the communication module responds with data from its bins, without communicating with the MPs. Write requests depend on scan time because the request must be communicated to and from the MPs.
Communication Bus Speed

The communication bus speed determines the speed at which data is communicated between the MPs and communication modules. If the amount of aliased data updated by the MPs is too large for a single scan, it may take several scans to update the aliased data stored in the communication modules.
Controller Version Tricon v9.0v9.5 Tricon v9.6 and later Speed/Bytes Per Second 20,000 100,000
Amount of Aliased Data and Scan Time

The amount of aliased data and scan time can affect the data communication timing because the MPs send updated data to the communication modules after each scan. If the amount of aliased data is large and the scan time is small, it may require several scans to update all the bins in the communication module. The number of bytes of aliased data is calculated as follows: Each group of eight or fewer contiguous BOOL data equals one byte. Each DINT or REAL data equals four bytes.
Use this formula to determine whether the data can be updated in a single scan: Bytes of aliased data must be bus speed factor times scan time This table includes examples.
Controller Version Tricon v9.0v9.5 Tricon v9.6 and later Communication Bus Factor 20 100 Scan Time (in ms) 100 150 Data can be Updated in a Single Scan if bytes of aliased data are
2000 15000
Network Speed and Loading

Network communication speeds are 10 to 100 megabits-per-second, which means that data transfer between the communication module and client is not usually affected by the physical network.
199
A 10-megabit-per-second Ethernet network with fewer than 15 nodes (less than 20 percent loading) should not experience throughput problems. (Network loading is the portion of the total network capacity that is currently being used.)
Performance Data
The performance data in this section indicates the type of performance you can anticipate. Actual performance will vary depending on the number of nodes on the network, the message size, and the client hardware and software. The network used for testing included the following two nodes: a Tricon controller with two chassis, and a 486 PC (33 MHz) for ACM and NCM or a Pentium 4 PC (1.4 GHz) for TCM. The scan time for the Tricon system was 100 milliseconds. The PC used UDP/IP protocols and a sample application program.
Connection Performance
The connection was immediately followed by a disconnect. This operation was repeated 2,000 times in a tight loop. The time was measured by reading the PC clock before and after the loop. The time required for ACM and NCM to perform a connect followed by a disconnect was 28 milliseconds for UDP. For TCM, the time required perform a connect followed by a disconnect was 26 milliseconds for UDP.
Read Performance
Read performance was measured by using READ_TRICON_DATA (message type 11) and READ_TRICON_RSP (message type 12). In the test, a connection was opened, the PC clock was read, and the read request was executed in a tight loop 2,000 times followed by a PC clock read and a disconnect. The requests were for bin 12 (8 values) and bin 7 (130 values) with 4 bytes per value. This table identifies an average read response time which includes the client request processing, network transmission time, and communication module processing. The average read time does not include the time to make the initial connection time between the client PC and Triconex controller.
Controller/ Communication Module Tricon ACM or NCM Tricon TCM Number of Bytes 502 502 Average Read Time 19 milliseconds 1 milliseconds
200
Appendix D
TSAA Protocol
Write Performance
Write performance was measured using WRITE_TRICON_DATA (message type 3) and WRITE_TRICON_DATA_RSP (message type 4). In this test, a connection was opened, the PC clock was read, and a write request and response was executed in a tight loop 200 times followed by a PC clock read and a disconnect. The requests were for bin 12 (8 values) and bin 10 (30 values) with 4 bytes per value. This table identifies an average write response time which includes the client request processing, network transmission time, communication bus time, and MP response processing. The average write time does not include the time to make the initial connection time between the client PC and Triconex controller.
Controller/ Communication Module Tricon ACM or NCM Tricon TCM Number of Bytes 120 120 Average Write Time 232 milliseconds 145 milliseconds
Response Codes
201
Response Codes
Every response sent by a Triconex controller in reply to an external device includes a code which indicates the result of the request. A response code of zero (0) indicates the message was successful. Other codes indicate specific errors.
Code 0 1 2 3 Description Request was successful. No buffer available to process the request. Retry the request. Bin number specified in the request was not in the range from 0 to12. The Triconex communication module is busy processing previous requests and cannot accept another request. This can happen if more than four WRITE_TRICON_DATA requests are outstanding at one time. No MP is running. TSX has rejected the request. The subReason field contains the specific reason. Request to TSX timed out. Invalid response from TX. Message was too big. Offset or numberOfValues in the request was invalid. No control program (TriStation application). Read-only port. Bad SOE number. Invalid SOE type. Invalid SOE state.
4 5 6 7 8 9 10 11 236 237 238
202
Appendix D
TSAA Protocol
E
Modbus Protocol
Overview 204 Message Response Time 205 Modbus Messages 207 Modbus Functions 213 Transmission Errors and Exception Conditions 223
204
Appendix E
Modbus Protocol
Overview
This appendix provides detailed information about Modbus protocol, which is a communication protocol used with serial ports to transmit data between a Modbus master and slave. Modbus protocol includes functions which define the message format for the query and response.
Query-Response Sessions
Modbus communication is a query-response session, in which the Modbus master initiates a query and a Modbus slave responds. In Modbus communication, a serial link transmits data in both directions, but in only one direction at a time. A query-response session consists of these actions: The master sends a query to a slave. The master starts a fail-safe timer while it waits for the slave response. Typical slave response time is in hundreds of milliseconds. The slave returns a response to the master. The master waits until it has received the response from the slave before sending another query. If there is a slave response timeout, the master will retry the query. The number of retries and the timeout interval is configured by the MBCTRL function block.
Message Response Time
205
Message Response Time

This section explains how to estimate the message response time, which is the total time for preparing, transmitting, receiving, and processing a Modbus query. Function blocks that are the least and most affected by scan time increases are also identified in this section. Topics include: Determining Message Response Time on page 205 Modbus Functions and Scan Time on page 206
Determining Message Response Time

This table explains how to estimate the number of milliseconds required for the message response time on a Triconex controller acting as a Modbus slave.
Modbus Operation Prepare Query (master) Transmit Query (master) Receive and Process Query Equation or Constraints Varies depending on the specific Modbus function (message) and any other program processing (1000 Baud Rate) x Bits per Characters x Number of Characters Tricon EICM or TCM slave: Writes: 3 x Scan Time Reads: 10 milliseconds Trident MP slave: Writes: 3 x Scan Time Reads: 2 x Scan Time Trident CM slave: Writes: 3 x Scan Time Reads: 10 milliseconds Transmit Response (slave) (in milliseconds) Process Response (master) (in milliseconds) Time-Out and Retry Values (1000 Baud Rate) x Bits per Characters x Number of Characters Depends on customer-provided equipment performance. Varies depending on settings for the MBCTRL function block, which determines the time-out and retry values which can increase the message time. Message Response Time = the sum of all the results.
206
Appendix E
Modbus Protocol
Modbus Functions and Scan Time

Modbus performance degrades slightly as the scan time of the controller increases. When the controller acts as a slave, the functions most affected by scan time increases are: Force Single Coil (Function Code 05) on page 217 Preset Single Register (Function Code 06) on page 218 Force Multiple Coils (Function Code 15) on page 221 Preset Multiple Registers (Function Code 16) on page 222
The functions least affected by scan time increases are: Read Coil Status Function (Function 01) on page 213 Read Input Status (Function 02) on page 214 Read Holding Registers (Function Code 03) on page 215 Read Input Registers (Function Code 04) on page 216
Modbus Messages
207
Modbus Messages
This section describes the Modbus messages (query and response functions) supported by Triconex communication modules. The serial ports on Triconex communication modules support several Modbus message formats and functions (queries and responses). Topics include: Communication Modes on page 207 Function Names and Aliases on page 208 Modbus Message Formats on page 208 Sample Query and Response Messages on page 211 Modbus Message Lengths on page 212
Communication Modes
A Modbus serial link must use either the RTU or ASCII mode of communication. If both modes are available, you should choose RTU because it is more efficient and robust than ASCII. Each serial port can use a different communication mode, assuming that each port is connected to a separate Modbus master or slave device. If you configure a port for combination Modbus master and slave operation, you must use RTU mode.
RTU Mode
In RTU mode, data is sent in 8-bit binary characters. Gaps between characters cannot exceed three character times (the time it takes to send a character). RTU mode uses a 16-bit cyclic redundancy check (CRC) to detect transmission errors.
ASCII Mode
In ASCII mode, data is transmitted in pairs of ASCII characters. The first character is the ASCII representation of the most significant 4 bits of the corresponding RTU character. The second character is the ASCII representation of the least significant 4 bits of the corresponding RTU character. For example, the RTU character 010011112 (4F16) is sent as the two ASCII characters 4 and F (3416 and 4616). Each ASCII message has a colon at the beginning and a carriage return and line feed at the end. Gaps between characters in an ASCII message are not significant.
208
Appendix E
Modbus Protocol
Function Names and Aliases

The starting address field of a Modbus message ranges from zero to one less than the number of coils or registers available. A serial port of a Trident or Tricon communication module maps the Modbus starting address field to an alias by adding a constant determined by the function code, as shown in this table.
Function Name Read Coil Status Read Input Status Read Holding Registers Read Input Registers Force Single Coil Preset Single Register Read Exception Status Loop Back Diagnostic Test Force Multiple Coils Preset Multiple Registers Code 01 02 03 04 05 06 07 08 15 16 Coil or Register Coil Coil Register Register Coil Register Coil Register Coil Register Constant 1 10001 40001 30001 1 40001 n/a n/a 1 40001
Modbus Message Formats

For each Modbus function, the message formats for RTU and ASCII modes are shown below.
Figure 44
Modbus Message Formats for RTU and ASCII Modes
Message Header Field (ASCII Only)

The Message Header in ASCII mode is a colon (:) and is required. There is no message header in RTU mode.
Modbus Messages
209
Station Address Field

The Station Address field identifies the station to which a query is directed or the station that is sending a response. In RTU mode, the station address has one character (eight bits). In ASCII mode, the station address has two characters. The range for station addresses is 1 through 247. Each station connected to a Modbus serial link must have a unique address. Station address 0 (zero) is the broadcast address and addresses all slaves. When a slave receives a query with the broadcast address, the slave processes the query but does not send a response.
Function Code Field

The Function Code field identifies the operation to be performed (the query), or the operation that was performed (the response). If the most significant bit of the function code in a response is 1, the response is an exception response. For more information, see Transmission Errors on page 223.
Data Fields
The Data fields contain information that is specific to the query or response. The length of the data varies, depending on the function code.
Checksum Field (CRC or LRC)

The Checksum field is a 16-bit word which is a CRC in RTU mode or an LRC in ASCII mode. The error check is performed by both the transmitting and the receiving units to detect transmission errors. For more information about error checking, see Transmission Errors on page 223. The following sections describe the error check calculations that are performed for CRC and LRC.
CRC Error Check RTU Mode

During a CRC error check, the CRC-16 polynomial is used to compute a checksum for the entire message. The CRC-16 polynomial is: x16 + x15 +x2 + 1 The CRC is computed across the station address, the function code, and the data and appended to the end of the message.
LRC Error Check ASCII Mode

The LRC checksum is an 8-bit binary number represented and transmitted as two ASCII hexadecimal characters. The checksum is produced in this manner: The hex characters that comprise the content of a message are converted to binary notation. The colon, carriage return, and line feed are ignored. The binary characters are summed without wrap-around carry. The resulting sum is negated.
210
Appendix E
Modbus Protocol
This table shows how to calculate the LRC for the sample message shown in Sample Query and Response Messages on page 211.
Message Content Address Function Code Starting Address (H.O.) Starting Address (L.O.) Quantity of Points (H.O.) Quantity of Points (L.O.) 0 0 0 1 0 2 2 1 0 3 0 5 + Checksum Calculation 0000 0000 0000 0001 0000 0010 0011 Ones-Complement: Add 1: Twos-Complement: Error Check + 1100 0000 1100 C 0010 0001 0000 0011 0000 0101 1011 0100 0001 0101 5
CR Field and LF Field (ASCII Only)

The CR field contains an ASCII carriage return and the LF field contains an ASCII line feed.
Modbus Messages
211
Sample Query and Response Messages

This table shows the content of a sample query and response in RTU and ASCII modes. The query is a Read Input Status (Function 02) requesting 37 (2516) points starting at point 20 (1316 + 1). The response packs the 37 points into five 8-bit bytes, and clears the three high-order bits of the last byte.
Query Message Header Station Address Function Code Starting Address (High Order) Starting Address (Low Order) Number of Points (High Order) Number of Points (Low Order) Error Check None 0000 0000 0000 0001 0000 0010 0000 0010 Trailer Response Message Header Station Address Function Code Byte Count Data Byte 1 Data Byte 2 Data Byte 3 Data Byte 4 Data Byte 5 Error Check None RTU None 0000 0000 0000 11001 0110 1011 0000 0001 0000 1111 Trailer None 0010 0001 0101 11012 1011 0010 1110 1011 0100 1111 CR LF : 0 0 0 C 6 B 0 1 E 2 1 5 D B 2 E B 5 0010 0001 0000 0011 0000 0101 1100 0111 CR LF ASCII RTU : 0 0 0 1 0 2 C 2 1 0 3 0 5 5 ASCII
1. The underscored digit indicates that Coil #27 is in the On state. 2. The underscored digit indicates that Coil #20 is in the On state.
212
Appendix E
Modbus Protocol
Modbus Message Lengths

The length of a Modbus message depends on the function being used and whether the message is a query or a response. This table shows the Modbus query message lengths per function:
Function Code 01 02 03 04 05 06 15 16 Query Read Coil Status Read Input Status Read Holding Registers Read Input Registers Force Single Coil Preset Single Register Force Multiple Coils Preset Multiple Registers Number of RTU Characters 8 8 8 8 8 8 9 + (1 per 8 coils) 9 + (2 per register) Number of ASCII Characters 17 17 17 17 17 17 19 + (2 per 8 coils) 19 + (4 per register)
This table shows the Modbus response message lengths per function:
Function Code 01 02 03 04 05 06 15 16 Response Read Coil Status Read Input Status Read Holding Registers Read Input Register Force Single Coil Preset Single Register Force Multiple Coils Preset Multiple Registers Number of RTU Characters 5 + (1 per 8 coils) 5 + (1 per 8 coils) 5 + (2 per register) 5 + (2 per register) 8 8 8 8 Number of ASCII Characters 11 + (2 per 8 coils) 11 + (2 per 8 coils) 11 + (4 per register) 11 + (4 per register) 17 17 17 17
Modbus Functions
213
Modbus Functions
This section includes details on Modbus functions. Functions include: Read Coil Status Function (Function 01) on page 213 Read Input Status (Function 02) on page 214 Read Holding Registers (Function Code 03) on page 215 Read Input Registers (Function Code 04) on page 216 Force Single Coil (Function Code 05) on page 217 Preset Single Register (Function Code 06) on page 218 Read Exception Status (Function Code 07) on page 219 Loop-Back Diagnostic Test (Function 08) on page 220 Force Multiple Coils (Function Code 15) on page 221 Preset Multiple Registers (Function Code 16) on page 222
Read Coil Status Function (Function 01)

Query Format
The Read Coil Status query requests the On/Off status of a group of logic coils from a station. You can request the status of as many as 2,000 coils with each query, but some Modbus devices have lower limits. The coils are numbered starting at 0; for example, coil 0 is alias 1, coil 1 is alias 2, and so forth. The Read Coil Status query is also known as the Read Output Status query.
RTU Mode
Bytes
7 CRC
Station 0000 0001 Address
Starting Address
Number of Coils
ASCII Mode
Bytes
1 2 3
4 5 0 1
10 11 12 13 14 15 16 17 Number of Coils LRC CR LF
Station Address
Starting Address
Response Format
The Read Coil Status response data is packed with one bit for each coil, where 1=On, and 0=Off. The low-order bit of the first RTU character contains the status of the first coil. For coil quantities that are not even multiples of eight, the last RTU character is zero-filled at the high-order end.
214
Appendix E
Modbus Protocol
Read Input Status (Function 02)

Query Format
The Read Input Status function operates in the same manner as Read Coil Status (Function Code 01), except that the status of digital inputs is obtained. Inputs are also numbered starting at 0. For example, input status 0 is alias 10001, input status 1 is alias 10002, and so forth. You can request the status of as many as 2,000 coils with each query, but some Modbus devices have lower limits.
Response Format
Modbus Functions
215
Read Holding Registers (Function Code 03)

Query Format
The Read Holding Registers query requests the binary content of holding registers from a station. You can request the status of as many as 125 registers with each query, but some Modbus devices have lower limits. The registers are numbered beginning with 0. For example, register 0 is alias 40001, register 1 is alias 40002, and so forth. The Read Holding Registers query is also known as the Read Output Registers query.
Response Format
The Read Holding Registers response data consists of two bytes for each register queried, with the binary content right-justified. The leftmost character includes the high-order bits, and the rightmost character includes the low-order bits.
216
Appendix E
Modbus Protocol
Read Input Registers (Function Code 04)

Query Format
The Read Input Registers function operates in the same manner as the Read Holding Registers query (Function Code 03), except that it obtains the status of input registers. You can request the status of as many as 125 registers with each query, but some Modbus devices have lower limits. The registers are numbered beginning with 0. For example, register 0 is alias 30001, register 1 is alias 30002, and so forth.
Response Format
Modbus Functions
217
Force Single Coil (Function Code 05)

Query Format
The Force Single Coil function turns a single coil On or Off, depending on its current state. Because the slave is actively scanning, it can also alter the state of the coil (unless the coil is disabled). Coils are numbered beginning with 0; for example, coil 0 is alias 1, coil 1 is alias 2, and so forth. A coil value of 65,280 (FF0016) turns the coil On, and a coil value of zero (000016) turns the coil Off. All other values are illegal and do not affect the coil. If the query contains legal values, the slave responds after the coil state has been altered.
Response Format
218
Appendix E
Modbus Protocol
Preset Single Register (Function Code 06)

The Preset Single Register function modifies the content of one holding register. Because the slave is actively scanning, it can also alter the registers content. Register values are 16 bits. Holding registers are numbered starting at 0; for example, register 0 is alias 40001, register 1 is alias 40002.
Query Format
Response Format
Modbus Functions
219
Read Exception Status (Function Code 07)

Query Format
The Read Exception Status function returns the status of eight coils from the slave application running in the controller. Which coils and what they represent depends on the slave. When a serial port, configured as a slave, responds to this query, it sends the status of the first eight coils (aliases 00001 through 00008) defined in the application. Coils are numbered from 0; for example, coil 0 is alias 1, coil 1 is alias 2, and so forth. The status of each coil is packed in the data field, one bit for each coil (1=On, 0=Off). You can program these coils to hold any type of information; for example, machine on or off, heads retracted, safeties satisfied, and receipt-inprocess error conditions. Note A TCM serial port configured as a Modbus master cannot use the Read Exception Status function.
Response Format
220
Appendix E
Modbus Protocol
Loop-Back Diagnostic Test (Function 08)

Query Format
The Loop-Back Diagnostics Test query tests the communications link between the Modbus master and slave. This query does not affect point values in the slave. When the serial port acting as a slave receives this query, it re-transmits the query as the response.
Response Format
Note
A EICM or TCM serial port configured as a Modbus Master cannot use the Loop-Back Diagnostic Test function.
Modbus Functions
221
Force Multiple Coils (Function Code 15)

Query Format
The Force Multiple Coils query sets each coil in a consecutive block of coils to the specified state (On or Off) regardless of whether the coils are enabled or disabled. Because the slave is actively scanning, it can also alter the state of a coil (unless it is disabled). Coils are numbered from 0; for example, coil 0 is alias 1, coil 1 is alias 2, and so forth. The status of each coil is packed in the data field, one bit for each coil (1=On, 0=Off). A single Force Multiple Coils query can set a maximum of 128 coils. The query-response time required by some Modbus masters might require a much smaller quantity.
Response Format
222
Appendix E
Modbus Protocol
Preset Multiple Registers (Function Code 16)

Query Format
The Preset Multiple Registers query can change the contents of a maximum of 60 consecutive holding registers, however, some Modbus devices have lower limits. Because the slave is actively scanning, it can also alter the state of the registers (unless they are disabled). The values are provided in binary code up to the maximum valid register value of the controller (16-bit for Trident). Unused high-order bits must be set to zero. The registers are numbered beginning with 0; for example, register 0 is alias 40001, register 1 is alias 40002, and so forth.
Response Format
Transmission Errors and Exception Conditions
223

During Modbus communication, transmission errors and exception conditions can occur. Transmission errors do not cause exception conditions and are not acknowledged by Modbus slaves. Programming and operation errors do cause exception conditions which elicit exception responses from slaves. Topics include: Transmission Errors on page 223 Exception Conditions on page 223 Exception Responses on page 224
Transmission Errors
The most frequent cause of transmission errors is noise. Noise sources include improperly installed or broken connectors, damaged cables, electrical equipment such as generators and elevators, and lightning. Transmission errors can be detected through the use of character framing, parity checking, and redundancy checking. When a slave detects a transmission error, it does not act on or respond to the message. The master assumes a communications error has occurred if there is no response within a specified time, usually three seconds. Parity checking helps detect single-bit transmission errors. However, if there are two errors within a single character, parity checking cannot detect a change. For example, if 1100 0100 is distorted to 1111 0100, the number of 1 bits in the data is still odd. Modbus protocol provides several levels of error checking in order to assure the accuracy of data transmission. To detect multiple bit errors, the system uses cyclic redundancy check (CRC) for RTU mode, or longitudinal redundancy check (LRC) for ASCII mode. For more information, see Checksum Field (CRC or LRC) on page 209.
Exception Conditions
If a master detects an exception in a response to a query or does not receive a response, it takes appropriate actions, which usually includes re-transmitting the query. This table lists exception conditions that are returned by the slave if a programming or operation error causes a master to send an incorrect query.
Exception Condition Query Message CRC or LRC Error Query Function Code Error Query Address Error Description The slave does not respond, because the error could be in the station address. The master uses its response fail-safe timer to recover. The slave sends an Illegal Function (01) response code when it detects an error in the function code field. The slave sends an Illegal Data Address (02) response code when it detects an error in the starting address field.
224
Appendix E
Modbus Protocol
Exception Condition Query Data Error Main Processors Not Communicating
Description The slave sends an Illegal Data Value (03) response code when it detects an error in the data field. This exception applies only to serial ports configured as slaves. If the slave port receives a query requiring a data exchange and it cannot communicate with the Main Processors, it sends a Busy, Reject Message (06) response code and turns off the Active indicator on the communication module. The slave port sends a Busy, Reject Message (06) response code if a master sends one of these queries and the slave port is not enabled for remote (external) writes: Force Single Coil (Function Code 05) Preset Single Register (Function Code 06) Force Multiple Coils (Function Code 15) Preset Multiple Registers (Function Code 16)
Remote Write Disabled
Exception Responses
When a slave detects an exception condition, it sends a response message to the master consisting of the slaves station address, function code, error code, and error-check fields. To indicate that the message is an exception response, the slave sets the high-order bit of the function code to 1. The example shows an exception response to a Preset Multiple Registers query.
Sample Query
225
Sample Exception Response
Exception Response Codes

This table lists exception response codes which are sent by the slave after an invalid query.
Code 01 02 03 04 05 06 07 08 Name Illegal Function Illegal Data Address Illegal Data Value Failure in Associated Device Description The requested function is not in the slaves repertoire. The alias in the query does not exist in the slave. The value is not in the range allowed for the alias. The slave failed to respond to a message or an error that occurred in the controller. When a master receives this response code, it must issue a supervisory alert. A slave port does not send this exception response code. The query was received without error, but the slave cannot comply. A slave port does not send this exception response code. A slave port does not send this exception response code.
Acknowledge Busy, Rejected Message Negative Acknowledge Memory Parity Error
226
Appendix E
Modbus Protocol
F
Tricon System Aliases
Overview of Tricon Aliases and Variables 228 Main Processor Status Aliases 230 Chassis Upper Power Supply Fault Aliases 231 Chassis Upper Power Supply Fault Aliases 231 Chassis Lower Power Supply Fault Status 232 Chassis Requires Maintenance Aliases 233 Chassis Has Active Board with Fault Aliases 234 Slot Status 234 Aliases for ACM, NCM, and TCM Network Status 284 Aliases for System-Wide Information 285
228
Appendix F
Overview of Tricon Aliases and Variables

System aliases are used in the place of system variables to access data in a Tricon controller from a Modbus master or another external computer. System aliases provide the same information to external hosts that system variables provide to TriStation 1131 applications. There are three general classes of variables and aliases used by a Tricon system: input/output (I/O), memory, and system. I/O aliases are automatically assigned by the Tricon when a user installs or moves a module in a chassis. Memory aliases must be assigned by the programmer according to the convention shown in this section. System aliases are predefined by Triconex and cannot be changed.
Alias numbers consist of five digits according to this convention.

Digit 1 (Modbus data type) 0 = Read/write discrete (coil) 1 = Read-only discrete (input coil) 3 = Read-only register (input register) 4 = Read/write register (holding register) Digits 2 to 5 Address of variable
Tricon Modbus Alias Ranges

This table lists the Modbus alias ranges for Tricon. An asterisk (*) means Modbus SOE data can be retrieved through the EICM or TCM.
Class Input Input Input Output Output Memory Memory Memory System Memory System Memory Memory Point Type Discrete Integer Real Discrete Integer Discrete Discrete Integer Integer Integer Integer Real Real Message Type Read-only Read-only Read-only Read/write Read/write Read/write Read-only Read-only Read-only Read/write Read/write Read-only Read/write Alias Range 10001-12000 30001-31000 32001-32120 00001-02000 40001-40250 02001-04000 12001-14000 31001-32000 38001-38999 40251-41000 48001-48002 33001-34000 41001-42000 AutoAssigned UserAssigned PreDefined
Overview of Tricon Aliases and Variables
229
Class System System Memory Memory
Point Type Discrete Integer Integer Discrete
Message Type Read-only Read-only Read-only Read-only
Alias Range 14001-19999 39001-39999 38000-39630 18001-19999
AutoAssigned
UserAssigned
PreDefined
System Variables Naming Convention

System variables are named according to this convention (applicable only for those systems using TriStation MSW).
Characters 1 and 2 $S Characters 3 and 4 Chassis number Characters 5 and 6 Physical slot number Character 8 A = Active indicator B = Load/fuse indicator F = Fault indicator I = Installed P = Pass indicator
To determine a system variable name, first determine the logical slot number, then look up its physical slot number in the appropriate chassis type as shown here. For example, the system variable name for the Pass Indicator in Chassis 1, Slot 4 is $S0104P. For all slots except the MP, RXM and COM slots, one logical slot number corresponds to two physical slot numbers. The physical slot number is used to determine the system variable name for that slot.
High-Density Logical and Physical Slot Numbers

This table identifies the logical and physical slot numbers for the high-density chassis.
Main Chassis and RXM Logical Slot Comm or Blank 2 3 4 5 6 7 Physical Slot 4 5, 6 7, 8 9, 10 11, 12 13, 14 15, 16 1 2 3 4 5 6 7 8 Expansion Logical Slot Physical Slot 1, 2 3, 4 5, 6 7, 8 9, 10 11, 12 13, 14 15, 16
230
Appendix F
Low-Density Logical and Physical Slot Numbers

This table identifies the logical and physical slot numbers for the low-density chassis.
Main Chassis and RXM Logical Slot 1 2 3 4 Physical Slot 5,6 7, 8 9, 10 11, 12 Expansion Logical Slot 1 2 3 4 5 Physical Slot 3, 4 5, 6 7, 8 9, 10 11, 12
Main Processor Status Aliases

This table lists the system aliases for the MP status.
Variable $MPMain $MPBad $ArithE $DivBy0 $OvrFlw $UdrFlw $BadPrm $PwrUp $FrstSc EMP-A pass EMP-A fault EMP-A active EMP-A maint2 EMP-A maint1 EMP-B pass EMP-B fault EMP-B active EMP-B maint2 EMP-B maint1 Alias 14001 14002 14003 14004 14005 14006 14008 14009 14010 14011 14012 14013 14014 14015 14017 14018 14019 14020 14021 Description Main Processor fault - Main Chassis alarm ON 2 EMPs faulted - Tricon in simplex mode Arithmetic error during scan Integer or real divided by zero Floating-point overflow Floating-point underflow Parameter out of range All EMPs reset - first scan after power-up First scan after power-up or halt Pass indicator of Main Processor A Fault indicator of Main Processor A Active indicator of Main Processor A Maintenance 2 on Main Processor A Maintenance 1 on Main Processor A Pass indicator of Main Processor A Fault indicator of Main Processor B Active indicator of Main Processor B Maintenance 2 on Main Processor B Maintenance 1 on Main Processor B
EICM Status Aliases
231
EMP-C pass EMP-C fault EMP-C active EMP-C maint2 EMP-C maint1 $IOMain $IOBad $WRTENB
14023 14024 14025 14026 14027 14029 14030 14031
Pass indicator of Main Processor C Fault indicator of Main Processor C Active indicator of Main Processor C Maintenance 2 on Main Processor C Maintenance 1 on Main Processor C 1 Comm bus leg or 1 MP not functioning I/O module is running in simplex mode Writes from external devices are enabled.
EICM Status Aliases

This table lists the aliases for the EICM module status.
Variable $rdy05 $rdy10 $ovfl05 $ovfl10 Alias 14229 14234 14245 14250 Description Printer ready Port 05 Printer ready Port 10 Printer overflow Port 05 Printer overflow Port 10
Chassis Upper Power Supply Fault Aliases

This table lists the aliases that identify whether there is a chassis upper power supply fault.
Variable $R01V1L $R02V1L $R03V1L $R04V1L $R05V1L $R06V1L $R07V1L $R08V1L $R09V1L $R10V1L $R11V1L Alias 14162 14163 14164 14165 14166 14167 14168 14169 14170 14171 14172 Description Chassis 1 Upper Power Supply Fault Chassis 2 Upper Power Supply Fault Chassis 3 Upper Power Supply Fault Chassis 4 Upper Power Supply Fault Chassis 5 Upper Power Supply Fault Chassis 6 Upper Power Supply Fault Chassis 7 Upper Power Supply Fault Chassis 8 Upper Power Supply Fault Chassis 9 Upper Power Supply Fault Chassis 10 Upper Power Supply Fault Chassis 11 Upper Power Supply Fault
232
Appendix F
Variable $R12V1L $R13V1L $R14V1L $R15V1L
Alias 14173 14174 14175 14176
Description Chassis 12 Upper Power Supply Fault Chassis 13 Upper Power Supply Fault Chassis 14 Upper Power Supply Fault Chassis 15 Upper Power Supply Fault
Chassis Lower Power Supply Fault Status

This table lists the aliases that identify whether there is a chassis lower power supply fault.
Variable $R01V2L $R02V2L $R03V2L $R04V2L $R05V2L $R06V2L $R07V2L $R08V2L $R09V2L $R10V2L $R11V2L $R12V2L $R13V2L $R14V2L $R15V2L Alias 14178 14179 14180 14181 14182 14183 14184 14185 14186 14187 14188 14189 14190 14191 14192 Description Chassis 1 Lower Power Supply Fault Chassis 2 Lower Power Supply Fault Chassis 3 Lower Power Supply Fault Chassis 4 Lower Power Supply Fault Chassis 5 Lower Power Supply Fault Chassis 6 Lower Power Supply Fault Chassis 7 Lower Power Supply Fault Chassis 8 Lower Power Supply Fault Chassis 9 Lower Power Supply Fault Chassis 10 Lower Power Supply Fault Chassis 11 Lower Power Supply Fault Chassis 12 Lower Power Supply Fault Chassis 13 Lower Power Supply Fault Chassis 14 Lower Power Supply Fault Chassis 15 Lower Power Supply Fault
Chassis Requires Maintenance Aliases
233
Chassis Requires Maintenance Aliases

This table lists the aliases that identify whether the chassis requires maintenance.
Variable $R01Mnt $R02Mnt $R03Mnt $R04Mnt $R05Mnt $R06Mnt $R07Mnt $R08Mnt $R09Mnt $R10Mnt $R11Mnt $R12Mnt $R13Mnt $R14Mnt $R15Mnt Alias 14194 14195 14196 14197 14198 14199 14200 14201 14202 14203 14204 14205 14206 14207 14208 Description Chassis 1 Requires Maintenance Chassis 2 Requires Maintenance Chassis 3 Requires Maintenance Chassis 4 Requires Maintenance Chassis 5 Requires Maintenance Chassis 6 Requires Maintenance Chassis 7 Requires Maintenance Chassis 8 Requires Maintenance Chassis 9 Requires Maintenance Chassis 10 Requires Maintenance Chassis 11 Requires Maintenance Chassis 12 Requires Maintenance Chassis 13 Requires Maintenance Chassis 14 Requires Maintenance Chassis 15 Requires Maintenance
234
Appendix F
Chassis Has Active Board with Fault Aliases

This table lists the aliases that identify whether the chassis has an active board with a fault.
Variable $R01Bad $R02Bad $R03Bad $R04Bad $R05Bad $R06Bad $R07Bad $R08Bad $R09Bad $R10Bad $R11Bad $R12Bad $R13Bad $R14Bad $R15Bad Alias 14210 14211 14212 14213 14214 14215 14216 14217 14218 14219 14220 14221 14222 14223 14224 Description Chassis 1 Has Active Board with Fault Chassis 2 Has Active Board with Fault Chassis 3 Has Active Board with Fault Chassis 4 Has Active Board with Fault Chassis 5 Has Active Board with Fault Chassis 6 Has Active Board with Fault Chassis 7 Has Active Board with Fault Chassis 8 Has Active Board with Fault Chassis 9 Has Active Board with Fault Chassis 10 Has Active Board with Fault Chassis 11 Has Active Board with Fault Chassis 12 Has Active Board with Fault Chassis 13 Has Active Board with Fault Chassis 14 Has Active Board with Fault Chassis 15 Has Active Board with Fault
Slot Status
These tables list the aliases that identify the slot status.
Chassis 1 Pass Indicator Aliases

This table lists the aliases that identify the Pass indicators for chassis 1.
Variable $S0104P $S0105P $S0106P $S0107P $S0108P Alias 14420 14421 14422 14423 14424 Description Chassis 1 Slot 4 Pass Indicator Chassis 1 Slot 5 Pass Indicator Chassis 1 Slot 6 Pass Indicator Chassis 1 Slot 7 Pass Indicator Chassis 1 Slot 8 Pass Indicator
Slot Status
235
Chassis 1 Fault Indicator Aliases

This table lists the aliases that identify the Fault indicators for chassis 1.
Variable $S0104F $S0105F $S0106F $S0107F $S0108F $S0109F $S0110F $S0111F $S0112F $S0113F $S0114F $S0115F $S0116F Alias 14436 14437 14438 14439 14440 14441 14442 14443 14444 14445 14446 14447 14448 Description Chassis 1 Slot 4 Fault Indicator Chassis 1 Slot 5 Fault Indicator Chassis 1 Slot 6 Fault Indicator Chassis 1 Slot 7 Fault Indicator Chassis 1 Slot 8 Fault Indicator Chassis 1 Slot 9 Fault Indicator Chassis 1 Slot 10 Fault Indicator Chassis 1 Slot 11 Fault Indicator Chassis 1 Slot 12 Fault Indicator Chassis 1 Slot 13 Fault Indicator Chassis 1 Slot 14 Fault Indicator Chassis 1 Slot 15 Fault Indicator Chassis 1 Slot 16 Fault Indicator
Chassis 1 Active Indicator Aliases

This table lists the aliases that identify the Active indicators for chassis 1.
Variable $S0104A $S0105A $S0106A $S0107A $S0108A $S0109A $S0110A $S0111A $S0112A $S0113A $S0114A $S0115A $S0116A Alias 14452 14453 14454 14455 14456 14457 14458 14459 14460 14461 14462 14463 14464 Description Chassis 1 Slot 4 Active Indicator Chassis 1 Slot 5 Active Indicator Chassis 1 Slot 6 Active Indicator Chassis 1 Slot 7 Active Indicator Chassis 1 Slot 8 Active Indicator Chassis 1 Slot 9 Active Indicator Chassis 1 Slot 10 Active Indicator Chassis 1 Slot 11 Active Indicator Chassis 1 Slot 12 Active Indicator Chassis 1 Slot 13 Active Indicator Chassis 1 Slot 14 Active Indicator Chassis 1 Slot 15 Active Indicator Chassis 1 Slot 16 Active Indicator
236
Appendix F
Chassis 1 Load/Fuse Indicator Aliases

This table lists the aliases that identify the Load/Fuse indicators for chassis 1.
Variable $S0105B $S0106B $S0107B $S0108B $S0109B $S0110B $S0111B $S0112B $S0113B $S0114B $S0115B Alias 14469 14470 14471 14472 14473 14474 14475 14476 14477 14478 14479 Description Chassis 1 Slot 5 Load/Fuse Indicator Chassis 1 Slot 6 Load/Fuse Indicator Chassis 1 Slot 7 Load/Fuse Indicator Chassis 1 Slot 8 Load/Fuse Indicator Chassis 1 Slot 9 Load/Fuse Indicator Chassis 1 Slot 10 Load/Fuse Indicator Chassis 1 Slot 11 Load/Fuse Indicator Chassis 1 Slot 12 Load/Fuse Indicator Chassis 1 Slot 13 Load/Fuse Indicator Chassis 1 Slot 14 Load/Fuse Indicator Chassis 1 Slot 15 Load/Fuse Indicator
Chassis 1 Installed Aliases

This table lists the aliases that identify whether slots are installed for chassis 1.
Variable $S0104I $S0105I $S0106I $S0107I $S0108I $S0109I $S0110I $S0111I $S0112I $S0113I $S0114I $S0115I $S0116I Alias 14484 14485 14486 14487 14488 14489 14490 14491 14492 14493 14494 14495 14496 Description Chassis 1 Slot 4 Installed Chassis 1 Slot 5 Installed Chassis 1 Slot 6 Installed Chassis 1 Slot 7 Installed Chassis 1 Slot 8 Installed Chassis 1 Slot 9 Installed Chassis 1 Slot 10 Installed Chassis 1 Slot 11 Installed Chassis 1 Slot 12 Installed Chassis 1 Slot 13 Installed Chassis 1 Slot 14 Installed Chassis 1 Slot 15 Installed Chassis 1 Slot 16 Installed
Slot Status
237

Variable $S0201P $S0202P $S0203P $S0204P $S0205P $S0206P $S0207P $S0208P $S0209P $S0210P $S0211P $S0212P $S0213P $S0214P $S0215P $S0216P Alias 14513 14514 14515 14516 14517 14518 14519 14520 14521 14522 14523 14524 14525 14526 14527 14528 Description Chassis 2 Slot 1 Pass Indicator Chassis 2 Slot 2 Pass Indicator Chassis 2 Slot 3 Pass Indicator Chassis 2 Slot 4 Pass Indicator Chassis 2 Slot 5 Pass Indicator Chassis 2 Slot 6 Pass Indicator Chassis 2 Slot 7 Pass Indicator Chassis 2 Slot 8 Pass Indicator Chassis 2 Slot 9 Pass Indicator Chassis 2 Slot 10 Pass Indicator Chassis 2 Slot 11 Pass Indicator Chassis 2 Slot 12 Pass Indicator Chassis 2 Slot 13 Pass Indicator Chassis 2 Slot 14 Pass Indicator Chassis 2 Slot 15 Pass Indicator Chassis 2 Slot 16 Pass Indicator

Variable $S0201F $S0202F $S0203F $S0204F $S0205F $S0206F $S0207F $S0208F $S0209F $S0210F Alias 14529 14530 14531 14532 14533 14534 14535 14536 14537 14538 Description Chassis 2 Slot 1 Fault Indicator Chassis 2 Slot 2 Fault Indicator Chassis 2 Slot 3 Fault Indicator Chassis 2 Slot 4 Fault Indicator Chassis 2 Slot 5 Fault Indicator Chassis 2 Slot 6 Fault Indicator Chassis 2 Slot 7 Fault Indicator Chassis 2 Slot 8 Fault Indicator Chassis 2 Slot 9 Fault Indicator Chassis 2 Slot 10 Fault Indicator
238
Appendix F
Variable $S0211F $S0212F $S0213F $S0214F $S0215F $S0216F
Alias 14539 14540 14541 14542 14543 14544
Description Chassis 2 Slot 11 Fault Indicator Chassis 2 Slot 12 Fault Indicator Chassis 2 Slot 13 Fault Indicator Chassis 2 Slot 14 Fault Indicator Chassis 2 Slot 15 Fault Indicator Chassis 2 Slot 16 Fault Indicator

This table lists the aliases that identify the Active indicators for chassis 2.
Variable $S0201A $S0202A $S0203A $S0204A $S0205A $S0206A $S0207A $S0208A $S0209A $S0210A $S0211A $S0212A $S0213A $S0214A $S0215A $S0216A Alias 14545 14546 14547 14548 14549 14550 14551 14552 14553 14554 14555 14556 14557 14558 14559 14560 Description Chassis 2 Slot 1 Active Indicator Chassis 2 Slot 2 Active Indicator Chassis 2 Slot 3 Active Indicator Chassis 2 Slot 4 Active Indicator Chassis 2 Slot 5 Active Indicator Chassis 2 Slot 6 Active Indicator Chassis 2 Slot 7 Active Indicator Chassis 2 Slot 8 Active Indicator Chassis 2 Slot 9 Active Indicator Chassis 2 Slot 10 Active Indicator Chassis 2 Slot 11 Active Indicator Chassis 2 Slot 12 Active Indicator Chassis 2 Slot 13 Active Indicator Chassis 2 Slot 14 Active Indicator Chassis 2 Slot 15 Active Indicator Chassis 2 Slot 16 Active Indicator
Slot Status
239

This table lists the aliases that identify the Load/Fuse indicators for chassis 2.
Variable $S0201B $S0202B $S0203B $S0204B $S0205B $S0206B $S0207B $S0208B $S0209B $S0210B $S0211B $S0212B $S0213B $S0214B $S0215B $S0216B Alias 14561 14562 14563 14564 14565 14566 14567 14568 14569 14570 14571 14572 14573 14574 14575 14576 Description Chassis 2 Slot 1 Load/Fuse Indicator Chassis 2 Slot 2 Load/Fuse Indicator Chassis 2 Slot 3 Load/Fuse Indicator Chassis 2 Slot 4 Load/Fuse Indicator Chassis 2 Slot 5 Load/Fuse Indicator Chassis 2 Slot 6 Load/Fuse Indicator Chassis 2 Slot 7 Load/Fuse Indicator Chassis 2 Slot 8 Load/Fuse Indicator Chassis 2 Slot 9 Load/Fuse Indicator Chassis 2 Slot 10 Load/Fuse Indicator Chassis 2 Slot 11 Load/Fuse Indicator Chassis 2 Slot 12 Load/Fuse Indicator Chassis 2 Slot 13 Load/Fuse Indicator Chassis 2 Slot 14 Load/Fuse Indicator Chassis 2 Slot 15 Load/Fuse Indicator Chassis 2 Slot 16 Load/Fuse Indicator

This table lists the aliases that identify whether the slot is installed for chassis 2.
Variable $S0201I $S0202I $S0203I $S0204I $S0205I $S0206I $S0207I $S0208I $S0209I $S0210I Alias 14577 14578 14579 14580 14581 14582 14583 14584 14585 14586 Description Chassis 2 Slot 1 Installed Chassis 2 Slot 2 Installed Chassis 2 Slot 3 Installed Chassis 2 Slot 4 Installed Chassis 2 Slot 5 Installed Chassis 2 Slot 6 Installed Chassis 2 Slot 7 Installed Chassis 2 Slot 8 Installed Chassis 2 Slot 9 Installed Chassis 2 Slot 10 Installed
240
Appendix F
Variable $S0211I $S0212I $S0213I $S0214I $S0215I $S0216I
Alias 14587 14588 14589 14590 14591 14592
Description Chassis 2 Slot 11 Installed Chassis 2 Slot 12 Installed Chassis 2 Slot 13 Installed Chassis 2 Slot 14 Installed Chassis 2 Slot 15 Installed Chassis 2 Slot 16 Installed

Variable $S0301P $S0302P $S0303P $S0304P $S0305P $S0306P $S0307P $S0308P $S0309P $S0310P $S0311P $S0312P $S0313P $S0314P Alias 14609 14610 14611 14612 14613 14614 14615 14616 14617 14618 14619 14620 14621 14622 Description Chassis 3 Slot 1 Pass Indicator Chassis 3 Slot 2 Pass Indicator Chassis 3 Slot 3 Pass Indicator Chassis 3 Slot 4 Pass Indicator Chassis 3 Slot 5 Pass Indicator Chassis 3 Slot 6 Pass Indicator Chassis 3 Slot 7 Pass Indicator Chassis 3 Slot 8 Pass Indicator Chassis 3 Slot 9 Pass Indicator Chassis 3 Slot 10 Pass Indicator Chassis 3 Slot 11 Pass Indicator Chassis 3 Slot 12 Pass Indicator Chassis 3 Slot 13 Pass Indicator Chassis 3 Slot 14 Pass Indicator
Slot Status
241

Variable $S0301F $S0302F $S0303F $S0304F $S0305F $S0306F $S0307F $S0308F $S0309F $S0310F $S0311F $S0312F $S0313F $S0314F $S0315F $S0316F Alias 14625 14626 14627 14628 14629 14630 14631 14632 14633 14634 14635 14636 14637 14638 14639 14640 Description Chassis 3 Slot 1 Fault Indicator Chassis 3 Slot 2 Fault Indicator Chassis 3 Slot 3 Fault Indicator Chassis 3 Slot 4 Fault Indicator Chassis 3 Slot 5 Fault Indicator Chassis 3 Slot 6 Fault Indicator Chassis 3 Slot 7 Fault Indicator Chassis 3 Slot 8 Fault Indicator Chassis 3 Slot 9 Fault Indicator Chassis 3 Slot 10 Fault Indicator Chassis 3 Slot 11 Fault Indicator Chassis 3 Slot 12 Fault Indicator Chassis 3 Slot 13 Fault Indicator Chassis 3 Slot 14 Fault Indicator Chassis 3 Slot 15 Fault Indicator Chassis 3 Slot 16 Fault Indicator

This table lists the aliases that identify Active indicators for chassis 3.
Variable $S0301A $S0302A $S0303A $S0304A $S0305A $S0306A $S0307A $S0308A $S0309A $S0310A Alias 14641 14642 14643 14644 14645 14646 14647 14648 14649 14650 Description Chassis 3 Slot 1 Active Indicator Chassis 3 Slot 2 Active Indicator Chassis 3 Slot 3 Active Indicator Chassis 3 Slot 4 Active Indicator Chassis 3 Slot 5 Active Indicator Chassis 3 Slot 6 Active Indicator Chassis 3 Slot 7 Active Indicator Chassis 3 Slot 8 Active Indicator Chassis 3 Slot 9 Active Indicator Chassis 3 Slot 10 Active Indicator
242
Appendix F
Variable $S0311A $S0312A $S0313A $S0314A $S0315A $S0316A
Alias 14651 14652 14653 14654 14655 14656
Description Chassis 3 Slot 11 Active Indicator Chassis 3 Slot 12 Active Indicator Chassis 3 Slot 13 Active Indicator Chassis 3 Slot 14 Active Indicator Chassis 3 Slot 15 Active Indicator Chassis 3 Slot 16 Active Indicator

This table lists the aliases that identify Load/Fuse indicators for chassis 3.
Slot Status
243

Variable $S0301I $S0302I $S0303I $S0304I $S0305I $S0306I $S0307I $S0308I $S0309I $S0310I $S0311I $S0312I $S0313I $S0314I $S0315I $S0316I Alias 14673 14674 14675 14676 14677 14678 14679 14680 14681 14682 14683 14684 14685 14686 14687 14688 Description Chassis 3 Slot 1 Installed Chassis 3 Slot 2 Installed Chassis 3 Slot 3 Installed Chassis 3 Slot 4 Installed Chassis 3 Slot 5 Installed Chassis 3 Slot 6 Installed Chassis 3 Slot 7 Installed Chassis 3 Slot 8 Installed Chassis 3 Slot 9 Installed Chassis 3 Slot 10 Installed Chassis 3 Slot 11 Installed Chassis 3 Slot 12 Installed Chassis 3 Slot 13 Installed Chassis 3 Slot 14 Installed Chassis 3 Slot 15 Installed Chassis 3 Slot 16 Installed

Variable $S0401P $S0402P $S0403P $S0404P $S0405P $S0406P $S0407P $S0408P $S0409P $S0410P Alias 14705 14706 14707 14708 14709 14710 14711 14712 14713 14714 Description Chassis 4 Slot 1 Pass Indicator Chassis 4 Slot 2 Pass Indicator Chassis 4 Slot 3 Pass Indicator Chassis 4 Slot 4 Pass Indicator Chassis 4 Slot 5 Pass Indicator Chassis 4 Slot 6 Pass Indicator Chassis 4 Slot 7 Pass Indicator Chassis 4 Slot 8 Pass Indicator Chassis 4 Slot 9 Pass Indicator Chassis 4 Slot 10 Pass Indicator
244
Appendix F
Variable $S0411P $S0412P $S0413P $S0414P $S0415P $S0416P
Alias 14715 14716 14717 14718 14719 14720
Description Chassis 4 Slot 11 Pass Indicator Chassis 4 Slot 12 Pass Indicator Chassis 4 Slot 13 Pass Indicator Chassis 4 Slot 14 Pass Indicator Chassis 4 Slot 15 Pass Indicator Chassis 4 Slot 16 Pass Indicator

This table lists the aliases that identify Fault indicators for chassis 4.
Slot Status
245


Variable $S0401B $S0402B $S0403B $S0404B $S0405B $S0406B $S0407B $S0408B $S0409B $S0410B Alias 14753 14754 14755 14756 14757 14758 14759 14760 14761 14762 Description Chassis 4 Slot 1 Load/Fuse Indicator Chassis 4 Slot 2 Load/Fuse Indicator Chassis 4 Slot 3 Load/Fuse Indicator Chassis 4 Slot 4 Load/Fuse Indicator Chassis 4 Slot 5 Load/Fuse Indicator Chassis 4 Slot 6 Load/Fuse Indicator Chassis 4 Slot 7 Load/Fuse Indicator Chassis 4 Slot 8 Load/Fuse Indicator Chassis 4 Slot 9 Load/Fuse Indicator Chassis 4 Slot 10 Load/Fuse Indicator
246
Appendix F
Variable $S0411B $S0412B $S0413B $S0414B $S0415B $S0416B
Alias 14763 14764 14765 14766 14767 14768
Description Chassis 4 Slot 11 Load/Fuse Indicator Chassis 4 Slot 12 Load/Fuse Indicator Chassis 4 Slot 13 Load/Fuse Indicator Chassis 4 Slot 14 Load/Fuse Indicator Chassis 4 Slot 15 Load/Fuse Indicator Chassis 4 Slot 16 Load/Fuse Indicator
Chassis 4 Installed Slot Aliases

Slot Status
247


248
Appendix F
Alias 14827 14828 14829 14830 14831 14832

Slot Status
249


250
Appendix F
Alias 14875 14876 14877 14878 14879 14880

Slot Status
251


252
Appendix F
Alias 14939 14940 14941 14942 14943 14944

Slot Status
253


254
Appendix F
Alias 15003 15004 15005 15006 15007 15008

Slot Status
255


256
Appendix F
Alias 15051 15052 15053 15054 15055 15056

Slot Status
257


258
Appendix F
Alias 15115 15116 15117 15118 15119 15120

Slot Status
259

This table lists the aliases that identify Load/Fuse indicators for chassis 8.8

260
Appendix F
Alias 15163 15164 15165 15166 15167 15168

Slot Status
261


262
Appendix F
Alias 15227 15228 15229 15230 15231 15232

This table lists the aliases that identify Load/Fuse indicators for chassis 9.9
Slot Status
263


264
Appendix F
Alias 15291 15292 15293 15294 15295 15296

Slot Status
265


266
Appendix F
Alias 15339 15340 15341 15342 15343 15344

Slot Status
267


268
Appendix F
Alias 15403 15404 15405 15406 15407 15408

Slot Status
269


270
Appendix F
Alias 15451 15452 15453 15454 15455 15456

Slot Status
271


272
Appendix F
Alias 15515 15516 15517 15518 15519 15552

Slot Status
273


274
Appendix F
Alias 15579 15580 15581 15582 15583 15584

Slot Status
275


276
Appendix F
Alias 15627 15628 15629 15630 15631 15632

Slot Status
277


278
Appendix F
Alias 15691 15692 15693 15694 15695 15696

Slot Status
279


280
Appendix F
Alias 15739 15740 15741 15742 15743 15744

Slot Status
281


282
Appendix F
Alias 15803 15804 15805 15806 15807 15808

Slot Status
283

284
Appendix F
Aliases for ACM, NCM, and TCM Network Status

This table lists aliases for the ACM, NCM, and TCM network communication modules. All system aliases used to obtain NET 1 status ($NET1L, $NET1R, $N01OK - $N10OK and $N01RD - $N10RD) always reflect the status of NET 1 on the NCM or TCM. They are not used with the ACM. System aliases used to obtain NET 2 status ($NET2L and $NET2R) always reflect the status of NET 2 on the NCM or TCM whenever NCM or TCM modules are configured on the system. However, if only ACM modules are configured, these aliases reflect the status of NET 2 on the ACM modules.
Variable $NET1L $NET2L $NET1R $NET2R $N01OK $N02OK $N03OK $N04OK $N05OK $N06OK $N07OK $N08OK $N09OK $N10OK $N01RD $N02RD $N03RD $N04RD $N05RD $N06RD $N07RD $N08RD $N09RD $N10RD 1. Alias 14081 14082 14083 14084 14098 14099 14100 14101 14102 14103 14104 14105 14106 14107 14130 14131 14132 14133 14134 14135 14136 14137 14138 14139 Description (discrete values) NET 1 on left NCM or TCM is operational NET 2 on left NCM or TCM is operational1 NET 1 on right NCM or TCM is operational NET 2 on right NCM or TCM is operational1 Communication with node 1 are OK Communication with node 2 are OK Communication with node 3 are OK Communication with node 4 are OK Communication with node 5 are OK Communication with node 6 are OK Communication with node 7 are OK Communication with node 8 are OK Communication with node 9 are OK Communication with node 10 are OK Redundant Communication exist with node 1 Redundant Communication exist with node 2 Redundant Communication exist with node 3 Redundant Communication exist with node 4 Redundant Communication exist with node 5 Redundant Communication exist with node 6 Redundant Communication exist with node 7 Redundant Communication exist with node 8 Redundant Communication exist with node 9 Redundant Communication exist with node 10
Reflects status of NCM or TCM, unless only ACM modules are configured.
Aliases for System-Wide Information 285
Aliases for System-Wide Information

This table lists aliases for system-wide information. These values are stored in 16-bit wide (integer) system status registers.
Variable $Year $Month $Day $Hour $Minute $Second $msec $WKday $keysw Alias 39633 39635 39637 39639 39641 39643 39645 39647 39649 Description (integer values) Current year Current month Current day Current hour Current minute Current second Current millisecond Current day of week (0 = Sunday to 6 = Saturday) Main chassis keyswitch position: 0 = Stop 1 = Prog 2 = Run 3 = Remote $SCNREQ $DELTA $SCNSUR $SCNOVR State 39651 39653 39655 39657 39659 Scan time (ms) selected in Setup Manager Measured scan time (ms) for latest scan Surplus scan time (averaged over last 100 scans) Number of overruns (averaged over last 100 scans) Program mode as follows: 0 = Running 1 = Halted 2 = Paused $Disabl $CPVer $CPVer 39675 39663 39664 Number of disabled variables (I/O points and memory variables) Minor version number of control program. Major version number of control program.
286
Appendix F
G
TCM Model 4351/4352 Configuration
Overview 288 Configuring TCM Ports 289 Using a Tricon TCM to Synchronize Time 298 Configuring a Tricon TCM Printer Port for Printing 304
288
Appendix G
Overview
Note If you have a newer model 4351A or 4352A TCM, do not use the procedures in this appendix. The procedures in this appendix apply specifically to configuring the ports on the model 4351 or 4352 TCM, and should be followed in place of the TCM configuration procedures provided in the preceding chapters of this guide.
Configuring TCM Ports
289

A single Tricon system supports a maximum of four TCMs, which must reside in two logical slots. You cannot mix model 4351A/4352A TCMs and 4351/4352 TCMs in the same system, even if they are installed in different chassis. See the Planning and Installation Guide for Tricon v9 v10 Systems for detailed TCM installation guidelines. TCM models 4351 (Copper)/4352 (Fiber) support the following protocols on network and serial ports.
Protocol TriStation TSAA (UDP/IP) Peer-to-Peer (UDP/IP) Peer-to-Peer (DLC) Modbus Slave (ASCII or RTU) Modbus Master (RTU) Modbus Master or Slave (TCP) GPS Time Synchronization Triconex Time Synchronization via DLC Triconex Time Synchronization via UDP/IP SNTP Triconex Time Synchronization Network Printing using Jet Direct 1. means the protocol is not available on this port. Network Ports NET 2 NET 2 NET 1 NET 1 NET 2 NET 1 NET 1 NET 2 NET 2 Serial Ports Port 4 1 Any port Any port Port 1
To configure specific types of ports, see these topics: Configuring TCM Network Ports on page 290 Configuring TCM Serial Ports on page 292 Configuring TCM Peer-To-Peer Ports on page 294 Configuring TCM Modbus TCP Ports on page 296
For additional information on configuring the TCM, see these topics: Note Using a Tricon TCM to Synchronize Time on page 298 for instructions on configuring the TCM to synchronize time. Configuring a Tricon TCM Printer Port for Printing on page 304 for instructions on configuring the TCM for use with a printer. Once TCM ports have been configured, but prior to downloading the configuration to the controller, you can change the existing TCM model to a different model TCM without losing your port settings. Note that you can switch only from a 4351 to a 4352, or viceversa; you cannot switch from a 4351 or 4352 to a 4351A or 4352A.
290
Appendix G
However, once the configuration has been downloaded to the controller, you cannot change the TCM model installed in the Tricon without downloading a new configuration.
Configuring TCM Network Ports

This procedure explains how to configure network ports on a Tricon TCM.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Network tab.

Property Slot Selection Not Installed, Installed Enable Network Action Select the slot where the TCM module you want to configure is installed. Click Installed to enable configuration of the module. Clicking Not Installed resets all options to their default state and makes them unavailable for configuration. The default is Not Installed. Select the check box to enable the network port to be configured.
291
Property Transceiver Mode
Action Select the communication mode. The default is Auto-Negotiate. If you have a model 4352 TCM with fiber connectors, you must select 100 Mbps as the communication mode. The 4352 module cannot connect at 10 Mbps.
IP Address
Enter the IP Address for the port. NET 1 and NET 2 cannot use the same IP address. The default for NET 1 is 192.168.1.0; for NET 2 is 192.168.1.1. If needed, enter the IP address for the subnet. The default is 255.255.255.0. If needed, enter the IP address for the default gateway. The default is 0.0.0.0. The UDP port to use for the TriStation connection. The default is 1502.
IP Subnet Mask Default Gateway IP Address TriStation Configuration: UDP Port Number TSAA Configuration: UDP Port Number Port Write Enabled
The UDP port to use for TSAA connections, including DDE Server, SOE Recorder, and OPC Server. The default is 1500. Select this check box if you want to allow TSAA writes to the network ports. Applies to all TSAA connections on these ports. The default is cleared (the port is read-only)..
5 Note
Click OK to save your changes. Changes to TCM IP addresses are not effective until the existing connection is closed and a new connection is opened. Once a connection is opened, it remains open until you close it, even if the IP address is changed via a download change operation.
292
Appendix G
Configuring TCM Serial Ports

This procedure explains how to configure serial ports on a Tricon TCM.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Serial tab.

Property Port Selection Protocol Action Click the port to be configured. Ports can be configured only for a slot with an installed module. Select the communication protocol for the port: All ports can use Modbus Master, Modbus Slave ASCII, Modbus Slave RTU. Only port 1 can use GPS. This port is automatically configured for GPS when you enable time synchronization. See Using a Tricon TCM to Synchronize Time on page 298. Only port 4 can use TriStation.
293
Property Port Write Enabled
Action Available only if Modbus Slave (ASCII or RTU) is selected as the communication protocol. Select this check box if you want to allow Modbus writes to this slave port. The default is cleared (the port is read-only).. If you selected Modbus Slave RTU or ASCII, enter the number of the Modbus slave device. The default is 1. Enter the communication rate for the port. The default is 9600. Select 8 or 7 bits. The default is 8. Available only with Modbus Slave ASCII. Select 1 or 2 bits. The default is 1 bit. Select the type of parity for the port. The default is Odd. Select RS-485 or RS-232. The default is RS232. On port 4 when TriStation is selected as the protocol, RS-485 is not available Select None or Hardware; the default is None. Select the type of termination used with cables. Only available with RS-485 Transceiver Mode. The default is None. Select the order to be used with floating point numbers. The default is Low 16 Bits First. Enter the minimum and maximum values to be used for the Modbus alias range. The default minimum is 0. The default maximum is 32,767. Enter the port number that the TCM will use in the Modbus Master functions to access the port. Only available for Modbus Master.
Modbus Slave Address Baud Rate Data Bits Stop Bits Parity Transceiver Mode Handshake Termination Options FP Ordering Modbus (Minimum and Maximum) Range Master Logical Port
5 Note
Click OK to save your changes. Even if port 4 is set to Not Configured (the default value), it can still be used to connect to the Tricon via TriStation. This is useful when you are unable to connect via a network connection.
294
Appendix G
Configuring TCM Peer-To-Peer Ports

This procedure explains how to configure the IP address for controllers communicating on a Peer-to-Peer network through a Tricon TCM.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Peer-to-Peer tab.
4 5
Under Slot Selection, select the module (slot) you want to configure Peer-to-Peer ports for. Select a node (controller), and specify these properties.
Property Destination UDP Port Action Enter the UDP port number for each controller to be communicated with on the Peer-to-Peer network. This must be the same number that the controller uses as its UDP Base Port Number. Enter the IP address for the controller.
IP Address
6 7 Note
Click Update to apply the new settings for the selected node. Repeat steps 4 through 6 for each node to be included in the network. If necessary, click Reset All to reset all node settings for the selected slot to their default, unconfigured state.
295
Once all nodes have been configured, specify these properties (applicable to all nodes on the Peer-to-Peer network).
Property UDP Base Port Number Action Enter the UDP base port number for the controller. Enter 0 to disable Peer-to-Peer over UDP/IP on the network. The default is 1503. UDP port numbers must be unique. Peer-to-Peer Time Synchronization Enabled Select the check box to enable time synchronization across the Peer-to-Peer network. See Using a Tricon TCM to Synchronize Time on page 298 for more information. Note: If you are using a Trident node along with a Tricon node, the Peer-to-Peer Time Synchronization will not work properly. Enable Communication with Tricon V8 and V9 Peer-to-Peer Systems Select the check box to enable communication with Tricon version 8 and 9 systems. The default is cleared. Available only for a module installed in the left slot.
296
Appendix G
Configuring TCM Modbus TCP Ports

This procedure explains how to configure Modbus TCP ports on a Tricon TCM, which enables Modbus communication through network ports.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Modbus TCP tab.
4 5
Under Slot Selection, select the module (slot) you want to configure Modbus TCP ports for. Select a port and specify these properties.
Property Protocol Port Write Enabled Action Select the communication protocol for the port. Options include Modbus TCP Master and Modbus TCP Slave Net. Available only if Modbus TCP Slave is selected as the communication protocol. Select this check box if you want to allow Modbus writes to this slave port. The default is cleared (the port is read-only).. Enter the number of the Modbus Master node. Available only with Modbus TCP Master protocol. Enter the number for the TCP port. The default is 502.
Master Logical Port TCP Port
297
Property IP Address
Action If the port uses Modbus Master protocol, enter the IP address of the slave node. If the port uses Modbus Slave protocol, enter either of these: To accept communication from any Modbus Master, leave the IP address as 0.0.0.0. To accept communication only from a defined Modbus Master, enter the specific master IP address.
FP Ordering Modbus (Minimum and Maximum) Range
Select the ordering to use for floating point numbers. Enter the minimum and maximum for the modbus alias range. Available only with Modbus TCP Slave Net.
298
Appendix G

This procedure explains how to enable time synchronization on a TCM. Time synchronization can be enabled using the following protocols: GPS SNTP Triconex Time Synchronization via DLC or UDP/IP on a Peer-to-Peer network
In a redundant network of Triconex controllers that each have two TCMs installed, you can implement redundant time synchronization by configuring time synchronization for both TCM modules (both left and right slots). Time synchronization can be enabled only for a single logical slot. If the TCM is installed in the COM slot, you configure time synchronization only for the left slot (there is no redundancy when installed in the COM slot).
Configuring GPS Time Synchronization on the TCM

This procedure explains how to configure a TCM to enable time synchronization through the Global Positioning System (GPS) by using the Trimble Acutime 2000 Synchronization Kit.
CAUTION
To ensure the accuracy of GPS time adjustments, the Tricon clock must be set to within 10 minutes of the correct local time.
If the TCM is in a Peer-to-Peer network, it can also be used as the master node for time synchronization of other controllers on the network. In this configuration, the master node TCM synchronizes time with the GPS, and any slave nodes on the Peer-to-Peer network synchronize their time with the master TCM. In this way, all nodes on the Peer-to-Peer network are synchronized with GPS time. If the TCM is acting as a slave node on a Peer-to-Peer network, it cannot be configured for GPS time synchronization. Slave nodes synchronize their time only to the master node on the Peerto-Peer network, and reject all other time change requests. GPS time synchronization uses Serial Port 1 on the TCM.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Time Sync tab.
299
4 5
Under Slot Selection, click Left Slot. You must configure the module in the left slot first. Under Time Synchronization Configuration, select GPS. If you previously configured Port 1 to use a Modbus protocol, selecting GPS will reset Port 1 to use the GPS protocol.
(Optional) If you have a redundant TCM installed in the right slot, under Slot Selection, click Right Slot, and then select GPS Redundant. Note The module in the right slot can be configured only if it has been installed and if the module in the left slot has already been configured for GPS time synchronization.
If you also want the TCM to be able to act as a master node for time synchronization of other controllers on a Peer-to-Peer network (using Triconex Time Synchronization) do the following: 1 2 In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box.
300
Appendix G
Configuring SNTP Time Synchronization on the TCM

This procedure explains how to configure TCM time synchronization to an SNTP server. If the TCM is in a Peer-to-Peer network, it can also be used as the master node for time synchronization of other controllers on the network. In this configuration, the master node TCM synchronizes time with the SNTP server, and any slave nodes on the Peer-to-Peer network synchronize their time with the master TCM. In this way, all nodes on the Peer-to-Peer network are synchronized with SNTP time. If the TCM is acting as a slave node on a Peer-to-Peer network, it cannot be configured for SNTP time synchronization. Slave nodes synchronize their time only to the master node on the Peerto-Peer network, and reject all other time change requests.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Time Sync tab.
4 5
Under Slot Selection, click Left Slot. You must configure the module in the left slot first. Select these properties.
Property Time Synchronization Configuration Action Select SNTP. The default is None.
301
Property SNTP Master IP Address
Action Enter the IP address of the SNTP server to synchronize time with.
(Optional) If you have a redundant TCM installed in the right slot, under Slot Selection, click Right Slot, and then select these properties.
Property Time Synchronization Configuration SNTP Master IP Address Action Select SNTP Redundant. Enter the IP address of the SNTP server to synchronize time with.
Note
The module in the right slot can be configured only if it has been installed and if the module in the left slot has already been configured for SNTP time synchronization.
If you also want the TCM to be able to act as a master node for time synchronization of other controllers on a Peer-to-Peer network (using Triconex Time Synchronization) do the following: 1 2 In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box.
302
Appendix G
Configuring Triconex Time Synchronization on the TCM

In a Peer-to-Peer network, Triconex Time Synchronization can be used to synchronize time across controllers on a network. The controller with the lowest node number serves as the master node. The master node can also synchronize its time with a GPS or an SNTP server. In this configuration, the master node synchronizes time with the GPS or SNTP server, and any slave nodes on the Peer-to-Peer network synchronize their time with the master node. In this way, all nodes on the Peer-to-Peer network are synchronized with GPS or SNTP time. Note Currently, when a Trident controller is on a Peer-to-Peer network using Triconex Time Synchronization, with a Tricon TCM acting as a master node, the Trident will not correctly synchronize its time to the master node.
Configuring a Master Node

This procedure describes how to configure the TCM as a master node on the Peer-to-Peer network when GPS or SNTP time synchronization is not being used. If you want the master node to synchronize to a GPS or SNTP server, use the procedures in the these sections: Configuring GPS Time Synchronization on the TCM on page 298 Configuring SNTP Time Synchronization on the TCM on page 300
Procedure
1 2 3 4 5 6 7 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Time Sync tab. Under Time Synchronization Configuration, select None. Click OK to save your changes. In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box. This allows the controller to participate as a master node in time synchronization across the Peer-to-Peer network.
303
Configuring a Slave Node

This procedure describes how to configure the TCM as a slave node on the Peer-to-Peer network.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Peer-to-Peer tab.
4 5 6 7 8
Under Slot Selection, click Left Slot. Select the Peer-to-Peer Time Synchronization Enabled check box. Click OK to save your changes. In the Configuration tree, click Operating Parameters. Select the Enable Tricon Node Time Synchronization check box. This allows the controller to participate as a slave node in time synchronization across the Peer-to-Peer network.
304
Appendix G
Configuring a Tricon TCM Printer Port for Printing

This procedure explains how to configure a Tricon TCM port that is connected to a Centronicscompatible printer. You do not need the printer driver that may have come with the printer package.
Procedure
1 2 3 Expand the Controller tree, double-click Configuration, and expand Hardware Allocation. Double-click the slot where the TCM module is installed and then click Setup. The TCM Setup dialog box appears. Click the Printer tab.
Specify these properties for the module installed in the Left Slot.
Property Printer Number Line Width TCP Port IP Address Action Enter the number for the printer; can only be 5 or 10. The default is 0, meaning a printer is not configured. Enter the number of characters to be printed on a line. The default is 80 characters. Enter the number of the TCP port for the print server. The default is 9100 for an HP printer. Enter the IP address of the printer server.
5 6
If a module is also installed in the Right Slot, repeat step 4 for that module. Click OK to save your changes.
Glossary
10Base2 The standard for an Ethernet LAN capable of transmitting 10 megabits of data per second through thin coaxial cables, to a maximum distance of 656 feet (200 meters). 10BaseT The standard for an Ethernet LAN capable of transmitting 10 megabits of data per second through twisted-pair wire. 100BaseTX The predominant standard for a Fast Ethernet LAN capable of transmitting 100 megabits of data per second through Category 5 twisted-pair cable only. ACM Stands for the Advanced Communication Module, which is a Tricon communication module that acts as an interface to a Foxboro Intelligent Automation (I/A) Series DCS. alias A five-digit number that can be used by an external device to read or write to an input, output, or memory point in a controller. Alias is a convention of the Modbus protocol. application In TriStation 1131, an application is the compiled code (built from program elements and configuration information) that is downloaded to and runs in a Triconex controller. ARP Stands for Address Resolution Protocol which is a TCP/IP protocol used to obtain the physical address of a node on an Ethernet network. A client station broadcasts an ARP request onto the network with the IP address of the target node it wants to communicate with. The node with that address responds by sending back its physical address so that packets can be transmitted to it. AUI Attachment Unit Interface. A coaxial cable connected to a transceiver that plugs into a 15-pin socket on the network interface card (NIC), to a maximum distance of 328 feet (100 meters). bin An address range of aliased variables in Triconex controllers, based on Class and Type combinations. Centronics A standard 36-pin parallel interface for connecting printers and other devices to a computer.
306
Glossary
client/server An architecture in which the client (PC or workstation) is the requesting machine and the server is the supplying machine, both of which are connected by means of a local area network (LAN) or wide area network (WAN). closed network A network designed for maximum safety which includes only Triconex devices. A Peer-to-Peer network is an example of a closed network. communication path The route between any two nodes. Same as line, channel, link, or circuit. communication protocol Hardware and software standards that govern data transmission between two computers or communications devices. There are several layers (levels) of functionality in a protocol. Each layer may be available as a separate software component, or several layers may be combined into one. controller A Triconex controller includes Main Processors, communication and I/O modules, and field termination panels. CTS signal In Modbus communication, an RS-232 signal sent from the receiving station to the transmitting station which indicates it is ready to accept data. data bits The number of bits used to represent one character of data. When a Modbus slave transmits ASCII text, either seven or eight bits can be used. When a Modbus master or slave uses the RTU mode, eight data bits are required. data transfer time In a Peer-to-Peer network, the time required to initiate a send operation, send the data over the network, and get an acknowledgment from the receiving controller. DCS Stands for distributed control system, which is a system that controls a process and provides status information to an operator. default gateway A router that forwards all messages not addressed to stations within the local subnet. duplex See full duplex and half duplex. EICM Stands for Enhanced Intelligent Communication Module, which is a Tricon communication module that enables serial communication.
Glossary 307
Ethernet A type of computer network which is defined by the IEEE 802.3 standard. An Ethernet network is typically a shared media LAN. All stations on the segment share the total bandwidth, which is either 10 megabits (Ethernet), 100 megabits (Fast Ethernet) or 1,000 megabits (Gigabit Ethernet) per second. exception condition In Modbus communication, a programming or operation error which involves an illegal or illogical query by the master. exception response In Modbus communication, the response of a slave to a programming or operation error. Fast Ethernet Another name for 100BaseTX Ethernet communication. Fast Ethernet transmits data at 100 megabits per second rather than 10 megabits per second as in regular Ethernet. Fast Ethernet operates in a LAN (local area network) that shares the 100 megabit per second bandwidth with all transmitting stations. fiber Glass or plastic threads used to transmit data. A fiber-optic cable consists of a bundle of glass threads. Fiber-optic cables have a much greater bandwidth than copper cables, so they can carry more data. They are also less susceptible than copper cables to interference. Fiber-optic cables allow data to be transmitted digitally rather than analogically. FM Stands for Factory Mutual Research is an independent third-party product testing and the development of engineering guidelines. full duplex Serial communication using two pairs of wiresone pair for Modbus reads and the other pair for Modbus writes. Called 4-wire in TriStation. function block A Program Organization Unit (POU) that defines a set of input and output parameters that can be used as connections to other blocks and internal variables. Function blocks define an algorithm (code) that runs each time the function block is executed. The data contained in a function block is persistent from one execution of the function block to the next. gateway A computer that performs protocol conversion between different types of networks or applications. For example, a gateway can convert a TCP/IP packet to a NetWare IPX packet and vice versa. GPS Stands for Global Positioning System which is a system of 24 satellites for identifying earth locations, launched by the U.S. Department of Defense. The GPS is used for navigation and is the most accurate time source for a local clock.
308
Glossary
half duplex Serial communication using one pair of wires to transmit Modbus reads and writes. Called 2wire in TriStation. hardware handshake Signals transmitted back and forth between two stations to coordinate the timing of data transmission. HIM Stands for Hiway Interface Module, which is a Tricon communication module that acts as an interface to a Honeywell TDC-3000 control system. hub A connecting device in a network that joins communication lines together in a star configuration. Passive hubs are connecting units that add nothing to the data passing through them. Active hubs (multi-port repeaters) regenerate the data bits to maintain a strong signal. Intelligent hubs provide added functionality. IP address The unique 32-bit address of a computer attached to an Ethernet network. Every client and server in an Ethernet network requires an IP address which is either permanently assigned or dynamically assigned at startup. JetDirect A print server for LaserJet printers from HP which is available as an internal card or external unit. It supports its own proprietary printing protocol and several others, depending on the model. The JetAdmin printer management software is used to configure and control the JetDirect print server. logical slot In a Triconex chassis, a logical slot is a repository for a primary module, a hot-spare module, and their associated field termination component. MAC address The unique physical address of a network device that is programmed into the Network Interface Card (NIC) of the device when it is manufactured. master In Modbus communication, a device that initiates all query and response exchanges with the slave devices. MAU Stands for media adapter unit which is a device used to convert one type of Ethernet media to another. In a Trident system, a MAU can be used to convert a CM port to another Ethernet media type or to extend network distances. message response time For a TSAA client/server or Modbus master/slave data exchange, the time required to initiate and send a query and get a response from the receiving controller.
Glossary 309
MII Stands for media independent interface which is a bus used between network controllers and physical interfaces that is based on the MII interface specification. Modbus protocol An industry-standard master/slave protocol that is traditionally used for energy management, transfer line control, pipeline monitoring, and other rugged industrial processes. A Modbus communication link can use either the Remote Terminal (RTU) or ASCII mode of transmission. module An active field-replaceable unit consisting of an electronic circuit assembly housed in a metal spine. Also called board or card. MTRJ MTRJ is a duplex fiber-optic connector. It uses pins for alignment and has male and female versions. Multimode only. multi-point In Modbus communication, a link that interconnects three or more master or slave devices. NCM Stands for Network Communication Module, which is a Tricon communication module that enables network communication. network topology In a network, the pattern of interconnection between nodes; for example, a bus, ring or star configuration. NIC Stands for Network Interface Card which is a printed circuit board that plugs into both a client and a server device and controls the exchange of data between them. Also called a network adapter card. node In computer communication, a node is a network junction or connection point. For example, a Trident controller in an Ethernet network is a node. A terminal connected to a minicomputer or mainframe is a node. node number The physical address of a node. OPC Stands for OLE for Process Control which is a standard set of non-proprietary interfaces used to develop client/server programs. OPC supports interoperability between field devices and applications for process control, factory automation, and business.
310
Glossary
open network An Ethernet network to which Triconex controllers and other Ethernet devices, including routers and gateways to other networks, can be connected. parallel port A socket on a computer used to connect a printer or other parallel device to the computer's parallel interface. parity checking An error detection method that tests the integrity of digital data during transmission over a serial communication path. Parity checking counts the number of 1 bits in a one-byte data item and sets the parity bit (the ninth bit) to 0 or 1, resulting in an odd or even total number of bits. path In computer communication, the route between any two nodes. Also called line, channel, link, or circuit. Peer-to-Peer protocol An Ethernet-based Triconex protocol that allows two applications running on separate Triconex controllers to exchange a limited amount of process control data. Because a Peer-to-Peer network is restricted to Triconex controllers, the cable can be isolated and protected more securely than an Ethernet cable. A Peer-to-Peer network requires the use of Ethernet ports on NCM or TCM modules. point-to-point In Modbus communication, a link that connects one master or slave device to another. port An interface that enables communication with external devices. Triconex controllers include serial and Ethernet ports that must be configured in TriStation 1131. print server A hardware device with multiple Ethernet ports that enables a printer to be located anywhere in an Ethernet network. process-tolerance time The maximum length of time that can elapse before the control algorithms in a TriStation application fail to operate correctly. protocol Rules that govern transmitting and receiving of data. See communication protocol. RARP Stands for Reverse Address Resolution Protocol which is a TCP/IP protocol used by a diskless workstation to obtain its IP address. redundancy The practice of using a spare device in parallel with a primary device so that, if the primary device fails, the spare device is easily or automatically placed into service. Examples are
Glossary 311
redundant modules which protect against internal faults, redundant cables which protect against cable breakage, and redundant workstations which protect against network failures. router A device that forwards data packets from one local area network (LAN) or wide area network (WAN) to another. Based on routing tables and routing protocols, routers read the network address in each transmitted frame and decide how to send it based on factors like network traffic, speed, or bad lines. RS-232 Stands for Recommended Standard 232 which is a standard interface approved by the Electronic Industries Association (EIA) for connecting serial devices in point-to-point configurations. RS-422 Stands for Recommended Standard 422 which is a standard interface approved by the Electronic Industries Association (EIA) for connecting serial devices in point-to-point differential configurations. RS-485 Stands for Recommended Standard 485 which is a standard interface approved by the Electronic Industries Association (EIA) for connecting serial devices in multi-point differential configurations. RTS signal In Modbus communication, an RS-232 signal sent from the transmitting station to the receiving station requesting permission to transmit. scan surplus A component of the scan time of a controller, the scan surplus is the time left after the executable elements and communication messages have been processed. The scan surplus should be positive. If the scan surplus is negative, the scan time should be increased. scan time The time required by a controller for the cycle of required control functions. The scan time includes input poll time; execution time for all executable elements in the TriStation project; processing time for TriStation and Peer-to-Peer messages, TSAA writes, and Modbus writes; and output poll time. slave In Modbus communication, a device that is controlled by another device called the master. The master initiates all query and response exchanges, and the slave can only respond. SMM Stands for Safety Manager Module, which is a Tricon communication module that acts as an interface to a Honeywell Universal Control Network.
312
Glossary
SNTP Stands for Simple Network Time Protocol, an Internet standard protocol that assures accurate synchronization to the millisecond of computer clock times in a network of computers. Running as a continuous background client program on a computer, SNTP sends periodic time requests to servers, obtaining server time stamps and using them to adjust the clients clock. station A computer, workstation or terminal in a network. Also called a node. subnet A division of a network into an interconnected, but independent, segment (domain) to improve performance and security. Typically, Triconex controllers are configured in a subnet that is part of a large network for process control. subnet mask The addressing method used to split networks into subnets. The mask is a binary pattern that subdivides a single IP address into a subnet number and a new host number. A typical subnet mask is 255.255.255.0, which means that 254 Class C addresses are available. TCM Stands for Tricon Communication Module, which is a Tricon module that enables network and serial communication for Tricon controllers. TCP/IP Stands for Transmission Control Protocol/Internet Protocol which is the global standard communication protocol for the Internet. Can also be used for private networks such as corporate intranets and distributed control systems. TCP/IP is a routable protocol, which means that all messages contain not only the address of the destination station, but the address of a destination network. This allows TCP/IP messages to be sent to multiple networks within an organization or around the world, hence its use in the Internet. time synchronization A Triconex protocol used to establish and maintain a synchronized, network-wide time basis. A controllers time can be synchronized with the master node in a network of Tricon or Trident controllers, or with a Distributed Control System (DCS). transceiver A transmitter and receiver of analog or digital signals, such as a transponder or network adapter. TriStation protocol A Triconex master/slave protocol in which the master (a TriStation PC) communicates with the slave (a Triconex controller) over an Ethernet network. TriStation communicates with the Main Processors in order to download the application to the Triconex controller and upload diagnostic information.
Glossary 313
TSAA Stands for Triconex System Access Application, a protocol that enables client/server communication between Triconex controllers and PCs. Two client/server programs, OPC Server and DDE Server, use TSAA protocol to exchange data with Triconex controllers. TSAA protocol can also be used to write other programs for accessing Trident points. UDP/IP Stands for User Datagram Protocol/Internet Protocol (UDP/IP), which are protocols for the Transport and Network layers of the OSI network model.
314
Glossary
Index
Numerics
100BaseTX, defined, 305 10Base2 defined, 305 10Base2 cable connection to media converter, 33 converting to faster media, 12 10BaseT, defined, 305 10BaseT cables, description, 19
BNC connectors terminating, 31, 32 terminating if unused, 11
C
cables description, 19 serial, 8 twisted-pair, 9 Category 5 shielded cable, 9 CDS, definition, 306 Centronics, defined, 305 Centronics printing EICM parallel port, 15 printing setup, 138 using a Tricon EICM port, 139 chassis, rules for selection, 10 client/server, defined, 306 client/server communication DDE Server, 60 overview, 48 using OPC Server, 6973 clock. See controller clock closed network, defined, 306 CM configuring Peer-to-Peer ports, 82 protocols supported, 2 COMM Bus, 146, 163 communication indicators on EICM front panel, 167 indicators on NCM and NCMG, 159 indicators on TCM front panel, 152 non-Triconex hardware, 8 communication path, defined, 306 communication protocol, defined, 306 configuration, Peer-to-Peer, 83 connectors BNC, 11 RJ-45, 9 control programs (TSAA), 48
A
access list, 42 configuring, 44 ACM changing node number, 30 configuring connection, 35 connection using media converter, 33 definition, 305 direct connection to TriStation, 31, 32 setting node number, 26 TriStation Ethernet connection, 20 ACM, protocols supported, 2 adapter, Triconex products, 8 ADJUST_TRICON_CLOCK message, 183 ADJUST_TRICON_CLOCK_RSP message, 184 alias, definition, 305 aliases, overview, 122 application, definition, 305 ARP, defined, 305 ASCII mode, defined, 207 AUI, defined, 305
B
big-endian order, 171 bin, definition, 305 bins (TSAA) binary mask used to identify, 177 requesting data, 177 bit and byte ordering, 170
316
Index
controller configuring Peer-to-Peer memory, 83 definition, 306 controller clock, setting, 127 CTS signal, defined, 306 customer support, xii
property, 136, 303 Enhanced Intelligent Communication Module. see EICM errors, Modbus data transmission, 223 Ethernet, defined, 307 Ethernet adapter. see network interface card Ethernet ports on ACM or NCM connecting to Ethernet devices, 11 converting to faster media, 12 Ethernet ports on ACM, NCM, or TCM overview, 49 TriStation configuration, 50 Ethernet ports on CM, overview, 49 Ethernet ports on TCM, physical description, 150 exception condition (Modbus), defined, 307 exception conditions, Modbus, 223 exception response (Modbus), defined, 307 exception responses, Modbus, 224225
D
data bits, defined, 306 data transfer time defined, 306 estimating for Peer-to-Peer, 78 Peer-to-Peer, 78 DB-pin adapter, Triconex product, 8 DDE address format, 67 network redundancy, 65 DDE Server configuring application, 62 configuring Triconex host, 62 installation, 61 overview, 2, 60 DDE., see also DDE Server debug port, TCM specifications, 151 default gateway defined, 306 sample network, 59 specifying in TriStation, 59 Device Clock tagname, 73, 124 DLC protocol, installing on TriStation PC, 21 dual redundancy, OPC Server, 73
F
Fast Ethernet, defined, 307 FM, definition, 307 Force Multiple Coils function, 221 Force Single Coil function, 217 full duplex, defined, 307 function block, definition, 307 function blocks Peer-to-Peer, 84 printing, 144 time adjustment, 124
E
EICM aggregate data rate, 162 available ports, 162 communication indicators, 167 configuring TriStation connection, 38 connecting to TriStation, 37 definition, 306 front panel, 166 hot spare feature unavailable, 162 parallel port specifications, 166 physical description, 165167 port numbers and connections, 166 protocols supported, 2 serial port specifications, 166 switch settings, 39 TriStation serial communication, 37 Enable Tricon Node Time Synchronization
G
gateway, defined, 307 Global Positioning System. See GPS global variables. See tagnames GPS defined, 307 redundant configuration, 125 synchronization with TCM, 131 time adjustments, 125 time synchronization protocol, 3
H
half duplex, defined, 308 hardware, Triconex products, 8 hardware handshake, defined, 308 HIM, definition, 308
Index
317
hub, defined, 308 hubs, description, 19
Modbus function names, listing, 208 Modbus functions, supported by serial ports, 207 Modbus message response time, 164 Modbus protocol exception conditions, 223 exception responses, 224225 message format, 208210 message lengths, 212 overview, 204 performance considerations, 206 sample query and response, 211 Modbus read queries, 163 Modbus write commands, 164 module communication capabilities, 5 definition, 309 modules, rules for selection, 10 monitor programs (TSAA), 48 monitoring Peer-to-Peer communication, 87 Trident response in DDE Server, 68 MP protocols supported, 2 system status aliases, 230 multi-point, defined, 309
I
ICM. see EICM indicators EICM front panel, 167 NCM and NCMG front panel, 159 TCM front panel, 152 installing TriStation, 24 Intelligent Communication Module. see EICM IP address defined, 308 methods for setting, 56 setting default, 56 setting Trident with a RARP Server, 58 setting with a Tricon EICM or TCM, 59 using CM to set, 59 using default, 56
L
little-endian ordering, 170 logical slot, definition, 308 longitudinal redundancy check. see LRC checksum. Loop-Back Diagnostic Test function, 220
M
MAC address, defined, 308 master node, defined, 123 master node, Triconex time synchronization, 135, 302 MAU, defined, 308 media converter, with ACM, NCM, or TCM, 33 message handling, TCM and MP, 146 processing, EICM, 164 processing, NCM and NCMG, 157 response time, Modbus, 164 response time, NCM and NCMG, 157 routing instructions, 59 message handling, description, 146 message processing, EICM, 163 message response time, 205 MII, defined, 309 Modbus, determining response time, 205 Modbus communication noise sources, 223 overview, 3 Modbus devices, RTU and ASCII modes, 207
N
NCM changing node number, 30 configuring connection, 35 connection using media converter, 33 definition, 309 direct connection to TriStation, 31, 32 setting node number, 28 TriStation Ethernet connection, 20 NCM and NCMG communication indicators, 159 front panel, 158 message processing, 157 operation, 156 physical description, 158160 protocols supported, 2, 160 specifications, 159 network adapter card. see network interface card network connection, testing, 65 Network Hardware Accessory Kit, 9 network printing, TCM Ethernet port, 15 network redundancy description, 13 for DDE Server, 65
318
Index
network redundancy (continued) OPC Server, 73 network routing, 59 network topology, defined, 309 NIC, defined, 309 NIC card, installing in a TriStation PC, 21 node, defined, 309 node number ACM, 26 changing on ACM, NCM, or TCM, 30 definition, 309 master node, 123
ports Tricon NCM, 52 Tricon TCM, 54 Preset Multiple Registers function, 222 Preset Single Register function, 218 print function blocks, purpose, 144 print server, with Trident CM, 138 PRINTER parameter, 144 printing Centronics interface, 15 configuring Tricon EICM port, 140 configuring Tricon TCM port, 143 connecting to Tricon TCM, 141 connecting to Trident CM, 141 Ethernet interface, 15 scan time increases, 137 with Trident, 138 printing devices, installing, 138 process tolerance time, defined, 310 protocol, defined, 310
O
OPC, defined, 309 OPC Data Manager (ODM), 73 OPC Redundancy Broker (ORB), 74 OPC Server configuration procedure, 7072 network redundancy, 73 overview, 2, 69 using with multiple controllers, 69 open network, defined, 310 ordering of bits and bytes in Triconex controllers, 170
R
RARP, defined, 310 Read Coil Status function, 213 Read Exception Status function, 219 Read Holding Registers function, 215 Read Input Registers function, 216 Read Input Status function, 214 read queries Modbus, 163 TSAA, 157 READ_TRICON_CLOCK message, 180 READ_TRICON_CLOCK_RSP message, 180 READ_TRICON_DATA message, 184 READ_TRICON_RSP message, 185 Recvid input parameter, 84 Recvnode input parameter, 84 redundancy, defined, 310 redundancy testing, 14 redundant DDE networks, required hardware, 65 redundant devices description, 13 testing for hardware failures, 14 two NCMGs and GPS, 125 workstations, 14 response codes, TSAA, 201 router, defined, 311
P
parallel port, defined, 310 parallel ports for EICM, specifications, 166 parity checking, defined, 310 path (communication), defined, 310 PC redundancy, OPC Server, 73 Peer-to-Peer configuring memory, 83 configuring ports, 80 data transfer time, 78 function blocks, 84 monitoring communication, 87 time synchronization with TCM, 135136, 302303 Peer-to-Peer communication overview, 3, 76 speed restrictions, 77, 86 using Send and Receive function blocks, 84 Peer-to-Peer protocol, defined, 310 performance, Modbus functions, 206 points, overview, 122 point-to-point, defined, 310 port, definition, 310
Index
319
routers in sample network, 59 RS-232 defined, 311 RS-422 defined, 311 RS-485 defined, 311 RST signal, defined, 311 RTU mode, defined, 207
system aliases, 122 (continued) chassis upper power supply, 231 MP, 230 slot status, 234283 system-wide information, 285 system requirements, 24 system time (TSAA), 181 adjusting, 183
T
tagnames finding starting address (TSAA), 194 overview, 122 TCM access level, 41 access list, 42 baseplate, 148 changing node number, 30 communication indicators, 152 configuring access list, 44 configuring connection, 35 connection using media converter, 33 controlling access, 41 definition, 312 direct connection to TriStation, 31, 32 front panel, 148 operation, 146 protocols supported, 2, 153 resource, 41 TriStation Ethernet connection, 20 TriStation serial communication, 37 types of ports, 149 TCP/IP, defined, 312 TCP/IP protocol for DDE network redundancy, 65 installing on TriStation PC, 21 technical support, xii time adjusting (TSAA), 183 requesting for controller (TSAA), 180 setting on controller (TSAA), 181 time stamp (TSAA), 186 associated with bin data, 177 time stamp in TSAA message, 190 time synchronization defined, 312 GPS time adjustments, 125 GPS, with TCM, 131 guidelines for networks, 126 overview, 123 protocol defined, 3
S
safety-critical applications, guidelines, 2 scan surplus, defined, 311 scan time affect on Modbus performance, 206 defined, 311 effect of print function blocks, 137 Sendid input parameter, 84 Sendnode input parameter, 84 sequential events recorder (TSAA), 48 serial ports on EICM, specifications, 166 serial ports on TCM physical description, 149 specifications, 149 SET_TRICON_CLOCK message, 181 SET_TRICON_CLOCK_RSP message, 182 slave (Modbus), defined, 311 slave node, Triconex time synchronization, 135, 303 SMM, definition, 311 SNTP time synchronization, 133, 300 SOE availability of data (TSAA), 192 block status (TSAA), 192 time stamp in TSAA message, 190 status, Peer-to-Peer communication paths, 87 subnet, defined, 312 subnet mask, defined, 312 symbol table getting with TSAA, 193 sending requested data (Trident), 194 symbol table (TSAA), information retrieval, 171 synchronizing time, Tricon TCM, 131 system aliases, 122 ACM, NCM, and TCM, 284 active board with fault, 234 chassis lower power supply, 232 chassis maintenance, 233
320
Index
time synchronization (continued) SNTP, with TCM, 133, 300 TCM master node, 135, 302 TCM slave node, 135, 303 Triconex, with TCM, 135, 302 with Tricon TCM, 131 TIMEADJ function block, 124 TIMESET function block, 124 training, xii transceiver, defined, 312 transfer time, Peer-to-Peer, 78 transmission errors, Modbus, 223 TriBus, voting, 146 TriBus voting, 164 EICM, 163 NCM, 156 Tricon communication overview, 5 write access, 121 Tricon ACM default IP address, 56 getting IP address using RARP server, 58 Tricon EICM configuring a printing port, 140 connecting a printer, 139 setting an IP address, 59 Tricon NCM default IP address, 56 getting IP address using RARP server, 58 ports, 52 Tricon TCM configuring a printing port, 143 connecting devices using a hub, 142 connecting printing devices, 141 default IP address, 56 GPS time synchronization, 131 ports, 54 setting an IP address, 59 SNTP time synchronization, 133, 300 time synchronization, 131 Triconex time synchronization, 135, 302 TRICON_CPSTATUS_REQ message, 191 TRICON_CPSTATUS_RSP message, 192 TRICON_DATA message, 175 TRICON_DATA_REQ message, 177 TRICON_GET_SYMBOL_REQ message, 193 TRICON_GET_SYMBOL_RSP message, 194 TRICON_SOE_DATAAVAIL message, 192 TRICON_SOE_REQ message, 187
TRICON_SOE_RSP message, 188 Triconex contact information, xii Triconex hardware products, 8 Triconex Time Synchronization, 131 Triconex Time Synchronization, with TCM, 135136, 302303 Trident printing devices, 138 write access, 121 Trident CM connecting devices using a hub, 142 connecting printing devices, 141 getting IP address using RARP server, 58 setting default IP address, 56 Trimble, Acutime 2000 Synchronization Kit, 125 TriStation connection to Tricon ACM, NCM, or TCM, 31, 32 installing, 24 installing DLC protocol, 21 installing protocols, 21 installing TCP/IP protocol, 21 system requirements, 24 verifying the installation, 25 TriStation protocol defined, 312 overview, 2 TSAA, defined, 313 TSAA client/server communication message format, 172175 ordering, 170 overview, 2 performance factors, 197 response codes, 201 using DDE Server, 60 using OPC Server, 6973 TSAA read queries, 157 TSAA write commands, 157 twisted-pair cables, description, 9
U
UDP/IP, definition, 313
V
verifying aTriStation installation, 25 view options, DDE Server, 68
W
write access by tagname or alias, 122
Index
321
write access (continued) Tricon, 121 Trident, 121 write commands Modbus, 164 TSAA, 157 WRITE_TRICON_DATA message, 178 WRITE_TRICON_DATA_RSP message, 180
322
Index

Comunication Guide, Tricon v9÷v10

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Comunication Guide, Tricon v9÷v10

Diunggah oleh

Hak Cipta:

Format Tersedia

Tricon Version 910 Systems

Document No. 9720088-004 Printed in the United States of America.

Communication Guide for Tricon v9v10 Systems

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Peer-to-Peer Data Transfer Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Related Communication Features

Appendix A TCM Capabilities

Appendix B NCM and NCMG Capabilities

Appendix C EICM Capabilities

EICM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Message Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Communication Guide for Tricon v9v10 Systems

Appendix D TSAA Protocol

Appendix E Modbus Protocol

Communication Guide for Tricon v9v10 Systems

Appendix F Tricon System Aliases

Appendix G TCM Model 4351/4352 Configuration

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Product and Training Information

We Welcome Your Comments

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Triconex OPC Server

Triconex DDE Server

Communication Guide for Tricon v9v10 Systems

Triconex Time Synchronization

Trimble GPS Time Synchronization

Communication Guide for Tricon v9v10 Systems

Centronics Interface for Printing

Communication Guide for Tricon v9v10 Systems

Module Capabilities and Usage

Module Capabilities and Usage

1. means this communication type is not available with this module.

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Communication Guide for Tricon v9v10 Systems

Serial Cables and Adapter

Communication Guide for Tricon v9v10 Systems

Network Hardware Accessory Kit

Ethernet Twisted-Pair Cable

Communication Guide for Tricon v9v10 Systems

Chassis and Module Selection

Communication Guide for Tricon v9v10 Systems

Connecting Ethernet Devices

Connecting Ethernet Devices

Ethernet Connection Between Tricon with NCM or ACM and TriStation PC

RJ-45 or MTRJ Connector on NET 1 or NET 2

RJ-45 or MTRJ Connector

Ethernet Router or Hub

RJ-45 or MTRJ Connector

Ethernet Connection Between Tricon with TCM and TriStation PC

Communication Guide for Tricon v9v10 Systems

Converting from 10Base2 to Faster Media

Using a Media Converter for Ethernet Connections

Communication Guide for Tricon v9v10 Systems

Sample Redundant Device Configuration

Communication Guide for Tricon v9v10 Systems

PC Redundancy for TriStation and SOE Recorder

Testing for Hardware Failures

Communication Guide for Tricon v9v10 Systems