<?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 Scalability</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34938/ble-mesh-scalability</link><description>Hi! 
 We are experimenting with BLE Mesh on nRF52832. 
 Our setup includes around 50 sensors located in a building which need to report sensor data ( 12 bytes ) in real time, at a rate of about 10 ms. 
 What we tried so far is to modify the Light Switch</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 May 2018 22:38:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34938/ble-mesh-scalability" /><item><title>RE: BLE Mesh Scalability</title><link>https://devzone.nordicsemi.com/thread/134095?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 22:38:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9c57a17-3a9e-4310-a955-b5dc0f51fb37</guid><dc:creator>leonwj</dc:creator><description>&lt;p&gt;hello,&lt;/p&gt;
&lt;p&gt;(1) It would be great to know which version of Mesh SDK you&amp;#39;re running on&lt;/p&gt;
&lt;p&gt;(2) Can you document the errors you are getting and/or post the error log is a response&lt;/p&gt;
&lt;p&gt;(3) Based upon the numbers you provided above, you are pushing ~60KB of data across the mesh every second (50 &lt;em&gt;sensors&lt;/em&gt; x 12 &lt;em&gt;bytes&lt;/em&gt; x 100 &lt;em&gt;intervals&lt;/em&gt;). The SIG&amp;nbsp;mesh spec limits each node to 24 Hz (as confirmed within the Nordic nRF5 Mesh&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v2.0.1%2Fmd_doc_introduction_mesh_hw_resources.html&amp;amp;cp=4_1_0_0_3" rel="noopener noreferrer" target="_blank"&gt;resource usage&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;page - see the &lt;em&gt;MSG_PER_SEC&lt;/em&gt;&amp;nbsp;per node constraint). &lt;em&gt;Can you not ensure that sensors only&amp;nbsp;publish&amp;nbsp;measurements if/when their value has changed or changed beyond a key variance/threshold? &lt;/em&gt;Alternatively, you could investigate the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v2.0.1/md_doc_libraries_instaburst.html?cp=4_1_0_1_2" rel="noopener noreferrer" target="_blank"&gt;Nordic Instaburst&lt;/a&gt; feature to see if that meets your throughput needs.&lt;/p&gt;
&lt;p&gt;(4) The following &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/31148/need-help-to-improve-bluetooth-mesh-throughput/124389#124389" rel="noopener noreferrer" target="_blank"&gt;link&lt;/a&gt; may provide you with some additional insight (especially on throughput and segmentation (SAR))&lt;/p&gt;
&lt;p&gt;In any case, the above are just some basic observations, post back once you have the additional details to share.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>