Technical information

Controller States and Behaviors
EIO0000000638 04/2012 63
7. All fieldbus communications are stopped and restarted after the boot application
is loaded successfully.
8. All I/O are reset to their initialization values and then to their user-configured
default values if the controller assumes a STOPPED state after the reboot.
For details on variables, refer to Remanent Variables (see page 67).
NOTE: The Check context test concludes that the context is valid when the
application and the remanent variables are the same as defined in the Boot
application.
NOTE: If you make an online change to your application program while your
controller is in the RUNNING or STOPPED state but do not manually update your
Boot application, the controller will detect a difference in context at the next reboot,
the remanent variables will be reset as per a Reset cold command, and the
controller will enter the STOPPED state.
Download Application
Effect:
Loads your application executable into the RAM memory. Optionally, creates
a Boot application in the Flash memory.
Starting Conditions:
z RUNNING, STOPPED, HALT, and EMPTY states.
z ControllerLockout = 0.
Methods for Issuing the Download Application Command:
z SoMachine:
Two options exist for downloading a full application:
z Download command.
z Multiple Download command.
For important information on the application download commands, refer to
Controller State Diagram (see page 48).
z FTP: Load Boot application file to the Flash memory using FTP. The updated file
is applied at the next reboot.
z USB memory key: Load Boot application file using a USB memory key connected
to the controller USB host port. The updated file is applied at the next reboot.
Refer to Saving your Application and Firmware on a USB Memory Key
(see page 93) for further details.
Effects of the SoMachine Download Command:
1. The existing application stops and then is erased.
2. If valid, the new application is loaded and the controller assumes a STOPPED
state.
3. Forcing is erased.
4. Diagnostic indications for detected errors are reset.
5. The values of the retain variables are reset to their initialization values.
6. The values of any existing retain-persistent variables are maintained.
7. All non-located and non-remanent variables are reset to their initialization values.