<?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>51822 RF setting Problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2912/51822-rf-setting-problem</link><description>For our application, As I used 24LU1(host) with 51822(device) be the platform.
I hope to transmit Audio data with 8 kHz, 10 bits data format. To commit the requirements , I send a packet with 32 bytes payload every 2 ms, the details settings as follow</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 25 Jun 2014 11:37:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2912/51822-rf-setting-problem" /><item><title>RE: 51822 RF setting Problem</title><link>https://devzone.nordicsemi.com/thread/11081?ContentTypeID=1</link><pubDate>Wed, 25 Jun 2014 11:37:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9e768e4-6048-49b0-8da6-4a0b672f17f4</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;I will recommend that you try my comments for Q3 first before altering any other gazell configurations.&lt;/p&gt;
&lt;p&gt;Q1. Most likely it&amp;#39;s because you&amp;#39;re losing sync. I would recommend that you scope the VDD_PA pin on your device, and post the results here. This pin will go high for each TX on-air operation, and will give you a good overview if the sync is off.&lt;/p&gt;
&lt;p&gt;Q2. This function sets the number of timeslots that the device considers itself to be in sync with the host after a successful transfer. In your case, if you set this to 10, it will consider itself in sync for 10 x timeslot (with no successful communication) before the link is not-in-sync.
If after 9 timeslots you receive an ACK from the host, the link will be considered in-sync for the whole process.&lt;/p&gt;
&lt;p&gt;This means that you can get one packet through every 9 timeslots (9 ms in your case), giving a throughput of 3.5 kBps, and your link is considered in sync for the whole period.&lt;/p&gt;
&lt;p&gt;Try these settings. Host:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#define GZLL_DEFAULT_PARAM_RX_CHANNEL_HOLD_PERIODS 5
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Device:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;nrf_gzll_set_device_channel_selection_policy(NRF_GZLL_DEVICE_CHANNEL_SELECTION_POLICY_USE_SUCCESSFUL);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will cause your link to be asynchronous, but it will force the host to not switch RF channel for 10 ms if it receives a packet. The device will then start communication on the last successful RF channel. This will be a &amp;quot;frequency agility&amp;quot; approach, where the host and device only changes RF channel when the re-transmission count is high.&lt;/p&gt;
&lt;p&gt;This approach is not very good if you have other devices that needs consistent data transfer, as it disrupts the host listening pattern.&lt;/p&gt;
&lt;p&gt;Q3: This will cause the external 16M to be stopped/started by the gazell library. Note that it takes up to 1.5 ms for a 16M xtal to start up (nom. 800 - 1000 us on most xtals). I would recommend that you set this to NRF_GZLL_XOSC_CTL_MANUAL, and start the xtal manually before enabling the gazell library:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;// Start 16 MHz crystal oscillator.
NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED = 0;
NRF_CLOCK-&amp;gt;TASKS_HFCLKSTART    = 1;

// Wait for the external oscillator to start up.
while (NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED == 0) 
{
    // Do nothing.
}
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>