Author Topic: REVIEW - Rigol MSO5000. Tests, bugs, questions  (Read 73583 times)

0 Members and 1 Guest are viewing this topic.

Offline Fungus

  • Super Contributor
  • ***
  • Posts: 16682
  • Country: 00
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #300 on: September 05, 2022, 11:55:18 pm »
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.
Hires is not averaging.

It's a calculation done on adjacent samples. It might be the mathematical average, it might be a FIR filter, we don't know.

We do know it's done in an FPGA with steps of 2x, 4x, 8x, 16x so I'm leaning towards "averaging".

Averaging is useful only for repetitive, low phase noise (low jitter) signals.

That usage of the word "averaging" isn't what was meant here, and you know it.

So you could say that 1 bit improvement would be transparent , like you say. But not more

That's the worst case scenario.

For 2 bit improvement BW is 0,0625 (1/16) of original Nyquist (8GS sample rate, 4GHz Nyquist  effective 250MHz).

2 bit improvement is roughly what MSO5000 need to show similar RMS of noise to RTB2000 or SDS2000X+.

So 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).

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.

Or we can be grownups and admit that most signals in daily life simply aren't so small that we need to do any of this. This makes for a nice bullet point on the sales brochure but it's mostly an edge case.
« Last Edit: September 06, 2022, 12:06:26 am by Fungus »
 

Online 2N3055

  • Super Contributor
  • ***
  • Posts: 6666
  • Country: hr
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #301 on: September 06, 2022, 07:12:08 am »
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.
Hires is not averaging.

It's a calculation done on adjacent samples. It might be the mathematical average, it might be a FIR filter, we don't know.

We do know it's done in an FPGA with steps of 2x, 4x, 8x, 16x so I'm leaning towards "averaging".

Averaging is useful only for repetitive, low phase noise (low jitter) signals.

That usage of the word "averaging" isn't what was meant here, and you know it.

So you could say that 1 bit improvement would be transparent , like you say. But not more

That's the worst case scenario.

For 2 bit improvement BW is 0,0625 (1/16) of original Nyquist (8GS sample rate, 4GHz Nyquist  effective 250MHz).

2 bit improvement is roughly what MSO5000 need to show similar RMS of noise to RTB2000 or SDS2000X+.

So 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).

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.

Or we can be grownups and admit that most signals in daily life simply aren't so small that we need to do any of this. This makes for a nice bullet point on the sales brochure but it's mostly an edge case.

Hires 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 that BW changes all the time in 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 a special acquisition 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.
 

Offline Fungus

  • Super Contributor
  • ***
  • Posts: 16682
  • Country: 00
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #302 on: September 06, 2022, 12:03:33 pm »
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.

I'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?

Hires is a special acquisition mode. Like peak detect mode it is there for special occasions.

Looking at mV signals is a 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)

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.

Pot, 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're really into mV signals. They keep their value very well.

PS: What do Siglent owners do when they need to see a 0.1mV signal?
« Last Edit: September 06, 2022, 12:06:57 pm by Fungus »
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3222
  • Country: pt
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #303 on: September 06, 2022, 03:01:29 pm »
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.

 :-DD

OTOH, 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?
« Last Edit: September 06, 2022, 03:08:23 pm by tv84 »
 

Offline Fungus

  • Super Contributor
  • ***
  • Posts: 16682
  • Country: 00
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #304 on: September 06, 2022, 03:22:51 pm »
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.

OTOH, should it be guests only?

Of course not. You can go there to see what it's all about and discover the pros/cons but you don't have to 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.

That's the responsibility of the searcher to distinguish.

To 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.
« Last Edit: September 06, 2022, 04:08:23 pm by Fungus »
 
The following users thanked this post: thm_w

Offline jord4231

  • Regular Contributor
  • *
  • Posts: 91
  • Country: au
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #305 on: September 07, 2022, 09:29:06 am »
Thought I'd leave this here for anyone interested.
Window triggering bug anyone else experienced it?
 :popcorn:
https://youtu.be/Fg9eL_EKgmE

Cheers

Offline mironex

  • Newbie
  • Posts: 8
  • Country: pl
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #306 on: September 12, 2022, 08:39:53 pm »
Mironex, I just tried to PM you and found your inbox was full.

This is a thread you may be interested in https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2769676/#msg2769676

"Better late than never"
Finally, I bought my MSO0574. Thanks for the help :-).
 

Offline Tommy_Vercetti

  • Contributor
  • Posts: 11
  • Country: us
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #307 on: October 30, 2022, 03:23:10 am »
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.
 

