Products > Test Equipment
REVIEW - Rigol MSO5000. Tests, bugs, questions
jord4231:
Thought I'd leave this here for anyone interested.
Window triggering bug anyone else experienced it?
:popcorn:
https://youtu.be/Fg9eL_EKgmE
Cheers
mironex:
--- Quote from: Gandalf_Sr on March 31, 2021, 03:29:22 pm ---Mironex, I just tried to PM you and found your inbox was full.
This is a thread you may be interested in https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2769676/#msg2769676
--- End quote ---
"Better late than never"
Finally, I bought my MSO0574. Thanks for the help :-).
Tommy_Vercetti:
Hello Everyone, I recently received my MSO5074. I noticed that I hear a faint audible sound coming from the scope when the time scale is around 10us or smaller. It can be best described as sounding like bugs in the summer night. The sound momentary goes away when I twist the knob to change the v/div and the screen updates. It also completely stops when I press the run/stop button. I have attached a mp3 file with the recorded sound, it is very faint but you can hear it pause momentary as I toggle different buttons. Has anybody else noticed this? I got the scope from amazon, should I exchange it? I recently did the patch to unlock all the features (hopefully I can still exchange it lol) but I did notice the sound before I did all that.
Tommy_Vercetti:
I am wondering if it could be power supply noise since it appears to be coming from the back left corner of the scope...and it appears thats where the power supply is. It might be some inductors or capacitors giving off the noise. I am not sure. Has anybody faced this issue?
teddychn:
--- Quote ---1. Low contrast, bad viewing angles of screen. It’s also not very bright. Seems to be Rigol scope’s family bug
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
2. Backlight of buttons is not bright enough (especially on 1’st channel button)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
3. Colors on screenshots are very, very different from what you see on screen
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
4. Windows on screen (DVM and Counter for example) are all different in size and don’t stick to each other, so it’s difficult to arrange them.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
5. Selected trigger mode has a very little indicator; single mode doesn’t indicate at all. Selected mode isn’t shown in trigger menu.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
6. In Dots mode you don’t see dots; even at small time base (2 ns) dots are connected with lines.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
7. In High Res mode signal is not less noisy then in usual Sample mode, although vertical resolution is higher
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
8. New measurement is added on the left and moves all other measurements to the right. It would be more convenient if it adds on the left of others
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
9. You can select a separate measurement but you can only DELETE it and can’t change nothing else (source, measurement type). Measurement selection is almost invisible.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
10. There is no user-defined probe ratio – only pre-defined values. Thus it’s difficult to measure current on sense resistor.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
11. Strange behavior. Advertisement says it has more than 500 000 wfrm/s update rate. That’s true, but ONLY in single ch., 10ns time base mode (with AUTO memory mode). Update rate dependence on time base and active channels’ number looks very strange – for example, with 1 active channel and 20 ns time base you have 12 000 wfrm/s, but with 2 active channels and 20 ns time base you have 310 000 wfrm/s. (see update rate testing results below)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
12. With time base more than 20 ms, update rate is higher with 200 MPoints memory selected then with 1 kPoints. (see update rate testing results below)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
13. In AUTO memory mode scope don’t use more than 25 MPoints, although available memory is 200 MPoints.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
14. The way the scope collect data looks strange: packets of samples, separated by a long pause. Pauses between packets take up to 87% of all blind time. For comparison, Rigol MSO4000 collects data in series, sample by sample, without any packets.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
15. No internal 50 Ohm termination, though there is an inactive setting in channel menu.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
16. Offset about 250 uV with external 50 termination connected. Without termination (open input) – just 50 uV
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
17. Scope saves waveform only in *.bin or *.csv, but loads just *.wfm – you can’t load saved waveforms.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
18a. No frequency and magnitude axes in FFT mode
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
18b. FFT does not have MAX and Average
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
18c. FFT size is not shown (and could not been set)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
18d. Lack of Kaiser-Bessel Derived Window and Dolph-Chebychev Window, all these 2 windows with variable alpha.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
19. Scope has Eye Analysis and Jitter functions in Measure menu, but they are not mentioned in manual and seem non-working
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
20. Color Grade function is VERY dependent on waveform’s Intensity setting (display>intensity). At maximum intensity you’ll see all white waveform, at minimum – all black, actually without any color difference. This feature is not mentioned in manual.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
21. Waveform Freeze function seems not working, and I don’t know what it should do.
It works: If you manually stop the acquisition, pressing "Stop", "Waveform freeze" keeps the display "as is" showing multiple waveforms overlaid (Just as if you would take a photo from an analogue scope). If you disable the option, manually pressing "Stop" just shows the trace from the last real-time acquisition. thx mimi
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
22. SCPI command ':LA:TCALibrate' doesn't do anything. This is something that should be a menu option on the scope, so maybe its not been implemented yet.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
--- Code: ---:LA:TCALibrate?
response: 0.000000
:LA:TCAL 0.000000100
:LA:TCALibrate?
response: 0.000000
--- End code ---
:channel1:tcal 0.000000100 for example, works OK
23. Lack of interpolation mode selection (line or sinc)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
24. The trigger delay only works up to 535..537ms (the limit appears to have some sort of hysteresis) for fast sweep rates (<=200us/div, in single channel mode). For faster sweep rates it wraps around, e.g. 600ms equals sone 40ms delay)
Same for FW v00.01.01.04.04 and v00.01.01.04.08
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]
--- End quote ---
I'm waiting for my MSO5074 delivery. For the sake of affordable price, characteristics of long memory, bode plot, power analyisis feature and high sample rate. I've known the high noise issue before placing the order. But I didn't aware that it doesn't come with amplifiers for the vertical ranges below 5mV/div. That's a pity. Just wish the Hi-Res mode could improve that a bit. And the power analysis features seem rough.
Regarding the bug 13, maybe it was the tradeoffs of refresh speed to not applying all the memory in auto memory mode. Regarding this point, I just wish it could use the full memory single acquisition mode. Maybe an option of high/mid/low speed mode could be considered for choosing high speed or high memory utilization here.
Also point 12 and 14 seem weired. I think it's important for Rigol to take it seriously.
I've seen the review on Amazon said the bugs are fixed. Wish that's true. I'm pinning my hope on it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version