On 11/02/2013 23:56, unruh wrote:
[]
You are always at the mercy of the receiver.
And it is not the fix time. ZDA puts out only to the nearest 10 ms. the
others to the nearest second or 10ths of a second. Fix
times are in the nanosecond realm. They put out times which are the time
label of the
On 2/11/13 6:48 PM, unruh wrote:
[Followup-To: header set to comp.protocols.time.ntp.]
why do that?
hey guys, fix the Newsgroup: header here.
On 2/11/13 6:48 PM, unruh wrote:
...
Yes. However what you can do is to filter out the all but the strongest
harmonic, and count which harmonic
unruh un...@invalid.ca wrote:
You are obviously wrong here. The messages that provide position data
do not include the current time, they include the time of fix.
None, not even ZDA put out current time. They all put out time in the
past. It takes a long time for any of the messages to be
On 12/02/2013 09:54, Rob wrote:
[]
You are describing implementation details in some particular receiver.
Why not read the actual specs of the protocol instead?
[]
Do you have the URL of the official $GPZDA protocol, please? Is it any
more than the receiver's best guess, given that there is
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 12/02/2013 09:54, Rob wrote:
[]
You are describing implementation details in some particular receiver.
Why not read the actual specs of the protocol instead?
[]
Do you have the URL of the official $GPZDA protocol, please? Is it
None, not even ZDA put out current time. They all put out time in the
past. It takes a long time for any of the messages to be composed in
the
receiver, to be queued, to be sent at 300-9000 bits per second, and to
be interpreted.
It is easy to change most GPS receivers to send NMEA
Here:
http://www.sparkfun.com/datasheets/GPS/NMEA%20Reference%20Manual-Rev2.1-Dec0
7.pdf
Or here: http://www.ekf.de/c/cgps/cg2/inf/nmea_reference_manual.pdf
SiRF Proprietary Binary Protocol Manual:
http://www.usglobalsat.com/downloads/SiRF_Binary_Protocol.pdf
Or search on (SiRF) NMEA
robert bristow-johnson wrote:
On 2/11/13 6:48 PM, unruh wrote:
[Followup-To: header set to comp.protocols.time.ntp.]
why do that?
hey guys, fix the Newsgroup: header here.
On 2/11/13 6:48 PM, unruh wrote:
...
Yes. However what you can do is to filter out the all but the strongest
james machado hvgeekwt...@gmail.com wrote:
you should not need to load the ktimer module to get your PPS working.
That is the debug module and fakes PPS to the kernel. Verify that
the kernel you installed was an uncompressed kernel. Did you compile
it yourself or did you get it off the net?
Does this look sane to you for a Raspberry Pi with a
Sure Electronics board and PPS enabled? It looks fine to me,
I just want to confirm that people more experienced than me
see it the same way.
remote refid st t when poll reach delay offset jitter
Ralph,
On Tue, Feb 12, 2013 at 6:04 AM, Ralph Aichinger ra...@pangea.at wrote:
Does this look sane to you for a Raspberry Pi with a
Sure Electronics board and PPS enabled? It looks fine to me,
I just want to confirm that people more experienced than me
see it the same way.
remote
On 2013-02-12, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 11/02/2013 23:56, unruh wrote:
[]
You are always at the mercy of the receiver.
And it is not the fix time. ZDA puts out only to the nearest 10 ms. the
others to the nearest second or 10ths of a second. Fix
times are
On 2013-02-12, james machado hvgeekwt...@gmail.com wrote:
On Tue, Feb 12, 2013 at 6:04 AM, Ralph Aichinger ra...@pangea.at
wrote:
Does this look sane to you for a Raspberry Pi with a Sure Electronics
board and PPS enabled? It looks fine to me, I just want to confirm
that people more
james machado hvgeekwt...@gmail.com wrote:
I would expect to see a PPS line if you have PPS up and working
correctly, this is what I see on my RPi.
I am using the built-in PPS support of the NMEA driver (flag1).
associd=0 status=0115 leap_none, sync_pps, 1 event, clock_sync,
version=ntpd
Steve Kostecke koste...@ntp.org wrote:
you that your GPS is the PPS peer. Plus the offset and jitter are
appropriate for a PPS ref-clock.
Thanks that helps a lot. The tally codes are well documented, of course,
but I was not quite sure if the offsets against known working
NTP servers were
On Tue, Feb 12, 2013 at 11:03 AM, Ralph Aichinger ra...@pangea.at wrote:
snip
You use the driver 20 (NMEA) without PPS (flag1 0) I (hopefully)
use it with (flag1 1).
and i learn something new - thanks :)
Thanks! The values from your setup are very helpful, as they
are quite close to
16 matches
Mail list logo
