Rigol MSO 5000 hardware/software revisions

[jemangedeslolos]

Did you take good pictures of your previous MSO5074 screen ?
It could be interesting if you could do the same with the new one in the same conditions 

[Gandalf_Sr]

Did you take good pictures of your previous MSO5074 screen ?
It could be interesting if you could do the same with the new one in the same conditions 

So the New MSO5074 arrived and it's way newer.  The new serial number is MS5A21340XXXX, the hardware is 01.01.000, the firmware is 00.01.01.04.08, and the cal date is 8/27/2019.  I've taken a picture but it's hard to say that the new one is brighter, a little perhaps, it does seem quieter though.

[Gandalf_Sr]

Couldn't get the second picture of the new scope to attach so here it is

[NoisyBoy]

Glad you finally get a fresh scope, this also serves as a warning to other buyers in the US, escalate with your AD before shipment so you don’t get the old stock.  I bet there are other unsold old stock in their warehouse.  I was lucky that mine arrived with a less than 30 day old cal, but that was when the scopes were back ordered.

If those old stock is functionally equivalent to the newer stock, the least Rigol can do is to do a fresh cal before shipment.

[whatisthis]

New firmware 00.01.02.00.03...
rar file seems to be corrupted, I couldn't open it

They re-uploaded that file 

Code: [Select]

v00.01.02.00.03 2020/02/27
     - It solves the error of SCPI instruction reading La channel memory data, and solves the error of SCPI instruction reading La channel memory data

[thm_w]

They re-uploaded that file 

Code: [Select]

v00.01.02.00.03 2020/02/27
     - It solves the error of SCPI instruction reading LA channel memory data, and solves the error of SCPI instruction reading LA channel memory data

In chinese its just the first sentence, so a copy paste translate error (解决了scpi指令读取LA通道内存数据错误).

How they can release a firmware update release in 2 days? weird.. Not to mention almost no one is going to be using that feature.

[Sergey Astakhov]

In Int site there is still a corrupted version.
In EU site the file now looks good.
Direct link: https://eu.rigol.com/Public/Uploads/uploadfile/files/ftp/DS/%E8%BD%AF%E5%9B%BA%E4%BB%B6/MSO5000(ARM)Update00.01.02.00.03.rar

[NoisyBoy]

Then we are still on 04.08 in the US, it is a mess.  Why have multiple regions on their site when they cannot maintain it.

BTW, as reported in the MSO5000 bug topic, some found their channel 3 come on even without signal when you press Auto, a new bug they introduced in the new firmware.  It is a nuisance and you must evaluate if you want this before you upgrade.  You will have to turn off channel 3, rescale the other channels and offsets. 

So my suggestion is unless you have a problem that you know the 02.0x release fixes, it is better to stay with the 04.0x firmware.  At least in my case, the new firmware does not fix anything and only introduces this new problem.

[Sighound36]

What Rigol needs is there own version of Tautech, to abuse, badger, strong arm and generally navel graze there way to a positive result.

A brand ambassador to look after most things which are realistically possibly, we all get frustrated with our test equipment from time to time especially with the newer equipment relying heavily on Processor / PC driven hardware so issues will arise, even the LeCroy we have has a couple of bugs I found, did I worry a forum no,I just make observations to the relevant parties, how long will it take? Who knows, though not as long as Rigol one would suspect!


But if have a customer care department that really wishes to make that companies products as good as possible given the various price points then Rigol should up their game without question. The have some good hardware just not the understanding of the firmware and demographic to gain total market place  confidence imho.

Rather than a whinge fest, lets make a positive step to find decent working solutions to 'help' Rigol to understand the error of the current methodology.

Just my tuppence and hopefully not 

All I can comment is if our company ran its customer service and back up like Rigol we would not have a business to run within 2 months!.

Come on Rigol get your house in order and employ some decent code monkeys and customer relations staff, you business will be more trust worthy and potential customers will increase YMMV

I am not Rigol bashing just making observations, we have seven pieces of Rigol test equipment so even I feel its time for Rigol to pull its self together

[tautech]

What Rigol needs is there own version of Tautech, to abuse, badger, strong arm and generally navel graze there way to a positive result.

A couple of years back they invited me onboard and I declined, if again today the answer would remain the same.

[Gandalf_Sr]

Has anyone here loaded and tried the new firmware vn 00.01.02.00.03?

Is there anyone who can give an objective report on it?

[Cerebus]

Has anyone here loaded and tried the new firmware vn 00.01.02.00.03?

Is there anyone who can give an objective report on it?

Not yet. I'm afraid I'm being a cowardly custard and waiting for someone else to try it.

