Open sgofferj opened 11 years ago
This is similar to (but not exactly the same as) issue #404
Based on my experiences with high-power LED-drivers, I'm working on a combined board with an amber 1W LED and a high power buzzer, which are powered from the flight battery and controlled by a 5V signal. That would complement that feature nicely
We are going to write an "AP_Notify" library that will abstract away the various ways that we can tell the pilot about the state of various things like GPS lock, failsafes, etc. I hope this will allow us to easily support a wider variety of devices even if their way of interacting with the APM is quite different. I.e. some LEDs can be directly controlled by output pins on the APM but some more sophisticated LEDs use an I2c connection.
I see the AP_Notify library has been implemented. Does this issue still stand?
The request is still valid although i have no idea if/when it will be implemented..
As we nowadays have even more failsafes that can lead to an autoland than at the time of the request creation, having some kind of acoustical warning might really be good. Something like the back up beeper of a truck or similar, so bystanders in the autolanding area do realize, the craft might not be able to sense them and get out of the way.
NOTIFY_OPTIONS
to enable the feature
AC3 does autolanding in certain failsafe conditions. For safety reasons and to help locate the copter after a failsafe-induced autolanding, buzzing the buzzer in intervals when in autoland mode would be good. Interval-buzzing is also likely to carry a psychological "do not touch me"-imperative in case, bywalkers find the copter after a failsafe-induced autolanding.
Buzzer could be controlled by a parameter: BUZ_WARN: 0=never (only ARM/DISARM beeps), 1=failsafe autolandings, 2=any autolanding (including manual set LAND mode), 3=any failsafe condition