Multilink central adding advertising. Error 12 on advertising_start()

RE: Multilink central adding advertising. Error 12 on advertising_start()

Philip — Tue, 23 Jul 2019 14:00:19 GMT

Thanks for the info.

Non connectable is not a massive deal for this application, would be nice to get it working but might give up on this for now as it is causing knock on issues else where.

RE: Multilink central adding advertising. Error 12 on advertising_start()

awneil — Tue, 23 Jul 2019 13:30:36 GMT

Note that the Advertising Module (used in most SDK 15 examples) does not let you do Non-Connectable advertising

https://devzone.nordicsemi.com/f/nordic-q-a/49354/non-connectable-advertising/196520#196520

https://devzone.nordicsemi.com/f/nordic-q-a/49872/advertise-connected-when-connected/198912#198912

RE: Multilink central adding advertising. Error 12 on advertising_start()

Philip — Tue, 23 Jul 2019 13:22:55 GMT

Thanks Joakim.

The advertising init is totally different to that in the NUS example, doesn't seem to be consistent across the examples. I managed to update my code so it uses the adv init function from blinky.

However I now can't get the power output function to work.

How would I modify the blinky example below to change the adv transmit power output? The below doesn't work, gives a 3004 error.

err_code = sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, &m_adv_handle, 8);
APP_ERROR_CHECK(err_code);

Thanks

static void advertising_init(void)
{
    ret_code_t    err_code;
    ble_advdata_t advdata;
    ble_advdata_t srdata;

    uint8_t testData[8] = {0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88 };

    ble_advdata_manuf_data_t manuf_specific_data;
    manuf_specific_data.company_identifier = APP_COMPANY_IDENTIFIER;
    manuf_specific_data.data.p_data = testData;
    manuf_specific_data.data.size   = 0x08;

    ble_uuid_t adv_uuids[] = {{LBS_UUID_SERVICE, m_lbs.uuid_type}};

    // Build and set advertising data.
    memset(&advdata, 0, sizeof(advdata));

    advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    advdata.include_appearance = true;
    advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    advdata.p_manuf_specific_data = &manuf_specific_data;

    memset(&srdata, 0, sizeof(srdata));
    srdata.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);
    srdata.uuids_complete.p_uuids  = adv_uuids;

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = ble_advdata_encode(&srdata, m_adv_data.scan_rsp_data.p_data, &m_adv_data.scan_rsp_data.len);
    APP_ERROR_CHECK(err_code);

    ble_gap_adv_params_t adv_params;

    // Set advertising parameters.
    memset(&adv_params, 0, sizeof(adv_params));

    adv_params.primary_phy     = BLE_GAP_PHY_1MBPS;
    adv_params.duration        = APP_ADV_DURATION;
    adv_params.properties.type = BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED;
    adv_params.p_peer_addr     = NULL;
    adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    adv_params.interval        = APP_ADV_INTERVAL;

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &adv_params);
    APP_ERROR_CHECK(err_code);
}

RE: Multilink central adding advertising. Error 12 on advertising_start()

Joakim Jakobsen — Mon, 22 Jul 2019 12:36:18 GMT

Hi.

In order to set the advertising type as non-connectable, you have to change the advertising event properties (ref. ble_gap.h, line: 663).

You can take a look how the advertising type is set in the ble_app_blinky example (ref. main.c, line: 242).

Refer to ble_gap.h, line:360 for the different GAP Advertising types.

Best regards,
Joakim

RE: Multilink central adding advertising. Error 12 on advertising_start()

Philip — Thu, 18 Jul 2019 11:14:29 GMT

Edit: I had to make NRF_SDH_BLE_PERIPHERAL_LINK_COUNT = 1 in the config file.

It is advertising now, but as connectable device. Where in the advertsing_init function do I set it to be non-connectable?

Thanks