# Timing of anemometer data
**URL:** https://community.tempest.earth/t/timing-of-anemometer-data/11013
**Category:** Tempest Owners
**Tags:** tempest
**Created:** [December 15, 2020, 3:30am UTC](https://community.tempest.earth/t/timing-of-anemometer-data/11013 "2020-12-15T03:30:18Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@cw08](https://community.tempest.earth/u/cw08)
#### Post date: [December 15, 2020, 3:30am UTC](https://community.tempest.earth/t/timing-of-anemometer-data/11013/1 "2020-12-15T03:30:18Z")
I’m interested in low-latency and frequent wind speed readings.
The documentation for the UDP packets shows the “rapid\_wind” packets, each sample having a timestamp with 1 second resolution.
Does anyone know the time delay between the actual reading at the instrument and the appearance of the UDP packet?
Thanks!
---
### Author:  [@sunny](https://community.tempest.earth/u/sunny)
#### Post date: [December 15, 2020, 10:43am UTC](https://community.tempest.earth/t/timing-of-anemometer-data/11013/2 "2020-12-15T10:43:34Z")
i don’t have an answer to your question, but it looks you plan using the device for a different purpose than just meteo data.
I’m not sure the instrument is using an instant measurement. Let me tell you again, I don’t know, but it might be that in order to get one speed/direction value ready to be send to the hub, it could do several intermediate ultrasound measurements between pairs of transducers. Those measurements take time. probably more time then any latency the udp creates. So the value you get might be from an average over a small period. It might even be that the assumption is that the wind is rather stable between intermediate measurements (which might not be the case, for whatever you are trying to measure).
In other words, depending on what you really want to measure with the unit, you better know a bit more about the unit itself before starting to wonder what udp latency might be.