SDS800X HD Bug Reports + Firmware

[Martin72]

Do as I do and you'll have peace and quiet.

[bd139]

As for the rest, can we quit the bitching and hyperbole and be specific and deterministic on this. No one is going to listen to you if you suffix everything with generic complaining.

I would suggest to stop answering; this person is not going to listen.
I suggested to keep discussions/complains in different/dedicated thread and bugs and feature requests in dedicated threads; the result is more noise on those threads as well.
Also other threads were started ... I guess the objective is just trolling.
I do not see other action we can take other that simply ignore.

I prefer the approach of pissing people off until they leave

[KungFuJosh]

I prefer the approach of pissing people off until they leave

Isn't that his mantra? 😉

 

[bd139]

I prefer the approach of pissing people off until they leave

Isn't that his mantra? 😉

 

I thought it was just complaining. I mean looking at the YT channel he bought a Rigol and moaned about that. Then bought a Siglent and moaned about that. I am playing "guess the next scope brand" at the moment. I am also picturing him crouched in front of a Tek 7904 trolley complaining about the grid not moving and the shitty user interface and it is cheering me up.

Edit: I'm on the software side of things these days but I have many customer conversations that are the same. There's 25,000 people without a complaint but 1 person with all the complaints, none of which are concrete or well described.

[KungFuJosh]

Fair enough. Two different paths to the same destination. 😉

[eTobey]

That looks quite ugly:
There where there is no space, there are useless digits (2 digits always beeing 0), and then where there is space (on the gate values) there is only one digit after the comma.

This has already beeing known quite some time ago i believe. (those useless digits)

[tautech]

That looks quite ugly:
There where there is no space, there are useless digits (2 digits always beeing 0), and then where there is space (on the gate values) there is only one digit after the comma.

This has already beeing known quite some time ago i believe. (those useless digits)

When you need them....you NEED them !

Our customer requires 10 digit accuracy and HQ are working on how to provide it.....in a different model.

Your view of how this scope should operate is just yours and certainly not universal !

[bd139]

That looks quite ugly:
There where there is no space, there are useless digits (2 digits always beeing 0), and then where there is space (on the gate values) there is only one digit after the comma.

This has already beeing known quite some time ago i believe. (those useless digits)

Are you sure they useless? The input parameter is to 1 d.p but the measurement or marker may be better precision with different rounding rules?

Does an HP 34401A display 1.5 when you are measuring 1.500000 volts or 1.500000?

An assumption either way if course but a demonstration that your perspective may not be the right one.

[eTobey]

That looks quite ugly:
There where there is no space, there are useless digits (2 digits always beeing 0), and then where there is space (on the gate values) there is only one digit after the comma.

This has already beeing known quite some time ago i believe. (those useless digits)

When you need them....you NEED them !

Our customer requires 10 digit accuracy and HQ are working on how to provide it.....in a different model.

You can say whatever you want, it still looks bloody ugly!

[KungFuJosh]

You can say whatever you want, it still looks bloody ugly!

Rather than whining like a toddler, or saying my way or the highway, you could put in a feature request to have an option to limit the digits on the axis markers. That way you can have what you want, and so can the adults.

[Martin72]

You can also turn off the axis labeling, which also solves the “problem”.

[2N3055]

Biggest problem is that he keeps repeating it, dozens of times.
And keeps opening topics on same things all time...
After being told dozens of times that it was reported already, by other people before him, and that Siglent is informed about, and working on it to optimize where in CAN be optimized.
And after 2 days there he goes again. And endless whining how "king is not happy!!" and whole world should not sleep until anything he does not like should be fixed immediately. And all of it is easy and he could fix all the problems in 10 minutes. And everybody else is stupid.

Like a spoiled 3 year old, demanding attention all the time.....
Endless drama, theatrics, narcissism, egocentricity etc...

Without really understanding how scope works, how it is used.. Shown numerous time....

[Furna]

Not only ... I would like this thread to be used for 2 reasons only:
- when a bug is found, reproducible and documented
- when a new firmware is released
This would allow me to subscribe to the thread and use it as an "alarm" that time to upgrade firmware arrived.
There are other threads for open discussions, opinions ...
Indeed it seems this person just start typing randomly in different threads or even opening a new one.
Frankly speaking a veri annoying behaviour.

[bd139]

That looks quite ugly:
There where there is no space, there are useless digits (2 digits always beeing 0), and then where there is space (on the gate values) there is only one digit after the comma.

This has already beeing known quite some time ago i believe. (those useless digits)

When you need them....you NEED them !

Our customer requires 10 digit accuracy and HQ are working on how to provide it.....in a different model.

You can say whatever you want, it still looks bloody ugly!

Correct > nice.

[eTobey]

I cant remember if this has been already posted. I may have forgotten this, as there was a lot of noise... The bug list is not updated anymore, as the user hasnt been seen since 3 months...

