How to use one gpio button to engage and disengage py-pilot

[Steve OShaughnessy]

I want to use buttons connected directly to pi gpios. But I would like to use one button to engage and disengage py-pilot. Is there an easy way to achieve that or do I need to learn python :-)

Thanks

[seandepagnier]

I am not sure if you want to use 1 button to engage and a different to disengage, or 1 button to toggle. By default the "auto" pin marked on the pypilot hat will do this.

Yes, assuming you are running the pypilot_hat service (already enabled on tinypilot) navigate to the host:33333, or in the web control of pypilot there is a link in the configuration to programming keypads and remotes.

From here you can reprogram the remotes but also any of the gpio pins to do any types of functions, including engage, standby, or auto which toggles (but exits menu if in the menu)

[Sailoog]

I am thinking of adding some pypilot actions to the openplotter-notifications app so that some pypilot controls can be triggered by predefined notifications in the Signak k server. This would include GPIO states, environmental conditions, any onboard sensor state... the possibilities are endless. Obviously, this should be handled with extreme care.

Initially I only would include:

ap.enabled
ap.heading_command
ap.mode
ap.tack.direction
ap.tack.state

This would also solve Steve's request because in openplotter-gpio app you can generate notifications using any GPIO.

Any suggestion?

[ironman]

I want to use buttons connected directly to pi gpios. But I would like to use one button to engage and disengage py-pilot. Is there an easy way to achieve that or do I need to learn python :-)

Thanks

You might find this and some more information here: https://github.com/pypilot/workbook/wiki...-interface.

So what you want can be done with the standard issue of pypilot. No python knowledge needed, but it might still be a bit intimidating. Let us know where you are at; if you have built or assembled a pypilot, you can do this as well!

[seandepagnier]

I am thinking of adding some pypilot actions to the openplotter-notifications app so that some pypilot controls can be triggered by predefined notifications in the Signak k server. This would include GPIO states, environmental conditions, any onboard sensor state... the possibilities are endless. Obviously, this should be handled with extreme care.

Initially I only would include:

ap.enabled
ap.heading_command
ap.mode
ap.tack.direction
ap.tack.state

This would also solve Steve's request because in openplotter-gpio app you can generate notifications using any GPIO.

Any suggestion?

This could work, but my main concern would be for manual control and the amount of delay time or lag to trigger events this way. It might end up being a lot less responsive. For other actions such as listed here, this is not very important.

Maybe it would be better to instead assign gpio to signalk, or pypilot or other apps similarly to assigning other hardware such as gps or serial ports?

[Sailoog]

After reading https://github.com/pypilot/workbook/wiki...-interface I have realized that currently openplotter is not checking GPIO conflicts well. We should parse ~/.pypilot/hat.conf and we are not doing this. I will add this to openplotter v4 ASAP.

Question. I can se this in ~/.pypilot/hat.conf: "gpio27_06", does this mean that both GPIO27 and GPIO06 are used?

[seandepagnier]

After reading https://github.com/pypilot/workbook/wiki...-interface I have realized that currently openplotter is not checking GPIO conflicts well. We should parse ~/.pypilot/hat.conf and we are not doing this. I will add this to openplotter v4 ASAP.

Question. I can se this in ~/.pypilot/hat.conf: "gpio27_06", does this mean that both GPIO27 and GPIO06 are used?

I am not sure exactly what you are referring to, but it likely indicates that if both of those gpio are pressed at the same time a particular action is triggered.   So yes, in that case both would be used.

I am not sure parsing hat.conf is the way to solve this though, that file just defines actions.   Instead we might need a separate way to manage GPIO.   Right now, pypilot_hat just grabs certain gpio and assumes it has the right to use them.