Technical information

Controller States and Behaviors
62
EIO0000000638 04/2012
Reboot
Effect:
Commands a reboot of the controller.
Starting Conditions:
z Any state.
z ControllerLockout = 0.
Methods for Issuing the Reboot Command:
z Power cycle.
z REBOOT by Script: The file transfer script on a USB memory key issues a
REBOOT as its final command. The controller will be rebooted into the
STOPPED state provided the other conditions of the boot sequence allow this to
occur. Refer to Saving your Application and Firmware on a USB Memory Key
(see page 93) for further details.
Effects of the Reboot:
1. The state of the controller depends on a number of conditions:
a. The controller state will be RUNNING if:
- The Reboot was provoked by a power cycle, and
- The Reboot was provoked by a power cycle and the HMI application had
been downloaded using a Multiple Download command with option Start all
application after download or online change selected.
- The Reboot was provoked by an HMI application download using a Multiple
Download command with option Start all application after download or
online change selected.
b. The controller state will be STOPPED if:
- Controller state was STOPPED prior to a power cycle, or
- The Reboot was provoked by a power cycle and the HMI application had
been downloaded using a Multiple Download command with option Start all
application after download or online change not selected
.
- The Reboot was provoked by an HMI application download using a Multiple
Download command with option Start all application after download or
online change not selected
.
c. The controller state will be EMPTY if there is no boot application or the boot
application is invalid.
d. The controller state will be INVALID_OS if there is no valid OS.
2. Forcing is maintained if the boot application is loaded successfully. If not, forcing
is erased.
3. Diagnostic indications for detected errors are reset.
4. The values of the retain variables are restored if saved context is valid.
5. The values of the retain-persistent variables are restored if saved context is valid.
6. All non-located and non-remanent variables are reset to their initialization values.