SDS800X HD Bug Reports + Firmware

[2N3055]

I saw this bug with 1.1.3.8 (and possibly earlier version, do not recall right now) so hopefully it will be included in next FW releases. Good to know it is acknowledged.
I know it is usability bug, nothing too critical. But it gets in the way very often.

It is only important when it was discovered and reported because that is the moment when someone can start fixing it.

And no need for apologetics. Bug is a bug, so fixing is in order. Criticality only applies to urgency.
As for how impactful it is, that will highly depend of what you do and how you use it.
It only obviously shows when you apply quite large offsets, and pay attention. I personally didn't notice, and I had the  scope much earlier than you...
I still see many people using these scopes without axis scales on...

But luckily, we are not all the same and everybody contributes some new value..

[eTobey]

I would not mind too much, of beeing used as a beta tester, as there are many functions for not so much money, but the bugs should be fixed ASAP then.  The grid is still not aligned with the numbers, which is REALLY BAD. That should have been fixed already. 

[eTobey]

Jeez, this thing is really naughty again (again). Two things at the same time. Tried to look for the file with the most recent date, but couldnt find it. Found out, that the time does not work of unknown reason! It worked before, but just not now. 

And then the next thing: loaded my mask, but now the level is wrong (see picture).

All those features, but ....


EDIT:
Wanted to move the level to fit the mask, it jumped back into the right position... 

[eTobey]

Wtf is this? Another issues appeared! The trigger is odd. When the level is at 151V, it triggers just fine on a 3.3V level pulse! Something must have crashed in the software, without an obvious sign.
https://youtu.be/22_viJaxcTI
https://youtu.be/99HdnPxrwTo

EDIT:
Issue dissapeared after restart. Scacle and position (maybe more?) of the problem channel changed though.

[tautech]

Jeez, this thing is really naughty again (again). Two things at the same time. Tried to look for the file with the most recent date, but couldnt find it. Found out, that the time does not work of unknown reason! It worked before, but just not now. 

And then the next thing: loaded my mask, but now the level is wrong (see picture).

All those features, but ....


EDIT:
Wanted to move the level to fit the mask, it jumped back into the right position... 

You should know better by now and post the FW version in use and the steps to reliably recreate any claimed bug.

All user error so let's break them down into the 3 issues and list them each.
1. As can be clearly seen NTP has not synced.
2. Loading a Setup and then a saved Mask may have been more successful.
3. You can't move a Mask.

[housemartin]

Whats the firmware update procedure?
Is it risky, can it brick your scope?

Simple via USB and the .ADS file from Siglent firmware download packages.
Done 100’s and never bricked a unit.

Latest for all SDS800X HD models is here:
https://int.siglent.com/download/firmwares/?ProId=74

You can also do the firmware via the web interface...

[2N3055]

Wtf is this? Another issues appeared! The trigger is odd. When the level is at 151V, it triggers just fine on a 3.3V level pulse! Something must have crashed in the software, without an obvious sign.
https://youtu.be/22_viJaxcTI
https://youtu.be/99HdnPxrwTo

EDIT:
Issue dissapeared after restart. Scacle and position (maybe more?) of the problem channel changed though.

I tried.

Channel 1 was set at 10x probe and 5V/div, 13V offset . Trigger set to pulse, negative. 1ms timeout. 1MPts, 20ms/div, time delay 1.25s, 5 MSa/s. 4 CH used.

I cannot reproduce (with data you published) neither 151V trig level (you cannot enter more than 7,5V with knob or keyboard) and Pulse-> Trigger level works normally.

[KungFuJosh]

I think the only way to fix those "bugs" is to have Siglent do some onsite training sessions. 😉

[eTobey]

Jeez, this thing is really naughty again (again). Two things at the same time. Tried to look for the file with the most recent date, but couldnt find it. Found out, that the time does not work of unknown reason! It worked before, but just not now. 

And then the next thing: loaded my mask, but now the level is wrong (see picture).

All those features, but ....


EDIT:
Wanted to move the level to fit the mask, it jumped back into the right position... 

You should know better by now and post the FW version in use and the steps to reliably recreate any claimed bug.

All user error so let's break them down into the 3 issues and list them each.
1. As can be clearly seen NTP has not synced.
2. Loading a Setup and then a saved Mask may have been more successful.
3. You can't move a Mask.

Where did i say the B-word? Of course its the current firmware 1.1.3.8
Yes NTP has obvioulsy not beeing synced. The reason is the scope failed to do so! I testet it before, and it worked, even with having the NTP server on AFTER the scope started. 
I meant the level of the signal of course.

