Progressive 3-step workflow

Analyze Parameter File

Upload the current .param or .parm file, optionally add symptom context, and get a bench-first verdict before another retest.

Props off before actuator or output testing.

Step 1 · File inputChoose the current .param or .parm file and confirm the quick parse summary before analysis.

Step 2 · Symptom contextChoose the primary symptom so the tool can rank the most relevant fault lanes first.

Step 3 · Output displayStart with the safety verdict, top three likely causes, and immediate props-off action.

Step 1 · File input

Problem aircraft parameter file

No file selected

Client-side file handling

Parameter files are parsed locally inside your browser; no raw configuration files are uploaded to Arimota servers during this self-service analysis.

The reference file is a troubleshooting guide, not a copy source.

Compare with a similar reference file

Known-good reference parameter file

No reference file selected

Step 2 · Primary symptom

Optional note

Saved result files keep the findings you export; Arimota does not retain the raw parameter upload when you use the self-service tool. On supported Chromium browsers, the first save can write into VTOL Review Results inside your chosen Arimota pCloud folder.

Learn how this works Method, references, diagrams, watchlists, and saved case studies Optional details

What the tool checks before it suggests another test.

This review follows the normal fixed-wing QuadPlane setup order: confirm the VTOL stack is enabled, verify orientation and outputs on the bench, check tilt or forward-thrust geometry, then use short logged retests instead of speculative changes.

Official ArduPilot references are built in.

The page carries a curated embedded ArduPilot VTOL reference set and ranks the most relevant official pages for each symptom and finding.

QuadPlane and VTOL detection come first.

QuadPlane support only exists after Q_ENABLE is enabled. If the file is not really a fixed-wing VTOL or 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-order or PID advice.

Output mapping tells the real aircraft story.

Servo functions, hover-motor outputs, forward-thrust outputs, tilt outputs, and reversals often explain more than a raw diff count, especially on 4+1 and tilt-rotor aircraft.

Transition geometry is a flight gate.

A front motor that is not truly vertical in VTOL mode, or a 4+1 forward-thrust lane that is mapped wrong, can look like a tuning problem while actually being a geometry or output 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.

Aircraft and parameter visuals

Open the layout and geometry reference cards only when you need them.

Tilt-rotor layout

Confirm both tilt lanes agree on vertical thrust, neutral angles, and the direction each servo should travel before transition logic matters.

Lift-plus-cruise / 4+1 layout

A 4+1 file should clearly separate hover-motor ownership from the forward-thrust output. If those lanes blur together, the file story is already wrong.

Motor direction check

Motor order and spin direction are still first-pass crash checks. A pretty tune cannot save a motor lane that is pushing the wrong way.

Servo direction and tilt geometry

Tilt-servo direction errors masquerade as tuning trouble all the time. Verify neutral geometry, travel direction, and endpoints on the bench first.

Flight controller orientation

If the controller thinks forward is right, every downstream correction lane becomes suspect. Orientation is a gate, not a footnote.

Hover-to-forward transition and comparison logic

The baseline aircraft is there to narrow the search, not to grant blind permission to copy settings into different geometry.

VTOL database watchlists

Prebuilt hover, transition, and fixed-wing offender lists stay here so they do not block the primary safety path.

Ready when the file is

Step 3 · Output display appears after validation.

After analysis, the first screen stays limited to the safety verdict, the top three likely causes, and the immediate props-off action. Full diagnostics, output maps, references, and debug trace stay collapsed until you ask for them.

Safety verdict

Waiting

Pending

Run the tool to generate the current call.

Do not fly until the items below are bench-checked with props removed.

Symptom –

Current ranking lane.

Problem aircraft Not loaded

Required

Reference Not loaded

Optional

Findings 0

0 problem rows parsed.

Orientation gate Pending

Shown after analysis.

Output map gate Pending

Shown after analysis.

Verified parameter evidence is shown directly. Any likely consequence is labeled as an inference.

Top likely causes

Check these before tuning

Next action

Start props-off output check

The first action stays limited to the highest-risk bench checks.

Show full checklist

0 / 0 steps checked

Pending

Bench gate unopened

Run an analysis first.

0 pass 0 fail 0 pending

View all differences Grouped remaining findings after the top three safety issues 0 more issues

Open this only when you need the full technical trail.

View output map Read the aircraft from the actuator map Optional details

This is often the fastest way to see when the file story and the real aircraft no longer match, including hover motors, forward-thrust outputs, tilt lanes, and control surfaces.

View matched references Embedded VTOL references behind the current review Optional details

Run an analysis to see which embedded VTOL references best match the current symptom and findings.

Run an analysis to surface related PDF/manual links from the embedded ArduPilot crawl data.

View diagnostics Debug trace, state summaries, and file-picker details Optional details

The page keeps a rolling client-side event log here for file-picker and analysis troubleshooting. The same trace is bundled into the saved result report.

No debug entries yet.

View full report Saved report contents and export behavior Optional details

The saved full report includes the verdict, grouped findings, output map, matched references, checklist state, and raw debug trace. It does not retain the raw uploaded parameter files.

Use Download report after analysis to save the generated review. On supported Chromium browsers, the same export can still write into VTOL Review Results when direct folder access is available.