Wow, that's impressive. How did you guys do it? Did they mess up in the key validation/generation and leave the priv key exposed somehow? Or, knowing Rigol, something dumber 
I wouldn't put these scopes on the internet, given that they have SSH exposed. Best to keep them isolated!
It would be impressive if it was verified. What is impressive is olivers repo, and tv84s infomation. This is the internet, been around way too long and am probably very cynical, but seen lots of claims of things, and have learned until you can actually verify things, you can't put much weight on them.
Wow, that's impressive. How did you guys do it? Did they mess up in the key validation/generation and leave the priv key exposed somehow? Or, knowing Rigol, something dumber I wouldn't put these scopes on the internet, given that they have SSH exposed. Best to keep them isolated!
It would be impressive if it was verified. What is impressive is olivers repo, and tv84s infomation. This is the internet, been around way too long and am probably very cynical, but seen lots of claims of things, and have learned until you can actually verify things, you can't put much weight on them.
Thanks
Just dropping a nother note here however,
it is all WiP and any damages to your scope are not my responsibility nor fault. Can't iterate this often enough, as I have not tested everything very well yet (the scripts on the scope) as I do not have one yet
What I really want at some point however is (broken scope anyone
) is to desolder all parts and 'sand down' the PCB with pictures, as I want to know where all the ZYNQ pins connect too :p
What I really want at some point however is (broken scope anyone ) is to desolder all parts and 'sand down' the PCB with pictures, as I want to know where all the ZYNQ pins connect too :p
This might be a job for an Xray inspection? Not sure how many layers the PCB is of course..
If you want to see something funny, try this:
Connect generator 1 to CH1, enable and change to square. Manually enter 999kHz as frequency then observe the waveform change when increasing to 1MHz.
Not worth 269$.
Interesting watch.... changed the frequency halfway through and some nasty jitter disappeared
https://www.dropbox.com/s/93mhrk51i9q0ubh/IMG_7637.MOV?dl=0
We should start a new thread for those numerous bugs.
I have quite a few:
- Generator, the knob to change the frequency: turn left -> -10 , turn right +1
and some severe ones
- CH1, probe to ground: never read 0V, but depends on vertical scale:
acquisition Normal
10V ~10V
5V ~ 8V
2V ~ 5V
1V ~ 1V
500mV ~ 1.3V
200mV ~ 280mV
100mV ~ 320mV
50mV ~ -20mV
20mV ~ 4mV
10mV ~ 12mV
5mV ~ 15mV
2mV ~ out of scale
1mV ~ out of scale
- CH1: the thickness of the trace is almost 1 scale large
CH1+CH2: the thickness is divided by 2
that's almost impossible to read a value.
And I have a lot more.
- Generator, the knob to change the frequency: turn left -> -10 , turn right +1
- CH1, probe to ground: never read 0V, but depends on vertical scale:
Generator Knob behaves like this only when decrasing from like 1MHz to sub 1Mhz (or 1kHz to Hz).
This is because the increments above 1Mhz are in 10kHz steps and the first decrement therefore is as well. If you are then in the kHz-range the decrements are 1kHz. I don't think this is a bug.
For your CH1 problem, this does not happen on my scope, probe to GND always reads 0V (more or less).
Also you have to adjust the scale of the math channel, this normally would be the larger scale setting of the two channels (when operation A+B is chosen).
What I really want at some point however is (broken scope anyone ) is to desolder all parts and 'sand down' the PCB with pictures, as I want to know where all the ZYNQ pins connect too :p
This might be a job for an Xray inspection? Not sure how many layers the PCB is of course..
Well its worth a try sure; but it's a 4 or probably 6 layer board, with chips ontop. So it can give you an indication, very roughly. Best way is to just the PCB down layer for layer and scan the PCB.
But first a scope needs to break
or we raid the PCB factory's trash-bin where they dump broken PCB's
Well its worth a try sure; but it's a 4 or probably 6 layer board, with chips ontop. So it can give you an indication, very roughly. Best way is to just the PCB down layer for layer and scan the PCB.
But first a scope needs to break or we raid the PCB factory's trash-bin where they dump broken PCB's
Access to an industrial X-ray tomography machine anyone? That should do the trick non-destructively.
- Generator, the knob to change the frequency: turn left -> -10 , turn right +1
- CH1, probe to ground: never read 0V, but depends on vertical scale:
Generator Knob behaves like this only when decrasing from like 1MHz to sub 1Mhz (or 1kHz to Hz).
This is because the increments above 1Mhz are in 10kHz steps and the first decrement therefore is as well. If you are then in the kHz-range the decrements are 1kHz. I don't think this is a bug.
For your CH1 problem, this does not happen on my scope, probe to GND always reads 0V (more or less).
Also you have to adjust the scale of the math channel, this normally would be the larger scale setting of the two channels (when operation A+B is chosen).
I took my old trusted DS1052E, connected MSO5.CH1 to DS1052E.TestSignal:
(RigolDS1.png)
1V offset from ground.
(exact same behaviour as the MSO5.TestSignal)
I then plugged DS1052E.CH1 to MSO5.TestSignal:
(NewFile0.bmp)
The test signal is perfect, ground aligned.
When I unplug every channel on the MSO, no one goes to gnd.
(RigolDS0.png)
And with the math(A+B), it just confirms the numbers, the crap B is reading.
(rigolDS2.png)
I really don't understand what's going on, bad scope?
Did you use the same probe in both scopes?
yes, even swapped every probes (2x100MHz, 4x350MHz), always the same result.
[edit] I'm now running the self cal procedure (manual didn't ask that, but meh, let's see)
I'm now running the self cal procedure
Please record how long it takes.
Much better after a self cal.
All channels properly aligned on gnd now.
It took almost one hour.
That's pretty embarrassing, self-cal won't work, it still produces that overshoot on measuring the 1khz square wave signal. Not only my scope like that, but we also have about four scopes have the same problem, this 4 scope contains one scope that is currently not patched. The not patched scope has the same behavior.
Are you using the probe in x1 oder x10 config? I can see a little overshoot in x1 mode but it can be perfectly flattened in x10.
That's pretty embarrassing, self-cal won't work
Have you disconnected all probes from the inputs before running self-cal?
I disconnected all input, absolutely.
That is no difference between x10 and x1. No matter how you adjust the probe, the little overshoot won't disappear.
And now, average(64) + fine + aliasing does something : a very fine trace (1px). To All: Do run a self cal.
TopLoser is playing with Photoshop...