• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 73 subscribers
  • Views 5240 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 124483
Options
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

Stanley

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.

Parents
  • 0

    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?

Reply
  • 0

    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?

Children
No Data
Related
Terms of service