At the moment my MSO5000 is in a tangle of cables actually doing some work, so I've got a good reason to delay.  That's my excuse and I'm sticking to it.

Look, I'm not even fibbing, taken just now:

[Gandalf_Sr]

Hey, looks like you got the outrageously-priced LA probe set there!  I used to be a Brit before I gave it up so I understand your banter and you're clearly not fibbing.

[Cerebus]

Hey, looks like you got the outrageously-priced LA probe set there!  I used to be a Brit before I gave it up so I understand your banter and you're clearly not fibbing.

I did. I figured by the time I'd spun up a board, bought some connectors and so on to make my own that I'd have spent most of the overpriced price of the probe set. I decided to bite the bullet and get to use the thing now rather than wait until I'd fabricobbled together a probe set. As my next project involves an FPGA I thought that it would be nice to have the LA functionality on hand.

[Gandalf_Sr]

From a time perspective, I've spent thousands of dollars on my design for an MSO5000 LA probe.  Maybe it will be a dud but, if I succeed, I'll have a design that can get close to the limits of the MSO5000 and cost a fraction of the PLA2216. The PCBs are ordered and I already have all the components.

Wish me luck.

[Cerebus]

Luck!

[thmjpr]

Here is my early stage Bode plot software: https://gitlab.com/thmjpr/mso5000-gui
I based it off of a post from timber23 here: https://www.eevblog.com/forum/testgear/new-rigol-16-bit-function-generators-dg800900-series/msg2425551/#msg2425551

Still need to add: relative plots, dB units mode, csv output, TCPIP/USB selection, etc.
May require some knowledge of python to run, the SCPI IP is hardcoded currently. But can easily run on windows on Pycharm.

Attached is example plot from buffer board (opamp THS3201).
Input: blue, 1Vpp
Output: green, 2Vpp

Internal generator seems to drop off at about 15MHz.

[thmjpr]

One interesting finding, the bandwidth seems to vary depending on selected vertical scale:
- 100mV and 200mV/div have higher amplitude at > 400MHz, -3dB only hits at ~640MHz, but its bumpy
- 50mV, 0.5V/div, etc. have amplitude drop off as we've seen in other threads at ~450MHz

I don't know if this is peaking in the filter design, or some different filter is selected in software, etc. I would say its a problem with my source, but, its too consistent, it should have peaking at all vertical scales not just some.

Range is 250-650MHz, 100mV/div, 0.5Vin:

[nctnico]

One interesting finding, the bandwidth seems to vary depending on selected vertical scale:
- 100mV and 200mV/div have higher amplitude at > 400MHz, -3dB only hits at ~640MHz, but its bumpy
- 50mV, 0.5V/div, etc. have amplitude drop off as we've seen in other threads at ~450MHz

For the lower ranges the signal needs to be amplified in the osciloscope's front-end. It is very normal for a DSO to show different frequency versus amplitude graphs although the DSO should meet the minimum bandwidths. When I do a DSO review I measure the bandwidth at a low v/div value and a medium v/div value.

[skander36]

Here is my early stage Bode plot software: https://gitlab.com/thmjpr/mso5000-gui
I based it off of a post from timber23 here: https://www.eevblog.com/forum/testgear/new-rigol-16-bit-function-generators-dg800900-series/msg2425551/#msg2425551


(Attachment Link)

Thank you for your work . 
I was able to run it .
Setup for PyCharm was a mess because I have already VS Code installed .
I think is good to add on line 123 - self.buttonStart.setEnabled(True) to be able to restart without close/open the application.
Waiting for another version to test , when you will have time to work on it.

Thank you !

[thmjpr]

I will add some features, although for now the oscilloscope is in pieces

Looking for tips on component values for the input compensation circuit mentioned here: https://www.eevblog.com/forum/testgear/review-rigol-mso5000-tests-bugs-questions/msg2897906/#msg2897906

Lx, Cx and Rx are the unknown components. Lx is very small, 4 turns on an inductor (thanks to Daves teardown). Maybe 0.4uH.
Rx and Cx I'm unsure of, I suspect the capacitor is physically large for high voltage rating (100V?).

The various paths into the ASIC seem to use the same components as the MSO7000 but they are unmarked so no way to know yet. Why there are various paths too, seems like they may be switched in depending on scale or timebase?

[Gandalf_Sr]

Ohhh, I like the idea of getting way more bandwidth by adding 3 SMT components per channel; you are a brave person.

Hope you don't  your scope.

[egonotto]

Hello Gandalf_Sr,

god luck, have fun.


Best regards
egonotto

[rolfdegen]

The latest Firmware



Greetings from germany. Rolf

[skander36]

00.01.02.00.03 is the latest .