Siglent SDS1104X-E and SDS1204X-E Mixed Signal Oscilloscopes

[tautech]

It's unreliable for me. Sometimes it works OK and the web interface is fairly usable. Sometimes it just won't connect or it connects but there is no useful data throughput.

One thing that may be an issue for me is that I have 3 wireless AP's in the house all broadcasting the same SSID's as our internal walls are far too thick to cover the house with one AP. This allows devices to roam between AP's automatically as they move around the house.

Even though one of the AP's is in the same room (about a metre away) from the scope, there's a possibility that the roaming support on the device is poor and it's sometimes connecting to a far away AP and thus not getting a usable signal. I'll need to do some more testing to see if this is the case.

Are you using DHCP or a static IP?
On my original firmware (ca 2020), I found that WiFi was unstable and constantly connected/disconnected when using DHCP but was rock stable when using static IP.
I posted this as a bug report back then and also to the Forum https://www.eevblog.com/forum/testgear/siglent-wifi-totally-flakey-with-dhcp-on-(but-rock-solid-with-dhcp-off)/msg3216354/#msg3216354

Some recent discussion:
https://www.eevblog.com/forum/testgear/sds1104x-e-wifi-needs-router-ssid-broadcast-all-the-time/

With the latest firmware behavior is consistent. (V6.1.37R8 and V2 OS)

[puterboy]

It's unreliable for me. Sometimes it works OK and the web interface is fairly usable. Sometimes it just won't connect or it connects but there is no useful data throughput.

One thing that may be an issue for me is that I have 3 wireless AP's in the house all broadcasting the same SSID's as our internal walls are far too thick to cover the house with one AP. This allows devices to roam between AP's automatically as they move around the house.

Even though one of the AP's is in the same room (about a metre away) from the scope, there's a possibility that the roaming support on the device is poor and it's sometimes connecting to a far away AP and thus not getting a usable signal. I'll need to do some more testing to see if this is the case.

Are you using DHCP or a static IP?
On my original firmware (ca 2020), I found that WiFi was unstable and constantly connected/disconnected when using DHCP but was rock stable when using static IP.
I posted this as a bug report back then and also to the Forum https://www.eevblog.com/forum/testgear/siglent-wifi-totally-flakey-with-dhcp-on-(but-rock-solid-with-dhcp-off)/msg3216354/#msg3216354

Some recent discussion:
https://www.eevblog.com/forum/testgear/sds1104x-e-wifi-needs-router-ssid-broadcast-all-the-time/

With the latest firmware behavior is consistent. (V6.1.37R8 and V2 OS)

The thread you cite seems to be mostly about SSID and DHCP lease issues.
The problem that I documented in the thread I cited (along with bug report to Siglent) is that a combination of certain routers & network topologies lead to unstable DHCP connections with the connection dropping and restarting every few seconds. This has nothing to do with SSID or DHCP leases.

I was able to solve the problem by using static DHCP.

I don't think it's a problem with my routers (Netgear r6700 running dd-wrt) as my network is otherwise rock stable and dd-wrt is pretty darn solid.
Also, the WiFi dongle works fine under Windows or Linux.
So presumably there was/is a problem with the Siglent firmware -- or at least the version I had from 2020 as I have not yet updated
When I update, I will check if problem still persists...

[Hfe72]

Hey guys! My sds1104x-e (hacked up to 200MHz) software version is 6.1.33 and Uboot-OS version is 8.1. Do I have to install every single update in incremental order or can I jump straight to the latest one without installing any updates in between them? The latest firmware is V6.1.37R8 and OS is Operating System -V2? And which one should be installed first, or does this matter?

[pope]

Hey guys! My sds1104x-e (hacked up to 200MHz) software version is 6.1.33 and Uboot-OS version is 8.1. Do I have to install every single update in incremental order or can I jump straight to the latest one without installing any updates in between them? The latest firmware is V6.1.37R8 and OS is Operating System -V2? And which one should be installed first, or does this matter?

I only got my scope a couple of weeks ago so I'm definitely not an expert but I went from 6.1.35R2 straight to V6.1.37R8 without problems. Maybe someone can be of more help though.

As far as the OS, I've been having problems to install OS2  but yesterday I read that the USB stick should be either 8gb or 32gb. Unfortunately I only have 2,4 and 16gb sticks so I don't know if this is the actual problem I'm having. 

[tautech]

Hey guys! My sds1104x-e (hacked up to 200MHz) software version is 6.1.33 and Uboot-OS version is 8.1. Do I have to install every single update in incremental order or can I jump straight to the latest one without installing any updates in between them? The latest firmware is V6.1.37R8 and OS is Operating System -V2? And which one should be installed first, or does this matter?

I only got my scope a couple of weeks ago so I'm definitely not an expert but I went from 6.1.35R2 straight to V6.1.37R8 without problems. Maybe someone can be of more help though.

As far as the OS, I've been having problems to install OS2  but yesterday I read that the USB stick should be either 8gb or 32gb. Unfortunately I only have 2,4 and 16gb sticks so I don't know if this is the actual problem I'm having.

