Closed neilyoung closed 6 years ago
neilyoung
commented
7 years ago Interesting turn in this matter: Up to now I just tested with RadBeacons (Dot). Now I used my iPhone as virtual Estimote beacon. And scans come in. The RSSI values are still nonsense (e.g. -8 very close to the beacon), but at least I receive scans...
heyinling
commented
7 years ago Hi @neilyoung ,
regarding the RSSI issue, the result I read from ESP_GAP_SEARCH_INQ_RES_EVT is consistent.
Here's the scan result I've got:
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-62,1a
+BTSCAN:INQ,24:0a:c4:03:f3:96,UGyJkawBIT,-48,02
+BTSCAN:INQ,7a:a4:60:dc:c8:54,NULL,-70,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-80,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-75,1a
+BTSCAN:INQ,76:3c:0d:b1:51:0a,NULL,-77,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-66,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-79,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-69,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-79,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-68,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-68,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-63,1a
+BTSCAN:INQ,76:3c:0d:b1:51:0a,NULL,-76,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-66,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-76,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-80,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-67,1a
+BTSCAN:INQ,76:3c:0d:b1:51:0a,NULL,-73,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-76,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-79,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-73,1a
+BTSCAN:INQ,76:3c:0d:b1:51:0a,NULL,-73,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-80,1a
+BTSCAN:INQ,7a:a4:60:dc:c8:54,NULL,-67,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-84,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-78,1a
+BTSCAN:INQ,24:0a:c4:03:f3:96,UGyJkawBIT,-46,02
+BTSCAN:INQ,7a:a4:60:dc:c8:54,NULL,-68,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-65,1a
+BTSCAN:INQ,7b:80:8e:e0:de:d7,NULL,-78,1a
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-60,1a
+BTSCAN:INQ,76:3c:0d:b1:51:0a,NULL,-76,1a
+BTSCAN:INQ,7b:88:26:5f:1a:6c,NULL,-83,1a
+BTSCAN:INQ,24:0a:c4:03:f3:96,UGyJkawBIT,-44,02
+BTSCAN:INQ,08:66:98:8c:ce:7e,NULL,-69,1a @heyinling : Yes, in fact, this looks awesome and as it should be. What board? What beacons? What happens, if you move the board very close to the beacon? I'm reading things like "-8" and "-10" then, complete nonsense and impossible.
neilyoung
commented
7 years ago Here is my latest result, scanning an Estimote Hardware beacon, which has a very weak battery. An Android sniffer shows approx -77 dBm while laying 5 cm left of the beacon. The Sparkfun shows this (note the times: I would expect to get ways more callbacks, because the Estimote advertises every 500 ms) while laying 1 m apart
I (3035) ble1: BDA: ea:19:6f:c1:48:39, RSSI -60 I (3645) ble1: BDA: ea:19:6f:c1:48:39, RSSI -61 I (5475) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (9775) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (12225) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (13445) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (14685) ble1: BDA: ea:19:6f:c1:48:39, RSSI -67 I (17745) ble1: BDA: ea:19:6f:c1:48:39, RSSI -61 I (18975) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (19585) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (23875) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (24485) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (25725) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (26335) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (26945) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (28795) ble1: BDA: ea:19:6f:c1:48:39, RSSI -70 I (30025) ble1: BDA: ea:19:6f:c1:48:39, RSSI -59 I (30635) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (32475) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (34925) ble1: BDA: ea:19:6f:c1:48:39, RSSI -64 I (35535) ble1: BDA: ea:19:6f:c1:48:39, RSSI -65 I (37995) ble1: BDA: ea:19:6f:c1:48:39, RSSI -58 I (39225) ble1: BDA: ea:19:6f:c1:48:39, RSSI -56 I (39845) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (41075) ble1: BDA: ea:19:6f:c1:48:39, RSSI -66 I (41685) ble1: BDA: ea:19:6f:c1:48:39, RSSI -62 I (43525) ble1: BDA: ea:19:6f:c1:48:39, RSSI -59 I (44145) ble1: BDA: ea:19:6f:c1:48:39, RSSI -60 I (45375) ble1: BDA: ea:19:6f:c1:48:39, RSSI -56 I (45985) ble1: BDA: ea:19:6f:c1:48:39, RSSI -55 I (47825) ble1: BDA: ea:19:6f:c1:48:39, RSSI -61 I (48445) ble1: BDA: ea:19:6f:c1:48:39, RSSI -61 I (49665) ble1: BDA: ea:19:6f:c1:48:39, RSSI -61 I (50285) ble1: BDA: ea:19:6f:c1:48:39, RSSI -62 I (52725) ble1: BDA: ea:19:6f:c1:48:39, RSSI -56 I (53335) ble1: BDA: ea:19:6f:c1:48:39, RSSI -55 I (55175) ble1: BDA: ea:19:6f:c1:48:39, RSSI -61 I (55785) ble1: BDA: ea:19:6f:c1:48:39, RSSI -60 I (57015) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (57635) ble1: BDA: ea:19:6f:c1:48:39, RSSI -57 I (58865) ble1: BDA: ea:19:6f:c1:48:39, RSSI -56 I (60095) ble1: BDA: ea:19:6f:c1:48:39, RSSI -56
You see, it is somehow constant, but ways too optimistic.
Then these are the results, if I let my iPhone make an Estimote vitrtual beacon. The readings are really following my movements (better if closer, worse if away), but what are these -8, -11 while having the Sparkfun laying on the iPhone? I have never seen such strong readings on every sniffer I used so far. This is simply physically impossible to be true.
I (365) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (495) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (655) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (815) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (845) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -20 I (905) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -19 I (1165) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -20 I (1205) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -19 I (1265) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (1295) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -20 I (1305) ble1: BDA: ea:19:6f:c1:48:39, RSSI -46 I (1365) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -19 I (1395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -20 I (1495) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -19 I (1555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (1755) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -20 I (1815) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -17 I (1875) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -19 I (1915) ble1: BDA: ea:19:6f:c1:48:39, RSSI -51 I (1915) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -18 I (1945) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -17 I (2015) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -18 I (2045) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -17 I (2145) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -18 I (2455) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -14 I (2555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (2615) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -13 I (2725) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (2895) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (3145) ble1: BDA: ea:19:6f:c1:48:39, RSSI -64 I (3155) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (3255) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (3315) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -13 I (3345) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (3415) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (3505) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (3575) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (3605) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -13 I (3665) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (3695) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (3755) ble1: BDA: ea:19:6f:c1:48:39, RSSI -64 I (3795) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (3855) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (3955) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (4055) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -14 I (4305) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (4395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (4455) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (4495) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -15 I (4565) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (4655) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -16 I (4855) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (4915) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (5005) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (5105) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -16 I (5145) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (5205) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (5265) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -16 I (5295) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (5395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -16 I (5455) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (5555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -16 I (5605) ble1: BDA: ea:19:6f:c1:48:39, RSSI -64 I (5615) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (5645) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (5815) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (5905) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (5945) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (6005) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -16 I (6065) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (6095) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (6195) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (6215) ble1: BDA: ea:19:6f:c1:48:39, RSSI -64 I (6315) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -15 I (6345) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (6405) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (6445) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -15 I (6505) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (6565) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (6595) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -15 I (6655) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (6695) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (6795) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (6915) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -15 I (6945) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (7005) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (7045) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -14 I (7105) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (7205) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -12 I (7365) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (7395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (7495) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (7555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (7715) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (7845) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8005) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8165) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8295) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -10 I (8615) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8705) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (8765) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8865) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (8895) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (8995) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (9065) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (9155) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (9215) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (9345) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (9445) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (9505) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (9605) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -9 I (9665) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (9765) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (9795) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (9915) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (9955) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (10045) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (10105) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (10205) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (10365) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -8 I (10395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -7 I (10495) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -11 I (10555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -19 I (10645) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -17 I (10715) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -13 I (10805) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (10865) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -24 I (10955) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -21 I (11025) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -23 I (11115) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -29 I (11245) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -31 I (11305) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -34 I (11405) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -30 I (11465) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -33 I (11555) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -38 I (11615) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -42 I (11705) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -46 I (11765) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -34 I (11865) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -46 I (11895) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -41 I (11995) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -42 I (12055) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -40 I (12155) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -43 I (12225) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -41 I (12315) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -37 I (12345) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -36 I (12355) ble1: BDA: ea:19:6f:c1:48:39, RSSI -67 I (12445) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -39 I (12505) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -36 I (12665) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -49 I (12765) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -32 I (12915) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -33 I (13045) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -34 I (13205) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -30 I (13395) ble1: BDA: 59:bb:83:e7:c6:dc, RSSI -33
And a RadBeacon (Dot) is not seen at all... I'm not even sure, if it is the ESP-IDF software or the Sparkfun hardware...
neilyoung
commented
7 years ago Maybe code sharing helps to come behind:
Here is the code:
EDIT: Updated as a result of later posts
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "sdkconfig.h"
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "freertos/event_groups.h"
#include "esp_system.h"
#include "esp_wifi.h"
#include "esp_event_loop.h"
#include "esp_log.h"
#include "nvs_flash.h"
#include "bt.h"
#include "esp_blufi_api.h"
#include "esp_bt_defs.h"
#include "esp_gap_ble_api.h"
#include "esp_bt_main.h"
#include "esp_bt_device.h"
extern void bt_task(void *ignore);
static const char tag[] = "BLE";
static uint8_t ibeacon_prefix[] = {
0x02,0x01,0x00,0x1A,0xFF,0x4C,0x00,0x02,0x15
};
void gap_event_handler(esp_gap_ble_cb_event_t event, esp_ble_gap_cb_param_t *param) {
esp_ble_gap_cb_param_t *p = (esp_ble_gap_cb_param_t *)param;
//ESP_LOGI(tag, "device address (bda): %02x:%02x:%02x:%02x:%02x:%02x", BT_BD_ADDR_HEX(p->scan_rst.bda));
if (p->scan_rst.search_evt == ESP_GAP_SEARCH_INQ_RES_EVT) {
// Check for iBeacon adv prefix. Ignore 3rd byte, this varies from beacon type to beacon type
p->scan_rst.ble_adv[2] = 0x00;
for (int i=0; i < sizeof(ibeacon_prefix); i++) {
if (p->scan_rst.ble_adv[i] != ibeacon_prefix[i]) {
return;
}
}
ESP_LOGI(tag, "BDA %02X:%02X:%02X:%02X:%02X:%02X, RSSI %d, UUID %02X%02X%02X%02X-%02X%02X-%02X%02X-%02X%02X-%02X%02X%02X%02X%02X%02X MAJ %d, MIN %d, TXPWR %d",
p->scan_rst.bda[0],
p->scan_rst.bda[1],
p->scan_rst.bda[2],
p->scan_rst.bda[3],
p->scan_rst.bda[4],
p->scan_rst.bda[5],
p->scan_rst.rssi,
p->scan_rst.ble_adv[9],
p->scan_rst.ble_adv[10],
p->scan_rst.ble_adv[11],
p->scan_rst.ble_adv[12],
p->scan_rst.ble_adv[13],
p->scan_rst.ble_adv[14],
p->scan_rst.ble_adv[15],
p->scan_rst.ble_adv[16],
p->scan_rst.ble_adv[17],
p->scan_rst.ble_adv[18],
p->scan_rst.ble_adv[19],
p->scan_rst.ble_adv[20],
p->scan_rst.ble_adv[21],
p->scan_rst.ble_adv[22],
p->scan_rst.ble_adv[23],
p->scan_rst.ble_adv[24],
(p->scan_rst.ble_adv[25] << 8) | p->scan_rst.ble_adv[26],
(p->scan_rst.ble_adv[27] << 8) | p->scan_rst.ble_adv[28],
p->scan_rst.ble_adv[29]-256
);
}
}
void bt_task(void *ignore) {
esp_err_t ret;
esp_bt_controller_init();
ret = esp_bt_controller_enable(ESP_BT_MODE_BTDM);
if (ret) {
ESP_LOGE(tag, "%s enable bt controller failed\n", __func__);
goto end;
}
ret = esp_bluedroid_init();
if (ret != ESP_OK) {
ESP_LOGE(tag, "%s init bluedroid failed\n", __func__);
goto end;
}
ret = esp_bluedroid_enable();
if (ret) {
ESP_LOGE(tag, "%s enable bluedroid failed\n", __func__);
goto end;
}
ret = esp_ble_gap_register_callback(gap_event_handler);
if (ret != ESP_OK) {
ESP_LOGE(tag, "esp_ble_gap_register_callback: rc=%d", ret);
goto end;
}
static esp_ble_scan_params_t ble_scan_params = {
.scan_type = BLE_SCAN_TYPE_PASSIVE,
.own_addr_type = ESP_PUBLIC_ADDR,
.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL,
.scan_interval = 1600,
.scan_window = 1600
};
ret = esp_ble_gap_set_scan_params(&ble_scan_params);
if (ret != ESP_OK) {
ESP_LOGE(tag, "esp_ble_gap_set_scan_params: rc=%d", ret);
goto end;
}
ret = esp_ble_gap_start_scanning(60);
if (ret != ESP_OK) {
ESP_LOGE(tag, "esp_ble_gap_start_scanning: rc=%d", ret);
goto end;
}
ESP_LOGI(tag, "Wait for scans...");
end:
vTaskDelete(NULL);
}
void app_main(void) {
xTaskCreatePinnedToCore(&bt_task, "btTask", 2048, NULL, 1, NULL, 0);
}The code is scanning for 60 seconds and it is examining incoming traces in order to accept just iBeacon advertisements. I have tried to vary esp_ble_scan_params_t to no avail.
Some info regarding the environment:
(29) boot: ESP-IDF v2.0-rc1-257-g4745895 2nd stage bootloader
I (29) boot: compile time 02:20:42
I (56) boot: Enabling RNG early entropy source...
I (56) boot: SPI Speed : 40MHz
I (56) boot: SPI Mode : DIO
I (59) boot: SPI Flash Size : 4MB
I (69) boot: Partition Table:
I (77) boot: ## Label Usage Type ST Offset Length
I (96) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (116) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (137) boot: 2 factory factory app 00 00 00010000 00100000
I (157) boot: End of partition table
This code running on a Sparkfun ESP32Thing does
1) Just displaying scattered scans from an Estimote Hardware beacon with weak battery like so:
I (325) BLE: Wait for scans... I (2745) BLE: BDA: ea:19:6f:c1:48:39, RSSI -60 I (4585) BLE: BDA: ea:19:6f:c1:48:39, RSSI -58 I (5205) BLE: BDA: ea:19:6f:c1:48:39, RSSI -60 I (13205) BLE: BDA: ea:19:6f:c1:48:39, RSSI -61 I (15045) BLE: BDA: ea:19:6f:c1:48:39, RSSI -67 I (15655) BLE: BDA: ea:19:6f:c1:48:39, RSSI -67
Looks OK, but frequency of scans results is too low and RSSI is too high.
2) Does show this with an iPhone running an virtual beacon Estimote beacon:
I (6445) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6515) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6545) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -8 I (6605) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6635) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6695) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -8 I (6735) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6795) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6865) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -8 I (6895) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6955) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (6985) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -8 I (7045) BLE: BDA: ea:19:6f:c1:48:39, RSSI -59 I (7045) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (7115) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (7145) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -8 I (7255) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9 I (7305) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -8 I (7335) BLE: BDA: 5a:4d:31:43:d2:21, RSSI -9
Frequency is OK, IMHO, but RSSI is nonsense... The Sparkfun lies on top of the iPhone.
3) Does literally show NOTHING at all (OK, maybe one or two in a minute, if in luck), if scanning a RadBeacon Dot.
What am I doing wrong?
TianHao-Yoursmake
commented
7 years ago .[0;31mE (531) BT: bta_dm_co_ble_load_local_keys: func not ported .[0m .[0;32mI (541) GATTC_DEMO: register callback .[0m .[0;32mI (541) GATTC_DEMO: EVT 0, gattc if 4 .[0m .[0;32mI (541) GATTC_DEMO: REG_EVT .[0m .[0;32mI (551) GATTC_DEMO: EVT 0, gattc if 5 .[0m .[0;32mI (551) GATTC_DEMO: REG_EVT .[0m BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
BD_ADDR: .c6:0e:71:b1:d0:7a:ADV_DATA: .02:01:06:1a:ff:4c:00:02:15:fd:a5:06:93:a4:e2:4f:b1:af:cf:c6:eb:07:64:78:25:27:32:e6:08:c5:02:
BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
BD_ADDR: .4e:0e:d3:9c:ab:5f:ADV_DATA: .02:01:1a:1a:ff:4c:00:02:15:bd:5f:80:21:33:31:49:ec:9e:df:9d:2d:62:ce:d7:70:00:01:00:01:c8:00:
Hi, this is iBeacon which esp32 received. I show the BD_ADDR and ADV_DATA. This iBeacon is sent by "iBeacon Scanner" application of iPhone.
neilyoung
commented
7 years ago @TianHao-Espressif Thanks for the trace. Unfortunately it does not show the timestamps and I can also not see the measured RSSI values. What kind of development board did you use? I can confirm, that virtual beacons (this is what you have produced with the iPhone app) work as best. But I have serious problems with several kind of hardware beacons.
Would you mind to use my little code snippet above and re-produce your trace with this?
BTW: This is the trace the iBeacon Scanner app produces here:
I (23955) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -25 I (24035) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -33 I (24105) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -24 I (24135) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -24 I (24195) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -33 I (24225) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -26 I (24295) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -24 I (24355) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -32 I (24385) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -30 I (24555) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -32 I (24585) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -28 I (24655) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -32 I (24685) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -48 I (24745) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -39 I (24775) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -35 I (24825) BLE: BDA: d4:38:ed:41:67:8b, RSSI -54 I (24835) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -30 I (24935) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -27 I (24995) BLE: BDA: c1:3f:fc:fb:03:e5, RSSI -57 I (24995) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -22 I (25035) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -25 I (25095) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -27 I (25125) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -25 I (25195) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -30 I (25255) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -29 I (25285) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -30 I (25385) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -31 I (25425) BLE: BDA: d4:38:ed:41:67:8b, RSSI -60 I (25445) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -30 I (25595) BLE: BDA: c1:3f:fc:fb:03:e5, RSSI -56 I (26195) BLE: BDA: c1:3f:fc:fb:03:e5, RSSI -57 I (26805) BLE: BDA: c1:3f:fc:fb:03:e5, RSSI -58 I (27405) BLE: BDA: c1:3f:fc:fb:03:e5, RSSI -59 I (29605) BLE: BDA: d4:38:ed:41:67:8b, RSSI -55
The virtual beacon produces scans starting with 49:8a...
That looks pretty OK. But if you move the ESP32 very close to the iPhone you read things like this:
I (16635) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -8 I (16705) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -8 I (16725) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (16795) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -8 I (16825) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (16885) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (16985) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -32 I (17045) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -8 I (17145) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17175) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17235) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17335) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17435) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17495) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17535) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17625) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17685) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17755) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17785) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17845) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -8 I (17875) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7 I (17975) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -8 I (18035) BLE: BDA: 49:8a:fb:27:92:3a, RSSI -7
Here are several things to be queried: What is the -32 freakout (BTW I would treat this to be the only valid value). And what are these -7, -8 values? You cannot achieve such reception values, even if you glue both devices together.
So, yes, virtual beacons work OK, real beacons NOT (with degrees of NOT: RadBeacaon pretty much NOT AT ALL, Estimotes a bit better, but still far away from ordinary scanners)
Please continue the investigations on this issue. Right now the ESP32 on a Sparkfun cannot be used properly for iBeacon scanning. This might be caused by ESP, ESP-IDF or bad Sparkfun desgin. I don't know yet.
TIA.
heyinling
commented
7 years ago HI @neilyoung ,
for the first issue, adv not come as much as expected, could you please do test with the following scan parameters?
esp_ble_scan_params_t ble_scan_param = {
.scan_type = BLE_SCAN_TYPE_PASSIVE,
.own_addr_type = ESP_PUBLIC_ADDR,
.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL,
.scan_interval = 0x640,
.scan_window = 0x640
};the adv of ibeacon should come at least once 3 seconds.
neilyoung
commented
7 years ago Hi @heyinling
thanks for chiming in again. In fact, something like this was my last attempt last night (to no avail):
static esp_ble_scan_params_t ble_scan_params = {
.scan_type = BLE_SCAN_TYPE_PASSIVE,
.own_addr_type = ESP_PUBLIC_ADDR,
.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL,
.scan_interval = 10000,
.scan_window = 10000
};
Now I tried your's with one RadBeacon alive. This is the result:
I (305) BLE: Wait for scans...
I (5545) BLE: BDA 0C:F3:EE:04:1E:AE, RSSI -54, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6 MAJ 2, MIN 0, TXPWR -59
I (59695) BLE: BDA 0C:F3:EE:04:1E:AE, RSSI -64, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6 MAJ 2, MIN 0, TXPWR -59
E (60305) BT: btc_search_callback BLE observe complete. Num Resp 6
A second attempt with an additional hardware Estimote beacons gave this (an improvement I would say), but RadBeacon did still not appear:
I (305) BLE: Wait for scans...
I (515) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -36, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (1115) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -34, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (1705) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -35, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (2925) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -33, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (3505) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -28, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (4115) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -30, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (4705) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -28, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (5315) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -28, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (5905) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -51, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (6525) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -29, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (7135) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -32, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (7705) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -28, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (8975) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -38, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (9525) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (10115) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (10715) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -54, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (11315) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -28, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (11925) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -39, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (12545) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (13125) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (13735) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -27, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (14435) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -36, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (14945) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -38, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (15545) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (16185) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -28, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (16855) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -27, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (17365) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -37, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (18095) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -38, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (18575) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (19175) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -31, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (19775) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -54, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
I (20395) BLE: BDA C1:3F:FC:FB:03:E5, RSSI -37, UUID B9407F30-F5F8-466E-AFF9-25556B57FE6D MAJ 997, MIN 64763, TXPWR -60
Pretty good I would say. Not that precise I'm used to see it with an iPhone or an Android device, but at lest it is there once per second minimum.
PS: I have updated my code sample above to match this trace output.
heyinling
commented
7 years ago HI @neilyoung ,
according to BLE Spec, controller will do scan in 3 channels one by one. it will stay on each channel for scan interval (scan window <= scan interval, means how long controller do scan within scan interval).
you may try with different scan interval to get better performance. and for your scenario you always need to set scan window = scan interval.
neilyoung
commented
7 years ago Yes, I did some experiments already, with values varying from the lowest (0x10) up to 10000. The issue is: I does not reveal my RadBeacons. Anybody having such a beacon could run the test script above? Would be great.
neilyoung
commented
7 years ago @TianHao-Espressif Any other suggestions to try? I'm wondering why this issue doesn't have more attention at all. For me the ESP32 is NOT a good choice if it comes to iBeacon scanning. Not only that the detection rate is low for some real successful hardware beacons, some of them are pretty much undiscoverable. Then as an additional problem there are the nonsense RSSI readings.
TianHao-Yoursmake
commented
7 years ago @neilyoung , the RSSI problem have been resolved today. But it will be in ESP-IDF several days later. And another thing, could provide the purchase URL to buy your RadBeacon, because I have seen multi products of RadBeacon. Thanks.
neilyoung
commented
7 years ago @TianHao-Espressif Oh, good news. Would you mind to ping me if available? I purchased my RadBeacons here https://store.radiusnetworks.com/products/radbeacon-dot
neilyoung
commented
7 years ago The fix is still not available in the most recent version. Any reason for that?
TianHao-Yoursmake
commented
7 years ago @neilyoung , it will be in the master branch later on.
neilyoung
commented
7 years ago Hehe, the question is just: When... Have a nice weekend
neilyoung
commented
7 years ago @TianHao-Espressif Well, I see several changes.
I (1497) BLE: BDA 62:ED:BA:91:56:1E, RSSI -39, UUID 8492E75F-4FD6-469D-B132-043FE94921D8, MAJ 9044, MIN 20493, TXPWR -56
I (1567) BLE: BDA 62:ED:BA:91:56:1E, RSSI -96, UUID 8492E75F-4FD6-469D-B132-043FE94921D8, MAJ 9044, MIN 20493, TXPWR -56
I (1617) BLE: BDA 62:ED:BA:91:56:1E, RSSI -40, UUID 8492E75F-4FD6-469D-B132-043FE94921D8, MAJ 9044, MIN 20493, TXPWR -56
-39, -96, -40 in a row?
I (53837) BLE: BDA 62:ED:BA:91:56:1E, RSSI -102, UUID 8492E75F-4FD6-469D-B132-043FE94921D8, MAJ 9044, MIN 20493, TXPWR -56`All in all my verdict is - doesn't work for me.
Below a 60 s scan result, just one virtual beacon (iphone) placed on top of the ESP32,
Setup is:
static esp_ble_scan_params_t ble_scan_params = {
.scan_type = BLE_SCAN_TYPE_PASSIVE,
.own_addr_type = ESP_PUBLIC_ADDR,
.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL,
.scan_interval = 0x50,
.scan_window = 0x30};
jkhax0r
commented
7 years ago You should check out #475. Sounds like it's probably the same issue or very closely related. Cannot get any scan results when doing an active scan.
@TianHao-Espressif I'd be happy to send my "bad" device and "good" if you can look into this so you can hopefully repeat it.
neilyoung
commented
7 years ago @TianHao-Espressif Any news on the RadBeacons? And what is your comment regarding my verdict, that your fix didn't entirely remove the problem?
neilyoung
commented
7 years ago OK, I will let this chip aside. If I scan through the tons of mails I receive a day, talking about problems over problems with nearly every part of software and hardware, that is not really convincing. Looking for alternatives then.
Best
mstewart-triva
commented
7 years ago Trying to run this example blufi_beacon_tracker but getting error with function esp_bt_controller_init().
it is saying too few arguments. Anybody know how to fix this?
johnnorbury
commented
7 years ago Have you recently updated the idf?
If so, try with:
esp_err_t ret;
esp_bt_controller_config_t bt_cfg = BT_CONTROLLER_INIT_CONFIG_DEFAULT();
ret = esp_bt_controller_init(&bt_cfg);
if (ret) {
ESP_LOGE(GATTS_TAG, "%s initialize controller failed\n", __func__);
return;
}it compiled, but terminal still saying BT: Controller not initialized.
I am new to the esp32, where do you find this information john?
johnnorbury
commented
7 years ago The code snippet was from the IDF blufi example (esp-idf/examples/bluetooth/blufi/).
The beacon example from @pcbreflux was created some time ago and due to the rapid addition of new features some functions can be outdated.
I guess you are running this code:
void app_main()
{
esp_err_t ret;
nvs_flash_init();
initialise_wifi();
esp_bt_controller_init();
ret = esp_bluedroid_init();
if (ret) {
BLUFI_ERROR("%s init bluedroid failed\n", __func__);
return;
}
ret = esp_bluedroid_enable();
if (ret) {
BLUFI_ERROR("%s enable bluedroid failed\n", __func__);
return;
}
...
}But with the blufi example code from the IDF we have:
void app_main()
{
esp_err_t ret;
ESP_ERROR_CHECK( nvs_flash_init() );
initialise_wifi();
esp_bt_controller_config_t bt_cfg = BT_CONTROLLER_INIT_CONFIG_DEFAULT();
ret = esp_bt_controller_init(&bt_cfg);
if (ret) {
BLUFI_ERROR("%s initialize bt controller failed\n", __func__);
}
ret = esp_bt_controller_enable(ESP_BT_MODE_BTDM);
if (ret) {
BLUFI_ERROR("%s enable bt controller failed\n", __func__);
return;
}
...
}It also looks like
esp_err_t esp_bt_controller_enable(esp_bt_mode_t mode)
now has a parameter, you can see in
/esp-idf/components/bt/include/bt.h
The different possible inputs:
/**
* @brief Bluetooth mode for controller enable/disable
*/
typedef enum {
ESP_BT_MODE_IDLE = 0x00, /*!< Bluetooth is not running */
ESP_BT_MODE_BLE = 0x01, /*!< Run BLE mode */
ESP_BT_MODE_CLASSIC_BT = 0x02, /*!< Run Classic BT mode */
ESP_BT_MODE_BTDM = 0x03, /*!< Run dual mode */
} esp_bt_mode_t;However, your terminal is specifying the controller isn't "Initialised" in which case a debug message should have popped up from:
ESP_LOGE(GATTS_TABLE_TAG, "%s enable controller failed\n", __func__);
TianHao-Yoursmake
commented
7 years ago @neilyoung , I'm sorry for delay. We have tested the RadBeacon devices. It might have something problem on Radbeacon device RF freq deviation. We will debug this.
negativekelvin
commented
7 years ago This EM9301 chipset maybe not widely used so interesting to see what the issue is.
mstewart-triva
commented
7 years ago @neilyoung could you post your project for review or on github
jkhax0r
commented
7 years ago @TianHao-Espressif I'm glad to hear you guys are working on this! I think this has been at the core of a lot of my problems too and I long suspected it to be RF frequency deviation but never 100% positive! I even bought a scanner (Ubertooth one) to try to look at frequencies and data sent on individual channels, but it wasn't worth the hassle. I also bought new ESP-WROOM-32 modules with the FCC logo thinking maybe the ones I populated on my PCBs (w/o the same shield) might be older and mistuned crystals or something.
neilyoung
commented
7 years ago @mstewart-triva Well, the entire "project" is here on thread. Look for my posting from March 13th It is just one file. Take whatever esp-idf sample and replace main.cpp by that.
neilyoung
commented
7 years ago @mstewart-triva OK, updated version here
EDIT: GIthub project provided. See next post
neilyoung
commented
7 years ago @mstewart-triva OK, please give it a try https://github.com/neilyoung/ESP32_blufi_beacon_tracker/tree/master
mstewart-triva
commented
7 years ago I tried it, @neilyoung , but am getting no beacon readings in my terminal. It is just showing some intitial set up.
mstewart-triva
commented
7 years ago For some reason I don't think my bluetooth is being enabled, you know why this could be?
mstewart-triva
commented
7 years ago All I'm getting in output is as follows:
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0x00 clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0008,len:8 load:0x3fff0010,len:3412 load:0x40078000,len:10388 load:0x40080000,len:252 entry 0x40080034 I (761) cpu_start: Pro cpu up. I (762) cpu_start: Single core mode I (763) heap_alloc_caps: Initializing. RAM available for dynamic allocation: I (775) heap_alloc_caps: At 3FFAFF10 len 000000F0 (0 KiB): DRAM I (795) heap_alloc_caps: At 3FFC6E20 len 000191E0 (100 KiB): DRAM I (816) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM I (837) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (859) heap_alloc_caps: At 40092B50 len 0000D4B0 (53 KiB): IRAM I (879) cpu_start: Pro cpu start user code I (938) cpu_start: Starting scheduler on PRO CPU. I (994) wifi: wifi firmware version: ba7c292 I (994) wifi: config NVS flash: enabled I (994) wifi: config nano formating: disabled I (1010) wifi: Init dynamic tx buffer num: 32 I (1010) wifi: Init dynamic rx buffer num: 64 I (1010) wifi: wifi driver task: 3ffcd494, prio:23, stack:3584 I (1013) wifi: Init static rx buffer num: 10 I (1016) wifi: Init dynamic rx buffer num: 64 I (1021) wifi: Init rx ampdu len mblock:7 I (1024) wifi: Init lldesc rx ampdu entry mblock:4 I (1029) wifi: wifi power manager task: 0x3ffd284c prio: 21 stack: 2560 I (1036) wifi: wifi timer task: 3ffd38dc, prio:22, stack:3584 I (1056) phy: phy_version: 350, Mar 22 2017, 15:02:06, 1, 0 I (1057) wifi: mode : sta (24:0a:c4:00:9f:0a)
t4r4n15
commented
7 years ago Same issue here, with code from examples on WROOM-32 we have many lost packets. We were changing esp_ble_scan_params_t (scan_interval and scan_window) and things are really messed up (most of the time it works for about 15 seconds and crashes or stops for 2 minutes). Best stability is for default params. We have mean interval at about 800ms from iBeacon (kontkat.io) set at 350ms.
TianHao-Yoursmake
commented
6 years ago @neilyoung ， the issues about Radbeacon have been resolved on newest master branch. So did you have re-test it?
neilyoung
commented
6 years ago @TianHao-Espressif Well, I'm not too crazy about the results. Having one Estimote and five Radbeacons here, and the single Estimote is by far more often scanned, than the others.
Given this is still a valid scanner
https://github.com/neilyoung/ESP32_blufi_beacon_tracker
I (31) boot: ESP-IDF v2.0-rc1-930-g058eb26 2nd stage bootloader I (31) boot: compile time 16:09:20
negativekelvin
commented
6 years ago @TianHao-Espressif what was the issue with EM9301 chipset?
TianHao-Yoursmake
commented
6 years ago @negativekelvin , The phy library have updated.
FayeY
commented
6 years ago Hi @neilyoung , is this problem solved? Can we close it?
neilyoung
commented
6 years ago @FayeY Clearly NO.
Not even that the RadBeacons (I have five dots here among one Estimote) are not scanned as much as often as the Estimote, I think I got two WDT crashes during 1 minute of scans. The scans came in very scattered and got stuck, while the WDT expired.
Setup is
static esp_ble_scan_params_t ble_scan_params = {
.scan_type = BLE_SCAN_TYPE_PASSIVE,
.own_addr_type = BLE_ADDR_TYPE_PUBLIC,
.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL,
.scan_interval = 0x10,
.scan_window = 0x10};
but I tried other values as well. Trace attached.
neilyoung
commented
6 years ago @FayeY @TianHao-Espressif Hi guys, not sure, what's going on, but after a long time I tried it again. My code is still here (unchanged) https://github.com/neilyoung/ESP32_blufi_beacon_tracker, but the results are meanwhile sub zero.
Now not even Estimote is received correctly, not to talk about the RadBeacon problem.
I (3125) cpu_start: Pro cpu start user code
I (3277) cpu_start: Starting scheduler on PRO CPU.
I (486) cpu_start: Starting scheduler on APP CPU.
I (506) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (686) phy: phy_version: 355.1, 59464c5, Jun 14 2017, 20:25:06, 1, 0
I (726) BLE: Wait for scans...
I (6776) BLE: BDA 0C:F3:EE:04:21:38, RSSI -75, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 0, MIN 1, TXPWR -96
I (9436) BLE: BDA 0C:F3:EE:04:21:38, RSSI -76, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 0, MIN 1, TXPWR -96
I (15756) BLE: BDA 0C:F3:EE:04:21:38, RSSI -81, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 0, MIN 1, TXPWR -96
I (17466) BLE: BDA 0C:F3:EE:04:1E:8F, RSSI -73, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 1, MIN 0, TXPWR -70
I (22086) BLE: BDA 0C:F3:EE:04:21:38, RSSI -80, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 0, MIN 1, TXPWR -96
I (23176) BLE: BDA 0C:F3:EE:04:1E:8F, RSSI -70, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 1, MIN 0, TXPWR -70
I (25716) BLE: BDA 0C:F3:EE:04:21:38, RSSI -79, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 0, MIN 1, TXPWR -96
I (26706) BLE: BDA 0C:F3:EE:04:21:38, RSSI -81, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 0, MIN 1, TXPWR -96
I (54266) BLE: BDA 0C:F3:EE:04:1E:8F, RSSI -69, UUID 2F234454-CF6D-4A0F-ADF2-F4911BA9FFA6, MAJ 1, MIN 0, TXPWR -70
E (60726) BT: btc_search_callback BLE observe complete. Num Resp 23
Have you abandoned this meanwhile?
neilyoung
commented
6 years ago BTW: I'm having here now 30 iBeacons from AprilBrothers, a Chinese company. And you know, what? My app scans like hell.
All beacons advertise with full power and 500 ms interval.
Do you have an explanation, why you're having problems with non-Chinese beacons :) ?
TianHao-Yoursmake
commented
6 years ago @neilyoung , you means ibeacon of AprilBrothers can be scanned by esp32, but RadBeacon and Estimote can not be scanned by esp32, right?
We're doing more test and debug on these similar things.
igrr
commented
6 years ago @neilyoung unrelated to the main topic, regarding
It should be made possible to fold/unfold those long quotes...
Here's how you can do this in Github comments:
<details>
<summary>BLE scan log</summary>
```
(log goes here)
```
</details>(make sure you have that empty line between <summary> and the backticks!)
The result will look like this:
negativekelvin
commented
6 years ago @neilyoung you would be a hero if you could collapse all these logs like that, ...i've been scrolling for days
So what chipset your April brother beacons use, cc2541?
Can we get a list of chipsets that work well with esp32 and those that don't?
neilyoung
commented
6 years ago @negativekelvin I feel with you, sorry :) @igrr Thanks for the hint, I will try to edit my posts later again.
It is a DA14580 https://www.dialog-semiconductor.com/products/connectivity/bluetooth-low-energy/smartbond-da14580
All in all a smart 3 chip solution with a CR2450 battery.
neilyoung
commented
6 years ago @negativekelvin OK, have updated the worst posts... Sorry again.
TianHao-Yoursmake
commented
6 years ago @neilyoung , we have fixed this RX packet losing bug, please wait the release/v2.1 version. Thanks.
Hi,
I'm using a slightly modified version of this iBeacon tracker https://github.com/pcbreflux/espressif/tree/master/esp32/app/ESP32_blufi_beacon_tracker
The modification just covers one line in the initialization code, matching the latest changes in ESP-IDF.
Whereas the scanner does see nearly all BLE devices around, it has two remarkable problems with iBeacons:
1) It provides just a scattered scan of iBeacons, even though the beacons are there and advertising once ever 600 ms. The scanner just comes with one or two scans per minute
2) The RSSI readings are kind of nonsense. I'm having two consecutive readings of one and the same stationary iBeacon. One reads RSSI -27, the other RSSI -84. This is simply impossible.
The board is a Sparkfun ESPThing.
Anybody having made a better experience?