Skip to content

Devdoc: the BLE notification packet loss was a firmware bug - #6

Merged
robdobsn merged 1 commit into
mainfrom
docs/ble-notification-loss
Oct 25, 2026
Merged

robdobsn merged 1 commit into
mainfrom
docs/ble-notification-loss

Conversation

@robdobsn

Copy link
Copy Markdown
Owner

devdocs/fs-over-serial-ws-ble-plan.md said that replies by notification lost a packet from messages of 4 KB or more (seen from Windows), which is why RaftCLI keeps replies on indications.

That was a firmware bug, fixed in robdobsn/RaftSysMods#12. When notifications used up NimBLE's packet buffers, the firmware passed NimBLE a null buffer, which NimBLE takes to mean "send the characteristic's value" (empty) while reporting success.

The update notes:

  • RaftCLI needs indications only for firmware up to RaftSysMods 1.27.0.
  • With fixed firmware, notifications reached 20-30 KB/s, against about 8 KB/s for downloads by indication, so notifications for downloads might be worth measuring.

Docs only.

🤖 Generated with Claude Code

Replies by notification lost a packet from messages of 4 KB or more. That was RaftSysMods passing NimBLE a null
buffer when its pool ran out (fixed after 1.27.0), not Windows. Notes when RaftCLI still needs indications, and
that notifications for downloads might be worth measuring.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robdobsn
robdobsn merged commit 805706b into main Oct 25, 2026
6 checks passed
@robdobsn
robdobsn deleted the docs/ble-notification-loss branch October 25, 2026 18:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant