11-30-2011 06:10 PM
I have a PCI 6033e card that has been running for a long time on an old computer (Windows 2000) that recently has the same issue as described in THIS post. The voltage reading in any NI-DAQmx tasks, or any VI run in LV is always the minumum voltage value in the negative domain, with no noise (i.e. -5V, -10V etc). When the voltage range is set to greater than 0V (i.e. 1V-5V) the voltage is a steady 0V.
I don't think I have the same problem as in the post I linked above because my card does not work on two separate computers; where as the post above, the card worked in one computer and not the other.
I am attempting to trouble shoot the card on a "new" computer (Windows 7) and have the following issues.
On both computers, old & new:
-Newest versions of drivers have been downloaded and updated.
-Card passes self test
-Card can reset.
-Card Fails Self Calibration (error 200545)
When I run the DAQ Diagnotistic utility 2.1, it get hung up after the following stage:
11/30/2011 3:46:58 PM
Results saved to: C:\Users\UWABL\Documents\Diagnostic Results.txt
Selected Device: Dev2
Device Type: PCI-6033E
Serial Number: 104FDFD
Device Support: (PASS)
NI-DAQmx Version: 9.4 (PASS)
Device Reset: (PASS)
At this point, the DAQ Diagnotistic utility 2.1 has a warning to unplug the cable to the DAQ to prevent unintentional actiavation of instrumentation. However, there is nothing connected to the DAQ. When asked if I would like to continue, the DAQ Diagnotistic utility says "testing" but does not procede with the Diagnotistic test.
Warning
State that the DAQ Diagnostic Utility is stuck in after I tell it to continue.
Any ideas on whether this is a bad card, or it needs to be sent out for calibration would be appreciated!
Thanks,
Jeff Campbell
Solved! Go to Solution.
12-01-2011 05:19 PM
Greetings Jeff,
Thank you for posting all that information! Based on the fact that you have tried this on both computers with updated drivers and the 6033e calibration failed on both, it is pointing towards sending it out for calibration.
However, before going that route, if you could post the results of C:\Users\UWABL\Documents\Diagnostic Results.txt that would help us get a better idea of what is going on.
Thanks!
12-01-2011 07:39 PM
Hello Aldo,
Thanks for getting back to me. The DAQ Diagnotistic utility 2.1 gets hung up before it is able to write anything to C:\Users\UWABL\Documents\Diagnostic Results.txt and so that file is simply a blank .txt file.
The only information I have is what appears on the DAQ Diagnostic Utility screen that I posted above,
11/30/2011 3:46:58 PM
Results saved to: C:\Users\UWABL\Documents\Diagnostic Results.txt
Selected Device: Dev2
Device Type: PCI-6033E
Serial Number: 104FDFD
Device Support: (PASS)
NI-DAQmx Version: 9.4 (PASS)
Device Reset: (PASS)
I would love it if we could send it in for a calibration. But is there a way to know if it's dead or in need of a calibration? For example, the fact that the card can't even complete the first set of the DAQ Diagnostic Utility has me worried it's finished. What are your thoughts?
To re-iterate, the DAQ Diagnostic Utility gets hung up after the "Device Reset" step because it comes up with a warning that an external cable is attached to it. However, nothing is attached.
Thanks,
Jeff Campbell
12-02-2011 06:14 PM
Hi Jeff,
one quick way to tell if your 6033e card is either dead or needs calibration is to do a quick voltage reading on sources which you know the value (battery for example). If the 6033e doesn't even respond to that type of input, then you can be sure that the card is toast. Otherwise, I just checked and you can send it in for calibration.
Let me know what you find out. Thanks!
12-05-2011 01:16 PM
Thanks Aldo,
I tried to go a step beyond what you mentioned and hooked up a function generator to apply a signal to the card. You can see the signal on the scope (below) and the card's response (flat-line).
From what you said above, I believe my card is toast. Would you agree?
As a side note, I verified this method on a different (working) card and the card's response was the same signal shown on the scope.
12-05-2011 02:01 PM
Hi Jeff,
Thanks for taking the extra step and based on the results, it looks like the card is done. I don't think this is a calibration issue either since there is absolutely no response to the signal from the oscilloscope. This is clear since you tried the same signal on a different card and it worked. If you are looking into replacing the card, the PCI 6033e is no longer available but you can check out our page http:\\www.ni.com/daq/multifunction to see the new M series and X series cards. Let me know if you have any questions, thanks!
12-05-2011 02:08 PM
Thanks Aldo! Is there a particular card you would recommend as a replacement?