Products > Test Equipment
Siglent SDS2000 new V2 Firmware
nctnico:
--- Quote from: smarteebit on July 19, 2016, 01:11:40 am ---I'm waiting for nctnico pouring oil on the flames. That should be funny. >:D
--- End quote ---
I just sit and watch the sad story continue :popcorn:
In a contorted way I'm glad I got so angry that I dumped the SDS2000 and bought some different scopes which just work otherwise I'd be like this:
tautech:
--- Quote from: TheDefpom on July 18, 2016, 11:11:33 pm ---I also just found this bug... at a certain timebase (500us) it glitches the display, showing high and low states at the same time, until you change the timebase to 200us, and then switch it back to 500us again, then it displays correctly, odd.
I just adjusted the memory depth to 14M (it had reduced itself to 1.4M) and the glitching went away, I also noticed the sample was not actually correct, as it is supposed to trigger on D0, and yet there was data showing before D0 ? closer inspection shows the data to be garbage.
--- End quote ---
Scott, from the info we have above I have some feedback from Siglent.
First Roll mode.
Particular to the SDS2000 series we know that Roll mode is auto engaged at slow timebase settings.
This can be overridden in both the 2000 and 2000X but each with a different method.
SDS2000: Select Horizontal key and then YT
SDS2000X: Select Roll key and toggle between Roll and YT modes.
Observed high and low glitches. (screenshots)
When the screenshot is taken (we think due to the display update) we get a displayed state where the high and low states at the same time are captured but not all the time or repetitively.
Stop the waveform for confirmation of the correct waveform.
As for the other decoding issues they are decoding setup as discussed privately and you've indicated that you'll do more with decode in the following days.
TheDefpom:
Thanks for the feedback.
The display glitch shows up on normal trigger mode (taken 1 sample only) so it is not an issue with repeated triggering causing a doubled display), it is only triggering once in this case.
TheDefpom:
I am just doing some more testing, if I stop the scope (from in Normal triggering), the data at the bottom does indeed scale with the sample (it does not do this when in normal trigger mode and has only been triggered once, displaying the same sample).
If I stop the scope when I have the glitch present, the glitch goes away, in the same was as if I change timebases, OR if I adjust the trigger position in either direction.
HOWEVER, the sample displayed is not correct, if you look at the first screen shot below, this sample is at 1ms, that is the true sample taken, the second screen shot (under exactly the same conditions, same sample etc) with a faster timebase of 500us if very different, not just twice is big, as you would expect it to be, as per the third screen shot, which is the 1ms sample, stopped and with the timebase increased to 500us (to be effectively the same), these are all set at 1.4M memory, which is when the glitch occurs (it doesn't do this at 7M etc)
Also I checked the YT vs ROLL setting, I already have it set to YT, perhaps this setting should "stick" regardless of timebase setting, so it stays set on the selected mode (digital) triggering, and trigger input. Don't forget it also changes the trigger input from my configured D0 inpu, to CH1 and jumps to auto triggering at the same time, even if I put the timebase back to 20ms CH1 stays, as does Auto trigger (but it does turn digital back on), basically it fails to remember the set configuration and return to it properly, it goes to some kind of defaults overriding what was set, ideally it try to be less smart here, and lets me do what I am trying to do, even if it will be slow to update the screen, I tried setting YT at the slow timebase and then set my trigger back to normal, and the trigger input back to D0, it works fine (but slow as expected).
TheDefpom:
Also, if you look at the glitched screen shots, it looks like it is overlaying two samples of two different timebases, as they line up perfectly with some of the sample at the other timebase.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version