Re: [weewx-user] Periodic incorrect date from a Davis Vantage Pro 2

[Tom Keffer]

I have never seen the Vantage emit a bad date. What does happen is either

1. The computer lacks a clock, so it synchronizes the Vantage to the wrong
time. There is a check in WeeWX to avoid starting up with a clock that's
really off, but the best protection is to install a real-time clock in the
computer.

2. The logger memory gets corrupted. This is pretty rare, but seems to be
triggered by power outages (although not always). The symptom is that WeeWX
fails to download any new data, so your webpage doesn't change. See the
Wiki article *Wiki generates HTML pages, but does not update them
*
for
details. This sounds the closest to the situation you describe, but with
WeeWX it does not result in a record being downloaded with a bad date.
Perhaps wview does something different in this situation. The problem can
always be solved by clearing the logger memory. If you do a memory dump
first, it does not result in loss of data.

Hope that answers your question.


On Fri, May 10, 2024 at 11:37 AM P Black  wrote:

> Hello,
>
> I am in the process of migrating from wview to weewx.  Yes I know I am
> very late to the game.
>
> The issue I have with wview is that the Davis Vantage Pro 2 periodically
> generates a future date that then hangs any further data collection.  The
> fix usually involves:
>
>  sudo service wview stop
>  vpconfig /dev/ttyUSB0 cleararchive
> remove the bad data from the sqlite and mysql databases
>  sudo service wview start
>
> Then if I am late to catch this issue, I have a lot of missing data.
>
> I plan to start installing weewx in the next few days on a raspberry pi 5
> with a 1TB NVMe and run using the mysql (mariadb) database choice after
> migrating my existing database to the new setup.
>
> Assuming that the date issue is a Davis glitch and not wview, is there a
> software check in weewx to determine if the date is wrong and either delete
> the data for that time or correct it to the correct time and then log?  I
> assume that the clear archive would also have to be automatically performed
> (how is that done by software)
>
> PS: I have tried the usual shutdown the Davis, remove batteries and still
> the bad date occasionally occurs.  The Davis is the wireless version
> purchased 2011.  Also, it must know when I am not around as the bad event
> occurs during my away times.
>
> Stay healthy,
> Pat
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAZgmewZQDDjs1GVLbSZ4CbFi4H0_P%2BK8RMqrKra9kUYA%40mail.gmail.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

jterr...@gmail.com schrieb am Freitag, 10. Mai 2024 um 20:35:20 UTC+2:

One more question : in your csv file,  the maximum values of the sunshine 
duration measured by the Weerhuisje/Instromet sunshine duration sensor , 
for a period of 5 minutes, are 324 seconds , higher than the 300 seconds 
interval. 
How should we interpret all these values ? Scale them proportionally so 
that a value of 324 correspond to a 300 second sunshine ?


The sensor sends a pulse every 36 seconds if the sun shines. 8 pulses are 
288 seconds, 9 pulses are 324 seconds. If the sun shines continuously, 
sometimes you get 8 pulses within one archive interval and sometimes 9. 
That is the reason for those values. So you may add those additional 24 
seconds to the previous or next archive interval.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7eac2de9-d869-451e-b76d-630c9170d955n%40googlegroups.com.

[weewx-user] Periodic incorrect date from a Davis Vantage Pro 2

[P Black]

Hello,

I am in the process of migrating from wview to weewx.  Yes I know I am very 
late to the game.

The issue I have with wview is that the Davis Vantage Pro 2 periodically 
generates a future date that then hangs any further data collection.  The 
fix usually involves:

 sudo service wview stop
 vpconfig /dev/ttyUSB0 cleararchive
remove the bad data from the sqlite and mysql databases
 sudo service wview start

Then if I am late to catch this issue, I have a lot of missing data.

I plan to start installing weewx in the next few days on a raspberry pi 5 
with a 1TB NVMe and run using the mysql (mariadb) database choice after 
migrating my existing database to the new setup.

Assuming that the date issue is a Davis glitch and not wview, is there a 
software check in weewx to determine if the date is wrong and either delete 
the data for that time or correct it to the correct time and then log?  I 
assume that the clear archive would also have to be automatically performed 
(how is that done by software)

PS: I have tried the usual shutdown the Davis, remove batteries and still 
the bad date occasionally occurs.  The Davis is the wireless version 
purchased 2011.  Also, it must know when I am not around as the bad event 
occurs during my away times.

Stay healthy,
Pat

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fe2e2e08-bf5b-4da4-a511-7926ede968afn%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[jterr...@gmail.com]

OK with the solar altitude.
One more question : in your csv file,  the maximum values of the sunshine 
duration measured by the Weerhuisje/Instromet sunshine duration sensor , 
for a period of 5 minutes, are 324 seconds , higher than the 300 seconds 
interval. 
How should we interpret all these values ? Scale them proportionally so 
that a value of 324 correspond to a 300 second sunshine ?

Le vendredi 10 mai 2024 à 20:15:23 UTC+2, Karen K a écrit :

> jterr...@gmail.com schrieb am Freitag, 10. Mai 2024 um 19:49:06 UTC+2:
>
> Karen, thanks. 
> I will do the calculation, and let you know. It will be interesting to 
> have a comparison , but I need some more information , particularly the 
>  latitude and longitude of the place where your sensors are installed. I 
> will send you a private email .
>
>
> I included the actual solar altitude in the file. So you can use it within 
> the calculation.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1c8d81b5-f2ce-435f-81de-b50816b7c45en%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[Karen K]

