<?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>When the TX_ADDRESS of the receiver nRF905 is 0x55, 0xA5, and 0xFF, only the data cannot be received.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50962/when-the-tx_address-of-the-receiver-nrf905-is-0x55-0xa5-and-0xff-only-the-data-cannot-be-received</link><description>HI, I recently used nRF905, a one-to-many intercommunication project, because one-to-many will send corresponding instructions for machines with different serial numbers, and need multiple receiving addresses (default is 0xE7). When I set to 0x55 as the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 15 Aug 2019 10:54:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50962/when-the-tx_address-of-the-receiver-nrf905-is-0x55-0xa5-and-0xff-only-the-data-cannot-be-received" /><item><title>RE: When the TX_ADDRESS of the receiver nRF905 is 0x55, 0xA5, and 0xFF, only the data cannot be received.</title><link>https://devzone.nordicsemi.com/thread/204272?ContentTypeID=1</link><pubDate>Thu, 15 Aug 2019 10:54:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7a84a7e-b7d5-4989-9e27-0ab7422ae54f</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;The only intention of the preamble is for the radio front-end to &amp;quot;lock on&amp;quot; the modulated carrier, it&amp;#39;s not&amp;nbsp;part of the received packet that is decoded by the application or radio. It&amp;#39;s added automatically by hardware before packet transmission, this ensure that the the receiver to successfully demodulate the address, data and crc.&lt;/p&gt;
&lt;p&gt;You may in your case also look into the design of the nRF905, to make sure you have in great detail follow the schematic and layout (with same clearance, cut-out, vias, matching etc). Verify the layout is working as intended by measure the carrier and output power on a spectrum analyzer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t have any other product for the sub 1GHz no.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: When the TX_ADDRESS of the receiver nRF905 is 0x55, 0xA5, and 0xFF, only the data cannot be received.</title><link>https://devzone.nordicsemi.com/thread/204230?ContentTypeID=1</link><pubDate>Thu, 15 Aug 2019 08:11:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c003ebed-d3da-4741-b521-d5cdbc9043ce</guid><dc:creator>LiAMI</dc:creator><description>&lt;div class="text-wrap tlid-copy-target"&gt;
&lt;div class="result-shield-container tlid-copy-target"&gt;&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span class="" title=""&gt;&lt;/span&gt;&lt;span title=""&gt;Thank you for your reply. I have enabled the 2byte CRC. I have read back the contents of the RF Config register when the device is in the receiving state. There is no problem, but the situation that 0x55 and 0xA5 cannot be received still exists. I will not use these two addresses for the time being. RX_ADDRESS value, do you have other better similar chip models that do not have address restrictions? &lt;br /&gt;In addition, can you explain in detail how the data packet identification is implemented when nRF905 receives data, for example, how is the preamble and address removed after the CRC check is completed? If the address error is set to 0x55 (01010101), will it Is it recognized as the preamble, caused to be removed and lose the packet ?&lt;/span&gt;&lt;/span&gt;&lt;span class="tlid-translation-gender-indicator translation-gender-indicator"&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div id="easyshare-extenstion-container"&gt;
&lt;div&gt;
&lt;div style="left:-12px;position:absolute;top:11px;"&gt;&lt;/div&gt;
&lt;div class="_3P0 "&gt;&lt;/div&gt;
&lt;aside style="right:0px;top:6px;"&gt;
&lt;div style="position:relative;right:6px;"&gt;&lt;/div&gt;
&lt;div style="position:absolute;right:0px;top:20px;" id="easyshare-menu"&gt;
&lt;div class="_3lO"&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/aside&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: When the TX_ADDRESS of the receiver nRF905 is 0x55, 0xA5, and 0xFF, only the data cannot be received.</title><link>https://devzone.nordicsemi.com/thread/204039?ContentTypeID=1</link><pubDate>Wed, 14 Aug 2019 11:18:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fe9cf8bd-8f39-495b-89be-7479e966a29d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;In general using address bytes of AA and 55 can be problematic since it resemble the preamble, using 00 and FF is a bad idea since it occurs frequently in random demodulated noise. So try to avoid those 4 bytes in your address (especially as the first byte).&lt;/p&gt;
&lt;p&gt;Also I recommend to enable 2byte CRC instead of 1byte CRC. You may consider readback all 9 bytes in the RF Config register to verify all are set as expected.&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>