2021-03-03, 07:27 PM
(2020-10-13, 09:52 PM)seandepagnier Wrote: It's a little more complicated... maybe
port 20220 is bi-directional nmea for pypilot. So opencpn can receive nmea from pypilot on this as well as send.
port 10110 is from signalk node server, not pypilot. So if you get pitch/heel this way, it is not directly from pypilot.
You may be able to convert this nmea to signalk also, but it's not recommended anymore because with pypilot 0.2 and later, pypilot automatically connects to signalk server, and if granted read/write permission, it can send as well as receive. This means that if you assign a usb nmea device to pypilot such as wind or even gps for example, it will forward the data to signalk. Or you could have signalk server receive this data first and pypilot will get it as well. It's best pypilot gets wind first for better reaction time, but gps doesn't matter as much.
It's true that only one program can read from one device such as gps. It's possible that this can be gpsd, opencpn, pypilot, or even signalk server, and all of these can relay the data to all of the others. Whichever program reads directly from the gps must be running then and if it stops all the others will lose it.
Hi Sean from your reply above (in bold) it seems that if you set-up the GPS in SignalK it should automatically be picked up by pypilot. Please help me as I have done this but can not get pypilot to detect the gps. In short, I have set-up the gps in signal K and when I enter sudo ca /dev/ttyACM0 I get beautiful NMEA sentences and the three green bars in the top left corner of OpenCPN. However, when I open up the pypilot plugin I can not get it to read these sentences. In the pypilot configuration there are a few options for the pypilot host (localhost(127.0.0.1) or 192.168.14.1), etc. I have tried all of them using the data port 20220 but the gps bearing never shows in pypilot. I do not have an IMU connected as I want to navigate using gps bearings, please help