semaphore TBOX LT2-530 Series, Руководство пользователя, Страница: 51 / 197

Version : 1.09 51
7.6.5. ModBus Transactions
Reset the device Trigger only if success When communicating as ‘Master’ using ‘ModBus
Transactions’, a Trigger is switching communication to the remote device (see chapter
15. ModBus Transactions).
This Trigger activates the communication according to a ‘State’ or ‘Edge’. Working with
‘Edge’, the RTU restores automatically the Tag after the transaction(s).
-
With this option active: the Trigger is restored only when communication has been
done successfully.
-
Without this option: the Trigger is restored when all ModBus Transactions
associated to the device have been executed, with or without error.
Remote device inactivity delay: this option allows defining a quarantine delay when a
Remote device is in communication error.
Keep socket open: working with OS >= 1.35.374
When carrying on Modbus Transactions in Modbus/TCP,
TB
OX
LT2
will use one TCP
context per remote device. Checkink this option, the socket for each device will be kept
opened, preventing overhead communication.
Working with OS < 1.35.374.
Only ONE is available socket available. Therefore, this socket is opened/closed at each
execution of a list of Modbus Transactions. When there is only ONE remote device, this
option allows keeping the socket opened and therefore improving the communication.
7.6.6. Ports
Each TCP/IP service has its own
unique TCP port. It provides a
logical location for the delivery of
TCP data. TCP Port number
complies with a standard defined
by the IANA to be sure everyone
using a TCP service uses the same
TCP ports according to protocols
used.
When working with
TB
OX
LT2
, in
some cases, you might want to
change this port number.