NUS CLIENT (NUSC) NRF_ERROR_RESOURCES from BLE_GQ

[wozix]

Hi,

I have a multilink NUS central that connects to several NUS Peripherals using SDK 16.0, S140 (NRF52840 REV1). Currently I'm testing with only one peripheral, sending and receiving data every 3-4 seconds (small 30 byte packet). I do have some other modules enabled like the mem_manager but I'm currently not doing much.

After 1 or 2 minutes of running, the central starts getting some errors from the Gatt Queue:

<info> app: NUS Sending 29 bytes... max unit (244)
<debug> nrf_ble_gq: Adding item to the request queue
<debug> nrf_ble_gq: GATTC Write Request
<error> nrf_ble_gq: SD GATT procedure (1) failed on connection handle 0 with error: 0x00000013.
<debug> ble_nus_c: A GATT Client error has occurred on conn_handle: 0X0

Then the next TX packet succeeds but then again after that one I get the same error and it goes on like that. Before I got that error, I was able to send around 30 packets without error. Error 0x13 is NRF_ERROR_RESOURCES. 

I have no idea what to do here, does anyone have any clue on what to change or how to debug this?

Thanks!.

[wozix]

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. 

[wozix]

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.

[wozix]

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.