<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF24L01+ Address byte order</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/612/nrf24l01-address-byte-order</link><description>Hello, I would like to know if the adress byte that is transmitted after the preamble is the MSB or LSB. 
 I&amp;#39;ve read the datasheet&amp;#39;s page 28 and it&amp;#39;s not very clear, it just says [b]&amp;quot;Figure 5.shows the
packet format with MSB to the left.&amp;quot;[/b] 
 I&amp;#39;ve</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 Oct 2013 22:52:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/612/nrf24l01-address-byte-order" /><item><title>RE: nRF24L01+ Address byte order</title><link>https://devzone.nordicsemi.com/thread/3174?ContentTypeID=1</link><pubDate>Wed, 09 Oct 2013 22:52:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb27bbba-f7a2-4abe-ad08-b85e63eaada5</guid><dc:creator>Carlos Cuevas</dc:creator><description>&lt;p&gt;What would be the best MSB (the one after the preamble, as cleared here) for the address in which the packet-error-rate is minimal?&lt;/p&gt;
&lt;p&gt;I just spent 4 hours debugging to find out that my address was the one causing problems.&lt;/p&gt;
&lt;p&gt;My application idea is to use 5-byte addressing but leave the MSByte constant for all of my devices, so the &amp;quot;internal&amp;quot; addresses of my sensor network would be 4 bytes long.&lt;/p&gt;
&lt;p&gt;I picked 0x48 as the constant MSB and had one device as PRX with address 0x48DDCCBBAA obviously DDCCBBAA was just a made up address to start coding the communication libraries.&lt;/p&gt;
&lt;p&gt;I found out that it was a terrible address, near 99% packets lost having the modules about 50cm apart, I switched the address to 0x481D1C1B1A (again, 1D1C1B1A was made up) and suddenly just 20% packets lost (I want to think due to interference with wifi networks around) a huge improvement!&lt;/p&gt;
&lt;p&gt;I would like to know what would be the best constant MSByte in order to avoid as much as possible lost packets.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m amazed at the suceptibility of the address value. In the field, this address is going to be generated randomly but would greatly appreciate if there are more detailed guidelines about choosing a strong address, maybe some algorithm which determines how strong a given address is, which also explains why some addresses cause high lost package counts.&lt;/p&gt;
&lt;p&gt;Thank you very much!
Over all, the nRF24L01+ is a great little chip!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ Address byte order</title><link>https://devzone.nordicsemi.com/thread/3173?ContentTypeID=1</link><pubDate>Tue, 08 Oct 2013 12:54:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd692f03-b368-41c4-a694-c0bac173ca3f</guid><dc:creator>Carlos Cuevas</dc:creator><description>&lt;p&gt;Thanks for clearing it out Håkon!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ Address byte order</title><link>https://devzone.nordicsemi.com/thread/3172?ContentTypeID=1</link><pubDate>Tue, 08 Oct 2013 10:37:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:838a0b96-ae95-4c06-b091-0618c4fee658</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;If you set your address in firmware to:
E3 59 59 59 53&lt;/p&gt;
&lt;p&gt;The way it goes over the air is:
53 59 59 59 E3&lt;/p&gt;
&lt;p&gt;The last byte you set in firmware is the first one to go on-air.
This byte should not be 0x00/0xFF/0x55/0xAA.&lt;/p&gt;
&lt;p&gt;Best regards
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>