Problems with bonding using "Heart Rate Application" example on nRF connect for desktop

Hi,

I'm trying the "Heart Rate Application" example on nRF52 DK. I successfully compiled and downloaded the hrs_example code to the board. When I used Toolbox app on the android phone to connect with the board, everything worked well, I could read constantly generating data and battery information. 

But when I tried to test this example on the nRF connect for desktop on the MAC OS following these steps, a bonding problem occurred. 

I Compiled and programed the application to the kit.and the BSP_INDICATE_ADVERTISING state is indicated. And I tried to Connected to the device from nRF Connect for Desktop, there was no device called 'Nordic_HRM' even after several scanning. And the LED1 stopped blinking.

How can I solve this? 

Thanks a lot for any advice.

Best.

Parents
  • Hi,

    As you write that LED1 stopped blinking I wonder if you perhaps ended up using the same DK with nRF Connect for Desktop as the one that is running the Heart Rate Application example? nRF Connect for Desktop will program a connectivity firmware on the DK and use that for communication, so if you want to test a DK with the nRF Connect for Desktop you actually need two DKs (one that you are running the firmware you are testing, and one that is used with nRF Connect for Desktop).

Reply
  • Hi,

    As you write that LED1 stopped blinking I wonder if you perhaps ended up using the same DK with nRF Connect for Desktop as the one that is running the Heart Rate Application example? nRF Connect for Desktop will program a connectivity firmware on the DK and use that for communication, so if you want to test a DK with the nRF Connect for Desktop you actually need two DKs (one that you are running the firmware you are testing, and one that is used with nRF Connect for Desktop).

Children
Related