Has anyone tried the latest firmware V6.1.37R8? I read somewhere it breaks wifi.
I've might have discovered a bug, maybe someone can duplicate. Whenever I have a USB drive plugged in (in this case, a 32GB thumb drive), my USB wifi module isn't recognized on boot, and the system locks up when I hit WiFi Set in the Utility->I/O submenu.
I have my USB Wifi module (TP-Link TL_WN725N) plugged into the USB port at the backside of my SDS1104X-E scope. In my experience the WiFi module is always detected after bootup, with or without USB drive plugged into the front USB port. But often detection of the Wifi module does not result in a reliable Wifi connection. Many times after boot up with Wifi module plugged in and detected by the the scope, I cannot access the web interface of the scope at the IP address of the Wifi module. When this happens I can repair the Wifi connection by switching Off and On WiFi and hit the Connect button in menu Utility => I/O => WiFi Set. Sometimes multiple attempts are needed to get a working WiFi connection, and the only way to find out if the WiFi connection is working is to check if the scope's web interface can be accessed on the IP address of the WiFi module. Once the WiFi connection is working the connection remains stable as long as the scope stays powered on.
To summarize, in my experience the scope most of the times does not establish a reliable WiFi connection with my WiFi router after boot up. When this happens I can make a working WiFi connection by switching Off/On WiFi and hit the Connect button in the Utility => I/O => WiFi Set menu. Many times multiple attempts are needed before a working WiFi connection is established. It could be that the occurrence of this problem depends on the WiFi Access Point (WiFi router) that is used.
There is certainly room for improvement wrt the reliability of the WiFi connection.
................
But it's not a big issue, now that I know it works with a maximized browser window. Just wanted to mention the issue in the forum, if anyone else happened to see the same.
For Windows, Ctrl + mouse scroll wheel is the quick fix to make the webserver ratio best fit monitors.
So not a big issue, only a bit space wasting and looks a bit stretched on a really big ultra wide monitor.
That's not entirely correct. By default Ctrl + mouse scroll zooming isn't enabled in Chrome, Edge and Firefox, so that doesn't work (but zooming is available in the browser option menu).
Thus, you can adjust the display to be smaller and click the upper right button to display all the buttons of the SDS1104X-E.
I have found what appears to be a bug in the Signal Logger on the SDS1104X-E. Applying a slow square wave with a 55 s period (18 mHz), I see frequency and period measured accurately by the logger at 2 samples per second (first screen shot). However, when the logger is set to 1 sample per second, the measured period is 68 s (second screen shot), a 24% error that can't be accounted for by the +/- 1 s resolution. The same error occurs with a longer period signal (e.g., 188 s is measured to be 231 s). I see no problem at 10 and 20 samples per second, or when acquiring the waveform in the scope's ordinary mode. Has anyone else observed this bug? My scope is updated to what I believe is the latest version of the firmware (6.1.37R6).
I have found what appears to be a bug in the Signal Logger on the SDS1104X-E. ...Thanks for your report.
Latest firmware version is here:
https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS1xx4X-E_V6.1.37R8_EN.zip
On its site siglent offers two versions of the V2 operating system.
Simple mistake?
On its site siglent offers two versions of the V2 operating system.
Simple mistake?
On its site siglent offers two versions of the V2 operating system.
Simple mistake?
It is cumbersome because there is no proper system for identifying distribution packages and programs and / or firmware versions.
Thanks god they don't make airplanes.
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.