Protocol Manager Operating Modes
To manage the operating modes of the devices, protocol manager is composed by Modbus TCP IOScanner.
The protocol manager state defines the behavior of the different devices in the device network. For each state, monitoring information (health bit, communication states, and so on) is specific.
The scanners states depend on the controller state:
|
Controller state |
Modbus TCP IOScanner state |
|---|---|
|
EMPTY |
IDLE |
|
CONFIGURED |
STOPPED |
|
STOPPED |
STOPPED |
|
HALT |
STOPPED |
|
RUNNING |
OPERATIONAL |
|
RUNNING with breakpoint |
OPERATIONAL with a specific behavior |
TCP/IP connections are closed.
Device states are managed according to their individual mode of operation.
The Modbus TCP IOScanner is not created (IDLE state).
Therefore, health bits and I/O images are not available.
TCP/IP connections are closed.
Controller enters in CONFIGURED state after:
oan application load.
oa reset (cold/warm) command sent by EcoStruxure Machine Expert.
The Modbus TCP IOScanner is in STOPPED state, all channels with the Modbus TCP slave devices are closed in half-sided mode.
The Modbus TCP IOScanner is in STOPPED state. All channels with the Modbus TCP slave devices are closed in half-sided mode.
Slave devices are managed according to their individual mode of operation.
This table presents the EcoStruxure Machine Expert variables for Modbus TCP IOScanner:
|
Variable |
Value |
Comments |
|---|---|---|
|
Health bit value |
0 |
- |
|
Input image |
0 or the last read value |
Input values depend on the Error Handling parameter. Input values are those when the controller entered in the STOPPED state and therefore may not reflect the actual state of the input thereafter. |
|
Output image |
0 or the last written value |
Output values depend on the Behavior for outputs in Stop parameter. Output values may not reflect the actual state of the output thereafter. |
|
|
|
OUTPUT VALUES IN MEMORY MAY BE DIFFERENT THAN THEIR PHYSICAL STATE |
|
Do not rely on the memory values for the state of the physical outputs when the controller is not in the RUNNING state. |
|
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
For Modbus TCP IOScanner, same behavior as the controller STOPPED state.
|
|
|
OUTPUT VALUES IN MEMORY MAY BE DIFFERENT THAN THEIR PHYSICAL STATE |
|
Do not rely on the memory values for the state of the physical outputs when the controller is not in the RUNNING state. |
|
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
TCP/IP connections are open.
Slave devices are managed by the controller.
This table presents the EcoStruxure Machine Expert variables:
|
Variable |
Value |
Comments |
|---|---|---|
|
Health bit value |
0...1 |
0: No reply from the device before the timeout expired. 1: Requests are sent and replied before the timeout expires. |
|
Input image |
Last read value |
Values are refreshed synchronously with the task which drives the scanners. |
|
Output image |
Last written value |
Values are managed by the application. |
Controller RUNNING with Breakpoint State
TCP/IP connections are open.
Slave devices are managed by the controller.
|
|
|
OUTPUT VALUES IN MEMORY MAY BE DIFFERENT THAN THEIR PHYSICAL STATE |
|
Do not rely on the memory values for the state of the physical outputs when the controller is not in the RUNNING state. |
|
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
