I want to create a synchronous link between a few systems. The “master” defines the timing by sending a packet and then waiting for an ack that will contain data. I want the “slave” to be able to calculate the time from receiving the packet until the next expected packet. It can then wait in low power rather than be actively receiving all the time.
I need to make a list of action packets on the master with fixed frame lengths. Transmit is fixed enough, but I am not sure about receive. Will the receive callback occur just after the packet is actually received, or will it generate a packet or timeout event at the end of the receive window?
On the slave side, I need to match the timing with respect to total duration of a cycle as well as the phase when receive is possible.
There is a bit in the action packet for TIMESTAMP_POSITION which sounds promising. Apparently it can measure from either the start of the received packet or the end of it. This is where the trail runs cold. What does it measure with respect to, and how do I get both ends of that value? I thought maybe it is just on the RTC, but that does not seem to be the case.
The NS_EN bit also seems interesting, but aside from automatically sending a response not much is said. I have not been able to receive this automatic response. So, what would the timing be for the automatic response? Can it contain data?