jterr...@gmail.com schrieb am Freitag, 10. Mai 2024 um 19:49:06 UTC+2:

Karen, thanks. 
I will do the calculation, and let you know. It will be interesting to have 
a comparison , but I need some more information , particularly the 
 latitude and longitude of the place where your sensors are installed. I 
will send you a private email .


I included the actual solar altitude in the file. So you can use it within 
the calculation.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/71e6d7cc-968b-476f-b278-d5dc79b9cab9n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[jterr...@gmail.com]

Karen, thanks. 
I will do the calculation, and let you know. It will be interesting to have 
a comparison , but I need some more information , particularly the 
 latitude and longitude of the place where your sensors are installed. I 
will send you a private email .
Le vendredi 10 mai 2024 à 19:26:46 UTC+2, Karen K a écrit :

> Jacques Terrettaz schrieb am Dienstag, 7. Mai 2024 um 15:26:49 UTC+2:
>
> Karen, except your  Weerhuilje sunhours sensor, do you have with your 
> weather station any global solar irradiance sensor ?  If yes, you could try 
> an alternate calculation of sunshine duration and compare.
>
>
> Unfortunately I cannot do the calculation actually due to lack of time. 
> But I can provide the raw data for you to do it yourself. The columns of 
> the table within the attached file are:
>
>- localTime: timestamp of the end of the measuring interval in local 
>time as text for reference
>- dateTime: timestamp of the end of the measuring interval in seconds 
>since 1.1.1970 0:0:0 UTC (Unix time)
>- radiation: readings of the global irradiance sensor of the Davis 
>weather station in Watt per squared meter
>- sunshineDur: readings of the Weerhuisje/Instromet sunshine duration 
>sensor in seconds per 5 minutes
>- solarAzimuth: solar azimuth in degrees
>- solarAltitude: solar altitude in degrees
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9222b143-9225-40d5-ad75-6a55cc4e976bn%40googlegroups.com.

[weewx-user] Error Reading GW1100

[Mitchell Tuckness]

Hi All,

I could use some help. I have weewx running on Ubuntu and I had an 
electrician out to replace a plug that had overheated. Anyway, after he 
left (we had to shut power off to the  area he worked on) I noticed that 
the webpage wasns't doing the live updates for the weather. I checked 
everything I could to see if it was hardware was unplugged, or shut off, 
but I havent seen anything. So I thought maybe the GW100 gateway was having 
issues and I had purchased a GW1100 gateway a while ago, so I hooked it up 
and configured it. 

I can login to the Gw1100 and it sees all the sensors, but I am getting 
errors from the WEEWX server. I could use some help diagnosing this. It has 
been a while since I created the website and while I remember some, I don't 
remember it all. Appreciate it! Here is some of the errors from the syslog:

May 10 08:22:51 weewx-pi weewx[1657] INFO __main__: retrying...
May 10 08:22:51 weewx-pi weewx[1657] DEBUG __main__: Initializing engine
May 10 08:22:51 weewx-pi weewx[1657] INFO weewx.engine: Loading station 
type GW1000 (user.gw1000)
May 10 08:22:53 weewx-pi weewx[1657] DEBUG user.gw1000: Failed to obtain 
response to attempt 1 to send command 'CMD_READ 
_STATION_MAC': timed out
May 10 08:23:05 weewx-pi weewx[1657] DEBUG user.gw1000: Failed to obtain 
response to attempt 2 to send command 'CMD_READ_STATION_MAC': timed out
May 10 08:23:17 weewx-pi weewx[1657] DEBUG user.gw1000: Failed to obtain 
response to attempt 3 to send command 'CMD_READ_STATION_MAC': timed out
May 10 08:23:17 weewx-pi weewx[1657] ERROR user.gw1000: Failed to obtain 
response to command 'CMD_READ_STATION_MAC' after 3 attempts
May 10 08:23:17 weewx-pi weewx[1657] ERROR weewx.engine: Import of driver 
failed: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 
attempts ()
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 Traceback (most recent call last):
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/weewx/engine.py", line 119, in setupStation
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 1598, in loader
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 return GatewayDriver(**config_dict[DRIVER_NAME])
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 2038, in __init__
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 super(GatewayDriver, self).__init__(**stn_dict)
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 872, in __init__
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 self.collector = GatewayCollector(ip_address=self.ip_address,
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 2428, in __init__
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 self.station = GatewayCollector.Station(ip_address=ip_address,
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 2966, in __init__
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 self.mac = self.get_mac_address()
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 3358, in get_mac_address
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 return self.send_cmd_with_retries('CMD_READ_STATION_MAC')
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:    
 File "/home/weewx/bin/user/gw1000.py", line 3556, in send_cmd_with_retries
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 raise GWIOError(_msg)
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL weewx.engine:  
 user.gw1000.GWIOError: Failed to obtain response to command 
'CMD_READ_STATION_MAC' after 3 attempts
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL __main__: Unable to load 
driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 
attempts
May 10 08:23:17 weewx-pi weewx[1657] CRITICAL __main__:   Waiting 
60 seconds then retrying...

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7eda5c4c-02c3-481a-96a3-3cc233b167d6n%40googlegroups.com.