The 2 and 4GB sticks should work just fine.

[pope]

Hey guys! My sds1104x-e (hacked up to 200MHz) software version is 6.1.33 and Uboot-OS version is 8.1. Do I have to install every single update in incremental order or can I jump straight to the latest one without installing any updates in between them? The latest firmware is V6.1.37R8 and OS is Operating System -V2? And which one should be installed first, or does this matter?

I only got my scope a couple of weeks ago so I'm definitely not an expert but I went from 6.1.35R2 straight to V6.1.37R8 without problems. Maybe someone can be of more help though.

As far as the OS, I've been having problems to install OS2  but yesterday I read that the USB stick should be either 8gb or 32gb. Unfortunately I only have 2,4 and 16gb sticks so I don't know if this is the actual problem I'm having.

The 2 and 4GB sticks should work just fine.

Thank you tautech. It was in the manual where it says for the 8/32gb so I gave up trying until I get the proper stick but since you say it should work, I'll give it another try.

[bdunham7]

Thank you tautech. It was in the manual where it says for the 8/32gb so I gave up trying until I get the proper stick but since you say it should work, I'll give it another try.

I've heard of difficulty with certain USB drives, but I have two different 16GB versions that work fine with both of my Siglent scopes.  Just make sure they are formatted FAT32.

[pope]

Thank you tautech. It was in the manual where it says for the 8/32gb so I gave up trying until I get the proper stick but since you say it should work, I'll give it another try.

I've heard of difficulty with certain USB drives, but I have two different 16GB versions that work find with both of my Siglent scopes.  Just make sure they are formatted FAT32.

I'm trying with a different USB stick as we speak. It's 4gb. The instructions say that after updating the scope should restart by itself and if not to do it manually after 10 minutes.

5 more minutes to go...

Also, the stick has a LED, which was blinking during the start-up but now it's been constantly ON.

EDIT: OK success! I had to manually restart the scopw but it appears to have the OS 8.2 version now 

[tautech]

Thank you tautech. It was in the manual where it says for the 8/32gb so I gave up trying until I get the proper stick but since you say it should work, I'll give it another try.

I've heard of difficulty with certain USB drives, but I have two different 16GB versions that work find with both of my Siglent scopes.  Just make sure they are formatted FAT32.

I'm trying with a different USB stick as we speak. It's 4gb. The instructions say that after updating the scope should restart by itself and if not to do it manually after 10 minutes.

5 more minutes to go...

Also, the stick has a LED, which was blinking during the start-up but now it's been constantly ON.

EDIT: OK success! I had to manually restart the scope but it appears to have the OS 8.2 version now 

Nice, enjoy OS 8.2. 

Yep correct observation, LED activity at boot indicates the new OS was being loaded.

[Hfe72]

Thank you tautech. It was in the manual where it says for the 8/32gb so I gave up trying until I get the proper stick but since you say it should work, I'll give it another try.

I've heard of difficulty with certain USB drives, but I have two different 16GB versions that work find with both of my Siglent scopes.  Just make sure they are formatted FAT32.

I'm trying with a different USB stick as we speak. It's 4gb. The instructions say that after updating the scope should restart by itself and if not to do it manually after 10 minutes.

5 more minutes to go...

Also, the stick has a LED, which was blinking during the start-up but now it's been constantly ON.

EDIT: OK success! I had to manually restart the scopw but it appears to have the OS 8.2 version now 

I thought that my scope did not autodetect the stick on startup, but when I manually restart the scope OS is now 8.2 

[tautech]

Thank you tautech. It was in the manual where it says for the 8/32gb so I gave up trying until I get the proper stick but since you say it should work, I'll give it another try.

I've heard of difficulty with certain USB drives, but I have two different 16GB versions that work find with both of my Siglent scopes.  Just make sure they are formatted FAT32.

I'm trying with a different USB stick as we speak. It's 4gb. The instructions say that after updating the scope should restart by itself and if not to do it manually after 10 minutes.

5 more minutes to go...

Also, the stick has a LED, which was blinking during the start-up but now it's been constantly ON.

EDIT: OK success! I had to manually restart the scopw but it appears to have the OS 8.2 version now 

I thought that my scope did not autodetect the stick on startup, but when I manually restart the scope OS is now 8.2 

During boot the scope's OS automatically looks for OS files in the root of a USB stick and if present autoloads them.

This is also how the recovery files work. With a USB stick with a activity LED you can monitor all this happening in realtime. 

OS and recovery files need be removed from your USB sticks otherwise they are uploaded again at each boot.

[rauldm]

Why autosetup doesn't adjust 4 channels like agilent or tek?, four signals in this scope it has same vertical position.

[tautech]

Why autosetup doesn't adjust 4 channels like agilent or tek?, four signals in this scope it has same vertical position.

0V is the default position for all channels however with setting your personal User default you can have all manner of scope settings just as you like them.
You can find it in the Save/Recall menu however it's wise to run a factory default before configuring and saving a User default.

