02-15-2010 07:03 PM
I have the same error with a PXI-4071 in a PXI 1044 chassis. The error occurs when taking DC measurements - I do not measure frequency. The error is occurring on only one of 18 test sets that we have, and happens about once every 1 to 2 days on the system which operates 24 hours/day. Closing and restarting the executable code cures the error, but re-running the program without exiting the app (compiled in LabVIEW 8.51) does not although the meter is reset either way. I'd be interested to hear if anything is resolved on this issue.
02-16-2010 06:22 AM
maybe review code to see if there is anywhere the dmm needs to autorange.
I never saw any similar errors after removing the frequency function (instead I digitized waveform using dcv function and ran separate vi to determine frequency), but NI suggested it had something to do with voltage ranging using the frequency function. If that was the case, I was never able to properly range it - and I tried exhaustively.
It's possible incorrect range or autorange on other functions also causes an intermittent problem...?
02-16-2010 08:25 PM
Thanks for the suggestion - I reviewed the code, but no auto-ranging in that application (although I've used it on another application where the meters haven't had any of these errors). I wonder if it could actually be a hardware problem with a batch of meters - this one was purchased last year, but the same code has been running on the 18 others that were purchased the year before that with no problems.
02-17-2010 04:04 PM
As far as we've seen so far, the issue seems to come from autoranging in any function, but more particularly taking frequency measurements. We're pretty close to implementing a fix, so it would be interesting to see if we could reproduce the error using your code. Do I have your permission to contact you offline so we can sync up about testing it out? If you're fine with that, I can have the web team retrieve your email from your profile so I can contact you.
02-18-2010 10:20 AM
02-22-2010 09:25 AM
03-19-2010 09:45 AM
Thanks for all your feedback. DMM 3.0.2 (ni.com/updates) is now live on the web and should fix the internal hardware error that you've been experiencing. Please try it out and let us know what you think of it.
02-15-2011 11:14 AM
I started getting this error today after updating to DMM 2.9 yesterday because of a hardware initilization issue. LV version is 7.1, is there anyting I can do for this?
02-15-2011 11:17 AM
try dmm 3.0.2
02-15-2011 01:29 PM
DMM 3.0.2 is compatible with LV 8.2.1 and later.