Of course, better coordinate.
In this version of Openplotter 3, we're trying to get rid of "sudo" because we're thinking of a web interface for future versions of Openplotter and non-sudo processes make our lives easier. You need sudo to start/stop systemd services and that's why we tried to switch to GUI managed pypilot services and python startup scripts. We return to systemd, no problem.
With pypilot running as a systemd service, the "Rescue" function no longer makes sense. I will remove it
At first glance, I can see that there are still some minor changes to be made and I will do it as soon as possible but I have a question. You removed openplotterPypilotRead.py and that script was there because pypilot_boatimu mode was not sending data to signal k server. Is pypilot sending data to Signal k server in both modes pypilot_boatimu and pypilot now?
In this version of Openplotter 3, we're trying to get rid of "sudo" because we're thinking of a web interface for future versions of Openplotter and non-sudo processes make our lives easier. You need sudo to start/stop systemd services and that's why we tried to switch to GUI managed pypilot services and python startup scripts. We return to systemd, no problem.
With pypilot running as a systemd service, the "Rescue" function no longer makes sense. I will remove it
At first glance, I can see that there are still some minor changes to be made and I will do it as soon as possible but I have a question. You removed openplotterPypilotRead.py and that script was there because pypilot_boatimu mode was not sending data to signal k server. Is pypilot sending data to Signal k server in both modes pypilot_boatimu and pypilot now?