<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Wireless MCUのトピックRe: Can JN5189HN operate Zigbee and Thread simultaneously?</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575416#M14243</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I apologize, but&amp;nbsp; in this case the way to use both stack would be based on the time sharing as there is only one radio in the device, while we do not have examples with Thread and ZigBee working together , you can check the available examples for the K32W for some hybrid examples with BLE and Thread that you can use a a base for the development of the example you are looking for. Still, please take into consideration the memory footprint of both stacks plus the application size.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Thu, 29 Dec 2022 05:40:39 GMT</pubDate>
    <dc:creator>stephanie_m</dc:creator>
    <dc:date>2022-12-29T05:40:39Z</dc:date>
    <item>
      <title>Can JN5189HN operate Zigbee and Thread simultaneously?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575107#M14240</link>
      <description>&lt;P&gt;Hello, Community&lt;/P&gt;&lt;P&gt;I'd like to know if JN5189HN can operate Zigbee and Thread simultaneously like WiFi/BT combo module.&lt;/P&gt;&lt;P&gt;If it is available, where can I find the information about it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 07:33:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575107#M14240</guid>
      <dc:creator>andy_kim</dc:creator>
      <dc:date>2022-12-28T07:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: Can JN5189HN operate Zigbee and Thread simultaneously?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575416#M14243</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I apologize, but&amp;nbsp; in this case the way to use both stack would be based on the time sharing as there is only one radio in the device, while we do not have examples with Thread and ZigBee working together , you can check the available examples for the K32W for some hybrid examples with BLE and Thread that you can use a a base for the development of the example you are looking for. Still, please take into consideration the memory footprint of both stacks plus the application size.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 29 Dec 2022 05:40:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575416#M14243</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2022-12-29T05:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: Can JN5189HN operate Zigbee and Thread simultaneously?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575936#M14253</link>
      <description>&lt;P&gt;Dear Estephania,&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jan 2023 04:55:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Can-JN5189HN-operate-Zigbee-and-Thread-simultaneously/m-p/1575936#M14253</guid>
      <dc:creator>andy_kim</dc:creator>
      <dc:date>2023-01-02T04:55:15Z</dc:date>
    </item>
  </channel>
</rss>

