Siglent SDS2000X Plus - Bugs / Missing Features / Feature Requests

[blurpy]

Empty dropdown for timezone is to be expected if you have a scope older than those shipped with firmware version 1.5.2R1 where timezone support was introduced.

Mine is also empty. The timezone data has never been included with any firmware updates. Just checked 1.6.2R5 and it's still not included. So it only works for those who have timezone data from the factory.

[tautech]

Empty dropdown for timezone is to be expected if you have a scope older than those shipped with firmware version 1.5.2R1 where timezone support was introduced.

Mine is also empty. The timezone data has never been included with any firmware updates. Just checked 1.6.2R5 and it's still not included. So it only works for those who have timezone data from the factory.

Interesting.
Can you please provide supporting screenshots ?
System Info too please.

We need take this to Siglent.

[blurpy]

We discussed this a while ago:

Version： V1.5.2R1

Although the Time Zone Setting appears on screen, I am unable to select or enter any Timezone information.

I'm having the same issue. I just see a timezone dropdown box with nothing in it and I can't select or change anything.

I see references to "/usr/share/zoneinfo/" in the firmware, which on a regular Linux system contains the timezone files.
But I can't see any timezone files shipped with the new firmware. So perhaps it's already included on new devices, but not older ones?

Update: since I haven't updated yet, I had a look around with telnet to see if I could find the files it's looking for:

Code: [Select]

/ # ls /usr/bin/siglent/usr/localtime
ls: /usr/bin/siglent/usr/localtime: No such file or directory

/ # ls /usr/share/zoneinfo/
ls: /usr/share/zoneinfo/: No such file or directory

Would be interesting to know if "/usr/share/zoneinfo/" exists on the latest generation of devices.

I can't look around the file system anymore since telnet is disabled, but none of the firmware updates following that has included any time zone files so I think that is the reason it still doesn't work.

The current time zone dropdown, with nothing in it, and the arrow button disabled:



System info:

[mon]

To be clear, the timezone weirdness I was mentioning was nothing like you're all experiencing...

For me, I'd try to set the time and timezone at once, but only one would stick (and I could never quite figure out which one did stick), then trying to set the other one would offset the time - but I'm in GMT+10, and the offset was always +6 or -8 or something nonsensical, so it took a few goes to actually set the time.

[Performa01]

I did have 1.6.2R5. I did what you said and reset to factory settings and then reloaded 1.6.2R5, but I still have an empty drop down box for the timezone. How can I fix this?

Here's what I have for versions currently:
Software: 1.6.2R5
Uboot-OS: 5.0.0
FPGA: 2024-01-29
CPLD: 03
Hardware: 02-00

For the timezone feature to work, the latest Uboot-OS 5.04 is required.

Unfortunately, Siglent forgot to make the upgrade package public together with the release of FW 1.6.2R5.

Tautech does have the upgrade in form of the latest recovery package for SDS2000X Plus, so he should be able to help.

[tautech]

I did have 1.6.2R5. I did what you said and reset to factory settings and then reloaded 1.6.2R5, but I still have an empty drop down box for the timezone. How can I fix this?

Here's what I have for versions currently:
Software: 1.6.2R5
Uboot-OS: 5.0.0
FPGA: 2024-01-29
CPLD: 03
Hardware: 02-00

For the timezone feature to work, the latest Uboot-OS 5.04 is required.

Unfortunately, Siglent forgot to make the upgrade package public together with the release of FW 1.6.2R5.

Tautech does have the upgrade in form of the latest recovery package for SDS2000X Plus, so he should be able to help.

Thanks for reporting this and will add to it requesting an updated FW ASAP.

We got steve1515 all sorted. 

[blurpy]

Awesome! I'm updated to uBoot 5.4.0 with the help of tautech, so now I've got time zones

[mawyatt]

Now if we can just get Siglent to include the NTP function like in the SDS800X HD

Best,

[BillyO]

Now if we can just get Siglent to include the NTP function like in the SDS800X HD

Best,

+1

[Performa01]

Now if we can just get Siglent to include the NTP function like in the SDS800X HD

It's on their todo list.

[hpw]

+1

To add as from reported SDS2000 plus thread:

- 500u/Div requires several times the Self calibrations to get stable values

- after boot an up to 15 second idle time as DSO looks as dead

- channels C1..C4 and mixed with FFT spectrum:

  - Nice, dependent of channel selection, text gets its related channel color.
  - But gets soon unreadable as text has no cleared background color as here black.
  - Same issue as on FFT text: text should have a cleared background color.

[hpw]

Have one more

- load as reload a saved picture.
  I cannot get ride of the loaded printed picture as stays permanently ... so no close icon or button presented

[alocam]

Hello,
I have just upgraded to 1.6.2.R5, everything seems to work fine, but remote instrument control shows a blank screen instead of the usual screen on different browsers. I have gone through the basic procedures of reinstalling same firmware, cold booting, to no avail.
I will post any news on the subject after a more thorough investigation...
If anyone has already gone through this issue, I would very much appreciate any guidance on how to solve it!

[tautech]

Try a Factory Default followed by a Secure Erase.
Then setup the scopes IP again and ensure no password has been set for webserver access.

[Performa01]

Hello,
I have just upgraded to 1.6.2.R5, everything seems to work fine, but remote instrument control shows a blank screen instead of the usual screen on different browsers. I have gone through the basic procedures of reinstalling same firmware, cold booting, to no avail.
I will post any news on the subject after a more thorough investigation...
If anyone has already gone through this issue, I would very much appreciate any guidance on how to solve it!

Fiddling with the instrument (facory default etc.) is ver unlikely to make a difference.

I have the same symptoms, but it happened from one day to the other, on different instruments, without any firmware update.

