Contact an Expert

Thread: Probe compensation problem on my MSOX3024


Permlink Replies: 4 - Pages: 1 - Last Post: Dec 13, 2011 10:04 PM Last Post By: Guest Threads: [ Previous | Next ]
DaveDE

Posts: 11
Registered: 11/12/11
Probe compensation problem on my MSOX3024
Posted: Dec 8, 2011 4:10 PM
Click to report abuse...   Click to reply to this thread Reply
I just received my Agient MSOX3024 oscillosope. Wow! This thing really rocks. I've been giving it a good workout, trying all of the features I can think of. However, during this process, I decided to calibrate my probes. Unfortunately I get no response when tweaking the adjustment pots in the probes. After trying two probes on channel 1, I decided to try channel 2. When I did this, the oscilloscope apparently lost its marbles and started doing all kinds of weird things. It could not display a waveform properly after that, and all channels were useless, displaying giberish. I finally got the scope back to normal after having to reload the latest firmware.

Has anyone else here with a 3000X tried compensating thier probes? My probes are the N2863B models. I think Agilent may have major bug here in the fimware and a dead probe comp problem.
Guest
Re: Probe compensation problem on my MSOX3024
Posted: Dec 8, 2011 11:31 PM   in response to: DaveDE in response to: DaveDE
Click to report abuse...   Click to reply to this thread Reply
Regarding the "no response while adjusting the pots", which hole did you poke?

Is it the one at the connector (2 holes), or the yellow one near the tip of the probe?
DaveDE

Posts: 11
Registered: 11/12/11
Re: Probe compensation problem on my MSOX3024
Posted: Dec 9, 2011 11:12 AM   in response to: DaveDE in response to: DaveDE
Click to report abuse...   Click to reply to this thread Reply
I hadn't realized (or even noticed) the probe compensation trimmer on the probe end. That did the trick, and I can do the low frequency compensation now. I also am unable to reproduce the problem that caused me to have to reload the firmware. I apparently don't remember the exact key sequences I entered because I can't reproduce it. I did power cycle the unit before reloading the firmware and it did not fix the problem. The problem basically resulted in all of the waveforms looking choppy as opposed to smooth, kind of as if the the screen resolution was very poor. I also noticed that when I injected a square wave pulse train and then zoomed out on it, the pulses before and after the trigger were greatly attenuated.

So anyway, the probe comp problem is no problem at all and I can't reproduce the scope going haywire so I'm not going to worry about it. False alarm I guess.
DaveDE

Posts: 11
Registered: 11/12/11
Re: Probe compensation problem on my MSOX3024
Posted: Dec 10, 2011 5:31 PM   in response to: DaveDE in response to: DaveDE
Click to report abuse...   Click to reply to this thread Reply
I know what happened now, with regard to the scope losing its marbles, going haywire, etc. I just experience the same problem when compensating probes again. I repowered the scope, still the same problem existed. While compensating another probe, the scope invoked averaging, 8 averages, and did not reset to zero averaging when done. That's why waveforms looked bad after that. After I turned off averaging, everything was fine, no firmware upload needed. This is a software bug, and I hope Agilent will correct it.
Guest
Re: Probe compensation problem on my MSOX3024
Posted: Dec 13, 2011 10:04 PM   in response to: DaveDE in response to: DaveDE
Click to report abuse...   Click to reply to this thread Reply
I'm not seeing the problem that you are having. Mine always go from Average to Normal after the Probe Check sequence is done, whether passed or canceled.

I have tried the following combination:
- Chan1, both passing and cancelling
- Chan2, both passing and cancelling
- Chan3, both passing and cancelling
- Chan4, both passing and cancelling

and all of the returned to Normal mode. I can't think of any other combination (please let me know).

The only time it stays at Averaging after Probe Check is when I first set the mode to Averaging before doing Probe Check. This is expected, since it returned to my previous state correctly.

Please provide more info or screenshots.

Point your RSS reader here for a feed of the latest messages in all forums