This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth connection parameters

I am working with nRFx modules and have a few questions about updating parameters. I started my project with an example and modified what I needed. However, I am not sure if the parameters are getting set when I change them. Currently I go into main.c and change the following parameters:

#define MIN_CONN_INTERVAL                          MSEC_TO_UNITS(20, UNIT_1_25_MS)           
#define MAX_CONN_INTERVAL                         MSEC_TO_UNITS(75, UNIT_1_25_MS)           
#define SLAVE_LATENCY                                  0                                         
#define CONN_SUP_TIMEOUT               
#define FIRST_CONN_PARAMS_UPDATE_DELAY  APP_TIMER_TICKS(5000, APP_TIMER_PRESCALER)  
#define NEXT_CONN_PARAMS_UPDATE_DELAY   APP_TIMER_TICKS(30000, APP_TIMER_PRESCALER) 
#define MAX_CONN_PARAMS_UPDATE_COUNT    3                                
#define TX_POWER_LEVEL                                4      

If I change these parameters, specifically the first three (connection interval, slave latency, and connection supervision timeout), will they automatically be set on with the central? I am currently connecting to a windows 10 device and trying to figure out if the parameters are being updated and if not, why? How would I check to see if they are getting updated?

Parents
  • What project you use? There are like hundred main.c files in SDK;) Normally these constants are indeed used in the code when you recompile and load it to the board so they should be used. The question is what you expect to happen;) Normally there is no debugging on Link Layer on systems like smart phones or Windows boxes so the usual way is to get RF analyzer/sniffer and see what is happening in the air.

  • (2/2) ... should prevent clock drift (even that shouldn't happen for certified HW and stack) so again higher chance that if there is disconnection because of link loss then it's because devices went too far and signals are too weak rather then some technical/SW issue while devices operate in standard range.

    When it comes to connection parameters update procedure all I can tell you is on Infocenter:

    Unfortunately I'm not familiar with the example you use and FIRST/NEXT CONN_PARAMS_UPDATE_DELAY constants and mechanisms so I cannot advise on these.

Reply
  • (2/2) ... should prevent clock drift (even that shouldn't happen for certified HW and stack) so again higher chance that if there is disconnection because of link loss then it's because devices went too far and signals are too weak rather then some technical/SW issue while devices operate in standard range.

    When it comes to connection parameters update procedure all I can tell you is on Infocenter:

    Unfortunately I'm not familiar with the example you use and FIRST/NEXT CONN_PARAMS_UPDATE_DELAY constants and mechanisms so I cannot advise on these.

Children
No Data
Related