Update MTU Exchange Procedure Not Occurring

[Pamela Keiles]

Hello there,

I have read other issues regarding working with a larger MTU size, but I still have not been able to get it to work correctly. I realize that the peripheral device does not initiate the actual update, but it should request the update procedure since the defined MTU size is larger (CONFIG_BT_L2CAP_TX_MTU=247). I have attached the output configuration file from my build.

Please let me know if you need any more information to help. I am using the SDK Version 1.9.1

Thanks and regards,

Pam

[Einarh]

Hi

Glad to hear that it worked!

Well, being a client only means that you're allowed to send requests to a server, such as the MTU exchange request. The only downside I can think of would be a slight increase in memory footprint, but since you're using large Bluetooth buffers this might not be the biggest concern for your application?

If you don't want your peripheral to be a client you would have to send the MTU exchange request from your central unit, so if you're not in control of the application on the central unit your peripheral will have to be a client.

-Einar