Products > Test Equipment

Rigol MSO 5000 hardware/software revisions

<< < (65/84) > >>

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: ---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

--- End code ---

So no changes to the FPGA this time around.

Sighound36:

--- Quote from: NoisyBoy on April 17, 2020, 01:17:26 am ---

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.

--- End quote ---

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  :-DD got to love that guy!


tv84:

--- Quote from: NoisyBoy on April 17, 2020, 04:51:34 am ---I will never understand why Rigol cannot pay the slightest care towards packaging firmware in a professional manner.

--- End quote ---

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod