UAV payload integration: MAVLink, UART, S.BUS and Ethernet explained

A payload is only as useful as its connection to the aircraft. Before comparing sensors, an integrator needs three answers: how the payload is controlled, how the video reaches the operator, and how it is powered and mounted.

• 4Control interfaces
• RTSPThe professional video path
• 20–53 VDCRange on professional pods
• 11 → 40 WStatic to ranging peak

MAVLink, UART and S.BUS Carry the Commands

MAVLink is the richest option: a two-way protocol spoken by common autopilots that carries gimbal pointing, camera commands, and telemetry such as attitude and target coordinates back to the ground station. If your flight stack is PX4 or ArduPilot based, MAVLink integration gives the deepest control with the least custom work — integrating gimbal cameras with ArduPilot and PX4 covers the specifics, including the angle feedback that geotagging depends on.

Plain UART serial suits custom flight computers and companion boards: a documented command set over a simple wire. The quality of that documentation is what decides whether integration takes days or months, which makes it a supplier question as much as a technical one — see evaluating payload suppliers.

S.BUS, inherited from the RC world, maps gimbal and camera functions to transmitter channels. Sixteen channels on one wire keeps FPV-style builds light and makes the payload usable with nothing more than a standard radio.

Ethernet control rounds out the set on networked payloads, exposing the same functions over IP for platforms that already run an onboard network. Gimbal control interfaces compared covers the electrical characteristics of each, including CAN.

RTSP Over Ethernet Is the Professional Video Path

Multi-sensor payloads stream H.264 or H.265 video over RTSP, typically at 1080p, while recording to a local microSD card — U3 class up to 256 GB on current models. The network stream feeds ground software, video links and AI pipelines without extra converters, which is the whole argument for it.

That path also makes VMS integration straightforward on ONVIF-capable payloads, where the drone appears to a security system as another network camera — ONVIF and IP video on drone payloads covers the control-room case, and video encoding and streaming architecture covers H.264, H.265 and RTSP behaviour.

FPV-oriented gimbals take a different route entirely: variants built for DJI O3 and O4 air units or analog systems output video directly into that link. This is why the same gimbal model often ships in several link-specific versions, and why a mismatched variant does not connect at all rather than working badly — matching a gimbal camera to your FPV link maps the full variant set.

Choose the variant that matches the radio system you already fly, and standardise the fleet on one link before standardising on payloads. Doing it in the other order creates a spares and training problem that outlasts the decision.

Plan the Power Budget and Mounting Direction Early

Professional payloads accept a wide DC range, typically 20 to 53 VDC, so they run from common 6S to 12S packs. The AX gimbals sit lower at 7.4–26.4 VDC, and mixing the two groups without checking is how a payload meets a voltage it cannot survive.

Budget for peak draw, not idle. A ranging payload can jump from around 11 W static to 40 W when the laser fires, and a brownout at that moment costs you the measurement — which is the one you flew there for. Payload power budgets covers wiring that holds, and the published gaps across the line are wider than most integrators assume.

Interface	Carries	Best fit
MAVLink	Pointing, camera commands, telemetry back	PX4 and ArduPilot flight stacks
UART serial	Documented vendor command set	Custom flight computers and companion boards
S.BUS	16 channels to transmitter switches	FPV and RC-ecosystem builds
Ethernet / IP	Control and RTSP video	Networked platforms and VMS integration
Link-native video	Video into O3/O4/analog air units	FPV builds — variant must match

Mounting is the last check and the one that costs the most to get wrong. Most spherical payloads install downward or upward, and vertical-mount gimbal variants exist for airframes with unusual geometry. Confirm mechanical clearance across the full gimbal travel — roughly −120° to +40° of pitch and continuous yaw on flagship models — before you cut carbon.

A Planning Sequence That Avoids Rework

Three answers first, in this order, before any sensor comparison.

1. How is it controlled? Match the interface to who issues commands — pilot, autopilot or companion computer.
2. How does video reach the operator? Match the variant to the link you already fly, or plan the network path.
3. How is it powered and mounted? Check the voltage range against your pack, size for peak draw, and walk the full travel envelope.
4. Then compare sensors, having eliminated everything that cannot physically integrate.

Answering these first shortens the sensor comparison considerably, because a large share of candidate payloads fail one of them. The integration checklist covers the mechanical and electrical detail, and what buyers should ignore first covers keeping the remaining comparison honest.

The recurring lesson from integrations that went badly is that none of them failed on sensor choice. They failed on a connector, a voltage, a protocol document that did not exist, or a bracket that fouled at the yaw limit.

Related reading

• Video Encoding and Streaming Architecture
• Payload Firmware Architecture
• Gimbal Control Interfaces Compared
• Integrating Gimbal Cameras with ArduPilot and PX4
• ONVIF and IP Video on Drone Payloads
• UAV Payload Integration Checklist
• UAV Payload Power Budgets
• Matching a Gimbal Camera to Your FPV Link
• OP-90A — multi-sensor pod with ranging
• LX-9B — multi-sensor pod
• AX-20T — 46 g three-axis gimbal
• Pipeline Monitoring UAV Payloads
• Choosing a thermal payload for ArduPilot or PX4 aircraft
• Zenmuse H30T alternatives: DJI airframe or independent payload

FAQ

Which interface should I choose for an autopilot-based aircraft?

MAVLink, and specifically gimbal protocol v2 if the payload supports it. It carries pointing commands, camera control and telemetry back — including the angle feedback that photo geotagging and target geolocation depend on. Many serious integrations combine MAVLink for pointing with a vendor serial SDK for camera functions such as zoom, tracking and palettes, which the standard protocol does not cover.

Can I use one payload across FPV and networked platforms?

Not usually, because the video path differs at the hardware level. FPV variants output directly into a specific air unit, while networked payloads stream RTSP over Ethernet — these are not adapter-away from each other. Standardise your fleet on one video architecture before standardising on payloads; supporting both doubles spares, cabling and training for little gain.

How much power headroom does a ranging payload need?

Size for the peak, which is substantially above idle — a ranging payload can jump from around 11 W static to 40 W when the laser fires, and some published figures go higher. A brownout at the moment of ranging costs you the measurement you flew for. Give the payload a dedicated fused feed rather than an accessory rail shared with a video transmitter, and check the voltage range holds across the full battery discharge curve.

Questions about the technology? Talk to our engineers — we reply within 2 business days.