<?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>How to identify the peripheral in Multilink central link ?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/79914/how-to-identify-the-peripheral-in-multilink-central-link</link><description>I have connected 3 Peripheral using Name Filters and 1 central. 
 I am able to connect and communicate with all correctly. 
 But I need to identify that conn_handle 0x0 , 0x1 and 0x2 is connected to respected which peripheral ? 
 I am trying on Standard</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Sep 2021 14:13:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/79914/how-to-identify-the-peripheral-in-multilink-central-link" /><item><title>RE: How to identify the peripheral in Multilink central link ?</title><link>https://devzone.nordicsemi.com/thread/330891?ContentTypeID=1</link><pubDate>Thu, 23 Sep 2021 14:13:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e837fd57-ba87-4846-a17f-1b0d5d2ed2c8</guid><dc:creator>Vipul2988</dc:creator><description>&lt;p&gt;Awesome. that will work.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you..!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to identify the peripheral in Multilink central link ?</title><link>https://devzone.nordicsemi.com/thread/330889?ContentTypeID=1</link><pubDate>Thu, 23 Sep 2021 14:11:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b6cd0b8e-f2d5-46ea-a230-fe23d0f2505e</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Yes, I found this approach in the &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.1.0%2Fble_sdk_app_rscs_relay.html"&gt;Experimental: BLE Relay Example&lt;/a&gt;, which attaches to one Heart Rate Service and one Running Speed and Cadence Service. It stores in main.c the handles as m_conn_handle_hrs_c and m_conn_handle_rscs_c. That way it keeps track of which connected peripheral is which.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to identify the peripheral in Multilink central link ?</title><link>https://devzone.nordicsemi.com/thread/330877?ContentTypeID=1</link><pubDate>Thu, 23 Sep 2021 13:27:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab62fbbe-dd3c-48ad-94a5-24e663cad254</guid><dc:creator>Vipul2988</dc:creator><description>&lt;p&gt;Is there any standard example in SDK use same thing ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to identify the peripheral in Multilink central link ?</title><link>https://devzone.nordicsemi.com/thread/330876?ContentTypeID=1</link><pubDate>Thu, 23 Sep 2021 13:25:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53e5e770-dd99-47d3-a4b3-92ac4a4a51d6</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You should store this mapping yourself in the application. For instance on the BLE_GAP_EVT_CONNECTED event. You then have to use the mapping (both ways) whenever you get an event from a handle or want to send something to a given device. Remember to remove the mapping on disconnect.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>