RE: Ant ACK retries

angel — Mon, 24 Apr 2017 13:09:30 GMT

Hi Petter,

In the end I found that my own developed SW ACK works better for my application than the ANT own ACK, since I can control every parameter. Thanks anyhow for the answer, was helpful in solving my question.

Best,

Angel.

RE: Ant ACK retries

Petter Myhre — Tue, 18 Apr 2017 12:07:16 GMT

This seems to be described in Section 9.5.5.2 in ANT Message Protocol and Usage 5.1, on Page 103:

Acknowledged data messages can be sent from a slave to a master. In this case the message is sent immediately after a message is received from the master. If the acknowledged data message is sent successfully, this will be indicated by the channel event TRANSFER_TX_COMPLETED. If no acknowledgement is received from the master, this will be indicated by TX_TRANSFER_FAILED, which either means that the message failed to reach the master, or that the response from the master failed to reach the slave. In this case the slave’s application layer may retry the message. A third possible scenario is that the channel is dropped and the slave begins to search; in this case the event GO_TO_SEARCH will be received, instead of either of the other two commands. If GO_TO_SEARCH is received then the acknowledged message will not be sent, and the channel should be unassigned

I dont' understand. What kind of information?
Depends on when you tell the stack to send the message, and the channel period. See the Figure 9-2 for more information.