Module Setup & Field Guides
Preparation, firmware deployment and troubleshooting for every PINGEQUA RF / Wi-Fi module. Pick a module on the left — everything lives on one page, deep-linkable by anchor.
Flipper Zero用 5Ghost WiFi開発ボード – BW16 RTL8720DN デュアルバンド #
HW_IDFLIPPER-ZERO-5GHOST-BW16-EXTERNAL-ANTENNA▶01 · PREPPreparation Manifest
- Host Device: Flipper Zero
- Compatible Flipper Firmware: Official, Momentum, or Unleashed.
- Required App File: Download the latest 5ghost_wifi_lab.fap from GitHub Releases:
https://github.com/pingequalab/5ghost-wifi-lab
- Hardware Note: The PINGEQUA 5Ghost board ships preloaded. No wiring, soldering, or module flashing is required for first-time setup.
- Antenna Note: Tighten the external SMA antenna before use.
- SD Path: Copy the .fap file to /ext/apps/GPIO/ on your Flipper microSD card.
- Support Note: Built for the PINGEQUA 5Ghost BW16 board only. Other BW16 / RTL8720DN boards are not supported.
▶02 · SETUPHardware & Firmware Deployment
Power OFF your Flipper Zero.
Tighten the external antenna first, then align the 5Ghost board with the top GPIO header and seat it straight. Do not force or tilt the pins.
Power ON the Flipper Zero.
Download the latest 5ghost_wifi_lab.fap from GitHub Releases.
Copy it to your microSD card under /ext/apps/GPIO/.
On the Flipper, open: Apps → GPIO → 5Ghost WiFi Lab.
Start with Scan Wi-Fi or Channel Map to confirm the board is communicating normally.
The module firmware is already preloaded from the factory. Browser flashing is only needed for recovery, not for normal setup.
▶03 · DEBUGTroubleshooting Guide
ISSUE App does not appear in Apps → GPIO.
FIX Confirm the file name is 5ghost_wifi_lab.fap and that it was copied to /ext/apps/GPIO/ on the microSD card. Reinsert the SD card or reboot the Flipper if needed.
ISSUE Board is not detected after installation.
FIX Power OFF the Flipper, remove the board, and reseat it on the top GPIO header without tilting the pins. Make sure the external antenna is tightened correctly before use. This board is designed for the PINGEQUA 5Ghost BW16 hardware only; other BW16 / RTL8720DN boards may not work correctly.
ISSUE Deauth does not work on some networks.
FIX This is usually not a hardware fault. PMF / 802.11w and WPA3-protected APs can ignore deauth by design. 5Ghost is designed to flag these protected targets instead of failing silently.
ISSUE Handshake capture is empty or inconsistent.
FIX Select a 5 GHz target AP when capturing WPA/WPA2 handshakes. On this platform, 5 GHz is the reliable capture path.
ISSUE Module firmware needs recovery or the board stops responding.
FIX Open https://flash.pingequa.com/devices/bw16-5ghost in Chrome or Edge on desktop, or Chrome on Android. Connect the board by USB-C and click Flash. If auto-entry fails, hold BOOT, tap RESET, release BOOT, and try again.
Flipper Zero用 CC1101モジュール – 433 MHz Sub-GHz #
HW_IDCC1101-433-MHZ-RF-DEVELOPMENT-BOARD-FOR-FLIPPER-ZERO▶01 · PREPPreparation Manifest
- Hardware: CC1101 Sub-GHz GPIO module with external high-gain antenna.
- Variants: Standard, and a High-Gain edition tuned for 433 MHz — nominal 20 dBm output (verified 18.6 dBm) for longer range. Setup is identical for both.
- Firmware:
[CRITICAL]Unleashed (highly recommended) or other 3rd-party forks (Momentum / RogueMaster). - Firmware link: https://flash.pingequa.com/devices/flipper-firmware
- Note: Official firmware does not support external CC1101 modules via GPIO by default. Update firmware before installing.
▶02 · SETUPHardware & Firmware Deployment
- Power OFF your Flipper Zero.
- Align the module pins with the top GPIO headers.
- Insert gently but firmly; tighten the SMA antenna securely.
- Power ON. Path: Main Menu → Sub-GHz → Radio Settings → Module.
- Toggle from
[Internal]to[External]. - Flipper now bypasses the internal chip and uses the high-power CC1101 GPIO module.
- "Receive" or "Read" a known signal (e.g. a remote) to verify the extended range from the external antenna.
▶03 · DEBUGTroubleshooting Guide
ISSUE "External Module Not Found" or no signal.
FIX Re-check the [Module] setting in Sub-GHz Radio Settings — it must be set to External. Ensure you are on Unleashed or compatible firmware. Check the physical connection; no bent or misaligned pins.
Flipper Zero WiFi Board #
HW_IDFLIPPER-ZERO-WIFI-DEVBOARD-BLACK▶01 · PREPPreparation Manifest
- Hardware: ESP32-S2 Wi-Fi dev board with an 18-pin gold GPIO header (Black or Green — identical board).
- Firmware (board): ships pre-flashed with ESP32-Marauder — no flashing needed out of the box.
- Firmware (Flipper): Official, Momentum or Unleashed — all include the WiFi Marauder companion app.
- Note: the board provides the Wi-Fi radio; the Flipper runs the companion app over GPIO UART. Flipper Zero host NOT included.
▶02 · SETUPHardware & Firmware Deployment
- Power OFF your Flipper Zero.
- Align the 18-pin header with the top GPIO pins and seat the board firmly.
- Power ON — the board's onboard LED indicates power.
- On the Flipper: Apps → GPIO →
[ESP32]WiFi Marauder. - The companion app talks to the pre-flashed board over UART — no PC needed.
- Run a basic
[scanap](list access points) to confirm the board responds. - Captures (PCAP) are written to the Flipper SD card.
- To update or restore Marauder, use the official web flasher: https://flash.pingequa.com/devices/flipper-wifi-devboard-marauder
- Use Chrome / Edge, via USB.
▶03 · DEBUGTroubleshooting Guide
ISSUE Marauder app shows no response, or the board is not detected.
FIX Re-seat the board (no bent or misaligned pins). Confirm the board has power (LED on). Update the WiFi Marauder companion app from the Flipper app catalog so its UART protocol matches the board firmware.
Horizon 433 Pro #
HW_IDHORIZON-433-PRO-FLIPPER-ZERO-CC1101-MODULE▶01 · PREPPreparation Manifest
- Hardware: Horizon 433 Pro — 433 MHz Sub-GHz GPIO module for Flipper Zero, built on the E07-433M20S RF module with PA/LNA control and a 4-layer impedance-matched PCB.
- Antenna: external SMA connector — use an antenna matched to the 433 MHz band.
- Output: up to 20 dBm (module rated), PA/LNA controlled, for longer range.
- Firmware:
[CRITICAL]Momentum or Unleashed recommended for external CC1101 support. - Firmware link: https://github.com/DarkFlippers/unleashed-firmware
- Note: Official firmware does not support external CC1101 modules via GPIO by default. Update firmware before installing.
▶02 · SETUPHardware & Firmware Deployment
- Power OFF your Flipper Zero.
- Attach the 433 MHz SMA antenna to the module.
- Align the module pins with the top GPIO headers and insert gently but firmly. No soldering or flying wires.
- Power ON. Path: Main Menu → Sub-GHz → Radio Settings.
- Set the radio to
[External CC1101]. - Flipper now bypasses the internal chip and uses the Horizon 433 Pro.
[TX / PA]lights when the transmit path is active.[RX / LNA]lights when the receive path is active.
- Use Read / Read RAW / Frequency Analyzer on a known 433 MHz signal (e.g. a remote) to verify range through the external antenna.
▶03 · DEBUGTroubleshooting Guide
ISSUE "External Module Not Found" / "CC1101 not found" or no signal.
FIX In Sub-GHz Radio Settings, confirm the radio is set to [External CC1101] and CC1101 SPI is [Default 4]. Use Momentum or Unleashed firmware. Reseat the module on the GPIO header and check for bent or misaligned pins.
ISSUE Weak or short range.
CAUSE Antenna not matched to 433 MHz, a loose SMA connection, or nearby interference.
FIX Make sure the SMA antenna is fully attached and rated for 433 MHz; move away from sources of interference.
ISSUE Unstable behavior when connecting.
FIX Always power the Flipper OFF before seating or removing the board.
Flipper Zero用 NRF24モジュール – nRF24L01+ 2.4 GHz #
HW_IDFLIPPER-ZERO-NRF24-MODULE▶01 · PREPPreparation Manifest
- Functional specs: 2.4 GHz RF transceiver (GFSK). Sniffs and injects wireless HID packets (mice / keyboards).
- Core capabilities:
- Sniffing: capture hardware addresses of unencrypted 2.4 GHz wireless devices.
- Mousejacking: inject BadUSB payloads into vulnerable wireless receivers (e.g. Logitech Unifying).
- Scanning: 2.4 GHz spectrum interference analysis.
- Required firmware:
[CRITICAL]Momentum or Unleashed. Official firmware lacks the SPI drivers and GPIO apps. - App path: Applications → GPIO →
[NRF24 Sniffer / MouseJacker].
▶02 · SETUPHardware & Firmware Deployment
- Power OFF your Flipper Zero.
- Insert the NRF24 module into the GPIO headers, aligned to the correct pins (3.3V on Pin 9).
- Power ON the device.
- Path: Applications → GPIO →
[NRF24 Sniffer]or[MouseJacker]. - Ensure SPI mode is selected in the app if prompted.
- Run the Sniffer near a known 2.4 GHz GFSK device to confirm capture.
- If you see "Module Not Found", re-check firmware and pin seating (see Troubleshooting).
▶03 · DEBUGTroubleshooting Guide
ISSUE "NRF24 Module Not Found" error.
FIX Confirm you are on third-party firmware (Official FW will not work). Check for bent pins or debris in the GPIO headers. Ensure stable 3.3V power (Pin 9).
ISSUE Sniffer captures nothing.
CAUSE Most modern "Bluetooth" mice use BLE encryption that NRF24 cannot crack; this module is effective against older 2.4 GHz GFSK protocols (early Logitech, Microsoft, non-brand wireless mice). High-traffic Wi-Fi can also drown out the sniffer.
FIX Move closer to the target receiver.
GPS Module #
HW_IDFLIPPER-ZERO-GPS-MODULE▶01 · PREPPreparation Manifest
- Hardware: GPS + GLONASS module for Flipper Zero, built on the Quectel L86-M33. Receive-only — no transmitter.
[CRITICAL]Outdoor use only: GPS cannot receive satellites indoors. Use it outside in an open area with a clear view of the sky — away from windows, walls, and metal — or you will get no fix. This is normal for any GPS receiver.- App: Install the GPS NMEA app from the Flipper app catalog.
- App link: https://lab.flipper.net/apps/gps_nmea
- Firmware: Official or Momentum (Momentum also has a built-in GPS feature).
- Note: Uses the Flipper default GPIO pins 13/14 — no wiring changes and no pin remapping.
▶02 · SETUPHardware & Firmware Deployment
- Power OFF your Flipper Zero.
- Seat the GPS module on the top GPIO header in the correct orientation — default pins 13/14, 3.3V, GND. Do not force the pins.
- Power ON.
- Install the
[NMEA]GPS app from the Flipper app catalog (lab.flipper.net/apps/gps_nmea), or enable the built-in GPS on Momentum. - Open it: Apps → GPIO →
[NMEA]GPS. - No data on screen? Long-press
[Up]to set the baud rate to 9600 (the module default).
- Go outside to an open area with a clear view of the sky. This step is essential (see the outdoor note above).
- Keep the module still and wait. The on-board LED shows it is active.
- A cold first fix can take a couple of minutes — that is normal.
- After the first fix, the supercapacitor keeps your last position, so later restarts lock on in seconds.
▶03 · DEBUGTroubleshooting Guide
ISSUE No fix / no location shown.
CAUSE You are almost certainly indoors, or your view of the sky is blocked.
FIX Go outside to an open area, away from windows, walls, and metal. Give it a clear view of the sky and wait a couple of minutes.
ISSUE No data at all in the GPS NMEA app.
FIX Long-press [Up] in the app to set the baud rate to 9600, and confirm the module is seated on the default pins 13/14.
ISSUE First fix is very slow.
CAUSE A cold start with no stored data always takes longer.
FIX Stay outdoors with open sky and keep the module still. Later restarts are much faster thanks to the supercapacitor.
ISSUE Lost the fast-restart benefit after long storage.
CAUSE The supercapacitor holds for hours, not days.
FIX Do a normal first fix outdoors; restarts will be quick again afterward.
Flipper Zero用 RF Lab 2-in-1 – nRF24L01+ + CC1101 433 MHz #
HW_IDFLIPPER-ZERO-2-IN-1-RF-MODULE▶01 · PREPPreparation Manifest
- Compatibility: Flipper Zero (Momentum firmware recommended).
- Critical SPI config — Path: START → PROTOCOLS → GPIO PINS. Set
[NRF24 SPI]to[Extra 7](mandatory for this module). - Notice: Smart Auto-Switching enabled — no physical toggle needed.
▶02 · SETUPHardware & Firmware Deployment
- Power OFF your Flipper Zero.
- Carefully insert the module into the LEFT GPIO headers.
- Power ON the device.
- Path: Sub-GHz → Radio Settings → Module → select
[External].
- Path: Apps → GPIO → run MouseJacker or other NRF24 tools.
- If the app fails to launch, re-verify the SPI pin setting from STEP_01.
▶03 · DEBUGTroubleshooting Guide
ISSUE NRF24 Scanner / Jammer not working.
CAUSE These apps use hardcoded pin definitions in their current version. This is a software limitation, not a hardware defect — we are working with developers on compatibility updates.
ISSUE CC1101 "External Module Not Found".
FIX Re-check Sub-GHz settings so [External] is active. Inspect GPIO pins for alignment issues or debris.
Scout Lite #
HW_IDSCOUT-LITE▶01 · PREPPreparation Manifest
必要なもの
- Flipper Zero。Momentum ファームウェア推奨 — https://momentum-fw.dev — Marauder アプリ同梱で、GPS UART を GPIO 15/16 にリマップできる。ストックファームではこれらのピンをリマップできない。
- Scout Lite ボード用の microSD カード（FAT32）。Marauder はここに WigleWifi CSV を書く。カードは付属しない。
- Scout Lite ボードと Dualband SMA アンテナ。電源を入れる前にアンテナをねじ込む。
- Marauder を再フラッシュ / 更新するなら USB-C データケーブル。
知っておくこと
- Scout Lite は ESP32 Marauder プリフラッシュ済み — https://github.com/justcallmekoko/ESP32Marauder — ドックすれば wardriving はすぐ動く。
- Flipper 上のライブ wardriving ダッシュボードには SigRoam を入れる。最新ファイル: https://github.com/pingequalab/sigroam-wardriving/releases/tag/v0.3 — sigroam-0.3.fap を SD Card/apps/GPIO/ にコピー。SigRoam を ESP32 にフラッシュしないでください。
- このボード向けの専用 SigRoam スキャナファームウェアは開発中。まだ flasher にはない。出荷ユニットは Marauder のまま。
- オンボード ESP32-C5-WROOM-1U は 2.4 と 5 GHz Wi-Fi 6 をカバー。5 GHz は scan / enumeration のみ。
- Quectel L86-M33 GPS（GPS / GLONASS / Galileo）が記録した各ネットワークに座標を付ける。
- ボードは Flipper GPIO ヘッダから給電。RF フロントエンド保護のため、電源投入前にアンテナを付ける。
▶02 · SETUPHardware & Firmware Deployment
- Flipper Zero の電源を切る
- Scout Lite を GPIO ヘッダに合わせてしっかり押し込む
- Dualband アンテナを SMA コネクタにねじ込む
- FAT32 microSD カードを Scout Lite ボードに入れる — Marauder は WigleWifi CSV をここに書く。Flipper のカードではない
- 工場出荷の Marauder イメージはボードに残す。SigRoam は Flipper アプリであり、ESP32 フラッシュではない。
- https://github.com/pingequalab/sigroam-wardriving/releases/tag/v0.3 から sigroam-0.3.fap をダウンロード
- Flipper の SD Card/apps/GPIO/ にコピー
- Settings → System → Log Device を Off にする。ピン 13/14 はシステムログと共有。
- Apps → GPIO → SigRoam を開き、Dashboard へ行き、OK で開始。Official と Momentum で一つのファイル。
- 同梱 Marauder アプリが欲しければ Flipper Zero に Momentum をフラッシュ — https://momentum-fw.dev
- Flipper ネイティブ GPS アプリを使うなら GPS UART をマップ: MNTM → Protocols → GPIO Pins → NMEA GPS UART → Extra 15,16
- Marauder 経由の wardriving は、このマップの有無に関係なく位置を記録する — GPIO 15/16 は Flipper GPS アプリ専用
- Flipper 上: Apps → GPIO →
[ESP32]WiFi Marauder、それから Wardrive
- オンボード GPS は空が開けた場所が必要。室内では fix しない。車内ではボードをフロントガラス近くに。
- 行に GPS 座標が付くのは fix 後だけ。オープンスカイでのコールドスタートは1分かかることがある。
- 電源を切り、Scout Lite の microSD カードを抜いてパソコンまたはスマホで読む。
- ファイルは標準の WigleWifi CSV。https://wigle.net または公式 WiGLE アプリでアップロード。
- Scout Lite を USB-C でコンピュータに接続
- https://flash.pingequa.com/devices/scout-lite から ESP32 Marauder を再フラッシュ / 更新
- そのページは Marauder のみ。専用 SigRoam スキャナファームウェアはまだない。
▶03 · DEBUGTroubleshooting Guide
ISSUE Flipper GPS アプリが fix を出さない
CAUSE GPS UART が GPIO 15/16 にマップされていない、または空が見えないコールドスタート
FIX ピンをマップ: MNTM → Protocols → GPIO Pins → NMEA GPS UART → Extra 15,16。アンテナに空が見えるようにする — コールドスタートは1分かかることがある。Flipper GPS アプリが fix を出さなくても、Marauder と SigRoam の wardriving はボード上で GPS を記録し続ける。
ISSUE ネットワークが記録されない
CAUSE Scout Lite スロットに FAT32 microSD がない、または Wardrive / SigRoam ではなく普通の Scan を開始した
FIX FAT32 カードを Scout Lite ボードに入れる（Flipper ではない）。Marauder で Wardrive を開始するか、SigRoam Dashboard からスキャンを開始。座標が付くのは GPS が fix した後だけ。
ISSUE SigRoam が serial port is busy と言う
CAUSE Flipper Settings → System → Log Device がピン 13/14 を占有
FIX Log Device を Off にしてから SigRoam を開き直す。
ISSUE SigRoam を ESP32-C5 にフラッシュするのか？
CAUSE SigRoam は Flipper の .fap であり、ボードファームウェアではない
FIX SigRoam を ESP32 にフラッシュしないでください。sigroam-0.3.fap を SD Card/apps/GPIO/ にコピー。Marauder はボードに残す。https://flash.pingequa.com/devices/scout-lite のブラウザフラッシュは今も Marauder リカバリのみ。
ISSUE 5 GHz handshake を取れるか？
CAUSE ESP32-C5 の 5 GHz は scan / enumeration のみ
FIX Scout Lite は 2.4 GHz 専用ボードが見逃す 5 GHz ネットワークを出す。handshake キャプチャ自体は 2.4 GHz の作業。
ISSUE BeiDou は対応するか？
CAUSE L86-M33 は GPS、GLONASS、Galileo を追う
FIX これで世界中の WiGLE 級 fix に十分な測位になる。BeiDou は不要。
ISSUE Marauder アプリが Flipper に出ない
CAUSE ボードがしっかり座っていない、または ESP32 GPIO アプリのないファームウェア
FIX ボードをしっかり挿し直す。Momentum か [ESP32] WiFi Marauder を含むビルドを使う。または SigRoam を入れる — Official と Momentum で一つのファイル。
Hydra RF Series #
HW_IDCARDPUTER-ADV-HYDRA-RF-424▶01 · PREPPreparation Manifest
One module family, one setup. The Hydra RF 424 / 824 / 924 are the same board — only the CC1101 band tuning differs — so these steps apply to every model in the series.
- Models & bands:
[424]433 MHz ·[824]868 MHz (EU / Intl ISM) ·[924]915 MHz (US ISM). - Compatibility: M5Stack Cardputer ADV version ONLY. Using on Cardputer v1.1 or older causes detection failure and possible firmware errors.
- Radios: CC1101 (Sub-GHz) + nRF24L01+ (2.4 GHz), with AutoBand smart switching — no physical toggle.
- Firmware: Bruce 1.14 (recommended).
[NOTE]Avoid v1.15 — a known bug can reboot the Cardputer (e.g. during RF Scan); 1.14 is stable. Source: https://github.com/BruceDevices/firmware - For one-click flashing: a desktop with Chrome or Edge + a USB-C data cable (Safari / Firefox not supported).
- Docs (pin reference, setup guide, troubleshooting): https://github.com/pingequalab/cardputer-adv-hydra-rf
▶02 · SETUPHardware & Firmware Deployment
Our web flasher installs Bruce and then automatically writes AND verifies the Hydra RF pin config — no manual pin editing.
- Use Chrome or Edge on a desktop (Safari / Firefox are not supported) + a USB-C data cable (not a charge-only cable).
- Remove the SD card first — an old config on the card can interfere.
- Connect the Cardputer to the PC over USB-C and open https://flash.pingequa.com/devices/cardputer-bruce
- Click
[Connect]and pick the device serial port in the popup. The Cardputer enters flash mode automatically — no buttons. - Keep the default version 1.14, click
[Flash], and wait for the progress bar.
- After flashing, the page waits for the device to reboot, then automatically writes and verifies the Hydra RF pin config.
- It succeeded when the log shows
[Module config applied and verified]. No manual action needed.
- Reinsert the SD card, then dock the Hydra RF module onto the Cardputer ADV backplane.
- Open Bruce's RF tools. Set the CC1101 frequency for your model — RF → Frequency:
[433.00](424) ·[868.35](824) ·[915.00](924) MHz. - nRF24 (2.4 GHz): launch any NRF24 tool (e.g. Spectrum) and select SPI mode.
- Wait until the device reaches the Bruce main screen, then click
[Apply module config]on the flasher page to retry once. - If the reinserted SD card holds an old brucePins.conf, the device may show a config error — delete it or format the SD card.
- Manual pin reference (last resort): https://github.com/pingequalab/cardputer-adv-hydra-rf
▶03 · DEBUGTroubleshooting Guide
ISSUE Module not found, or a config error, after flashing.
FIX Once the device reaches the Bruce main screen, click [Apply module config] on the flasher page to retry. If the SD card holds an old brucePins.conf, delete it or format the card. Last resort — set pins manually: https://github.com/pingequalab/cardputer-adv-hydra-rf
ISSUE No serial port shows in the flasher picker.
FIX Use a USB-C data cable (not charge-only) and try a different port. Flashing works only in Chrome / Edge (desktop) or Chrome (Android).
ISSUE Failed to connect, or wrong chip detected.
FIX Unplug and replug the device, then click Connect again. Close any app holding the port (Arduino IDE, serial monitor).
ISSUE RF / Sub-GHz menus show no radio.
FIX The Hydra RF module must be plugged into the Cardputer ADV — without it there is no RF hardware to drive.
ISSUE Cardputer reboots unexpectedly (e.g. during RF Scan).
CAUSE A Bruce v1.15 firmware bug — not a hardware fault.
FIX Re-flash the stable Bruce 1.14 from the one-click flasher.
ISSUE Reboot during Record Raw or high-power TX.
CAUSE The Cardputer shared SPI bus can congest under high-speed traffic — a hardware limitation, not a module defect.
FIX Remove the SD card during Record Raw, or connect external USB-C power for long sessions.
M5Stack StickS3 用 RF Pack S3 – nRF24L01+ + CC1101 433 MHz #
HW_IDM5STACK-STICK-S3-RF-PACK-S3-V1-BLACK▶01 · PREPPreparation Manifest
- Host device: M5Stack Stick S3.
- Firmware:
[CRITICAL]Bruce v1.14 or later (Latest / Beta). - Flasher: https://flash.pingequa.com/devices/sticks3-bruce
- Warning: DO NOT use v1.12 or v1.13 — only v1.14+ has the SPI & power patches required for hardware recognition. If the module is not detected, check the version first.
▶02 · SETUPHardware & Firmware Deployment
- Align the pins and plug the RF board firmly into the back of your M5Stack Stick S3.
- CC1101 (433 MHz) — Path: RF → CONFIG → RF MODULE → select
[CC1101 (Legacy)]. - NRF24 (2.4 GHz) — no setup required; open the NRF24 menu and turn it on.
▶03 · DEBUGTroubleshooting Guide
ISSUE "CC1101 Not Found" error.
CAUSE Typical firmware mismatch — older versions fail to power the module via SPI.
FIX Use Bruce v1.14 or a newer Beta.
ISSUE Module unresponsive or freezing.
FIX Check the Stick S3 physical power switch (side) is ON. Re-plug the module so pins are aligned and not bent. For stable RF transmission, keep battery above 30%.
Stick RF 424 #
HW_IDSTICK-RF-424-MODULE▶01 · PREPPreparation Manifest
- Host device: M5Stack Cardputer / M5StickC Plus 1.1 & 2.
- Firmware:
[CRITICAL]latest Beta from https://flash.pingequa.com/devices/stickc-plus2-bruce - Firmware alert: DO NOT use v1.13 / v1.14 Stable — these have SPI bus timing issues on M5StickC / Cardputer hardware. The Beta includes AXP2101 power-management patches for 100% recognition.
- In the box: RF board, microSD interface, Grove cable.
▶02 · SETUPHardware & Firmware Deployment
- Insert the RF board into the SD slot of the Cardputer.
- Connect the board's GPIO pins to the Cardputer with the included Grove cable.
- CC1101 (433 MHz) — toggle the physical switch to
[433MHz]. Path: RF → CONFIG → RF MODULE → select[CC1101 (Legacy)]. - NRF24 (2.4 GHz) — toggle the physical switch to
[2.4GHz]; NRF24 functions are now active.
▶03 · DEBUGTroubleshooting Guide
ISSUE "Module Not Found" error.
FIX Re-verify you are on the latest Beta firmware. Ensure the Grove cable is firmly seated and the physical switch is in the correct position.
ISSUE Limited NRF24 jammer range.
CAUSE Low-power hardware design and 2.4 GHz anti-interference naturally limit range — a design characteristic, not a defect.
FIX For advanced config see https://github.com/pr3y/Bruce/wiki