Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot connect my custom app with wahoo

Hello, 

I am using s112_nrf52_7.0.1
I have the nrfRF5 SDK and I built a custom application using BLE. 

When trying to test it I use the example ble_app_hrs and it works, I am able to connect and read simulated values off wahoo. When I load my custom application I see it and I try to connect but I am unable to connect... 

Can you please help me. 

  • Hi

    I think I need some more information in order to help you out here. Can you explain what this custom application does, and what example project it is based on? What nRF52 series device are you developing an application for?

    I'd also like to know what SDK version you're using for development, and if you're able to see any error messages when trying to connect to your custom application, either on the Wahoo app or on the nRF side? I hope you're developing your application on a development board of some kind so you have the opportunity to debug the application.

    Best regards,

    Simon

  • I am using the sdk 17.0.0. For the hardware I am using a Nordic development kit nRF5, the end goal is to flash a nRF52810, but for now i just want to be able to safely flash the dev kit. The example we used to start with is the ble_app_cscs

    For the moment the custom application is supposed to connect to the phone through wahoo and it is supposed to output the power in watts . 
    When I go in my function to simulate the watts, I put logs and i see the value in the terminal output. 

    The thing I realized is when I use the ble_app_hrs, i see the application on wahoo, I try and connect to it, and then it says connected and the data transfer occurs. 

    As opposed to my custom application, I try and connect to it, and then it never actually connnects  connected and the data transfer occurs.
    Here is a screenshot of what I see 

  • Hi Dimitar

    Okay, first off it's strongly recommended to move to SDK v17.0.2 or newer, as there are some bug fixes that should be implemented from SDK v17.0.0, as stated in v17.0.2 release notes. 

    I'm guessing the connection issue is either due to the peripheral not handling connection requests correctly, or due to the Wahoo app requiring some security parameters or services that your peripheral doesn't provide. Are you sure it includes the same security parameters, connection handling, and services as the ble_app_hrs example?

    It would also help if we could see a debug log either using the UART backend and a terminal like PuTTY (which I think is default), or the RTT backend and the RTT viewer. If you're new to the development process in our SDK and with nRF devices, I would suggest checking out this guide on debugging in the nRF5 SDK.

    Best regards,

    Simon

  • Hello Simon, 

    Thank you for the advice, we will switch to the SDK v.17.0.2. 

    I managed to fix the error. 

    As I am quite new in this, I accidentally had commented application_timers() function and i belive that was creating the issue. 

    Thanks, 

  • Glad to hear you found the root cause of this issue, and thank you for sharing your solution as it might help future developers with the same/similar issues.

    Let me know if we can close this case now.

    Best regards,

    Simon

Related