Siglent SDS2000X HD, missing Features and Bugs

[danils]

Thanks for feedback,

I'll open a ticket with Siglent.

Dan

[Martin72]

Yepp, it seems to be a failure, me I I didn´t nothing different than you in your video.

[tautech]

Hi all,

I experimented again with the clock setting and I still experience what, afaik, looks like "clock getting confused" bug.
As you can see at the beginning of the video, firmware version is the last (1.2.1.1)

It displays 00:11, I set it to 22:11 and cycling power, time is back to 00:11

Do I miss something performing clock setting? The procedure I perform is the same showed in the user manual,

Please refer to the video below
https://youtu.be/2gQLOtG5NPU

FWIW try installing the latest firmware again as how you changed the time is correct but it's not remembering it. 
Also try powering OFF with the power button to check if it remembers the time instead of OFF with the UI SW.

[2N3055]

Hi all,

I experimented again with the clock setting and I still experience what, afaik, looks like "clock getting confused" bug.
As you can see at the beginning of the video, firmware version is the last (1.2.1.1)

It displays 00:11, I set it to 22:11 and cycling power, time is back to 00:11

Do I miss something performing clock setting? The procedure I perform is the same showed in the user manual,

Please refer to the video below
https://youtu.be/2gQLOtG5NPU

FWIW try installing the latest firmware again as how you changed the time is correct but it's not remembering it. 
Also try powering OFF with the power button to check if it remembers the time instead of OFF with the UI SW.

I don't know if this was mentioned, but it is recommended to reset scope to factory defaults after FW update...

[tautech]

Hi all,

I experimented again with the clock setting and I still experience what, afaik, looks like "clock getting confused" bug.
As you can see at the beginning of the video, firmware version is the last (1.2.1.1)

It displays 00:11, I set it to 22:11 and cycling power, time is back to 00:11

Do I miss something performing clock setting? The procedure I perform is the same showed in the user manual,

Please refer to the video below
https://youtu.be/2gQLOtG5NPU

FWIW try installing the latest firmware again as how you changed the time is correct but it's not remembering it. 
Also try powering OFF with the power button to check if it remembers the time instead of OFF with the UI SW.

I don't know if this was mentioned, but it is recommended to reset scope to factory defaults after FW update...

Where ?
Actually I'm pursuing a thought danils clock issue could be shutdown method related. 
We need feedback to eliminate that it might be.

[2N3055]

Hi all,

I experimented again with the clock setting and I still experience what, afaik, looks like "clock getting confused" bug.
As you can see at the beginning of the video, firmware version is the last (1.2.1.1)

It displays 00:11, I set it to 22:11 and cycling power, time is back to 00:11

Do I miss something performing clock setting? The procedure I perform is the same showed in the user manual,

Please refer to the video below
https://youtu.be/2gQLOtG5NPU

FWIW try installing the latest firmware again as how you changed the time is correct but it's not remembering it. 
Also try powering OFF with the power button to check if it remembers the time instead of OFF with the UI SW.

I don't know if this was mentioned, but it is recommended to reset scope to factory defaults after FW update...

Where ?
Actually I'm pursuing a thought danils clock issue could be shutdown method related. 
We need feedback to eliminate that it might be.

Well let's say I recommend it then... :-)
Sometimes new firmware does changes in internal data structures, and it makes sure all variables are properly initialized...

I do think that your suggestion is a good one, don't get me wrong.... I just wanted to add another possible thing to try...

[Martin72]

Reset to factory defaults could be a good idea to prevent seeing ghost things...

[tautech]

Reset to factory defaults could be a good idea to prevent seeing ghost things...

Nah, ghost stuff appears at boot before you get the chance to run a Default.

[danils]

Hi,

Following your advice:

1) I reinstalled the the last firmware
2) I reset the scope to default
3) I switched it off via the button instead of UI SW

Unfortunately the bug is still there.

Two hours ahead the time I set, but it is not incremental, so it is:

12:00 -> 14:00 -> 14:00 -> 14:00 etc.

and not

12:00 -> 14:00 ->16:00 ->18:00 etc.

[luudee]

Hi,

Following your advice:

1) I reinstalled the the last firmware
2) I reset the scope to default
3) I switched it off via the button instead of UI SW

Unfortunately the bug is still there.

Two hours ahead the time I set, but it is not incremental, so it is:

12:00 -> 14:00 -> 14:00 -> 14:00 etc.

and not

12:00 -> 14:00 ->16:00 ->18:00 etc.

From this discussion, it sounds like the back-up power source (battery or super cap) for the RTC has failed.

I do not know how they are built, if the battery is in a socket, it might have gotten loose, or just expired ...

Should be an easy check if you want to open the baby up ...


luudee

[2N3055]

Hi,

Following your advice:

1) I reinstalled the the last firmware
2) I reset the scope to default
3) I switched it off via the button instead of UI SW

Unfortunately the bug is still there.

Two hours ahead the time I set, but it is not incremental, so it is:

12:00 -> 14:00 -> 14:00 -> 14:00 etc.

and not

12:00 -> 14:00 ->16:00 ->18:00 etc.

