Hi. I'm wid. A couple years ago a flying buddy gave me an old MultiWii Spider quad to see if I could get it flying. I was/am into gliders but he loves FPV Quads and knew I love a "fix it " challenge. But I was totally ignorant about flight controllers and MultiWii or any other controller firmware. Got it flying but no FPV. When it died I got a NightHawk 250 to fix.

About a  year and a half ago I was making a final LOS test flight with  the NightHawk 250 before attempting FPV and lost the quad. I  found it a couple weeks ago.

Finding it was exhilarating and I have spent the last couple weeks upgrading to Matek F722. Using BetaFlight 3.5.7 because I am slightly familiar with it and not ready for the challenges of upgrading to BetaFlight4.

I have the quad ready for test but  won't until I get the buzzer working right. I had a buzzer and GPS in the crash but the battery disconnecting killed the buzzer, GPS was off by 50'. So now I have a vifly-finder-2-buzzer but can't get it working right.

I can't get it to work on a switch. I have set one up on an F3 and it switches and works fine. I have changed alarms to test and they both work on the F3 but not the F7. The F7 setup does beep on startup but not sure what is going on. I can't get the switch to work. Having trouble with LEDLOW switch too but that is not keeping me from flying.

I am stumped.

I suspect I will be embarrassed when I see what I did wrong. Has to be a setting somewhere, right?

I  have no ability to use this but thought I should post the "diff all". If I should post more let me know.


# _rescue_velocity_i = 20
set gps_rescue_velocity_d = 15
set gps_rescue_yaw_p = 40
set gps_rescue_throttle_min = 1200
set gps_rescue_throttle_max = 1600
set gps_rescue_throttle_hover = 1280
set gps_rescue_sanity_checks = RESCUE_SANITY_ON
set gps_rescue_min_sats = 8
set deadband = 3
set yaw_deadband = 7
set yaw_control_reversed = OFF
set pid_process_denom = 16
set runaway_takeoff_prevention = ON
set runaway_takeoff_deactivate_delay = 500
set runaway_takeoff_deactivate_throttle_percent = 25
set tlm_inverted = OFF
set tlm_halfduplex = ON
set frsky_default_lat = 0
set frsky_default_long = 0
set frsky_gps_format = 0
set frsky_unit = IMPERIAL
set frsky_vfas_precision = 0
set hott_alarm_int = 5
set pid_in_tlm = OFF
set report_cell_voltage = OFF
set ibus_sensor = 1,2,3,0,0,0,0,0,0,0,0,0,0,0,0
set smartport_use_extra_sensors = OFF
set ledstrip_visual_beeper = OFF
set ledstrip_grb_rgb = GRB
set sdcard_dma = OFF
set osd_units = IMPERIAL
set osd_warn_arming_disable = ON
set osd_warn_batt_not_full = ON
set osd_warn_batt_warning = ON
set osd_warn_batt_critical = ON
set osd_warn_visual_beeper = ON
set osd_warn_crash_flip = OFF
set osd_warn_esc_fail = ON
set osd_warn_core_temp = OFF
set osd_rssi_alarm = 20
set osd_cap_alarm = 2200
set osd_alt_alarm = 100
set osd_esc_temp_alarm = -128
set osd_esc_rpm_alarm = -1
set osd_esc_current_alarm = -1
set osd_core_temp_alarm = 70
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_tim1 = 2560
set osd_tim2 = 2561
set osd_vbat_pos = 2117
set osd_rssi_pos = 234
set osd_tim_1_pos = 234
set osd_tim_2_pos = 234
set osd_remaining_time_estimate_pos = 234
set osd_flymode_pos = 2133
set osd_anti_gravity_pos = 2129
set osd_g_force_pos = 234
set osd_throttle_pos = 234
set osd_vtx_channel_pos = 234
set osd_crosshairs_pos = 205
set osd_ah_sbar_pos = 206
set osd_ah_pos = 2126
set osd_current_pos = 234
set osd_mah_drawn_pos = 234
set osd_craft_name_pos = 2091
set osd_gps_speed_pos = 234
set osd_gps_lon_pos = 234
set osd_gps_lat_pos = 234
set osd_gps_sats_pos = 2105
set osd_home_dir_pos = 2125
set osd_home_dist_pos = 2423
set osd_compass_bar_pos = 234
set osd_altitude_pos = 2434
set osd_pid_roll_pos = 234
set osd_pid_pitch_pos = 234
set osd_pid_yaw_pos = 234
set osd_debug_pos = 234
set osd_power_pos = 234
set osd_pidrate_profile_pos = 234
set osd_warnings_pos = 2444
set osd_avg_cell_voltage_pos = 234
set osd_pit_ang_pos = 234
set osd_rol_ang_pos = 234
set osd_battery_usage_pos = 49
set osd_disarmed_pos = 2282
set osd_nheading_pos = 234
set osd_nvario_pos = 234
set osd_esc_tmp_pos = 234
set osd_esc_rpm_pos = 234
set osd_rtc_date_time_pos = 234
set osd_adjustment_range_pos = 234
set osd_core_temp_pos = 234
set osd_stat_rtc_date_time = OFF
set osd_stat_tim_1 = OFF
set osd_stat_tim_2 = ON
set osd_stat_max_spd = ON
set osd_stat_max_dist = ON
set osd_stat_min_batt = ON
set osd_stat_endbatt = OFF
set osd_stat_battery = ON
set osd_stat_min_rssi = ON
set osd_stat_max_curr = ON
set osd_stat_used_mah = ON
set osd_stat_max_alt = ON
set osd_stat_bbox = ON
set osd_stat_bb_no = ON
set task_statistics = ON
set debug_mode = NONE
set rate_6pos_switch = OFF
set cpu_overclock = OFF
set pwr_on_arm_grace = 5
set vtx_band = 1
set vtx_channel = 2
set vtx_power = 1
set vtx_low_power_disarm = OFF
set vtx_freq = 5845
set vtx_pit_mode_freq = 0
set vtx_halfduplex = ON
set vcd_video_system = NTSC
set vcd_h_offset = 0
set vcd_v_offset = 0
set max7456_clock = DEFAULT
set max7456_spi_bus = 2
set displayport_msp_col_adjust = 0
set displayport_msp_row_adjust = 0
set displayport_max7456_col_adjust = 0
set displayport_max7456_row_adjust = 0
set displayport_max7456_inv = OFF
set displayport_max7456_blk = 0
set displayport_max7456_wht = 2
set esc_sensor_halfduplex = OFF
set esc_sensor_current_offset = 0
set led_inversion = 0
set dashboard_i2c_bus = 1
set dashboard_i2c_addr = 60
set camera_control_mode = HARDWARE_PWM
set camera_control_ref_voltage = 330
set camera_control_key_delay = 180
set camera_control_internal

