Unexpected packet in beacon scanner.

RE: Unexpected packet in beacon scanner.

cl — Wed, 06 Jan 2016 04:21:34 GMT

You're right. After inserting memset() code, strange packet is no longer detected in scanner! So it seems like it's just problem of scanner not clearing default value of evt struct. Thanks!

RE: Unexpected packet in beacon scanner.

cl — Tue, 05 Jan 2016 11:38:29 GMT

For the first comment, other devices are not advertising with custom UUID. Only one beacon (that I set) is advertising with custom UUID. But, scanner get packets as if other devices is advertising not that beacon. For the second comment, I'll try tomorrow and report. Thanks!

RE: Unexpected packet in beacon scanner.

Anders Strand — Tue, 05 Jan 2016 10:29:04 GMT

On line 238 of scanner_beacon.c, try changing

ble_scan_beacon_evt_t evt;

ble_scan_beacon_evt_t evt;
memset(&evt, 0, sizeof(evt))

RE: Unexpected packet in beacon scanner.

Anders Strand — Tue, 05 Jan 2016 10:20:06 GMT

So other devices are advertising beacon packets with the custom UUID you created? It might seem that the uuid field is not deleted between each scan result.

RE: Unexpected packet in beacon scanner.

cl — Tue, 05 Jan 2016 04:56:09 GMT

I checked out one of the address in the strange packet. and setup nrf sniffer to see if the device with that address is really advertising with specified UUID. But, in the sniffer, there's no packet with specified UUID. In summary, it seems like those strange packet is not actually come from other ble device. but these packets comes in scanner with address of ble devices. I'm now confusing why these packet is scanned in scanner. For your reference, this is uuid_cmp() function.

static uint8_t uuid_cmp(const unsigned char *strA, const unsigned char *strB, unsigned int size) {
int i = 0;

int ret = 0;


for(i = 0; i<size;i++) {
	if(strA[i] == strB[i])
		ret++;
}
return (ret == size);
}

RE: Unexpected packet in beacon scanner.

cl — Tue, 05 Jan 2016 02:19:07 GMT

Thank you for your kind answer. Scanning without advertising is working nicely. But, for the problem of unexpected packet still not understanding. First of all, uuid_cmp() function is working correctly. (I checked the uuid value using debugger and it is not NULL.) But there's something strange I found out. These unexpected packets comes in scanner only when there's a beacon who is advertising for custom UUID. If I turn off a beacon which is advertising with specified UUID, unexpected packet doesn't apear in a scanner. So, my thinking is something like collision is happening when a beacon advertise. Any idea for this situation? Thanks. +) One more thing, all these unexpected packet has the same major, minor value but just have different addr(which is not fake, but an address of real ble device).

RE: Unexpected packet in beacon scanner.

Anders Strand — Mon, 04 Jan 2016 13:01:58 GMT

Hello.

When scanning, you will get advertising packets from all devices around you. It is up to you to filter the advertisement packets (Like you are doing in beacon_evt_handler). It does not make any sense that the other advertisement packets have the same uuid. Are you sure of this? Maybe there is a bug in uuid_cmp? For example if the uuid is NULL?

Is there some sort of broadcasting feature in ble or beacon?

Yes. Broadcasting and advertising is basically the same thing. Non-connectible advertising is often called broadcasting. This is how a BLE beacon broadcasts its packets. A BLE beacon is simply a device advertising a specific packet with the "non-connectible" flag set. You cannot filter it out, as it is what you are scanning for.

Is it possible to setup beacon scanner without advertising?

Yes. In main(), the line

err_code = ble_advertising_start(BLE_ADV_MODE_FAST);

starts the advertising.