Raspberry Pi GPS Stratum 1 NTP Server

[Tobi2707]

forgot to stop ntp, but after stopping same error..

running gpsstatus opens new windows, like "gpsmon" and this in the console:

Code: Select all

pi@raspberrypi ~ $ gpsstatus /dev/ttyAMA0
Traceback (most recent call last):
  File "/usr/local/bin/gpsstatus", line 577, in <module>
    rc = curses.wrapper(main)
  File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper
    return func(stdscr, *args, **kwds)
  File "/usr/local/bin/gpsstatus", line 571, in main
    input_loop(fg)
  File "/usr/local/bin/gpsstatus", line 437, in input_loop
    time.sleep(0.250)
KeyboardInterrupt

[Tobi2707]

ah wait, now i get this:

Code: Select all

pi@raspberrypi ~ $ gpsinit -s 115200 -f /etc/gpsinit_nav.conf /dev/ttyAMA0
Making sure the unit is in NMEA mode
Making sure the speeds match
GPS and port are now synchronized at 115200
Processing commands...
PMTK301,2
Failed to get ACK.
PMTK313,1
Failed to get ACK.
PMTK314,1,1,1,1,1,5,1,1,1,1,1,0,0,0,0,0,0,1,0
Failed to get ACK.
PMTK319,1
Failed to get ACK.
PMTK225,0
Failed to get ACK.
PMTK286,1
Failed to get ACK.
PMTK386,0.50
Failed to get ACK.
PMTK869,1,1
Failed to get ACK.
PMTK220,1000
Failed to get ACK.
Done
pi@raspberrypi ~ $ 

[gtj]

Strange. I wonder if it's something with the older Pis?

Try this... Power down the Pi and remove the battery from the hat for a minute to reset it, then try again.

[Tobi2707]

Is the second output not right?
with the done at the end?

[gtj]

Failed to get ack means the command was sent to the gps but it didn't reply. It may have worked however. The only way to tell is to get the gpsstatus working and I don't understand why it isn't.

[Tobi2707]

is gpsstatus not working? what should happen?
So i removed the battery for a minute an now?

[Tobi2707]

This after rebooting:

Code: Select all

pi@raspberrypi ~ $ gpsinit -s 115200 -f /etc/gpsinit_nav.conf /dev/ttyAMA0
Making sure the unit is in NMEA mode
Making sure the speeds match
The GPS speed and the port speed couldn't be synchronized.
Retrying
Making sure the speeds match
The GPS speed and the port speed couldn't be synchronized.
pi@raspberrypi ~ $ sudo service ntp stop
[ ok ] Stopping NTP server: ntpd.
pi@raspberrypi ~ $ gpsinit -s 115200 -f /etc/gpsinit_nav.conf /dev/ttyAMA0
Making sure the unit is in NMEA mode
Making sure the speeds match
The GPS speed and the port speed couldn't be synchronized.
Retrying
Making sure the speeds match
GPS and port are now synchronized at 115200
Processing commands...
PMTK301,2
Failed to get ACK.
PMTK313,1
Failed to get ACK.
PMTK314,1,1,1,1,1,5,1,1,1,1,1,0,0,0,0,0,0,1,0
PMTK319,1
Failed to get ACK.
PMTK225,0
PMTK286,1
Failed to get ACK.
PMTK386,0.50
Failed to get ACK.
PMTK869,1,1
PMTK220,1000
Done

What's with this?

[gtj]

Looks like some of the commands are working and some aren't.

I wonder if the hat is making intermittent connection to the Pi? You might want to double check that the pins are all soldered correctly, particularly the TXD and RXD pins. Maybe re-solder them just to make sure. Then re-seat the hat on the Pi.

[Tobi2707]

i don't have something to solder hat home, it's at work... would gaps work if the connections were not right?
when i run gpsstatus is see a black window with my time and my coordinates..and see satellites, my device and the nmea sentences...
what if we just go on and see if it's working? with the next command?

What's the command the set the gps module and the RPi back to factory state?

If nothing doesn't help, i get the RPi 2 within the next week, I'm waiting for 2 weeks for it:D

[gtj]

Yeah, if gpsstatus is working, keep going.

To reset to factory state use "gpssend PMTK104 /dev/ttyAMA0" PMTK104 is the GPS command to reset to factory state.

[Tobi2707]

Now after the second command i get this:

Code: Select all

pi@raspberrypi ~ $ gpsinit -s 115200 -f /etc/gpsinit_time.conf /dev/ttyAMA0
Making sure the unit is in NMEA mode
Making sure the speeds match
The GPS speed and the port speed couldn't be synchronized.
Retrying
Making sure the speeds match
GPS and port are now synchronized at 115200
Processing commands...
PMTK314,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0
PMTK220,1000
Done

Is this right? What's after?

Is there any difference to:

Code: Select all

./gpsinit -s 9600 -i factory_reset /dev/ttyAMA0

[gtj]

YES!!

You should now be able to start ntp and watch with 'ntpq -pn'

There's no real between the 2 commands, gpssend just sends the one command while gpsinit -i factory_reset also does the baud rate changes. gpsinit is probably better.

[Tobi2707]

before the

Code: Select all

sudo update-rc.d nt. defaults

?
what is this for?
and then start ntp and then ntpq -pnß

[gtj]

before the

Code: Select all

sudo update-rc.d nt. defaults

?
what is this for?
and then start ntp and then ntpq -pnß

That just insures that ntp is started when the system boots.
Yep, go for it.

[Tobi2707]

The Output is:

Code: Select all

pi@raspberrypi ~ $ sudo update-rc.d ntp defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match ntp Default-Stop values (none)
pi@raspberrypi ~ $ sudo service ntp start
[ ok ] Starting NTP server: ntpd.
pi@raspberrypi ~ $ sudo ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 127.127.20.0    .GPS0.           1 l   6h    8    0    0.000    0.000   0.004
 129.70.132.37   129.70.130.70    2 u    1   64    1   28.380    1.400   0.092
pi@raspberrypi ~ $ sudo ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*127.127.20.0    .GPS0.           1 l    5    8    1    0.000    0.016   0.004
 129.70.132.37   129.70.130.70    2 u    1   64    1   28.280    1.060   0.244

What do you mean?:)