Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Kenneth — Mon, 06 Apr 2020 15:54:08 GMT

For testing I suggest to try NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM.

Best regards,
Kenneth

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Linxi — Mon, 06 Apr 2020 13:24:09 GMT

I will double check my code and procedure. Actually, I just wanna know something about this situation. Is there any official instructions that Nordic provides to guide developers?

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Linxi — Mon, 06 Apr 2020 13:18:04 GMT

#define NRF_CLOCK_LFCLKSRC                                                     \

  {                                                                            \

    .source = NRF_CLOCK_LF_SRC_XTAL, .rc_ctiv = 0, .rc_temp_ctiv = 0,          \

    .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM                         \

  }

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Kenneth — Mon, 06 Apr 2020 09:33:52 GMT

I think looking at my previous suggestions will help, they may not help individually, but combined they should make a considerable difference. There is one thing I have not asked about, what LFCLK source and tolerance have you used when init the softdevice stack?

Best regards,
Kenneth

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Linxi — Fri, 03 Apr 2020 08:13:55 GMT

Hi Kenneth:

It seems very hard for me to fix it. I struggled this week. In my use scenario, i need ANT+ display, central and periphral keep active. This means ANT+ search for tracking, Ble scan,ANT+ background search may work together.I am not sure how much you know about bike computer. It should keep tracking sensors that user assigned.It also need to be connected by App to receive and response command.I am going to be crazy.Because I often receive disconnetion timeout event.Could you give me some advise?

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Kenneth — Wed, 01 Apr 2020 10:09:00 GMT

Typically it is the conn_params_init() that can initiate and handle this for you. For instance in ble_conn_params_init() you specify a FIRST_CONN_PARAMS_UPDATE_DELAY delay, which is the delay from connection event until it will try to negotiate new connection parameters (MIN_CONN_INTERVAL, MAX_CONN_INTERVAL, SLAVE_LATENCY and CONN_SUP_TIMEOUT). A supervisor timeout of only 75ms sounds very short yes.

My suggestion may be that you stop ANT channel search when you receive the BLE_GAP_EVT_CONNECTED event, and wait until BLE_GAP_EVT_CONN_PARAM_UPDATE event to check the updated connection parameters in &p_ble_evt->evt.gap_evt.params.conn_param_update.conn_params, for instance that the parameters use slave latency and that supervisor timeout is more than for instance 500ms before you start ANT channel search again.

Best regards,
Kenneth

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Linxi — Wed, 01 Apr 2020 07:01:41 GMT

Hi Kenneth:

I printed the connection parameters when peripheral receives BLE_GAP_EVT_CONNECTED. And it shows superversion timeout is 500 with Android and 75 with IOS. I think it's the key that causes disconnection when i use IPhone. Is there any way wo update the superversion timeout to a bigger value？It's expected to be MSEC_TO_UNITS(4000, UNIT_10_MS) that i defined.

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Linxi — Wed, 01 Apr 2020 03:36:12 GMT

Hi Kenneth:

I disabled high priority search in ANT+ background scan, and the reason of disconnection changed to BLE_HCI_INSTANT_PASSED. For my scenario, start the ble and ANT+ scan orderly, then periodically transmit result from Nus notification by timer. Is there any better solutions to avoid disconnection of peripheral role?

RE: Nrf52832 periphral disconnects timeout when BLE/ANT+ scan

Kenneth — Tue, 31 Mar 2020 14:00:42 GMT

Hi,

Check out this application note on ANT channel search:
https://www.thisisant.com/resources/an11-ant-channel-search-and-background-scanning-channel/

Likely you need to disable high priority search, in addition the BLE link should use slave latency (for instance >10) to allow some blocking by the ANT channels.

Best regards,
Kenneth