|
From: | aimdev |
Subject: | Re: [gpsd-users] Galileo |
Date: | Wed, 7 Mar 2018 07:21:28 +0000 |
Hi My quickest way, chmod 444 /usr/sbin/gpsd then service gpsd stop or killall -9 gpsd The settings on my gps are not saved when it asks if you want to write setting, there is a small button to be pressed on ublox-centre which I never noticed before. Quick test showed gpsd didn't change settings after use, but I will check it again. No GAGSV sentences seen using gpspipe or gpsmon /dev/ttyACM0, but they are being produced, according to ublox-centre and with stty -F /dev/ttyACM0 -echo && cat /dev/ttyACM0. My client software needs to identify the constellation based on a prn, which is not apparent in all sets, so gpsd appears to resolve in the code (driver_nmea0183,c), // NMEA-ID (33..64) to SBAS PRN 120-151. if (satnum >= 33 && satnum <= 64) satnum += 87; if (satnum != 0 && satnum < 32) { /* map Beidou IDs */ if (talker[0] == 'B' && talker[1] == 'D') satnum += 200; else if (talker[0] == 'G' && talker[1] == 'B') satnum += 200; /* GLONASS GL doesn't seem to do this, but better safe than sorry */ if (talker[0] == 'G' && talker[1] == 'L') satnum += 37; /* QZSS */ if (talker[0] == 'Q' && talker[1] == 'Z') satnum += 193; } return satnum; The problem is that it appears Galileo sentences use a numeric nmea id starting at 1, so the fact that it is from a GAG nmea sentence is required to be used to add an offset for Galileo, presumable via the relevant talker. I haven't delved into the code any further yet. If anyone could confirm my findings that would be very useful These are my thoughts, I am sure people more knowledgeable with gpsd’s code will be able to provide a solution. Aimee
|
[Prev in Thread] | Current Thread | [Next in Thread] |