This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2340R5: I can't connect well to the persistent app with SimpleLink Connect when I set advertising to 2000 ms instead of 100 ms.

Part Number: CC2340R5

Tool/software:

Good Afternoon,

I can't connect well to the persistent app with SimpleLink Connect when I set advertising to 2000 ms instead of 100 ms.

TI SimpleLink Connect: 1.3.7

Chip: CC2340R5

it seems that on Iphone I connect directly without any problem but with another android phone I have problems. I don't know if it is link to the phone or maybe it is coincidence.

My goal is to be able to load an application into the chip with more or less any phone in your pocket

I need to increase the advertising in order to reduce power consumption.

When I use NRFConnect mobile app to connect, there's no problem.

Do you have any idea to fix that ?

Thank you in advance,

Regards

Yohan

  • Hello Yohan,

    Thanks for reaching out.

    Could you please confirm if the SimpleLink connect app works as you expect with Iphone but not with Android? A 2 second advertising would decrease the chances of a master to detect the peripheral device while scanning in any of the 3 adv channels. Of course this would depend on the scanning parameters (scanning window, scanning period, for instance). If you are dealing with your own mobile application, these are parameters you should be able to set and tune yourself.

    BR,

    David.

  • Hello David,

    I can confirm that it works very well on IOS but remains random and complicated with android.

    I have the impression that it is linked to the application because via the nrf connect application with android, I can connect directly to my device without error.

    Regards,

    Yohan

  • Hello Yohan,

    I see. By "random and complicated with android" you mean that the device appears some times on the scanning window (inside SimpleLink Connect mobile app) and it is difficult to select it in order to connect? As you mentioned, this is most likely due to the scanning parameters that are being used by the app running on Android. Would you see the behaviour across different Android phones? You could confirm this by using a Bluetooth sniffer and check the different between how scanning is done in Android vs IOS. However, if you are planning on developing your own mobile application when released to production, these are parameters you should be able to set and tune yourself. This repository provides the code of the app for developing references: github.com/.../simplelink-connect

    BR,

    David.