From this discussion, it sounds like the back-up power source (battery or super cap) for the RTC has failed.

I do not know how they are built, if the battery is in a socket, it might have gotten loose, or just expired ...

Should be an easy check if you want to open the baby up ...


luudee

No it is not RTC battery...
It doesn't forget time and date.
It is some kind of time zone recalculation problem.

[PartialDischarge]

Not a bug, but it would be interesting to be able to reduce the significant digits in the measurements to 2 or 1 digits. 4 is too much imo

[2N3055]

Not a bug, but it would be interesting to be able to reduce the significant digits in the measurements to 2 or 1 digits. 4 is too much imo

Which ones exactly do you mean?

[PartialDischarge]

These ones, seeing 4 digits after the comma makes it harder to read the number

[danils]

A mini bug,

Two different mouse pointers before and after the screensaver activated

[Martin72]

LOL, didn´t recognize it so far...

[tautech]

Hi,

Following your advice:

1) I reinstalled the the last firmware
2) I reset the scope to default
3) I switched it off via the button instead of UI SW

Unfortunately the bug is still there.

Factory Tech support can reproduce it.
It caused by the time zone set to Europe/Rome.
Sent to R&D to fix.

Suggested workaround is instead set time zone to UTC.

[tv84]

Factory Tech support can reproduce it.
It caused by the time zone set to Europe/Rome.
Sent to R&D to fix.

Suggested workaround is instead set time zone to UTC.

Better: Europe/Berlin   

[Martin72]

Better: Europe/Berlin   

Gentlemen, we have a bug....

As mentioned the last posts here, my adjusted time never gets "lost", even when it´s completely powered off for days.
Now:
Seeing tv84 post and thought, good idea.
My timezone was UTC, so I´ve switched it to European/Berlin and bingo...
After re-start, the adjusted time is lost, instead of e.g. 22h35 it shows 0h35, Date stays correct.
Switching back to UTC, adjusting the time to 22h35, restart....It stays, no lost.
Thx to danils for finding this. 

Feature wanted :
Today we did a kind of "technology transfer":
A project where we use a old lecroy 9310, we want to use the siglent in the future for it.
So we test it if this was a problem concerning math and several measure displying - Not it wasn´t, good.
But:
We got both scopes on, on the lecroy when you change the vertical scale, the zeroline always stays where it is while on the siglent the line is gone and you have to readjust to have it in the middle.
Example : 5V/div., decreasing to 2V/div., old lecroy let the trace where it is, a marker appear and shows in which direction the 0V are (above or under).
Very nice, want to have it on the siglent also...

Wanted polish:

FFT....
Splitscreen mode is a nice and useful thing, but it has an annoying effect:
To get the full amplitudes visible the minimum scaling is 20dB/div. which is sometimes too much, when switching to 10dB/div., it goes "out of the screen".
A kind of compressed displaying would be good like the lecroy did when it is in split mode /dual grid.

[tautech]

Feature wanted :
Today we did a kind of "technology transfer":
A project where we use a old lecroy 9310, we want to use the siglent in the future for it.
So we test it if this was a problem concerning math and several measure displying - Not it wasn´t, good.
But:
We got both scopes on, on the lecroy when you change the vertical scale, the zeroline always stays where it is while on the siglent the line is gone and you have to readjust to have it in the middle.
Example : 5V/div., decreasing to 2V/div., old lecroy let the trace where it is, a marker appear and shows in which direction the 0V are (above or under).
Very nice, want to have it on the siglent also...

Floating not Fixed Vertical Reference level setting ?

[Martin72]

Hmmm....RTFM again, Rob ? 
Will have a look.

[tautech]

Hmmm....RTFM again, Rob ? 
Will have a look.

Maybe you just haven't used the Reference Position feature on the Siglent DSO's you've had. 

It offers fixed reference positions for both horizontal and vertical adjustments so when your waveform has reference positions that are not default (0s, 0V) the positions or waveform remain on the display regardless of adjustments made.
Really handy for the Horizontal position in particular when you need the 0s position off near the left edge of the display to accommodate full packets of data for example.
For the Vertical reference it allows for a vertical zoom onto the top of a waveform but drives the 0V reference position off the bottom of the display.

Utility>System>Reference Pos is where you set all this to best suit your job or just preferences.
Do remember that both H and V reference positions (0s, 0V) are always displayed in the timebase and channel tabs.
Screenshot for study with the Reference Pos menu open.

[jord4231]

Yep I got bugs with the time aswell
Set to Australia/Sydney.
More annoying than that it keeps dropping my static IP I set.
Keeps defaulting to 0.0.0.0

[jord4231]

Actually scrap that, something else hopped on the network taking its assigned ip 

[Frankupthehall]

Hey Folks,

I got a demo unit the other day from my local Siglent guy, I played around with it over the day. It's a fun and cute (compared to the SDS6000) little unit , no major issues until I turned the unit off.

I noticed an audible hum from, what I presume, is the power supply; probably some low power instability. I had to actually unplug the unit for it to go away (which first makes the hum climb in frequency; sounds funny).

Curious if anybody else has noticed this or if it may just be a bad power supply?