Rigol MSO 5000 hardware/software revisions

[typoknig]

Hi all, an interesting finding to share with you.

If you follow the readme file in the latest 02.03 firmware Rigol released quickly after 02.02, probably there is little to no reason for doing another upgrade for most users.  However, I found the 02.03 update fixes a couple issues that are not documented in the readme file:

1. At least in my case, it fixes the problem with Auto randomly turning on channel that have nothing attached.  I have seen channel 2 (rarely), and channel 3 (almost always) turning on and display traces of noise.  Self-cal does not help, but after applying the fix, the problem is gone.  I have not been able to recreate it, when I press Auto, channels without input no longer comes on.

2. As sb42 had shared, when you press Auto, you sometimes get an intermediate image of other channels flashing on the screen for a moment, before it settles on the final screen.  This problem is also gone, there is no momentary flashing of random channels.

These are important fixes for the new bug introduced in 02.02, but unfortunately in Rigol fashion, the fix documentation did not fully describe what it fixes. 

I hope you will find this tip useful, and perhaps more owners can test it out so we have more than a sample of 1.

And a big thank you for mabl for pointing out the change in the FPGA and appEntry, his effort prompted me to test out the 02.03 firmware even though Rigol did not mention these hidden fixes.

Good luck and stay healthy.

Regarding your second point, I did still see this problem in the 00.01.02.00.03 firmware when performing my tests. It didn't happen often, maybe like 3 or 4 times through all my testing. When it did happen it was always channel 1 that flashed.

[Sighound36]

Hi NoisyBoy

I have checked both the 5 & 7000 scopes this morning, zero issues with the channel turning on and they are all running the latest FW.

On the 8000 noise (full bandwidth 2Ghz +) open port, 50Ohm setting No high resolution (normal acquisition) or precision settings 200ps on the HTB, average noise on channel was 322uV.

If you switch on the 20Mhz BM limit, high resolution and precision you obtain on average around 80uV, the Wavepro 254 is around 44uV with the ERCS in use @ the same 20Mhz BW limit and open port

[NoisyBoy]

Hi Sighound36 and typoknig, thank you for the input and datapoint. 

I’ll have to turn on the BM limit and see how it affects the noise floor, I meant to do that but forgot, my test was run with full BW.  If it makes a meaningful reduction, reducing the BW could be an useful trick for those who needs a lower noise floor for low signal level measurement.

[UA3MQJ]

Hello, all!
I finally got an oscilloscope today,
Model Rigol MSO 5072 (Max BW:70M)
Firmware: 00.01.02.00.03
Hardware: 01.01.000
Boot: 2018.06.27
Build: 2020-02-26 17:47:28

Interestingly, the set included probes at 350 MHz - Rigol PVP2350

[NoisyBoy]

Enjoy your scope.  That is the standard probe Rigol sends out with the MSO5000 scopes, they are all 350 MHz probes.

This costs Rigol more, but it is a nice perk for owners of an upgradable scope.  They could have saved some money to ship the lower bandwidth probe but chose to go the more generous route, excellent move on their part to motivate owners to upgrade bandwidth with no hardware changes or buying four new probes. 

Some other brands requires you to upgrade all your probes when you upgrade the bandwidth, kudos to Rigol for doing the right move while still keeping the scope affordable.

[Martin72]

Some other brands requires you to upgrade all your probes when you upgrade the bandwidth

Oh yes….

[Gandalf_Sr]

I'm getting nothing from my HDMI connector although I'm trying an old monitor that only has DVI which I'm trying with a DVI-HDMI adapter.

Earlier in this thread skanders (I think) says...

v00.01.02.00.02  2020/02/25
       
     - Optimized the connection HDMI start problem optimized the connection HDMI start problem

Questions:
1. Do I need to update to vn00.01.02.00.02 or higher to make it work?
2. Is there somewhere in the menus to turn on the HDMI? I can't find anything.
3. When the HDMI monitor is on, does the main screen stop working?
4. If I change the HDMI resolution for the external monitor does the main screen change too?

Thanks in advance

[skander36]

HDMI work in any versions .
Just activate (every time ... ) through Utility-IO-HDMI ...

[Gandalf_Sr]

HDMI work in any versions .
Just activate (every time ... ) through Utility-IO-HDMI ...

Thanks, so it was under the IO menu, not the display menu; TILT 

I plugged in 2 different monitors using the DVI-HDMI adapter, got nothing from either of them. My firmware is 01.01.04.08, any ideas?

[skander36]

DVI must work is just a physical remapping of pins , signals are the same on both ends (HDMI to DVI) ...
Check that you have selected the right input on the monitor (VGA/DVI) ... I don't see other reason ...
P.S. Currently I am using the same fw.

[Gandalf_Sr]

