Here's my attempt to catalog the bugs and wish list items for the Rigol DS1000Z oscilloscopes.
...(snip)...
The scope only uses the screen memory buffer for decoding. You pretty much need to be able to see all the bits in each character yourself for accurate decoding. It's a severe limitation and one that Rigol will hopefully address in a future upgrade, it's (B) on the wishlist at the top of this thread.
I'm debugging an SPI communication issue with a chip that uses SPI mode 3, and while using the Rigol DS1000Z's SPI decoding, I noticed something odd:
It decodes individual bits in an 8-bit SPI transfer as '0xFF'.
This happens when 'Polarity' is (incorrectly) set to GND=1 - otherwise it decodes it as '00' which is not incorrect but confusing enough for a 1 bit value. Edge is set to 'falling'; when set to rising edge (which is what I need) it doesn't decode at all. Likewise, if I change Polarity it doesn't decode either. Width is set to 8. If I zoom out further, it doesn't decode the full 8 bit 'packet' either, just the individual bits.
Bug, or am I just missing something?
DS1074Z-S 'upgraded', Software Version 00.04.03.SP1, Board Version 4.1.1.
I suspect there may be something not quite right with your decoder set up, maybe the CLK/CS/MOSI not assigned to the correct channels?
I suspect there may be something not quite right with your decoder set up, maybe the CLK/CS/MOSI not assigned to the correct channels?
Yeah, but I checked every setting available multiple times. CLK, CS and MOSI are certainly correct.
I only started seeing this when I went to set it up for SPI mode 3, i.e. active low CLK and on rising edge - it successfully decoded packets in a SPI mode 0 setup before, with otherwise unmodified settings.
See photo: I tried all four SPI modes, all OK.
See photo: I tried all four SPI modes, all OK.
Strange. I think I'll do a factory settings reset later just to be sure, and then try to reproduce it and post the exact settings.
What firmware are you running on? Also, you're using an MSO, which I think is subtly different hardware/firmware especially in the logic analyzer / decoding department, isn't it? That may or may not make the difference as well...
I'm not with the scope right now, but it's the version DS/MSO1000Z version that was released about a month or so ago that everyone's complaining about the UI response speed, ISTR 04.03.02.03. Board version 6.1.1.
There may be some differences, but I deliberately left the MSO channels off and used the same channels as you and the same settings to the extent that I could see (and guess!).
I have an MSO 1104z. Nice Scope for the money. I wish they would have chosen green for the channel 2 or 4 trace. I often use all four channels, and sometimes get channels 2 and 4 (light and dark blue) mixed up when changing circuit test points. A better match of the probe color rings to the corresponding traces would be nice.
13) RAW mode of data acquisition over USB returns garbage, rather than the waveform.
3) The FFT function only works for channel 1. However it will work for the other channels as long as channel 1 is turned on.
There is, however, a new bug: the TMC command :MATH:SOUR1 CHAN1 or :MATH:SOUR1 CHAN2 is ignored by the scope,
so, it's impossible to select the source channel for the FFT via remote connection.
Hello Karel,There is, however, a new bug: the TMC command :MATH:SOUR1 CHAN1 or :MATH:SOUR1 CHAN2 is ignored by the scope,
so, it's impossible to select the source channel for the FFT via remote connection.
Test following:
:MATH:FFT:SOUR? // ok - entgegen S.107
:MATH:FFT:SOUR CHAN1 // ok - entgegen S.107
LG Wolfgang
Thanks but that doesn't work either.
And Rigol's programming guide from July 2015 says :MATH:SOUR1 CHAN1
*IDN?
RIGOL TECHNOLOGIES,DS1104Z,DS1ZAxxxxxxxx,00.04.03.SP2
:MATH:FFT:SOUR?
CHAN2
:MATH:FFT:SOUR CHAN1
:MATH:FFT:SOUR?
CHAN1
Hello Karel,Thanks but that doesn't work either.
And Rigol's programming guide from July 2015 says :MATH:SOUR1 CHAN1
It does work ! Look at my Log & Picture before and after ...
I know, the Manual does say an other syntaxCode: [Select]*IDN?
RIGOL TECHNOLOGIES,DS1104Z,DS1ZAxxxxxxxx,00.04.03.SP2
:MATH:FFT:SOUR?
CHAN2
:MATH:FFT:SOUR CHAN1
:MATH:FFT:SOUR?
CHAN1
LG Wolfgang
I believe I found another bug.
When the FFT is activated in splitscreen and "trace" mode, when you remotely change the horizontal timebase, the string
"FFT: CH2 10.00 dBV 12.5KHz/Div 500K Sa/s" will not be updated and as a result will show wrong values.
:SYST:KEY:DECR HSCALE,1
But when you turn the Horizontal-Knob remotely, then it works.Code: [Select]:SYST:KEY:DECR HSCALE,1
What is this, another undocumented "feature" of Rigol?