On Wed, Jul 17, 2019 at 7:59 PM William Unruh wrote:
> I suspect it will be a bad outcome. The rpoblem is that you get
> interrupt contention, and the two interrups will put in time delays into
> the second one processed.
>
That was my observation when I did some tests years ago with a single cor
On 07/18/19 11:13, William Unruh wrote:
Sure, but I do not have faith in the "averaging" If one is always 30us
after the other, then the average will always be out by 15us.
One would expect a difference, but how can you tell which one is right
using just 2 pps ?. With three, you could choose
On 2019-07-19, Chris wrote:
> On 07/18/19 11:13, William Unruh wrote:
>
>>
>> Sure, but I do not have faith in the "averaging" If one is always 30us
>> after the other, then the average will always be out by 15us.
>
> One would expect a difference, but how can you tell which one is right
> using j
On Sat, Jul 20, 2019 at 2:26 AM Gabs Ricalde wrote:
>
> On Wed, Jul 17, 2019 at 7:59 PM William Unruh wrote:
> > I suspect it will be a bad outcome. The rpoblem is that you get
> > interrupt contention, and the two interrups will put in time delays into
> > the second one processed.
> >
>
> That
David Taylor kindly added one of my old graphs to his Garmin LVC18 pages:
https://www.satsignal.eu/ntp/Garmin-GSP18x-LVC-firmware-issue.htm#3.60
The graph is from an email exchange with Garmin ~seven years ago and shows
timing of the NMEA version 3.60 firmware. This version suffered from drift
and