-
-
Notifications
You must be signed in to change notification settings - Fork 2
Hardware Compatibility
The Flipper's onboard radio is BLE-only and cannot do Wi-Fi monitor mode. Flock cameras are found most reliably by the Wi-Fi probe requests they send trying to phone home, so all Wi-Fi work runs on a separate ESP32 board. If you're only getting BLE-side results with no ESP32 attached, that's expected, not a bug.
Any ESP32 Flipper board works:
- Wi-Fi Dev Board
- ESP32 Marauder boards
- ReksLab Tri-Board
- Bare WROOM / WROVER modules
- Xiao ESP32-S3
Each can run either Marauder firmware (existing, unmodified) or the project's Companion firmware — see Features & Board Modes for what each mode unlocks. Companion firmware flashes from the Flipper itself via ESP32 Firmware, no computer required.
| Device | Flipper port | Pins |
|---|---|---|
| ESP32 | USART | 13 (TX) / 14 (RX), 3V3, GND |
| GPS | LPUART | 15 / 16 |
The ESP32 and an optional GPS module run at once, on separate UARTs. Ports and bauds are configurable in Settings for boards with nonstandard pinouts.
A GPS module isn't required to run FlipDeFlock, but turning GPS on in Settings enables geotagging on detections, the Flock Map, and the Locator's "strongest here" note. GPS is off by default; a cold outdoor start typically takes 30–90 seconds to get a fix, and indoors it may never lock.
Board-level troubleshooting (UART conflicts, baud mismatches, ESP32 flasher error
codes) is covered in Troubleshooting and, at full length, in
docs/TROUBLESHOOTING.md
in the repo.