ANT Forum

Hi,
I’d like to ask you some questions about ANT-FS.
I'm developing a display app in android that can interact with ANT+ Weight Scale, it is supported ANT-FS function.
Sensor is using ANTFSClientDemo.exe, ANTFS PC Tools.
The base source of App is AntfsTest in Java.(changed ANTFSHostDemo source)

The path to reproduce the problem are as follows:
1. Run ANTFSClientDemo.exe. Set Option and Click Open and Click Open Broadcast.
(Quick Config : Weight Scale)
2. Run a developing display app. And Open channel, then channel is established.
Subsequently, Send a LINK-Command for request ANT-FS Session.
3. After completing the required work, Send a DISCONNECT-Command for disconnect ANT-FS session.

Intermittently, LINK-Command/DISCONNECT-Command after the transfer(as 2 or 3),
received continuously the EVENT_RX_FAIL.
Following, received the EVENT_RX_FAIL_GO_TO_SEARCH and closed the channel.

LINK-Command/DISCONNECT-Command is received through serial message of ANTFSClientDemo.exe if a problem occurs.
It has been confirmed through the Debug log.

I’d like to ask you some questions.
1. Why did happen continuously EVENT_RX_FAIL?
2. Could happen the normal case?
3. What should I do to solve the problem?

Thanks.
Have a nice day.      

How big are the files that you are transferring? Regarding the intermittent EVENT_RX_FAIL, because ANT-FS relies on bursting, it is possible that you are loosing synchronization after completing a long burst transfer. Please refer to the Bursting FAQ for more details, look for the question titled "After a prolonged burst has finished (successfully) my channel appears to have become unsynchronized, it misses packets and then goes into search mode before re-establishing. Is this normal?"
http://www.thisisant.com/developer/resources/tech-faq/category/bursting/

The logs generated by the ANT-FS client (DeviceX.txt), as well as the higher level application logs (ao_debug_antfs...) may provide more clues on this. It may also be helpful to try to reproduce the same procedure with the ANT-FS host and compare the behaviour with what you see on your own application to see if there are problems in the implementation of the code you are working from.