Products > Test Equipment
New Rigol HDO1000 12-bit DSO - BUGs
dominicc:
There's a bug with the SPI trigger thresholds in FW 00.02.07, and probably earlier:
Steps to repeat:
1) Setup 4 channels on SPI CS/CLK/MOSI/MISO using a 3.3v p-p SPI signal.
2) Adjust each channel to a non-zero offset.
3) Change the trigger to SPI trigger, using CS to trigger with a 1.5V.
4) Configure SPI decoding, Set the SPI decoding levels to 1.5V on each channel.
5) Ensuring the decode event view is visible and displaying correct data.
6) Now go back into the trigger and simply change the CS channel to a different channel and back again.
7) Observe the event view is now empty, this is because the SPI decode trigger levels have changed (!!!)
8) Now go back into the SPI decode setup, observe all the trigger levels still show 1.5V (!!!)
9) Now click one, observe the UI now shows it’s current value, which is different to 1.5V (!!!)
10) Adjust them all back to 1.5V, and observe that the event view is again correct.
See video recorded from the webui:
Other things, other than the Step 6 above, also cause the issues with incorrect or reset trigger levels. For instance, turning off and on and on any channel will reset one or more to 0v.
I've reported this to my supplier and will follow up with Rigol based on their response.
dominicc:
The rotary encoders on my DHO4204 aren't reliable, as this video demonstrates:
It feels like the light isn't passing through some of the holes in the encoder wheel as the issue is present at the exact same spot on the dial. I've not taken mine apart, just guessing based on what I know about how MCUs process the signals from a rotary encoder (example attached).
dominicc:
Has anyone been able to get the video triggering working on a PAL or NTSC signal?
I can't get it to work here... (see images attached).
It works OK on my old DS1074Z with the same signal... Did I miss something?
maxwell3e10:
When saving data to .csv file in full memory format the x-scale tInc is wrong. Sometimes it is the same as for "screen" format- which only has 1000 points, but other times seems to be off by another factor. So often one cannot tell the time axis of the data saved.
When the scope is running in average acquisition mode, it stops triggering randomly and one needs to press "run" again.
hfiennes:
Just got my DH1074 today, and I'm having issues with i2c decode.
Basically, the scope is always assuming 10 bit addressing. There is nowhere to set 10 bit (I guess the "without/with" sets 7/8 bit) so I can't clear it. I've tried setting 7 bit addressing in the I2C trigger and copying this across with the "copy trig" button in the decoder setup, but no luck.
It came with 2.00 and have updated to 2.11, but the bug persists. Anyone else see this? I was going to try a factory reset in case there's something randomly stale, but couldn't find one of those either.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version