ANTcontinuous scan mode will impact BLE advertising

RE: ANTcontinuous scan mode will impact BLE advertising

Kenneth — Wed, 22 Apr 2020 08:42:28 GMT

Sounds good. If you find more descriptive information about these configuration bytes, don't hesitate to wrap it up here.

Thanks,
Kenneth

RE: ANTcontinuous scan mode will impact BLE advertising

anikchen — Tue, 21 Apr 2020 12:58:13 GMT

Million thanks all the same. I will seek more information in the ANT Forum.😀

RE: ANTcontinuous scan mode will impact BLE advertising

Kenneth — Tue, 21 Apr 2020 09:58:56 GMT

I don't have any specific details on this feature, I saw the administrator on thisisant.com recommended to do this: https://www.thisisant.com/forum/viewthread/7332/

"If you still run into issues try doubling “search channel fixed interval priority config” to reduce the impact of the ANT search."

The ANT implementation in the softdevices are developed and maintained by Dynastream (thisisant.com).

RE: ANTcontinuous scan mode will impact BLE advertising

anikchen — Mon, 20 Apr 2020 15:48:15 GMT

Thanks, Kenneth.

Follow the link you provided, I get a clue related to sd_ant_coex_config_set().

Since I added the following simple code to my project, BLE advertising has been working well with ANT continuous scanning :

err_code = sd_ant_coex_config_get(ANT_SCAN_CHANNEL_NUMBER, &ant_coex_config, NULL);
APP_ERROR_CHECK(err_code);
ant_coex_config.pucBuffer[0] = 0; //disable all configuration
err_code = sd_ant_coex_config_set(ANT_SCAN_CHANNEL_NUMBER, &ant_coex_config, NULL);
APP_ERROR_CHECK(err_code);

But exactly, I cannot understand those parameters clearly related to ANT_BUFFER_PTR in sd_ant_coex_config_set():

/** @brief This function sets ANT radio coexistence behaviour. Supported only if ANT is sharing radio HW concurrently with another wireless protocol.
* Configuration structure is as follows:
* Byte0 = Configuration enable bitfield
* bit0 - enable/disable tx/rx channel keep alive config (Byte4/5 & Byte6/7)
* bit1 - enable/disable tx/rx channel fixed interval priority config (Byte1)
* bit2 - enable/disable transfer keep alive config (Byte2)
* bit3 - enable/disable search channel fixed interval priority config (Byte3)
* else - reserved
* Byte1 = tx/rx channel fixed interval priority configuration
* Byte2 = transfer keep alive configuration
* Byte3 = search channel fixed interval priority configuration
* Byte4(LSB)/Byte5(MSB) = tx channel keep alive configuration
* Byte6(LSB)/Byte7(MSB) = rx channel keep alive configuration
* Byte8 = ANT counts/16 spent in high priority mode during search scan.
* Byte9 = ANT counts/16 spent in low priority mode during search scan.
*
* Advanced configuration structure is as follows:
* Byte0 = Configuration enable bitfield
* bit0 - enable/disable priority override config (Byte1)
* bit1-7 - reserved
* Byte1 = ANT priority override. 0 = low, 1 = normal(default), 2 = high, 3 = critical
* Byte2 = Reserved
* Byte3 = Reserved
* Byte4 = Reserved
* Byte5 = Reserved
* Byte6 = Reserved
* Byte7 = Reserved
*/

So I'll appreciate very much if you can give more guide.

Thanks & Best Regards.

RE: ANTcontinuous scan mode will impact BLE advertising

Kenneth — Mon, 20 Apr 2020 12:01:49 GMT

I believe you can use the trick described here:

https://devzone.nordicsemi.com/f/nordic-q-a/60158/how-to-arrange-ble-and-ant-event/244652#244652