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
TCP In/Out Connection for Autopilot
#3
e-sailing, thank you for your answer. The RS422 to TCPIP server works op port 2000, sofar it worked flawlessly. Connecting the RPi to Miniplex 2USB by USB is an option I'm aware of. The network on the NMEA183/Seatalk/N2K side of the NMEA/TCPIP converter is the main place for all the navigation at the moment so I prefer not to change anything in that network.

Working with OpenPlotter and without autopilot-control is no problem for now. It is great to try-out all the possibilities of SignalK , OpenCPN and the other features. I installed OpenCPN with oeSENC charts on the RPi to use them on via VNC my laptop and tablet.

I'm just wondering about the reason that two-way traffic over TCPIP is not working. Is it a bug that needs to worked on [because Kplex does support it] or is it a feature that has been decided on.

I find OpenPlotter a very fine and promising development which I fully support ..
Reply


Messages In This Thread
TCP In/Out Connection for Autopilot - by Zeilzin - 2017-08-04, 09:16 PM
RE: TCP In/Out Connection for Autopilot - by Zeilzin - 2017-08-05, 06:09 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)