You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run the program first:
btle_rx -c chan -g gain -a access_addr -k crc_init -o
I can see the adv data,then I connect my phone with bluetooth modules,but I can not see the hopping data,any help will be appreciated.
The text was updated successfully, but these errors were encountered:
@lanlanwei This may be because you are looking in the wrong place. Since Bluetooth core V4.0, connection requests in the form of AUX_CONNECT_REQ can go across the secondary advertising channels. These channels are specified as the 37 PHY channels that were previously reserved for Data PDUs. There is no difference between the packet structures of the CONNECT_IND and the AUX_CONNECT_REQ. The only difference is the latter is part of the new extended advertising protocol and is triggered by ADV_EXT_IND on one of the data channels (BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 6, Part B Section 4.4.2.4.4)
So if you have a bluetooth device that implements V4.0+ you may have to scour the data channels instead.
From the Bluetooth Core Specification page:
BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 6, Part B Section 2.3
BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 1, Part A Section 3.3.2.2.2
I run the program first:
btle_rx -c chan -g gain -a access_addr -k crc_init -o
I can see the adv data,then I connect my phone with bluetooth modules,but I can not see the hopping data,any help will be appreciated.
The text was updated successfully, but these errors were encountered: