11-27-2012 10:00 AM
I am using a NI USB-6009 OEM with the NI-DAQmx C Library. Recently I am running into a problem where exceptions are happening in NI functions. i.e. DAQmxReadAnalogF64. Normally when an problem occurs in a NI function, it returns an error, however we are having a few boards causing exceptions randomly. Any ideas on how to found out what is causing the problem? (We are using the 8.7 drivers for Windows XP Embedded.)
I have also noticed on Windows 7 64-bit using the latest drivers, if I am using a NI USB-6009 and I unplug the USB cable, the computer Blue Screens pointing to an NI dll.
Is it safe to assume an exception happening in DAQmxReadAnalogF64 is due to a hardware issue? Any suggestions?
I have attached an image of the exception.
Thanks
11-28-2012 06:38 PM
Hi c++Programmer,
At this point, I don't think there's enough information to safely say it is definitively a hardware issue. What happens when the exception is thrown? Could you try catching the exception for more information and effectively handling it?
Cheers,
12-11-2012 09:03 AM
I have been able to reproduce the problem on my laptop running Windows XP or Windows 7 (NI drivers 9.2.3) but instead of an exception, Windows Blue Screens. When our program is running, if I unplug the USB cable, Windows will blue screen pointing to nimxdfk.dll.
Attached is a screen shoot of the STOP (Blue screen)
12-12-2012 05:19 PM
Hello c++Programmer,
Hvae you been able to capture any more information related to the exception/crash? You could try updating your XP or 7 machine to the latest version of NI-DAQmx.
Cheers,