<?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>ble nus central disconnect immediately</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/129394/ble-nus-central-disconnect-immediately</link><description>Hello, i have unexpected disconnection on a nRF54L15 SoC. The goal is to synchronise 2 nRF devices : device 1 is a nRF54L15 SoC and ble nus central software, device 2 is a nRF52832 SoC and ble NUS server software. Device 1 will scan for ble NUS services</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Oct 2026 13:25:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/129394/ble-nus-central-disconnect-immediately" /><item><title>RE: ble nus central disconnect immediately</title><link>https://devzone.nordicsemi.com/thread/572176?ContentTypeID=1</link><pubDate>Tue, 13 Oct 2026 13:25:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d405ec0b-1636-4a98-b89b-1734191eff15</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello Andre,&lt;/p&gt;
&lt;p&gt;This connection error is expected to occur occasionally, especially when other active scanners are within range (e.g., if you are scanning for LE devices in the nRF connect app on your phone), as their scan requests may overlap with your connection request PDU. The connection error is raised when the peripheral is not responding to the request. &amp;nbsp;The solution should be to simply&amp;nbsp;retry the connection.&lt;/p&gt;
&lt;p&gt;Excessive clock drift on the 32K source may also lead to this error, but then I would also expect the connection to be unstable in the cases where the connection is established successfully.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Edit to clarify: There are of course other reasons why a connection request might not be received by the peer. The connection request is only sent once per attempt. Noise&amp;nbsp;from other Wifi,BT,etc devices operating on the same frequency is another example. It is just that in my experience, nearby active scanners are typically the most common cause if you experience this connection error.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>