Hello @Alex-Kushleyev , This is exactly what we needed ... thank you for turning the combined flip + GNSS-fix driver around so fast! Confirming our plan against your docs: We're on the encoded (ISP) path ... large_encoded for the pilot's low-latency FPV feed, not MISP ... so the ISP should pull the reversed bayer from the flip sensormodule and debayer correctly (no R/B swap). We'll run the version-agnostic combo: the flip sensormodule + en_rotate = true, plus maxRAWSizes=20 in camxoverridesettings.txt. Bit rate: going with 2088 Mbps. Our GNSS is a Septentrio mosaic dual-antenna running moving-baseline heading, so GPS L1 integrity is critical for us ... your analysis showing 2088 sitting ~10 MHz off L1 center with only a 1–2 dB drop is exactly the margin we need. We'll keep our FPV mode clear of the three forced-2200 modes (staying 1080p ≤120 fps). We'll validate by logging the Septentrio C/N0 and satellite count with the camera streaming vs. off, in representative daylight (noting your point that under-exposed frames worsen the interference). One quick check: for our single hires IMX412 on the M0173, is the default i2c 0x34 the right choice, or is there a scenario where we'd want the 0x20 variant? I'll report back the before/after GNSS numbers once we've tested ... happy to share the data if it's useful. Thanks again, John

@JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

Wanted to check in again. Any advice on swapping spektrum RC for ghost atto on voxl2?

This is the commit that I'm planning to propagate: https://github.com/modalai/px4-firmware/commit/c4fd40afc9f0c79a83a633023013f11b1185cf23

Hey @alex-kushleyev, good to know it holds up like that under load, and thanks again for the reply. Two things I'm trying to pin down on the Mini: Power. Can a USB port on the VOXL Mini actually supply around 2-2.5 W, and can it do that on one port while a small USB camera runs on the other? Or should I plan to power those externally? Extra camera slot. From the D0013-V2 CAD the imager board looks like 5 DF56 coax connectors with 4 used (EO + dual AR0144 + Boson+), and the Lepton is on the M0187 SPI adapter so it's off the CSI bus. Is that spare coax connector wired to a usable CSI lane, and would voxl-camera-server take a 5th sensor (an M0161) there without a custom config? Thanks, Eyal