Effect: Commands a transition to the RUNNING controller state.
Starting Conditions: BOOTING or STOPPED state.
Methods for Issuing a Run Command:
oRun/Stop Input: If configured, command a rising edge to the Run/Stop input (assuming the Run/Stop switch is in the RUN position). Set the Run/Stop to 1 for all of the subsequent optionsto be effective.
Refer to Run/Stop Input for more information.
oSoMachine Online Menu: Select the Start command.
oBy an HMI command using the PLC_W. q_wPLCControl and PLC_W. q_uiOpenPLCControl system variables of the PLCSystem library.
oLogin with online change option: An online change (partial download) initiated while the controller is in the RUNNING state returns the controller to the RUNNING state if successful.
oMultiple Download Command: sets the controllers into the RUNNING state if the Start all applications after download or online change option is selected, irrespective of whether the targeted controllers were initially in the RUNNING, STOPPED, HALT, or EMPTY state.
oThe controller is restarted into the RUNNING state automatically under certain conditions.
Refer to Controller State Diagram for further details.
Effect: Commands a transition to the STOPPED controller state.
Starting Conditions: BOOTING, EMPTY, or RUNNING state.
Methods for Issuing a Stop Command:
oRun/Stop Input: If configured, command a value of 0 to the Run/Stop input. Refer to Run/Stop Input for more information.
oSoMachine Online Menu: Select the Stop command.
oBy an internal call by the application or an HMI command using the PLC_W. q_wPLCControl and PLC_W. q_uiOpenPLCControl system variables of the PLCSystem library.
oLogin with online change option: An online change (partial download) initiated while the controller is in the STOPPED state returns the controller to the STOPPED state if successful.
oDownload Command: implicitly sets the controller into the STOPPED state.
oMultiple Download Command: sets the controllers into the STOPPED state if the Start all applications after download or online change option is not selected, irrespective of whether the targeted controllers were initially in the RUNNING, STOPPED, HALT, or EMPTY state.
oREBOOT by USB file system download: The application download from a USB memory key will issue 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 and Reboot for further details.
oThe controller is restarted into the STOPPED state automatically under certain conditions.
Refer to Controller State Diagram for further details.
Effect: Resets all variables, except for the remanent variables, to their default values. Places the controller into the STOPPED state.
Starting Conditions:
oRUNNING, STOPPED, or HALT states.
oControllerLockout = 0.
Methods for Issuing a Reset Warm Command:
oSoMachine Online Menu: Select the Reset warm command.
oBy an internal call by the application or an HMI command using the PLC_W. q_wPLCControl and PLC_W. q_uiOpenPLCControl system variables of the PLCSystem library.
Effects of the Reset Warm Command:
1.The application stops.
2.Forcing is erased.
3.Diagnostic indications for detected errors are reset.
4.The values of the retain variables are maintained.
5.The values of the retain-persistent variables are maintained.
6.All non-located and non-remanent variables are reset to their initialization values.
7.The values of %MW0 to %MW65535 registers are maintained.
8.All fieldbus communications are stopped and then restarted after the reset is complete.
9.All I/O are reset to their initialization values.
For details on variables, refer to Remanent Variables.
Effect: Resets all variables, except for the retain-persistent type of remanent variables, to their initialization values. Places the controller into the STOPPED state.
Starting Conditions:
oRUNNING, STOPPED, or HALT states.
oControllerLockout = 0.
Methods for Issuing a Reset Cold Command:
oSoMachine Online Menu: Select the Reset cold command.
oBy an internal call by the application or an HMI command using the PLC_W. q_wPLCControl and PLC_W. q_uiOpenPLCControl system variables of the PLCSystem library.
Effects of the Reset Cold Command:
1.The application stops.
2.Forcing is erased.
3.Diagnostic indications for detected errors are reset.
4.The values of the retain variables are reset to their initialization value.
5.The values of the retain-persistent variables are maintained.
6.All non-located and non-remanent variables are reset to their initialization values.
7.The values of %MW0 to %MW65535 registers are maintained.
8.All fieldbus communications are stopped and then restarted after the reset is complete.
9.All I/O are reset to their initialization values.
For details on variables, refer to Remanent Variables.
Effect: Resets all variables, including the remanent variables, to their initialization values. Erases all user files on the controller. Places the controller into the EMPTY state.
Starting Conditions:
oRUNNING, STOPPED, or HALT states.
oControllerLockout = 0.
Methods for Issuing a Reset Origin Command:
oSoMachine Online Menu: Select the Reset origin command.
Effects of the Reset Origin Command:
1.The application stops.
2.Forcing is erased.
3.All user files (Boot application, data logging) are erased.
4.Diagnostic indications for detected errors are reset.
5.The values of the retain variables are reset.
6.The values of the retain-persistent variables are reset.
7.All non-located and non-remanent variables are reset.
8.All fieldbus communications are stopped.
9.Embedded Expert I/O are reset to their previous user-configured default values.
10. All other I/O are reset to their initialization values.
For details on variables, refer to Remanent Variables.
Effect: Commands a reboot of the controller.
Starting Conditions:
oControllerLockout = 0.
Methods for Issuing the Reboot Command:
oPower cycle.
oREBOOT by USB file system download: The file application download from on a USB memory key will issue 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 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
- Controller state was RUNNING prior to the power cycle.
b.The controller state will be STOPPED if:
- The Reboot was provoked by a Reboot by script, or
- The boot application is different than the application loaded before the reboot, or
- Controller state was STOPPED prior to a power cycle, or
- The previously saved context is invalid.
c.The controller state will be EMPTY if:
- There is no boot application or the boot application is invalid, or
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.
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.
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.
Effect: Loads your application executable into the RAM memory. Optionally, create a Boot application in the Flash memory.
Starting Conditions:
oRUNNING, STOPPED, HALT, and EMPTY states.
oControllerLockout = 0.
Methods for Issuing the Download Application Command:
oSoMachine:
Two options exist for downloading a full application:
oDownload command.
oMultiple Download command.
For important information on the application download commands, refer to Controller State Diagram.
oUSB 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 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.
8.All fieldbus communications are stopped and then any configured fieldbus of the new application is started after the download is complete.
9.Embedded Expert I/O are reset to their previous user-configured default values and then set to the new user-configured default values after the download is complete.
10. All other I/O are reset to their initialization values and then set to the new user-configured default values after the download is complete.
For details on variables, refer to Remanent Variables.
Effects of USB memory key Download Command:
There is no effect until the next reboot. At the next reboot, the effects are the same as a reboot with an invalid context. Refer to Reboot.
