¿ªÔÆÌåÓý

Re: Repeating "GPSD: Location fix is now 2D/3D"


 

Hi Fred,

Both my Ublox devices - LEA4 (IIRC) and a considerably newer M8 - have 1PPS so yours likely does too. The Garmin I dabbled with was the 18-5Hz with sentences sent five times per second for better positional accuracy but its PPS seemed to not play nicely with gpsd. Either that or I wasn't smart enough to make it happen! I cut my losses and bought the M8 board for the RPi4 for my Stratum 1 network time server.

Take care

Regards
Ray vk2tv

On 7/10/21 3:33 am, Fred Hillhouse wrote:
Hi Ray,

Thanks for the link. I think my networked GPS (u-blox) has 1PPS. I haven't really checked it out. The Garmin GLO2 doesn¡¯t have the capabilities. At least, that is what I gather from ppscheck. This project doesn't need it and hopefully the JS8CALL project doesn't either.

Fred N7FMH

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Ray Wells
Sent: Friday, October 01, 2021 8:55 PM
To: [email protected]
Subject: Re: [direwolf] Repeating "GPSD: Location fix is now 2D/3D"

Fred,

I know you've done the hard yards and it's working for you but you may
still find this page about gpsd interesting.


FWIW I ran into the same 2D/3D problem as you but I can't remember which
(RS232) GPS (Garmin 18 series or older Ublox) I used at the time. I
ended up compiling GPSD from sources to get an updated version. But this
was near enough to two years ago.

Ray vk2tv

On 2/10/21 9:18 am, Fred Hillhouse wrote:
Hi David,



Thanks for the update and how strange if this was a gpsd thing. What
version were you running before?

Version 3.17

Gary¡¯s comment: Wow, that is 4 years old. You need to update that.
3.23.1 is current.

I am not sure but came from the apt repository. I didn¡¯t install gpsd
initially on this RPI. I wouldn¡¯t have done a build from source.

Do you know what was the specific fix in the newer GPSD that resolved
your problem?

Sorry I don¡¯t.

Best regards,

Fred N7FMH

--David
KI6ZHD

On 10/01/2021 02:30 PM, Fred Hillhouse wrote:

Problem has been resolved. I now get a solid 3D fix.

The solution: update to the latest revision of GPSD. Revision 3.23.1

As background, I have a Garmin GLO 2 which will support up to four
users. A similar unit is the Dual XGPS160. I have used it in the
past for an Android tablet with the hopes of also sharing with an
RPi. Currently, The tablet, RPI and my PC are receiving data.

I was asked why I would use a GPS like this. When running multiple
RPIs, which may not have sky view, a GPS with a view can share
with each.

Best regards,

Fred N7FMH

*From:*[email protected] <mailto:[email protected]>
[mailto:[email protected] <mailto:[email protected]>] *On Behalf
Of *Fred Hillhouse
*Sent:* Wednesday, September 29, 2021 5:06 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [direwolf] Repeating "GPSD: Location fix is now 2D/3D"

GPS has been running for at least a day.


Define "GPS has been running for at least a day". By default,
your GPS puck won't be activated by gpsd and start listening for
GPS details until it has a listening client like direwolf, cgps,
gpsmon, etc. This seems to be a default for minimizing power
consumption. The gpsmon tool doens't show how long it's been
running with a 3D fix but cgps does.

The GPS has had a device connected to a device. It supports 4
different devices. One device is the same RPi Direwolf is running
on but is an terminal window on my PC with /cgps /running. Now a
second device (PC/u-center) is connected.

What constitutes a ¡°very good¡± lock?


That's evidently a huge topic in itself and is well outside the
scope of this Direwolf. I did a search for "gpsd 3d lock" and
this hit seems like a good start:


<>

A key point in that article is that though your system lists it's
using X satellites, it doesn't mean it's hearing them well. This
can be due to local RF interference, etc.

I can see I have a 3D position all the time now that my Windows PC
is connected. I am aware of the FIX differences and how everything
can affect the satellite signal; trees buildings, angle of
antenna, etc. Not being snarky! If this was a serial GPS or a
USB-GPS (serial?) there would be no BT layer and for serial, using
/dev/ttyS0 would be correct and USB would be similar. Based on an
exchange with Robert KB8RCO it seems this maybe the case here. If
may be that each of the four possibilities need /dev/ttys0-3? In
the end, I will have learned a little more.

This is what I get when running /gpsmon/. Any clues there?


More information is available in cgps but there are other tools
available to troubleshoot GPS issues such as gpsprof but I've
never used them. Ultimately, I don't think your issue is with
Direwolf.. it's going to be somewhere in the GPS into GPSD area.
I would start here:
<>

I will certainly check this group. From my PC experience on
needing to actually connect to a COM port, I wonder if a RPi
¡°comport¡± must be connected as well. Robert, KB8RCO, suggested
something regarding auto-connecting at reboot but I haven¡¯t chased
that since the basic connection is not functional yet.

Thank you!

Fred N7FMH


Screenshots from the u-blox u-center app:

------------------------------------------------------------------------

Avast logo <>



This email has been checked for viruses by Avast antivirus software.
www.avast.com <>










--
This email has been checked for viruses by Avast antivirus software.





Join [email protected] to automatically receive all group messages.