And so it seems, in this case, the compensation problem lies unfortunately in the frontend, when any probe can´t be trimmed to normal.
Helo
New firmware? MSO5000_00.01.01.04.04
http://www.rigol.com/Support/SoftDownload/3
- Added 500uV/div in vertical scale.
- The waveform can zoom out by drawing a rectangle. If you draw a rectangle
from the top left to the bottom right, the waveform will zoom in. If you
draw it from the bottom right to the top left(the opposite direction),
the waveform will zoom out.
- Added the GND coupling in channel.
- Enriched the color options of the LA channels.
- The boot time is reduced to less than 1 minute.
- Added the 12-bit high resolution mode.
Wonky hi-res, hmm.
Hi,
As I told, rigol anwered me today...very nice.
They already know about and work on it...
So it´s an "official" bug with the overshoots…
Martin
Hi guys,
I recently received my 5074. While trying to compensate the 10x probes, I'm unable to get the perfect square shape of the signal. On channels 1,2,4 I always get some overcompensation. On channel 3 it looks perfect. I've attached pictures to illustrate. Is it normal or should I return it, while still can?
Thanks!
QuoteWonky hi-res, hmm.
Thought about the "non-functional" hi-res mode…
What Do I expect from - Cleaner filtered waveforms.
What don´t happen if You choose the hi-res mode on the 5000 ?
Right, nothing:
Interesting objection, test it out on monday - Scope is on work.
Although I did tests under various mem depth conditions already, but I´ll test it under auto again.
Nevertheless, I want the hi-res option selectable by 0.5 bits steps, as the lecroy and siglent models got.
Interesting objection, test it out on monday - Scope is on work.
Although I did tests under various mem depth conditions already, but I´ll test it under auto again.
Nevertheless, I want the hi-res option selectable by 0.5 bits steps, as the lecroy and siglent models got.
This basically is the same as input signal filtering but with a variable cut-off frequency. I'd prefer the cut-off frequency to be constant over memory depth and samplerate. Do keep in mind that the signal will need a certain amount of noise for hires to actually work and not show fantasy signals. Hires isn't a replacement for having more bits from the ADC.
Hires isn't a replacement for having more bits from the ADC.
This might be easy enough to check; is the record length halved when high resolution mode is used? What about in average mode?
QuoteHires isn't a replacement for having more bits from the ADC.
I knew it already, but other brands could handle it as it allows to show noisy signals crisper, actually the rigol couldn´t do it.
QuoteThis might be easy enough to check; is the record length halved when high resolution mode is used? What about in average mode?
Will be checked on monday.
Edit :
Have a look at the pics:
https://www.eevblog.com/forum/blog/new-rigol-scope/msg2233980/#msg2233980
Record length won´t change or will not displayed.
Interestingly, I observed the same overshoots after upgrading to 01.01.04.04 and doing a calibration. Before everything look very nice. (It also appears in the non-hacked firmware)
EDIT3:
The problematic calibration is lfcal.hex. Just replacing that file gives perfectly shaped squares again.
EDIT3:
The problematic calibration is lfcal.hex. Just replacing that file gives perfectly shaped squares again.
Sounds to me like they're driving one of the front-end opamps harder than before and creating a problem with overload/recovery.
It's good to know it can be fixed and it's not a hardware problem.
OTOH it needs fixing ASAP.
Told them(rigol eu).
What I can´t complain in general:
Why do I haven´t these issues ?
Bought it, everything was fine - where others with the same firmware have the problem.
Then the new firmware is avaible, I did the upgrade - And still have no problems with overshoots.