Easy ways to debug BLE connectivity issues

Are there any convenient ways to debug BLE connectivity issues? I have the service up and running but the connection on nRFConnect App doesn't quite go through: it remains stuck on "Connecting" state.

It was working all fine until of a sudden and I can't seem to figure out what went wrong

  • Could I ask which phone you are using the nRF Connect application with, and what version of the application you are using?

    App version 2.4.12, and it's an iOS app.

    What does the log on the nRF Connect's side say when you connect to a peripheral device (as indicated by the connected event on the peripheral side)?

    Turning Off Scanner...
    Scanner On.
    Device Scanned.
    [Callback] centralManager(central, didDiscover: peripheral, advertisementData: ["kCBAdvDataRxSecondaryPHY": 0, "kCBAdvDataTimestamp": 656911790.671123, "kCBAdvDataServiceUUIDs": <__NSArrayM 0x28272db00>(
    F3641400-00B0-4240-BA50-05CA45BF8ABC
    )
    , "kCBAdvDataIsConnectable": 1, "kCBAdvDataRxPrimaryPHY": 1, "kCBAdvDataLocalName": Xyp-CUS], rssi: -62)
    Attempting to connect...
    cbCentralManager.connect()

  • morpho said:
    App version 2.4.12, and it's an iOS app.

    Thank you for clarifying.
    I just tested this on an iPhone X with the 2.4.12 version without issues - testing against the ble_app_uart application.
    Are these the only loggings available in the "Log" section during a connection? Does it not show anything about service discovery and connection parameter updates, etc?

    I know that iOS devices sometimes might experience a caching issue if their bluetooth adapter has been on for a long time. Could you try this again after having turned off and on again the phone's bluetooth?
    If this does not resolve the issue, could you try this again after uninstalling and reinstalling the nRF Connect application for smartphone entirely?

    Best regards,
    Karl

  • could you try this again after uninstalling and reinstalling the nRF Connect application for smartphone entirely?

    I actually tried this the first time it happened, and it solved the issue but this time i have tried like 4-5 times to no avail

  • morpho said:
    I actually tried this the first time it happened, and it solved the issue but this time i have tried like 4-5 times to no avail

    That sounds very peculiar indeed. I have not heard of anyone else experiencing this either yet, but I will file an internal ticket with the developers of the application so that they could be aware of it.

    Before I do so, could you try to clear the app's cache too, to see if this perhaps fixes the issue?
    And just to have it confirmed, the issue is that the view in the screenshot you sent does not change to 'connected' right? It only ever says 'connecting' when this happens?

    Best regards,
    Karl

  • Yes, it says Connecting even though I think it's connected as mentioned earlier. How do you clear the app's cache? In settings?

Related