• State Verified Answer
  • Replies 9 replies
  • Subscribers 74 subscribers
  • Views 2140 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 292553
Options

How to use Zigbee and Thread for multi-protocol.

OYAMA YUKIO

Hello,

At the following URL,

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_multiprotocol_support.html

In "The Thread and Zigbee protocols support running another protocol in parallel.", does "another protocol" refer to BLE?

So, as with the following question.

 Concuurent Multiprotocol Communication (BLE ,Zigbee,Thread) 


Is Zigbee+Thread still not possible today, and only Zigbee+BLE or Thread+BLE combinations can be run simultaneously?

Is it possible to combine two protocols into one firmware unless Zigbee and Thread are running at the same time?

It is a solution to switch between Zigbee and Thread by giving some kind of trigger. (At least, that trigger is not the incoming signal of the respective protocol.)


And can the protocol switching be done within the application? Or do I have to start from boot when making that switch?

Best Regards,

Yukio Oyama

  • 0 in reply to OYAMA YUKIO

    Hi and thank you for your patience.

    I've heard back with the MPLS, ZigBee and Radio driver teams after the vacation period and they say that ZigBee + Thread multiprotocol combo is not supported in NCS . This would require two instances of a radio driver to be present, which we do not have any solutions for at this point in time.

    Apologies for the long response time, and I hope this answers your question

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi Andreas-san,

    Thanks for remembering to follow up.

    Does the answer from the driver team mean that Zigbee and Thread cannot be changed dynamically?


    Before Zigbee and Thread networking issues, nRF52840 cannot switch between Zigbee and Thread within one application?

    Can it switch back to boot?

    Best Regards,

    Yukio Oyama

  • +1 in reply to OYAMA YUKIO

    Hi,

    Apologies for the delay in answer. I've been out of office this week.


    Yes, currently we do not support dynamically change between ZigBee and Thread in the same application.

    If the device has sufficient memory to store both stacks, you can switch between the protocols during boot and selecting if the device should be a Tread device or a ZigBee device at boot. You can do it like it is done for the Sleepy End device in the light switch, i.e if you hold a button while you boot it up, you choose ZigBee, while holding another button selects Thread. Then you can initialize the protocol and start a thread for the protocoll chosen.

    Note that the same issues with regards to leaving the network will be present if you intend to design a protocol switching algorithm that includes rebooting, i.e going from Z -> T -> Z will still cause issues with the device leaving and rejoining the network

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi Andreas-san,

    I understood that it is not possible to dynamically switch between Zigbee and Thread within one application. That fact affects our plans in no small way.

    However, there is a slight hope that we can switch by starting over from the boot.

    Now that I know what kind of system would allow me to switch between the two protocols, I close the case.

    I appreciate your support, thank you.

    Best Regards,

    Yukio Oyama

Related
Terms of service