02-08-2010 02:04 PM
I recently built a new computer for data acquisition. I didn't have any issues taking a data acquisition program for a high speed digitizer written in LabWindows 8.5 and running it successfully with LabWindows 9.0 on the new machine. The only issue I encountered was naming the high speed digitizer card in MAX the appropriate resource name expected by the data acquisition program. Everything ran fine for 4 days. Today I attempt to run the same program and cannot get it to run. Debugging the code shows that the device fails to initialize when niScope_init() is called.
In MAX the digitizer card passes a self-test, and I can call up test panels and see a signal input. I checked the device name to ensure that it matches the resource named expected in the program. I also reset the device in MAX and then tried to run the acquisition program. None of these attempts has succeeded.
I can't really find anything that has changed between the last time I ran the program and today. Has anybody run up against this issue in the past, and is there a solution or suggested further troubleshooting?
Solved! Go to Solution.
02-08-2010 03:00 PM
02-09-2010 12:05 AM
I used the function niScope_error_message to find out.
Did you try running the NI-Spy while operating the test panels?
NI-Spy can be configured to capture NI-SCOPE library calls, from which you can see how MAX is initialising the card successfully.
Hope this helps,
02-11-2010 08:15 AM
This issue was solved by re-installing the drivers for our high speed digitizer. I still have no idea why after four days something happened to the original driver installation.