I updated the OS and the firmware and I'm not sure if the OS update worked correctly. I inserted a USB flash with all the files in the root directory and restarted the oscilloscope, but it looked like nothing happened during the restart.
I attached the versions after the updates. Do these version indicate a successful update?
No.
See blurpy's reply:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg3648412/#msg3648412
I tried to downgrade the OS version to the previous one and it showed 7.1. Then I installed the new OS again and it shows 7.2 again.
Ah OK then it might be fine.
Will check my now years old beta SDS1104X-E SN#14 for its OS version...... it's one of the earliest HW versions.
Providing you now have a P3 for the probe menu, a Time/Date and logging and Counter in Utility the full update was successful.
I see the new options and Wi-Fi stopped working. Just version 7.2 instead of 8.2 looks strange.
I see the new options and Wi-Fi stopped working. Just version 7.2 instead of 8.2 looks strange.
Yes 37R2 breaks WiFi however a public fix is to be released soon and with the 37R3 we got last evening WiFi is working again.
It seems older HW models report 7.2 with the latest OS update yet newer production units ex our stock update to 8.2.
This ^ has just been checked.
My old unit reports OS = 7.2 yet all the new features work just fine.
Time ago I have told where is OS version.
It is second number
In old time it was displayed just before FW number
Today it is named as Uboot-OS version:
And there is two number where last one is OS version.
As in image attached.
Where is Uboot version. Where is OS version.
Is there any way to save the data from an FFT?
It would be useful to me to be able to save the FFT after it is smoothed by many averages. I would like to be able to compare the FFT plots from various configurations of my circuit.
I can save the plots, and assuming I did not touch any for the positioning and/or scaling controls I can compare those, however it would be nice to actually have the frequency/magnitude data in a CSV file.
Chris
I just got an e-mail advertisement or newsletter from Siglent and one of the 'articles' is a blurb about all the features in the new 37R2 firmware. Are they not aware that it is broken? They're actively encouraging people to download defective firmware without mentioning that it kills your WiFi.
I just got an e-mail advertisement or newsletter from Siglent and one of the 'articles' is a blurb about all the features in the new 37R2 firmware. Are they not aware that it is broken? They're actively encouraging people to download defective firmware without mentioning that it kills your WiFi.
Yeah dumb.
Within 10 days of 37R2 release I had a 37R3 beta that fixes WiFi
but the new NTP feature and WiFi boot staging needs a fix too for it to boot and sync NTP properly as it does for LAN.
Just 12 hrs before your post I sent Siglent an email to check how they were getting on with adding a boot timeout to the NTP code in the hope they would have a 37R* to share with you all but not heard back yet.
I'll keep pushing.........
37R5 beta FW in my inbox to test over the weekend.
For what it's worth, I had the same problem trying to update the OS on my SDS1204X-E. The ADS update went fine, but the unit would not boot from an 'empty' flash drive. I have several 4 GB drives and I just purchased a brand new 32 GB drive. None of them worked as a boot drive, even after I deleted everything and EACH drive reported itself as a FAT32 partition to Windows. After some sleuthing it appears that, unless you specifically format the USB drive as a FAT32 partition prior to copying the OS files over, that it is possible that new drives contain "special" software in the boot sector used for security and other Mfg-specific things that interferes with the boot process on the scope.
After I reformatted one of my 4 GB flash drives as FAT32 and copied the files over, the OS update finished perfectly in about 20 seconds. I really don't know what was different because nothing changed in the file explorer window in Windows. I'm using Windows 10, BTW.
Hope that helps!
I think it has nothing to do with the flash drive as being bootable or not, just being formatted at FAT32 does the trick.
37R5 beta FW in my inbox to test over the weekend.
Had a few issues with it still not always WiFi boot syncing the NTP clock especially if you booted time and time again however if left for a few minutes between boots it seemed to sync properly and all seems well.
Why it initially played up IDK.
Just one little thing that's sort of associated that needs polishing and it should be ready for release but when that might be IDK.
Will do my best to have them push it through.
Hey,
I have just updated to the latest firmware and OSV2.
Now when I connect wifi dongle it says wifi device connected but I do not have wifi action in menu, it just dissapeared.
Network interface available now is only LAN. TL725N does not turn green when I plug in.
Anyone had this problem?
Hey,
I have just updated to the latest firmware and OSV2.
Now when I connect wifi dongle it says wifi device connected but I do not have wifi action in menu, it just dissapeared.
Network interface available now is only LAN. TL725N does not turn green when I plug in.
Anyone had this problem?
Yes, everyone.
Check a few posts further back in this thread where it is talked about...
Downgrade to 6.1.35R2 for now if you need WiFi working.
37R5 beta FW in my inbox to test over the weekend.
Had a few issues with it still not always WiFi boot syncing the NTP clock especially if you booted time and time again however if left for a few minutes between boots it seemed to sync properly and all seems well.
Why it initially played up IDK.
Just one little thing that's sort of associated that needs polishing and it should be ready for release but when that might be IDK.
Will do my best to have them push it through.
Have you checked if DHCP is working now? In my network i like to use dhcp with reservation instead of fixed ip addressing...
It is although not quite like I was expecting.
WiFi connection:
Change IP to an address where conflict is almost guaranteed then Save....DHCP = OFF
DHCP = ON ....IP returns to previous setting and one given some weeks back where any IP conflict would be very unlikely.
Will forward this info.
Seem that at best is ignoring the dhcp lease time. Now that have the current time via ntp would be easy to know when do a new request after the lease time expire. Another approach (that not require storing the last dhcp request) would be a new request every boot, then doing a renew when the lease time expires. This need only a variable in ram counting the seconds from the last renew
A DHCP lease renewal is actually initiated after 50% of the time has expired. At this point, if successful, the lease time is reset to zero.
So in theory a device can keep an IP for a very long period if the renewal is successful during the 50% to end period.
Even after the expiry period, the same IP can still be assigned if it wasn’t used by another device. So it can appear to be ‘fixed’, but is actually just not being re-used by something else.
It is although not quite like I was expecting.
WiFi connection:
Change IP to an address where conflict is almost guaranteed then Save....DHCP = OFF
DHCP = ON ....IP returns to previous setting and one given some weeks back where any IP conflict would be very unlikely.
Will forward this info.
Sometimes I get the feeling that tautech should be in the developer's team... don't know why...
I can't say I checked this in previous firmware versions as I've only had my unit for a short time and updated the firmware soon after getting it, but on the latest firmware my 8GB USB thumb drive is not detected if it is already plugged in when the device boots, I have to plug it in after it has booted. (Or unplug it then plug it back in again, after I realise it is not detecting it)
Is anyone else having a similar problem ? Not the end of the world, but it is a little annoying as I like to have a thumb drive plugged into the rear port out of the way but then have to fiddle around removing it and reinserting it if I want to actually use it.
I actually prefer to keep scopes plugged into network, and for screen captures, just take a snapshot from web interface directly on a PC... That is where I take it in the end eventually anyways..
If I recall correctly this was already reported..
I actually prefer to keep scopes plugged into network, and for screen captures, just take a snapshot from web interface directly on a PC... That is where I take it in the end eventually anyways..
If I recall correctly this was already reported..
Yes, I use the screen capture feature in the web interface too - when it's sitting on my desk beside the computer where Ethernet is available.
Everywhere else I need to use a thumb drive - especially given that the current firmware version has broken the WiFi... and so far I've actually used the scope more away from its usual desk (including outside on a car) than I have on the desk with Ethernet available.
So a reliably working USB save function is still important to me. Having a dedicated thumb drive plugged in out of the way at the back so its always ready to press print at a moments notice is useful, so it's a little annoying that I have to unplug and reconnect the drive every time the scope is powered up.
They seem to be missing some pretty obvious problems in this recent firmware version - how did they not notice WiFi was broken for example ? No regression testing, that's how...