Re: [time-nuts] Quick check of a GPS controller oscillator

2020-05-06 Thread Sanjeev Gupta
On Wed, May 6, 2020 at 8:22 PM Bob kb8tq wrote: > If all of that sounds like a lot of work (or not complete enough), buy a > second ( or third > or fourth ….) GPSDO. Next get a couple Rb’s …. maybe a Cs or three …. have > you > looked into Masers? :) > AT, AT. He meant "looked AT Masers" :-)

Re: [time-nuts] an interesting timing problem

2020-05-06 Thread Steven Sommars
This discussion focuses on interactive audio/data streams. One-way streams are treated differently, since delay is less important. Media transport typically uses IPv4/6 networks and can often be captured at one of the endpoints or somewhere in the network path. E.g., I captured a Skype call

Re: [time-nuts] an interesting timing problem

2020-05-06 Thread Joseph Gwinn
On Wed, 06 May 2020 12:00:02 -0400, time-nuts-requ...@lists.febo.com wrote: Re: time-nuts Digest, Vol 190, Issue 10 > > -- > > Message: 6 > Date: Wed, 6 May 2020 07:00:51 -0700 > From: jimlux > To: Discussion of precise time and frequency measurement > >

[time-nuts] Fwd: [New post] Sun-Seeking Sundial Self-Calibrates in No Time

2020-05-06 Thread djl
for fun Original Message SUBJECT: [New post] Sun-Seeking Sundial Self-Calibrates in No Time DATE: 2020-05-06 14:01 FROM: Hackaday TO:

Re: [time-nuts] an interesting timing problem

2020-05-06 Thread jimlux
On 5/6/20 7:33 AM, Chris Howard wrote: At my current job we were looking into delay timings of video systems. We were doing end-to-end measurement by putting a time display in front of a monitor and have the camera show both the time display and the monitor. It looks a bit like the old

Re: [time-nuts] Quick check of a GPS controller oscillator

2020-05-06 Thread Giuseppe Marullo
Sorry, images where too big, had to repost. Please use this link https://www.iw2jww.it/trimble-and-progrock/ to download them, thanks. On 5/6/2020 8:57 PM, Giuseppe Marullo wrote: Ok, first of all many thanks for your  help. Yep, not exactly a time-nut piece of engineering, but I need more

Re: [time-nuts] an interesting timing problem

2020-05-06 Thread Anton Strydom
Good day Easy way of testing such is to make a skype or team viewer call and then get the other side to synchronize the computer that side as simultaneously as possible with you by click on change date and time settings and then Internet time. It for a few seconds are absolutely perfect but

Re: [time-nuts] an interesting timing problem

2020-05-06 Thread Chris Howard
At my current job we were looking into delay timings of video systems. We were doing end-to-end measurement by putting a time display in front of a monitor and have the camera show both the time display and the monitor. It looks a bit like the old infinite mirror. If you arrange things right

[time-nuts] an interesting timing problem

2020-05-06 Thread jimlux
Given that there's a lot more people spending time zooming, webexing, teaming, skype, facetime, etc. these days, I'm curious if anyone has figured out to *quantify* the issues of lag, desynchronization, etc. How would one go about instrumenting it (without access to the source code or servers

Re: [time-nuts] Quick check of a GPS controller oscillator

2020-05-06 Thread Bob kb8tq
Hi Sure, phase lock vs frequency lock is a fun twist to this. Does it matter in the general case? Regardless of phase lock vs frequency lock, the error on the device should be below the 1 ppb limit mentioned in the post. That’s plenty good enough to resolve the 0.25 ppm (ppm not ppb) errors

Re: [time-nuts] Quick check of a GPS controller oscillator

2020-05-06 Thread Tim Shoppa
Bob, your list isn't bad, but it completely misses the point whether the lock is phase-lock (certainly what anyone in telecom trying to lock a wide network would expect) or frequency-lock (like some BG7BTL's and probably some other Chinese clone cobbled-together units). A large chunk of hobbyist

Re: [time-nuts] Quick check of a GPS controller oscillator

2020-05-06 Thread Bob kb8tq
Hi With any GPSDO (not just the TBolt) you can do some basic checks: (They are in no particular order) 1) Are there > 6 sats in view at all times, if not, move the antenna 2) Is the unit locked to at least 4 sats at all times, if not, move the antenna. 3) Has the unit completed its survey