ABB CP405 1SAP500405R0001 Operation panel
Cold start
stopped The command to cold start the resource had been initiated by the person
responsible for commissioning, or from the system function „Force cold
start”. Indicates self-test of the FieldController was OK, however, the
RUN/STOP switch on the FieldController was in the STOP position or the
resource was stopped by the person responsible for commissioning before
achieving running state.
The cold start task, Name.ColdSt (where Name = resource name)
is executed only when the resource is started (STOP to RUN).
When cold starting, all the resource data is initialized. The operat ing system is not affected and the output module channels assume
their safety values.
Warm start
stopped The command to warm start the resource was initiated by the person re sponsible for commissioning or a power failure (power-fail signal from the
power supply unit), the RUN/STOP switch on the FieldController was set to
STOP or the resource was stopped before achieving running state by the
person responsible for commissioning.
The warm start task, Name.WarmSt (where Name = resource
name) is executed only when the resource is started (STOP to
RUN). When warm starting, all data and variable values of the re source are unaffected and the output module channels assume
their safety values.
Starting Resource in transition from stopped to running
This state is only displayed if task processing takes a relatively
long time.
Running Resource started and RUN/STOP switch in RUN position
Running partially Not all resource program objects are processing, e.g. task in stop or pro gram list OFF
Version error,
running There are user program version disparities between the active station and
the assigned resource. Such disparities are displayed independently of the
run state of the resource, and are therefore also displayed when stopped.
[del2] Resource objects have been deleted, in this case, two objects
Wrong
station number The station number in the FieldController does not match the station num ber in the hardware structure (network).
Incompatible
EPROM version The EPROM version of the CPU module or FieldController does not match
the software version of the engineering software.

6.4.3 Task state displays
Ready Task already loaded and manual start possible.
If no autostart has been configured for a task, it reverts to the
ready state after each cold start and has to be restarted.
Non-existent Task is loaded but cannot be started. A software version error exists.
Not loaded A change to a task, or to a program within the task, which has a side effect
on the task, has not yet been loaded.
Unrunnable During execution of the task either an unrecoverable error occurred or a recoverable error occurred while automatic error correction was switched off.
Automatic error correction for a task is switched on in the default
setting. If automatic error correction is switched off, the task
changes to the unrunnable state on any error, even if the error is
recoverable. The error appears in text form in the task header and
the object number of the faulty project object is also displayed.
Exceptions are tasks which, although loadable, have no
lower-level user program. Such a task is thus unable to initiate
execution of a program, and if started nevertheless, it goes into the
unrunnable state.
Running After manual start of the task or when the task has been set up with
Autostart.
When a higher-level resource is stopped and re-started, the
lower-level task reverts to its old state. A task with Autostart
changes automatically to running. A task’s state may also be
changed when the resource is stopped, and the changed state will
be reassumed when the resource is restarted.
Stopped After execution of Stop task, Stop station (HW) or Stop higher-level resource (SW).
If a stopped task is reset to the ready state (not visible) with Reset,
no change to its state of stopped is displayed to the user. When
Stop is changed to Start, the RUN task is executed.