<?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>Unable to connect</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46511/unable-to-connect</link><description>Using the latest version of Bluetooth low energy (V2.2.1) running on nRF Connect V2.6.2 I was never able to connect to a peripheral device. 
 The peripheral devices are based on the TI&amp;#39;s CC2642 chip and running the example Simple BLE Peripheral project</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Apr 2019 14:16:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46511/unable-to-connect" /><item><title>RE: Unable to connect</title><link>https://devzone.nordicsemi.com/thread/183535?ContentTypeID=1</link><pubDate>Wed, 24 Apr 2019 14:16:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3e85de7-9b23-47fe-8677-f70434eb968a</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There are typically 2 reasons why&amp;nbsp;&lt;span&gt;B&lt;/span&gt;&lt;span&gt;LE_HCI_CONN_FAILED_TO_BE_ESTABLISHED may occur:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;1. There is noise in the environment that cause the connection request packet to be lost, this may occur from time to time (e.g. 1-5%) depending on other 2.4GHz traffic, but not all the time no.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;2. The peripheral you want to connect to have enabled whitelist to prevent new central devices to connect and bond, in such case you may need to put the peripheral device in a pairing mode by following the manufacturer description.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Can any of the above be the case here?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If not, then an on-air sniffer log with working and failing situation (e.g old and new software) could be useful:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;a href="https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer"&gt;https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Connect-for-desktop/Download#infotabs"&gt;https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Connect-for-desktop/Download#infotabs&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>