SDS800X HD Bug Reports + Firmware

[eTobey]

I saved settings before, and after restart for the trigger settings lost issue. Maybe some other settings get lost also?

[ebastler]

Another issue: i am pretty sure i could use the b-word:
The setting of the trigger type edge influences the qualified trigger. In the first part of the video the trigger is not exactly stable, only if the slope of edge trigger is changed, the qualified triggers works without issues.

That is a strange one... Did you check the details of the qualified trigger settings before and after the edge trigger change? I.e. did anything get changed in the displayed settings for the qualified trigger, as a side effect of the change you made to the edge trigger?

[electronics hobbyist]

The setting of the trigger type edge influences the qualified trigger. In the first part of the video the trigger is not exactly stable, only if the slope of edge trigger is changed, the qualified triggers works without issues.

These two issues look the same and have been added to Bug No.14.

https://www.eevblog.com/forum/testgear/sds800x-hd-featureimprovment-disscusions/msg5459225/#msg5459225

[electronics hobbyist]

I found a bug:
When adjusting the level for source A in "trigger delay", and setting it below low level of signal, acquire stops. At 50% level it triggers kind of slow, but below the rate increases, but then eventually stops completely. The trigger does not restart after moving it back.

This problem is related to the signal. It requires that the signal of both channels is above or below zero level. Added to Bug No.15.

[eTobey]

Zoom function not working properly after loading mask:
Creating a mask and loading breaks the zoom function. See picture.

Also:
Creating a mask does not show the view that was set up for it.

I really would like that this feature "would" work with the zoom.

[2N3055]

Zoom function not working properly after loading mask:
Creating a mask and loading breaks the zoom function. See picture.

Also:
Creating a mask does not show the view that was set up for it.

I really would like that this feature "would" work with the zoom.

It does work.
You did not set it up properly.

[ebastler]

Still, something is wrong in the screenshot eTobey shared. Mask details aside, the zoomed view does not show the time window indicated in the upper window. What happened there?

[2N3055]

Still, something is wrong in the screenshot eTobey shared. Mask details aside, the zoomed view does not show the time window indicated in the upper window. What happened there?

I have no idea.
I have shown how it looks on mine.

[eTobey]

Zoom function not working properly after loading mask:
Creating a mask and loading breaks the zoom function. See picture.

Also:
Creating a mask does not show the view that was set up for it.

I really would like that this feature "would" work with the zoom.

It does work.
You did not set it up properly.

You missed a little detail: i made a custom mask by hand.

[eTobey]

Another little issue:
The timout counter for closing the menu is not restart, when a sub menu settings is choosen. At least on cursors menu and search menu, and i guess on every menu.

Not a big one, but still annoying and confusing.

[2N3055]

Zoom function not working properly after loading mask:
Creating a mask and loading breaks the zoom function. See picture.

Also:
Creating a mask does not show the view that was set up for it.

I really would like that this feature "would" work with the zoom.

It does work.
You did not set it up properly.

You missed a little detail: i made a custom mask by hand.

I didn't miss anything. You are again posting things without proper setup and explanation.
You said mask does not work in zoom. It does.

If here are requisite tigers in the next room eating cheesecake to make bug appear, than that information needs to be shared.

[eTobey]

If here are requisite tigers in the next room eating cheesecake to make bug appear, than that information needs to be shared.

On the picture, there is a mask that has been obviously made by hand.

You should have seen that sign, that said "Tigers room 22", but yes, it would have helped from my side to say, that they were eating cheesecake. In fact i didnt know, that the cheesecake was of importance.

[2N3055]

If here are requisite tigers in the next room eating cheesecake to make bug appear, than that information needs to be shared.

On the picture, there is a mask that has been obviously made by hand.

You should have seen that sign, that said "Tigers room 22", but yes, it would have helped from my side to say, that they were eating cheesecake. In fact i didnt know, that the cheesecake was of importance.

And again, smartass, antisocial, but so true to you signature on your account.

"Sometimes, after talking with a person, you want to pet a dog, wave at a monkey, and take off your hat to an elephant." (Maxim Gorki)

