Scripting

Wonderware Application Server script attributes

| Greg Dubiel

The following table describes the scripting attributes available in Wonderware Application Server (aka Wonderware System Platform, aka ArchestrA software) version 3.x for each script defined in the Galaxy:

Attribute Description Run-Time Access (Supervisory, User, Read-Only, None)
<Script>.AsyncShutdownCmd If set to TRUE, the currently executing asynchronous script will be requested to shut down. This does not mean that the script actually will shut down. The script must be written to check this flag. Supervisory, User
<Script>.Disabled If set to TRUE, the calculation of the expression and the execution of the script code will be stopped. Supervisory, User
<Script>.ErrorCnt The number of errors detected for this script since last reset. Read-Only
<Script>.ExecutionCnt The number of times this script has executed since the last reset. Only applies to Execute type scripts, both synchronous and asynchronous. Read-Only
<Script>.ExecutionError.Condition If TRUE, the script engine encountered an error, such as divide-by-zero, .NET error or execution timeout) during last execution. This attribute can be alarmed. If alarmed, the alarm message is ExecutionError.Desc. Read-Only
<Script>.ExecutionError.Desc The error message associated with the execution error condition. Read-Only
<Script>.ExecutionTime The amount of time, in milliseconds, the script has been executing for asynchronous scripts. For synchronous scripts, this attribute reflects the time of the last execute. When the script has finished executing, the value remains at the final elapsed time for the script. When the script is restarted, this value is reset to zero (0). Read-Only
<Script>.ExecutionTimeAvg The average per scan execution time, in milliseconds, since the script was last reset. Read-Only
<Script>.ExecutionTimeStamp The last time the script executed. Read-Only
<Script>.State Indicates the state the object’s script is in: Initializing, Error, Disabled, Busy, Ready.

  • Initializing indicates at least one of the script’s external references in the script expression is still initializing.
  • Error indicates an error occurred since the last time the script was triggered.
  • Disabled indicates the script execution was disabled.
  • Busy indicates that the script is currently executing (only applies to asynchronous scripts).
  • Ready indicates that an asynchronous script is not currently executing or that a synchronous script is not in an error or disabled state.
 Read-Only
<Script>.StatsReset If set to TRUE, all statistics will be set to zero. Supervisory, User

Three Wonderware Tech Notes on deploying custom script function libraries in Wonderware Application Server are available

| Greg Dubiel

Wonderware Application Server provides you the ability to leverage the .NET development language for custom and advanced functionality made available through the ArchestrA Integrated Development Environment (IDE).

Custom Script Function Libraries are integrated with Wonderware Application Server by

  • Importing multiple, independent DLLs, or;
  • Importing multiple DLLs that have dependencies into the Galaxy.

Wonderware Application Server accommodates importing of multiple DLLs and DLLs with dependencies through the use of aaSLIB files. aaSLIB files make managing multiple DLLs and their dependencies easier by eliminating the need to track multiple DLLs.

Wonderware recently released three new Tech Notes on deploying custom script function libraries in Wonderware Application Server:

Wonderware customers from outside of the Wonderware PacWest distribution area can access the Tech Notes on the Wonderware Support Website.