Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Guido Cioni]

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 lloyd...@gmail.com 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 ljm.h...@gmail.com 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 arlen@gmail.com:
>>
>>> 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  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 arlen@gmail.com:

> 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 storm...@gmail.com  
> wrote:
>
>> I use the following driver: https://gitlab.com/wjcarpenter/bme280wx
>>
>> On Friday, April 9, 2021 at 10:22:36 PM UTC-4 arlen@gmail.com 
>> wrote:
>>
>>> Perfect, thank you. I was just googling around for something like 
>>> this.
>>>
>>> On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com  
>>> 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=bme280=1618020646=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 arlen@gmail.com 
 wrote:

> Well that would certainly do it. Thank you for your help!
>
> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  
> 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 
>> arlen@gmail.com:
>>
>>> 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
>>>

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lloyd Brown]

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 ljm.h...@gmail.com 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 arlen@gmail.com:
>
>> 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  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 arlen@gmail.com:
>>>
 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 storm...@gmail.com  
 wrote:

> I use the following driver: https://gitlab.com/wjcarpenter/bme280wx
>
> On Friday, April 9, 2021 at 10:22:36 PM UTC-4 arlen@gmail.com 
> wrote:
>
>> Perfect, thank you. I was just googling around for something like 
>> this.
>>
>> On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com  
>> 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=bme280=1618020646=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 arlen@gmail.com 
>>> wrote:
>>>
 Well that would certainly do it. Thank you for your help!

 On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  
 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 
> arlen@gmail.com:
>
>> 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  
>> 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 
>>> arlen@gmail.com:
>>>
 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 
 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

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 arlen@gmail.com:

> 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  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 arlen@gmail.com:
>>
>>> 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 storm...@gmail.com  
>>> wrote:
>>>
 I use the following driver: https://gitlab.com/wjcarpenter/bme280wx

 On Friday, April 9, 2021 at 10:22:36 PM UTC-4 arlen@gmail.com 
 wrote:

> Perfect, thank you. I was just googling around for something like this.
>
> On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com  
> 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=bme280=1618020646=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 arlen@gmail.com 
>> wrote:
>>
>>> Well that would certainly do it. Thank you for your help!
>>>
>>> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  
>>> 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 
 arlen@gmail.com:

> 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  
> 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 
>> arlen@gmail.com:
>>
>>> 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
>>> 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

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 arlen@gmail.com:

> 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 storm...@gmail.com  
> wrote:
>
>> I use the following driver: https://gitlab.com/wjcarpenter/bme280wx
>>
>> On Friday, April 9, 2021 at 10:22:36 PM UTC-4 arlen@gmail.com wrote:
>>
>>> Perfect, thank you. I was just googling around for something like this.
>>>
>>> On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com  
>>> 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=bme280=1618020646=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 arlen@gmail.com wrote:

> Well that would certainly do it. Thank you for your help!
>
> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  
> 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 arlen@gmail.com
>> :
>>
>>> 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  
>>> 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 
 arlen@gmail.com:

> 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}
> 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Weird, the image lost in transmission, lemme try again...

On Sunday, April 11, 2021 at 9:39:17 PM UTC+2 kobuki wrote:

> It's not UV for sure. UV looks something like image attached (it was a 
> cloudy day here). It must be a bogus channel you catch on air or some 
> metric flagged as UV. It looks like barometer data, if anything.
>
> On Sunday, April 11, 2021 at 9:14:13 PM UTC+2 arlen@gmail.com wrote:
>
>> 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 storm...@gmail.com  
>> wrote:
>>
>>> I use the following driver: https://gitlab.com/wjcarpenter/bme280wx
>>>
>>> On Friday, April 9, 2021 at 10:22:36 PM UTC-4 arlen@gmail.com wrote:
>>>
 Perfect, thank you. I was just googling around for something like this.

 On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com  
 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=bme280=1618020646=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 arlen@gmail.com 
> wrote:
>
>> Well that would certainly do it. Thank you for your help!
>>
>> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  
>> 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 
>>> arlen@gmail.com:
>>>
 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  
 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 
> arlen@gmail.com:
>
>> 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 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

It's not UV for sure. UV looks something like image attached (it was a 
cloudy day here). It must be a bogus channel you catch on air or some 
metric flagged as UV. It looks like barometer data, if anything.

On Sunday, April 11, 2021 at 9:14:13 PM UTC+2 arlen@gmail.com wrote:

> 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 storm...@gmail.com  
> wrote:
>
>> I use the following driver: https://gitlab.com/wjcarpenter/bme280wx
>>
>> On Friday, April 9, 2021 at 10:22:36 PM UTC-4 arlen@gmail.com wrote:
>>
>>> Perfect, thank you. I was just googling around for something like this.
>>>
>>> On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com  
>>> 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=bme280=1618020646=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 arlen@gmail.com wrote:

> Well that would certainly do it. Thank you for your help!
>
> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  
> 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 arlen@gmail.com
>> :
>>
>>> 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  
>>> 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 
 arlen@gmail.com:

> 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: 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Arlen Abraham]

Perfect, thank you. I was just googling around for something like this.

On Fri, Apr 9, 2021 at 19:15 storm...@gmail.com 
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=bme280=1618020646=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 arlen@gmail.com wrote:
>
>> Well that would certainly do it. Thank you for your help!
>>
>> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  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 arlen@gmail.com:
>>>
 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  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 arlen@gmail.com:
>
>> 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 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[storm...@gmail.com]

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=bme280=1618020646=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 arlen@gmail.com wrote:

> Well that would certainly do it. Thank you for your help!
>
> On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  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 arlen@gmail.com:
>>
>>> 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  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 arlen@gmail.com:

> 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 
> payload = lines[0].strip()
> IndexError: list index out of range
>
> 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Arlen Abraham]

Well that would certainly do it. Thank you for your help!

On Fri, Apr 9, 2021 at 12:22 PM Lucas Heijst  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 arlen@gmail.com:
>
>> 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  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 arlen@gmail.com:
>>>
 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 
 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 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

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 arlen@gmail.com:

> 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  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 arlen@gmail.com:
>>
>>> 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 
>>> 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 ljm.h...@gmail.com wrote:
>>>
 uvedhe wrote on github 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

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 arlen@gmail.com:

> 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 
> 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 ljm.h...@gmail.com wrote:
>
>> uvedhe wrote on github :
>>>
>> I will answer this in the weewx-rtldavis topic in the weewx-development 
>>> forum.
>>> Luc
>>>
>> uvedhe  commented 14 hours ago 
>>> 
>>>
>> 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 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Arlen Abraham]

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 
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 ljm.h...@gmail.com wrote:

> uvedhe wrote on github :
>>
> I will answer this in the weewx-rtldavis topic in the weewx-development 
>> forum.
>> Luc
>>
> uvedhe  commented 14 hours ago 
>> 
>>
> 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 the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Germano S]

Hello,
Thank you both for the advise. 

I recompiled the driver with DENABLE_ZEROCOPY=0 and that did not help.
i tried using -u and i didn't get any extra output.
Randomly it will not set the power correctly, I will set  -gain 338 for 
example and still get 0db

I will have a revisit of the antenna. I do have three antennas with the 
largest being a 15db one. They are meant to pick up that part of the 
spectrum as i can see gliders running on 868mhz as well as my local mobile 
tower as i can see packets on the 950mhz band.

Anyone have any recommendations for antennas that they use? 

Regards,

On Friday, September 25, 2020 at 7:10:06 PM UTC+1 wor...@wormley.com wrote:

> If you're using the version from: https://github.com/lheijst/rtldavis it 
> should just work provided you told it "-tr US" and provided any ppm 
> correction. 
>
> Now, the one problem you may have is if you're using the system provided 
> librtlsdr, and if it's saying something about Zero Copy Buffers, not sure 
> if it's a problem on x86/amd64 but the Raspberry Pi's definitely didn't 
> like it. Unless they fixed that you'll need to uninstall the system 
> librtlsdr and compile one from scratch per the instructions and give it the 
> -DENABLE_ZEROCOPY=0 flag when compiling.
> (Or set LD_LIBRARY_PATH to your version if you don't want to remove the 
> system version)
>
> -Steve
>
>
>
>
>
> On Wed, Sep 23, 2020 at 1:06 PM Germano S  wrote:
>
>> Hello,
>> Just checking in if there is still development on this driver.
>>
>> I was given a used Vantage pro (US) a not to long a ago. I have installed 
>> everything as far as i can tell, but rtldavis reports no data being 
>> transmitted which makes me think my frequencies are incorrect. 
>>
>> I am running on Debian 10 (Buster) with Weewx 4.1.1 along with an RTL-SDR 
>> V3 which has been calibrated. I am scanning the frequencies to see if i can 
>> find anything.
>>
>> If anyone can give me a bit of further direction or if anyone has 
>> succeeded i would be most appreciative. :)
>>
>>
>>
>>
>>
>> On Friday, May 10, 2019 at 5:45:24 PM UTC+1 storm...@gmail.com wrote:
>>
>>> Luc
>>>
>>> Is there a way to put the Channel Id, Channel Freq, and Error into the 
>>> LOOP packet with the data?  I looked through rtldavis.py but could not find 
>>> a the spot.
>>>
>>> Rich
>>>
>>>
 -- 
>> 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 weewx-developm...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-development/25bd9d93-544e-4d19-a363-fb6aa3c4222an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/f3993023-6e25-4ce6-a4e5-bae5353bc6c1n%40googlegroups.com.

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Steve Wormley]

If you're using the version from: https://github.com/lheijst/rtldavis it
should just work provided you told it "-tr US" and provided any ppm
correction.

Now, the one problem you may have is if you're using the system provided
librtlsdr, and if it's saying something about Zero Copy Buffers, not sure
if it's a problem on x86/amd64 but the Raspberry Pi's definitely didn't
like it. Unless they fixed that you'll need to uninstall the system
librtlsdr and compile one from scratch per the instructions and give it the
-DENABLE_ZEROCOPY=0 flag when compiling.
(Or set LD_LIBRARY_PATH to your version if you don't want to remove the
system version)

-Steve





On Wed, Sep 23, 2020 at 1:06 PM Germano S  wrote:

> Hello,
> Just checking in if there is still development on this driver.
>
> I was given a used Vantage pro (US) a not to long a ago. I have installed
> everything as far as i can tell, but rtldavis reports no data being
> transmitted which makes me think my frequencies are incorrect.
>
> I am running on Debian 10 (Buster) with Weewx 4.1.1 along with an RTL-SDR
> V3 which has been calibrated. I am scanning the frequencies to see if i can
> find anything.
>
> If anyone can give me a bit of further direction or if anyone has
> succeeded i would be most appreciative. :)
>
>
>
>
>
> On Friday, May 10, 2019 at 5:45:24 PM UTC+1 storm...@gmail.com wrote:
>
>> Luc
>>
>> Is there a way to put the Channel Id, Channel Freq, and Error into the
>> LOOP packet with the data?  I looked through rtldavis.py but could not find
>> a the spot.
>>
>> Rich
>>
>>
>>> --
> 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 weewx-development+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-development/25bd9d93-544e-4d19-a363-fb6aa3c4222an%40googlegroups.com
> 
> .
>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CAF47bhH6PLEj%3DuhNGNc0poqkwoM2fY8PPLyOugOt6vSf2Prm8A%40mail.gmail.com.

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Steve Wormley]

I'd try a couple things, 1. add "-u true" to see if it's picking up any
transmitters on any channel. And try specifying a gain value "-gain 338" or
so, 0 should be automatic gain, but it never hurts to try to set it
yourself.
It's odd that it's reporting the SetFreqCorrection as '0' but it obviously
knows the correct number, but that's a low enough PPM that it should still
be able to lock.

I assume this rtl/antenna has been checked on some other program and
frequencies to make sure it's working.

-Steve


On Wed, Sep 23, 2020 at 2:46 PM Germano Soru  wrote:

> Thank you Steve for the quick response. (sorry i think it sent it
> directly to your email)
> I am using an x86/x64 system.
> I have tried with both the one bundled with Debian and the compiled one
> linked in the git repo.
>
> Occasionally the Zero buffer does pop up, there are no errors or
> warnings that come with it, just no data seams to be found
>
> germano@weewx:~$ $GOPATH/bin/rtldavis -tf US -tr 1 -ppm -14
> 22:38:14.085423 rtldavis.go VERSION=0.15
> 22:38:14.094201 tr=1 fc=0 ppm=-14 gain=0 maxmissed=51 ex=0
> receiveWindow=300 actChan=[0] maxChan=1
> 22:38:14.094250 undefined=false verbose=false disableAfc=false
> deviceString=0
> 22:38:14.094526 BitRate: 19200
> 22:38:14.094538 SymbolLength: 14
> 22:38:14.094545 SampleRate: 268800
> 22:38:14.094552 Preamble: 1100101110001001
> 22:38:14.094559 PreambleSymbols: 16
> 22:38:14.094566 PreambleLength: 224
> 22:38:14.094572 PacketSymbols: 80
> 22:38:14.094579 PacketLength: 1120
> 22:38:14.094585 BlockSize: 512
> 22:38:14.094592 BufferLength: 2048
> Found Rafael Micro R820T tuner
> 22:38:46.554454 Hop: {ChannelIdx:0 ChannelFreq:902419338 FreqError:0
> Transmitter:0}
> Exact sample rate is: 268800.001367 Hz
> 22:38:46.823028 GetTunerGain: 0 Db
> 22:38:46.823774 SetFreqCorrection 0 ppm Successful
> 22:38:46.830107 Init channels: wait max 135 seconds for a message of
> each transmitter
> 22:41:02.643549 Init channels: wait max 135 seconds for a message of
> each transmitter
> 22:41:02.645021 Hop: {ChannelIdx:0 ChannelFreq:902419338 FreqError:0
> Transmitter:0}
>
>
> On Wed, 2020-09-23 at 14:08 -0700, Steve Wormley wrote:
> > If you're using the version from: https://github.com/lheijst/rtldavis
> >  it should just work provided you told it "-tr US" and provided any
> > ppm correction.
> >
> > Now, the one problem you may have is if you're using the system
> > provided librtlsdr, and if it's saying something about Zero Copy
> > Buffers, not sure if it's a problem on x86/amd64 but the Raspberry
> > Pi's definitely didn't like it. Unless they fixed that you'll need to
> > uninstall the system librtlsdr and compile one from scratch per the
> > instructions and give it the -DENABLE_ZEROCOPY=0 flag when compiling.
> > (Or set LD_LIBRARY_PATH to your version if you don't want to remove
> > the system version)
> >
> > -Steve
> >
> >
> >
> >
> >
> > On Wed, Sep 23, 2020 at 1:06 PM Germano S  wrote:
> > > Hello,
> > > Just checking in if there is still development on this driver.
> > >
> > > I was given a used Vantage pro (US) a not to long a ago. I have
> > > installed everything as far as i can tell, but rtldavis reports no
> > > data being transmitted which makes me think my frequencies are
> > > incorrect.
> > >
> > > I am running on Debian 10 (Buster) with Weewx 4.1.1 along with an
> > > RTL-SDR V3 which has been calibrated. I am scanning the frequencies
> > > to see if i can find anything.
> > >
> > > If anyone can give me a bit of further direction or if anyone has
> > > succeeded i would be most appreciative. :)
> > >
> > >
> > >
> > >
> > >
> > > On Friday, May 10, 2019 at 5:45:24 PM UTC+1 storm...@gmail.com
> > > wrote:
> > > > Luc
> > > >
> > > > Is there a way to put the Channel Id, Channel Freq, and Error
> > > > into the LOOP packet with the data?  I looked through rtldavis.py
> > > > but could not find a the spot.
> > > >
> > > > Rich
> > > >
>
> --
> 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 weewx-development+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-development/304359d87fec7cb94a5d40e8819f3e111b419804.camel%40soru.me.uk
> .
>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CAF47bhF0u6Ng1wHAUiZj-x%2BwH55rmuSM7MUUn7AQXzSo6b7%2Bmg%40mail.gmail.com.

