REVIEW - Rigol MSO5000. Tests, bugs, questions - Page 1
Forum section: electronics / testgear

author: WinnieThePooh
author_rank: Newbie
timestamp: June 17, 2019, 10:14:18 am
content: Hello community!In this post I’d like to tell about my impression and testing results of Rigol MSO5074 oscilloscope.Testing methods are based on Altemir’s postREVIEW - Rigol MSO4000 and DS4000. Tests, bugs, firmware, questions, etc.... Some results to compare with were also taken from his post.After weekly testing I’ve written a little report for Rigol’s local distributor on Russian language. Some most significant bugs are listed below with a little description.Please let me know if you found other problems.Known Firmware Bugs/Issues(red indicates latest FW version available,italicindicates requires for testing - please, inform me about results)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]Rigol MSO5000Rigol MSO400015.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:channel1:tcal 0.000000100 for example, works OK23.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]Testing results1.System info2.Acquisition - all with open input, 1ms time base2.1 Normal mode2.2 HighRes mode. Signal isn't less noisy then in Normal mode (bug #7).2.3 Average mode, 256 averages3.Waveform update rate3.1 Sample rates3.2 Waveform update rate. Input signal - sin 10 MHz 1 Vp-pMSO 4000 results:3.3 Waveform update rate. Input signal - sin 1 MHz 1 Vp-pMSO 4000 results:Tests 3.2 and 3.3 is a good illustration of bug #11. Scope has maximum update only in certain time base (10ns in 1ch mode, 20ns in half ch mode, 50ns in all ch mode). MSO4000 results is much linear and smooth, without unexpected peaks.3.4 Blind time3.5 As mentioned in bug #14, scope has strange acquisition mode - packets of samples, separated by a long pause. Duration of each phase of acquisition cycle was measured at different time base.4.Frequency response4.1 With and without correction of measuring path. Average value4.2 With correction. For each channel separately4.3 Comparison with other scopes4.4 -3dB frequency in HighRes modeedit 1.Added bug#22, thanks tothm_wedit 2.Added bug#18b, #18c, #18d, #23, #24, thanks toalexvg,mim

author: WinnieThePooh
author_rank: Newbie
timestamp: June 17, 2019, 11:02:36 am
content: All tests results and report (only in Russian, sorry)

author: thm_w
author_rank: Super Contributor
timestamp: June 17, 2019, 09:18:13 pm
content: Very comprehensive report!I noticed the same odd thing with the packets of samples. If you turn on zone triggering, I saw it change to more consistent sampling and the dead time was reduced (more spread out I guess), seemingly regardless of whether it was hitting the signal. But maybe there was some other reason for it, related to my triggering.Now I'm checking wfm/s and zone triggering doesn't seem to effect that much (reduces it about 10%). No difference between 1 zone or 2 zones.There are definitely oddities to how this scope works, whether due to the ASIC and its functionality or software bugs, not sure.QuoteYes someone here even reported it to Rigol tech support, that their non-paid for feature is not workingedit: looks like you did the same thing, hopefully they don't mind. But thanks for passing all this on.QuoteThis is normal, sort of a placeholder and to tell you the input impedance. In the case of DS2000->DS2000A they added a 50 ohm option to later hardware, they may or may not do this with the MSO5000. Usually its a good way to differentiate the low/high end models. A generic BNC pass through is only ~$6.QuoteI think you should just set it to 50% for color grading (or set auto to that). But it would be nice if changing this did something like change the color pattern or similar.Bug 22.[FW v00.01.01.04.04]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.Code::LA:TCALibrate?response: 0.000000:LA:TCAL 0.000000100:LA:TCALibrate?response: 0.000000:channel1:tcal 0.000000100 for example, works OK

author: WinnieThePooh
author_rank: Newbie
timestamp: June 18, 2019, 07:53:22 am
content: Quote from: thm_w on June 17, 2019, 09:18:13 pmJust checked zone triggering, and noticed another couple of odd things.1 When zone triggering is active, there is no 500 000 wfms/s peak. Just 90 000 wfms/s - looks much more linear2 If you create a zone that can't be intersected by signal, trig out will still be active and generate trig signal (see pictures). And - magic - trig out shows update rate much higher than in normal mode without any zone triggering. More than that, there is no any packets in this case. (Test mode: input signal - sin 10MHz 1Vp-p, channel 1, 20ns time base. 12 735 wfm/s without zone triggering, 11 400 wfm/s with settings from picture "Zone0", 63 800 wfm/s with settings from picture "Zone1". Last picture - trig out signal for "Zone1" case. )

author: WinnieThePooh
author_rank: Newbie
timestamp: June 18, 2019, 08:21:58 am
content: Quote from: thm_w on June 17, 2019, 09:18:13 pmYes, works great with 50% intensity. But when intensity is set to 100% and you turn on color grading, you just don't understand what is going on. Influence of intense on color grading isn't mentioned in manual. Moreover, intensity setting isn't available in color grading mode.Quote from: thm_w on June 17, 2019, 09:18:13 pmThanks, added in bug list

author: Martin72
author_rank: Super Contributor
timestamp: June 30, 2019, 03:25:29 pm
content: Hi,Maybe a bug:Want to look about new Firmware, so I connected the MSO to LAN, pressing "Online Upgrade".After take the confirmation in the popup box, it freezes.Switch off/on, it still freezes.Switch off, disconnect the lan, switch on, everything is OK.Thought, this behaviour comes with the hack, so I reinstalled the former FW.Same as above, it freezes when You will do the online upgrade thing.Martin

author: tv84
author_rank: Super Contributor
timestamp: June 30, 2019, 04:05:03 pm
content: Quote from: Martin72 on June 30, 2019, 03:25:29 pmVery strange!!I don't think mine does that...

author: tv84
author_rank: Super Contributor
timestamp: June 30, 2019, 04:14:37 pm
content: Quote from: thm_w on June 17, 2019, 09:18:13 pmAs you can see in the list of SCPI commands that I posted, this command has function_ID 11031 assigned to it so I think it's implemented.Could be a bug but maybe you're not supposed to trigger that without some vendor validation... just guessing.

author: Martin72
author_rank: Super Contributor
timestamp: June 30, 2019, 04:43:57 pm
content: QuoteA few weeks ago, mine doesn´t do that too - After a while the message appears, there is no new firmware avaible.Maybe the server is down and this is a situation which can trigger this behaviour, I don´t know.Nervertheless I´ve informed rigol.Also about the "bug", that the power-state is always the same.You could choose between "Default" and "Last", but it´s always "Last" after turning on....

author: Martin72
author_rank: Super Contributor
timestamp: July 01, 2019, 07:34:11 pm
content: QuoteIt´s known (since testing my scope after modification) and has been forwarded.

author: alexvg
author_rank: Regular Contributor
timestamp: July 13, 2019, 09:03:06 pm
content: Thanks to your report and measurementsI add some...18b. FFT does not have MAX and Average18c. FFT size is not shown (and could not been set)18d. Lack of Kaiser-Bessel Derived Window and Dolph-Chebychev Window, all these 2 windows with variable alpha.I don't try to save a FFT trace, I don't know if this feature exists.23. Lack of interpolation mode selection (line or sinc)

author: hhappy1
author_rank: Contributor
timestamp: July 14, 2019, 06:26:35 am
content: Thanks to your report and measurements2. ^^I think number 14 is very important.Because of black time, The mso5000 cannot be measured.Set time is 2us and play a waveform with a glitch, Failed to measure.Measurements are made for other products of 3,600wf/s.Modify the trigger to a slope or pulse, and 2ch & 3ch on-off. You can see it if you do it.If you're doing very well......

author: Sighound36
author_rank: Frequent Contributor
timestamp: July 16, 2019, 08:12:10 am
content: Another suspected bug for you chapsWhen testing power mains 240Vac noise with the power analysis feature using a fully active Micsig DP20003 probe on channel 1 and a Pico TA189 current probe on channel 3 the scope would lock up and a hard reset required.Performed numerous tests over a three hour period with the scope locking up around 50% of the time, tried the probes on adjacent channels (1+2 etc) also (3+4) same result, no spurious readings or spikes.

author: KC0PPH
author_rank: Unknown
timestamp: August 03, 2019, 02:44:06 pm
content: Thanks for Posting this information.

author: hhappy1
author_rank: Contributor
timestamp: August 13, 2019, 12:16:17 am
content: We have a new firmware.I heard that the wf/s has been improved.Let's compare who's different. ^^

author: mimi
author_rank: Newbie
timestamp: September 05, 2019, 01:24:13 pm
content: Hello!I checked the update rates for FW v00.01.01.04.08 and they are completely unchanged. The spec'd 500k wfm/s are only available with a single channel at 10ns/div. Might be a bug in their ASIC (which would be not so cool).The only improvement I saw is that "color grading" now disables the intensity option (which makes sense). Also with 00.01.01.04.04 the intensity settings would be randomly greyed out even with "color grading" off. That has been apparently fixed. That's a fix for Bug 20 in WtP's list.iMO 21) is not a bug. 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. In fact when I got the sope this option was on, and I was quite irritated that when pressing "Stop" it would not show a clear trace.I have another Bug for the list: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

author: Sighound36
author_rank: Frequent Contributor
timestamp: September 05, 2019, 06:19:39 pm
content: When using the cursors try using measurement mode, mine just doesn't work, neither does it when in the jitter measurement mode either.All other cursor functions are fine

author: mimi
author_rank: Newbie
timestamp: September 05, 2019, 07:05:11 pm
content: Quote from: Sighound36 on September 05, 2019, 06:19:39 pmWorks here (after RTFM). Allows to enable or disable "indicators" for auto measurements.Best regards

author: Martin72
author_rank: Super Contributor
timestamp: September 05, 2019, 07:41:13 pm
content: Quote from: mimi on September 05, 2019, 01:24:13 pmHi,See also here:https://www.eevblog.com/forum/blog/new-rigol-scope/msg2047141/#msg2047141And:https://www.eevblog.com/forum/blog/new-rigol-scope/msg2058052/#msg2058052Where I wondered about this:QuoteMartin

author: mimi
author_rank: Newbie
timestamp: September 05, 2019, 09:20:00 pm
content: Hi,I cannot confirm the 500k wfm/s for 5ns/div here.Depth fixed at 1k pts:5ns/div, 1ch (8G/s,1k) 102k wfms/s10ns/div, 1ch (8G/s,1k) 502k wfms/sThough 5ns/div and 10ns/div have the same acquisition duration of 125ns...One observation: If you use 10ns/div and feed a 100kHz signal you apparently not loose a single trace (i.e. you get a stable 100.000 kwfms/s). It starts skipping traces at about 200kHz.

author: Martin72
author_rank: Super Contributor
timestamp: September 05, 2019, 09:50:48 pm
content: QuoteIf desired, I will repeat the measure..

author: mimi
author_rank: Newbie
timestamp: September 06, 2019, 07:18:36 am
content: Quote from: Martin72 on September 05, 2019, 09:50:48 pmNot urgent, we cannot do much against the weird behavior anyway. Rigol is probably well aware of the issue and tries to address it.I am wondering if the MSO7000 behaves similarily ?

author: tinhead
author_rank: Super Contributor
timestamp: September 07, 2019, 09:09:29 am
content: Quote from: mimi on September 05, 2019, 01:24:13 pmit's not a bug, it is what the Hardware can do. When you check MSO5000 Datasheet, Page 8 "500,000 wfms/s Capture Rate", you can clearly see Rigol Shows screenshots with 10ns/div and 1k mem Depth as "reference Picture" for 500000 wfms/s". There is no single statement like "500000 wfms everywhere", so it is enought to get that rate at least once - as they did.

author: AngusBeef
author_rank: Regular Contributor
timestamp: September 10, 2019, 01:54:45 am
content: I seem to have an issue with overshooting in channel 1 despite upgrading to the 01.01.04.08 firmware on gitlab...I thought 1.0.04.08 was supposed to fix it? I saw no change from 01.01.04.04 to current.https://gitlab.com/riglol/rigolee/tree/MSO5000/GEL

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: September 10, 2019, 02:47:44 am
content: This is a much better topic to post this than the hacking thread.While some users reported 04.08 correct their overshoot/undershoot problems, the official readme in 04.08 does not specifically state this particular fix.I presume you adjusted your probes with the reference signal, and did a self-cal after the upgrade? As the upgrade alone will not fix the problem.This issue seem to be hardware related, as it only affects certain users. I don't have this problem even with 04.04 on all four channels, so I cannot test whether 04.08 makes a difference.The word is Rigol is aware of this issues a few months back, and they are working on a firmware fix for it. The question is whether it is fully implemented in 04.08, or you have to wait for a future release. If it persists, you may want to let Rigol know so they can help you to fix it.

author: AngusBeef
author_rank: Regular Contributor
timestamp: September 10, 2019, 03:18:46 am
content: Quote from: NoisyBoy on September 10, 2019, 02:47:44 amThanks - removed from the other post - I've only got it on one channel, the other 3 look a hair undercompensated when it's as good as I can get it, so my fear is that it's a hardware issue...it's just disappointing that the new toy isn't perfect - but it's a Rigol so it happens. I'll get ahold of them and see what I can do. Thanks!

author: AngusBeef
author_rank: Regular Contributor
timestamp: September 26, 2019, 08:50:36 am
content: Used the lfcal.hex from @mabl, backed up both the lfcal.hex from /default and /data then overwrote both of them and my issue with overcompensation went away.Self-cal completed, I can get still get all 4 probes compensated correctly - no ringing, no overshooting, etc.

author: matlipinski
author_rank: Contributor
timestamp: October 29, 2019, 12:35:26 pm
content: Hi.I am writing once again (but in this thread this time).I have bought MSO5074 (hw. version 1.00) some time ago, and from the beginning I have overshoot undershoot issues, as well as square signal from arbitral generator has also 20% over and undershoot. After applying newest firmware 01.01.04.08 and lfcal.hex from mable and running self calibration they are still there. After applying mable's lfcal.hex they vanished from 1st channel, almost vanished from second channel, but they are still on 3rd 4th channel. Do You think i should send it to Rigol? What can I do else? Is it normal?Please look at the screenshots.There is also screen shot from Rigol 1054Z - square signal from 1KHz test signal of MSO5074 seems to be OK on 1054Z. Under/oveshoot is also visible on 1054Z.

author: TK
author_rank: Super Contributor
timestamp: October 29, 2019, 12:41:23 pm
content: If you have 01.01.04.08 you should not apply other ifcal.hex file. I think you have a faulty scope. When was it purchased? Have you contacted Rigol EU to ask if your unit has the latest HW fixes (LCD, fan noise)?

author: matlipinski
author_rank: Contributor
timestamp: October 29, 2019, 01:19:07 pm
content: OK I will revert lfcal.hex to original state and test it again.Yes I have asked Rigol, if I have all fixes applied, they confirmed.I have asked Rigol if this over/usndeshoot is normal, they said no, and sent me beta firmware 03.01.04.04. On 03.01.04.04 it was like on 01.01.04.08.After sending them screenshots from 03.01.04.04 they said that this time it is OK.I think it is not, it is my third oscilloscope, I had never such issues before.I couldn't test arbitral generator, I had no licence earlier.

author: matlipinski
author_rank: Contributor
timestamp: October 29, 2019, 09:51:50 pm
content: I have posted in "New Low Cost Rigol MSO5000 Oscilloscope" and "REVIEW - Rigol MSO5000. Tests, bugs, questions" threads.Could You please show me Your 1KHz signal from MSO5000 as well as 1 or 10KHz signal from arb. signal gen. on Your MSO5000?I will ask Rigol for help.After self cal. on factory lfcal.hex it looks like this:

author: TK
author_rank: Super Contributor
timestamp: October 29, 2019, 10:33:42 pm
content: CH1 and CH31KHz square wave from Wavegen, direct COAX cable with 50ohm passthrough, 1X

author: Martin72
author_rank: Super Contributor
timestamp: November 07, 2019, 09:24:05 pm
content: Got two "new" bugs/missing features:Power on state:Choosable are "Last" or "Default" - None of them works, in every case after power on my scope has the optinon menu open.Cursors :The horizontal and vertical cursor-lines are always together dispaying, you can´t choose between only vertical, only horizontal or both.

author: thm_w
author_rank: Super Contributor
timestamp: November 07, 2019, 11:19:36 pm
content: Quote from: Martin72 on November 07, 2019, 09:24:05 pmThe "Last" or "default" is more to save all of the configuration values: time base, probe attenuation, etc. I wouldn't expect it to save the exact state of the UI (although it could be nice if it did).Seems like its storing a reasonable amount of data:Quote

author: Martin72
author_rank: Super Contributor
timestamp: November 07, 2019, 11:28:28 pm
content: QuoteYes and no…"Default" means to me, that the scope starts "like it was" on delivery state."Last" means to me that it will start with the last configurations I´ve taken before shut-down.Seems logical....only to me ?

author: SimonH
author_rank: Contributor
timestamp: November 23, 2019, 09:33:19 am
content: No. 17 is fine. You have to switch from 'screen' to 'memory'. Then you can save wfm. A bit strange, though, that by default, it saves only the screen.FW FW v00.01.01.04.08No. 1 is fine with HW version 1.01One more thing: The protocol analyzer often just stops working. I think it has to do do with a faulty threshold. I've once also seen that it 'sees' some data, although the threshold was way beyond the waveform. And putting it to the right place made the decoding disappear. Not reproducible though.

author: Martin72
author_rank: Super Contributor
timestamp: November 23, 2019, 11:42:01 am
content: QuoteTo 18b, it got peakhold, what MAX concerns.To 18c, showing memorysize is indeed missing, sample-size is displayed instead.

author: Martin72
author_rank: Super Contributor
timestamp: November 23, 2019, 09:44:14 pm
content: Quote from: Martin72 on November 07, 2019, 09:24:05 pmForgot to post the answer from rigol ( always rigol support in EU meant) :For them it´s not a bug or missing feature, they suggest me to put the vertical or horizontal lines "away" when vertical or horizontal cursor value only are interesting...

author: SimonH
author_rank: Contributor
timestamp: November 23, 2019, 11:11:16 pm
content: One more thing about protocol analysis:Apparently, the decoder only works if the context it needs to decode, i.e. a CAN frame, is visible on the screen. It seems to 'see' just what we see on the screen. Fair enough. BUT: If I have, say, a very long CAN frame, then I have to squeeze it so much that I cannot distinguish the data bits any more. And also cannot read what's the data any more. Of course, then there is still the table view. But it would be nice if I could zoom into the frame and actually see the data. This is not possible because as soon as I zoom in, it loses the context.Am I missing something? Can I somehow "freeze" the decoding, so that it stays visible, keeps track on the waveform, but does not try to re-decode anymore? This would solve this issue.

author: SimonH
author_rank: Contributor
timestamp: November 24, 2019, 07:55:45 am
content: Concerning my post above about protocol analyzer:Of course I don't mean real-time encoding while a signal is being repeatedly captured, but inspecting a previously captured signal. Actually, I don't see any reason why the decoder should try to re-analyze the waveform every time I move or zoom it. Shouldn't it just decode (to get good speeds just the visible section) when it actually captures a signal, and as soon as the signal is stable, start a complete decoding of the whole memory content. And then just show that decoding, which is moved and zoomed simultaneously with the waveform? This would be simple, and one could zoom in into every detail.One more thing: If I save a waveform (memory content, not screen) after having captured many bursts of communication into segmented memory ('recording'), I would assume the scope to store all these captures (the memory content, that is). Instead, only the actually seen segment is stored.

author: SimonH
author_rank: Contributor
timestamp: November 25, 2019, 10:49:03 pm
content: I just found that if you enable the zoom function, you actually can zoom into details. As long as the context is visible on the "original" waveform, you can see the decoded data also in the zoom window. I though I have once seen this not working. But apparently it works.

author: thm_w
author_rank: Super Contributor
timestamp: November 25, 2019, 11:47:20 pm
content: Quote from: SimonH on November 24, 2019, 07:55:45 amMay be possible to do it in a script:Code:save:format csvsave:csv:length maximumfor x in range(5)::record:current x:save:csv D:\x.csvDepending on if the "save" functionality works the same in record mode as it does in other modes.

author: matlipinski
author_rank: Contributor
timestamp: November 26, 2019, 10:17:21 am
content: For all whose MSO5000 has over/undershoot. I have bought MSO5074, and from the beginning i had over/undershoot problem. I contacted Rigol support. They sent me all possible firmware versions and told me: make self calibration procedure for each firmware version we have sent to you. But nothing changed.I decided to send my MSO to them. They have fixed over/undershoot problem, and calibrated the scope. They have also applied newest hardware fixes (also to built in signal generator).They also changed HW version number to 1.01. I had 1.00 earlier.Now everything is fine.Over/undershoots looked like attached bellow.

author: irw
author_rank: Newbie
timestamp: December 03, 2019, 12:39:48 pm
content: Hi all,How is the current status of the firmware? Still too buggy?Thanks

author: Martin72
author_rank: Super Contributor
timestamp: December 03, 2019, 06:36:03 pm
content: Hi,It wasn´t to buggy even from the beginning, depending on what things you work on, you wouldn´t recognize them.

author: irw
author_rank: Newbie
timestamp: December 03, 2019, 06:46:34 pm
content: My main concern is the vertical accuracy, as I read that it was about 4mV/div... at least the "True" value... As I need to measure low currents, I wonder how low can I get, if the accuracy is that "high"...

author: Martin72
author_rank: Super Contributor
timestamp: December 03, 2019, 09:41:06 pm
content: Hi,This is a point which doesn´t have much to do with bugs, it´s a hardware thing.When i remember it right, in the first FW update a 500µV Resolution was implemented."Of course" bandwith-limited and not really a true one.QuoteGenerally, scopes aren´t precisely as dedicated volt-/amperemeters.If you need to measure dc-currents, you should do it better with an suitable amperemeter.For example, we must record loadsteps and static values of our converters/inverters.First one we do of course with a scope, but last we do with a high precision voltage/current/power device.Because everyone knows that the vertical accuracy of a scope couldn´t reach the precision of a dedicated measure device.For recording loadsteps the accuracy ist not the most important thing.Finally we talk about a scope for 1000 bucks….

author: matlipinski
author_rank: Contributor
timestamp: December 03, 2019, 10:22:33 pm
content: Quote from: irw on December 03, 2019, 12:39:48 pmI think FW 01.01.04.08 and HV 1.01 is usable, there is still a lot to do, but if are aware of limitations of the device, you are able generally measure what you want to.

author: Martin72
author_rank: Super Contributor
timestamp: December 03, 2019, 10:32:36 pm
content: Nothing else I said before..And what the "limitations" concerns, we got two scopes for 26000 bucks together in october.Generally, they couldn´t do "more" as a scope for 1000....they could do some things better, but more...no.

