https://devzone.nordicsemi.com/f/nordic-q-a/71415/timeout-in-changing-mtuChip: nrf52832 SDK: 15 SD: s132_nrf52_6.0.0_softdevice After connection, we request a new MTU size. Some values work, other don&#39;t. For example, trying to get 187 bytes we have a timeout issue calling sd_ble_gap_data_length_update() nrf_ble_gatten-USTelligent Community 13Wed, 10 Feb 2021 11:54:13 GMThttps://devzone.nordicsemi.com/thread/293746?ContentTypeID=1Wed, 10 Feb 2021 11:54:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d3c46688-bc5d-416a-b3ef-d3db092417a5Susheel Nuguru<p>Hi Andrea,</p> <p>Thanks for the message log, it would be more insightful if you can provide the sniffer trace to be able to see how this transaction timeout</p> <p>Also note that the error you get is NRF_ERROR_RESOURCES and the documentation for <a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v6.0.0%2Fgroup___b_l_e___g_a_p___f_u_n_c_t_i_o_n_s.html&amp;anchor=gac4a6ef5c106107eb2a1707bb26f3245c">sd_ble_gap_data_length_update </a>says</p> <div> <div><span></span></div> <pre class="ui-code" data-mode="text"> * @retval ::NRF_ERROR_RESOURCES The connection event length configured for this link is not sufficient for the requested parameters. * Use @ref sd_ble_cfg_set with @ref BLE_CONN_CFG_GAP to increase the connection event length. * Inspect p_dl_limitation to see where the limitation is.</pre> <div><span></span></div> </div><div style="clear:both;"></div>