<?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>8-bit Microcontrollers中的主题 Re: MC1321x BeeStack - Corrupt Packets</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC1321x-BeeStack-Corrupt-Packets/m-p/146165#M7296</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BR /&gt;I get these type of messages when my system is not connected (I should have checked this first)...&amp;nbsp; it appears to be a Daintree SNA issue (or just the way it interprets the RF environment).&lt;BR /&gt;We are having problems with disconnects on certain channels (25 and 26) and apparently I was barking up the wrong tree here.&amp;nbsp; I will repost (a new thread) once I have more info on the disconnect problem (but I now do not think it is related to these random packets).&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;- Ware&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2009 23:15:50 GMT</pubDate>
    <dc:creator>Ware</dc:creator>
    <dc:date>2009-01-26T23:15:50Z</dc:date>
    <item>
      <title>MC1321x BeeStack - Corrupt Packets</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC1321x-BeeStack-Corrupt-Packets/m-p/146164#M7295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;BR /&gt;&lt;IMG alt="" src="https://community.nxp.com/" /&gt;&lt;SPAN&gt;I have recently noticed that while running our ZigBee system described below I occasionally (a few times per hour) get corrupt packets (sometimes multiple consecutive packets as in the screenshot example attached).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Network Contains:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1 ZigBee Coord&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; BeeStack 2.00&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; Unique MAC Address&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; No Freq Agility&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; Joining Disabled after ZED associated&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1 ZigBee End Device&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; BeeStack 2.00&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; Unique MAC Address&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; MatchDesc used to associate to ZC&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; Low Power mode (wake-up period varied from every 64ms to every 1second)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; ReJoin attempted after loss of sync indication&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I could not find anything regarding these type of "corrupt" packets on the forums or BeeStack documentation.&amp;nbsp; Has anyone else seen these corrupt packets?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;NOTE: The Src / Dst network address varies (but they're always nonsensical).&amp;nbsp; And the "MAC Payload" is usually just a single byte (typically 0x00).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas are appreciated,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;- Ware&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Message Edited by Ware on &lt;/SPAN&gt;&lt;SPAN class="date_text"&gt;2009-01-23&lt;/SPAN&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;SPAN class="time_text"&gt;06:11 PM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Jan 2009 07:07:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC1321x-BeeStack-Corrupt-Packets/m-p/146164#M7295</guid>
      <dc:creator>Ware</dc:creator>
      <dc:date>2009-01-24T07:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: MC1321x BeeStack - Corrupt Packets</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC1321x-BeeStack-Corrupt-Packets/m-p/146165#M7296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BR /&gt;I get these type of messages when my system is not connected (I should have checked this first)...&amp;nbsp; it appears to be a Daintree SNA issue (or just the way it interprets the RF environment).&lt;BR /&gt;We are having problems with disconnects on certain channels (25 and 26) and apparently I was barking up the wrong tree here.&amp;nbsp; I will repost (a new thread) once I have more info on the disconnect problem (but I now do not think it is related to these random packets).&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;- Ware&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2009 23:15:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC1321x-BeeStack-Corrupt-Packets/m-p/146165#M7296</guid>
      <dc:creator>Ware</dc:creator>
      <dc:date>2009-01-26T23:15:50Z</dc:date>
    </item>
  </channel>
</rss>

