New Rigol DS7000

[tv84]

Does anyone have any experience with this ?

Looking at the patches that are public, I see no way around that.

[CookieMonster]

You mean there is no way around accepting the generator and analyser UI elements that have appeared ?

Are there any links to explain how the patches were created ?

Would it be possible that the appEntry executables are different for the MSO and DS models ?
Perhaps one could upload the original appEntry of the MSO, so that I can compare it to mine.

[tv84]

You mean there is no way around accepting the generator and analyser UI elements that have appeared ?

Are there any links to explain how the patches were created ?

Would it be possible that the appEntry executables are different for the MSO and DS models ?
Perhaps one could upload the original appEntry of the MSO, so that I can compare it to mine.

1. Yes, with that hacking method.
2. No.
3. The app is the same.

[CookieMonster]

pity.. I guess there is too little demand for someone to make a patch w.o. the the LA and Gen. 

[CookieMonster]

BTW In case anyone in interested in silencing the D7000..

I changed the fan in mine for a Noctua NF-P12 redux-1300.
This worked flawlessly, it fits well mechanically and there is no apparent current monitoring like in the DP832 - at least it wouldn't trigger with the ca. 200mW reduced power consumption.

I also changed the fan direction, this takes away the whiney noise.
It's still audible, but its a much more bearable lower volume and low pitch air flow noise.
 

[tom0021]

There is a new firmware here: https://www.rigol.eu/En/Index/listView/catid/28/tp/6/wd/MSO7000

v00.01.02.01.03
from 03.12.2021

it has a long changelog:
[Supported Model]    All the MSO/DS7000 Series Digital Oscilloscopes
[Latest Revision Date] 2021/12/03

[Updated Contents]
--------------------
v00.01.02.01.03  2021/12/03
       
     - Added average operation in math function
     - Added CAN-FD protocol decoding (DS7000-AUTO option)
     - Added SCPI instruction to switch the manual cursor measurement area
     - Added SCPI instruction to set the contents of the analog channel label
     - Analog channel labels support resizing and add SCPI instructions
     - Supported dragging analog channel labels to change positions and adding SCPI instructions
     - Added SCPI instruction to switch the measurement threshold setting mode
     - Delay and phase measurement supported edge event setting, edge support first, last or
        automatic, and added SCPI instruction
     - Supported changing the cursor position by inputting time or voltage
     - The storage depth can be modified in the stop state
     - Updated touch screen driver
     - Optimizing DC calibration algorithm in self calibration
     - When zoom is on, the cursor function will measure the extended time base by default
     - Fixed the problem that the probe ratio parameter is invalid for the search function threshold setting
     - Optimized the waveform of XY mode
     - Supported turning off the display of the source channel of the math waveform
     - Modified the identification instability of RP7000 series probe
     - Improved WebControl web page refresh speed (related to network speed)
     - Optimized WebControl web page control, supports dragging and drawing rectangles with the mouse
     - Supported modifying labels and file names through the physical keyboard
     - Optimized bandwidth frequency response @1MΩ input impedance
     - Supported the connection communication of T2R1000 probe adapter
     - Optimized the digital filtering function in math function
     - Modified the problem that the network printer cannot print

Has anyone already tested this version?

[drhex]

Ok, had a quick look at 00.01.02.01.03, the signatures for the patches are still there, albeit in different places. Have patched one tonight but not tried yet, will post the patch here provided it works.

[drhex]

