Scan beacon local name

RE: Scan beacon local name

Jørgen Holmefjord — Thu, 24 Aug 2017 07:52:53 GMT

You can find the S130 v2.0.1 softdevice API documentation in the infocenter.

RE: Scan beacon local name

Stanley — Thu, 24 Aug 2017 07:44:57 GMT

Hi Jorgen, Thank you for your help. The problem is solved. Now, I can get the beacon information. I have checked the parameter description in struct define. Is there any documentations to describe such kind of struct? We can check it with our application in the future.

RE: Scan beacon local name

Jørgen Holmefjord — Wed, 23 Aug 2017 13:31:37 GMT

Hi Stanley,

Most likely the local name is placed in the scan response packet by the beacon manufacturer. The ble_app_multilink_central example is by default not configured to use active scanning, and will therefore not receive the scan response packet.

You can change this by setting the parameter .active = 1 in ble_gap_scan_params_t m_scan_params struct.

Best regards,

Jørgen

RE: Scan beacon local name

Stanley — Wed, 23 Aug 2017 01:48:20 GMT

I have uploaded the image both of two devices. the left side is SDK v12.0.0 peripheral blinky, the right side is the beacon which we bought it from China. We would like to develop a beacon scanner for door security purpose. Due to the beacon product is more cheaper in China than Taiwan, so we want to focus on scanner with security application. The issuue on v12.0.0 blinky central SDK is that the local name cannot be found from blinky. Why we implement beacon scanner based on blinky application is that we saw someone who also want to make a beacon scanner on nRF51822 platform. We searched this topic in Nordic Developer Zone.

RE: Scan beacon local name

Jørgen Holmefjord — Tue, 22 Aug 2017 17:33:16 GMT

You can upload images by editing your original question. Is the issue with connection or with service discovery? UUID should not matter for matching the name and initiate the connection. Could you explain in more detail what you are trying to do? The SDK have changed quite a bit from SDK v9.0.0 until SDK v12.0.0.

RE: Scan beacon local name

Stanley — Tue, 22 Aug 2017 15:16:38 GMT

I check the SDK v9.0.0. There is a "MULTILINK_PERIPHERAL_BASE_UUID" at the both of central and peripheral. I don't know is it a cause to make this issue happened, but I cannot found this UUID at SDK v12.0.0.

RE: Scan beacon local name

Stanley — Tue, 22 Aug 2017 14:57:10 GMT

How can I upload the photo for you to check it?

RE: Scan beacon local name

Stanley — Tue, 22 Aug 2017 14:56:23 GMT

I checked the advertising data on LightBlue. I found the difference when I tried to connect to device. The UUID what I saw on LightBlue is different, but the local name is the same, showing up "MiniBeacon_xxxxx" (xxxxx means a s/n number). Is possible the different UUID cause this issue?

RE: Scan beacon local name

Jørgen Holmefjord — Tue, 22 Aug 2017 13:40:59 GMT

There should not be any limitations in the name other than the available bytes in the advertising packet. Have you tried doing some log printing, to check if m_target_periph_name is set to what you expect, and if any name is found in the advertising packets?

RE: Scan beacon local name

Stanley — Tue, 22 Aug 2017 08:54:15 GMT

Yes, I have checked the local name at lightblue. It can be identified at lightblue. Is there any limited about the length of periph_name? The original one is "Nordic_Blinky", and I changed it to "beacon_00001"

RE: Scan beacon local name

Jørgen Holmefjord — Mon, 21 Aug 2017 07:53:24 GMT

It should be sufficient to change m_target_periph_name. Have you checked the advertising data of the beacon, that the local name is present and identical to the one you used in m_target_periph_name?