author: SimonH
author_rank: Contributor
timestamp: December 08, 2019, 09:44:42 am
content: One more quite significant one, I guess:While in the decoding menu, the available signals are named correctly (MOSI, MISO,..), in both the search and trigger menus they are names "i2c-ish" (SDA, SCL). I think, this typo has been mentioned before somewhere. But actually, it doesn't appear to be just a typo. SPI search and trigger do not work in any way. Decoding works fine.FW 01.01.04.08Hope this will be fixed in the release that appears to be about to come.

author: SimonH
author_rank: Contributor
timestamp: December 08, 2019, 09:46:52 am
content: oops... As you might guess "decoding menu" here should be "SPI decoding menu"

author: SimonH
author_rank: Contributor
timestamp: December 08, 2019, 01:14:41 pm
content: I just found another big one, I guess. Saving waveforms doesn't seem to work at all. When I save a waveform showing nice 3.3V SPI as .wfm, then press autoset w/o any signals on the probes, then load the same waveform again, strange things happen. Once I just got a flatline, and one I got a part of the waveform, but with signal levels 0V-330mV instead of 0V-3.3V (probes were 1:1).

author: SimonH
author_rank: Contributor
timestamp: December 09, 2019, 10:35:32 pm
content: Can anyone confirm that last one? When I store large wavefiles, (250MB) as .wfm, and then reload these, I constantly get very strange things back. As said before, parts of the waveform, but with amplitude wrong by a factor of 10 (happened once), and very often a waveform of 10 us length (original was some 100ms), an amplitude of some mV, and a frequency of exactly 4GHz (which means that it apparently assumes that the sample rate was 8GSa/s, and the samples are somehow alternated).This one is quite a bummer...Then, there is a minor one. Playing around with the segmented memory ("record"), I found that when displaying a data record, the delta-T reading in the record window is updated to the correct value only after modifying the x-scale.Then, the decoding is still a bit unstable. But I found that when it shows most of the data correctly, but just some incorrectly, it helps to just slightly move the threshold(s) a bit. They were perfectly in the middle, and the wrongly decoded data did not have any glitches. But after just "touching" the threshold a little bit, the data showed up perfectly.BTW: Is this the right place to place these things? I mean to remember someone stating that Rigol is reading this or someone is collecting this stuff for them...?Apart from some minor things and the real bummer addressed here, the scope works very well in my opinion.

author: Martin72
author_rank: Super Contributor
timestamp: December 09, 2019, 10:53:21 pm
content: Hi,QuoteBoris (from Rigol EU) and I have a "deal" :Waiting for the next update and then he will comment ( I post) the points mentioned in Post#1 of this thread.He confirms some of then as "real bugs" they´d take notice about.Will mean, this thread is known by rigol.

author: SimonH
author_rank: Contributor
timestamp: December 10, 2019, 12:15:51 am
content: Great!There is one more thing that puzzles me. Maybe someone can explain it. Not a bug, actually the opposite of a bug... somehow...When working with the recording function, it appears that the scope does not have 200MSa of memory, but (a bit less than) 1GSa. For example, if I record with 200MSa, I get a maximum of four frames. And if I decrease the sampling depth, it always sums up to some 900 MSa. Only with very small frames, the number of total memory decreases. It really looks like all of these frames have the same granularity as if recorded as a single shot.Do I oversee something here?

author: SimonH
author_rank: Contributor
timestamp: December 10, 2019, 06:59:31 am
content: Ok, I think I've found why this is possible. It appears that when recording, not only the sample memory is used. I hooked up a 15MHz square and recorded as fast as it could. This resulted in a rate of about 15'000 recordings per second (if I believe the delta-T shown in the window). So, it appears to not segment the actual sample memory, but just keep moving the samples into "normal" memory.Fair enough.

author: rowifi
author_rank: Contributor
timestamp: December 20, 2019, 07:17:14 pm
content: Well, I had a similar bug when I evaluated a 7000 scope. Memory saves and recalls were totally buggy and random. Maybe the usb stick compatibility, but it was one reason to reject the scope (among other reasons ).Looks like the 5000 is still not suitable as a professional tool. I can't have flakey data decodes.Still, I rejected a R & S due to a few of its bugs. What's the matter with these manufacturers. . We're at a race to the bottom in terms of quality just to get to market first.

author: Martin72
author_rank: Super Contributor
timestamp: December 30, 2019, 10:18:09 pm
content: Today, I´ve noticed some "issues":- Under circumstances (which are not clear to define) the acquisition field is greyed out, you can´t do any changes - Until you press the "Auto" button, after the automatic setup, the field is active again.Sometimes it´s only the acquisition mode, sometimes acquisition and memory depth ( you can choose between the values but it will always stay the same).Reading the manual, there are no situations described which can cause these effects, so I think it´s a bug.- Trigger: The markers for trigger level/time are always in the colour of the first channel (yellow), it´s sometimes irritating (I know it from other scopes, if you trigger on e.g. ch2, the markers changes their colours to the colour of the selected channel.)- Working with AC coupling: When I short the probe, there´s a offset on the channel - Disconneting the probe, offset disappears…Martin

author: Alfons
author_rank: Regular Contributor
timestamp: December 31, 2019, 11:03:06 am
content: Quote from: rowifi on December 20, 2019, 07:17:14 pmOnly then buy a device until you are informed about the bugs. Do not rely on first reviews, but on user experience.The cost pressure means that more and more manufacturers are packing their devices with software. Hardware is still expensive, so software is traded. And that often doesn't work.Micsig, for example, shows with its tablet devices that there is another way. However, these devices are only equipped with the essentials and cannot do as much. But hardly any manufacturer dares to enter the market today with devices, which are not full packet with Software. It takes years for all bugs to be fixed. But not everyone like Keysight or Tektronix can keep a device on the market for so long. The Rigol will probably always remain a crutch, but you can still live with it at the price if you don't need everything. At R&S, you don't know where you're going. And the R&S devices would have the potential if the manufacturer is ready to invest. But I also don't understand how to deliver such a wonderful device with lots of errors.

author: Martin72
author_rank: Super Contributor
timestamp: January 01, 2020, 02:00:43 am
content: Quote"Today" tested again...it´s a generally thing when you are in the 1mV....5mV range ( or 10mV/50mV when using 10x Probe).Measuring output ripple noise when the DUT´s claimed values lies in this rangeseemsnot possible with this scope - Makes me not happy...Try it again with an extendend filter.

author: sinpie
author_rank: Newbie
timestamp: January 17, 2020, 09:20:15 am
content: I report a new bug. It may or may not be a bug, but I think it has to be fixed.Search -> Threshold shows an analog input voltage even 10x attenuation is set.(e.g. by 10x atten., 10mV is an actually 100mV. but when I set the threshold voltage, it shows 10mV as the threshold voltage)So it confuses me whenever I set the threshold voltage.%% A threshold voltage on the Trigger menu shows the right voltage.

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 17, 2020, 09:36:17 am
content: SinpieTry using the precision button

author: sinpie
author_rank: Newbie
timestamp: January 17, 2020, 11:22:19 am
content: What I mean was, the vertical location on the picture should be 1.6V, not 160mV, at the 10x probe. (I already set the channel as 10x)Anyway, where could I find the precision button on MSO5000 then I'll try it.Thank you.

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 17, 2020, 01:49:14 pm
content: Hi SinpieIf you go into measure menu <> settings <> Mode then set to "precision" this engages all of the memory for a much tighter 'accurate' readings coupled with high resolution really helps.

author: sinpie
author_rank: Newbie
timestamp: January 17, 2020, 03:55:32 pm
content: I think the precision option in measurement menu doesn't matter with the thresold setting of Search menu(button), but I will try.Thank you.

author: sinpie
author_rank: Newbie
timestamp: January 18, 2020, 12:29:50 pm
content: Quote from: Sighound36 on January 17, 2020, 01:49:14 pmnothing has been changed after I set 'precision' on measurement.Search->Threshold still shows 160mV for 1.6V on 10x probe and 10x attenuation setting on the scope.

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 20, 2020, 11:48:02 am
content: Hi SinpieI had a quick check of one of our two 5000's over the weekend and it reads corrects with the Rigol 500Hhz probeWill check the other later in the week for you.

author: sinpie
author_rank: Newbie
timestamp: January 20, 2020, 03:00:29 pm
content: Quote from: Sighound36 on January 20, 2020, 11:48:02 amThank you.Did you set attenuation to 10x in the CH menu when you press CH button? Voltage Reading in my mso5000 shows a correct value in all situations and conditions, but the reading is not correct only in Search>threshold.Please let me know an CH attenuation setup and test procedure of your result.I'm using 10x prove PVP2350 which is a default accessory.Picture1. PVP2350 10x settingPicture2. CH1 10x settingPicture3. Test waveform (yellow, CH1)cursor(which shows 2.22V, correct voltage reading)measurement (Vmax1, shows 3V, correct voltage reading)Search>threshold(yellow dot line, which shows 234mV misreading)

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 20, 2020, 05:02:34 pm
content: SinepieHave you tried a different robe?Due to both scopes being fully opened we use the 500Mhz Rigol version which is 10:1 only and 13pfhttps://www.rigol-uk.co.uk/Rigol-RP3500A-500MHz-Passive-Oscilloscope-Probe-p/rp3500a.htmWill have a look for you

author: tautech
author_rank: Super Contributor
timestamp: January 20, 2020, 06:04:05 pm
content: Quote from: sinpie on January 20, 2020, 03:00:29 pmQuestionWith more waveform cycles on the display are the measurements then correct ?

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 20, 2020, 06:16:17 pm
content: SinpieI have just the 7000 model, I have the same result as yourself, with the 10:1 probe the threshold reads just 10% of displayed value on a 10:1 probe. On a 1:1 probe the threshold is identical to the displayed probe value.

author: sinpie
author_rank: Newbie
timestamp: January 20, 2020, 11:52:28 pm
content: Quote from: tautech on January 20, 2020, 06:04:05 pmThis is not a measurement issue. Measurement is correct. But when I go to a certain menu (which is search>threshold setting), setting voltage shows wrong value which shows a 'before' attenuation voltage.

author: sinpie
author_rank: Newbie
timestamp: January 20, 2020, 11:58:14 pm
content: Quote from: Sighound36 on January 20, 2020, 06:16:17 pmThank you for help meSince I don't have a 500Mhz probe, I could not able to test it.

author: gaelellon
author_rank: Newbie
timestamp: January 21, 2020, 01:55:03 pm
content: Hi!My MSO5072 (FW 01.01.04.08 HV 01.01) does not display in hdmi mode 720p.Did anyone else have it?

author: vr2whf
author_rank: Contributor
timestamp: January 24, 2020, 04:14:24 pm
content: What is the noise floor performance? especially compared with Rigol DS2000A, Siglent SDS2000X?

author: neon416
author_rank: Contributor
timestamp: January 24, 2020, 05:00:47 pm
content: It's about strange frequency response in 400-600 MHz range.The analog fronted after BNC in MSO5000 have not populated serial RLC network components in comparsion of MSO7000. May be installation of this components can get more flat responce after 400 MHz? I think LC is tuned on to ~500 MHz but I have not MSO7000 to check them values.

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 24, 2020, 05:40:33 pm
content: The best you will get out of a 5000 opened up is 470Mhz, the 7000 around 830Mhz

author: thm_w
author_rank: Super Contributor
timestamp: January 25, 2020, 12:54:54 am
content: Quote from: Sighound36 on January 24, 2020, 05:40:33 pmThey are saying maybe some HW filtering is the cause. I would be skeptical and suspect MSO7000 is using higher quality PCB or front end components, but in terms of the ASICs it should be possible.Quote from: vr2whf on January 24, 2020, 04:14:24 pmWorse than Siglent (<350uV?), they have very good noise floor.Hopefully once they get hi-res working properly it will improve a bit, but the benefit of the 5000 is very high sample rate.A low noise front end amp would probably be a good addition..

author: Sighound36
author_rank: Frequent Contributor
timestamp: January 27, 2020, 04:05:38 pm
content: We have tried quite a bit to extend the 7000 as far as is possible FW wise although we can obtain the magical 1Ghz model, the best I can see is 830Mhz.You are correct the hardware inside the 7000 is superior, however I feel they (Rigol) have not fully worked to the best way to bring their ASIC into full focus yet!The 8000 they seem to be getting there with extracting the potential on the chip more I feel

author: neon416
author_rank: Contributor
timestamp: February 01, 2020, 03:15:50 pm
content: Quote from: Sighound36 on January 24, 2020, 05:40:33 pmIt sounds like true, but look at this pictureMSO5000 have 500 MHz bandwidth on -3dB, but 900 MHz on -6dB. I think bandwidth as in 7000 may be obtained by simple RLC correction network in frontend which is not soldered on PCB in 5000. Or not))Thank you EEVblog channel!

author: tv84
author_rank: Super Contributor
timestamp: February 01, 2020, 03:38:07 pm
content: Or extend 7000 BW by desoldering?

author: skander36
author_rank: Frequent Contributor
timestamp: March 07, 2020, 08:39:31 am
content: Hi ,Someone observed that in versions 00.01.02.00.02 & 00.01.02.00.03 , when AUTO function is used , it will activate CH 3 even if is not signal on this ? Nothing improve after calibration .This can be avoided in Utility ->More->Autoconfig->Only active ch. but at next boot is back.In 00.01.01.04.08 this is not happened .AUTO function is supposed to save your time but now turning off CH3 an resizing trace to center will not help .

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: March 07, 2020, 01:29:15 pm
content: Yep, exactly same problem with the new firmware. The only workaround is to change the startup to the last state rather than the default.

author: skander36
author_rank: Frequent Contributor
timestamp: March 07, 2020, 01:35:51 pm
content: Quote from: NoisyBoy on March 07, 2020, 01:29:15 pmThank you for the tip !

author: pmaggi
author_rank: Contributor
timestamp: April 05, 2020, 02:04:12 pm
content: One possible bug... when performing fft analysis, if you use Vrms instead of dB, peak search doesn't work, although you adjust the threshold...This happends with FW 00.01.02.00.03

author: pmaggi
author_rank: Contributor
timestamp: April 05, 2020, 03:19:40 pm
content: my mistake, it works perfectly. I forgot to adjust the excursionSorry

author: Back2Volts
author_rank: Unknown
timestamp: April 19, 2020, 02:50:34 pm
content: I was looking for the SIGROK download when I noticed there has been a very recent update to PULSEVIEW, and looking a little back in the blog I noticed that, on the driver library, they have added support for the MSO5000. I wonder what that does. Does any one have any idea about it?

author: el_man
author_rank: Contributor
timestamp: April 21, 2020, 06:58:03 pm
content: Quote from: Back2Volts on April 19, 2020, 02:50:34 pmCould you be more specific. Thanks

author: neon416
author_rank: Contributor
timestamp: April 21, 2020, 07:06:35 pm
content: Quote from: tv84 on February 01, 2020, 03:38:07 pmHow? It's serial RLC net.

author: thm_w
author_rank: Super Contributor
timestamp: April 21, 2020, 09:34:21 pm
content: Quote from: Back2Volts on April 19, 2020, 02:50:34 pmhttps://github.com/sigrokproject/libsigrok/commit/f6129c8f0c92e45de5d70b4101bf2bd759a5fdf7https://github.com/sigrokproject/libsigrok/blob/4c5f70063ad6ae311809ee7818ddc9070fbe05cf/src/hardware/rigol-ds/api.cShould be able to read analog and digital channels, not sure what if any limitations there are for triggering/etc.Try it out and let us know.

author: Phils
author_rank: Newbie
timestamp: May 05, 2020, 03:50:17 pm
content: Hello! Bought Mso5072 firmware was 00.01.02. 00.03, when measuring in signal mode sinus with a voltage of 0.5 volts, the probe x10 after pressing the auto button oscillograph can not synchronize the signal, installed firmware ..... 08 opened all the options, calibrated, the problem is the same. If I switch the probe x1 there are no problems with synchronization. I still have dso4102c there all right... The seller offers to return the oscillograph, can I fix it myself?

author: TK
author_rank: Super Contributor
timestamp: May 05, 2020, 03:58:20 pm
content: Quote from: Phils on May 05, 2020, 03:50:17 pmThe signal is noisy, looks like ground connection is missing. It will trigger on the spikes and you end up seeing an out of sync signal, but the scope is triggering correctly.

author: Phils
author_rank: Newbie
timestamp: May 05, 2020, 04:10:31 pm
content: There is no grounding in the 220 volt socket if I include HFR no problem in the oscillograph no, but there is a buzz as to why dso4102c is fine. Maybe capacitors on the main voltage do not work?

author: thm_w
author_rank: Super Contributor
timestamp: May 05, 2020, 08:47:46 pm
content: Quote from: Phils on May 05, 2020, 04:10:31 pmWhen you have the probe set to 1x the bandwidth is reduced, and maybe these spikes are as well.Measure something else other than the 220V socket. Use the internal function generator, the cal signal, or some other circuit you have. Don't rely on 220V mains voltage to be consistent as a reference.edit: as TK pointed out its gen already, can see scope probe connected to the gen 1 output.

author: TK
author_rank: Super Contributor
timestamp: May 05, 2020, 08:51:14 pm
content: Quote from: thm_w on May 05, 2020, 08:47:46 pmI think the signal source is the internal waveform generator, not the 220V mains. The reference to 220V mains not having ground is probably due to an old installation. If the source is the internal waveform generator, then I would like to know how it was connected to CH1 input.

author: neon416
author_rank: Contributor
timestamp: May 05, 2020, 10:52:51 pm
content: Quote from: Phils on May 05, 2020, 04:10:31 pmTry to connect probe tip to SG output case (ground). If you whatever see this spikes - problem is in EMC, if not - in SG signal.

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: May 06, 2020, 12:05:40 am
content: I'm on 01.03.00.01 and there is a still a bug for the external HDMI. Mine won't output a signal even though the output is switched to on. After the scope has run a few minutes (5 maybe), it will work but only after restarting the scope. When I've tried to get it working too early, I get a distorted HDMI picture that's all red-toned

author: TK
author_rank: Super Contributor
timestamp: May 06, 2020, 01:11:41 am
content: Quote from: neon416 on May 05, 2020, 10:52:51 pm

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: May 06, 2020, 02:21:39 am
content: Quote from: Gandalf_Sr on May 06, 2020, 12:05:40 amI have my monitor attached to the MSO5000, from a cold start, I was able to get a perfect display as soon as I can get to the menu to turn the external display on, no restart involved. You have to consider the possibility of a hardware issue. My hardware is ver 1.00.00I presume it is a HDMI cable straight to the monitor in your case with no switch involved?

author: Phils
author_rank: Newbie
timestamp: May 06, 2020, 04:45:33 am
content: Changed all the entries 1-4. Changed the output of generator 1 and 2, which does not change. Today I'll check at work, there is a grounding in 220v

author: Phils
author_rank: Newbie
timestamp: May 06, 2020, 07:35:23 am
content: Once connected with grounding, the noise is now greater.When you connect the probe to the ground there is a big noise. Send it to the seller?

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: May 06, 2020, 08:48:48 am
content: Quote from: NoisyBoy on May 06, 2020, 02:21:39 amThanks, my hardware is 1.01.00 (I think). I tried 2 different HDMI cables - yes it's just a cable, no switch or anything. The symptom was there with the 'old' monitor that jumped off the shelf after 2 days so it's likely hardware or firmware in the scope. One of the latest updates lists something like "improved HDMI startup" so I had assumed it was a firmware issue.

author: aristarchus
author_rank: Regular Contributor
timestamp: May 06, 2020, 10:00:29 am
content: Is the HDMI monitor connected in prior to oscope before power on?If it is not then it does not hurt to give it a try.

author: TurboTom
author_rank: Super Contributor
timestamp: May 06, 2020, 10:29:15 am
content: @Phils: You are running the scope at a vertical sensitivity of 20mV/div. If you (properly) dialed in a probe scaling factor of 1:10 then the sensitivity at the BNC is 2mV/div. Under these circumstances, some noise is to be expected. Since I haven't got an MSO5000, I cannot tell how much can be considered normal. At these kind of sensitivity settings and the full bandwidth of the scope enabled, even the ground lead of the probe may pick up considerable RF interference. You can try to experiment with the short grounding spring at the proble sleeve - this usually helps a lot at reducing received RF background. Probing techniques can sometimes be awkward.Edit: Typos

author: neon416
author_rank: Contributor
timestamp: May 06, 2020, 10:41:45 am
content: Quote from: Phils on May 06, 2020, 07:35:23 amWait a little)Now try this experiment with probe grounddirectlyconnected to TG BNC case (by steel contact spring from probe packaging), not by alligator wire.Oops. I look not on previous message))) TurboTom wrote right things)

author: neon416
author_rank: Contributor
timestamp: May 06, 2020, 10:54:07 am
content: Quote from: TurboTom on May 06, 2020, 10:29:15 amIt's a problem. I live about 10km from FM/TV broadcast tower. If I simple short probe by connecting alligator to it's tip this "antenna" receive about 0.1V of EMI from that tower)) Only "spring grounding" to DUT make deal.

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: May 06, 2020, 11:06:57 am
content: Quote from: aristarchus on May 06, 2020, 10:00:29 amI tried both connected and not connected, it seems that, when the scope is cold, the HDMI doesn't want to start up. The caption on the screen allows you to turn HDMI on and off but the monitor reports that there is no signal.

author: Phils
author_rank: Newbie
timestamp: May 06, 2020, 05:32:43 pm
content: I sent the seller to replace the oscillograph. With grounding only worse because I was unable to sync with the internal calibration of the 1 kHz square, 2 volts, without grounding synchronized, probably broken EMC. How to get a new review...Thank you all so much

author: TK
author_rank: Super Contributor
timestamp: May 06, 2020, 05:38:49 pm
content: Quote from: Gandalf_Sr on May 06, 2020, 08:48:48 amIt looks like you have a faulty unit. Have you tried contacting Rigol USA?

author: Back2Volts
author_rank: Unknown
timestamp: May 08, 2020, 02:16:51 pm
content: Quote from: el_man on April 21, 2020, 06:58:03 pmhttps://www.sigrok.org/blog/blog...The following hardware is now (additionally) supported:...Oscilloscopes: Agilent DSO1000B series, Hameg HMO3522,Rigol MSO5000 series, R&S HMO1000/RTA4000/RTB2000/RTC1000/RTM3000 series, YiXingDianZi MDSO...

author: Back2Volts
author_rank: Unknown
timestamp: May 10, 2020, 09:14:49 am
content: Quote from: thm_w on April 21, 2020, 09:34:21 pmThe comment in the first link points to some data flow limitations. Talking about trigger limitations, I have not pulled the trigger yet for buying one of these. There are some things that need to fall in place before I do, plus warm weather seasonal activity adjustment may postpone it till fall.

author: stafil
author_rank: Regular Contributor
timestamp: May 12, 2020, 05:44:25 am
content: I am busting my head but can't seem to be able to find the segmented memory feature. All I see is the record option, but it records in intervals and not based on the trigger. What am I missing?Edit: Nevermind, found it, I needed to be in Normal mode.

