Burst transfer problems

RE: Burst transfer problems

Asbjørn — Mon, 10 Nov 2014 13:32:18 GMT

When you see one TRANSFER_SEQUENCE_NUMBER_ERROR you never recover from it at the test of the burst is lost? From the ANT message, protocol and usage you find that:

"However, the success/failure notification is for the entire burst transfer rather than for each packet and, unlike acknowledged messages, any lost data packets in the transfer will be automatically retried. Should any packet fail to transmit successfully after five retries, ANT will abort the burst transfer and notify the host MCU with a failure message."

So the failing package should be re-tried and if this fails five times it will collapse. What kind of environment are you testing this is? Could there be some interference from other sources that are interrupting your ANT link for shorter periods of time? What's the distance between your two units? Could you try a different frequency? Do you have other ANT nodes in the area with same network key and frequency?

The sequence number is written by you on the nRF24AP2, how do you control this in your application? Could there be something that occurs in your application that would change the sequence number you write?

RE: Burst transfer problems

Klaus Roy-Poulsen — Wed, 05 Nov 2014 14:46:24 GMT

Hi Asbjørn No, that is not the case. My statement regarding correct messages, sequence numbers and acknowledge described the situation up to the point where I get the TRANSFER_SEQUENCE_NUMBER_ERROR. All further burst messages fail with the same error regardless of the sequence number in the message.

RE: Burst transfer problems

Asbjørn — Tue, 04 Nov 2014 14:03:54 GMT

Just to be certain, you are receiving a TRANSFER_SEQUENCE_NUMBER_ERROR from the nRF24AP2, but you still see all the correct and expected packages/payload from the burst on the serial interface? Even after you get the TRANSFER_SEQUENCE_NUMBER_ERROR it continues to work and the sequence number is in correct order?