<?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>Bluetooth 5 retransmission on NRF52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/35574/bluetooth-5-retransmission-on-nrf52832</link><description>hi all, 
 Our application is a peripheral device with sensor data that is sending up to 540kb/s (68kB/s) to the central device (data rate could probably be reduced if necessary). A 5k and a 10k buffer are ready to transmit every 250ms and each of those</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Jun 2018 14:50:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/35574/bluetooth-5-retransmission-on-nrf52832" /><item><title>RE: Bluetooth 5 retransmission on NRF52832</title><link>https://devzone.nordicsemi.com/thread/137140?ContentTypeID=1</link><pubDate>Thu, 21 Jun 2018 14:50:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7cdb8633-848d-4ae7-a581-70ecf8024622</guid><dc:creator>ilw</dc:creator><description>&lt;p&gt;Thanks for clarifying so quickly, it sounds like i just got lost in the 3k page standard...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth 5 retransmission on NRF52832</title><link>https://devzone.nordicsemi.com/thread/136899?ContentTypeID=1</link><pubDate>Wed, 20 Jun 2018 12:21:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae686280-f578-4c41-b411-10d7c28ce8ee</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Ian,&lt;/p&gt;
&lt;p&gt;For the ATT (GATT/GAP) case, there is really no reason for using indication. There is anyway retransmission of the link layer, so you know that the data will make it to the peer eventually (unless there is a connection supervision timeout).&lt;/p&gt;
&lt;p&gt;Support for L2CAP Connection-Oriented Channels was introduced with S132 version 5.0.0,&amp;nbsp;but it&amp;nbsp;is quite limited, supporting only LE Credit Based Flow Control Mode. See&amp;nbsp;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/group___b_l_e___l2_c_a_p.html?cp=2_3_1_1_0_2_5"&gt;Logical Link Control and Adaptation Protocol (L2CAP) API documentation&lt;/a&gt;&amp;nbsp;for details. There is no support for streaming etc.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>