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
SignalK not sending $GPGSV (sats in view) to Cpn
#15
(2020-03-07, 02:21 PM)paul42 Wrote: Checked "settings.json" - there was an entry but it was:  ""
Deleted the line, made no difference after a restart.

Are you absolutely sure? Because an empty string as sentenceEvent would explain all your symptoms.

Quote:Found this setup info:
https://opencpn.org/wiki/dokuwiki/doku.p...signalk:a6
which seems to show you do need the convertor plugin, also suggests a UDP NMEA0183 Sender Plugin could do the job.

Confused now....

Adding more references is unlikely to help. When we figure out what is stopping the raw nmea0183 data from appearing at tcp 10110 we can work out the rest of the details.

Trust me, I'm one of the authors of the Signal K server, so I supposedly know what I'm talking about here..

Quote:Just looking again at the Instrument Panel WebApp & it shows the wrong longitude, lat is correct
In the Telnet stream it's  00055.1925,W which is as shown in Cpn, the Inst Panel shows W 000.91988

If you log and share some of your raw data I can have a look. Without more details it is impossible to help.
Reply


Messages In This Thread
RE: SignalK not sending $GPGSV (sats in view) to Cpn - by tkurki - 2020-03-07, 09:28 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)