So we need to get two extra buttons somewhere!
So we need to get two extra buttons somewhere!
With the new firmware, this has gotten me curious as to whether shorting the 'Source' button position will pop-out the AWG side menu... perhaps it's time to finally open my DSO.
And the Metal case is Ready for BNC outputs,
But does Not look like an Add-on board
Not only are there holes in the front panel for the two buttons, the keypad PCB is already laid out for the two additional (illuminated) buttons:
Are you able to obtain waveform data that is 2GS/sec ? Everything Ive tried results in a file containing 1GS/Sec data. Ive set horizontal to max, memory depth to 56Mpoints, 14, 1.4, aliasing on and off - scope says 2GS/Sec on the display but always outputs 1GS/sec to the wavefile. Acquire mode is normal.
To check the scope. It "seems" to be sampling at 2GS/sec. I generated a 10 - 950 Mhz sine wave sweep at -20dBm and it displayed it on the FFT. Its a bit iffy above 200 Mhz.
BTW. Does anybody succeed with Rigol support. I sent numerous mails to support@rigol.com and from the feedback form from Customer Center. It seems they are in permanent meditation or dead.
Are you able to obtain waveform data that is 2GS/sec ? Everything Ive tried results in a file containing 1GS/Sec data. Ive set horizontal to max, memory depth to 56Mpoints, 14, 1.4, aliasing on and off - scope says 2GS/Sec on the display but always outputs 1GS/sec to the wavefile. Acquire mode is normal.
To check the scope. It "seems" to be sampling at 2GS/sec. I generated a 10 - 950 Mhz sine wave sweep at -20dBm and it displayed it on the FFT. Its a bit iffy above 200 Mhz.
To check the sampling rate, all you have to do is STOP acquiring when it displays '2GSs/s', then change the timebase to the smallest possible (e.g. 5ns), switch 'Display' -> 'Vectors' to 'Dots', then count the actual sample points. 2GSa/s means a 500ps acquire time for the ADC, so at 5ns/div, you should see 10 dots per div. If you don't, then I would imagine you have a technical problem.
Theres two possibilities, 1. the scope does decimate and saves 1GS/sec waves, or 2. the tool Im using to view the waveform is parsing the binary data incorrectly. I noticed the wfm file for the DS2072 isnt the same as the DS1052E. It contains preamble. Either case Ill check with the baudline author.
BTW. Does anybody succeed with Rigol support. I sent numerous mails to support@rigol.com and from the feedback form from Customer Center. It seems they are in permanent meditation or dead.
From what I've read, people have had varying levels of success. In some areas, it seems Rigol is quick and responsive to their customers - in other areas, not so much. I've had success communicating to Rigol through my dealer - which is sometimes the better path to take than directly.
So, if I am a registered customer, why I could not get the support from the only place where I registered?
BTW. They suggest me to visit their Munich office
Well, that's one reason the Rigol (and Hantek and Owon and Siglent) threads are so numerous (and often large) in this forum - because we (the owners/users of the equipment) are offering support to each other to make up for a deficiency from the manufacturers. If the Chinese companies provided better documentation and software for their devices - as well as a speedy, reasonable level of after-sales support, many of us would probably spend a lot less time here
Theres two possibilities, 1. the scope does decimate and saves 1GS/sec waves, or 2. the tool Im using to view the waveform is parsing the binary data incorrectly. I noticed the wfm file for the DS2072 isnt the same as the DS1052E. It contains preamble. Either case Ill check with the baudline author.I'm guessing it's almost certainly #2 - there wouldn't be any logical reason for #1 (except a bug). And yes, the WFM format has been drastically changed - and there is no published documentation about it - typical Rigol/Chinese behavior which pisses me off. And they appear to have changed it even some more in the latest firmware version (01.00.00.03)!
We are currently working on documenting the format - so that conversion routines can be written.
BTW, if you want to know what version of firmware you're running, you need to use a specific sequence of buttons. Read the instructions at the bottom of this post.
Are you saying the DS2072 is same hardware as DS2200 and only needs sofware to get 200MHz bandwidth
The insides should be the same.
Evan Cirelli,, sales team, VP and co-founder of TEquipment.NET
Hi Evan ,
Are you saying the DS2072 is same hardware as DS2200 and only needs software to get 200MHz bandwidth?
Heres a plot of the DS2072, captured via usbtmc piped into baudline, Hz = Mhz in this case. Waveform averaging is enabled vertical at 2mV/div. 2GS/Sec sampling.
All total nonsense.
@MikeR
What was your time base set at? (100ns/div?)
Probably
Was the frequency generator sweeping?
No manual stepping at 10Mhz
Does Baudline use multiple display waveforms or just just one?
It supports multiple inputs and channels. From STDIN, the channel data needs to be interleaved
chan1,chan2, etc
The Averaging by the Ds2072 during a sweep must have an affect.
It will, the longer dwell per step increases the snr due to the averaging, the steps here were
roughly timed to be similar - but not perfect hence my last comment.
The time base setting will affect the number of Samples and thus your data used by baudline
I now realize this thanks to your help.
-Cheers,
-Anyhow the .wfm file format is rather odd, baudline is able to parse unsigned bytes easily - it will display the spectrum showing e.g radio channels in the right places but only for sample rates set to 1GS/Sec, the file was captured at 2GS/sec, if I load that setting the sample rate accordingly they are in the wrong "spot" suggesting the original data isnt 2GS/sec.