How to get accurate localization with Firefox or others when using a map with a PC using an ethernet cable

promeneur · November 23, 2023, 11:04am

I read many docs. There is nothing to do according to get a location from a gnss dongle.
Just install gpsd, plug in the dongle and that’s all.

I wonder if the inside location of the dongle is the problem.

Inside my home perhaps the gnss signal is too weak.

Or perhaps I must wait for an update, from the satellites, of the data used to compute a location.

dcurtisfra · November 23, 2023, 2:17pm

Yes, often – GPS requires that, at least 4 satellites are “visible” for accurate calculation of your position.

And, as everyone who has a vehicle with a navigation system knows – when you first activate the system, you have to wait at least 10 to 15 minutes before enough satellites have “flown” over your location to provide an accurate enough initial position …

promeneur · November 23, 2023, 3:09pm

I keep the Wi-Fi solution. With an accurracy of 20 m, it’s good for all app I use with my PC.

malcolmlewis · November 23, 2023, 3:09pm

@promeneur I don’t use the USB dongles here (as such), I have one on a Raspberry Pi3 for a local time server, it is also inside next to my ADS-B setup.

I did write an SDB about it… https://en.opensuse.org/HCL:Raspberry_Pi3_GPS

But i also connect to the above devices via USB Serial cable…

promeneur · November 23, 2023, 3:28pm

Thanks but i don’t need a time server.

malcolmlewis · November 23, 2023, 3:48pm

@promeneur that doesn’t matter, it’s the setup of gpsd… the time part is the pps output…

So I just plugged another one in here to my Tumbleweed setup and ran (just make sure gpsd service AND socket are stopped);

gpsd -N -G -n -b -D 3 /dev/ttyUSB0

the -D is debug assuming your device it present at ttyUSB0?

All was good after a minute or so…

promeneur · November 23, 2023, 4:06pm

the dongle is at /dev/tty/ACM0

malcolmlewis · November 23, 2023, 4:11pm

@promeneur So if you run gpsd -N -G -n -b -D 3 /dev/ttyACM0 do you start to see output, then as your user run cgps in a terminal, does it start working after awhile, do you see satellites present?

promeneur · November 23, 2023, 4:15pm

:~> sudo gpsd -N -G -n -b -D 3 /dev/ttyACM0
[sudo] Mot de passe de root : 
gpsd:INFO: launching (Version 3.25, revision 3.25)
gpsd:INFO: starting uid 0, gid 0
gpsd:INFO: Command line: gpsd -N -G -n -b -D 3 /dev/ttyACM0 
gpsd:INFO: listening on port gpsd
gpsd:INFO: stashing device /dev/ttyACM0 at slot 0
gpsd:INFO: SER: opening read-only GPS data source type 12 at '/dev/ttyACM0'
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8O1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: KPPS:/dev/ttyACM0 RFC2783 path:/dev/pps0, fd 8
gpsd:INFO: KPPS:/dev/ttyACM0 pps_caps 0x1133
gpsd:INFO: KPPS:/dev/ttyACM0 have PPS_CANWAIT
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS will be used
gpsd:INFO: SHM: ntpshm_link_activate(/dev/ttyACM0): NTP NTP activated 7
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: running with effective group ID 490
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2023-11-23T16:14:24.000Z (1700756064)
gpsd:INFO: CORE: /dev/ttyACM0 identified as type NMEA0183, 1 sec
gpsd:INFO: CORE: /dev/ttyACM0 9600bps
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: PPS:/dev/ttyACM0 unchanged state, ppsmonitor sleeps 10
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GPGSV: Satellite data no good (1 of 1).
gpsd:WARN: NMEA0183: GBGSV: Satellite data no good (1 of 1).

hui · November 23, 2023, 4:22pm

Please provide terminal output in preformatted text tags </> . This makes it easier to read. Additionally to have all your terminal output in english, please prepend commands with LANG=C, e.g.

LANG=C sudo gpsd -N -G -n -b -D 3 /dev/ttyACM0

malcolmlewis · November 23, 2023, 4:38pm

@promeneur leave it running for at least 10 minutes and see what happens…

promeneur · November 23, 2023, 4:59pm

Same thing after 17 mn

malcolmlewis · November 23, 2023, 5:40pm

@promeneur Might have to do some more tweaking with the ublox tool…?

promeneur · November 24, 2023, 6:26am

Some progress but no fix.
I let my PC running this night.
I use “gpsd /dev/ttyACM0”

promeneur · November 24, 2023, 7:18am

this time we get something different.

