<?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 pairing how to add payload to the acknowledgement</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10608/gazell-pairing-how-to-add-payload-to-the-acknowledgement</link><description>Hi
I did not quit yet understand the Gazell Pairing library. 
 If an encrypted message is send, how do I add some payload to the acknowledgement.
And how will I be able to read this payload from the acknowledgement? 
 What is the maximum size of the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Dec 2015 13:30:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10608/gazell-pairing-how-to-add-payload-to-the-acknowledgement" /><item><title>RE: Gazell pairing how to add payload to the acknowledgement</title><link>https://devzone.nordicsemi.com/thread/39530?ContentTypeID=1</link><pubDate>Mon, 07 Dec 2015 13:30:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1986379e-be25-453d-b701-041b6163bebe</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Q1: Unfortunately, when using the encrypted pipe 1 with GZP, it will consume the ACK payload for key exchange. You will not be able to use ACK_PAYLOAD when an encrypted pipe is in use with GZP, as it will flush the TXFIFO to ensure there&amp;#39;s space in the FIFO for doing the key update.&lt;/p&gt;
&lt;p&gt;Q2: With Gazell you can send 32 bytes payload over-the-air, both in forward and reverse (ie: in the ACK-payload).&lt;/p&gt;
&lt;p&gt;Q3: Only one encrypted pipe is supported with GZP. This means that other devices connected to the same host must use an unencrypted RF pipe for communicating.
If you have the same configuration on the third device, it will try to pair with the host, and it will not spam due to the pairing sequence (there&amp;#39;s loads of delays in there) if it fails to pair up properly.&lt;/p&gt;
&lt;p&gt;Cheers,
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>