Hello Ana,
which version of Garmin 35 do You have? I had PC version, but it didn't
have PPS at all. And I'm not sure if its better in other versions of 35.
Now I'm using 18LVC and works perfectly.
Best regards,
Radovan Mzik
On Thu, 18 Jan 2007, Ana Hernandez wrote:
Hi,
I use Debian 3.0, the kernel is 2.4.27 i686. I use pps-clock 2-2 to
catching PPS signal and synchronize the node with ntp-4.1.0-8.
Besides the node have a DAG card 3.6GE that catching PPS signal too, and
this card have a tool called dagpps that get information about the
length of the pulse, for example for a good node I get:
on 959616, off 9040384
Positive pulse, cabling is correct.
Pulse length about 95962 microseconds
but in this case I get
on 6, off 9999994
Positive pulse, cabling is correct.
Pulse length about 1 microseconds.
I do not know other way to check pps signal.
The DAG card received the PPS singnal, but seem that it is short. I have
tried to lengthen the signal of GPS but I do not get it. The GPS is
garmin 35
Ana
El mar, 16-01-2007 a las 16:12 +0100, Tim Lundström escribió:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi again,
I took a closer look at your mail and then I saw that you are using
127.127.28.0 as refclock. If I remember correctly 127.127.28.0 referes
to the NMEA output of gpsd. The PPS pulse is 127.127.28.1. Are you sure
that gpsd is reading your GPS as all? It can be checked by the programs
distributed along with gpsd such as xgps.
/Tim
Tim Lundström wrote:
Hi,
Could you please tell us a little about your hardware? What software are
you using for catching the PPS signal? What is your configuration?
- From your information I can't tell what's wrong. Are you sure you are
recieving PPS signals? Are you sure you are recieving them on the right
pin? Are you sure the GPS is sending PPS signals? The GPS needs a good
fix before sending PPS.
/Tim
Ana Hernandez wrote:
Hi Rob,
I read your mail, and I have a problem about you said, I have a node
with a GPS Garmin, the signal of pps that I receive is very short, so I
can not to synchronize the node.
remote refid st t when poll reach delay offset
jitter
==============================================================================
127.127.28.0 .SHM. 0 l - 64 0 0.000 0.000
4000.00
+193.224.70.7 195.111.99.186 2 u 300 512 377 25.619 1.349
0.087
*130.206.169.218 .SHM. 1 u 239 512 377 40.112 1.271
0.085
The pulses are too short for transmission via RS232. I try to lengthen
them,
/bin/echo -ne "\n\$PGRMC,,$ALTITUDE,,,,,,,,3,,2,48,\n\n" > $GPSDEVICE
but I can not get to lengthen the pulses, you think that is posible the problem
is in the wire?
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFrOtU/V2VyZDycRcRAq6hAKDDrauBB5I+c8ahB7YDTM4bE04PHACguYbC
1RNUwVfv68eghi4HTNhBBgQ=
=iDRR
-----END PGP SIGNATURE-----
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
--
Radovan MZIK
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 603 106 630
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: [EMAIL PROTECTED]
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
