<?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 in Ant Acknowledgment message coming from the receiving node</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5440/what-is-in-ant-acknowledgment-message-coming-from-the-receiving-node</link><description>We all know we can send acknowledged data in Ant channel. 
 But based on my test. the acknowledgement message coming back to the originating device is just a dumb packet. It doesn&amp;#39;t include a hash code or message id to identify what it is acknowledging</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Feb 2015 16:58:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5440/what-is-in-ant-acknowledgment-message-coming-from-the-receiving-node" /><item><title>RE: What is in Ant Acknowledgment message coming from the receiving node</title><link>https://devzone.nordicsemi.com/thread/19001?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2015 16:58:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba52ebd0-532f-43aa-abfd-202d6edc573f</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;Not unless you use payload in the ACK. Then you could is that payload to identify which of them that actually ACKed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is in Ant Acknowledgment message coming from the receiving node</title><link>https://devzone.nordicsemi.com/thread/19000?ContentTypeID=1</link><pubDate>Thu, 05 Feb 2015 20:08:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17bb2d0d-0a01-4451-87db-6b8955f93519</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;Thanks Asbjorn. Understood I should use different configuration for my application.
I just wanted to confirm that the same ACK could be interpreted by different slaves and trigger EVENT_TRANSFER_TX_COMPLETED.
My next attempt will be: is there anything useful and accessible inside the ACK coming back could be used to tell if this ACK is actually initiated by MY acknowledged broadcasting?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is in Ant Acknowledgment message coming from the receiving node</title><link>https://devzone.nordicsemi.com/thread/18999?ContentTypeID=1</link><pubDate>Thu, 05 Feb 2015 15:02:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:62c65eeb-fc68-4cc8-8c14-44ae6e6bfc6e</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;You have configured two slaves with same address talking to the same master on the same ANT channel. The ACK will be interpreted by both slaves as their ACK. You should either use a shared channel and no ACKs or open a separate channel for each slave with their own ACKs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is in Ant Acknowledgment message coming from the receiving node</title><link>https://devzone.nordicsemi.com/thread/18998?ContentTypeID=1</link><pubDate>Wed, 04 Feb 2015 21:41:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81ef9e49-51be-4b2d-9d5e-c2cf96d6c046</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;Basically what I am saying is EVENT_TRANSFER_TX_COMPLETED event doesn&amp;#39;t guarantee the message got delivered correctly. I hope I was wrong, or my code had a bug. Keep testing :-)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>