4. Configuration
107
Write Data Range: this field shows the MODBUS write data range configured for each request. The
initial address of writing plus the size of the write data will result in the range of write data for each
request.
Diagnostic Variable: the configured MODBUS request diagnostics, either by symbolic mapping or
by direct representation, are stored in variables of type T_DIAG_MODBUS_ETH_CLIENT_1 and
the mapping by direct representation are in 4-byte and 2-word, which is described in Table 4-73 (n is
the value configured in the field Diagnostics Initial Address in %Q).
Direct
Representation
Variable
Diagnostics of
T_DIAG_MODBUS_ETH_MAPPING_1.*
Type Variable
Communication Status Bits:
Communication idle (waiting to
be executed)
Communication deferred,
because the maximum number
of concurrent requests was
reached. Deferred
communications will be carried
out in the same sequence in
which they were ordered to
avoid indeterminacy. The time
spent in this State is not counted
for the purposes of time-out. The
bCommIdle and
bCommExecuting bits are false
when the bCommPostponed bit
is true.
Communication disabled. The
bCommIdle bit is restarted in this
condition.
Communication terminated
previously was held
successfully.
Communication terminated
previously had an error. Check
error code.
Previously terminated
communication was interrupted
due to connection failure.
Last error code (enabled when bCommError = true):
Informs the possible cause of
the last error in the MODBUS
mapping. Consult Table 4-74 for
further details.
Last exception code received by master:
NO_EXCEPTION (0)
FUNCTION_NOT_SUPPORTED
(1)
MAPPING_NOT_FOUND (2)
ILLEGAL_VALUE (3)
ACCESS_DENIED (128) *
MAPPING_DISABLED (129) *
IGNORE_FRAME (255) *
Communication statistics:
Communications counter
terminated, with or without
errors. The user can test when
communication has finished
testing the variation of this
counter. When the value 65535