Hi
I have a Lookout 6.5 system that has been running properly for well over a year. Normally we usually experience a computer lockup (Usually Windows is Frozen) and have to reboot the computer 2 or 3 times a year. But recently we are having a problem where all of the modbus secondary units are giving us an error the says cannot communicate with the modbus secondary ETC. We get this error message for all of our RTU's except the local MODBUS controller which is a Zetron 1700. When this happens we get the red X's on all of the I/O points in our process and everything in the field stays at its current state. This has happened at least 6 times in the last month!
To try and narrow down the problem I have had my customer power cycle the MODBUS controller and the radio and that does not fix the problem. When the MODBUS controller is power cycled we can see the controller is getting responses from all of the external RTU's but Lookout still does not see the data. I have also had them shut down Lookout and then restart Lookout and this also does not fix the problem. The only fix seems to be to restart the computer and then everything comes back up running properly. Because we can see what time the problem occurred I can then go into the Windows Event Viewer and look for any problems around the time when the problem started. But there is absolutely no events that would indicate a problem in either the System or Applications Event Logs?
The system is running Lookout 6.5 build 49153 on Windows 7 64 Bit. The serial connection is using a USB to RS-232 converter. Any help you can give me in troubleshooting this issue would be greatly appreciated. I need to get this resolved ASAP because the process is running a city's fresh water system and so far we have overflowed the tank several times and one time we got dangerously low because of this issue.
Thank You
Rob
