Custom Defaults
Rotorflight Wiki is replaced by www.rotorflight.org.
Custom defaults are the base hardware configuration for a flight controller. They are a file that contain allocations to connect controller functions to the input/output pins where they interface with other board components. These include pin assignments for things like Motors and servos, timers, dma, Gyro's etc. In Betaflight these files are loaded after flashing. They configure all of the pins as they are marked on the flight controller.
For Rotorflight these pin assignments generally have to change. We allocate Servos to spare pads on the board such as the LED_STRIP, extra RX or TX pads, or the FC multi-cable. The same goes for motors. This remapping of functions means that the labels on the FC often no longer reflect what is to connect to them.
Not every Rotorflight Custom default will be suitable for your application. Motorised tails and Variable (Servo) tail helicopters require different mapping. Files in the Custom defaults repo will contain both (MT) - Motorised tail and (ST) servo tail versions for each flight controller (AIO boards are motorised tail).
Temporary custom defaults repository. Use these until the official repo is ready.
This will be the official repo when ready custom defaults repository
- Overview
- Back-up and restore
- Servo Wiring and adapter boards
- Custom Defaults
- Custom defaults remapping spreadsheet
- Receiver Setup
- Gyro & Board Orientation
- Voltage & Current Sensors
- ESC Setup
- Motor Setup
- Servos Setup
- Mixer
- Modes
- RPM Filters
- Filter Setup
- Governor Setup
- Adjustments
- Introduction
- Initial Tuning
- Governor Tuning
- Feed forward Tuning
- Tail Tuning
- Tuning on the Field with Lua Scripts
- Blackbox Logging
- Working with Blackbox Explorer
- K110 with Play F4
- Profile (Bank) switching example
- Using stability modes (6G)
- Adding OSD support for FPV Setups