<?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>pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55099/pc-ble-driver-py-multi-peripheral-problem</link><description>Hi. 
 I&amp;#39;m testing multi peripheral using pc-ble-driver-py. 
 I tested one peripheral device using heart_rate_collector.py. 
 It was ok. 
 But, when I try connecting two peripheral device in one central device, I got exception: Failed to ble_gap_connect</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 06 Dec 2019 00:22:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55099/pc-ble-driver-py-multi-peripheral-problem" /><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/224044?ContentTypeID=1</link><pubDate>Fri, 06 Dec 2019 00:22:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50bcae68-8fa6-43a1-868d-34078cd7fd58</guid><dc:creator>Youngjun</dc:creator><description>&lt;p&gt;Thanks Kenneth.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223924?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 13:38:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:38b01f64-41f2-4e17-b6e5-cebde61d3dd5</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Try to add before ble_enable():&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;gap_cfg = BLEConfigConnGap()
gap_cfg.conn_count = 2
self.adapter.driver.ble_cfg_set(BLEConfig.conn_gap, gap_cfg) &lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223843?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 10:34:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6dd5ba52-1722-4bb7-a856-0afb77223d9f</guid><dc:creator>Youngjun</dc:creator><description>&lt;p&gt;Ok. I understand.&lt;/p&gt;
&lt;p&gt;I Checked heart_rate_collector.py example.&lt;/p&gt;
&lt;p&gt;In open() method, I can change central_conn_count when i use nRF51.&lt;/p&gt;
&lt;p&gt;But, my central device is nRF52 and nrf_sd_ble_api_ver is 5.&lt;/p&gt;
&lt;p&gt;Is it possible to change central connection count using nRF52(nrf_sd_ble_api_ver 5)?&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;
    def open(self):
        self.adapter.driver.open()
        if config.__conn_ic_id__ == &amp;quot;NRF51&amp;quot;:
            self.adapter.driver.ble_enable(
                BLEEnableParams(
                    vs_uuid_count=1,
                    service_changed=0,
                    periph_conn_count=0,
                    central_conn_count=1,
                    central_sec_count=0,
                )
            )
        elif config.__conn_ic_id__ == &amp;quot;NRF52&amp;quot;:
            gatt_cfg = BLEConfigConnGatt()
            gatt_cfg.att_mtu = self.adapter.default_mtu
            gatt_cfg.tag = CFG_TAG
            self.adapter.driver.ble_cfg_set(BLEConfig.conn_gatt, gatt_cfg)

            self.adapter.driver.ble_enable()&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223782?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 08:12:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4db61e4-e0c7-4a80-a661-d5c6e2859d16</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;No need to change firmware or driver. You should only need to increment &amp;#39;&lt;span&gt;central_conn_count&amp;#39; in your source code.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223745?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 04:06:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd01d0ff-543f-40b2-8c79-8f8e3553b222</guid><dc:creator>Youngjun</dc:creator><description>&lt;p&gt;Ok.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m using pc-ble-driver-py(0.12.0) and connectivity_4.1.1 s132_5.1.0.hex file.&lt;/p&gt;
&lt;p&gt;When i test multi peripheral using heart_rate_collector.py example, i got error code 18.&lt;/p&gt;
&lt;p&gt;So, i thought i had to modify the central firmware code.&lt;/p&gt;
&lt;p&gt;Is it possible to connect multi peripheral just modifying heart_rate_collector.py?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223607?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2019 13:16:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9eb6a91-6a36-4af4-99a3-145e7330f3d4</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;The connectivity.hex files are already delivered pre-compiled for each release. It is possible to build the connectivity.hex files, however it is not straight forward, and I am not sure why you would want to do so. If you still want to build them, you can find a description here on how to compile pc-ble-driver from source:&lt;br /&gt;&lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver/#compiling-connectivity-hex-files"&gt;https://github.com/NordicSemiconductor/pc-ble-driver/#compiling-connectivity-hex-files&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;[Recommended:] If you don&amp;#39;t want to build your own connectivity.hex files, but use the pre-compiled hex files, then you can find an overview of releases here:&lt;br /&gt;&lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver-py/releases"&gt;https://github.com/NordicSemiconductor/pc-ble-driver-py/releases&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;To install the latest release see:&lt;br /&gt;&lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver-py#installing-from-pypi"&gt;https://github.com/NordicSemiconductor/pc-ble-driver-py#installing-from-pypi&lt;/a&gt;&amp;nbsp;&lt;br /&gt;&lt;span&gt;Example: pip install pc-ble-driver-py&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;After installation you can find pre-compiled connectivity.hex files in the following path (actual connectivity.hex files will depend on the release you have installed):&lt;br /&gt;&amp;lt;your python install path&amp;gt;\Lib\site-packages\pc_ble_driver_py\hex&lt;/p&gt;
&lt;p&gt;The latest release (as of 4th Dec 19) support nRF51 S130 v2 (nRF51822) and nRF52 S132 v5 (nRF52832 and nRF52840).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223447?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2019 00:21:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d9d57e44-b9e2-4206-95fe-e045a0abb8fb</guid><dc:creator>Youngjun</dc:creator><description>&lt;p&gt;Hi, Kenneth&lt;/p&gt;
&lt;p&gt;Thanks for replying.&lt;/p&gt;
&lt;p&gt;Can i modify connectivity.hex file in pc-ble-driver-py?&lt;/p&gt;
&lt;p&gt;Or, Can i use central example(in SDK folder) with pc-ble-driver?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py multi peripheral problem</title><link>https://devzone.nordicsemi.com/thread/223046?ContentTypeID=1</link><pubDate>Mon, 02 Dec 2019 12:48:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e8cde02-dfb5-495d-8d27-3e45cdccc4cb</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;From:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_p___f_u_n_c_t_i_o_n_s.html#gacca0e56084c7b3ed832b1bfa3911b7fe"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_p___f_u_n_c_t_i_o_n_s.html#gacca0e56084c7b3ed832b1bfa3911b7fe&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I can see that 18 =&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group__nrf__error.html#ga5fc58fcfed7097d1205c96acb5a66ab8"&gt;NRF_ERROR_CONN_COUNT&lt;/a&gt;&lt;span&gt;&amp;nbsp;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I assume you need to change &amp;#39;central_conn_count&amp;#39; to something more than 1?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;br /&gt;Kenneth&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>