Glossary
- Last UpdatedJun 30, 2020
- 3 minute read
|
Term |
Description |
|
Application |
In TriStation 1131, an application is the compiled code running in a Triconex controller |
|
Backtrack |
A snapshot in time of the simulator process model, I/A Series controls, historian, and alarms. Occurs automatically every 60 seconds while the simulation is running. |
|
Block |
A data structure that resides in Main Processor memory |
|
Controller |
A Triconex controller includes Main Processors, communication and I/O modules, and field termination panels |
|
DEW |
Data Entry Window, which is used to enter model parameters into DYNSIM model objects |
|
Download |
The process of transferring a compiled application to a Triconex controller |
|
DSS |
Dynamic Simulation Suite (Infrastructure for the simulator) |
|
DYNSIM |
AVEVA Dynamic Simulation (aka DYNSIM Dynamic Simulation) |
|
FS |
Flow Sheet |
|
Function Block |
A Program Organization Unit (POU) defining input and output parameters used as connections. Function blocks define an algorithm running each time the function block is executed. The data in a function block is persistent from one execution of the function block to the next. |
|
GUI |
Graphical User Interface |
|
IC |
Initial Condition; a snapshot in time of the simulator process model, I/A Series controls, historian, and alarms. Press the IC Save button in the DYNSIM Graphical User Interface to save an IC. |
|
I/O |
Input/Output – physical communication to and from the control system and plant thermocouples, pressure transmitters, actuators, etc. that control plant operation |
|
Library |
In TriStation 1131, a set of functions, function blocks, and data types automatically included or added to projects. Each TriStation 1131 project includes libraries, standard functions, and controller-specific functions. In DYNSIM, a set of related function blocks that appear under the Types Tree. |
|
Memory Point |
In TriStation 1131, a memory point stores application data such as calculation values and program state information. An application accesses memory points by associating tagnames with memory point addresses. A memory point address has the format: Mxy.<point> "x" indicates the data type (B=bool, D=dint, R=real) "y" indicates the type of modbus alias (W-read/write, R-read only, N-Unaliased). Example: the address MBW.46 references memory point 46 in the BOOL Write Aliased controller memory table. |
|
Module |
An active field-replaceable unit consisting of an electronic circuit assembly housed in a metal spine. Also called board or card. |
|
POU |
Stands for Program Organization Unit. In TriStation 1131 POUs include programs, functions, and function blocks |
|
Program |
The highest-level Program Organization Unit (POU). Programs are executed by the controller and are the only POUs that can access input, output, and memory points. |
|
PT2 |
File extension for a TriStation 1131 program. For the purposes of this document, PT2 will refer to both PT2 and PT2x files. |
|
SIM4ME |
Term for any of SimSci’s software product lines |
|
S4M/JS4M |
DYNSIM Simulation file extension |
|
Scan Surplus |
The time left after the TriStation 1131 application and communication messages have been processed by the controller |
|
Scan Time |
The time required by a controller to process the TriStation 1131 application and associated communication messages |
|
SimExec |
See Simulation Executive |
|
Simulation Executive |
Controls time, synchronizes engines, sends data between engines in a simulator |
|
Snapshot |
An Initial Condition or Backtrack that contains a picture of the state of a simulation engine at a specific point in time. For the FSIM Engine, it is a picture of the Control Processor (CP) database memory. |
|
Tagname |
A name that identifies a global variable that is used to access input, output, and memory points in a TriStation controller file. |
|
TPM |
Trainee Performance Monitoring |
|
TRISIM |
AVEVA Triconex Simulation |
|
UOM |
Unit of Measure |
|
XREF |
Cross Reference |