¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

GPS INOP since BAP 3 #gps


 

Quickly, my? that I've had since June 2019 essentially stopped working after FINALLY upgrading to BAP 3 last year. I've run the below many times with no success.
-----------
sudo apt-get purge gpsd gpsd-clients python-gps chrony python-gi-cairo
cd ~/Downloads
wget
sudo bash gpsinstall
-----------
Both of the below are active
systemctl is-active gpsd
systemctl is-active chronyd
The result of "ls /dev/serial/by-id/" is:
usb-u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver-if00
The result of "ls -al /dev/ttyUSB* /dev/ttyACM*" is the expected "ttyACM0"
crw-rw---- 1 root dialout 166, 0 Feb? 2 22:35 /dev/ttyACM0
In?/etc/default/gpsd I've made sure:
USBAUTO="false" and
GPSD_OPTIONS="-n -b"
I've walked through the GPS install of OH8STN, dl1gkk, and KM4ACK's for any errors or suggestions but am at loss.
The Raspi definitely "sees" the UBLOX receiver every single time I reboot, but for whatever reason cgps, xgps, or gpsmon comes up with nothing.
With "chronyc sources -v"
the last line is:
"NMEA? ? ? ? ? ? ? ? ? ? ? ? ? 0? ?4? ?377? ? 21? ?+373us[ +571us] +/-? 100ms"?
Could it be the GPS Chipset "U-blox 8 Engine" isn't registering as well as the 7020? Maybe I should buy a cheap GPS and see if it works.
Of course the GPS is in a window and I've made changes and waited up to 12 hours for anything to change. Prior to BAP 3, it would lock within a minute or two.
Thanks for any help!
73
Troy
DA1SNL/KN4SNL


Dave - N9QNZ
 

The first step is to take it all outside to confirm you can get a satellite lock.

On Tue, Feb 2, 2021 at 5:35 PM Troy Morken via <tmorken=[email protected]> wrote:
Quickly, my? that I've had since June 2019 essentially stopped working after FINALLY upgrading to BAP 3 last year. I've run the below many times with no success.
-----------
sudo apt-get purge gpsd gpsd-clients python-gps chrony python-gi-cairo
cd ~/Downloads
wget
sudo bash gpsinstall
-----------
Both of the below are active
systemctl is-active gpsd
systemctl is-active chronyd
The result of "ls /dev/serial/by-id/" is:
usb-u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver-if00
The result of "ls -al /dev/ttyUSB* /dev/ttyACM*" is the expected "ttyACM0"
crw-rw---- 1 root dialout 166, 0 Feb? 2 22:35 /dev/ttyACM0
In?/etc/default/gpsd I've made sure:
USBAUTO="false" and
GPSD_OPTIONS="-n -b"
I've walked through the GPS install of OH8STN, dl1gkk, and KM4ACK's for any errors or suggestions but am at loss.
The Raspi definitely "sees" the UBLOX receiver every single time I reboot, but for whatever reason cgps, xgps, or gpsmon comes up with nothing.
With "chronyc sources -v"
the last line is:
"NMEA? ? ? ? ? ? ? ? ? ? ? ? ? 0? ?4? ?377? ? 21? ?+373us[ +571us] +/-? 100ms"?
Could it be the GPS Chipset "U-blox 8 Engine" isn't registering as well as the 7020? Maybe I should buy a cheap GPS and see if it works.
Of course the GPS is in a window and I've made changes and waited up to 12 hours for anything to change. Prior to BAP 3, it would lock within a minute or two.
Thanks for any help!
73
Troy
DA1SNL/KN4SNL


 

Just a thought, but can you install an SDCard or USB stick with just a Raspberry Pi OS, then run through the GPS setup forom here:

Does it work outside BAP?


Dave - N9QNZ
 

Yes, what that link describes is the preferred (IMO) first step in GPS troubleshooting.? Namely, are you able to get NMEA sentences on the serial port from the GPS?? If so, do the NMEA sentences show position data?

BAP has NOTHING to do with "getting a lock" and as they say: "correlation does not imply causation".


On Tue, Feb 2, 2021 at 6:38 PM Kevin <kd9efv@...> wrote:
Just a thought, but can you install an SDCard or USB stick with just a Raspberry Pi OS, then run through the GPS setup forom here:

Does it work outside BAP?


 

Is conkY running? If no, then watch this video from Jason KM4ACK , it solved my gpa & conky ?issue.?


 

The GPS has worked in the past, but I'll try it again on my old Window 7 laptop. Also thanks for the good idea try to run a different SDCard. Received a card last week with NOOBS preloaded and haven't swiped it for something useful yet.


 

Good question about Conky, thanks Dean.
Conky works when I either 1) disconnect the GPS or 2) comment out the GPS lines in conky.conf :-) neither ideal, but does let Conky run so I can see my last few QSOs.
The steps in the video haven't helped. I've removed gpsd and chrony and reinstalled the latest. I think gpsd is on 3.17-7 if memory serves.


 