author: SimonH
author_rank: Contributor
timestamp: May 13, 2020, 09:38:17 am
content: I may be wrong, but I think the MSO5000 doesn't have a real segmented memory feature. After all, they also don't call it like that. Instead of segmenting the sample memory, it just waits for a trigger, samples, stores the samples in "normal/slow" memory, and waits for a trigger again. Still very useful in many cases, but you have a long dead-time after each waveform sample.

author: Ayraidizko
author_rank: Newbie
timestamp: May 17, 2020, 11:20:12 pm
content: So, I'm about to purchase the Rigol 5074 and potentially hack it to 350. I feel that this Oscilloscope still has great value, but it seems to have a lot of issues as well... Is everybody hapy with their MSO? and would you recommend it?

author: Martin72
author_rank: Super Contributor
timestamp: May 17, 2020, 11:27:57 pm
content: I´ve owned the MSO5000 over a year and what I could say about it is, that you can´t get wrong with it, when you couldn´t/wouldn´t spend more money.I know siglent, rigol models under the price of a MSO5074, they couldn´t reach it in any way.Like I was mostly saying, this puppy is a raw diamond.If you could spend 1400 bucks, then go for the siglent sds2k+ like I did.If not, take the 5074, nothing else.And don´t worry about the issues it got - Make your decision, does they affect your work with the scope…

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: May 18, 2020, 01:01:19 am
content: I'm happy with mine. It's hard to get close to it in terms of value for money.

author: ve2mrx
author_rank: Regular Contributor
timestamp: May 18, 2020, 03:05:11 am
content: Hi everyone!After reading almost everything about the Rigol MSO5000 on this forum and comparing the MSO5074 with the Rigol DS1054Z, DS1104Z-S Plus and Siglent SDS1104X-E, I ordered the MSO5074. There's currently a promo with the options bundle for free, probably because they know it's hacked ;-)I don't need 100MHz now, so I won't pay for it until I need it, and when I will need more that 4 channels of serial decoding, I'll buy a separate LA like the DSLogic U3Pro16.Comparing the Rigol MSO5074 and the Siglent SDS1104X-E, I came to the conclusion that the SDS was a bit older, mature, and that the MSO wasn't mature yet but more capable. I hesitated as I wanted a stable scope, but it looks like you enjoy using it. Besides, it will be my first scope in 25 years! I don't think it will be a mistake for hobby work.Also, I ordered a 121GW from Dave :-)Thanks for your information while I lurked here reading your adventures in MSO5000 land.MartinEDIT: I meant to post in this thread:https://www.eevblog.com/forum/blog/new-rigol-scope/

author: Ayraidizko
author_rank: Newbie
timestamp: May 19, 2020, 07:01:22 am
content: Quote from: Martin72 on May 17, 2020, 11:27:57 pmQuote from: Gandalf_Sr on May 18, 2020, 01:01:19 amThank you so much for both your responses! I think I will pull the trigger on it.

author: macaba
author_rank: Regular Contributor
timestamp: May 19, 2020, 10:51:37 am
content: Had my MSO5074 for a week, quite happy. Attached is a small bit of analysis that I've done so far.

author: ve2mrx
author_rank: Regular Contributor
timestamp: May 26, 2020, 02:51:10 pm
content: Hi everyone!I think I found a bug in FW 00.01.03.00.01:Set up for I2C decodingIn Decode > Decode? > Bus Status > ONPress Menu off, Back, some other buttonThe intensity dial only moves the Bus Status, but won't change the intensityCan anyone confirm if it's me or a bug?Thanks,Martin

author: macaba
author_rank: Regular Contributor
timestamp: June 04, 2020, 04:17:57 pm
content: Been using my MSO5074 for a few weeks now. By far the most annoying behavior:Say you're on 100uV/div with a -200uV offset. Rotate the knob to change to 50uV/div and the offset changes to -100uV rather than staying on -200uV!Is there a setting for this?

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: June 04, 2020, 07:54:09 pm
content: If we're using this as a list of annoying aspects of the MSO5000, here's mine.I leave my probe switches at x10. Every time I cycle power, the setting returns to x1, I'd like it to remember the settings until I change them.

author: tcottle
author_rank: Contributor
timestamp: June 04, 2020, 08:12:27 pm
content: Its buried 3 levels downUtility>System>Power On>Last

author: Martin72
author_rank: Super Contributor
timestamp: June 04, 2020, 09:17:46 pm
content: QuoteAnd this is imho a main problem of the UI...

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: June 05, 2020, 12:18:38 am
content: Starting the scope at the previous state is a workaround but has problems of its own. One does not always want to return to the previous state if you are working on more than one project, it creates far more problems than it solves. A better option is to have a set of user configuration that one can store, and a menu to choose the default config to boot the scope with. It shouldn’t be hard to code, but I don’t know if Rigol really care about what it’s customer has to say, so I won’t hold my breath.

author: ve2mrx
author_rank: Regular Contributor
timestamp: June 05, 2020, 01:53:32 am
content: Hi!I, for one, use the settings save and restore function, but if you don't set the channels to x10 (like the probes are set) before you restore, odd stuff happens (IIRC, with the trigger).Also, I think that the restore to last function needs to have a saved settings done before it works as expected.Diamond in the rough, but nice to use still!Martin

author: Fungus
author_rank: Super Contributor
timestamp: June 05, 2020, 07:47:32 am
content: Quote from: NoisyBoy on June 05, 2020, 12:18:38 amPowering it on/off to load a preset in stead of pressing a few buttons?How is that a good idea? Remind me again how long these take to boot...Quote from: Martin72 on June 04, 2020, 09:17:46 pmMaybe it's not used often enough to deserve being at top level.

author: Sighound36
author_rank: Frequent Contributor
timestamp: June 05, 2020, 08:39:03 am
content: You can also 'save' your particular measurement parameters for you experiment as a 'setup' then just load it up when you boot or when you change experiments. Works for me

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: June 05, 2020, 07:22:51 pm
content: Here's another bug (sorry if it's already been raised)...When performing a self-calibration, the pop up dialogue box that has the % complete says "waitting" (too many 't's)

author: Axk
author_rank: Regular Contributor
timestamp: June 05, 2020, 11:00:00 pm
content: Hi everyone!Sorry for a silly question looking at buying such a scope and wonder if it has a plastic smell.If you keep it on the workbench can you feel the smell in the room?(I'm allergic to strong smells so an important consideration for me as silly as it may sound)

author: ve2mrx
author_rank: Regular Contributor
timestamp: June 05, 2020, 11:38:27 pm
content: Hi Axk,It smelled a bit when I unpacked it, but I couldn't smell it after a few days. In doubt, open the package in a well ventilated place outside the house and leave it there for a few hours/days.Every fresh electronics does smell when sealed for a time. But this one is on the low side. Of course, YMMV!Martin

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: June 05, 2020, 11:48:22 pm
content: You missed my point, I never referred to rebooting the scope just to load a different config. Getting back to the original requirement - the ability to select 10X as the default as one boots the scope. My suggestion was to save a config with the 10X option selected, then provide an option to choose it as the default boot config. That way, every time you boot the scope, the probe is set at 10X as the default.Quote from: Fungus on June 05, 2020, 07:47:32 am

author: Axk
author_rank: Regular Contributor
timestamp: June 06, 2020, 12:42:40 am
content: ve2mrx, I'm asking because I've a 1054z and it has this rather strong smell, the gray plastic of the probes and the scope. Fills the room even hands smell for some time after holding the probes. And it's been 4 years (I keep it in an airtight box most of the time to keep the smell away).

author: ve2mrx
author_rank: Regular Contributor
timestamp: June 06, 2020, 01:23:34 am
content: Hi Axk,You are probably making things worse by sealing it up between uses. The gasses need to get out of the material for the smell to go away.It is pretty much like trying to dry out a towel by sealing it up in a plastic bag: it never dries, and the moisture end up interacting with the content making things worse like altering the materials.I think further discussions about outgassing and smell should be in another thread so we don't hijack this one. Post the link back in the MSO5000 thread list and here.Martin

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: June 06, 2020, 10:25:38 am
content: I don't have a very sensitive sense of smell but my MSO5074 doesn't smell at all IMHO.

author: macaba
author_rank: Regular Contributor
timestamp: June 07, 2020, 12:21:29 pm
content: I got curious about the analog gains in the front end. Using the SCPI interface, I was able to get the raw ADC counts. I then swept the channel 1 vertical offset to establish Vmin and Vmax for each of the vertical gains being tested.Code:500uV. ADC 0 = -7.3mV, ADC 255 = +7.65mV (Screen: -2mV to +2mV)1mV. ADC 0 = -14.6mV, ADC 255 = +15mV (Screen: -4mV to +4mV)2mV. ADC 0 = -14.6mV, ADC 255 = +15mV (Screen: -8mV to +8mV)5mV. ADC 0 = -25.6mV, ADC 255 = +26.2mV (Screen: -20mV to +20mV)10mV. ADC 0 = -51.2mV, ADC 255 = +52.8mV (Screen: -40mV to +40mV)20mV. ADC 0 = -101mV, ADC 255 = +104mV (Screen: -80mV to +80mV)50mV. ADC 0 = -254mV, ADC 255 = +258mV (Screen: -200mV to +200mV)100mV. ADC 0 = -500mV, ADC 255 = +512mV (Screen: -400mV to +400mV)200mV. ADC 0 = -1.01V, ADC 255 = +1.03V (Screen: -0.8V to +0.8V)500mV. ADC 0 = -2.56V, ADC 255 = +2.64V (Screen: -2V to +2V)It seems the 500uV isn't a 'lie' as it is the final analog gain step (but 1mV is a lie). Probably should have been: 5mV, 2.5mV, 1mV (with no 500uV range).Might also make more sense if the top and bottom UI moved to the left/right, and we got 4.5 divisions up and 4.5 divisions down.Edit: What's not so good; SCPI interface slows the UI down, and it's just crashed the UI.

author: AlexS
author_rank: Contributor
timestamp: June 15, 2020, 07:58:38 pm
content: Hey guys! Maybe somebody has resolved a bug and can share with the experience.Different levels of the same signal from trigger. And measure results between input and output signal looks much more horrible

author: Martin72
author_rank: Super Contributor
timestamp: June 15, 2020, 08:17:22 pm
content: On the first pic, the different measure seems plausible to me, as the negative halfwave are slightly more and under the divison grid, as the positive one.

author: tautech
author_rank: Super Contributor
timestamp: June 15, 2020, 09:17:19 pm
content: Quote from: Martin72 on June 15, 2020, 08:17:22 pmExactly, it's a probe compensation output FFS not some precision square wave supply.There also could be some minor channel 0V offset indicating the scope needs Self Cal run.

author: AlexS
author_rank: Contributor
timestamp: June 15, 2020, 11:11:54 pm
content: It was self calibrated and compensation was installed. The only one that I can imagine - I hacked it and did not used previous backup. Does it make sense?! What do you think guys?

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: June 15, 2020, 11:36:40 pm
content: Did you run a self calibration?

author: AlexS
author_rank: Contributor
timestamp: June 16, 2020, 07:35:58 am
content: Sure! I’ve used self calibration and has removed previous. And the problem you know... When I’m measuring amplified signal is about 6-7 times sine wave loosing symmetricality.

author: AlexS
author_rank: Contributor
timestamp: June 16, 2020, 07:38:33 am
content: That’s very strange. DS1054z showing normal data - everything perfect. Higher model MSO showing incorrect. Paradox. Ahah

author: TK
author_rank: Super Contributor
timestamp: June 16, 2020, 12:27:32 pm
content: Maybe it is the opposite. You need a third scope to compare

author: ve2mrx
author_rank: Regular Contributor
timestamp: June 16, 2020, 01:42:59 pm
content: IIRC, the calibration verification guide mentioned to re-run self-calibration if out of spec...I recommend doing it away from any potential electrical interference... You know, like in the middle of electrical nowhere ;-) For me, it's the kitchen table with lights and electronics off while the fridge compressor is not running!I wonder if those "option" channel caps would help?

author: AlexS
author_rank: Contributor
timestamp: June 18, 2020, 07:43:46 pm
content: Kitchen table sounds greatAhahaI've sent a message to Rigol. Will waiting for a reply. Keep you posted, guys.

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: June 18, 2020, 09:27:05 pm
content: I discovered MSO5000 is indeed susceptible to electrical noise and RF interference, you can look up our discussion on phantom channels if you want to read more. In my case, my WiFi was creating enough noise to turn random channels on when I pressed the Auto button. I think this is due to inadequate shielding on the front end, as the shield has an opening to expose the heat sink when compared to the 7000, so definitely move the scope to a spot far from any electrical or RF noise while you do your calibration as it can really mess the calibration up.You should also take noise into consideration when you do your final placement in your lab.

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 01:23:55 am
content: Quote from: NoisyBoy on June 18, 2020, 09:27:05 pmThanks for the 'heads-up' on thisI still have not fully deployed my new 5074, but when I do - I will do some specific testing.Having a SSA (now SVA) and multiple 'controlled' RF generators - I should be able to see what level of RF and perhaps what Freq the MSO5000 is sensitive

author: Sighound36
author_rank: Frequent Contributor
timestamp: June 19, 2020, 04:47:13 am
content: I know a few chaps have suffered from this with the 5000, we have not at all on any of 5/7 and 8000 Rigol models.While you firing your rf pulses around noreply and checking for various anomalies do hook up your 5000 to SA directly from say port one and set for a general 7.5Ghz sweep and have a look for anything interesting?

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 08:20:43 am
content: Quote from: Sighound36 on June 19, 2020, 04:47:13 amI wish (he says with envy) - not all of us are as fortunate to enter the 7.5Ghz club

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 08:48:35 am
content: Quote from: Sighound36 on June 19, 2020, 04:47:13 amInteresting you say this ...I had been watching (several times) various teardowns on 5000 and 7000- as the 5000 was released after the 7000, Rigol appears to have made some mods in general shielding and power distribution- at least different to the 7000- better in MHO ...That said, I'm thinking that the RF susceptibility could be software related ??How could that be, you might ask?Well one thing that comes to mind- if I configure the front-end ASIC to 'listen' on FULL BW its capable- sure I'm going to 'open the door' for some unwanted RF to enterTo mitigate this (an example), one would limit the front end ASIC to only listen for the MSO's defined BW.Maybe this is already implemented- just thinking aloud here- as to why some of the 5000's could have this problem with stray RF fieldsAnother potential problem is ‘poor’ power supply filtering.Under static (non RF field testing) the PSU can pass with flying colours.However if ‘stray RF’ (even low level pulse) enters its ‘control loop / regulation’ subsystem– this will manifest in all sort of potential problems with the signal processing of the MSO.One quick fix (very easy and low cost)- is to put the ‘supply’ cable which plugs-into the main board through a large Ferrite Core for Power Supply Decoupling (see attached picture)– doing this can only improve and protect from any future problems.Anyway, it will be interesting to see if the general susceptibility of the 5000 to RF is related to early batch or FW revisions.I wonder if they ‘changed’ the revision on the PSU from the early release HW to current release??OR– the overall HW revision designation– also covers the PSU changes??

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 08:56:26 am
content: Quote from: Sighound36 on June 19, 2020, 04:47:13 amoops ... sorry forgot to attach the picture

author: tautech
author_rank: Super Contributor
timestamp: June 19, 2020, 08:58:05 am
content: Quote from: noreply on June 19, 2020, 08:20:43 amBut 3.2 GHz is possible.

author: Sighound36
author_rank: Frequent Contributor
timestamp: June 19, 2020, 12:37:14 pm
content: Hi noreplyNone of our units have this problem that's been reported I have found another potential issue, just curious of you can replicated on your 5000.You can rule out power supply noise coupling and pretty much all of the conducted emissions I have taken care of that on my personal models. I rebuilt them to a standard I am now happy with.I also use a interesting mains filtration device that helps no end with a lot of unwanted UK rubbish (but not all)Having been all over the 5/7/8000 scopes with rf probes, rf current probes and LISN's I would be interested in anything you may find, the shielding on the 8000 is particularly good with rf fingers absolutely everywhere. Though not surprising as the FFT function goes way beyond 3.7Ghz.One of the points you listed may be pertinent possible ADC noise, nearly finished out internal reworking of many of the localized power supplies and decoupling on the 8000 board.Sorry I wasn't being funny 7.5Ghz is my lowest normal SA. Even with 3.2Ghz you may find some something worth looking at.Many thanksSighound

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 02:05:51 pm
content: Quote from: Sighound36 on June 19, 2020, 12:37:14 pmSure, no worries - this was MY tong-in-cheek remarktv warned me about you and the insatiable quest for high end (not label - but performance) kit - it can be addictive and danger to my walletIf you use your 'kit' to make a living - that's great - best of both worlds - love what you do and get paid for doing itUnfortunately at this moment in time - my 'kit' is more hobby / quest for knowledge than paying the billsBut yeah .. I hear what you sayI've got some housekeeping to do before deploying the 5000, like get all of my attenuators working (building a 30dB 250W attenuator for high level RF stuff), connectors, probes, PSU's , etc,etc - all in a nice and ergonomic workstation style bench / desk.I also have got the Rigol PLA2216 Active Logic Probe kit - so am eager to do some digital testing with the 5000To get me going my Rigol distributor was kind enough to provide me with the DS6000-DK Demo Board (attached picture) for extended loan.Not sure if other forum members have ever used this device - it’s got an Cyclone III as the core - so don't know what exactly Rigol configured here (other than the obvious) - or whether there is a way to control the FPGA directly - so we could have ‘full’ control with this demo HWFor about GBP200 – for use as ‘demo board’ to generate test signals – it’s a ‘rip-off’BUTIf we can program the FPGA and create our own test vectors – this then becomes a valuable tool for the GBP200Any input on the is welcome ..Anyway, I look forward in getting ALL my kit 'up and running' - so I can then start to do the really interesting stuff

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 03:03:02 pm
content: BTW Sighound ...Have you seen this bit of 'kit' - SM200C — 20 GHz Real-time Spectrum Analyser with 10GbEIt can tune from 100 kHz to 20 GHzANDIt can sweep at1 THz/secat30 kHz RBWIt just scraped under uncle sam's ATF regulations - so we can buy it... PLEASE don't tell me you got one already(I'm Joking, I really AM - after all its made by a company, Signalhound, not very far removed from your eevblog 'tag' Sighound - only difference is 'na' - short for no, I don't have one- so I hope you can forgive me for posting this with a double tong-in-cheek)But if I win 'lotto' and after I help my fellow human beings less fortunate AND still have some $$ left over - this WILL be on my bench for sure

author: Sighound36
author_rank: Frequent Contributor
timestamp: June 19, 2020, 05:02:49 pm
content: Hi noreplyThe Sighound unit looks interesting but its stops at 20Ghz its only downside unless you are using down-mixers of frequency extenders. Seriously a worth a look productThere has been a version of this before I believe, still again quite an achievementTo be honest its not all about £$£ it is finding that piece of equipment that works for you personally, in the way that you work with it, and will help you in your work or quest for learning. As we really do not stop learning and EEV blog and forum are great placed to help understand those areas we are not good at.Plus the vast majority of participants on here are genuinely happy to help unlike other hobby/interest forums.My knowledge is ok in a few areasand its nice to see so many genuinely intelligent and articulate people sharing their thoughts and ideas with the general population.Mind you Tautech can be a pain in the arse occasionally but aside the fact he tries to flog sand to Southend on Sea council for beach reclamation, his hearts in the right place and his Siglent knowledge is well used on this forum.Coding and myself are like Trump and common sense they don't mix, so I find the coding, FPGA and associated hardware of great interest.Anyhow happy to help were I can

author: tv84
author_rank: Super Contributor
timestamp: June 19, 2020, 05:44:00 pm
content: Quote from: noreply on June 19, 2020, 03:03:02 pmDon't forget you also need a "decent" PC...

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 06:22:41 pm
content: Quote from: Sighound36 on June 19, 2020, 05:02:49 pmYes .. you are 100% about the people here ..I like thepay-it-forwardapproach, if you join a group of knowledgeable people -bring something to the 'table' before you start taking food from it which is not yours- where 'food' = 'knowledge'This philosophy will always work with the people you respect - simply by default – because they are the knowledgeable individuals with whom you want to engage and share in the first placeSo here is something useful (at least for myself) which I found and happy as always to share with others here …Yes I’m happy to check out the Rigol DS6000-DK Demo Board, but like I said , if it does not have some hidden capability - via the FPGS - that we can use for ‘other’ stuff, then its not a keeper for meMy alternative (I’ve already hedged myself with this device) – is a cheap < GBP 10 device – a STM32F103 Nucleo-64 (see attached image) which is easy to program to use as BOTH an analogue and digital test bed for generating some test signals for use as ‘inputs’ for various devices under test that we may have.There is LOTS of user guides for this type of device and easy to ‘break into’ the programming / coding space.Second, useful device I have acquired are BNC Male to SMA plugs (see attached image) – the idea here is to use the AWG(s) of the MSO to directly drive my stuff – which usually has SMA connectors.I’m slowly realizing that the cost of this– what I call ‘glue’ bits and pieces– slowly adds-up to more that the device you will be using the items withWith the SVA, I’ve spend at least GBP500 on all sorts of connectors, attenuators, amplifiers, etc, etc, just to have a flexible instrument which I can use with many different DUT(s) that I intend to connect in the future.I’m sure you know this aready - as so should others on this thread

author: Sighound36
author_rank: Frequent Contributor
timestamp: June 19, 2020, 09:15:33 pm
content: I feel you have the nail on the head there no replyBuying the scope/sa/vna/impedance analyser/TDR device power analyser etc is just the start, the test fixtures, cabling adapters, couplets, lists, attenutators, probes etcThe costs can be almost as much as the hardware and new players (got to love Dave) are not aware of what is required even for basic power measurements or rf probing etcNow some items I have fabricated rf amplifiers breakout boxes etc.However certain items we just have to have to enable us to achieve the desired results and you can not scrimp on them especially with ultra quiet power supplies the probes are silly money for what the really are.Maybe worth while putting together a list of basic essential accessories for say scopes, sa and vna's and a price and performance level that will support hobbyists parametersOur next purchase is likely to be a higher bandwidth dedicated VNA or a TDR device though that will be after the MXR if it passes muster

author: noreply
author_rank: Frequent Contributor
timestamp: June 19, 2020, 10:50:39 pm
content: Quote from: Sighound36 on June 19, 2020, 09:15:33 pmSounds like you have a well-equipped ship (lab)- and I'm sure you are a first rate captain (engineer) to navigate troubled watersWith all the firepower of your 'ship' you must have some interesting waters into which you enterThis link istotally of topic- but something I found very interesting (I think you will also)- so wanted to share in the general chat section ...https://www.eevblog.com/forum/chat/nixi-tube-vs-led-latency/Sooner or later I will attempt to do the 'experiment' with LED's- I should have sufficient firepower on my ship to get me some answers

