More than 1 packet per CI with S132 V3.0.0

RE: More than 1 packet per CI with S132 V3.0.0

AmiguelS — Tue, 21 Mar 2017 11:52:46 GMT

Thank you all for your answers. As it turns out, the reason I was not achieving the expected result was due to very high Wi-Fi interference. The implementation presented on the question is working.

RE: More than 1 packet per CI with S132 V3.0.0

AmiguelS — Thu, 16 Mar 2017 18:50:34 GMT

@kristin It is printing 1 packet added.

RE: More than 1 packet per CI with S132 V3.0.0

FormerMember — Wed, 15 Mar 2017 10:39:06 GMT

Ah, yes, that's right.

In the while-loop for sending packets, could you add a counter that you print to a terminal, containing the number of packets added to the TX buffer before the error code BLE_ERROR_NO_TX_PACKETS is returned?

RE: More than 1 packet per CI with S132 V3.0.0

AmiguelS — Tue, 14 Mar 2017 13:42:17 GMT

@kristin The idea is exactly to send new packets as soon as possible. So, when a packet transmission is finished (TX_COMPLETE received), a new packets is queued, with send(). And in send(), if NO_TX_PACKETS is returned and waiting is set, the function will return, it will not clear waiting.

RE: More than 1 packet per CI with S132 V3.0.0

FormerMember — Tue, 14 Mar 2017 12:20:28 GMT

I suspect that the problem is in case BLE_EVT_TX_COMPLETE:

The code snippet below will send more packets when "waiting" is 'true' ('1').

if(waiting)
            send();
        break;

In send(), "waiting" is set to '0' before exiting the function. Therefore, "waiting" will most likely be '0' in the event BLE_EVT_TX_COMPLETE.

My suggestion is to try the following:

if(waiting)
{
     waiting = 0;
     send();
}
break;

RE: More than 1 packet per CI with S132 V3.0.0

AmiguelS — Mon, 13 Mar 2017 10:16:04 GMT

@kristin I have edited the original question and added a code sample.

RE: More than 1 packet per CI with S132 V3.0.0

FormerMember — Mon, 13 Mar 2017 07:49:03 GMT

Okay, I see. What does your code for sending the notifications look like?

RE: More than 1 packet per CI with S132 V3.0.0

AmiguelS — Fri, 10 Mar 2017 17:28:51 GMT

As per your suggestion, I used a nRF51 dongle connected to a PC, along with nRF Connect. Still, I only received 1 TX_COMPLETE event for each connection interval, with p_ble_evt->evt.common_evt.params.tx_complete.count = 1.

RE: More than 1 packet per CI with S132 V3.0.0

FormerMember — Fri, 10 Mar 2017 13:26:54 GMT

@AmiguelS: Do you have a nRF51/2-DK or a nRF51-Dongle that you could use as central? If so,could you use nRF Connect (PC) as a central and compare with the results from the phone, check if there is still only one packet per connection interval?

RE: More than 1 packet per CI with S132 V3.0.0

AmiguelS — Fri, 10 Mar 2017 11:20:15 GMT

@endnode Hi! Thanks for the reply. My central device (Android phone) only receives notifications. I have used this same phone, along with an nRF51 device running S110 (SDK 6) and have been able to receive 4 notification packets per connection interval.

RE: More than 1 packet per CI with S132 V3.0.0

endnode — Fri, 10 Mar 2017 10:55:22 GMT

Hello Amiguel,

But it depends on both sides of the link! Are you sure that your GAP Central device is able to send multiple PDUs/MTUs within one connection interval? Have you tested it with some SDK example which works (like Nordic BLE UART example and their mobile application)?

Cheers Jan