:~> sudo gpsd -N -G -n -b -D 3 /dev/ttyACM0
gpsd:INFO: launching (Version 3.25, revision 3.25)
gpsd:INFO: starting uid 0, gid 0
gpsd:INFO: Command line: gpsd -N -G -n -b -D 3 /dev/ttyACM0 
gpsd:INFO: listening on port gpsd
gpsd:INFO: stashing device /dev/ttyACM0 at slot 0
gpsd:INFO: SER: opening read-only GPS data source type 12 at '/dev/ttyACM0'
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8O1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: KPPS:/dev/ttyACM0 RFC2783 path:/dev/pps0, fd 8
gpsd:INFO: KPPS:/dev/ttyACM0 pps_caps 0x1133
gpsd:INFO: KPPS:/dev/ttyACM0 have PPS_CANWAIT
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS will be used
gpsd:INFO: SHM: ntpshm_link_activate(/dev/ttyACM0): NTP NTP activated 7
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: running with effective group ID 490
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2023-11-24T07:15:21.000Z (1700810121)
gpsd:INFO: CORE: /dev/ttyACM0 identified as type NMEA0183, 0 sec
gpsd:INFO: CORE: /dev/ttyACM0 9600bps
gpsd:WARN: NMEA0183: TXT: Notice: u-blox AG - www.u-blox.com
gpsd:WARN: NMEA0183: TXT: Notice: HW UBX-M8130 00080000
gpsd:WARN: NMEA0183: TXT: Notice: ROM CORE 3.01 (107888)
gpsd:WARN: NMEA0183: TXT: Notice: FWVER=SPG 3.01
gpsd:WARN: NMEA0183: TXT: Notice: PROTVER=18.00
gpsd:WARN: NMEA0183: TXT: Notice: GPS;GLO;BDS
gpsd:WARN: NMEA0183: TXT: Notice: QZSS
gpsd:WARN: NMEA0183: TXT: Notice: GNSS OTP=GPS;BDS
gpsd:WARN: NMEA0183: TXT: Notice: LLC=FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFD
gpsd:WARN: NMEA0183: TXT: Notice: ANTSUPERV=AC SD PDoS SR
gpsd:WARN: NMEA0183: TXT: Notice: ANTSTATUS=OK
gpsd:WARN: NMEA0183: TXT: Notice: PF=3FF
gpsd:INFO: CORE: /dev/ttyACM0 identified as type u-blox, 1 sec
gpsd:INFO: CORE: /dev/ttyACM0 9600bps
gpsd:INFO: CORE: Sats used (0):
gpsd:INFO: CORE: Sats used (0):
gpsd:INFO: CORE: Sats used (0):
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:INFO: CORE: Sats used (0):
gpsd:INFO: CORE: Sats used (0):
gpsd:INFO: CORE: Sats used (0):

promeneur · November 24, 2023, 7:24am

i installed pps tools then i got this :

:~> sudo gpsd -N -G -n -b -D 3 /dev/ttyACM0
[sudo] Mot de passe de root : 
gpsd:INFO: launching (Version 3.25, revision 3.25)
gpsd:INFO: starting uid 0, gid 0
gpsd:INFO: Command line: gpsd -N -G -n -b -D 3 /dev/ttyACM0 
gpsd:INFO: listening on port gpsd
gpsd:INFO: stashing device /dev/ttyACM0 at slot 0
gpsd:INFO: SER: opening read-only GPS data source type 12 at '/dev/ttyACM0'
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8O1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: SER: fd 7 current speed 9600, 8N1
gpsd:INFO: KPPS:/dev/ttyACM0 RFC2783 path:/dev/pps0, fd 8
gpsd:INFO: KPPS:/dev/ttyACM0 pps_caps 0x1133
gpsd:INFO: KPPS:/dev/ttyACM0 have PPS_CANWAIT
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS will be used
gpsd:INFO: SHM: ntpshm_link_activate(/dev/ttyACM0): NTP NTP activated 7
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Interrupted system call(4)
gpsd:INFO: running with effective group ID 490
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2023-11-24T07:21:47.000Z (1700810507)
gpsd:INFO: CORE: /dev/ttyACM0 identified as type NMEA0183, 0 sec
gpsd:INFO: CORE: /dev/ttyACM0 9600bps
gpsd:WARN: NMEA0183: TXT: Notice: u-blox AG - www.u-blox.com
gpsd:WARN: NMEA0183: TXT: Notice: HW UBX-M8130 00080000
gpsd:WARN: NMEA0183: TXT: Notice: ROM CORE 3.01 (107888)
gpsd:WARN: NMEA0183: TXT: Notice: FWVER=SPG 3.01
gpsd:WARN: NMEA0183: TXT: Notice: PROTVER=18.00
gpsd:WARN: NMEA0183: TXT: Notice: QZSS
gpsd:WARN: NMEA0183: TXT: Notice: GNSS OTP=GPS;BDS
gpsd:WARN: NMEA0183: TXT: Notice: LLC=FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFD
gpsd:WARN: NMEA0183: TXT: Notice: ANTSUPERV=AC SD PDoS SR
gpsd:WARN: NMEA0183: TXT: Notice: ANTSTATUS=OK
gpsd:WARN: NMEA0183: TXT: Notice: PF=3FF
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.
gpsd:INFO: CORE: Sats used (0):
gpsd:WARN: NMEA0183: can't use GLL time until after ZDA or RMC has supplied a year.
gpsd:INFO: KPPS:/dev/ttyACM0 kernel PPS timeout Connection timed out(110)
gpsd:WARN: NMEA0183: can't use GGA time until after ZDA or RMC has supplied a year.

promeneur · November 25, 2023, 8:16am

The building where i live is built with concrete. Perhaps this is the problem.

But the in-built GNSS in my smartphone gets no problem. How do you explain this ?

Do you know any mouse GNSS device with antenna ?

marel · November 25, 2023, 9:15am

That could well be. Good you tried also your smartphone.

The smartphone was likely not at the same place as the GPS USB dongle and just moving a few centimeters can make a significant difference. What not helps is that this USB dongle is small so no room for a good antenna.

I would get a longer USB cable and move the GPS dongle close to a window and see if things work better.

That shows that it knows which satellites to expect but it can not find any. If moving the USB dongle to a good location does not help I would assume the dongle is broken and replace it.

marel · November 25, 2023, 9:27am

The editing time-out for this forum are really too short…

On my last reply, looking better at the picture I am not 100% sure how to interpret this does “Stats Seen: 21” means that 21 satellites are seen and locked? If so, the problem is different.

hcvv · November 25, 2023, 9:40am

Maybe you are too trigger happy in clicking the Reply button before thouroughly checking at right if you have made typos or forgot something.