Update 4.6r
Moderator: Mattk
Re: Update 4.6r
hm, log entry tells that one record has been skipped. SO no big issue, but we should keep an eye on it.
Does it always happen, when you halt data logging for 15 minutes and restart logging again?
It needs a minimum gap of 10 minutes to start internal logger read-out.
Does it always happen, when you halt data logging for 15 minutes and restart logging again?
It needs a minimum gap of 10 minutes to start internal logger read-out.
Re: Update 4.6r
I forced an error (disconnect).
The result for the logger:
Hardware Version: 2.0.2
Firmware Version: 1.0.9
The data (only th0). Timestamp Problem?
The result for the logger:
Hardware Version: 2.0.2
Firmware Version: 1.0.9
logger (28.10.2010 19:44:32): station 0 (Vantage), error connect socket 192.168.178.8: port 22222: No route to host
logger (28.10.2010 19:45:03): station 0 (Vantage), error connect socket 192.168.178.8: port 22222: No route to host
logger (28.10.2010 19:45:36): station 0 (Vantage), error connect socket 192.168.178.8: port 22222: No route to host
logger (28.10.2010 19:46:08): station 0 (Vantage), error connect socket 192.168.178.8: port 22222: No route to host
logger (28.10.2010 19:46:38): connect station 0 (Vantage via TCP/IP).
logger (28.10.2010 19:46:43): station 0 (Vantage), syncing.
logger (28.10.2010 19:46:44): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (28.10.2010 19:46:44): station 0 (Vantage), transmitter 1 active as station type (#0) "ISS".
logger (28.10.2010 19:46:44): station 0 (Vantage), transmitter 2 active as station type (#4) "Wireless Anemometer".
logger (28.10.2010 19:46:44): station 0 (Vantage), transmitter 3 active as station type (#8) "SensorLink".
logger (28.10.2010 19:46:44): station 0 (Vantage), transmitter 4 active as station type (#1) "Temperature Only" mapped to "t1".
logger (28.10.2010 19:46:49): station 0 (Vantage), data gap of 40 minutes, start reading Vantage's internal logger after 2010-10-28 19:46 (local time).
logger (28.10.2010 19:46:49): station 0 (Vantage), internal logger provides 3 pages of data.
logger (28.10.2010 19:46:51): logged records not of type "revision B" as needed.
logger (28.10.2010 19:46:51): logged records not of type "revision B" as needed.
logger (28.10.2010 19:46:51): logged records not of type "revision B" as needed.
logger (28.10.2010 19:46:51): logged records not of type "revision B" as needed.
logger (28.10.2010 19:46:51): station 0 (Vantage), finished reading internal logger, 8 records inserte
The data (only th0). Timestamp Problem?
This system is my backup and for a few graphs, so i can play with it...20101028170447 th0 91 81 0060
20101028170519 th0 90 81 0059
20101028170634 th0 89 81 0058
20101028181000 th0 88 82 0059
20101028181500 th0 89 82 0060
20101028182000 th0 86 83 0059
20101028182500 th0 83 84 0058
20101028183000 th0 82 85 0058
20101028183500 th0 80 85 0056
20101028184000 th0 81 86 0059
20101028184500 th0 79 86 0057
20101028174721 th0 78 86 0056
20101028174823 th0 78 86 0056
20101028174924 th0 78 86 0056
20101028175025 th0 78 86 0056
20101028175053 th0 78 87 0058
20101028175146 th0 78 86 0056
20101028175200 th0 77 86 0055
20101028175237 th0 77 87 0057
20101028175340 th0 77 87 0057
20101028175432 th0 78 87 0058
20101028175534 th0 78 87 0058
20101028175636 th0 78 87 0058
20101028175727 th0 77 87 0057
Re: Update 4.6r
Looks like your Vantage/Envoy does not have the same time zone as your Meteohub. Do your clocks differ about an hour?
That could also explain the illegal data records.
That could also explain the illegal data records.
Re: Update 4.6r
Weatherlink-IP is on GMT +1h (Berlin..) set with the software weatherlink. (Do to summertime in real +2h).
Meteohub also on Europe/Berlin, but logging with GMT.
The actual time seems to be the same for both systems..
Meteohub also on Europe/Berlin, but logging with GMT.
The actual time seems to be the same for both systems..
Davis VP2 > Weather-Envoy > Weatherlink-IP > SheevaPlug > Meteohub >
Re: Update 4.6r
To my knowledge Envoy does not allow to select time zone or daylight saving settings
through its setup program. How did you setup time/date values for your Envoy?
through its setup program. How did you setup time/date values for your Envoy?
Re: Update 4.6r
Boris, yes those can set those through the Davis Weatherlink software. The Envoy is basically the same as a Davis console minus the LCD display and buttons. I have two of them.To my knowledge Envoy does not allow to select time zone or daylight saving settings
through its setup program.
Will you be updating the user manual to explain something about the "supports read-out of internal logger of Vantage in case of missing data in Meteohub" feature? Thanks.
Re: Update 4.6r
@rabit: I added some new code to compensate time offsets in the vantage logger. You can try this by updating to the "4.6-experimental" version (auto-update) and can go back to "4.6r" from there, when it does not work.
Please post results on using the experimental version. I hope it fixes your timezone/daylightsaving issue.
Please post results on using the experimental version. I hope it fixes your timezone/daylightsaving issue.
Re: Update 4.6r
I installed the experimental version and stopped between 18:31 and 18:58 MESZ.
logger (30.10.2010 18:58:30): station 0 (Vantage), data gap of 22 minutes, start reading Vantage's internal logger after 2010-10-30 18:58 (Vantage's local time).
logger (30.10.2010 18:58:31): station 0 (Vantage), internal logger provides 2 pages of data.
logger (30.10.2010 18:58:32): station 0 (Vantage), logged record #5 skipped as not of "revision B" type (ff).
logger (30.10.2010 18:58:32): station 0 (Vantage), logged record #5 skipped as not of "revision B" type (ff).
logger (30.10.2010 18:58:32): station 0 (Vantage), logged record #5 skipped as not of "revision B" type (ff).
logger (30.10.2010 18:58:32): station 0 (Vantage), finished reading internal logger, 5 records inserted.
20101030163218 th0 136 69 0080
20101030163228 th0 135 69 0079
20101030163258 th0 136 69 0080
20101030163349 th0 135 69 0079
20101030163350 th0 136 69 0080
20101030163551 th0 136 69 0080
20101030173400 th0 136 69 0080
20101030173900 th0 136 69 0080
20101030174400 th0 136 70 0082
20101030174900 th0 136 70 0082
20101030175400 th0 136 70 0082
20101030165906 th0 136 71 0084
20101030165958 th0 135 71 0083
20101030170008 th0 136 71 0084
20101030170018 th0 135 71 0083
20101030170028 th0 136 71 0084
20101030170040 th0 135 71 0083
Davis VP2 > Weather-Envoy > Weatherlink-IP > SheevaPlug > Meteohub >
Re: Update 4.6r
hm... could you please give me login at port 22 and port 7777?
Re: Update 4.6r
Now, with no "daylight saving" the archiv data reading and the timestamps are ok!
Davis VP2 > Weather-Envoy > Weatherlink-IP > SheevaPlug > Meteohub >
Re: Update 4.6r
I guess there is moonrise today 

Re: Update 4.6r
I got these floating point exception errors while running 4.6r in less than 24 hours after reboot. I've upgraded to 4.6s now, but want to post these errors in case others running 4.6r see them. My system is a eBox-3300. Thanks.
/home/meteohub/wmr928fulleval: line 37: 2441 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c min5 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2957 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c min10 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2959 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c min30 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2964 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c hour1 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2967 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c hour6 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2968 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c day1 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2969 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c month1 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/histeval3: line 18: 2977 Floating point exception/usr/bin/nice -n -2 /home/meteohub/wmr928eval -c alltime -t 19900101000000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -H
/home/meteohub/histeval3: line 18: 2978 Floating point exception/usr/bin/nice -n -2 /home/meteohub/wmr928eval -c month1 -t -34560000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -S
/home/meteohub/histeval3: line 18: 2980 Floating point exception/usr/bin/nice -n -2 /home/meteohub/wmr928eval -c year1 -t `date +%Y`0101000000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -H
/home/meteohub/histeval2: line 18: 2984 Floating point exception/home/meteohub/wmr928eval -c month1 -t -3500000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -H
/home/meteohub/wmr928fulleval: line 37: 2441 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c min5 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2957 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c min10 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2959 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c min30 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2964 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c hour1 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2967 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c hour6 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2968 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c day1 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/wmr928fulleval: line 37: 2969 Floating point exception/usr/bin/nice -n 2 /home/meteohub/wmr928eval -n -c month1 -w /data/weather/ -s /home/meteohub/wmr928fulleval.do.conf
/home/meteohub/histeval3: line 18: 2977 Floating point exception/usr/bin/nice -n -2 /home/meteohub/wmr928eval -c alltime -t 19900101000000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -H
/home/meteohub/histeval3: line 18: 2978 Floating point exception/usr/bin/nice -n -2 /home/meteohub/wmr928eval -c month1 -t -34560000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -S
/home/meteohub/histeval3: line 18: 2980 Floating point exception/usr/bin/nice -n -2 /home/meteohub/wmr928eval -c year1 -t `date +%Y`0101000000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -H
/home/meteohub/histeval2: line 18: 2984 Floating point exception/home/meteohub/wmr928eval -c month1 -t -3500000 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -H