F 8627X (0650)
380
6.4.4 Connection via port 8896
The MODBUS TCP master accesses the process data image from the F 8627X via port 8896.
In this case, the F 8627X is an active MODBUS TCP slave and relieves the burden on the
F 865x.
On port 8896, the BUSCOM variables are mapped into the F 8627X's process data image. For
this reason, the MODBUS TCP master must access the identity numbers
resulting from the
process data mapping (see Chapter 7).
F 8627X reacts to a MODBUS request via port 8896 as described below:
• If the F 8627X is in mono operation mode (i.e. no HSR connection to a second
F 8627X), then the MODBUS TCP slave on the F 8627X must be active to answer a
MODBUS request with the corresponding MODBUS response.
• If two F 8627X are operating redundantly (i.e. HSR connection to a second
F 8627X), then the MODBUS TCP slaves must be active on one of the two redun-
dant F 8627X to answer a MODBUS request with the corresponding MODBUS
response.
If the MODBUS request cannot be passed to an active MODBUS TCP slave, the F 8627X
sends the error code 0x0B back to the MODBUS master.
The WORD and BOOL variables are located in a common memory
area on the F 8627X.
In case of port 8896, a MODBUS telegram for WORD can access the
address range of the WORD and BOOL variables.
The user must pay attention to correctly interpret the variable types of
reading and writing data.
Note MODBUS function codes 2, 4, 23 and 43 are supported by port 8896.
HK-COM 3 function block must allow the not safety-related data
exchange via MODBUS TCP. The address mapping of the BUSCOM
variables into the F 8627X is described in Chapter 7.
Note If port 502 is not used in the H41q/H51q controller, the polling interval
for port 8896 can be set to t
Poll
≥ CT.
Note HSR communication for a MODBUS TCP slave via port 8896 is only
possible if both F 8627X are operating in redundant mode (DIP-switch
2/2 OFF) and the HPRO-S-DIRECT mode is deactivated (DIP-switch
1/7 OFF).
To Next Page