Re: [weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Germano Soru]

Thank you Steve for the quick response. (sorry i think it sent it
directly to your email)
I am using an x86/x64 system.
I have tried with both the one bundled with Debian and the compiled one
linked in the git repo.

Occasionally the Zero buffer does pop up, there are no errors or
warnings that come with it, just no data seams to be found

germano@weewx:~$ $GOPATH/bin/rtldavis -tf US -tr 1 -ppm -14
22:38:14.085423 rtldavis.go VERSION=0.15
22:38:14.094201 tr=1 fc=0 ppm=-14 gain=0 maxmissed=51 ex=0
receiveWindow=300 actChan=[0] maxChan=1
22:38:14.094250 undefined=false verbose=false disableAfc=false
deviceString=0
22:38:14.094526 BitRate: 19200
22:38:14.094538 SymbolLength: 14
22:38:14.094545 SampleRate: 268800
22:38:14.094552 Preamble: 1100101110001001
22:38:14.094559 PreambleSymbols: 16
22:38:14.094566 PreambleLength: 224
22:38:14.094572 PacketSymbols: 80
22:38:14.094579 PacketLength: 1120
22:38:14.094585 BlockSize: 512
22:38:14.094592 BufferLength: 2048
Found Rafael Micro R820T tuner
22:38:46.554454 Hop: {ChannelIdx:0 ChannelFreq:902419338 FreqError:0
Transmitter:0}
Exact sample rate is: 268800.001367 Hz
22:38:46.823028 GetTunerGain: 0 Db
22:38:46.823774 SetFreqCorrection 0 ppm Successful
22:38:46.830107 Init channels: wait max 135 seconds for a message of
each transmitter
22:41:02.643549 Init channels: wait max 135 seconds for a message of
each transmitter
22:41:02.645021 Hop: {ChannelIdx:0 ChannelFreq:902419338 FreqError:0
Transmitter:0}


On Wed, 2020-09-23 at 14:08 -0700, Steve Wormley wrote:
> If you're using the version from: https://github.com/lheijst/rtldavis
>  it should just work provided you told it "-tr US" and provided any
> ppm correction. 
> 
> Now, the one problem you may have is if you're using the system
> provided librtlsdr, and if it's saying something about Zero Copy
> Buffers, not sure if it's a problem on x86/amd64 but the Raspberry
> Pi's definitely didn't like it. Unless they fixed that you'll need to
> uninstall the system librtlsdr and compile one from scratch per the
> instructions and give it the -DENABLE_ZEROCOPY=0 flag when compiling.
> (Or set LD_LIBRARY_PATH to your version if you don't want to remove
> the system version)
> 
> -Steve
> 
> 
> 
> 
> 
> On Wed, Sep 23, 2020 at 1:06 PM Germano S  wrote:
> > Hello,
> > Just checking in if there is still development on this driver.
> > 
> > I was given a used Vantage pro (US) a not to long a ago. I have
> > installed everything as far as i can tell, but rtldavis reports no
> > data being transmitted which makes me think my frequencies are
> > incorrect. 
> > 
> > I am running on Debian 10 (Buster) with Weewx 4.1.1 along with an
> > RTL-SDR V3 which has been calibrated. I am scanning the frequencies
> > to see if i can find anything.
> > 
> > If anyone can give me a bit of further direction or if anyone has
> > succeeded i would be most appreciative. :)
> > 
> > 
> > 
> > 
> > 
> > On Friday, May 10, 2019 at 5:45:24 PM UTC+1 storm...@gmail.com
> > wrote:
> > > Luc
> > > 
> > > Is there a way to put the Channel Id, Channel Freq, and Error
> > > into the LOOP packet with the data?  I looked through rtldavis.py
> > > but could not find a the spot.
> > > 
> > > Rich
> > > 

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/304359d87fec7cb94a5d40e8819f3e111b419804.camel%40soru.me.uk.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

Is there a way to put the Channel Id, Channel Freq, and Error into the LOOP 
packet with the data?  I looked through rtldavis.py but could not find a 
the spot.

Rich


>

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/c2b6a802-5957-43b5-a9cd-d61ba956eebd%40googlegroups.com.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

Hi uvedhe,

Let me start with your Ventus W830 station. 
You can read its data with the weewx intercepter driver. Go to the 
weewx-user forum and search for Ventus W830.
There are three forum items referring to this station.
When you have problems with installing or configuring the intercepter 
driver, start a thread in the weewx-user forum with your question.
It will help when you set debug=1 in weex.conf and include in your message 
the syslog from the start of weewx until a problem occurs.

Then the Davis weather station of your neighbour. 
BTW. You can put your RTL-SDR antenna on a round metal surface to get a 
better reception.

You don't have to know the serial number of the Vantage station, but you 
need to know which channel the ISS is set to.
It can be set from 0 to 7 and usually the owner will leave the default 
channel 0. That is also the default of the rtldavis GO program.
You could try a few other channels with:
$GOPATH/bin/rtldavis -tr 1 (channel 0)
$GOPATH/bin/rtldavis -tr 2 (channel 1)
$GOPATH/bin/rtldavis -tr 4 (channel 2)
$GOPATH/bin/rtldavis -tr 8 (channel 3)
..
$GOPATH/bin/rtldavis -tr 128 (channel 7)

When your neighbour has a separate station for its wind meter, then the 
rtldavis program has to be setup for two channels.
Just add the numbers of the channels you want. Generally one will set ISS 
to channel 0 and the anemometer to channel 1, so the command will be:
$GOPATH/bin/rtldavis -tr 3 (channels 0 and 1)

The way the programs rtldavis (GO) and weewx with the rtldavis driver 
cooperate are as follows:

The rtldavis GO program reads the radio data of the RTL-SDR device, does 
the frequency hopping and outputs the raw binary weather data on stdout.
Besides the 8-byte raw message data the rtldavis program outputs some 
additional data which weewx uses to calculate the percentage of 'good' and 
'missed' signals.
Typically a message is received each 2.625 - 3.0 seconds (depending on the 
used channel).
So, as long as the rtldavis GO program doesn't receive messages on a 
regular interval, it has no use to start the weewx program. It cannot make 
'something' from 'nothing'.

The weewx program with the weewx-rtldavis driver installed does the 
following:
a. It calls the rtldavis GO program with the parameters which can be set in 
the Rtldavis section of weewx.conf.
   IMPORTANT: don't start the rtldavis GO program yourself when using 
weewx-rtldavis!
b. The weewx driver parses the data output of the rtldavis GO program.
   The raw data messages are decoded and send as 'loop' data to weewx which 
will do the further handling of the data. See the weewx documentation.
   The received frequency-error data can be used to analyse the reception. 
I have configured a weewx plot to show the errors over time.
   When the frequency-errors are big (i.e. < -15.000 Hz or > + 15.00 Hz) is 
is likely you will miss signals. This can be fixed by setting a positive or 
negative ppm correction.
   The 'good-message-counters' of the first 4 channels are analysed by the 
weewx driver and each archive interval a summary is printed in the syslog 
file.
   Example: 
   May  8 06:45:15 pi35 rtld[452]: rtldavis: ARCHIVE_STATS: last time: 
last_cnt[0-3]:   15573084151149511254110410
   May  8 06:45:15 pi35 rtld[452]: rtldavis: ARCHIVE_STATS: curr time: 
curr_cnt[0-3]:   15573087151160511364111470
   May  8 06:45:15 pi35 rtld[452]: rtldavis: ARCHIVE_STATS: 
total_max_count=342 total_count=326 total_missed=16  pctGood= 95.32
   May  8 06:45:15 pi35 rtld[452]: rtldavis: ARCHIVE_STATS: station 1: 
max_count=  117 count= 110 missed=   7 pct_good= 94.02
   May  8 06:45:15 pi35 rtld[452]: rtldavis: ARCHIVE_STATS: station 2: 
max_count=  114 count= 110 missed=   4 pct_good= 96.49
   May  8 06:45:15 pi35 rtld[452]: rtldavis: ARCHIVE_STATS: station 3: 
max_count=  111 count= 106 missed=   5 pct_good= 95.50

Hope this helps.

Luc

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/c56f912f-c761-45e6-8236-b192c34ac1b6%40googlegroups.com.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[uvedhe]

Hi Luc,

Thanks for your quick response! I tried the -ppm adjustments, but to no 
avail. As I said, I'm new to all of this so it might well be that I haven't 
fully understood how things work. Let me give you some more background 
information in the hope it clarifies things a little:

What I'm trying to achieve is to have Python read in weather data (wind 
speed & direction mostly) and then use that to do some calculations in 
Python (I'm assuming WeeWX is the best way to go here but do let me know if 
I'm really going in the wrong direction here!). I have a Ventus W830 on my 
roof but can't find a driver for it. There's a Davis weather station about 
10 meters from my house, so I thought I'd try to capture that one instead 
(I'm in EU yes). I have an RTL-SDR dongle with antenna. 

So, I guess I'm stuck at a more basic level, which is: How can I connect to 
this particular Davis station? Do I need to know it's serial number? If I 
open CubicSDR I see a repeated signal on 868MHz so I do think I can receive 
it (though not sure it's my Ventus W830 competing on the same frequency?). 
However, conceptually I might not have fully grasped yet the different 
stages: 1. capturing a signal (using RTL-SDR), 2. connecting(?) to the 
station (using WeeWX??), 3. decoding using a driver (using `$ 
$GOPATH/bin/rtldavis` ??), then 4. reading out the data using Python (using 
`pyrtlsdr`?)?

Thanks in advance for bearing with my basic (or rather lack of) 
understanding here!




On Wednesday, May 8, 2019 at 10:37:45 AM UTC+2, Lucas Heijst wrote:
>
> uvedhe wrote on github :
>> I will answer this in the weewx-rtldavis topic in the weewx-development 
>> forum.
>> Luc
>> uvedhe  commented 14 hours ago 
>> 
>> 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 the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/3715f7c3-1e74-4c81-aaa9-b5105c16bfd9%40googlegroups.com.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

>
> uvedhe wrote on github :
> I will answer this in the weewx-rtldavis topic in the weewx-development 
> forum.
> Luc
> uvedhe  commented 14 hours ago 
> 
> 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 the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/144712bb-7edc-458c-bd10-970c8ff40fb9%40googlegroups.com.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Lucas Heijst]

uvedhe wrote on github the following comment.
I will answer this in the weewx-rtldavis topic in the weewx-development 
forum.
Luc
uvedhe  commented 14 hours ago 


I'm trying to read in wind data from my weather station into a Python 
script, to then be able to do some calculations with the data. I discovered 
WeeWX and thought this was the way to go. Now I've been trying to get the 
RTL Davis driver to work. I'm using an RTL-SDR v3 dongle on OS X 10.13. 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}

Now I was hoping to actually get some data out, so I thought I needed to 
install the rtldavis driver. Install all went successfully, but when I run 
PYTHONPATH=bin 
python bin/user/rtldavis.py --cmd="/Users/user/go/bin/rtldavis" I get the 
error IndexError: list index out of range.

Not sure where it's going wrong?

Here's the full output:

19:03:46.160784 rtldavis.go VERSION=0.12
19:03:46.161047 tr=1 fc=0 ppm=0 gain=0 ex=0 maxmissed=51 actChan=[0] maxChan=1
19:03:46.161326 BitRate: 19200
19:03:46.161340 SymbolLength: 14
19:03:46.161347 SampleRate: 268800
19:03:46.161359 Preamble: 1100101110001001
19:03:46.161368 PreambleSymbols: 16
19:03:46.161375 PreambleLength: 224
19:03:46.161387 PacketSymbols: 80
19:03:46.161394 PacketLength: 1120
19:03:46.161405 BlockSize: 512
19:03:46.161411 BufferLength: 2048
Found Rafael Micro R820T tuner
19:03:46.610555 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
Exact sample rate is: 268800.001367 Hz
19:03:46.814340 GetTunerGain: 0 Db
19:03:46.814362 SetFreqCorrection 0 ppm Successful
19:03:46.818456 Init channels: wait max 17 seconds for a message of each 
transmitter
Traceback (most recent call last):
  File "bin/user/rtldavis.py", line 1337, in 
payload = lines[0].strip()
IndexError: list index out of range

-- 
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 weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/a1dfeb9f-fb2a-4d57-81dd-e334d5d80c06%40googlegroups.com.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

You were correct, I missed the rain bucket setting in the weewx config file.

Thanks

Rich

On Wednesday, May 1, 2019 at 8:00:41 AM UTC-4, ljm@gmail.com wrote:

>
> On Sunday, 28 April 2019 11:36:14 UTC-3, rich T wrote:
>>
>> Right now all my consoles (Davis and Acurite) indicate 0.09 inches fell 
>> but the driver is indicating 0.07 inches. 
>>
>
> Rich,
>
> You must have set the default rain_bucket_type = 1 (0.2 mm). For US it 
> should be set to 0 (0.01 inch)
>
> When I correct your values: with the formula: rtldavis inches * 0.254 
> mm/bucket  / 0.2 mm/bucket I get:
> 0.07 * 0.0254 / 0.2 = 0.0889 inch. Rounded to two decimals: 0.09 (the 
> value of Davis and Acurite)
>
> Luc
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Sunday, 28 April 2019 11:36:14 UTC-3, rich T wrote:
>
> Right now all my consoles (Davis and Acurite) indicate 0.09 inches fell 
> but the driver is indicating 0.07 inches. 
>

Rich,

You must have set the default rain_bucket_type = 1 (0.2 mm). For US it 
should be set to 0 (0.01 inch)

When I correct your values: with the formula: rtldavis inches * 0.254 
mm/bucket  / 0.2 mm/bucket I get:
0.07 * 0.0254 / 0.2 = 0.0889 inch. Rounded to two decimals: 0.09 (the value 
of Davis and Acurite)

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

Will check later this evening, when I get back into the area.

Rich

On Wednesday, May 1, 2019 at 4:17:37 AM UTC-4, ljm@gmail.com wrote:

> Rich,
> What is the value of rain_bucket_type in weewx.conf? Default it is set to 
> 1 (0.2) mm.
> Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Thanks Luc.  Will set the Debug and track it.

Rich

On Monday, April 29, 2019 at 5:09:02 PM UTC-4, ljm@gmail.com wrote:

> On Sunday, 28 April 2019 11:36:14 UTC-3, rich T wrote:
>>
>> Was wondering if there was a way to add an optional JSON output?  
>>
>
> Hi Rich,
>
> There probably is, but I have no plans to add such.
>
> What you can do to track the problem:
>
> 1. Activate rain debug logging in weewx.conf:
> [Rtldavis]
> ...
> debug_rain  = 1
>
> 2. Plot the rain values of both systems on one graph (or two graphs next 
> to each other).
> Then you will notice when a difference occurs.
>
> Luc
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Monday, 29 April 2019 04:55:45 UTC-3, Nigel Head wrote:
>
> Apr 28 12:40:15 raspberrypi weewx[2299]:   TypeError: float 
> argument required, not NoneType
>

Hi Nigel,

I thought I fixed this already, but not. When no single message is 
received, the PctGood value is None and I have to check for this to avoid 
the TypeError.

Luc 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Sunday, 28 April 2019 11:36:14 UTC-3, rich T wrote:
>
> Was wondering if there was a way to add an optional JSON output?  
>

Hi Rich,

There probably is, but I have no plans to add such.

What you can do to track the problem:

1. Activate rain debug logging in weewx.conf:
[Rtldavis]
...
debug_rain  = 1

2. Plot the rain values of both systems on one graph (or two graphs next to 
each other).
Then you will notice when a difference occurs.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Hi Luc,

My RTLdavis test system died yesterday, error below...

Possibly relevant is that I was also transmitting from my Amateur Radio 
station around the time it failed (these dongles are easily overloaded), 
maybe something?

I have restarted the test system, but now of course, there is a gap in data 
as there is no offline logging as there is with the console.
My console has a DIY logger and is wirelessly (RF) linked to my main weewx 
system using zigbee modules (in place of the USB logger), so the console is 
not physically tethered to the computer.  None of this is affected by my 
'ham' radio transmissions.

Apr 28 12:35:18 raspberrypi weewx[2299]: imagegenerator: Generated 14 
images for SeasonsReport in 1.18 seconds
Apr 28 12:35:18 raspberrypi weewx[2299]: copygenerator: copied 0 files to 
/home/weewx/public_html
Apr 28 12:40:15 raspberrypi weewx[2299]: engine: Main loop exiting. 
Shutting engine down.
Apr 28 12:40:15 raspberrypi weewx[2299]: engine: Shutting down StdReport 
thread
Apr 28 12:40:15 raspberrypi weewx[2299]: rtldavis: shutdown process 
/home/pi/work/bin/rtldavis -ppm 7 [options] -tf EU -tr 1
Apr 28 12:40:15 raspberrypi weewx[2299]: rtldavis: rtldavis with pid 2304 
killed
Apr 28 12:40:15 raspberrypi weewx[2299]: engine: Caught unrecoverable 
exception in engine:
Apr 28 12:40:15 raspberrypi weewx[2299]:   float argument required, 
not NoneType
Apr 28 12:40:15 raspberrypi weewx[2299]:   Traceback (most recent 
call last):
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/weewx/engine.py", line 890, in main
Apr 28 12:40:15 raspberrypi weewx[2299]:   engine.run()
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/weewx/engine.py", line 202, in run
Apr 28 12:40:15 raspberrypi weewx[2299]:   
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
Apr 28 12:40:15 raspberrypi weewx[2299]:   callback(event)
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/weewx/engine.py", line 582, in post_loop
Apr 28 12:40:15 raspberrypi weewx[2299]:   
self._software_catchup()
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/weewx/engine.py", line 646, in _software_catchup
Apr 28 12:40:15 raspberrypi weewx[2299]:   
self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD, 
record=record, origin='software'))
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
Apr 28 12:40:15 raspberrypi weewx[2299]:   callback(event)
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/user/rtldavis.py", line 908, in new_archive_record
Apr 28 12:40:15 raspberrypi weewx[2299]:   
self._update_summaries()  # calculate summaries
Apr 28 12:40:15 raspberrypi weewx[2299]: File 
"/home/weewx/bin/user/rtldavis.py", line 897, in _update_summaries
Apr 28 12:40:15 raspberrypi weewx[2299]:   (total_max_count, 
total_count, total_missed, self.stats['pct_good_all']))
Apr 28 12:40:15 raspberrypi weewx[2299]:   TypeError: float 
argument required, not NoneType
Apr 28 12:40:15 raspberrypi weewx[2299]:   Exiting.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