This morning again, the CH1 settings were lost/changed. But at least the NTP server worked.

I am really tired of trying to reproduce issues, when they are rather hard to reproduce. One of the reason is you guys denying it, and letting me look bad, and the other is, that it will propably not beeing fixed by siglent in the near future as it seems. Just the grid not aligning is the best example. Should be an easy fix, but it hasnt been fixed. And this is a "cheap chinese device bug"... 

[eTobey]

Wtf is this? Another issues appeared! The trigger is odd. When the level is at 151V, it triggers just fine on a 3.3V level pulse! Something must have crashed in the software, without an obvious sign.
https://youtu.be/22_viJaxcTI
https://youtu.be/99HdnPxrwTo

EDIT:
Issue dissapeared after restart. Scacle and position (maybe more?) of the problem channel changed though.

I tried.

Channel 1 was set at 10x probe and 5V/div, 13V offset . Trigger set to pulse, negative. 1ms timeout. 1MPts, 20ms/div, time delay 1.25s, 5 MSa/s. 4 CH used.

I cannot reproduce (with data you published) neither 151V trig level (you cannot enter more than 7,5V with knob or keyboard) and Pulse-> Trigger level works normally.

If the user cant enter more than 7.5V trigger level, but the picture shows 151V, then it can be classified as a bug?

[2N3055]

Wtf is this? Another issues appeared! The trigger is odd. When the level is at 151V, it triggers just fine on a 3.3V level pulse! Something must have crashed in the software, without an obvious sign.
https://youtu.be/22_viJaxcTI
https://youtu.be/99HdnPxrwTo

EDIT:
Issue dissapeared after restart. Scacle and position (maybe more?) of the problem channel changed though.

I tried.

Channel 1 was set at 10x probe and 5V/div, 13V offset . Trigger set to pulse, negative. 1ms timeout. 1MPts, 20ms/div, time delay 1.25s, 5 MSa/s. 4 CH used.

I cannot reproduce (with data you published) neither 151V trig level (you cannot enter more than 7,5V with knob or keyboard) and Pulse-> Trigger level works normally.

If the user cant enter more than 7.5V trigger level, but the picture shows 151V, then it can be classified as a bug?

It can be classified as a photo with a number on it.

Look, don't start again. You are making drama about things that are supposed to be facts.

I didn't DISPUTE anything you say. I took your post seriously and I went and tried to reproduce.
I could NOT, based on information you gave.

That is all I said. If you can give us more info how you confused scope to show you that error, maybe somebody will be able to reproduce. And then we have something to report.

In meantime, what CAN we report to Siglent? If they cannot catch it happening how are they going to troubleshoot? What are they going to troubleshoot?

[ebastler]

I agree. There obviously is a bug: The trigger threshold gets displayed as 151 V, which is supposed to be well out of range and which is not the real threshold value applied. But we need to know more about the steps which preceded this -- ideally a step-by-step sequence that provokes the bug, or if that is not available, as much detail as possible on "what did I do before".

[eTobey]

Wtf is this? Another issues appeared! The trigger is odd. When the level is at 151V, it triggers just fine on a 3.3V level pulse! Something must have crashed in the software, without an obvious sign.
https://youtu.be/22_viJaxcTI
https://youtu.be/99HdnPxrwTo

EDIT:
Issue dissapeared after restart. Scacle and position (maybe more?) of the problem channel changed though.

I tried.

Channel 1 was set at 10x probe and 5V/div, 13V offset . Trigger set to pulse, negative. 1ms timeout. 1MPts, 20ms/div, time delay 1.25s, 5 MSa/s. 4 CH used.

I cannot reproduce (with data you published) neither 151V trig level (you cannot enter more than 7,5V with knob or keyboard) and Pulse-> Trigger level works normally.

If the user cant enter more than 7.5V trigger level, but the picture shows 151V, then it can be classified as a bug?

It can be classified as a photo with a number on it.

Look, don't start again. You are making drama about things that are supposed to be facts.

I didn't DISPUTE anything you say. I took your post seriously and I went and tried to reproduce.
I could NOT, based on information you gave.

That is all I said. If you can give us more info how you confused scope to show you that error, maybe somebody will be able to reproduce. And then we have something to report.

In meantime, what CAN we report to Siglent? If they cannot catch it happening how are they going to troubleshoot? What are they going to troubleshoot?

