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

Is there any relation between connection parameters and occasionally disconnection

I have a system, with cc2540 as central and n51822 as peripheral with s130. Sometimes while they are close to each other, the connection link gets lost. I disabled updating the connection parameters on the client(cc2540), and I set them just on peripheral. Is it acceptable or not? Where I can find best practices/settings on these parameters while I need to get fast feedback on getting out from the RSSI range and also need to do as much as fast on reconnecting;

Could you please clarify me with the impression of these parameters on my occasional disconnection problem?

Parents
  • Yes, I think I know them. These are what I set on peripheral: Minimum Connection interval = 500 ms; Maximum Connection interval = 1000 ms; Slave Latency = 0; Connection supervision timeout = 6 S

    Values I received on BLE_GAP_EVT_CONNECTED event: Minimum Connection interval = 100 ms; Maximum Connection interval = 100 ms; Slave Latency = 0; Connection supervision timeout = 20 S;

    Values I received on BLE_GAP_EVT_CONN_PARAM_UPDATE event: Minimum Connection interval = 500 ms; Maximum Connection interval = 500 ms; Slave Latency = 0; Connection supervision timeout = 6 S;

    Crashing our system because of abnormal disconnection is fatal. Currently, timeout is the reason of crashing our system, on both client and peripheral, while they are really in the response range and are close to each other.

Reply
  • Yes, I think I know them. These are what I set on peripheral: Minimum Connection interval = 500 ms; Maximum Connection interval = 1000 ms; Slave Latency = 0; Connection supervision timeout = 6 S

    Values I received on BLE_GAP_EVT_CONNECTED event: Minimum Connection interval = 100 ms; Maximum Connection interval = 100 ms; Slave Latency = 0; Connection supervision timeout = 20 S;

    Values I received on BLE_GAP_EVT_CONN_PARAM_UPDATE event: Minimum Connection interval = 500 ms; Maximum Connection interval = 500 ms; Slave Latency = 0; Connection supervision timeout = 6 S;

    Crashing our system because of abnormal disconnection is fatal. Currently, timeout is the reason of crashing our system, on both client and peripheral, while they are really in the response range and are close to each other.

Children
No Data
Related