Extended Advertising

[BarbaraTurner]

Hi, 

I'm trying to implement non-connectable, non-scannable, undirected extended advertising mode. I'm using nRF52832 board,  SDK 15.2.0 version and latest Softdevice 6.1. 0. version.

I'm getting ADV_EXT_IND on my sniffer but I'm not sure how to send data on secondnary channels. 

Could you help.

Barbara

[Simon]

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.

[BarbaraTurner]

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?

[BarbaraTurner]

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?

[Simon]

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

[BarbaraTurner]

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. 

[ntn]

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;

to

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 :)

[BarbaraTurner]

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.2335.extended adv sniffer snapshot.docx

I can see ADV_EXT_IND but no AUX_ADV_IND.

[Simon]

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.