<?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>serial example with Instaburst (extended advertising)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/60160/serial-example-with-instaburst-extended-advertising</link><description>I turn on the Instaburst feature already , after that , I program serial example to 2 nRF52832 and run it with interactive_pyaci 
 when i try to do PacketSend with 20 bytes payload , it advertise with 2 segment in data channel 
 how can i send more payload</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 19 May 2020 13:18:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/60160/serial-example-with-instaburst-extended-advertising" /><item><title>RE: serial example with Instaburst (extended advertising)</title><link>https://devzone.nordicsemi.com/thread/250747?ContentTypeID=1</link><pubDate>Tue, 19 May 2020 13:18:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0b368011-9534-4316-a7eb-52c517744507</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Instaburst is a replacement for the Bearer layer in Bluetooth mesh, where multiple Network PDUs are sent each advertising interval. This way throughput increases (by the ability to send more Network packets per time interval.)&lt;/p&gt;
&lt;p&gt;However, the rest of the stack is not changed by introducing the Instaburst bearer layer. This means Lower Transport layer PDUs are still the same size, which means segmentation and reassembly (SAR) will happen as normally. Changing PDU sizes throughout the stack requires changes in headers and in payload sizes throughout the stack and would require careful consideration regarding how many bytes are available at each layer and how many (additional) bits and bytes are needed for increased size ranges in header fields.&lt;/p&gt;
&lt;p&gt;As is, when sending e.g. a maximum Access payload of 380 bytes, this is segmented into 32 packets. Those are sent down the stack, and on the Bearer layer they are either sent one packet in each advertisement (ADV bearer) or they are sent multiple packets in the same advertisement (Instaburst bearer).&lt;/p&gt;
&lt;p&gt;For an overview of the stack and mesh network data flow, see &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v4.1.0%2Fmd_doc_user_guide_mesh_basic_architecture.html"&gt;Bluetooth Mesh stack architecture&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>