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

Why waking up every conn_interval even with slave latency?

I have a min connection interval of 200ms and max of 250ms. I have set slave latency to 10. These parameters are set both on peripheral and on central. Still, after connecting peripheral nRF to oscilloscope I can see that it wakes up every connection interval (~250ms). I expected it to wake up every 2500ms. Is this expected (why?) or do I have some other thing going on in the code?

image description

Parents
  • Are you sure that all the connection parameters are accepted at the central? Some devices may not accept this combination of connection interval and slave latency (e.g. iphone).

    What are the current measurements at this intervals? Can it be something else like a repeating task started by app_timer? If you are using RC LFCLK, the clock will be started regulary for calibration. Are you using NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION?

Reply
  • Are you sure that all the connection parameters are accepted at the central? Some devices may not accept this combination of connection interval and slave latency (e.g. iphone).

    What are the current measurements at this intervals? Can it be something else like a repeating task started by app_timer? If you are using RC LFCLK, the clock will be started regulary for calibration. Are you using NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION?

Children
No Data
Related