<?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>How to speed up NRF52832 mesh data</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64236/how-to-speed-up-nrf52832-mesh-data</link><description>Dear Nordic. 
 We are using NRF52832. According to Mesh spec, It can send up to 380 bytes, So I sent Mesh Data(PAYLOAD) up to 380 bytes. It was successful, but the data was too slow. It took about 3 seconds. 
 I found that it doesn&amp;#39;t take long if the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 03 Aug 2020 08:25:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64236/how-to-speed-up-nrf52832-mesh-data" /><item><title>RE: How to speed up NRF52832 mesh data</title><link>https://devzone.nordicsemi.com/thread/262716?ContentTypeID=1</link><pubDate>Mon, 03 Aug 2020 08:25:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1a8d199-9597-472d-b1f8-e04343aab6b2</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Sorry about the late reply, but I had to wait for a reply from one of our Mesh experts before getting back to you.&lt;/p&gt;
&lt;p&gt;First off, in order to send data as fast as possible, you can send the next message straight away after getting the &lt;strong&gt;nrf_mesh_evt_tx_complete&lt;/strong&gt; event. Mesh is not very well designed for large amounts of data transfers at a time, so by decreasing the amount of data you send to 11&amp;nbsp; bytes at a time, you should be able to increase the throughput somewhat as well.&lt;/p&gt;
&lt;p&gt;Alternatively, you can check out our &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v4.2.0%2Fmd_doc_user_guide_modules_instaburst.html&amp;amp;"&gt;Nordic Advertiser Extension (Instaburst)&lt;/a&gt; which is a drop-in replacement for the standard BLE Advertiser bearer for the mesh network. When enabled, all communication will happen through Instaburst instead of regular advertisers, yielding higher throughput, but breaking compatibility with some other Bluetooth Mesh implementations.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to speed up NRF52832 mesh data</title><link>https://devzone.nordicsemi.com/thread/262076?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2020 23:19:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7ea9962f-6437-4f92-9665-066ed0a545ed</guid><dc:creator>skago2862</dc:creator><description>&lt;p&gt;Dear Simonr.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;See below for our environment.&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;1. Two NRF52832 -Development Kits(server,client)&lt;/span&gt;&lt;br /&gt;&lt;span&gt;2. Measurements at a distance of 20Cm&lt;/span&gt;&lt;br /&gt;&lt;span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span&gt;Source Reference&lt;/span&gt;&lt;br /&gt;&lt;span&gt;genic_onoff_server.c&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;static uint32_t status_send(generic_onoff_server_t * p_server,&lt;br /&gt; const access_message_rx_t * p_message,&lt;br /&gt; const generic_onoff_status_params_t * p_params)&lt;br /&gt;{&lt;/p&gt;
&lt;p&gt;generic_onoff_status_msg_pkt_t msg_pkt;&lt;br /&gt; uint8_t data[379];&lt;br /&gt; memset(data,&amp;#39;K&amp;#39;,&lt;span&gt;3&lt;/span&gt;&lt;span&gt;79&lt;/span&gt;);&lt;/p&gt;
&lt;p&gt;if (p_params-&amp;gt;present_on_off &amp;gt; GENERIC_ONOFF_MAX ||&lt;br /&gt; p_params-&amp;gt;target_on_off &amp;gt; GENERIC_ONOFF_MAX ||&lt;br /&gt; p_params-&amp;gt;remaining_time_ms &amp;gt; TRANSITION_TIME_STEP_10M_MAX)&lt;br /&gt; {&lt;br /&gt; return NRF_ERROR_INVALID_PARAM;&lt;br /&gt; }&lt;/p&gt;
&lt;p&gt;msg_pkt.present_on_off = p_params-&amp;gt;present_on_off;&lt;br /&gt; if (p_params-&amp;gt;remaining_time_ms &amp;gt; 0)&lt;br /&gt; {&lt;br /&gt; msg_pkt.target_on_off = p_params-&amp;gt;target_on_off;&lt;br /&gt; msg_pkt.remaining_time = model_transition_time_encode(p_params-&amp;gt;remaining_time_ms);&lt;br /&gt; }&lt;/p&gt;
&lt;p&gt;access_message_tx_t reply =&lt;br /&gt; {&lt;br /&gt; .opcode = ACCESS_OPCODE_SIG(GENERIC_ONOFF_OPCODE_STATUS),&lt;br /&gt; //.p_buffer = (const uint8_t *) &amp;amp;msg_pkt,&lt;br /&gt; .p_buffer = (const uint8_t *) &amp;amp;data,&lt;br /&gt; //.length = p_params-&amp;gt;remaining_time_ms &amp;gt; 0 ? GENERIC_ONOFF_STATUS_MAXLEN : GENERIC_ONOFF_STATUS_MINLEN,&lt;br /&gt; .length = strlen(data),&lt;br /&gt; .force_segmented = p_server-&amp;gt;settings.force_segmented,&lt;br /&gt; .transmic_size = p_server-&amp;gt;settings.transmic_size&lt;br /&gt; };&lt;/p&gt;
&lt;p&gt;if (p_message == NULL)&lt;br /&gt; {&lt;br /&gt; return access_model_publish(p_server-&amp;gt;model_handle, &amp;amp;reply);&lt;br /&gt; }&lt;br /&gt; else&lt;br /&gt; {&lt;br /&gt; return access_model_reply(p_server-&amp;gt;model_handle, p_message, &amp;amp;reply);&lt;br /&gt; }&lt;br /&gt;}&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Except for the above part, We didn&amp;#39;t modify it.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Please tell me how to speed up data rate.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to speed up NRF52832 mesh data</title><link>https://devzone.nordicsemi.com/thread/262005?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2020 13:38:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:57f8831c-9092-40e9-a534-be203a4ae75c</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;In our Mesh throughput tests here we&amp;#39;ve managed to get ~3.4kbps (that&amp;#39;s kbits per second) point to point. 380 bytes will result to 3040 bits, so the transmission should take ~1 second in optimal conditions, however, you haven&amp;#39;t specified how many hops your transmission is doing, etc. so depending on that, I think it should be possible to decrease the transmission time, at least somewhat depending on the testing environment.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I will need more information on your application and Mesh network in order to come with any specific advice.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>