<?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>Is the amount of connections limited by spec, chip or stack?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12474/is-the-amount-of-connections-limited-by-spec-chip-or-stack</link><description>I would like to know whether the amount of connections for BLE is limited by BLE spec, chip or stack (soft device)? 
 Also, same question regarding the possibility of the central to perform scanning while being connected to one or more peripherals. Is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 10 Mar 2016 10:19:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12474/is-the-amount-of-connections-limited-by-spec-chip-or-stack" /><item><title>RE: Is the amount of connections limited by spec, chip or stack?</title><link>https://devzone.nordicsemi.com/thread/47244?ContentTypeID=1</link><pubDate>Thu, 10 Mar 2016 10:19:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89669e64-1e76-4cc3-867e-236be29a728f</guid><dc:creator>Anders Strand</dc:creator><description>&lt;p&gt;Hello.&lt;/p&gt;
&lt;p&gt;On our BLE devices, the stack (softdevice) is the limiting factor for number of connections. The limits in the stack are linked to the amount of memory and flash, so one could argue that the chip is the limiting factor, albeit indirectly :)&lt;/p&gt;
&lt;p&gt;The softdevice (stack) is also the limiting factor when is comes to concurrently filling many BLE roles (peripheral,central, observer,scanner).&lt;/p&gt;
&lt;p&gt;Our S130 softdevice is able to have a maximum amount of connections, while both scanning and advertising. All these activities use the radio, so the internal scheduling will split the time between them. A scanner running concurrently with 8 connections, will not be able to scan 100% of the time, but rather in the time in between the connection events.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>