weewx4 - vantagepro issue
132 views
Skip to first unread message
weerstation Maurik
Mar 18, 2020, 7:56:00 AM3/18/20
to weewx-user
I have installed version 4 according to the docs in the install archive on my RPi.
Added my old databases (54MB) in the weewx/archive folder and started weewx from the command line.
A full import of the database took place and it grew to 60MB.
I have however problems getting data in the system as the connection to the vantag pro seems off.
When running as a daemon I get
ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
and later
ERROR weewx.drivers.vantage: DMPAFT try #1; error: Timeout in get_data_with_crc16
If I run it from the command line after issuing the command I get the loop packets visible and this continues till ctrl-c
LOOP: 2020-03-18 11:47:10 CET (1584528430) altimeter: None, appTemp: 55.1173360971, barometer: 30.288, beaufort: 0, cloudbase: 3768.61590836, consBatteryVoltage: 4.47, dateTime: 1584528430, dayET: 0.021, dayRain: 0.0, dewpoint: 40.7060900032, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 6, forecastRule: 9, heatindex: 57.2, humidex: 57.2, inDewpoint: 45.1749354896, inHumidity: 44.0, insideAlarm: 0, inTemp: 67.9, leafWet4: 0.0, maxSolarRad: 554.161850926, monthET: 0.71, monthRain: 2.5039369926, outHumidity: 54.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 57.2, pressure: None, radiation: 322.0, rain: None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1584511920.0, sunset: 1584555504.0, txBatteryStatus: 0, usUnits: 1, UV: 1.5, windchill: 57.2, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, yearET: 2.2, yearRain: 19.4015746848
The website build remains stuck at the last date from the old database (altough it is refreshed in the new layout).
I added relevant sections from the syslog
Anybody any ideas where to look?
Thanks,
Thomas Keffer
Mar 18, 2020, 8:12:31 AM3/18/20
to weewx-user
I think WeeWX is probably working fine when you ran it from the command line. It's just that its archive interval is 10 minutes, and you did not let it run that long, so you did not see any new reports.
As for the I/O errors while running as a daemon: I noticed that the time on the Vantage clock was 640 seconds fast, then two minutes later it was 641 seconds slow. Not sure what happened there. Had the RPi just been booted, and had not settled on a time? If you let the RPi run for a few minutes, then start the daemon, what happens?
--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1f91fe4b-340c-47cb-94df-1aa5d32585e4%40googlegroups.com.
weerstation Maurik
Mar 18, 2020, 8:32:29 AM3/18/20
to weewx-user
Thanks for the quick reply Thomas.
I have restarted the RPi, now wait half an hour or so and then start weewx from the commandline.
Wait another half an hour and see what I got. Will report back here later.
The time thing I noticed the 640sec or so but didn't see the fast and slow !
The daemon starts on RPI startup so no delay there, for now removed it.
Will investigate that after the commandline is running properly.
weerstation Maurik
Mar 18, 2020, 12:02:49 PM3/18/20
to weewx-user
Restarted the RPi and same things occurred.
Decided to remove the old database and see what happened then.
command line runned as it should be, all updating database and website = all good
ctrl-c on command line and executed the daemon commands.
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.restx: CWOP: Posting not enabled.
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.restx: WOW: Posting not enabled.
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.restx: AWEKAS: Posting not enabled.
Mar 18 16:31:31 rpi-weather weewx[1217] INFO __main__: Starting up weewx version 4.0.0b14
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.engine: Clock error is -5.90 seconds (positive is fast)
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.drivers.vantage: Clock set to 2020-03-18 16:31 :32 CET (1584545492)
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Mar 18 16:31:31 rpi-weather weewx[1217] INFO weewx.manager: Starting backfill of daily summaries
Mar 18 16:31:33 rpi-weather weewx[1217] INFO weewx.manager: Added record 2020-03-18 16:30:00 CET (1584545400) to database 'weewx.sdb'
Mar 18 16:31:34 rpi-weather weewx[1217] INFO weewx.manager: Added record 2020-03-18 16:30:00 CET (1584545400) to daily summary in 'weewx.sdb'
Mar 18 16:31:34 rpi-weather weewx[1217] INFO weewx.engine: Starting main packet loop.
Mar 18 16:31:49 rpi-weather weewx[1217] ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
So that didn't work.
Another stop and start seems to get things running.
Basically the old-database most likely was not writable.
using commandline therefore new values were not written aback and website didn't update
using daemon still see problems related to times I guess which upsets weewx.
How can a RPi loose 6 seonds when not running weewx for maybe 15min
Anyway it works for now.
vince
Mar 18, 2020, 1:10:23 PM3/18/20
to weewx-user
On Wednesday, March 18, 2020 at 9:02:49 AM UTC-7, weerstation Maurik wrote:
How can a RPi loose 6 seonds when not running weewx for maybe 15min
All computers can do this if they are starting to fail.
You should be running ntp or systemd equivalent to keep the clock in sync with reality.
Thomas Keffer
Mar 18, 2020, 2:25:48 PM3/18/20
to weewx-user
In addition to Vince's recommendation:
- you should also set debug=1 in weewx.conf, then restart. It may give you more clues as to what is going on.
- Run the command "dmesg". This will show you if anything is going on with the kernel. Long shot, but worth checking.
- Is your console connected to AC, or running just on batteries? Low batteries can show these symptoms (although the 4.47 V you are seeing is pretty normal).
-tk
--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e10c1057-d745-475d-90e0-03f53dd65a7d%40googlegroups.com.
0 new messages