Was wondering if there was a way to add an optional JSON output?  The 
output can aid in debugging an issue.   Right now all my consoles (Davis 
and Acurite) indicate 0.09 inches fell but the driver is indicating 0.07 
inches.  

Thanks for your work on the driver.

Rich

On Wednesday, March 13, 2019 at 7:50:29 PM UTC-4, ljm@gmail.com wrote:

> To all, 
>
> In the weewx forum I started a thread about reception of Davis vantage 
> messages with a RTL-SDR dongle. 
> I have (re)written two programs 
> 1. A modified version of rtldavis which reads the raw messages and print 
> the data to stderr. 
> 2. A weewx-rtld driver which parses the raw data and store the weather 
> data in the weewx database. This driver is not public yet as by now. 
>
> Until now we couldn’t find a usefull set of US frequencies. The modified 
> program rtldavis works resonable well for the EU frequencies. 
> In this thread we will discuss the progress to get a good working program 
> for both EU and US. 
>
> Luc Heijst

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 24 April 2019 19:08:53 UTC-3, Nigel Head wrote:
>
> How do I set the ppm offset in weewx.conf?
>

Use the cmd = line in the [Rtldavis] section.
You can set all desired parameters here except for -tr and -tf
(The values of tr and tf are added by the weewx driver itself.)

Example:

[Rtldavis]
..
cmd = ./work/bin/rtldavis -ppm 7 -maxmissed 4

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 24 April 2019 19:00:58 UTC-3, Nigel Head wrote:
>
> Apr 24 22:57:02 raspberrypi weewx[1790]: rtldavis: data: 22:57:02.337671 
> A0034E823B004F69 105 0 0 0 0 msg.ID=0
> Console Out Hum reads 90%
>

Hi Nigel,

The code is: A0 03 4E 82 3B 00 4F 69
The outside humidity part is: 82 3B
"B' means: digital sensor (variant b)
The hex value is: 382 => 898 decimal => divided by 10 => outside humidity 
89.8%
The Davis console show only integer values, thus 90%

Why I was puzzled?
I have seen the following variants of outside humidity codes:

# A0 00 00 C9 3D 00 2A 87 (digital sensor, variant a)
# A0 01 3A 80 3B 00 ED 0E (digital sensor, variant b)
# A0 01 41 7F 39 00 18 65 (digital sensor, variant c)
# A0 00 00 22 85 00 ED E3 (analog sensor)
# A1 00 DB 00 03 00 47 C7 (no sensor, checked by hex value 
= 000)

What puzzled me is that you sensor reports alternating the b (0xB) and c 
(0x9) variant. So bit 1 (0x02) of your code means something we don't know 
yet. 

You can find the changed weewx-rtldavis driver with the outside humidity 
fix on github.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Luc,

How do I set the ppm offset in weewx.conf?

Using rtl_test and from old experiments against known GSM frequencies, I 
know this RTL dongle needs a ppm offset of +68.
Oddly, when running rtldavis in standalone a -ppm 7 correction puts it 
pretty much spot on, whereas a -ppm 70 puts it a mile off and nothing is 
received !!

Nigel

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Hi Luc,

Ran for 2 mins and the same data for each error (luckily!)

Apr 24 22:57:02 raspberrypi weewx[1790]: rtldavis: data: 22:57:02.337671 
A0034E823B004F69 105 0 0 0 0 msg.ID=0
Apr 24 22:57:02 raspberrypi weewx[1790]: engine: 2019-04-24 22:57:02 BST 
(1556143022) LOOP value 'outHumidity' 439.932 outside limits (0.0, 100.0)
Apr 24 22:57:02 raspberrypi weewx[1790]: rtldavis: chan: 22:57:02.337850 
Hop: {ChannelIdx:2 ChannelFreq:868317250 FreqError:-2853}

Console Out Hum reads 90%

HTH

Nigel

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 24 April 2019 17:48:01 UTC-3, Nigel Head wrote:
>
> Also this dup
>

Hi Nigel,

The rtldavis.go program filters out most duplicate messages.
Now and then a duplicate message is reported by rtldavis.go and then the 
weewx-rtldavis program filters this message.
Nothing to worry about.

Luc
 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Hi Nigel,

The data of your "A" code messages is a complete puzzle for me (and I don't 
say that often!).

Could you please tell me what the outside humidity values are on your Davis 
console?
You have to run the test once more for 2 minutes and write down the outside 
humidities you see on your console during that period.

Thanks in advance!

Luc 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Hi Luc,

As requested

Apr 24 21:31:53 raspberrypi weewx[2237]: rtldavis: info: 21:31:53.103767 
Init ch
   annels: wait max 17 seconds for a message of each 
transmitter
Apr 24 21:32:02 raspberrypi weewx[2237]: rtldavis: info: 21:32:02.811824 
TRANSMITTER 0 SEEN
Apr 24 21:32:02 raspberrypi weewx[2237]: rtldavis: chan: 21:32:02.812278 
Hop: {ChannelIdx:2 ChannelFreq:868317250 FreqError:-608}
Apr 24 21:32:05 raspberrypi weewx[2237]: rtldavis: data: 21:32:05.373595 
500341FF73001407 2 0 0 0 0 msg.ID=0
Apr 24 21:32:05 raspberrypi weewx[2237]: rtldavis: chan: 21:32:05.373768 
Hop: {ChannelIdx:4 ChannelFreq:868557250 FreqError:-508}
Apr 24 21:32:07 raspberrypi weewx[2237]: rtldavis: data: 21:32:07.937045 
900341050334F02A 3 0 0 0 0 msg.ID=0
Apr 24 21:32:07 raspberrypi weewx[2237]: rtldavis: chan: 21:32:07.937206 
Hop: {ChannelIdx:1 ChannelFreq:868197250 FreqError:-473}
Apr 24 21:32:10 raspberrypi weewx[2237]: rtldavis: data: 21:32:10.498829 
8003411EEB00B6F0 4 0 0 0 0 msg.ID=0
Apr 24 21:32:10 raspberrypi weewx[2237]: rtldavis: chan: 21:32:10.499400 
Hop: {ChannelIdx:3 ChannelFreq:868437250 FreqError:-538}
Apr 24 21:32:13 raspberrypi weewx[2237]: rtldavis: data: 21:32:13.062732 
E00341710300C7A9 5 0 0 0 0 msg.ID=0
Apr 24 21:32:13 raspberrypi weewx[2237]: rtldavis: chan: 21:32:13.062891 
Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:-501}
Apr 24 21:32:15 raspberrypi weewx[2237]: rtldavis: data: 21:32:15.624525 
500241FF7300BE56 6 0 0 0 0 msg.ID=0
Apr 24 21:32:15 raspberrypi weewx[2237]: rtldavis: chan: 21:32:15.624685 
Hop: {ChannelIdx:2 ChannelFreq:868317250 FreqError:-1120}
Apr 24 21:32:18 raspberrypi weewx[2237]: rtldavis: data: 21:32:18.186239 
A002417F3B0090D5 7 0 0 0 0 msg.ID=0
Apr 24 21:32:18 raspberrypi weewx[2237]: engine: 2019-04-24 21:32:18 BST 
(1556137938) LOOP value 'outHumidity' 440.835 outside limits (0.0, 100.0)
Apr 24 21:32:18 raspberrypi weewx[2237]: rtldavis: chan: 21:32:18.186455 
Hop: {ChannelIdx:4 ChannelFreq:868557250 FreqError:-985}
Apr 24 21:32:20 raspberrypi weewx[2237]: rtldavis: data: 21:32:20.749697 
8001421EE9000FCD 8 0 0 0 0 msg.ID=0
Apr 24 21:32:20 raspberrypi weewx[2237]: rtldavis: chan: 21:32:20.749853 
Hop: {ChannelIdx:1 ChannelFreq:868197250 FreqError:-915}
Apr 24 21:32:23 raspberrypi weewx[2237]: rtldavis: data: 21:32:23.311535 
E00141710100E548 9 0 0 0 0 msg.ID=0
Apr 24 21:32:23 raspberrypi weewx[2237]: rtldavis: chan: 21:32:23.311685 
Hop: {ChannelIdx:3 ChannelFreq:868437250 FreqError:-1023}
Apr 24 21:32:25 raspberrypi weewx[2237]: rtldavis: data: 21:32:25.875027 
500241FF7100D834 10 0 0 0 0 msg.ID=0
Apr 24 21:32:25 raspberrypi weewx[2237]: rtldavis: chan: 21:32:25.875427 
Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:-948}
Apr 24 21:32:28 raspberrypi weewx[2237]: rtldavis: data: 21:32:28.436767 
A001417F39001865 11 0 0 0 0 msg.ID=0
Apr 24 21:32:28 raspberrypi weewx[2237]: engine: 2019-04-24 21:32:28 BST 
(1556137948) LOOP value 'outHumidity' 440.835 outside limits (0.0, 100.0)
Apr 24 21:32:28 raspberrypi weewx[2237]: rtldavis: chan: 21:32:28.436928 
Hop: {ChannelIdx:2 ChannelFreq:868317250 FreqError:-1633}
Apr 24 21:32:31 raspberrypi weewx[2237]: rtldavis: data: 21:32:30.998573 
8001411EE9009411 12 0 0 0 0 msg.ID=0
.
.
Apr 24 21:33:09 raspberrypi weewx[2237]: rtldavis: data: 21:33:09.438434 
A0034B7F3B00522F 27 0 0 0 0 msg.ID=0
Apr 24 21:33:09 raspberrypi weewx[2237]: engine: 2019-04-24 21:33:09 BST 
(1556137989) LOOP value 'outHumidity' 440.835 outside limits (0.0, 100.0)
Apr 24 21:33:09 raspberrypi weewx[2237]: rtldavis: chan: 21:33:09.438998 
Hop: {ChannelIdx:4 ChannelFreq:868557250 FreqError:-2330}
Apr 24 21:33:12 raspberrypi weewx[2237]: rtldavis: data: 21:33:12.000194 
8003491EE9005551 28 0 0 0 0 msg.ID=0
Apr 24 21:33:12 raspberrypi weewx[2237]: rtldavis: chan: 21:33:12.000351 
Hop: {ChannelIdx:1 ChannelFreq:868197250 FreqError:-2399}
Apr 24 21:33:14 raspberrypi weewx[2237]: rtldavis: data: 21:33:14.561830 
E0024B7103000553 29 0 0 0 0 msg.ID=0
Apr 24 21:33:14 raspberrypi weewx[2237]: rtldavis: chan: 21:33:14.561989 
Hop: {ChannelIdx:3 ChannelFreq:868437250 FreqError:-2618}
Apr 24 21:33:14 raspberrypi weewx[2237]: rtldavis: info: 21:33:14.563868 
duplicate packet: E0024B7103000553
Apr 24 21:33:17 raspberrypi weewx[2237]: rtldavis: data: 21:33:17.125730 
500351FF710069C2 30 0 0 0 0 msg.ID=0
Apr 24 21:33:17 raspberrypi weewx[2237]: rtldavis: chan: 21:33:17.125891 
Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:-2736}
Apr 24 21:33:19 raspberrypi weewx[2237]: rtldavis: data: 21:33:19.687495 
A003547F3B009D66 31 0 0 0 0 msg.ID=0
Apr 24 21:33:19 raspberrypi weewx[2237]: engine: 2019-04-24 21:33:20 BST 
(1556138000) LOOP value 'outHumidity' 440.835 outside limits (0.0, 100.0)
Apr 24 21:33:19 raspberrypi weewx[2237]: rtldavis: chan: 21:33:19.687657 
Hop: {ChannelIdx:2 ChannelFreq:868317250 FreqError:-3258}
Apr 24 21:33:22 raspberrypi weewx[2237]: rtldavis: data: 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Nigel,

When your wind meter is on the same transmitter as the humidity sensor, 
look at data lines starting with A.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 24 April 2019 12:10:12 UTC-3, Nigel Head wrote:
>
> The Pi3 is complaining about 'outHumidity' - what do you think
>

Hi Nigel,

Please change in weewx.conf the following:

debug = 1

[Rtldavis]
debug_rtld  = 2

Then restart weewx-rtldavis

Look at data lines starting with code A00, like:

rtldavis: data: 16:35:27.084624 A0A13D00184D 11 9 10 0 0 msg.ID=0

Please report the data of a few of such lines.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Ha! fat fingers - 2013

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Then it's from the future! Jokes aside, digital sensors were introduced for 
the VP2 line in 2006 so yours must be digital. It means something else is 
the issue, most likely.

On Wednesday, April 24, 2019 at 8:44:27 PM UTC+2, Nigel Head wrote:
>
> Cool, my console is AJ130501...so at least the console is 20013
>
> Nigel
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Cool, my console is AJ130501...so at least the console is 20013

Nigel

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Yes, see: 
https://www.manula.com/manuals/pws/davis-kb/1/en/topic/find-the-model-mfg-code

On Wednesday, April 24, 2019 at 6:44:59 PM UTC+2, Nigel Head wrote:
>
> I believe my VP2 is circa 2013 (it was an eblag special a  little over a 
> couple of years ago)  and I was informed it was a round 3 years old.
> Does the console serial number mean anything, date wise?
>
> Nigel.
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

I believe my VP2 is circa 2013 (it was an eblag special a  little over a 
couple of years ago)  and I was informed it was a round 3 years old.
Does the console serial number mean anything, date wise?

Nigel.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Deja vu. Nigel, how old is your VP2? Is it possible you also have an analog 
T/H sensor pair? I can't remember off the top of my head, but you might 
either need to use another git branch or use a patch. Maybe you're using a 
slightly older version.

