<?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のトピックLeave indication after long sleep problem</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/Leave-indication-after-long-sleep-problem/m-p/946159#M7504</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial',sans-serif; color: black; background: white;"&gt;Hello, we are developing a custom application based on the JN-AN-1229 template. After long sleep (&amp;gt;5 mins) through the PWRM_eScheduleActivity function we wake up the device and make a poll request ZPS_eAplZdoPoll and we get the following events: &lt;BR /&gt; &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 15 &lt;BR /&gt; NWK: ZPS_EVENT_NEW_POLL_COMPLETE, status = 0 &lt;BR /&gt; NWK: MAC_ENUM_SUCCESS &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 15 &lt;BR /&gt; NWK: ZPS_EVENT_NEW_POLL_COMPLETE, status = 0 &lt;BR /&gt; NWK: MAC_ENUM_SUCCESS &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 11 &lt;BR /&gt; NWK: Poll request unhandled event - 11 &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 8 &lt;BR /&gt; NWK: Poll request unhandled event - 8 &lt;BR /&gt; &lt;BR /&gt; Therefore, after wake up the coordinator (i guess) asks the node to leave the network and then attemps to rejoin but it fails. &lt;BR /&gt; &lt;BR /&gt; Note: The network is 1 coordinator and 1 sleeping end node. &lt;BR /&gt; &lt;BR /&gt; Please help.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Oct 2019 20:54:35 GMT</pubDate>
    <dc:creator>hernanolave</dc:creator>
    <dc:date>2019-10-03T20:54:35Z</dc:date>
    <item>
      <title>Leave indication after long sleep problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Leave-indication-after-long-sleep-problem/m-p/946159#M7504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial',sans-serif; color: black; background: white;"&gt;Hello, we are developing a custom application based on the JN-AN-1229 template. After long sleep (&amp;gt;5 mins) through the PWRM_eScheduleActivity function we wake up the device and make a poll request ZPS_eAplZdoPoll and we get the following events: &lt;BR /&gt; &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 15 &lt;BR /&gt; NWK: ZPS_EVENT_NEW_POLL_COMPLETE, status = 0 &lt;BR /&gt; NWK: MAC_ENUM_SUCCESS &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 15 &lt;BR /&gt; NWK: ZPS_EVENT_NEW_POLL_COMPLETE, status = 0 &lt;BR /&gt; NWK: MAC_ENUM_SUCCESS &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 11 &lt;BR /&gt; NWK: Poll request unhandled event - 11 &lt;BR /&gt; NWK: New event on the stack APP_msgZpsEvents = 8 &lt;BR /&gt; NWK: Poll request unhandled event - 8 &lt;BR /&gt; &lt;BR /&gt; Therefore, after wake up the coordinator (i guess) asks the node to leave the network and then attemps to rejoin but it fails. &lt;BR /&gt; &lt;BR /&gt; Note: The network is 1 coordinator and 1 sleeping end node. &lt;BR /&gt; &lt;BR /&gt; Please help.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Oct 2019 20:54:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Leave-indication-after-long-sleep-problem/m-p/946159#M7504</guid>
      <dc:creator>hernanolave</dc:creator>
      <dc:date>2019-10-03T20:54:35Z</dc:date>
    </item>
    <item>
      <title>Re: Leave indication after long sleep problem</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Leave-indication-after-long-sleep-problem/m-p/946160#M7505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Heman,&lt;/P&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;The End Device Timeout Request command is sent by an end device informing its parent of its timeout requirements. This allows the parent the ability to delete the child entry from the neighbor table if the child has not communicated with the parent in the specified amount of time. Please look at the Zigbee Spec.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;In this case, the timeout request is 4 minutes. please see the image attached.&lt;/DIV&gt;&lt;DIV style="color: #000000; font-size: 13.3333px;"&gt;&lt;/DIV&gt;&lt;DIV style="color: #000000; font-size: 13.3333px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/33572i421ABE96FB4BA594/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;DIV style="color: #000000; font-size: 13.3333px;"&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;The parameter passed to the&amp;nbsp;ZPS_bAplAfSetEndDeviceTimeout decides the end device timeout , below are the values that this function can take:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;typedef enum {&lt;BR /&gt;ZED_TIMEOUT_10_SEC, // 0 -&amp;gt; 10 seconds&lt;BR /&gt;ZED_TIMEOUT_2_MIN, // 1 -&amp;gt; 2 minutes&lt;BR /&gt;ZED_TIMEOUT_4_MIN, // 2 -&amp;gt; 4 minutes&lt;BR /&gt;ZED_TIMEOUT_8_MIN, // 3 -&amp;gt; 8 minutes&lt;BR /&gt;ZED_TIMEOUT_16_MIN, // 4 -&amp;gt; 16 minutes&lt;BR /&gt;ZED_TIMEOUT_32_MIN, // 5 -&amp;gt; 32 minutes&lt;BR /&gt;ZED_TIMEOUT_64_MIN, // 6 -&amp;gt; 64 minutes&lt;BR /&gt;ZED_TIMEOUT_128_MIN, // 7 -&amp;gt; 128 minutes&lt;BR /&gt;ZED_TIMEOUT_256_MIN, // 8 -&amp;gt; 256 minutes (4 hrs 16 min)&lt;BR /&gt;ZED_TIMEOUT_512_MIN, // 9 -&amp;gt; 512 minutes (8 hrs 32 min)&lt;BR /&gt;ZED_TIMEOUT_1024_MIN, // 10 -&amp;gt; 1024 minutes (17 hrs 4 min)&lt;BR /&gt;ZED_TIMEOUT_2048_MIN, // 11 -&amp;gt; 2048 minutes (1 day 10 hrs 8 min)&lt;BR /&gt;ZED_TIMEOUT_4096_MIN, // 12 -&amp;gt; 4096 minutes (2 days 20 hrs 16 min)&lt;BR /&gt;ZED_TIMEOUT_8192_MIN, // 13 -&amp;gt; 8192 minutes (5 days 16 hrs 32 min)&lt;BR /&gt;ZED_TIMEOUT_16384_MIN, // 14 -&amp;gt; 16384 minutes (11 days 9 hrs 4 min)&lt;BR /&gt;ZED_TIMEOUT_INDEX_MAX,&lt;BR /&gt;ZED_TIMEOUT_UNDEFINED = 0xff&lt;BR /&gt;}teZedTimeout;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ZPS_bAplAfSetEndDeviceTimeout( &lt;SPAN style="color: #3d3d3d;"&gt;ZED_TIMEOUT_8_MIN&lt;/SPAN&gt;);&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Oct 2019 02:50:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Leave-indication-after-long-sleep-problem/m-p/946160#M7505</guid>
      <dc:creator>mario_castaneda</dc:creator>
      <dc:date>2019-10-08T02:50:09Z</dc:date>
    </item>
  </channel>
</rss>

