ESPNOW timestamping
Posted: Mon Oct 25, 2021 3:35 pm
Hola everyone
I am thinking of doing a project and I would like to use the packet itself as "event timestamp" So node send to master a packet, and master mark the time of the recieved packet as real event time like:
Node send packet ----> 3-6ms roundtrip ----> Master recieved packet at Xxxx milis (master internal clock)
Of course I want to archieve this without nodes/master synchronization
On paper, the time between you "order" the packet to send and the master recieve should not be longer than 10ms, I can handle with that error, but I'm sure there are a lot of scenarios where that time could dramatically increase like channel busy, retries, master busy, cpu priorities ...
So I wonder if there is a way to take these unknown times into account, I know in another products there it's a feature called "recieved timestamp" , this feature helps you (on reciever side) to know "how long ago" the order to send was generated at the packet recieved
Thanks
I am thinking of doing a project and I would like to use the packet itself as "event timestamp" So node send to master a packet, and master mark the time of the recieved packet as real event time like:
Node send packet ----> 3-6ms roundtrip ----> Master recieved packet at Xxxx milis (master internal clock)
Of course I want to archieve this without nodes/master synchronization
On paper, the time between you "order" the packet to send and the master recieve should not be longer than 10ms, I can handle with that error, but I'm sure there are a lot of scenarios where that time could dramatically increase like channel busy, retries, master busy, cpu priorities ...
So I wonder if there is a way to take these unknown times into account, I know in another products there it's a feature called "recieved timestamp" , this feature helps you (on reciever side) to know "how long ago" the order to send was generated at the packet recieved
Thanks