<?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>nRF905 preamble</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47122/nrf905-preamble</link><description>Hi everyone, 
 I am working on a project using nRF905 as an emitter and another Receiver(different than nRF905), the receiver is programmed in a way to perform some actions only when it received a specific frame(for example: 0x156666) but after reading</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 18 May 2021 06:27:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47122/nrf905-preamble" /><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/310016?ContentTypeID=1</link><pubDate>Tue, 18 May 2021 06:27:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0bde5557-ec8c-4aff-b243-64605d03ecfa</guid><dc:creator>Witek</dc:creator><description>&lt;p&gt;Hello Inubot,&lt;/p&gt;
&lt;p&gt;Been a while.&lt;/p&gt;
&lt;p&gt;Thanks for this info. It certainly helped... But I am not getting a reliable communication between the chips. If I am able to receive a message in nRF905 then it&amp;nbsp;sometimes is correct and sometimes is mangled up depending on what I send in the message. For the time being I am not using CRC checking, just to keep it simple.&lt;/p&gt;
&lt;p&gt;Can you confirm that you were albe to get the&amp;nbsp;two devices communicate reliably?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Witek&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/260040?ContentTypeID=1</link><pubDate>Wed, 15 Jul 2020 07:06:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d98e9d55-8c85-4bc5-99cb-849bcce13547</guid><dc:creator>Inubot</dc:creator><description>&lt;p&gt;Hi Witek,&lt;/p&gt;
&lt;p&gt;I have used the S2-LP DK GUI (&lt;a href="https://www.st.com/en/embedded-software/stsw-s2lp-dk.html"&gt;https://www.st.com/en/embedded-software/stsw-s2lp-dk.html&lt;/a&gt;) to tinker with the register values of the S2-LP to match the RF parameters of the NRF905.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In my case the S2-LP was setup with the following radio settings (have a look at the above link for a screenshot of the DK):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;433 MHz freq base (assuming no channel offset on NRF905)&lt;/li&gt;
&lt;li&gt;100 ksps data rate (data transmission rate of the NRF905)&lt;/li&gt;
&lt;li&gt;50 kHz freq deviation (typical freq deviation of NRF905)&lt;/li&gt;
&lt;li&gt;250 kHz channel filter&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Max power ticked&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For the packet settings, you need to remove the preamble, sync word, length and CRC segments of the packet structure, and uncheck data whitening. You should only be left with the payload section of the packet.&lt;/p&gt;
&lt;p&gt;In order to transmit data from the S2-LP to an NRF905 device, you will have to build up the payload to include the NRF905 preamble and address before the actual transmission data, followed by the CRC:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;1111110101[Address][Data][CRC]&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This entire stream should be written to the TX buffer of the S2-LP.&lt;/p&gt;
&lt;p&gt;If done correctly, the NRF905 should pick up the transmission and an interrupt should be triggered on the DR pin. You can also use the AM pin to help with troubleshooting.&lt;/p&gt;
&lt;p&gt;Hope this helps!&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/260029?ContentTypeID=1</link><pubDate>Wed, 15 Jul 2020 05:49:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a942bcb0-5adb-4e55-beee-e73158a07513</guid><dc:creator>Witek</dc:creator><description>&lt;p&gt;Hello Inubot,&lt;/p&gt;
&lt;p&gt;It has been a while but thanks for sharing your experience.&lt;/p&gt;
&lt;p&gt;I am facing the same task as you did. Would you be able to share more info on how you set up the S2-LP chip to enable the two to communicate.&lt;/p&gt;
&lt;p&gt;Any info will be appreciated.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Witek&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/205830?ContentTypeID=1</link><pubDate>Fri, 23 Aug 2019 09:43:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63912c99-13b6-468a-9299-0c0afd672ee9</guid><dc:creator>Inubot</dc:creator><description>&lt;p&gt;I also ran into this problem with no answers online. I needed an S2-LP device from STMicroelectronics to communicate with an NRF905 in a legacy system. After a few days of reverse-engineering multiple packets sent by an NRF905 device, I was able to decode the preamble and CRC algorithm:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Preamble:&amp;nbsp;01010101010110011001 (Manchester IEEE encoded) 1111110101 (bits)&lt;/li&gt;
&lt;li&gt;CRC uses the&amp;nbsp;CRC-16/CCITT-FALSE algorithm&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The raw bitstream you need to send then becomes 1111110101[Address][Payload][CRC]. Remember that the bitstream that is transmitted should first by Manchester IEEE encoded!&lt;/p&gt;
&lt;p&gt;Hope this helps!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/186747?ContentTypeID=1</link><pubDate>Mon, 13 May 2019 13:47:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6659069f-d85c-447f-ad99-a3b25cd0a6db</guid><dc:creator>El Farissi</dc:creator><description>&lt;p&gt;I&amp;nbsp;&lt;span&gt;agree with you! but I am using a receiver different than nRF905 an I want to know the content of the preamble to have an idea of the whole frame send by the nRF. where can I find the content of the preamble?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/186723?ContentTypeID=1</link><pubDate>Mon, 13 May 2019 13:09:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4df2831-70c8-4099-8195-2fd5bffebc08</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;The preamble is used by the receiver to lock on to the signal. Not something the application mcu need to handle.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/186628?ContentTypeID=1</link><pubDate>Mon, 13 May 2019 09:57:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5859331-d275-46af-a74b-9ca358152c0b</guid><dc:creator>El Farissi</dc:creator><description>&lt;p&gt;Thank your for your Answer. Do you have any idea about the content of the preamble because I need to handle it by the receiver?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF905 preamble</title><link>https://devzone.nordicsemi.com/thread/186572?ContentTypeID=1</link><pubDate>Mon, 13 May 2019 08:03:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d76ffb19-cd16-4129-b8f4-f4a76bf45a88</guid><dc:creator>run_ar</dc:creator><description>[quote user=""]My question is: it is possible to remove the preamble and the address and keep only the payload? If not, what does 10 bit of the preamble looks like?[/quote]
&lt;p&gt;&amp;nbsp;No. That is not possible.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>