This section provides a detailed description of the controller states.
|
|
|
UNINTENDED EQUIPMENT OPERATION |
|
oNever assume that your controller is in a certain controller state before commanding a change of state, configuring your controller options, uploading a program, or modifying the physical configuration of the controller and its connected equipment. oConsider the effect of any of these operations on all connected equipment before performing any of these operations. oPositively confirm the controller state by viewing its LEDs before acting on the controller. oConfirm the condition of the Run/Stop input (if so equipped and configured) and/or the Run/Stop switch (if so equipped) before acting on the controller. oVerify the presence of output forcing before acting on the controller. oReview the controller status information via EcoStruxure Machine Expert before acting on the controller.(1) |
|
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
(1) The controller states can be read in the PLC_R.i_wStatus system variable of the M262 System library.
The following tables describe the controller states:
|
Controller State |
Description |
LED Status |
|---|---|---|
|
BOOTING |
The controller executes the boot firmware and its own internal self-tests. It then verifies the checksum of the firmware and user applications. |
Each LED, from the PWR LED to the NS or S3 LED, depending on the controller reference, flashes before turning solid green. The boot sequence is complete when all the LEDs are solid green. The LEDs then flash together briefly to indicate that the controller is operational. |
|
INVALID_OS |
There is not a valid firmware file present in the flash memory or the firmware is not from Schneider Electric. The controller does not execute the application. Refer to the Updating Firmware section to restore a correct state. |
FSP LED stays solid red after the boot sequence. |
|
Controller State |
Description |
LED |
||
|---|---|---|---|---|
|
RUN (Green) |
ERR (Red) |
I/O (Red) |
||
|
EMPTY |
The controller has no application. |
OFF |
Single flash |
OFF |
|
EMPTY after a system error detected |
This state is the same as the normal EMPTY state. But the application is present, and is intentionally not loaded. A next reboot (power cycle), or a new application download, restores correct state. |
OFF |
Fast flash |
OFF |
|
RUNNING |
The controller is executing a valid application. |
ON |
OFF |
OFF |
|
RUNNING with breakpoint |
This state is same as the RUNNING state with the following exceptions: oThe task-processing portion of the program does not resume until the breakpoint is cleared. oThe LED indications are different. oFor more information on breakpoint management, refer to EcoStruxure Machine Expert Programming Guide. |
Single flash |
OFF |
OFF |
|
RUNNING with external error detected |
Configuration, TM3, SD card, or other I/O error detected. When I/O LED is ON, the details about the detected error can be found in PLC_R.i_lwSystemFault_1 and PLC_R.i_lwSystemFault_2. Any of the detected error conditions reported by these variables cause the I/O LED to be ON. |
ON |
OFF |
ON |
|
STOPPED |
The controller has a valid application that is stopped. See details of the STOPPED state for an explanation of the behavior of outputs and field buses in this state. |
Regular flash |
OFF |
OFF |
|
STOPPED with external error detected |
Configuration, TM3, SD card, or other I/O error detected. |
Regular flash |
OFF |
ON |
|
HALT |
The controller stops executing the application because it has detected an application error |
Regular flash |
ON |
– |
|
Boot Application not saved |
The controller has an application in memory that differs from the application in Flash memory. At next power cycle, the application is changed by the one from Flash memory. |
ON or regular flash |
Single flash |
OFF |
This figure shows the difference between the fast flash, the regular flash and single flash:
The following statements are true for the STOPPED state:
oThe input configured as the Run/Stop input remains operational.
oThe output configured as the Alarm output remains operational and goes to a value of 0.
oEthernet, Serial (Modbus, ASCII, and so on), 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.
oOutputs initially assume their configured default 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. For more information on the behavior of the TM3 outputs, refer to Modicon TM3 Expansion Modules Configuration - Programming Guide.
Task and I/O Behavior When Update IO While In Stop Is Selected
When the Update IO while in stop setting is selected:
oThe Read Inputs operation continues normally. The physical inputs are read and then written to the %I input memory variables.
oThe Task Processing operation is not executed.
oThe Write Outputs operation continues. The %Q output memory variables are updated to reflect either the Keep current values configuration or the Set all outputs to default configuration, adjusted for any output forcing, and then written to the physical outputs.
CANopen Behavior When Update IO While In Stop Is Selected
The following is true for the CANopen buses when the Update IO while in stop setting is selected:
oThe CANopen bus remains fully operational. Devices on the CANopen bus continue to perceive the presence of a functional CANopen Master.
oTPDO and RPDO continue to be exchanged.
oThe optional SDO, if configured, continue to be exchanged.
oThe Heartbeat and Node Guarding functions, if configured, continue to operate.
oIf the Behaviour for outputs in Stop field is set to Keep current values, the TPDOs continue to be issued with the last actual values.
oIf the Behaviour for outputs in Stop field is Set all outputs to default the last actual values are updated to the default values and subsequent TPDOs are issued with these default values.
Task and I/O Behavior When Update IO While In Stop Is Not Selected
When the Update IO while in stop setting is not selected, the controller sets the I/O to either the Keep current values or Set all outputs to default condition (as adjusted for output forcing if used). After this, the following becomes true:
oThe Read Inputs operation ceases. The %I input memory variables are frozen at their last values.
oThe Task Processing operation is not executed.
oThe Write Outputs operation ceases. The %Q output memory variables can be updated via the Ethernet, Serial, and USB connections. However, the physical outputs are unaffected and retain the state specified by the configuration options.
CANopen Behavior When Update IO While In Stop Is Not Selected
The following is true for the CANopen buses when the Update IO while in stop setting is not selected:
oThe CANopen Master ceases communications. Devices on the CANopen bus assume their configured fallback states.
oTPDO and RPDO exchanges cease.
oOptional SDO, if configured, exchanges cease.
oThe Heartbeat and Node Guarding functions, if configured, stop.
oThe current or default values, as appropriate, are written to the TPDOs and sent once before stopping the CANopen Master.
