VTOL Parameter Evaluation Tool

VTOL Trouble Desk

Mission Planner parameter evaluation that actually starts with the files.

Upload the problem aircraft parameter export and, if you have one, a known-good reference file. The tool blocks bad file types, rejects non-QuadPlane inputs, and turns the parameter set into a bench-first VTOL troubleshooting plan instead of a blind copy session.

Upload files VTOL knowledge base Bench checklist

Hard Gates

The problem-aircraft file must be a real Mission Planner parameter export with a proper .param or .parm extension, valid KEY,VALUE rows, and Q_ENABLE=1. If QuadPlane support is not enabled, this tool will not evaluate it.

Bias

Known-good is optional. When it exists, the tool runs comparison mode. When it does not, the tool still audits the problem aircraft against the VTOL setup knowledge base and builds a step-by-step fix ladder.

Upload Tool

Load the problem aircraft first

The problem-aircraft file is required. The known-good file is optional and only sharpens the comparison lanes.

Required

Select a .param or .parm file.

This file drives the audit. Without it, nothing else matters.

Optional

Optional: select a .param or .parm file.

Helpful when the airframes are genuinely comparable. Not required for a useful bench plan.

VTOL Knowledge Base

What the tool is grounded on

This logic follows the normal QuadPlane setup order: enable the Q stack, verify orientation and outputs on the bench, confirm tilt geometry, then use short hover tests and logs instead of stacking speculative changes.

Q_ENABLE=1 is the gate.

QuadPlane support only exists after Q_ENABLE is enabled. If the file is not actually a VTOL/QuadPlane setup, the tool stops instead of pretending otherwise.

Orientation comes before tuning.

HUD attitude, board orientation, and wrong-way correction checks happen before any motor or PID advice.

Output assignment tells the real aircraft story.

Servo functions, motor outputs, tilt outputs, and reversals are higher-value clues than a raw diff count.

Tilt geometry is a flight gate, not a cosmetic detail.

A front motor that is not truly vertical in VTOL mode can look like a “tuning” issue while actually being a geometry problem.

Retests stay short and logged.

The tool favors minimal reversible changes, props-off confirmation, and short hover-only retests with logs after each pass.

Ready State

Nothing loaded yet

Upload the problem aircraft parameter file to start. The tool will validate the extension, parse the Mission Planner rows, confirm Q_ENABLE=1, and then switch into either audit mode or comparison mode depending on whether you also supplied a known-good file.