Automatically included variables
- Last UpdatedSep 11, 2025
- 1 minute read
The following table list the variables automatically included in the cycle script working environment. You can use these variables in your scripts. You should not create variables or functions that use these names.
|
Command |
Description |
|
Log |
A sequence uses this variable to log diagnostics information. The syntax is similar to Console.WriteLine(). For example, Log.Information(), Log.Error(), and Log.Warning() log to sequence-specific log files. See Log files for more information. Non-fatal log messages also appear in the rts.exe console window (when you manually run a sequence). |
|
LogsPath |
The full path of the \Logs folder for AVEVA Process Simulation. |
|
SequenceName |
The name of the running sequence. |
|
SequencePath |
The full path of the sequence folder. You can use this variable to access other files in that folder. |
|
SequencesPath |
The full path of the root \sequences folder in the AVEVA Real-Time System (RTS) installation. |
|
SequencesLibPath |
The full path of the \Libs folder for AVEVA Process Simulation. |
|
sc |
The variable that you use to access the Scripting Interface object. See Access AVEVA Process Simulation for more information. |
|
HistTimestamp |
The history timestamp that the script should use to get data from a historian. Typically, the scheduler sets this variable. The value is in local time, not Coordinated Universal Time (UTC). When you pass this value to a Scripting Interface TagCollection function, you should convert it to UTC by using the following code: HistTimestamp.ToUniversalTime().ToString() |
|
Activity |
The variable that you use to access help classes to work with the Scripting Interface. See Access AVEVA Process Simulation for more information. |