<?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+ doesn&amp;#39;t receive on pipes 2-5</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5429/nrf24l01-doesn-t-receive-on-pipes-2-5</link><description>Hello all, 
 after a long period of trial and error I come for advice. I use the NRF24L01+ module with a slightly modified NRF24-library based on the work of MikeM ( www.airspayce.com/.../) . I am aware of the upgrade to the RadioHead library, I just</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 05 Feb 2015 18:52:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5429/nrf24l01-doesn-t-receive-on-pipes-2-5" /><item><title>RE: NRF24L01+ doesn't receive on pipes 2-5</title><link>https://devzone.nordicsemi.com/thread/18940?ContentTypeID=1</link><pubDate>Thu, 05 Feb 2015 18:52:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbfa32a6-3fea-4a99-a71e-1219971d9afa</guid><dc:creator>Jack</dc:creator><description>&lt;p&gt;Thank you for the reply, yes I figured it out :D Just wanted to share for in case someone else bumps into this problem, either with or without the specific library I mentioned.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF24L01+ doesn't receive on pipes 2-5</title><link>https://devzone.nordicsemi.com/thread/18939?ContentTypeID=1</link><pubDate>Thu, 05 Feb 2015 16:41:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bccda8bf-1388-444c-863e-6e4f94d0b522</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;It sounds like you figured it out or am I misunderstanding something here? The order of the bytes is important as pipe 1-5 share 4 MSB and the LSB needs to unique.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF24L01+ doesn't receive on pipes 2-5</title><link>https://devzone.nordicsemi.com/thread/18938?ContentTypeID=1</link><pubDate>Thu, 05 Feb 2015 10:16:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f90a9c16-1a73-44b4-97f9-68f913ee0afa</guid><dc:creator>Jack</dc:creator><description>&lt;p&gt;The address for the pipes is shifted in LSB first. Pipe 2-5 share the 4 MSB&amp;#39;s with pipe 1. In my code something happens like:&lt;/p&gt;
&lt;p&gt;[code]
address = &amp;quot;recv1&amp;quot;&lt;/p&gt;
&lt;p&gt;shift this into the address for pipe 1.
[/code]&lt;/p&gt;
&lt;p&gt;And this is where things go wrong: &amp;quot;recv1&amp;quot; sort of implies the &amp;quot;1&amp;quot; is the LSB, but the code shifts this out to the NRF24 as the last byte, so the NRF treats it like the MSB. To the NRF the LSB is &amp;quot;r&amp;quot; !&lt;/p&gt;
&lt;p&gt;Now in order to set pipe 2 to &amp;quot;recv2&amp;quot; I did:&lt;/p&gt;
&lt;p&gt;[code]
address = &amp;quot;recv2&amp;quot;&lt;/p&gt;
&lt;p&gt;and shift this into pipe 2.
[/code]&lt;/p&gt;
&lt;p&gt;The code does pick the &amp;quot;2&amp;quot; as the LSB to shift out to the NRF (thinking address[4] is the LSB), but instead of setting the address to &amp;quot;recv2&amp;quot; we get &amp;quot;2ecv1&amp;quot;.&lt;/p&gt;
&lt;p&gt;My solution was to adapt the code so address runs from LSB to MSB, and for pipe 2-5 it uses address[0] to write for the LSB for one of the pipes 2-5.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Jack&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>