Re: Advertising and scanning states in Bluetooth Low-Energy
Re: Advertising and scanning states in Bluetooth Low-Energy
- Subject: Re: Advertising and scanning states in Bluetooth Low-Energy
- From: Joakim Linde <email@hidden>
- Date: Fri, 17 Feb 2012 00:29:31 -0800
Hi Pietro,
Please see comments below.
Thanks, Joakim
On Feb 14, 2012, at 3:43 AM, pietro gonizzi wrote: Hi Joakim,
thanks for replying.
For instance, if you use Advertising Interval=20 ms, then the time between two consecutive PDUs should be at least less than 20/3=6.66 ms. Is this correct?
| No, the advertising PDUs can be clustered. Meaning, you can send them back to back at the beginning of the event.
So, if you send 3 PDUs back to back on 3 different channels (37, 38, and 39, respectively) you then have to synchronize the receiver to these channels to listen to a response PDU. For instance, let's suppose that the advertising PDU is of type ADV_IND and the response PDU is either of type SCAN_REQ or CONNECT_REQ. How do you know the exact time interval you have to listen to each channel?
You don't. Since the two devices are not yet connected, they are not time synchronized. The observer will have to scan for the broadcasters advertising packet.
You then have to do channel switching, isn't it?
The observer switches channel every so often.
Pietro
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden