ant scan can't found any device

[nanty]

Hi 

I'm encountering a problem than the ANT device cannot be scanned. you can use project "ble_ant_app_hrm_v324"(ncs 324）, and modify "

light_rx_open_head" to connect to your ant device, you will see the error "0x4015", and ant device cannot be scanned anymore. And, I use that project "ble_ant_app_hrm_v292" run with ncs 292（test code is same with "ble_ant_app_hrm_v324"）, it does't report error.

Plase help me solve this issue. Thanks.

 ble_ant_app_hrm_v324.zipble_ant_app_hrm_v292.zip

[Kenneth]

Hello,

If I remember correctly ant_channel_open() return 0x4015 means channel is in wrong state.

Are you sure the channel is in closed state? E.g. wait for EVENT_CHANNEL_CLOSED before you open it again. When the issue occurs, what does sd_ant_channel_status_get() return?

Kenneth

[nanty]

Hi，

This issue occur then I do  ant_channel_close and can't get EVENT_CHANNEL_CLOSED response. And ant_channel_status_get() always is 2. 

[nanty]

Hi,
This issue is affecting our project schedule. Please assist in resolving it and provide the expected repair time. Thank you.

[sread]

Thanks for checking in, we're working to reproduce this issue now. Is the ANT traffic still the same as the sample project? How frequent are the 0x4015 errors? If you have a log with the latest code we can take a look. 

[nanty]

Hi，
The project ble_ant_app_hrm_v324.zip and ble_ant_app_hrm_v292.zip that I have provide before, the code is the same, but it has issuse running on V324, while it runs normally on V292. It seems to be unrelated to the printfs? Can you check the differences between the ncs v324 and v292?

[nanty]

HI
Did you find the reason why version 292 doesn't have this problem?

[sread]

We're still attempting to reproduce the issue on our side with v3.2.4 and the modified handler. If you're able to share a log from that build, even a short one showing the first occurrence, that would be helpful.

As far as the v2.9.2 differences, there were no changes to event dispatch in the ANT components. We are evaluating SDK dependencies between versions to determine if timing and context changes exposed an issue. I will update you as soon as I have more information.