J
Joerg
Guest
Hello Guy,
corroborates the WWV time signal on 15MHz. The signal via the web was
again about two seconds late this morning, right now it is a little over
one second late.
We do use a HW firewall, maybe that has indeed something to do with it.
Also, I did not use any SW that performs latency averaging.
Regards, Joerg
http://www.analogconsultants.com
Well, both. The atomic clock was low cost, about $20. But it perfectlyI thought that too, but such delays really can't explain why
[ http://tycho.usno.navy.mil/cgi-bin/anim ] would be two seconds
off. If you look at the traffic, once the page is loaded it
sends a handful of bytes once per second, regular as clockwork.
It's hard to come to any conclusion other than tycho.usno.navy.mil
sending late or whatever Joerg is using to detect WWVB being early.
(The latter is remotely plausable if he is using one of those low-
cost "atomic clocks", impossible if he is listening to it.)
corroborates the WWV time signal on 15MHz. The signal via the web was
again about two seconds late this morning, right now it is a little over
one second late.
We do use a HW firewall, maybe that has indeed something to do with it.
Also, I did not use any SW that performs latency averaging.
Regards, Joerg
http://www.analogconsultants.com