Products > Test Equipment

Siglent SDS1104X-E and SDS1204X-E Mixed Signal Oscilloscopes

<< < (506/518) > >>

Calambres:
I quote myself:

--- Quote from: Calambres on September 19, 2023, 09:17:45 am ---.../...
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  ::)

--- End quote ---

Well, I got a better quality and shielded USB extension cable and yes, the WLAN now connects with no issues albeit I still got some noise induced by the crappy USB hub. Less noise than before but still there. I need to address this problem but nowadays is not easy to get a good quality USB2 hub and we all know the problems with USB3 hubs and WLAN connections! ::)


--- Quote from: Calambres on September 19, 2023, 09:17:45 am ---But stilll there's a possible bug with the NTP implementation in the scope!  ;)

--- End quote ---
Yes, this is definitely a bug!

2N3055:

--- Quote from: Calambres on November 16, 2023, 08:49:26 am ---
--- Quote from: Calambres on September 19, 2023, 09:17:45 am ---But stilll there's a possible bug with the NTP implementation in the scope!  ;)

--- End quote ---
Yes, this is definitely a bug!

--- End quote ---

Not really, IMO.  You cannot call anything you don't like a bug.

NTP is separate service from basic TCP/IP stack. NTP will refresh when it's time interval is due.
It uses TCP/IP routing and connectivity to server is transparent to it.
It does not know anything changed on TCP/IP level and don't care.

Would it be nice it would do that. Maybe. Maybe not.

What is real purpose of that?
You have a scope that is connected to LAN, and it got it's time from NTP.
Time is correct now.

You switch to WLAN.
It won't requery NTP server because it is already set and time interval for next update is not due.
It has nothing to do with how networks are being connected-disconnected. Clock in device (soft clock) is actually keeping time in meantime.

Did I understand correctly?

tautech:
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.

2N3055:

--- Quote from: tautech on November 16, 2023, 09:45:05 am ---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.

--- End quote ---

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..

If you boot with network connected it will work normally. If you boot with network not connected, it will timeout on initial synch. Until next scheduled update, when it will update if network was connected in meantime. Were you can use manual update to speed up things.
If you need reliable NTP, provide reliable network.

There is no built in "option to enable" or "bug to fix".
What can be done is to make separate monitor service that will be aware that time is not set (NTP client connect failed, or synch failed), and would keep that status and be mindful of network connectivity.
But you can have Ethernet port or WIFI connection UP and still have no connectivity to Internet.
What to do then? How do we detect NTP servers are available for synch then?
Gets complicated quickly...

What I think could be useful would be a marker (clock background painted red or something) to user that NTP is set to synch and failed last time. So they know they have network problems and that clock might be in in "uncal" state of a sort..

tautech:

--- Quote from: 2N3055 on November 16, 2023, 10:14:20 am ---
--- Quote from: tautech on November 16, 2023, 09:45:05 am ---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.

--- End quote ---

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..

--- End quote ---
Correct, not a bug but could be improved.
X-E do not have RTC so when we need it, we need it and it's reliable operation should be linked/latched to network connectivity status.
That is, when when we connect we have a network indicator which shows the OS is monitoring connectivity when NTP refresh could be linked to the network indication rather than need to rely on a NTP sync.

An NTP autosync tied to network connectivity indication will solve this issue automatically and almost instantly.
Those that have these know this issue.  ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod