---
title: 'mmE-Loc: Precise Drone Landing via Event Camera & Radar'
url: https://www.emergentmind.com/topics/mme-loc
type: topic
---

# mmE-Loc: Precise Drone Landing via Event Camera & Radar

Searching arXiv for the cited paper and closely related baseline work.
arxiv_search(query="mmE-Loc Facilitating Accurate Drone Landing with Ultra-High-Frequency Localization", max_results=5, sort_by="relevance")
Searching for event-camera drone localization and radar-camera fusion baselines mentioned in the source material.
arxiv_search(query="Falanga event camera drone localization arXiv", max_results=10, sort_by="relevance")
arxiv_search(query="milliEye frame camera radar IoTDI 2021 arXiv", max_results=10, sort_by="relevance")
arxiv_search(query="radar only tracker Zhao ICRA 2021 drone localization arXiv", max_results=10, sort_by="relevance")
arxiv_search(query="event camera radar fusion localization arXiv", max_results=10, sort_by="relevance")
mmE-Loc is a ground localization system for precise drone landing that combines an event camera with an mmWave FMCW radar in order to satisfy the simultaneous requirements of high spatial precision, high update rate, and low end-to-end latency during descent guidance. It is introduced in "mmE-Loc: Facilitating Accurate Drone Landing with Ultra-High-Frequency Localization" [2507.09469] as a response to the sampling-frequency mismatch between conventional frame cameras and radar: frame cameras operate at $\leq 50$ Hz with exposure time $>20$ ms, whereas mmWave radar can operate at up to $200$ Hz or more. The central design choice is to replace the frame camera with a bio-inspired event camera that reports per-pixel brightness changes asynchronously with millisecond latency and effectively samples at kHz rates, then to fuse event-stream image information and radar depth measurements through two modules, Consistency-instructed Collaborative Tracking and Graph-informed Adaptive Joint Optimization, for accurate landing-site localization.

## 1. Problem setting and operating requirements

mmE-Loc is formulated for real-time localization of descending drones by a ground platform that must guide the vehicle to a designated landing spot. The stated landing requirement is stringent: the pad should place drones within a few centimeters, specifically $\leq 10$ cm, of a charging port to avoid damage or safety risks [2507.09469]. The control-side requirement is similarly explicit: drone flight controllers typically require pose updates $\geq 150$ Hz to maintain stable descent trajectories under closed-loop control, while sensing and computation should introduce only a few milliseconds of latency, ideally $<10$ ms.

The system addresses a specific systems bottleneck. Conventional frame cameras are too slow relative to mmWave radar, so naïve fusion forces the overall update rate down to the camera rate. mmE-Loc therefore targets both throughput and accuracy simultaneously rather than treating sensor fusion only as a perception problem. A common misconception is that radar-camera fusion is limited primarily by estimator design; the reported formulation instead identifies sensor-rate harmonization as a first-order systems constraint.

This suggests that mmE-Loc should be understood not merely as a multimodal localization algorithm, but as a co-design of sensing stack and inference stack. The event camera is introduced precisely because its asynchronous measurement regime better matches the temporal granularity of radar updates.

## 2. Sensor configuration and measurement models

The hardware configuration consists of a Prophesee EVK4 HD event camera in frame $E$ and a TI IWR1843 FMCW radar in frame $R$, with a known rigid transform $T_{ER}$ between them [2507.09469]. The event camera has resolution $1280 \times 720$ pixels and a $47^\circ$ field of view, and outputs events of the form $e=(x,y,t,p)$ with polarity $p \in \{\pm 1\}$. The radar operates at $76$--$81$ GHz and uses $3$ Tx and $4$ Rx antennas arranged in two orthogonal linear arrays. The coordinate frames $E$ and $R$ are static, whereas the object or drone frames $O$ and $D$ have unknown translations $t_{EO}(i)$ or $t_{ED}(i)$ at time index $i$.

