This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Scan beacon local name

image description

Hello,

I am trying to scan a local name for beacon device on nrf51822 SDK12.0.0 ble_app_multilink_central. The original peripheral sample was working as well. But the beacon device cannot be found when I changed peripheral name in "ble_app_multilink_central". Is there only the parameter of "m_target_periph_name" need to be changed? or some where else.

  • 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.

  • 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.

  • 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.

  • 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

  • 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.

Related