Offline Tommy_Vercetti

  • Contributor
  • Posts: 11
  • Country: us
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #308 on: October 30, 2022, 03:42:03 am »
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?
 

Offline teddychn

  • Contributor
  • Posts: 46
  • Country: 00
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #309 on: October 30, 2022, 04:14:10 pm »
Quote
1. Low contrast, bad viewing angles of screen. It’s also not very bright. Seems to be Rigol scope’s family bug
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

2. Backlight of buttons is not bright enough (especially on 1’st channel button)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

3. Colors on screenshots are very, very different from what you see on screen
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

4. Windows on screen (DVM and Counter for example) are all different in size and don’t stick to each other, so it’s difficult to arrange them.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

5. Selected trigger mode has a very little indicator; single mode doesn’t indicate at all. Selected mode isn’t shown in trigger menu.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

6. In Dots mode you don’t see dots; even at small time base (2 ns) dots are connected with lines.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

7. In High Res mode signal is not less noisy then in usual Sample mode, although vertical resolution is higher
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

8. New measurement is added on the left and moves all other measurements to the right.  It would be more convenient if it adds on the left of others
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

9. You can select a separate measurement but you can only DELETE it and can’t change nothing else (source, measurement type). Measurement selection is almost invisible.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

10. There is no user-defined probe ratio – only pre-defined values. Thus it’s difficult to measure current on sense resistor.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

11. Strange behavior. Advertisement says it has more than 500 000 wfrm/s update rate. That’s true, but ONLY in single ch., 10ns time base mode (with AUTO memory mode).  Update rate dependence on time base and active channels’ number  looks very strange – for example, with 1 active channel and 20 ns time base you have 12 000 wfrm/s, but with 2 active channels and 20 ns time base you have 310 000 wfrm/s. (see update rate testing results below)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

12. With time base more than 20 ms, update rate is higher with 200 MPoints memory selected then with 1 kPoints. (see update rate testing results below)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

13. In AUTO memory mode scope don’t use more than 25 MPoints, although available memory is 200 MPoints.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

14. The way the scope collect data looks strange: packets of samples, separated by a long pause. Pauses between packets take up to 87% of all blind time. For comparison, Rigol MSO4000 collects data in series, sample by sample, without any packets.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

15. No internal 50 Ohm termination, though there is an inactive setting in channel menu.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

16. Offset about 250 uV with external 50 termination connected. Without termination (open input) – just 50 uV
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

17. Scope saves waveform only in *.bin or *.csv, but loads just *.wfm – you can’t load saved waveforms.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

18a. No frequency and magnitude axes in FFT mode
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

18b. FFT does not have MAX and Average
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

18c. FFT size is not shown (and could not been set)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

18d. Lack of Kaiser-Bessel Derived Window and Dolph-Chebychev Window, all these 2 windows with variable alpha.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

19. Scope has Eye Analysis and Jitter functions in Measure menu, but they are not mentioned in manual and seem non-working
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

20. Color Grade function is VERY dependent on waveform’s Intensity setting (display>intensity). At maximum intensity you’ll see all white waveform, at minimum – all black, actually without any color difference.  This feature is not mentioned in manual.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

21. Waveform Freeze function seems not working, and I don’t know what it should do.
It works: If you manually stop the acquisition, pressing "Stop", "Waveform freeze" keeps the display "as is" showing multiple waveforms overlaid (Just as if you would take a photo from an analogue scope). If you disable the option, manually pressing "Stop" just shows the trace from the last real-time acquisition. thx mimi
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

22. SCPI command ':LA:TCALibrate' doesn't do anything. This is something that should be a menu option on the scope, so maybe its not been implemented yet.
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

Code: [Select]
:LA:TCALibrate?
response: 0.000000
:LA:TCAL 0.000000100
:LA:TCALibrate?
response: 0.000000


:channel1:tcal 0.000000100 for example, works OK


23. Lack of interpolation mode selection (line or sinc)
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]

24. The trigger delay only works up to 535..537ms (the limit appears to have some sort of hysteresis) for fast sweep rates (<=200us/div, in single channel mode). For faster sweep rates it wraps around, e.g. 600ms equals sone 40ms delay)
Same for FW v00.01.01.04.04 and v00.01.01.04.08
[FW v00.01.01.04.04] / [FW v00.01.01.04.04]



I'm waiting for my MSO5074 delivery. For the sake of affordable price, characteristics of long memory, bode plot, power analyisis feature and high sample rate. I've known the high noise issue before placing the order. But I didn't aware that it doesn't come with amplifiers for the vertical ranges below 5mV/div. That's a pity. Just wish the Hi-Res mode could improve that a bit. And the power analysis features seem rough.