On Wednesday, April 24, 2019 at 5:10:12 PM UTC+2, Nigel Head wrote:
>
> Hi Luc,
>
> Some progress.
> a) I first tried on a clean Debian install on a spare Sheevaplug I had (my 
> previous logs are from that) - didn't work, but might be a USB issue? - 
> will try again sometime with a powered USB hub as the Sheevaplug only has 
> one USB port.
>
> b) Made a clean Debian install on a recycled ex thin client - Intel Atom 
> i386 - didn't properly compile rtldavis and so didn't work.
>
> c) Shut down on of my Pi3's and made a clean install on a fresh SD card, 
> compiled/installed everything and it works (well, mostly).
>
> The Pi3 is complaining about 'outHumidity' - what do you think Luc??
> Nothing is being shown on the humidity graph either.
>
> Apr 24 16:00:53 raspberrypi weewx[8765]: engine: 2019-04-24 16:00:53 BST 
> (1556118053) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
> Apr 24 16:01:03 raspberrypi weewx[8765]: engine: 2019-04-24 16:01:03 BST 
> (1556118063) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
> Apr 24 16:01:44 raspberrypi weewx[8765]: engine: 2019-04-24 16:01:44 BST 
> (1556118104) LOOP value 'outHumidity' 471.838 outside limits (0.0, 100.0)
> Apr 24 16:01:54 raspberrypi weewx[8765]: engine: 2019-04-24 16:01:55 BST 
> (1556118115) LOOP value 'outHumidity' 471.838 outside limits (0.0, 100.0)
> Apr 24 16:02:35 raspberrypi weewx[8765]: engine: 2019-04-24 16:02:36 BST 
> (1556118156) LOOP value 'outHumidity' 471.236 outside limits (0.0, 100.0)
> Apr 24 16:02:45 raspberrypi weewx[8765]: engine: 2019-04-24 16:02:46 BST 
> (1556118166) LOOP value 'outHumidity' 471.236 outside limits (0.0, 100.0)
> Apr 24 16:03:26 raspberrypi weewx[8765]: engine: 2019-04-24 16:03:27 BST 
> (1556118207) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
> Apr 24 16:03:37 raspberrypi weewx[8765]: engine: 2019-04-24 16:03:37 BST 
> (1556118217) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
> Apr 24 16:04:18 raspberrypi weewx[8765]: engine: 2019-04-24 16:04:18 BST 
> (1556118258) LOOP value 'outHumidity' 472.741 outside limits (0.0, 100.0)
>
>
> You can see both my console based weewx and the RTLdavis one here 
> www.nthead.co.uk
>
> Once again, thanks for your efforts Luc.
>
> Nigel
>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Hi Luc,

Some progress.
a) I first tried on a clean Debian install on a spare Sheevaplug I had (my 
previous logs are from that) - didn't work, but might be a USB issue? - 
will try again sometime with a powered USB hub as the Sheevaplug only has 
one USB port.

b) Made a clean Debian install on a recycled ex thin client - Intel Atom 
i386 - didn't properly compile rtldavis and so didn't work.

c) Shut down on of my Pi3's and made a clean install on a fresh SD card, 
compiled/installed everything and it works (well, mostly).

The Pi3 is complaining about 'outHumidity' - what do you think Luc??
Nothing is being shown on the humidity graph either.

Apr 24 16:00:53 raspberrypi weewx[8765]: engine: 2019-04-24 16:00:53 BST 
(1556118053) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
Apr 24 16:01:03 raspberrypi weewx[8765]: engine: 2019-04-24 16:01:03 BST 
(1556118063) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
Apr 24 16:01:44 raspberrypi weewx[8765]: engine: 2019-04-24 16:01:44 BST 
(1556118104) LOOP value 'outHumidity' 471.838 outside limits (0.0, 100.0)
Apr 24 16:01:54 raspberrypi weewx[8765]: engine: 2019-04-24 16:01:55 BST 
(1556118115) LOOP value 'outHumidity' 471.838 outside limits (0.0, 100.0)
Apr 24 16:02:35 raspberrypi weewx[8765]: engine: 2019-04-24 16:02:36 BST 
(1556118156) LOOP value 'outHumidity' 471.236 outside limits (0.0, 100.0)
Apr 24 16:02:45 raspberrypi weewx[8765]: engine: 2019-04-24 16:02:46 BST 
(1556118166) LOOP value 'outHumidity' 471.236 outside limits (0.0, 100.0)
Apr 24 16:03:26 raspberrypi weewx[8765]: engine: 2019-04-24 16:03:27 BST 
(1556118207) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
Apr 24 16:03:37 raspberrypi weewx[8765]: engine: 2019-04-24 16:03:37 BST 
(1556118217) LOOP value 'outHumidity' 471.537 outside limits (0.0, 100.0)
Apr 24 16:04:18 raspberrypi weewx[8765]: engine: 2019-04-24 16:04:18 BST 
(1556118258) LOOP value 'outHumidity' 472.741 outside limits (0.0, 100.0)


You can see both my console based weewx and the RTLdavis one here 
www.nthead.co.uk

Once again, thanks for your efforts Luc.

Nigel

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

As for the SDR dongle issues  "r82xx_write: i2c wr failed=-9 reg=12 len=1" 
and "r82xx_set_freq: failed=-9", might want to try in a different USB port 
and ensure the RPI is not indicating low voltage (lightning bolt upper 
right hand corner) during the time you see these errors.

On Tuesday, April 23, 2019 at 6:55:10 PM UTC-4, Nigel Head wrote:
>
> I see some occasional errors as well...
>
> 23:52:05.468829 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
> 23:52:23.397721 Init channels: wait max 17 seconds for a message of each 
> transmitter
> 23:52:23.402227 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
> r82xx_write: i2c wr failed=-9 reg=12 len=1
> r82xx_set_freq: failed=-9
> 23:52:23.951562 SetCenterFreq: 868077250 error: pipe error
> 23:52:41.363466 Init channels: wait max 17 seconds for a message of each 
> transmitter
>
> G'night
>
> Nigel
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

I see some occasional errors as well...

23:52:05.468829 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
23:52:23.397721 Init channels: wait max 17 seconds for a message of each 
transmitter
23:52:23.402227 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
r82xx_write: i2c wr failed=-9 reg=12 len=1
r82xx_set_freq: failed=-9
23:52:23.951562 SetCenterFreq: 868077250 error: pipe error
23:52:41.363466 Init channels: wait max 17 seconds for a message of each 
transmitter

G'night

Nigel

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Hi Luc,

Recompiled and better, but still no cigar (data) !!

pi@sheevaplug:~/work/src/github.com/lheijst/rtldavis$ $GOPATH/bin/rtldavis 
-gain 402
23:36:32.801134 rtldavis.go VERSION=0.12
23:36:32.802467 tr=1 fc=0 ppm=0 gain=402 ex=0 maxmissed=51 actChan=[0] 
maxChan=1
23:36:32.808792 BitRate: 19200
23:36:32.809444 SymbolLength: 14
23:36:32.810007 SampleRate: 268800
23:36:32.810555 Preamble: 1100101110001001
23:36:32.811062 PreambleSymbols: 16
23:36:32.811719 PreambleLength: 224
23:36:32.812227 PacketSymbols: 80
23:36:32.812740 PacketLength: 1120
23:36:32.813345 BlockSize: 512
23:36:32.813841 BufferLength: 2048
Found Rafael Micro R820T tuner
23:36:33.212036 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
Exact sample rate is: 268800.001367 Hz
23:36:33.402663 Supported tuner gain: 0 Db
23:36:33.403512 Supported tuner gain: 9 Db
23:36:33.404303 Supported tuner gain: 14 Db
23:36:33.405080 Supported tuner gain: 27 Db
23:36:33.405855 Supported tuner gain: 37 Db
23:36:33.406719 Supported tuner gain: 77 Db
23:36:33.407453 Supported tuner gain: 87 Db
23:36:33.408161 Supported tuner gain: 125 Db
23:36:33.408882 Supported tuner gain: 144 Db
23:36:33.409578 Supported tuner gain: 157 Db
23:36:33.410276 Supported tuner gain: 166 Db
23:36:33.411005 Supported tuner gain: 197 Db
23:36:33.411706 Supported tuner gain: 207 Db
23:36:33.412403 Supported tuner gain: 229 Db
23:36:33.412527 Supported tuner gain: 254 Db
23:36:33.413133 Supported tuner gain: 280 Db
23:36:33.413256 Supported tuner gain: 297 Db
23:36:33.413370 Supported tuner gain: 328 Db
23:36:33.413793 Supported tuner gain: 338 Db
23:36:33.413990 Supported tuner gain: 364 Db
23:36:33.414386 Supported tuner gain: 372 Db
23:36:33.414791 Supported tuner gain: 386 Db
23:36:33.415221 Supported tuner gain: 402 Db
23:36:33.415483 Supported tuner gain: 421 Db
23:36:33.415749 Supported tuner gain: 434 Db
23:36:33.416087 Supported tuner gain: 439 Db
23:36:33.416424 Supported tuner gain: 445 Db
23:36:33.416760 Supported tuner gain: 480 Db
23:36:33.417101 Supported tuner gain: 496 Db
23:36:33.443209 SetTunerGain 402 Successful
23:36:33.443991 GetTunerGain: 402 Db
23:36:33.444812 SetFreqCorrection 0 ppm Successful
23:36:33.449819 Init channels: wait max 17 seconds for a message of each 
transmitter
23:36:51.400263 Init channels: wait max 17 seconds for a message of each 
transmitter
23:36:51.431887 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
23:37:09.348922 Init channels: wait max 17 seconds for a message of each 
transmitter
23:37:09.380552 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
23:37:27.307983 Init channels: wait max 17 seconds for a message of each 
transmitter
23:37:27.339578 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
23:37:45.263694 Init channels: wait max 17 seconds for a message of each 
transmitter
23:37:45.295215 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}



What else can I try? (it's late and I need some zzz's - tomorrow...)

Thanks for your time on this.

Nigel

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Tuesday, 23 April 2019 12:45:32 UTC-3, Nigel Head wrote:
>
> Can you change the tuner gain?
>

Hi Nigel, 

I have option "gain" added in rtldavis.

Default: -gain 0 selects autogain

The integer value sets the gain value in tenths of a Db.

Supported gain values: 0, 9, 14, 27, 37, 77, 87, 125, 144, 157, 166, 197, 
207,
 229, 254, 280, 297, 328, 338, 364, 372, 386, 402, 421, 434, 439, 445, 480, 
496.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Nigel Head]

Hi Luc,

I'm trying to get rtlsdr receiving on my EU (UK) VP2 and am not getting any 
data when testing with  $GOPATH/bin/rtldavis
I notice that the receiver tuner gain appears to be set to 0 Db
If I use the RTL dongle in Windows and use SDR# and tuner gain to 0, then 
it is as deaf as a post and needs some gain for it to receive signals.
Can you change the tuner gain? I know from other uses in Linux, it is 
possible to set gain(s) or AGC.

Google turns this up...
https://github.com/bemasher/rtldavis/issues/3 (2nd post down with 
possibility to change gain)

My output so far ...
pi@sheevaplug:~$ $GOPATH/bin/rtldavis
16:37:43.031432 rtldavis.go VERSION=0.11
16:37:43.033277 tr=1 fc=0 ppm=0 ex=0 maxmissed=51 actChan=[0] maxChan=1
16:37:43.037735 BitRate: 19200
16:37:43.038632 SymbolLength: 14
16:37:43.039369 SampleRate: 268800
16:37:43.040329 Preamble: 1100101110001001
16:37:43.041106 PreambleSymbols: 16
16:37:43.042106 PreambleLength: 224
16:37:43.043029 PacketSymbols: 80
16:37:43.044103 PacketLength: 1120
16:37:43.044990 BlockSize: 512
16:37:43.045873 BufferLength: 2048
Detached kernel driver
Found Rafael Micro R820T tuner
16:37:43.510046 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
Exact sample rate is: 268800.001367 Hz
16:37:43.701273 SetFreqCorrection 0 ppm Successful
16:37:43.702261 GetTunerGain: 0 Db
16:37:43.707200 Init channels: wait max 17 seconds for a message of each 
transmitter
16:38:01.658391 Init channels: wait max 17 seconds for a message of each 
transmitter
16:38:01.690025 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
16:38:19.641552 Init channels: wait max 17 seconds for a message of each 
transmitter
16:38:19.673082 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
16:38:37.604817 Init channels: wait max 17 seconds for a message of each 
transmitter
16:38:37.636377 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
16:38:55.555271 Init channels: wait max 17 seconds for a message of each 
transmitter
16:38:55.586802 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
16:39:13.509975 Init channels: wait max 17 seconds for a message of each 
transmitter
16:39:13.579969 Hop: {ChannelIdx:0 ChannelFreq:868077250 FreqError:0}
this repeats endlessly

Nigel.

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

Just letting you know the driver (US Frequencies) been running over a week 
without any issues. Thanks for all your work.

Rich


>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

I have my first ISS together with anemometer kit and leaf-soil station now for 
four years. Recently I had to replace a broken temp/hum sensor and the 
rechargeable batteries for my 24h aspiration kit. Never changed other batteries 
for those three stations. I bought a ‘spare’ ISS two years ago as a replacement 
for my broken TFA Primus/Opus station.
And the funny part is: four months a year the sun at my place goes from east 
via north to west, so the solar sensors facing south don’t get any direct 
sunlight that period!

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Right, as I've said, I also don't have a use for their console. Partly for 
reasons you mentioned. But still, fractions in humidity are still useless 
when the instrument accuracy is no better than ±3%. Of course it's more a 
technical viewpoint than an aesthetic :) I agree on the awesomeness, I have 
the devices for about 6 years without a single issue. Hard to say that 
about just anything nowadays...

On Saturday, April 6, 2019 at 9:47:55 PM UTC+2, ljm@gmail.com wrote:
>
> It is the Davis console which presents the lower resolution. Also you 
> can’t read the data of a solar or uv sensor conected to a anemometer kit 
> sender with the Davis console for example. Which all other devices do 
> support. 
> But the Davis ISS and other sensor equipment are awesome!

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

It is the Davis console which presents the lower resolution. Also you can’t 
read the data of a solar or uv sensor conected to a anemometer kit sender with 
the Davis console for example. Which all other devices do support.
But the Davis ISS and other sensor equipment are awesome!

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Meteostick not template!

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

I agree on the console part - as you might know I don't even have one. I 
also don't have a use for it. I have an Envoy but I'm using my own receiver 
instead. But we're talking about data representation and accuracy. The 
console is just one way to show the data (thankfully just an option...)

On Saturday, April 6, 2019 at 9:32:55 PM UTC+2, ljm@gmail.com wrote:
>
> My Davis console stays in the corner of a small room next to my nerwork 
> switch and my raspberry pi’s together with the Davis receivers 
> meteotemplate, wetterbox (of weather365) and a rtl-sdr dongle for rtldavis. 
> For me it is a total waste of money to have a davis console with data 
> logger. Never ever looked at the screen besides the configuration for my 
> two Davis ISS stations. 
>
> Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Kobuki

For some reason the graph was plotting values like 83.783%.  It should plot 
to the tenth of a percent. I will let it run to see what happens.

Rich

On Saturday, April 6, 2019 at 12:30:46 PM UTC-4, kobuki wrote:

> Luc, I was only following the thread half-eyed, were you able to devise a 
> formula for humidity for this old analog sensor?
>
> OTOH, "thousandth of a percent" is not 0.1 percents. It's 3 decimal places 
> after the dot. Rich, are you seeing values like 34.567%? In any case, with 
> a humidity sensor like these, fractions are useless, you don't even need 
> any, Davis isn't using any, for a reason. Accuracy =/= resolution.
>
> On Saturday, April 6, 2019 at 6:24:34 PM UTC+2, ljm@gmail.com wrote:
>>
>> Rich,
>>
>> As the integer humidity_raw value is divided by 10 the resolution is 0,1 
>> percent.
>> This is a 10 times better resolution than the Davis console presents.
>>
>> Luc
>>
>>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Yeah, I know - for me this is completely meaningless. I always set a fixed 
scale so I can tell at a glance what's up without checking the current 
scale so I never see the staircases. For each his own, though. I still say 
if it's good for a reputable vendor, it's good for most of us.

