I’ve gotten the simpleRTK2B to communicate using a direct connection to the serial port on a Raspberry Pi, but this isn’t ideal.
However, when using the gpsmon tool, which connects to the gpsd daemon, it is hit or miss. Sometimes, the connection will go through, and other times, communication will happen, but the raw messages will be (I’m pretty sure) binary; stuff like this will show up at the bottom of gpsmon:
The odd thing is, that sometimes, gpsd will grab a few good fixes (you can see good NMEA strings), and then, after a few seconds, you see the b5620120…. stuff as above. I know gpsd automatically configures to
gpsd on the rPi is 3.17
Is the system going to a different mode of some sort?
….message was cut off – gpsd will automatically configure itself based on baud rate of serial port. I wonder if this is the cause of the issue.
One solution is to use:
This forces NMEA strings. However, it seems you have to either wait a bit after gpsd has started, or issue the command *twice*.