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

Connection stability with S130

Hello,

has anyone done some good testing on the connection quality between multiple nRF51 chipsets running on the S130 SoftDevice? (Using all four connections, 3 as Central, 1 as Peripheral) Given an environment with very low interferance and a timeout of 6 seconds with a connection interval of 100ms, can the SoftDevice stay in connection for multiple months? I am currently experiencing connection losses at a rather high frequency (about 2-3 per day) and I am wondering wether this is a bug that I introduced somewhere in my code. At times, I receive the BLE_GATTC_EVT_TIMEOUT event which basically forces me to close the connection. But I am wondering why this happens, because both sides process the BLE events quickly.

I guess that Nordic has done quite a bit of testing on connection stability, would you share these results?

Thanks, Marius

Edit: I am initializing the SoftDevice with NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, maybe that is part of the issue, I am currently investigating this.

Parents
  • It is strange you receive BLE_GATTC_EVT_TIMEOUT, when using supervision timeouts of 6s, and if you do correctly implement GATTC responses on your peer. Please be aware that in S130 v1, APIs do return NRF_ERROR_BUSY, APIs need retry (future releases SD API will better mitigate this).

    If you need greater support, one of our support engineers will be glad to assist you.

    Cheers, Vinayak

Reply
  • It is strange you receive BLE_GATTC_EVT_TIMEOUT, when using supervision timeouts of 6s, and if you do correctly implement GATTC responses on your peer. Please be aware that in S130 v1, APIs do return NRF_ERROR_BUSY, APIs need retry (future releases SD API will better mitigate this).

    If you need greater support, one of our support engineers will be glad to assist you.

    Cheers, Vinayak

Children
No Data
Related