I have Freezing problem at Telvent HU-AF.

Hi Murat,

Can you confirm what version of MODNET (Modbus tcp/ip) driver you are using?

If you want to guarantee that only one IO Device is communicating with RTU at one time, you can enable "Exclusive" mode on the IO Device (via the IO Device configuration). See extract from help:

This setting controls the way in which redundant I/O device(s) configured with the same network number on different I/O servers activate communications to the physical device they represent.

When Exclusive is set to TRUE, only one I/O device (on one I/O server) will activate communications to the physical device at a time. The best available I/O device (online with the lowest priority) at a particular time will be chosen to actively communicate. When this I/O device is no longer the best available, it will deactivate, which will in turn trigger the best available I/O device on another server to activate.

When Exclusive is set to FALSE (default), the best available I/O device will typically be the only active I/O device; however this may not be enforced. When a different I/O device becomes the best it will activate immediately, without waiting for the other I/O device to deactivate. An I/O device that is not the best may also be forced into actively communicating with the physical device if a particular client can only communicate with the I/O server that I/O device is running on.

Note: The parameter [IOServer]PeerServerConnectTimeOut has been implemented so that on startup of an I/O server, all I/O devices with Exclusive set to TRUE will not be allowed to activate before the I/O server has successfully connected to its peers. This parameter defines how long an I/O server will wait until it ceases trying to connect to peer I/O servers.

Hi Murat,

Can you confirm what version of MODNET (Modbus tcp/ip) driver you are using?

If you want to guarantee that only one IO Device is communicating with RTU at one time, you can enable "Exclusive" mode on the IO Device (via the IO Device configuration). See extract from help:

This setting controls the way in which redundant I/O device(s) configured with the same network number on different I/O servers activate communications to the physical device they represent.

When Exclusive is set to TRUE, only one I/O device (on one I/O server) will activate communications to the physical device at a time. The best available I/O device (online with the lowest priority) at a particular time will be chosen to actively communicate. When this I/O device is no longer the best available, it will deactivate, which will in turn trigger the best available I/O device on another server to activate.

When Exclusive is set to FALSE (default), the best available I/O device will typically be the only active I/O device; however this may not be enforced. When a different I/O device becomes the best it will activate immediately, without waiting for the other I/O device to deactivate. An I/O device that is not the best may also be forced into actively communicating with the physical device if a particular client can only communicate with the I/O server that I/O device is running on.

Note: The parameter [IOServer]PeerServerConnectTimeOut has been implemented so that on startup of an I/O server, all I/O devices with Exclusive set to TRUE will not be allowed to activate before the I/O server has successfully connected to its peers. This parameter defines how long an I/O server will wait until it ceases trying to connect to peer I/O servers.