NUS CLIENT (NUSC) NRF_ERROR_RESOURCES from BLE_GQ

RE: NUS CLIENT (NUSC) NRF_ERROR_RESOURCES from BLE_GQ

vincent.golle — Tue, 04 Feb 2020 14:50:27 GMT

I am actually experiencing the same issue and increasing NRF_SDH_BLE_GAP_EVENT_LENGTH to 320 both in peripheral and central did not solve my issue.

In my application I start sending as many NUS packets as soon as the MTU has been exchanged, and I think the procedure then fails because it can never isend ts own packets...

The result is then a disconnection.

I wonder if somebody from Nordic could advise on what to do in that case ?

RE: NUS CLIENT (NUSC) NRF_ERROR_RESOURCES from BLE_GQ

wozix — Sat, 11 Jan 2020 16:46:57 GMT

Ok, the trick was to increase that parameter (NRF_SDH_BLE_GAP_EVENT_LENGTH ) but for the peripheral. I will just need to tune it now.

RE: NUS CLIENT (NUSC) NRF_ERROR_RESOURCES from BLE_GQ

wozix — Sat, 11 Jan 2020 16:38:46 GMT

Didn't work, I tried increasing the NRF_SDH_BLE_GAP_EVENT_LENGTH to 400 but didn't fix the issue.

Maybe I have to increase that in peripheral also since I only increased the number in the central.

The MAX_CON_INTERVAL is 1000ms and the PHY IS CODED_PHY.

RE: NUS CLIENT (NUSC) NRF_ERROR_RESOURCES from BLE_GQ

wozix — Sat, 11 Jan 2020 06:12:10 GMT

Actually I have an idea of what's going on. It has to do with the event length and the fact that I'm using coded phy. I will adjust that parameter tomorrow and see if that fixes the issue.