2019-07-31, 01:42 PM
(2019-07-30, 09:18 PM)johnm Wrote: Making some progress.
I can connect to tinypilot from opencpn on linux notebook using the pypilot plugin.
In opencpn created a tcp connection to 192..18.14.1 port 20220 send and receive.
Opencpn can see compass pitch and heel.
tinypilot can see gps as it's on the mode list.
This is a good start to evaluate but need to make some changes to make a satisfactorily solution for me
I have a miniplex 3 MiniPlex-3Wi-N2K.f
http://www.shipmodul.com/en/miniplex-3.html
It ties together all my mostly old instruments.
Really works great.
I want to connect tinypilot to it.
In hindsight wish I would have bought ethernet version and plugged into a real wifi router.
The miniplex is unable to originate a nmea network connection.
So will need tinypilot connect to it.
Reading through the signalk documentation looks like it can make a tcp nmea connection to another device but have not made any progress figuring it out. I see a signalk.conf in tinypilot but see just one line.
Can I configure the signalk in tinypilot to make a tcp or udp nmea connection somehow.
Ultimately I'm willing to spend a lot of time working out the details.
Not right now. It is a server only.
You could write a simple client which connects to both miniplex and tinypilot and relays tcp nmea messages. You can also use opencpn to do this.
Quote:Assuming that can be dealt with will need to have one or both of devices to be client to an access point. Realistically neither are up to being the access point.If you want to avoid the problem of the AP going down and breaking the whole network, you could use an ad-hoc network instead.
I can't see my autopilot as my primary access point and the miniplex has no way to
to map mac addresses to fixed ip addresses. I'm capable of finding devices on a network it should not be part routine part of boating
So at this point I'm leaning towards another access point and probably a backup.
I'm going to add support for fixed ip client for the next version of tinypilot