Action execution order
You can define multiple actions for one event.
If multiple actions are defined, they will be executed in order from top to bottom each time an event occurs.
About parallel event processing
Each event is processed independently. If multiple events occur at the same time, the actions are executed in parallel without being affected by other events.
For example, if you want to use logger actions to log to two databases at a one-second interval, creating two Periodic events and defining a logger action for each event will result in faster processing than defining two logger actions in a single Periodic event.
Example 1) Define two actions in E01
When an event occurs, "A02" processing is executed after "A01" processing is completed.
Example 2) Define different actions for E01/E02
"E01" |
"E02" |
|
|
Each event occurs independently, and the processing of A01 and the processing of A02 do not affect each other (however, there may be an effect if the processing contents overlap, for example when communicating with the same PLC).
Example 3) Define the same action for E01/E02
"E01" |
"E02" |
|
|
Each event occurs independently, but if an action is already being performed on another event, the subsequent event will wait until the previous event has finished processing.