I use a NMEA wind sensor which is connected to the SignalK node server on the computer running OpenCPN.
Tinypilot works on a Pi-Zero and exchanges wind data and heading via NMEA or SignalK. The TC runs the core PyPilot.
For OpenPlotter it should be even more easy since SignalK and PyPilot (the core system, not the plugin) are running on the same machine.
Playing with OpenPlotter I was able to install the OpenPlotter packages on top of Ubuntu (so it should work with Buster as well).
I used OpenPlotter-PyPilot for compass-only (heading) with an IMU.
Setting it to AutoPilot should activate the PyPilot Core with the steering abilities (which can be controlled from the PyPilot_Pi, the plugin, or a simple Web Interface).
Configuration can be handled by either OpenPlotter-Pypilot and/or PyPilot_Pi.
That said, I find the configuration with a seperate pi-zero very confinient and very stable.
I have never used OpenPlotter as AutoPilot.
Just for the terminology:
- PyPilot - the core scripts to connect with the IMU and the MotorController
- PyPilot_Pi - the control plugin for OpenCPN to connect with the core scripts
- TinyPilot - a tinycore linux OS which runs the PyPilot core on a Pi Zero (or similar) and connects to the IMU.
- OpenPlotter - a raspbian OS which runs OpenCPN, SignalK and the PyPilot core (+IMU) on a RPI3 or RPI4.
- MotorController - the system to actually steer the tiller, mostly based on Arduino. It handles some simple sensors (temperature, rudder position and end switches).
- OpenPlotter-Settings - the installer for the OpenCPN packages to get the pypilot working on your Buster system if you are not using the standard NOOBS or OpenPlotter package.
- OpenPlotter-PyPilot - the package which contains the PyPilot core for OpenPlotter (to be installed with the settings package).
The complete set of Pypilot scripts runs on the Tinypilot and MotorController or OpenPlotter and Motorcontroller.
Tinypilot works on a Pi-Zero and exchanges wind data and heading via NMEA or SignalK. The TC runs the core PyPilot.
For OpenPlotter it should be even more easy since SignalK and PyPilot (the core system, not the plugin) are running on the same machine.
Playing with OpenPlotter I was able to install the OpenPlotter packages on top of Ubuntu (so it should work with Buster as well).
I used OpenPlotter-PyPilot for compass-only (heading) with an IMU.
Setting it to AutoPilot should activate the PyPilot Core with the steering abilities (which can be controlled from the PyPilot_Pi, the plugin, or a simple Web Interface).
Configuration can be handled by either OpenPlotter-Pypilot and/or PyPilot_Pi.
That said, I find the configuration with a seperate pi-zero very confinient and very stable.
I have never used OpenPlotter as AutoPilot.
Just for the terminology:
- PyPilot - the core scripts to connect with the IMU and the MotorController
- PyPilot_Pi - the control plugin for OpenCPN to connect with the core scripts
- TinyPilot - a tinycore linux OS which runs the PyPilot core on a Pi Zero (or similar) and connects to the IMU.
- OpenPlotter - a raspbian OS which runs OpenCPN, SignalK and the PyPilot core (+IMU) on a RPI3 or RPI4.
- MotorController - the system to actually steer the tiller, mostly based on Arduino. It handles some simple sensors (temperature, rudder position and end switches).
- OpenPlotter-Settings - the installer for the OpenCPN packages to get the pypilot working on your Buster system if you are not using the standard NOOBS or OpenPlotter package.
- OpenPlotter-PyPilot - the package which contains the PyPilot core for OpenPlotter (to be installed with the settings package).
The complete set of Pypilot scripts runs on the Tinypilot and MotorController or OpenPlotter and Motorcontroller.