author: Lysanthe
author_rank: Newbie
timestamp: July 03, 2020, 03:27:30 pm
content: Hello,just got my MS5074 today, hacked in less than 1min (kudos to you guys here).Tried the awg.Sine wave is all ok.With Square wave I am getting some serious overshooting (hope I picked the right term).Made some screenshots for 100kHZ, 1MHz and 15MHz (doesn't look like square wave by any mean).Is this behavior intended that way?RegardsMartin

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: July 03, 2020, 08:39:34 pm
content: Do you have the ground connection made? Such ringing on the analog inputs of a scope is often because there' isn't a good ground. Try a walking stick ground connector on the scope probe.

author: ve2mrx
author_rank: Regular Contributor
timestamp: July 04, 2020, 03:20:43 am
content: Hi Lysanthe,Just checking, the probes are in x10 and are calibrated, right? :-)Martin

author: Lysanthe
author_rank: Newbie
timestamp: July 04, 2020, 06:14:25 am
content: Yes and in made the messaurements with 1x Probe since the should Work Till 30MHz

author: Fungus
author_rank: Super Contributor
timestamp: July 04, 2020, 10:15:56 am
content: Quote from: Lysanthe on July 04, 2020, 06:14:25 amYes, but square waves are made out of sine waves. What's the frequency of thehighestsine wave in your signal? Is it more than 30MHz?https://en.wikipedia.org/wiki/Square_wave#Fourier_analysis

author: noreply
author_rank: Frequent Contributor
timestamp: July 05, 2020, 05:40:36 pm
content: Finally did some testing on the MSO5074 -> now a 5350A precursor to my full review - coming soonFrequency BW testThere have been various comments regarding the -3dB bandwidth limit for the MSO5000 - some forum members have stated that you can 'stretch it' to as high as 480MhzWell , I decided to make an accurate test with my deviceSignal source was via a calibrated RF Sig Gen using a directly connected low loss 6GHz capable cable with inline 50 Ohm termination on the Rigol Channel 1 input.The Rigol MSO5000 was set to 'full BW'The Initial frequency and amplitude was set to be precisely 100Mhz at 1.00VppThen I swept the frequency until I reached 707mVpp - giving me the -3dB pointThe frequency where the -3dB point was reached was 415MHzThis figure is well below the 'claimed' 450+ MHz by others, but at least its a trusted figure for my device.One important caveat for the above measurements and result ...The testing was made with direct (in effect lossless at this frequency) cable connection.If you are going to use your supplied PVP2350 probes - your mileage might vary - since the probes are rated at 350MhzHope the above information is usefulScreen Cap 1The initial input signal frequency and levelScreen Cap 2The -3dB signal frequency point

author: Lysanthe
author_rank: Newbie
timestamp: July 06, 2020, 08:20:15 am
content: Quote from: Gandalf_Sr on July 03, 2020, 08:39:34 pmFor some reasons I thought that the grounds are internally connected and therefore it doesn't matter whether it's connected or not.Boy, was I wrong;) Though the are of course internally connected, I had to connect GND to get a way better signal.Still some overshooting, but not as bad as previously posted.Thx for your support!

author: neon416
author_rank: Contributor
timestamp: July 11, 2020, 03:30:23 pm
content: I try my MSO5074 "upgraded" scope on direct cable (without probe).-3dB bandwidth is 630 MHz.-6dB bandwidth is 700 MHz.

author: sb42
author_rank: Contributor
timestamp: July 11, 2020, 08:19:36 pm
content: Quote from: neon416 on July 11, 2020, 03:30:23 pmInteresting. Do you mean hardware modifications? And are you going to post an updated frequency-response graph?

author: neon416
author_rank: Contributor
timestamp: July 11, 2020, 08:48:54 pm
content: Quote from: sb42 on July 11, 2020, 08:19:36 pmI did not make any hardware modifications. May be slightly later)P.S. Used cable has 50 Ohm impedance and terminated close to oscilloscope BNC. Signal source alsо have 50 Ohm output impedance. Maybe this is important?

author: noreply
author_rank: Frequent Contributor
timestamp: July 11, 2020, 11:26:25 pm
content: Interesting resultsMade me revisit - to see if there is some consistency with these results and what I measured beforeHere is what I observed as some major differences, and before any judgement can be made - as I really don't know what the proper convention is and if these observations have any relevance, can someone with experience in -3db BW measurements PLEASE chime-inMy original measurements were at 1Vrms at 100MHz as the 'base' before testing for the -3dB pointRepeating the same type of measurement asneon416- notable difference was using CH4 (just in case there is some HW differences between CH1) and HIGHER base frequency as well as LOWER input voltageThe 2nd round measurements I obtained were much betterUsing CH4, 300MHz at 1Vrms, the -3dB point was reached at 498MHz - a significant improvement from the 415MHz when using 100MHz as base frequency.SeeMSO5074 now 5354 with 300MHz 1Vrms input on CH4.pngandMSO5074 now 5354 with 598MHz 708mVrms -3db point on CH4.pngAlso using a smaller input voltage300MHz at 100 mVrms , the -3dB point was reached at 605MHz - again an improvementseeMSO5074 now 5354 with 300MHz 100mVrms input on CH4.pngandMSO5074 now 5354 with 605MHz 71mVrms -3db point on CH4.pngSo what does all this mean?1. If we use a higher 'base' frequency to do the -3dB test - we get better results2. If we use a lower input voltage for the -3dB test - we get better resultsCan someone please chime-in to explain the above observations, and perhaps define - if there is a detention - as to how to perform the -3dB bandwidth test - so that we can get some meaningful results that can be used as a good comparison to other scope measurements.Thanks toneon416for your input, at least we can now try to figure out the observations.I also tried to reproduce similar input levels asneon416and obtained similar resultsseeMSO5074 now 5354 with 300MHz 167mVrms input on CH4.pngMSO5074 now 5354 with 611MHz 118mVrms -3db point on CH4.png

author: neon416
author_rank: Contributor
timestamp: July 12, 2020, 12:34:48 am
content: Quote from: noreply on July 11, 2020, 11:26:25 pmWhat type of signal generator you are use? I discouraged about some jitter or visual "aliases" on you pictures. Is it caused by signal quality or scope specific?On over hand, rise time measurement of scope gives about 700ps. This provide 0.35/0.7 = 500 MHz bandwidth using common formula. I think it's more correct result.

author: noreply
author_rank: Frequent Contributor
timestamp: July 12, 2020, 01:12:00 am
content: Quote from: neon416 on July 12, 2020, 12:34:48 amRigol DSG815I did not tune trigger - I am happy with the signal - my cable is not brilliant - but should handle the Freq (will check)But despite the above - the -3dB readings still should be okYes the 'rise time' measurement is a good confirmation - BUT, it still would be nice to fully understand why the -3dB points vary so much depending of base frequency (your refrence point Frequency) and to a smaller extend - the input voltage level

author: neon416
author_rank: Contributor
timestamp: July 12, 2020, 05:50:06 am
content: Quote from: noreply on July 12, 2020, 01:12:00 amNothing strange)Wavelength of you signal is comparable with cable length when you looking for hundred of megahertz. So this cable can significantly disturb frequency (and pulse) response if not fully terminated. But this oscilloscope have not dedicated 50 Ohm input mode so if you also terminate you cable near oscilloscope input by yourself you get not properly termination because of oscilloscope input capacitance (I measure it about 17pF).You can also commit this by changing cable length or terminator resistance selection)At second, this oscilloscope frontend gain may vary depending of gain range if far from characterized by factory (350 MHz) frequency. It's looks ugly, but every thing has its price))

author: Verticon
author_rank: Contributor
timestamp: July 12, 2020, 09:49:42 am
content: Some quick results from my MSO5074 which I upgraded to a 5354. The measurements were made either with direct cable connection (1m of RG400) from the generator to the 50Ohms adaptor plugged on the scope or with measuring the signal with a detector after a power splitter just before the 50Ohms adaptor. The -3dB results vary primarily with the y-range settings of the Rigol and lie between 410 to 610MHz. Tendency wise the higher range settings seem to result in higher bandwiths.

author: Sighound36
author_rank: Frequent Contributor
timestamp: July 12, 2020, 07:37:16 pm
content: Both of the units we have exceed 460Mhz when using a 200Mhz sine wave at 2V pk<>pk the -3db is 1.41v at 460Mhz on one and 469Mhz on the other one, after calibration. Also using a Bodnar 40ps referencen is 755ps average 780ps peak

author: seronday
author_rank: Regular Contributor
timestamp: July 12, 2020, 08:26:46 pm
content: Quote from: noreply on July 11, 2020, 11:26:25 pmWhen doing frequency response ( bandwidth ) tests, the frequency of the amplitude reference level needs to be in the flat part of the response before the roll off starts.The frequency for the amplitude reference level is usually chosen to be in the range of 100Khz to 10Mhz.In the performance verification guide for the MSO5000 series, Rigol specify using 1Mhz as the reference frequency for the "Bandwidth Test".Regards.

author: noreply
author_rank: Frequent Contributor
timestamp: July 12, 2020, 09:28:04 pm
content: Quote from: seronday on July 12, 2020, 08:26:46 pmGreat !That's exactly what's required - will do some tests with the verification guide guidelines soon.seronday- Thank You

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 13, 2020, 01:55:45 am
content: Hello All. I am a lifetime user of (mostly Tek) scopes (going back to the 70's). I need a home scope so I did my research (many thanks to Dave!) and I just received my MSO5074. It has many nice features, but a couple of problems cropped up right away:1) Channel 2 seems to be the only one that gets 8GSa (If I am to believe the display at the top), while channel 1 gets 2GSa; the other two channels get 4GSa. This is for one active channel. Is this bug about the displayed sample size, or is it a "real" bug?2) Channel 2 has a gain error - its about 25mV lower then the other channels. I have re-calibrated it several times to no avail.Has anyone else seen these things? I may have to send it back (ugh!)Respectfully,Tony

author: neon416
author_rank: Contributor
timestamp: July 13, 2020, 12:57:57 pm
content: Quote from: Pulsepowerguy on July 13, 2020, 01:55:45 amI gets the same strange behavior after updating from 01.01.04.08 to 00.01.03.00.01.The only CH1 gets 8GSa. CH4 or CH1+CH4 gets 4GSa. All over combination gets only 3GSa.UPD: SORRY for Rigol))) It's my mistake. Samplerate segmentation is also based on sync input selection. I.e. if you select synchronisation from any channel this channel become active even if disabled in channel mode menu.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 15, 2020, 12:32:42 am
content: neon416: I did not quite understand your message, but now I know what you meant. The triggered channel always gets the highest sample rate. Thanks! The manual does not make that clear at all.Now, onto number 2):The self-calibration process for this scope seems to be hit or miss. I have run it many times and channel 2 always is always off the most. I used GEN I to generate a square wave of 5Vp-p. I have tried using a BNC coax directly to each channel but have also used the probes at 1x to gate a live comparison of all at once. Attached are the results. Does anyone else get these results?

author: noreply
author_rank: Frequent Contributor
timestamp: July 15, 2020, 03:38:01 pm
content: You most likely heard the saying ‘you get what you pay for’ right?Well it sure applies well to ‘test equipment’ accessories.I recently purchased a Rigol MSO5074 (full review in progress) and was kindly ‘loaned’ a Rigol ADP0150BNC – an inline 50 ohm Termination from DC to 1GHz – from Telonic (my go to UK Rigol Distributor)I also had a ‘Amazon’ P57 device – also claiming to be an inline ‘load resistor 50 ohm’ with bandwidth from DC to 1GHzI took some photos of BOTH devices (see below)Here are some notable differences;-RigolThe male BNC connection is machined on a lathe – you can see the fine one piece construction.Quality of ‘gold’ connection pin and socket is very good – the socket has 4 stress release slots.Perfect fit onto the factory Rigol probesThe unit comes with protective ‘condoms’ for both endsResistance measurement is precisely 50.0 ohms (at room temp at my bench)Amazon P57The male BNC connection is ‘cast’ – you can see the ‘seem’ in the middle.The tolerance is poor (compared to the Rigol)The Female BNC is covered with plastic molding – easier to grip and push-on and clamp as well as remove.The metal BNC inside is also cast – not machined.The quality of the pin and socket are not as good as the Rigol – the ‘gold’ socket 3 stress slots.Resistance measurement is 49.8 ohms (same room temp measurement conditions and meter as Rigol test above)Unfortunately I was unable to do accurate bandwidth tests with the SVA at this moment in time – as awaiting BNC to SMA connectors (see photo - arriving soon)I will post the Bandwidth Response for each of the respective inline 50 ohm terminators as soon as possible.Conclusion(so far - pending BW testing)You certainly get what you pay for.If you have already spend $1000 on the scope and probes – don’t try to save a few $$ on cheap 50 ohm terminators.The Rigol ADP0150BNC is a perfect fit for anyone requiring precision connector with a 50 ohm impedance.Thank You Telonic for the review sample (I will be purchasing this)EDIT: I noticed that some images which were posted with the original 'post' - have disappeared - perhaps a moderator can alert DAVE or whoever looks after server - to check the software / database - I believe this has been happening to other members with various attachments - not just photos

author: noreply
author_rank: Frequent Contributor
timestamp: July 15, 2020, 04:04:20 pm
content: the missing photos from above post

author: noreply
author_rank: Frequent Contributor
timestamp: July 16, 2020, 02:34:05 am
content: Just been playing around with ‘single’ capture mode with the MSO 5350I wanted to see how sensitive the input stage is to RF pulses.I formed a loop with the ‘earth’ wire on the PVP2350 probe – a poor man’s inductive loop (see photo)Then set-up the MSO CH1 to a 5mv per div Voltage and 5ms per div FrequencyMoved trigger level slightly above the reference of CH1 (see photo)Then set ‘single’ captureNow I placed the Car Key Fob on top of the earth-loop on probe – and momentarily pressed a Key Fob buttonVoilà– the MSO captured my Key Fob data (see photo)This is great !I then looked at the data structure – a preamble, 3 data and 1 stop pulseI am not an expert on the data structure that most manufacturers use for the Car Key Fobs- but I guess it’s some form of Manchester encoding?Despite the ‘poor-mans-inductive-loop’ capture mechanism– the captured data is good enough to decode. (see photos)If anyone is interested to repeat this experiment– then make a better ‘loop’ to capture the stray RF from the Key Fob.You can then use the MSO’s serial decoding– to look at the data transmitted– not sure if Manchester decoding is supported by Rigol or Siglent?I know some Keysight MSO do definitely support this.So there you are– your MSO is a very handy tool– you just need to learn how to apply it to various things lying around that you would like to measure– like Car Key Fob’s in my exampleBTW – it’s possible to store this waveform– and then use this data– to perform a ‘replay’– using the either of the built-in AWG channels.Simply connect a small antenna wire (preferably at ¼ wave of the transmitted freq) to the 50 ohm terminated BNC output of the AWG channel you used– and ‘play’ the waveform– your car– if in range should open its doors.(EDIT: Oops .. probably not if it uses rolling code ...)Any further improvements / refinements and experimentation with the above is most welcome!Please report your findings here.

author: dustooff
author_rank: Contributor
timestamp: July 16, 2020, 05:19:35 am
content: Pulsepowerguy, some shots from my unit, 1 month out of the box. Haven't done any cal yet, just adj probe comp so far.The thing that I'm trying to resolve, is why do my traces have the fuzzies, source for these shots was the probe comp output.

author: neon416
author_rank: Contributor
timestamp: July 16, 2020, 09:59:49 am
content: Quote from: Pulsepowerguy on July 15, 2020, 12:32:42 amI repeat you measurements and get Vtops:1. 2.4792. 2.4963. 2.5084. 2.487The worst case difference is about 0.4%. I think its not bad result for this equipment class.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 16, 2020, 11:41:24 am
content: Quote from: dustooff on July 16, 2020, 05:19:35 amDustooff: Those look quite good, but how about at 2uS/div? I used the built-in signal generator for my shots. As to the fuzzies, did you use averaging?Quote from: neon416 on July 16, 2020, 09:59:49 amneon416: your measuremnts look great, but what time base did you use?I am finding that the settling time varies greatly from channel to channel. Ch1 is very fast while ch2 is slowest. The Tech Manager at Rigol North America has offered to send a replacement unit.Crossing my fingers.

author: neon416
author_rank: Contributor
timestamp: July 16, 2020, 12:26:13 pm
content: Quote from: Pulsepowerguy on July 16, 2020, 11:41:24 amAll measurements made in same conditions as yours) On the same signal and oscilloscope settings. Without averaging.Impulse response of channels looks slightly different in part of oscillations. But amplitude of that still stay within ~1%.But rise time of channels looks very close.

author: noreply
author_rank: Frequent Contributor
timestamp: July 16, 2020, 05:18:51 pm
content: Quote from: noreply on July 15, 2020, 03:38:01 pmOK - I have received appropriate connectors for the SVA - so can perform some BW test now.Guess what??Looks like there is not much difference between the Rigol and the P57Obviously from a mechanical point of view - the Rigol is miles ahead - worthy of the extra $$BUTFrom a BW point of view - they are pretty much identical - at least to 1GHzSo perhaps - there is more to inline 50 ohm probe terminators- at least at the sub 1GHz frequencies- quality of mechanical construction and exact value of the termination resistance (at least within 0.5 of an ohm) does not seem to make much difference with regard to the BW capabilities of the device- they both seem to have the same (approximately -3.6dB) attenuation @ 250 MHZ and (approximately -4.4dB) @ 500MHzPlease see the attached response plots belowInteresting finding for sureBONUS FINDING:In the process of doing the SVA screen captures - there is a 'bug' in the annotation software.You can clearly see the 'plot' colors (yellow and purple)However - the Annotation colors - I chose yellow and purple for these - to be identical - the purple annotation color AFTER SCREEN CAPTURE - turns into bright green colorPerhaps someone with similar SVA and latest FW - can verify if getting same result?If so - hope Siglent makes note to 'fix' in next FW revision

author: noreply
author_rank: Frequent Contributor
timestamp: July 16, 2020, 06:24:38 pm
content: Once again - problem with attachmentsHere are the missing screenshots

author: Sighound36
author_rank: Frequent Contributor
timestamp: July 16, 2020, 08:18:11 pm
content: Hello no replyYou have been a very busy boy in the 6 weeks since joining with all these trails and investigations on Rigol and Siglent equipment, honestly do not know where you find the time to perform all of these tests and correlate the results with work and home lifeImpressive throughput of small investigations, envious of the amount of time you have for these tasksgreat work ethicOne would seriously feel you would looking to take on Dave's mantle in the Europe possible even a UK pundit can you tell what next on the review agenda also what other projects you are currently working on to the wee small hours.With your ability to acquire respectable equipment almost at will I wonder if you are one of Tautech world wide secret squirrel network beavering away for the good of the T&E populationWhy not give a little background about yourself , work experiences and current projects pretty sure the guys would like some insight on what makes you tick and your ability to get the bit between your teeth.With you superb work ethic I have to admit you do not strike me as a native Brit, simply as they would be down the pub after the first sideways step

author: noreply
author_rank: Frequent Contributor
timestamp: July 17, 2020, 06:12:01 pm
content: Quote from: Sighound36 on July 16, 2020, 08:18:11 pmHey sighound36Thank you for your kind words – not sure if this is a backhanded compliment or not – as I know you DO have a well-tempered sense of humor.Yeah, I’m new to EEVblog as a registered member – but been browsing about for about 12 months.I’m a victim of covid-19 (not medically – I’m fine I think?) as I am unable to continue with my normal work and am in essence working from home.By doing this– I can manage my own schedule– and unfortunately have shifted my ‘day’ to ‘night’– hence lurking and posting early morning UK time.What do I do for living?At the moment– I am enjoying being semi-retired because of covid-19– but I am a research scientist in microelectronics– a bit of a mouthful , but it sounds good.I have not been active in this field (I mean being at the cutting edge) for over 15 years, however I do projects and consult here and there– usually by word-of-mouth introductions.Why do I do investigations on Rigol and Siglent and perform all these tests whilst still having time for work and homelife?Trying to be savvy with $$ and not having immediate ‘paying’ clients– my choices in test equipment are limited to Rigol and Siglent, as are many other forum members on a budget.Right now, I work from home and don’t have homelife (kids left nest) so decided to deplete my savings and finally treat myself to some ‘kit’ so I can rekindle some of my design aspirations I never could see through years ago.I HAVE purchased ALL of the ‘kit’ I use from a UK distributor– so no I am not part of Tautech’s secret squirrel network– but if he does indeed have such a network– I am happy to ‘play’ with some new kit and write a review.I have also taken member Elisia’s advice on how to best decide on which type of ‘kit’ to purchase– especially when you really don’t know what is the best for your needs and don’t want to make the wrong decision.Elisia suggested to ask your Test Equipment distributor– to ‘test drive’ the kit you want to buy– on a sale or return basis.Fortunately my distributor was willing to do this with meI have committed to purchase an RF signal generator– either a Rigol or a Siglent– so they agreed for me to ‘test drive’ each instrument.As a thank you for their willingness to do this for me, I offered to write an ‘as you go’ review on EEVblog– so other members can possibly ‘see’ or have some further insights into these products– possibly making their purchasing decisions easier.Of cause– if someone wants to buy a Rigol or Siglent product– I would personally recommend my distributor (PM me if you are interested)– but don’t want to overtly publicize sales related stuff in the forum posts.Sorry but Tautech is already doing plenty of this– so more from anyone else is not wise– unless you are prepared to bring something to the table– so every member here can benefit indirectly.As far as Dave’s mantle in EU / UK– this is not desired– Dave does a great job already, and anybody who thinks it’s easy to do a decent review or teardown, they don’t know what’s involved for sure.- Its bloody hard work!– as Dave would say with his ‘OZ accent.My superb work ethic?Flattery will get you everything …No , not really, I just feel bad if I got something I just did with my new ‘kit’ and after making some quick observations and screen shots– for myself– why not share it with others– only takes a few minutes and indirectly documents your own findings for yourself as well.Am I a native Brit?Well, I don’t know what gave me away here– but you caught me– no not native- although I have been here long enough to be passionate about politics and fight social injustices.(Please don’t ask me about Boris – you I will have to start my rant …)What’s on the upcoming review addenda?Basically all the kit I have purchased– so as I learn about the features and stuff you can do with these instruments, I like to make some presentations– so everyone benefits.Strong believer of pay-it-forward!Hopefully will be reviewing SSG3021X soon (I need to either purchase DSG815 or the Siglent)I have just received a GPSDO– so will do a mini ‘review’– great bit of ‘kit’– in my opinion a must have device for any test lab.Just got a replacement (Via Amazon) programmable digital attenuator– there is a dedicated thread on this which I started– my original was a DOA– this second unit works– but has broken switch– so will complete this review soon.Got the logic probe kit for Rigol MSO5074– so will be doing ‘hands-on’ documentation as I discover its capabilities– will start new thread for this.I have also been given ‘on loan’ a Rigol DSK6K DemoBoard because I asked if I could borrow this and they said yes(lesson to be learned – if you don’t ask , you don’t get opportunity to have)– to have a baseline learning platform for the MSO5074 digital probes.As I learn to use the logic probe kit myself– I will document my ‘learning’ on a forum thread– so others who are interested can view.I also got a set of Sensepeek – PCBite probes– a great bit of kit– member Elisia has a set and using already, I still have not opened my box– but it’s a important bit of kit for me– as I want to test this probe kit for use with RF circuits.I have RF amplifier with LPF on same PCB– want to check the LPF frequency response by injecting RF signal (hence RF signal generator interest) with micro-probe and test response on SVA– without powering the amplifier– because the LPF is a passive component structure on the PCB.If I am still ‘at home’ due to covid-19 after finishing all of the above stuff– then I might also do some testing with the ADLM (Analog Devices Learning Module) Pluto SDR– it is capable of doing some complex RF modulation– so will synthesize a DVB-T television signal– and observe the spectral quality on the SVA– nothing to prove– just observations and deeper understanding on the use of the test equipment.So, I hope the above has enlightened some of the members visiting this thread (I feel naked now) and at the same time quenched your thirst to know more about me and my activities on the EEVblog forum - more importantly, my mysterious endless supply of decent ‘kit’ , any secret association with tautech, aspiration to steal Dave’s mantle, and future projects have now been answeredSorry for the delayed response - I time shifted - my day starts at 3PM GMT - at least until I can get back to normal time - hopefully this weekend.CheersEDIT: Apologies for such a long - essentially 'off topic' post in this interesting thread - but I guess better than starting another thread instead

