How to debug: "exception occurred within the external code called by a Call Library Node"

[whatsthis 163]

I recieve this error after 8-9 hours of running a vi. Using LV 7.0 with 4 nidaq6052e's. Labview returns the message: "VI 'my vi' was stopped at node 0x22CC of subvi 'AI SingleScan (single point waveform).vi'". The best part is I'm not using this vi and it never gets loaded into memory. Using only two 6052e's it takes 2 days two throw the exception, 3 can go about 15 hours, I haven't seen one card crash yet, but it ran for over 2.5 days.

I also used the same code with older nidaq drivers-6.9.2, and the computer reboots instead of throwing the error.

The code itself has a lot of AI Config, Start, Reads, Clears, that all get called for different channels with practically every iteration of a while loop. Also has the same calls for AO but AI seems to be the problem.

Is there any known bug for the drivers? I want to point the finger at the drivers (of course the code can still be the problem) because they seem to corrupt themselves faster or slower depending on how many cards are in the computer.

[Salvador_Santolucito]

Hi whatsthis,

Although I do not have a solution to the error, I would like to make a suggestion. I would HIGHLY suggest moving your application over to DAQmx. I see that you have LabVIEW 7.0 and PCI-6052E DAQ cards. Both of these support DAQmx. Traditional NI-DAQ is the older driver that will eventually be phased out. All of our newest boards support MX and in the future traditional DAQ will not be supported in new boards.

DAQmx has many signifigant advantages over Traditional NI-DAQ:

1) It is the new driver that will be used in the future, boards that support traditional DAQ will eventually be phased out
2) The DAQmx programming is much simplier than traditional DAQ
3) All new LabVIEW programming examples are going to be written in DAQmx
4) The DAQmx driver will be continually updated and revised to make it better and fix bugs. The traditional DAQ driver will most likely not change


-Sal