<?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>Burst transmission triggered many times</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6350/burst-transmission-triggered-many-times</link><description>I am doing burst transfers using exactly the code suggested here devzone.nordicsemi.com/.../ 
 The problem is, the data is received three times by the receiver (three times the same packet) 
 Additional info: 
 
 I have a registered a callback function</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Apr 2016 15:51:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6350/burst-transmission-triggered-many-times" /><item><title>RE: Burst transmission triggered many times</title><link>https://devzone.nordicsemi.com/thread/22130?ContentTypeID=1</link><pubDate>Tue, 12 Apr 2016 15:51:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31ae3790-b4cf-4117-b27c-6e592d266a26</guid><dc:creator>Sven</dc:creator><description>&lt;p&gt;Year late, but this approach works okay until the burst sequence does not get very long (in my case got 30 times 8byte packets)....&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Burst transmission triggered many times</title><link>https://devzone.nordicsemi.com/thread/22129?ContentTypeID=1</link><pubDate>Tue, 07 Apr 2015 04:25:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:518caca4-4832-4459-b1bf-91377ead4974</guid><dc:creator>testy</dc:creator><description>&lt;p&gt;It is worth registering at thisisant.com.&lt;/p&gt;
&lt;p&gt;thisisant SDK shows, when flag is needed (antfs.c x message_types_main.c).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Burst transmission triggered many times</title><link>https://devzone.nordicsemi.com/thread/22128?ContentTypeID=1</link><pubDate>Mon, 06 Apr 2015 09:01:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2ed938dc-e81d-40cd-9309-21d932be4eda</guid><dc:creator>Vito</dc:creator><description>&lt;p&gt;Hi, thanks a lot.
I have googled for uses of sd_ant_burst_handler_request() but the two links you posted are in a restricted area, so they weren&amp;#39;t showing up.
For completeness, this is what made my burst transmission work:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;do
{
    err_code = sd_ant_burst_handler_request(CHANNEL_0, TX_PACKET_LEN, ant_msg, (BURST_SEGMENT_START|BURST_SEGMENT_END) );                
} 
while (err_code == NRF_ANT_ERROR_TRANSFER_IN_PROGRESS);
APP_ERROR_CHECK(err_code);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I notice that the registering of the wait flag became useless and I can remove it, am I right?&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;err_code = sd_ant_burst_handler_wait_flag_enable(&amp;amp;burst_wait);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;However, the use of sd_ant_burst_handler_request() is a bit hard to guess, maybe an example in the SDK or in the documentation would be nice to have.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Burst transmission triggered many times</title><link>https://devzone.nordicsemi.com/thread/22127?ContentTypeID=1</link><pubDate>Fri, 03 Apr 2015 14:43:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9199ce46-94e5-443e-872e-c7c1b6669aa3</guid><dc:creator>testy</dc:creator><description>&lt;p&gt;This works for me to send 64 bytes of 72:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;uint8_t m_burst_data[72];
err_code = sd_ant_burst_handler_request(CHANNEL_1, ((sizeof(m_burst_data))-8), m_burst_data, (BURST_SEGMENT_START | BURST_SEGMENT_END));
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Consider:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Burst: the &lt;strong&gt;last&lt;/strong&gt; packet of the burst will be retransmitted on the next channel period if ANT has not received any new data from the master’s host MCU.
Advanced Burst: the &lt;strong&gt;first&lt;/strong&gt; packet of the burst will be retransmitted on the next channel period if ANT has not received any new data from the master’s host MCU.
Unlike normal burst transfers, the retransmitted data will be the &lt;strong&gt;first&lt;/strong&gt; packet of the burst (the initial 8-byte normal burst packet).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;That&amp;#39;s for nRF51 master (sends Advanced Burst) -&amp;gt; ANT &lt;strong&gt;AP2&lt;/strong&gt; 81M5IB slave (Burst only capable device):&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/burst.PNG" alt="image description" /&gt;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s funny, but after I figured this line of code out, today I found exactly the same solution &lt;a href="http://www.thisisant.com/resources/n5-starter-kit-sdk-1/"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.thisisant.com/forum/viewthread/4151/"&gt;This&lt;/a&gt; can help too.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>