2016-05-31, 07:16 PM
How to … make Adafruit Ultimate GPS work?
Hi!
I can’t make my Adafruit Ultimate GPS work with Openplotter. The NMEA Inspector freeze almost immediately after it starts when GPS is connected.
I have been able to make the GPS work on standard Jessie distro, with gpsmon and cgps , but I must have missed something when setting up openplotter.
Any ideas? It is probably something simple…
//Oskar
----
The GPS is connected to a Raspberry Pi 2. I’m using a serial TTL to USB converter. Besides GPS and WiFi USB-stick, no other hardware is connected.
I’m using the latest stable release of openplotter (0.8), and has run apt-get update / apt-get upgrade (a few of days ago), but not installed anything else.
On Openplotter distro I’ve checked I get a steady NMEA-stream from GPS by “cat /dev/ttyUSB0”. Inspector doesn’t freeze if GPS isn’t connected. I just says no data / waiting.
With GPS Inspector has once showed correct UTC time, but usually it only manage to write GP as source or something similar. (I guess it should be GPS, but it generally freeze after 0-2 letters). CPU utilisation is always 100% when running Inspector, with or without GPS.
Hi!
I can’t make my Adafruit Ultimate GPS work with Openplotter. The NMEA Inspector freeze almost immediately after it starts when GPS is connected.
I have been able to make the GPS work on standard Jessie distro, with gpsmon and cgps , but I must have missed something when setting up openplotter.
Any ideas? It is probably something simple…
//Oskar
----
The GPS is connected to a Raspberry Pi 2. I’m using a serial TTL to USB converter. Besides GPS and WiFi USB-stick, no other hardware is connected.
I’m using the latest stable release of openplotter (0.8), and has run apt-get update / apt-get upgrade (a few of days ago), but not installed anything else.
On Openplotter distro I’ve checked I get a steady NMEA-stream from GPS by “cat /dev/ttyUSB0”. Inspector doesn’t freeze if GPS isn’t connected. I just says no data / waiting.
With GPS Inspector has once showed correct UTC time, but usually it only manage to write GP as source or something similar. (I guess it should be GPS, but it generally freeze after 0-2 letters). CPU utilisation is always 100% when running Inspector, with or without GPS.