nRF9160 DK lte_ble_gateway sample to get beacon UUID

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Simon — Thu, 23 Jan 2020 13:59:13 GMT

[quote user="Tejaswini"]But strangely, we are able to see that, the UUID of the above vendor (Gimbal) is changing every time.

As per our understanding, UUIDs of beacon should be same as its constant value for each beacon.

Please share us some info about, why UUID is changing.[/quote]

Please contact Gimbal about this, I think they are in a better position about it.

Best regards,

Simon

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Tejaswini — Tue, 21 Jan 2020 04:50:55 GMT

still not able to findout,why UUID changing everytime. Please share if you have any information about it.

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Simon — Mon, 20 Jan 2020 12:36:40 GMT

I am sorry for the delay, have you been able to figure this out?

Best regards,

Simon

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Tejaswini — Thu, 09 Jan 2020 13:02:21 GMT

Hi,

We are able to filter the BLE beacons values with UUID values without any issues.

For information: We are testing only with 2 Gimbal beacons.
And we are filtering by using vendor ID of Gimbal beacon (0x008C).

But strangely, we are able to see that, the UUID of the above vendor (Gimbal) is changing every time.

As per our understanding, UUIDs of beacon should be same as its constant value for each beacon.

Please share us some info about, why UUID is changing.

Thank you.

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Tejaswini — Wed, 04 Dec 2019 07:27:02 GMT

I got expected UUID, major and minor values.

Thanks Simon..

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Simon — Wed, 04 Dec 2019 00:36:57 GMT

Check out this ticket where I have provided the complete code to get this working.

Best regards,

Simon

RE: nRF9160 DK lte_ble_gateway sample to get beacon UUID

Simon — Sun, 01 Dec 2019 16:54:54 GMT

You need to somehow filter the advertising data. This is because beacon data usually is in the form of manufacturer-specific data (see this link), and you need to check all incoming advertising packets and check if it contains a manufacturer-specific AD type (check the bottom of this link). I am not too familiar with the Zephyr BLE libraries, and I am not sure what the proper way of going about this is, but here is one approach:

Make a copy of the lte_ble_gateway example, which you can modify
Inside <..>\ncs\nrf\samples\nrf9160\lte_ble_gateway\src\ble.c do the following
- Change scan_start() to the following:

static void scan_start(void){
        int err;
      
      	err = bt_le_scan_start(&scan_param, scan_cb);
	if (err) {
		printk("Starting scanning failed (err %d)\n", err);
		return;
	}
}

- Change scan_cb to the following:

static void scan_cb(const bt_addr_le_t *addr, s8_t rssi, u8_t adv_type,
		    struct net_buf_simple *buf)
{
        bt_data_parse(ad, adv_data_found, NULL);
}

Create adv_data_found:

static bool adv_data_found(struct bt_data *data, void *user_data)
{
	struct bt_scan_control *scan_control =
			(struct bt_scan_control *)user_data;

	if(data->type== BT_DATA_MANUFACTURER_DATA) {
	   //process the "data" variable
	   //Get minor and major values, uuid etc. from data
	   return false
	}


	return true;
}

Then delete everything from <..>\ncs\nrf\samples\nrf9160\lte_ble_gateway\src\ble.c that you don't need, e.g. functionality for connecting to a device.

I have not tested this myself, and my approach my contain errors/mistakes. Please ask if this approach doesn't work, or if you want me to elaborate more on anything.

Best regards,

Simon