Yes, Dave, good copy regarding correlation. The results of "gpsmon /dev/ttyUSB0" is that it's being used by another resource. Running gpsmon alone draws a completely blank / black terminal window. It seems odd (read: also slightly frustrating) that the device can be recognized as Ublox GPS but run into a critical error that crashes M0IAX tools, Conky, and other apps trying to retrieve GPS data.

Thanks all for the help so far. More testing needed.


 

Confirmed-->GPS works on that NOOBS SDCard I got last week... guess it turned out to be more useful than expected :-)
I simply ran the below commands on a relatively fresh install. Of note I unplugged the USB from one PI and plugged it into the other. Therefore, the GPS should work with the BAP install right where it is.
Thanks again to everyone giving feedback!
------------------------
sudo apt-get purge gpsd gpsd-clients python-gps chrony python-gi-cairo
cd ~/Downloads
wget?
sudo bash gpsinstall
------------------------


 

Did you swap with power on or off? GPS are not hot swap-able for the gpsd.


 

FIXED... Maybe? Workaround will do! Here's what just worked with my BAP currently connected to transceiver and GPS.
1. Start Raspi with GPS plugged in (as normal, like Kevin states, it's not hot swap-able)
2. Open Terminal, stop and disable gpsd
sudo systemctl?stop?gpsd.socket
sudo systemctl?disable?gpsd.socket
3. Verify gpsd is not active, aka "failed"
systemctl is-active gpsd
4. Restart and enable gpsd
sudo systemctl?enable?gpsd.socket
sudo systemctl?
start?gpsd.socket
5. Verify gpsd is active
systemctl is-active gpsd
Conky displayed correctly, M0IAX JS8 Call Tools works now. The workaround is tolerable.
Next step might be to delay start of gpsd to see if that could fix it.
Thank you again everyone!


 

BTW, to save typing, you could create a bash script with those commands in it (with a sleep2 between each command)
call it /home/pi/gpsd.sh
and a sleep 10 or sleep 15 at the beginning.
Run the script as part of a cron
sudo crontab -e
add this at the end:
@reboot /home/pi/gpsd.sh

I do similar things with other devices...


 

I just did this.

pi@raspberrypi:~ $ sudo systemctl stop gpsd.socket
pi@raspberrypi:~ $ sudo systemctl disable gpsd.socket
Removed /etc/systemd/system/sockets.target.wants/gpsd.socket.
pi@raspberrypi:~ $ systemctl is-active gpsd
inactive
pi@raspberrypi:~ $ sudo systemctl enable gpsd.socket
Created symlink /etc/systemd/system/sockets.target.wants/gpsd.socket ¡ú /lib/systemd/system/gpsd.socket.
pi@raspberrypi:~ $ sudo systemctl start gpsd.socket
pi@raspberrypi:~ $ systemctl is-active gpsd
inactive
pi@raspberrypi:~ $


I see my GPS is red and not flashing.

73

Don va7dgp
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU ? VOICE


Winlink: va7qu@...
Subject://wl2k ? ? ? ? ??

ALLSTAR? 530780
HH# 5971
HH# 11384
? ? ? ? ? ? ? ? ? ??
??




?


On Wed, Feb 3, 2021 at 12:56 PM Troy KN4SNL via <tmorken=[email protected]> wrote:
FIXED... Maybe? Workaround will do! Here's what just worked with my BAP currently connected to transceiver and GPS.
1. Start Raspi with GPS plugged in (as normal, like Kevin states, it's not hot swap-able)
2. Open Terminal, stop and disable gpsd
sudo systemctl?stop?gpsd.socket
sudo systemctl?disable?gpsd.socket
3. Verify gpsd is not active, aka "failed"
systemctl is-active gpsd
4. Restart and enable gpsd
sudo systemctl?enable?gpsd.socket
sudo systemctl?
start?gpsd.socket
5. Verify gpsd is active
systemctl is-active gpsd
Conky displayed correctly, M0IAX JS8 Call Tools works now. The workaround is tolerable.
Next step might be to delay start of gpsd to see if that could fix it.
Thank you again everyone!


 

Anyone else having issues running with their system clock not syncing over GPS? This has been a problem with field ops when my system clock is not sync'd using JS8CALL & other modes.?

(1) I've tried restarting gpsd service.
(2) Purging gpsd & re-installing.
(3) Used BAP for initial install & re-install.
(4) Used the steps in this thread to no avail
(5) cgps shows current time / position
(6) XGPS is accurate
(7) YAAC & XASTIR move me around the map while driving.?


 

Here are the instructions I wrote up to be able to use NMEA strings to set time.
There are a few options mentioned but not in the instructions,like NTP server for network,
GPS Grid Square sharing, etc, that I can write up / post if needed / wanted. This was a
project I did when I didn't have any Internet network capability for field work.


 

Thank you very much!!! Just tested it and watched it update the system as soon as it got the GPS signal.?

For me: line 12 needed to be: sudo nano /etc/default/gpsd




 

I blame lack of caffeine, phase of the moon, and local air temperature.
Thank you for the catch, corrected in attached.