Although the beeper is switched on via an RX channel (Mode Beeper), the beeper output-pin does not work if, for example, the setting "beeper -HW_FAILURE" has been made and there is a hardware problem (e.g. connection to the GPS receiver is lost) or the setting "beeper - BAT_LOW" has been made and the battery is low.
Workaround:
To ensure that the beeper can always be activated via RX-Chanel, you must activate all beeper sources with "beeper all".
Steps to Reproduce
set "beeper -HW_FAILURE" on CLI
Assign Mode Beeper to RX Chanel
All Hardware without any problem, GPS-Receiver is connected and activated
Activate Beeper via RC Chanel
external Beeper is beeping
Disconnect GPS-Receiver
external Beeper stops beeping
Expected behavior
The beeper should not respond to deactivated sources, but other, non-deactivated sources can always switch on the beeper
Current Behavior
Although the beeper is switched on via an RX channel (Mode Beeper), the beeper output-pin does not work if, for example, the setting "beeper -HW_FAILURE" has been made and there is a hardware problem (e.g. connection to the GPS receiver is lost) or the setting "beeper - BAT_LOW" has been made and the battery is low.
Workaround: To ensure that the beeper can always be activated via RX-Chanel, you must activate all beeper sources with "beeper all".
Steps to Reproduce
Expected behavior
The beeper should not respond to deactivated sources, but other, non-deactivated sources can always switch on the beeper
Suggested solution(s)
change the logic to the expected behavior