OpenMarine

Full Version: Pypilot actions added to openplotter-pypilot v4.x.x
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
We have just released openplotter-pypilot v4.0.11 and now pypilot is integrated into the openplotter actions system.

This means that you will be able to program these actions:

Command (+x, -x, x)
Engage AP
Disengage AP
Tack starboard
Tack port
Tack cancel

which can be triggered by any parameter present in the system. This includes GPIO, any sensor, or any threshold defined on any Signal K key.

Once updated to openplotter-pypilot v4.0.11 you have to go to openplotter-notifications app and these new actions will be available when defining actions in Actions tab.

The openplotter-notifications app has not yet been documented, but we will do so ASAP. If you want to try this, you can create the notifications that will trigger the actions in the "Send" tab and create the actions that will react to these notifications in the "Actions" tab, as you can see in the screenshots below:

[attachment=2970]

[attachment=2972]

To trigger the actions select the notification in "Send" tab and click "Play".

Report here any issue please.
WOW! it is what I need!
Any plans to add switches between modes (wing/gps/compas)? and maybe... PID profiles?
More settings can be added. "Modes" is a candidate, but I am not sure if it is worth adding more elaborate settings like PID. We will not add settings that require a quick response even though the current settings only take milliseconds.
I think by profiles he means switching to different profiles which doesnt require a response. The profile change updates all the gains and servo settings at once.

This might be tricky since the user can define any number of profiles with arbitrary names.
Ah ok. I have not played enough with gains yet. If names and files of the profiles are stored somewhere they could be listed but if they are saved as files somewhere we can add the path to them in the data field when setting an action.
The profiles can be queried/updated from pypilot by reading the profiles key eg:
pypilot_client profiles

They are also stored in the pypilot.conf

Honestly I would not bother trying to implement this until the previous features are more widely used/tested, but just to be aware of it.
Agree. This new feature has great potential and endless possibilities, but it must be managed carefully. There are obvious combinations that use GPIO or react to heading or wind values, but some combinations could lead to even dangerous and unexpected results. With this, you could even control the autopilot from home if that makes any sense.