Driver failover

InduSoft has several settings over the driver configuration to really be able to address all kinds of awkwardness when the subject is communication with external devices(noisy networks, bad device communication, intermittent connection, etc...). You can increase timeouts, add retries, and you can also create your own algorithm to address a driver failover.

This sample application will show you how to restart the driver module after the ReadStatus from the Main Driver Sheet starts to show that the communication is not good (different from 0).

The application is composed by a Scheduler that will count up the timeout whenever the readstatus tag is different from 0.

If the communicaiton is good (readstatus=0) than the timeout will be set to 0.

After the readstatus is different from 0 for 7 seconds (bad communication) the application starts the restart procedure.

The restart will Stop the driver module (EndTask("Driver") and after 2 seconds the driver is stopped it will re-start it, and it will also restart all the timeout counters.

If the communication does not come back, the application will restart it again after 7 seconds.