Sooo - an unexpected problem late in the build (5" race quad)… my FC - a Tmotor H7 Mini does not feature a buzzer pad (did not know this was even a thing 
)
Am I right thinking that as the buzzer (Vifly mini) has its own battery/power connection - I can use ‘any pad’ and reroute the buzzer function there using Betaflight CLI? Any recommended resource for this kind of procedure?
Thank you!
Have you got a link to the manual… All I can find if the following (if it’s even the correct FC)
Yes in theory a PWM can be remapped, look at the pins you’re not using, what it’s currently mapped to and remap it in BF CLI. Make sure you keep a dump of the current output just in case.
Bardwell is always a good resource on remapping stuff.
I guess as it’s a racing quad FC it doesn’t have a buzzer pad, as well hopefully you don’t go too far. A H7 hey?! 
There appear to be pins marked "+ and “-” … are you sure those aren’t them?
Use a continuity tester to check. If “-” does not go to ground then they are probably the ones you want.
Just checked, those + and - pads have continuity to the battery plug.
Thanks for confirming - I can get on with the soldering to a spare pad – not plugged it into BF yet - soon 
Ummm I’d always recommending plugging into BF or IiNav straight out the box to check it’s not D.O.A! Before any soldering, tinkering, etc…
makes sense - will try to remember for my future builds
I never bother with buzzers. I just set my motors up to beep in beta flight then assign to a switch.
I spent hours looking for quads in not so tall grass (I do 99% of my flying over fields) - those Vifly buzzers really help in some situations (unplugged batteries,…). I usually have the GPS-mate (buzzer+GPS battery) but no space on this one so went for a RealPit switch for the vtx to deal with the gps and I have a tiny Vifly mini buzzer - just need something to stick it/cable-tie it to (considering options for 30mn now - must decide 
)
What Martin @GunjaFPV says is solid, no supplier will accept a DOA return if it’s been soldered 
Back to mapping the Buzzer to a spare pad and I am a bit worried tbh
it seems the Vifly are ‘passive’ by the way they operate - and connecting a passive buzzer to a remapped pad is a no no without some extra circuitry as this will damage the FC by drawing too much current…
Let me know if you believe ^ is wrong (result of me reading about it for the last hour or so 
)
I think I have a plan B though
If I only connect the 5v & Gr to the Vifly - it will act as expected if battery is ejected
Then I can use the ESC beeper for the ‘on demand’ case scenario
Something else I learned today - some FC come with no ESC protocol set - getting only 3 beeps on start up does not mean you need to pull all the electronics apart…
^^ This is what I love about this hobby, learn summit new everyday! If you’re not learning from each build or crash, or whatever… You ain’t doing it right IMO! And there so much to learn! LOVE IT!!
I’m sure I’ve used a vifly before on a remapped pad, been a while though (I too use buzzers on all quads, cos well you know… I learnt when I lost my first, haha! although that had a buzzer, but I guess they don’t work too well at the bottom of a river (likeliest location of loss, still will never know)). Where you going for this info out of interest @Cedric ?
I remapped a damaged buzzer pad to the unused LEDSTRIP, Out of completeness (read OCD) I added a simple transistor buffer and it worked just fine.
Maybe it didn’t need it, but better safe than have you MCU overloaded and having to replace the whole FC
was doing some googling on resource mapping - found a few reddit posts gravitating around this article from Oscar L. where he specifically mention Buzzer pad
Tutorial: Betaflight Resource Remapping - Oscar Liang
Yeah oscar a top resource.
