Tools

Console and SSH

A collapsible workspace beside the map holds the tools, so they never replace the operational picture: the MAVLink console, an SSH terminal to the companion computer, and the plugins. A station that never uses the console or the SSH terminal can switch either tab off in Settings, Side panel.

The MAVLink console open in the right hand workspace next to the live map, listing timestamped messages with a command field underneath.
The MAVLink console next to the live map.

The MAVLink console

Your direct line to the aircraft.

  • Filter the live stream by text.
  • Read severity from the colour rather than hunting through level buttons: errors red, warnings amber, success green, your own commands in the accent colour, shell replies blue.
  • Pause freezes the view while still buffering behind it, so reading one message does not cost you the next fifty.
  • Tab completes commands, ↑ walks the history (kept across launches), and ? prints the whole command table.
  • Copy and Save hand you the visible lines for a bug report. The LOGS page in the left rail exports the whole session's transcript.

Console commands

Corvus's own commands work on both stacks:

CommandWhat it does
helpAsk the backend which commands it accepts.
arm, disarmArm or disarm the vehicle. Arming is still refused unless the autopilot is satisfied.
mode HOLDSet a flight mode by name.
takeoff 10Take off to the given height above ground in metres (10 when left out).
landLand at the current position.
rtlReturn to launch.

The PX4 shell

On PX4 a set of shell commands is passed to NSH, the autopilot's own shell, over SERIAL_CONTROL, and its answers come back in blue:

CommandWhat it does
listener sensor_combinedStream a uORB topic.
top, tasksTasks and their CPU load.
freeFree memory.
dmesg, boot_logThe boot and kernel log.
perfPerformance counters.
hrtHigh resolution timer information.
shell <command>Send any other NSH command exactly as typed, case included, for example shell param show MPC_*.

ArduPilot has no such shell. On an ArduPilot link these commands are left out of ? and of Tab completion, and typing one anyway is answered with a sentence saying why.

For the shell itself, with its prompt, top redrawing in place and Ctrl+C to stop a running program, open the NuttX Console plugin, which is installed separately.

SSH terminal

Two SSH sessions during a flight: one to the companion computer in the side panel and one to the payload computer in a floating window over the map.
One SSH session in the side panel, a second in a window of its own over the map.

A real terminal into an onboard companion computer, not a command box. Every keystroke goes straight to the remote shell, so top, vim, sudo password prompts, colour output and Ctrl+C all behave as in any other terminal, and the prompt you see is the machine's own. The remote side is told the terminal's actual size.

Full screen and pop-out

The panel is only a few hundred pixels wide, so there is a full screen button next to the connection name (Shift+Esc leaves it; plain Esc belongs to whatever is running), and a pop-out button beside it that opens the same session in a terminal window of its own. Both show one shell: what you type in either reaches it, what it prints appears in both, and it lays itself out for the one you are typing in.

Saved connections

Connections are saved by name, with password or key file authentication, so reconnecting is one click. Beside each one:

  • the arrow connects it if needed and opens it in a terminal window of its own instead of in the tab,
  • the pencil edits its address and login, and is where you delete it. Deleting asks first, and closes the session if it is open.

Saved connections are also managed under Settings, SSH Connections, and are what the launcher plugins use to start programs. How host keys are checked is described under Network and security.

Suggest a change to this page