2020-06-06, 02:42 AM
Trying to figure out the best way to keep things simple.
Would really like to keep routers and OpenPlotter out of the picture.
Pre-tinypilot config:
Quark-A027 acquires AIS, GPS and Seatalk wind and makes that info available as NMEA 0183 via WiFi ad-hoc connection with cheap Android tablet (no GPS), running Dave's Android OpenCPN (AO) in cockpit.
Now, in addition to receiving GPS, AIS and MWV, AO needs to send APB and XTE messages to tinypilot (TP).
New config 1:
Quark sends GPS, AIS, and MWV (wind) to TP via USB. TP repeats these messages out via TCP port 20220. AO connects to TP access point to receive GPS, AIS and MWV and to send APB and XTE messages to TP. Currently, TP is not repeating AIS messages out port 20220 so AO is AIS-unaware. Possible TP fix in the works.
New config 2:
AO and TP (reconfigured as a client) each connect to Quark (192.168.1.100) via WiFi ad-hoc connections. TP will always be assigned 192.168.1.101 if it is first to connect and AO would then get 192.168.1.102. However, no traffic (pinging or otherwise) passes between ...101 and ...102. I guess that's the nature of ad-hoc connections. So, this configuration is a no-go.
Thanks in advance for any comments or suggestions.
--Bob M
Would really like to keep routers and OpenPlotter out of the picture.
Pre-tinypilot config:
Quark-A027 acquires AIS, GPS and Seatalk wind and makes that info available as NMEA 0183 via WiFi ad-hoc connection with cheap Android tablet (no GPS), running Dave's Android OpenCPN (AO) in cockpit.
Now, in addition to receiving GPS, AIS and MWV, AO needs to send APB and XTE messages to tinypilot (TP).
New config 1:
Quark sends GPS, AIS, and MWV (wind) to TP via USB. TP repeats these messages out via TCP port 20220. AO connects to TP access point to receive GPS, AIS and MWV and to send APB and XTE messages to TP. Currently, TP is not repeating AIS messages out port 20220 so AO is AIS-unaware. Possible TP fix in the works.
New config 2:
AO and TP (reconfigured as a client) each connect to Quark (192.168.1.100) via WiFi ad-hoc connections. TP will always be assigned 192.168.1.101 if it is first to connect and AO would then get 192.168.1.102. However, no traffic (pinging or otherwise) passes between ...101 and ...102. I guess that's the nature of ad-hoc connections. So, this configuration is a no-go.
Thanks in advance for any comments or suggestions.
--Bob M