Rockwell Automation 57C620 AutoMax Programming Executive Version 3.8 - Manual (Page 166)

12Ć4 AutoMax Programming Executive Version 3.x
If there is any discrepancy between the information in the
configuration for the rack and an actual application task, the fault
code E" 0" is displayed on the AutoMax Processor and no
application tasks are reĆstarted. In a multiple Processor configuration,
this check is performed by one Processor only. The particular
Processor on which the fault code appears bears no relation to the
location of the problem.
Tasks are reĆstarted in order of priority from highest to lowest on each
Processor module. Tasks with the same priority are started in
alphabetical order. Tasks on different Processors are not
synchronized. In addition, unless the programmer uses interrupts to
synchronize them, tasks on UDC modules are not synchronized with
tasks on AutoMax Processors.
Task execution always begins from the first statement in the task,
regardless of the point at which the task stopped. Tasks on different
UDC modules will be reĆstarted independently of each other. The
drive A task is always executed first, followed by the drive B task.
UDC task execution always begins from the first statement in the
task, regardless of the point at which the task may have been
stopped. After CCLK is enabled, the starting of tasks on all UDC
modules in the rack will be coordinated.
12.4.1 Application Tasks Not ReĆStarted with AUTOĆRUN
The following tasks are not reĆstarted automatically when the system
powers up and AUTOĆRUN is enabled.
1. Any task that was was not in run when power was turned off. You
must put the task into run manually. See 15.0 for more
information about running tasks.
2. Any task that was stopped by a STOP or STOPĆALL command
issued from the personal computer. You must put the task(s) into
run manually. See 15.0 for more information about running tasks.
3. Any task that was stopped by the occurrence of a STOPĆALL fault
described in 10.12. You should first clear any error codes from
the error log or from Processor LEDs and then put the task into
run manually. See 19.0 for more information about clearing the
error log or LEDs and 15.0 for more information about running
tasks.
12.4.2 Application Task AUTOĆRUN and Memory
Fragmentation
Occasionally, there may be insufficient memory in the Processor(s)
after a system reĆstart to accommodate application tasks that were
initially loaded (recall that the tasks must be built" again) due to
memory fragmentation. Since system reĆstarts are inevitable, after
loading the rack configuration and application tasks, you should
verify that there will be sufficient memory should a reĆstart occur. You
can do this by issuing a STOPĆALL command from the personal
computer or by cycling power and then checking that all application
tasks are present and installed