You can turn the FP-I4C unit into a Modbus/TCP server that listens to the specified port.
All Modbus/TCP requests from clients will be translated into the protocol that has been set for the specified interface on the COM Interface page (MEWTOCOL, MEWTOCOL7, or Modbus).
When the internal interface INTERN is specified, TCP packets are not redirected to a physical device and the Modbus/TCP gateway setting has no effect. The interface INTERN refers to the addressable internal memory areas of the FP-I4C unit which are accessible via Modbus/TCP or the script function.
If Modbus/TCP gateway is enabled, you cannot enable Allow FPWIN Pro.
If Transparent is set for the COM interface, this setting is ignored.
If no restrictions are specified (default setting), no address can be read or written.
Modbus/TCP translation rules:
The Modbus/TCP gateway supports the following function codes:
Holding registers can be mapped to all types except WX.
Examples:
Map 1000 holding registers starting from the first address to DT0 to DT999.
Select DT for Memory area, enter an address range from 0 to 999, set the access type, select the data type Holding register, and enter 0 for Modbus/TCP offset.
Map the next 1000 holding registers to LD0 to LD999.
Select LD for Memory area, enter an address range from 0 to 999, set the access type, select the data type Holding register, and enter 1000 for Modbus/TCP offset.
Map the first 1500 input registers to FL1000 to FL5999 (FP2SH only).
Select FL for Memory area, enter an address range from 1000 to 5999, set the access type, select the data type Input register, and enter 0 for Modbus/TCP offset.
Coils can only be mapped to bit address areas WR, WL, WY.
Example:
Map the first 160 coils (10 words) to WR0 to WR9.
Select WR for Memory area, enter an address range from 0 to 9, set the access type, select the data type Coil, and enter 0 for Modbus/TCP offset.