inav icon indicating copy to clipboard operation
inav copied to clipboard

The beeper ouput pin is blocked by deactivated sources, other sources that are not deactivated cannot activate the beeper

Open 1972linux opened this issue 2 years ago • 1 comments

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

  1. set "beeper -HW_FAILURE" on CLI
  2. Assign Mode Beeper to RX Chanel
  3. All Hardware without any problem, GPS-Receiver is connected and activated
  4. Activate Beeper via RC Chanel
  5. external Beeper is beeping
  6. Disconnect GPS-Receiver
  7. 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

Suggested solution(s)

change the logic to the expected behavior

  • FC Board name and vendor: Speedybee F405 V3
  • INAV version string: 7.0.0

1972linux avatar Dec 19 '23 21:12 1972linux

That does indeed not sound right. Good find.

b14ckyy avatar Mar 22 '24 17:03 b14ckyy