Hello.
Thank you, Jefferson. The states were not the problems. First I didn't care much about what ANT wanted to tell me. Data received by ANT I just dumped. It worked for transmitting (I know: check EVENT_TX). In the pictures in the different manuals it seems to be that SEN has 2 Functions:
1.) kind of ACK when host wants to send and pulls MSG_RDY down!
2.) to show that ANT wants to transmit.
SEN seems to be idle high...
So my receive-function used the falling SEN-edge as interrupt, which never happend...
So I started to take care about the ANT Responses and used a state machine as adviced in the manual. But again no ISR, because SEN = 0.
Interesting:
"SEN will pulse after the synchronous reset sequence, but not necessarily after sending a command (such as the reset command). When SEN is high, it means that ANT is not ready to send/receive serial messages - it provides flow control.
Right after the reset command, ANT should be ready to receive messages from the host. Wait ~500ms after the command for the reset to be completed, and you should be able to start sending other commands." -alejandra
http://www.thisisant.com/component/option,com_fireboard/Itemid,146/func,view/catid,25/id,209/#308
"SEN needs to be on an interrupt capable I/O pin on the microcontroller." - ap2_transceiver_datasheet
However... Now I don't use an interrupt and I can receive too. In my opinion the datasheets could explain the things much better.
BG, Matthias