How do I use "logging protocol" to get data from MeteoHub to

[AAMFlyer]

Ahhhhh - I get it! :P

Okay - then - mine is doing the same thing - crashing after about 16 hours of data!

Thanks!

[skyewright]

Thank you skyewright for your help!

Happy to help. :)
I also took the opportunity to remind Brian (the WD developer) about this. He's taken another look and has spotted the cause. I hope to have time to test the fix sometime today. :)

[skyewright]

He's taken another look and has spotted the cause. I hope to have time to test the fix sometime today. :)

Brian has now successfully collected a sample of around 5 days backlog in one go. I have the latest version of WD running on a spare WD installation here and I'm letting it chew on collection of around 6 weeks of data - which may take sometime. So far so good. :)

He's also looking at a 'temp only' sensor issue I've seen, but so far he hasn't been able to reproduce it at his end.

[skyewright]

I have the latest version of WD running on a spare WD installation here and I'm letting it chew on collection of around 6 weeks of data - which may take sometime.

Twice now crashed after picking up 8 days worth of backlog, but that's a great improvement on 16 hours worth. I'll let Brian know the results and see what he chooses to do.

[Patxi]

Fine, it's a good improvement!

I have to report that WD data collecting from meteohub have some problem with the rain data. The main problem is relative to the accumulated rain. I think that the new rain from one day, whe WD collects data from meteohub, transfers it like an accumulation from the day before.

I say, for example. In december, only was raining two days, 28/12/2008 and 29/12/2008, 10.7 mm the first day and 2.0 mm the day 29.

But in the WD logfile, there appears 10.7 mm for the 28th, 12.7 mm for the 29th (when really was 2.0mm), and repeats 12.7 mm for the next days, till there is another day o f real rain. And then the same story.


I've been changing values with WD, but it could be interesting to the WD developer.

I wish you understood what i try to say :S

regards!

[skyewright]

I wish you understood what i try to say :S

I believe I understand.

It probably wasn't helped by the crashes during collection, maybe that meant that some end of day resets got missed out?
Once you have it running 'normally' it should be fine (mine is).

In terms of latest WD devlopment:

a) 'temp only' sensors from Meteohub are now handled well.
Previously, they were subject to spikes in 'live' data collection (which I worked around using my 'proxy' cgi).

b) Collection of large volumes of backlogged data still hits a wall after ~8 days. Brian is still working on that one.

[Patxi]

Yes, it is possible that frequent crashes during data collention could produce this rain data error.

When the new version of WD, with this problem solved, will be available, I'll recollect all the data again, then I'll tell you the result :)

[skyewright]

When the new version of WD, with this problem solved, will be available, I'll recollect all the data again, then I'll tell you the result :)

A new version is now available. With the new version the 'missed data' collection stage can manage around 2 weeks worth of data (when tested on my system) before it packs in.

Unlike previously, when collection stops all you need to do is restart WD. It will automatically pick up collecting missed data from where it left off, i.e. there is no longer any need to 'tweak' the [Davis Download] section of WDISPLAY.INI before restarting. :)