2020-08-22, 05:13 AM
(This post was last modified: 2020-08-22, 05:21 AM by seandepagnier.)
I'm imagining the boat that is designed to turn in tighter circles to port in a specific harbor, or maybe it's one of those catamarans that has asymmetrical hulls... anyway, I should be able to map it to a single key for pypilot, but is this really needed?? Is this a real case or an imagined one? Most rudders stall beyond a certain angle and you want the autopilot to be able to reach this angle on both tacks if possible. It's only useful to go past this angle (afaik) in harbors when docking it can increase maneuverability and act as a brake (at least under sail or sculling I know nothing about power) to move the rudder past the stall angle, but this is rarely done with the autopilot.
I would be mostly happy to sweep away the keys that are pilot specific. These are what annoy me about the current spec.
I always want to minimize redundant code and logic even in seemingly trivial cases if possible, it's just easier to maintain when you can make a single change rather than several. you could be right that it's needed for signalk especially if the clients have significant lag so I will concede this point for now and it's not that much work...
What about manual control, dodging (manual control override while autopilot is engaged could maybe share this) and tacking? I think we could use keys for these.
I would be mostly happy to sweep away the keys that are pilot specific. These are what annoy me about the current spec.
I always want to minimize redundant code and logic even in seemingly trivial cases if possible, it's just easier to maintain when you can make a single change rather than several. you could be right that it's needed for signalk especially if the clients have significant lag so I will concede this point for now and it's not that much work...
What about manual control, dodging (manual control override while autopilot is engaged could maybe share this) and tacking? I think we could use keys for these.