01-06-2008 11:28 AM
01-06-2008 11:53 AM
01-07-2008 12:46 PM
01-14-2008 08:28 PM
Dan,
Thanks so much, you were effectively helpful.
The " DAQmx Initialize External Calibration.vi " didn't buy the " password " password but it did accept " NI ".
I feel I had scrutinized the various very extensive NI documentations but apparently I have overseen this important clue.
Yes, yet, my board was never calibrated before ( it is new ).
It passes the self test ( in MAX ) but the MAX self-calibration says " failed, the self-calibration date has not changed " ( which is correct, there was no self calibration before ).
In " DAQ-Assistant>Calibration tab " it says " Calibration data is 1-1-1904 " which appears to me the default non-self calibration prompt.
I am the first user and I did not ( even could not ) calibrate, neither externally, nor internally self calibrate ( that being the reason for my question in this discussion forum ) thru the DAQmx (internally self and externally ) calibrations.vi's.
Only in DAQAssistant's ( not MAX's ) tab " Calibration " ( externally ) I can calibrate and the result is perfect.
However, this cal works only within the DAQAssistant and any other ( non DAQAssistant - ) DAQ(mx).vi keeps ( warning 200016 ) asking for " blah blah ...self calibrate the board .. " and presents weird measurement values, be it in differential or RSE or NRSE.
After running " DAQmx Initialize External Calibration.vi " ( with the default password " Ni ", which, btw, I can change properly ) I get a calibration handle value which value I tried to fill out in the " DAQmx Adjust M-Series Calibration.vi " ( I run a M-Series PCI 6221 ), but the result is an error 200112 ( " Calibration handle is invalid " ).
Apparently, again, I do miss something, maybe I misunderstand the relation between " Initialize External Calibration " and " Adjust M-Series Calibration ", but I cannot find other relevant calibration.vi's.
Please advise.
Thanks alot.
Peter.
01-15-2008 09:38 AM
01-15-2008 09:07 PM
01-16-2008 10:05 AM
01-16-2008 03:49 PM
01-17-2008 04:29 AM
Hi Peter,
Unfortunatly this warning can be caused by numerous things. On of the most know causes is discribed in the KB linked below:
http://digital.ni.com/public.nsf/allkb/ECFBB4C79B2F07238625720D007DFB6E?OpenDocument
Regards,
RikP - National Instruments Applications Engineering
07-18-2008 12:53 PM