<?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>Any way to signal non-advertising peripheral?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10279/any-way-to-signal-non-advertising-peripheral</link><description>We have a peripheral device that we would like to have sleeping 99% of the time. I have a single timer waking it at 1-second intervals to look for things it might need to do. One of those things is seeing another device it will want to connect to over</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Nov 2015 19:02:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10279/any-way-to-signal-non-advertising-peripheral" /><item><title>RE: Any way to signal non-advertising peripheral?</title><link>https://devzone.nordicsemi.com/thread/38149?ContentTypeID=1</link><pubDate>Wed, 18 Nov 2015 19:02:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9d0de28-16bd-40f8-bece-1374cb6f9c4b</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;If you look at the power profile of an Advertisement, you see that the Rx portion is immediately after the Tx transmission.  You cannot affect this timing, other than setting the Crystal accuracy.   So you absolutely can send out an Advertisement and then go to sleep.  The &amp;quot;listening&amp;quot; portion is considered contains within that Advertisement.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Any way to signal non-advertising peripheral?</title><link>https://devzone.nordicsemi.com/thread/38148?ContentTypeID=1</link><pubDate>Wed, 18 Nov 2015 18:28:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1decb1b-a3f6-4edd-a6d9-b1774c777b14</guid><dc:creator>Lee Daniel Crocker</dc:creator><description>&lt;p&gt;But it can&amp;#39;t just send an advertising packet and go immediately to sleep, can it? Doesn&amp;#39;t it also have to listen for a response for some amount of time? Is that configurable, or it is fixed and short enough that it doesn&amp;#39;t consume much?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Any way to signal non-advertising peripheral?</title><link>https://devzone.nordicsemi.com/thread/38147?ContentTypeID=1</link><pubDate>Wed, 18 Nov 2015 10:11:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:049c485a-ec6e-44a7-9577-3e09419ba71e</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;What do you mean by a 20 ms advertisement every 2 seconds? The length of the advertisement is fixed (a advertisement package), and it is sent on all three advertisement channels each advertisement interval. The advertisement interval is configurable, from 20ms to 10.24 seconds, in steps of 0.625ms. (In addition there is a pseudo-random value from 0ms to 10ms that is automatically added.) The length of the advertisement interval is a trade-off between battery lifetime and time to detect the peripheral. Moreover you should note that the central may have a configurable scan interval and scan window, so it is difficult to be exact.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Any way to signal non-advertising peripheral?</title><link>https://devzone.nordicsemi.com/thread/38150?ContentTypeID=1</link><pubDate>Tue, 17 Nov 2015 18:31:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fea6163c-fac0-4e43-b3a6-8dac0764f0c0</guid><dc:creator>Lee Daniel Crocker</dc:creator><description>&lt;p&gt;Thanks, that&amp;#39;s kind of what I assumed. I have other gadgets on the board, so I won&amp;#39;r get your battery life numbers, but it&amp;#39;s good to hear that it can be done. If I do, say, a 20ms advertisement every 2 seconds, is that likely to be caught by device scanning for, say, 10 sec?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Any way to signal non-advertising peripheral?</title><link>https://devzone.nordicsemi.com/thread/38146?ContentTypeID=1</link><pubDate>Tue, 17 Nov 2015 03:44:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1e06a09-6167-4669-ace9-ba1f6100f9e0</guid><dc:creator>Dave_couling</dc:creator><description>&lt;p&gt;This is not possible.  Once the device is asleep it can be awoken from a GPIO or a timer.  You cannot trigger from an RF event if you are not using the radio.  Its akin to not being able to see when you close you&amp;#39;r eyes.   Can&amp;#39;t you simply have a longer interval?   Advertising at 1.8second intervals would allow a CR2032 to last 479days.&lt;/p&gt;
&lt;p&gt;Also operating as a Central will consume more power than operating as peripheral.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>