• State Not Answered
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 237 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 256664
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth functionality with nRF5 IoT SDK - is it limited?

henris42

Hi,

I made a demo app using advertising and scanning functionality in SDK 16. Now I'm trying to get it working in our company's full blown C++ framework, which is based on SDK for Thread and Zigbee 4.1.0. 

With practically the same code, advertising works but scanning does not, nrf_ble_scan_start() gives an error 6.  

Are the normal and Thread SDK:s different in this sense? Does Thread SDK give full Bluetooth functionality or not?

Chip is 52840, soft devices ones with aforementioned sdk:s.

Parents
  • 0

    Hi,

    Applications running on the nRF SoC can only use one radio protocol at a time, and therefore you have to implement a way to use multiple. This can be done by either using switched multiprotocol or dynamic multiprotocol. You can read more about multiprotocol support with BLE and the two different types here. Note that switched multiprotocol is only supported for Thread, and not for Zigbee.

    We do already have some multiprotocol examples, so I would recommend you take a look at how this is implemented there. If you want to use Thread and BLE, you can find the examples here, both switched multiprotocol and dynamic multiprotocol. For Zigbee you should look here.

    So to conclude, the SDKs are a bit different, but both have support for BLE. The difference is that you're using multiple radio protocols at the same time, which requires some extra implementation.

    Best regards,

    Marte

Reply
  • 0

    Hi,

    Applications running on the nRF SoC can only use one radio protocol at a time, and therefore you have to implement a way to use multiple. This can be done by either using switched multiprotocol or dynamic multiprotocol. You can read more about multiprotocol support with BLE and the two different types here. Note that switched multiprotocol is only supported for Thread, and not for Zigbee.

    We do already have some multiprotocol examples, so I would recommend you take a look at how this is implemented there. If you want to use Thread and BLE, you can find the examples here, both switched multiprotocol and dynamic multiprotocol. For Zigbee you should look here.

    So to conclude, the SDKs are a bit different, but both have support for BLE. The difference is that you're using multiple radio protocols at the same time, which requires some extra implementation.

    Best regards,

    Marte

Children
No Data
Related
Terms of service