On Saturday, April 6, 2019 at 6:54:59 PM UTC+2, ljm@gmail.com wrote:
>
> Kobuki,
>
> Look at the humidity and soil temp graphs on this page: 
> http://www.lucdesign.nl/_weewx/mstk/index.html
> Then you will see what I mean with smoother graphs.
>
> Luc
>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Kobuki,

Look at the humidity and soil temp graphs on this page: 
http://www.lucdesign.nl/_weewx/mstk/index.html
Then you will see what I mean with smoother graphs.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Kobuki,

I need a set of raw humidity values and the values presented by the vantage 
driver over a reasonable range to be able to correlate the two data-sets.
It depends how much the humidity fluctuates at Pauls place.

A 10-times bigger humidity resolution is not more precise but it will produce 
smoother graphs.
The same for the temp graphs which have a 5-times bigger resolution than the 
Davis ones.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Luc, I was only following the thread half-eyed, were you able to devise a 
formula for humidity for this old analog sensor?

OTOH, "thousandth of a percent" is not 0.1 percents. It's 3 decimal places 
after the dot. Rich, are you seeing values like 34.567%? In any case, with 
a humidity sensor like these, fractions are useless, you don't even need 
any, Davis isn't using any, for a reason. Accuracy =/= resolution.

On Saturday, April 6, 2019 at 6:24:34 PM UTC+2, ljm@gmail.com wrote:
>
> Rich,
>
> As the integer humidity_raw value is divided by 10 the resolution is 0,1 
> percent.
> This is a 10 times better resolution than the Davis console presents.
>
> Luc
>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Rich,

As the integer humidity_raw value is divided by 10 the resolution is 0,1 
percent.
This is a 10 times better resolution than the Davis console presents.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Friday, 5 April 2019 16:24:52 UTC-3, Paul Anderson wrote:
>
>  now won't start until I comment out lines 960 and 961 ?
>

Paul, 

I thought I had removed all references to "_log_unknown", but I forgot one. 
Fixed in commit a911fdd 


You can change line 960 yourself if you like:

Change:
elif self._log_unknown and lines:
into:
elif lines: 

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

To all,

New release of weewx-rtldavis driver

See: https://github.com/lheijst/weewx-rtldavis

Release notes rtldavis.py v0.11

- fixed: self.rain_per_tip is now 0.254 inch for bucket_type 0; 
thanks to Paul Anderson for detecting this bug
- cleaned up coding
- removed parameters log_unknown_sensors and log_unmapped_sensors
- added parameter save_pct_good_per_transmitter; default is False
- saving frequency errors of first 5 frequencies now limited to EU band
- pct_good of transmitter 1 is not saved when we have only one transmitter
because pct_good_0 is the same as pct_good_all
- the mapping of pct_good per channel is now controlled by the 
DEFAULT_SENSOR_MAP
note: the mapping of pct_good_all remains hardcoded mapped to 
rxCheckPercent
- added debug logging for raw humidity data; default: no logging

  Again, thanks to Paul Anderson and Rich T for testing!

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 3 April 2019 22:49:10 UTC-3, Paul Anderson wrote:
>
> rtldavis.py
> Line 735
> change this
> self.rain_per_tip = 0.0254 if bucket_type == 0 else 0.2 # mm
>
> to
> self.rain_per_tip = 0.254 if bucket_type == 0 else 0.2 # mm
>

Paul,

Good catch, thanks!

I don't know how it got there; I copied the parser section from 
meteostick.py and there it is 0.254.

Luc  

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Paul Anderson]

We had some rain today and noticed that rtl-davis was reporting very low 
amount. After checking Bucket size was set correctly for my US bucked 
looked at databases vales for both my normal production and the development 
machine. Bucket tips should record 0.01 however they were 0.001
Development machine rtldavis:0.01
sqlite> select datetime,sum(rain) from archive where datetime between 
1554253200 and datetime('now');
1554341700|0.037

Production davis vantage 
sqlite> select datetime,sum(rain) from archive where datetime between 
1554253200 and datetime('now');
1554341700|0.37

Seems like a simple decimal point error.
Maybe as simple as 
rtldavis.py
Line 735
change this
self.rain_per_tip = 0.0254 if bucket_type == 0 else 0.2 # mm

to
self.rain_per_tip = 0.254 if bucket_type == 0 else 0.2 # mm
Unfortunately I don't know if more changes are required because by the time 
I made the change it stopped raining!  
Thanks
Paul  

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Paul Anderson]

That sounds OK. Slightly nervous about running a modified weewx-vantage 
driver on my production machine, but I guess I will get over my fears:) BTW 
both machines run ntp to the same server list , so times are always close 
to identical. Also please be aware that on both machines WeeWx logs to 
/var/log/weewx.log not syslog. Also the logs get rotated at midnight daily.
Values came from weewx.sdb I checked to be sure and there are no 
corrections being applied by WeeWx or the vantage console.
Humidity Values Seen:
Last Week 19% - 96%
Last Month 13% - 98%
Last Year 13% - 99% 

Thanks
Paul
On Wednesday, April 3, 2019 at 8:16:39 AM UTC-4, ljm@gmail.com wrote:
>
> Paul,
>
> For the parsing of your analog humidity sensor we need probably a look up 
> table, as we have used similar for the soul moisture and leaf-wetness 
> sensor data.
>
> There is a positive relation between the raw humidity value and the 
> temperature as you can see in the attached table.
> Each set with the same raw humidity codes has different humidity 
> percentages as result of different outTemps. 
>
> For the look up table I will need the raw data over a as big humidity 
> range as possible. 0-100 % would be ideal, but let's see how far we come.
>
> Paul, what are the lowest and highest humidity values you have recorded 
> the last months? With this range we got to work.
> And which driver you use on your other computer? Is this the weewx-vantage 
> driver?
>
> I suggest we do the following:
> 1. I modify both weewx-vantage and weewx-rtldriver so, that they will 
> output a debug line showing the raw values (rtldavis) and decoded values 
> (vantage).
> 2. You run both programs during a week. The RPI saves 8 days of syslog.
> 3. Assuming both computers running these drivers have about the same 
> system times, we can combine these two sets of debug data in one table and 
> come with a table similar as attached below, but with a greater range. 
> 4. With this set we can try to find a correlation formula.
> 5. When a correlation formula could not be found, I will compose a lookup 
> table with segments where the values within can be interpolated lineair.
>
> What do you think?
>
> Luc
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 3 April 2019 10:27:22 UTC-3, kobuki wrote:
>
> Alright. The leaf wetness sensor is a completely different animal, I think 
> it can be ignored. If anything, in air, the temps are inversely 
> proportional WRT humidity because of natural reasons, not because they are 
> mathematically related. Making a lookup table as you hinted is a workable 
> solution. Based on that you could even invent a suitable approximation 
> formula. I might try to convert the raw value and the sensor specs to 
> invent something. Sadly all they provide is a printed curve, no numerical 
> values. I'll try to dig for more info or maybe MCU C code later, I'm sure 
> capacitive sensors have working formulas for them since long ago.
>

Right,

But first of all we need a table with raw and parsed values over a bigger 
humidity range than the 9% we have now.

Luc  

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Wednesday, 3 April 2019 09:37:32 UTC-3, kobuki wrote:
>
> *Temperature and humidity are independent values.* *There is no direct 
> relation between the two*.
>

Kobuki,

I know, you mentioned that before. :-)

I work with the following data:
1. Raw humidity values as received in the weewx-rtldavis driver. Not sure 
about the hi-bits because one byte always had value 0x85; for now I assume 
the right nibble (5) are the hi-bit part of the raw humidity value.
2. Values received from the Vantage driver, both humidity and outTemp 
values.

We know the Davis console and the rtldavis.go program will receive the same 
radio-signals from the ISS, so the raw message codes for both are equal.

We then take a group of samples with the same raw humidity value.
They all should have the same humidity % value as presented by the Davis 
console, which is read by the Vantage driver. Shouldn't they?

But, they have not!

For samples with all the same raw humidity value, the samples with the 
higher percentage presented by the Vantage driver have also a higher 
temperature value.
That's why I presume a relation between the two.

Luc

PS. I noticed the same behaviour for the soil-moisture and leaf-wetness 
sensors. By experiment I detected norm factors to compensate for 
temperature influences.
See the code below:

# soil moisture potential
# Lookup soil moisture potential in SM_MAP
norm_fact = 0.009  # Normalize potential_raw
soil_moisture = lookup_potential(
"soil_moisture", norm_fact,
potential_raw, temp_c, SM_MAP)


# leaf wetness potential
# Lookup leaf wetness potential in LW_MAP
norm_fact = 0.0  # Do not normalize 
potential_raw
leaf_wetness = lookup_potential(
"leaf_wetness", norm_fact,
potential_raw, temp_c, LW_MAP)

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Luc,

Sorry, but I have to bark in again. *Temperature and humidity are 
independent values.* *There is no direct relation between the two*. It's a 
normal, natural occurrence to see them move with different sign day by day. 
You can measure humidity by itself - hygrometers are stand-alone 
instruments you can buy in stores, either analog or digital. I repeat, *there 
is no direct relation*. (There exist indirect relations, though, like the 
sun drying up humidity in the air, etc.) You cannot use one to 
calculate/tune the other by definition.

Please see the PDF specification sheet of the actual humidity sensor used 
in the ISS. I've linked it before, if you don't find it, I will link it 
again. That is something that will help you with the calculations. Also, 
please feel free to ask a weather technician or meteorologist if you don't 
believe me - there's a common friend of ours. Just email him (it's private 
info so I won't mention his name but you'll know). Of course there are 
learning/study material on the net in great numbers.

You see a positive relation between humidity and temperature because of the 
nature of the humidity calculation. The calculation relies on the 
capacitance of the sensor. Temperature increases -> humidity in the air is 
getting lower -> resonant frequency of the cap is getting lower -> its 
reciprocal, the period is getting higher. I think what we have as raw 
humidity value is the period pertaining to the frequency, expressed in some 
digital unit: it's x times the actual periods in millisecs, for instance. 
If we can find x, we can make a formula. There's also some constant shift, 
since the cap only works from 10% to 90% (per specs).

On Wednesday, April 3, 2019 at 2:16:39 PM UTC+2, ljm@gmail.com wrote:
>
> Paul,
>
> For the parsing of your analog humidity sensor we need probably a look up 
> table, as we have used similar for the soul moisture and leaf-wetness 
> sensor data.
>
> There is a positive relation between the raw humidity value and the 
> temperature as you can see in the attached table.
> Each set with the same raw humidity codes has different humidity 
> percentages as result of different outTemps. 
>
> For the look up table I will need the raw data over a as big humidity 
> range as possible. 0-100 % would be ideal, but let's see how far we come.
>
> Paul, what are the lowest and highest humidity values you have recorded 
> the last months? With this range we got to work.
> And which driver you use on your other computer? Is this the weewx-vantage 
> driver?
>
> I suggest we do the following:
> 1. I modify both weewx-vantage and weewx-rtldriver so, that they will 
> output a debug line showing the raw values (rtldavis) and decoded values 
> (vantage).
> 2. You run both programs during a week. The RPI saves 8 days of syslog.
> 3. Assuming both computers running these drivers have about the same 
> system times, we can combine these two sets of debug data in one table and 
> come with a table similar as attached below, but with a greater range. 
> 4. With this set we can try to find a correlation formula.
> 5. When a correlation formula could not be found, I will compose a lookup 
> table with segments where the values within can be interpolated lineair.
>
> What do you think?
>
> Luc
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Paul,

For the parsing of your analog humidity sensor we need probably a look up 
table, as we have used similar for the soul moisture and leaf-wetness 
sensor data.

There is a positive relation between the raw humidity value and the 
temperature as you can see in the attached table.
Each set with the same raw humidity codes has different humidity 
percentages as result of different outTemps. 

For the look up table I will need the raw data over a as big humidity range 
as possible. 0-100 % would be ideal, but let's see how far we come.

Paul, what are the lowest and highest humidity values you have recorded the 
last months? With this range we got to work.
And which driver you use on your other computer? Is this the weewx-vantage 
driver?

I suggest we do the following:
1. I modify both weewx-vantage and weewx-rtldriver so, that they will 
output a debug line showing the raw values (rtldavis) and decoded values 
(vantage).
2. You run both programs during a week. The RPI saves 8 days of syslog.
3. Assuming both computers running these drivers have about the same system 
times, we can combine these two sets of debug data in one table and come 
with a table similar as attached below, but with a greater range. 
4. With this set we can try to find a correlation formula.
5. When a correlation formula could not be found, I will compose a lookup 
table with segments where the values within can be interpolated lineair.

What do you think?

Luc
Table showing the raw humidity values of the weewx-rtldavis driver 
and the measured humidity and temperature values of the weewx-vantage driver.

humcod  outHumidity outTemp
129965,554,4
129965,654,4
129965,654,5
129965,654,6
130065,454,3
130065,554,4
130065,454,4
130065,754,7
130165,254,2
130165,354,3
130165,854,8
130165,854,8
130265,154,3
130264,954,4
130265,154,4
130265,954,8
130265,954,9
130266,055,1
130366,055,3
130366,055,4
130464,854,4
130464,754,4
130464,654,5
130466,055,5
130466,155,7
130466,155,9
130466,156,2
130566,056,3
130566,056,4
130565,956,4
130565,856,4
130565,856,4
130565,856,4
130565,856,4
130565,756,4
130665,756,4
130665,656,4
130765,656,4
130765,656,5
130865,556,5
130865,656,5
130965,556,4
131065,556,4
131065,556,4
131165,556,4
131265,556,4
131265,556,4
131365,056,3
131365,056,3
131365,556,4
131465,156,3
131465,156,3
131464,856,3
131465,456,4
131464,956,4
131564,756,3
131565,256,4
131565,456,4
131565,356,4
131565,356,4
131664,756,3
131664,656,3
131664,556,3
131764,556,2
131864,556,1
131964,656,0
132064,656,0
132164,655,8
132264,755,7
132464,655,7
132564,655,7
132664,655,7
132764,555,7
132964,255,7
132964,455,7
132964,455,7
132964,355,7
132964,355,7
132964,155,8
132964,055,8
133063,856,0
133163,756,1
133163,656,1
133263,456,2
133363,356,3
133463,256,3
133563,156,3
133563,156,3
133663,156,3
133763,156,3
133863,156,2
133963,156,2
134263,156,3
134662,956,4
135162,956,5
135362,457,2
135462,856,6
135462,357,4
135562,756,9
135562,657,0
135562,557,1
135662,357,6
135662,157,8
135762,856,7
136162,058,1
136461,658,8
136556,266,7
136661,259,4
136960,660,0
136956,166,9
137060,460,3
137160,460,2
137256,166,9
137360,560,3
137660,560,3
137756,466,3
138060,660,2
138456,565,8
138660,760,3
138956,465,8
139460,560,6
139459,862,2
139559,462,6
139558,963,5
139660,161,6
139656,765,9
139760,461,0
139757,065,7
139859,263,1
139958,963,2
140059,163,0
140058,164,7
140158,564,1
140157,665,3

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Note that the capacitive type humidity sensor is only usable between 10 and 
90% - and add to that the age of Paul's device which is long over it's life 
cycle. All sensors tend to drift and I wouldn't bet on its accuracy any 
more. In any case, for the old sensor we shouldn't see values outside of 
that band, and even if we do it's pretty much useless per specs.

OTOH, temperature and humidity are independent metrics. There's only an 
indirect relation between them, influenced only by current weather 
conditions. (Like how a sunny day dries up most of the humidity in the air.)

