Mk3 no Bluetooth

Q&A for the RaceCapture Plug & Play - general hardware related usage and operation; for app related questions please post in the RaceCapture app section.

also see the <a href="https://wiki.autosportlabs.com/RaceCapture_Quickstart">RaceCapture quick start guide</a>
Post Reply
MrBanana
Posts: 1
Joined: Sat Oct 10, 2026 7:04 pm

Mk3 no Bluetooth

Post by MrBanana »

Hi Autosport Labs team,

The Bluetooth on my RaceCapture/Track MK3 won't come up. Bluetooth is enabled in the config, but the unit never detects the module. WiFi, GPS, CAN and IMU all work normally.

Unit details

Model: RaceCapture/Track MK3 (RCT_MK3)
Firmware: 2.24.1 (official, the latest release)
Purchased in 2022 from PFTuning

What I've tried

Confirmed the firmware is the latest release
Ran resetConfig from the USB console and rebooted. The behaviour didn't change.
Unplugged USB and vehicle power for 30 s and powered back up
Scanned from a phone. The unit's Bluetooth does / does not appear

Status over USB (getStatus / getConnCfg)


"bt":{"init":0}
"btCfg":{"btEn":1,"name":"","pass":""}
Setting the name and PIN with setConnCfg returns rc:1, but reading them back still gives blank values.

Debug log (setLogLevel 7, viewLog) after a reboot


[BT] Setting baudrate: 115200
[BT] Probing module JDY-31
[BT] Probing module HC-06
[BT] Detecting baud rate 230400
[BT] Setting baudrate: 230400
[BT] Probing module JDY-31
[BT] Probing module HC-06
[BT] Detecting baud rate 9600
[BT] Setting baudrate: 9600
[BT] Probing module JDY-31
[BT] Probing module HC-06
[BT] Could not detect device using known baud rates.
[BT] Failed to communicate with device.
[BT] Restoring to target baud: 115200
[BT] Failed to provision module. A client may already be connected.
No phone or other device was connected to it over Bluetooth during this test.

The module doesn't answer at any baud rate the firmware tries. That looks like a hardware fault to me, or possibly a module this firmware doesn't support. Could you advise on next steps or start a repair/RMA? I can send the full boot log or run other diagnostics if useful.

Thanks,
Will Koscielny
Post Reply