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
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,14 @@ A BTLE (Bluetooth Low energy)/BT4.0 radio packet sniffer/scanner and sender ( bu
5
5
6
6
# News (See complete introduction section after news section):
7
7
8
-
## Nov. 2015: So excited that the packet sniffer/scanner btle_rx can follow BTLE hopping data channels now! It follows ~8ms hopping link successfully! (Because the fastest speed of my btle_tx is about 8ms gap between successive packets). Currently it only works on a simple case (which is the most cases in real world) where channel mapping is 0x1FFFFFFFFF (This means all data channel 0~36 will be used for freq hopping). btle_rx is a fast moving target currently. More for demonstration purpose than full verification for now. Will release more soon.
8
+
## Nov. 2015: So excited that the HACKRF BTLE packet sniffer/scanner can follow hopping data channels automatically now! Just like TI's sniffer.
9
9
10
10
New added options:
11
11
12
+
-o --hop
13
+
14
+
This will turn on data channel tracking (frequency hopping) after link setup information is captured in ADV_CONNECT_REQ packet.
15
+
12
16
-f --freq_hz
13
17
14
18
This frequency (Hz) will override channel setting (In case someone want to work on freq other than BTLE. More general purpose).
@@ -17,10 +21,6 @@ This frequency (Hz) will override channel setting (In case someone want to work
17
21
18
22
If a bit is 1 in this mask, corresponding bit in access address will be taken into packet existing decision (In case someone want a shorter/sparser unique word to do packet detection. More general purpose).
19
23
20
-
-o --hop
21
-
22
-
This will turn on data channel tracking (frequency hopping) after link setup information is captured in ADV_CONNECT_REQ packet.
0 commit comments