• State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 74 subscribers
  • Views 2846 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 276724
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Change MTU with nRF Connect for Desktop

acanidio

Hello,

I am using nRF Connect for Desktop 3.7.1 with a nRF52840 USB dongle for testing purposes.

In the Bluetooth Low Energy 2.5.3 application I deselected the "Auto accept update requests".
This shows me a view to request an ATT MTU exchange. The problem is that the field cannot
be edited but only accepted or discarded (correctly leading to a disconnection).

Is it a bug or the program is working as intended and I am missing something? I'd like something
like the “Request MTU” menu entry in the nRF Connect Android version.

PS: I saw a different ticket very similar to my request but I didn't find any answer that satisfies me:
devzone.nordicsemi.com/.../request-mtu-with-nrf-connect-for-desktop-as-gatt-client

Best regards,

Andrea

Parents
  • 0

    It would be acceptable if it was possible.

    I don't know how you can change the MTU after the initial accept request (or the Auto accept update request) since in my case the
    Data Length is still configurable but the ATT MTU isn't.

    For what I understood the ATT MTU can be changed once per connection according to BLE specification and Nordic followed
    implemented the functionality correctly (while other silicon vendors allow multiple MTU change)

    Hence I don't know how you manage your "Update MTU" because mine grays out when I both accept manually the MTU or auto-accept it.

    Could you possibly explain it?

    Best regards,

    Andrea

Reply
  • 0

    It would be acceptable if it was possible.

    I don't know how you can change the MTU after the initial accept request (or the Auto accept update request) since in my case the
    Data Length is still configurable but the ATT MTU isn't.

    For what I understood the ATT MTU can be changed once per connection according to BLE specification and Nordic followed
    implemented the functionality correctly (while other silicon vendors allow multiple MTU change)

    Hence I don't know how you manage your "Update MTU" because mine grays out when I both accept manually the MTU or auto-accept it.

    Could you possibly explain it?

    Best regards,

    Andrea

Children
No Data
Related
Terms of service