Connection parameters in nrf ble

Hello,

The best way to see exactly how your connection parameter configuration affects the connection would be to use the nRF Sniffer tool to see exactly what is happening on-air.
Alternatively, if you just would like to play around with different connection parameters to see how each of them affects your connection you could take a look at the experimental ATT MTU throughput example from the SDK.
 
If you would like to visualize different connection parameter configurations you could take a look at the Online Power Profiler, which will let you see the effects of each configuration on the packet exchanges (as well as estimated power consumption).

Best regards,
Karl

Karl i am finding a difficulty in normal understanding the connection interval thing. Actually, by definition of CI i found it is the time btw two consecutive events for which the radio is turned ON. how can i judge this in nrf connect app?

Hello Karl,

My code works as:

 press button

device advertise with name BTLog

Then i connect on nrf connect app on mobile

i press a button and put device in data logging mode with flash storage and temperature sensor interfaced

then after logging i press button again to make the device sleep

then again press button to readvertise

the from the service created i get the logged data using notification

 i face issue in setting connection parameters :

i found that increasing CI reduces power consumption but 

1st is for 7.5-100ms connection interval which accounts for more than 20 logs

2nd is for  1000-1000ms connection interval which only  4 logs after which i dont get logs

i am sharing you the wireshark traces:

user87869 pls administer the above issue

Hello again,

Please note that we do not provide support in the forum during the weekend.

RIDHIMA said:

i found that increasing CI reduces power consumption but 

This is correct, because it will lead to much more infrequent use of the RADIO peripheral, which in turn saves power.

RIDHIMA said:

i am sharing you the wireshark traces:

Thank you for providing the traces. I do not immediately see anything abnormal in the traces - the connections are terminated by either the peripheral or the central in either cases, with no error. Everything seems nominal.

This makes me suspect that it is a application layer logical issue that is causing this. What could cause either the peripheral or the central to terminate the connection? Are they both programmed to terminate the connection when certain conditions are met, such as no data being sent for a specific period, or similar?
Both instances have a period of empty packets leading up to the connection termination.

Best regards,
Karl

 i havent changed anything except the Connection Interval values, i am not getting why this is hampering

Please go through all the conditions that would trigger a link termination by your application, and see if any of these may be triggered unexpectedly as a result of the changed connection interval.

Best regards,
Karl

Please go through all the conditions that would trigger a link termination by your application, and see if any of these may be triggered unexpectedly as a result of the changed connection interval.

Best regards,
Karl