meteohub.de

I updated to the 4.9u release on 16 April.

After the upgrade my eBox 3300 reported no data from the USB datalogger of my VantagePro2 weather station.

I just rolled back to release 4.9t and I have data again.

newest 4.9u should have this fixed.

brianeh wrote:I updated to the 4.9u release on 16 April.

After the upgrade my eBox 3300 reported no data from the USB datalogger of my VantagePro2 weather station.

I just rolled back to release 4.9t and I have data again.

How do you rollback to previous versions? Better yet, once you have everything working well how do you prevent further updates when rebooting?

Meteohub is not affected by the bug you was faced with Meteobridge.

Meteohub IS efected!! Problm is NOT fixed for serial Data logger! Since 6942 no connecion to logger. With WSWIN it's ok.

Log:
logger (24.04.2013 18:17:09): station 0 (Vantage), internal logger activated.
logger (24.04.2013 18:17:09): station 0 (Vantage), syncing.
logger (24.04.2013 18:17:09): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:17:09): station 0 (Vantage), time offset of Vantage: -70 minutes
logger (24.04.2013 18:17:09): station 0 (Vantage), eeprom request sent.
logger (24.04.2013 18:17:09): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (24.04.2013 18:17:09): station 0 (Vantage), transmitter 2 active as station type (#0) "ISS".
logger (24.04.2013 18:17:09): station 0 (Vantage), version request sent.
logger (24.04.2013 18:17:19): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:17:29): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:17:29): station 0 (Vantage), firmware version 0.00
logger (24.04.2013 18:17:29): station 0 (Vantage), wrong checksum of DMPAFT response, restarting logger read out.
logger (24.04.2013 18:17:29): station 0 (Vantage), wakeup sent.
logger (24.04.2013 18:17:29): station 0 (Vantage), internal logger activated.
logger (24.04.2013 18:17:29): station 0 (Vantage), syncing.
logger (24.04.2013 18:17:44): station 0 (Vantage), wakeup sent.
logger (24.04.2013 18:17:44): station 0 (Vantage), internal logger activated.
logger (24.04.2013 18:17:44): station 0 (Vantage), syncing.
logger (24.04.2013 18:17:44): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:17:44): station 0 (Vantage), time offset of Vantage: -70 minutes
logger (24.04.2013 18:17:44): station 0 (Vantage), eeprom request sent.
logger (24.04.2013 18:17:44): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (24.04.2013 18:17:44): station 0 (Vantage), transmitter 2 active as station type (#0) "ISS".
logger (24.04.2013 18:17:44): station 0 (Vantage), version request sent.
logger (24.04.2013 18:17:54): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:18:04): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:18:05): station 0 (Vantage), firmware version 0.00
logger (24.04.2013 18:18:05): station 0 (Vantage), wrong checksum of DMPAFT response, restarting logger read out.
logger (24.04.2013 18:18:05): station 0 (Vantage), wakeup sent.
logger (24.04.2013 18:18:05): station 0 (Vantage), internal logger activated.
logger (24.04.2013 18:18:05): station 0 (Vantage), syncing.

Warning: do not install currently - connection is broken!

Rollback to 4.9t - and it is OK
Log:
logger (24.04.2013 18:55:48): data logger (version 4.9t, build 6893) started.
logger (24.04.2013 18:55:57): connect station 0 (Vantage via serial).
logger (24.04.2013 18:55:58): station 0 (Vantage), wakeup sent.
logger (24.04.2013 18:56:01): station 0 (Vantage), internal logger activated.
logger (24.04.2013 18:56:01): station 0 (Vantage), syncing.
logger (24.04.2013 18:56:11): station 0 (Vantage), gettime request sent.
logger (24.04.2013 18:56:11): station 0 (Vantage), no Vantage time offset.
logger (24.04.2013 18:56:11): station 0 (Vantage), eeprom request sent.
logger (24.04.2013 18:56:11): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (24.04.2013 18:56:11): station 0 (Vantage), transmitter 2 active as station type (#0) "ISS".
logger (24.04.2013 18:56:21): station 0 (Vantage), data gap of 718 minutes, start reading Vantage's internal logger after 2013-04-24 06:55 (Vantage's local time).
logger (24.04.2013 18:56:22): station 0 (Vantage), internal logger provides 134 pages of data.
logger (24.04.2013 18:56:41): Bad th0(0) sensor data, "humidity" (255) out of range [0:100]
logger (24.04.2013 18:56:41): Bad th0(0) sensor data, "humidity" (255) out of range [0:100]
logger (24.04.2013 18:56:41): Bad th0(0) sensor data, "humidity" (255) out of range [0:100]
logger (24.04.2013 18:56:42): station 0 (Vantage), finished reading internal logger, 666 records inserted.

awekas wrote:Meteohub IS efected!! Problm is NOT fixed for serial Data logger! Since 6942 no connecion to logger.

It's not simply a serial logger issue.

I have a serial data logger.

6942 works fine for me, both as a direct feed (i.e. to the serial port of an ALIX-1D) and daisy chained to another meteohub on a second ALIX-1D.

It's a issue with a special kind of datalogger firmware. Boris inverigate it.

Reason for issue "awekas" has reported is that an envoy is used. Envoys dont reply on "NVER" command,
which Meteohub uses to determine firmware version to decide if LOOP2 protocol can be used to
read station pressure from the vantage, which otherwise only provides sealevel corrected pressure.

Newest 4.9u handles the missing reply from envoy better.

No sure if it helps diagnosing, but my Envoy has no issues:
Also not with the previous version of 4.9u:

Envoy of user "awekas" does not reply on "NVER" command and the manual (version 2.5)
does also not mention envoy as being a station to expect this from.

Looks like Davis has a lot of funny/differently behaving stations/versions out there...

Hi Boris,

Just let me know if you want to have a look at my setup and check what is different...