Emlid Reach M2 — GNSS Positioning and Camera Events for UAV Mapping

Reach M2 is a 35 g multi-band GNSS module for UAV integration, supporting RTK or PPK positioning, RINEX logging with camera events and position output for compatible systems. It is an onboard integration component, not a self-contained pole-survey receiver.

Technical content reviewed against official sources · 16 November 2026
Emlid Reach M2 GNSS module for UAV integration.
Reach M2 onboard GNSS module. Manufacturer product reference image.
WORKFLOW ARCHITECTURE01 — 04
01AIRCRAFT INTEGRATION
02GNSS + EVENT LOG
03PPK / RTK
04GEOTAGGED IMAGES

Observed data, configuration and quality evidence remain attached through handover.

Where Reach M2 for UAV integration fits in the working system.

M2 is intended for aircraft and navigation integrations where size, mass, power, antenna placement and electrical interfaces matter. For mapping, a camera hot-shoe or compatible event signal can associate image exposure timing with GNSS observations for subsequent geotagging.

Integration is an engineering task. Aircraft power, autopilot interfaces, antenna ground plane and placement, camera triggering, electromagnetic interference, cable routing and fail-safe behaviour must be assessed for the exact build. A module specification does not establish compatibility with every UAV or camera.

Compact hardware with explicit interfaces.

GNSS
184 channels; current documentation lists GPS/QZSS, GLONASS, BeiDou and Galileo multi-band signals.
Dimensions and mass
56.4 × 45.3 × 14.6 mm; 35 g module weight. Antenna, cabling and integration hardware are additional design considerations.
Logging and rate
RINEX logging with events and GNSS update rates up to 10 Hz under the documented configuration.
Corrections and output
NTRIP/VRS/RTCM3 correction inputs and NMEA/LLH/XYZ position outputs for compatible integrations.
Interfaces
USB, UART and event interfaces, with documented power requirements. Camera hot-shoe accessories and antennas are scoped separately.
Storage
16 GB internal storage listed in current manufacturer documentation.

From exposure event to photogrammetric input.

01 / Engineer the installation

Confirm mechanical mounting, regulated power, antenna location, camera trigger, autopilot interface and aircraft electromagnetic compatibility.

02 / Test on the ground

Verify GNSS logging, base/reference logging, event registration and time synchronization before flight. Trigger test images and inspect the recorded events.

03 / Fly and retain the dataset

Keep base and rover logs, images, event/MRK information, antenna details and mission notes together under consistent naming.

04 / Process in Emlid Studio

Compute the event positions and geotag the matching images. Review solution coverage and event-to-photo counts before mapping.

05 / Reconstruct and check

Process imagery in suitable photogrammetry software and evaluate control, checkpoints, offsets and output quality.

Different hardware for different roles.

Reach M2 for UAV integration: Different hardware for different roles.
RequirementReach M2Reach RS4 / RS3Reach RX2
Primary roleOnboard UAV/navigation moduleBase and rover field surveyingCompact field rover
Integrated survey-pole housingNoYesYes
Camera-event integrationSupported event workflowNot the primary purposeMobile-device integration rather than UAV hot-shoe role
RINEX loggingYes, with eventsYesConfirm current rover workflow and project need
Typical output useGeotagged drone imagery and navigation positionsSurvey features, base corrections and controlGIS features and supported mobile capture
Integration burdenAircraft-specific engineeringField kit and correction architectureCorrection source and mobile-device setup

Resolve these items before procurement.

Aircraft and autopilot

Confirm electrical, UART/autopilot, mounting and firmware requirements for the exact aircraft rather than relying on a generic “compatible drone” statement.

Antenna and interference

Plan antenna type, cables, sky view, ground plane and separation from interference sources. Validate under operating conditions.

Camera and shutter events

Confirm hot-shoe or trigger signal, voltage/interface requirements and that each exposure creates one usable event.

Operations and compliance

Integration changes can affect aircraft mass, reliability and approvals. The module itself does not confer flight authorisation or regulatory acceptance.

Prototype the integration before scaling it.

Easepect can scope the positioning, base/reference, event logging and photogrammetric processing route alongside your aircraft integration specialist. A ground-tested prototype and representative mapping dataset should precede fleet deployment.

Training should cover logs, event verification, Studio processing and downstream QA as well as field recovery when no events or incomplete observations are discovered after a mission.

Before choosing Reach M2 for UAV integration.

No. M2 is an onboard GNSS module for UAV and navigation integrations. RS4 Pro, RS4, RX2 and RS3 are the primary field-receiver options presented in this microsite.

Not sure which Emlid receiver suits your project?

Tell us what you are surveying, your operating environment and required deliverables. Model selection is optional; Easepect can help identify a suitable hardware and software workflow.