Products > Test Equipment

New Rigol DS7000

<< < (68/72) > >>

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:

--- Quote from: maxwell3e10 on August 12, 2022, 03:03:49 pm ---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                 

--- End quote ---

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).

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