But then I don't get what the underlying problem is. Two diffrent consoles, 
same problem?

torsdag den 11. november 2021 kl. 12.13.09 UTC+1 skrev gjr80:

> Setting record_generation to hardware does not cure the corrupt station 
> memory, rather it mitigates the symptoms. The underlying problem is still 
> there, though it will now largely have no day to day effect on WeeWX 
> operation. However, you should be aware that while the corrupt station 
> memory remains you will no longer have the ability to backfill missing 
> archive records from your station should WeeWX go offline for some reason.
>
> Gary
>
> On Thursday, 11 November 2021 at 20:32:36 UTC+10 [email protected] wrote:
>
>>
>> wee_device --clear-memory:
>> ...
>> raise weewx.WeeWxIOError("Unable to read hardware type")
>> weewx.WeeWxIOError: Unable to read hardware type
>>
>> I don't understand why this happens. I even tried to use another console, 
>> same problem.
>>
>> Then, as sugested option, I used:
>>
>> [StdArchive]
>>     ...
>>     record_generation = software
>>
>> - and this worked, thanks.
>>
>> torsdag den 11. november 2021 kl. 10.04.18 UTC+1 skrev gjr80:
>>
>>> No errors but what is missing is WeeWX is not obtaining any archive 
>>> records from you console. You have all the symptoms of corrupt station 
>>> memory. I suggest you refer to the Troubleshooting the Davis Vantage 
>>> station 
>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station>
>>>  
>>> wiki page and work through the steps in the Corrupt station memory 
>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>
>>>  section.
>>>
>>> Gary
>>> On Thursday, 11 November 2021 at 18:35:01 UTC+10 [email protected] 
>>> wrote:
>>>
>>>> Debug = 1
>>>> Apparently no errors?
>>>> torsdag den 11. november 2021 kl. 07.47.56 UTC+1 skrev gjr80:
>>>>
>>>>> Thanks but that log extract is not much use at all. We need to see a 
>>>>> log extract showing the WeeWX startup and processing at least a couple of 
>>>>> report cycles. I suggest you go to the link in my first post next work 
>>>>> through the steps under ‘To get a good, useful log’ and post the 
>>>>> resulting 
>>>>> log.
>>>>>
>>>>> Gary
>>>>> On Thursday, 11 November 2021 at 16:04:44 UTC+10 [email protected] 
>>>>> wrote:
>>>>>
>>>>>> Nov 11 07:00:17 jjk-F5RL weewx[10103]: cheetahgenerator: Generated 3 
>>>>>> files for report StandardReport in 0.07 seconds
>>>>>> Nov 11 07:00:18 jjk-F5RL weewx[10103]: imagegenerator: Generated 24 
>>>>>> images for StandardReport in 1.69 seconds
>>>>>> Nov 11 07:00:18 jjk-F5RL weewx[10103]: copygenerator: copied 14 files 
>>>>>> to /home/weewx/public_html
>>>>>> Nov 11 07:00:20 jjk-F5RL weewx[10103]: ftpgenerator: ftp'd 41 files 
>>>>>> in 2.05 seconds
>>>>>>
>>>>>> Tried to stop and start weewx, delete all files from public_html - no 
>>>>>> change.
>>>>>>
>>>>>> torsdag den 11. november 2021 kl. 06.33.16 UTC+1 skrev gjr80:
>>>>>>
>>>>>>> I suggest we start with the log 
>>>>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>, 
>>>>>>> you don’t need an error in the log to diagnose a problem
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>> On Thursday, 11 November 2021 at 15:19:03 UTC+10 [email protected] 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Suddenly, 11 days ago, weewx keeps generating same images over and 
>>>>>>>> over. No error in syslog, wee_device says: weewx.WakeupError: Unable 
>>>>>>>> to 
>>>>>>>> wake up Vantage console.
>>>>>>>> I tried to unplug the console, no change, even switched to another 
>>>>>>>> console, no change.
>>>>>>>> ?
>>>>>>>>
>>>>>>>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/072bcc96-2287-4b66-94b9-5b65218b4519n%40googlegroups.com.

Reply via email to