Issue: Identifying beacons with 128-bit UUID for nRF9160 DK (PCA 10090)

RE: Issue: Identifying beacons with 128-bit UUID for nRF9160 DK (PCA 10090)

Simon — Thu, 12 Dec 2019 09:22:49 GMT

I wrote the wrong name, it should be the ble_lte_gateway sample. I've updated it now.

Best regards,

Simon

RE: Issue: Identifying beacons with 128-bit UUID for nRF9160 DK (PCA 10090)

Apfelsine — Wed, 11 Dec 2019 19:15:12 GMT

Where can I find the sample scan_beacons, please?

RE: Issue: Identifying beacons with 128-bit UUID for nRF9160 DK (PCA 10090)

Simon — Fri, 06 Dec 2019 13:01:57 GMT

Could you upload your application? Then I can try to reproduce the error myself. I can make the ticket private if you would like so.

Best regards,

Simon

RE: Issue: Identifying beacons with 128-bit UUID for nRF9160 DK (PCA 10090)

Dheeraj — Wed, 04 Dec 2019 10:09:24 GMT

Hi Simon,

Thank you for your reply.

Actually I have migrated the lte_ble_gateway code changes along with the above snippet to asset_tacker application, as per the requirement demand.

But unfortunately, I am getting the following errors, while testing the above code to observed the UUID values.

/*************************************** Logs **************************************/

Initializing Bluetooth..

<err> bt_driver: Unknown H:4 type 0x01

[00:00:00.365,905] <wrn> bt_hci_core: opcode 0x0000 pool id 5 pool 0x20030ea4 != &hci_cmd_pool 0x20030e80

[00:00:18.555,236] <wrn> bt_driver: Discarding event 0x3e
[00:00:18.561,920] <wrn> bt_driver: Discarding event 0x3e

[00:00:00.368,011] <err> bt_driver: Not enough space in buffer
[00:00:00.374,511] <err> bt_driver: Unknown H:4 type 0x00
[00:00:00.380,584] <err> bt_driver: Unknown H:4 type 0x00
ASSERTION FAIL [err == 0] @ C:/ncs/zephyr/subsys/bluetooth/host/hci_core.c:340
k_sem_take failed with err -11

[00:00:00.581,085] <wrn> bt_driver: Discarding event 0x3e
[00:00:00.587,188] <err> bt_driver: Unknown H:4 type 0x01
[00:00:00.593,322] <err> bt_driver: Not enough space in buffer
[00:00:00.599,822] <err> bt_driver: Unknown H:4 type 0xee
[00:00:00.605,926] <err> bt_driver: Unknown H:4 type 0x2a
[00:00:00.611,999] <err> bt_driver: Unknown H:4 type 0x72
[00:00:00.618,072] <err> bt_driver: Unknown H:4 type 0x22
[00:00:00.624,176] <err> bt_driver: Unknown H:4 type 0x69
[00:00:00.630,249] <err> bt_driver: Unknown H:4 type 0x00
[00:00:00.636,352] <err> bt_driver: Unknown H:4 type 0xd4

/************************** End of Logs ***********************************/

NOTE: I have ported the all required code changes needed by the lte_ble_gateway in the asset_tracker application.

And observed the NO warnings and NO errors, while compiling the code.

Please help me with the above issue, whether I am missing anything, apart from code changes.

HW Tested: nRF9160 DK (PCA10090)

SW Used: V1.1.0 branch

Thank you.

RE: Issue: Identifying beacons with 128-bit UUID for nRF9160 DK (PCA 10090)

Simon — Wed, 04 Dec 2019 00:33:24 GMT

I modified the ble_lte_gateway example in NCS v1.1.0 to scan for beacons, parse the advertising data and store the 128 bit UUID, the major and the minor value. Execute these steps to get the example up and running

Follow the steps explained here to build and run the LTE Sensor Gateway example
Swap the file <..>\ncs\nrf\samples\nrf9160\lte_ble_gateway\src\ble.c with the file provided below, then rebuild and flash your example.

devzone.nordicsemi.com/.../2677.ble.c

Best regards,

Simon