Hi again,

Lost contact with my station and will not have possibility to check it out 
before end of August.
I have had similar incidents over the past year. I swapped the RPi to the 
latest version some 6 months ago and it seemed to work for a while.
How likely is it that the station memory is corrupt beyond repair?
I have tried powering off the console a number of times and I have cleared 
the station memory. This seems to have fixed the issue for a short period 
of time.
Real time clock on the RPi might be my next attempt unless it is likely 
that the station is corrupt beyond repair :-(

Rune.

torsdag 2. august 2018 02.51.50 UTC+2 skrev gjr80 følgende:
>
> Hi Rune,
>
> My apologies I did forget you, an internet outage for a couple of days and 
> by that time your post had dropped down the list. No excuse though.
>
> Having a look at your log I suspect you may have corrupt station memory. 
> If you look down the log around 17:00 25 July you will see that no archive 
> records are being read from the station and consequently no archive records 
> are being saved to database. Have a look at the Corrupt station memory 
> <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated> 
> section in the User's Guide. There are a couple of suggested fixes there, 
> first try fix 1., power off to the console. Restart WeeWX and see if it 
> runs error free. If you still have the same errors try using the Dump the 
> logger memory 
> <http://weewx.com/docs/hardware.htm#vantage_dumping_the_logger_memory>, 
> this won't fix the problem but it might help prevent loss of data when we 
> do the next step. Once you have dumped the logger memory try fix 2., clear 
> the console memory. Again restart WeeWX and see how it goes.
>
> One other thing you might consider is a real time clock for your RPi or 
> failing that delaying the WeeWX start until NTP has properly sync'd your 
> clock. There are couple of instances of the station clock being reset in 
> the log you posted, probably did not cause the issue you currently have but 
> it can cause issues for WeeWX. If you don't go down the realtime clock path 
> there are a number of threads in the forums on delaying the WeeWX startup, 
> one only last month or so I think.
>
> Let us know how you go.
>
> Gary
>
> On Wednesday, 1 August 2018 18:19:02 UTC+10, Rune Lægreid wrote:
>>
>> Hi Gary,
>>
>> Did you have time to look at the logs?
>>
>> Rune.
>>
>> mandag 23. juli 2018 14.35.35 UTC+2 skrev gjr80 følgende:
>>>
>>> Hi Rune,
>>>
>>> You will usually find the WeeWX log entries in /var/log/syslog unless 
>>> you have modified your install to put WeeWX log entries in another file 
>>> (/var/log/weewx.log is commonly used). What we are after is at least a 
>>> couple of cycles of saving a record to database and running the report 
>>> suite.
>>>
>>> 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.

Reply via email to