<?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: Working with channels</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841584#M5612</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok. I did test, and unfortunately this doesn't behave as you stated on Dec. 17th. When switching to a new channel, I'm not receiving any more messages from devices. I need to re-do the pairing !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Last but not least if what you say would work, how will the coordinator send to the rest of the devices which are on 'battery' and Receive-on-Idle off !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Jan 2019 10:40:05 GMT</pubDate>
    <dc:creator>zigbee1</dc:creator>
    <dc:date>2019-01-07T10:40:05Z</dc:date>
    <item>
      <title>Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841576#M5604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Understanding on how to work with Channels&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have some difficulties to understand the purpose of ZPS_tsAplZdpMgmtNwkUpdateReq() versusZPS_vNwkNibSetChannel()&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can understand the purpose of ZPS_tsAplZdpMgmtNwkUpdateReq() when using 'scanning' mechanism, but what about chencg the radio channel use ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that something we can do on the fly ? what will happen to the object, will they switch to the new radio channel ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ZigBee pro stack / version 4170&lt;/P&gt;&lt;DIV style="left: 335.9px; top: 124.633px; font-size: 20px; font-family: sans-serif; transform: scaleX(1.05349);"&gt; &lt;/DIV&gt;&lt;DIV style="left: 335.9px; top: 124.633px; font-size: 20px; font-family: sans-serif; transform: scaleX(1.05349);"&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2018 11:11:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841576#M5604</guid>
      <dc:creator>zigbee1</dc:creator>
      <dc:date>2018-11-15T11:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841577#M5605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was not able to locate this API (ZPS_vNwkNibSetChannel()) in the software stack, nonetheless, I believe that what you are looking for it's the&amp;nbsp;following API&amp;nbsp;ZPS_teStatus ZPS_eAplZdpMgmtNwkUpdateRequest , could you please check &lt;A href="https://www.nxp.com/docs/en/user-guide/JN-UG-3113.pdf"&gt;it &lt;/A&gt;(page 341) and verify it works for you?&amp;nbsp;Also, there are more details and information on how to use it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Estephania&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Nov 2018 18:32:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841577#M5605</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2018-11-16T18:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841578#M5606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your response. My question was more related to Channel Management, and I wonder if there is a way to move an existing running network from one channel to an other channel due to disturbances. Is that something which is done automaticaly and transparently by the ZigBee Pro stack ? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Dec 2018 13:08:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841578#M5606</guid>
      <dc:creator>zigbee1</dc:creator>
      <dc:date>2018-12-03T13:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841579#M5607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No, you need to call the API I mentioned,&amp;nbsp;that it's not done automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By any chance, have you tried using the&amp;nbsp;ZPS_eAplZdpMgmtNwkUpdateRequest API?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Estephania&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 9.5pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2018 22:53:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841579#M5607</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2018-12-14T22:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841580#M5608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So far, I play with APP_eZdpMgmtNetworkUpdateReq for scanning the network and looking for the interference level. i'll try to play with the 'Change' Flag. &lt;BR /&gt;My question in that case is will the objects connected will move to the new channel or will I have to re-pair all of them ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Dec 2018 10:13:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841580#M5608</guid>
      <dc:creator>zigbee1</dc:creator>
      <dc:date>2018-12-15T10:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841581#M5609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Still I have trouble to understand the purpose of :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ZPS_vNwkNibSetChannel versus ZPS_eAplZdpMgmtNwkUpdateRequest&amp;nbsp; (with the change/update flag) ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Dec 2018 08:22:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841581#M5609</guid>
      <dc:creator>zigbee1</dc:creator>
      <dc:date>2018-12-17T08:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841582#M5610</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Whe using ZPS_eAplZdpMgmtNwkUpdateRequest and setting channel with the 'update' flag ( 0xFE as scanDuration), this indeed change the Channel, no doubt on that.&lt;/P&gt;&lt;P&gt;However , All my existing Network Zigbee (for instance all end devices) are not talking to the controller anymore !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So while I could understand that we can using this at setup phase, then on run rate this seems not to be possible .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Am I'm missing something ? Should I do something more ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Dec 2018 12:23:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841582#M5610</guid>
      <dc:creator>zigbee1</dc:creator>
      <dc:date>2018-12-17T12:23:58Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841583#M5611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;When using the&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;ZPS_eAplZdpMgmtNwkUpdateRequest in the coordinator,&amp;nbsp; it will modify the coordinator and it will send a message to the rest of the devices to move to that channel.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Regards,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Estephania&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Dec 2018 18:57:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841583#M5611</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2018-12-17T18:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Working with channels</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841584#M5612</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok. I did test, and unfortunately this doesn't behave as you stated on Dec. 17th. When switching to a new channel, I'm not receiving any more messages from devices. I need to re-do the pairing !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Last but not least if what you say would work, how will the coordinator send to the rest of the devices which are on 'battery' and Receive-on-Idle off !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jan 2019 10:40:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Working-with-channels/m-p/841584#M5612</guid>
      <dc:creator>zigbee1</dc:creator>
      <dc:date>2019-01-07T10:40:05Z</dc:date>
    </item>
  </channel>
</rss>