After a bit of rigmarole (seems gel_pack.sh doesn't produce a working image) I can confirm the patch still works, locations have changed of course.

[drhex]

@cookiemonster Different issue, tried again my end, this is about the formatting of the USB stick, probably the lower blocksize on the smaller sticks. So DSO7000 behaves differently from MSO7000 apparently.

[GurljoM]

After a bit of rigmarole (seems gel_pack.sh doesn't produce a working image) I can confirm the patch still works, locations have changed of course.

Figured it out based on your previous patch and confirmed the assembly code changes in Ghidra. Works great on the scope too.

Tha appEntry changes for FW v00.01.02.01.03 are:

offset       values
1810B4: 00 00 A0 E1
1810D0: 00 00 A0 E1
37BE0C: 00 00 A0 E1
37BE28: 00 00 A0 E1
42FA30: 00 00 A0 E1 01 00 A0 E3

See attached the patch file.

Cheers

[IW4EGX]

Hello,
a DS7014 is going to arrive in my Lab in the next days....i've purchased it new but i don't know what revision of firmware is loaded in the oscilloscope until it arrive.
Is there a way to unlock Bandwidth and Memory Expansion?
thank you

Nicola

[wat]

Hello,
I've prepared a 1 click patch for the latest fw 1.02.01.03 using the details from GurljoM and the automatic patch script from mabl

The procedure is pretty straightforward:
-Upgrade fw as normal
-Copy the content of the rar file into the usb stick, and "upgrade" the fw again: the screen will turn white, press "Menu off" button (I tried other buttons but they didn't work). You should see the details of the patch being applied.

Done!

P.S. It is similar to what omgoleus did here

[toybuilder]

Thanks for the easy-to-use patch, @wat!

As @cookiemonster mentioned already, the patch results in the system running as a MSO7000 and turns on the soft buttons for the Logic Analyzer and the Signal Generators that are not on the DS7000.   If you activate them through the soft buttons, otherwise hidden LEDs turn on for those features!

When I performed a self-calibration after the patch, the self-calibration process failed while working on the non-existent Logic Analyzer. Since I had already calibrated my unit after the initial firmware update, it is not clear to me whether it is running with the calibrations data stored prior to the patch, or if the second self-calibration process correctly set up CH1-CH4 before failing calibration on LA. So far, it looks like it is at least correctly calibrated.  For anyone else with a DS7000, I suggest running the self-calibration immediately after the firmware update, before the patch.

I'm glad your patch works with FW 1.02.01.03, as that added support for using the keyboard to set the label names and print output file names!  That was a key feature that I felt was missing with earlier firmware.

[maxwell3e10]

Rigol likes to advertise fast waveform update rates for their DS7000 and DS8000 series scopes. They have several videos on Youtube showing how well it works. It does seem to be second only to Keysight. But if one looks closely, all the videos use 10 ns/div time scale and there is a note in the datasheet saying that 600,000 waveforms/sec is specified only for 10 ns/div time scale. So, the question is how fast is the update rate at other time scales? There is evidence that it maybe is substantially slower, even for shorter time scales.

For comparison, here is a table from a Keysight app note on the update rate in their 3000-X series scopes:
1 ns/div  - 20 ns/div 960,000                             
50 ns/div                  570,000                         
100 ns/div                340,000                   
200 ns/div                170,000                       
500 ns/div                 74,000     
1 μs/div                    38,000                 

[JehTeh]

Rigol likes to advertise fast waveform update rates for their DS7000 and DS8000 series scopes. They have several videos on Youtube showing how well it works. It does seem to be second only to Keysight. But if one looks closely, all the videos use 10 ns/div time scale and there is a note in the datasheet saying that 600,000 waveforms/sec is specified only for 10 ns/div time scale. So, the question is how fast is the update rate at other time scales? There is evidence that it maybe is substantially slower, even for shorter time scales.

For comparison, here is a table from a Keysight app note on the update rate in their 3000-X series scopes:
1 ns/div  - 20 ns/div 960,000                             
50 ns/div                  570,000                         
100 ns/div                340,000                   
200 ns/div                170,000                       
500 ns/div                 74,000     
1 μs/div                    38,000                 

When I was messing around with this yesterday on my MSO8204, I noticed the following (waveform rate was captured using a second scope on trigger out. Trigger source was a 10M signal on Trig IN. All measurements single channel enabled).

- At 10ns/div, auto memory (scope sets 1kpts, 10GS/s): ~700k/s
- *any* other timebase I tried (auto or 1k mem) (200ps - ms range) - 110k/s max
- At 10ns/div, manual 1k memory (scope drops to 5GS/s): 110k/s

In fact I can never seem to get above 110k/s except in that explicit first case, where it jumps to well over 600k. I also noticed that when running in 'fast mode' there is the occasional long dead-time where no triggering occurs - you can see seconds worth of ~700k/s triggers on the other scope then a 'long' (100's of ms) period where nothing happens.

This strikes me as somewhat strange. I didn't spend more than 20m playing with it, but my initial, very probably unfair,  reaction is something along the lines of 'is this just a special path Rigol has in here for advertising?' - not saying it is the case, I don't have enough information yet, but suffice to say I am going to be emailing my rep shortly for further clarity because it strikes me as very strange. I fully understand there will be lots of cases where the scope won't be hitting 600k+, but as it is it looks like someone spent a lot of time either optimising for just a single path or there is a bug somewhere in other modes (very, very possible - despite the price of the CAN decoder for example it is pretty buggy, albeit still quite usable).

[maxwell3e10]

I've confirmed with Rigol tech support that DS7000 has the same "feature", only 10ns/div scale gives 680,000 wfs/sec update rate, any other time scale it is at least 5 times slower.

To me the most interesting question is how they managed to speed up the firmware for only one horizontal setting but not others? It's like making a car that can drive 5 times faster on only one road.

[tv84]

I've confirmed with Rigol tech support that DS7000 has the same "feature", only 10ns/div scale gives 680,000 wfs/sec update rate, any other time scale it is at least 5 times slower.

To me the most interesting question is how they managed to speed up the firmware for only one horizontal setting but not others? It's like making a car that can drive 5 times faster on only one road.

Maybe that's the only real HW rate the scope works on. All others are calc/emulated in software.

[maxwell3e10]

I've confirmed with Rigol tech support that DS7000 has the same "feature", only 10ns/div scale gives 680,000 wfs/sec update rate, any other time scale it is at least 5 times slower.

To me the most interesting question is how they managed to speed up the firmware for only one horizontal setting but not others? It's like making a car that can drive 5 times faster on only one road.

Maybe that's the only real HW rate the scope works on. All others are calc/emulated in software.

10GS/sec*10 nsec/div*10 div =1000 points. The display is 1024 pixels. So it could just write horizontal scale directly to display.  I am wondering about anti-aliasing/bandwidth limiting filters though, seems like they would be more time consuming than simple scaling.

[luky315]

Comming back to the self-calibration issue: Does someone have informations what the failed self calibration after the "liberation" patch means? Are the analog channels still correctly calibrated, even if the logic analyzer part fails?

[Wong]

The new firmware version v00.01.03.00.01 has been released. I don't know whether it can be hacked.
https://www.rigol.com/products/detail/MSO7000

v00.01.03.00.01  2022/12/08

     - Provides the VNC remote control function
     - Optimized response speed for controlling vertical gear offset
     - Optimized response speed for controlling horizontal time base migration
     - Optimized the trigger Settings menu physical key response time
     - Control the real-time response of the cursor position
     - Cursor measurement supports simultaneous measurement of two sources
     - Manual cursor measurement supports multiple cursor display types
     - Manual cursor mode Allows the cursor to move according to the waveform
     - Multi-function knob can be pressed to switch the adjustment of cursor A and cursor B
     - The cursor indicates that the color changes with the source color
     - Manual mode cursor measurement added dual channel source Settings menu
     - Changed the Delay Scan (ZOOM) mask color
     - ZOOM mode supports cross-area measurement of the cursor
     - Latency Scan (ZOOM) function on and off response time
     - Optimized waveform movement speed in the delayed scan (ZOOM) area
     - Improved waveform display brightness
     - Changed the color of analog channel CH4
     - Measure any edge add modification
     - Improve reset instruction *RST response rate
     - Improves the response rate of the clear command
     - Improve the response rate of measurement instructions
     - Improve the command rate of waveform export
     - Webcontrol Adds the function of exporting screen and memory data

[wat]

Hello, I've been away for a while from his forum... Did anyone make a patch for the latest fw?

[carlos33193]

Anyone have an update on this for MSO7000? Latest firmware. Thank you!

[carlos33193]

Hello,
I've prepared a 1 click patch for the latest fw 1.02.01.03 using the details from GurljoM and the automatic patch script from mabl

The procedure is pretty straightforward:
-Upgrade fw as normal
-Copy the content of the rar file into the usb stick, and "upgrade" the fw again: the screen will turn white, press "Menu off" button (I tried other buttons but they didn't work). You should see the details of the patch being applied.

Done!

P.S. It is similar to what omgoleus did here

Your patch worked beautifully easy on firmware 01.02.01.03. Even though my Rigol came with this firmware already it was failing the checksum in your patch script, downloaded the 01.02.01.03 firmware from previous post link (https://www.rigol.eu/En/Index/listView/catid/28/tp/6/wd/MSO7000) and flashed over and then re-ran your script and it succeeded checksum and restarted with all options. THANKS!

Any chance you could make this auto flasher for the latest 01.03.00.01 firmware?

[wat]

I wish it was that simple: I can generate the batch, but I need from someone the details on which bytes to patch

[luky315]

Now they have the v00.01.04 MSO7000 Firmware