Calling any Garmin 18x users,
I noticed this morning that my Garmin 18x was giving the time 1 second
slow to UTC - it has been running in sync with UTC for about 2 years
now.
Garmin has recently ( 13th Dec 2010 ) changed the 18x firmware from
3.30 to 3.50, so I updated my GPS sensor just now to t
> I noticed this morning that my Garmin 18x was giving the time 1 second slow
> to UTC - it has been running in sync with UTC for about 2 years now.
I assume it was working correctly previously. If not... At least one GPS
receiver I've used is off by a second. There is an ambiguity as to whe
Hal Murray wrote:
> I assume it was working correctly previously. If not... At least one GPS
> receiver I've used is off by a second. There is an ambiguity as to whether
> the time applies to the previous or next PPS.
You were correct Hal, the problem with the new firmware for the 18x,
is the
In my various tinkering it always seems that I have to recreate a software
clock that accounts for the behavior thats advanced by 1 second. Have done
that on 2-3 projects the most recent being the GOES DC468 simulator.
Regards
On Thu, Dec 23, 2010 at 5:49 AM, Kiwi Geoff wrote:
> Hal Murray wrote
precise time and frequency measurement
Sent: Thu, December 23, 2010 11:43:45 AM
Subject: Re: [time-nuts] My Garmin 18x, Ver 3.50, currently 1 second slow to UTC
In my various tinkering it always seems that I have to recreate a software
clock that accounts for the behavior thats advanced by 1 second
ccount for this behaviour would be nice (:
>
>
>
> - Original Message
> From: paul swed
> To: Discussion of precise time and frequency measurement <
> time-nuts@febo.com>
> Sent: Thu, December 23, 2010 11:43:45 AM
> Subject: Re: [time-nuts] My Garmin 18x, Ver
I don't believe so. I paid for my copy.
- Original Message
From: paul swed
To: Discussion of precise time and frequency measurement
Sent: Thu, December 23, 2010 12:07:07 PM
Subject: Re: [time-nuts] My Garmin 18x, Ver 3.50, currently 1 second slow to UTC
Is tac32 free to ama
Calling any Garmin 18x users,
I noticed this morning that my Garmin 18x was giving the time 1 second
slow to UTC - it has been running in sync with UTC for about 2 years now.
[]
So I wondered, any other folk out there with a Garmin 18x - is it 1 second
slow to UTC ?
Regards, Kiwi Geoff (Chri
Le 29/12/2010 08:32, David J Taylor a écrit :
Calling any Garmin 18x users,
I noticed this morning that my Garmin 18x was giving the time 1 second
slow to UTC - it has been running in sync with UTC for about 2 years now.
[]
So I wondered, any other folk out there with a Garmin 18x - is it 1
Ooops... 3.50 firmware is still available at garmin.. I had clicked the
wrong link.. sorry
Le 29/12/2010 09:55, Cook Mike a écrit :
Le 29/12/2010 08:32, David J Taylor a écrit :
Calling any Garmin 18x users,
I noticed this morning that my Garmin 18x was giving the time 1
second slow to UTC
David Taylor wrote:
> I see the same effect on my GPS 18x LVC with the 3.50 firmware.
> Have you reported this to Garmin?
No I haven't reported this to Garmin, at first I just wanted to find
out if "my" GPS was at fault or was this common across any 18x.
The reason it caught me out, is that I had
> It is possible that this has been reported as I do not see 3.50 available
> on garmin.com. 3.10 is the latest. Could not find anything in faq's or
> alerts though.
This page has comments for 3.20 and 3.50:
http://www8.garmin.com/support/download_details.jsp?id=4055
(But it's all in a Window
Ooops... 3.50 firmware is still available at garmin.. I had clicked the
wrong link.. sorry
Mike, I have the 3.20, two different versions of the 3.30, and the 3.50.
I would still encourage as many folk as possible to report this to Garmin.
I would be reluctant to go back as I recall it was a pr
The reason it caught me out, is that I had changed to version 3.30
(where it also delays NMEA) on the 27th Sep 2010, and it took a couple
of months to manifest as a problem. It was the "rising of the sap" in
my trees combined with windy weather - which pushed the NMEA into the
next second for my a
From: "Hal Murray"
Sent: Wednesday, December 29, 2010 9:16 AM
To: "Discussion of precise time and frequency measurement"
Subject: Re: [time-nuts] My Garmin 18x, Ver 3.50, currently 1 second slow
to UTC
This page has comments for 3.20 and 3.50:
http://www
Hi Geoff,
Did you and I run into the same issue with NMEA from old Jupiter
receivers? (many years ago at the now dead forum at gpskit.nl)
--
Björn
>> To me it's unacceptable that the NMEA output is delayed into the next
>> PPS
>> signal, making the unit much less useful. I measure the NMEA
Björn wrote:
> Did you and I run into the same issue with NMEA from old Jupiter
> receivers? (many years ago at the now dead forum at gpskit.nl)
We may have Björn, I know we have communicated before, but I'm not
sure on what topic(s).
I have never owned or played with a Jupiter - so I have never
David Taylor wrote:
But which would you trust?
I have only run extensive tests on Version 3.00 (for the 18x LVC) so I
know I can trust that version with respect the NMEA completing within
the second and stability of 1PPS.
I admit I just "assumed" subsequent versions were OK (without testing
my
David Taylor wrote:
> Thanks, Geoff. I have just look for that version on the Garmin
> Web site but could not find it,
David, a quick Google Search found this:
http://www.gawisp.com/perry/oem_sensor/
>From there I downloaded: GPS18xPC_LVC_300.exe
and it is an exact file match for the fi
David, a quick Google Search found this:
http://www.gawisp.com/perry/oem_sensor/
From there I downloaded: GPS18xPC_LVC_300.exe
and it is an exact file match for the file I downloaded from Garmin (Feb
2009).
Regards, Geoff (Christchurch, New Zealand)
Your Googling is better than mine!
So, what is the final consensus as to which is the best firmware
version to use for NTP purposes?
Joe Gray
W5JG
On Thu, Dec 30, 2010 at 7:11 AM, David J Taylor
wrote:
>> David, a quick Google Search found this:
>>
>> http://www.gawisp.com/perry/oem_sensor/
>>
>> From there I downloaded: GP
> So, what is the final consensus as to which is the best firmware
> version to use for NTP purposes?
I don't know, but I trust y'all know about:
http://support.ntp.org/bin/view/Support/ConfiguringGarminRefclocks
H
___
time-nuts mailing list -- time-
So, what is the final consensus as to which is the best firmware
version to use for NTP purposes?
Joe Gray
W5JG
Any, providing you don't use the NMEA data to get the nearest second, but
use a secondary reference source. Bit of a problem for a stand-alone
system, though.
I certainly would /
If I am using the NMEA data (as in the Garmin is the only time
source), what firmware is recommended by all those using a GPS18x-LVC?
Joe Gray
W5JG
On Fri, Dec 31, 2010 at 1:52 AM, David J Taylor
wrote:
>> So, what is the final consensus as to which is the best firmware
>> version to use for NTP
If I am using the NMEA data (as in the Garmin is the only time
source), what firmware is recommended by all those using a GPS18x-LVC?
Joe Gray
W5JG
Kiwi Geoff recommended:
__
http://www.gawisp.com/perry/oem_sensor/
From there I downloaded: GPS18x
On 12/31/2010 10:20 AM, Joseph Gray wrote:
If I am using the NMEA data (as in the Garmin is the only time
source), what firmware is recommended by all those using a GPS18x-LVC?
Here are measurements on the bad versions:
http://n1.taur.dk/permanent/gps18x-330-pps.jpg
http://n1.taur.dk/permanent/
Joseph Gray wrote:
> If I am using the NMEA data (as in the Garmin is the only time
> source), what firmware is recommended by all those using a GPS18x-LVC?
I thought I would run some tests for you Joe, using Version 3.0 and 3.2
Although I myself have run version 3.0 for a number of months (when
Geoff,
Thanks a lot for comparing firmwares. That hard information helps tremendously.
Joe Gray
W5JG
On Tue, Jan 4, 2011 at 8:46 PM, Kiwi Geoff wrote:
> Joseph Gray wrote:
>> If I am using the NMEA data (as in the Garmin is the only time
>> source), what firmware is recommended by all those usi
I agree, very helpful, thanks Joseph!
I recently got two 18x that I upgraded to 3.50. (I'm starting to work on
integrating some M12+T modules to supplement/replace the 18x's).
Has anyone had trouble with reverting firmware upgrades on Garmin products?
Of course, feedback on going back from 3.50
Kevin, Geoff, Joseph, and anyone else who has this problem
Thanks to Geoff for those measurements.
I had an e-mail response from Garmin which suggested turning off the
position averaging introduced as a new option in 3.50 firmware. Whilst
that may have helped a little, I still saw (at 192
On Jan 5, 2011, at 1:15 AM, David J Taylor wrote:
> [...]
> The Garmin rep who wrote to me suggested that Garmin were unaware of the
> problem, but would investigate it. Could I urge you all to report this
> problem to Garmin, please, so that we have a greater chance of getting a fix
> in the n
David, that's a fine idea. Do you have an email address (or other
contact info)
where our reports of this issue have a greater chance of getting to the
firmware
group compared to being forwarded to a write-once, read-never file?
Kevin
Kevin,
I only have a generic e-mail address:
product [pe
david-tay...@blueyonder.co.uk said:
> I had an e-mail response from Garmin which suggested turning off the
> position averaging introduced as a new option in 3.50 firmware. Whilst
> that may have helped a little, I still saw (at 19200 baud) sentences
> starting during the PPS signal, i.e. more th
I think you will have a much better chance of getting Garmin to fix
something
if we can come up with a clear description of what is broken and/or a
simple
recipe for a setup that demonstrates the problem.
What do you mean by "more than one second delayed"? That sounds like
you are
looking at
Hal Murray wrote:
> It would be really neat if you could run similar experiments on 3.3 and/or
> 3.5.
I have run some more tests Hal, with V3.5, averaging ON and OFF.
I include V3.2 for comparison.
I measured the time of the "START" character ($) of the $GPRMC
sentence and the "LAST" 0x10 (Line
On Jan 5, 2011, at 4:08 AM, Kiwi Geoff wrote:
> I have "reverted" quite a number of times now Kevin - trying to
> understand why the 18x can be 1 second slow. I have never had an issue
> putting in an older version into the 18x, the updater software does
> know what your doing, it says:
Hi Geoff (
This agrees with what Kasper Pedersen wrote earlier:
3.10 starts transmitting 350ms .. 480ms after PPS
3.30 starts transmitting 920ms .. 1220ms (!) after PPS
3.50 starts transmitting 700ms .. 1220ms (!) after PPS
Folks,
With some help from Hal Murray who knows more of NTP than I do, we have
w
37 matches
Mail list logo