For radar ranging, the transmitted FMCW chirp is
$$
S_{TX}(t)=\exp\bigl[j(2\pi f_c t+\pi K t^2)\bigr],
$$
and the received echo from a target at distance $D^i$ is modeled as a delayed, attenuated copy,
$$
S_{RX}(t)\approx \alpha S_{TX}(t - 2D^i/c).
$$
After mixing and low-pass filtering, the intermediate-frequency tone is
$$
S_{IF}(t)\approx \alpha \exp\!\bigl[j2\pi (K\,2D^i/c)\,t\bigr],
$$
with beat frequency $f_{IF}=2K\,D^i/c$, yielding
$$
D^i=\tfrac{c}{2K}\,f_{IF}.
$$
Angular estimation uses phase differences $\Delta\phi_x,\Delta\phi_y$ between adjacent receive elements spaced by $d$:
$$
\cos\theta_x=\tfrac{\Delta\phi_x\,\lambda}{2\pi d},\quad
\cos\theta_y=\tfrac{\Delta\phi_y\,\lambda}{2\pi d}.
$$
A unit direction vector is then formed as
$$
v^i = \bigl[\cos\theta_x\cos\theta_y,\;\cos\theta_x\sin\theta_y,\;\sqrt{1-\cos^2\theta_x-\cos^2\theta_y}\bigr]^T.
$$
Each radar point in radar coordinates is
$$
P^i_R=D^i\,v^i,
$$
and in camera coordinates
$$
P^i_E = T_{ER}\oplus P^i_R.
$$
A simple constant-velocity Kalman filter tracks $t_{EO}^i$ from successive $P_E^i$.

For the event camera, each pixel $(x,y)$ generates an event
$$
e^i = \bigl(x,y,t^i_{xy},p^i_{xy}\bigr)
$$
whenever its log intensity changes by a threshold $\Delta L$. A 3D point $X_E=(X,Y,Z)^T$ projects to image coordinates via the pinhole model
$$
\pi(X_E)=
\begin{bmatrix}
f_x\;\tfrac{X}{Z}+c_x\\[4pt]
f_y\;\tfrac{Y}{Z}+c_y
\end{bmatrix},
$$
using intrinsics $f_x,f_y,c_x,c_y$. Conversely, a bounding-box center $x^i$ can be back-projected along a camera ray if depth is known.

These models establish the modal complementarity exploited by mmE-Loc: radar contributes explicit depth and direction, while the event camera contributes high-rate image-plane information with millisecond latency.

## 3. Consistency-instructed Collaborative Tracking

Consistency-instructed Collaborative Tracking, or CCT, is the front-end module that jointly processes noisy high-rate radar and event outputs to identify the landing drone and extract basic 3D measurements [2507.09469]. Its logic is based on two cues: cross-modal temporal consistency and drone-specific physical signatures.

The temporal-consistency rule is simple but restrictive. Radar points and event-based detections produced by the same object should coincide in time within a few milliseconds and should lie along the same camera ray. The system projects each radar point $P^i_E$ into the event camera and retains only radar returns that fall within current event bounding boxes. Conversely, event clusters without support from any radar return are discarded. This makes CCT a mutual-gating mechanism rather than a unilateral proposal stage.