History time wrong
Steps to reproduce:
- Factory reset
- activate the option to show time on the bottom right
- acquire some frames (i used channel 4)
- open the list view in history menu
- obsere the time in the list, and compare with the time in the bottom right

Expected time in the list: 16:53:xx
Observed time in the list: 01:17:xx

Seems, that time "time since device start" has snug into the history module. 

Interestingly, a factory reset did not reset all date settings, just the option to show the date.

Edit:
A reboot after the factory reset, did reset some more settings in the date menu, but not all.

[2N3055]

I cant remember if this has been already posted. I may have forgotten this, as there was a lot of noise... The bug list is not updated anymore, as the user hasnt been seen since 3 months...

History time wrong
Steps to reproduce:
- Factory reset
- activate the option to show time on the bottom right
- acquire some frames (i used channel 4)
- open the list view in history menu
- obsere the time in the list, and compare with the time in the bottom right

Expected time in the list: 16:53:xx
Observed time in the list: 01:17:xx

Seems, that time "time since device start" has snug into the history module. 

Interestingly, a factory reset did not reset all date settings, just the option to show the date.

There were not bugs reported in meantime... Maybe one or two small ones that were already known from internal testing and are being addressed.

But for this one, I can confirm there is a bug here. It would be nice if you could add FW version next time, for completeness, for other people that can read this later to be able to know what FW it applies to.
But this time you provided decent enough data for others to test. 

I tested on 1.1.38 FW and reproduced it.
There is no need for any additional steps, after boot with network connected, NTP will set time but History will not get it.

If you go into NTP settings and manually force NTP sync then it works fine. That can be used as a workaround at this time.

Will report.

[watchmaker]

This concerns the manual.

Can we please have the section title added to the header of the pages?  For example, "TRIGGER" at the top of the page for each page in section 15.  For me this makes PDFs much more useable.  (I get lost easily).

[ttelectronic]

This concerns the manual.

Can we please have the section title added to the header of the pages?  For example, "TRIGGER" at the top of the page for each page in section 15.  For me this makes PDFs much more useable.  (I get lost easily).

Not going to guarantee this is a perfect conversion. This is what I managed to do. =)

[watchmaker]

This concerns the manual.

Can we please have the section title added to the header of the pages?  For example, "TRIGGER" at the top of the page for each page in section 15.  For me this makes PDFs much more useable.  (I get lost easily).

Not going to guarantee this is a perfect conversion. This is what I managed to do. =)

Works for Me!!  Thanks!

[ttelectronic]

No problem, my apologies, a number snuck away on me resulting in the TOC being off by 1. I have fixed it in this file. It's the little things that get ya. =/ Fixed file attached.

[eTobey]

Issue:
Using SCPI commands creates false traces in history playback.

- Capture  frames and let continues playback of history run.
- Execute the following script: printinfos.py from https://gitlab.com/Tobey16/siglent-virtual-feature/-/tree/fed40c6703ba4b2ed608fb817cd940966a231c27

[electr_peter]

Potential display bug: after changing time base in RUN mode, displayed waveform intensity becomes much brighter briefly (0.5-1s duration), then turns back to previous intensity. This happens both when increasing and decreasing timebase. Tested with single channel 4 ON, in Normal & Peak Detect modes. Input signal - 1Vpp noise at 200mV/div, base intensity at 50%.

SW version 1.1.3.8/OS 3.8.12/FPGA 2024-04-11/HW version 00

EDIT: similar intensity changes can be seen with more regular signals like square and sine waves. In this case only the very top/bottom (i.e. most "dense") areas change intensity when changing timebase (thus not that visible). Most obvious with random noise signal.
Not sure why intensity is changing under these conditions as there are enough triggers and update rate - maybe intensity settings are recalculated with a lag.

[nanopico]

SW version 1.1.3.8/OS 3.8.12/FPGA 2024-04-11/HW version 00

Can someone explain why there are two versions for Uboot-OS Version: 2.8.12 vs. 3.8.12?

[eTobey]

... displayed waveform intensity becomes much brighter briefly (0.5-1s duration), then turns back to previous intensity. ...

So this then goes away?  I have posted much more severe bugs and was scolded...

[eTobey]

Bug(s):
Mask test
i dont know where to start: the mask test failed to detect a fail condition (see picture).
It is already annoying to have to do quite a few clicks, to have a mask loaded, that just has been created, yet, it does not work reliable. And when the mask is loaded, scale and position of the selected channel changes. 

It fails on the first 3 pass conditions. And it does give false fail triggers!

Edit:
Now it fails reliable (see pic 2) 


Edit 2:
I suspect something has happend (or something i did), so that the scope did not really function anymore as it should. A restart solved the issue. (I did not use any scripts of mine, that could have interfered!)

Edit 3: Issue appeared again... Oh what fun it is to use it right now... 

Oh nice, the time is wrong again too.... great

Edit4:
The mask test now does not work at all anymore, even after (soft) restart.
See setup 9