.../...
BUT, while fiddling with all these configurations I suspected from that very USB extender cable and, know what?... it is also not shielded, as it was the cable from the hub!... again the chinesium curse strikes me back! it is quite possible that buying a good quality USB extender cable will solve the noise problems I'm having
But stilll there's a possible bug with the NTP implementation in the scope!
But stilll there's a possible bug with the NTP implementation in the scope!Yes, this is definitely a bug!
As member mwb1100 suggests:
whenever the scope goes from a disconnected to connected state (whether LAN or Wifi), it should automatically Sync NTP if "Power On Sync" or "Periodic Sync" is on
Is proposed for Siglent to consider.
As member mwb1100 suggests:
whenever the scope goes from a disconnected to connected state (whether LAN or Wifi), it should automatically Sync NTP if "Power On Sync" or "Periodic Sync" is on
Is proposed for Siglent to consider.
I'm not against it.
But it is not a bug. No NTP service does that. I'm not even defending Siglent scope here. It's just no NTP is supposed to do that. On any device.
It is not a bug.
NTP does not care about network. After initial synch (on boot) because it has not battery backed up clock, next refresh is when built in software clock accuracy is questionable because it has been running too long, and then we recheck with NTP server if there are corrections needed.
Actually, if device clock is any good, it is recommended not to synch NTP too often, because it introduces timing jitter...
Updates are not correlated to network config, but only to clock needs..
As member mwb1100 suggests:
whenever the scope goes from a disconnected to connected state (whether LAN or Wifi), it should automatically Sync NTP if "Power On Sync" or "Periodic Sync" is on
Is proposed for Siglent to consider.
I'm not against it.
But it is not a bug. No NTP service does that. I'm not even defending Siglent scope here. It's just no NTP is supposed to do that. On any device.
As member mwb1100 suggests:
whenever the scope goes from a disconnected to connected state (whether LAN or Wifi), it should automatically Sync NTP if "Power On Sync" or "Periodic Sync" is on
Is proposed for Siglent to consider.
I'm not against it.
But it is not a bug. No NTP service does that. I'm not even defending Siglent scope here. It's just no NTP is supposed to do that. On any device.
Actually, that is incorrect. The scope is using a variant of NTP known as Simple NTP or SNTP. (The key difference is polling and directly setting time instead of the full NTP approach of synchronized, adaptive feedback loop keeping time in sync potentially as both a client and a server.) Many network devices which obtain time using SNTP do indeed poll the NTP server when the network connection is started, and start their polling interval from that event. In those devices if the network disconnects then the NTP service will poll again immediately on reconnect whether or not the polling interval has lapsed.
A full NTP implementation actually creates a lot more network traffic than SNTP as the poll intervals for SNTP are typically multiple orders of magnitude longer than that for a full NTP implementation (often 1024 seconds max compared to hours or even a daily poll for SNTP). This means that it is more important for a SNTP implementation to poll on connect since it might be a very long time before the interval expires compared to a few seconds for a full NTP implementation. One of the primary reasons this has become best practice is the only time you know the network is available is when it connects. In a few hours? Maybe, maybe not.
How do I know this? I have over 30 years of directly applicable standard definition and implementation experience, and currently work as a senior principal firmware engineer in this field. All of the devices running firmware produced by my current employer poll immediately on connect, and so do the vast majority of network devices I've worked with from all the "smart" gadgets in my house to devices costing hundreds of thousands of dollars, at least when using SNTP.
It was added to scope because it does not have a battery backed up RTC, so users don't have to set up clock manually.
Hello I am looking for an measurement tool on my Siglent SDS1104X-E to automatically count edges for a time interval between a specified start-point and end-point.
I can't find such an option. Is this possible or can it be implemented by Siglent?
Can anyone explain the weird jumps in channel skew (like hundreds of uS) when changing vertical gain on one channel on my SDS1104XE?
Hello I am looking for an measurement tool on my Siglent SDS1104X-E to automatically count edges for a time interval between a specified start-point and end-point.
I can't find such an option. Is this possible or can it be implemented by Siglent?
we will still get some maintainance for the X-E series.
I have this vague feeling it probably has been answered somewhere already, but i can't find the information : how does my sds1104x-e reports "Uboot-OS Version: 8.1", while the official siglent updates page mentions "SDS1xx4X-E Operating System -V3 (Only For 4-Channel models) (Release Date 01.05.23 )" ? The only "8.1" mentionned on the page are related to the sla1016 (which i don't own neither care).
I have a recent firmware (6.1.37r6) even if not the latest, and the other informations on the "about" page are unrelated to the OS.
Does "8.1" mean i have the "V1" ? Does "V1" even exist ?
The pdf included in the previously mentioned download (see attachment) mentions versions "1" "2" "3" without the "V". I'm not even sure what i have.
Bonus question: my hardware is old ("01-03"), and i understand i dont "need" version 3, but i can still install it ? I kinda guess 'yes', but I of course don't want to brick my scope because it's only intended for newer hardware revisions.
V1 was the very first OS now updated to V3 to support the later added featureset...
V1 was the very first OS now updated to V3 to support the later added featureset...
I know all of this. I have updated the firmware for sure, and i kinda recall also updating the OS. (but thanks for caring !)
My questions are really focused on "8.1". What is it ? What does it mean ? It seems so unrelated to the official documents / web pages.
As I recall the 8 signifies the product line or maybe UI type and 1 is the OS version.
Not all get 8.3 displayed after installing with some displaying 8.2 but V3 OS can be confirmed installed correctly if you have the Logging or NTP feature working correctly.
As I recall the 8 signifies the product line or maybe UI type and 1 is the OS version.
Not all get 8.3 displayed after installing with some displaying 8.2 but V3 OS can be confirmed installed correctly if you have the Logging or NTP feature working correctly.
Ok, so it's really messy, no wonder i was lost. Thanks for clarifying somehow !
With other words: If your HW version is below 09-xx) do not update to V3. (If you still try, nothing happens but you waste time - remember that it is a non-renewable resource at the personal level)