meteohub.de

While testing the new DC01 my VantagePro was disconnected from another meteohub (4.9g build 6326-VMWARE) for nearly 60 minutes.
When reconnecting the VP meteohub displays in its log:
logger (25.04.2012 17:58:37): station 0 (Vantage), data gap of 63 minutes, start reading Vantage's internal logger after 2012-04-25 16:55 (Vantage's local time).
a few $ - 5 times but than:
logger (25.04.2012 17:59:43): station 0 (Vantage), wrong checksum of DMPAFT response, restarting logger read out.

And meteohub starts the whole process again:
ogger (25.04.2012 17:59:43): station 0 (Vantage), wakeup sent.
logger (25.04.2012 17:59:43): station 0 (Vantage), internal logger activated.
logger (25.04.2012 17:59:43): station 0 (Vantage), syncing.
logger (25.04.2012 17:59:53): station 0 (Vantage), gettime request sent.
logger (25.04.2012 17:59:53): station 0 (Vantage), no Vantage time offset.
logger (25.04.2012 17:59:53): station 0 (Vantage), eeprom request sent.
logger (25.04.2012 17:59:53): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (25.04.2012 17:59:53): station 0 (Vantage), transmitter 2 active as station type (#1) "Temperature Only" mapped to "t1".
logger (25.04.2012 17:59:53): station 0 (Vantage), transmitter 7 active as station type (#0) "ISS".
wmr928fulleval(25.04.2012 18:00:01): recomputation of weather data started.
logger (25.04.2012 18:00:05): station 0 (Vantage), data gap of 64 minutes, start reading Vantage's internal logger after 2012-04-25 16:55 (Vantage's local time).
which than results in the same error, etc.
Normally i could resolve this by using weatherlink to clear the vp logger.
I did, weatherlink says only one block exists with 5 records but still meteohub tries and not succeeds in reading the missing data.
The last message was
logger (25.04.2012 18:17:46): station 0 (Vantage), data gap of 82 minutes, start reading Vantage's internal logger after 2012-04-25 16:55 (Vantage's local time).

After deleting and defining the vp station again it does not work either.

Does anyone has an idea how to solve this?

Hi,

Is MH the only piece of software that talks to the Vantage? You will need to make sure that no other software (including your old MH) is trying to talk to the vantage.

For a problem description you might want to add what connection you are using (serial/USB/TCP/IP); im missing a message like "connect station 1 (Vantage via TCP/IP)" in your log output.

Ysbrand

Error occurs only after long delay in connection 9for one reason or another).
I am only directly reading from usb when this error occurs.
A copy of the list of errors is attached.

SOLUTION:
Lets call the meteohub with the problem " reading Vantage's internal logger" meteohubUSB .
I have another meteohub. Lets call it meteohubIP.
I let meteohubUSB read good data via meteohup/ip:5500 by changing the connection type.
MeteohubUSB restarts and does not complain about a datagap.
Than i change meteohubUSB back to reading from usb and there ara no more messages about missing dat because the data gap is less than 10 minutes.

Conclusion:
Can the relative new feature of reading the VP logger made a user choice. for certain configurations it does not work.

I am a bit reluctant to add more and more switches to it. From my understanding reading the vantage internal logger does not make sense when a meteohub is daisy chained via a tcp/ip socket connection to another meteohub that has the vantage physically connected via USB/serial or tcp/ip. Would changing behavior this way solve your issue?

Normally it is reading from a USB VP console.
So the only solution after a more than 10 minutes outage is daisy chaining with another meteohub.
No problem in my test-situation although the usb is normally listening to anther VP than the daisy chained one.
But daisy chaining is only necessary for some seconds, after switching back to usb meteohub detects only a less than 10 minutes gap and does not read the logger.

But when a remote station would go down for more than 10 minutes it can not restart itself and i have no clue what to do.

Every time meteohub tries to start reading the log when connected via usb to a " Cygnal Integrated CP2102 USB to UART Bridge Controller " the logging fails.
And at the remote site i have only one logger.

So the possibility to overrule reading of the logger would be extremely appreciated.

What puzzles me is that other users don't have that problems, and I cannot reproduce the effects here.
Can you please try another cheap FTDI or PL2303 based converter? My guts feeling tells me that this might cause the trouble.

I will buy another one and try again.