PCI-6052E error -200329. Diagnostic Utility hangs.

[klgraf]

I have a PCI-6052E multifunction DAQ installed in a PC with Windows 7 Professional operating system.  My device drivers are NI-DAQmx 9.1.1.  The device functioned properly for several months, but has recently begun giving error -200329.  The full text of my error is:

Engine: NIDAQmx.py error -200329: 'An error has occurred while attempting to configure the device for an analog input acquisition.\n\nIf an external master time base is being used, make sure the source is connected and generating an appropriate clock. Otherwise, contact National Instruments Technical Support.\nTask Name

: _unnamedTask<0>\n\nStatus Code: -200329'

I have checked the device in the test panel of Measurement & Automation Explorer, and the edge counting of the inputs are counting as I would expect.  Also, the device passes the Self-Test.

I have downloaded the DAQ Diagnostic Utility 2.1.  When I run this utility, it only makes it a few steps in, and then, after it passes the Device Reset, it hangs.  I have let it sit there for a half hour and it does not seem to be progressing.  The full text of the diagnostic up to the point that it hangs is:

11-06-21 4:30:39 PM
Results saved to:  C:\Users\vlf\Desktop\Diagnostic Results.txt
Selected Device: Dev1
Device Type: PCI-6052E
Serial Number: 1033976
Device Support: (PASS)
NI-DAQmx Version: 9.1 (PASS)
Device Reset: (PASS)

Based on other posts I have read concerning this error code, it seems that something may be broken on my NiDAQ card.  I chose to make a new post because most the other posts I found were several years old, and none of them also had this problem of a hanging Diagnostic Utility.

I should also mention that the computer with the PCI-6052E installed is a remote computer.  It is difficult for me to have any physical changes made to the system.  At the moment, I have not been able to unplug the data cable attached to the card.  I do not know if this affects the Diagnostic Utility.

[Eric_L]

Hello,

I assume that you are, but I just want to confirm, are you using the onboard clock for you AI task?

Does the AI Test Panel function properly? If it does not, the hardware may be damaged.

As a troubleshooting step, can you upgrade to DAQmx 9.3?

If the above items do not help resolve the problem, there is possible hardware damage. The only way to confirm this would be to inspect the hardware.

Eric

[klgraf]

Thank you for the reply.  We are actually using an external clock signal.  To check that signal, I was using the Counter I/O test panel in edge counting mode.  For our setup, we expect a 1 Hz signal on PFI0, and a 100 kHz signal on PFI1.  These both count properly.

I had not yet run the AI test panel, however.  I just tried running that test now, and it failed, giving the same error code 200329.  I guess I will still download DAQmx 9.3 for good measure, but it looks like I have a hardware problem and should arrange to replace the card.

[klgraf]

Since I am debugging this setup remotely, the simplest way for me to fix a potentially defective card would be to send a new card to that site and have someone there just swap it in.  Your answer was already pretty clear, but before I buy and ship a new card, can you confirm for me that seeing this error -200329 in the AI test panel is strongly indicative of a hardware problem within the PCI-6052E card and that replacing that card will likely fix the problem? 

[Eric_L · Accepted solution]

Hello,

It is likely that the clock trace leading to the ADC has been damaged. As you have mentioned, the quickest troubleshooting method is to swap in a new card.

Eric

[klgraf]

Thank you.  I will try that.