So I have purchased a v1.1 board that has the remote trigger facility.  As I understand it, I need to link the H/L pad to a pad I can trigger in BF.  Does the pad need to be a UART or can it be any pad that provides a signal/power.  So for example, I have spare pads for buzzer and LED.  Could I use the LED + pad to trigger the remote?  I ideally want to keep the buzzer pads for a buzzer.

I have seen a couple of mentions of linking it to a resource pad, but they aren't very exact in what constitutes a resource pad.

https://www.runcam.com/download/RUNCAM-DVR-S-Manual.pdf

My FC is a CrazyBee F4 V3.1 AIO Flight Controller (SPI Frsky D8 Receiver, 5V 1A BEC)

   

Thanks.

I believe you just need to wire the H/L pad of the RunCam DVR-S to any spare pad on the FC that has a timer resource associated with it. So on the CrazyBee F4 FC you can use the LED pad if you aren't planning to use it for any external LEDs. The SpeedyBee app will then (normally) take care of remapping the resource correctly. Unfortunately the latest version of the SpeedyBee app the Mode & Pin Associate tab seems to be broken and just shows a "Flight controller data acquisition failed, please open the network and re-acquire." error message. I've tried connecting / re-connecting it to most of the FC's I have which covers the F411, F405, F7 and H7 MCU's so it's not an MCU type specific issue. I also have a couple of CrazyBee F4 boards as well but it doesn't work on those either.

Behind the scenes the SpeedyBee app will just be automatically remapping resources to use PINIO, so to set up the LED_STRIP pad to start the DVR when you arm the quad and stop the DVR when you disarm the quad, run the following commands in the CLI...

Thanks.

I don't think this board comes with bluetooth, so the app wouldn't work anyway. That Speedybee F411 is not the same board. Mine is the outdated FrSky SPI version, which is probably why Unmannedtech can knock the kits out so cheap (guessing when they approached Happymodel about making a cheap drone DIY kit, they said, "Oh we have 1000 of these FC we can do you for a low price", LOL). Of course if it all works well, you get a minimal solder 3S cinewhoop for £85. Once it all gets here I will try it out.

I'm going to run it slightly different to how the manual says to set it up. I intend to split the camera feed at the camera, send one wire to the VTX, the other to the DVR, so failure of DVR doesn't equal no video. On that same topic, would you take power for it from the VTX or the FC? Does it make any difference?

Slightly offtopic. Do you have any resources/links on the technical side of the CLI. I get what "resource" means and pinio is pin I/O. But how it maps, I would like to know, so I can work this stuff out myself. I know you all have had a lot of years to get a handle on all of this, but I would also like to learn it too. Also how to assign it in BF Configurator, so i can trigger it from the Radio.

Thanks.

Any FC supports the SpeedyBee app. It doesn't need to have Bluetooth capabilities. If you have an Android device you can just connect it to the FC using an OTG cable and use the SpeedyBee app over a wired connection. If you have an Apple device however you are out of luck due to their "security" policies that disallow cabled connections to unapproved 3rd party devices.

It doesn't matter how you power the DVR board. Just make sure the BEC on the FC or VTX has enough current capacity to power all the devices connected to it.

You can only do custom resource remapping and PINIO configuration using the CLI, but the configured PinioBox values determine which mode(s) in the Modes tab of Betaflight Configurator activates the PINIO switches that are mapped to the associated output pads on the FC.

Below are some resources on resource remapping, PINIO, and PinioBox...

• Oscar's Betaflight Resource Remapping Article: https://oscarliang.com/betaflight-resource-remapping
  
• Betaflight GitHub Pinio & PinioBox Wiki Article: https://github.com/betaflight/betaflight...d-PinioBox
  

And here are some relevant JB videos...

Thanks, SnowLeopard.