@wpwrak has suggested an implementation for my first two bullets, for which thanks. That solution however requires hacking the scope and is not integrated into the UI. It also does not implement the features from my last two bullets.
I.m.o. getting time from NTP server should not be done too frequent to minimize (inter)network traffic (unless the scope firmware is unable to maintain time accurately, which I doubt because operating the scope already requires precision timing but Siglent will know this best).
1. You can, ATM, use the SCPI SHELLCMD command and as a parameter pass your NTP string command. This doesnt require any "hacking".
2. After sync the clock, you can kill the NTP daemon.
Although it gives a little more work everytime you want to save files, another option is:
Since to save the files you need to have the USB drive inserted, one can run a script (residing in the USB) only when you want to do a "save files" session.
For that, you only have to create a proper script that activates the ntpd and I can make an .ADS from it.
How to: With that, you can run an "Update" with that .ADS just before doing the "save files" session. It takes 1 or 2 seconds and you're ready to save files with the proper datetime.
Benefit: This method, like the SHELLCMD, doesnt imply any changes to the scope's settings and is more complete than the SHELLCMD because you can execute a more complex script (launch NTPD, kill it, etc..).
Nice but I just want to press the 'On' button and then things should work without having to do any fancy stuff / perform manual actions etc. and without having to perform any actions on some PC.
That executes with root privilege?
I.m.o. getting time from NTP server should not be done too frequent to minimize (inter)network traffic (unless the scope firmware is unable to maintain time accurately, which I doubt because operating the scope already requires precision timing but Siglent will know this best).Keeping proper ntp synchronization, although simple (the support is there, in the Linux system they use) is maybe overkill.
But just a ntpdate to set the proper date and time at boot time would be really useful. It would mean the files would be timestamped with a usable date and time, just like it had a RTC.
@wpwrak has suggested an implementation for my first two bullets, for which thanks. That solution however requires hacking the scope and is not integrated into the UI. It also does not implement the features from my last two bullets.
I.m.o. getting time from NTP server should not be done too frequent to minimize (inter)network traffic (unless the scope firmware is unable to maintain time accurately, which I doubt because operating the scope already requires precision timing but Siglent will know this best).
1. You can, ATM, use the SCPI SHELLCMD command and as a parameter pass your NTP string command. This doesnt require any "hacking".
2. After sync the clock, you can kill the NTP daemon.
Nice but I just want to press the 'On' button and then things should work without having to do any fancy stuff / perform manual actions etc. and without having to perform any actions on some PC.
Not just at boot time, but also whenever there has been no time synchronization after boot and a network cable is connected (if the device can detect such at runtime), or when it has been long enough since last sync (preferably adjustable period). The last case would handle (rare?) situations where the scope is being used 24/7 and never turned off or disconnected/reconnected to network, so the periodic resync prevents eventual drifting to get out of hand (assuming exact time is important).
Also, would be nice if the user has an option to configure the time server to be used. E.g. in some cases the LAN might not be connected to internet at all, and a local network time server would be used instead. Or, as I have noticed (only) couple times, the preconfigured time server has since vanished, or service has changed to only provide time for better tier clients (i.e. other time servers), not for ordinary end users.
I'm confused, you want a cheap and capable oscilloscope with all of the bells and whistles so you can fix and/or work on electronics, and yet you don't want to do anything to make your chosen device capable of the things you want it to do? That seems like a tall order.
What you have is a great device with lots of features that is still under development, and you have a dogged group of engineers and scientists (the people in this thread) who are dedicated to finding ways to make this device better at no additional cost to you. You have the solution to your problem in your hand, use it instead of complaining about how a device under development doesn't come with everything you want out of the box.
Add Time and Date support:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1756706/#msg1756706
"... just for those people that are willing to connect their scopes to the net ..."
Unfortunately I see only very limited constructive suggestions for Siglent like the one below in this thread. Even while clearly marked as 'suggestions for new features', several people appear to have difficulty reading them and react to the latest posts in this thread instead.
...
I have many devices that require tweaks but I dislike managing them all manually and having to fix things again after the next software/firmware update. So I preferably want certain features to be supported by the manufacturer and supported in the UI, which is why I have made the efforts to add several suggestions for new features and reported a security bug in this thread.
So who is complaining here?
FYI my SDS1104X-E is @SDS1204X-E.
"With the WiFi this will be a good solution"
Requesting time and date from an NTP server via the network works for both wireless and wired network connections (my scope is connected wired to the network).
anyone have problems with long PSK's on wifi?
I am using a long PSK ~25 characters long with spaces in it, and it doesn't seem to be working.There is a bug with network SSIDs which contain spaces. The scope will see this network but won't be able to connect to it.
Siglent confirmed this bug but I don't know when it will be fixed.
My WiFi dongle was not supplied by Siglent and works fine with networks without spaces in SSIDs.
anyone have problems with long PSK's on wifi?
I am using a long PSK ~25 characters long with spaces in it, and it doesn't seem to be working.There is a bug with network SSIDs which contain spaces. The scope will see this network but won't be able to connect to it.
Siglent confirmed this bug but I don't know when it will be fixed.
My WiFi dongle was not supplied by Siglent and works fine with networks without spaces in SSIDs.Is it the Siglent or the TP-Link TL-WN725N that gives the problem with spaces in the SSID?
I once bought a TP-Link wireless router that didn't allow spaces in the SSID, when all my other devices did. Replaced it with a Netgear and all was well again.
Looking to get this scope and use that bode plotting feature but a bit confused on what configuration to get. You can get that SAG1021 AWG that plugs with usb and I suppose you need to buy a separate AWG licence also to use that dongle... But apparently you could get a siglent brand SDG (1032X?) external AWG that can also plug in with usb(?) and use the automated plotting feature without a licence? Some page stated that external AWG doesnt require a licence for some reason.
e. ok found some old comments, 1104X-E + SDG1032X should work together out of the box, nice.
New to scopes. Testing my new 1204x-e. What really makes think bad is the fact that just sitting scope on the bench is showing 20-30 mV on its outputs without probes connected.
Is it for sure problem with mine example or might it be a problem with bad 220v line/ground?
Attch. 59-63 what I see on display of 1204 without probes or cables in it.
39-40 - what is seen in the "220v/50" line of my socket.
Please advice should I go back asap to the dealer and change this one example.
39-40 - what is seen in the "220v/50" line of my socket.
My machine showed 7.6.1.20.r3 on the screen.
so I am little bit confused is that lower or higher than 6.1.26 Depending on the logic of what way to read might be both.
Started mache to run for 30 min to make calibration. Actually, I have made it once after for sure few hours of runtime.
New to scopes. Testing my new 1204x-e. What really makes think bad is the fact that just sitting scope on the bench is showing 20-30 mV on its outputs without probes connected.
Is it for sure problem with mine example or might it be a problem with bad 220v line/ground?
Attch. 59-63 what I see on display of 1204 without probes or cables in it.
39-40 - what is seen in the "220v/50" line of my socket.
Please advice should I go back asap to the dealer and change this one example.