Skip to content
Eric Stockenstrom edited this page Oct 29, 2020 · 2 revisions

ESP32 and ESP8266 only!

Mav2PT reads Mavlink telemetry from one of these sources

  • Serial port or
  • Bluetooth or
  • WiFi or
  • SD/TF Card

translates it to the FrSky DIY (passthrough) protocol and streams it through a serial port to S.Port/F.Port

In addition, it can then stream a Mavlink telemetry downlink to

  • Serial port or
  • Bluetooth or
  • WiFi or
  • WiFi and BT simultaneously and
  • SD/TF Card

In config.h #define macros are used to select the FrSky port type.

If "No FrSky Port support needed" is selected, like the example below, then all the telemetry switching functionality remains, and Mav2PT becomes a configurable telemetry router or switch. All FrSky related settings are removed from the web interface.

// Choose either S.Port or F.Port or None

#define FrSky_Port_Type 0 // No FrSky Port support needed "Mavlink Switch"

//#define FrSky_Port_Type 1 // S.Port

//#define FrSky_Port_Type 2 // F.Port v1/v2 FrSky ISRM/ACCESS capable transmitters and receivers only

For all the uplink sources and downlink destination I/O types to become available for selection in the web interface, ensure that they are un-commented as below. This will make the relavent run time code available for selection in the web interface.

//=================================================================================================

// D E F A U L T U P L I N K ( F C ) S E T T I N G S

//=================================================================================================

// Choose only one of these default Flight-Controller-side I/O channels

// How does Mavlink telemetry enter this translator?

#define FC_Mavlink_IO 0 // Serial Port (default)

//#define FC_Mavlink_IO 1 // BlueTooth Classic - ESP32 only

//#define FC_Mavlink_IO 2 // WiFi - ESP32 or ESP8266 only

//#define FC_Mavlink_IO 3 // SD Card / TF - ESP32 only

//=================================================================================================

// D E F A U L T D O W N L I N K ( G C S ) S E T T I N G S

//=================================================================================================

// Choose only one of these default GCS-side I/O channels

// How does Mavlink telemetry leave this translator?

// These are optional, and in addition to the F.Port telemetry output

//#define GCS_Mavlink_IO 0 // Serial Port - simultaneous uplink and downlink serial not supported. Not enough uarts.

//#define GCS_Mavlink_IO 1 // BlueTooth Classic - ESP32 only

//#define GCS_Mavlink_IO 2 // WiFi - ESP32 or ESP8266 only - auto selects on ESP8266

#define GCS_Mavlink_IO 3 // WiFi AND Bluetooth simultaneously. DON'T DO THIS UNLESS YOU NEED IT. SRAM is scarce! - ESP32 only

// NOTE: The Bluetooth class library uses a lot of application memory. During Compile/Flash

// you may need to select Tools/Partition Scheme: "Minimal SPIFFS (1.9MB APP ...) or similar

#define GCS_Mavlink_SD // SD Card - ESP32 only - mutually inclusive with GCS I/O

//#define FPort_To_SD // SD Card - ESP32 only - mutually inclusive with F.Port

The web interface will now look like this:

Setup the Uplink and downlink as required, save and reboot.