Hi, On Saturday, 23 February 2019 14:35:53 UTC+10, Mohamed Al-Sabri wrote:Ouh > OK now I understand the interval thing! > How do I know that I’m running two instances? I’m not sure how to kill one > of them or which one I kill in order to get the data. >
This part of your log extract shows two different processes (1393 and 1338) trying to communicate with you station, it happens if you start WeeWX again with stopping it first or doing a restart: Feb 22 20:45:10 raspberrypi weewx[1393]: engine: Starting up weewx version 3.9.1 Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Gentle wake up of console successful Feb 22 20:45:10 raspberrypi weewx[1393]: manager: Daily summary version is 2.0 Feb 22 20:45:10 raspberrypi weewx[1393]: manager: Daily summary version is 2.0 Feb 22 20:45:10 raspberrypi weewx[1393]: engine: Clock error is -0.09 seconds (positive is fast) Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Getting archive packets since 2017-01-24 04:00:00 +04 (1485216000) Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Gentle wake up of console successful Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Retrieving 138 page(s); starting index= 0 Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: DMPAFT complete: page timestamp 2017-01-23 12:00:00 +04 (1485158400) less than final timestamp 2017-01-24 04:00:00 +04 (1485216000) Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Catch up complete. Feb 22 20:45:10 raspberrypi weewx[1393]: engine: Starting main packet loop. Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Gentle wake up of console successful Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Requesting 200 LOOP packets. Feb 22 20:45:10 raspberrypi weewx[1393]: vantage: Gentle wake up of console successful Feb 22 20:46:00 raspberrypi weewx[1338]: engine: retrying... Feb 22 20:46:00 raspberrypi weewx[1338]: engine: Using configuration file / home/weewx/weewx.conf Feb 22 20:46:00 raspberrypi weewx[1338]: engine: Debug is 1 Feb 22 20:46:00 raspberrypi weewx[1338]: engine: Initializing engine Feb 22 20:46:00 raspberrypi weewx[1338]: engine: Loading station type Vantage (weewx.drivers.vantage) Feb 22 20:46:00 raspberrypi weewx[1338]: vantage: Driver version is 3.1.1 Feb 22 20:46:00 raspberrypi weewx[1338]: vantage: Opened up serial port /dev /ttyUSB0; baud 19200; timeout 4.00 Feb 22 20:46:00 raspberrypi weewx[1338]: vantage: Gentle wake up of console successful Feb 22 20:46:04 raspberrypi weewx[1393]: vantage: LOOP try #1; error: Expected to read 99 chars; got 2 instead Feb 22 20:46:04 raspberrypi weewx[1393]: vantage: Requesting 200 LOOP packets. Feb 22 20:46:04 raspberrypi weewx[1393]: vantage: Gentle wake up of console successful Feb 22 20:46:04 raspberrypi weewx[1338]: vantage: No <ACK> received from console Feb 22 20:46:04 raspberrypi weewx[1338]: vantage: _determine_hardware; retry #0 Feb 22 20:46:04 raspberrypi weewx[1338]: vantage: Hardware type is 76 Feb 22 20:46:04 raspberrypi weewx[1338]: vantage: No <ACK> received from console To kill one of them use: $ sudo kill -9 PID where PID is the process ID, in this case 1338 or 1393. I would kill the latter one 1393. You also have a few other issues. Whilst WeeWX is clearly communicating with your console it seems to have regular problems in obtaining loop packets from your console: Feb 22 20:21:34 raspberrypi weewx[711]: vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead Feb 22 20:21:34 raspberrypi weewx[711]: vantage: Requesting 200 LOOP packets . Feb 22 20:21:34 raspberrypi weewx[711]: vantage: Rude wake up of console successful Feb 22 20:21:38 raspberrypi dhcpcd[514]: wlan0: no IPv6 Routers available Feb 22 20:21:38 raspberrypi weewx[711]: vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead Feb 22 20:21:38 raspberrypi weewx[711]: vantage: Requesting 200 LOOP packets . Feb 22 20:21:38 raspberrypi weewx[711]: vantage: Rude wake up of console successful It may be these errors are due to the undervoltage issue you have or maybe it it something else. I would make sure you deal with the undervoltage issue though. I owudl also make sure your logger is properly seated in the back of the console. As you are aware you also have an archive period mismatch, that in itself does not cause a problem as in your case WeeWX will default to hardware archive interval (30 minutes). If you wish to retain a 30 minute archive interval then you might want to change archive_interval under [StdArchive] in weewx.conf to 1800, if nothing else it silences that warning. Of course if you do want a 5 minute archive interval then you need to set the archive interval in the console either through the panel buttons or with wee_device. If using wee_device you need to stop WeeWX first (all instances in your case) - only one program can communicate with the console at once. As changing the archive interval on the console or with wee_device will clear the logger you might like to use wee_device --dump first to obtain any archive records in the logger but not in your archive before the logger is cleared. These archive records will be 30 minutes apart not 5 minutes. Up to you if you want them or not. Remember WeeWX must be stopped before running wee_device. Once your archive interval is set to your liking, and given the communications problems you have had with your console, I would clear the logger with wee_device --clear. If you did not previously do a --dump because you retained the 30 minute archive interval then I woudl do a --dump before doing the --clear. Once this is all done restart WeeWX and let it run for at least an archvie interval or two. It makes life difficult to analyse the logs in a meaningful way when WeeWX is never allowed ot run through a full archive interval. If after a couple of archive intervals things are still not working post a log extract from when you started WeeWX showing a least two archive intervals of log entries. Gary -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
