<?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>Synchronize Central Connection Attempts with Known, but Slow, Peripheral Advertising Interval</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64429/synchronize-central-connection-attempts-with-known-but-slow-peripheral-advertising-interval</link><description>Hello, 
 I have a system composed of one central that needs to 1) briefly connect to many (100+) peripherals, 2) download a small amount of data from each, and then 3) disconnect. At the moment, the peripheral devices advertise with a 1 second interval</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 02 Aug 2020 07:52:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64429/synchronize-central-connection-attempts-with-known-but-slow-peripheral-advertising-interval" /><item><title>RE: Synchronize Central Connection Attempts with Known, but Slow, Peripheral Advertising Interval</title><link>https://devzone.nordicsemi.com/thread/262671?ContentTypeID=1</link><pubDate>Sun, 02 Aug 2020 07:52:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46a4608d-d194-4cc6-a93d-16532f512231</guid><dc:creator>Dmitry</dc:creator><description>&lt;p&gt;Hi Kyle,&lt;/p&gt;
[quote userid="3119" url="~/f/nordic-q-a/64429/synchronize-central-connection-attempts-with-known-but-slow-peripheral-advertising-interval"]My reading of the S140 documentation regarding &amp;quot;initiator timing&amp;quot; leads me to believe that if I call sd_ble_gap_connect() immediately after seeing an advertisement that SoftDevice will do nothing until the connection is established or the connection timeout occurs.&amp;nbsp; Is this a correct interpretation?[/quote]
&lt;p&gt;Yes, it will scan for advertising packets from connection target(s), also serve all established connections at the same time.&lt;/p&gt;
[quote userid="3119" url="~/f/nordic-q-a/64429/synchronize-central-connection-attempts-with-known-but-slow-peripheral-advertising-interval"]Instead of wasting this time between advertisements, I&amp;#39;d like the central to keep scanning for additional peripherals (and service any existing connections). Do you have recommendations for how to make this system as efficient as possible?[/quote]
&lt;p&gt;As I understood your case, you need to query each of 100+ devices once a 15 minutes. You can set a whitelist of up to 8 devices, it will connect to the first found one. From peripheral side, you can put device to 15-minute sleep right after successful connection, then wake up and advertise all the time until it&amp;#39;s found by central again, maybe increasing advertising interval after 1 minute. &lt;/p&gt;
[quote userid="3119" url="~/f/nordic-q-a/64429/synchronize-central-connection-attempts-with-known-but-slow-peripheral-advertising-interval"]Alternatively, it is possible for the peripherals to be modified to send 2-3 closely-spaced advertising events every 1 second so that sd_ble_gap_connect() could be called with a short scan timeout?[/quote]
&lt;p&gt;I didn&amp;#39;t get how this could help... Anyway, peripheral sends 3 advertising packets one-by-one on three channels (37,38,39), but you cannot know an exact time point - a random value is added to advertising interval each time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>