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
3 ways to bring gps to OpenCPN and Pypilot in OP2
#1
Hello to all!

For my entry into Pypilot I would have liked a detailed overview of the configuration. After a lot of research and trial and error, I have clarified some problems.

Because other users might have similar questions, I recorded an overview of the connections for the GPS signal in OpenPlotter 2.

   

I hope it can help some people to understand the system.
If there are still proposals for changes, please let me know. Maybe it can be added to the OP manual.

Bye
Reply
#2
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.
Reply
#3
Quote:port 20220 is bi-directional nmea for pypilot.    So opencpn can receive nmea from pypilot on this as well as send.

Yes right. I have added this accordingly.


Quote:port 10110 is from signalk node server, not pypilot.   So if you get pitch/heel this way, it is not directly from pypilot.


Yes, it is drawn like that. The data comes from the Pypilot, but is transmitted via SignalK.
Reply
#4
Well, also pypilot since 0.2 has bidirectional communication to signalk via signalk websockets not using nmea or port 20220 for this. gps to opencpn as gpsd -> pypilot -> signalk -> opencpn is actually possible (maybe not always desirable) it makes more sense when pypilot is not on the same machine as signak.

Unfortunately so many possible channels leads to inevitable data loops so these may need filters.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)