How do I use the nRF5 Connect SDK for dynamic multi-protocol development

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Lipeng Yang — Sat, 08 Jun 2024 02:41:38 GMT

Hi Marte,

I have solved the problem. I deleted the device from my phone and reconnected.

Thank you for your reply.

Best regards,

Lipeng

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Marte Myrvold — Tue, 21 May 2024 08:57:39 GMT

Hi,

Do you get the same issue with Bluetooth-only samples, such as the Bluetooth: Peripheral LBS sample?

What phone are you using to test? Have you tested with different phones?

Best regards,
Marte

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Lipeng Yang — Sat, 18 May 2024 03:23:56 GMT

Hi Marte,

While I was learning about Zigbee Light Switch, I encountered a new problem. I followed the Nordic documentation, but the nRF Toolbox's UART feature didn't connect to my board. In other words, it is connected, but it automatically disconnects immediately. The information in the terminal is as follows:

In addition, I am able to connect my development board using nRF Connect.

This is because of some kind of vulnerability in the nRF Toolbox. Or I need to make some changes to the case or APP. Please help me solve this problem, thank you.

Best regards,

Lipeng

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Lipeng Yang — Fri, 17 May 2024 11:18:48 GMT

Hi Marte,

Thank you for your help. This is very useful for me to learn dynamic multi-protocol.

Best regards,

Lipeng

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Marte Myrvold — Thu, 16 May 2024 14:33:30 GMT

Hi Lipeng,

One main reason is that the nRF Connect SDK integrates the Zephyr RTOS, compared to the bare-metal nRF5 SDK.

The SoftDevice controller in the nRF Connect SDK still provides the multi-protocol support used in the SoftDevices in the nRF5 SDK, but the overlaying API is different. The MPSL also provides multiple additional features other than multiprotocol support and timeslots, such as TX power control, clock control, as well as IEEE 802.15.4 and Bluetooth external radio coexistence.

Best regards,
Marte

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Lipeng Yang — Thu, 16 May 2024 08:47:07 GMT

Hi Marte,

[quote userid="92402" url="~/f/nordic-q-a/111120/how-do-i-use-the-nrf5-connect-sdk-for-dynamic-multi-protocol-development/483445"]Then I recommend reading the links in my previous post, as they explain how MPSL handles this. The main thing is that MPSL allows for the radio drivers to negotiate for transmission timeslots.[/quote]

Okay, I've got some ideas. And I have one more question. Why didn't Nordic continue to use the previous radio scheduler and instead use the current MPSL? Both are time slicing, so what are the advantages of the latter?

Best regards,

Lipeng

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Marte Myrvold — Wed, 15 May 2024 09:31:21 GMT

Hi Lipeng,

[quote user="Lipeng Yang"]My current job is to tease out the dynamic multi-protocol workflow, from the RF module to the application layer.[/quote]

Then I recommend reading the links in my previous post, as they explain how MPSL handles this. The main thing is that MPSL allows for the radio drivers to negotiate for transmission timeslots.

Best regards,
Marte

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Lipeng Yang — Wed, 15 May 2024 07:52:27 GMT

Hi,

[quote userid="92402" url="~/f/nordic-q-a/111120/how-do-i-use-the-nrf5-connect-sdk-for-dynamic-multi-protocol-development/483216"]What specifically is it you want to learn?[/quote]

My current plan is to apply dynamic multi-protocol technology to wireless sensors, using local area networks to send data. I don't know the details yet. My current job is to tease out the dynamic multi-protocol workflow, from the RF module to the application layer.

Looking forward to your reply.

Best regards,

Lipeng

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Marte Myrvold — Tue, 14 May 2024 10:51:07 GMT

Hi Lipeng,

[quote user="Lipeng Yang"]Finally, could you give me some advice on how to learn dynamic multi-protocol, because I feel like my learning progress is too slow.[/quote]

What specifically is it you want to learn?

The samples are the best starting points for learning how to use it. If you want to learn more in-depth about how the timeslots work, then I recommend reading about it in our documentation here: Multiprotocol Service Layer - Timeslot. You can also check out the Multiprotocol Service Layer API.

Best regards,
Marte

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Lipeng Yang — Tue, 14 May 2024 07:45:09 GMT

Hi,

First of all, thanks for your reply. I had been looking for examples in the nRF5 SDK for Thread and Zigbee, but none of them were a good fit. I've spent months looking for dynamic multiprotocol cases in order to learn dynamic multiprotocol. Your reply saved me a lot of time.

Secondly, the cases mentioned in your reply are very good, which is exactly what I need. I will carefully study the case you recommend, although it will take a little time.

Finally, could you give me some advice on how to learn dynamic multi-protocol, because I feel like my learning progress is too slow.

Thank you for your reply.

Best regards,

Lipeng

RE: How do I use the nRF5 Connect SDK for dynamic multi-protocol development

Marte Myrvold — Mon, 13 May 2024 12:11:26 GMT

Hi,

There is already support for dynamic multiprotocol in nRF Connect SDK. The Zigbee Light Switch and Thread CoAP Client samples support multiprotocol out of the box, and all you need to do is enable the multiprotocol extension. How to do this is explained in each of the sample's documentation.

The Multi-Protocol Service Layer (MPSL) handles many of the tasks involved in multiprotocol applications in the nRF Connect SDK, so implementing a multiprotocol Zigbee + BLE or Thread + BLE application is even more straightforward in the nRF Connect SDK than it was in the nRF5 SDK.

If you want to know more, I recommend reading Multiprotocol support in our documentation and checking out the two samples I mentioned.

Best regards,
Marte