docs: add custom mixes page for exotic setups

[Raffi1202]

Ports "Custom mixes for exotic setups" from the wiki to docs/06-advanced-features/custom-mixes.mdx and updates the multirotor setup guide to link to it.

Checked against the sources

Examples and CLI syntax were checked against maintenance-10.x: firmware cli.c, mixer.c, servos.c, servos.h, fc_msp_box.c, settings.yaml, plus the Configurator mixer presets and servo input names in js/model.js and js/fc.js.
Every mix that has a preset is identical to it; the flaperon, flap and RC-servo examples have none.

• Replace the removed smix reverse command with negative rule weights.
• Correct the servo command to five arguments.
• Rename servo mixer input 29 to Fixed Value and update platform types and preset names.
• Document that servo rules, like motor rules, are read only up to the first empty slot, and that a short mmix line keeps the weights it parsed despite the error.
• mmix/smix act on the selected mixer profile.
• FLAPERON mode is available whenever has_flaps is ON (mixer.c, fc_msp_box.c).

Bicopter, dualcopter, singlecopter and helicopter tables remain excluded: the wiki marked them untested and the corresponding Configurator presets are disabled with empty mixer tables. A dedicated section explains the missing verified mixes.

Also

docs/05-core-features/flight-modes-standard.mdx stated flaperon_throw_offset as default 250, max 400. The firmware defines default 200, range 50 to 450 (settings.yaml, FLAPERON_THROW_MIN/MAX in servos.h), so that line is corrected too.

Validation

Merges cleanly into current master (git merge-tree). A local npx docusaurus build of current master merged with this branch passes (Node 22, versions.json limited to 9.1.0); its only warnings are the ones master itself produces (release notes directives, fwsetup and hardware-overview SSG). No PR previews exist on this repo.

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document custom mixes for exotic airframes

📝 Documentation 🕐 20-40 Minutes

AI Description

• Adds verified motor and servo mixes for uncommon multirotor and fixed-wing airframes.
• Documents current CLI syntax, safety checks, and unsupported configurations.
• Replaces the external wiki link with the maintained Docusaurus guide.

Diagram

graph TD
  A["Setup Guide"] --> B["Custom Mixes"] --> C{"Preset exists?"} -->|Yes| D["Load preset"] --> E["Adjust rules"] --> F["Bench test"]
  C -->|No| E

Loading

High-Level Assessment

The chosen approach is appropriate: keeping the verified examples in a dedicated Docusaurus page makes them searchable, build-validated, and maintainable alongside the related mixer documentation. Linking to the old wiki risks continued syntax drift, while embedding every example in the general mixer reference would make that page harder to navigate; excluding unverified mixes is also the safest choice.

Files changed (2) +383 / -1

Documentation (2) +383 / -1

06-mr-gettingstarted.mdxLink setup guidance to the local custom-mixes page +1/-1

Link setup guidance to the local custom-mixes page

• Replaces the external GitHub wiki URL with a relative link to the new Docusaurus custom-mixes guide while preserving the adjacent Mixer and Mixer Tab references.

docs/03-getting-started/06-mr-gettingstarted.mdx

custom-mixes.mdxAdd verified custom mixer guidance for exotic airframes +382/-0

Add verified custom mixer guidance for exotic airframes

• Adds worked mmix and smix configurations for uncommon multirotor and fixed-wing setups, with current CLI syntax, preset mappings, servo endpoint guidance, and bench-safety warnings. It also identifies unsupported or unverified configurations rather than reproducing obsolete mixer tables.

docs/06-advanced-features/custom-mixes.mdx

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Flaperon guidance uses the wrong range ✓ Resolved

Description

The custom-mixes page says flaperon_throw_offset defaults to 200 and accepts values from 50 to
450. The documented firmware setting instead defaults to 250 and has a maximum of 400, so users
following this page may expect the wrong deflection or try an unsupported value.

Code

docs/06-advanced-features/custom-mixes.mdx[R95-97]

+Input `14` is called `Flaperon Mode` in the Configurator and `FEATURE FLAPS` in the firmware settings.
+It is `0` until `FLAPERON` flight mode is active, and then carries the `flaperon_throw_offset` value, which defaults to 200 and can be set between 50 and 450.
+`FLAPERON` mode is only offered when the platform type is `AIRPLANE` and `has_flaps` is `ON`.

Evidence

The new guide claims a default of 200 and a range ending at 450, while the repository's existing
flight-mode documentation identifies the same setting as defaulting to 250 with a maximum of 400.

docs/06-advanced-features/custom-mixes.mdx[95-97]
docs/05-core-features/flight-modes-standard.mdx[311-318]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The custom-mixes guide gives an incorrect default and range for `flaperon_throw_offset`: it says 200 and 50–450, while the repository's flight-mode documentation says the default is 250 and the maximum is 400.
### Fix Focus Areas
- docs/06-advanced-features/custom-mixes.mdx[95-97]
- docs/05-core-features/flight-modes-standard.mdx[311-318]
### Recommended Fix
Update the custom-mixes sentence to state that `flaperon_throw_offset` defaults to 250 and can be configured up to 400, matching the existing flight-mode documentation.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[Raffi1202]

/agentic_review

[qodo-free-for-open-source-projects]

Code review by qodo was updated up to the latest commit 40327bb

[Raffi1202]

/agentic_review

Please reassess the remaining flaperon range finding against the pinned firmware sources now linked in the page: https://github.com/iNavFlight/inav/blob/86a0441c0003466d54a7711e7240d8297c8d067f/src/main/fc/settings.yaml defines flaperon_throw_offset with default 200; https://github.com/iNavFlight/inav/blob/86a0441c0003466d54a7711e7240d8297c8d067f/src/main/flight/servos.h defines FLAPERON_THROW_MIN=50 and FLAPERON_THROW_MAX=450. The documented 200 and 50–450 match those sources. Changing them to 250 and 50–400 would contradict this firmware version.

[qodo-free-for-open-source-projects]

Code review by qodo was updated up to the latest commit be70b9b