After talking to you I do marvel at how nice and intelligent monkeys are..

Your apology was obviously just a manipulation not to get blocked so you get to keep being obtuse troll.

[KungFuJosh]

I don't know what you guys are talking about, but now I want cheesecake.

[eTobey]

I don't know what you guys are talking about, but now I want cheesecake.

Get the ingredients, i bake one for us. But be warned, i have never done this  .

Another issue:
Level indicator is wrong in zoom modus. It is not right in the bottom window (find the arrow).

[eTobey]

And again, smartass, antisocial, but so true to you signature on your account.

"Sometimes, after talking with a person, you want to pet a dog, wave at a monkey, and take off your hat to an elephant." (Maxim Gorki)

After talking to you I do marvel at how nice and intelligent monkeys are..

Your apology was obviously just a manipulation not to get blocked so you get to keep being obtuse troll.

You have to see the beauty of this signature, you can put yourself on which ever side you want.

You may want to read what i wrote about that teamwork we somehow uintentionally did together, and realize that we could get along quite nicely if... I just used your creative  example, in which i actually acknowledged, that i could have done better. As i was meaning before, it might help to forget what there was before. 

[ebastler]

Level indicator is wrong in zoom modus. It is not right in the bottom window (find the arrow).

I can confirm this one. It applies to Qualified and Delay triggers; seems to work OK with other trigger modes.
Steps to reproduce:

Trigger threshold for Qualified and Delay triggers is displayed incorrectly in Zoom mode

Test signal:
None required; leave inputs open.

Scope settings:
- Start from Default mode
- Set trigger mode "Qualified" or "Delay". Leave all other trigger settings at default values.
- Switch axis labels on -- just to visualize the problem more clearly
- Switch zoom mode on
- In the lower window, increase vertical amplification -- e.g. two steps, to 200 mV/div
- Adjust the trigger threshold via the rotary encoder, and observe the screen

Observed behavior:
- The trigger threshold is displayed as a dashed line, both in the upper and lower window.
- Its position is correct in the upper window.
- In the lower window, its position is incorrect. It ignores the different vertical scale in the lower window.

[2N3055]

Level indicator is wrong in zoom modus. It is not right in the bottom window (find the arrow).

I can confirm this one. It applies to Qualified and Delay triggers; seems to work OK with other trigger modes.
Steps to reproduce:

Trigger threshold for Qualified and Delay triggers is displayed incorrectly in Zoom mode

Test signal:
None required; leave inputs open.

Scope settings:
- Start from Default mode
- Set trigger mode "Qualified" or "Delay". Leave all other trigger settings at default values.
- Switch axis labels on -- just to visualize the problem more clearly
- Switch zoom mode on
- In the lower window, increase vertical amplification -- e.g. two steps, to 200 mV/div
- Adjust the trigger threshold via the rotary encoder, and observe the screen

Observed behavior:
- The trigger threshold is displayed as a dashed line, both in the upper and lower window.
- Its position is correct in the upper window.
- In the lower window, its position is incorrect. It ignores the different vertical scale in the lower window.

Will check .. Thanks.

[2N3055]

And again, smartass, antisocial, but so true to you signature on your account.

"Sometimes, after talking with a person, you want to pet a dog, wave at a monkey, and take off your hat to an elephant." (Maxim Gorki)

After talking to you I do marvel at how nice and intelligent monkeys are..

Your apology was obviously just a manipulation not to get blocked so you get to keep being obtuse troll.

You have to see the beauty of this signature, you can put yourself on which ever side you want.

You may want to read what i wrote about that teamwork we somehow uintentionally did together, and realize that we could get along quite nicely if... I just used your creative  example, in which i actually acknowledged, that i could have done better. As i was meaning before, it might help to forget what there was before. 

Your idea of teamwork is that all of us do the work for you...

[ebastler]

Your idea of teamwork is that all of us do the work for you...

From eTobey's side, it might feel like he is doing work for Siglent? -- You have to grant it to him: He has found a surprising number of bugs and rough edges within a short time.

