Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BLE - check MTU size ipad/robot #639

Closed
ladislas opened this issue Apr 4, 2022 · 1 comment · Fixed by #1356
Closed

BLE - check MTU size ipad/robot #639

ladislas opened this issue Apr 4, 2022 · 1 comment · Fixed by #1356
Assignees
Labels
01 - type: story Clear roadmap to implement a new feature, refactor code, etc.

Comments

@ladislas
Copy link
Member

ladislas commented Apr 4, 2022

No description provided.

@ladislas ladislas self-assigned this Apr 4, 2022
@ladislas ladislas added the 01 - type: task Something to do label Apr 4, 2022
@ladislas ladislas added this to the v1.0.0 milestone Apr 4, 2022
@YannLocatelli YannLocatelli modified the milestones: v1.0.0, Future releases Jun 8, 2022
@ladislas ladislas added 01 - type: story Clear roadmap to implement a new feature, refactor code, etc. and removed 01 - type: task Something to do labels Mar 1, 2023
@YannLocatelli
Copy link
Member

You can check BLE exchanges with PacketLogger (presented on WWDC 2019) [Link]

MTU proposed by iOS devices is 185, on robot side, it depend on mbed/cordio configuration. There is one for MTU desired, but another parameter set the reception buffer and that one also influence the negotiation of MTU.

        "rx-acl-buffer-size": {
            "help": "Size of the buffer holding the reassembled complete ACL packet. This will limit the effective ATT_MTU (to its value minus 4 bytes for the header). The size of the buffer must be small enough to be allocated from the existing cordio pool. If this value is increased you may need to adjust the memory pool.",
            "value": 70

[Link]

On robot side, the desired MTU cannot exceed 251.

@YannLocatelli YannLocatelli linked a pull request Jan 18, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
01 - type: story Clear roadmap to implement a new feature, refactor code, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants