<?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>SD130 Packet per interval as central</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12216/sd130-packet-per-interval-as-central</link><description>Hi, 
 I&amp;#39;ve been trying to send a batch of data from 2 nRF51-DK boards, peripheral to central, and it seemed that there is a bottleneck on BLE since the buffer on the peripheral side continuously overflows. I have read that on SD120 a central device is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Mar 2016 12:09:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12216/sd130-packet-per-interval-as-central" /><item><title>RE: SD130 Packet per interval as central</title><link>https://devzone.nordicsemi.com/thread/46220?ContentTypeID=1</link><pubDate>Tue, 01 Mar 2016 12:09:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de7b6e7c-0fa3-4834-879f-2c39a8b1d72f</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;The latest version of S130, S130 v.2.0.0, should support up to 6 packets per connection interval when being a central.
I would assume that 6 packets per connection interval only is possible to achieve when the S130 device is acting a central only, and with only one peripheral connected.&lt;/p&gt;
&lt;p&gt;When the softdevice specification for S130 v.2.0 has been released, it will be possible to find this information there.&lt;/p&gt;
&lt;p&gt;In order to achieve the maximum bandwidth, the softdevice will have to be configured that way, see release notes:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The API to configure the bandwidth of BLE connections is now functional. The application can configure the bandwidth of
BLE connections with the BLE_OPT_CONN_BW_SET option before the BLE connection is established (DRGN-6468). When
using the configurable bandwidth option the application must have specified beforehand, at BLE stack initialization time, a
set of connection bandwidth that includes the ones that it intends to use through this option. The sd_ble_gap_connect()
and sd_ble_gap_adv_start() SV calls can now return NRF_ERROR_NO_MEM if there is not enough memory to honor the
requested bandwidth configuration.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The S130 v.2.0 API is not out on the infocenter yet, however it should be done the same way as for S132:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Use  &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v2.0.0%2Fgroup___b_l_e___c_o_m_m_o_n___f_u_n_c_t_i_o_n_s.html&amp;amp;cp=1_3_0_1_0_2_0_0_0_3_3&amp;amp;anchor=ga511d431bc3d9ccf9bef09ad20cbf855a"&gt;sd_ble_opt_set(..)&lt;/a&gt; to set the bandwidth configuration.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The bandwidth configuration struct can be found &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v2.0.0%2Fstructble__opt__conn__bw__t.html"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>