advertising PDUs

wireHound

I have a central device that scans for and then connects to a peripheral device. Most of the the time the scan and link establishment process works without any problems. Occasionally, however, I notice that I am not able to make that connection. When I sniff the data packets using the TI Packet Sniffer program I notice that when I am not able to connect my central device witha peripheral device I am getting a repeated 'ADV_NON_CONN_IND' type of advertisment packet that my central device seems to be ignoring.

What is the ADV_NON_CONN_IND data packet and how should I be responding to it?

Thanks...

over 11 years ago

0 J Lindh over 11 years ago

TI__Guru 57865 points

Hi Ben,

ADV_NONCONN_IND packets are nonconnectable advertisement packets, so essentially broadcast packets. A central device cannot and will not connect to those, so no response at all from central.

Best Regards

0 wireHound over 11 years ago in reply to J Lindh

Intellectual 430 points

What is the purpose of a 'broadcast' advertisement package? How do I interpret the data in one of those packets? Where can I find information regarding the advertisement modes and data packages ane the process? I have lookin the bluetooth core document, but I find it very confusing and in some cases kind fo vague. Are there any other resources that explain some of the bluetooth process and modes?

Thanks...

0 Aslak N. over 11 years ago in reply to wireHound

TI__Mastermind 23440 points

Hi Ben,

The purpose is to broadcast meaningful data without being in a connection. I.e. to broadcast.

See the spec vol 3, part c, ch 18 for the different formats your data may have. You may be most interested in 18.11.

Basically, a nugget of advertisement data (broadcast if Non-connectable) consists of [len of flag+data][flag][data]

BR,
Aslak

0 wireHound over 11 years ago in reply to Aslak N.

Intellectual 430 points

Thank you Aslak and Joakim, both of your responses were helpful. I found the data first included a length byte followed by a flag that idendtified the type of data that was to follow, (core document vol 3; part c; ch 18 like you mentioned). I noticed that the flag was included with the data when the length was determined.

Thanks again....

0 Peyton Davari over 9 years ago in reply to Aslak N.

Expert 1180 points

HI,

Could you let me know what the core document being referred to in this thread is? Thanks.

0 Peyton Davari over 9 years ago in reply to Peyton Davari

Expert 1180 points

For Future Reference:

https://www.bluetooth.org/en-us/specification/adopted-specifications

0 Kadari Rajamallaiah over 8 years ago in reply to Peyton Davari

Intellectual 685 points

Hi Aslak ,

can we find out no.of Advertised packets since cc2541-ble powered up? if yes how to do it?

0 Aslak N. over 8 years ago in reply to Kadari Rajamallaiah

TI__Mastermind 23440 points

Hi,

Yes, but you need to keep track of it yourself.

Use the API called HCI_EXT_AdvEventNoticeCmd( uint8 taskID, uint16 taskEvent ), where you input your task ID and an event # that your ProcessEvent function should be called with.

This can be done after the device is started, for example in the case GAPROLE_STARTED:. You will get one OSAL event after each advertising event.

Best regards,
Aslak

0 Kadari Rajamallaiah over 8 years ago in reply to Aslak N.

Intellectual 685 points

Hello Aslak ,

I am getting an osal_event from HCI_EXT_AdvEventNoticeCmd( uint8 taskID, uint16 taskEvent ) after advertisement event completes , but this is happening initially once . I want to count total advertisement frames .

Can you suggest do I need to do any changes in my code

Bluetooth®︎

Bluetooth forum

advertising PDUs