Products > Test Equipment

Siglent SDS2000 new V2 Firmware

<< < (42/56) > >>

tautech:
New FW for the SDS2000 (not X) series:
http://www.siglentamerica.com/USA_website_2014/Firmware&Software/firmware/SDS2000%20P3301.rar


From the changelog:

1. Improved the user experience on the universal knob
2. Added virtual numeric keypad function in cases inputting large number is possible (push the universal knob to call it)
3. Optimized the persistence display in pass/fail mode
4. Added ASCII decoding
5. Fixed some bugs
a) Pushing the trigger level knob in AC coupled trigger mode does not bring the level back to zero
b) Value jumps up and down when setting baud rate in trigger setting
c) Arrow in decoding list displays abnormally
d) Digital channel display problem
e) All frames are not mapped to the display in sequence mode with frames quantity > 1024


Edit
fix URL

rf-loop:
Small improvement-bugfix  in serial decoding.

It is not yet free of all bugs. One example is in image. When there is RX TX and here example TX (in this case CH2) is shut off it copy CH1 (RX here) to TX.
But, overall it works now lot of better!

Now it can decode and display also ASCII  as also HEX and Binary.
Hope they later do some finishing for visibility including also font in decode displays.

rf-loop:

--- Quote from: Performa01 on January 07, 2016, 04:32:24 pm ---


--- Quote ---There is one open question.
Example. Sequence mode. If example in one sequence is 80000 segments. After these are acquired then acquisition of course stop and scope start do many things including display update for show waveform before it start new sequence. Question is, how many segments it display overlayed on the display before it start new sequence. It is least some hundreds in this case but how much really?

--- End quote ---

I might have finally found a way to estimate this. After several experiments I believe that the scope just displays any (the first  - or last – or whatever?) 750 +/-50 waveforms for every filled buffer.

I got these results rather consistently for 80000 segments at timebases from 1 to 10ns/div (used Ch. 4 again, but that probably doesn’t matter in this case). Not tested anything else yet.

--- End quote ---

It strongly looks like that last FW update have changed this.  I have not now enough time for test it using SDS2304 but with tiny fast test with SDS1202X give sign that now it overlay all acquired segments in sequence to display after sequence is ready. And fast look with SDS2304 looks like doing same. But, this lounge is not free. Price is that it need more process time between sequences depending amount of segments in sequence and also depending display settings.
But, imho this is low price for this improvement.

Performa01:

--- Quote from: rf-loop on April 20, 2016, 12:30:37 pm ---It strongly looks like that last FW update have changed this.  I have not now enough time for test it using SDS2304 but with tiny fast test with SDS1202X give sign that now it overlay all acquired segments in sequence to display after sequence is ready. And fast look with SDS2304 looks like doing same. But, this lounge is not free. Price is that it need more process time between sequences depending amount of segments in sequence and also depending display settings.
But, imho this is low price for this improvement.

--- End quote ---

So this might be item e) from the changelog?

e) All frames are not mapped to the display in sequence mode with frames quantity > 1024

I think dead time in sequence mode is not that important anyway, as the whole idea of sequence recording is to capture any rare event within one sequence. Obviously, when we set up a sequence recording, we already need to have an idea of what we're trying to capture, so we can choose the parameters such as timebase and memory depth (which in turn determines the maximum acquisitions in the sequence buffer) appropriately.

On the other hand, if all buffer data is mapped to the screen and if the average trigger rate is actually higher than in standard recording mode (just with background history), it might have some uses in glitch finding.

That being said, I'm not a huge fan of the waveform update rate hype with some made-up test scenarios. Up to now I've always found other means to isolate glitches. But then again, a reasonable fast update rate does have its charm, particularly when the mask testing works the same speed, as is the case with these scopes.  :-+

I have not updated my SDS2304 yet, but will certainly do within the next couple days and then have a brief look at what Siglent have given us. ;)

rf-loop:

--- Quote from: Performa01 on April 20, 2016, 01:01:53 pm ---
--- Quote from: rf-loop on April 20, 2016, 12:30:37 pm ---It strongly looks like that last FW update have changed this.  I have not now enough time for test it using SDS2304 but with tiny fast test with SDS1202X give sign that now it overlay all acquired segments in sequence to display after sequence is ready. And fast look with SDS2304 looks like doing same. But, this lounge is not free. Price is that it need more process time between sequences depending amount of segments in sequence and also depending display settings.
But, imho this is low price for this improvement.

--- End quote ---

So this might be item e) from the changelog?

e) All frames are not mapped to the display in sequence mode with frames quantity > 1024

I think dead time in sequence mode is not that important anyway, as the whole idea of sequence recording is to capture any rare event within one sequence. Obviously, when we set up a sequence recording, we already need to have an idea of what we're trying to capture, so we can choose the parameters such as timebase and memory depth (which in turn determines the maximum acquisitions in the sequence buffer) appropriately.

On the other hand, if all buffer data is mapped to the screen and if the average trigger rate is actually higher than in standard recording mode (just with background history), it might have some uses in glitch finding.

That being said, I'm not a huge fan of the waveform update rate hype with some made-up test scenarios. Up to now I've always found other means to isolate glitches. But then again, a reasonable fast update rate does have its charm, particularly when the mask testing works the same speed, as is the case with these scopes.  :-+

I have not updated my SDS2304 yet, but will certainly do within the next couple days and then have a brief look at what Siglent have given us. ;)

--- End quote ---

Yes, roughly agree.

But I see it important if all segments are mapped to display after sequence ready. This way after sequence is easy to see  if acquired segments have some anomalies. (I do not mean "usual" thinking about rare random glitch hunting)

What I hope Siglent also improve. History view function need develop so that there is more tools. When we stop scope for looking normal bacround stored history or sequence mode captured segments I hope they add user adjustable cumulative overlay mode when run playback and/or least persistence in playback. Even many old HP have this overlay mode when playback stored segments. Fast way to look if there is anything what need look more deeply.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod