<?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>Where in nRF8001_PS whitepaper does it mention 1 packet per connection interval for sending?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1431/where-in-nrf8001_ps-whitepaper-does-it-mention-1-packet-per-connection-interval-for-sending</link><description>Hello, 
 I&amp;#39;m using the nRF8001, and I&amp;#39;m trying to max out the bandwidth between itself and an iPhone. The iPhone&amp;#39;s connection interval is 30ms (minimum). I&amp;#39;m sending 20 bytes of data from the nRF8001 ever 30ms in one packet. This gives me around 5.4</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Jan 2014 15:31:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1431/where-in-nrf8001_ps-whitepaper-does-it-mention-1-packet-per-connection-interval-for-sending" /><item><title>RE: Where in nRF8001_PS whitepaper does it mention 1 packet per connection interval for sending?</title><link>https://devzone.nordicsemi.com/thread/6409?ContentTypeID=1</link><pubDate>Thu, 23 Jan 2014 15:31:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1dc505be-06c6-4b8c-bdd9-6ea1fdbe39cd</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;No, it does not. However this depends on the number of credits available on the firmware build.
The current latest build seems to have 2 credits (see the ACI Device Started Event) which will allow for 1 packet per connection event in a sustained transfer and 2 in a bursty mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>