<?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>Slave latency useful if always transmitting data?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/93562/slave-latency-useful-if-always-transmitting-data</link><description>Hi, 
 I am developing the nRF52833 DK with NCS v2.0. The goal of the application is continuously send temperature data (using health thermometer service). I am currently trying to reduce energy consumption as much as possible to save battery life . 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 Nov 2022 08:05:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/93562/slave-latency-useful-if-always-transmitting-data" /><item><title>RE: Slave latency useful if always transmitting data?</title><link>https://devzone.nordicsemi.com/thread/394838?ContentTypeID=1</link><pubDate>Wed, 09 Nov 2022 08:05:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79e06953-a807-4dc8-bef3-c0f6494e8da8</guid><dc:creator>Karl Ylvisaker</dc:creator><description>&lt;p&gt;No problem at all, Adam! :)&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Please do not hesitate to open another ticket if you should encounter any other issues or questions in the future.&lt;br /&gt;&lt;br /&gt;Good luck with your development!&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Slave latency useful if always transmitting data?</title><link>https://devzone.nordicsemi.com/thread/394818?ContentTypeID=1</link><pubDate>Tue, 08 Nov 2022 23:50:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a72a975-05ab-4087-8373-5353f91fa197</guid><dc:creator>adam_atmo</dc:creator><description>&lt;p&gt;Thanks Karl!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Slave latency useful if always transmitting data?</title><link>https://devzone.nordicsemi.com/thread/394068?ContentTypeID=1</link><pubDate>Fri, 04 Nov 2022 08:43:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e20bcb0a-0264-4979-8246-0e13dcb45e4a</guid><dc:creator>Karl Ylvisaker</dc:creator><description>&lt;p&gt;Hello Adam,&lt;br /&gt;&lt;br /&gt;Correct - using slave latency will allow the peripheral to skip a connection event (or multiple) if it does not have any new data to transmit, which will reduce your over all power consumption by reducing the number of empty packets being sent in order to maintain the link.&lt;br /&gt;&lt;br /&gt;If you are&amp;nbsp;&lt;em&gt;certain&lt;/em&gt; that there always will be data ready for transfer when a connection event is upcoming then the peripheral will always transfer in these events, and so there will be no impact of enabling slave latency. In this case the slave latency would indeed be redundant.&lt;br /&gt;In this case your best bet would be to increase the connection interval as much as possible, in order to decrease power consumption by the radio.&lt;br /&gt;Having slave latency enabled does not cost any additional power, so if there is a chance that you will not have data to send for some time, then it would be beneficial to enable slave latency.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>