Skip to content

Expose MTU onto the peripheral server - #161

Merged
kevincar merged 1 commit into
masterfrom
113-expose-the-ble-mtu-that-is-negotiated-between-central-and-peripheral
Dec 27, 2025
Merged

Expose MTU onto the peripheral server#161
kevincar merged 1 commit into
masterfrom
113-expose-the-ble-mtu-that-is-negotiated-between-central-and-peripheral

Conversation

@kevincar

Copy link
Copy Markdown
Owner

This is really a brute force and odd approach to the solution. Each backend obtains the MTU differently, and because data transfers are often initiated by the central, the MTU will default to None until some action is taken. On windows and MacOS, that action must be a subscription to a characteristic so that the MTU can be negotiated and exposed. On Linux, it is updated every read and write request.

This is really a brute force and odd approach to the solution. Each
backend obtains the MTU differently, and because data transfers are
often initiated by the central, the MTU will default to None until some
action is taken. On windows and MacOS, that action must be
a subscription to a characteristic so that the MTU can be negotiated and
exposed. On Linux, it is updated every read and write request.
@kevincar
kevincar merged commit 946316b into master Dec 27, 2025
9 checks passed
@kevincar
kevincar deleted the 113-expose-the-ble-mtu-that-is-negotiated-between-central-and-peripheral branch December 27, 2025 04:29
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.

Expose the BLE MTU, that is negotiated, between central and peripheral.

1 participant