On Monday, April 1, 2019 at 1:57:29 AM UTC+2, ljm@gmail.com wrote:
>
> Paul,
>
> This is what I have so far.
>
> I have created a table with the one-byte decimal data of the humidity. The 
> other byte, until now, always is 85, but it is likely some bits of the "85" 
> byte are used to extend the code.
> The question is which bytes?
>
> In the ideal situation we should have sampled data from 0 to 100% 
> humidity. Now we only have a small band: 54-67 % humidity.
>
> In the the attached plot file you can see that the temp has influence. 
> Currently I can't get MS Excel Analysis Tool Pack activated, so I got stuck 
> right now.
>
> Luc 
>
> code  Hum Temp
> 2165,254,2
> 2165,354,3
> 2065,454,3
> 2265,154,3
> 2464,854,4
> 2264,954,4
> 2265,154,4
> 2065,554,4
> 2065,454,4
> 1965,554,4
> 1965,654,4
> 2464,754,4
> 2464,654,5
> 1965,654,5
> 1965,654,6
> 2065,754,7
> 2165,854,8
> 2165,854,8
> 2265,954,8
> 2265,954,9
> 2266,055,1
> 2366,055,3
> 2366,055,4
> 2466,055,5
> 4964,255,7
> 4464,655,7
> 4564,655,7
> 4664,655,7
> 4764,555,7
> 4964,455,7
> 4964,455,7
> 4964,355,7
> 4964,355,7
> 2466,155,7
> 4264,755,7
> 4964,155,8
> 4164,655,8
> 4964,055,8
> 2466,155,9
> 4064,656,0
> 5063,856,0
> 3964,656,0
> 5163,756,1
> 3864,556,1
> 5163,656,1
> 2466,156,2
> 5863,156,2
> 5963,156,2
> 3764,556,2
> 5263,456,2
> 2566,056,3
> 3365,056,3
> 3564,756,3
> 3664,756,3
> 3664,656,3
> 3664,556,3
> 5363,356,3
> 5463,256,3
> 5563,156,3
> 5563,156,3
> 5663,156,3
> 5763,156,3
> 3465,156,3
> 3365,056,3
> 6263,156,3
> 3465,156,3
> 3464,856,3
> 2566,056,4
> 3565,256,4
> 2565,956,4
> 2565,856,4
> 2565,856,4
> 2565,856,4
> 2565,856,4
> 2565,756,4
> 2665,756,4
> 2665,656,4
> 2965,556,4
> 3065,556,4
> 3065,556,4
> 3165,556,4
> 3265,556,4
> 3265,556,4
> 3365,556,4
> 3465,456,4
> 3565,456,4
> 3565,356,4
> 3565,356,4
> 3464,956,4
> 6662,956,4
> 2765,656,4
> 2865,556,5
> 7162,956,5
> 2765,656,5
> 2865,656,5
> 7462,856,6
> 7762,856,7
> 7562,756,9
> 7562,657,0
> 7562,557,1
> 7362,457,2
> 7462,357,4
> 7662,357,6
> 7662,157,8
> 8162,058,1
> 8461,658,8
> 8661,259,4
> 8960,660,0
> 10060,660,2
> 9160,460,2
> 10660,760,3
> 9360,560,3
> 9660,560,3
> 9060,460,3
> 11460,560,6
> 11760,461,0
> 11660,161,6
> 11459,862,2
> 11559,462,6
> 12059,163,0
> 11859,263,1
> 11958,963,2
> 11558,963,5
> 12158,564,1
> 12058,164,7
> 12157,665,3
> 11757,065,7
> 10956,465,8
> 10456,565,8
> 11656,765,9
> 9756,466,3
> 8556,266,7
> 8956,166,9
> 9256,166,9
>
>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Paul,

This is what I have so far.

I have created a table with the one-byte decimal data of the humidity. The 
other byte, until now, always is 85, but it is likely some bits of the "85" 
byte are used to extend the code.
The question is which bytes?

In the ideal situation we should have sampled data from 0 to 100% humidity. 
Now we only have a small band: 54-67 % humidity.

In the the attached plot file you can see that the temp has influence. 
Currently I can't get MS Excel Analysis Tool Pack activated, so I got stuck 
right now.

Luc 

code  Hum Temp
2165,254,2
2165,354,3
2065,454,3
2265,154,3
2464,854,4
2264,954,4
2265,154,4
2065,554,4
2065,454,4
1965,554,4
1965,654,4
2464,754,4
2464,654,5
1965,654,5
1965,654,6
2065,754,7
2165,854,8
2165,854,8
2265,954,8
2265,954,9
2266,055,1
2366,055,3
2366,055,4
2466,055,5
4964,255,7
4464,655,7
4564,655,7
4664,655,7
4764,555,7
4964,455,7
4964,455,7
4964,355,7
4964,355,7
2466,155,7
4264,755,7
4964,155,8
4164,655,8
4964,055,8
2466,155,9
4064,656,0
5063,856,0
3964,656,0
5163,756,1
3864,556,1
5163,656,1
2466,156,2
5863,156,2
5963,156,2
3764,556,2
5263,456,2
2566,056,3
3365,056,3
3564,756,3
3664,756,3
3664,656,3
3664,556,3
5363,356,3
5463,256,3
5563,156,3
5563,156,3
5663,156,3
5763,156,3
3465,156,3
3365,056,3
6263,156,3
3465,156,3
3464,856,3
2566,056,4
3565,256,4
2565,956,4
2565,856,4
2565,856,4
2565,856,4
2565,856,4
2565,756,4
2665,756,4
2665,656,4
2965,556,4
3065,556,4
3065,556,4
3165,556,4
3265,556,4
3265,556,4
3365,556,4
3465,456,4
3565,456,4
3565,356,4
3565,356,4
3464,956,4
6662,956,4
2765,656,4
2865,556,5
7162,956,5
2765,656,5
2865,656,5
7462,856,6
7762,856,7
7562,756,9
7562,657,0
7562,557,1
7362,457,2
7462,357,4
7662,357,6
7662,157,8
8162,058,1
8461,658,8
8661,259,4
8960,660,0
10060,660,2
9160,460,2
10660,760,3
9360,560,3
9660,560,3
9060,460,3
11460,560,6
11760,461,0
11660,161,6
11459,862,2
11559,462,6
12059,163,0
11859,263,1
11958,963,2
11558,963,5
12158,564,1
12058,164,7
12157,665,3
11757,065,7
10956,465,8
10456,565,8
11656,765,9
9756,466,3
8556,266,7
8956,166,9
9256,166,9

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Paul Anderson]

Thanks for explaining it to me. I just did a " grep 'packet missed '" on 
the log file and thought I understood:)


Thanks
Paul

On Sunday, March 31, 2019 at 3:49:43 PM UTC-4, ljm@gmail.com wrote:
>
> Paul, 
>
> The number of time-out (“missed”) messages is not the same as the real 
> number of missed signals. The weewx-rtldavis driver has the following 
> calculation: number of missed signals is theoretical number of expected 
> signals minus number of received signals. For one transmitter the data you 
> found might be close, but if there are more transmitters near-by, the 
> hopping frequencies will interfere at a regular interval. In my situation, 
> with four transmitters active, about 10% of the messages of each 
> transmitter is lost. 
> Channel 0 should get a message each 2.5625 seconds; add 0.0625 seconds for 
> each next channel. The messages of channel 7 should come exactly each 3.0 
> seconds. 
>
> Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Paul,

The number of time-out (“missed”) messages is not the same as the real number 
of missed signals. The weewx-rtldavis driver has the following calculation: 
number of missed signals is theoretical number of expected signals minus number 
of received signals. For one transmitter the data you found might be close, but 
if there are more transmitters near-by, the hopping frequencies will interfere 
at a regular interval. In my situation, with four transmitters active, about 
10% of the messages of each transmitter is lost.
Channel 0 should get a message each 2.5625 seconds; add 0.0625 seconds for each 
next channel. The messages of channel 7 should come exactly each 3.0 seconds.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Ok, not so good idea thus...

Paul, did you play with your antenna setup? I have my antenna situated on a 
metal lid of a round cookies drum. Receiving my four Davis transmitters goes 
better when the radio signals go through a stone wall than to an antenne 
situated in the neighbourhoud of metal anti-theft racks in front of the windows.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Guys, aside from the stick PPM, there should be no reason to fiddle with 
frequency correction. 10-20 kHz is easily correctable with AFC, or at least 
the code and the stick must be capable of it, otherwise it can safely be 
called useless. All of the hardware receivers I've encountered can do that. 
If this solution can't, then it's good for toying around and for fun and 
learning but not much else, honestly. I'm not sure if any packet statistics 
degradation is stemming from such small errors. Just my 2¢.

On Sunday, March 31, 2019 at 7:44:50 PM UTC+2, ljm@gmail.com wrote:
>
> Paul, 
>
> Do you think a frequency correction per transmitter would help? Or would 
> it be too difficult for new users to configure?
>
> Luc
>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Paul, 

Do you think a frequency correction per transmitter would help? Or would it be 
too difficult for new users to configure?

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Paul Anderson]

Sorry did not forget this request for a testlife just got busy:) 
Started a test last night at midnight , planning on running until noon 
today. Does output temp and humidity data for my old analog sensor, temp 
runs very close with in .4 F, humidity runs low but does not seem like  
linear offset error. Last night was low by 10 now it's low by 3.   Test is 
only running as -tr 1 because if I run tr-3  there are to many receive 
errors. Not programs fault rather my old tired equipment . My ISS and Wind 
Transmitters differ in frequency by app 10.5 Khz. That makes it very hard 
to set a PPM that both can hear with. Difference between transmitters is 
over 12 PPM. 
And it's real if I look on Davis Console diagnostics screen it shows ISS as 
correction factor of +6 and Wind as correction factor of -21.Maybe poor old 
tired equipment to blame. Surprisingly Davis console shows 98% good receive 
for ISS and 92% for wind.   

Thanks
Paul
On Friday, March 29, 2019 at 4:17:43 PM UTC-4, ljm@gmail.com wrote:
>
> On Friday, 29 March 2019 15:50:41 UTC-3, Paul Anderson wrote:
>>
>> It is a pretty old VP2 from April of 2006.
>>
>
> Paul,
>
> For the few samples I got from you I have found a formula. 
> I don't understand the logic of the formula, but it works for these 
> samples. :-)  I need more data to be sure.
> Could you please change the parsing section of humidity in your 
> rtldavis.py with the following?
>
> ===
> elif message_type == 0xA:
> # outside humidity
> # message examples:
> # A0 00 00 80 85 00 3E 1F (old model vantage pro)
> # A0 00 00 C9 3D 00 2A 87 (new model vantage pro)
> # A1 00 DB 00 03 00 47 C7 (no sensor)
> humidity_raw = ((pkt[4] >> 4) << 8) + pkt[3]
> if humidity_raw != 0:
> # valid humidity value
> if pk[4] == 0x85:
> # format of old model Vantage Pro2
> humidity = (680 - pkt[3]) / 10.0
> else:
> # format of new model Vantage Pro2
> humidity = humidity_raw / 10.0
> if data['channel'] == th1_ch:
> data['humid_1'] = humidity
> elif data['channel'] == th2_ch:
> data['humid_2'] = humidity
> else:
> data['humidity'] = humidity
> dbg_parse(2, "humidity_raw=0x%03x value=%s" %
>   (humidity_raw, humidity))
> ===
>
> Then let the program run over night and send me by mail the zipped syslog 
> and syslog.1 files tomorrow
> Also I would like a list of the 5-minute averages in the weewx database 
> over the same period.
>
> Thanks in advance.
>
> To kobuki: the hex-code is checked both in protocol.go and rtldavis.py for 
> crc-errors. Both programs didn't complain.
>
> Luc
>  
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

I think that will be a good approach, let the user decide if they want to 
write it to the database or not.  Everything else is tracking with the 
console.

Rich 

On Saturday, March 30, 2019 at 11:36:30 PM UTC-4, ljm@gmail.com wrote:

> Rich, 
>
> The pct good data will be written to the database, but you don’t need two 
> values pct good with the same content; just write one. The overall tag will 
> be rxpercent. 
> I will add a parameter to let one chooce to have individual pct good 
> written to the database or not. Default will be no. 
>
> Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Rich,

The pct good data will be written to the database, but you don’t need two 
values pct good with the same content; just write one. The overall tag will be 
rxpercent.
I will add a parameter to let one chooce to have individual pct good written to 
the database or not. Default will be no.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

For now I will comment those lines out.  As for signal quality, calculating 
 the average percentage good for one transmitter I think is beneficial.  
Over time you might notice some signal degradation, which could indicate 
you might have an issue with transmitter or receiver. 

Thanks
Rich

On Saturday, March 30, 2019 at 10:30:29 PM UTC-4, ljm@gmail.com wrote:

> Rich, 
>
> Good point, thanks! 
>
> First of all I didn’t realize it is useless to calculate an average 
> percentage good when you only have one transmitter. 
>
> Secondly, the pct good values don’t use the sensor map but are ‘hardcoded’ 
> to the fields they use. I have copied this from the meteostick driver and 
> will sort out why the program doesn’t use the sensor map. Now the values 
> are written to the database unless you comment out the lines in the archive 
> section of the program where the values are written. 
>
> Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Rich,

Good point, thanks! 

First of all I didn’t realize it is useless to calculate an average percentage 
good when you only have one transmitter.

Secondly, the pct good values don’t use the sensor map but are ‘hardcoded’ to 
the fields they use. I have copied this from the meteostick driver and will 
sort out why the program doesn’t use the sensor map. Now the values are written 
to the database unless you comment out the lines in the archive section of the 
program where the values are written.

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[rich T]

Luc

The driver seems to be working fine.  What I notice that identical values 
are being written into extraTemp1 and rxCheckPercent columns of the archive 
database.  Even though I'm mapping only "rxCheckPercent" value, it appears 
in both the "Temperature1" and "Signal Quality" fields of the Seasons skin. 
Do I need to REM anything else out in rtldavis.py?

rtldavis mapping:

DEFAULT_SENSOR_MAP = {
  'windSpeed': 'wind_speed',
  'windDir': 'wind_dir',
  'outTemp': 'temperature',
  'outHumidity': 'humidity',
# To use a rainRate calculation from this driver that closely matches
# that of a Davis station, uncomment the rainRate field then specify
# rainRate = hardware in section [StdWXCalculate] of weewx.conf
  'rainRate': 'rain_rate',
  'radiation': 'solar_radiation',
  #'UV': 'uv',
  'rxCheckPercent': 'pct_good',
  'txBatteryStatus': 'bat_iss'
}

weewx sensor map:

[[sensor_map]]

outTemp = temperature
outHumidity = humidity
windSpeed = wind_speed
windDir = wind_dir
rainRate = rain_rate
radiation = solar_radiation
txBatteryStatus = bat_iss
rxCheckPercent = pct_good

Thanks
Rich

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Yeah, it could be the same sensor set inside. But Paul just has an old ISS 
where the sensor is located inside the screen just like ours in the newer 
version. I've linked a sensor spec page with a sensor that has identical 
specs as the old one actually in the ISS, please see one of my previous 
posts. You can find the actual part specs on the second link. In that PDF 
they spec the accuracy and give an RH/cap curve. My theory is that the old 
SIM board somehow measures a value linearly related to the capacity, and 
transmits that value as the actual raw value in the packets. If we consider 
the RH/cap curve linear, calculating the RH value might be as simple as a 
division by a fixed constant. For this rare case a linear function just 
might be good enough.

On Friday, March 29, 2019 at 10:51:02 PM UTC+1, ljm@gmail.com wrote:
>
> On Friday, 29 March 2019 18:40:14 UTC-3, kobuki wrote:
>>
>>  We're dealing with the capacitive humidity sensor now, right?
>>
>
> Yep! So far I couldn't find on the internet the formula for the Davis 
> polymer humidity sensor. Are we the first ones? Again???
>
> This I found here: 
> https://www.davisinstruments.com/product_documents/weather/spec_sheets/7859_spec_Rev_D.pdf
>
> *"The humidity sensor is a thin film capacitor element. A dielectric 
> polymer layer absorbs water molecules from the*
> *air through a thin metal electrode, which causes a change in capacitance 
> proportional to relative humidity."*
>
> Luc
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Friday, 29 March 2019 18:40:14 UTC-3, kobuki wrote:
>
>  We're dealing with the capacitive humidity sensor now, right?
>

