<?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>Message synchronization with no connection</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42623/message-synchronization-with-no-connection</link><description>Hello, 
 We are working on a network of low energy sensors that work without connection. The sensors have a configurable service, so from time to time it makes itself available for new configuration of the service that it is running. Based only on advertisements</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 21 Jan 2019 16:01:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42623/message-synchronization-with-no-connection" /><item><title>RE: Message synchronization with no connection</title><link>https://devzone.nordicsemi.com/thread/166943?ContentTypeID=1</link><pubDate>Mon, 21 Jan 2019 16:01:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9d0ed8b2-5603-46d2-9d0d-3c0a9baed133</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The scan request/response mechanism is not really designed for message synchronization in mind. Also note that all active scanners will generally request the scan response packet. So both sensor and network node need to know each other&amp;rsquo;s BLE address, to filter out other scanners. And you will need to add the network-node BLE address in the sensor whitelist, so that only the network-node will trigger the sensor to send a&amp;nbsp;&lt;span&gt;scan_response.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;1)&amp;nbsp;&lt;/span&gt;&lt;span&gt;No. The SoftDevice will send the application the BLE events asynchronous, and also note that&amp;nbsp;the real advertising interval is adv_interval + advDelay, where advDelay is a pseudo-random value with a range of 0 ms to 10 ms generated by the Link Layer for each advertising event. So you should just enable the scanner with a given scan interval and window, and wait for the network node to send the configuration ADV packet, and the sensor to receive it. If you have not received&amp;nbsp;it within a couple of seconds, you could turn the scanner off and restart the procedure.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2)&amp;nbsp;The SoftDevice handles this for you. The 3 advertising channels(37,38,39) will be used.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;3) It could work, but it will depend on your implementation&amp;nbsp;on how&amp;nbsp;robust it will be. I think it would be a lot more robust to connect to the sensor devices. The network node could keep a list of all senors, and when it wants to configure them, it could&amp;nbsp;iteratively connect to the sensors and configure them. &lt;/span&gt;If you have alot of sensor devices, it could also be worth checking out &lt;a href="https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK-for-Mesh"&gt;Bluetooth Mesh &lt;/a&gt;for this type of sensor network.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>