Update 4.6r

[admin]

Update to Meteohub V4.6r (NSLU2, x86, SheevaPlug) brings these features:

• more corrections to wd-live forecast codes
• support for German vantage forecast texts by variable "actual_thb*_fc_textde"
• support for weather station server ADCON A850
• adds rain data to APRS and CWOP messages
• fixes false "leaf-4" reading on vantage stations
• supports read-out of internal logger of Vantage in case of missing data in Meteohub

Link: http://www.meteohub.de/files/update-v4.6r.upd

[benz]

supports read-out of internal logger of Vantage in case of missing data in Meteohub

Heisst das, dass nun bei einem Stromausfall die Meteohub-Software nachträglich Daten von Vantage-Datenlogger auslesen kann?
Das wäre ja der Hammer!

Gruss benz

[admin]

Yes, exactly. As it is brand new, please be prepared for bugs...

[benz]

Vielen Dank für dieses wichtige Feature!
Nun, meine Vantage und Meteohub hängt an einer USV. Deshalb wird diese Funktion bei mir kaum benötigt. Jedoch bin ich sicher, dass einige Nutzer davon profitieren werden!

Gruss Bruno

[Automan]

I think my WD Live has gone funny saying "Undefined" as part of location, says "Clearing,." for forecast and shows thunderstorm icon.

History of last 31 days also takes a long time before it displays...

http://www.morlocks.co.uk/weather/

Any thoughts?

[admin]

Sorry, that was a silly bug, caused by not replacing the spaces in the vantage forecast text by underscores. The wd-live upload format is a sequence of a couple of hundred values separated by spaces. When one of the values is omitted or more values separated by spaces are included, all information behind that point in the sequence goes mad. This makes the protocol very error-prone, even when anything of minor reason does kick the sequence out of order.

Please update again to 4.6r if you do NOT already have one of the following build numbers:
NSLU2: 183
Sheeva: 296
X86: 4577

[Automan]

Sorry, that was a silly bug, caused by not replacing the spaces in the vantage forecast text by underscores. The wd-live upload format is a sequence of a couple of hundred values separated by spaces. When one of the values is omitted or more values separated by spaces are included, all information behind that point in the sequence goes mad. This makes the protocol very error-prone, even when anything of minor reason does kick the sequence out of order.

Please update again to 4.6r if you do NOT already have one of the following build numbers:
NSLU2: 183
Sheeva: 296
X86: 4577

Yes, that is better.
Many thanks

[Heuer]

Does this version fix the rain offset bug?

[admin]

Rain Offset bug?

[semtex]

After upgrade to version 4.6r
I have problem with the monthly rain.....1094.40 mm in one day (saturday 23/10)
please help my....check here http://www.meteobasaldella.it/
Thanks

[admin]

When you mention the wd-live errors... yes, these should be fixed.

[Heuer]

Rain Offset bug?

Yes. I want to get Meteohub to show the rainfall so far this year (about 20 inches here). I put it in as an offset but it is not calculated in the WD-Live display - still only shows rainfall for the last two months. I added a barometer pressure offset and that works OK so I assume there is a bug that prevents rainfall offset from working. Not tried any of the other offsets.

David

[rabit]

I updateded today and after a few hours a resync was necessary, however.

At the and i found an interesting message with "revision B"... What´s that?

logger (27.10.2010 16:13:17): station 0 (Vantage), data gap of 17 minutes, start reading Vantage's internal logger after 2010-10-27 16:13 (local time).
logger (27.10.2010 16:13:18): station 0 (Vantage), internal logger provides 177 pages of data.
logger (27.10.2010 16:14:46): logged records not of type "revision B" as needed.
logger (27.10.2010 16:14:46): station 0 (Vantage), finished reading internal logger, 2 records inserted.

I use a davis envoy with weatherlink-ip.

[admin]

Cite from "Vantage serial protocol documentation":

There are two different archived data formats. Rev "A" firmware, dated before April 24, 2002 uses the old format. Rev "B" firmware dated on or after April 24, 2002 uses the new format. The fields up to ET are identical for both formats. The only differences are in the Soil, Leaf, Extra Temperature, Extra Humidity, High Solar, High UV, and forecast fields (reedOpen and reedClosed fields are removed).

You can use the VER command and parse the date returned to determine the archive data format, or you can examine byte 42 in the archive record. In a Rev B record, it will have the value 0x00. In a Rev A record, this byte is used for "Leaf Wetness 4" which is never assigned a real data value, so it will always contain 0xFF. Future record formats may assign different values for this field.

I doubt you have a station/firmware that old? or is it a false reading? or a vue?

[rabit]

I doubt you have a station/firmware that old? or is it a false reading? or a vue?

No, a 8 weeks old envoy with vp2.
But the archiv interval is set too 1h. I never thought meteohub will read out this data