Stacked Smol unable to communicate with receiver

[Amelia-bun]

Stacked smols are unable to communicate with both Promicro and Holyiot receivers on the latest firmware version. Reads connection error; status 26. Stacked smols do not show up in the server as a result.

Trackers using the mochi pcb are able to communicate fine with both receiver types on the latest firmware.

Older firmware from the main branch in November does not have this issue, however it's worth noting that the now defunct before-clang branch had similar issues with stacked smols and receivers.

[Sacred-Shadow]

Same here:
Holyiot SlimeNRF Receiver Holyiot-21017
SlimeVR-Tracker-nRF-Receiver 0.6.9+0 (Commit 9892a021b4bc, Build 2025-12-07 13:05:31)
Board: holyiot_21017
SOC: nrf52840
Target: holyiot_21017/nrf52840

SlimeVR SlimeNRF Tracker ProMicro
SlimeVR-Tracker-nRF 0.6.9+0 (Commit 2656194, Build 2025-12-18 13:27:13)
Board: promicro_uf2
SOC: nrf52840
Target: promicro_uf2/nrf52840/spi

tracker:

pair
[00:01:25.368,377] �[0m<inf> esb_event: Pairing requested�[0m
[00:01:25.443,572] �[0m<inf> status: Cleared status: 2�[0m
[00:01:25.443,603] �[0m<inf> status: Status: 24�[0m
[00:01:25.443,603] �[0m<inf> esb_event: Pairing�[0m
[00:01:25.443,756] �[0m<inf> esb_event: Device address: 46D4BE7075F3�[0m
[00:01:25.443,786] �[0m<inf> esb_event: Checksum: 27�[0m
[00:01:26.444,519] �[0m<inf> esb_event: Paired�[0m
[00:01:28.055,328] �[0m<inf> esb_event: Tracker ID: 0�[0m
[00:01:28.055,358] �[0m<inf> esb_event: Receiver address: 5D91646D47FC�[0m
[00:01:37.168,365] �[1;33m<wrn> status: Connection error�[0m
[00:01:37.168,395] �[0m<inf> status: Status: 26�[0m

Receiver:

pair
[02:28:59.778,900] �[0m<inf> esb_event: ESB deinitialize requested�[0m
[02:28:59.779,022] �[0m<inf> esb_event: Deinitializing ESB�[0m
[02:28:59.779,083] �[0m<inf> esb_event: Initializing ESB, RX mode�[0m
[02:28:59.789,184] �[0m<inf> esb_event: ESB denitialize cancelled�[0m
[02:29:03.413,482] �[0m<inf> esb_event: RX Pairing Request�[0m
[02:29:03.413,787] �[0m<inf> esb_event: Added device on id 0 with address 46D4BE7075F3�[0m
>>> exit
exit
[02:29:37.948,883] �[0m<inf> esb_event: ESB deinitialize requested�[0m
[02:29:37.948,913] �[0m<inf> esb_event: Deinitializing ESB�[0m
[02:29:37.959,106] �[0m<inf> esb_event: Initializing ESB, RX mode�[0m
>>> list
list
Stored devices:
46D4BE7075F3

[SmilingEnchanter]

My terminal looks same as @Sacred-Shadow . Don't know how to fix the problem :(

[SmilingEnchanter]

My terminal looks same as @Sacred-Shadow . Don't know how to fix the problem :(

"same" means I am using the same version of the firmwares. I'll try the older ones.

[Jatoxo]

Until the automated builds are fixed, you can use my fork. I just uploaded a release with precompiled firmware for stacked builds
https://github.com/Jatoxo/SlimeVR-Tracker-nRF/releases/tag/v20251221

If this becomes outdated, you can ping me @Jatoxo here or on Discord or alternatively build my fork yourself. The only difference to building on main is applying an extra devicetree overlay as described here

[SmilingEnchanter]

Until the automated builds are fixed, you can use my fork. I just uploaded a release with precompiled firmware for stacked builds https://github.com/Jatoxo/SlimeVR-Tracker-nRF/releases/tag/v20251221

If this becomes outdated, you can ping me @Jatoxo here or on Discord or alternatively build my fork yourself. The only difference to building on main is applying an extra devicetree overlay as described here

Connects smoothly and works well. Thank you!

[Sacred-Shadow]

Can you say anything about this yet? @sctanf

Do we still need an issue in the SlimeVR Tracker nRF Receiver?
For us as users, it’s not entirely clear whether the issue is on the tracker side or the receiver side.