<?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>S132: Concurrent BT operations on multi connection implementation, large BT packets</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12772/s132-concurrent-bt-operations-on-multi-connection-implementation-large-bt-packets</link><description>Hello everybody, 
 Does the S312 v2.0.0 handle BT operations completely independent for each BT connection? Can I read/write from/to different characteristics on different BT devices at the same time? Especially when transferring large characteristics</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 25 Mar 2016 02:09:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12772/s132-concurrent-bt-operations-on-multi-connection-implementation-large-bt-packets" /><item><title>RE: S132: Concurrent BT operations on multi connection implementation, large BT packets</title><link>https://devzone.nordicsemi.com/thread/48517?ContentTypeID=1</link><pubDate>Fri, 25 Mar 2016 02:09:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f2758f0-6071-41af-b6c0-a3ca4f0ac1b0</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;The softdevice handles all the details of all connections, all reads, all writes and does it all transparently. It schedules all buffer transfers into the available radio slots and ensures everything gets some radio time when it needs it, prioritising as necessary. So just use it.&lt;/p&gt;
&lt;p&gt;Nope - 23 bytes is still the max with all the nordic softdevices. BTLE has always supported MTUs bigger than 23 bytes, but implementations are not required to do so and that is still the case with the latest BTLE spec.&lt;/p&gt;
&lt;p&gt;If you look at the code you&amp;#39;ll see the two handlers you mention are called from the same interrupt, or put into the scheduler queue from the same interrupt, so no they don&amp;#39;t interrupt each other.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>