Regarding the bug 13, maybe it was the tradeoffs of refresh speed to not applying all the memory in auto memory mode. Regarding this point, I just wish it could use the full memory single acquisition mode. Maybe an option of high/mid/low speed mode could be considered for choosing high speed or high memory utilization here.

Also point 12 and 14 seem weired. I think it's important for Rigol to take it seriously.

I've seen the review on Amazon said the bugs are fixed. Wish that's true. I'm pinning my hope on it.




« Last Edit: October 31, 2022, 11:47:21 am by teddychn »
 

Offline Piasecznik

  • Newbie
  • Posts: 4
  • Country: pl
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #310 on: November 07, 2022, 01:15:57 am »

About noisy digital scopes.
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 28396
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #311 on: November 07, 2022, 01:25:25 am »
About noisy digital scopes.
Welcome 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.
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 
The following users thanked this post: Piasecznik

Offline mironex

  • Newbie
  • Posts: 8
  • Country: pl
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #312 on: November 07, 2022, 08:09:52 am »
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.

I have a similar experience.
 

Offline Piasecznik

  • Newbie
  • Posts: 4
  • Country: pl
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #313 on: November 10, 2022, 08:29:20 am »
Got mine yesterday.
FW 1.03.0.03 build 2021-10-18
Quite 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 RTFM ;) waveform save in *.wfm format is possible only when source is selected to be Memory. WFM format is not available when saving waveform from Screen.
« Last Edit: November 10, 2022, 09:21:45 am by Piasecznik »
 

Offline thm_w

  • Super Contributor
  • ***
  • Posts: 6389
  • Country: ca
  • Non-expert
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #314 on: November 10, 2022, 10:18:20 pm »
Got mine yesterday.
FW 1.03.0.03 build 2021-10-18
Quite 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 RTFM ;) waveform save in *.wfm format is possible only when source is selected to be Memory. WFM format is not available when saving waveform from Screen.

Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 
The following users thanked this post: Piasecznik

Offline Piasecznik

  • Newbie
  • Posts: 4
  • Country: pl
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #315 on: November 11, 2022, 01:58:29 am »
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.
 

Offline imolnar

  • Newbie
  • Posts: 7
  • Country: hu
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #316 on: January 13, 2023, 06:30:36 pm »
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?
 

Offline jeffjmr

  • Regular Contributor
  • *
  • Posts: 144
  • Country: us
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #317 on: January 16, 2023, 02:55:40 am »
Searched for this but no joy.

Does anyone know the output impedance of the AWGs?

Thanks,
Jeff
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 28396
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #318 on: January 16, 2023, 03:17:43 am »
Searched for this but no joy.

Does anyone know the output impedance of the AWGs?

Thanks,
Jeff
Normally just 50  \$\Omega\$ however 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  \$\Omega\$
Avid Rabid Hobbyist
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 

Online NE666

  • Regular Contributor
  • *
  • Posts: 72
  • Country: gb
Tigger Level cursor goes AWOL
« Reply #319 on: December 03, 2023, 01:19:21 pm »
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.00

Thanks in advance.


TIA
 

Offline Pulsepowerguy

  • Regular Contributor
  • *
  • Posts: 52
  • Country: us
Re: REVIEW - Rigol MSO5000. Tests, bugs, questions
« Reply #320 on: December 03, 2023, 05:53:44 pm »
FWIW, I have 00.01.03.00.03 and I have not noticed this behavior
 
The following users thanked this post: NE666

Offline ebastler

  • Super Contributor
  • ***
  • Posts: 6512
  • Country: de
Re: Tigger Level cursor goes AWOL
« Reply #321 on: December 03, 2023, 06:42:12 pm »
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.

Any 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.
 
The following users thanked this post: NE666

Online NE666

  • Regular Contributor
  • *
  • Posts: 72
  • Country: gb
Re: Tigger Level cursor goes AWOL
« Reply #322 on: December 03, 2023, 09:30:44 pm »
Any chance you have switched the trigger coupling to AC or LFR?

Not 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)?
 

Offline ebastler

  • Super Contributor
  • ***
  • Posts: 6512
  • Country: de
Re: Tigger Level cursor goes AWOL
« Reply #323 on: December 03, 2023, 09:58:33 pm »
Any chance you have switched the trigger coupling to AC or LFR?

Not 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)?

I 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?
 
The following users thanked this post: NE666

Online NE666

  • Regular Contributor
  • *
  • Posts: 72
  • Country: gb
Re: Tigger Level cursor goes AWOL
« Reply #324 on: December 04, 2023, 08:58:54 am »
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?

Indeed, 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.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf