been cruising since 1997 and using the old vnc suite on a pc.
have a pc display at helm
and one at navstation.
use the navstation display to do radar
use the helm
display for active nav.
what has worked well for us is to have two separate displays running
with the helm taking waypoint, nav, and route
data from the nav station
as a slave over nema183. Allows different scales and doesn't upset the helmsman when I plan an avoidance maneuver on the plotter as the scale and position would
go all wacky on them.
i have just purchased opencpn on android and set it all up.
works great, only the android seems to ignore NEMA sentences re: route
,xte,bearing, and waypoint from the helm pc which has the ships gps
. It won't even seem to display routing data unless I set a route on the android itself. (the data is getting there as verified by wireshark and the nema debug window on both ends so its not an issue with setup).
I really don't want to have to shutdown both units and copy configs around or fiddle with export and import
while underway to avoid a container ship on the horizon and still keep off the reef. Is there anyway to force the android to display at least the current
waypoint and bearing information to the helm via the UDP encapsulated NEMA the opencpn mux is sending?
the info is getting there, its just nobody is listening.
realvnc works fine, but the problem there
is still the two displays are slaved so
a zoom or shift on one is echoed on the other, i am really looking for a UDP tethered solution rather than a video solution.
Any neat tricks with autopilot
sentences or the like to make the helm android or even pc respond?
yelling at the wife from below seems to work just like the old days, but after 18 years of cruising, we tend to ignore each other too much for that
to be effective anymore.
thanks for a great and open source product