All embedded platform instruments are affected: SDS824X HD, SDS2304X Plus, SDS2504X HD, SDG7102A: web server is functional, but instrument control shows a blanc screen. Only exception is the PC-based SDS7404A H12.

So my conclusion is that this functionality has gone with one of the latest security updates in my Windows 10 Pro 22H2.

I would like to hear from others who have similar issues, so I get an idea which operating systems cause problems. Since the SDS7404A is not affected, there is clearly something missing on the embedded instruments, which hopefully can be added by Siglent. Yet I would like to collect some data before I report the issue to them.

[optotester]

I observed that a lot of company’s firewall/GPO are preventing the use of VNC, even on local network. Changing the port may help or not depending on the rules being set.

[2N3055]

On my PC with Windows 10 Pro 22H2 it works just fine. Chrome (Version 126.0.6478.182 (Official Build) (64-bit)) and Edge (Version 126.0.2592.113 (Official build) (64-bit)).
Siglent uses well known noVNC for this functionality.

I guess there is something in browser blocking page components or some kind of FW blocks traffic.

Way to troubleshoot this is to try connecting with standalone VNC viewer, and also sniffing traffic with Wireshark.

[tautech]

So my conclusion is that this functionality has gone with one of the latest security updates in my Windows 10 Pro 22H2.

I would like to hear from others who have similar issues, so I get an idea which operating systems cause problems.

Same OS and version in operation here without issue.

However, after installation of 1.6.2.R5 into SDS2354X Plus the LAN IP address was all up the creek. 
To correct:
Select Auto DHCP and close LAN Config and then reopen it, provided the correct LAN IP where Auto DHCP can be set to OFF and have the scope webserver connect without issue.

[Helix70]

I did have 1.6.2R5. I did what you said and reset to factory settings and then reloaded 1.6.2R5, but I still have an empty drop down box for the timezone. How can I fix this?

Here's what I have for versions currently:
Software: 1.6.2R5
Uboot-OS: 5.0.0
FPGA: 2024-01-29
CPLD: 03
Hardware: 02-00

For the timezone feature to work, the latest Uboot-OS 5.04 is required.

Unfortunately, Siglent forgot to make the upgrade package public together with the release of FW 1.6.2R5.

Tautech does have the upgrade in form of the latest recovery package for SDS2000X Plus, so he should be able to help.

Thanks for reporting this and will add to it requesting an updated FW ASAP.

We got steve1515 all sorted. 

How do you update the U-Boot? I am stuck at 5.0.0 after the firmware update and also have no timezones.

[alocam]

Hello again,

Thank you for your assistance. I have gone through this factory default / secure erase procedure, no changes. I can send SCPI, but no instrument remote control or viewing possible. BTW, should I upgrade U-boot in order to keep the unit fully updated? If so, how can I do that?
Any further suggestions on the remote connection issue?
Thank you!

[tautech]

I did have 1.6.2R5. I did what you said and reset to factory settings and then reloaded 1.6.2R5, but I still have an empty drop down box for the timezone. How can I fix this?

Here's what I have for versions currently:
Software: 1.6.2R5
Uboot-OS: 5.0.0
FPGA: 2024-01-29
CPLD: 03
Hardware: 02-00

For the timezone feature to work, the latest Uboot-OS 5.04 is required.

Unfortunately, Siglent forgot to make the upgrade package public together with the release of FW 1.6.2R5.

Tautech does have the upgrade in form of the latest recovery package for SDS2000X Plus, so he should be able to help.

Thanks for reporting this and will add to it requesting an updated FW ASAP.

We got steve1515 all sorted. 

How do you update the U-Boot? I am stuck at 5.0.0 after the firmware update and also have no timezones.

Hello again,

Thank you for your assistance. I have gone through this factory default / secure erase procedure, no changes. I can send SCPI, but no instrument remote control or viewing possible. BTW, should I upgrade U-boot in order to keep the unit fully updated? If so, how can I do that?
Any further suggestions on the remote connection issue?
Thank you!

Helix70 and alocam

Check your messages.

[Helix70]

Big thanks to Tautech for helping me. Much appreciated!

[alocam]

As usual, Tautech's help has proven invaluable! Thank you!

[alocam]

Just in case it helps whoever may be struggling with the NOVNC Windows 10 failure, I have two PCs with Win10 22H2, one of them connects flawlessly to SDS2000X+, the other one gives a blank screen instead of the instrument's screen, irrespective of using Edge, Firefox, Chrome or Brave.
I disabled both, firewall as well as antivirus, just in case.
I can connect with no issues using a VNC viewer (on the PC that is not working via browser), hence the scope should be OK.
Somehow latest Windows 10 update is interacting with browsers and stops NOVNC dead on its tracks when using any of them to connect.
Regards!

[don_apple]

I did have 1.6.2R5. I did what you said and reset to factory settings and then reloaded 1.6.2R5, but I still have an empty drop down box for the timezone. How can I fix this?

Here's what I have for versions currently:
Software: 1.6.2R5
Uboot-OS: 5.0.0
FPGA: 2024-01-29
CPLD: 03
Hardware: 02-00

For the timezone feature to work, the latest Uboot-OS 5.04 is required.

Unfortunately, Siglent forgot to make the upgrade package public together with the release of FW 1.6.2R5.

Tautech does have the upgrade in form of the latest recovery package for SDS2000X Plus, so he should be able to help.

Thanks for reporting this and will add to it requesting an updated FW ASAP.

We got steve1515 all sorted. 

Hello, I just registered here to report that I'm having the same issue with the timezone feature not working even after updating to FW 1.6.2R5.

Until an updated firmware with a fix for this is available, is there another way to fix this?