Hi there
Unruh wrote:
> This is confusing. You first say that one NMEA sentence pers second is too
> much data, and then that youarranged that it sent 6 sentences per second.
> Note that only one sentence ( which should take about 140ms at 4800Bd) is
> allo you need.
GPRMC, GPGGA, GPGSA and th
>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Hal Murray) writes:
Hal> When I setup a GPS receiver, I try to remember to write down the
Hal> recipe. (and enough notes to remind me what/why) Then I can cut-paste
Hal> from one window looking at my notes to another shell window.
Hal> I've
>My Garmin was sending to much data, sending a NMEA sentence once per
>second. So I put '$PGRMO,,4' in a file and send it to the Garmin.
>Now it's at six lines per second; GPRMC, GPGGA, GPGSA and three GPGSV
>lines (plus one PGRMT per minute).
When I setup a GPS receiver, I try to remember to w
Rob van der Putten <[EMAIL PROTECTED]> writes:
>Hi there
>root wrote:
>> No GPS NMEA should not do that. The length of the sentence is almost fixed
>> length, so the timing on it should vary by perhaps a few msec, as you found,
>> certainly not by seconds. It sounds like you have troubles.
>
Hi there
Steve Kostecke wrote:
> There is no benefit to sending all of those NMEA sentences.
>
> Select one and turn the rest off.
For just time GPRMC will do.
Regards,
Rob
--
When the Iron Curtain fell, all of the West rejoiced that the East
would become just as free as the West. It was ne
On 2008-01-29, Rob van der Putten <[EMAIL PROTECTED]> wrote:
> My Garmin was sending to much data, sending a NMEA sentence once per
> second. So I put '$PGRMO,,4' in a file and send it to the Garmin.
> Now it's at six lines per second; GPRMC, GPGGA, GPGSA and three GPGSV
> lines (plus one PGRMT
Hi there
Rob van der Putten wrote:
> My Garmin was sending to much data, sending a NMEA sentence once per
> second.
Sorry, once per two seconds.
Regards,
Rob
--
When the Iron Curtain fell, all of the West rejoiced that the East
would become just as free as the West. It was never suppose
Hi there
root wrote:
> No GPS NMEA should not do that. The length of the sentence is almost fixed
> length, so the timing on it should vary by perhaps a few msec, as you found,
> certainly not by seconds. It sounds like you have troubles.
>
> You could try using minicom ( assuming you are on
Unruh wrote:
>
> He was refering solely to the NMEA signal not the PPS. Some GPS receovers
> have no pps.
In general those are not suited to accurate time transfer, and ones with
PPS cost a lot less than the the commodity car navigation devices,
because they don't have loads of map data (the pr
>I am afraid I simply do not believe this. NMEA is lucky to get a ms not a
>usec. The offset on the NMEA should be a lot bigger than .001
The NMEA driver includes built-in PPS support.
--
These are my opinions, not necessarily my employer's. I hate spam.
__
[EMAIL PROTECTED] (Folkert van Heusden) writes:
>> The GPS time is not very accurate anyway, and can vary wildly, probably
>> depending on the device, so don't expect perfect offsets. On my Garmin G
>PS
>> 18 LVC, I use 0.190 which gets it in the ballpark, but can randomly jump
>> +16ms to
> The GPS time is not very accurate anyway, and can vary wildly, probably
> depending on the device, so don't expect perfect offsets. On my Garmin GPS
> 18 LVC, I use 0.190 which gets it in the ballpark, but can randomly jump
> +16ms to -10ms at any time.
But if you let ntp handle the pps sign
Nero Imhard <[EMAIL PROTECTED]> writes:
>David J Taylor schreef:
>> The fact that you have a 0.2s offset suggests you are synching to the
>> trailing edge of the PPS signal and not the leading edge.
>The NMEA output would be my prime suspect. It is not surprising to have
>an offset there. The ti
Dennis Hilberg, Jr. wrote:
[]
> I was actually referring to the time emitted in the NMEA data (GPS
> time), not the PPS signal. Sorry, I should have specified that. The
> PPS is accurate to a microsecond, but not the GPS time. I happen to
> use a fudge factor of 0.190 to get the GPS time close t
David J Taylor wrote:
> Dennis Hilberg, Jr. wrote:
> []
>> The GPS time is not very accurate anyway, and can vary wildly,
>> probably depending on the device, so don't expect perfect offsets. On my
>> Garmin GPS 18 LVC, I use 0.190 which gets it in the ballpark,
>> but can randomly jump +16ms to -
ourth NMEA sentence. Soldering
everything together snapped everything together.
Erik.
> Date: Thu, 24 Jan 2008 10:23:18 -0500
> From: [EMAIL PROTECTED]
> To: questions@lists.ntp.org
> Subject: [ntp:questions] First attempt GPSD/PPS ->NTP time server
>
> All,
>
>
"Dennis Hilberg, Jr." <[EMAIL PROTECTED]> writes:
>Jason wrote:
>> All,
>I could be wrong here, but it seems to me that your ntpd is having a hard
>time finding out the actual time, as your only source of time is nearly 2
>seconds off and varies wildly (GPS time does that, although not usually
David J Taylor schreef:
> The fact that you have a 0.2s offset suggests you are synching to the
> trailing edge of the PPS signal and not the leading edge.
The NMEA output would be my prime suspect. It is not surprising to have
an offset there. The time in an NMEA sentence doesn't tell you what t
Dennis Hilberg, Jr. wrote:
[]
> The GPS time is not very accurate anyway, and can vary wildly,
> probably depending on the device, so don't expect perfect offsets. On my
> Garmin GPS 18 LVC, I use 0.190 which gets it in the ballpark,
> but can randomly jump +16ms to -10ms at any time.
With a good
Jason wrote:
> All,
>
> This is my first attempt to build an 'accurate' GPS-based time server.
> There is no Internet connectivity, so the GPS (and it's PPS) are the
> only sources of timing data.
>
> I'm using a San Jose Navigation FV-M8 [1]. As a GPS, it works great. I
> piped the PPS signal
All,
This is my first attempt to build an 'accurate' GPS-based time server.
There is no Internet connectivity, so the GPS (and it's PPS) are the
only sources of timing data.
I'm using a San Jose Navigation FV-M8 [1]. As a GPS, it works great. I
piped the PPS signal to the CTS line (gpsd-2.36 su
21 matches
Mail list logo
