Update on previous thread.
MH 4.9u b6960, Vantage Pro2, pre-2006, firmware 1.9, USB logger. Altitude 1299m for both MH and console. Baro offset is 0 for both. Send CWOP altimeter.
With a terminal program I captured LOOP and LOOP2 packets, then compared with MH, VPLive and what was submitted to CWOP; and compared to a nearby airport reference. The MH derived data differs significantly from those in the LOOP2. I also loaded 4.9r (pre LOOP2 code), with identical results. Minor differences in pressures are time dependent.
LOOP2
Bar raw (offset 65) 863.1
SLP (offset 7) 1006.3
Absolute Bar (offset 67) 863.1
Altimeter (offset 69) 1009.4
MH SLP calc from weather station
Bar raw 854.2
SLP 1007.0
CWOP Altimeter 998.9
MH SLP calc temp & alt
Bar raw 854.2
SLP 998.9
CWOP Altimter 998.9
VPLive (reads VP SLP, calculates raw & altimeter)
Bar raw 862.3
SLP 1006.4
MADIS Altimeter 1008.7
Nearby airport KRDM, from METAR
SLP 1008.5
Altimeter 1008.8
VPLive, LOOP2, and the airport reference are all in close agreement. Why does MH differ? It looks like it isn't reading LOOP2. Even calculating from console SLP, the values are also off. Since my station is at some altitude, could the formulas used by MH incorrectly factor the altitude? These discrepancies do not exist my other VP2/MH setup that is much closer to sea level.
Also note that the MH query of the Vantage firmware returns for both of my stations:
"logger (21.05.2013 21:04:40): station 0 (Vantage), no firmware version returned."
MH 4.9u fails to read LOOP2 Baro raw **solved**
Moderator: Mattk
Re: MH 4.9u fails to read LOOP2 Baro raw: confirmed
Meteohub can only make use of LOOP2 protocol, when this is supported by the station.
When readout of firmware fails by "no firmware version returned", LOOP2 is not used.
What makes me wonder is, that a 1.9 firmwared station does not report on "NVER"
command.
If you can give me access on ports 22 and 7777 I will try to further analyze this.
BTW: I have seen Envoys that don't report "NVER", but up-to-date Vantages/Vues do afaik.
When readout of firmware fails by "no firmware version returned", LOOP2 is not used.
What makes me wonder is, that a 1.9 firmwared station does not report on "NVER"
command.
If you can give me access on ports 22 and 7777 I will try to further analyze this.
BTW: I have seen Envoys that don't report "NVER", but up-to-date Vantages/Vues do afaik.
Re: MH 4.9u fails to read LOOP2 Baro raw: confirmed
Boris,
NVER returns "1.90"
VER returns "Sep 29 2009"
Any other data that you need?
NVER returns "1.90"
VER returns "Sep 29 2009"
Any other data that you need?
Re: MH 4.9u fails to read LOOP2 Baro raw: confirmed
strange, can you give me a login?
Meteohub asks for "NVER" so that should work, but it doesn't.
Meteohub asks for "NVER" so that should work, but it doesn't.

Re: MH 4.9u fails to read LOOP2 Baro raw: confirmed
fixed with just re-released 4.9u.
Code: Select all
logger (26.05.2013 03:29:37): station 0 (Vantage), firmware version request sent.
logger (26.05.2013 03:29:37): station 0 (Vantage), firmware version 1.90
Re: MH 4.9u fails to read LOOP2 Baro raw **solved**
Thank you, Boris. So far the data look good, but I will need to verify over the next few days.
Any thought about the option to read the altimeter calculated by VP2 (LOOP2 offset 69)?
Any thought about the option to read the altimeter calculated by VP2 (LOOP2 offset 69)?