DVI must work is just a physical remapping of pins , signals are the same on both ends (HDMI to DVI) ...
Check that you have selected the right input on the monitor (VGA/DVI) ... I don't see other reason ...
P.S. Currently I am using the same fw.

Thanks, I knew that it was just a remap and that it should work but these are kind of old monitors.  I'm thinking of buying a new one but I don't want to go to all that expense and find it still doesn't work.  Maybe there IS a problem with the HDMI startup, at least on my MSO5000?

I tried the search on the inputs, both monitors I tried said there were no signals.

[skander36]

I don't think it worth buying a new one for this.
Instead a used one with a HDMI connection . There are very cheap at 22, 23 inch on ebay or other sources near you .

[Gandalf_Sr]

I don't think it worth buying a new one for this.
Instead a used one with a HDMI connection . There are very cheap at 22, 23 inch on ebay or other sources near you .

I meant a new monitor.  Anyway, I tried a 4K monitor (newest I own) that has native HDMI inputs, I plugged it in and it worked immediately (although it had a black surround on the screen) so I've proved that my MSO5000 and HDMI cable are good.  I will order an Asus VZ229HE 21.5" monitor which I can get here for $100 - I checked the manual, it will do 1280 x 720 @ 60Hz so I should be good with that model.

If anyone's curious, the HDMI display runs in addition to the scope's screen so you can work the touch screen and soft buttons on the MSO5000 and look at the HDMI monitor; would be a great scope for a teaching environment.

[NoisyBoy]

What about trying your TV with HDMI?  If you go straight HDMI, you can rule out issue with your adapter.  As skander36 said,  there is no known issue with HDMI.  Make sure you set it at a resolution your monitor can support, it does not output full 1920x1080 HD.  But it is good enough at the highest resolution, it is nice not having to connect it to the Internet to output the display.

[Gandalf_Sr]

What about trying your TV with HDMI?  If you go straight HDMI, you can rule out issue with your adapter.  As skander36 said,  there is no known issue with HDMI.  Make sure you set it at a resolution your monitor can support, it does not output full 1920x1080 HD.  But it is good enough at the highest resolution, it is nice not having to connect it to the Internet to output the display.

Thanks but I think we cross-posted, I sorted the problem out by plugging into a native HDMI port on a newish monitor (actually a 4K one) and now it's like iMax MSO5000 
I also plugged in a Logitech wireless mouse with unifying receiver and that worked great too   It's really so much better working from a large monitor with a mouse.

[luma]

DVI is goofy in that it has pins for both digital and analog signals, and it might not offer both digital and analog modes.  An older monitor that has VGA and DVI inputs may very well only accept an analog signal, meaning a straight pin conversation from HDMI won't work.

[NoisyBoy]

Excellent, glad it is working for you.  The HDMI out is definitely a nice feature in the MSO5000, I wish it can support native HD resolution, but it is good the way it is.

[NoisyBoy]

A feature that has long been discussed for over a year is finally here,

v00.01.03.00.01 2020/04/13
     -Add bode map function

There is no mention of any other changes at this point, but it will be a welcoming new feature to bring the scope on par with the Siglent Bode Plot offerings. 

[pmaggi]

I've upgraded to this new firmware... And bode plot works 
The problem with channel 3 in auto mode is still there...

[pmaggi]

Here are some pictures...

[NoisyBoy]

Excellent, thanks for sharing.  I believe the ghost channel may be caused by RF interference due to inadequate shielding on the front end, leaving the heat sinks exposed and acting as an antenna.  Try removing it from strong RF sources (WiFi in my case) and see if the ghost channel goes away.

Was your plot created by using the internal AWG?  I notice it goes up to nearly 100MHz.  I hope they support external AWG as the internal AWG is very limited in capabilities.

BTW, I am absolutely surprised that they decided to release it on the 5000 ahead of the 7000 or the 8000 flagship as their firmware has much in common.

[NoisyBoy]

More woes in Rigol patch packaging.

In the US, you can access the Rigol firmware here: https://www.rigolna.com/firmware/

But when you click on the 01.03.00.01 link, you will get a file named MSO5_FW_V1_1_4_4.zip

The file name threw me off at first, thinking that they had put the old 04.04 patch from a year ago on the server, as it has the exact same name.

But have no fear, go ahead an unpack the ZIP file, the unpacked file contains the new firmware to upgrade the scope.

I will never understand why Rigol cannot pay the slightest care towards packaging firmware in a professional manner. 

[mabl]

File level changes:

