Connectable vs. nonconnectable Advertisements.

Ask the Community
Close
Ask the Community
nav search Icon
Forums gray-arrow gray-arrow
Resources gray-arrow gray-arrow
About gray-arrow gray-arrow
Groups gray-arrow gray-arrow
nav-user Account

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob

Connectable vs. nonconnectable Advertisements.

Anonymous
Not applicable
‎Aug 26, 2014 03:38 PM
‎Aug 26, 2014 03:38 PM
Jump to solution

Dear WICED BLE Forum,

According to "Bluetooth Low Energy: The Developer's Handbook", page 81, there are seven types of advertising packets:

ADV_IND, ADV_DIRECT_IND, ADV_NONCONN_IND, ADV_SCAN_IND, SCAN_REQ, SCAN_RSP, CONNECT_REQ.

How may I generate ADV_NONCONN_IND or ADV_SCAN_IND in my WICED-Smart application?  In particular I would

like to advertise/broadcast dynamic information at a low data rate while I am connected to a central device. 

--Blake.

Labels
0 Likes
Subscribe
1 Solution

Re: Connectable vs. nonconnectable Advertisements.

Anonymous
Not applicable
‎Aug 26, 2014 05:16 PM
‎Aug 26, 2014 05:16 PM
Jump to solution

Hello Blake,

We have several Apps in our SDK 2.1 that show the types of Advertising Packets:

Hello_Sensor is a Connectable Advertisement as you might have guessed.  It can also send Notifications and Indications from the Peripheral.

We also have a my_beacon app that uses a Non-connectable undirected advertisement.

We have an ibeacon_device with hard-coded UUID, Major/Minor Numbers and Xmit Power and you can easily advertise as a beacon and be in a connection with a Central to send dynamic data as you would with hello_sensor.c App.

But hello_sensor is a great place to start.

Hope this helps

JT

View solution in original post

4 Replies