Dynamic Signal Acquisition

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 200152 when running self test on MAX

Hi Mallorim,
 
I would try to clear up the situation as best as I can...
 
On the notebook with the PCI-4472 DSA placed in the Magma Expansion Chassis, Error 200152 is returned when I try to run the "Self-Test" or "Test Panels" under NI-DAQmx (please refer to Image "Error200152"). However when I use the "Test Panel" under the Traditional NI-DAQ (Legacy Devices) it would be able to acquire data (please refer to Image "testpanel2").
 
No issues were experienced when card is installed in the desktop.
 
On the current status, I'm waiting for a replacement part by Magma that MIGHT solve the problem. However I believe NI should be aware of this issue too as there are inconsistencies when trying to acquire data with NI-DAQmx.
 
I did not send the PCI-4472 card back to NI as I'm using it on a desktop currently.
 
Do let me know if you need other details. Thanks for your help.
 
Warm regards...
Download All
0 Kudos
Message 21 of 24
(4,871 Views)
Hey there again, Scuzzy,
I severely hope the "new" part from MAGMA will help your problem.  I remembered you said earlier:

<quote>
- Put card on desktop (No errors detected)
- Remove card and place into Magma box (Error 200152 detected when running self test. Open test panels to try to force to acquire also is unsuccesful) 
- Put card back to desktop (Error 200152 detected when running card test. However switch to Test Panels and force to acquire each channel and then return to Card Test no errors would be detected).
</quote>

So I am to assume that you are no longer having trouble with the card when you put it back in a desktop?  That, at least, further proves it is a compatibility problem with the MAGMA chassis.

I do want to say a few things.  We are only "inconsistent" in that we don't have the error checking in Traditional DAQ (NI-DAQ) we do in DAQmx.  This check that is failing is one of two.  Either the checksum is wrong (usually fixable by using the Calibration Info Property Node trick) or the EEPROM is returning all zeros (bad, could be power rail, etc.).  Traditional DAQ is returning acquired data, but if (for whatever reason) we can't read correctly from the EEPROM, then default calibration constants will be loaded, so your data will NOT be as accurate as you'd like.  DAQmx checks for this and errors early so that you don't continue on with your application receiving "bad" (uncalibrated) data.  Basically, it's a good thing Smiley Very Happy

Remind me...did I have you check your power rails in the Magma chassis?  What did you find?

Please keep us updated.  We are *all* concerned with getting you up and running. Smiley Happy

Gavin Goodrich
Software Engineer - MIO/DSA Software
National Instruments
0 Kudos
Message 22 of 24
(4,848 Views)

Hi all,

Sorry for the late update... anyway all the problem was solved when we used a different Cardbus. We upgraded from the Cardbus to the Expresscard 54 and all was solved. Thanks!

0 Kudos
Message 23 of 24
(4,694 Views)

Hey Scuzzy!

Glad to hear!  Thank you so much for posting your solution!

-gaving

0 Kudos
Message 24 of 24
(4,689 Views)