[rauldm]

Yes, I do it, but I would hope siglent can set the autosetup with vertical offset and vertical scale like othera brands really is easy to see when you touch autosetup and get all signals with vertical scale and vertical offset without touch between them, I dont use to much autoset, but helps for more fast and easy adjust

[MathWizard]

Anyone else have a problem when choosing the trigger channel source ? Today I was changing trigger channel, in the trigger menu along the bottom of the screen, it says in a little box, CH1, and that on screen text stopped changing. The trigger itself still seems to change and work, but that text does not.

On the upper right, the trigger info up there updates and changes. See in the picture, I chose CH2 in the menu, and it did it, but the little status box in the bottom still says CH1.

I rebooted, but never unpluged the standby pwr, and when I turned it back on, I seem to have the same problem.

I don't remember having this problem before, I might have pressed the button really fast earlier

[tautech]

Anyone else have a problem when choosing the trigger channel source ? Today I was changing trigger channel, in the trigger menu along the bottom of the screen, it says in a little box, CH1, and that on screen text stopped changing. The trigger itself still seems to change and work, but that text does not.

On the upper right, the trigger info up there updates and changes. See in the picture, I chose CH2 in the menu, and it did it, but the little status box in the bottom still says CH1.

I rebooted, but never unpluged the standby pwr, and when I turned it back on, I seem to have the same problem.

I don't remember having this problem before, I might have pressed the button really fast earlier (Attachment Link)

A few things a missing from this report.....
The screenshot is from the webserver UI and you haven't said if the Trigger setting changes were made from within the webserver or from the scopes front panel. (possible webserver bug ?)
What is the installed FW version ?

[MathWizard]

Hi it's software version 6.1.35R2, a 1104 hacked to a 1204.

I set the trigger on the machine, by pressing setup, then the source button. I unplugged for a while, and just restarted, and the trigger soucre box in the setup menu, read correct, but then again when I changed it, it scrolls through in the little pop-up menu, but it still never changed it in the box.

Ok but if I leave the trigger menu, by say going to CH1 menu, then go back to trigger, it then says the correct CH# in that box.

No big deal, but I don't remember it being like this before.

[tautech]

Hi it's software version 6.1.35R2.............

2 year old FW, 3 versions outta date. 

See if the latest fixes this but don't forget to install the new OS too so to get the full range of new features.
https://int.siglent.com/download/firmwares/?ProId=12

[MathWizard]

OK thanks, but that won't undo the BW hack right ? and I DL stuff for 1204x-e?

[tautech]

OK thanks, but that won't undo the BW hack right ?

No.
BW upgrades are just like options, they remain after FW upgrades.

[matli]

Are there any solutions for using the 1104X-E embedded web server on ultra wide monitors? Problems were mentioned previously in this thread, but I couldn't see any real solutions.
For me, the issue means that the embedded web controls are more or less unusable. I have a 3440x1600 ultrawide monitor.

The initial view looks OK, I can see a representation of the scope's screen. However, when I push the little arrow in the upper right corner to access the controls, I get a super zoomed-in view of just a part of the scope. Even if I maximize the window, I still just can see a small portion of the interface. If I try to resize the browser window, it all snaps back to just showing me the initial view.

The only workaround I have been able to find is to zoom out the browser to 25% or so before switching on the controls, but then everything else is tiny and totally unreadable. And if I try to resize the window or so, then it all snaps back to a tiny miniature window.

[Roman oh]

I also thought that the scope had failed to detect the USB stick, because it just seemed to start normally. In hindsight, I think the welcome screen did flash briefly after about 2 seconds, but then the CRO started up normally. No indication whatsoever that anything had happened. Repeat several times with several different sticks. Same result.  In frustration, I went ahead and updated the firmware anyway (OS upgrade is not needed for 6.1.37R8), and only then checked the System Status. OS is 8.2. Firmware is 6.1.37R8.
Looks like the OS install guide may be misleading. No power cycle, no 10 minute wait - wham! Bam! Thank you m’am, in the space of a few seconds. But the installation process itself - silky smooth! Shame they couldn’t save the WiFi credentials😁

Roman

[tautech]

Shame they couldn’t save the WiFi credentials😁

WiFi is working just fine now since most special characters were supported.

What issues are you having ?

[Roman oh]

No issues - WiFi is indeed working fine. Rock solid with static IP. My tongue-in-cheek comment alluded to the fact that my WiFi password is rather long and the input mechanism gets a bit tiresome. That’s me, not the CRO, or the many other devices in my house that use a similar HMI.

[tautech]

No issues - WiFi is indeed working fine. Rock solid with static IP. My tongue-in-cheek comment alluded to the fact that my WiFi password is rather long and the input mechanism gets a bit tiresome. That’s me, not the CRO, or the many other devices in my house that use a similar HMI.

Connected to a wired LAN using the scopes webserver, a PC mouse and virtual keyboard makes such tasks a doddle.