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
On pypilot-provided heading information
#3
(2021-01-12, 12:02 AM)seandepagnier Wrote: you seem to have found out what is going on

If you have any suggestions to change how pypilot, the pypilot plugin, or opencpn handles this interaction to improve it would be helpful

Yeah it took me quite a while to figure it out, so I thought I'd share it. I love the modularity of it all and how it all fits together makes sense to me. If there's any improvements possible it would be documentation and release notes.

Only since you ask for it, I could imagine that the Forward NMEA functionality presents the incoming data in the nmea debug window, like the NmeaConverter plugin does, tagging its lines as '(virtual)'. This way it'd be self-explanatory. Or, in addition, have two check boxes, like ForwardNMEA and ImportNMEA, with one of those help buttons next to it. This all depends on the shift towards signalk, I guess. But I don't think nmea will be obsolete soon.
Reply


Messages In This Thread
RE: On pypilot-provided heading information - by ironman - 2021-01-12, 10:43 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)