Hi wid,
Welcome to the forum.

Wiring ok? 5v, Gnd, -Bz.

Not much more than that other then to set a switch.

When you first power it on does it make lots of beeps?

Maybe post up a full dump as I am seeing nothing in there for the beeper or what is set to beep when you power on the quad.

Welcome to the forum  

We need to see a full dump, and also some photos of the wiring between the VIFLY buzzer and the FC would be useful.

What transmitter are you using, and have you set up the beeper switch to output a value on one of the auxiliary channels? You need to do that on the transmitter itself.

Are the beeps you're hearing on startup definitely coming from the VIFLY buzzer and not the motors? Disconnect the VIFLY to see if those beeps still occur. The reason I ask is because the VIFLY required the tiny LiPo on it to be healthy and charges for the buzzer to work. If not the the VIFLY buzzer won't work at all, not even as a normal buzzer.

(07-Nov-2020, 11:45 AM)SnowLeopardFPV Wrote: Welcome to the forum  

We need to see a full dump, and also some photos of the wiring between the VIFLY buzzer and the FC would be useful.

What transmitter are you using, and have you set up the beeper switch to output a value on one of the auxiliary channels? You need to do that on the transmitter itself.

Are the beeps you're hearing on startup definitely coming from the VIFLY buzzer and not the motors? Disconnect the VIFLY to see if those beeps still occur. The reason I ask is because the VIFLY required the tiny LiPo on it to be healthy and charges for the buzzer to work. If not the the VIFLY buzzer won't work at all, not even as a normal buzzer.

Hey Guys. Great to hear from you.
The VIfly switches  fine on a different quad. Its battery is sufficiently charged.
I definitly hear beeps from the VIFLY on startup. Put my thumb over the buzzer and it is obvious.
Wiring ok. 5v, Gnd, -Bz
I have set end points and mid points.
Using Taranis 9d+
Watching BetaFlight reciever tab shows beeper mode responds properly to switch.




