<?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>Which is the best proprietary stack to pair multiple Devices (single FW) to a single Host and use several systems (e.g. Host_1 with Device_1 and Host_2 with Device_2) concurrently (one within the antenna range of the other) without interferences?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27227/which-is-the-best-proprietary-stack-to-pair-multiple-devices-single-fw-to-a-single-host-and-use-several-systems-e-g-host_1-with-device_1-and-host_2-with-device_2-concurrently-one-within-the-antenna-range-of-the-other-without-</link><description>I&amp;#39;m developing a system which consists of 1 or more remotes (3 or 4 max) that have to communicate with a single host. 
 I need a fairly simple protocol, low power optimised especially from the Remote side. I already have the nRF51 Dongle (PCA10031) and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 10 Nov 2017 12:43:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27227/which-is-the-best-proprietary-stack-to-pair-multiple-devices-single-fw-to-a-single-host-and-use-several-systems-e-g-host_1-with-device_1-and-host_2-with-device_2-concurrently-one-within-the-antenna-range-of-the-other-without-" /><item><title>RE: Which is the best proprietary stack to pair multiple Devices (single FW) to a single Host and use several systems (e.g. Host_1 with Device_1 and Host_2 with Device_2) concurrently (one within the antenna range of the other) without interferences?</title><link>https://devzone.nordicsemi.com/thread/107420?ContentTypeID=1</link><pubDate>Fri, 10 Nov 2017 12:43:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d607db2-91b8-4c99-a238-68ea8b1cd9ad</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;(or not declare it as BT compliant device...)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Which is the best proprietary stack to pair multiple Devices (single FW) to a single Host and use several systems (e.g. Host_1 with Device_1 and Host_2 with Device_2) concurrently (one within the antenna range of the other) without interferences?</title><link>https://devzone.nordicsemi.com/thread/107419?ContentTypeID=1</link><pubDate>Fri, 10 Nov 2017 12:21:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d54b2034-7873-48e5-9a5d-c4c026a245a8</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Gazell was made for use in keyboard and mouse, which are very similar to a remote application. You have one device that needs to be low power (device), and you have one device that doesn&amp;#39;t have the same constraints (host), so it can be scanning all the time.&lt;/p&gt;
&lt;p&gt;The Gazell pairing library only supports one encrypted pipe, see &lt;a href="https://devzone.nordicsemi.com/question/123657/gazell-pairing-library-only-support-one-encrypted-pipe/"&gt;this&lt;/a&gt; for more information.&lt;/p&gt;
&lt;p&gt;The pipe address has to be set. What you could do is to have the host scanning on pipe 0, and have the devices transmit on pipe 0. Then the host can tell device 0 which address it should use for further communication, which address device 1 should use for further communication and so on. If you want several system to operate in close vicinity you should randomize the addresses uses.&lt;/p&gt;
&lt;p&gt;If you need more than one encrypted link BLE might be the way to go, it is suited for this kind of application, the main drawback of BLE is that you have to pay the declaration fee.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Which is the best proprietary stack to pair multiple Devices (single FW) to a single Host and use several systems (e.g. Host_1 with Device_1 and Host_2 with Device_2) concurrently (one within the antenna range of the other) without interferences?</title><link>https://devzone.nordicsemi.com/thread/107423?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 15:25:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a2b9712-bcea-43e4-817b-13a6269e6158</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Well you are asking for pairing so I assume you want to secure a link. Then you speak about multi-link (or concurrent) links. So it&amp;#39;s definitely far from &amp;quot;just sending 4 bits from point A to point B&amp;quot;...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Which is the best proprietary stack to pair multiple Devices (single FW) to a single Host and use several systems (e.g. Host_1 with Device_1 and Host_2 with Device_2) concurrently (one within the antenna range of the other) without interferences?</title><link>https://devzone.nordicsemi.com/thread/107422?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 15:21:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3874c57-d5b2-4e8e-90a3-21de2bd8d90f</guid><dc:creator>Marascalchi</dc:creator><description>&lt;p&gt;Well, it just seemed to me that these proprietary protocols were the most easy to use and since I just have to send a payload of 4 bits I thought that BLE, ANT etc were overkill. However I admit I&amp;#39;m no BLE expert so maybe it&amp;#39;s perfectly acceptable to use BLE even in this case.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Which is the best proprietary stack to pair multiple Devices (single FW) to a single Host and use several systems (e.g. Host_1 with Device_1 and Host_2 with Device_2) concurrently (one within the antenna range of the other) without interferences?</title><link>https://devzone.nordicsemi.com/thread/107421?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 15:02:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fba7a4c5-1007-4130-9d14-d501e6d934be</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;I actually do believe that BLE is the best technology for such use case... any specific reason why not use it and rather favor some proprietary protocol?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>