Frankly, I am kind of OK with the "division of labor". It would not be my thing to play around and try features in all sorts of combinations, hence I would not have found most of these glitches any time soon. On the other hand, I like to work systematically, try to reproduce things and reduce them to the simplest possible scenario. So why not divide tasks according to personal preferences and strengths?

If Siglent then does their part and works on fixing the issues -- which seems to be happening right now -- everybody benefits.

[eTobey]

Your idea of teamwork is that all of us do the work for you...

From eTobey's side, it might feel like he is doing work for Siglent? -- You have to grant it to him: He has found a surprising number of bugs and rough edges within a short time.

Frankly, I am kind of OK with the "division of labor". It would not be my thing to play around and try features in all sorts of combinations, hence I would not have found most of these glitches any time soon. On the other hand, I like to work systematically, try to reproduce things and reduce them to the simplest possible scenario. So why not divide tasks according to personal preferences and strengths?

If Siglent then does their part and works on fixing the issues -- which seems to be happening right now -- everybody benefits.

Amen!

[ebastler]

I can confirm this one. It applies to Qualified and Delay triggers; seems to work OK with other trigger modes.

Will check .. Thanks.

Thanks for looking into this.

Looking back over the past few days, it seems like Qualified and Delay trigger are problematic in multiple ways: Bug entries #14 to #16 refer to them, now this new "trigger threshold in zoom mode" issue; they also both have a less-than-obvious UI and very sparse documentation in the manual.

I noticed that the SDS2000X+ manual does not mention them, so these two trigger types were probably added later and have not seen as much field testing as the rest of the firmware? I realize that it's probably very late in the game for the firmware update currently in the works, but if there's still a chance to overhaul Qualified and Delay triggers, that would make them a stronger part of the offering.

Come to think of it -- it seems that the Nth Edge and Setup/Hold triggers are also later additions which were not in the original 2000X+. Maybe they deserve some extra scrutiny too? I'll try to find some time tomorrow.

[2N3055]

I can confirm this one. It applies to Qualified and Delay triggers; seems to work OK with other trigger modes.

Will check .. Thanks.

Thanks for looking into this.

Looking back over the past few days, it seems like Qualified and Delay trigger are problematic in multiple ways: Bug entries #14 to #16 refer to them, now this new "trigger threshold in zoom mode" issue; they also both have a less-than-obvious UI and very sparse documentation in the manual.

I noticed that the SDS2000X+ manual does not mention them, so these two trigger types were probably added later and have not seen as much field testing as the rest of the firmware? I realize that it's probably very late in the game for the firmware update currently in the works, but if there's still a chance to overhaul Qualified and Delay triggers, that would make them a stronger part of the offering.

Come to think of it -- it seems that the Nth Edge and Setup/Hold triggers are also later additions which were not in the original 2000X+. Maybe they deserve some extra scrutiny too? I'll try to find some time tomorrow.

Like I said, new FW is coming. That is all I can share.

[ebastler]

As suggested yesterday, I checked which of the "modern" triggers (Qualified, Delay, Nth Edge, Setup/Hold) are affected by the recently found trigger-related bugs, to get a complete picture. Results are mixed:

#17 Wrong trigger threshold displayed in zoom mode
Qualified, Delay, Setup/Hold are affected
Nth Edge is OK

#16 Trigger settings are lost upon reboot
Qualified, Delay, Setup/Hold, Nth Edge all forget their complete setup:
Assigned channels, thresholds, delay/timeout settings, edge count setting are lost.

#15 Normal trigger does no resume after wrong threshold is corrected
Delay trigger is the only one affected.
(Clarification: Only change of a Source A threshold in the dialog causes this.
Change of Source B threshold via trigger level knob is OK.)

Qualified, Nth Edge, Setup/Hold are OK.

#14 Edge trigger setting affects Qualified trigger operation
I could not reproduce this one at all.
More information about the settings is needed. @eTobey?

[electronics hobbyist]

#14 Edge trigger setting affects Qualified trigger operation
I could not reproduce this one at all.

When the edge is alternating, switching to interval also causes the trigger to have two lines. So the culprit is the edge alternating trigger. Before the new version is released, the only way is not to set the edge alternation.