Modifying Cycle Timing

While running an application online, for example, connected, the cycle timing for individual controllers can be modified. When modifying cycle timing, view the following cycle timing information from system variables for individual controllers:
Cycle Information
System Variable
Description
True Cycle Time
__SYSVA_TCYTRUECURRENT
The real duration of a cycle
Current Cycle Time
__SYSVA_TCYCURRENT
The time spent with the virtual machine
Maximum Cycle Time
__SYSVA_TCYMAXIMUM
The longest period of time used for a current cycle (__SYSVA_TCYCURRENT), since connecting to the controller
Cycle Overflow
__SYSVA_TCYOVERFLOW
The number of current cycles (__SYSVA_TCYCURRENT) having exceeded the programmed cycle time
Programmed Cycle Time
__SYSVA_TCYCYCTIME
The defined cycle time for the controller
The minimum cycle time for an AADvance application is 64 milliseconds. The cycle time for most applications is between 64 and 260 milliseconds, depending on the system size. The cycle time increases during an update or when a new processor is synchronizing.
TIP: Setting the Programmed Cycle Time to 0 allows the controller to execute cycles as fast as possible, for example, at a rate close to the True Cycle Time.
To modify cycle timing
  1. From the
    Online
     menu, click
    Cycle Timing
    .
    The
    Cycle Timing
     dialog box displays cycle time information for all controllers defined in the project.
  2. Select the controller for which to modify the cycle timing, indicate a new programmed cycle time, and then click
    Update
    .
  3. (optional) To refresh the maximum cycle time and cycle overflow information display for controllers, click
    Reset all Statistics
    .
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal