CORVON AI GCS

What you can ask Copilot to do

Speak or type a request. The examples below cover status checks, configuration, missions, and flight commands. Configuration changes and high-risk flight actions require your confirmation.

Checks before commands run

1. Phase 1

   Understand

   Copilot matches your request to a supported command or sequence of actions.

2. Phase 2 · you confirm

   Check & approve

   The app checks the required conditions. For high-risk actions, it shows the command and risk level, then waits for your approval.

3. Phase 3

   Execute

   The app runs the approved action, checks the result, and records it in a local action log.

• Separate permissions control what Copilot can read and what it can run. Tools outside those permissions are not offered to the model.
• Before each write, the app checks permissions, telemetry freshness, and safety conditions. It repeats these checks at every step of a command sequence.
• Writes are checked against the flight controller’s response. If the result cannot be confirmed, it is marked unverified.
• Available actions depend on the flight phase. During an in-flight alert, Copilot switches to read-only.
• A hard cap limits repeated action calls. If a request is unclear, Copilot stops and asks. Status answers cite specific telemetry fields.

Permission checks · operator approval · local action log

Copilot works within a defined set of commands. High-risk actions pause for your approval.

FLIGHT-LOG DIAGNOSIS

Find issues in your flight logs

Upload a PX4 .ulg or ArduPilot .bin file, up to 100 MB. The app checks the log for flight events and anomalies, then Copilot explains the findings. You can also retrieve logs over MAVLink without removing the SD card. Saved diagnostic summaries are encrypted at rest.

Enlarge

Segmentation

Splits the flight at each arm and disarm, then classifies how every segment ended: normal, hard landing, manual descent, or crash. Each verdict carries a confidence level, the evidence for it, and the evidence against.

Anomalies

GPS fix loss, voltage sag, high vibration, EKF innovation spikes, and (on PX4) actuator saturation, each with the measured value, the time window, and the threshold it crossed.

Firmware events

On ArduPilot, reads the failsafe, fence, EKF, and thrust-loss events the flight controller itself recorded, with the parameter values at the time.

Analysis limits

Findings state what the evidence supports and what it does not establish about a possible cause. They also identify checks that could not run, such as “EKF check skipped: data missing”.

Explanation

Copilot summarizes the findings with citations and notes where the evidence is incomplete.

Use the cited findings to investigate an incident. A diagnosis may be incomplete when the log lacks the required data.

Enlarge

MAVLINK WORKBENCH

Inspect and plot live MAVLink data

Inspect messages, plot signals, adjust message rates, and use the PX4 console.

Inspector

Browse every MAVLink message seen on the link, sorted by rate, name, or count, each with an Hz health badge. Expand fields, filter, pause and resume.

Charts

Plot up to 8 signals over a 10-second to 5-minute window. Gaps in received data stay visible. Send any inspector field to a chart.

Rates

Set message intervals or choose a preset, then check the measured receive rate in Hz.

Console

Use the PX4 NSH shell with command history. Input is disabled when the vehicle is armed or its armed state is unknown. The console is unavailable on ArduPilot.

Know when data is missing or unconfirmed

The interface distinguishes confirmed results, stale telemetry, and missing data.

• Parameter changes are marked successful only after confirmation from the flight controller. Unconfirmed writes do not replace cached values.
• Armed state shows “unknown” until the app receives confirmation.
• Telemetry values have individual freshness indicators: amber for stale data and red for lost data. Missing values appear as “—”.
• Calibration completion requires confirmation from the flight controller. A 120-second watchdog detects stalled calibration.
• Disabled command and setup buttons explain why the action is unavailable.

Check the reported status and telemetry before making a flight decision.

Use the ground station with or without Copilot

Enlarge

Enlarge

Enlarge

Built for CORVON flight-controller users, with support for other PX4 or ArduPilot vehicles over MAVLink. The app includes CORVON hardware specifications and a wiring helper, so Copilot can answer questions about your flight controller, GNSS module, and ESCs. Setting up a flight stack? See our user guides.