[Bug]: RAK12500 GPS not detected on RAK19001 — firmware only probes UART, never I2C #9909
Replies: 6 comments 5 replies
-
@mowaxuk, Welcome to Meshtastic! 👋Thanks for opening your first issue. If it's helpful, an easy way If you have ideas for features, note that we often debate big ideas We're very active on discord, Welcome to the community! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Please provide device logs to further diagnose the issue. If using Web Flasher, connect the device via USB, open the device console in the log output area, reproduce the problem, and share the logs. If using Meshtastic CLI, run: meshtastic --port --noproto, reproduce the problem, and provide the terminal output. Also, ensure context includes the steps to reproduce the issue and any expected vs actual behavior details. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I2C is not used for gps |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification! That explains a lot. Just to close the loop on why this was so confusing — the RAK documentation for the RAK12500 states that Slot A or Slot C should be used, which is what I had been following when I should have been following the mesh, but I went straight to the RAK docs first, my bad. The Meshtastic docs say Slot F. For reference: RAK docs (says Slot A or C): https://docs.rakwireless.com/product-categories/wisblock/rak12500/quickstart/ |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Category
Other
Hardware
Rak4631
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.15.567b8ea
Description
Hardware:
Base board: RAK19001 (Dual IO, 6 sensor slots A-F)
Core: RAK4630 (nRF52840)
GPS module: RAK12500 (u-blox ZOE-M8Q) in Sensor Slot A
SD card: RAK15002 in IO slot (SPI, no I2C conflict)
Firmware: 2.7.15.567b8ea VANILLA
Describe the bug:
The RAK12500 GPS module is not detected by Meshtastic firmware. gps_mode is set to ENABLED but gps_enabled persistently reports false and position returns empty {}.
Serial debug output via PuTTY (115200 baud) shows the firmware probing for GPS over UART only, cycling through all baud rates and chip families before giving up:
The firmware never attempts I2C detection. The u-blox ZOE-M8Q communicates over I2C, so it is never found.
Hardware confirmed working:
Flashing the RAK WisBlock Hardware Test firmware (WB_HW_Test_V1.1.11_H) immediately detects and communicates with the RAK12500, producing valid GNSS output. This confirms the module, wiring, and slot are all correct — the issue is specific to Meshtastic firmware.
Expected behaviour:
Meshtastic should probe for GPS over I2C on the RAK19001 sensor slots, as the RAK12500 uses the u-blox ZOE-M8Q which communicates over I2C. The 3V3_S power rail (controlled by IO2/GPIO34) may also not be being enabled by firmware, preventing the module from powering up before UART probing begins.
**
**
RAK4630 on RAK19001 base board
RAK12500 in Sensor Slot A
Flash Meshtastic 2.7.15 VANILLA
Enable GPS in position config
Observe serial debug — GPS probe attempts UART only and fails
Additional context:
GPS pin settings are all at 0 (rx_gpio, tx_gpio, gps_en_gpio) which is understood to be correct for RAK WisBlock builds per the RAK forum. This issue has also been discussed at https://forum.rakwireless.com/t/issue-with-rak19001-and-rak12500/16109
Relevant log output
Beta Was this translation helpful? Give feedback.
All reactions