Eddystone and ibeacon with Timeslot API

RE: Eddystone and ibeacon with Timeslot API

Sourabh — Fri, 02 Mar 2018 11:04:28 GMT

Hi Tar,

Thanks for the support, it works but don't see it as a separate device.

This is the only advertisement I get.

This is my gap_params_init() function

static void gap_params_init(void)
{
    uint32_t                err_code;
    ble_gap_conn_params_t   gap_conn_params;
    ble_gap_conn_sec_mode_t sec_mode;

    ble_gap_privacy_params_t ble_gap_privacy_params = {0};

    ble_gap_privacy_params.privacy_mode = BLE_GAP_PRIVACY_MODE_DEVICE_PRIVACY;
    ble_gap_privacy_params.private_addr_type = BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE;
    ble_gap_privacy_params.private_addr_cycle_s = 900; //adress change cycle
    ble_gap_privacy_params.p_device_irk = NULL;

    err_code = sd_ble_gap_privacy_set(&ble_gap_privacy_params);
    APP_ERROR_CHECK(err_code);


    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&sec_mode);

    err_code = sd_ble_gap_device_name_set(&sec_mode,
                                          (const uint8_t *) DEVICE_NAME,
                                          strlen(DEVICE_NAME));
    APP_ERROR_CHECK(err_code);

    memset(&gap_conn_params, 0, sizeof(gap_conn_params));

    gap_conn_params.min_conn_interval = MIN_CONN_INTERVAL;
    gap_conn_params.max_conn_interval = MAX_CONN_INTERVAL;
    gap_conn_params.slave_latency     = SLAVE_LATENCY;
    gap_conn_params.conn_sup_timeout = CONN_SUP_TIMEOUT;

    err_code = sd_ble_gap_ppcp_set(&gap_conn_params);
    APP_ERROR_CHECK(err_code);


}

RE: Eddystone and ibeacon with Timeslot API

TAR CHAL — Fri, 02 Mar 2018 10:20:56 GMT

Hi,

the two advertisements are done but you don't ses it because they are on the same MAC adress, if you want to see those two simultaneously, you must have an other MAC adress, for that you must activate privacy in gap_params_init() function, and it must work,

    
    ble_gap_privacy_params_t ble_gap_privacy_params = {0};
    
    ble_gap_privacy_params.privacy_mode = BLE_GAP_PRIVACY_MODE_DEVICE_PRIVACY;
    ble_gap_privacy_params.private_addr_type = BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE;
    ble_gap_privacy_params.private_addr_cycle_s = 900; //adress change cycle
    ble_gap_privacy_params.p_device_irk = NULL;


    err_code = sd_ble_gap_privacy_set(&ble_gap_privacy_params);
    APP_ERROR_CHECK(err_code);

RE: Eddystone and ibeacon with Timeslot API

Sourabh — Fri, 02 Mar 2018 04:44:57 GMT

I've used the exact same code present in advertiser_timeslot.c of the example. I just changed the application code to broadcast the beacon message even if it is not connected. I did this by just calling app_beacon_start in the main function I've added the snippet for reference:

int main(void)
{


    uint32_t err_code;
    bool     erase_bonds;

    // Initialize.
    err_code = app_timer_init();
    APP_ERROR_CHECK(err_code);

    uart_init();
    log_init();

    buttons_leds_init(&erase_bonds);
    ble_stack_init();
    beacon_adv_init();
    gap_params_init();
    gatt_init();
    services_init();
    advertising_init();
    conn_params_init();

    NRF_LOG_INFO("UART Start!");
    err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
    APP_ERROR_CHECK(err_code);

    app_beacon_start();
    // Enter main loop.
    for (;;)
    {
        power_manage();
    }
}

RE: Eddystone and ibeacon with Timeslot API

TAR CHAL — Thu, 01 Mar 2018 10:26:47 GMT

can you send me your code that i can verify it?

RE: Eddystone and ibeacon with Timeslot API

Sourabh — Thu, 01 Mar 2018 05:32:18 GMT

Hi Tar,

I'm trying to implement the same on nrf52 using SDK 14 and sd v5.0.0. I'm unable to get advertisement (SD) + ibeacon (Timeslot) configuration to work. Standalone the timeslot beacon works but when i enable SD advertising I only get the SD advertisement packet. Could you let me know if there are any other configurations to be changed?

I have also referred to the sdk v11 multiactivity_beacon : \examples\ble_peripheral\experimental_ble_app_multiactivity_beacon\hrs_advertiser

Thanks

RE: Eddystone and ibeacon with Timeslot API

TAR CHAL — Wed, 28 Feb 2018 16:05:10 GMT

Hi Håkon,

Thanks for reply, i followed your advise and effectively i switch between protocols in every timeslot, and it works, but there is a small problem, the advertising intervals for each format is not correct.

explanation :

i coded these adv intervals :

adv_int sofdevice advertisement = 200 ms;

adv_int ibeacon (timeslot) = 400 ms;

adv_int eddystone (timeslot)= 1000 ms

but with nrf connect i see these values :

adv_int sofdevice advertisement = 200 ms;

adv_int ibeacon = 1400 ms;

adv_int eddystone = 1400 ms

it seems like there is a sum of adv_int ibeacon and adv_int eddystone somewhere, i checked the code but i don't have any idea where the sum could be ?

i'll attach my final code, if you can check it and would you tell me where is the problem ?

thanks,

regards,

/cfs-file/__key/communityserver-discussions-components-files/4/advertiser_5F00_beacon_5F00_timeslot.c

RE: Eddystone and ibeacon with Timeslot API

Håkon Alseth — Tue, 27 Feb 2018 14:31:48 GMT

Hi,

Yes, you can merge the two. The logic depends on how you want this to work, but what you can do is to alternate between ibeacon and eddystone frames in the timeslot, or switch between the protocols in every other timeslot.

I'd recommend looking at the functions that are equal and combine them. After this, check the timeslot logic and do an alteration based on if the timeslot is supposed to be ibeacon or eddystone.

Same logic applies to the sys_handlers.

Best regards,

Håkon