- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
HI,
We have developed peripheral based on TI simple peripheral application and our custom hardware and also developed the android application.
What i have observed is the time taken to connect to the peripheral varies all time some time it is 4 to 5 seconds, sometimes it is 30-40 seconds.
1. Is it possible to make the connection time within 2-3 seconds on every connection?
2. What changes are needed for this on the central side and on the peripheral side ?
3. Observed that the android application is making connection request but dont get any reply and it does not go into the callback so android application does not understand what happened with the request and there is no timeout so we cannot make the retry it is entering in the call back after 20 seconds and getting status disconnected.
Please find the attached debug logs from the peripheral (Android app side)
Additional information.
On peripheral side
1. MTU size= 75, maximum data frame length = 46 bytes.
2. Connection parameters
DEFAULT_DESIRED_MIN_CONN_INTERVAL = 80
DEFAULT_DESIRED_MAX_CONN_INTERVAL = 800
SLAVE LATENCY = 0
DEFAULT_CONN_PAUSE_PERIPHERAL = 6 Seconds
DEFAULT_DESIRED_CONN_TIMEOUT = 1000 (10 Seconds)
3. BLE STACK VERSION : TI BLE 2.2.3
On Central side
1. Central is making the connection request then making the measurement request and then data request.
2. once connected then it makes measurement and data request every 5 seconds.
if during the measurement request it finds that the peripheral is disconnected then it makes the connection request first.
