15 system re-initialization, 15 system rećinitialization – Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 User Manual
Page 156
![background image](/manuals/580826/156/background.png)
10Ć8
AutoMax Programming Executive Version 3.x
The task is stopped and will not go into run again until you put it
into run using the RUN command described in 15.1.
2. You stop all tasks in the rack to which you are connected, either
directly or over a network, using the STOPĆALL command
described in 16.2.
All tasks in the rack are stopped and all I/O modules are cleared,
i.e., set to 0, false, or off.
Application tasks will not go into run again until you put them all
into run using the RUNĆALL command described in 15.2. You can
also put the tasks into run individually using the RUN command
described in 15.1.
3. A StopĆAll fault occurs.
All tasks in the rack are stopped and all I/O modules are cleared.
The Processor module detecting the fault will display an error
code. See 10.12 for more information about stopĆall faults.
Before you run tasks again, you should first clear the error log
described in 19.0. Application tasks will not go into run again
until you use the RUN or RUNĆALL commands described in 15.1
and 15.2, respectively.
4. You cycle power or a power failure occurs.
All tasks in the rack are stopped and all I/O modules are cleared.
When power is returned to the system, a reĆinitialization occurs.
Application tasks in the rack can be put into run in two ways after
power comes back on: manually, using the RUN or RUNĆALL
commands described in 15.1 and 15.2, respectively; or
automatically by the system if AUTOĆRUN was enabled at the
time power went off.
AUTOĆRUN puts into run only those application tasks that were
running when power went off. It will not put any tasks into run if
any errors occurred prior to power going off, or if any errors
occur during the system reĆstart.
10.15 System ReĆInitialization
System reĆinitialization refers to a condition that occurs in a rack that
contains at least one Processor module. It does not necessarily affect
other racks on networks connected to the rack through 57C404.
57C404A, or 57C404B modules.
A system reĆinitialization will occur under the following conditions:
D when the system powersĆup after power to the system is turned
off either by cycling power or through a power failure,
D after the occurrence of a STOPĆALL fault,
D after you issue a STOPĆALL command
The following steps occur during a system reĆinitialization:
1. The following codes are cleared:
drive fault codes 81" through 86"
status codes d0" through dF"
configuration task error codes E0" through EF"
Any other fault codes are reĆdisplayed.