Dump:
# rm = 2200
set osd_alt_alarm = 100
set osd_esc_temp_alarm = -128
set osd_esc_rpm_alarm = -1
set osd_esc_current_alarm = -1
set osd_core_temp_alarm = 70
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_tim1 = 2560
set osd_tim2 = 2561
set osd_vbat_pos = 2117
set osd_rssi_pos = 234
set osd_tim_1_pos = 234
set osd_tim_2_pos = 234
set osd_remaining_time_estimate_pos = 234
set osd_flymode_pos = 2133
set osd_anti_gravity_pos = 2129
set osd_g_force_pos = 234
set osd_throttle_pos = 234
set osd_vtx_channel_pos = 234
set osd_crosshairs_pos = 205
set osd_ah_sbar_pos = 206
set osd_ah_pos = 2126
set osd_current_pos = 234
set osd_mah_drawn_pos = 234
set osd_craft_name_pos = 2091
set osd_gps_speed_pos = 234
set osd_gps_lon_pos = 234
set osd_gps_lat_pos = 234
set osd_gps_sats_pos = 2105
set osd_home_dir_pos = 2125
set osd_home_dist_pos = 2423
set osd_compass_bar_pos = 234
set osd_altitude_pos = 2434
set osd_pid_roll_pos = 234
set osd_pid_pitch_pos = 234
set osd_pid_yaw_pos = 234
set osd_debug_pos = 234
set osd_power_pos = 234
set osd_pidrate_profile_pos = 234
set osd_warnings_pos = 2444
set osd_avg_cell_voltage_pos = 234
set osd_pit_ang_pos = 234
set osd_rol_ang_pos = 234
set osd_battery_usage_pos = 49
set osd_disarmed_pos = 2282
set osd_nheading_pos = 234
set osd_nvario_pos = 234
set osd_esc_tmp_pos = 234
set osd_esc_rpm_pos = 234
set osd_rtc_date_time_pos = 234
set osd_adjustment_range_pos = 234
set osd_core_temp_pos = 234
set osd_stat_rtc_date_time = OFF
set osd_stat_tim_1 = OFF
set osd_stat_tim_2 = ON
set osd_stat_max_spd = ON
set osd_stat_max_dist = ON
set osd_stat_min_batt = ON
set osd_stat_endbatt = OFF
set osd_stat_battery = ON
set osd_stat_min_rssi = ON
set osd_stat_max_curr = ON
set osd_stat_used_mah = ON
set osd_stat_max_alt = ON
set osd_stat_bbox = ON
set osd_stat_bb_no = ON
set task_statistics = ON
set debug_mode = NONE
set rate_6pos_switch = OFF
set cpu_overclock = OFF
set pwr_on_arm_grace = 5
set vtx_band = 1
set vtx_channel = 2
set vtx_power = 1
set vtx_low_power_disarm = OFF
set vtx_freq = 5845
set vtx_pit_mode_freq = 0
set vtx_halfduplex = ON
set vcd_video_system = NTSC
set vcd_h_offset = 0
set vcd_v_offset = 0
set max7456_clock = DEFAULT
set max7456_spi_bus = 2
set displayport_msp_col_adjust = 0
set displayport_msp_row_adjust = 0
set displayport_max7456_col_adjust = 0
set displayport_max7456_row_adjust = 0
set displayport_max7456_inv = OFF
set displayport_max7456_blk = 0
set displayport_max7456_wht = 2
set esc_sensor_halfduplex = OFF
set esc_sensor_current_offset = 0
set led_inversion = 0
set dashboard_i2c_bus = 1
set dashboard_i2c_addr = 60
set camera_control_mode = HARDWARE_PWM
set camera_control_ref_voltage = 330
set cam

The alarm is getting signal. It is sounding the startup alarms. That is what I thought so I turned on the lost signal alarm and turned off my Tx. No alarm. 

That is what confused me. Turns out that using a serial connection like s-bus to connect the FC to the Rx prevents the FC from knowing the Tx is off. Something about fail safe flags.

Still no luck with the switch.

But now I can hear the alarm by arming and dis arming. I will Have to do better than that but for now  at least I can go fly FPV now.

EDIT: The s-bus issue is talked about here:

or here:

I am posting this embarrassing solution so other newbies searching beeper troubles who find this thread can see what I got wrong. 

In the configuration tab I had not turned on the "RX_SET"

Welcome  

Glad you got it fixed 

Thanks. I thought it might be something simple I was overlooking. Now when this virus stuff is under control I can join the guys and get serious about FPV!  

By the way, what does RX_SET actually do?

(15-Dec-2020, 12:01 PM)iFly4rotors Wrote: By the way, what does RX_SET actually do?

Makes the buzzer go when the beeper mode is set via the radio. Honestly, I'm not sure why it's even an option.

Thanks, Banelle.    

(15-Dec-2020, 12:01 PM)iFly4rotors Wrote: By the way, what does RX_SET actually do?

RX_SET  has to be on for the beeper to be able to be activated by a switch on the Tx, even if it is properly set up in Modes.

That is what confused me. When I went to Modes and tested the switch I had set up for Beeper, it responded as expected, turning on and off as expected, so I thought I was good to go. But it only works if RX_SET is on. (BetaFlight 3.5.7)