Yep! So far I couldn't find on the internet the formula for the Davis 
polymer humidity sensor. Are we the first ones? Again???

This I found here: 
https://www.davisinstruments.com/product_documents/weather/spec_sheets/7859_spec_Rev_D.pdf

*"The humidity sensor is a thin film capacitor element. A dielectric 
polymer layer absorbs water molecules from the*
*air through a thin metal electrode, which causes a change in capacitance 
proportional to relative humidity."*

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Yes, right, I saw that too, that's why I said sorry in my previous post. I 
also concluded we indeed have the old type analog sensors. In fact, I 
should have known by the age of the ISS - it's from 2006...

Therefore I don't think I know what you'd like to point out with the log 
excerpt - care to add some details? We're dealing with the capacitive 
humidity sensor now, right?

On Friday, March 29, 2019 at 10:35:10 PM UTC+1, ljm@gmail.com wrote:
>
> On Friday, 29 March 2019 17:48:37 UTC-3, kobuki wrote:
>>
>> Right - sorry. But, then we do have an analog capacitive sensor.
>>
>
> Kobuki,
>
> I checked Pauls logging and this I've got for the thermister temperature:
>
> Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: data: 13:48:26.296732 
> 8075C5000E79 5 4 0 0 0 msg.ID=0
> Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: r (k ohm) 16.7307020296 
> temp_raw 471 thermistor_temp 13.4890938147
> Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: thermistor temp_raw=0x1d7 
> temp_c=13.4890938147
> Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: pkt= {'outTemp': 
> 13.489093814713613, 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 
> 1553881706}
>
> Luc 
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Friday, 29 March 2019 17:48:37 UTC-3, kobuki wrote:
>
> Right - sorry. But, then we do have an analog capacitive sensor.
>

Kobuki,

I checked Pauls logging and this I've got for the thermister temperature:

Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: data: 13:48:26.296732 
8075C5000E79 5 4 0 0 0 msg.ID=0
Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: r (k ohm) 16.7307020296 
temp_raw 471 thermistor_temp 13.4890938147
Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: thermistor temp_raw=0x1d7 
temp_c=13.4890938147
Mar 29 13:48:26 pi3-dev weewx[8185]: rtldavis: pkt= {'outTemp': 
13.489093814713613, 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 
1553881706}

Luc 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Right - sorry. But, then we do have an analog capacitive sensor.

According to 
http://www.wxforum.net/index.php?topic=33534.msg340277#msg340277 we're 
dealing with a sensor that precedes this one: 
https://www.newark.com/vishay-bc-components/2322-691-90001/humidity-sensor/dp/89F5822

They have apparently identical specs. On the second link there's a PDF with 
specs for the part. They don't state curve details, though.

On Friday, March 29, 2019 at 9:36:44 PM UTC+1, ljm@gmail.com wrote:
>
> On Friday, 29 March 2019 17:28:47 UTC-3, kobuki wrote:
>>
>> But if I'm right, temps should also be wrong. For the NTC Davis is using 
>> we already have the formula IIRC. 
>>
>
> Kobuki,
>
> You are wrong! :-) The analog temperatures are calculated right, see code 
> below:
>
> 
> elif message_type == 8:
> # outside temperature
> # message examples:
> # 80 00 00 33 8D 00 25 11 (digital temp)
> # 81 00 00 59 45 00 A3 E6 (analog temp)
> # 81 00 DB FF C3 00 AB F8 (no sensor)
> temp_raw = (pkt[3] << 4) + (pkt[4] >> 4)  # 12-bits temp value
> if temp_raw != 0xFFC:
> if pkt[4] & 0x8:
> # digital temp sensor
> temp_f = temp_raw / 10.0
> temp_c = weewx.wxformulas.FtoC(temp_f) # C
> dbg_parse(2, "digital temp_raw=0x%03x temp_f=%s temp_c=%s"
>   % (temp_raw, temp_f, temp_c))
> else:
> # analog sensor (thermistor)
> temp_raw /= 4  # 10-bits temp value
> temp_c = calculate_thermistor_temp(temp_raw)
> dbg_parse(2, "thermistor temp_raw=0x%03x temp_c=%s"
>   % (temp_raw, temp_c))
> if data['channel'] == th1_ch:
> data['temp_1'] = temp_c
> elif data['channel'] == th2_ch:
> data['temp_2'] = temp_c
> else:
> data['temperature'] = temp_c
> 
>  
> The formula of the humidity I didn't know. Probably my formula wont work 
> then...
>
> Luc
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

Paul,

I've got two typo's in the code I send you. Sorry for that! The right code 
should be:

=
elif message_type == 0xA:
# outside humidity
# message examples:
# A0 00 00 80 85 00 3E 1F (old model vantage pro)
# A0 00 00 C9 3D 00 2A 87 (new model vantage pro)
# A1 00 DB 00 03 00 47 C7 (no sensor)
humidity_raw = ((pkt[4] >> 4) << 8) + pkt[3]
if humidity_raw != 0:
# valid humidity value
if pkt[4] == 0x85:
# format of old model Vantage Pro2
humidity = (680 - pkt[3]) / 10.0
else:
# format of new model Vantage Pro2
humidity = humidity_raw / 10.0
if data['channel'] == th1_ch:
data['humid_1'] = humidity
elif data['channel'] == th2_ch:
data['humid_2'] = humidity
else:
data['humidity'] = humidity
dbg_parse(2, "humidity_raw=0x%03x value=%s" %
  (humidity_raw, humidity))
=

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Friday, 29 March 2019 17:28:47 UTC-3, kobuki wrote:
>
> But if I'm right, temps should also be wrong. For the NTC Davis is using 
> we already have the formula IIRC. 
>

Kobuki,

You are wrong! :-) The analog temperatures are calculated right, see code 
below:


elif message_type == 8:
# outside temperature
# message examples:
# 80 00 00 33 8D 00 25 11 (digital temp)
# 81 00 00 59 45 00 A3 E6 (analog temp)
# 81 00 DB FF C3 00 AB F8 (no sensor)
temp_raw = (pkt[3] << 4) + (pkt[4] >> 4)  # 12-bits temp value
if temp_raw != 0xFFC:
if pkt[4] & 0x8:
# digital temp sensor
temp_f = temp_raw / 10.0
temp_c = weewx.wxformulas.FtoC(temp_f) # C
dbg_parse(2, "digital temp_raw=0x%03x temp_f=%s temp_c=%s"
  % (temp_raw, temp_f, temp_c))
else:
# analog sensor (thermistor)
temp_raw /= 4  # 10-bits temp value
temp_c = calculate_thermistor_temp(temp_raw)
dbg_parse(2, "thermistor temp_raw=0x%03x temp_c=%s"
  % (temp_raw, temp_c))
if data['channel'] == th1_ch:
data['temp_1'] = temp_c
elif data['channel'] == th2_ch:
data['temp_2'] = temp_c
else:
data['temperature'] = temp_c

 
The formula of the humidity I didn't know. Probably my formula wont work 
then...

Luc

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

I think I get it now. This is an old VP2 with an old, analog T/H sensor! It 
has a capacitive type humidity sensor, and I think they provide the raw 
values or something related closely so it requires a special formula. Since 
it's a capacitive sensor, its output is not linear - unless the firmware 
already compensates for the nonlinearity, which I doubt since they could 
have coded the complete formula into it anyway and the SIM tends to send 
raw sensor data for all sensors anyway. I think we'll need at least a full 
day of samples that includes nights, humid dawns and dry daytime to be able 
to calculate an approximation formula.

But if I'm right, then the temperature sensor is also analog (an NTC), and 
temps should also be wrong. For the NTC Davis is using we already have the 
formula IIRC.

On Friday, March 29, 2019 at 9:17:43 PM UTC+1, ljm@gmail.com wrote:
>
> On Friday, 29 March 2019 15:50:41 UTC-3, Paul Anderson wrote:
>>
>> It is a pretty old VP2 from April of 2006.
>>
>
> Paul,
>
> For the few samples I got from you I have found a formula. 
> I don't understand the logic of the formula, but it works for these 
> samples. :-)  I need more data to be sure.
> Could you please change the parsing section of humidity in your 
> rtldavis.py with the following?
>
> ===
> elif message_type == 0xA:
> # outside humidity
> # message examples:
> # A0 00 00 80 85 00 3E 1F (old model vantage pro)
> # A0 00 00 C9 3D 00 2A 87 (new model vantage pro)
> # A1 00 DB 00 03 00 47 C7 (no sensor)
> humidity_raw = ((pkt[4] >> 4) << 8) + pkt[3]
> if humidity_raw != 0:
> # valid humidity value
> if pk[4] == 0x85:
> # format of old model Vantage Pro2
> humidity = (680 - pkt[3]) / 10.0
> else:
> # format of new model Vantage Pro2
> humidity = humidity_raw / 10.0
> if data['channel'] == th1_ch:
> data['humid_1'] = humidity
> elif data['channel'] == th2_ch:
> data['humid_2'] = humidity
> else:
> data['humidity'] = humidity
> dbg_parse(2, "humidity_raw=0x%03x value=%s" %
>   (humidity_raw, humidity))
> ===
>
> Then let the program run over night and send me by mail the zipped syslog 
> and syslog.1 files tomorrow
> Also I would like a list of the 5-minute averages in the weewx database 
> over the same period.
>
> Thanks in advance.
>
> To kobuki: the hex-code is checked both in protocol.go and rtldavis.py for 
> crc-errors. Both programs didn't complain.
>
> Luc
>  
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Friday, 29 March 2019 15:50:41 UTC-3, Paul Anderson wrote:
>
> It is a pretty old VP2 from April of 2006.
>

Paul,

For the few samples I got from you I have found a formula. 
I don't understand the logic of the formula, but it works for these 
samples. :-)  I need more data to be sure.
Could you please change the parsing section of humidity in your rtldavis.py 
with the following?

===
elif message_type == 0xA:
# outside humidity
# message examples:
# A0 00 00 80 85 00 3E 1F (old model vantage pro)
# A0 00 00 C9 3D 00 2A 87 (new model vantage pro)
# A1 00 DB 00 03 00 47 C7 (no sensor)
humidity_raw = ((pkt[4] >> 4) << 8) + pkt[3]
if humidity_raw != 0:
# valid humidity value
if pk[4] == 0x85:
# format of old model Vantage Pro2
humidity = (680 - pkt[3]) / 10.0
else:
# format of new model Vantage Pro2
humidity = humidity_raw / 10.0
if data['channel'] == th1_ch:
data['humid_1'] = humidity
elif data['channel'] == th2_ch:
data['humid_2'] = humidity
else:
data['humidity'] = humidity
dbg_parse(2, "humidity_raw=0x%03x value=%s" %
  (humidity_raw, humidity))
===

Then let the program run over night and send me by mail the zipped syslog 
and syslog.1 files tomorrow
Also I would like a list of the 5-minute averages in the weewx database 
over the same period.

Thanks in advance.

To kobuki: the hex-code is checked both in protocol.go and rtldavis.py for 
crc-errors. Both programs didn't complain.

Luc
 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Ah, I see you have 2 stations, an ISS on ID 1 and the anemometer 
transmitter on ID 2, same as my setup (I also have solar and UV on the 
latter, though). Forget what I said about the values. Both could be 
theoretically good, but the packets where the hum. is off, still should not 
pass validation. I guess Luc will debug it when he gets to it.

On Friday, March 29, 2019 at 7:50:41 PM UTC+1, Paul Anderson wrote:
>
> No valid humidity data from rtl_davis. Normal vantage console shows good 
> data, as well as Weewx directly connected to it.  It is a pretty old VP2 
> from April of 2006.
> Had run this at one point:
>  Davis Vantage EEPROM settings:
>
> CONSOLE TYPE:   VantagePro2
>
> CONSOLE FIRMWARE:
>   Date: Sep 29 2009
>   Version:  1.90
>
> CONSOLE SETTINGS:
>   Archive interval: 300 (seconds)
>   Altitude: 161 (foot)
>   Wind cup type:large
>   Rain bucket type: 0.01 inches
>   Rain year start:  1
>   Onboard time: 2017-09-06 16:41:30
>
> CONSOLE DISPLAY UNITS:
>   Barometer:mbar
>   Temperature:  degree_F
>   Rain: inch
>   Wind: mile_per_hour
>
> CONSOLE STATION INFO:
>   Latitude (onboard):   +42.5
>   Longitude (onboard):  -71.2
>   Use manual or auto DST?   AUTO
>   DST setting:  N/A
>   Use GMT offset or zone code?  GMT_OFFSET
>   Time zone code:   N/A
>   GMT offset:   -4.0 hours
>
>
> TRANSMITTERS:
>   Channel 1:iss
>   Channel 2:wind
>   Channel 3:(N/A)
>   Channel 4:(N/A)
>   Channel 5:(N/A)
>   Channel 6:(N/A)
>   Channel 7:(N/A)
>   Channel 8:(N/A)
>
> RECEPTION STATS:
>   Total packets received:   24
>   Total packets missed: 0
>   Number of resynchronizations: 0
>   Longest good stretch: 24
>   Number of CRC errors: 0
>
> Thanks
> Paul
> On Friday, March 29, 2019 at 2:37:37 PM UTC-4, kobuki wrote:
>>
>> Do you receive valid humidity values at all? The data in these packets is 
>> completely bogus at the nybbles responsible for the humidity values. It 
>> comes as byte[3][lower nybble as high 4 bits] + byte[4] as a 12-bit number 
>> which is 10*actual humidity value. I'm just guessing that these packets 
>> shouldn't pass CRC validation. They should not be able to pass as valid 
>> packets at all. Your console values are OK, so the T/H sensor is not likely 
>> to be at fault.
>>
>> On Friday, March 29, 2019 at 7:20:05 PM UTC+1, Paul Anderson wrote:
>>>
>>> Luc,
>>> No worries here is the new log with dbug. Actual out temp was app 56 F 
>>> Humidity 55% during the test.
>>>
>>>
>>>  Time   Wind Dir   Wind Spd   Wind Gust   Humidity TempBarometer   
>>> Rain
>>>  Degmph mph  %Deg F   mb
>>>  in
>>> 
>>>
>>> 13:45270  4  10 55 55.9   1015.7   
>>> 0.00
>>> 13:50248  4   8 55 55.9   1015.7   
>>> 0.00
>>> 13:55248  3   9 55 55.7   1015.7   
>>> 0.00
>>> 14:00248  2   8 56 55.6   1015.7   
>>> 0.00
>>> 14:05270  2   6 57 55.4   1015.7   
>>> 0.00
>>>
>>>
>>>
>>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: chan: 13:49:35.180655 
>>> Hop: {ChannelIdx:11 ChannelFreq:907901123 FreqError:-612}
>>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
>>> 'dateTime': 1553881775}
>>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: data: 13:49:35.484835 
>>> A0828500507F 30 31 0 0 0 msg.ID=0
>>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
>>> value=217.8
>>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 
>>> 217.8, 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881776}
>>> Mar 29 13:49:35 pi3-dev weewx[8185]: engine: 2019-03-29 13:49:36 EDT 
>>> (1553881776) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
>>> --
>>> Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: chan: 13:50:25.052790 
>>> Hop: {ChannelIdx:38 ChannelFreq:921448364 FreqError:-687}
>>> Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
>>> 'dateTime': 1553881825}
>>> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: data: 13:50:26.736444 
>>> A0828500507F 50 49 0 0 0 msg.ID=0
>>> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
>>> value=217.8
>>> Mar 29 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Paul Anderson]

No valid humidity data from rtl_davis. Normal vantage console shows good 
data, as well as Weewx directly connected to it.  It is a pretty old VP2 
from April of 2006.
Had run this at one point:
 Davis Vantage EEPROM settings:

CONSOLE TYPE:   VantagePro2

