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

Recommended scan window and scan interval for a slow advertising device

I'm trying to run nRF52840 as central to discover and connect to a sensor. This sensor advertises once every 5 seconds. I find it's time consuming to discover the sensor and usually takes multiple tries to connect to it. What would be recommended scan window and interval in this case?

For connection, would it be better to set a short scan_timeout to trigger BLE_GAP_EVT_TIMEOUT and call sd_ble_gap_connect() again or rather make it long and wait for the sensor to eventually connect?

Thanks

Parents
  • Hi

    Sorry about the delayed reply, but we're in the middle of the summer vacation period in Norway and are therefore low on staff. Terje is taking some time off, and we're just now getting through his backlog.

    Yes, to maintain a steady connection, you can increase the connection timeout, reduce connection interval, and use higher slave latency.

    Best regards,

    Simon

Reply
  • Hi

    Sorry about the delayed reply, but we're in the middle of the summer vacation period in Norway and are therefore low on staff. Terje is taking some time off, and we're just now getting through his backlog.

    Yes, to maintain a steady connection, you can increase the connection timeout, reduce connection interval, and use higher slave latency.

    Best regards,

    Simon

Children
No Data
Related