<?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>failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/66568/failed-to-write-on-ble-lbs-in-central</link><description>hai , 
 i am using nrf52840 sdk 15.2 and in my application i have to connect nrf52840 central to peripheral after connection i have write data on ble_lbs_led_status_send i can able to write from central to peripheral and also getting response but some</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Oct 2020 13:56:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/66568/failed-to-write-on-ble-lbs-in-central" /><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/273010?ContentTypeID=1</link><pubDate>Mon, 05 Oct 2020 13:56:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0377c1d-027f-4692-a565-3ecd9c4cd14c</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Have you tuned and verified output power and antenna matching on your hardware? This is something we can help you with, but first we need to review your schematic and layout. You can create a private case to upload your schematic and layout for feedback.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/272934?ContentTypeID=1</link><pubDate>Mon, 05 Oct 2020 10:49:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:203af711-4291-4770-83b0-80b352494655</guid><dc:creator>sowmiya</dc:creator><description>&lt;p&gt;yes, tried to reconnect and sending data after 2 to 3 retires getting success&amp;nbsp; and when central to peripheral distance at 5 meters sometimes getting failed when i retried also. on peripheral side gap connection interval is&lt;/p&gt;
&lt;p&gt;#define MIN_CONN_INTERVAL MSEC_TO_UNITS(100, UNIT_1_25_MS) /**&amp;lt; Minimum acceptable connection interval (0.5 seconds). */&lt;br /&gt;#define MAX_CONN_INTERVAL MSEC_TO_UNITS(200, UNIT_1_25_MS) /**&amp;lt; Maximum acceptable connection interval (1 second). */&lt;br /&gt;#define SLAVE_LATENCY 3 /**&amp;lt; Slave latency. */&lt;br /&gt;#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS) &amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/272610?ContentTypeID=1</link><pubDate>Thu, 01 Oct 2020 15:59:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cec3b4e8-b811-4280-827d-3be967ec5b13</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED is something you can get shortly after the central tries to establish a connection. This means that the central have sent the connection request packet, but due to noise in environment, the packet was lost, and no link was established. In such case the central should try to re-connect again, and re-send data.&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><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/272536?ContentTypeID=1</link><pubDate>Thu, 01 Oct 2020 13:01:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:254efbde-c1bb-40f8-aae0-97995a427218</guid><dc:creator>sowmiya</dc:creator><description>&lt;p&gt;NRF_CLOCK_LF_ACCURACY_20_PPM&lt;/p&gt;
&lt;p&gt;&amp;nbsp;i have noted that the disconnection&amp;nbsp;p_gap_evt-&amp;gt;params.disconnected. reason is 62 (disconnected reson is&amp;nbsp; 0x3e), i m looking whats the reason&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;thanks.&lt;/p&gt;
&lt;p&gt;sowmiya&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/272527?ContentTypeID=1</link><pubDate>Thu, 01 Oct 2020 12:44:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c05ca24-3ae4-4094-bb6f-859a176dae82</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;What LFCLK source (32kHz) are you using, and what tolerance (in ppm) have you configured when enabling the softdevice?&lt;/p&gt;
&lt;p&gt;What is the disconnect reason when receiving the disconnect event?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/272515?ContentTypeID=1</link><pubDate>Thu, 01 Oct 2020 12:20:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6a3d8d9-8d26-4350-9d6c-215e0ce8b827</guid><dc:creator>sowmiya</dc:creator><description>&lt;p&gt;thank you for your quick reply&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I have debugged on both central and peripheral&amp;nbsp; its not getting reset , dont know why its disconnecting frequently&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: failed to write on ble lbs   in central</title><link>https://devzone.nordicsemi.com/thread/272499?ContentTypeID=1</link><pubDate>Thu, 01 Oct 2020 11:26:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a63cd9c8-2b68-4d0e-a3ba-4a1dd48313eb</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;You should add debugging on the peripheral and central, are both peers experiencing a disconnect or is possible one peer doing a reset. A reset may for instance be caused by an assert, since the fault handler is by default setup to do a reset on assert to recover.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>