2020-05-19, 05:29 AM
(2020-05-18, 04:08 PM)affinite Wrote: This has become a bit of a "pebble in my shoe"
I just tried putting the USBGPS onto my laptop and setup NAVMON to route the NMEA data from the USBGPS to its TCP server on 192.168.1.92:10110 (my laptop)
I have an SK Connection pointing to that IP address as a client and, just as before, SignalK on the Rpi sees the data and shows a valid "navigation.position" and the other GPS paths.
But, like before with simulated data, no NMEA data appears in OCPN.
If I activate the "Convert SK to NMEA" plugin in SK and configure it to create GLL and GGA from SK, voila, the little red boat appears in OCPN!
PaddyB, Like you said I shouldn't have to do that.
As far as I understood, I would have expected all live SK paths to be converted to NMEA sentences and sent out on port 10110 to OCPN
I dont want to waste your time guys if Im simply misunderstanding how to configure this connection, but I'm beginning to think that there is some sort of bug relating to NMEA over IP into SK at play here.
Has anyone else successfully sent NMEA 0183 to SignalK over TCP/IP ?
Got me stumped as well
I can send over tcp from node red on another computer on the same network and receive it in node red on the pi, but can't seem to connect to sigK in a new connection. It says connected from the other machine to the 192.168.. Pi address port 10110 but can't see any data coming into SK - that's sending a repeated RMC nmea string. So dunno... WHat you could try is a flowe in node red to see what's coming in from navmon >
Or ask on the sigK slack channel maybe. http://slack-invite.signalk.org/