On the verge of giving up!! I will not fly without a buzzer, and can’t get mine working right (or at all!)
I’ve got the following two buzzers, neither of which can get working on my new build
Wiring diagram is as follows:
I wire the yellow (or green for the none vi finder v2 version) to Buz-, and the GND to GND, and then tried both the buz+ and the close by 5V. They are giving 5V. I’ve continuity checked the pads, I’ve even wired up a multimeter and seems they both giving 5V, and the “Buz-” when the beeper on fluctuates up and down. Setting DSHOT RX mode in BF also “buzzers” the motors, so the radios right…
Why is this so hard, and ready to chuck it all in… Also tested the buzzers with a 5V source (red/black charges it, red/yellow to gnd makes it buzz!) also used a different wire… Grrrrrrr
Also checked beeper_frequency = 0 in the cli of BF…
I not changed any mapping or updated/flashed the FC at all btw. out the box config more or less (setup the ELRS RX and VTX table is all I’ve done so far)
Just thought would check with my other quad… And had wired the B- to 3.3V… doh! It worked though, weird. red and black were to 5v and gnd, and yellow/ to 3.3… Changed it and working fine. going to get the config off of that.
How that been flying for weeks OK! haha. Still that’s a side issue. The new FC is a H7 Diatone Mambo MK4 BTW the one not working!
yeah this is common though for the 3 wire buzzers with on board battey. You wire the 5V on the buzzer to either B+ or any 5V, the GND to GND and the yellow/green (on the cheaper amazon buzzers) to B-.
here is the config from the BabyHawk “now working properly as I had the B- to 3.3V on the FC!!!”
Heh cheers. Think was Stevie’s comments on
cli settings and thinking of checking the babyhawk which glad I’m did as how that worked with the 3.3v wiring god only knows!
Now onto resource remapping for the babyhawk and using undocumented pads to get gps in that. Conformal coat them all and get them rebuilt!
Ahhh @notveryprettyboy and @Steviegeek think this is my issue from yesterday as probably hard reset the board from 4.3 to 4.4 between checking the hardware…not home atm but fingers crossed this sorts it!