Using nRF Connect (Windows) to connect to a peripheral using a bigger MTU.

[JenR]

I have a peripheral (nrf52832) which is using a higher MTU (140 bytes). When I connect to it using the nRF Connect Android app, everything works. I can see the BLE_GAP_EVT_PHY_UPDATE_REQUEST and BLE_GAP_EVT_PHY_UPDATE being handled on the peripheral after calling nrf_ble_gatt_att_mtu_periph_set(..).

When I use the nRF Connect windows app (using a nRF52832) to connect to the peripheral, I don't see the BLE_GAP_EVT_PHY_UPDATE_REQUEST/BLE_GAP_EVT_PHY_UPDATE on the peripheral. 

Does the windows nRFConnect app not support higher MTU's? Are there plans for this in the future?

[Bjørn Kvaale]

Hi,

The problem lies with nrf connect for desktop. It is currently using the s132 v3.1 softdevice, whereas the phy update request functionality was implemented in a later softdevice (s132 v5). Could you please explain why you are referring to the phy update request when you want to use a higher MTU?