AnsweredAssumed Answered

Wrong value from gpib

Question asked by riwin on Jun 25, 2010
Latest reply on Aug 16, 2010 by anand_jog

Like • Show 0 Likes0
Comment • 3

Hi

When I want to read a voltage value of a waveform, at times I get a wrong value of " 99.00000000000E+36" (when communicating with an oscilloscope using GPIB). I do not know why I get this value. Has somebody experienced this and can explain this to me? Thank you.

No one else has this question

Outcomes

3 Replies

riwin Jun 28, 2010 8:01 AM
Mark Correct
Correct Answer
Thanks for the reply.

But I had used the same command to read the values before too. This happens only at times. Also, When I change the source to a different channel in the oscilloscope, this wrong value appears( There are 4 channels in the scope). Is there anything that I should do before changing the channel ?

Thanks
Like • Show 0 Likes0
Actions
brandon.irwin Jun 30, 2010 12:18 PM
Mark Correct
Correct Answer
Same problem here.

My solution has been to either recapture the waveform when that wrong value is seen, or just transfer the waveform data and manually get the measurements I need. Personally, I think it's absolutely *ridiculous* that we see this problem. I will not be buying Agilent in the future unless the salesman can prove to me that this has been fixed.
Like • Show 0 Likes0
Actions
anand_jog Aug 16, 2010 2:28 PM
Mark Correct
Correct Answer
Hello,

Regarding the reading of 9.9E+37, I've found that the best way to address this is to place the measurement in a while loop and simply test for the faulty condition, i.e

do {
data = capture_on_trigger(parameters);
} while (data > 1e+18);

I find that either I read the right value (say 2.3V) or 9.9e+37 which the while loop takes care of. This is also a remedy when interfacing to the DSO (or MSO) using USB and VISA.

Could this (reading 9.9E=37) be happening due to faulty (not robust) triggering?

Anand
Like • Show 0 Likes0
Actions

Wrong value from gpib

Outcomes

Related Content

Recommended Content