cause the read errors on the vp2, so is off-topic, but
> worth pointing out.
> cheers
>
>
> On 18 Jun 2022, at 2:23 pm, mup...@gmail.com wrote:
>
> The archive interval in the configuration file (300) does not match the
> station hardware interval (1800)
>
>
Hello Graham,
Can you enlighten me just a bit more? Where is the "config error"?
Thank you!
On Friday, June 17, 2022 at 7:20:46 PM UTC-7 Graham Eddy wrote:
> not the reported problem, but config error needs to be fixed nonetheless
>
>
> On 18 Jun 2022, at 1:14 am, m
wiki section
> *Corrupt
> station memory
> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>?*
>
>
> On Fri, Jun 17, 2022 at 2:54 PM mup...@gmail.com wrote:
>
>> I did change back to hardware record generation.
>&g
t; <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory>*
> .
>
>
>
>
>
> On Fri, Jun 17, 2022 at 9:14 AM mup...@gmail.com wrote:
>
>> Thank you for your response.
>> I have set debug=1. I had tried cha
reason why you are using software record generation?
>
> -tk
>
> On Thu, Jun 16, 2022 at 6:49 PM mup...@gmail.com wrote:
>
>> Hello,
>> Just checked my log to see how things were operating and found this:
>>
>> Jun 16 17:45:20 weewx-RPi weewx[76976] ERROR weewx.d
Hello,
Just checked my log to see how things were operating and found this:
Jun 16 17:45:20 weewx-RPi weewx[76976] ERROR weewx.drivers.vantage: LOOP
max tries (4) exceeded.
Jun 16 17:45:20 weewx-RPi weewx[76976] INFO weewx.engine: Main loop
exiting. Shutting engine down.
Jun 16 17:45:20
PM UTC-7 mup...@gmail.com wrote:
>
> Just took an installation that used the deb file and changed the
> /etc/weewx/weewx.conf to reflect /dev/ttyS0.
> I no longer get the data spitting out to the console as before.
> What I do see is lots of data coming out of sudo tail -f
you used
> /dev/ttyS0 ?
>
> Perhaps you might capture the "bunch of data being spit out" and share it
> with us, because it sure sounds like it's working as expected.
>
>
> On Thursday, June 9, 2022 at 2:43:15 PM UTC-7 mup...@gmail.com wrote:
>
>> Update:
>&
Update:
I am becoming more certain that the issue I'm having is with the ability to
get the serial ports configured properly on a Pi 4.
Any recommendations would be welcomed.
Thank you!
Michael
On Wednesday, June 8, 2022 at 12:31:27 PM UTC-7 mup...@gmail.com wrote:
> Meant to post this to
Meant to post this to all!
Got through the installation process and populated my info in the
weewx.conf file. The issue now appears to be one with the serial port
selection.
Using /dev/ttyS0, the result is a bunch of data being spit out to my
screen, which doesn't appear to be where it should
Thank you Vince and Gary for your replies.
Vince: I am using the quickstart guide you reference, even thought it
references the Buster distro rather than the Bullseye distro. I found that
using Buster, I continuously ended up with 'configobj' problems. Using
Bullseye, that is no longer an
Getting the following error when running for the first time:
weewx@weewx-RPi:~/weewx-4.8.0 $ sudo ./bin/weewxd
Traceback (most recent call last):
File "/home/weewx/weewx-4.8.0/./bin/weewxd", line 248, in
main()
File "/home/weewx/weewx-4.8.0/./bin/weewxd", line 147, in main
engine =
Hello,
I decided to upgrade my Weewx system to a Pi4 from the Pi original and have
hit nothing but hiccups! I've checked my cabling; found a broken wire and
corrected it.
Here is my log file showing the problem:
Jun 4 16:40:17 weewx-pi systemd[1]: Starting weewx weather system...
Jun 4
Has someone worked out a cron job that will periodically check to see that
weewx is running and issue a restart if it is not?
I have been getting notified (email) about once per week letting me know
that weewx stopped sending data.
On Thursday, November 25, 2021 at 12:57:32 PM UTC-8 Clyde
14 matches
Mail list logo
