<?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>Switch GZLL stack frequently on/off</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4335/switch-gzll-stack-frequently-on-off</link><description>Hi all, 
 I try to reduce the power consumption of my GZLL host (RFDduino/nRF51822).
I use the Arduino IDE to program my RFDuino.
My Idea was to synchronize the host and the device so that the host is able to sleep
between the receives. The host starts</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Nov 2014 10:10:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4335/switch-gzll-stack-frequently-on-off" /><item><title>RE: Switch GZLL stack frequently on/off</title><link>https://devzone.nordicsemi.com/thread/15432?ContentTypeID=1</link><pubDate>Thu, 06 Nov 2014 10:10:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:694ab39f-52d4-4a3c-b7be-3427b939d4f0</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;Q1: Yes, you should be able to put the host to sleep en between radio events, but you need to take clock and hence timing drift into account. So you might wake up too early and hence get the incoming packet, but the ACK might be lost due to the host going into sleep too early for the ACK. For debugging I would recommend you to try and verify the on/off cycles compared to the actual radio events. Perhaps you need to prolong the on periods in order to get a stable link.&lt;/p&gt;
&lt;p&gt;Q2: If you are able to fine tune the timing on the on/off you should see some improvement on average power consumption. But again, you need to have listening windows wide enough to send packet and receive ACK. If not, you will re-transmit more than needed and hence actually have worse power consumption than needed.&lt;/p&gt;
&lt;p&gt;Q3: It sounds like timing issues between the host and the device due to the sleep. Check the drift on your timing source and compare actual on-air-activity to you sleep cycles.&lt;/p&gt;
&lt;p&gt;Q4: Yes, there&amp;#39;s a FIFO on the host. If the host receives a message, it will give the application an interrupt/event right away as long as it was received correctly.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>