:LA:TCALibrate?
response: 0.000000
:LA:TCAL 0.000000100
:LA:TCALibrate?
response: 0.000000
19. Scope has Eye Analysis and Jitter functions in Measure menu, but they are not mentioned in manual and seem non-working
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]
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]
:LA:TCALibrate?
response: 0.000000
:LA:TCAL 0.000000100
:LA:TCALibrate?
response: 0.000000
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.
Quote20. 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]
I 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: [Select]:LA:TCALibrate?
response: 0.000000
:LA:TCAL 0.000000100
:LA:TCALibrate?
response: 0.000000
:channel1:tcal 0.000000100 for example, works OK
Switch off/on, it still freezes.
Switch off, disconnect the lan, switch on, everything is OK.
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.
I don't think mine does that...
Nervertheless I´ve informed rigol.
When using the cursors try using measurement mode, mine just doesn't work, neither does it when in the jitter measurement mode either.Works here (after RTFM :D). Allows to enable or disable "indicators" for auto measurements.
...
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).Hi,
Interesting:
The measurements were taken with a 25Mhz Sine at 5ns/div.
But if you zoom out to 20ns/div AND with all channels on, the waveform rate increases to appx 200000...hm.
I cannot confirm the 500k wfm/s for 5ns/div here.
Not urgent, we cannot do much against the weird behavior anyway. Rigol is probably well aware of the issue and tries to address it.QuoteI cannot confirm the 500k wfm/s for 5ns/div here.
If desired, I will repeat the measure..
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).
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.
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 option menu open.
Syntax :SYSTem:SETup <setup_data>
contains 2506 bytes of effective data.
The "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).
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]
Cursors :
The horizontal and vertical cursor-lines are always together dispaying, you can´t choose between only vertical, only horizontal or both.
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.
save:format csv
save:csv:length maximum
for x in range(5):
:record:current x
:save:csv D:\x.csv
As I need to measure low currents
Hi all,
How is the current status of the firmware? Still too buggy?
Thanks
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...?
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.
- Working with AC coupling: When I short the probe, there´s a offset on the channel - Disconneting the probe, offset disappears…
Hi Sinpie
If 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.
Hi Sinpie
I had a quick check of one of our two 5000's over the weekend and it reads corrects with the Rigol 500Hhz probe
Will check the other later in the week for you.
QuestionHi Sinpie
I had a quick check of one of our two 5000's over the weekend and it reads corrects with the Rigol 500Hhz probe
Will check the other later in the week for you.
Thank 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 setting
Picture2. CH1 10x setting
Picture3. 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)
QuestionHi Sinpie
I had a quick check of one of our two 5000's over the weekend and it reads corrects with the Rigol 500Hhz probe
Will check the other later in the week for you.
Thank 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 setting
Picture2. CH1 10x setting
Picture3. 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)
With more waveform cycles on the display are the measurements then correct ?
Sinpie
I 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.
The best you will get out of a 5000 opened up is 470Mhz, the 7000 around 830Mhz
What is the noise floor performance? especially compared with Rigol DS2000A, Siglent SDS2000X?
The best you will get out of a 5000 opened up is 470Mhz, the 7000 around 830MhzIt sounds like true, but look at this picture
Yep, exactly same problem with the new firmware. The only workaround is to change the startup to the last state rather than the default.Thank you for the tip !
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?
Or extend 7000 BW by desoldering?How? It's serial RLC net.
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?
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?The 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.
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?
I 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.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?
When 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.
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?Try to connect probe tip to SG output case (ground). If you whatever see this spikes - problem is in EMC, if not - in SG signal.
:popcorn: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?Try to connect probe tip to SG output case (ground). If you whatever see this spikes - problem is in EMC, if not - in SG signal.
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
I 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.00Thanks, 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.
I presume it is a HDMI cable straight to the monitor in your case with no switch involved?
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?Wait a little)
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.It'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.
Is the HDMI monitor connected in prior to oscope before power on?I 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.
If it is not then it does not hurt to give it a try.
It looks like you have a faulty unit. Have you tried contacting Rigol USA?I 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.00Thanks, 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.
I presume it is a HDMI cable straight to the monitor in your case with no switch involved?
https://www.sigrok.org/blog/blog (https://www.sigrok.org/blog/blog)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?
Could you be more specific. Thanks
The 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.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?
https://github.com/sigrokproject/libsigrok/commit/f6129c8f0c92e45de5d70b4101bf2bd759a5fdf7
https://github.com/sigrokproject/libsigrok/blob/4c5f70063ad6ae311809ee7818ddc9070fbe05cf/src/hardware/rigol-ds/api.c
Should 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.
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…
I'm happy with mine. It's hard to get close to it in terms of value for money.
Its buried 3 levels down
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.
QuoteIts buried 3 levels downAnd this is imho a main problem of the UI...
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.
Powering 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...QuoteIts buried 3 levels downAnd this is imho a main problem of the UI...
Maybe it's not used often enough to deserve being at top level.
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)
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.Exactly, it's a probe compensation output FFS not some precision square wave supply.
I discovered MSO5000 is indeed susceptible to electrical noise and RF interference ..
... and set for a general 7.5Ghz sweep ...
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.
- is to put the ‘supply’ cable which plugs-into the main board through a large Ferrite Core for Power Supply Decoupling (see attached picture)
But 3.2 GHz is possible. ;)... and set for a general 7.5Ghz sweep ...
I wish (he says with envy) - not all of us are as fortunate to enter the 7.5Ghz club :P
Sorry I wasn't being funny 7.5Ghz is my lowest normal SA ...
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 ;)
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
Our 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
Yes and in made the messaurements with 1x Probe since the should Work Till 30MHz
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.For some reasons I thought that the grounds are internally connected and therefore it doesn't matter whether it's connected or not.
I try my MSO5074 "upgraded" scope on direct cable (without probe).
-3dB bandwidth is 630 MHz.
-6dB bandwidth is 700 MHz.
Do you mean hardware modifications? And are you going to post an updated frequency-response graph? :)I did not make any hardware modifications. May be slightly later)
Interesting resultsWhat 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?
Interesting resultsWhat 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.
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 :-\Nothing strange)
IHere 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-in
My original measurements were at 1Vrms at 100MHz as the 'base' before testing for the -3dB point
In the performance verification guide for the MSO5000 series, Rigol specify using 1Mhz as the reference frequency for the "Bandwidth Test".
Regards.
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?
Now, onto number 2):I repeat you measurements and get Vtops:
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.
Now, onto number 2):I repeat you measurements and get Vtops:
1. 2.479
2. 2.496
3. 2.508
4. 2.487
The worst case difference is about 0.4%. I think its not bad result for this equipment class.
Dustooff: 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?All measurements made in same conditions as yours) On the same signal and oscilloscope settings. Without averaging.
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
Hello no reply
You 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 life
Impressive throughput of small investigations, envious of the amount of time you have for these tasks :clap: great work ethic
One 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 population 8)
Why 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 :-DD
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.
matlipinski: What do your overshoots look like now at 50mV/div ?
I just did some testing as you requested
– to see how the ‘standard’ PVP2350 probes with the 1KHz (internal) calibration frequency response looks like.
See the attached screen captures below
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.
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.
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.
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 answered :P
Sorry 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.
Cheers
I just did some testing as you requested
– to see how the ‘standard’ PVP2350 probes with the 1KHz (internal) calibration frequency response looks like.
See the attached screen captures below
Not 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 overshooting
https://www.dropbox.com/s/pzda82cryolwhrx/2020-03-11%2015.14.18.jpg?dl=0 (https://www.dropbox.com/s/pzda82cryolwhrx/2020-03-11%2015.14.18.jpg?dl=0)
ch1 with compensation adjustment to try to remove overshoot
https://www.dropbox.com/s/el38jdvrrlb5olt/2020-03-11%2015.40.11.jpg?dl=0 (https://www.dropbox.com/s/el38jdvrrlb5olt/2020-03-11%2015.40.11.jpg?dl=0)
So do you see anything like THAT? :)
Increase 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
Increase 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
I'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
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.
Do you remember EXACT configuration settings - each setting , like impedance , etc, etc
Basically - 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 above ;)
If 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.
EDIT::o Sure there is. You edit the msg and de-select the image.
Is there a way to edit / delete unwanted attachments?
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.
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 Care
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 Care
Thanks 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)?
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?
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.
I wish there was a better X-Y mode resolution though (I know its a tricky process with digital sampling) but thats another topic.
I wish there was a better X-Y mode resolution though (I know its a tricky process with digital sampling) but thats another topic.
Yeah - 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-Y
This is possible on the 1054z - so unless I missed something in the menus - perhaps they remove this feature from the 5000 series??
Hit the 'Acquire' button and then 'Time base mode' (XT, XY, Roll)
I wish there was a better X-Y mode resolution though (I know its a tricky process with digital sampling) but thats another topic.
Sorry, noreply. I misunderstood your question (as is usual for me).
I wish there was a better X-Y mode resolution though (I know its a tricky process with digital sampling) but thats another topic.
Interesting - just trying to see 'why' digital sampling would have this inherent side-effect?
Nice video of a pre-release unit doing X-Y for you to download here:
Perhaps someone could 'chime-in' with a screen shot from the Siglent 2104X Plus in X-Y mode with a spinning circle?
Nice video of a pre-release unit doing X-Y for you to download here:
Perhaps someone could 'chime-in' with a screen shot from the Siglent 2104X Plus in X-Y mode with a spinning circle?
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2787208/#msg2787208 (https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg2787208/#msg2787208)
Kehall,Thanks, 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' file :-DD
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.
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.
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?
@Pulsepowerguy
A 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 ;)
... all four probes are at 1X ...
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 :)
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. :palm: 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.
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?
@noreply, I would still like to see your results. Please don't stay up so late just for this though. ;)
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/div
There 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!
You 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?
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
Dave, any chance of an update video like this ^^ ever happening in the future?
They offered me a patch for the problemWhat fix have you been offered? Can you share it?
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.
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 ?
I see it is an old post but maybe someone still can take a look at the photo. Is it some bug in firmware?If 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.
The probe are on x1 and all settings are the same expect the 50mV/div vs 51mV/div. Thanks much for any response!!
Is there such an option for MSO5000 other than slow MATH functions?
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.AFAIK all 4 channels in MSO5000 are processed by one ASIC which sampling rate gets divided down by the # of channels active.
Still i like the mso5000 and I never get tired about to tell how good it is for it´s price.
But if you can spend appx 400 bucks more there is, in my opinion, no alternative to the sds2k+.
AFAIK 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.
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."
My 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...............Your very first scope and respectively may I ask what qualifications and equipment you might have to put a modern oscilloscope through its paces ?
3. 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.
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.
As written that you chose to delete: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.
Does 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?
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.
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.
Thank 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.
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.
Thank 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.
It's called "high res" mode.
https://www.youtube.com/watch?v=n_dXvpEV18g (https://www.youtube.com/watch?v=n_dXvpEV18g)
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:
https://www.youtube.com/watch?v=036Ems1z-o0 (https://www.youtube.com/watch?v=036Ems1z-o0)
C'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.
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.
.... using Hires to make a 350 MHz scope a 50Mhz or 20Mhz or 500kHz scope, depending on how much bits of Hires you apply.
C'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.
I 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.As for Hires, it IS NOT replacement, fix, or solution for high noise in input channel of the scope.
I specifically said that it wasn't, but it does help.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.
Huh? 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.
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.
Averaging is useful only for repetitive, low phase noise (low jitter) signals.
So you could say that 1 bit improvement would be transparent , like you say. But not more
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+.
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.
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.
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.
Hires is a special acquisition mode. Like peak detect mode it is there for special occasions.
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.
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.
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?
That's the responsibility of the searcher to distinguish.
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 (https://www.eevblog.com/forum/testgear/hacking-the-rigol-mso5000-series-oscilloscopes/msg2769676/#msg2769676)
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]
About noisy digital scopes.Welcome to the forum.
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.
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.
Searched for this but no joy.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.
Does anyone know the output impedance of the AWGs?
Thanks,
Jeff
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?
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)?
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?
1. Is it possible to switch off the sinx/x interpolation to see the raw sampled data points on the display?
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 problem towards Rigol, do they usually care of this inquries of the users?
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 stays
on the screen when I change the timebase, so when two event is far from each other and if I would like to
measure the time difference between them, that needs both event on screen. The result of this that the
accuracy/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 evet
zoom 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 problem
towards Rigol, do they usually care of this inquries of the users?
I appreciate any response,
Thank you.