CONSOLE FIRMWARE:
  Date: Sep 29 2009
  Version:  1.90

CONSOLE SETTINGS:
  Archive interval: 300 (seconds)
  Altitude: 161 (foot)
  Wind cup type:large
  Rain bucket type: 0.01 inches
  Rain year start:  1
  Onboard time: 2017-09-06 16:41:30

CONSOLE DISPLAY UNITS:
  Barometer:mbar
  Temperature:  degree_F
  Rain: inch
  Wind: mile_per_hour

CONSOLE STATION INFO:
  Latitude (onboard):   +42.5
  Longitude (onboard):  -71.2
  Use manual or auto DST?   AUTO
  DST setting:  N/A
  Use GMT offset or zone code?  GMT_OFFSET
  Time zone code:   N/A
  GMT offset:   -4.0 hours


TRANSMITTERS:
  Channel 1:iss
  Channel 2:wind
  Channel 3:(N/A)
  Channel 4:(N/A)
  Channel 5:(N/A)
  Channel 6:(N/A)
  Channel 7:(N/A)
  Channel 8:(N/A)

RECEPTION STATS:
  Total packets received:   24
  Total packets missed: 0
  Number of resynchronizations: 0
  Longest good stretch: 24
  Number of CRC errors: 0

Thanks
Paul
On Friday, March 29, 2019 at 2:37:37 PM UTC-4, kobuki wrote:
>
> Do you receive valid humidity values at all? The data in these packets is 
> completely bogus at the nybbles responsible for the humidity values. It 
> comes as byte[3][lower nybble as high 4 bits] + byte[4] as a 12-bit number 
> which is 10*actual humidity value. I'm just guessing that these packets 
> shouldn't pass CRC validation. They should not be able to pass as valid 
> packets at all. Your console values are OK, so the T/H sensor is not likely 
> to be at fault.
>
> On Friday, March 29, 2019 at 7:20:05 PM UTC+1, Paul Anderson wrote:
>>
>> Luc,
>> No worries here is the new log with dbug. Actual out temp was app 56 F 
>> Humidity 55% during the test.
>>
>>
>>  Time   Wind Dir   Wind Spd   Wind Gust   Humidity TempBarometer   
>> Rain
>>  Degmph mph  %Deg F   mb 
>> in
>> 
>>
>> 13:45270  4  10 55 55.9   1015.7   
>> 0.00
>> 13:50248  4   8 55 55.9   1015.7   
>> 0.00
>> 13:55248  3   9 55 55.7   1015.7   
>> 0.00
>> 14:00248  2   8 56 55.6   1015.7   
>> 0.00
>> 14:05270  2   6 57 55.4   1015.7   
>> 0.00
>>
>>
>>
>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: chan: 13:49:35.180655 Hop: 
>> {ChannelIdx:11 ChannelFreq:907901123 FreqError:-612}
>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
>> 'dateTime': 1553881775}
>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: data: 13:49:35.484835 
>> A0828500507F 30 31 0 0 0 msg.ID=0
>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
>> value=217.8
>> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 
>> 217.8, 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881776}
>> Mar 29 13:49:35 pi3-dev weewx[8185]: engine: 2019-03-29 13:49:36 EDT 
>> (1553881776) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
>> --
>> Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: chan: 13:50:25.052790 Hop: 
>> {ChannelIdx:38 ChannelFreq:921448364 FreqError:-687}
>> Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
>> 'dateTime': 1553881825}
>> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: data: 13:50:26.736444 
>> A0828500507F 50 49 0 0 0 msg.ID=0
>> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
>> value=217.8
>> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 
>> 217.8, 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881827}
>> Mar 29 13:50:26 pi3-dev weewx[8185]: engine: 2019-03-29 13:50:27 EDT 
>> (1553881827) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
>> --
>> Mar 29 13:51:17 pi3-dev weewx[8185]: rtldavis: chan: 13:51:17.552978 Hop: 
>> {ChannelIdx:37 ChannelFreq:920947083 FreqError:-1313}
>> Mar 29 13:51:17 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
>> 'dateTime': 1553881878}
>> Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: data: 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Sorry, I'm not Luc, but I've had a look. How many stations do you have? A 
single one on ID 2 or 2 on IDs 1 and 2? All the station 1 data seems 
garbage while all station 2 data looks fine. Did you check the transmitter 
IDs in your weewx config?

On Friday, March 29, 2019 at 7:37:04 PM UTC+1, Paul Anderson wrote:
>
> Luc,
> In case you want to see everything here it is.
>
> Thanks
> Paul
>
> On Friday, March 29, 2019 at 8:15:07 AM UTC-4, ljm@gmail.com wrote:
>>
>> Paul,
>>
>> My mistake, sorry! "debug_parse = 1" only logs a single message.
>>
>> Please set "debug_parse = 3" in weewx.conf in the Rtldavis section and 
>> repeat the test.
>> Then we will know for sure if the problem is with the driver.
>>
>> Thanks in advance.
>>
>> Luc
>>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Do you receive valid humidity values at all? The data in these packets is 
completely bogus at the nybbles responsible for the humidity values. It 
comes as byte[3][lower nybble as high 4 bits] + byte[4] as a 12-bit number 
which is 10*actual humidity value. I'm just guessing that these packets 
shouldn't pass CRC validation. They should not be able to pass as valid 
packets at all. Your console values are OK, so the T/H sensor is not likely 
to be at fault.

On Friday, March 29, 2019 at 7:20:05 PM UTC+1, Paul Anderson wrote:
>
> Luc,
> No worries here is the new log with dbug. Actual out temp was app 56 F 
> Humidity 55% during the test.
>
>
>  Time   Wind Dir   Wind Spd   Wind Gust   Humidity TempBarometer   
> Rain
>  Degmph mph  %Deg F   mb 
> in
> 
>
> 13:45270  4  10 55 55.9   1015.7   
> 0.00
> 13:50248  4   8 55 55.9   1015.7   
> 0.00
> 13:55248  3   9 55 55.7   1015.7   
> 0.00
> 14:00248  2   8 56 55.6   1015.7   
> 0.00
> 14:05270  2   6 57 55.4   1015.7   
> 0.00
>
>
>
> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: chan: 13:49:35.180655 Hop: 
> {ChannelIdx:11 ChannelFreq:907901123 FreqError:-612}
> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
> 'dateTime': 1553881775}
> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: data: 13:49:35.484835 
> A0828500507F 30 31 0 0 0 msg.ID=0
> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
> value=217.8
> Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.8, 
> 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881776}
> Mar 29 13:49:35 pi3-dev weewx[8185]: engine: 2019-03-29 13:49:36 EDT 
> (1553881776) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
> --
> Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: chan: 13:50:25.052790 Hop: 
> {ChannelIdx:38 ChannelFreq:921448364 FreqError:-687}
> Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
> 'dateTime': 1553881825}
> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: data: 13:50:26.736444 
> A0828500507F 50 49 0 0 0 msg.ID=0
> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
> value=217.8
> Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.8, 
> 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881827}
> Mar 29 13:50:26 pi3-dev weewx[8185]: engine: 2019-03-29 13:50:27 EDT 
> (1553881827) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
> --
> Mar 29 13:51:17 pi3-dev weewx[8185]: rtldavis: chan: 13:51:17.552978 Hop: 
> {ChannelIdx:37 ChannelFreq:920947083 FreqError:-1313}
> Mar 29 13:51:17 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
> 'dateTime': 1553881878}
> Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: data: 13:51:17.987123 
> A0818500092F 68 69 0 0 0 msg.ID=0
> Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x881 
> value=217.7
> Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.7, 
> 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881878}
> Mar 29 13:51:18 pi3-dev weewx[8185]: engine: 2019-03-29 13:51:18 EDT 
> (1553881878) LOOP value 'outHumidity' 217.7 outside limits (0.0, 100.0)
> --
> Mar 29 13:52:07 pi3-dev weewx[8185]: rtldavis: chan: 13:52:07.426793 Hop: 
> {ChannelIdx:47 ChannelFreq:925964600 FreqError:-1228}
> Mar 29 13:52:07 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
> 'dateTime': 1553881927}
> Mar 29 13:52:09 pi3-dev weewx[8185]: rtldavis: data: 13:52:09.238038 
> A0818500092F 85 85 0 0 0 msg.ID=0
> Mar 29 13:52:09 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x881 
> value=217.7
> Mar 29 13:52:09 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.7, 
> 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881929}
> Mar 29 13:52:09 pi3-dev weewx[8185]: engine: 2019-03-29 13:52:09 EDT 
> (1553881929) LOOP value 'outHumidity' 217.7 outside limits (0.0, 100.0)
> --
> Mar 29 13:52:59 pi3-dev weewx[8185]: rtldavis: chan: 13:52:59.927960 Hop: 
> {ChannelIdx:7 ChannelFreq:905894592 FreqError:-2234}
> Mar 29 13:52:59 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
> 'dateTime': 1553881980}
> Mar 29 13:53:00 pi3-dev weewx[8185]: rtldavis: data: 13:53:00.487267 
> A08085003E1F 103 103 0 0 0 msg.ID=0
> Mar 29 13:53:00 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x880 
> value=217.6
> Mar 29 13:53:00 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.6, 
> 'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881981}
> Mar 29 13:53:00 pi3-dev weewx[8185]: engine: 2019-03-29 13:53:01 EDT 
> (1553881981) LOOP value 'outHumidity' 217.6 outside limits (0.0, 100.0)
> --
> Mar 29 13:54:42 pi3-dev weewx[8185]: rtldavis: chan: 13:54:42.301452 Hop: 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[Paul Anderson]

Luc,
No worries here is the new log with dbug. Actual out temp was app 56 F 
Humidity 55% during the test.


 Time   Wind Dir   Wind Spd   Wind Gust   Humidity TempBarometer   Rain
 Degmph mph  %Deg F   mb in


13:45270  4  10 55 55.9   1015.7   0.00
13:50248  4   8 55 55.9   1015.7   0.00
13:55248  3   9 55 55.7   1015.7   0.00
14:00248  2   8 56 55.6   1015.7   0.00
14:05270  2   6 57 55.4   1015.7   0.00



Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: chan: 13:49:35.180655 Hop: 
{ChannelIdx:11 ChannelFreq:907901123 FreqError:-612}
Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
'dateTime': 1553881775}
Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: data: 13:49:35.484835 
A0828500507F 30 31 0 0 0 msg.ID=0
Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
value=217.8
Mar 29 13:49:35 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.8, 
'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881776}
Mar 29 13:49:35 pi3-dev weewx[8185]: engine: 2019-03-29 13:49:36 EDT 
(1553881776) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
--
Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: chan: 13:50:25.052790 Hop: 
{ChannelIdx:38 ChannelFreq:921448364 FreqError:-687}
Mar 29 13:50:25 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
'dateTime': 1553881825}
Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: data: 13:50:26.736444 
A0828500507F 50 49 0 0 0 msg.ID=0
Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x882 
value=217.8
Mar 29 13:50:26 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.8, 
'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881827}
Mar 29 13:50:26 pi3-dev weewx[8185]: engine: 2019-03-29 13:50:27 EDT 
(1553881827) LOOP value 'outHumidity' 217.8 outside limits (0.0, 100.0)
--
Mar 29 13:51:17 pi3-dev weewx[8185]: rtldavis: chan: 13:51:17.552978 Hop: 
{ChannelIdx:37 ChannelFreq:920947083 FreqError:-1313}
Mar 29 13:51:17 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
'dateTime': 1553881878}
Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: data: 13:51:17.987123 
A0818500092F 68 69 0 0 0 msg.ID=0
Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x881 
value=217.7
Mar 29 13:51:18 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.7, 
'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881878}
Mar 29 13:51:18 pi3-dev weewx[8185]: engine: 2019-03-29 13:51:18 EDT 
(1553881878) LOOP value 'outHumidity' 217.7 outside limits (0.0, 100.0)
--
Mar 29 13:52:07 pi3-dev weewx[8185]: rtldavis: chan: 13:52:07.426793 Hop: 
{ChannelIdx:47 ChannelFreq:925964600 FreqError:-1228}
Mar 29 13:52:07 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
'dateTime': 1553881927}
Mar 29 13:52:09 pi3-dev weewx[8185]: rtldavis: data: 13:52:09.238038 
A0818500092F 85 85 0 0 0 msg.ID=0
Mar 29 13:52:09 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x881 
value=217.7
Mar 29 13:52:09 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.7, 
'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881929}
Mar 29 13:52:09 pi3-dev weewx[8185]: engine: 2019-03-29 13:52:09 EDT 
(1553881929) LOOP value 'outHumidity' 217.7 outside limits (0.0, 100.0)
--
Mar 29 13:52:59 pi3-dev weewx[8185]: rtldavis: chan: 13:52:59.927960 Hop: 
{ChannelIdx:7 ChannelFreq:905894592 FreqError:-2234}
Mar 29 13:52:59 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
'dateTime': 1553881980}
Mar 29 13:53:00 pi3-dev weewx[8185]: rtldavis: data: 13:53:00.487267 
A08085003E1F 103 103 0 0 0 msg.ID=0
Mar 29 13:53:00 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x880 
value=217.6
Mar 29 13:53:00 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.6, 
'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553881981}
Mar 29 13:53:00 pi3-dev weewx[8185]: engine: 2019-03-29 13:53:01 EDT 
(1553881981) LOOP value 'outHumidity' 217.6 outside limits (0.0, 100.0)
--
Mar 29 13:54:42 pi3-dev weewx[8185]: rtldavis: chan: 13:54:42.301452 Hop: 
{ChannelIdx:5 ChannelFreq:904890625 FreqError:-1336}
Mar 29 13:54:42 pi3-dev weewx[8185]: rtldavis: pkt= {'usUnits': 17, 
'dateTime': 1553882082}
Mar 29 13:54:42 pi3-dev weewx[8185]: rtldavis: data: 13:54:42.988878 
A07F8500F17C 132 136 0 0 0 msg.ID=0
Mar 29 13:54:42 pi3-dev weewx[8185]: rtldavis: humidity_raw=0x87f 
value=217.5
Mar 29 13:54:42 pi3-dev weewx[8185]: rtldavis: pkt= {'outHumidity': 217.5, 
'usUnits': 17, 'txBatteryStatus': 0, 'dateTime': 1553882083}
Mar 29 13:54:43 pi3-dev weewx[8185]: engine: 2019-03-29 13:54:43 EDT 
(1553882083) LOOP value 'outHumidity' 217.5 outside limits (0.0, 100.0)
--
Mar 29 13:56:24 pi3-dev weewx[8185]: rtldavis: chan: 13:56:24.675103 Hop: 
{ChannelIdx:25 

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[kobuki]

Why do you think one should't run WeeWx for that task? It's simple, free, 
open-source and well-supported. And with templating it's much more flexible 
than a fixed-output application. It's also a LOT more work. As Luc already 
noted, it would require re-implementing the Davis binary packet decoder in 
another application. I see no particular benefit doing that when perfectly 
workable solutions already exist.

On Friday, March 29, 2019 at 1:14:29 PM UTC+1, rich T wrote:
>
> Luc
> In my opinion I think there should be two versions of the driver, this 
> version and a standalone version. The current version allows someone with a 
> SDR/Davis to directly interface into Weewx.  The standalone version/w JSON 
> output will allow someone to interface with Node Red and publishing the 
> data via MQTT.
>
> Thanks
> Rich
>
> On Friday, March 29, 2019 at 1:28:34 AM UTC-4, ljm@gmail.com wrote:
>
>> Rich,
>> Please tell me a bit more. json output as standalone function or together 
>> with weewx? What application do you have in mind to use this data?
>> Luc
>
>

[weewx-development] Re: Receiving Davis Vantage data with RTL-SDR dongle and program rtldavis

[ljm . heijst]

On Friday, 29 March 2019 09:14:29 UTC-3, rich T wrote:
>
> The standalone version/w JSON output will allow someone to interface with 
> Node Red and publishing the data via MQTT.
>

Rich,

I like the idea, but someone else has to code it. :-)

The weewx-driver does currently all the parsing.

I'm not going to port all this to the go-program.

Luc