nRF52 SDK: ANT+ examples ant_bpwr and ant_bsc (RTT logs OK) are not discoverable on 2 different bike computers

[Salmat]

I am having a persistent issue with the ANT+ examples in the nRF5 SDK on an nRF52832 DK PCA10040. The application firmware compiles and runs correctly, but the ANT+ signal is never detected by 2 bikes computers.

Summary of the problem:

   * Goal: Run a standard ANT+ sensor profile (Bicycle Power or Bicycle Speed & Cadence).
   * Symptom: The application runs perfectly according to RTT logs. I can see the main function starting, the ANT channels opening, and the sensor data being generated (not null), and sent to the stack for transmission. However, the device is completely invisible to two different commercial bike computers, bryton Rider 320, and Garmin EDGE 530 (firmware are up to date).

What I have tested :

 1. Regarding project-specific issue:
       * I first tried with the ant_bpwr_tx example s212 v7.0.1 compiled with SDK 7.1 and SDK 7.0.2
       * which I migrated to use the S332 v7.0.1 compiled with SDK 7.1 and SDK 7.0.2
       * I created a completely clean project using the standard `ant_bsc_tx` example from SDK v17.1.0 with its default S212 v7.0.1
       * Both projects show the exact same failure => not detected on the bike computers.

 2. Regarding an hardware issue:
       * I have reproduced the exact same problem on two different nRF52832 DK boards (v2.0.0 and v1.1.1).

 3. Regarding compiler issue:
       * I have tried compiling with two different GCC toolchains (one for SDK 17.1.0, and older one for an attempt with SDK 17.0.2).

 4. Regarding basic configuration issue:
       * ANT License Key: I have verified in the nrf_sdm.h file that the ANT_LICENSE_KEY is
         uncommented. The project would not compile otherwise.

Any ideas ?

Thanks

[Turbo J]

Re-read the sections about the LICENSE KEY and the NETWORK KEY on thisisant.com website.

Not a nordic problem - those keys are not supposed to be public IIRC.

[Salmat]

Thanks for your response.

I have find nothing saying that ? I understand a licence has to be payed  for commecial use :

nrf_sdm.h :

/** @brief Evaluation key for the ANT SoftDevices. Use this key in sd_softdevice_enable call to start using the evaluation stacks.
    You MUST obtain a valid commercial license key BEFORE releasing a product to market that uses the ANT SoftDevices. For
    more information about licensing please visit the website below:
    www.thisisant.com/.../licensing */
#define ANT_LICENSE_KEY "XXXXXXXX" // This is an EVALUATION license key - DO NOT USE FOR COMMERCIAL PURPOSES
#ifndef ANT_LICENSE_KEY
   #error "You must obtain a valid license key to use ANT. You may use the evaluation key for non commercial use only by uncommenting it above this error. Commercial use license keys are available from ANT Wireless."
#endif

On www.thisisant.com/.../licensing :

   ANT+
If you are building a product that is intended to interoperate with other ANT+ devices or applications, you’ll find our ANT+ Device Profiles, and an array of design tools, on the downloads page. Items marked with the ANT+ logo are only accessible to ANT+ Adopters. You can access them by signing up (for free!) to become an ANT+ Adopter, here: ANT+ Adopter sign-up. This will also give you access to a lot of good ANT+ forum advice, and the ANT+ network key.

   Protocol Stacks
With some System on Chip (SoC) devices, the ANT protocol stack is not embedded on the device, and is accessed as a downloadable software component by the developer who is using the SoC.

For the Nordic Semiconductor nRF51 Series SoC device, the ANT capable protocol stacks are accessed with a click through agreement from Nordic’s website.

ANT protocol stacks for the Nordic Semiconductor nRF52 Series SoC devices are licensed by ANT Wireless for evaluation and for commercial or other revenue generating purposes under two separate agreements. Use of the ANT stacks for evaluation purposes only is free. There is a per-instance royalty fee associated with use of the ANT stacks for revenue-generating purposes.  Please see the nRF52832 component page and the FAQ (basic user account login required) for more information on the click through licenses associated with these protocol stacks.

For information www.thisisant.com/.../ :
ANT+ Adopter Account
You are an ANT+ Adopter

That permited to dowload s212 and s332, giving the license...



The execution show the is not any error, the license is acceptée :

<info> app_timer: RTC: initialized.
<info> ant_bsc: ANT BSC channel 0 init
<info> ant_bsc: BSC TX Page: "Combined Speed & Cadence Page"
<info> ant_bcs_combined_page_0: Cadence Revolution count: 0
<info> ant_bcs_combined_page_0: Cadence event time:       0.000s
<info> ant_bcs_combined_page_0: Speed Revolution count:   0
<info> ant_bcs_combined_page_0: Speed event time:         0.000s

<info> ant_bsc: ANT BSC channel 0 open
<info> app: ANT+ Bicycle Speed and Cadence TX example started.
<info> ant_bsc: BSC TX Page: "Combined Speed & Cadence Page"
<info> ant_bcs_combined_page_0: Cadence Revolution count: 1
<info> ant_bcs_combined_page_0: Cadence event time:       0.856s
<info> ant_bcs_combined_page_0: Speed Revolution count:   0
<info> ant_bcs_combined_page_0: Speed event time:         0.000s

<info> ant_bsc: BSC TX Page: "Combined Speed & Cadence Page"
<info> ant_bcs_combined_page_0: Cadence Revolution count: 2
<info> ant_bcs_combined_page_0: Cadence event time:       1.713s
<info> ant_bcs_combined_page_0: Speed Revolution count:   0
<info> ant_bcs_combined_page_0: Speed event time:         0.000s

[Turbo J]

Ant+ has a non-trivial NETWORK key, which is different from license key. 

I'm afraid you have not made it far enough into the documentation yet. And no, I don't even remember right now where that one is actually documented. But you should have access to that document as an adopter IIRC.

[Kenneth]

Without the proper network key it won't work within the ANT+ ecosystem no, think this is also described:
https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/ant_examples_bicycle_spd_cad.html#ant_bsc_test_3

Kenneth

[Salmat]

exact Thanks
I had to set the network key