CORVON
USER GUIDE · REV A · 2026-09-22

CV0850 Ground Station
and ToF Configuration

CV0850
GROUND STATION
USER GUIDE

Remove propellers before bench setup. Use MAVLink output from the module for PX4 / ArduPilot and MSP output for INAV / Betaflight. UART4 and TELEM 2 are examples: use the port actually wired to the module. On ArduPilot 4.7+, MAVx identifies the MAVLink channel, not the SERIALx port number. Verify the channel mapping before changing options. Screenshots illustrate the UI and are not proof of flight validation; names and available features depend on the installed firmware build.

01/MODULE INSTALLATION GUIDE

Module Installation Guide

CV0850 module installation orientation for INAV and APM/PX4 firmware
02/PX4 CONFIGURATION

PX4 Configuration

STEP 1

Open the tool and select Vehicle Configuration;

Open QGroundControl and select Vehicle Configuration
STEP 2

Set MAV_1_CONFIG to TELEM 2 and save;

Set MAV_1_CONFIG to TELEM 2
STEP 3

Click “Tools,” then click “Reboot Vehicle”;

Reboot Vehicle from the Tools menu
STEP 4

Set MAV_1_MODE to Normal and save;

Set MAV_1_MODE to Normal
STEP 5

Set SER_TEL2_BAUD to 115200 8N1 and save it;

Set SER_TEL2_BAUD to 115200 8N1
STEP 6

Optional height-fusion setup: leave EKF2_RNG_CTRL unchanged for the communication check in step 8. The illustrated Enabled setting enables continuous range fusion; choose it only after assessing the installed PX4 version, mounting, reliable sensor range and flight conditions. This is not a required step for receiving sensor messages.

Example: EKF2_RNG_CTRL options
STEP 7

Optional height reference: EKF2_HGT_REF = Range sensor is intended only for operation over a flat surface within the reliable range of a downward-facing sensor. Terrain changes move the local height reference. Keep the existing height reference for the communication check; do not copy this setting as a general flight configuration.

Example: EKF2_HGT_REF options
STEP 8

After the configuration is completed, restart the flight controller. You should be able to see the DISTANCE_SENSOR and OPTICAL_FLOW_RAD messages in the MAVLink Inspector page of QGC. It's fine as long as there is a change in the values. Note that the messages displayed on the QGC are sent by the flight control. The message frequency is not the same as the data frequency of the sensor. This frequency is determined by the Settings of the flight control and the speed of the data link, and is mainly used for observation. The number of the message frequency is not important.

Open MAVLink Inspector in QGroundControl
View DISTANCE_SENSOR values in MAVLink Inspector
View OPTICAL_FLOW_RAD values in MAVLink Inspector
03/APM CONFIGURATION

APM Configuration

STEP 1

In Mission Planner, set the corresponding serial port baud rate SERIAL4_BAUD to 115(115200), and set the options parameter according to the firmware version: for 4.7 and later, use MAVx_OPTIONS and enable bit 1 (mask 2, disable MAVLink forwarding) while preserving other bits; for 4.6 and earlier, use SERIALx_OPTIONS and enable bit 10 (mask 1024, private MAVLink channel) while preserving other bits. Then set the serial port protocol value SERIAL4_PROTOCOL to 1(Mavlink1). Click "Write Params" to save;

Mission Planner SERIAL4 parameter settings
STEP 2

Set the optical flow FLOW_TYPE value to 5 and save it;

Set FLOW_TYPE to 5
STEP 3

Set the RNGFND1_TYPE value to 10 and save it;

Set RNGFND1_TYPE to 10
STEP 4

Restart the flight controller after enabling the rangefinder. For ArduPilot 4.7 and later, set RNGFND1_MAX to 8 and RNGFND1_MIN to 0.02 (metres). For 4.6 and earlier, set RNGFND1_MAX_CM to 800 and RNGFND1_MIN_CM to 2 (centimetres). Set RNGFND1_ORIENT to 25 only for a downward-facing installation. Save the settings. Screenshots show the older parameter names.

Set RNGFND1_MAX_CM, RNGFND1_MIN_CM, and RNGFND1_ORIENT
STEP 5

On the status page, you can see the values of rangefinder1, opt_m_x, opt_m_y, and opt_qua.

View rangefinder and optical flow values on the status page
04/INAV CONFIGURATION

INAV Configuration

STEP 1

Open the Ports interface, enable the MSP function for the corresponding serial port (we are connected to UART4),Select a baud rate of 115200,save, and restart.

Enable MSP and select 115200 for UART4 on the INAV Ports page
STEP 2

In the Configuration interface, set the Rangefinder option and the Optical flow option to MSP, save and restart. If the configuration is correct, you can see that the Sonar indicator light and the Flow indicator light on the main interface are on.

Set Rangefinder and Optical flow to MSP in INAV Configuration
STEP 3

Set the Debug data to optical flow data in the CLI interface;

set debug_mode = FLOW_RAW

Entering the "save" command will save and restart.

Set optical flow Debug data in the INAV CLI
STEP 4

In the Sensors interface, check the Sonar option and the Debug option; If configured correctly, it can be seen that the waveform and the X value are changing.

Check Sonar and Debug data on the INAV Sensors page
05/TOF / OPTICAL FLOW BETAFLIGHT CONFIGURATION

ToF / Optical Flow Betaflight Configuration

STEP 1

Switch ToF to MSP mode.

STEP 2

On the Ports page, enable MSP for UART4, then save and reboot.

Betaflight Ports page with MSP enabled for UART4
STEP 3

Enter the following commands in CLI, one line at a time, and save:

set rangefinder_hardware = MTF01P set opticalflow_hardware = MT feature RANGEFINDER feature OPTICALFLOW save
Betaflight CLI with ToF and optical flow configuration commands
STEP 4

View rangefinder data:

set debug_mode = RANGEFINDERsave

VIEW DATAOn the Sensors page, view Sonar - cm, Raw Altitude, and Calc Altitude.

Betaflight Sensors page showing rangefinder data
STEP 5

View optical flow data:

set debug_mode = OPTICALFLOWsave

VIEW DATAOn the Sensors page, view Quality and Raw flow rates X/Y.

Note

debug_mode can display only one data type at a time. Switch modes to view rangefinder and optical flow details.

Betaflight CLI with OPTICALFLOW debug mode
Betaflight Sensors page showing optical flow data