Driver dialog option |
MODRTU32 -> Configuration -> Settings in the driver dialog -> Driver dialog option |
Show all Hide all |
Connection |
Decide which type of connection is required. Either serial via a COM interface or TCP/IP For serial mode, you can choose between Modbus RTU and Modbus ASCII. If you check the box ASCII, the driver will communicate via the Modbus ASCII protocol. If you uncheck the box, the driver will use Modbus RTU. If you select a TCP/IP connection, you have to enter a configuration file. This file stores the TCP/IP settings. |
Sequence for FLOAT objects |
This option sets the Floatordering either to Standard Modbus or to 'HB Controler' Float Ordering. |
Sequence for DWORD objects |
This option defines the DWORD Ordering of the ModRTU driver. Either according to Intel format or Motorola format. |
General
RTS Handshake |
Some PLCs need the RTS handshake for a correct communication. |
Offset 1 |
The "Offset 1" affects the addressing of all variables. It subtracts 1 from all addresses. (Coils, Register) |
Max block size |
Maximum block size of a data telegram. !Attention (zenon < 5.50 SP6)! Block size must be < 64. |
TCP configuration file |
Here the name of the TCP configuration file has to be entered |
Send delay |
Delay for "send" requests (in milliseconds); affects the whole driver. |
Skip non-existing data points |
The driver reads data in a block. If there is no data between two address areas close to each other, the driver will still try to access these non-existing areas. This option will avoid that. |
Reconnect timeout |
Time in milliseconds to wait after a communication error before trying to reestablish the connection. |
Communication timeout |
Time in milliseconds to wait for a response from the Slave. If there is no response within this time, a communication error will be displayed. |