Topics

GPS Puck for time


Greg Engle
 

I’ve done the archive search and the solutions provided don’t seems to be working.

 

Pi 4 with the latest IOS

 

Using Jason’s, KM4ACK’s directions, no luck

Using OH8STN’s directions, no luck

 

The only difference is I identified the puck in /dev as ttyusb0 and made the appropriate changed in the /etc/default/gpsd

 

I’m thinking there is some subtle difference in the Pi 4 and 3+ that might be the difference but I’m at a loss since this is my first Pi

 

Ideas??

 

Thanks,

Greg

NZ6E


David Ranch
 


I have a guide for getting this working as well.  Follow the setup / troubleshooting steps and tell us where things break:

   http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi4-setup.html#34.usb-gps

--David
KI6ZHD


On 09/20/2020 08:23 AM, Greg Engle wrote:

I’ve done the archive search and the solutions provided don’t seems to be working.

 

Pi 4 with the latest IOS

 

Using Jason’s, KM4ACK’s directions, no luck

Using OH8STN’s directions, no luck

 

The only difference is I identified the puck in /dev as ttyusb0 and made the appropriate changed in the /etc/default/gpsd

 

I’m thinking there is some subtle difference in the Pi 4 and 3+ that might be the difference but I’m at a loss since this is my first Pi

 

Ideas??

 

Thanks,

Greg

NZ6E



Greg Engle
 

I think I see this issue.

 

Your example for the NMEA data

Example bottom NMEA streaming data

      --

      (40) $GPGSV,3,3,10,15,03,041,,16,00,236,*7A\x0d\x0a

      (72) $GPRMC,224315.000,A,3720.6148,N,12159.9942,W,0.00,167.23,141016,,,A*78\x0d\x0a

      (77) $GPGGA,224316.000,3720.6148,N,12159.9942,W,1,05,1.9,26.2,M,-25.7,M,,0000*5D\x0d\x0a

      (49) $GPGSA,A,3,10,32,27,21,18,,,,,,,,6.6,1.9,6.3*30\x0d\x0a

      (72) $GPRMC,224316.000,A,3720.6148,N,12159.9942,W,0.00,167.23,141016,,,A*7B\x0d\x0a

      (77) $GPGGA,224317.000,3720.6148,N,12159.9942,W,1,05,1.9,26.2,M,-25.7,M,,0000*5C\x0d\x0a

      (49) $GPGSA,A,3,10,32,27,21,18,,,,,,,,6.6,1.9,6.3*30\x0d\x0a

      (72) $GPRMC,224317.000,A,3720.6148,N,12159.9942,W,0.00,167.23,141016,,,A*7A\x0d\x0a

      (77) $GPGGA,224318.000,3720.6148,N,12159.9942,W,1,05,1.9,26.2,M,-25.7,M,,0000*53\x0d\x0a

      (49) $GPGSA,A,3,10,32,27,21,18,,,,,,,,6.6,1.9,6.3*30\x0d\x0a

(I don’t have mail on the Pi)

 

I’m seeing UNK and a bunch of hex streaming, line by line

Pretty sure my GPS isn’t streaming NMEA strings.

 

Greg

NZ6e

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of David Ranch
Sent: Sunday, September 20, 2020 1:30 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] GPS Puck for time

 


I have a guide for getting this working as well.  Follow the setup / troubleshooting steps and tell us where things break:

   http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi4-setup.html#34.usb-gps

--David
KI6ZHD

On 09/20/2020 08:23 AM, Greg Engle wrote:

I’ve done the archive search and the solutions provided don’t seems to be working.

 

Pi 4 with the latest IOS

 

Using Jason’s, KM4ACK’s directions, no luck

Using OH8STN’s directions, no luck

 

The only difference is I identified the puck in /dev as ttyusb0 and made the appropriate changed in the /etc/default/gpsd

 

I’m thinking there is some subtle difference in the Pi 4 and 3+ that might be the difference but I’m at a loss since this is my first Pi

 

Ideas??

 

Thanks,

Greg

NZ6E

 


Greg Engle
 

Ok, fixed… SirfDemo and set to NMEA string from SiRF string

 

