EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: pOM on December 02, 2021, 03:01:19 pm
-
When I look at "System Status", it shows:
Startup Times:
95
Software Version:
6.1.37R6
Uboot-OS Version:
8.1
FPGA Version:
2021-07-12
Hardware Version:
01-04
Product Type:
SDS1104X-E
Serial No.:
SDSMMEBD . . . . .
Is "Uboot-OS Version" 8.1 the current operating system? Is that V1? If so, when V2 (currently available) would be installed, should it indicate 8.2?
Or is the Operating System version not actually shown in "System Status"?
-
Have you updated the firmware or is it as you got it ?
If you haven't got the new Logging feature in the Utility menu V2 OS needs installing and you can find it down the page here:
https://int.siglent.com/download/firmwares/?ProId=12
-
Thanks for the prompt reply;
Yesterday, I had updated the firmware to the latest version, 6.1.37R6. However, I also noticed there's a fairly recent Operating System update to V2. I got the scope in early 2020 and while I have now installed 2 Firmware updates, I've not installed an OS update. That suggests I probably don't have V2 of the OS, but was trying to verify that in the System Status.
The Revision History for the Firmware shows that the Data Logger was added in Firmware version 6.1.37R2, so it would be in 6.1.37R6 which I have now. And, indeed in the Utility menu (4 pages) there is a "Data Logger" button on page 2, and that splits to "Sample Logger" and "Measure Logger". But that only verifies that the Firmware is up-to-date.
The Revision History for the OS (only 3 entries) makes no mention of the Data Logger function.
[attach=1]
-
Incidentally, the Update Instructions to install OS V2 conclude with:
"4) Confirm the OS updated successfully by observing the system information on the scope. If the software version is 2, the update was successful. To show OS version ID, the SDS1xx4X-E must have ADS version of >6.1.25R1."
But it doesn't say what the "system information" would/should actually show in regard to the current operating system version. (I presume "system information" is the "System Status" under "Utility".)
-
If you had searched in the X-E thread... there are several msgs there confirming that the Uboot-OS version is "uboot version"."OS version".
-
My bad!
I had seen the mega-thread "Siglent SDS1104X-E and SDS1204X-E Mixed Signal Oscilloscopes" when I joined here last year, but never managed to read through it. But I finally did now, and, yes, the answer is there.
"Uboot-OS Version:
8.1"
does indicate that the OS is version 1 (disregard the "8."), and when the OS is updated to V2, it would show 8.2.
Thanks for the push! I learned a lot more about the scope in the process.
(Now to rest my eyes after reading through 80+ pages.)
But before I do that, I did the OS update; Took just a few seconds from powering on, to complete. System Status now shows 8.2. All good.
-
Good. You're all sorted then. :-+
On all the Siglent websites the firmware Release Notes for V6.1.37R2 offer full info and clues to needing V2 OS for the new features.
V6.1.37R6 came along soon after to fix the WiFi issues.
-
It was in the Firmware Release Notes that I first noticed the availability of the new Version 2 of the Operating System, and wondered what Imy scope had; although it's needed only to activate the Network Time Protocol to have local real time display.
Yes, all good now.
Thanks
-
My bad!
I had seen the mega-thread "Siglent SDS1104X-E and SDS1204X-E Mixed Signal Oscilloscopes" when I joined here last year, but never managed to read through it. But I finally did now, and, yes, the answer is there.
"Uboot-OS Version:
8.1"
does indicate that the OS is version 1 (disregard the "8."), and when the OS is updated to V2, it would show 8.2.
Thanks for the push! I learned a lot more about the scope in the process.
(Now to rest my eyes after reading through 80+ pages.)
But before I do that, I did the OS update; Took just a few seconds from powering on, to complete. System Status now shows 8.2. All good.
Hi pOM, I need your advice., if you please.
I copied 4 files extracted from OS v2 zip file to the USB, inserted to the scope powered-off and then powered on the scope but nothing happened. Device just rebooted to the normal state, no auto-upgrade procedure started, though.
Is there any trick to be done during this procedure?
Will appreciate help.
(I upgraded the firmware to the latest without any problems, just OSv2 did not succeed)
-
I copied 4 files extracted from OS v2 zip file to the USB, inserted to the scope powered-off and then powered on the scope but nothing happened. Device just rebooted to the normal state, no auto-upgrade procedure started, though.
Is there any trick to be done during this procedure?
Will appreciate help.
(I upgraded the firmware to the latest without any problems, just OSv2 did not succeed)
Welcome to the forum.
The only indication V2 OS is being installed is boot time is a little longer than normal. A USB stick with an activity LED is useful to indicate the upgrade is happening.
It seems some old models like my pre-production SDS1104X-E do not show the OS is installed and still report OS 8.1 although if the new NTP feature works correctly, indeed the new OS V2 has been correctly installed.
-
The only indication V2 OS is being installed is boot time is a little longer than normal. A USB stick with an activity LED is useful to indicate the upgrade is happening.
It seems some old models like my pre-production SDS1104X-E do not show the OS is installed and still report OS 8.1 although if the new NTP feature works correctly, indeed the new OS V2 has been correctly installed.
So, there's no way to know whether OS2 is installed or not other than wild guessing? Weird.
-
Did you read my msg above?
-
The only indication V2 OS is being installed is boot time is a little longer than normal. A USB stick with an activity LED is useful to indicate the upgrade is happening.
It seems some old models like my pre-production SDS1104X-E do not show the OS is installed and still report OS 8.1 although if the new NTP feature works correctly, indeed the new OS V2 has been correctly installed.
So, there's no way to know whether OS2 is installed or not other than wild guessing? Weird.
As reported above my old pre-release unit still reports 8.1 however the new NTP feature works perfectly and without OS V2 it should not work at all according to the release notes.
However every unit in stock we have updated to OS V2 reports 8.2 in the Sys info page.
-
. . . I copied 4 files extracted from OS v2 zip file to the USB, inserted to the scope powered-off and then powered on the scope but nothing happened. ll appreciate help.
(I upgraded the firmware to the latest without any problems, just OSv2 did not succeed)
Was the power off when the USB stick was "inserted to the scope". I think this was the case, but I can read the description as if the stick was inserted while the power was on, then scope was "powered-off" and then powered on. Small possibility, but just want to be sure. The instructions say to insert the USB stick when the scope power is off, then turn it on. That's the way I did it. And as tautech noted, I was using a stick with a light, so I could see there was "activity" during the updated. The update was, indeed, very fast.
The USB stick I used for the OS update had no other data on it. I had used it for the firmware update, but removed those files before use for the OS. Not sure if this might be relevant for you.
That's about all I can offer. (This is all relatively new to me, but I'm learning fast!)
-
. . . I copied 4 files extracted from OS v2 zip file to the USB, inserted to the scope powered-off and then powered on the scope but nothing happened. ll appreciate help.
(I upgraded the firmware to the latest without any problems, just OSv2 did not succeed)
Was the power off when the USB stick was "inserted to the scope". I think this was the case, but I can read the description as if the stick was inserted while the power was on, then scope was "powered-off" and then powered on. Small possibility, but just want to be sure. The instructions say to insert the USB stick when the scope power is off, then turn it on. That's the way I did it. And as tautech noted, I was using a stick with a light, so I could see there was "activity" during the updated. The update was, indeed, very fast.
The USB stick I used for the OS update had no other data on it. I had used it for the firmware update, but removed those files before use for the OS. Not sure if this might be relevant for you.
Yes, like our recovery packages an OS update also needs be in the root of the USB drive whereas a FW update can be deep within folders providing you can navigate to it and select it with a press of the multipurpose encoder.
USB sticks of 8GB max and FAT32 4k clusters work with all Siglent instruments and larger ones will work in some models.
Ideally Siglent should consider providing a compatible and Siglent branded USB stick with all instruments preloaded with all manuals and SW for the model instead of the CD's we get in our boxes. Even a tiny 2 or 4 GB stick would easily fit all the manuals and SW plus a good many FW updates.