We have a Lookout 6.0.2 (with updates) application on a new Win XP Pro computer containing all the latest MS updates. We are using Rockwell Software RSLinx as the opc server. We have one Lookout opc client object, which communicates to the RSLinx opc server. We have periodic crashes (blue screen) crashes with this system, usually when computer is unattended and not being used for development, and after a clean boot. We have recently re-built the SCADA computer on another machine, which had the same crash problem. We re-built on new machine after NI advise to do so, to see whether problem was hardware related nor not. So I assume that now we have isolated the problem to software. We also get periodic crashes of lookout.exe (without blue screen) when making changes to opc links in the application. For example, as a test we have seen a crash of lookout.exe when changing a link to a variable that does not exist in the PLC. We do see an opc error alarm in the Lookout alarm messages that shows us that a certain tag is not available in the PLC. We have had several of these "bad opc links" exist throughout the development process, but saw very few crashes until further on in the development process. We have tried changing to another SCADA computer, and have tried re-compiling from the lks. None of these efforts has helped. We still have the opc error alarm in the Lookout alarm messages that shows us that a certain tag is not available in the PLC, so we know that we still have "bad opc links" in the system. Does anyone know, does a bad opc link cause Lookout crash? Is it good practice to ensure that we have no bad opc links, and no Lookout opc alarm messages? Is there any other steps that we can take to test, diagnose, or fix this problem other than eliminating all "bad opc links"? Thanks very much for the support.
