<?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>Disable standard adressing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7104/disable-standard-adressing</link><description>Hi, 
 I&amp;#39;m trying to implement an existing proprietary protocol on the nRF51422 SoC. In this protocol the device address is placed differently in the frame than the predefined adress fields and also it is not sent in every packet. I would like to know</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 May 2015 06:56:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7104/disable-standard-adressing" /><item><title>RE: Disable standard adressing</title><link>https://devzone.nordicsemi.com/thread/25094?ContentTypeID=1</link><pubDate>Wed, 20 May 2015 06:56:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0051dfdf-f63f-46b0-b3f4-808fe782532a</guid><dc:creator>cth</dc:creator><description>&lt;p&gt;Thanks for your help, Hung Bui. Now I know how to continue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Disable standard adressing</title><link>https://devzone.nordicsemi.com/thread/25093?ContentTypeID=1</link><pubDate>Tue, 19 May 2015 14:23:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25d1cd84-a94d-42c9-a735-ad90dd73a096</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@cth: You are correct on how the frame sync works.
No, it&amp;#39;s not possible to have a packet received without knowing the address that the RX expecting. Usually we use an common access address for broadcasting.&lt;/p&gt;
&lt;p&gt;For example, with Bluetooth Low Energy, the access address for BLE advertising (broadcast) is 0x8E89BED6&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Disable standard adressing</title><link>https://devzone.nordicsemi.com/thread/25092?ContentTypeID=1</link><pubDate>Tue, 19 May 2015 13:33:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1bed810-b0ce-46fa-8d7f-2fe26b4ac504</guid><dc:creator>cth</dc:creator><description>&lt;p&gt;Okay, I see so the transmitter uses one of 8 logical adresses when transmitting and the receiver has a correlator for each of these adresses that if active and matching triggers a frame sync. I wonder then how pairing/registration is done if I have a receiving unit that don&amp;#39;t know the BASE and PREFIX configuration of the transmitter. I guess this is not possible and that these units should be matched from production or enter a pairing/registration mode with a fixed address.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Disable standard adressing</title><link>https://devzone.nordicsemi.com/thread/25091?ContentTypeID=1</link><pubDate>Tue, 19 May 2015 11:23:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31cd4161-2f4f-44f1-8ec7-4ee20ff02176</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Cth,&lt;/p&gt;
&lt;p&gt;You can reduce the size of the BASE to 2 bytes to have 3 bytes address (BASE+PREFIX). But you can&amp;#39;t remove the field completely.&lt;/p&gt;
&lt;p&gt;The access address together with the preamble act as the sync words or START signal to tell the receive there&amp;#39;s a packet coming. Without the address you only have one byte preamble, it&amp;#39;s very easy to miscapture a false packet because of noise.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>