Controllers

Produce code for simulation for an application

Each controller has defined compiler options. The Code Generator uses these parameters to to build and optimize the controller code. In the Compilation Options for a controller, select the type of code to generate according to corresponding equipment and set up the optimizer parameters according to the expected compilation and run-time requirements. The general compiler options are:

(Read-only) Compiler produces TIC code

For the 9110 processor module, enables the battery alarm informing of a low voltage for the battery and need for replacement. For standard and mixed controllers, the default value is enabled. For Eurocard controllers, the default value is disabled.

Resets faulty processors from a remote location and joins processors to a running system. To enable, enter a non-zero hexadecimal value matching the value of the control integer

Allow Remote Fault Reset

. Possible values range from 0x1 to 0xFFFFFFFF, or 0x0 to disable.

Memory space allocated for I/O structures. The default value is 150000 bytes.

Space reserved for monitoring variables, constants, and temporary compiler variables

(Read-only) Target type to which is attached the controller

For targets supporting online changes, enables modifying I/O devices and structures while running an application online.

Plain text

(Read-only) Compilation version number

Rich text

(Read-only) Full name of the controller indicating the project to which it belongs

(Read-only) Date of the last compilation of the controller code

(Read-only) Name of the controller. Controller are limited to 128 characters beginning with a letter followed by letters, digits, and single underscores. The last character for a controller name must be a letter or digit; controller names cannot end with an underscore character. Reserved words, defined words, or data types such as, elementary, structures, or arrays are not valid names. The same type of elements within a scope must have unique names.

Unique number identifying the controller within the project. Also known as the resource number in

AADvance Discover

. This number is automatically assigned. When changing the number, assign a value that is unique within the project. The resource number identifies the physical AADvance controller that runs the application code.

(Read-only) Controller is protected by a password controlling its access

(Read-only) Complete path where the controller files are stored on the computer. The path is automatically assigned to a controller folder within the project folder.

Defines the amount of memory that is reserved for all updates on the controller. The

Code Size

value can be increased up to 1441640 bytes.

The total usage of the controller memory space is the sum of the

Code Size

value and the length of the controller name, project name, and POU names.

For example, controller memory space usage can consist of these values:

Or

Maximum number of POUs (other than SFC) that can be added while performing updates

The memory space allocated for step and transition structures. A step requires 40 bytes and a transition requires 20 bytes.

For updates, the amount of memory reserved for adding variables data. When generating monitoring symbols information for a POU, the same amount of memory is also reserved for the POU.

The maximum time, in milliseconds, that the controller outputs remain in the ON state after detecting important diagnostic or application faults. The outputs go into their specified safe states when exceeds the defined PST. Set the PST for the controller. The default value for the controller is 2500 ms. By default, each group of I/O modules inherits the PST from the controller. Also set an alternate PST for each I/O group.

Amount of time given to each cycle. If a cycle is completed within the cycle timing period, the system waits until this period has elapsed before starting a new cycle. The cycle consists of scanning the physical inputs of the process to drive, executing the POUs of the controller, then updating physical outputs. The virtual machine executes the controller code according to the execution rules.

Unit of measure for the cycle time. Possible values are ms (milliseconds) or µs (microseconds). To use µs, the equipment must support this unit of measure.

Store errors. Define

Nb Stored Errors

.

Location where retained values are stored (the required syntax depends on the implementation).

Number of entries. For example, the size of the queue (FIFO) in which detected errors are stored

Controller executes in real time or cycle-to-cycle. Real-time mode is the run time normal execution mode where the cycle timing triggers the controller cycles. In cycle-to-cycle mode, the virtual machine loads the controller code but does not execute it until execute one cycle or activate real-time mode. When generating debug information for POUs, the controller automatically switches to step-by-step mode when the application encounters a breakpoint.

Controller cycle executes according to the defined

Cycle Time

For Sequential Function Chart (SFC), specifies factor of dynamic behavior limits determining the amount of memory, allocated by a controller at initialization time, designated to manage token moving. The amount of allocated memory is calculated as a linear relation with the number of SFC POUs:

For SFC, specifies factor of dynamic behavior limits determining the amount of memory, allocated by a controller at initialization time, designated to manage token moving. The amount of allocated memory is calculated as a linear relation with the number of SFC POUs:

Type of the controller. Possible values are:

Export controllers as exchange files (*.pxf).

If a

CIP

consumer link is defined for a controller and the controller is deleted before adding

CIP

links to other controllers, close and then reopen

AADvance-Trusted SIS Workstation software

.