VTOL Parameter Comparison Dashboard
Compare two ArduPilot VTOL parameter files side by side and see the differences most likely to affect stability, transition behavior, tilt geometry, servo direction, output mapping, and controller response. This dashboard is built to shorten the time between “something is wrong” and a sensible bench-test plan.
What this page actually helps you do
This dashboard is designed to compare two similar VTOL aircraft configurations side by side. One aircraft is known to fly well, while the other shows unstable forward-tilt behavior. The goal is to isolate parameter differences that may explain the instability before further flight testing.
Bench-first diagnosis beats blind copying
Parameter differences can point toward likely fault lanes, but they are not proof by themselves. The board helps prioritize orientation, tilt-geometry, output mapping, transition, and failsafe checks before anyone starts copying tune values into the wrong airframe.
What you can learn before opening the toolbox
The current comparison is centered on the available parameter exports. Flight logs, bench video, and servo direction checks would strengthen the diagnosis further, but this page already makes the highest-risk configuration differences visible in one place.
Primary comparison lanes
Flight controller setup
Board orientation, frame assumptions, output order, and control-direction mismatches that can create immediate instability.
Q modes and transition behavior
QuadPlane and VTOL transition settings that influence forward tilt, handoff timing, and mixed hover-to-forward-flight behavior.
Motor tilt and servo outputs
Tilt-servo direction, endpoints, output assignment, and control-response patterns that can push thrust the wrong way in hover.
Attitude control and tuning
PID, attitude, and rate settings that may amplify a setup issue after the mechanical or orientation layer has already gone wrong.
Airspeed, throttle, and failsafes
Throttle logic, airspeed dependencies, and failsafe triggers that can change how the aircraft behaves during takeoff or transition.
EKF, GPS, compass, and receiver assumptions
Navigation, sensor, and radio assumptions that matter when the airframe is otherwise close but still behaves unpredictably.
Known-good baseline versus unstable aircraft
Reference aircraft
Known good aircraft: Heewing Ranger T1 VTOL. The current dashboard treats this setup as the flight-worthy reference configuration, not as a guarantee that every value should be copied directly.
Problem aircraft
Problem aircraft: ZOHD Altus VTOL. The reported failure symptom is a forward tilt or runaway attitude response that ends in unstable flight or a crash before the aircraft is safely controllable.
Shared hardware assumptions
Current comparison notes assume similar supporting hardware such as RadioMaster XR4 ExpressLRS receivers, comparable GPS modules, and a RadioMaster Pocket transmitter, while still respecting airframe-specific differences in geometry and output mapping.
Working goal
Use the board to identify the most likely configuration causes before repair, rebuild, or retest. This is a triage and verification tool, not a replacement for props-off bench checks or cautious follow-up flight work.
Open the live responsive comparison board
The embedded tool below is the working board. It reflows for desktop, tablet, and mobile so you can review the same comparison findings without switching to a different page. Use the known-good reference to narrow the fault lane, not to bulk-copy settings into a different geometry. If the interactive board fails to load, the fallback note below points to the safest next step.
Fallback note: If the interactive board does not render, reload the page first. If it still fails, use the contact path below and request a VTOL parameter review with the known-good and problem-aircraft parameter files attached.
Request VTOL ReviewHow to use the comparison board safely
- Load the known-good parameter file first so the baseline aircraft behavior stays anchored to a real flying setup.
- Load the problem-aircraft parameter file and review the highlighted differences before changing anything on the airframe.
- Prioritize high-risk VTOL, servo, attitude, transition, receiver, and failsafe parameters over low-risk tune noise.
- Generate a short change list instead of bulk-copying values across different airframes.
- Apply changes carefully, one group at a time, and keep a full parameter backup before each round.
- Bench test all motor and servo outputs with props off before attempting restrained hover or transition tests.
Suggested meta description: Compare ArduPilot VTOL parameter files for Ranger T1 and ZOHD Altus aircraft. Identify configuration differences affecting tilt, transition, stability, servo outputs, and flight safety.
Do not treat parameter edits as harmless
- VTOL parameter changes can cause loss of control, property damage, or injury.
- Always back up the current parameters before changing anything.
- Change one group at a time so the root cause stays traceable.
- Bench test all servo and motor outputs with props off.
- Verify failsafes, flight modes, orientation, and control direction before flight.
- Perform cautious test flights only in a safe area after the bench gate is cleared.
Need another airframe reviewed?
Send the known-good file, the problem-aircraft file, and any flight logs or bench notes that already exist. That gives the next review a faster, cleaner starting point than trying to reconstruct the failure after another crash.
For the fastest follow-up review, include both parameter files, firmware versions, airframe names, and any flight logs or bench-test notes that already exist.