author: jemangedeslolos
author_rank: Frequent Contributor
timestamp: July 17, 2020, 08:04:17 pm
content: Most interesting post are always off topic

author: kehall
author_rank: Contributor
timestamp: July 19, 2020, 09:57:28 am
content: Quotematlipinski: What do your overshoots look like now at 50mV/div ?

author: noreply
author_rank: Frequent Contributor
timestamp: July 20, 2020, 06:31:03 pm
content: Has anyone made any x-y plots with the MSO5000 series?I noted that in the old Rigol 1054z - there is an option to display the channel(s) - the x and y as well as the x-y Lissajous figure on the SAME screen.With the MSO5074 - I can easily select the x-y plot mode (see screen capture below) - but cannot display the individual channels at the SAME time.Am I missing something - in driving the MSO settings?Or is this no longer possible with the MSO5000 series - but still remains on the DS1054z range?Also, with regard to the x-y mode on the MSO5074 - is it possible to select the individual channels - again I could not see how - only CH1 and CH2 default to the x-y plotting?If this IS the case - perhaps they could have at least chosen CH1 and CH3 (or CH2 or CH4) - to allow the full sampling speed of each channelI'm using the MSO to perform some testing of the Rigol DSG815 - and how stable is its internal clock.The MSO (or any scope) with x-p plot capability is an excellent tool for frequency comparison and drift calculations.An easy way to do this is to 'dial-up' precisely 10.00000000 MHz on the 815 and then compare to the GPSDO which has been stabilized and disciplined the internal OCXO.Interesting results ...If you are interested to know how to do this and calculate the drift in the respective clock frequencies using the MSO then go to thehttps://www.eevblog.com/forum/testgear/rigol-dsg815-testing-feedback-and-comments/msg3122450/#msg3122450thread where I have posted the results and details of 'how-to' make such measurementsEDIT: confirmed posted results for above link

author: noreply
author_rank: Frequent Contributor
timestamp: July 20, 2020, 08:10:22 pm
content: Quote from: kehall on July 19, 2020, 09:57:28 amHello kehall,Thanks for your PMI just did some testing as you requested– to see how the ‘standard’ PVP2350 probes with the 1KHz (internal) calibration frequency response looks like.First of all I made the following settings on the MSOAcquisition settings:Hires mode ONFine ONMeasure Settings:Precession ONBW was set to 20MHz (did not make any diff when I switched to FULL BW)I switched on counter – for CH1I set cursor mode to tracking – so you can see some measurementsI set 50mv/div for Vertical and made a -150mV offset – to fit the displayI set the time base to 3uSec / div for one plot and then again at 20uSec – so you can see both ‘close-up’ and slightly zoomed out.See the attached screen captures belowI did not ‘touch’ my probes – or even do a ‘self-calibration’ on the MSO – so its literally out of the box.I do have the latest FW and my 5074 is now a 5354 –but this should not make any difference at all!I did not check CH3 and CH4 but suspect they would be similar results– let me know if you want me to check?(I have not even opened the 2nd packet of probes – so never checked as yet)You will note that the CH2 plot is ‘on top’ of CH1 (the yellow plot)– for pretty much all of the time– there is a slight bleed through of the yellow– but this does not bother me and not worth calibrating.Hope the above test / results are helpful to you.Good Luck with your experiments.Don’t worry too much– the MSO5000 is a great scope– you will be able to sort it out– or Rigol will help you if indeed the unit is not performing to specifications.