When running xgps I get an error Couldn’t find foreign struct converter for ‘cairo.Context’

 

Time to load python-gi-cairo ?

 

Greg

NZ6E

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of David Ranch
Sent: Sunday, September 20, 2020 1:30 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] GPS Puck for time

 


I have a guide for getting this working as well.  Follow the setup / troubleshooting steps and tell us where things break:

   http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi4-setup.html#34.usb-gps

--David
KI6ZHD

On 09/20/2020 08:23 AM, Greg Engle wrote:

I’ve done the archive search and the solutions provided don’t seems to be working.

 

Pi 4 with the latest IOS

 

Using Jason’s, KM4ACK’s directions, no luck

Using OH8STN’s directions, no luck

 

The only difference is I identified the puck in /dev as ttyusb0 and made the appropriate changed in the /etc/default/gpsd

 

I’m thinking there is some subtle difference in the Pi 4 and 3+ that might be the difference but I’m at a loss since this is my first Pi

 

Ideas??

 

Thanks,

Greg

NZ6E

 


Mark Griffith
 

Greg,

This is pretty easy as long as the GPS device adheres to the NEMA standard, which all are supposed to do.  Some don't.

Since you know the name, set the serial port speed with "sudo stty -F /dev/ttyUSB0 ispeed 4800".  This sets the serial port to 4800 baud which the NEMA standard calls for.  Again, not all will support this.

One you do that, look at the data stream with "sudo cat < /dev/ttyUSB0".  You should see a stream of hex characters.  To decode them: "cat < /dev/ttyUSB0 | gpsdecode"

If you don't have gpsdecode, install it with "sudo apt-get -y install gpsd gpsd-clients python-gps"

Running that command with gpsdecode you should see text characters with the GPS data.

From there you can decide what to so with it.  gpsd is supposed to set the system clock, but I don't use it, rather I parse the time from the data stream and set the clock.  You only need to set it once when the system boots, after that it keeps good time.  However, if you want to use the Pi for FT8, that may not be good enough.  I would get an RTC in that case.

For a nice view on what is going on, use gpsmon.  To learn about that "man gpsmon".  You don't need gpsd running to use it.

Lots of info is available on the Internet.  Good luck!

Mark
KD0QYN



On Sunday, September 20, 2020, 10:40:21 AM CDT, Greg Engle <gfe@...> wrote:


I’ve done the archive search and the solutions provided don’t seems to be working.

 

Pi 4 with the latest IOS

 

Using Jason’s, KM4ACK’s directions, no luck

Using OH8STN’s directions, no luck

 

The only difference is I identified the puck in /dev as ttyusb0 and made the appropriate changed in the /etc/default/gpsd

 

I’m thinking there is some subtle difference in the Pi 4 and 3+ that might be the difference but I’m at a loss since this is my first Pi

 

Ideas??

 

Thanks,

Greg

NZ6E


Greg Engle
 

The GPS is working and I'm decoding WSJT-X FT8. Issue was the GPS wasn't outputting NMEA. Easy fix with a utility (SiRFDemo)
But now I can't transmit.
The radio keys but the SignaLink isn't going into TX. Since the audio is coming from the SignLink and decoding, it's 1/2 right.
Since I'm at a decent point to backup, I'm doing that!
More trouble shooting!

Greg
NZ6E


Don Melcher
 

Hey Greg - still got that 1.2 slug???
--
Don Melcher
W6CZ


Greg Engle
 

yup
Somewhere :-)


Greg Engle
 

Thanks David. The troubleshooting section is what got it done for me.
Once I got the GPS working I used
G4WNC's site
This has a fix for the xgps not displaying properly.
Plus some of David's tweaks

Rpi and WSJT-X FT8 working 100% now.

73,
Greg
NZ6E


Bill AA6BD
 

The problem I ran into is that gpsd changes the mode of the GPS I use, BU353S4, so that it sends binary rather than NEMA.  This can be reversed and gpsd can be told to not change the mode.  I documented how to do this in the YAAC-users forum at https://groups.io/g/yaac-users/message/544

--
Bill AA6BD