Products > Test Equipment

Siglent SDS2000 new V2 Firmware

<< < (44/56) > >>

TheDefpom:
I have been using my SDS2102 the past couple of days on the latest firmware, using my logic probe function (digital), and have found several little bugs.

When viewing digital, and the B1 line at the bottom of the screen shows the value, if you zoom, the line does not expand with the sample (as shown in first 2 images, so you cannot zoom into the value.

When switching zoom on and off, of you were set to low in the channel height setting (to fill the screen), it forgets that when turning zoom back off, and goes back to middle.

If you then set the height to low again, and there is a sample on screen, the sample stays at the middle point, whilst the lines move to the low one (it may also do this in reverse, I didn't try).

If using Normal triggering, to get a sample at each change, and you try to adjust the timebase to be 50ms (more than 20ms), the digital turns off, and it goes to auto triggering, when turning back to 20ms it stays on auto triggering (why does it change trigger modes?), also if the Source menu is not being displayed at the time, it also forgets which triggering input that was selected, and swaps to CH1 instead of whatever digital channel was selected, even when switched back to digital.

I wish the digital did not stop at the 20ms time, and allowed it to sample for longer time periods, it shows as 14Mpts being used, but the scope is capable of more than that, even if it reduced the sampling frequency in order to get a longer capture time.

I also noticed that even though I had turned off lines D5, D6, D7, somehow they got turned back on again, I didn't notice when.

tautech:
Thanks Scott
When using slower than 20ms the scope goes into Roll mode but if you stay at 20ms and then if using the Zoom function the zoomed traces can be displayed at slow timebases as seen in your #5 image.

If you can add the image # to the text it may make things a little easier to follow.

I've just got a SDS2kX series (very similar) with MSO so I can work through these issues with you if that's any help.
Maybe we can do a workshop at your place to zero in on any issues?

Rob

TheDefpom:
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.

tautech:
I see some triggering issues, you have selected CMOS levels and rising edge, is this appropriate?
Are the TTL or User defined trigger settings better?

smarteebit:
I'm waiting for nctnico pouring oil on the flames. That should be funny. >:D

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