<?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>topic Re: MC13213 - BeeStack - Extra &amp;quot;Command: Data Request&amp;quot; Packets from ZED in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC13213-BeeStack-Extra-quot-Command-Data-Request-quot-Packets/m-p/172781#M11763</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;There are two causes:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- By default the App Layer is written to call "ASL_Nlme_Sync_req(FALSE)" everytime the ZED wakes up. (main problem)&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- Sync Req is also automatically sent after every cluster is transmitted from a ZED (when low-power mode in use).&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Sending it once per second or when other clusters are sent both seem to work just fine.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The BeeStack documentation only mentions that ASL_Nlme_Sync_req() is called when the ZED needs to resync with it's parent.&amp;nbsp; I guess the BeeStack&amp;nbsp;automatically assumes a ZED waking up from deep sleep needs to resync?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- Ware&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Jan 2008 03:43:14 GMT</pubDate>
    <dc:creator>Ware</dc:creator>
    <dc:date>2008-01-25T03:43:14Z</dc:date>
    <item>
      <title>MC13213 - BeeStack - Extra "Command: Data Request" Packets from ZED</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC13213-BeeStack-Extra-quot-Command-Data-Request-quot-Packets/m-p/172780#M11762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;In the development of this simple (2 device) network, my ZigBee EndDevice (ZED) wakes up (from LOW POWER MODE) periodically to report values to my ZigBee Coord (ZC).&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The problem is that it is transmitting at least 5 "Command: Data Request" packets every time I send a report packet (see seq no 25,27,29,31 in "Packet_List.txt").&amp;nbsp; This is not a big problem when the wake-up period is long (512ms or 1024ms), but when I start reporting faster (like every&amp;nbsp;64ms) there is a lack of bandwidth issue due to ALL THESE extra "Command: Data Request" packets.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;My question is, what are these "Command: Data Request" packets for?&lt;/DIV&gt;&lt;DIV&gt;How can I get rid of them (or at least reduce them)?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thank you,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- Ware&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class="msg_source_code"&gt;&lt;DIV class="text_smallest"&gt;Example "Command: Data Request" packet decode:&lt;/DIV&gt;&lt;PRE&gt;Frame 145 (Length = 12 bytes)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sequence Number: 145&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Channel Sequence Number: 145&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Channel: 15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Time Stamp: Thu, 13 Dec 07, 08:04:29.097&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Frame Length: 12 bytes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Capture Length: 12 bytes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Link Quality Indication: 82&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Receive Power: -70 dBmIEEE 802.15.4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Frame Control: 0x8863&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... .... .... .011&amp;nbsp; = Frame Type: Command (0x0003)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... .... .... 0...&amp;nbsp; = Security Enabled: Disabled&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... .... ...0 ....&amp;nbsp; = Frame Pending: No more data&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... .... ..1. ....&amp;nbsp; = Acknowledgment Request: Acknowledgement required&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... .... .1.. ....&amp;nbsp; = Intra PAN: Within the PAN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... ..00 0... ....&amp;nbsp; = Reserved&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .... 10.. .... ....&amp;nbsp; = Destination Addressing Mode: Address field contains a 16-bit short address (0x0002)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ..00 .... .... ....&amp;nbsp; = Reserved&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.. .... .... ....&amp;nbsp; = Source Addressing Mode: Address field contains a 16-bit short address (0x0002)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Sequence Number: 66&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Destination PAN Identifier: 0x03c4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Destination Address: 0x0000&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Source Address: 0x034f&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MAC Payload&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Command Frame Identifier = Data Request: (0x04)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Frame Check Sequence: Correct&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2020 09:21:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC13213-BeeStack-Extra-quot-Command-Data-Request-quot-Packets/m-p/172780#M11762</guid>
      <dc:creator>Ware</dc:creator>
      <dc:date>2020-10-29T09:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: MC13213 - BeeStack - Extra "Command: Data Request" Packets from ZED</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC13213-BeeStack-Extra-quot-Command-Data-Request-quot-Packets/m-p/172781#M11763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;There are two causes:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- By default the App Layer is written to call "ASL_Nlme_Sync_req(FALSE)" everytime the ZED wakes up. (main problem)&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- Sync Req is also automatically sent after every cluster is transmitted from a ZED (when low-power mode in use).&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Sending it once per second or when other clusters are sent both seem to work just fine.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The BeeStack documentation only mentions that ASL_Nlme_Sync_req() is called when the ZED needs to resync with it's parent.&amp;nbsp; I guess the BeeStack&amp;nbsp;automatically assumes a ZED waking up from deep sleep needs to resync?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;- Ware&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jan 2008 03:43:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC13213-BeeStack-Extra-quot-Command-Data-Request-quot-Packets/m-p/172781#M11763</guid>
      <dc:creator>Ware</dc:creator>
      <dc:date>2008-01-25T03:43:14Z</dc:date>
    </item>
  </channel>
</rss>

