Ummm, I dont know if this is helpful or not....
I have some IP knowledge (the sort thats dangerous
) but certainly dont understand the ins and outs of UDP, broadcast and multicast. I really work on known IP addresses, DHCP to some extent and dont really get subnet addressing etc (mostly laziness I expect). So....
empirically heres what I found worked when configuring kplex/OCPN to do what RythmnDoctor
<!-- This one does the inputs -->
/jffs/kplex -o mode=background serial
<!-- This one does the output -->
/jffs/kplex -o mode=background serial:name=AUTOPILOT,direction=out,filename=/dev/ttyUSB1 tcp:mode=client,persist=yes,address=192.168.20.118 ,port=10111
Note that there are 2 connections in OCPN (3.2.2) defined, trying to do this with 1 connection hung OCPNs data capability iirc. In my case kplex is being run on a router and can access the laptop
running OCPN both wired and wireless. The GPS
connections are wired through the router, not the laptop
, using a single
USB/Serial converter into an Actisense Opto 1 serial connection into USB1, USB0 is AIS
. Inputs and outputs at the Opto 1 go to different places.