Professional Documents
Culture Documents
Users Guide
Triconex Emulator
Version 1.1.0
Assembly Number 9700115-003
November 2010
Information in this document is subject to change without notice. Companies, names and data used in
examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or
transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express
written permission of Invensys Systems, Inc.
20042010 by Invensys Systems, Inc. All rights reserved.
Invensys, the Invensys logo, Triconex, Tricon, Trident, and TriStation are trademarks of Invensys plc, its
subsidiaries and affiliates. All other brands may be trademarks of their respective owners.
Contents
Preface
iii
New Features in Triconex Emulator v1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Summary of Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Product and Training Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
We Welcome Your Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Chapter 1
Getting Started
Chapter 2
15
Chapter 3
29
iv
Contents
Index
55
Preface
The Triconex Emulator is software that allows you to emulate, execute, and test TriStation
1131 applications without connecting to a Tricon, Trident, or Tri-GP controller.
Summary of Sections
Related Documents
Product Release Notices for specific Tricon, Trident, Tri-GP, and TriStation 1131 versions
vi
Preface
Technical Support
Customers in the U.S. and Canada can obtain technical support from the Invensys Global
Customer Support (GCS) center at the numbers below. International customers should contact
their regional support center.
Requests for support are prioritized as follows:
Requests from customers with a support agreement and customers with purchase
order or charge card authorization are given next priority
If you require emergency or immediate response and do not have a support agreement, you
may incur a charge. Please have a purchase order or credit card available for billing.
Telephone
Toll-free number 866-746-6477, or
Toll number
508-549-2424 (outside U.S.)
Fax
Toll number
508-549-4999
Web Site
http://support.ips.invensys.com/ (registration required)
E-mail
iom.support@invensys.com
Preface
vii
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 name, company name, job title, phone number, and e-mail address
viii
Preface
1
Getting Started
10
13
Chapter 1
Getting Started
TSAA protocol communication, including support for DDE and SOE clients, and
multicasting (DDE clients only)
System status function blocks for MP and I/O modules, including system state
transitions
Disabling of points
You can also use third-party process simulation software with the Emulator (via external DDE
servers, and/or Modbus Masters and Slaves) to provide a complete process control emulation.
Depending on the protocol being used, external servers communicating with the Emulator can
be running on the same PC as the Emulator, or on separate PCs, as long as they are on the same
network.
The following figure shows how the Emulator works with the TriStation 1131 software and
other Triconex and third-party elements in a simple system simulation.
P2P
Tricon, Trident
or Tri-GP
Controller
TSAA
External DDE
Servers
Triconex
Emulator
TriStation 1131
Emulator
Control Panel
Third-Party
Process
Simulation
Packages
DDE
Modbus
TSAA
Figure 1
Modbus
Master or
Slave
SOE
Recorder
When simulating a safety or process control system that includes multiple Triconex controllers,
as well as third-party DCS and control systems, multiple Emulator instances can be running at
the same time, communicating with each other via the Peer-to-Peer (P2P) protocol. If you are
using the DDE server built into the Emulator, the simulation application must be running on the
same PC as the Emulator; if you are using an external DDE server (as shown above), the
simulation application can run on a different PC.
The following figure shows how multiple Emulator instances can be used to simulate a more
complex safety or process control system.
Triconex
Emulator
Tricon, Trident
Simulation
Interface
or Tri-GP
Triconex
Emulator
Third-Party
Process
Simulation
Packages
P2P
P2P
P2P
DDE /
TSAA
Controller
External OPC
Servers
TSAA
Simulation
Interface
Figure 2
Triconex
Emulator
P2P
SOE
Recorder
Chapter 1
Getting Started
Network Communication
The Emulator supports redundant TSAA network communication, so that if the IP address you
identify as the primary server goes offline, the Emulator will automatically switch over to the
IP address you identify as the redundant server.
You can emulate multiple communication protocols (such as Modbus TCP and Peer-to-Peer)
simultaneously in one application running on the Emulator, as long as separate ports are
configured for each protocol. See Configuring the Emulators Settings on page 16 for
configuration information.
TSAA Protocol
The Emulator supports the TSAA protocol, allowing you to simulate communication between
a Triconex controller and clients using TSAA (such as DDE Server and SOE Recorder). Only the
following TSAA protocol commands are supported for emulation:
TRICON_DATA_REQ
READ_TRICON_CLOCK
WRITE_TRICON_DATA
ADJUST_TRICON_CLOCK
READ_TRICON_DATA
TRICON_CPSTATUS_REQ
SET_TRICON_CLOCK
TRICON_SOE_REQ
TRICON_GET_SYMBOL_REQ
Events can be retrieved from the Emulator by using the Triconex SOE Recorder software.
You can use the Emulator to test the SOE blocks configured in your application, verifying that
event collection is enabled and ensuring the correct retrieval of events by your SOE client. If you
have SOE blocks configured in your application, SOE functionality will be available in the
Emulator automatically after you download your application. No additional configuration in
the Emulator is necessary. See Testing SOE Communication on page 32 for more information.
Chapter 1
Getting Started
Peer-to-Peer Communication
Peer-to-Peer communication allows Triconex controllers to send and receive information from
each other. Peer-to-Peer communication is performed through Send and Receive function
blocks included in the application.
If you will be using Peer-to-Peer communication in your application, you can test it via the
Emulator. However, only one Peer-to-Peer configuration can be used by the Emulator.
If redundant communication modules are installed in a single logical slot, prior to downloading
your application to the controller, you need to select the physical module (LEFT or RIGHT) with
the Peer-to-Peer configuration you want to use. This module selection is made in the Emulator
Project Options dialog box; see Specifying Emulator Project Options on page 10 for more
information.
See Testing Peer-to-Peer Communication on page 34 for more information.
ALARM_DEVIATION_DINT
ALARM_RATEOFCHANGE_REAL
ALARM_DEVIATION_REAL
ALARM_TRIP
ALARM_LEVEL_DINT
BYPASS_DINT
ALARM_LEVEL_REAL
BYPASS_REAL
ALARM_RATEOFCHANGE_DINT
BYPASS_BOOL
For detailed information about these function blocks, please see the TriStation 1131 Libraries
Reference.
TR_MP_STATUS (Tricon)
SYS_MP_STATUS (Trident/Tri-GP)
For instructions on changing the value of the output parameters you want to emulate for each
MP system status function block, see Testing the Impact of MP System Status Changes on
page 44.
The Emulator also supports the following I/O status function blocks for emulation:
TR_SLOT_STATUS (Tricon)
SYS_RO32_STATUS (Trident/Tri-GP)
SYS_IO_STATUS (Trident/Tri-GP)
SYS_PI06_STATUS (Trident/Tri-GP)
SYS_AI32_STATUS (Trident/Tri-GP)
SYS_DO16_STATUS (Trident/Tri-GP)
SYS_AO04_STATUS (Trident/Tri-GP)
SYS_HRDI32_STATUS (Trident/Tri-GP)
SYS_DI16_AI16_STATUS (Trident/Tri-GP)
SYS_SDO16_STATUS (Trident/Tri-GP)
SYS_DI32_STATUS (Trident/Tri-GP)
For instructions on changing the value of the output parameters you want to emulate for each
I/O module, see Testing the Impact of I/O Status Changes on page 47.
Note
For detailed information about the MP and I/O status function blocks, please see the
TriStation 1131 Libraries Reference.
Disabling Points
When a point is disabled, inputs from field instruments do not change the value of the point,
and the application running on the controller (or the Emulator) will not write to the point.
Disabling points is typically used when field instruments need to be replaced or repaired.
An application running on a controller should not contain disabled points unless there is a
specific reason for disabling them, such as initial testing or maintenance. Testing your
application on the Emulator allows you to freely disable points so that you can assess the impact
of disabling those points in an application before downloading and running it on the controller.
For instructions on disabling points, see Disabling Points on page 53.
Because Download Changes behavior on the Emulator differs from that on the
controller, do not use the Emulator to test the impact of making library changes.
See the TriStation 1131 Developers Guide for more information about updating and changing
libraries.
See Downloading to the Emulator on page 36 for instructions on using these commands with
the Emulator.
Chapter 1
Getting Started
Each installed version of TriStation 1131 can be associated with only one installation of
the Emulator. If you have multiple versions of TriStation 1131 installed on your PC, you
can install multiple versions of the Emulator as well, as long as the TriStation 1131 and
Emulator versions are compatible.
The procedures in this section describe how to update an existing Emulator installation.
Topics include:
System Requirements
The following are the minimum system requirements for the Triconex Emulator:
CD-ROM drive
If the Emulator setup cannot locate a compatible version of TriStation 1131 to associate
with the Emulator, installation will be cancelled automatically. For example, TriStation
1131 v4.6 is not compatible with the Emulator v1.1.0; attempting to install the Emulator
v1.1.0 on a PC where only TriStation 1131 v4.6 is installed will result in an error, causing
the Emulator install program to automatically exit.
Procedure
1
When prompted, select the version of TriStation 1131 you want to associate with this
installation of the Emulator, and then click Next.
Only versions of TriStation 1131 (4.7.0 or later) currently installed on your PC can be
selected. If you do not select a TriStation 1131 version, installation will be cancelled.
Click Install.
The Emulator must be installed in the default destination folder, which is: C:\Program
Files\Triconex\TriStation 1131 <x.x.x>\Programs, where <x.x.x> is the version
of TriStation 1131 you selected in step 5.
Note
For 64-bit Windows systems (Windows 7 or Windows 2008 Server R2), the
default folder is: C:\Program Files(x86)\Triconex\TriStation 1131
<x.x.x>\Programs.
10
Chapter 1
Getting Started
Procedure
1
Start TriStation 1131 v4.7.0 or later, and open the project with the programs you want to
run on the Emulator.
On the Project menu, click Project Options, and then click the Emulator tab.
Property
Action
Number of
Instances
11
Emulator File
Generation
Select the files you want generated each time you download the
application to the Emulator.
Select the BT2 check box if you want a backup project file (.BT2)
generated (not recommended).
Select the SOE check box if you want an SOE definition file
(.SOE) generated. If you want to be able to test your SOE
configuration with the Emulator, you must select this option.
If selected, the .BT2 file and/or .SOE file are generated in the same
directory where the TriStation 1131 project is located. The default
setting is for the files to not be generated.
Note: These files will look just like the .BT2 and .SOE files
generated by the TriStation 1131 software when you
download an application to the controller. You will not be
able to distinguish between files generated by a
download to the Emulator, and files generated by a
download to the controller. You may want to make a note
of the date and time each time you download the
application to the Emulator, so you can compare that
timestamp to the date/time of the generated files.
12
Chapter 1
Getting Started
Property
Action
Communication
Modules (CMs)
for Peer-to-Peer
Communication
Modules (CMs)
for Modbus
13
CAUTION
If you have Triconex DDE Server or SOE Recorder running on the same
PC as the Emulator, they must be configured to use different UDP port
numbers (1500 for Emulator, 1501 for DDE Server, and 1509 for SOE
Recorder). Prior to connecting to the Emulator, verify that you have
configured the UDP ports correctly.
Please note that the Emulator will not be able to communicate with a
Triconex DDE Server or SOE Recorder application running on the same
PC as the Emulator. To test DDE and SOE communication with the
Emulator, the DDE and SOE clients must be running on a separate PC.
Procedure
1
Start TriStation 1131 v4.7.0 or later, and open the project with the programs you want to
run on the Emulator.
Open the Controller workspace, expand the Configuration tree, and double-click
Emulator Panel.
Click Connect
14
Chapter 1
Getting Started
2
Configuring the Emulator
16
20
21
22
16
Chapter 2
CAUTION
If you have Triconex DDE Server or SOE Recorder running on the same
PC as the Emulator, they must be configured to use different UDP port
numbers (1500 for Emulator, 1501 for DDE Server, and 1509 for SOE
Recorder). Prior to connecting to the Emulator, verify that you have
configured the UDP ports correctly.
Please note that the Emulator will not be able to communicate with a DDE
Server or SOE Recorder application running on the same PC as the
Emulator. To test DDE and SOE communication with the Emulator, the
DDE and SOE clients must be running on a separate PC.
Procedure
1
17
The dialog box name differs, depending on the controller type and the Emulator options
settings:
For Tricon, Trident, and Tri-GP applications, if the multiple Emulator instances
option is enabled (see Specifying Emulator Project Options on page 10), the dialog
box is named the same as the node name defined on the TriStation Communication
screen (the default is TRINODEx, where x is the node number configured in the
application).
If you have previously configured the Emulator for use with this application, and
you saved the Emulator settings to a file, go to Loading the Emulator Configuration
from a File on page 21.
If you have not configured the Emulator for use with this application before, or you
do not want to use saved configuration settings, go to the next step.
Only the Node Number and Server IP Address properties are required. All other
properties are optional. You do not need to specify properties that do not apply
to your desired testing scenario. For example, if you will not be using TSAA
functionality, you do not need to configure the TSAA properties.
Settings
Property
Action
Communication
Node
Number
Server IP
Address
18
Chapter 2
Settings
Property
Action
Peer-to-Peer
(P2P)
P2P (UDP)
Port Number
TSAA
Support
TSAA
Protocol
TSAA Port
Number
Multicast
Interval
Settings
19
Property
Action
Multicast IP
Address
Redundant IP
Address
Once you have configured all the settings required for your testing scenario, you are
ready to download the application to the Emulator. Do one of the following:
The Emulators settings are NOT saved automatically. Once you disconnect from the Emulator
(or click End in the TRxEMCodeEmulator dialog box), all settings are cleared and reset to the
default values the next time you connect to the Emulator. To save these settings to a file for
future use, see Saving the Emulator Configuration to a File on page 20.
20
Chapter 2
Changes you have made to the MP and I/O module status function block parameters
will also be saved as part of the Emulator configuration file, as long as you have
downloaded an application to the Emulator using those changes. See Testing the Impact
of MP System Status Changes on page 44 and Testing the Impact of I/O Status Changes
on page 47 for more information.
Procedure
1
In the TRxEMCodeEmulator dialog box, under Set Configuration File, click Browse. The
Open dialog box appears.
Browse to the location where you want to save the Emulator configuration file.
In the File Name field, enter a name for the Emulator configuration file. You can use any
naming convention that you like.
Click Open. The Open dialog box closes and you are returned to the
TRxEMCodeEmulator dialog box.
Click Save Configuration. The configuration information you entered for the Emulator
is saved to the file you created.
21
Procedure
1
In the TRxEMCodeEmulator dialog box, under Set Configuration File, click Load
Configuration.
The Open dialog box appears.
Browse to the location where you previously saved the Emulator configuration file.
When asked to confirm that you want to load configuration information from the
selected file, click OK.
The configuration information from the selected file is copied into the Emulator
configuration dialog box.
Verify the Emulator settings loaded from the file are correct.
Once you have verified all the settings required for your testing scenario are correct, you
are ready to download the application to the Emulator. Do one of the following:
22
Chapter 2
For detailed information about configuring and using Peer-to-Peer in an application, see
the TriStation 1131 Developers Guide.
The following six steps describe how to configure Peer-to-Peer communication in your
application so it can be tested on the Emulator:
You should complete all of these steps before downloading your application to the Emulator.
Procedure
1
23
Node Number
Locate the number entered in the Node Number field. For the TCM, this is the number
represented by the Network Node Address setting on the MP front panel.
You may want to write this number down, so you can compare it to the Emulators node
number in the next step.
Verify the node number entered on the Emulator configuration screen matches the node
number entered on the TriStation Communication screen.
See Configuring the Emulators Settings on page 16 for instructions on accessing the
Emulator configuration screen.
24
Chapter 2
Peer-to-Peer communication with the Trident v1.x CM is not supported by the Emulator.
This procedure explains how to configure the IP addresses for controllers communicating on a
Peer-to-Peer network through a Tricon TCM, Trident v2.x CM, or Tri-GP CM.
Note
Because NET 2 is reserved for OPC communication, the Peer-to-Peer protocol is not
available on NET 2 for model 4353 and 4354 TCMs. Peer-to-Peer communication can be
configured on NET 1 only for these TCMs.
Procedure
1
In TriStation 1131, expand the Controller tree, double-click Configuration, and expand
Hardware Allocation.
Double-click the slot where the TCM or CM module is installed, and then click Setup.
The TCM Setup (Tricon) or CM Setup (Trident/Tri-GP) dialog box appears.
Under Slot Selection, select the module you want to configure Peer-to-Peer ports for.
25
Action
Network
IP Address
Click Update to save the new settings for the selected node.
If you forget to click Update before selecting another node, your settings will be lost.
If you need to start over for any reason, 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
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 both NET 1 and NET 2 (meaning Peerto-Peer is enabled on both ports). UDP port numbers do not
need to be unique, as long as the IP addresses for each port is
unique. See the TriStation 1131 Developers Guide for reserved
values.
Available only for NET 1 on model 4353 and 4354 TCMs.
Enable Communication
with Tricon V8 and V9
Peer-to-Peer Systems on
NET 1 (TCM Only)
Enable Communication
with Tricon V8, Tricon
V9, and Trident v1 Peerto-Peer Systems
26
Chapter 2
Be sure to select the same network for the Select CM to Download Peer-to-Peer
Configuration From option prior to downloading your application (see Specifying
Emulator Project Options on page 10). If you configure the Peer-to-Peer port for NET 1,
but select NET 2 for the communication module, Peer-to-Peer will not work.
CAUTION
The default value for these properties is zero (0). If Maximum Number of
Peer-to-Peer Receives and Maximum Number of Peer-to-Peer Sends are
both set to zero, Peer-to-Peer communication is NOT enabled in your
application, and you will not see any Peer-to-Peer messages sent, even if
Peer-to-Peer communication is configured on the TCM or CM.
27
The maximum number does not have to be the same for Sends and Receives. For example, a
TriStation 1131 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
In the TriStation 1131, expand the Application tree, double-click Implementation, and
then click Peer-to-Peer Configuration.
Note
If you change these settings for an application running on the controller or the Emulator,
you must build the application and perform a Download All.
See the TriStation 1131 Libraries Reference for detailed information about available Send
and Receive function blocks.
See the TriStation 1131 Developers Guide for more information about configuring Peerto-Peer communication in your application.
28
Chapter 2
3
Testing Applications on the Emulator
30
32
34
35
36
41
42
Monitoring Variables
43
44
47
52
Disabling Points
53
30
Chapter 3
Under certain conditions, an application may appear to work correctly during testing
on the Emulator, but will not work when downloaded to the controller. The Emulator is
designed only to check your application code; it does not check the application against
any restrictions imposed by the specific controller you will be downloading to.
For example, the size of your application is not emulated exactly due to code differences
between the Emulator and a controller. Thus, an application that appears to download
correctly to the Emulator may be unable to be downloaded to the controller, due to size
restrictions imposed by the controller.
Many function blocks in the controller library (TR1LIB, TRDLIB, or TX1LIB) are not
emulated. One exception is TR_CALENDAR, which is emulated using the local time on
your PC. Also, the print function blocks print to the TriStation 1131 output window, not
to the specified printer.
The ERROR parameter is not emulated in the Tricon function blocks TR_CRITICAL_IO
and TR_SHUTDOWN. 0 will appear as the value for this parameter. On the
controller, this would indicate No Error; however, on the Emulator, this value should
not be considered an accurate representation of the error status. (The ERROR_NUM
parameter is emulated in all Trident/Tri-GP function blocks.)
The Download Changes behavior on the Emulator is different than that on the
controller. A Download Changes performed on the Emulator is the same as a
Download All, with the exception that a Download Changes command will keep any
changes youve made to the MP or I/O module system status parameters.
The Emulator must be separated from its clients by at least one of the following: router,
bridge, or hub.
31
Multiple instances of the Emulator are allowed. See Specifying Emulator Project
Options on page 10 for instructions on enabling multiple instances.
Instances of the Emulator may be running on the same PC, or on different PCs.
Each instance of the Emulator can emulate only one Tricon, Trident, or Tri-GP
controller at a time.
For SOE data, a maximum of 63 controllers can be emulated. Nodes 1-31 can be Tricon,
Trident, or Tri-GP controllers, while nodes 32-63 can be Trident or Tri-GP controllers
only. (However, since SOE Recorder can only retrieve events from up to 16 controllers
simultaneously, you dont need to emulate more than 16 controllers.) Each controller
being emulated requires a separate instance of the Emulator. For example, if you are
emulating two Tricon controllers and three Trident controllers, youll need to have five
instances of the Emulator running.
The maximum number of Emulator instances you can run simultaneously on a single
PC is dependent upon the size and complexity of your application, and the amount of
memory you have installed in your PC. The bigger and/or more complex your
application, the more memory you will need for multiple instances.
Single Emulator instances are terminated when the TriStation 1131 software
disconnects from the Emulator, but multiple Emulator instances must be terminated
manually.
32
Chapter 3
Events can be retrieved from a Triconex controller or the Emulator. You can use the Emulator
to test the SOE blocks configured in your application, verifying that event collection is enabled
and ensuring the correct retrieval of events by your SOE client. If you have SOE blocks
configured in your application, SOE functionality will be available in the Emulator
automatically after you download your application. No additional configuration in the
Emulator is necessary.
Each instance of the Emulator can simulate a Tricon, Trident, or Tri-GP controller that is
generating SOE data. Multiple Emulator instances allow you to test SOE event retrieval from
multiple controllers. See Specifying Emulator Project Options on page 10 for instructions on
enabling multiple instances.
Note
SOE clients must be running on a different PC than the Emulator. The Emulator cannot
communicate with an SOE client that is running on the same PC, even if the UDP ports
are different.
When you download your application to the Emulator, an SOE definition file (.SOE) is
generated in TriStation 1131 (only if you selected the SOE file generation option; see Specifying
Emulator Project Options on page 10). The .SOE file is created in the same directory where the
corresponding TriStation project is located. SOE configuration information is then extracted
from that file and downloaded to the Emulator.
CAUTION
The .SOE file generated by TriStation 1131 for use with the Emulator
cannot be used for SOE event retrieval on a controller. If this file is used
for event retrieval on a controller, events will not be collected. After you
have completed testing SOE on the Emulator, delete this file from the
SoeConfig folder on the SOE Recorder PC.
33
When you run your program, the Emulator generates SOE data based on state changes in the
following variables:
Discrete Input
Note
SOE data generation is available when the Emulator is using the primary server IP
address only. If the Emulator switches to the redundant server IP address, SOE data
generation will stop. See Configuring the Emulators Settings on page 16 for information
on the primary and redundant server IP addresses.
Alias-to-Bin Offset
SOE requests are sent for specific SOE block numbers; tagnames are assigned to each block.
Each tagname is associated with a unique alias number. However, the Emulators SOE
simulation accesses discrete variables (tagnames) using TSAA bin and offset instead of alias
numbers. The following tables show how alias numbers are translated to bin/offset numbers in
the Emulator.
Table 1
Alias Range
Bin Number
Offset
2001 4000
10001 12000
2 (Discrete Input)
12001 14000
Table 2
Alias Range
Bin Number
Offseta
5000 9999
10001 14999
2 (Discrete Input)
15000 19999
a. For Trident and Tri-GP controllers, the offset is calculated dynamically using the symbol table.
For more information about SOE, see the SOE Recorder Users Guide and the Communication
Guide for your controller.
34
Chapter 3
For more information about using Peer-to-Peer in an application, see the TriStation 1131
Developers Guide.
You should complete the steps outlined in Configuring Peer-to-Peer Communication for
Testing on page 22 before downloading your application to the Emulator.
The following are guidelines for using the Emulator to test Peer-to-Peer communication:
The Emulator does not support Peer-to-Peer for Tricon EICMs, NCMs, or the Trident
1.x controller.
Instances of the Emulator may be running on the same PC, or on different PCs.
A maximum of 63 nodes are supported. Nodes 1-31 can be Tricon, Trident, or Tri-GP
controllers. Nodes 32-63 can be Trident or Tri-GP controllers only.
The Emulator cannot communicate via Peer-to-Peer between a Tricon controller and a
Trident or Tri-GP controller if the Trident or Tri-GP node number is 32 or greater. For
communication between Tricon and Trident or Tri-GP controllers, all node numbers
must be 31 or less.
The Emulator supports up to five Peer-to-Peer functions per scan, and up to 50 total
Peer-to-Peer functions.
The transfer delay time is emulated at a time equal to twice the maximum of TS or SS,
where:
TS: Time for the sending node to transfer aliased data over the communication bus,
in milliseconds (number of aliased variables in bytes / 20000) * 1000.
SS: Scan time of the sending node in milliseconds.
35
Master
Slave
Application
with
Modbus TCP
Configured
Slave
Triconex
Emulator
Master
Figure 3
The following are guidelines for using the Emulator to test Modbus TCP communication:
Only one Modbus TCP configuration can be used by the Emulator. If redundant
communication modules are installed in a single logical slot, prior to downloading
your application to the controller, you need to select the physical module (LEFT or
RIGHT) with the Modbus configuration you want to use. This module selection is
made in the Emulator Project Options dialog box; see Specifying Emulator Project
Options on page 10 for more information.
The network selected in the Emulator Project Options dialog box (NET 1 or NET 2)
must be the same as the network selected in the Modbus TCP configuration in the
application. If these do not match, Modbus emulation will not work.
A maximum of 63 nodes are supported. Nodes 1-31 can be Tricon, Trident, or Tri-GP
controllers. Nodes 32-63 can be Trident or Tri-GP controllers only.
Emulated Modbus TCP functions support all features (including scaling) of Modbus
TCP functions when executed on a Triconex controller.
The Emulator will check for Modbus TCP messages on both the master and slave every
10 milliseconds (ms).
For more information about using the Modbus protocol, see the TriStation 1131 Developers
Guide, the TriStation 1131 Libraries Reference, and the Communication Guide for your controller.
36
Chapter 3
Canceling the
download
Status of
tagname,
variable and
function block
values
Status of
disabled points
On the Controllera
On the Emulator
Applicable
Not applicableb
Allowed
Not allowed
37
On the Controllera
On the Emulator
Not allowed
Allowed
Not allowed
Allowed
Allowed under
certain conditions
only
Allowed
Deleting libraries
Not allowed
Allowed
Not allowed
Allowed
Not allowed
Allowed
Deleting a program
Not allowed
Allowed
Shown
Not shown
Note
For detailed information about using the Download Changes command on the
controller, see the TriStation 113 Developers Guide.
The Download Changes command will be unavailable for the Emulator if any of the following
situations applies:
You have not yet performed a Download All of the project to the Emulator. The
Download Changes command is not enabled for the Emulator until after a Download
All has been completed.
You used the Change State to Download All command in TriStation 1131 to change the
projects state to Download All for the controller. The Download Changes command in
the Emulator will be unavailable until you perform another Download All to the
Emulator.
The Emulator downloaded project version has a major or minor value less than the last
controller downloaded project version. Only a Download All to the Emulator is
allowed in this situation. See Changes to the Project Version After Downloading on
page 39 for more detailed information.
38
Chapter 3
Procedure
1
Verify you have connected to the Emulator and configured the settings as described in
Configuring the Emulators Settings on page 16.
If you want to test Peer-to-Peer and/or Modbus communication with the Emulator,
verify you have selected the CM with the Peer-to-Peer and/or Modbus configuration
information you want to use. See Specifying Emulator Project Options on page 10 for
more information.
Note
If you want an SOE definition file (.SOE) or project backup file (.BT2) generated, verify
you have selected the appropriate file generation project options. See Specifying
Emulator Project Options on page 10 for more information.
CAUTION
Note
These files will look just like the .BT2 and .SOE files generated by
TriStation when you download an application to the controller. You will
not be able to distinguish between files generated by a download to the
Emulator, and files generated by a download to the controller. You may
want to make a note of the date and time each time you download the
application to the Emulator, so you can compare that timestamp to the
date/time of the generated files.
If a communication module is found in the application being downloaded, but it has not
been configured for Peer-to-Peer or Modbus communication, warning message(s) will
appear in the Messages pane. These messages will also appear if you have an EICM,
NCM, or a Trident v1.x CM configured in the application being downloaded. If you
dont want to test Peer-to-Peer or Modbus communication with the Emulator, ignore
these messages.
39
See the TriStation 1131 Developers Guide for more information about how the projects
download state affects downloading to the controller.
This section describes the rules for downloaded version numbering, and how the projects
downloaded version changes after a download to the Emulator.
Topics include:
The controller downloaded project version is the last version of the project file (.pt2)
downloaded to the controller. The version is provided in the format major.minor (for
example, in version 3.7, the major version is 3 and the minor version is 7).
A Download All operation increments the major version, and resets the minor
version to 0.
A Download Changes operation increments the minor version.
The Emulator downloaded project version is the last version of the project file (.pt2)
downloaded to the Emulator. The version is provided in the format
major.minor.EmulatorCount (for example, in version 3.7.12, the major version is 3, the
minor version is 7, and the EmulatorCount is 12).
The major.minor version is the same as the last controller downloaded project
version.
The EmulatorCount value is incremented sequentially after either a Download All
or a Download Changes to the Emulator.
If the Emulator downloaded project version has a major or minor value less than the
last controller downloaded project version, a Download Changes to the Emulator is
not allowed. Only a Download All to the Emulator is allowed in this situation. For
example, if the Emulator downloaded project version is 5.7.4 and the controller
downloaded project version is 5.8, a Download Changes operation to the Emulator
is not allowed.
40
Chapter 3
For example, if the existing downloaded version is 6.8 for both the Emulator and the
controller, a Download All to the Emulator will change the downloaded version for the
Emulator to 6.8.1, while maintaining the controllers downloaded version at 6.8.
If the project is then downloaded to the Emulator again, the Emulator downloaded
version will be 6.8.2 (where 2 indicates the project has been downloaded to the
Emulator twice since the last time it was downloaded to the controller).
A project that has not yet been downloaded to the controller, but has been downloaded to the
Emulator, will have a project version of 0.0.x, where x is the EmulatorCount value.
When you create a new project, the version is set to 0.0.0. The first time you download
to the Emulator, the project version is changed to 0.0.1.
The major.minor version is 0.0, because these values are not incremented until at least
one Download All to the controller (major version increment, such as 1.0.x) and one
Download Changes to the controller (minor version increment, such as 1.1.x) are
performed.
When a project has not yet been downloaded to the controller, you can perform either a
Download All or a Download Changes to the Emulator at any time.
For a project where the Emulator downloaded project version is less than the controller
downloaded version, a Download All is required, and the Emulator downloaded version will
be reset.
For example, if the existing downloaded version is 7.3.6 for the Emulator, but 8.2 for the
controller, you must perform a Download All to the Emulator.
After performing the Download All operation to the Emulator, the major.minor version
of the Emulator downloaded version is reset to 8.2.1 (to match the major.minor value of
the last controller downloaded version, and increment the EmulatorCount value).
You can now perform a Download Changes operation to the Emulator, which will
increment the Emulator downloaded version to 8.2.2.
41
The Emulator is dependent on the Windows timer to calculate the actual time to start a
scan. As a result, Windows timer inaccuracies can result in the actual scan time not
exactly equaling the requested scan time. You may be able to make the actual scan time
closer to the requested scan time by changing the requested scan time. For example, a
requested scan time of 300ms may result in an actual scan time of 307ms, while a
requested scan time of 200ms may result in an actual scan time of 200ms.
Procedure
1
The dialog box name differs, depending on the controller type and the
Emulators options settings. See Configuring the Emulators Settings on page 16
for more information.
Description
Req Scan
Real Scan
Displays the actual scan time for the application running on the
Emulator. The actual scan time is the actual length of time
required by the Emulator to complete the last scan. The actual scan
time is equal to or greater than the requested scan time.
Exec Time
Status
42
Chapter 3
Procedure
1
On the Emulator tree, expand Programs, and click the program you want to monitor.
Figure 4
.
or Single Step
Note
.
.
.
Single Emulator instances are terminated when the TriStation 1131 software
disconnects from the Emulator, but multiple Emulator instances must be
terminated manually.
Monitoring Variables
43
Monitoring Variables
This procedure explains how to monitor and test values for variables in an application running
on the Emulator.
Procedure
1
Double-click a variable to view its Item Properties dialog box and make changes to its
value.
For the Set Value property, enter a test value and click Confirm. The value is applied to
the selected variable.
44
Chapter 3
TR_MP_STATUS (Tricon)
SYS_MP_STATUS (Trident/Tri-GP)
For detailed information about these function blocks, please see the TriStation 1131 Libraries
Reference.
State transitions and/or changes to the controllers system status can impact the application
running on the controller. This procedure explains how to force changes to the MP system status
function blocks running on the Emulator, so you can test how your application reacts to MP
status changes.
As long as you save your configuration before you disconnect from the Emulator, changes you
make to the MP system status function block parameters will be saved as part of the Emulator
configuration file. This means you do not need to reconfigure these parameter settings each time
you download an application to the Emulator. See Saving the Emulator Configuration to a File
on page 20.
Note
The Emulator will not validate any logic when emulating the MP system status function
blocks. It is up to you to use a valid combination of output parameter settings. See the
TriStation 1131 Libraries Reference for assistance in determining valid combinations of
parameter settings.
Procedure
1
If you want to use previously saved changes to the MP system status function block
parameters, load the configuration file with the settings you want to use. See Loading
the Emulator Configuration from a File on page 21.
On the Emulator tree, expand Programs, and click the program with the MP system
status function blocks you want to test.
Click Run
The dialog box name differs, depending on the controller type and the
Emulators options settings. See Configuring the Emulators Settings on page 16
for more information.
45
Click the MP System Status tab. A list of the input and output parameters available for
the MP system status function block appears.
10
To save your parameter status changes for future use, be sure to save the
Emulator configuration file before you disconnect from the Emulator. See Saving
the Emulator Configuration to a File on page 20.
46
Chapter 3
A value is TRUE if the parameters check box is selected. A value is FALSE if the
parameters check box is cleared.
The following tables provide the default values for emulated Tricon and Trident/Tri-GP MP
system status parameters.
Table 3
Parameter
Status
MPMAIN
FALSE
MPBAD
FALSE
IOMAIN
FALSE
IOBAD
FALSE
Table 4
Parameter
Status
Parameter
Status
Parameter
Status
TMR
TRUE
NET_OK_LEFT
TRUE
LOCKED_RIGHT
TRUE
GE_DUAL
TRUE
PASS_MID
TRUE
BATT_OK_RIGHT
TRUE
NO_FLTS
TRUE
ACTIVE_MID
TRUE
NET_OK_RIGHT
TRUE
LOGIC_PWR1_OK
TRUE
INSTALLED_MID
TRUE
APP_RUNNING
TRUE
LOGIC_PWR2_OK
TRUE
LOCKED_MID
TRUE
TEMP_OK
TRUE
PASS_LEFT
TRUE
BATT_OK_MID
TRUE
SYSTEM_OK
TRUE
ACTIVE_LEFT
TRUE
NET_OK_MID
TRUE
LOGIC_PWR_OK
TRUE
INSTALLED_LEFT
TRUE
PASS_RIGHT
TRUE
FLD_PWR_OK
TRUE
LOCKED_LEFT
TRUE
ACTIVE_RIGHT
TRUE
PROG_ALARM_ON
FALSE
BATT_OK_LEFT
TRUE
INSTALLED_RIGHT
TRUE
47
SYS_RO32_STATUS (Trident/Tri-GP)
SYS_IO_STATUS (Trident/Tri-GP)
SYS_PI06_STATUS (Trident/Tri-GP)
SYS_AI32_STATUS (Trident/Tri-GP)
SYS_DO16_STATUS (Trident/Tri-GP)
SYS_AO04_STATUS (Trident/Tri-GP)
SYS_HRDI32_STATUS (Trident/Tri-GP)
SYS_DI16_AI16_STATUS (Trident/Tri-GP)
SYS_SDO16_STATUS (Trident/Tri-GP)
SYS_DI32_STATUS (Trident/Tri-GP)
For detailed information about these function blocks, please see the TriStation 1131 Libraries
Reference.
State transitions and/or changes to the controllers I/O module(s) status can impact the
application running on the controller. This procedure explains how to force changes to the I/O
status function blocks running on the Emulator, so you can test how your application reacts to
I/O status changes.
As long as you save your configuration before you disconnect from the Emulator, changes you
make to the I/O module status function block parameters will be saved as part of the Emulator
configuration file. This means you do not need to reconfigure these parameter settings each time
you download an application to the Emulator. See Saving the Emulator Configuration to a File
on page 20.
Note
The Emulator will not validate any logic when emulating the I/O module status
function blocks. It is up to you to use a valid combination of output parameter settings.
See the TriStation 1131 Libraries Reference for assistance in determining valid
combinations of parameter settings.
Procedure
1
If you want to use previously saved changes to the I/O module status function block
parameters, load the configuration file with the settings you want to use. See Loading
the Emulator Configuration from a File on page 21.
On the Emulator tree, expand Programs, and click the program with the I/O module
status function blocks you want to test.
Click Run
48
Chapter 3
Note
The dialog box name differs, depending on the controller type and Emulator
options settings. See Configuring the Emulators Settings on page 16 for more
information.
Select the I/O module you want to change status parameters for. Changes can only be
made to the parameters for one module at a time.
Note
The module selection list includes only the I/O modules that are configured in
the application currently running on the Emulator. For an explanation of the
module addresses provided in the list, see Interpreting the I/O Module Address
and Description on page 49.
A list of the parameters available for the selected modules I/O status function block
appears.
10
49
The default value for each status parameter is the value for a healthy module. See I/O
Module Status Parameter Default Values on page 50 for a complete list of default values.
11
12
To make changes to the status parameters for another I/O module, repeat steps 8 10.
Note
To save your parameter status changes for future use, be sure to save the
Emulator configuration file before you disconnect from the Emulator. See Saving
the Emulator Configuration to a File on page 20.
Chassis_Slot_Model_Description (Tricon)
IOP_Slot_Model_Description (Trident/Tri-GP)
For a visual reference of Tricon and Trident/Tri-GP controller slot locations, see the Enhanced
Diagnostic Monitor Users Guide.
50
Chapter 3
A value is TRUE if the parameters check box is selected. A value is FALSE if the
parameters check box is cleared.
The following tables provide the default values for emulated Tricon and Trident/Tri-GP I/O
module status parameters.
Table 5
Parameter
DI
DO
AI
AO
PI
RO
Thermocouple
SDO
EPI
PASS
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
FAIL
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
ACTIVE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
LOADFUSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
INSTALLED
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
VOTER_FAULT
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
OVD_ENABLED
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
NOGOOD
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
Table 6
Parameter
DI
DO
AI
AO
PI
RO
HRDI
SDO
EPI
DI_AI
TMR
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
GE_DUAL
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
GE_SINGLE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
NO_FLTS
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
LOGIC_PWR1_OK
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
LOGIC_PWR2_OK
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
PASS_LEFT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
ACTIVE_LEFT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
INSTALLED_LEFT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
LOCKED_LEFT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
NO_ACTIVE_FLTS
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
PASS_RIGHT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
ACTIVE_RIGHT
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
FALSE
INSTALLED_RIGHT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
LOCKED_RIGHT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
NO_FLD_ALARM_LEFT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
Table 6
51
Parameter
DI
DO
AI
AO
PI
RO
HRDI
SDO
EPI
DI_AI
NO_FLD_ALARM_RIGHT
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
FLD_PWR1_OK
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
FLD_PWR2_OK
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
NO_FLD_FLTS
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
NO_VOTER_FLTS
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
TRUE
FLD_OK_01
TRUE
FLD_OK_02
TRUE
FLD_OK_03
TRUE
FLD_OK_04
TRUE
SIGNAL_PRESENT_1
TRUE
SIGNAL_PRESENT_2
TRUE
SIGNAL_PRESENT_3
TRUE
SIGNAL_PRESENT_4
TRUE
SIGNAL_PRESENT_5
TRUE
SIGNAL_PRESENT_6
TRUE
INPUT_STABLE_1
TRUE
INPUT_STABLE_2
TRUE
INPUT_STABLE_3
TRUE
INPUT_STABLE_4
TRUE
INPUT_STABLE_5
TRUE
INPUT_STABLE_6
TRUE
OVD_RUNNING_01_16
0xFFFF
0xFFFF
FLD_OK_01_16
0xFFFF
0xFFFF
SPRVSD_ON_01_16
0xFFFF
a. A dash () indicates that the parameter does not apply to this module.
52
Chapter 3
Procedure
1
Double-click a variable, and select the Annotate check box on the Variable tab.
Annotate
check box
Click the Macros button to change the macro identified with the annotation.
To paste the macro, close the Edit Macros dialog box, click in the Annotation area,
and press Ctrl+V.
Disabling Points
53
Disabling Points
While your program is running on the Emulator, you can disable points so that you can assess
the impact of disabling those points in an application running on the controller.
Disabling points on the Emulator is completely separate from disabling points on the controller.
Points that are disabled in the program running on the Emulator will NOT also be disabled in
the application that is currently running on (or will be downloaded to) the controller.
When a point is disabled, it holds its last value. Inputs from field instruments or the application
running on the Emulator do not change the value of the point. Disabling points is typically used
when field instruments need to be replaced or repaired. Disabling points can increase the scan
time.
For Tricon v9.x controllers, a maximum of 64 points can be disabled at any one time. For Tricon
v10.x controllers, a maximum of 256 points can be disabled. There is no maximum to the
number of points that can be disabled for Trident or Tri-GP controllers.
When you disable one or more points, the number of disabled points output parameter
(POINTS_DISABLED) in the TR_PROGRAM_STATUS (Tricon) or SYS_MP_EXT_STATUS
(Trident/Tri-GP) function block is updated on the Emulator. Additionally, the alarm state for
disabled points is also changed to TRUE in the TR_SHUTDOWN (Tricon) or SYS_SHUTDOWN
(Trident/Tri-GP) function block. See the TriStation 1131 Libraries Reference for more information
about these function blocks.
In order to disable points in the Emulator, the Allow Disabling of Points property must be
selected on the TriStation 1131 Operating Parameters screen. Enabling this property can
increase the scan time, regardless of whether any points are actually disabled. See the TriStation
1131 Developers Guide for more information.
The disabling (and subsequent re-enabling) of points is saved to the TriStation 1131 Project
History. To view information about when a point was disabled, and who disabled it, from the
Project menu, select View Project History.
Topics include:
54
Chapter 3
Procedure
1
Click Run
Procedure
1
Click Run
If desired, select the points you want to enable, and then click OK.
You can also enable points from the List of Disabled Points dialog box.
Click Run
Click Run
All points that are currently disabled on the Emulator are re-enabled.
Index
configuration
Emulator 16
Modbus 12, 35
Peer-to-Peer 12, 22, 26
Peer-to-Peer ports 24
TSAA server 18
ALARM_DEVIATION_DINT 6
ALARM_DEVIATION_REAL 6
ALARM_LEVEL_DINT 6
ALARM_LEVEL_REAL 6
ALARM_RATEOFCHANGE_DINT 6
ALARM_RATEOFCHANGE_REAL 6
ALARM_TRIP 6
alarms, process 6
alias ranges 33
alias-to-bin offset, SOE 33
configuration file
Emulator 20, 21
saving I/O module parameters in 47
saving MP parameters in 44
connecting to Emulator 16
customer support iv
DDE Server 13
APP_LOCKED parameter 46
applications
configuring Peer-to-Peer in 22
differences on Emulator 30
downloading 7, 36
testing 30
disabled points
re-enabling 54
viewing 54
B
backup file (.bt2) generation 11, 38
bin numbers 33
board addresses 49
broadcast messaging 4
BYPASS_BOOL 6
BYPASS_DINT 6
BYPASS_REAL 6
C
Change State to Download All command 37
communication
client/server 30
network 4
redundant 4
disabling points 7, 53
download aborted message 11
Download All command 7, 36
Download Changes command 7, 37
download state 39
downloaded project version 37, 39, 40
downloading
applications 7, 36
disabled points, affect on 53
Modbus configuration 12, 35, 38
Peer-to-Peer configuration 12, 38
project version changes after 39
timeout value 11, 38
to Emulator 36
warning messages during 38
E
Emulator
accessing 13
56
Index
Emulator (continued)
associating with TriStation 1131 8
configuring 16
connecting to 16
differences from controller 30
downloading to 7, 36
features 4
installing 8
instances of 3, 11, 13, 31
node number 17
overview 2
project options 10
rules for communication 30
system requirements 8
uninstalling 9
updating installation 9
IP multicasting 4, 18, 19
L
libraries
functions not emulated 30
process alarms 6
updating 7
List Disabled Points command 54
loading Emulator configuration 21
M
macros, in variables 52
major.minor version 39
event, defined 4, 32
Modbus
downloading configuration 35
functionality 5
module selection 12
overview 5
testing with Emulator 35
warning messages 38
F
file generation 11, 38
forcing points 7, 53
function blocks
I/O module status 6, 47
MP status 6, 44
non-emulated 30
Peer-to-Peer 27
process alarm 6
SOE 4, 32
system status 6, 44, 47
module addresses 49
monitoring
execution times 41
program execution 42
scan time 41
variables 43
MP status
differences on Emulator 46
function blocks 6, 44
parameter defaults 46
halting a program 42
I
I/O module status
board addresses 49
function blocks 6, 47
parameter defaults 50
installation 8
instances, multiple 3, 11, 13, 31
Invensys contact information iv
IP address
Emulator 17
multicasting 19
primary server 17
redundant server 19
N
network communication 4
node number
Emulator 17
Peer-to-Peer 22
TCM 23
Node Number property 17
Number of Instances property 11
Index
O
offset, alias-to-bin 33
options, setting 10
protocols
emulating 4
supported 2
57
S
saving Emulator configuration 20
scan time, monitoring 41
Server IP Address property 17
SET_TRICON_CLOCK command, TSAA 4
SOE
alias-to-bin offset 33
controllers emulated 31
definition file (.SOE) 11, 32, 38
function blocks supported 4, 32
testing 32
variables, data for 32
SOECLR function block 4, 32
SOESTAT function block 4, 32
SOESTOP function block 4, 32
SOESTRT function block 4, 32
starting the Emulator 13
stopping a program 42
POUs 38
SYS_AI32_STATUS 7, 47
SYS_AO04_STATUS 7, 47
SYS_DI16_AI16_STATUS 7, 47
SYS_DI32_STATUS 7, 47
project options 10
SYS_DO16_STATUS 7, 47
project state 39
SYS_IO_STATUS 7, 47
project version
changes 39
downloaded 39, 40
SYS_MP_EXT_STATUS 53
SYS_MP_STATUS 6, 44, 46
58
Index
SYS_PI06_STATUS 7, 47
SYS_RO32_STATUS 7, 47
SYS_SDO16_STATUS 7, 47
SYS_SHUTDOWN 53
system requirements 8
TSAA
broadcast messaging 4
commands supported 4
enabling in Emulator 18
IP multicasting 4, 18, 19
redundant server 19
server configuration 18
UDP port 18
TCM
Modbus support 5
node number 23
Peer-to-Peer ports 24
technical support iv
UDP ports 13
Peer-to-Peer 18, 25
TSAA 18
testing
applications 30
I/O module status changes 47
Modbus communication 35
MP status changes 44
Peer-to-Peer communication 34
SOE communication 32
U
UDP Base Port Number property 25
uninstalling 9
update rate, TSAA multicasting 18
updating the Emulator 9
TR_MP_STATUS 6, 44
variables
adding annotations to 52
changing value of 43
macros in 52
monitoring 43
SOE data for 32
TR_PROGRAM_STATUS 53
TR_SHUTDOWN 53
TR_SLOT_STATUS 7, 47
training iv
transfer delay time, emulation of 34
Tricon
I/O module status 47
Modbus functionality 5
MP status 44
TRICON_CPSTATUS_REQ command, TSAA 4
TRICON_DATA_REQ command, TSAA 4
TRICON_GET_SYMBOL_REQ 4
TRICON_SOE_REQ command, TSAA 4
Trident
I/O module status 47
Modbus functionality 5
MP status 44
Trident 2.x Peer-to-Peer ports 24
Tri-GP
I/O module status 47
Modbus functionality 5
MP status 44
Peer-to-Peer ports 24
TriStation 1131
associating with Emulator 8
Peer-to-Peer configuration 22
TRxEMCodeEmulator dialog box 16
version, project
changes 39
major.minor 39
number, downloaded 40
viewing disabled points 54
W
warning messages, Modbus or Peer-to-Peer 38
WRITE_TRICON_DATA command, TSAA 4