meteohub.de

My setup:
Vantage Pro2
Meteohub 4.9t (build 69) on mini X plus
CWOP ID: EW2013
Using station info for sea level calculation
Altimeter selected...

So, the data log from meteohub looks to have accurate data that matches what the console displays (also closely matches nearest airport data and expected forecast data):
20130206041515 thb0 242 20 -002 8236 2 10095
20130206041615 thb0 242 20 -002 8235 2 10094
20130206041715 thb0 242 20 -002 8236 2 10095
20130206041815 thb0 242 20 -002 8237 2 10096
20130206041917 thb0 242 20 -002 8237 2 10096
20130206042019 thb0 242 20 -002 8237 2 10096

Over roughly the same time frame, this is what CWOP is receiving:
EW2013>APRS,TCPXX*,qAX,CWOP-2:@060417z4001.77N/10504.52W_327/001g003t044r000p000P000b09972h38eMH49
EW2013>APRS,TCPXX*,qAX,CWOP-2:@060422z4001.77N/10504.52W_273/001g003t044r000p000P000b09973h39eMH49
EW2013>APRS,TCPXX*,qAX,CWOP-2:@060427z4001.77N/10504.52W_286/001g003t043r000p000P000b09973h40eMH49
EW2013>APRS,TCPXX*,qAX,CWOP-2:@060432z4001.77N/10504.52W_287/001g003t043r000p000P000b09973h41eMH49
EW2013>APRS,TCPXX*,qAX,CWOP-2:@060437z4001.77N/10504.52W_213/001g004t043r000p000P000b09972h41eMH49
EW2013>APRS,TCPXX*,qAX,CWOP-2:@060442z4001.77N/10504.52W_259/001g004t042r000p000P000b09972h43eMH49

997mb? I'm pretty sure there isn't some sort of sneaky inland tornado/hurricane over head...

The elevations are all the same on CWOP, meteohub and the console (and correct within a few feet)... The Weather underground data that I am uploading closely matches the console/log data.

I saw that there were issues with CWOP changing the algorithm but I thought this was fixed in a previous release of meteohub?

Help?

Thanks,
Garth

Hmmm... If I set the meteohub altitude to "0" feet then the barometric pressure readings normalize on CWOP... It looks like meteohub/CWOP is adding the altitude twice for my setup. Not sure if this is a bug or not...

Garth

Alrightly then... That worked for a few days but of course as temperature/pressure changed I was off again by 5-10mb. So, I realize the CWOP is based in part on the inaccurate readings of surrounding stations but I am no where near where I should be. Mesonet and Wunderground readings are the same as what the console reports so there almost has to be an issue with what meteohub is sending to CWOP from the Davis Vantage Pro2. I have the latest version of the meteohub software (rebooted/recalculated mutiple times)... I have the elevations set correctly and set to the same value on the console, meteohub and cwop (verified via Topo map, GPS unit and google maps)... I am using the station info for the sea level calculation... And I have selected the altimeter option for sending data... I can see that the data that I am receiving in the meteohub logs matches the nearest airport, mesonet and wunderground...

And yet here I am:
http://weather.gladstonefamily.net/site/E2013

Am I the only one with this issue? I know that CWOP is not a high priority for many people but I don't want to be the guy that messes up the accuracy even worse for those who chase the gladstone quality check numbers... Yes, I could just stop sending but I would like to think that someone may want to use the aggregated data as well...

Many have stated that you can set the console elevation to zero and then put in the local known good value on a calm, high pressure day (offset) but disabling some of the features on a $800 weather station seems ridiculous.

Thanks in advance,
Garth

Hi,
maybe the problem is similar to the problem I had (viewtopic.php?f=14&t=9122&p=12897&hilit=altimeter).

Unfortunately Davis will only send the sea level pressure via serial via the LOOP packet and then Meteohub will calculate the local and altimeter pressure from there.
There is a new LOOP2 packet include as well the local/raw pressure but this is new documentation was published August 2012 and seems Meteohub will not support this yet.
Hopefully Boris will include this in future versions, this would fix all these problems.

El

Thanks El... I think this is exactly the same issue... Even though there is not a solution at present it's nice to know I'm not the only one waiting for the Loop2 fix.
Thanks again,
Garth

LOOP2 is on my todo list.

Version 4.9u (ready for download now) makes use of LOOP2 packets to read station and sealevel barometer data from the console.
Hopefully, this solves the issue of non-perfect computation from sea level pressure back to station pressure when dealing with higher altitudes.