Is there a method to determine if a receiving nRF24 device has completed the ACK (assuming AA is enabled on both transmitting ang receiving devices)?
I ask because I was tracking down a subtle problem where in response to a message, I was performing some configuration actions which included resetting the TX and RX0 addresses on the receiving device. I discovered that doing this too quickly was effectively killing the ACK from the receiving device to the transmitting device, and so the the transmitting device did not see that the message had been received correctly even though this was the case. This had me scratching my head trying to figure out what the problem was. I found that putting a fixed delay in the code of 6500us before resetting the TX and RX0 addressing worked as a crude fix, but this is not ideal, as the code is in an interrupt handler.
I had another look through the datasheet to see if I could spot any discussion of the issue there, but couldn't see it.
Is there a known minimum time documented anywhere you need to allow to ensure not interfering with the AA response? I know the 6500us is excessive, it was just a hack to test the hypothesis of what was going wrong. Or alternatively is there a flag that can be tested somewhere that tells the AA has in fact completed? More generally, is there a way to ensure you never clobber the AA of an incoming packet when setting the TX/RX0 addresses? I was a bit surprised to discover the device doesn't actually handle the issue itself, as the AA response is otherwise fairly invisible. Thanks for any advice and insights.