This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Using GPSD is not mandatory, though it presents the advantage to allow using NMEA, as, in this case SignalK receives the NMEA flow coming from the GNSS.
Consequently, the GNSS status of OpenCPN becomes available (among other goodies ...)

However there is, since some times, a bug in this utilization :
After startup, GPSD simply doesn't work Angry until a gpsd client is activated (any of them, gpsmon, cgps, xgps ...) then immediately GPSD starts to present NMEA to SignalK and all is fine.

This isn't an activation issue because if (just after start-up procedure), I pass the command :
systemctl is-active gpsd
I get the response : active, but gpsd still does'nt work and NMEA don't reach Signal K ! Huh

Only after using any gpsd clients, everything is OK again

Could Dev team add something in the start up procedure which REALLY  would activate that daemon, e.g. start/stop one of its clients  Exclamation ?

Thanks in advance for your answers ! Rolleyes

Used versions : Openplotter 2.9.1, OpenCPN 5.6.2, Signal K 1.45.0
BTW Signal K displays : connected to localhost 2947 which seems right !
Didier B
Pi4, SSD USB3, OP 3.0 OC  5.6.2


Forum Jump:

Users browsing this thread: 1 Guest(s)