author: kehall
author_rank: Contributor
timestamp: July 21, 2020, 10:05:05 am
content: Quote from: noreply on July 20, 2020, 08:10:22 pmNot sure what's going on with images, I'm not getting the pictures expected...Anyway can't really see too well from thumbnails, but looks like no overshoots?The probes won't make any difference to this concern, its more about the response of the scope (which compensation or self-cal can't fix). I could upload an image but not sure it'll work given everything. perhaps best link to dropbox...ch1 and 2 50mV compensated... ch2 fine, ch1 overshootinghttps://www.dropbox.com/s/pzda82cryolwhrx/2020-03-11%2015.14.18.jpg?dl=0ch1 with compensation adjustment to try to remove overshoothttps://www.dropbox.com/s/el38jdvrrlb5olt/2020-03-11%2015.40.11.jpg?dl=0So do you see anything like THAT?

author: mawyatt
author_rank: Super Contributor
timestamp: July 21, 2020, 07:54:14 pm
content: Quote from: mawyatt on July 21, 2020, 07:39:15 pmInteresting results on terminations, thanks for sharing.Have a similar background (advanced research in analog, RF, MW & RFIC design) and retired 3/1/2019. Trying to build up a home lab and looking into the Siglent & Rigol scopes, and maybe AWG and PS, so been monitoring posts relative to such.This site and Dave's reviews are a great resource. Any advice on these instruments is welcome.BTW developed a few home calibration devices (not NIST but moderate cost and flexible) for DVMs (need to calibrate a couple repaired 34401As against a new Keysight 34465A), these will be made available on here after the due Friday PCBs are assembled and tested.Best,

author: noreply
author_rank: Frequent Contributor
timestamp: July 21, 2020, 08:33:56 pm
content: Quote from: kehall on July 21, 2020, 10:05:05 amIncrease your time base to 20uSec and then to 3uSec and tell me if this improves your response - post a picture if you can - so we can compare like for like

author: kehall
author_rank: Contributor
timestamp: July 21, 2020, 10:18:16 pm
content: Quote from: noreply on July 21, 2020, 08:33:56 pmI'm afraid the scope is in for repair so I can't do anything myself - can you please compare against my settings (top of trace will go off screen of course but only interested in whether you get overshoots like you could see on Ch1 in my screenshot) but they're claiming it as being 'normal' for such overshoots - I'm of the opposite opinion given ch2-3-4 on that screenshot was flat and fine, and I've had no issues with another unit, and also evidenced from what's been said earlier in this thread and other threads, just some more screenshots would really help.To be honest I think all that's needed is the probe connecting to compensation output, 'default' and then 'auto' pressed, 10x and then twiddle vertical to 50mV or whatever to see if you get any overshooting like that on any of the 4 channels :/Much appreciated

author: noreply
author_rank: Frequent Contributor
timestamp: July 21, 2020, 11:08:26 pm
content: Quote from: kehall on July 21, 2020, 10:18:16 pmDo you remember EXACT configuration settings - each setting , like impedance , etc, etcBasically - press the 'default' button (assuming this has not been redefined in any way), then make whatever settings you want - make notes and post here the settings you make after pressing the 'default' button.I will copy EXACT and rerun the rests for you.Also - please check the probe attenuation settings - what were they set to? 1x or 10x - need to know this of cause.No problem doing this for you - just awaiting your feedback to the aboveCheers

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: July 22, 2020, 06:13:40 am
content: Kehall, if you are referring to the probe compensation issue (inability to remove overshoot/undershoot with test signal, no matter how you adjust the screw at the probe) it has been a known issue for 16 months. It affects some scopes, but not others. For a healthy unit, all four channel should look the same, with minimal overshoot/undershoot, your picture definitely show an issue with your unit. I have no idea why Rigol would tell you the channel 1 behavior is normal, you should tell them that it is normal for you to return the scope for a full refund for defects like this.Last year, there were rumors that newer firmware would correct the issue, but it was pretty clear that it did not address the problem for most people with the issue even with the newest firmware. There were some successful attempts by replacing the ifcal.hex with a copy from a healthy scope, jump over to this set of discussion here to learn more:https://www.eevblog.com/forum/blog/new-rigol-scope/msg2241315/#msg2241315If it is a new scope, my suggestion is to send it back for a replacement, you should not have to fix something like this and the unit should have never passed QA. If you have had it for a while (I believe all units should still be under warranty), I would send it back and let them deal with it. Who knows, they may just change the mother board and you may get the 1.01 hardware and a fresh calibration.Hope this helps.

author: kehall
author_rank: Contributor
timestamp: July 22, 2020, 07:37:47 am
content: Quote from: NoisyBoy on July 22, 2020, 06:13:40 amThanks - ok I'll explain the whole story. The image with the overshoot on Ch1 was the first scope I received in March. I indeed had this replaced straightaway. The replacement I received had perfect response - all 4 channels looked like Ch2 on that image, no overshoots.Only problem was there was a delayed fault with that scope which I didn't find until May (hadn't needed to use the scope in ernest until then), after half an hour or so of time in use the very bottom of the touchscreen would not respond, and worse, would randomly activate things at the bottom of the screen, changing settings by itself making it unusable.This went back to Rigol for repair back in June... It came back with a new board (1.01) but all 4 channels then had the overshoot. Worse still, the touchscreen fault had not been repaired either!It went back AGAIN a couple of weeks ago to be replaced by a factory brand new unit, I mentioned them to check the overshooting issue and they say that the new one has the same overshoots and that it's normal, and they say a Tektronix they found the same on??!??I mentioned this thread, and the ifcal.hex (lfcal.hex?) stuff - they say that file didn’t come from their R&D and the overshoot / undershoot which was visible in the past with some devices were resolved with the firmware upgrades...I don't think they're speaking to the right person in their R&D if so, they ought to know the scope!They say it's normal (can't expect 50mV resolution on a 5v p-p signal?) and I can either have this replacement or a refund, very much Hobson's choice

author: kehall
author_rank: Contributor
timestamp: July 22, 2020, 08:01:49 am
content: Quote from: noreply on July 21, 2020, 11:08:26 pmTo be honest if you have the overshoots I think you'd have said by now, but ok try this (from memory and photos):Press DefaultConnect Ch1 and Ch2 to probe compensation output, ground clip to ground (not that this should be needed)Press Autoprobe set to 10x,should get pretty much the display in the quick setup/manual @ 200us/500mV? something like this:set attenuation 10x just to correct the values at the bottomnow 'zoom in' on the vertical (timebase can stay same, its not really that relevant) to the bottom edge of the display to 50mV (bottom edge can stay centred on screen). Interested in what you see.Thanks again

author: kehall
author_rank: Contributor
timestamp: July 22, 2020, 08:13:55 am
content: Quote from: NoisyBoy on July 22, 2020, 06:13:40 amThis is what they claim is ok on the brand new unit and not 'something they see as a bug'...It is less of an overshoot but a significant overshoot all the same - BUT Ch 2,3,4 on the first unit I had and ALL 4 channels on the replacement were really nice and flat, so this feels wrong and what if I need to trust the display when checking higher frequencies than the in built 1Khz 5vp-p square probe compensation output, wouldn't take much for the overshoot to really get in the way?!They say it doesn't overshoot as much on mV signals so it's ok and if I expect to get flat response at 50mV on 5v P-P maybe this scope is not for me?Frustrated!As you know self cal doesn't change anything but I think there should be a lower level calibration routine to build that lfcal.hex file that the service centre (and their R&D contact) doesn't know about.

author: noreply
author_rank: Frequent Contributor
timestamp: July 22, 2020, 05:50:46 pm
content: OK, I repeated the test - as per your instructions / settingsDS14 and 15 are at lower vertical resolutionDS25 and 26 are at higher vertical resolutionAs you can see I offset the vertical slightly - so you can see the separate channel tracesKeep in mind - I DID NOT ADJUST THE PROBES in any way - to try to compensate - this is straight from the 'packet'I don't use probes much - have direct BNC connections - that's why I never calibrated as yet.The interesting thing is that the probes 'track' each other very well - considering they were not 'calibrated' my me.If you want me to try to calibrate the probes for a better response - let me know.Happy to help out.

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: July 22, 2020, 06:07:42 pm
content: I don't use the MSO5000 much these days and it is stashed away behind other equipment. I can try to take some pictures when I have a chance. But I can tell you this is not right, it should be nice and flat.I don't know what type of overshoot is acceptable to Rigol, even my $30 scope does better with the test signal. If I were you, I would not have accepted this as normal and put up with it, and I would have them keep replacing it until it is right. If they can't, get a refund and buy something else. Given the level of support you get from Rigol in the UK, I would shop other brands as there have been some pretty interesting new scopes out there.I find it disheartening that they tried to convince you even a Tek does that and it was perfectly normal. Either their support is clueless, or they treat their customers like they are clueless, neither is acceptable in my book. Based on their latest arrogent response to you, I would just get a refund and buy a different brand.

author: noreply
author_rank: Frequent Contributor
timestamp: July 22, 2020, 06:23:31 pm
content: @NoisyBoyI just made some more tests - this time 'tuned' the probes - yes of cause you can reduce the overshoot - my probes were not calibratedDS27 shows result after probe adjustment.I offset the vertical in DS28 - so you can see the CH1- but its not 100% correctable - slight overshoot?I then tried the SAME probes on CH3 and CH4 - see DS29Then back to CH1 and CH2 - see DS31The switching of the channels with the same probes - confirms that the probes are not the problemIt appears that CH1 has something different internally - possible impedance mismatch - or not set 'spot-on' in factory calibration?I don't know.Personally it does not bother me as long as I can understand the reason for this behavior.Why CH1 only?Is there something specific with CH1?Hope the above helps you out kehall - at least you now have an independent benchmark.Let me know if there is anything else I can do?Take CareEDIT:found way to delete the doubble image and correct

author: tv84
author_rank: Super Contributor
timestamp: July 22, 2020, 07:24:03 pm
content: Quote from: noreply on July 22, 2020, 06:23:31 pmSure there is. You edit the msg and de-select the image.

author: kehall
author_rank: Contributor
timestamp: July 22, 2020, 08:43:55 pm
content: Quote from: NoisyBoy on July 22, 2020, 06:07:42 pmThanks... It is disappointing and frustrating as it seems like it otherwise is a very capable device...Can this forum do polls I wonder, it'd be interesting to do a poll and find out who has good and bad units - its like there's someone on the production line thats get the factory calibration right and others don't care so much!UPDATE: created poll:https://www.eevblog.com/forum/testgear/rigol-mso-5000-overshoot-or-not-overshoot/

author: kehall
author_rank: Contributor
timestamp: July 22, 2020, 09:04:41 pm
content: Quote from: noreply on July 22, 2020, 06:23:31 pmThanks noreply - what firmware is this running please as the trace looks fairly thick - suggesting possibly before 1.1.4.8 (or you're in quite a noisy environment)?

author: noreply
author_rank: Frequent Contributor
timestamp: July 22, 2020, 09:50:53 pm
content: Quote from: kehall on July 22, 2020, 09:04:41 pmPleasure to be of help - this is why we are all here - to help each other!My firmware is 00.01.03.00.01Hardware 01.01.000Yeah, I do have a 'noisy' environment - but there is a lot of jitter / noise on the trace.I have been to busy to check the latest FW updatesI use the MSO for RF design and frequency stability tests - so precise voltage readings not an issue for me - even to the extent I did not calibrate the probes until just now.I will try to check why the 'noise' on the trace and update to the latest FW soon.I presume - this was an issue before with earlier FW??Also - as mentioned in earlier post - the overshoot problem is only on CH1 - did you experience similar?If so, would be nice to see if there is some underlying reason for this - as if it happens in more than one device - there must be some HW or tweek that is common to all of the MSO5074's??Take Care

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: July 22, 2020, 10:05:29 pm
content: I dug out the Rigol and did a few quick snapshots, I also tried to test a few other probes from other scopes to check the difference probes make:In photo DS0, Ch1 and Ch2 are both with the 350MHz Rigol probes that came with the scope.In photo DS1, Ch1 is the same, Ch2 is tested with a 500MHz probe from the LeCroy scope.In photo DS2, Ch1 is the same, Ch3 is tested with a 500MHz probe from the Keysight scope.In photo DS3, Ch1 is the same, Ch4 is tested with a 500MHz probe from the R&S scope.The probe bandwidth and quality makes a difference, as you can see in the more square corners. Both I don't see noticeable overshoot/undershoot as you had mentioned.I hope that helps. I hope Rigol will do the right thing and correct the overshoot problem instead of telling you it is normal.

author: kehall
author_rank: Contributor
timestamp: July 22, 2020, 10:12:58 pm
content: Quote from: noreply on July 22, 2020, 09:50:53 pmThanks, yes I know there was a FW update which reduced the noise somewhat but looks like you're already ahead of that version anyway so probably the environment to a degree.I wish there was a better X-Y mode resolution though (I know its a tricky process with digital sampling) but thats another topic.My first unit bought March was the one with that overshoot on channel 1 only, which made it rather obvious. It was a 1.00 unit - I spent a bit of time trying various things but the supplier intervened and swapped with another. That one had flat, consistent response on all 4 channels, so I was happy until the touchscreen threw a wobbler after some time powered up.It went back for repair in May (really should have been replacement then too as I believe was DOA, just undiscovered), but anyway the board got replaced rather than the screen, so it came back with the same screen fault and a new 1.01 board that then had overshoots on all 4 channels...It's back in for repair now, and offered new replacement, but that has overshoots on all four too so I'm in the middle of trying to get that sorted before they send it me - I don't really want a refund, it doesn't really help anyone - I just want a working, consistent, trustworthy device, and if we can get this issue addressed it'll serve a greater purpose!NoisyBoy, thank you for those images, that's a great help too. I'll point Rigol and my supplier at this thread again (and the poll if it gets any responses)

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 22, 2020, 10:22:51 pm
content: Quote from: NoisyBoy on July 22, 2020, 06:13:40 amNoisyboy, The trimmers on the probes only affect the 10X setting. They have no effect in the 1x position which I think is to be expected.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 22, 2020, 10:30:09 pm
content: Noreply, my channel 2 is not in agreement with the others (as I have shared on page 8 ), and it seems that several other folks have had similar experiences. I in the process of getting a replacement and will post results when I get it. Rigol NA support has been very good so far.I am getting the impression that the calibration process at the factory is a bit spotty. There has been mention of a file that is responsible, but it is likely to be scope-specific and one version is not suitable for all scopes (obviously).

author: noreply
author_rank: Frequent Contributor
timestamp: July 22, 2020, 10:35:43 pm
content: Quote from: kehall on July 22, 2020, 10:12:58 pmYeah - I found the same - BUT I guess my specific reason for using X-Y is to see the 'spinning circle' - where the 'spin' is under observation (the period) no the thickness of the trace.I also posted earlier - if there is a way to display CH1 and CH2 while displaying the X-YThis is possible on the 1054z - so unless I missed something in the menus - perhaps they remove this feature from the 5000 series??

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: July 22, 2020, 10:58:28 pm
content: Pulsepowerguy, agreed, the compensation were only done at 10X. All my tests were done using the 10X setting on the Rigol probe, and 10X setting within the scope.For all the other probes I used in the test, they are all 10X only probes.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 22, 2020, 11:00:30 pm
content: Quote from: noreply on July 22, 2020, 10:35:43 pmHit the 'Acquire' button and then 'Time base mode' (XT, XY, Roll)

author: noreply
author_rank: Frequent Contributor
timestamp: July 22, 2020, 11:48:45 pm
content: Quote from: Pulsepowerguy on July 22, 2020, 11:00:30 pmYeah .. this is correct - but it will put you the X-Y plot ONLY or the Time Base mode ONLYWhat I am trying to do is display BOTH timebase - the CH1 and CH2 lots and 'below' this the X-Y plotLike - take the DS32 and put DS33 below this image - to form one large image waveform containing BOTH plots at the SAME timeThis IS possible on the 1052z

author: noreply
author_rank: Frequent Contributor
timestamp: July 22, 2020, 11:59:28 pm
content: Quote from: kehall on July 22, 2020, 10:12:58 pmInteresting - just trying to see 'why' digital sampling would have this inherent side-effect?

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: July 23, 2020, 12:22:58 am
content: Sorry, noreply. I misunderstood your question (as is usual for me).

author: noreply
author_rank: Frequent Contributor
timestamp: July 23, 2020, 02:55:33 am
content: Quote from: Pulsepowerguy on July 23, 2020, 12:22:58 amNo problem - was difficult to visualize from description.I have attached a photo I managed to capture from YouTube - as it shows exactly what I am asking about.Much easier to understand

author: kehall
author_rank: Contributor
timestamp: July 23, 2020, 07:45:40 am
content: Quote from: noreply on July 22, 2020, 11:59:28 pmThe way I understand it - X-Y on a 'proper' analogue scope is easy as the signals literally drive the horiz and vertical amps and therefore the plates in the CRT, you can only have one 'spot width' at any one point on the screen.A digital scope has to sample the signal voltages passing through an ADC, and then draw pixels. These samples are done thousands/millions/billions of times per second and plotted on the screen.Noise levels (externally, and within the scope) mean that these samples can vary 'wildly' and therefore you see the square rather than a single point you see when XY is on a digital scope.Averaging or some other filtering should really help but it doesn't look like the MSO5000 has this right yet, and worse still, this noise seems to occur irrespective of any adjustments to attenuation/amplification, as you can see in these two images (of the same signal, two sine waves from in-built generator one slightly higher frequency than the other so you have a bit of a slowly 'rotating/flipping' circle showing phase change).The 2nd image is just the same but at 100V/div, and you see the trace 'width' doesn't change.The display is suggesting there’s around 20-25V of noise on a 5V amplitude signal which clearly cannot be!

author: noreply
author_rank: Frequent Contributor
timestamp: July 24, 2020, 09:58:16 pm
content: Thanks for the nice 'explanation' it certainly makes sense.Yeah, I remember the 'crisp and bright' Lissajous figures on the CRTBut those old CRT scopes - compared to the MSO5000 - were true dinosaurs - not only big and heavy but not so clever at the same timeBTWI also came across a YT video from which I 'lifted a frame' - clearly showing that even an 'old' R&S scope is able to do better job with X-Y - it look much crispier than the Rigol - but at a much higher price.I guess for my immediate needs - the use of the Rigol's X-Y is 'good enough' for me.Perhaps someone could 'chime-in' with a screen shot from the Siglent 2104X Plus in X-Y mode with a spinning circle?I'm thinking it will be same as Rigol

author: tautech
author_rank: Super Contributor
timestamp: July 25, 2020, 02:12:20 am
content: Quote from: noreply on July 24, 2020, 09:58:16 pmNice video of a pre-release unit doing X-Y for you to download here:https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2787208/#msg2787208

author: noreply
author_rank: Frequent Contributor
timestamp: July 25, 2020, 03:45:00 am
content: Quote from: tautech on July 25, 2020, 02:12:20 amInteresting...That was back in 2919Any chance of getting a 2000x Plus and doing the following;-Get a 10MHz Sine 500mv signal - out of the AWG on the 2000x and connect to CH1 on the 2000xGet another 10MHz Sine 500mv signal - from another source and connect to CH2 on the 2000xThen select X-Y mode on the 2000xYou should see a circleIf the circle is not moving - the two 10MHz frequency sources should be 'in sync'Take a screen shot and post hereThank YouIts probably unlikely that the circle is perfectly 'still' and not moving - because the respective independent 10Mhz clocks will be drifting.If CH1 source is from a GPSDO - stabilized and locked to GPS signal - you should have (if you have a well disciplined clock) at least 10E-12 accuracy.That's 0.000001Hz accuracyNow you can use this 10MHz signal to calibrate all the other equipment in the labGet your other 10MHz signal - from the device being calibrated is connected and connect to CH2 on the 2000xPut 2000x in X-Y modeCircle will most likely be spinning.Adjust the frequency on the source connected to CH2 (the device you are calibrating) - until the circle is virtually frozen i.e not moving.Unfortunately the circle will still be moving very slightly.Write down the frequency shown on the source connected to CH2Note the last significant digit.It should be at least 0.01Hz - if you have a good frequency source.Now look at the circle and get a stop watch.Start the stopwatch and time 'in seconds' - how long it takes for the circle to rotate 2 times.The circle actually rotates 360 degrees - because we see it in 2D on the 2000x screen - we need to have 2 x 180 degree spins.Write down the number of seconds and now divide 1 by the number of seconds.Hopefully you will get a small fraction - something like 0.004567 - as an example.Now you can ADD this number to the least significant figures you recorded earlier for frequency of CH2 source.For example if the least significant figures were 0.01Hz - then adding 0.004567 will yield 0.014567 HzNow you will have CH2 calibrated to 'atomic time' accuracy and the frequency will be 10.000 000 014567 HzHope the above procedure is useful for anyone wanting to calibrate CH2 frequency to the CH1 reference (as used in the above example

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: July 25, 2020, 09:22:28 am
content: Kehall,If the sellers of the scope won't refund your money and you paid with a credit card, or even a debit card that has a VISA or MC logo on it, you can use that to get sorted out. Call your card company and simply tell them that you purchased with their card and the vendor won't refund for a defective item that's been back several times for repair and ask them to raise a claim; they will probably put you onto VISA or MC.If you pursue this avenue, you may well end up with a refund without having to return the scope.In the UK there is also buyer protection law that says that an item sold has to be of "merchantable quality" meaning it has to perform the designed function properly.I like my MSO5000 but the first one I got was hw 1.0 after I'd specifically stated that I wanted a new unit on my order through Tequipment.net. They (Tequipment.net) got be a brand new scope (hw vn 1.1) and sent me a free shipping RMA for the return of the first one.Good luck.

author: kehall
author_rank: Contributor
timestamp: July 25, 2020, 10:39:06 am
content: Quote from: Gandalf_Sr on July 25, 2020, 09:22:28 amThanks, the refund has been offered and the dealer is not being an issue, the new scope they will supply has overshoots though and the service centre isn't really believing it isn't 'normal' as unfortunately the other scopes they have had the same problem and they're not speaking the right people at the R&D/factory as they claim to know nothing about the 'lfcal.hex' fileHence the poll I created to help evidence the fact that it is NOT normal and they need to get to the bottom of it...Do me a favour please and lodge your 'vote' herehttps://www.eevblog.com/forum/testgear/rigol-mso-5000-overshoot-or-not-overshoot/I'm happy with the scope if I can get a good one, but that's the problem, I have the worst luck when it comes to things like this so even the brand new 'factory fresh' replacement they offered is 'bad'...

author: jemangedeslolos
author_rank: Frequent Contributor
timestamp: August 13, 2020, 05:46:53 pm
content: Hello,Has anyone ever tried to loop TRIG OUT to EXT TRIG?I tried this to engage the totalizer on EXT TRIG but it doesn't work.I checked my TRIG OUT signal and it's OK.I checked my EXT TRIG input and the totalizer function with my AWG and it's OK.I checked my cable and it's OK.The only thing I haven't checked is the TRIG OUT signal level.Any ideas ? (I have a MSO7000 but I guess the implementation is the same )Thank you

author: Testtech
author_rank: Regular Contributor
timestamp: August 13, 2020, 08:38:40 pm
content: UPDATE:Thanks for the input, I am aware of you points, I tried 3 other signal sources with the same result.I contacted Rigol Tech Support, and after discussion, an RMA was issued and the instrument shipped back today for replacement.I will advise when the replacement arrives.Greetings,I have encountered an issue with my MSO5204 where a high frequency sinewave shows what I am calling artifacts, for lack of a better term.Please see the pictures.The "artifacts" can be changed by slightly varying the frequency, or can be made to disappear by turning on another channel. Also, changing the depth from AUTO to a much higher value will seem to make it disappear. It is apparent without the Color Grading on, but is easier to see in Color Graded mode.These are most easily seen at higher frequency, and yes, I have tried several other sine sources, and all present the same.Has anyone else encountered this? Perhaps someone can try this with their instrument and see if it does something similar

author: noreply
author_rank: Frequent Contributor
timestamp: August 13, 2020, 09:24:59 pm
content: Quote from: Testtech on August 13, 2020, 08:38:40 pmSure ... happy to check this out for youBUTBefore you go any further - can you please provide more details on your high frequency sinewave like ;-1. What is the source of the sinewave2. Have you checked the signal - is it clean?3. Perhaps your source has the mysterious 'artifacts'If you have a 'dodgy' source signal - the MSO will be doing its 'job' to detect the 'artifacts'By varying the source frequency - and the artifacts disappear is agood cluethat the source is generating the 'artifacts'By changing input channels (depending on which one you use)- this also will / may reduce the MSO's sampling rate- hence the 'artifacts' disappear- from your 'plots' this CAN BE CONFIRMED- because CH2 has reduced sampling (shares ADC) and CH3 is same as CH1- so its expected to 'see' the 'artifacts' on CH1 AND CH3 - if its really there - but not on CH2 - soyour MSO is behaving as expectedYou need to get a verified and 'clean' Source to do MSO waveform 'artifacts' debugging - otherwise the MSO might be doing its 'job' and reporting the 'artifacts'because they are really thereIf you are still having problems after checking your sine source- then please give me your EXACT MSO parameters you used for your measurement (best way is to press the 'default' button first - then record all the settings you make)- also the sine source frequency / amplitude

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 13, 2020, 10:05:41 pm
content: Greetings All,I received my replacement MSO5074 this week and updated to the latest firmware, calibrated, etc.. Here are some new measurements. As before (see my post on page 8 ) all four probes are at 1X and connected to AWG I output (set to 100kHz and 5Vp-p). As can be seen, the four channels are much closer in agreement than with my first scope. This is a big improvement. Interestingly though, they are not quite the same at the 200nS area. Ch1 and Ch4 are in very close agreement so they may have to be my go-to channels. This, I suppose, is what $1k buys and I should accept it and move on. Any thoughts?

author: noreply
author_rank: Frequent Contributor
timestamp: August 13, 2020, 10:40:48 pm
content: @PulsepowerguyFirst of all - hope that your new MSO meets your expectationsPlease don't dismiss the capabilities of this nice bit of 'kit' - even if its in the $1K range - it will blow much higher priced devices out of the water.My first suggestion to you is to do your testing again - but this time - see if you can 'borrow' some 500MHz 'expensive' probes.My gut feeling is that the current problems you are having are related to your probes rather than the MSO itself.The MSO can handle without problems 400MHZ+ which is great.The supplied probes are rated to 350MHZ - but these are 'cheap' probes - mainly intended for low frequency work - despite their rating.There are significant 'clues' in your plots that - at least at 1st step in your quest to get the response you are expecting - indicating potential probe issues.The rising edges and trailing on your plots seem to be fine and are all 'in tune' with each other.Your problems appear with the 'overshoots' - an area which closely correlates to probes and their inherent ability to handle these signals.So, before you start to- just try things out with the 'best' highest specification probes you can get your hands on and see how the MSO behavesAfter checking out your probes, if you are still having identical issues - we can then try to see what might be causing thisBTWA quick test (but not 100% conclusive) is to switch probes with the different channels - and see if the plots 'follow the probes' - if it does that's a big clue

author: Howardlong
author_rank: Super Contributor
timestamp: August 13, 2020, 11:20:19 pm
content: Quote from: Pulsepowerguy on August 13, 2020, 10:05:41 pm

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 13, 2020, 11:53:05 pm
content: Quote from: noreply on August 13, 2020, 10:40:48 pmSorry. I neglected to mention that I swapped the probes every which way and nothing changes, so the probes are not the issue as far as channel to channel differences go.I really like many things about the scope - this one is definitely better than the last one - I just get the impression that this is the best it gets for the money. I have been a Tek user for my entire 40 year engineering career and I never thought I could afford a decent scope for my home. From what I can tell on this forum, the factory calibration of this scope has a degree of variability from unit to unit (and from channel to channel in my sample of two machines). That is a pity, as I would go to great lengths to tune this thing if I could.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 14, 2020, 01:02:43 am
content: Well, well. I happen to have a Probemaster 500Mhz probe and a Tek P6139B. Below are all three (one at a time, plugged directly into AWG I) - all three were tuned for the scope and note that the Rigol probe is now at 10X. Interesting how the Rigol has the least overshoot, and the Probemaster the greatest. These overshoots are not tunable as the trimming cap only affects the relatively long time behavior. I kinda like the Tek probe's behavior the best.All of these traces look a lot cleaner because I no longer am trying to compare channels so the connection to the generator is very short.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 14, 2020, 01:05:27 am
content: ...and here are the same three probes looking at the same output, but plugged into a TEK DPO3034 (all probes re-tuned for it). Interesting.

author: noreply
author_rank: Frequent Contributor
timestamp: August 14, 2020, 01:06:32 am
content: Quote from: Pulsepowerguy on August 13, 2020, 10:05:41 pmLike I said - your MAIN problem is in the probes - see video Dave made (thanks @Howardlong) posted above.Swapping probes as suggested and like you did only confirms that ALL probes exhibit identical behavior - it is not conclusive that your problem is not probe related.First of all CH1 and CH4 - your best channels are using different ADC's as the MSO has 2 of these shared between the 4 channels.CH1 and CH2 if used simultaneously will be lower sampling hence BW capability than if you used CH1 and CH3 or CH2 and CH4 - in effect to have a dedicated ADC per channel.So don't expect to have SAME performance across ALL channels at the same time when pushing the BW / sampling rate.It would still be very interesting - if you are able to get hold of much better probes which are rated WELL ABOVE the MSO specifications - I suspect you will get a much better response.For now - try to run the test again but compare only CH1 to CH3 OR CH2 to CH4 - set your probes to x10 when you do this - see what happens ?*** If you can try a direct coax connection to CH1 from sig gen and to CH3 from sig gen and compare this - make sure the COAX is appropriately terminated.EDIT:SORRY - I think our posts crossed

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 14, 2020, 01:37:22 am
content: Here are the two scopes looking at AWG I with a bit of coax - no probes. ARgh! I noticed that the tek bandwidth was set to 20MHz for the previous captures.This time it is set to full (350MHz). Also, I don't have a terminator for the Rigol scope so left the TEK input at 1Meg. Take that into account.NOREPLY: I do not agree that the sharing of the digitizers is involved here. I maintain that this is a "front end" issue, where each channel's signal conditioning is noticeably different. I turned off all but one channel and the response was indiscernible from that with all four channels active.I would really like to see the behavior of the 350MHz version of this scope.

author: noreply
author_rank: Frequent Contributor
timestamp: August 14, 2020, 03:29:08 am
content: @PulsepowerguyThanks for your feedbackAlso for doing some more testing.I did notice that your source frequency was set to 100KHz - if this is still the case than the ADC sampling should not be an issue.My comment(s) about the channels and the 2 ADC shared between 4 channels was just to alert you (just in case you were not) that all channels are NOT identical with regard to sampling - and calibration - as you most likely know now.I am happy to 'run' your tests on my MSO - which has been enhanced to 350MHzPLEASE let me know your exact settings - AFTER you perform a reset to the default settings (press the default button) and them let me know precisely what settings you make - step by step - including your AWG setup.I will reproduce this - and we will see how the two MSO's compare.Its really late here in London - so I need to get somejust now.I wanted to quickly post this message - so you can let me know your setup - this way when you are catching some, i'll run the testsTake Care for now

author: jemangedeslolos
author_rank: Frequent Contributor
timestamp: August 14, 2020, 06:56:02 am
content: Quote from: jemangedeslolos on August 13, 2020, 05:46:53 pmJust checked and there is no EXT TRIG input on the MSO5000I will try on the MSO7000 desert topic !

author: Howardlong
author_rank: Super Contributor
timestamp: August 14, 2020, 01:31:15 pm
content: Quote from: Pulsepowerguy on August 14, 2020, 01:37:22 amSorry if this has been mentioned before, but are you sure you're not over driving the channel inputs? a lot of the trace isn't displayed.If it's a Hi-Z input that leaves the source unterminated. I'm not sure you can draw many conclusions from that.I'm now not sure what it is you're trying to show?If it's that the channels behave differently when you're over driving them or not terminating the source, then I'm not sure now what the complaint is?

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 14, 2020, 03:07:01 pm
content: Quote from: Howardlong onTodayat 01:31:15 pmI agree with you on several points - over driving the inputs eventually leads to problems, but there is a level at which the signal can exceed the vertical boundaries without distortion and that can be discerned by switching the range while looking at the response. Both the Rigol and the Tek scopes appear to be working well with a setting of 100mV/div and 2.5V offset to look at a 5Vp-p square wave (but of course I could be mistaken). The source really should be terminated at 50, so my measurements have the nasty spike on the leading edge (I have no termintator at home, but will work on that). Still the comparison seems valid.My concern has been with the variance from channel to channel, and this newer scope is much much better than the first one I received. I guess you could say that I am in the validation phase of the purchase - I am coming to terms with the behavior of this scope while learning of its limitations. It is definitely a good piece of gear for the price.Update: I wised up and added two, 100 Ohm, 1/4W resistors to the end of my bit of coax (shortest possible connection for low inductance) and reconnected all of the Rigol Probes (set to 10X) to the resistors. See attached. The match up is, in fact, better looking now.I appreciate everyone's feedback BTW.@noreply, I would still like to see your results. Please don't stay up so late just for this though.

author: noreply
author_rank: Frequent Contributor
timestamp: August 16, 2020, 03:05:13 pm
content: Quote from: Pulsepowerguy on August 14, 2020, 03:07:01 pmPlease provide EXACT MSO configuration / settings - so I can reproduce SAME conditions here & do the testing.

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 16, 2020, 05:08:55 pm
content: @noreply I think the attached setup file will work. After loading it myself I had to activate AWG I, but it then duplicated my setup exactly.The external setup is:~8" coax with BNC on one end (connected to AWG I) while the other end is terminated with 2, 100 Ohm resistors (shortest possible leads). Ch1 is connected to these resistors with a very short (imperfect, I know) BNC to alligator clip adapter. Ch2 is a TEK probe, Ch3 is a Rigol probe, and Ch4 is a ProbeMaster probe. The photo shows this mess.

author: Howardlong
author_rank: Super Contributor
timestamp: August 16, 2020, 05:53:33 pm
content: I'm probably being a bit thick here.I loaded up your setup file.As discussed previously, the channels are being overdriven, 3Vpp on 100mV/divThere are now four different probing arrangements, one on each channel, so I'm not sure how you're demonstrating that each channel is different?What is true is that this scope has a very, very noisy front end!

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: August 16, 2020, 06:33:22 pm
content: Quote from: Howardlong onTodayat 05:53:33 pmYou are certainly not being thick.Someone suggested that the Rigol probes were responsible for the odd responses I was seeing, and I am 'shifting gears' by attempting to show here that the different probes look very similar to each other (though not identical) on this scope whereas the direct connection to Ch1 looks pretty flat. These same probes look different from this on the TEK scope (see attached). Its a bit odd. What is it about the front end of this scope that causes the 10X probes to interact differently than direct (tied to 50 ohms) connection. The TEK scope traces for the same conditions (re-tuned the probes of course) do look different from each other, but none of them exhibit the ripple that shows up on the Rigol.I do not see any evidence of overdrive with this setup though. What am I missing? Many modern scopes must deal with this kind of signal and do it well. The Tek scope shows no problems with this either. That being said, the older scopes (20th century) I have used do not do so well. I do know that the direct connection (1X) will be over driven at one setting more sensitive than what I stored. I must reiterate that this particular scopes is behaving much much better than my first one and I am very happy with it now. I do look forward to seeing the behaviour of the 350MHz version for comparison.Your comment about the noisy front end is interesting - what scope(s) are you comparing to?

author: Howardlong
author_rank: Super Contributor
timestamp: August 17, 2020, 01:56:28 pm
content: Quote from: Pulsepowerguy on August 16, 2020, 06:33:22 pmRunning a scope channel outside of the graticule, i.e., overdriving, isn't typically a recommended use case because the preamps in the front end will typically be in saturation, and will have a recovery time and usually uncharacterised behaviour while coming out of saturation. There is a frankly weird video that Rigol put up supposedly demonstrating their high resolution mode that seems to suggest the Rigol will operate without problems with channels well outside the graticule, but it doesn't seem to demonstrate high resolution mode at all. What's not clear from this is what the limits and behaviour of the scope channels are if overdriven, for example recovery time.QuoteI did some measurements about a week or so ago to derive the effective bit resolution. The MSO5000 typically had around a ~10dB worse noise floor (a bit less than a 2 bit deficit on average).Tests were done in all cases with:o 20MHz channel bandwidtho 1us/divo 1MSa memory depth (or as close as possible)o 8 bito 1M ohm channel, with 50 ohm terminator attached

author: Testtech
author_rank: Regular Contributor
timestamp: August 21, 2020, 04:32:05 pm
content: Update,I have received and tested the replacement instrument, and it works properly.Kudos to Rigol tech support, they were very prompt with email response and shipping a replacement instrument. I could not be more pleased in my dealings with Rigol support.Quote from: Testtech on August 13, 2020, 08:38:40 pm

author: noreply
author_rank: Frequent Contributor
timestamp: August 22, 2020, 03:58:49 pm
content: GreatIts good to know it 'was' a HW fault and more importantly that Rigol did provide a great service

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: August 24, 2020, 12:25:03 am
content: Testtech,Glad you git it sorted out. Kudos to Rigol for fixing it.

author: dreamcat4
author_rank: Frequent Contributor
timestamp: November 01, 2020, 01:09:10 pm
content: Hello, thanks for all of this community work sharing information about the rigol. I understand that this is the current list of known bugs. However what I feel is missing is getting a better insight / understanding which of those bugs are not as important as the other ones which Dave had initially raised at the release.I am trying to get a better understanding about the specific areas which put the Rigol at a disadvantage to the more polished Keysight DSOX1204G. Mostly in terms of usability, and confidence in getting a quick set of readings which are easy to understand and not misleading. Or without having to go away and lookup how to access an option because it is obscurely placed and is always forgotton because it gets less frequently used.Another comment on other thread was about the graphical display lag, despite having a faster cpu that does not necessarily mean the video display side is as good. For example when I see videos of people using the keysight it looks so responsive, it almost kindda emulates the 'feeling' of an analog scope. Which is all great and all. But I have still yet to see such good demos of the rigol on youtube. Ideally what would make it easier for me to decide is a video, where somebody has them both side by side. And is doing 'a per' feature walkthru togther on both scopes. Comparing with the very latest 2020 newest rigol firmware. And really showing the strengths and weaknesses of each one.Quote from: EEVblogHe is probably still far too busy tied up with all that other stuff. Moving offices and again trying to free up new space for the inevitable hoarding of more and more things.But maybe there are 1-2 other youtubers instead of Dave who already own these scopes. And would be able to do their own comparison. That would be fantastic I think.We might also hope for Keysight to plan updating their DSOX1204G. To make a more capable version in response to the Rigol. If that would ever happen.And of course people also bring up other Brands. But I am much more doubtful of those coming anywhere near close to the Keysight in terms of usability factor.A simple way of posing my quesiton is like this:* If you were to have both scopes in front of you, on a daily basis. Which one would you be reaching for time and time again?I believe the main counter argument (in favor of the Rigol) is: well the Rigol can do things which the Keysight simply cannot do. So if you can only afford 1 scope, it should be the Rigol. Otherwise those possibilities are entirely shut off to you.However that argument does nothing to think about or address areas where the Rigol is worse than the Keysight. So this is why I feel a side by side walkthrough / comparison is perhaps a fairer way to judge the 2 scopes against one another. Since they have different strengths and weaknesses in different specific areas. It's not a checkbox / specs thing either.I feel what is most frustrating is that because the SPECS of the Rigol are better, then why can't Rigol eventually (in the software) also just solve those usability and user interface problems too? And be 'close enough'. To address these 'rough around the edges' problems and other crazy bugs that make no sense to the outsider. Without understanding the internals.So this is really where I am saying... well "its a lot of money" and if I cannot feel happy with either one. Then perhaps it's better not to buy either one. And just defer purchase of a scope (yet again). As I have already been doing for so many years at this point.

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: November 13, 2020, 12:45:42 am
content: I used to own a Keysight MSOX4054A with all the options enabled (legit). Then I bought the Rigol MSO5074 and found that I liked the screen better on the Rigol (it's higher resolution and you can make the menus go away so the whole screen width is traces) so I sold the MSOX4054A for $7,500 (less eBay fees). The MSO5074 does everything I need and makes much more sense for the money I paid.

author: ro_ok_bo
author_rank: Newbie
timestamp: January 15, 2021, 09:51:24 am
content: Hello and sorry everyone for my bad English and I find this forum just great.I bought a MSO5104 and with Python3 and (pyvisa) I can communicate with it.Unfortunately I can't understand what command I have to send to receive the values captured by the markers.I can set the instrument with the commands of the software manual;for example :# measure ................scope.write (": MATH1: FFT: HCENter" + str (Center_Freq))scope.write (": MATH1: FFT: HSCale" + str (BW_set_Misura)) #scope.write (': MATH1: FFT: SEARch: ENABle ON') #scope.write (': MATH1: FFT: SEARch: NUM 3') #scope.write (': MATH1: FFT: SEARch: ORDer AMPorder') #Unfortunately I cannot understand from the manual which command to send to have the values of the markers as a response.Any suggestions please?Or a link with an example?Many thanks to all.

author: tim_
author_rank: Regular Contributor
timestamp: January 19, 2021, 07:49:36 am
content: I have a rather stupid question: Is it possible to save settings on the MSO5000? For example, it is quite annoying to have to change the communication settings every time I turn the scope on to assign an IP address.

author: tcottle
author_rank: Contributor
timestamp: January 19, 2021, 01:08:00 pm
content: TryUtility > System > Power ON > Last

author: normi
author_rank: Regular Contributor
timestamp: March 22, 2021, 06:26:10 pm
content: When is another firmware update expected for the MSO5000, it's almost a year since the last update.

author: mironex
author_rank: Newbie
timestamp: March 31, 2021, 02:20:36 pm
content: I am considering purchasing the MSO5000. It has good hardware.I asked a question about firmware update and I got answer.Please see print screen.

author: Gandalf_Sr
author_rank: Super Contributor
timestamp: March 31, 2021, 03:29:22 pm
content: Mironex, I just tried to PM you and found your inbox was full.This is a thread you may be interested inhttps://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2769676/#msg2769676

author: normi
author_rank: Regular Contributor
timestamp: April 09, 2021, 12:07:59 pm
content: I just got my new MSO5074 and was speaking with support and mentioned firmware and the XY mode noise issue. They offered me a patch for the problem, I have not applied it as I am still going through the features of the scope. Has anyone else got it, and tested it.

author: MegaVolt
author_rank: Frequent Contributor
timestamp: April 12, 2021, 09:52:00 am
content: Quote from: normi on April 09, 2021, 12:07:59 pmWhat fix have you been offered? Can you share it?

author: normi
author_rank: Regular Contributor
timestamp: April 12, 2021, 01:17:41 pm
content: This was a firmware with build date of March 17 this year, I sent the link in a PM to you. I am still familiarizing myself with the scope to see how it functions that I can see what improvements firmware brings. But support specifically mentioned the XY mode.

author: luma
author_rank: Regular Contributor
timestamp: April 12, 2021, 08:25:41 pm
content: Quote from: normi on April 12, 2021, 01:17:41 pmTo my knowledge, this is the first anyone has mentioned a 2021-03 build for the MSO5000 series. Sounds like a new release maybe?

author: Noy
author_rank: Frequent Contributor
timestamp: April 13, 2021, 09:21:00 pm
content: Just a short question. In the RSA thread there was mentioned that modding the SMPS significantly reduced noise in the RSA. And sighound said that the PSU is the same like the MSO7k and he also modified this PSU for better noise..Is it also the same PSU in the MSO5K? Maybe wie get less noise if we also modify the PSU with better quality caps?Does somebody knows ?

author: thm_w
author_rank: Super Contributor
timestamp: April 14, 2021, 09:35:01 pm
content: Quote from: Noy on April 13, 2021, 09:21:00 pmWhat difference did he see on the MSO7k? I wouldn't expect any change like on a SA. Also the noise is mostly from the front end ADC which is well shielded, etc. so probably not much can be done there. But I would try it if he say a large difference with the 7000.

author: normi
author_rank: Regular Contributor
timestamp: April 19, 2021, 12:23:50 am
content: Managed to test the firmware, it looks like possible a beta version. But it corrected the XY mode and another issue I had with exportingevent table. Not sure what else it fixes. Before and after pictures posted.

author: TK
author_rank: Super Contributor
timestamp: April 19, 2021, 12:56:01 am
content: Does it lower the noise only in XY mode? Can you test if noise is lower also in normal (non XY) mode?

author: normi
author_rank: Regular Contributor
timestamp: April 19, 2021, 12:11:33 pm
content: Does not appear to affect noise elsewhere. Noise issue may need hardware solution.

author: Noy
author_rank: Frequent Contributor
timestamp: April 19, 2021, 12:58:17 pm
content: Or it is pretty early (march build) for an release in june / july.. I think there was an "announcement" in one of the other 5K threads..So maybe they are testing currently the fix in xy mode and will activate it in the final release for all "modes". Will be interesting if there are some advantages about noise maybe some features of the Phoenix chip not yet implemented / activated? Noise is currently one of the big "issues" if the 5K is compared with the siglent one so i think rigol has to react in some kind to still be attractive with their cashcow against the siglent 2k+

author: Noy
author_rank: Frequent Contributor
timestamp: April 19, 2021, 01:57:03 pm
content: Just found the "Waveform freeze" "button" what does that mean? Couldn't get clear with the manual..

author: normi
author_rank: Regular Contributor
timestamp: April 19, 2021, 02:42:16 pm
content: You can play around with it and do run/stops, if enabled it basically shows what you currently see on the screen which includes memory, if disabled it shows just the last capture. If you had a signal with a lot of jitter, when enabled the run/stop would show the jitter, disabled would show the last trigger and would have missed some of the jitter. Almost like no persistence

author: agorlach
author_rank: Newbie
timestamp: April 23, 2021, 02:38:55 am
content: Just to contribute before my question, I found the bug in the CAN decoder. ACK field always marked as "Err" (tested on 250 kbps CAN bus), because it skips the CRC delimiter field. At the screenshot below I marked last four bits of CRC (0x3BA6, and it is correct CRC, checked). 6 is binary 0110, and the next bit is CRC delimiter, not ACK. ACK is placed after CRC delimiter.And my main question is: I have the latest firmware (00.01.03.00.01) and in 99% it can't load saved WFM back correctly. Every time I have new problems. Signal length is doubled. Or signal form is incorrect. Is it normal for this firmware or I need to check the memory? Does it have memory diagnostic tool? Even without saving, I meet strange bugs, like desynchronization of decoder and wave in the Zoom window from time to time. I do not believe that it is software with 3y of updates, I think it is defective hardware of my oscilloscope.Thank you.

author: agorlach
author_rank: Newbie
timestamp: April 24, 2021, 02:51:56 pm
content: First picture is before saving to WFV, second after loading back. No changes in settings, scale was enlarged after loading. Is it normal? I can load back one or two files from ten.

author: Howardlong
author_rank: Super Contributor
timestamp: June 06, 2021, 05:05:43 pm
content: I've had the MSO5074 out on the bench again for a couple of weeks.I noticed that one of the probes PVP2350 had become a bit intermittent, but if I jiggled it about a bit I could get it to behave.Today, it's completely failed in 10:1 mode: it looks like the series 9Mohm resistor has failed, as it responds to transitions but there's no DC.Scope channels themselves are fine.Is there a secret to taking these probes apart, or are they completely sealed?This unit's only seen a few days of use, and it sits in a Rigol carry case when not in use with a front panel cover. There's only me uses it too, so I know it's not been mishandled (other than by me!).

author: jemangedeslolos
author_rank: Frequent Contributor
timestamp: June 07, 2021, 08:12:06 pm
content: Tautech

author: jundar
author_rank: Contributor
timestamp: June 21, 2022, 02:51:45 am
content: I see it is an old post but maybe someone still can take a look at the photo. Is it some bug in firmware?The probe are on x1 and all settings are the same expect the 50mV/div vs 51mV/div. Thanks much for any response!!

author: Fungus
author_rank: Super Contributor
timestamp: June 21, 2022, 05:11:52 am
content: Not a bug. It's probably switching to a different front-end attenuation/amplifier range when it goes to 50mV.If that's the case then 51nV will be at the outside limit of the previous range.

author: MegaVolt
author_rank: Frequent Contributor
timestamp: June 21, 2022, 06:24:06 am
content: Quote from: jundar on June 21, 2022, 02:51:45 amIf I'm not mistaken, he can choose from round values 1, 2, 5V .... And he can also set a fractional gain per cell. I don't know how it's implemented. But this is not a mistake. This is a feature.

author: jundar
author_rank: Contributor
timestamp: June 21, 2022, 02:11:37 pm
content: Thank you all for reply.It should be mentioned, such behavior is observed using x1 probe only and does not show using probe set at x10.

author: cebrax
author_rank: Contributor
timestamp: August 30, 2022, 05:46:36 am
content: Hello everybody,I used to have NoiseFilter in my Tektronix MSO2024 scope that goes down under 100 Hz. That is a VERY FAST software low pass filter that helped me a lot! For example I could convert my 5 kHz sine PWM to a real analog sine signal easily..Is there such an option for MSO5000 other than slow MATH functions?

author: MegaVolt
author_rank: Frequent Contributor
timestamp: August 30, 2022, 08:26:30 am
content: Quote from: cebrax on August 30, 2022, 05:46:36 amOnly: math filter: low-pass filter, high-pass filter, band-pass filter, and band-stop filterHave you tried their work? Do they work fast enough for me?

author: vicki20july
author_rank: Contributor
timestamp: September 04, 2022, 09:40:45 pm
content: Hello everybodyMy apology if this is slightly off topic but I think it is still relevant to the MSO5000 tests, bugs, questions. I have been looking to buy my very first oscilloscope and I narrowed my selections down to either Siglent SDS2104X Plus or Rigol MSO5074. As of today, I can buy a new MSO5074 for $1215 CAD (taxes + shipping included) and the SDS2104X Plus for $2055 CAD (taxes + shipping included). I was very close to buying the Siglent but at the current price point, as of today’s pricing, the Rigol is approx. $840 CAD cheaper, and similar if not better spec-wise. This is a significant price difference. I have watched several review videos and have read through several threads about the two and I am finally on the verge of buying the MSO5074.I have few questions about the MSO5074 that I would like to ask. Based on original review video from Dave and comparison video on YouTube between the two scopes by a user named “Nezbrun” in 2020, and several other bug reports in forums, I am wondering1. If the firmware updates have solved most of the initial bugs and UI responsiveness issues, since it has been more than 3 years.2. Are there are any major/minor remaining bugs that still needs to be addressed and I should be aware of prior to purchase. Please let me know.Next, more importantly, since this will be my very first oscilloscope for casual / hobby use. I will be learning it while using it. Even though, I have engineering background, I don’t have much hands-on experience with using oscilloscopes before, I would like to ask3. Once I receive the Oscilloscope, is there a list of some common / basic tests that I can do to verify the proper functionality of the oscilloscope upon receiving. If possible, please highlight some basic / quick tests that I can do to verify this. For peace of mind, I would like to ensure that the Oscilloscope I received is functioning as intended and does not have any hardware related issues. Any help is greatly appreciated.Thank you

author: Martin72
author_rank: Super Contributor
timestamp: September 04, 2022, 09:49:47 pm
content: Hi,https://www.eevblog.com/forum/testgear/siglent-sds1104x-e-vs-micsig-sto1004-plus/msg4388230/#msg4388230Martin

author: vicki20july
author_rank: Contributor
timestamp: September 04, 2022, 10:09:30 pm
content: Hi MartinThank you very much for the post and your experience. It is very informative.What about the 200 Mhz probes if i upgrade the Siglent to 500 MHz. Would they still hold or I would need to buy new more expensive ones above 200 Mhz measurements. I believe the MSO5074 comes with 350 MHz probes. Does this make any meaningful realistic difference in performance, comparison wise.Also what is your opinion on the 8Ga/s vs. 2Ga/s. Is this really a limitation for Siglent when put to real world use or compared against MSO5000.Thank you

author: Martin72
author_rank: Super Contributor
timestamp: September 04, 2022, 10:39:34 pm
content: Hi,Your questions would fit better in the thread I´ve posted before...Nevertheless:All depends on what your needs are..At work we got some elder lecroy scopes which are having max. 1GSa/s and 500Mhz bandwith and we aren´t having any problems with it at all.Because our needings won´t reach the "spheres" where this could make a difference.Same by me in private.Same what the probes concerns.

author: tautech
author_rank: Super Contributor
timestamp: September 04, 2022, 10:59:37 pm
content: Quote from: vicki20july on September 04, 2022, 10:09:30 pmAFAIK all 4 channels in MSO5000 are processed by one ASIC which sampling rate gets divided down by the # of channels active.SDS2000X Plus has two, yes two 2GSa/s ADC's so if an input is assigned to each ADC the max sampling rate in unaffected.Therefore with 4ch active sampling rate is 1GSa/s, sufficient to meet Nyquist at 350 MHz but not at 500 MHz where the SW dictates it to be a 500 MHz 2ch DSO or if 4ch must be used restricts capability to 350 MHz.On each active channel tab this info is displayed for the user to be fully informed of how the scopes is configured.

author: vicki20july
author_rank: Contributor
timestamp: September 05, 2022, 12:31:22 am
content: ok thank you both of you for the info. Now you guys got me thinking about the Siglent again. Will make my decision in next couple of days. Can anyone please answer my point no. 3 above. Repeated here."Is there a list of some common / basic tests that I can do to verify the proper functionality of the oscilloscope upon receiving. If possible, please highlight some basic / quick tests that I can do to verify this. For peace of mind, I would like to ensure that the Oscilloscope I received is functioning as intended and does not have any hardware related issues. Any help is greatly appreciated."Thank you All

author: Fungus
author_rank: Super Contributor
timestamp: September 05, 2022, 01:09:47 am
content: Quote from: Martin72 on August 29, 2022, 10:09:19 pmIt's not $400 more at the moment, but... that about sums it up. Youcouldstop reading there.Quote from: tautech on September 04, 2022, 10:59:37 pmIt never has more than half of the Rigol.You can use the extra sample rate on the Rigol reduce noise by oversampling. This is a new feature added in a firmware update (it happens!) so it makes all older threads that discuss noise less valid.It won't ever be as good as the Siglent, noise-wise, but how much the noise affects you depends on what type of signals you''re looking at. If the signal can be made as big as the screen then it makes no real difference. It's only a problem when the signal is tiny compared to the screen.TLDR; If you mostly work on digital signals then don't worry.People will go on and on about "power supply ripple" but some people might say that if ripple is too small to see on an MSO5000 then it's not really worth worrying about.The Siglent is obviously better, but ... it's 70% more money right now. If that's a lot of money to you then take a moment to think what else you could spend that money on.Quote from: vicki20july on September 05, 2022, 12:31:22 amPower it on.Run self-cal, see if it finishes.Connect all 4 probes to the test signal, see if it's there.Switch between DC and AC coupling on each channel.Turn the vertical up and down and listen for relays clicking (I think theybothhave relays, right? Correct me if I'm wrong)Press all the buttons, twist all the knobs.

author: tautech
author_rank: Super Contributor
timestamp: September 05, 2022, 01:13:29 am
content: Quote from: vicki20july on September 04, 2022, 09:40:45 pmYour very first scope and respectively may I ask what qualifications and equipment you might have to put a modern oscilloscope through its paces ?Then consider all are built to a design brief yet the model you buy may not be the top model is that series and instead a lesser model with its capabilities restricted by SW, however even when this is the case BW traditionally exceeds that stated on the label, normally by 10-20% but sometimes to a substantial degree as I discovered when checking the -3dB BW of the very first SDS2104X Plus we received that instead of a little above the 100 MHz label as one would expect it was actually ~185 MHz !So astonished I was I checked it again with 2 further signal sources before posting about it here a couple years back.Then if we are to check amplitude accuracy, how ?Scopes typically offer+3% vertical accuracy which is not a particularly challenging specification however it is typically over their entire frequencyandattenuation range, and not just a DC value.When you could maybe use a AWG but then how do we know its output is level over its frequency range which perfectly demonstrates this stuff gets hard.....and fast !Good luck with your decisions.

author: Fungus
author_rank: Super Contributor
timestamp: September 05, 2022, 01:25:55 am
content: Quote from: tautech on September 04, 2022, 10:59:37 pmDoes it have a 350Mhz low pass filter in the front end or is it up to the user to understand why the displayed signal is wrong?

author: tautech
author_rank: Super Contributor
timestamp: September 05, 2022, 02:07:01 am
content: Quote from: Fungus on September 05, 2022, 01:25:55 amAs written that you chose to delete:On each active channel tabthis info is displayed for the user to be fully informedof how the scopes is configured.As you should know BW capability is controlled in the analogue section of the input and normally in the same IC that provides 20 MHz limiting which notification also appears in the channel tab when it's engaged.So this IC controls label BW and depending on how it's SW controlled the signal pass integrity and user indication of what the scope is actually doing so the user can decide how best to use it.For SDS2000X Plus channel tab BW indications are as follows:Full = Max label stated BW for the model350 = 500 MHz model with 2 active channels on either ADC. (auto BW limit to meet Nyquist)100 = 10 bit mode engaged.20 = BW limiter engaged.

author: vicki20july
author_rank: Contributor
timestamp: September 05, 2022, 02:24:13 am
content: Quote from: Fungus on September 05, 2022, 01:09:47 amThank you all for the replies. Just wondering, Fungus is it there any video showing this functionality / improvement or is it documented anywhere. Is it a respectable improvement.

author: Fungus
author_rank: Super Contributor
timestamp: September 05, 2022, 09:42:04 am
content: Quote from: vicki20july on September 05, 2022, 02:24:13 amIt's called "high res" mode.nb. The video also shows also color grading mode which can use "averaging" mode to highlight the true signal inside the noise by averaging various waveforms together.If you mess around using the two techniques you can probably find what you're looking for.Siglent owners will counter that they don't need to "mess around", which is true. Again: It all comes down to what you're going to be using your 'scope for. FUD is an easy thing to spread here.Difference between high res and averaging:

author: 2N3055
author_rank: Super Contributor
timestamp: September 05, 2022, 12:02:01 pm
content: Quote from: Fungus on September 05, 2022, 09:42:04 amC'mon Fungus, we had lengthy discussions (plural) about that first Rigol video and Hires mode in general.First, that first video from Rigol is wrong and misleading. They abused fact that Rigol MSO5000 has better overdrive recovery than RTB2000 (which is a shame they didn't point that out because it is very important parameter), but choose to fake less noise by using that. Also it is pointless anyways, because despite better recovery it still distorts signal so it is not to be trusted anyways. Also it is misleading (and wrong) changing vertical sensitivity and offset and call that "zoom". Zoom is just that: graphic zoom on the screen without messing with input channel settings, but that is not so useful for 8 bit scopes as for scopes with higher resolution.As for Hires, it IS NOT replacement, fix, or solution for high noise in input channel of the scope. Hires uses filter that filters high frequencies out. That way it filters out noise energy in those high frequencies, leaving just low frequency noise. Which makes residual noise smaller and only fraction of full range noise.It does that by using Hires to make a 350 MHz scope a 50Mhz or 20Mhz or 500kHz scope, depending on how much bits of Hires you apply. If you only do audio range, that might not matter to you. For everything else it is a problem. Because of this it is very important that user have control of how much Hires is applied, because that defines lowpass filtering effect.That is one problem. Other is: other scopes, including ones with much better frontends, have their own version of Hires..And some scopes have less noise than MSO5000 with Hires, even when working full range 500MHz. Just think how low noise those get when you apply Hires on those...A note: we also had many (some heated) discussions of how important the scope noise is in general. A short version is that it is very important if you work on devices that need low noise measurements. If you only work on stuff that is digital level and you generally only need to look at general waveforms etc, it might not be important. It is up to user and user's work. But if low noise measurements are needed, there is no trick or fix to an noisy instrument. Only solution is a low noise instrument (scope).Just making facts straight.Best,

author: Fungus
author_rank: Super Contributor
timestamp: September 05, 2022, 12:56:16 pm
content: Quote from: 2N3055 on September 05, 2022, 12:02:01 pmI didn't post if because of that. I posted it because there's a clear moment where hires mode is turned on and yu see the difference. The color mode is also interesting/useful and it's shown clearly.Quote from: 2N3055 on September 05, 2022, 12:02:01 pmI specifically said that it wasn't, but itdoeshelp.Quote from: 2N3055 on September 05, 2022, 12:02:01 pmHuh? If you're sampling at 8GHz then you have multiple samples within each 350MHz time period. Averaging them won't make the bandwidth less then 350Mhz, it simply reduces the noise inherent in the ADC process.

author: Fungus
author_rank: Super Contributor
timestamp: September 05, 2022, 01:51:08 pm
content: Quote from: 2N3055 on September 05, 2022, 12:02:01 pmIn practical terms: That's what you'resupposedto do. Whenever you're measuring power supply ripple (or whatever) you're supposed to use 1x probes and limit the bandwidth to 20Mhz.Speaking of practicality; There's also the fact that looking at 350Mhz signals is something you only do with 50 Ohm cables, etc. If you're poking at circuits with probes then it simply isn't going to happen, you'll be lucky to be seeing anything over 100Mhz. 16x oversampling with pokey probes is probably going to show you something a lot closer to the truth than leaving it at full bandwidth.So again, the "depends on how you're planning to use it" clause comes into play. I'm not doubting the noise is better on a Siglent, I'm pointing out that inpracticalterms, it's not as big a deal as it might sound.(Yes, you have to fiddle around optimizing the amount of samples...but most people will only do it on edge cases, not all the time)

author: 2N3055
author_rank: Super Contributor
timestamp: September 05, 2022, 08:21:17 pm
content: Quote from: Fungus on September 05, 2022, 12:56:16 pmHires is not averaging. Averaging is useful only for repetitive, low phase noise (low jitter) signals.Hires is lowpass filtering.Single channel calculations (for 2 ch divide by2, for 3 and 4 channels divide by 4)For 1 bit improvement BW is 0,238 (1/4) of original Nyquist (8GS sample rate, 4GHz Nyquist effective 1GHz 1 h/250MHz 4ch).For 2 bit improvement BW is 0,0625 (1/16) of original Nyquist (8GS sample rate, 4GHz Nyquist effective 250MHz 1ch/62.5MHz 4ch).2 bit improvement is roughly what MSO5000 need to show similar RMS of noise to RTB2000 or SDS2000X+.For 3 bit improvement BW is 0,0625 (1/64) of original Nyquist (8GS sample rate, 4GHz Nyquist effective 15.625MHz 1ch/3,9MHz 4ch).So you could say that 1 bit improvement would be transparent , like you say. But not more, and since it has much more noise to begin with, it is not enough.In practical terms, you DO NOT filter signal unless you want to do that deliberately because you only want to look at partial signal. Or shall I say, I was always missing MORE bandwidth not less.Or I could just say your are right. It doesn't matter, and we should all just stop using any scopes with more than 20 MHz BW because it is all just some unwanted interference we don't care about anyways.And I'm fine with your characterisation that if run lowpass filtered it is a fine normal noise scope. Except Rigol should be selling it as a 50 or 20 MHz scope because that how it's going to get used.MSO5000 is good scope for the price. It has a noisy front end, but has many features that make it useful instrument. That isdespitethe fact that is a bit noisy, not because noise is irrelevant. It is not unusable, but its noise figures are not good. If that is important for user, then it is.Like I said.I know you are trying to simplify it for a beginner, but you can't. One of the biggest problems of the beginners is not lack of answers but a lack of good questions. They simply cannot formulate their needs because they don't have enough data and knowledge.That is why, for beginners, I tend to recommend some of the simpler, cheaper scopes. Today's entry level scopes like the SDS1104X-E or equivalents can carry a beginner for many years. Heck, they can do for a professional for most routine tasks... After many years, if they keep the hobby, they will know where to go from there... They are also easier to learn how to use, where we see that even professionals coming from CRT analog scopes need quite some time to learn how to use digital scope to its full extent.

author: Fungus
author_rank: Super Contributor
timestamp: September 05, 2022, 11:55:18 pm
content: Quote from: 2N3055 on September 05, 2022, 08:21:17 pmIt's a calculation done on adjacent samples. It might be the mathematical average, it might be a FIR filter, we don't know.Wedoknow it's done in an FPGA with steps of 2x, 4x, 8x, 16x so I'm leaning towards "averaging".Quote from: 2N3055 on September 05, 2022, 08:21:17 pmThat usage of the word "averaging" isn't what was meant here, and you know it.Quote from: 2N3055 on September 05, 2022, 08:21:17 pmThat's the worst case scenario.Quote from: 2N3055 on September 05, 2022, 08:21:17 pmSo with 1 channel enabled you can get as good as a Siglent (16x oversample, 500Mhz NYquist). Even with two channels enabled you can still get very close (8x oversample, 500Mhz Nyquist).Quote from: 2N3055 on September 05, 2022, 08:21:17 pmOr we can be grownups and admit that most signals in daily life simply aren't so small that we need to doanyof this. This makes for a nice bullet point on the sales brochure but it's mostly an edge case.

author: 2N3055
author_rank: Super Contributor
timestamp: September 06, 2022, 07:12:08 am
content: Quote from: Fungus on September 05, 2022, 11:55:18 pmHires can be implemented only one way. As a filter, of whatever implementation you chose. But result is same, lowpass filtering of current sample buffer.If it is not implemented that way then it is not Hires, but something else. Simple. So we know exactly how it's made.And it creates BW limiting.Also averaging is averaging. That is also term that is well defined in this context. In this context it means repetitive triggers and combining (averaging) multiple buffers on top of each other. It does not create BW limiting and can be used to extract signals that are autocorrelated and in a fixed timing to trigger from noise. Signals have to be stable and repetitive.I calculated whole table to show how rapidly BW drops and how it drops to very low bandwidth if you try to use Hires to actually have some usefulness from it. From it you took one data point and proclaimed victory.. Numbers are if you run at fastest sample rate. If you go with slower timebases and scope decides to drop sample rate BW will drop too.Problem with Hires that is annoying thatBW changes all the timein seemingly unpredictable ways. Every time you change timebase sample rate might change. You enable or disable a channel it changes. You change how much Hires, it changes. You change memory size it might change. You end up with a scope that has "random" BW. What it does is that signal on the screen changes all the time. Looking at I/O pin on Arduino, signal risetime will vary from 1ns to 5 ns depending on Hires. You go slower timebase, it will drop slower than that.That is confusing as hell.Expectation from the scope is that BW won't change with you twiddling knobs and signal won't look different at different setting of timebase.Hires is aspecialacquisition mode. Like peak detect mode it is there for special occasions.Yes we could behave like adults. And admit that you are wrong. You are pushing that worse specification of a specific device are not important to all and everybody, because you are of the opinion that it doesn't matter because everybody out there is doing same thing as you, apparently.Signals in real life are absolutely small and large and all in between. All together on a same scope screen.What are you saying, that we don't need vertical sensitivities better than 100mV/DIV, and scopes faster than 50Mhz?I said many times, if you are doing only digital level signals, on low speed digital, MSO5000 is going to do good job for you. In it's price class it is a decent device for that kind of work. It has few quirks, but it will do that work.If you want to look at analog domain properly, on mV level signals, any number of devices (including cheaper ones like Micsigs, SDS1104X-E, hires Picos etc) are going to be better for that. Tool for the job.Stretching that to a statement that it makes it same as a devices with much better specs is what is wrong in your efforts. These workarounds might work for you, for the stuff you do. Good for you and enjoy. That doesn't make it universal truth. Just workarounds that happen to be good enough for you.

author: Fungus
author_rank: Super Contributor
timestamp: September 06, 2022, 12:03:33 pm
content: Quote from: 2N3055 on September 06, 2022, 07:12:08 amI've said many times that it isn't the same.What I'm saying is that prices aren't equivalent (70% more) and that those "workarounds" will do the job for many people.To use a car analogy: Asking for oscilloscope buying advice on EEVBLOG is like asking for car buying advice at a drag strip or a BMW-owners club. The answers you get will be skewed.Yes, you'll have to fiddle around to get to see a really low level signal on a Rigol. If it's only occasionally though, where's the problem?Quote from: 2N3055 on September 06, 2022, 07:12:08 amLooking at mV signalsisa special occasion for many people. Don't pretend it isn't.(bites tongue to not go down the "Siglents seem to think that zooming out is a 'special occasion' " path)Quote from: 2N3055 on September 06, 2022, 07:12:08 amPot, kettle.The person asking the question a person who is buying a"very first oscilloscope for casual / hobby use". With the money saved they could buy a multimeter+soldering iron+hot air gun+power supply. Which is a better investment right now?A Rigol can always be sold later on if OP discovers they'rereallyinto mV signals. They keep their valueverywell.PS: What do Siglent owners do when they need to see a 0.1mV signal?

author: tv84
author_rank: Super Contributor
timestamp: September 06, 2022, 03:01:29 pm
content: Quote from: Fungus on September 06, 2022, 12:03:33 pmOTOH, should it be guests only? That's the responsibility of the searcher to distinguish. I could ask for car advice in a pharmacy but is it the pharmacists fault that the advice was biased?

author: Fungus
author_rank: Super Contributor
timestamp: September 06, 2022, 03:22:51 pm
content: Quote from: tv84 on September 06, 2022, 03:01:29 pmOf course not. You can go there to see what it's all about and discover the pros/cons but you don'thaveto come away owning one.Toyotas are perfectly driveable and can get to your destination for a lot less money. The need to get down a 1/4 mile in 10 seconds is a specialist need. The massaging seats and little robot arm that hands you your seatbelt when you sit down are nice but they aren't a necessity.Quote from: tv84 on September 06, 2022, 03:01:29 pmTo do that:a) They need to hear both sides.b) They probably need to have some oscilloscope experience under their belt to pick features based on how they used one in the past.Edit: Suggestion: Go to a Rigol MSO5000 owners club and listen to them talk for a while.

author: jord4231
author_rank: Regular Contributor
timestamp: September 07, 2022, 09:29:06 am
content: Thought I'd leave this here for anyone interested.Window triggering bug anyone else experienced it?https://youtu.be/Fg9eL_EKgmECheers

author: mironex
author_rank: Newbie
timestamp: September 12, 2022, 08:39:53 pm
content: Quote from: Gandalf_Sr on March 31, 2021, 03:29:22 pm"Better late than never"Finally, I bought my MSO0574. Thanks for the help :-).

author: Tommy_Vercetti
author_rank: Contributor
timestamp: October 30, 2022, 03:23:10 am
content: 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.

author: Tommy_Vercetti
author_rank: Contributor
timestamp: October 30, 2022, 03:42:03 am
content: 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?

author: teddychn
author_rank: Regular Contributor
timestamp: October 30, 2022, 04:14:10 pm
content: QuoteI'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.

author: Piasecznik
author_rank: Newbie
timestamp: November 07, 2022, 01:15:57 am
content: About noisy digital scopes.

author: tautech
author_rank: Super Contributor
timestamp: November 07, 2022, 01:25:25 am
content: Quote from: Piasecznik on November 07, 2022, 01:15:57 amWelcome to the forum.An 8 year old video is not representative of today's DSO's and there was a Pt2 as the original didn't cover everything.Then there are Why Digital Scopes Appear Noisy and others that don't.Each must be judged on their own merit.

author: mironex
author_rank: Newbie
timestamp: November 07, 2022, 08:09:52 am
content: Quote from: Tommy_Vercetti on October 30, 2022, 03:23:10 amI have a similar experience.

author: Piasecznik
author_rank: Newbie
timestamp: November 10, 2022, 08:29:20 am
content: Got mine yesterday.FW 1.03.0.03 build 2021-10-18Quite annoying bug:Added measurements to channel are measuring based only on displayed datapoints but are not dependent on trigger.Counter on other hand is measuring based on all gathered datapoints even for disabled channel but is dependent on trigger and "Reject noise" setting. For example without noise reject it can show inaccurate frequency.Unit have tendency to stop registering all user input in Zoom mode. Happened to me twice in few hours of testing.About point no 17 in the bug list - as per RTFMwaveform save in *.wfm format is possible only when source is selected to be Memory. WFM format is not available when saving waveform from Screen.

author: thm_w
author_rank: Super Contributor
timestamp: November 10, 2022, 10:18:20 pm
content: Quote from: Piasecznik on November 10, 2022, 08:29:20 am

author: Piasecznik
author_rank: Newbie
timestamp: November 11, 2022, 01:58:29 am
content: Yeah, all good and dandy but he mentions that counter is dependent on trigger which is opposite what I found in Rigol, and do not mention anything on what window those two methods uses.Thanks for video. It is always good to learn something more.

author: imolnar
author_rank: Newbie
timestamp: January 13, 2023, 06:30:36 pm
content: Hi,Please someone help!I have an mso5074. When I connect LA there is no message.All digital channels indicate permanent GND. If I touch PIN1 to GND, it doesn't detect that either. Without load, PIN1 is 0.6V.What to do?

author: jeffjmr
author_rank: Regular Contributor
timestamp: January 16, 2023, 02:55:40 am
content: Searched for this but no joy.Does anyone know the output impedance of the AWGs?Thanks,Jeff

author: tautech
author_rank: Super Contributor
timestamp: January 16, 2023, 03:17:43 am
content: Quote from: jeffjmr on January 16, 2023, 02:55:40 amNormally just 50however most also allow for a HiZ load but impedance doesn't change for that only a amplitude adjustment to better suit HiZ.This why AWG amplitude spec is double into HiZ of into 50

author: NE666
author_rank: Frequent Contributor
timestamp: December 03, 2023, 01:19:21 pm
content: I've had my MSO5k for a few months now and every now and again, I observe what feels like abnormal behavior with the trigger level cursor.There are no problems at boot time and mostly, none throughout my work period. However, sometimes the orange cursor on the vertical axis which denotes the currently set trigger level disappears and I'm unable to find a way to restore it. Triggering continues to work as expected, the level knob causes the displayed numeric value in the trigger menu bar (top RHS of screen) to update as expected, there's just no on-grid cursor.I'm unable to offer steps to reproduce, since by the time I've noticed it has gone the Last Known Good condition is behind me as is the precise sequence of operations that follow. It's also, as I say, infrequent.Does anyone know the reason and the solution? Loath to call it a bug at this point, as I've seen no other posts mention it. Likely to be something I am doing but I can't figure out what.FW 00.01.03.03.00Thanks in advance.TIA

author: Pulsepowerguy
author_rank: Regular Contributor
timestamp: December 03, 2023, 05:53:44 pm
content: FWIW, I have 00.01.03.00.03 and I have not noticed this behavior

author: ebastler
author_rank: Super Contributor
timestamp: December 03, 2023, 06:42:12 pm
content: Quote from: NE666 on December 03, 2023, 01:19:21 pmAny chance you have switched the trigger coupling to AC or LFR? There is no defined DC relationship between the signal and the trigger threshold then, so the orange level indicator gets disabled.

author: NE666
author_rank: Frequent Contributor
timestamp: December 03, 2023, 09:30:44 pm
content: Quote from: ebastler on December 03, 2023, 06:42:12 pmNot intentionally, not to my knowledge. Is there any easy way that I might do so inadvertently, other than explicitly calling for it through the trigger menu? Is this setting linked to any other(s)?

author: ebastler
author_rank: Super Contributor
timestamp: December 03, 2023, 09:58:33 pm
content: Quote from: NE666 on December 03, 2023, 09:30:44 pmI don't have an MSO5000 myself, only a DS1054Z (which does show the same behavior). I am not aware of other settings which would implicitly activate AC or LFR trigger coupling. The coupling setting is linked to Edge trigger mode, but in a way which is "harmless", at least the way it is implemented in the DS1054Z:Edge trigger is the only mode which is affected by the trigger coupling. When you switch to a different trigger mode, AC/LFR trigger coupling is no longer active. On the DS1054Z, the trigger coupling falls back to "DC" when you go back to Edge-trigger, even if you had selected AR/LFR when you last were in Edge-trigger mode. Maybe the MSO5000 is "smarter" in that situation and remembers the last coupling setting, i.e. reactivates AC/LFR coupling when you switch back to Edge trigger mode?

author: NE666
author_rank: Frequent Contributor
timestamp: December 04, 2023, 08:58:54 am
content: Quote from: ebastler on December 03, 2023, 09:58:33 pmIndeed, it does. Otherwise the implementation is as you describe for the 1054Z.For the time being I'll put what I'm observing down to fat fingers at the controls and monitor the situation. Thanks for your input.

author: RobbiTobi
author_rank: Contributor
timestamp: January 25, 2024, 06:18:42 pm
content: Hi guys,could anybody help me out on finding an encoder replacement part for my MSO5000?I have a defective dented encoder which is annoying me so muchMany thanks!

author: AxeMan
author_rank: Newbie
timestamp: March 03, 2024, 10:26:11 am
content: Hello MSO5000 users,I have several questions which are not answered by the manual.1. Is it possible to switch off the sinx/x interpolation to see the raw sampled data points on the display?2. It is my first oscilloscope and the behavior of cursors is strange for me. On MSO5000 the cursors stayson the screen when I change the timebase, so when two event is far from each other and if I would like tomeasure the time difference between them, that needs both event on screen. The result of this that theaccuracy/resulolution low and based how accurate can I put the cursor to the even.I use often logic analyzers where (during time measurement) the cursors stick to the point where I put them,regadless the zoom or timescroll. I zoom in, put the cursor to the first event, zoom out, I find the second evetzoom in and I put the cursor to the second event. That produces a precise time difference measurement.It is possible to use the MSO5000 cursors on the same way?It it usual that the oscilloscopes' cursors work that way or it is a MSO5000 specific?I noticed that the software update rate of this scope quite slow. Worth to communicate the problemtowards Rigol, do they usually care of this inquries of the users?I appreciate any response,Thank you.

author: ebastler
author_rank: Super Contributor
timestamp: March 03, 2024, 03:38:46 pm
content: Quote from: AxeMan on March 03, 2024, 10:26:11 amSee the chapter on "Display Control" in the manual. In the online copy I found, it's the first section of chapter 16, "Display Type".QuoteIt's certainly the standard behaviour of oscilloscope cursors to work in the screen region only; I am not sure whether some brands offer alternative modes. If you can use an automated measurement instead of cursor readout, that will typically take a lot of uncertainty away.To precisely measure time delays between two events which you need to select manually, reading the delay time instead of using cursors may be more precise: Zoom in (on the time axis) onto the first event, position it e.g. on the central vertical grid line via the horizontal delay control, and take note of the Delay readout on the screen. (I.e. the time delay from trigger event to centered event.) Then repeat the same with the second event and take the difference of the two Delay times.QuoteYou mean the response to user interactions like turning the position knobs? I'm afraid what we get there is the best the CPU can do. Compared to other DSOs it is "par for the course" -- not something to brag about, but some competiting scopes are doing worse.Rigol is certainly aware of the limitations; but given how long the MSO5000 has been on the market, I would not expect that they can (and/or want to) improve this.

author: 2N3055
author_rank: Super Contributor
timestamp: March 03, 2024, 05:24:08 pm
content: Quote from: AxeMan on March 03, 2024, 10:26:11 amOn Siglent touch scope series you can do exactly that but in zoom mode:You capture long, enable zoom, go to first event and position cursor there while magnified, go to the other event, do the same, and you have full accuracy.Maybe MSO5000 can do something similar?

author: Verticon
author_rank: Contributor
timestamp: March 16, 2024, 09:35:40 pm
content: Hello MSO5000 users,I have my MSO5000 already several years but these days I used it the first time in "power analysis" mode in order to measure power factor etc. and observed a problem where I wonder if its a bug or if I am not able to use the scope reasonably. Unfortunately the manual is here not very helpful. When I connect e.g. a 1kHz sine signal to both channels 1 and 2 the "Measure" function window shows the correct phase difference of about zero. On the other hand the "power analysis" window shows roughly 7 degrees difference. This is independant if I change the frequency or amplitude of the signal.The same behaviour shows up when I use 2 identical signals from the internal awgs with a zero phase difference. The strange thing is when I increase the phase difference of awg 2 from 0 to e.g. 40 degree both function windows show the identical value of roughly 40 degrees. It seems that the 7 degrees is not a simple offset but it successively decreases by increasing phase difference between the two channels.The pictures below show the described behaviour. First picture with phase difference 0 and the 2nd with 40 degrees.Has anybody made a similar experience or an explanation for this behaviour? I am sorry to say but with this behaviour the power analysis is useless. Only thing I can do is to write a python script and use the "Measure" values.

author: core
author_rank: Regular Contributor
timestamp: March 23, 2024, 06:54:23 pm
content: I tried it myself, with the internal generator but also with an external generator.I tried different waveforms, amplitude and DC offset.The results are the same, below 20 degrees the errors are getting bigger and bigger.Below about 7 degrees it doesn't decrease regardless of the settings.Doesn't inspire much confidence.

author: passenger54321
author_rank: Newbie
timestamp: November 06, 2024, 09:05:16 pm
content: Hi,When trying to script for the statistics mode of my MSO5074, I ran into the following observation.User issue or bug?The goal is reading the noise level (Vrms) statistics for the different vertical ranges.For completeness, I am using the following SCPI command which is not listed in the programming manual.Not sure though if it is hidden for a reasonSetting the moving average window (in display: Measure -> Statistics -> Counter):MEASure:STATISTIC:COUNTrange probably [10..100000]This one exists once for all up to 10 ITEMsSo, I am setting :MEASure:STATISTIC:COUNT to 10.The issue I am observing is that the reset does not completely reset for larger time base settings e.g. 1 sec / div.So after a:MEASURE:STATISTIC:RESETI am waiting until:Measure:Statistic:Item? Cnt, VRMSreaches the value of above COUNT, so I know the window is full.(and yes, the Cnt comes back as a scientific E-notation float, but should be int. And this is not my main issue)While waiting, I can see on the display that the first [1..5] values in the statistics box are still from the previousmeasurement (from before the reset). The # is somewhat random; mostly 1So, when next calling:Measure:Statistic:Item? AVerages, VRMSthe average is wrong.After every measurement cycle, I am completely erasing the measurement ITEMs like this::Measure:Statistic:Display OFF:Measure:Clear ALL:Channel' + str(active_channel) +':Display OFFIs this behaviour known and understood? Any workaround available?Thanks for taking the time to look into the topic.And thanks to thm_w. As suggested, I am moving the entry to this topic-UlrichP.S. with regards toPresumably the workaround would be to read Vrms every trigger, run that ten times, and average the result?-> Yes, this was my first approach. But, runtime.... I stopped it after three days, and still not complete. So, saw the statistics are much faster.Next try would be to make statistic from RMS and RMS from the waveform reading. Howerver this is another issue, let me investigate it before I post nonsense.

author: Bill3745
author_rank: Contributor
timestamp: December 09, 2024, 09:15:29 pm
content: Has anyone verified the amplitude flatness of their built-in AWGs? The spec states +/- 0.5 db from a 1 KHz reference, but mine drops closer to 1 db when cranked all the way up to 25 MHz. Both 50 Ohm (properly terminated) and HighZ were tested with similar results, although it seems to do slightly better on HighZ. I ruled out cable, terminator and scope by running a similar test with a known good external AWG.Scope is a 5074 purchased in late '21 running on current 1.03.03 unpatched firmware.

author: sorenkir
author_rank: Regular Contributor
timestamp: December 11, 2024, 04:22:17 pm
content: Hi,I have checked generator 1 on my MSO5074.The graph is below.G1 @ 1Vpp, 50 ohm cable and termination, measured with a HP3403C.Michel.

author: Bill3745
author_rank: Contributor
timestamp: December 11, 2024, 04:42:28 pm
content: Quote from: sorenkir on December 11, 2024, 04:22:17 pmThanks so much. Roll off looks fairly similar to what I am seeing and not to the spec of +/-0.5 db. Not a big deal as I wasn't expecting a ton of accuracy from the built in AWGs, but annoying that it doesn't meet their published spec. Really just wanted to see if my unit was an anomaly.

author: Bill3745
author_rank: Contributor
timestamp: December 12, 2024, 08:12:30 pm
content: Quote from: sorenkir on December 11, 2024, 04:22:17 pmAs a point of comparison here is a plot of my G2 with similar settings, but measured directly on the scope.

author: nephilim
author_rank: Newbie
timestamp: February 19, 2025, 04:14:31 pm
content: Not sure if this is the correct place to post. I wanted to share an issue I ran into, which might be a bug or simply my incompetence:Pass/Fail analysis on the MSO5074. How everybody except me would do it:Adjust display and press "single" to freeze the waveform to be used to create the maskEnable PF analysis, create the mask, select information window and the required optionsPress play button to start the analysisThis automatically switches from single to continuous measurement and the PF analysis is done as expected.What I did and how I wasted my time throughout the past days is thisAdjust display and press "single" to freeze the waveform to be used to create the maskEnable PF analysis, create the mask, select information window and the required optionsPress Stop/RunPress play button to start the analysisThe latter seems to kill the PF analysis for the whole session, i.e., no event is counted, no beep (if selected), etc even though the signal clearly intersects the mask. Even if you then switch to the correct method the PF analysis would be in the faulty state. The device needs to be powered off and on. Not sure if this is covered in the manual or common knowledge over here.Now if somebody could tell me why admin/rigol does not work as default login to WebControl, even though it is shown in the scope's network information window and I resetted the scope (safe clear and restore defaults during booting), I would be really happy.Switched to VNC.