Can't get examples to run correctly

Question

Hi

I've tried several of the example applications on the 52840 DK board and I'm not seeing the expected services when using the iOS nRF Connect App. No matter what I run I seem to only be able to see the LED Button Service. I have tried cycle speed and cadence and the heart rate examples, both by building and running them within Segger as well as dropping the respective pre-built hex files onto the JLINK drive. I'm using a Mac. I've also tried looking for the services using another app on my phone called BLE Scanner with the same results.

More specifics using the cycle speed example: In the nRF Connect scanner page, I see Nordic_CSC show up. The Service UUID section lists "Cycling Speed and Cadence<1816> Battery Service<180F> Device Information<180A>". When I press the Connect button it takes me to the Services page and only one service is listed: "LED Button Service".

The very first time I used this board after receiving it I tried the heart rate example and was seeing heart rate and battery level. I then loaded the Blinky example and since then I have not been able to see anything other than the LED Button Service.

What would cause this to happen?

SDK Version: nRF_SDK_15.3.0

MaxOS: Mojave 10.14.6

nRF Connect Version: 1.8.8

Segger Embedded Studio: Release 4.18

Edvin · Accepted Answer

Yes. The (i) button is only for bonded devices, meaning that they have exchanged keys for future encryption, so if you haven't ran an example that does this, it will not show. 
 Sometimes it helps to just turn off and on Bluetooth from the phone settings (not the slide up panel on iOS, as this doesn't turn it off properly). Sometimes (!) it deletes the cached BLE data when you do this. But the failsafe way is to change the address, since it then will appear as a new device. 
 This becomes less annoying when you work mainly on one application, and don't have to add/change services that often. 
 
 Note that there is also a "Service changed" service which will tell the connected device that they should do a new service discovery because something has changed. Most of the simple examples don't use this, and if it wasn't present the first time, adding it later will not help, since the phone is not aware of the service telling it to check for new services, ironically. But this is useful in applications where you intend to add services during the lifetime of the product. 
 
 Best regards, 
 Edvin

Can't get examples to run correctly

Top Replies