Been using weewx-rtldavis for a few weeks now and I'm super happy with the performance. I receive the data from a Davis Vantage Vue ISS only. However, there are a few things that I cannot figure out
- The fraction of missed packages/good packages is not saved into the database: pct_good_0 to _4 are all nulls... why? - In order to save data from my BME280 I had to comment the lines for inTemp and inHumidity in DEFAULT_SENSOR_MAP. Is that normal? On Monday, October 18, 2021 at 10:28:58 PM UTC+2 [email protected] wrote: > Rain data. > I am running the RTL-SDR program Luc set up on a Raspberry Pi 3 B with the > Nooelec > NESDR Smart v4 Bundle SDR. I am comparing it to a Raspberry Pi 3 B using a > RFM-69 receiver. > > Everything was working nicely until yesterday which was a sunny rainless > day. The SDR setup reported 3.84" of rain with the current conditions graph > showing two periods of approximately 1.3" - There was no rain, the RFM-69 > setup showed no rain (so the data didn't come from the Davis ISS) so I was > wondering if anyone has run across something like this and if there is a > fix? > > On Sunday, April 11, 2021 at 11:50:38 PM UTC-6 [email protected] wrote: > >> >> In the [StdQC] section set: >> UV = 100,101 # any other value of UV will be set to None >> Op maandag 12 april 2021 om 00:06:13 UTC-3 schreef [email protected]: >> >>> No obvious foreign objects/debris, just some (what I believe to be) >>> dielectric grease. I did pull off the PCB cover and notice that my supercap >>> is bad, so I'll be replacing that. >>> >>> I also noticed that my console is displaying a UV index of 16, so I >>> think there's a problem with the ISS, I'll get in touch with Davis >>> Instruments. >>> >>> In the meantime, what's the best way to stop logging the UV data? >>> >>> [image: IMG_5523.HEIC][image: IMG_5522.HEIC][image: IMG_5521.HEIC][image: >>> IMG_5519.HEIC] >>> >>> Cheers, >>> --a >>> >>> >>> On Sun, Apr 11, 2021 at 1:06 PM Lucas Heijst <[email protected]> wrote: >>> >>>> Strange! Could you check the UV connector in your ISS? Maybe there are >>>> spiders or bugs there which mess up the readings. >>>> >>>> Op zondag 11 april 2021 om 16:14:13 UTC-3 schreef [email protected]: >>>> >>>>> One more question: >>>>> >>>>> I noticed that I’m logging UV data, which is not a sensor that I have. >>>>> I don’t quite have enough data to infer any correlations, but it does >>>>> seem >>>>> to be somewhat correlated with daytime. Any ideas what this might be? >>>>> I've >>>>> attached some logs. Is this useful data that I could be logging by >>>>> changing >>>>> the sensor map, or should I just tell weewx.conf that I don't have a UV >>>>> sensor? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, Apr 9, 2021 at 19:49 [email protected] <[email protected]> >>>>> wrote: >>>>> >>>>>> I use the following driver: https://gitlab.com/wjcarpenter/bme280wx >>>>>> >>>>>> On Friday, April 9, 2021 at 10:22:36 PM UTC-4 [email protected] >>>>>> wrote: >>>>>> >>>>>>> Perfect, thank you. I was just googling around for something like >>>>>>> this. >>>>>>> >>>>>>> On Fri, Apr 9, 2021 at 19:15 [email protected] <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> You can use a BME280 sensor for the pressure. Here is one I use: >>>>>>>> https://www.amazon.com/Adafruit-BME280-Temperature-Humidity-Pressure/dp/B013W1AJUY/ref=sr_1_7?dchild=1&keywords=bme280&qid=1618020646&sr=8-7 >>>>>>>> >>>>>>>> >>>>>>>> I been using this driver for a couple of years without any issues >>>>>>>> on one of my RPIs. >>>>>>>> >>>>>>>> On Friday, April 9, 2021 at 3:57:59 PM UTC-4 [email protected] >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Well that would certainly do it. Thank you for your help! >>>>>>>>> >>>>>>>>> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> The pressure sensor is in the Davis console; you can’t read this >>>>>>>>>> data with this driver. >>>>>>>>>> >>>>>>>>>> Op vrijdag 9 april 2021 om 16:06:21 UTC-3 schreef >>>>>>>>>> [email protected]: >>>>>>>>>> >>>>>>>>>>> Hi Luc, >>>>>>>>>>> >>>>>>>>>>> Ok I took a look at the weewx web interface and it does look >>>>>>>>>>> like it's receiving data, which is good! I had not checked before >>>>>>>>>>> because I >>>>>>>>>>> thought the driver was not working. It's just this that fails: >>>>>>>>>>> >>>>>>>>>>> pi@wxpi:~ $ sudo PYTHONPATH=/usr/share/weewx python3 >>>>>>>>>>> /usr/share/weewx/user/rtldavis.py --cmd="/home/pi/work/bin/rtldavis >>>>>>>>>>> --tf US" >>>>>>>>>>> >>>>>>>>>>> Weewx itself seems fine though, no errors in the logs. >>>>>>>>>>> >>>>>>>>>>> Not a big deal for me, but if you would like to continue >>>>>>>>>>> troubleshooting the driver I am happy to help. >>>>>>>>>>> >>>>>>>>>>> Unrelated (?) question. I don't seem to be getting any pressure >>>>>>>>>>> data. Station is a Vantage Pro 2. Maybe the loop period needs to be >>>>>>>>>>> longer? >>>>>>>>>>> Happy to attach some data if that is helpful. >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> --a >>>>>>>>>>> >>>>>>>>>>> On Fri, Apr 9, 2021 at 4:37 AM Lucas Heijst <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Arlen, >>>>>>>>>>>> >>>>>>>>>>>> Running weewx directly seems to be broken. I have to look at >>>>>>>>>>>> that. >>>>>>>>>>>> Please set debug=1 in weewx.conf and run weewx as a daemon. >>>>>>>>>>>> Then send the log file from start till the first error. >>>>>>>>>>>> >>>>>>>>>>>> Op vrijdag 9 april 2021 om 03:53:36 UTC-3 schreef >>>>>>>>>>>> [email protected]: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Luc, >>>>>>>>>>>>> >>>>>>>>>>>>> Sorry for the thread necromancy but I'm not really sure what >>>>>>>>>>>>> the norms are around starting new threads or opening github >>>>>>>>>>>>> issues. I'm >>>>>>>>>>>>> having the same issue as uvedhe, but I believe that I am getting >>>>>>>>>>>>> data, it >>>>>>>>>>>>> just takes a while. >>>>>>>>>>>>> >>>>>>>>>>>>> For example, here's what happens when I run rtldavis directly >>>>>>>>>>>>> >>>>>>>>>>>>> pi@wxpi:/ $ $GOPATH/bin/rtldavis -tf US >>>>>>>>>>>>> 23:31:41.484368 rtldavis.go VERSION=0.15 >>>>>>>>>>>>> 23:31:41.485107 tr=1 fc=0 ppm=0 gain=0 maxmissed=51 ex=0 >>>>>>>>>>>>> receiveWindow=300 actChan=[0] maxChan=1 >>>>>>>>>>>>> 23:31:41.485224 undefined=false verbose=false disableAfc=false >>>>>>>>>>>>> deviceString=0 >>>>>>>>>>>>> 23:31:41.486233 BitRate: 19200 >>>>>>>>>>>>> 23:31:41.486286 SymbolLength: 14 >>>>>>>>>>>>> 23:31:41.486329 SampleRate: 268800 >>>>>>>>>>>>> 23:31:41.486366 Preamble: 1100101110001001 >>>>>>>>>>>>> 23:31:41.486403 PreambleSymbols: 16 >>>>>>>>>>>>> 23:31:41.486439 PreambleLength: 224 >>>>>>>>>>>>> 23:31:41.486479 PacketSymbols: 80 >>>>>>>>>>>>> 23:31:41.486517 PacketLength: 1120 >>>>>>>>>>>>> 23:31:41.486553 BlockSize: 512 >>>>>>>>>>>>> 23:31:41.486589 BufferLength: 2048 >>>>>>>>>>>>> Found Rafael Micro R820T tuner >>>>>>>>>>>>> 23:31:41.926203 Hop: {ChannelIdx:0 ChannelFreq:902419338 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> Exact sample rate is: 268800.001367 Hz >>>>>>>>>>>>> 23:31:42.103009 GetTunerGain: 0 Db >>>>>>>>>>>>> 23:31:42.103037 SetFreqCorrection 0 ppm Successful >>>>>>>>>>>>> Allocating 1 zero-copy buffers >>>>>>>>>>>>> 23:31:42.106932 Init channels: wait max 135 seconds for a >>>>>>>>>>>>> message of each transmitter >>>>>>>>>>>>> 23:32:52.437316 TRANSMITTER 0 SEEN >>>>>>>>>>>>> 23:32:52.437491 Hop: {ChannelIdx:19 ChannelFreq:911952597 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:32:54.999338 600557FFC100B25F 2 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:32:54.999764 Hop: {ChannelIdx:41 ChannelFreq:922991108 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:32:57.561300 80055C206900FA0A 3 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:32:57.561605 Hop: {ChannelIdx:25 ChannelFreq:914963100 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:33:00.124869 E0045C800300563E 4 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:33:00.125445 Hop: {ChannelIdx:8 ChannelFreq:906433342 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:33:02.686749 500359FF73008A63 5 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:33:02.686858 Hop: {ChannelIdx:47 ChannelFreq:926001611 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:33:05.248703 400358FD0100E608 6 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:33:05.248811 Hop: {ChannelIdx:32 ChannelFreq:918475353 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:33:07.812769 800456205B005B07 7 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:33:07.812888 Hop: {ChannelIdx:13 ChannelFreq:908942094 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:33:10.374274 E00362800300BF59 8 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> 23:33:10.374381 Hop: {ChannelIdx:36 ChannelFreq:920482355 >>>>>>>>>>>>> FreqError:0 Transmitter:0} >>>>>>>>>>>>> 23:33:12.936296 500458FF7100FD61 9 0 0 0 0 msg.ID=0 >>>>>>>>>>>>> >>>>>>>>>>>>> As you can see, it takes >60s to start parsing data. When I >>>>>>>>>>>>> try to run the weewx driver, it crashes after ~10s >>>>>>>>>>>>> >>>>>>>>>>>>> 23:19:53.355369 Init channels: wait max 135 seconds for a >>>>>>>>>>>>> message of each transmitter >>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>> File "/usr/share/weewx/user/rtldavis.py", line 1407, in >>>>>>>>>>>>> <module> >>>>>>>>>>>>> payload = lines[0].strip() >>>>>>>>>>>>> IndexError: list index out of range >>>>>>>>>>>>> >>>>>>>>>>>>> Sometimes rtldavis is faster or slower, but rarely does it >>>>>>>>>>>>> start in <10s. From reading other comments, it sounds like the >>>>>>>>>>>>> driver times >>>>>>>>>>>>> out after 10s of no data here. >>>>>>>>>>>>> >>>>>>>>>>>>> Any ideas what might be happening here? The antenna that I >>>>>>>>>>>>> have on there is a cheap set of rabbit ears (dipole), could >>>>>>>>>>>>> certainly get a >>>>>>>>>>>>> better one, the station is about 80ft (25m) away on the roof of >>>>>>>>>>>>> the next >>>>>>>>>>>>> building over. Hardware is a raspberry pi and and an RTL-SDR blog >>>>>>>>>>>>> brand >>>>>>>>>>>>> R820T2 RTL2832U SDR. Pi is running latest raspbian. >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you for all your hard work, I am so close! >>>>>>>>>>>>> On Wednesday, May 8, 2019 at 1:37:45 AM UTC-7 >>>>>>>>>>>>> [email protected] wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> uvedhe wrote on github : >>>>>>>>>>>>>>> >>>>>>>>>>>>>> I will answer this in the weewx-rtldavis topic in the >>>>>>>>>>>>>>> weewx-development forum. >>>>>>>>>>>>>>> Luc >>>>>>>>>>>>>>> >>>>>>>>>>>>>> uvedhe <https://github.com/uvedhe> commented 14 hours ago >>>>>>>>>>>>>>> <https://github.com/lheijst/weewx-rtldavis/issues/1#issue-441358316> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> I can successfully run $GOPATH/bin/rtldavis which returns >>>>>>>>>>>>>>> various entries, like these: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 19:10:43.856163 Init channels: wait max 17 seconds for a >>>>>>>>>>>>>>> message of each transmitter >>>>>>>>>>>>>>> 19:11:01.793521 Init channels: wait max 17 seconds for a >>>>>>>>>>>>>>> message of each transmitter >>>>>>>>>>>>>>> 19:11:01.794049 Hop: {ChannelIdx:0 ChannelFreq:868077250 >>>>>>>>>>>>>>> FreqError:0} >>>>>>>>>>>>>>> 19:11:19.732536 Init channels: wait max 17 seconds for a >>>>>>>>>>>>>>> message of each transmitter >>>>>>>>>>>>>>> 19:11:19.732580 Hop: {ChannelIdx:0 ChannelFreq:868077250 >>>>>>>>>>>>>>> FreqError:0} >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi uvedhe, >>>>>>>>>>>>>> >>>>>>>>>>>>>> The rtldavis log show you didn't receive any data. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The rtldavis program use default the EU-frequencies. You use >>>>>>>>>>>>>> the EU version of the Davis Vantage, right? >>>>>>>>>>>>>> The program runs succesfully on a Raspberry PI, Not sure if >>>>>>>>>>>>>> it will run on OS X 10 too. >>>>>>>>>>>>>> >>>>>>>>>>>>>> You could try to run the rtldavis program with several other >>>>>>>>>>>>>> ppm settings to check if any data will b read like: >>>>>>>>>>>>>> $GOPATH/bin/rtldavis -ppm 3 >>>>>>>>>>>>>> or >>>>>>>>>>>>>> $GOPATH/bin/rtldavis -ppm -3 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Luc >>>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>> You received this message because you are subscribed to a topic >>>>>>>>>>>> in the Google Groups "weewx-development" group. >>>>>>>>>>>> To unsubscribe from this topic, visit >>>>>>>>>>>> https://groups.google.com/d/topic/weewx-development/jhGleLxu-p0/unsubscribe >>>>>>>>>>>> . >>>>>>>>>>>> To unsubscribe from this group and all its topics, send an >>>>>>>>>>>> email to [email protected]. >>>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-development/93e51a21-294a-4736-982a-83efabc4e03dn%40googlegroups.com >>>>>>>>>>>> >>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-development/93e51a21-294a-4736-982a-83efabc4e03dn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>>> . >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>> You received this message because you are subscribed to a topic >>>>>>>>>> in the Google Groups "weewx-development" group. >>>>>>>>>> To unsubscribe from this topic, visit >>>>>>>>>> https://groups.google.com/d/topic/weewx-development/jhGleLxu-p0/unsubscribe >>>>>>>>>> . >>>>>>>>>> To unsubscribe from this group and all its topics, send an email >>>>>>>>>> to [email protected]. >>>>>>>>>> >>>>>>>>> To view this discussion on the web visit >>>>>>>>>> https://groups.google.com/d/msgid/weewx-development/297b95f2-6904-4d9b-aced-dd52d6b2dd4an%40googlegroups.com >>>>>>>>>> >>>>>>>>>> <https://groups.google.com/d/msgid/weewx-development/297b95f2-6904-4d9b-aced-dd52d6b2dd4an%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>> . >>>>>>>>>> >>>>>>>>> -- >>>>>>>> You received this message because you are subscribed to a topic in >>>>>>>> the Google Groups "weewx-development" group. >>>>>>>> To unsubscribe from this topic, visit >>>>>>>> https://groups.google.com/d/topic/weewx-development/jhGleLxu-p0/unsubscribe >>>>>>>> . >>>>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>>>> [email protected]. >>>>>>>> >>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/weewx-development/dcd953a3-771f-4eb9-bf8b-f7ef50f08eb1n%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/weewx-development/dcd953a3-771f-4eb9-bf8b-f7ef50f08eb1n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "weewx-development" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/weewx-development/jhGleLxu-p0/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-development/8abd1574-df46-41b2-9155-2a29bc3d4f1fn%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/weewx-development/8abd1574-df46-41b2-9155-2a29bc3d4f1fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "weewx-development" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/weewx-development/jhGleLxu-p0/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-development/5e6149e4-1e57-4a28-8988-f65d54af2c16n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-development/5e6149e4-1e57-4a28-8988-f65d54af2c16n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/37a64830-6944-4fdc-b958-e93849514238n%40googlegroups.com.
