06-24-2014 12:21 AM
I have a crash on a compiled LabView EXE after running this application a while.
This application reading and writing some digital and analog input values continuously with a frequency of around 100 cycles per second.
After 3 to 5 minutes the application crashed without a user input.
Windows do display the application window continuous without any reaction. With the windows task manager i can't kill the application.
After such a crash also the NI MAX do hang.
Do anybody have/had a similar issue and experiance about to analyse it?
description of the environment:
EXE developed under Labview 7
I/O device -> NI-USB 6009
NI DAQmxBase 1.4
Windows XP SP3 on a Atom CPU with around 860 MB RAM
no screensaver
power option for standby / sleep / monitor off / HD off all to 'never'
06-24-2014 12:42 AM
06-24-2014 01:01 AM
'Crash' means, the cyclic program execution is stopped. 'Hang up' is a better description.
Screenshots are not possible because is not a ' 5min NI Express VI development'.
The application running on 40 other PC's around the world without a issue.
How can you analyze something like this?
06-24-2014 01:07 AM
I guess 860MB of RAM might be the issue. Do you have anyother PC RAM info where it is running without a problem? Also are you running any other application (like MS office) along with this application in parallel?
06-24-2014 01:40 AM
In my laboratory the application runnning perfect on a Pentium 4 with 1024MB RAM. But the additional installed software on both PC's is not comparable (different virus scan and other third party software) and out of my control.
06-24-2014 02:37 AM
Did you try to plug the 6008 into another USB port? Do you use a USB Hub?
There have been incidents (esp. with cheap USB hubs) that the USB connection is lost to the instruments. If this happens during access of the instruments, the calling application most likely hangs up or crashes to desktop.
Norbert
06-24-2014 02:43 AM - edited 06-24-2014 02:43 AM
Try it on a different port and ensure it has got nothing to do with bad usb ports. Just a thought i had been hit by this before.
Edit : or whatever norbert says
06-24-2014 02:49 AM
The NI USB-6009 is direct connected, no hub. I will try a nother USB plug.
06-24-2014 04:35 AM
It's happens also with a different USB port.
Anybody has more ideas to analyse this issue?
06-24-2014 04:45 AM
Atleast for testing can you close all the other application and run only your software and check? When you are running the software check the Memory and CPU usage in Task Manager.