<?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>What is a good way to identify paired devices with Gazell?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117212/what-is-a-good-way-to-identify-paired-devices-with-gazell</link><description>I am developing a USB dongle (nRF52833) for computers and a controller (nRF52833). As a basic configuration, multiple controllers need to be connected to one dongle. Multiple controllers will send data to the dongle at the same time. 
 Is there a good</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 12 Dec 2024 02:03:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117212/what-is-a-good-way-to-identify-paired-devices-with-gazell" /><item><title>RE: What is a good way to identify paired devices with Gazell?</title><link>https://devzone.nordicsemi.com/thread/514629?ContentTypeID=1</link><pubDate>Thu, 12 Dec 2024 02:03:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d8d0437-e4af-4947-8b2b-e48fbf85f9f8</guid><dc:creator>DX_HK</dc:creator><description>&lt;p&gt;Thanks for your response.&lt;br /&gt;Very clear.&lt;br /&gt;I will implement an application for individual identification.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is a good way to identify paired devices with Gazell?</title><link>https://devzone.nordicsemi.com/thread/514590?ContentTypeID=1</link><pubDate>Wed, 11 Dec 2024 16:18:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e36abae2-8571-4b19-b226-96cbf6258cea</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Historically gazell have been used for HID devices, where each pipe have been assigned for a specific purpose, e.g.:&lt;/p&gt;
&lt;p&gt;pipe 0 - pairing&lt;/p&gt;
&lt;p&gt;pipe 1 (synchronous) - mouse&lt;/p&gt;
&lt;p&gt;pipe 2 (asynchronous) - keyboard&lt;/p&gt;
&lt;p&gt;pipe 3-5 - other type of hid devices&lt;/p&gt;
&lt;p&gt;So theoretically you could have for instance several keyboard using pipe2, but gazell did not need to differentiate them, so there is no way to identify which type of mouse or keyboard that was at any time using the various pipes.&lt;/p&gt;
&lt;p&gt;If you need to differentiate them the easiest may simply be to add a random number in each packet sent from the controller-&amp;gt;host, the random number is unique for each &amp;quot;controller&amp;quot;. Such that when controller 1 send data, the first (or last) 2-4 bytes random unique number for the specific controller. This must be added by the application.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>