Hi Andy,
no, I am not sending the packets at the same time.
Image above represents the temporal flow of the process.
Init1 sends a packet first that is addressed to Resp1 (only Resp alive), which then replies. There is then a wait for del_t ms.Now Init2 repeats the process, (very likely) gets a reply, followed by another del_t ms wait and so on.
I get the above issue when del_t = 0, but not when del_t >= 50 ms.
DWM3000 RX Timestamp not updated on every packet, CIA processing does not complete remotely resembles my issue, but I get a wrong reading relatively scarcely (~ 1 in 100 readings per init-resp pair).
I haven’t seen this issue when running just 1 Initiator, but I do in some cases also get a situation where resp_rx_ts < poll_tx_ts. The latter can easily be caught but am not sure why it occurs. If it were a reflected signal from a previous iteration, the check for the incremental frame sequence should catch it. Moreover, the timestamp in this situation varies by a large factor, i.e., is sometimes ‘missing’ a digit.