UAVCAN is supported in the following APM firmwares:
- ArduPlane 3.2.1 and newer
- ArduCopter 3.3rc1 and newer
Mission Planner is a ground control station for Plane, Copter and Rover. It is compatible with Windows only and can be used on Linux using mono. Mission Planner can be used as a configuration utility or as dynamic control supplement for your autonomous vehicle.
To download and install software please refer to the relevant documentation for details.
Mission Planner is a Windows-only application. You can use APM Planner on Linux. To download and install APM Planner please refer to the relevant documentation for details.
You can also run Mission Planner on Linux under Mono.
Mono, the open source development platform based on the .NET Framework, allows developers to build cross-platform applications with improved developer productivity. Mono’s .NET implementation is based on the ECMA standards for C# and the Common Language In Common Language Infrastructure.
The below instructions show how to install Mission Planner on Linux using mono.
Add the Mono repository to your system
Add yourself to dialout group on Ubuntu - be sure to replace username with your actual username in Linux.
Download the zip version of Mission Planner.
Create folder and extract the zip file.
Launch Mission Planner.
Since Zubax GNSS 2 can be powered directly from the bus, the electrical connections are quite simple:
- Connect Zubax GNSS 2 with Pixhawk using the appropriate cable. In case you’re using a non-redundant CAN interface (which is the only available option for Pixhawk v1), only CAN1 must be used, leaving CAN2 empty.
- Terminate the CAN bus using the termination plug.
Configuring Pixhawk with APM firmware
Open Mission Planner application.
Attach Pixhawk with computer using the micro USB cable and then click on
Open the tab
CONFIGRATIONS then select
Full Parameter List and search for CAN parameters.
Turn on CAN and UAVCAN stack by setting the parameters
CAN_P1_DRIVER to 1.
In order to make APM receive measurements from an UAVCAN-interfaced GNSS receiver, set the parameter
GPS_TYPE to 9.
Click on button
Write Params to write all parameters to the controller. Disconnect serial port and reboot flight controller.
GPS will may take several seconds to get locked. You can check the status by clicking on tab
GNSS has an onboard compass and barometer attached to the UAVCAN bus. To use the GNSS compass follow these instructions below.
Make sure Zubax GNSS and PX4 are aligned (use arrow markings) as shown below.
Open the tab
INITIAL SETUP then select
HW ID and search for compass on UAVCAN bus. As shown in the image below, GNSS compass has ID3.
Open the tab
INITIAL SETUP then select the
Primary Compass to
Compass3 and select parameters
Use this compass and
Externally mounted .
Now perform calibration until you will get indication
MAG_CALL_SUCESS as shown below.
After that your external compass is ready to use.
First we need to enable a barometer on GNSS.
Zubax GNSS is equipped with a command-line interface (CLI) exposed over a serial port that provides access to the device’s internal command shell. Refer to the relevant documentation for details.
To use command-line interface attach GNSS to computer using a USB interface.
GNSS will appear as COM port.
Open COM port under the following configurations.
- Baud rate: 115200
- Word length: 8
- Parity: None
- Stop bits: 1
Command-line interface parameters:
- Line ending: CR+LF (0x0D+0x0A,
- Local echo: Off
- Local line editing: Off
Execute the following:
Once enabled Mission planner will automatically detect a barometer on GNSS and set it as a primary barometer.
To check the number of barometers on board. Open the tab
FLIGHT DATA then select tab
Status. It will appear that two barometers are detected. One barometer is on PX4 and other on the GNSS module.
To set other barometer as the primary one. Change the parameter
GND_PRIMARY to 1.
ArduPilot supports the MAVLink protocol for communication with Ground Stations and Companion Computers. You can use Mavlink Inspector for debugging or checking the status of a vehicle. Refer to the relevant documentation for details.