Input options

Input Options

There are several ways to provide input to the controller. The best choice depends on whether you are using a flight controller, telemetry sensors, sBus, or direct RC channels.

Flight Controller

controller msp

MSP Protocol

The best option, and the one that provides the most functionality, is the MSP protocol.

  • iNav provides the most functionality.
  • ArduPilot provides almost as much functionality, but a few advanced messages are not provided.
  • BetaFlight will also work, but it is missing some airplane-specific messages.

Use the following wiring diagram to hook up to a flight controller. Use the CLI command input m to set MSP protocol. MSP is the default input option.

Mavlink

Mavlink on ArduPilot provides almost as much functionality as MSP. Mavlink on iNav is much more limited.

Use the CLI command input v to set Mavlink protocol.

SmartPort (S.Port) Protocol

controller sport

If you do not have a flight controller but do have SmartPort sensors, the controller can use whatever data is available.

  • You must have a receiver that is able to read the sensors.
  • You will need to tap into the S.Port line and feed it into the controller.
  • The S.Port update is much slower than MSP, but it can provide much of the same functionality as MSP when the correct sensors are installed.

Use the CLI command input p to set S.Port. Use input i for inverted S.Port.

sBus Protocol

controller sbus

The controller can also use the sBus protocol. It will use the 4 primary channels and feed them into the internal simulator. The simulator will do its best to estimate what should be displayed on the screens.

Use the CLI command input s to set sBus protocol.

RC Channels

controller rc

The controller can also take input from 2 RC channels: aileron and elevator. It will use the simulator, simulate the throttle at half, and keep the rudder centered.

Use the CLI command input r to set RC channel input. If you use RC channels, make sure they are 3.3V and not 5V.