Code: [Select]

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   firmware/fw4linux.sh
        modified:   firmware/fw4uboot.sh
        modified:   firmware/rootfs/rigol/Qt5.5/plugins/generic/libqevdevmouseplugin.so
        modified:   firmware/rootfs/rigol/Qt5.5/plugins/platforms/libqlinuxfb.so
        modified:   firmware/rootfs/rigol/appEntry
        modified:   firmware/rootfs/rigol/drivers/usbtmc_dev.ko
        modified:   firmware/rootfs/rigol/resource/appmeta.xml
        modified:   firmware/rootfs/rigol/resource/dsometa.xml
        modified:   firmware/rootfs/rigol/resource/help/b/help.hlp
        modified:   firmware/rootfs/rigol/resource/help/b/histogram.hlp
        modified:   firmware/rootfs/rigol/resource/help/b/trigger.hlp
        modified:   firmware/rootfs/rigol/resource/help/d/help.hlp
        modified:   firmware/rootfs/rigol/resource/help/d/histogram.hlp
        modified:   firmware/rootfs/rigol/resource/help/d/trigger.hlp
        modified:   firmware/rootfs/rigol/resource/menu/b.hex
        modified:   firmware/rootfs/rigol/resource/menu/c.hex
        modified:   firmware/rootfs/rigol/resource/menu/d.hex
        modified:   firmware/rootfs/rigol/resource/menu/desc.hex
        modified:   firmware/rootfs/rigol/resource/menu/h.hex
        modified:   firmware/rootfs/rigol/resource/menu/i.hex
        modified:   firmware/rootfs/rigol/resource/menu/j.hex
        modified:   firmware/rootfs/rigol/resource/menu/k.hex
        modified:   firmware/rootfs/rigol/resource/menu/l.hex
        modified:   firmware/rootfs/rigol/resource/menu/m.hex
        modified:   firmware/rootfs/rigol/resource/menu/menu.hex
        modified:   firmware/rootfs/rigol/resource/menu/modelconfig_ch.hex
        modified:   firmware/rootfs/rigol/resource/menu/modelconfig_ext.hex
        modified:   firmware/rootfs/rigol/resource/menu/msg.h
        modified:   firmware/rootfs/rigol/resource/menu/n.hex
        modified:   firmware/rootfs/rigol/resource/menu/o.hex
        modified:   firmware/rootfs/rigol/resource/menu/res.hex
        modified:   firmware/rootfs/rigol/resource/menu/t.hex
        modified:   firmware/rootfs/rigol/resource/menu/u.hex
        modified:   firmware/rootfs/rigol/resource/res.qrc
        modified:   firmware/rootfs/rigol/resource/scpi/CHANnel1.xml
        modified:   firmware/rootfs/rigol/resource/scpi/CHANnel2.xml
        modified:   firmware/rootfs/rigol/resource/scpi/CHANnel3.xml
        modified:   firmware/rootfs/rigol/resource/scpi/CHANnel4.xml
        modified:   firmware/rootfs/rigol/resource/scpi/HISTogram.xml
        modified:   firmware/rootfs/rigol/resource/scpi/scpiConfig.xml

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        firmware/rootfs/rigol/resource/help/b/bodeplots.hlp
        firmware/rootfs/rigol/resource/help/d/bodeplots.hlp
        firmware/rootfs/rigol/resource/satable/hori_10g/
        firmware/rootfs/rigol/resource/satable/hori_20g/
        firmware/rootfs/rigol/resource/satable/hori_2_5g/
        firmware/rootfs/rigol/resource/satable/hori_5g/
        firmware/rootfs/rigol/resource/satable/hori_5g_100m/
        firmware/rootfs/rigol/resource/scpi/BODe.xml
        firmware/rootfs/rigol/resource/scpi/compatible/BODe.xml
        firmware/rootfs/rigol/resource/scpi/compatible/Ref.xml
        firmware/rootfs/rigol/resource/scpi/compatible/common.xml
        firmware/rootfs/rigol/resource/scpi/compatible/cursor.xml
        firmware/rootfs/rigol/resource/scpi/compatible/quick.xml

So no changes to the FPGA this time around.

[Sighound36]

BTW, I am absolutely surprised that they decided to release it on the 5000 ahead of the 7000 or the 8000 flagship as their firmware has much in common.

Hello Noisy Boy

No Rigol's plan was to release the MSO5000 bode plot update first due to the pressure from 5000 owners (all be it late!) however the 7/8000 will follow very shortly I believe there are a few other eggs in the basket for those two models.

Possibly now the FW updates will start to be more regular for the later devices 

It is currently a shame that Rigol doesn't seem to have ability to jump on the Tautech bandwagon of badgering the manufacturer into submission which seems to work for Siglent

As I have mentioned before Rigol need a brand ambassador with out jumping on ever thread to promote themselves  ideally a version of the Danny Bogoff show from Keysight with even more attitude  got to love that guy!

[tv84]

I will never understand why Rigol cannot pay the slightest care towards packaging firmware in a professional manner.

I think it has to do with the webpage (what name it assigns to the download) and not so much with the file.