Hi,
the last few days I played around with my raspberries and the images of tinypilot and the connection to my raspberry with opencpn.
In short: It seems to work.
I take the beta image (tinypilot_2020_10_11.img.xz) and bring it to work with a raspberry pi 2b (later I´ll use a raspberry zero w).
I take my raspberry 3b+ with opencpn 5.2.4 running on it and install there the pypilot plugin 0.22.xx from the setting menue in OC.
With both pis in my network:
I then set the connection in the plugin and in OC a TCP data connection.
The two pis communicate together, I get feedback from tinypilot in OC and back so I think this will work.
Now I´ll have to wait for the motorcontroller (I´ll try it with IBT_2) and an Arduino nano witch I ordered. Also the IMU is on the way.
Thank you Sean for the great work.
Some questions left:
Control buttons (keypad): The GPIO-Pins declared in the webgui under configuration and then under the point: lcd keypad… are the actual ones?
I tried to connect a small tft (found in my grabbox) to the raspberry with tinypilot but I was unsuccessful.
It was a display using hardware spi (I was totally wrong it was a 8 bit databus).
So is it possible to connect a small tft display (witch type then? Witch driver IC?) and how to wire it with the raspberry pi?
Or do I need an Arduino switched between the raspberry and a display?
I just want to get some information about the status of the autopilot, no touch or so.
I think every display uses spi works?
Tackfunction:
Is it possible to use a keypad to tell the autopilot to tack to starboard or to port? I saw the "tack" knob but then there´s a fielt to tell the ap wich side to tack.
But when input only with a keypad how can I tell the ap witch side to tack?
When using my old Raymarine ST2000 (tillerpilot) I press two of the function knobs together to tack to one side.
Thanks and regards
Andreas
the last few days I played around with my raspberries and the images of tinypilot and the connection to my raspberry with opencpn.
In short: It seems to work.
I take the beta image (tinypilot_2020_10_11.img.xz) and bring it to work with a raspberry pi 2b (later I´ll use a raspberry zero w).
I take my raspberry 3b+ with opencpn 5.2.4 running on it and install there the pypilot plugin 0.22.xx from the setting menue in OC.
With both pis in my network:
I then set the connection in the plugin and in OC a TCP data connection.
The two pis communicate together, I get feedback from tinypilot in OC and back so I think this will work.
Now I´ll have to wait for the motorcontroller (I´ll try it with IBT_2) and an Arduino nano witch I ordered. Also the IMU is on the way.
Thank you Sean for the great work.
Some questions left:
Control buttons (keypad): The GPIO-Pins declared in the webgui under configuration and then under the point: lcd keypad… are the actual ones?
I tried to connect a small tft (found in my grabbox) to the raspberry with tinypilot but I was unsuccessful.
It was a display using hardware spi (I was totally wrong it was a 8 bit databus).
So is it possible to connect a small tft display (witch type then? Witch driver IC?) and how to wire it with the raspberry pi?
Or do I need an Arduino switched between the raspberry and a display?
I just want to get some information about the status of the autopilot, no touch or so.
I think every display uses spi works?
Tackfunction:
Is it possible to use a keypad to tell the autopilot to tack to starboard or to port? I saw the "tack" knob but then there´s a fielt to tell the ap wich side to tack.
But when input only with a keypad how can I tell the ap witch side to tack?
When using my old Raymarine ST2000 (tillerpilot) I press two of the function knobs together to tack to one side.
Thanks and regards
Andreas