<?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+ radio pipe address</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7523/nrf24l01-radio-pipe-address</link><description>Hello, 
 Is there a restriction that I cannot have same address LSByte for radio pipes?
It seems that i am failing to receive data on pipe 0 if for example I have pipe 0 and pipe 1 address LSByte as 0. 
 thank you
jing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Jun 2015 15:51:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7523/nrf24l01-radio-pipe-address" /><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26795?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 15:51:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae9553e5-c38b-4f37-bc44-f0b52a5b4804</guid><dc:creator>jing</dc:creator><description>&lt;p&gt;you are right.
how could I missed this!&lt;/p&gt;
&lt;p&gt;thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26790?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 15:42:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97462285-7832-49f6-8a2f-35d6cae2da4e</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Jing: thanks for the link. Sorry we have so many product that I couldn&amp;#39;t remember the abbreviation.&lt;/p&gt;
&lt;p&gt;Actually, you were correct in the observation that LSB of Pipe 0 should not equal to LSB of Pipe 1 or other pipe. If you have a look at page 44 in the nRF24LU1+ Product Specification you can find this:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;The LSByte must be unique for all six pipes
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Same can be found in the nRF24L01+ and nRF24LE1 documentation.&lt;/p&gt;
&lt;p&gt;So, even for pipe 0 where it has its own base address, the LSB must be Unique.&lt;/p&gt;
&lt;p&gt;I couldn&amp;#39;t find that in the nRF51 documentation but I suspect that the same applied. I will check this with the developer.&lt;/p&gt;
&lt;p&gt;Sorry that I didn&amp;#39;t catch this at the first place.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26793?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 14:45:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7f4e27d-88c2-423e-a895-d3ef4f95bbd3</guid><dc:creator>jing</dc:creator><description>&lt;p&gt;nrfready desktop 2 --&amp;gt; &lt;a href="https://www.nordicsemi.com/eng/Products/Bluetooth-Smart-Bluetooth-low-energy/nRFready-Desktop-2-Reference-Design"&gt;www.nordicsemi.com/.../nRFready-Desktop-2-Reference-Design&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26794?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 14:36:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b218e3a-bbf8-4cd6-946b-5a891b8d025f</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@jing:Sorry that I might not very familiar with legacy product, but what is dt2 v2.2.0 ? Could you give me a link ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26792?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 14:20:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:869e9d55-5450-4572-8cf7-39e23e3d5533</guid><dc:creator>jing</dc:creator><description>&lt;p&gt;original dt2 v2.2.0 code works.
but as long as there is an opened non-zero pipe with prefix byte similar to pairing pipe (pipe 0) prefix byte, I cannot seem to be able to pair with the dongle&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26797?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 12:46:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5253f629-2001-4506-abbf-c7e9f35151c6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Jing:
Could you let me know what exactly the Base Address Pipe 0 and Base Address Pipe 1 are and prefix Pipe 0 and Prefix Pipe 1 are ?&lt;/p&gt;
&lt;p&gt;Also please let me know what set up worked, what set up doesn&amp;#39;t work. If you don&amp;#39;t change the prefix byte for pipe 1 to 0 but something else, would it work ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26796?ContentTypeID=1</link><pubDate>Thu, 11 Jun 2015 02:51:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0f28d0e-57b0-4de8-a40f-7eea9b72caa3</guid><dc:creator>jing</dc:creator><description>&lt;p&gt;yes. I am using gazell which is based on ESB.
and yes, confirmed&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;LU1p ChidID is different from the gzp pairing address; therefore base address for pipe 0 and 1 should be different on the dongle side.&lt;/li&gt;
&lt;li&gt;initial base address for pipe &amp;gt; 0 is different from gzp pairing address on the device side&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Receiver side is using the nrf24lu1p dongle code while Device side is running nrf51822 application using the gzll_arm.lib provided with the DT2.&lt;/p&gt;
&lt;p&gt;For this experiment, i just changed the gzp_update_radio_params() on both dongle and device code to set the prefix byte for pipes 1 onward to start from 0 and then i could not pair.&lt;/p&gt;
&lt;p&gt;jing&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf24L01+ radio pipe address</title><link>https://devzone.nordicsemi.com/thread/26791?ContentTypeID=1</link><pubDate>Wed, 10 Jun 2015 10:39:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17f6e7cd-94f9-4112-b869-d1d13d0fdfc4</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Jing: I am assuming you were talking about Enhanced Shockburst protocol. On Pipe 0 and Pipe 1 you should have no problem having them with same LSByte.&lt;/p&gt;
&lt;p&gt;The restriction is applied only for Pipe 1 to pipe 5 where they share the same 4 MSBytes.&lt;/p&gt;
&lt;p&gt;Have you made sure the MSB first 4 bytes on pipe 0 and pipe 1 are different ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>