<?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+ -&amp;gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22480/nrf24l01---nrf24lu1-rf-communication</link><description>HI. 
 I want to send data from nRF24L01 + to RF communication and receive it from nRF24LU1 +.
The nRF24L01 + is connected to the STM32. The settings are as follows. 
 
 nRF24L01+ code 
 
 #if (DEMO_TX_SINGLE)

// The transmitter sends a 5-byte</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 15 Jun 2017 14:32:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22480/nrf24l01---nrf24lu1-rf-communication" /><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88405?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2017 14:32:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f1a5229-36dc-43de-9ee2-66734cf6dcfc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Ha ha thanks. But disabling CRC is not the solution. It&amp;#39;s only to check what would cause the issue. No CRC check will result getting corrupted packet without detecting it. With your result, it could be that the CRC setting was wrong.&lt;/p&gt;
&lt;p&gt;I would suggest you to check the raw packet you receive to see any corruption (when you have no CRC)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88406?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 10:01:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:84dd5c8a-bde7-41ef-b16c-1df8d9a69677</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;I turned off CRC, It worked really well !!&lt;/p&gt;
&lt;p&gt;Thank you so much.&lt;/p&gt;
&lt;p&gt;You were a great help to me&lt;/p&gt;
&lt;p&gt;Are you a genius? or you must be a saviour of mankind.&lt;/p&gt;
&lt;p&gt;If you don&amp;#39;t mind, could you tell me how to figure out the solution?&lt;/p&gt;
&lt;p&gt;It said &amp;quot;The CRC is the error detection mechanism in the packet.&amp;quot; in the datasheet. What role does it play in communication?&lt;/p&gt;
&lt;p&gt;Again, Thank you so much and I really appreciate for your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88397?ContentTypeID=1</link><pubDate>Fri, 09 Jun 2017 12:53:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:68d82af7-ccf7-45ce-a239-5c99d0d705fa</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;nRF24LU1 and nRF24L01+ should be able to talk to each other. We have millions of product doing that out there on the market (wireless mouse keyboard, etc).&lt;/p&gt;
&lt;p&gt;Please follow my suggestion.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88392?ContentTypeID=1</link><pubDate>Fri, 09 Jun 2017 09:59:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7eb8839c-0b13-4938-b5a5-a422a0300acf</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;nRF24L01+ nRF24LU1+ is available for communication? TT TT&lt;/p&gt;
&lt;p&gt;nRF24L01+ &amp;lt;-&amp;gt; nRF24L01+ The communication was successful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88404?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2017 12:26:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8db70d51-7dc9-4a65-bd5e-b3692ed888ba</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Thanks for updating the case, the address setting was much different before the update.&lt;/p&gt;
&lt;p&gt;From the configuration you sent I can&amp;#39;t find anything wrong with that.&lt;/p&gt;
&lt;p&gt;My suggestions are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Try to test with no CRC. This is to check if there is lots of interference or if the radio on the nRF24LU1 was not good. Have you tried to use 2 nRF24LU1/LE1 to talk to each other ?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Read the radio configuration register on the L01 and compare with the register on the LU1. This is to verify that the writing from the STM to the L01 was correct. And so that we can reproduce here.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88391?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2017 09:29:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b2825cd1-1ad2-45b8-8dcf-c2519220f629</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;?!?!?!!?&lt;/p&gt;
&lt;p&gt;nrf24l01&lt;/p&gt;
&lt;p&gt;nRF24_SetRFChannel(2);&lt;/p&gt;
&lt;p&gt;static const uint8_t nRF24_ADDR[] = { 0xE7,0xE7,0xE7,0xE7,0xE7 };&lt;/p&gt;
&lt;p&gt;nrf24lu1&lt;/p&gt;
&lt;p&gt;hal_nrf_set_rf_channel(2);&lt;/p&gt;
&lt;p&gt;hal_nrf_set_address(HAL_NRF_PIPE1, default_pipe_address);&lt;/p&gt;
&lt;p&gt;// static uint8_t xdata default_pipe_address[5] = PIPE_ADDRESS;
(#define PIPE_ADDRESS {0xE7,0xE7,0xE7,0xE7,0xE7})&lt;/p&gt;
&lt;p&gt;Is this not a match??!?!?!?!!?&lt;/p&gt;
&lt;p&gt;Sometimes I thought the address and channel were consistent because the data was received.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88390?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2017 08:23:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0ec526e-7b7b-430f-a3f6-41f5219f5311</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;If you use those code, address and channel doesn&amp;#39;t match. You need to create very simple code to test.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88389?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2017 08:05:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9914e686-3a5f-4619-9a26-7cb416bde032</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;I posted the code.&lt;/p&gt;
&lt;p&gt;The 01+ code was referenced in github.&lt;/p&gt;
&lt;p&gt;The U1 + code was referenced to enhanced_shockburst_prx_nrf24lu1p in nRFgo SDK 2.3.0.10040.&lt;/p&gt;
&lt;p&gt;NRF24L01+ &amp;lt;-&amp;gt; nRF24L01+ communication is good.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88393?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2017 16:32:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:86526f5d-d8f6-4c0b-99ca-e7a9df2d10ce</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Please follow what I suggested, use Appendix A. Also please post your code where you configure the radio, on both nRF24L01 and nRF24LU1.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88400?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2017 13:49:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:38bb51a0-fc4b-4920-b845-dbd01bed18ff</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;Normally, no data is received.&lt;/p&gt;
&lt;p&gt;However, very occasionally data is received. only once.&lt;/p&gt;
&lt;p&gt;I will go crazy.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88403?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2017 07:55:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f9581327-a525-4ab0-9e38-e76a1122edd2</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Powerup: I don&amp;#39;t see the point of creating a new case. You can always edit the question and add more information in. And why would you say here &amp;quot;sometimes an interrupt occurs&amp;quot; but in the other case you mentioned &amp;quot;there is no reaction at all &amp;quot; ?&lt;/p&gt;
&lt;p&gt;The example for STM you pointed to, looks a little bit complex. I would suggest you to create a very simple one, try to follow &lt;strong&gt;Appendix A&lt;/strong&gt; in the nRF24L01P product spec. Make sure you match the address on the nRF24L01P and the nRF24LU1. I&amp;#39;m not sure which address you are using. Then match the RF channel you use, and other setting such as ACK, number CRC bytes, data rate, etc.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88402?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2017 02:47:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f857e98e-2199-4bbd-a4e4-ccf0d0a94032</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;I updated the question again in detail.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/question/149170/nrf24l01-nrf24lu1-rf-communication-problem/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88401?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2017 02:44:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:089ab955-c6fe-446b-a9a5-2e17d4f1c4c9</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;You are viewing NRF_ISR () triggered by the HAL_NRF_RX_DR event.
Sometimes an interrupt occurs, but sometimes it does not.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88399?ContentTypeID=1</link><pubDate>Tue, 06 Jun 2017 11:51:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d36d94b-4e2a-4f55-a91d-8c6b84f64f14</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;NRF_ISR() is as description, the radio interrupt. It&amp;#39;s defined in isrdef24lu1p.h
Do you see the NRF_ISR() triggered with HAL_NRF_RX_DR event  on the PRX side ?&lt;/p&gt;
&lt;p&gt;What exactly you meant by &amp;quot;the interrupt timing of the NRF_ISR () function is different&amp;quot; ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88398?ContentTypeID=1</link><pubDate>Mon, 05 Jun 2017 08:53:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a066ae1-4317-4732-8901-dfc0c1d8047d</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;NRF_ISR () When does this function&amp;#39;s interrupt occur?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88396?ContentTypeID=1</link><pubDate>Fri, 02 Jun 2017 09:14:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b088045c-85ae-420e-83b4-24f5dee9de03</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Sorry I was not clear in my answer. I suggest that so that you can test the Radio and make sure the 2 chips can talk to each other, after that you can implement HID or copy the code for RF setting and add it into the HID example.&lt;/p&gt;
&lt;p&gt;In the ESB example, you can verify if the RF communication is successful by turning off or on an LED for example, depends if the bit you send is 1 or 0.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88395?ContentTypeID=1</link><pubDate>Fri, 02 Jun 2017 03:53:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb0002c3-2ef5-4a3d-aef6-5870c639eb75</guid><dc:creator>powerup</dc:creator><description>&lt;p&gt;If you use the example, it will not recognize it as a USB device.
Also, how do you know that RF communication is successful?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF24L01+ -&gt; nRF24LU1+ RF communication.</title><link>https://devzone.nordicsemi.com/thread/88394?ContentTypeID=1</link><pubDate>Thu, 01 Jun 2017 11:32:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ba13880-68d3-439b-ac41-fe3ec417393a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;I would suggest you to write you code for nRF24LU1 based on the ESB example we have in the nRFGo SDK instead of using the nAN-22. The example is inside \nRFgo SDK 2.3.0.10040\source_code\projects\nrfgo_sdk\enhanced_shockburst_examples&lt;/p&gt;
&lt;p&gt;If you have 2 nRF24LU1 board you can test and make sure they talk to each other first, then you can test with nRF24L01P&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>