<?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>ble mesh</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62345/ble-mesh</link><description>HI , 
 We use official hardware and software to develop mesh products. Taking light_server as an example, the test is as follows: Hardware: nRF52840-DK Software: nrf5_SDK_for_Mesh_v4.1.0_src nRF5_SDK_16.0.0_98a08e2 
 In the process of debugging the example</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Jun 2020 13:52:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62345/ble-mesh" /><item><title>RE: ble mesh</title><link>https://devzone.nordicsemi.com/thread/254066?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2020 13:52:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf53d991-bdce-4ea0-a122-4d50af796c60</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Zhao,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you give an example of how long it would take to scan and connect to the device ?&amp;nbsp;&lt;br /&gt;There could be a chance that the phone doesn&amp;#39;t do scanning very often, increasing the time it take to&amp;nbsp;establish a connection.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You can&amp;nbsp;reduce&amp;nbsp;the advertising interval , to make the mesh node advertise more often. This will improve the time it take to get connected. However the draw back is that it will affect the mesh performance (because the radio can&amp;#39;t do two things at a time)&lt;br /&gt;&lt;br /&gt;To increase the rate of advertising packet you can modify the following configuration in nrf_mesh_config_core.h:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;-&amp;nbsp;MESH_GATT_PROXY_NETWORK_ID_ADV_INT_MS : this is by default set at 2 seconds. Please try to test changing it down to 200 ms or 500ms.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;-&amp;nbsp;NRF_MESH_PROV_BEARER_GATT_UNPROV_BEACON_INTERVAL_MS: this is the advertising before the node provisioned to the network. By default it&amp;#39;s 200ms, you can try to change it down to 100ms&amp;nbsp;&lt;/p&gt;
&lt;p&gt;-&amp;nbsp;MESH_GATT_PROXY_NODE_IDENTITY_ADV_INT_MS: this is the advertising right after provisioning, before configuration. By default it&amp;#39;s 200ms, but you can reduce it to 100ms or less.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When you flash the application again, you have to make sure you do erase all before you flash the application. Otherwise the flash manager&amp;nbsp;can be confused.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>