RE: How many retries in Eddystone beacon advertisement ?

Sigurd — Tue, 04 Dec 2018 16:51:15 GMT

Hi,

Q1) The TLM information is by default updated every 10 sec. (APP_CONFIG_TLM_TEMP_VBATT_UPDATE_INTERVAL_SECONDS in es_app_config.h).

Information about temperature and battery voltage is updated every 30 sec(APP_CONFIG_TLM_TEMP_INTERVAL_SECONDS/ APP_CONFIG_TLM_VBATT_INTERVAL_SECONDS).

We send a packet(one packet across 3 advertising channels) each APP_CFG_NON_CONN_ADV_INTERVAL_MS(default value 1000). When investigating this some more, I figured out that the SoftDevice expects this to be in 625 us units when calling sd_ble_gap_adv_set_configure(), and we unfortunately don't do this in adv_start() function in the file es_adv.c. This mismatch will affect the ADV_COUNT, so we should fix this.

The function adv_start() in es_adv.c with the fix should look like this:

static void adv_start(ble_gap_adv_params_t * p_adv_params)
{
    ret_code_t err_code = NRF_SUCCESS;

    es_tlm_adv_cnt_inc();

    uint32_t interval_0625 = MSEC_TO_UNITS(p_adv_params->interval,UNIT_0_625_MS);

    p_adv_params->interval = interval_0625;

    err_code = sd_ble_gap_adv_set_configure(mp_adv_handle, &m_adv_data, p_adv_params);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_start(*mp_adv_handle, BLE_CONN_CFG_TAG_DEFAULT);

    if (err_code != NRF_ERROR_BUSY && err_code != NRF_SUCCESS)
    {
        APP_ERROR_CHECK(err_code);
    }
}

The ADV_COUNT is not the numbers of retries per say, it's just an incremented counter that is incremented for every APP_CONFIG_TLM_ADV_INTERLEAVE_RATIO packets that are sent.(default value 5).

Q2) A packet will be send every APP_CFG_NON_CONN_ADV_INTERVAL_MS, and ADV_COUNT is increment when you have sent APP_CONFIG_TLM_ADV_INTERLEAVE_RATIO numbers of packet(s).

Q3) It will send a packet each advertising interval(by defeault 1000 ms with the fix).