Failure to recognise data acquisition card

[JLM]

I am trying to use LabVIEW with a Gage CompuScope 1450 data acquisition
card. (I was previously using LabVIEW 6, and have recently upgraded to
LabVIEW 7.1, and I am having exactly the same problem with both versions of
the program.) When I try to look at the data using an oscilloscope program
within LabVIEW, the program works properly for a few seconds, and then
crashes, with the following error message: "Unexpected problem detected in
the program "LabVIEW.exe". See the report file "C:\Program Files\National
Instruments\LabVIEW 7.1\CrashReport.txt" for more info."

When I look at the file, the first line of it is "Unhandled exception
0xC0000094 (INT_DIVIDE_BY_ZERO) caught at address 0x65A0DBD2 in the thread
200." When I try to restart the program, it tells me that the data
acquisition card is not found or not configured properly. But when I quite
LabVIEW and restart it, the program works again, but again crashes after a
few seconds. Can you help?

[Johnner]

JLM,

It seems like there are two main possibilities:
1. The driver software you installed for the 1450 card is incorrect or corrupted
2. The LabVIEW code that calls the driver (presumably via LabVIEW's Call Library node) is doing so incorrectly

I am not familiar with Gage hardware, and, given the lack of responses to your question so far, I would guess that none of the other regulars here have experience with it either. It may be that your best course of action is to contact Gage for support. At the very least, perhaps you can verify whether you are using the latest version of whatever LabVIEW VIs they provide to interface with their driver.

If you are stuck debugging this yourself, then you should start with more basic tests: find the simplest possible function that is exposed via a LabVIEW VI, and run that. Does it crash LabVIEW? You might be able to dig into the VI and isolate one or more DLL calls (Call Library node) that are causing the problem. It might be as simple as identifying one node that is misconfigured, perhaps using the wrong calling convention setting, or perhaps feeding the wrong values to the underlying DLL function. It's incredibly easy to crash LabVIEW if you use a DLL incorrectly.

Hope this helps,
John