2023-07-11 01:30 AM - edited 2023-07-11 01:31 AM
Hello all,
We are developing a product that connects to a mobile application through BLE. Sometimes, not all the time, the product does not connect to the smartphone the first time, it retries to connect until it gets there. As a consequence, the connection is sometimes quite long, which is not acceptable. By using a BLE connection app on the smartphone (LightBlue), we can see that some connection does not succeed:
In your opinion, what is the reason for this? I tried to switch from clock LSE to HSE but it doesn’t change anything. Could we have conflicting timing (advertising/connection)?
It seems that it is the physical layer that refuses the connection. Is there something to change in the configuration of the BLE stack? We have used the Heart rate example provided by ST to write our code.
Sincerely,
Audrey
2023-07-27 09:03 AM
Hello,
Are you able to perform air trace to see what's happens when the connection failed? Did you same the same behavior when using BLE_HeartRate example without any modification? If not, can you describe a bit more the modification that you have performed?
Best Regards