<?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+ as TX and nRF51822 as RX</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6840/nrf24l01-as-tx-and-nrf51822-as-rx</link><description>I have a nRF24L01+ connecting to an Arduino board using the RF24 library code. It is a print of the registers: 
 
 On the nRF51822 I have the following code: 
 int main()
{
 // Initialize ESB
 (void)nrf_esb_init(NRF_ESB_MODE_PRX);
	
 nrf_esb_set_base_address_length</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 06 May 2015 09:51:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6840/nrf24l01-as-tx-and-nrf51822-as-rx" /><item><title>RE: nRF24L01+ as TX and nRF51822 as RX</title><link>https://devzone.nordicsemi.com/thread/24108?ContentTypeID=1</link><pubDate>Wed, 06 May 2015 09:51:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a0fb075-8eed-4cbe-a463-021aab669e7b</guid><dc:creator>Jose Xavier</dc:creator><description>&lt;p&gt;It was indeed a address problem, thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ as TX and nRF51822 as RX</title><link>https://devzone.nordicsemi.com/thread/24107?ContentTypeID=1</link><pubDate>Mon, 04 May 2015 14:29:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ee471af-4837-43a8-b8da-5eb8bce0e764</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Jose&lt;/p&gt;
&lt;p&gt;In my experience most of the compatibility issues between the nRF24L and nRF51 series are address related, as the address configuration is handled quite differently between them.&lt;/p&gt;
&lt;p&gt;To see if this is the issue for you as well could you please try to configure both devices with the following address?
0xE7, 0xE7, 0xE7, 0xE7, 0xE7&lt;/p&gt;
&lt;p&gt;Then we will  know if its address related or not, making it easier to isolate the issue.&lt;/p&gt;
&lt;p&gt;Regards
Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>