Rockwell Automation GMLC Reference Manual User Manual
Page 537
![background image](/manuals/580918/537/background.png)
Publication GMLC-5.2 - November 1999
500
Controller Variables
Use the Current_Task variable when several tasks use identical
(duplicate) modules in a diagram. Within a duplicate module, you can use
the Current_Task variable to make decisions based on which task is
currently executing the module.
CPU Utilization
CPU_utilization is a floating-point value, between 0 and 1, which
represents the relative amount of the available CPU capacity currently
being used for motion-related calculations.
In the Tag Explorer, select General System Variables, then select
CPU_utilitzation in the Tag Window.
You can use the CPU_utilization variable during application development
to check whether program execution and RIO Adapter block transfer
speed are being degraded due to the application’s motion requirements.
Subtracting the CPU_utilization from 1 yields the relative amount of CPU
capacity available for processing the application program (generated from
the GML Commander diagram and downloaded to the motion controller).
See the CPU Utilization chapter for more information.
CPU Utilization Peak
The CPU_utilization_peak variable (enabled only in iCODE versions 3.5
and higher) displays the historic high value for the CPU_utilization
variable. This value is reset at power up, and when you press the motion
controller’s Reset button.
In the Tag Explorer, select General System Variables, then select
CPU_utilitzation_peak in the Tag Window.
Controller Address
If Extended AxisLink is not selected in the General page of the Configure
Control Options dialog box, Controller_address is an integer value from 0
to 7, and equals the current setting of the motion controller’s front panel
ADDRESS
selector switch.