Advertise Configuration of manufacturer specific data

RE: Advertise Configuration of manufacturer specific data

Simonr — Mon, 07 Dec 2020 11:56:29 GMT

Glad to hear that!

RE: Advertise Configuration of manufacturer specific data

RatocKen — Mon, 07 Dec 2020 02:34:22 GMT

Hi Simonr-san,

Thank you for your sound advice.

Following code work fine using ble_app_proximity sample code.

static void advertising_init(void)
{
    ret_code_t             err_code;
    ble_advertising_init_t init;

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

    // Configuration of manufacturer specific data ----------------------
	ble_advdata_manuf_data_t manuf_data; //Variable to hold manufacturer specific data
//                            1         2         3         4         5         6
	uint8_t data[] ="01234567890123456789012345678901234567890123456789012345678901";

	manuf_data.company_identifier = 0xFFFF; 
	manuf_data.data.p_data = data;
	manuf_data.data.size = sizeof(data);
	init.advdata.p_manuf_specific_data = &manuf_data;
	NRF_LOG_INFO("Size of manufacturer specific data: %d", manuf_data.data.size);

    init.advdata.name_type               = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance      = true;
    init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    init.advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    init.advdata.uuids_complete.p_uuids  = m_adv_uuids;

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;
    init.config.ble_adv_extended_enabled = true;

    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

RE: Advertise Configuration of manufacturer specific data

Simonr — Fri, 04 Dec 2020 13:36:28 GMT

Hi there

Indeed, the Running Speed and Cadence application does include extended advertising, so you can use the advertising_init() function there as reference when setting up your advertiser. From a first glance, it doesn't seem like you have included init.config.ble_adv_extended_enabled = true; to your advertising init function. I would also suggest setting the advertising data flags to BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE to put it in General Discoverable Mode when using extended advertising.

Best regards,

Simon

RE: Advertise Configuration of manufacturer specific data

hmolesworth — Fri, 04 Dec 2020 03:22:48 GMT

Ah, maybe have a look at .\examples\ble_peripheral\ble_app_rscs I seem to recall that project uses extended advertising. Otherwise someone from Nordic pitch in here?

RE: Advertise Configuration of manufacturer specific data

RatocKen — Fri, 04 Dec 2020 02:04:59 GMT

Thank you for quick reply.

I found following information "Extended Advertising support", why I can extend manufacturer specific data size?

infocenter.nordicsemi.com/index.jsp

S132 SoftDevice Specification
Key features

Extended Advertising support

Advertising and scanning up to 255 bytes of advertising data in an advertising event

RE: Advertise Configuration of manufacturer specific data

hmolesworth — Fri, 04 Dec 2020 01:51:23 GMT

The max length is 31 bytes, 32 is not an option. Have a look at my answer here for an explanation length-error-with-this-advertisement