Thanks will follow that & come back with results.
Paul
Paul
SignalK not sending $GPGSV (sats in view) to Cpn
|
Thanks will follow that & come back with results.
Paul
Disabled SK>NMEA0183 Plugin
SK Instrument Panel shows data incl Pos, Sog, DateTime,MagVar,No of Sats Output from "localhost:3000/signalk/v1/api/sources" {"Quark":{"label":"Quark","type":"NMEA0183","GP":{"talker":"GP","sentences":{"RMC":"2020-03-07T11:34:14.000Z","GGA":"2020-03-07T11:34:14.000Z","GLL":"2020-03-07T11:34:13.000Z","VTG":"2020-03-07T11:34:14.268Z"}}}} (I notice no GSV) Output from "telnet localhost 10110" Nothing, says connected but no data flow If I enable the SK>0183 plugin data flows incl $IIZDA, $IIVTG as well as above, still no GSV
2020-03-07, 02:10 PM
(2020-03-07, 12:58 PM)paul42 Wrote: Disabled SK>NMEA0183 Plugin GSV missing is to be expected, as there is no conversion from GSV to Signal K yet. LIkewise for the conversion back from SK. (2020-03-07, 12:58 PM)paul42 Wrote: Output from "telnet localhost 10110" So we are missing the raw nmea0183 input at 10110. Next, take a look at your settings for the connection. There should be absolutely nothing in the sentenceEvent field, not even an invisible space character. You can use the admin UI or simply check ~HOME/.signalk/settings.json - there should be no "sentenceEvent" there.
Checked "settings.json" - there was an entry but it was: ""
Deleted the line, made no difference after a restart. 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.... 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 Tried the UDP Plugin, couldn't get that working either. Paul
2020-03-07, 09:28 PM
(2020-03-07, 02:21 PM)paul42 Wrote: Checked "settings.json" - there was an entry but it was: "" Are you absolutely sure? Because an empty string as sentenceEvent would explain all your symptoms. Quote:Found this setup info: 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 If you log and share some of your raw data I can have a look. Without more details it is impossible to help.
Ok thanks, I do appreciate the help.
I'm not available for several days now but will check the settings.json again as soon as possible & report back. Will try to get some logging data for you to look at. I'm lifting out of the water next week so going to be very busy. Paul Eureka Checking the settings.json there is definitely no "sentenceEvent" line but there is a "supress0183event":true line. Changed that to false & all the data is now streaming to 10110 just as you said it should without the converter plugin. Don't know what caused that to be set to true. Can see all the sentences now using telnet localhost 10110 & in Cpn with the NMEA Debug window. Instrument panel still has some incorrect readings but not bothered about that at the moment. Will look at this more closely in the next two weeks. Thank you again for your help, at least I am learning! Paul Thanks again thurki |
« Next Oldest | Next Newest »
|