Přeskočit na hlavní obsah

MAVlink (Pixhawk) Integration

The Beacon allows you to read sensor data from your MAVlink-compatible flight controller such as Pixhawk. Moreover, it can detect whether the drone is airborne or grounded and act accordingly by starting/ending the flight on your device.

The prerequisite for interconnection of Dronetag device and flight controller is having the right cable. Please order interconnection cable on our e-shop or make sure that you have compatible one by hand. All the wiring must be as described below.

Dronetag Beacon Extension Port

The connector on Dronetag Beacon is common JST SH 4-pin with UART interface with no flow control.

Pin #NameScheme ColorDescription
1VCCRedUART logic level, see instructions in chapter bellow
2UART RXGreenReceive of the Dronetag device (3.3V logic)
3UART TXBlueTransmit of the Dronetag device (3.3V logic)
4GroundBlackGround connection

Pixhawk Telem Port

Most MAVlink-compatible flight controllers (such as Pixhawk) use JST GH 6-pin connectors that can be configured as UART/Serial interface.

Pin #NameScheme ColorDescription
1VCCRedSupply from the flight controller (5V)
2UART TXGreenTransmit of the flight controller (3.3V to 5V logic)
3UART RXBlueReceive of the flight controller (3.3V to 5V logic)
4CTSGrayFlow control pin (3.3V to 5V logic)
5RTSGrayFlow control pin (3.3V to 5V logic)
6GroundBlackGround connection

Beacon Connected to Flight Controller

The way how to connect Dronetag Beacon to the flight controller differs based on hardware revision of the device. You can find the revision code on the label on both the device and the packaging. If you are not sure what hardware revision your Dronetag Beacon device has, please contact our support team at support@dronetag.com

For the successful integration of your Dronetag device with the flight controller, only pin UART RX (pin 2), UART TX (pin 3) and Ground (pin 4) must be always connected. VCC (pin 1) may or may not be connected based on hardware revision of the device (see the section below). Not following the instructions below may permanently damage your device and void the warranty.

Revision R2

Revision R2S

Connecting revision R2S

For this revision, pin 1 of the Dronetag Beacon extension connector is UART logic level VCC input. Supported logic level is in the range from 3.3 V up to 5 V. Dronetag Beacon extension connector pin 1 shall be connected to 3.3 V supply of the flight controller.

Connection example for R2S revision

Connecting revision R2 and others

In these revisions, UART logic level is set internaly by the Dronetag Beacon itself. Supported logic level is 3.3 V (5 V tolerant). Leave the pin 1 of the Dronetag Beacon extension connector unconnected.

Connection example for R2 revision and others

Caution
  • Never put any voltage greater than 5.5 V to pin 1 (VCC pin) on Dronetag Beacon side!
  • Always check that pin 1 (VCC pin) is handled correctly based on the hardware revision of the Dronetag Beacon
  • Always check that you wiring of UART TX/RX is as described above.
  • Ground pin must be always connected.

On the flight controller side, you must ensure that you selected following parameters on the UART/Serial port

  • 115200 baudrate
  • MAVlink 2 protocol

Last step is to setup MAVlink as GNSS input and optionally as trigger for starting/ending the flight.

  • Open up the Device Configuration
  • Select MAVlink option as GNSS input. The internal GNSS receiver will turn off.
  • If you want to have your flight state managed by the flight controller, enable MAVlink flight control option in General section

At this point, MAVlink data are read through Extension connector and broadcasted locally/send to Dronetag cloud. You can do a quick check if your integration was succesfull by disconnecting the Extension connector when you already have GNSS fix on your drone. GNSS LED which was previously green should turn into pulsing orange.

Caution
  • Dronetag flight can be only started when your drone has GNSS fix.