https://devzone.nordicsemi.com/f/nordic-q-a/66127/bluetooth-functionality-with-nrf5-iot-sdk---is-it-limitedHi, I made a demo app using advertising and scanning functionality in SDK 16. Now I&#39;m trying to get it working in our company&#39;s full blown C++ framework, which is based on SDK for Thread and Zigbee 4.1.0. With practically the same code, advertisingen-USTelligent Community 13Mon, 21 Sep 2020 07:00:13 GMThttps://devzone.nordicsemi.com/thread/270457?ContentTypeID=1Mon, 21 Sep 2020 07:00:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ac0f9795-8279-45fa-8471-771588e9228dMarte Myrvold<p>Hi,</p> <p>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&nbsp;multiprotocol. You can read more about multiprotocol support with BLE and the two different types&nbsp;<a href="https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/ble_154_multiprotocol.html">here</a>. Note that switched multiprotocol is only supported for Thread, and not for Zigbee.</p> <p>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&nbsp;<a href="https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/thread_multi_examples.html">here</a>, both switched multiprotocol and dynamic multiprotocol. For Zigbee you should look&nbsp;<a href="https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/zigbee_multi_examples.html">here</a>.</p> <p>So to conclude, the&nbsp;SDKs are a bit different, but both have support for BLE. The difference is that you&#39;re using multiple radio protocols at the same time, which requires some extra implementation.</p> <p>Best regards,</p> <p>Marte</p><div style="clear:both;"></div>