Hello Weewx Community,
I've been running weewx since the 3.7 builds and just upgraded to 3.9.2.
Since the 3.8 builds (don't remember which one), I've noticed that every
once in awhile reports stop getting generated and then will begin working
some time later. Upon closer inspection, in
Hi Rich,
Both transmitters work with the same sets of frequencies, so it is likely they
both fail or succeed at a given frequency.
It is a good idea to start a tread in weewx-development, which I just did, so
we can continue from there.
Luc
--
You received this message because you are
Luc
The approach sounds like a good way to proceed. Currently running option
-tr 3 and receiving the same results. Do you think we should move this to
weewx-development group?
Rich
On Wednesday, March 13, 2019 at 7:10:21 PM UTC-4, Luc Heijst wrote:
> Hi Rich,
>
> We need another approach.
On Wednesday, March 13, 2019 at 2:15:09 PM UTC-7, pete...@gmail.com wrote:
>
> Thank you for your answer again. I will have to get used to weewx to full
> understand what I need to do. Right now, my weewx.conf uses the patches
> from the AS3935 configuration and should generate (right?) a new
>
I would like to correct the rain of the same day but making sure that the
rain gradually recounts me.
As an example, today 15/03/2019 the weather station has not scored 10mm of
rain on a total of 20mm, what should I do to correct this value?
But above all if it continues to rain, is it added to
Hi Rich,
We need another approach. As I said before, the frequencies of RFM69 didn’t
work for my EU transmitter either.
Note: the lowest and highest frequencies in the RFM69 table were not modified
by me, so that can’t be a cause here.
I plan to write a testprogram as follows.
1. Start with a
Hi Luc
I re-compiled the code with the frequencies you provided and here is what I
get:
pi@raspberrypi:~/work/src/github.com/lheijst/rtldavis $
$GOPATH/bin/rtldavis -tf US
17:53:20.344708 rtldavis.go VERSION=0.7
17:53:20.345197 tr=1 actChan=[0] maxChan=1 *transmitterId=0 msgIdToChan=[0
9 9 9
Thank you for your answer again. I will have to get used to weewx to full
understand what I need to do. Right now, my weewx.conf uses the patches
from the AS3935 configuration and should generate (right?) a new
lightning.sdb database. The sensor_map contains:
[WeatherFlowUDP]
driver =
On Wednesday, March 13, 2019 at 1:34:38 PM UTC-7, pete...@gmail.com wrote:
> I've installed the WF UDP driver and am getting data into weewx OK. For
> the start, I have 3 questions:
>
>1. My plots (temperature, humidity, barometer, etc.) do not show any
>labels nor axis labels. I've
Item 1 resolved.
Dne sreda, 13. marec 2019 21.34.38 UTC+1 je oseba pete...@gmail.com
napisala:
>
> Hi,
> I'm the new weewx user having no experience with weewx before.
>
> My system:
>
>- Raspberry Pi 3 B+
>- WeatherFlow station
>- neowx skin
>
> I've installed the WF UDP driver
Hi,
I'm the new weewx user having no experience with weewx before.
My system:
- Raspberry Pi 3 B+
- WeatherFlow station
- neowx skin
I've installed the WF UDP driver and am getting data into weewx OK. For the
start, I have 3 questions:
1. My plots (temperature, humidity,
Hi Jacques
>
>
They're in differents machines. VVP is running on a Windows 10 computer in
the same local network (192.168.1.xxx) that orange pi is running weewx.
I'm gonna test with Cumulus MX on the orange pi in a different TCP/IP port
to see if it also loses connection to VVP at the same
It works fine now. Feel free to delete this issue in github unless you want
to add this group to your skin.
Thanks!
On Wednesday, March 13, 2019 at 2:43:02 PM UTC-3, HoracioDos wrote:
>
> I didn't read this message. I knew that some group was missing. I going to
> try it and report back.
>
>
Rich,
You can read both transmitters simultanious with option -tr 3.
AFAIK, the Davis console (and the weewx Vantage driver) won’t show the UV data
when it is not coming from the same transmitter as the ISS.
Anyhow, the rtldavis driver will read the data. I have my solar sensor mounted
on
I didn't read this message. I knew that some group was missing. I going to
try it and report back.
On Tuesday, March 12, 2019 at 9:45:50 PM UTC-3, Pat wrote:
>
> Horacio, I had to ask for help with this one. As mentioned in Tom's
> response
>
On Wednesday, March 13, 2019 at 7:29:21 AM UTC-7, David Beach wrote:
> I seem to recall that Raspian, if stripped of fake-hwclock, etc., does NOT
> start up with the universal Linux Jan 1970 date but uses a date that
> corresponds to the release date of that version of Raspian. This means
>
On Wednesday, March 13, 2019 at 11:03:43 AM UTC-4, V. Kelly Bellis wrote:
>
>
> Mar 13 10:30:17 raspberrypi weewx[2614]: forecast: XTideThread: XTide: got
> no tidal events
> Mar 13 10:30:17 raspberrypi weewx[2614]: forecast: XTideThread: XTide:
> generate forecast failed: XTide Error:
Oh.
I'm afraid that I cannot help you. The problem is almost surely related to
VVP --- something I know nothing about.
On Wed, Mar 13, 2019 at 8:27 AM jmviper wrote:
> VirtualVP is an application that is collecting data from a Davis vantage
> console and let communications through Virtual COM
VirtualVP is an application that is collecting data from a Davis vantage
console and let communications through Virtual COM Ports or TCP/IP with
several weather programs like weewx.
>
>
Webpage:
http://www.softwx.com/weather/virtualvp.html
I think a lot of people uses it to have more than one
://flaterco.com/files/xtide/XTide%20v2.15.2%20Help%20b20190309.chm)
20190312 Examined /var/log/syslog and discovered xtide STATION_NOT_FOUND
errors
20190313 Examined /usr/bin/ and discovered tide v2.13.2 was not removed(!)
- manually removed - and left wondering what other lingering bits could
VVP is how I call Virtual VP ... Sorry for the inconvenience :)
--
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.
For more
I do not know what "VVP" is. Some sort of VPN?
-tk
On Wed, Mar 13, 2019 at 6:40 AM jmviper wrote:
>
> I've already tried loop_on_init (searching for answers before) and
> effectively it didn't fix the problem.
> I know that the problem is related to VVP cause though weewx is trying to
>
Someone who is a Raspian expert can correct me on this if I'm wrong:
I seem to recall that Raspian, if stripped of fake-hwclock, etc., does NOT
start up with the universal Linux Jan 1970 date but uses a date that
corresponds to the release date of that version of Raspian. This means
that
I've been a fan of chrony.
Hasn't been a problem on any system I've installed it on, easier (for me)
to configure and monitor.
--
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
I've already tried loop_on_init (searching for answers before) and
effectively it didn't fix the problem.
I know that the problem is related to VVP cause though weewx is trying to
communicate with IP machine in which runs VVP it is still sending loops
(without asking for them weewx who is
Seems like I may not be upgrading. I have to point out that even after
switching back to 11rc3 the memory growth is still there albeit slower. I
guess I did not notice it before as the failure occurred over a longer
period of time than what happened when a different driver was installed
after
Thanks.
Normally, when a persistent error occurs in the driver, WeeWX restarts from
the top. The exception is that restart itself --- if the WeeWX engine
cannot load the driver at all, it exits, the theory being that there is a
configuration problem.
If you are confident that the driver has been
Mar 13 06:25:15 localhost weewx[29634]: cheetahgenerator: Generated 9 files
for report StandardReport in 2.67 seconds
Mar 13 06:25:17 localhost weewx[29634]: imagegenerator: Generated 12 images
for StandardReport in 2.02 seconds
Mar 13 06:25:17 localhost weewx[29634]: copygenerator: copied 0
Please include the system log from when you had this error. WeeWX should
have restarted itself.
On Wed, Mar 13, 2019 at 12:19 AM jmviper wrote:
> Hi
>
> I've got weewx running through VVP IP/TCP connection in a local network
> and works fine but sometimes (when there's a problem with the local
Luc
Will use the frequencies you provided tonight when I get back into the
area. My ISS is located approximately 50 feet from the console and is set
as Id 0. Only additional sensor I have is the UV sensor, which I just
recently added.
Rich
--
You received this message because you are
I forgot to tell one more thing about the frequencies. In the RFM69 table the
frequencies are sorted in the sequence they are transmitted.
In the rtldavis program the frequencies are sorted from low to high and the
frequency order used for the hopping comes from the hop table.
Hi
I've got weewx running through VVP IP/TCP connection in a local network and
works fine but sometimes (when there's a problem with the local router) Weewx
exits with Vantage: ip-read error: Timed out Unable to wake up console. I see
at that moment VVP and is still sending loops and the only
As the ID of the second station is 1, it could be from an anemometer kit.
I, for example, have set my ISS to 0, my anemometer station to 1, and my
leaf-soil station to 2.
But a reception range of 2 miles? It’s way above Davis specifications!
--
You received this message because you are
Rich,
FSTEP = 32MHz / (2^19) = 61.xxx Hz. So the formula is: freq from table *
61.xxx
After translating the table I did another step. I calculated the difference
between each two frequencies. As they were close to each other, but all
different, I thought the frequencies might differ each
34 matches
Mail list logo
