• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 62 subscribers
  • Views 4154 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 102439
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

Bond Manager or Device Manager

Adrian Eggenberger

Hi I'm trying to implement bonding in a device based on the S120. As counter part i've used a S110 device or an iOS device (realized with LightBlue App).

While searching the Nordic developer zone i found a lot of documentation for the "Bond Manager". But in the SDK 5.2 there also exists a Device Manger which as far as i see also handles bonding. Documentation for the Device Manager can't be found.

Questions:

  • What is the difference between the Bond Manger and the Device Manager?
  • Which one should be used on central and peripherial devices?

As the device manager looked newer and more advanced to me i decided to go with it. As a result the bonding between a S110 and a S120 device works. In the next step i tried to do bonding with the iOS device. There the bonding fails as the iOS Device advertises with private address. Should this work already or is the implementaion for that missing?

Questions:

  • Is the device manager for central devices ready for bonding with iOS devices?
  • When will a new version of the SDK be released (with hopfully improved device manager)?

Regards Adrian

  • 0

    Hi Adrian,

    @What is the difference between the Bond Manger and the Device Manager

    The Device Manager is the next version of the Bond Manager. The Bond Manager will be deprecated in a future version of the SDK and the Device Manager will replace it.

    The Device Manager included in the latest version of the SDK is of experimental quality (not thoroughly tested and will be missing functionality).

    @- Which one should be used on central and peripherial devices?

    So far the Device Manager has been tested only for central (s120) applications. You will find that the s120 applications included in the SDK use the Device Manager only. But the s110 applications still use the Bond Manager. So if you need to look at examples to see how its done, I suggest you develop your peripheral application using the Bond Manager.

    But if you want to be ready to do a quick port of your applications whenever a new SDK version is available, then I recommend that you develop both central and peripheral applications using the Device Manager. But you should be prepared for any form of API changes in the Device Manager module in the upcoming SDK release.

    @Is the device manager for central devices ready for bonding with iOS devices?

    This is an area that has not been tested (as mentioned above). So it is not ready yet.

    @When will a new version of the SDK be released (with hopfully improved device manager)?

    I do not have the answer for this right now. I will have to get back to you on this.

    EDIT: The target is to release a new SDK with improved Device Manager by the end of this month.

    Cheers, Balaji

  • 0 in reply to Balaji Srinivasan

    Wow! What an extended answer! Your posting clears things up a lot!

    I our case it was right to go with device manager on both sides (peripherial and central). So we are prepared for the upcoming SDK's.

    We are looking forward to the release of the new SDK and the improved device manager. Thanks!

Related

core_v2_widget.Hide()