Level of trigger is not saved when turning off....
This is even worse than saving nothing at all, as you would not expect this, and then you may end up looking at the board...
Perhaps I missed the chatter in last page or so around remembering settings at power-off.
Isn't there an on/off setting for just that, to "start with last settings"?
The trigger ID format is not only not remembered (sets to binary), the right value is shown, but not triggering. It triggers on any ID it seems!
I am having trigger problems for any channel even single waveforms below 100us timebase.
I cannot trigger it correctly since for a simple 0-5Vp square waveform appears flickering as shown in attacment.
I have reduced the Horizontal Acquisition, the Memory depth. nothing.
The problem appears for any waveforms also in the 100us timebase.
What am I doing wrong?
Thank You in advance.
I am having trigger problems for any channel even single waveforms below 100us timebase.
I cannot trigger it correctly since for a simple 0-5Vp square waveform appears flickering as shown in attacment.
I have reduced the Horizontal Acquisition, the Memory depth. nothing.
The problem appears for any waveforms also in the 100us timebase.
What am I doing wrong?
Thank You in advance.
I cannot trigger it correctly since for a simple 0-5Vp square waveform appears flickering as shown in attacment.
What am I doing wrong?
playing with 16bit data out of DHO800 to PC and plot FFT... i'm sensing 156.25MHz -30dB artefact when no signal on input (50 ohm terminated), attached also different artefact profile from 8bit DS1054Z, maybe it matters? or something i did wrong
playing with 16bit data out of DHO800 to PC and plot FFT... i'm sensing 156.25MHz -30dB artefact when no signal on input (50 ohm terminated), attached also different artefact profile from 8bit DS1054Z, maybe it matters? or something i did wrong
This peak at a frequency of 156-odd MHz (and its harmonics) is clearly visible even on the oscilloscope itself in the FFT window. Some kind of internal interference from the operation of the circuit.
This peak at a frequency of 156-odd MHz (and its harmonics) is clearly visible even on the oscilloscope itself in the FFT window. Some kind of internal interference from the operation of the circuit.
It's 1/8 of the main 1.25 GHz sampling clock, right?
This peak at a frequency of 156-odd MHz (and its harmonics) is clearly visible even on the oscilloscope itself in the FFT window. Some kind of internal interference from the operation of the circuit.It's 1/8 of the main 1.25 GHz sampling clock, right?
I can try to take out the bin file from DHO1074, just tell more about the settings.
Also, I am interested regarding the software you have used. It's open source or
This peak at a frequency of 156-odd MHz (and its harmonics) is clearly visible even on the oscilloscope itself in the FFT window. Some kind of internal interference from the operation of the circuit.
It's 1/8 of the main 1.25 GHz sampling clock, right?
I can try to take out the bin file from DHO1074, just tell more about the settings.my setting was 625MSps because i was watching a 20MHz signal, full sample rate 1.25GSps will make that signal goes further to the left, less undesirable. but that FFT plot i linked above is when no signal at 1X dso input setting and 50 ohm terminator in place. anything greater than 1Mpts points will make a descent FFT resolution plot (at least when using my app). as AndyBig mentioned you should be able to see it on your scope's display as well if the artefact presents or not. ymmv.Also, I am interested regarding the software you have used. It's open source oryou can google VisaDSO in soasystem.com for setup file download. i've given up promoting it since i guess new kids on the block dont like older VB app, let the lucky persons found it by themselves. sometime stranger from unknown emailed me for the code, but once i sent it, they never come back to give feedback, so its like a waste of time, and probably nobody like nor can comprehend the old VB syntaxes anyway... i saw some bugs on latest upgrade to support DHO800/900, since afaik i'm the only one who's using it, i dont bother to fix asap, unless when necessity arrived. ymmv.
I have seen some reviews, starting by Dave one's .......
Also, while I was making the screenshots, I have found that the Rigol has only 10 divisions on the time axes , whereas the Siglent shows 14.
So on the 2 first screenshot, we can see more of the signal on the Siglent than on the Rigol
So on the 2 first screenshot, we can see more of the signal on the Siglent than on the Rigol
Seems like Rigol has slowed down firmware releases for the DHO800/900 family. They were averaging ~1 release per month but that change after December 2023.
- v00.01.02.00.02 2023/12/28 (latest release)
- v00.01.02.00.01 2023/12/5
- v00.01.02.00.00 2023/11/2
- v00.01.01.00.02 2023/09/12
- v00.01.01.00.01 2023/08/10
- v00.01.00.00.19 2023/07/24