<?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: BeeStack V1.02 Siamese EndDevices Problem in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/BeeStack-V1-02-Siamese-EndDevices-Problem/m-p/140278#M5591</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I have had the same problem with BeeStack v1.02.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Recently I have downloaded the new BeeStack version v1.03, and it seems that this problem has been solved. This new version comes in the BeeKit v1.5.0 package.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=BEEKIT_WIRELESS_CONNECTIVITY_TOOLKIT&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab" rel="nofollow" target="_blank"&gt;http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=BEEKIT_WIRELESS_CONNECTIVITY_TOOLKIT&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab&lt;/A&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Oct 2007 21:01:14 GMT</pubDate>
    <dc:creator>elect</dc:creator>
    <dc:date>2007-10-22T21:01:14Z</dc:date>
    <item>
      <title>BeeStack V1.02 Siamese EndDevices Problem</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/BeeStack-V1-02-Siamese-EndDevices-Problem/m-p/140277#M5590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello&lt;/SPAN&gt;&lt;BR /&gt;&lt;P&gt;Has anybody seen this ZigBee effect? In our customer project, we have detected a state in which two end devices get the same short address from the coordinator. We do have a Snifferlog that shows the effect. In text form:&lt;/P&gt;&lt;P&gt;1. Network with 1 Coordinator and 2 Enddevices.&lt;BR /&gt;2. Enddevices are turned on and send "Beacon Requests"&lt;BR /&gt;3. Coordinator is turned on and forms a network&lt;BR /&gt;4. End Devices try to join nearly at the same time&lt;BR /&gt;5. As soon as the first End Device has joined (Addr. 0x796F) our application on the End Device starts sendig a packet (AF_DataRequest incl. Ack Request)&lt;BR /&gt;6. The paket is not acked by the coordinator! It seems to be busy with the join procedure of the second device.&lt;BR /&gt;7. In the mean time, the second device has joined the PAN successfully (0x7970).&lt;BR /&gt;8. The second device starts sending application packets. They are acked correctly by the coord.&lt;BR /&gt;9. The first device (0x796F) resends the unacked packet (Stack functionality). No ack is received either.&lt;BR /&gt;10. We assume a failure, leave the network and restart (new join).&lt;BR /&gt;11. It works but the coordinator gives us the address 0x7970.&lt;/P&gt;&lt;P&gt;We end up in a network in which two devices with different IEEE addresses have the same short address.&lt;BR /&gt;Its also possible that we simply missunderstood something concerning the usage of the stack. I would be very grateful for an answer what we could do to circumvent this behaviour.&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many thanks for any hint on this topic!&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.freescale.com%2Ffiles%2Fcommunity_files%2F8BITCOMM%2F6823_errorlog1.jpg" rel="nofollow" target="_blank"&gt;errorlog1.jpg&lt;/A&gt;&lt;/P&gt;&lt;DIV class="message-edit-history"&gt;&lt;SPAN class="edit-author"&gt;Message Edited by t.dowe on&lt;/SPAN&gt; &lt;SPAN class="local-date"&gt;2009-09-22&lt;/SPAN&gt; &lt;SPAN class="local-time"&gt;10:50 AM&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2007 16:22:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/BeeStack-V1-02-Siamese-EndDevices-Problem/m-p/140277#M5590</guid>
      <dc:creator>rolf</dc:creator>
      <dc:date>2007-07-17T16:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: BeeStack V1.02 Siamese EndDevices Problem</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/BeeStack-V1-02-Siamese-EndDevices-Problem/m-p/140278#M5591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I have had the same problem with BeeStack v1.02.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Recently I have downloaded the new BeeStack version v1.03, and it seems that this problem has been solved. This new version comes in the BeeKit v1.5.0 package.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=BEEKIT_WIRELESS_CONNECTIVITY_TOOLKIT&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab" rel="nofollow" target="_blank"&gt;http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=BEEKIT_WIRELESS_CONNECTIVITY_TOOLKIT&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab&lt;/A&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Oct 2007 21:01:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/BeeStack-V1-02-Siamese-EndDevices-Problem/m-p/140278#M5591</guid>
      <dc:creator>elect</dc:creator>
      <dc:date>2007-10-22T21:01:14Z</dc:date>
    </item>
  </channel>
</rss>