What is your bloody problem? There was a question that could be answered with "yes" or "no", but you make a dram out of it, and telling me to not start something? I am not starting anything, i am documenting issues (if you dont like the b-word).

As for Siglent:
There would be a possibility to implement plausible catches, that would catch this bug and then save debug data...

[voltsandjolts]

In meantime, what CAN we report to Siglent? If they cannot catch it happening how are they going to troubleshoot? What are they going to troubleshoot?

The videos demonstrate the issue. Reporting this alone can lead to a fix, if the firmware engineer reviews the relevant code and then see's how it could get into such a fault state. Yes, it is better to have a sequence of events to reproduce the fault, but sometimes that is just not possible, especially with the complexity of modern firmware.

[2N3055]

In meantime, what CAN we report to Siglent? If they cannot catch it happening how are they going to troubleshoot? What are they going to troubleshoot?

The videos demonstrate the issue. Reporting this alone can lead to a fix, if the firmware engineer reviews the relevant code and then see's how it could get into such a fault state. Yes, it is better to have a sequence of events to reproduce the fault, but sometimes that is just not possible, especially with the complexity of modern firmware.

Video demonstrates nothing.

It shows screen with some weird numbers.

It was not explained what he was doing to achieve that state. It can be fake video for all we know (which I'm not saying it is), until someone replicates steps.

I said that I took it seriously, performed investigation, tried several ways of doing things and nothing.
He himself cannot reproduce it.

So what do we report? Pretty please  magical fix to something that happened once to one person out of 10s of thousands ?

I will repeat: I do not contest he had something happen.
But what do we do: go to service, give the car keys and say: "I am not happy, while I was driving something happened. Please fix it!!"

[watchmaker]

Two requests:

Ability to select colors for channel and math traces.  This would also improve usability for the those with visual color impairments.

Also, and I know this has been mentioned earlier, but it would be real nice if the Math Function was mouse selectable.  On the screen bottom maybe??

Regards,

Dewey

[2N3055]

Two requests:

Ability to select colors for channel and math traces.  This would also improve usability for the those with visual color impairments.

Also, and I know this has been mentioned earlier, but it would be real nice if the Math Function was mouse selectable.  On the screen bottom maybe??

Regards,

Dewey

Hi.

800xHD is simplest touchscope they make. AFAIK custom colors are not planned.

As for math channels, if you click on (+) at bottom to make a new channel, you can create math channel there directly.
If Math channel is already active, clicking to on it brings Math menu back. Hope that helps.

[watchmaker]

  ^

THANKS!

[awakephd]

Is there a way to configure the 804 not to ask for confirmation when the Auto key is pressed? If not, it is certainly not a bug, but it is a wish - or at least, I would like to be able to turn that confirmation off. Not sure if others would like this as well. Or if I just haven't yet figured out how to turn it off!

[tautech]

Is there a way to configure the 804 not to ask for confirmation when the Auto key is pressed? If not, it is certainly not a bug, but it is a wish - or at least, I would like to be able to turn that confirmation off. Not sure if others would like this as well. Or if I just haven't yet figured out how to turn it off!

Well take this as you like....don't use it !

Alternatives are:
Configuring your own User Default.
Saving and recalling preferred Setups.

[KungFuJosh]

Does hitting the button a second time bypass the confirmation?

[Martin72]

800xHD is simplest touchscope they make. AFAIK custom colors are not planned.

I had suggested the custom colors for the SDS2000Xplus at the time and also “got” them.
The SDS800X HD has two extras that the SDS2000Xplus did not get for performance reasons: 4 math channels and digital filters.
So it seems that the 800X HD is not that simple, an implementation of custom colors seems possible from that point of view - just not wanted, for obvious reasons.

[tautech]

800xHD is simplest touchscope they make. AFAIK custom colors are not planned.

I had suggested the custom colors for the SDS2000Xplus at the time and also “got” them.
The SDS800X HD has two extras that the SDS2000Xplus did not get for performance reasons: 4 math channels and digital filters.
So it seems that the 800X HD is not that simple, an implementation of custom colors seems possible from that point of view - just not wanted, for obvious reasons.

SDS1000X HD also doesn't support custom colors and I suspect that will remain as a point of difference between 800 and 1k models vs 2k+ models.

[Cyclotron]

Does hitting the button a second time bypass the confirmation?

Yes, second push does for me. And pushing and holding it will jump past the confirmation.

[eTobey]

Video demonstrates nothing.

Only to fanyboys. Others have an objective view.