What is DAQmxErrorPrimingCfgFIFO (-200329)?

[WM_John_Weeks]

A customer has reported DAQmxErrorPrimingCfgFIFO (-200329) while trying a simple scanning operation on a PCI-6052E device. I am guessing this is a sign of a hardware failure. Is that accurate?

thanks!

[David L.]

Hi John,

It is possible that the card is broken, but I would like to ask for more information before you send it in for repair. When and how are you getting this error? Are you using test panels in Measurement and Automation Explorer (MAX) or a LabVIEW VI? If you are in MAX, please detail steps to recreate the issue including sample rates, voltages, etc. and I will try to do so. If you are in LabVIEW, please attach a small portion of code which exhibits the problem for me to look at. I would also like to ask for a screenshot of the error.

Did the card work well before or is this a new card? Does the error occur when the card is in different PCI slots? Different computers? Happen on other cards as well? This will help us narrow down if it may be a hardware issue or possibly corrupt driver.  I would also like to ask that you run, and post, the results of using the DAQ Diagnostic Utility. Click here for version 2.0, which supports DAQmx 8.3 and later. You can find which version of DAQmx you have by opening MAX >> My System >> Software >> NI-DAQmx, look in the window on the right-side for the version number.

Regards,

[WM_John_Weeks]

Thanks, David L.

The card belongs to a customer so I don't know the answers to all your questions. The card fails under MAX as well. The card is running under C++ code I wrote for a plug-in for my company's graphing application, so I don't have Labview code.

I will pass along your comments and maybe we can get you some answers.

[Gene Civillico]

hello David -

I am the customer in question.  Thanks for your response.  Here is some more info:

I am taking over this machine from a previous user who was acquiring directly into Matlab using traditional NiDAQ.  This was working fine as of about a month ago.  I am trying to switch to acquiring into Igor Pro, which is made by Wavemetrics, where John works, and which encourages the use of NiDAQ MX.

So first I installed the latest version of NiDAQ MX.  The MX installer started up, but told me I needed a later version of Traditional NiDAQ so I installed the latest version of that too, then went back and did the MX install.  The error was still happening so I uninstalled everything NI from the machine using the Windows add/remove programs utility.  Then I installed MX again and this time it didn't ask about Traditional so I didn't reinstall that.

I downloaded v2.0 of the Diagnostic Utility and it gave the same error 200329 I was seeing in Igor Pro.  The diagnostic report is attached to this post.  The card passes the clock and digital output tests but fails everything else.

Fortunately I had a spare 6052E card which I installed in the same machine, after which everything seems to be working fine.  Just to be sure I installed the "bad" card in a different machine, and the diagnostic report is identical.  So I think I can rule out driver problems.  Does the card have some firmware which could become corrupted?  If not then I think it's definitely the hardware.  If you agree could you link me to some instructions for getting a repair quote?

thanks very much,

Gene Civillico

Postdoctoral Research Associate
Princeton University

[David L.]

Hi Gene,

Thank you for all of the testing you have done - this truly narrows down the issue to hardware and one specific card. This help to reduce sending cards in for repair when the problem may be with the PCI slot, software, etc. Since this is a hardware issue, the card will need to be brought in for repair (there is no firmware update or repair  that may resolve the issue). For a repair cost estimate, I suggest calling our sales department at 1-800-433-3488. Please tell them about the forum discussion and debugging we have done, else they may direct you to an engineer to do this over again. (Reiterating, that we are trying to prevent jumping the gun, and bringing in working cards to be repaired.)

Regards,