Telink TLSR8232 BLE SDK Developer Handbook
AN-19112700-E1 75 Ver.1.0.0
As required by BLE Spec, it’s not recommended to set adv interval as fixed value; in
Telink BLE SDK, the eventual adv interval is random variable within the range of
intervalMin ~ intervalMax. If intervalMin and intervalMax are set as same value, adv
interval will be fixed as the intervalMin.
Adv packet type has limits to the setting of intervalMin and intervalMax. Please refer
to Core_v5.0 (Vol 6/Part B/ 4.4.2.2 “Advertising Events”) for details.
2) advType
As specified in BLE Spec, the following four basic advertising event types are
supported.
Figure 3-24 Four Adv Events in BLE Stack
In the “Allowable response PDUs for advertising event” column, “YES” and “NO”
indicate whether corresponding adv event type can respond to “Scan request” and
“Connect Request” from other device. For example, “Connectable Undirected Event”
can respond to both “Scan request” and “Connect Request”, while “Non-connectable
Undirected Event” will respond to neither “Scan request” nor “Connect Request”.
For “Connectable Directed Event”, “YES” marked with an asterisk indicates the
matched “Connect Request” received won’t be filtered by whitelist and this event will
surely respond to it. Other “YES” not marked with asterisk indicate corresponding
request can be responded depending on the setting of whitelist filter.
Among the four advertising events “Connectable Directed Event” supports two sub-
types including “Low Duty Cycle Directed Advertising” and “High Duty Cycle Directed
Advertising”. Therefore, five types of adv events are supported in all, as defined in
“stack/ble/ble_common.h”:
/* Advertisement Type */
typedef enum{
ADV_TYPE_CONNECTABLE_UNDIRECTED = 0x00, // ADV_IND
ADV_TYPE_CONNECTABLE_DIRECTED_HIGH_DUTY = 0x01,
//ADV_INDIRECT_IND (high duty cycle)
ADV_TYPE_SCANNABLE_UNDIRECTED = 0x02 //ADV_SCAN_IND
To Next Page
Loading...