OpenMarine

Full Version: [SOLVED] false connection error in "check system"
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
After upgrading OpenCPN to v.5.2 (supports SignalK), I connected openCPN to signalK server directly (deleted connection via TCP - NMEA0183).
This works, but "Check system" reports error:
"The default OpenCPN connection is disabled and is not getting data from Signal K. Please enable this connection in OpenCPN:
Network
Protocol: TCP
Address: localhost
Data Port: 10110"
  • OpenPlotter version: 2
  • Raspberry Pi version: 4B 4GB
  • Connected devices: only GNSS reciver (Hollux m-215+)
yes, this will be changed on next version. We will make the signal k connection the default one instead of the NMEA 0183
Maybe better "SignalK" OR "NMEA0183"? (in "Check system")
Since we are generating most of the data in SK format in openplotter, the SK connection in opencpn should be "mandatory".
What we could add is a warning about duplicated data if you have a SK connection and a NMEA 0183 connection to TCP localhost 10110
OK thank you. I understood.

BTW: I see new strings to translate (on Crowdin). But DataPort is (in both strings) empty. Shouldn't the value "3000" be there (like "10110" in TCP/NMEA 0183)?
DataPort value will be there, it is not translatable because it will be replaced by the current Signal k port. Remember that you can set a different port than 3000 in openplotter-signalk-installer app.
fixed in openplotter-opencpn-installer 2.2.1
Unfortunately, not all data so far accessed via nmea 0183 from the SignalK server is directly accessible via the SignalK protocol...
It's a bit strange and surprising...

I have no idea how to provide ONLY the sequence "GSV" from the GNSS receiver, especially since the conversion with the plugin "SignalK-to-NMEA0183" does not include this sequence to choose from... Turn on the plugin-converter (SK->nmea0183) with no any sequences marked?

https://www.cruisersforum.com/forums/sho...ost3202164
(2020-08-09, 10:28 AM)wbartoszy Wrote: [ -> ]Unfortunately, not all data so far accessed via nmea 0183 from the SignalK server is directly accessible via the SignalK protocol...
It's a bit strange and surprising...

I have no idea how to provide ONLY the sequence "GSV" from the GNSS receiver, especially since the conversion with the plugin "SignalK-to-NMEA0183" does not include this sequence to choose from... Turn on the plugin-converter (SK->nmea0183) with no any sequences marked?

https://www.cruisersforum.com/forums/sho...ost3202164

Signalk doesn't decode GSV nmea messages into sigK data. Messages which are decoded automatically are here >
https://github.com/SignalK/signalk-parser-nmea0183
GSV NMEA messages received by signalk server on a connection get sent straight out again on port 10110, no point in using the sigk-nmea converter, the message is there already. If you want the dashboard to receive those then you can set up a tcp connection in opencpn as well as the sigK connection  to just receive GSV messages on tcp port 10110, the dash will then display the sat data.
[Image: pIbOpxF.png]