Extended Advertising

RE: Extended Advertising

Simon — Mon, 23 Mar 2020 10:00:21 GMT

Do you have any questions? If so, could you open a new ticket and address them there?

Best regards,

Simon

RE: Extended Advertising

Salman — Sun, 22 Mar 2020 07:24:28 GMT

I was able to set 230 bytes of data in adv. This is how I was able to do with example "ble_app_rscs" in function "advertising_init"

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

uint8_t temp_data[230];

for(uint8_t i = 1 ; i <= 230; i++)
temp_data[i] = i;

adv_tmp_data.company_identifier = 0x1111;
adv_tmp_data.data.size = sizeof(temp_data);
adv_tmp_data.data.p_data = temp_data;

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

//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.advdata.p_manuf_specific_data = &adv_tmp_data;

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_primary_phy = BLE_GAP_PHY_1MBPS;
init.config.ble_adv_secondary_phy = BLE_GAP_PHY_2MBPS;
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: Extended Advertising

Simon — Thu, 10 Jan 2019 14:44:47 GMT

I modified the rscs example (using the nRF52832, SDK 15.2 and SoftDevice S132 6.1.0) in the same manner as you did, and I was able to successfully show both the ADV_EXT_IND and the AUX_ADV_IND packets using the sniffer (see image below). I am using the the Ellisys Vanguard sniffer along with the software Ellisys Bluetooth Analyzer.

Based on my findings it seems like the problem is with your sniffer, and a reason could be that you haven't enabled Extended advertising. In the Ellisys program, this is done by clicking Record->Recording Options->Wireless->(Check the boxes 2Mbps and Advertising Extension).

Best regards,

Simon

RE: Extended Advertising

Simon — Wed, 09 Jan 2019 16:13:30 GMT

Been a little busy lately, but I will take a look at the document tomorrow.

RE: Extended Advertising

BarbaraTurner — Tue, 08 Jan 2019 16:12:06 GMT

Hi Simon,

the attached file explains my findings and questions.

Thanks

devzone.nordicsemi.com/.../ExtendedAdvertisingEval.docx

RE: Extended Advertising

Simon — Tue, 08 Jan 2019 09:47:49 GMT

Have you been able to figure this out, or should I look into it?

RE: Extended Advertising

Simon — Thu, 20 Dec 2018 16:52:27 GMT

The advertising packet from the sniffer results seems correct, as seen here the payload of the extended advertisement packet should include the field "Extended Header", which your advertisement packet indeed does. As explained here the "Extended Header" field contains a sub-field AUX Pointer, and gives infomation on what channel to look for to find the actual data. In your case it ponts to channel 15. Thus, the packet ADV_EXT_IND points to channel 15 where the auxiliary advertisement packet (AUX_ADV_IND) can be found.

I am not sure what the problem actually is? That the sniffer is not capable of displaying the extended data packet (AUX_ADV_IND), or that the nRF-device hasn't actually sent the extended data?

I am not at the office at the moment and does not have the possibility to test it out, and most of the support people have taken vacation. But I have the posssibility to dig deeper into it from the 7'th of january. However, I will do some more research online and see if I can figure out your problem.

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 13:54:55 GMT

Hi the above file is a screenshot of your ble_app_rscs project. It fails. It reports error 9, null pointer.

I have moded this example, as I need rf to work in NONCONNECTABLE_NONSCANNABLE_UNDIRECTED mode. You can see snapshot from the sniffer below.devzone.nordicsemi.com/.../2335.extended-adv-sniffer-snapshot.docx

I can see ADV_EXT_IND but no AUX_ADV_IND.

RE: Extended Advertising

ntn — Wed, 19 Dec 2018 12:00:39 GMT

There's no SDK for that in SDK15.2. You need to modify SDK manually.

SDK 15.2, file ble_advertising.c, line 317,

Change

p_advertising->adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED;

p_advertising->adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;

That works for me. If that doesn't work for you, good luck Nordic guys :)

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 11:53:01 GMT

Simon, are you in position to answer my question or I need to speak to local Nordic representative? Your example ble_app_rscs hits the NULL pointer error btw.

RE: Extended Advertising

Simon — Wed, 19 Dec 2018 11:21:36 GMT

Sorry, my fault. For some reason I thought you were using the nRF Sniffer. Then forget everythin I have said.

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 11:20:08 GMT

Errrr....?????????Are you saying that BLE Sniffer doesn't support extended advertising or Nordic doesn't. And how do you know which sniffer I am using? So to clarify that for you I am using Teledyne sodera sniffer with the latest firmware that supports extended advertising.

You still haven't answered my question. Does Nordic support non-connectable, non-scannable, undirected mode?

RE: Extended Advertising

Simon — Wed, 19 Dec 2018 11:15:08 GMT

I've got it confirmed from the people developing the nRF Sniffer, it does not support extended advertising at the moment.

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 10:19:54 GMT

Right, I'm using the sniffer to analyse what the radio is doing. Can you then clarify whether you support, non-connectable, non-scannable, undirected mode? Where can I get this information from?

RE: Extended Advertising

Simon — Wed, 19 Dec 2018 10:01:41 GMT

I don't know what the core of the issue is? Even though you have set it up properly on the chip-side, I am afraid it won't show up in nRF Sniffer, since it is not supported yet. See the comment from respectively Sigurd and Mohammad, here and here. As explained here, the ADV_EXT_IND packet is the initial packet, sent on the advertising channels 37, 38 and 39. The AUX_ADV_IND packet is sent on one of the 37 data channels, and can contain more data, but I am not too familiar with the sniffer and don't know how to make this show up there.

Do you have another nRF chip that supports extended advertising? Then you can use BLE Running Speed and Cadence Collector Example to confirm that the Running Speed and Cadence Application works.

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 09:57:07 GMT

I used your ble_app_rscs example as a baseline and modify it for my use case. I need non-conetable, non-scannable, undirected mode. I do get ADV_EXT_IND but no AUX_ADV_IND.

RE: Extended Advertising

ntn — Wed, 19 Dec 2018 09:51:18 GMT

When you put data in to advertising packet (like in RSCS example), SoftDevice automatically put it into secondary channel (0-36). There's nothing special you need to do for that to happen.

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 09:24:44 GMT

I can't find any explanation to how to put the data on secondary channels in your documentation. Could you please show some working example.

RE: Extended Advertising

BarbaraTurner — Wed, 19 Dec 2018 09:22:12 GMT

Your example doesn't work.

RE: Extended Advertising

ntn — Wed, 19 Dec 2018 08:03:11 GMT

You can look into RSCS example in SDK15.2, located at nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_rscs.

RE: Extended Advertising

BarbaraTurner — Tue, 18 Dec 2018 17:22:28 GMT

I set adv_data.adv_data.len to 238 (extended advertising ) but sd_ble_gap_adv_set_configure() turncate it to 65.

RE: Extended Advertising

Simon — Tue, 18 Dec 2018 16:06:37 GMT

I currently looking into your problem and will reply as soon as I figure it out