I am using an AP2 module and AntwareII PC software. Asynchronous interface, 57.6K.
Initialisation, broadcast messages work OK.
When I try to queue up a burst message sequence, the RTS line only pulses high after the first message. I do not start to send the second message until after RTS has gone low. (Checked with scope). Adding delays do not help.
What reasons are there for RTS not responding to a message? I expect serial framing error or checksum error. Are there others?
I can see no problem with either of these in my case.
Would an incorrect sequence number cause this, or would that error be reported later?
(The sequence number/channel Number bytes I am using - channel 0 - are: 0x00, 0x20, 0x40, 0x60, 0xA0. Is this correct for a 5 message sequence?)
I get the first message received OK by the PC, but then get an EVENT_TRANSFER_TX_FAILED error.
I have also tried only queuing up one message, then sending the rest after an EVENT_TRANSFER_START has been received. In this case, RTS pulses after the first of these subsequent messages only. Two messages get through to the PC - the queued one, and the first one sent in response to the start event.
The problem is consistently repeatable, so would not appear to be flakey HW.
I am new to ANT, so I may have missed something basic.
Any ideas?
Thanks, Graeme.