CCT also uses the physical structure of a descending multicopter. The drone is described as the only object producing both high-frequency micro-motion bursts from fast propeller rotation and axial-symmetry patterns in the spatial layout of events, with $4$- or $6$-propeller-arm structure. Over a short window $[i,i+\Delta i]$, events are binned into a $2$D histogram $H(u,v)$, for example with $5\times 5$-pixel bins. Candidate bins satisfy
$$
H(u,v)\geq H_{thresh},\quad \frac{\#(+)}{\#(-)}\approx 1,
$$
capturing dense bipolar event activity generated by true propellers. Connected-component clusters of these hot bins are then ellipse-fitted, and only clusters exhibiting one or more axes of symmetry consistent with $4$- or $6$-fold propeller layouts are accepted as drone.

The CCT output is a preliminary estimate of the drone translation $t_{ED}^i$ in the camera frame, together with a filtered event cluster center $x^i$ and the corresponding radar tuple $(D^i,v^i,U^i_E)$ for downstream fusion. The reported ablation results indicate that these physically informed filters are not incidental engineering details: CCT precision and recall are both above $80\%$ on both modalities, and the Radar + CCT configuration achieves error $0.178$ m with latency $7.3$ ms.

A plausible implication is that CCT functions as a domain-specific association prior. Instead of learning object identity from generic appearance, it encodes periodicity and symmetry that are specific to multirotor descent, which is particularly useful in cluttered landing environments.

## 4. Graph-informed Adaptive Joint Optimization

Graph-informed Adaptive Joint Optimization, or GAJO, is the back-end fusion and smoothing module. It estimates the set of drone poses
$$
\mathcal{X}=\{t_{ED}^k\mid k\in\mathcal{T}\}
$$
from measurements
$$
\mathcal{Z}=\{\,x^k,\;D^k,\;v^k,\;U^k_E\mid k\in\mathcal{T}\},
$$
by maximizing the posterior
$$
\hat{\mathcal{X}}
= \arg\max_{\mathcal{X}} p(\mathcal{X}\mid\mathcal{Z})
\propto p(\mathcal{X})\prod_k p(x^k\mid t^k)p(D^k,v^k,U^k_E\mid t^k),
$$
which yields a non-linear least-squares problem [2507.09469].

The factorization includes three types of terms. A prior factor imposes constant-velocity motion. An event likelihood factor penalizes reprojection error between $\pi(t_{ED}^k)$ and the image observation $x^k$. A radar likelihood factor incorporates consistency with measured range $D^k$, angle $v^k$, and frame-to-frame motion $U^k_E$. In operational terms, the graph combines geometric agreement with dynamic regularization.

Optimization proceeds in two stages. Inter-SAE Tracking performs an instantaneous update in which only the current pose $t_{ED}^i$ is optimized while the history is fixed; this runs at every event/radar update and is intended for low latency. Local Location Optimization performs batch reoptimization over a sliding window of the last $W$ poses,
$$
\{t_{ED}^{i-W+1},\ldots,t_{ED}^i\},
$$
every few frames or when the IMU-predicted pose diverges by more than $\Delta$.

GAJO is explicitly motion-aware. The drone’s onboard IMU acceleration is used to predict $t_{ED}^i$, and the deviation $\|\hat t^i_{ED}-t^i_{pred}\|>\Delta$ triggers the batch-window update. The window size $W$ is adjusted dynamically to balance drift correction against computation. Incremental inference uses an iSAM-style strategy, specifically the ISAM2 approach, so that only affected parts of the QR-factorized system are updated instead of relinearizing the entire window at each step. The stated worst-case per-step complexity is $O(M^2)$ for window size $M$, while typical incremental steps cost $O(M)$.

The ablation study positions GAJO as more than a conventional filter replacement. Radar + GAJO reaches error $0.139$ m with latency $11.5$ ms, and the full system improves error by $50$--$60\%$ relative to EKF or graph-only alternatives. The design therefore treats low latency and temporal consistency as joint optimization targets rather than separate concerns.

## 5. Empirical performance and robustness

The experimental campaign spans indoor and outdoor landing scenarios. Indoor experiments use an $8\text{ m}\times 8\text{ m}$ capture volume with Vicon motion capture at $1$ mm accuracy. Outdoor experiments use RTK-GPS reference at $2$ cm accuracy. The tested drones are DJI Mini 3 Pro, MAVIC 2, and M30T, covering varying size and propeller count. Conditions include bright and dim indoor lighting, moving balls and partial occlusions as background dynamics, slow descent and spiral trajectories at $30$ m, and velocities up to $1.5$ m/s. The reported dataset exceeds $30$ h and $400$ GB raw [2507.09469].

The evaluation compares mmE-Loc to four baselines: single-chip radar only + tracker [Zhao et al. ICRA’21], mono-event 3D localization with known geometry [Falanga et Sci. Robots ’20], stereo-event depth estimation adapted from Falanga et al., and a deep-fusion CNN using frame camera + radar [milliEye IoTDI’21]. The reported results indicate that mmE-Loc outperforms these baselines in both accuracy and latency.

| Setting | mmE-Loc | Baselines / note |
|---|---:|---:|
| Indoor 3D error, 90th percentile | $0.12$ m | $0.26$ m, $0.35$ m, $0.21$ m, $0.16$ m |
| Indoor 3D error, mean | $0.083$ m | reported with 90th-percentile values above |
| Outdoor average error (M30T) | $0.135$ m | $0.22$ m--$0.31$ m |
| End-to-end latency, indoor mean | $5.12$ ms | $10$--$31$ ms |
| End-to-end latency, outdoor mean | $6.8$ ms | $15$--$40$ ms |

Robustness results are reported across multiple nuisance factors. Across different drones, mmE-Loc maintains error $\leq 0.14$ m, whereas the baselines degrade heavily when geometry changes. Under dim illumination, mmE-Loc remains at $\leq 0.10$ m, while event-only methods degrade. Under heavy background clutter, average error is $0.13$ m, whereas radar-only and event-only methods drift to $>0.25$ m. By distance, the average error is $0.07$ m for $\leq 3$ m, $0.09$ m for $3$--$6$ m, and $0.10$ m for $>6$ m. Under partial occlusion of $25$--$50\%$, error remains $\leq 0.12$ m. By velocity band, the average error is $0.08$ m for $\leq 0.5$ m/s, $0.10$ m for $0.5$--$1.0$ m/s, and $0.11$ m for $1.0$--$1.5$ m/s.

Ablation results isolate the contribution of modality fusion and module design. Combining modalities reduces error by $50$--$60\%$ relative to radar-only or event-only systems. Radar + CCT yields error $0.178$ m at $7.3$ ms latency; Radar + GAJO yields $0.139$ m at $11.5$ ms; full mmE-Loc yields $0.083$ m at $5.12$ ms. Resource usage is modest: CPU utilization $\leq 18\%$ and memory $\leq 120$ MB on a $12$-core i7 with GTX1070 GPU.

These figures support a specific interpretation of the method’s contribution. The best operating point is not obtained by maximizing back-end sophistication alone or by maximizing front-end selectivity alone; it emerges from the interaction between a physically constrained front-end and an adaptive incremental graph back-end.

## 6. Scope, limitations, and relation to adjacent approaches

The reported system is explicitly limited to a single-pad scenario with one landing drone at a time [2507.09469]. Multi-pad or simultaneous-landing extensions require track ID management. It is also a ground-station deployment rather than an onboard localization system; an onboard analogue would require motion compensation in the event stream and denser radar returns. The experiments evaluate mmE-Loc as a standalone system rather than in tight coupling with GPS/RTK or visual markers, although such coupling is identified as a possible route to increased reliability in urban canyons.

Environmental boundaries are also clearly stated. Heavy rain, fog, and RF interference remain unevaluated. Generalization to other fast-rotating platforms, including VTOL multicopters, would require parameter tuning for propeller frequencies and symmetry. These are not incidental caveats: several parts of CCT rely directly on periodicity and axial symmetry, so deployment beyond the tested operating envelope is not guaranteed by the present results.

Within the broader multimodal localization landscape, mmE-Loc occupies a specific position. It is not a radar-only tracker, not an event-only estimator, and not a frame-camera-plus-radar deep-fusion pipeline. Its stated contribution is to use event cameras and mmWave radars at matched high rates in order to break the camera-radar throughput bottleneck, while also using physical priors and adaptive graph optimization to maintain millisecond-scale latency on commodity hardware. The reported evidence therefore supports viewing mmE-Loc as an integrated sensing-and-inference architecture for precision landing rather than as an isolated fusion module.

In summary, mmE-Loc couples ultra-high-rate event imaging with mmWave depth sensing, uses CCT to extract drone-consistent measurements through temporal consistency and propeller-aware structure, and uses GAJO to fuse these measurements into a smooth 3D trajectory at low latency. The resulting system is reported to satisfy the practical descent-guidance regime of $\geq 150$ Hz updates, few-millisecond latency, and sub-decimeter average localization error in the tested landing scenarios [2507.09469].

Source: https://www.emergentmind.com/topics/mme-loc