<?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>Invisible beacon (Peripheral) at Ultra low power and able to make DFU over the air from Reader (Central)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/32730/invisible-beacon-peripheral-at-ultra-low-power-and-able-to-make-dfu-over-the-air-from-reader-central</link><description>Hello, 
 I am developing a new application for Asset Tracking, whose general architecture is the common one - where Beacons are mounted on asset and the Reader scan for Advertisement data. The architecture is clear and simple but with 3 special requirements</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 28 Mar 2018 11:42:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/32730/invisible-beacon-peripheral-at-ultra-low-power-and-able-to-make-dfu-over-the-air-from-reader-central" /><item><title>RE: Invisible beacon (Peripheral) at Ultra low power and able to make DFU over the air from Reader (Central)</title><link>https://devzone.nordicsemi.com/thread/126310?ContentTypeID=1</link><pubDate>Wed, 28 Mar 2018 11:42:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a51d2033-8bdf-49c6-b80c-d2755ce76e74</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For new application we suggest you to start your development with nRF52 series. nRF51 is older and we stopped development of any new feature with this series. The nRF52810 has very similar price range to nRF51 and offer much better features and lower power consumption.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;1. Bluetooth Advertising is public and can be scanned by any BLE device. So it&amp;#39;s not possible to make your beacon packet visible to your scanner but not other BLE scanner. What you can do is to encrypt your data and use resolvable address (address that &amp;#39;s regenerate periodically) to protect your privacy. You can consider using EID with EddyStone ,have a look &lt;a href="https://developers.google.com/beacons/eddystone-eid"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;2. Yes, it&amp;#39;s practical. We had seen our customer made their beacons with 10 years battery life. It&amp;#39;s just how big the battery can be :) You can calculate your power consumption base on the interval &lt;a href="https://devzone.nordicsemi.com/power/"&gt;here&lt;/a&gt;. A 2450/2477 coincell battery with 600mAh/1000mAh should be enough for your application to last 3 year+ with 1 second interval.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;3. You would need to advertise not only in beacon mode but also in normal mode once in a while to wait for the command to tell your device to enter DFU mode. This will result of little bit more power consumption.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>