<?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>Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50926/measure-nrf24l01-rssi</link><description>Hey, 
 
 I have a product which is using nrf24l01+ for communication. There is packet loss in the communication which I am trying to figure out the reason for. Is it possible to build a sniffer which can measure the RSSI at the receiver side, with nrf52</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 Aug 2019 07:42:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50926/measure-nrf24l01-rssi" /><item><title>RE: Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/thread/207010?ContentTypeID=1</link><pubDate>Fri, 30 Aug 2019 07:42:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4fc605e9-c356-4dfa-9d77-b4b41933a816</guid><dc:creator>Ashish</dc:creator><description>&lt;p&gt;Thanks for your reply Kenneth.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I will try your suggestions and will let you know.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/thread/206528?ContentTypeID=1</link><pubDate>Wed, 28 Aug 2019 08:26:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76c4ef41-726d-4cbb-b7f3-f69165cd523d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;I don&amp;#39;t understand why 1Mbps is very slow either, because the turn around time is not a big difference, e.g.:&lt;/p&gt;
&lt;p&gt;TX 2Mbps 32byte payload with ack: 130us+160us+130us+40us = 460us&lt;br /&gt;&lt;span&gt;TX 1Mbps 32byte payload with ack: 130us+320us+130us+80us = 660us&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I do not see any advantage of setting retransmit delay to max (4000), set it to 500us should be fine. It should also increase the speed.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/thread/206374?ContentTypeID=1</link><pubDate>Tue, 27 Aug 2019 12:18:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:40ce3522-15c7-4c9a-8539-f21729d3a469</guid><dc:creator>Ashish</dc:creator><description>&lt;p&gt;Retransmit count is set to 15 and retransmit delay is at max. The frequencies once set are not changed. On the PRX side, I am using RF24 library (&lt;a href="https://tmrh20.github.io/RF24/RPi.html"&gt;https://tmrh20.github.io/RF24/RPi.html&lt;/a&gt;) with raspberry pi, so that handles the PRX pin status. I have tried once with the 1Mbps rate, but that became very slow so didn&amp;#39;t test that much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/thread/206365?ContentTypeID=1</link><pubDate>Tue, 27 Aug 2019 12:08:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b75283a0-0082-46dd-a5ff-88c645fc9786</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;What retransmit count and retransmit delay are you using here? Are you changing frequency? Do you on the PRX keep CE high at all times, or do you cycle the CE at any time? Have you tried using 1Mbps instead?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/thread/206355?ContentTypeID=1</link><pubDate>Tue, 27 Aug 2019 11:56:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:333ffccf-9b13-4b07-8158-6cd11b1a7404</guid><dc:creator>Ashish</dc:creator><description>&lt;p&gt;Hi Keneth,&lt;/p&gt;
&lt;p&gt;Thanks for your reply.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I understand making a pure sniffer will be difficult, so I have dropped that idea.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regarding the packet losses, they appear to be random. The transmitter while sending 500+ packets may miss 1 or 2 packets in between. It doesn&amp;#39;t happen always though.&lt;/p&gt;
&lt;p&gt;Also, the transmitter misses ack packets. I am not using ack payloads, so I guess there will be a ack packet with the PID only. The transmitter sometimes just misses that ack packet and as it is depending upon the ack packet to know whether the receiver has succesfully received the packet or not, it sometimes gets into a stage where the transmitter feels like there were packet drops however the receiver has received all the packets. I have a packet retransmit mechanism on the application side too, but it is dependent on the hardware level ack which are missing for some reason. Right now I am trying to change this, I have implemented a simple ack mechanism on the software side but the results will take some time.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;From my initial testings, more the distance, more are the packet loss but it surely happens sometimes with nearby sensor too. I&amp;nbsp;get that there might be interference due to other devices running on same band, so I am still looking into this.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regarding the PCB layout, we have checked the reference layout and the PCB guidelines and tried to follow them.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you have any idea on why am I loosing the hardware ack packets, please let me know.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Measure nrf24l01+ RSSI</title><link>https://devzone.nordicsemi.com/thread/206331?ContentTypeID=1</link><pubDate>Tue, 27 Aug 2019 11:02:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:485c3084-f7c9-4c27-9f4e-914e8d1efb51</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It is not straight forward to make a&amp;nbsp;pure sniffer RX no, but if you know the address and frequency, then you can setup for instance an nRF24L01+ in standard SB mode (clear FEATURE and EN_AA registers), set maximum payload length (32) and disable CRC. Then each time there is an address match, the data will be received by the nRF24L01+, and the payload can be read out by MCU. However, the&amp;nbsp;received payload&amp;nbsp;will then include the 9bit PID field in the beginning of the packet, and actual data is shifted thereby 9bits, also CRC will not be checked in any way, so you will need to check the data entirely by the application firmware on the MCU, data may be erroneous, and random demodulated noise will be at the end of the packet if the payload is shorter than maximum length (32).&lt;/p&gt;
&lt;p&gt;I highly doubt measure RSSI will&amp;nbsp;help, I think it will help you can describe a bit more when you experience packet loss. Does it happen independent of distance, is there other 2.4GHz noise in near proximity, what amount of packet loss do you experience, are you using ack payloads, if yes what is the size of the ack payload and retransmit delay? Have you measured the output power on an spectrum analyzer? Have you followed the reference layout carefully and the PCB guidelines in the datasheet?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>