Connection parameters in nrf ble

[Ridhi]

want to know how can i judge that the variation is caused in the connection interval, connection supervision timeout, slave latency once i have flashed ble_app_template code in nrf52832 s132.

[Karl Ylvisaker]

Hello again,

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

Ridhi 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.

Ridhi 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

[Ridhi]

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

[Karl Ylvisaker]

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