Technical information

Controller States and Behaviors
EIO0000000638 04/2012 53
Details of the STOPPED State
The following statements are always true for the STOPPED state:
z Ethernet, Serial (Modbus, ASCII, etc.), and USB communication services remain
operational and commands written by these services can continue to affect the
application, the controller state, and the memory variables.
z All outputs initially assume their configured state (Keep current values or Set all
outputs to default) or the state dictated by output forcing if used. The
subsequent state of the outputs depends on the value of the Update IO while in
stop setting and on commands received from remote devices.
NOTE: There are no local or remote I/O on XBT GT and XBT GK HMI Controllers.
%I input memory variables and %Q output memory variables are attached to
CANopen data if configured.
Task and I/O Behavior When Update IO While In Stop Is Selected
When the Update IO while in stop setting is selected:
z The Read Inputs operation continues normally. The physical inputs are read
and then written to the %I input memory variable.
z The Task Processing operation is not executed.
RUNNING with
Breakpoint
This state is the same as the RUNNING state with the following exceptions:
z The task-processing portion of the program does not resume until the
breakpoint is cleared.
See CoDeSys online help in SoMachine for details on breakpoints
management.
RUNNING with
detection of an
External Error
This state is the same as the normal RUNNING state.
STOPPED The controller has a valid application that is stopped. See Details of the
STOPPED State (see page 53) for an explanation of the behavior of outputs
and field buses in this state.
STOPPED
with detection
of an External
Error
This state is the same as the normal STOPPED state.
HALT The controller stops executing the application because it has detected an
Application or a System Error.
This description is the same as for the STOPPED state with the following
exceptions:
z The task responsible for the Application Error always behaves as if the
Update IO while in stop option was not selected. All other tasks follow
the actual setting.
Controller
State
Description