1. Identify the actual camera and firmware mode
The reference MG880FM sheet lists GC8613, IMX415 and IMX335 as configuration possibilities. Ask for the exact sensor fitted to the evaluation sample and request the corresponding camera/firmware configuration. A product family supporting multiple sensors does not mean one shipped board supports all sensors without changes.
Its document lists 1080p at 60/90 fps and 720p at 120 fps, with H.264/H.265 encoder choices. These are configuration-dependent manufacturer values. In particular, high-frame-rate options can require a specific codec and sensor mode. Confirm the resulting image format and software build rather than assuming simultaneous availability.
2. Define the complete RF chain
Evaluate the transmitter and its intended ground receiver as a system. Confirm frequency band, antennas, connector type, polarization, usable channel plan and transmitter power. The MG880FM reference describes two 5.8 GHz IPEX antenna ports. RF output and allowed channels vary by region: check local regulations and certification evidence for the actual hardware.
The specification mentions a 16 km favorable line-of-sight figure, but no independent Telewoo measurement currently supports a general range promise. For a real project, set pass/fail thresholds for your own test environment and consider RF interference, antenna placement and receiver quality.
3. Budget for power and cooling
The documented input is 9–22 V DC with a manufacturer-stated peak up to 15 W. Account for supply transients, connector current, cable gauge and thermal airflow. The active fan and aluminum heatsink occupy space; keep the camera ribbon clear of propellers and hot components.
4. Check mechanical and electrical integration
The reference mainboard is 30.6 × 33 mm with a 25.1 × 25.1 mm mounting-hole pattern; the separate M12 camera module and ribbon affect packaging. Ask for actual drawing revisions, weight of the proposed BOM and connector mating parts. On the six-pin harness, power and UART are combined: do not mistake the two N pins for spare signals.
5. Decide what telemetry means for your system
Some deployments only need an OSD data feed, while others need bidirectional MAVLink connectivity to Mission Planner or QGroundControl. Write down the required message types, transports, forwarding path, baud rate and return-channel behavior. Compatibility must be demonstrated with the exact transmitter firmware, ground receiver and flight controller combination.
6. Request an evaluation plan instead of a headline claim
- Specify target aircraft, expected supply voltage and mounting space.
- Choose the image sensor, lens field of view and required frame-rate mode.
- Document the receiver hardware, antennas and legal radio operating conditions.
- Define telemetry/OSD requirements and acceptable end-to-end behavior.
- Agree on a bench-test checklist, sample BOM and acceptance criteria before buying in quantity.
Source: MG880FM manufacturer reference sheet, dated 11 Nov 2026. Regulatory eligibility, latency, usable range and support for specific firmware features require independent evaluation.