Before I update the workbook I first ran the install myself and updated the how-to, herewith attached. I have a few questions, but before that, may I say what a significant and momentous effort this is, and how impressive it is to see two brilliant initiatives in the openmarine universe come together in this way!
I have done the install only once, and possibly not in the right order. I could see a number of checks and balances kick in, and that was very helpful. However, these checks seem to cut off a few options:
https://github.com/pypilot/workbook/file...ion.v3.pdf
I have done the install only once, and possibly not in the right order. I could see a number of checks and balances kick in, and that was very helpful. However, these checks seem to cut off a few options:
- The HAT service does not seem to start without the HAT hardware. This seems incorrect; even without PyPilot HAT it should be possible to enable the service to assign raspberry GPIO pins or IR codes to keys.
- I could not start pypilot without the connection to signalk having been established. If this is intended, I understand, but pypilot can run very well without, and the dependency on signalk could be seen as complication.
- I think the reason why the app did not automatically approve the signalk access request was that I had not logged in once to signalk yet, and no admin account had been created. Is that right? In that case, a simple reshuffle of the installation steps would solve this.
- The UART mechanism requires an additional reboot, which is a bummer. I did enable the UART in Raspi-Config. Can this mechanism be streamlined? Without having the insight you guys have, I'd say just check for ttyS0 instead of serial0.
https://github.com/pypilot/workbook/file...ion.v3.pdf