Lookout 5.0 Crashes with XP and XP Pro

[haroldc_gtmc@sbcglobal.net]

Lookout 5.0 crashes with various actions when in the modify application mode and the application is left running. It only happens when my local "Modbus RTU" is connected via the comm port. If I disconnect the equipment and reset the application is does not crash. If I disconnect the equipment and don't reset the application it will continue to crash. I have duplicated the problem on 2 diffrent computers, one with XP home and one with XP profesional.

[Chad E]

First, make sure that you have the latest Lookout 5.0 fixes installed.

If that doesn't solve the issue, then what error do you see? Can you reproduce the error with a new process with only the minimum objects needed to reproduce it? If you can, attach the lks file of this small process to your response.

[jzizzi]

I have noticed the same situation when I use Windows 2000. It will only occure when the memory available drops below 30%. This would suggest a leak in the program. I got around this by increasing the V Memory to a large amount and making sure to stay out of the edit mode as much as possible.

[MACM_Alan]

I'm having the same problem with win2k-sp4. Using NI pci 485-2 com board with modbus 4 wire. Had to go back to Ver 4.5.1 b19 to get system to run. NI has some serious problems with this but appears to be ignoring them to support NI Week and new releases of LAbView instead. I've been looking for assistance and answers for almost a month.

[tommy_scharmann]

I experienced frequent crashes in Win 2K SP3 with Lookout 5.0 (I had all patches installed for Lookout). I found that my Lookout driver object (specifically a TIWAY object) was polling analog values with no deviation entered (I forgot to put a few in). When I entered deviation values the crashes stopped. I reproduced this problem.

So my recommendation is to check your driver object's database. If you are polling any analog addresses BE SURE you have a deviation entered.

Hope this helps.

Regards,
Tommy Scharmann