Wind Data samples lost in VP2 (updates WL.com 10 min) **solved**

[agallardo1980]

Hi,

I have enabled the WL.com updates every 10 min in MB PRO. I have read this from Meteobridge releases notes:

Code: Select all

increases logging timeout period of 15 secs to 20 secs in order to allow more stable WLIP uploads to Davis weather link server.

Can not Weatherlink-IP have multiple tasks at the same time? (i.e. send LOOP2 pachets to MB and uploads data to WL.com)

I am somewhat worried about this because it would mean that in my case I would lose 8 wind samples (2,5s per sample in 20 s timeout period) from the console every 10 minutes, that is to say (8 / 240 samples = 3,33% loss in wind samples)

Is this a normal issue?

[Mattk]

WL.com does not upload data continuously or in real time anyway, typically every 60 seconds, what the MB control does is eliminate any conflicts. Reading data and uploading data are separate processes

[agallardo1980]

Ok. But... Why is neccesary this logging timeout period in MB? What type of conflict may there be? I understand that in these timeout period I loose wind samples my station

[agallardo1980]

Has anyone a response? Is there any limitation with Weatherlink IP datalogger to upload to WL.com and send data to MB at same time?

[Mattk]

If you call trying to do 2 things at exactly the same time then some may call that a limitation, other than that no as the MB can be set to a specific time slice to complete the WL.com upload without conflicts and this can be 1, 5 or 10 minutes

[admin]

No worry, wind spikes are not lost, even when Meteobridge does not see all live wind data. LOOP2 packets hold wind max spikes and Meteobridge does make use of this.

[agallardo1980]

Ok. I am more quiet knowing that the MB takes into account the max gust speed from datalogger in this 20seg timeout period.
Thank you very much.