1. Confirm the six-pin connector before power-on
The MG880FM manufacturer's reference sheet describes one external six-pin harness for both DC power and flight-controller UART. The pins are marked V, G, R, T, N, N in that order when viewed as specified by the document. The two N pins are not connected on the reference board. Cable colors can vary between production runs: check the actual silkscreen and a meter rather than trusting colors alone.
| Pin | Mark | Function | Connect to |
|---|---|---|---|
| 1 | V | 9–22 V DC power input | Suitable regulated supply + |
| 2 | G | Ground | Supply return / common FC ground |
| 3 | R | Module receive (RX) | Flight-controller TX |
| 4 | T | Module transmit (TX) | Flight-controller RX |
| 5–6 | N | Not connected (reference) | Leave open |
Do not swap the supply pins or exceed 22 V. A 5 V-only UART signal should not be assumed tolerant of every serial logic level: confirm the actual module's electrical interface before connecting a new controller.
2. Configure and confirm the serial interface
Identify an unused UART on the flight controller and use a common signal ground. The manufacturer document suggests 115200 baud and MAVLink v1 or v2 for its reference firmware. Treat this as a starting point, not a universal requirement: both ends must agree on framing and baud rate, and the installed firmware must support the intended MAVLink flow.
With ArduPilot, select the correct SERIALx port and inspect its protocol and baud settings in Mission Planner or QGroundControl. Always consult the parameter meanings for your exact firmware version. On other autopilots, use the manufacturer's documented serial-port setup process.
3. Distinguish UART data from ground-side telemetry
A bidirectional UART connection does not automatically mean the wireless radio forwards MAVLink in both directions. Check whether the video device firmware receives serial bytes, whether a ground receiver exposes a compatible UDP/TCP or serial transport, and whether replies from the ground station can return to the flight controller. Verify message traffic in both directions separately.
4. Bench-test in a safe sequence
- Power off, identify the exact PCB revision and verify the full connector pin order.
- Check supply polarity and voltage with a meter; inspect fan airflow and cable routing.
- Connect V/G and cross R→FC TX, T→FC RX. Do not assume the two N pins are usable.
- Attach approved antennas before enabling RF transmission; never energize an RF transmitter with its antennas disconnected.
- Start with a nonflight bench test. Check video transport and ground-station MAVLink reception independently.
- Test ground-to-air commands or telemetry acknowledgments using an appropriate safety procedure. Do not rely on the link for aircraft control until behavior is validated and legal use is confirmed.
5. Typical integration failures
No telemetry: confirm cross-wiring, common ground, serial port choice and baud rate. Video but no return telemetry: check whether the ground receiver and firmware support a return data path. Unstable link: verify power headroom, antenna attachment, RF configuration and cooling. Unexpected OSD data: verify the actual serial protocol and version rather than assuming a default.
Source: MG880FM manufacturer's specification (document revision dated 11 Nov 2026). Network routing and MAVLink functionality are configuration-dependent and require on-device validation.