<?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>Gazell bi-directional communication between paired devices</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/32865/gazell-bi-directional-communication-between-paired-devices</link><description>Hello, 
 We are developing a system in which a device controls a host and the device should receive status information about the host. In some use cases multiple hosts are in close proximity, so pairing is required to avoid incorrect behavior. 
 We have</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Apr 2018 13:29:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/32865/gazell-bi-directional-communication-between-paired-devices" /><item><title>RE: Gazell bi-directional communication between paired devices</title><link>https://devzone.nordicsemi.com/thread/127852?ContentTypeID=1</link><pubDate>Wed, 11 Apr 2018 13:29:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c972687-792b-4b14-a8fc-dfe446e83e0e</guid><dc:creator>DonaldInspiro</dc:creator><description>&lt;p&gt;Thank you for your answer. We had seen both hosts react to a message, but this was due to incorrect initialization of gazell pairing (not calling gzp_init) which caused all hosts and devices to use the same addresses.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazell bi-directional communication between paired devices</title><link>https://devzone.nordicsemi.com/thread/126981?ContentTypeID=1</link><pubDate>Thu, 05 Apr 2018 08:35:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de6b1c44-28de-481c-a59b-c37ea970bacd</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When using the encrypted pipe (pipe 1), gazell will claim the ACK payload for AES counter updates.&lt;/p&gt;
&lt;p&gt;You might get some data on the reverse from time-to-time (it&amp;#39;ll look very unstable, and you&amp;#39;ll see &amp;quot;garbage&amp;quot; values), but once the host receives data on encrypted pipe&amp;nbsp;1, it will flush the FIFO in order to ensure that the crypto-related data is sent back to the device.&lt;/p&gt;
&lt;p&gt;In the case you are pairing a device to a specific host, and there are several hosts in close proximity, we recommend that you turn down the transmit power on both device and host, and on the host side, check if the &amp;quot;RPD&amp;quot; field (the &amp;quot;1 bit RSSI&amp;quot;, detects if power level higher than -64 dBm) when initiating a pairing request.&lt;/p&gt;
&lt;p&gt;Once a device is successfully paired, the base RF address for communication will be changed (&amp;quot;system address&amp;quot; as it&amp;#39;s called in GZP), and each host will have its own random generated RF base address.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>