nRF8001 problem with connection interval shoud be 7.5ms but it is 50 ms

RE: nRF8001 problem with connection interval shoud be 7.5ms but it is 50 ms

run_ar — Tue, 25 Oct 2016 09:39:40 GMT

I would recommend capturing a sniffer log so you can see what is happening on air. this way you will be able to see the connection interval and how often notifications are actually sent (to see which side we need to debug). Maybe UART debugging could help as well. Print timing events and timestamp when you call lib_aci_send_data to see if you are filling the buffers fast enough.

RE: nRF8001 problem with connection interval shoud be 7.5ms but it is 50 ms

run_ar — Mon, 24 Oct 2016 10:57:04 GMT

So you are actually getting a TimingEvent with the new connection parameters? What speed are you using for SPI?

RE: nRF8001 problem with connection interval shoud be 7.5ms but it is 50 ms

kirem rahmani — Fri, 21 Oct 2016 19:27:34 GMT

Hi run_ar,

In my case I get a timing change event acknowledging the change request. Surely this is a sign that the master has accepted it?

RE: nRF8001 problem with connection interval shoud be 7.5ms but it is 50 ms

run_ar — Thu, 20 Oct 2016 10:18:31 GMT

Is the Phone accepting the new connection parameters or rejecting them? When setting both max and min value to the minimum interval there is a high probability that the master doesn't accept the parameters. In case the parameters is rejected I would recommed sending another request but increasing the max value. Note that you it might also be necessary to increase the timeour value when increasing the max value. Continue to retry using increasingly bigger values, until the master accepts the request. Note that the master is the one deciding what interval to use.

RE: nRF8001 problem with connection interval shoud be 7.5ms but it is 50 ms

kirem rahmani — Fri, 14 Oct 2016 22:19:14 GMT

Hi Mathew, I hope that you managed to get an answer to this problem. If so, could you provide some information ?

I am seeing exactly the same problem when connecting to an android 4.4.2 device.

I am using the function lib_aci_change_timing_GAP_PPCP() that will use the following defines in the service.h file:

#define GAP_PPCP_MAX_CONN_INT 0x6 /< Maximum connection interval as a multiple of 1.25 msec , 0xFFFF means no specific value requested */ #define GAP_PPCP_MIN_CONN_INT 0x6 /< Minimum connection interval as a multiple of 1.25 msec , 0xFFFF means no specific value requested */

The preferred max and min connection interval parameter are set to the same value that represents the required 7.5ms.

This should be the same as calling:

bool lib_aci_change_timing(uint16_t minimun_cx_interval, uint16_t maximum_cx_interval, uint16_t slave_latency, uint16_t timeout);

with the necessary timing requirements but utilises predefined constants.

I get a timing event in response that reflects the change in requested timing parameters but my measurements show otherwise. In fact, closer to what you are seeing at around 30ms.

Hopefully, someone at Nordic will see this as a bump and help provide a solution or a method to diagnose the cause of the problem.

Thanks, Kirem