Execution of Modbus Tasks is managed by the ModbusWorker. It…​ - executes Write-Tasks as early as possible (directly after the EXECUTE_WRITE event) - executes Read-Tasks as late as possible to have values available exactly when they are needed (i.e. just before the BEFORE_PROCESS_IMAGE event). To achieve this, the ModbusWorker evaluates all execution times and 'learns' an ideal delay time, that is applied on every Cycle - the 'CycleDelay' - handles defective ModbusComponents (i.e. ones where tasks have repeatedly failed) and delays reading from/writing to those components in order to avoid having defective components block the entire communication bus. Maximum delay is 5 minutes for read from defective components. ModbusComponents can trigger a retry from a defective Component by calling the retryModbusCommunication() method.

Read-Tasks can have two different priorities, that are defined in the ModbusProtocol definition: - HIGH: the task is executed once every Cycle - LOW: only one task of all defined LOW priority tasks of all components registered on the same bridge is executed per Cycle Write-Tasks always have HIGH priority, i.e. a set-point is always executed as-soon-as-possible - as long as the Component is not marked as defective

Each Modbus Bridge provides Channels for more detailed information: - CycleTimeIsTooShort: the configured global Cycle-Time is too short to execute all planned tasks in one Cycle - CycleDelay: see 'CycleDelay' in the 'ModbusWorker' description above

Often it is useful to print detailed logging information on the Console for debugging purposes. Logging can be enabled on Task level in the definition of the ModbusProtocol by adding .debug() or globally per Modbus Bridge via the LogVerbosity configuration parameter:

• NONE: Show no logs

• DEBUG_LOG: Shows basic logging information via the Controller.Debug.Log

• READS_AND_WRITES: Show logs for all read and write requests

• READS_AND_WRITES_VERBOSE: Show logs for all read and write requests, including actual hex or binary values of request and response

• READS_AND_WRITES_DURATION: Show logs for all read and write requests, including actual duration time per request

• READS_AND_WRITES_DURATION_TRACE_EVENTS: Show logs for all read and write requests, including actual duration time per request & trace the internal Event-based State-Machine

The log level via configuration parameter may be changed at any time during runtime without side-effects on the communication.