<?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>GATT CONN FAIL ESTABLISH</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11923/gatt-conn-fail-establish</link><description>Hi,
I am debugging the UART example from SDK 10 and I am using S130 Softdevice.When ever i am trying to connect the Master it gives the error as [Error 62(0x3e):GATT CONN FAIL ESTABLISH
Error 133(0x85):GATT ERROR] .I am using MCP 4.0.4 in Moto E2 and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Feb 2016 14:30:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11923/gatt-conn-fail-establish" /><item><title>RE: GATT CONN FAIL ESTABLISH</title><link>https://devzone.nordicsemi.com/thread/45164?ContentTypeID=1</link><pubDate>Mon, 22 Feb 2016 14:30:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d59edb8e-ae57-4e16-85c1-1b2af227196b</guid><dc:creator>ponlakshmi</dc:creator><description>&lt;p&gt;Currently I don&amp;#39;t have a Sniffer Trace .Once i got that i will post.Thanks for your quick reply.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GATT CONN FAIL ESTABLISH</title><link>https://devzone.nordicsemi.com/thread/45163?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2016 08:00:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2dd71d5d-c7f4-4138-a75f-9f2e04d8047e</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;I was actually wondering if you are using a development kit or some other pcb?&lt;/p&gt;
&lt;p&gt;The 32KHz source is used for protocol timing. Using the internal rc would make sure there are no issues with the timing. If you have issues with your 32KHz source you might not be able to connect as the listening window on the slave would be misplaced, thus loosing packets from the master (the first packet after the connection request is critical for the link to be established). It could also lead to problems keeping a connection and you might suffer from packet loss.&lt;/p&gt;
&lt;p&gt;Do you have a sniffer trace that shows the on air packets?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GATT CONN FAIL ESTABLISH</title><link>https://devzone.nordicsemi.com/thread/45162?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2016 04:47:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb048ddb-ac97-4f22-ba10-a9565358f842</guid><dc:creator>ponlakshmi</dc:creator><description>&lt;p&gt;I am not using whitelist.My hardware is nrf51822QFAAHO.How the performance of Rc source will affect connection and disconnection event?????&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GATT CONN FAIL ESTABLISH</title><link>https://devzone.nordicsemi.com/thread/45161?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2016 09:59:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b758d6d-e2dd-4485-a7a3-93527554a78a</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;As far as I can see the connection is not established. Which means the connection request was not received or it was ignored by the peripheral. Are you sure that you ate not using a whitelist?&lt;/p&gt;
&lt;p&gt;What hardware are you running this on? Are you sure your 32kHz rc source is ok? Consider testing the internal RC to see if this works better.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>