Thank you so much Andrew. I was left with the impression that even without 
any wind the program will still print out the value of the current position 
of the weather vane. After re-soldering the anemometers cable back and 
re-attaching it back to the weather vane I can confirm that was the root of 
my problem. Thank you as well for quoting the setting I can change to force 
it to print out a value. 
On Monday, 8 July 2019 17:46:57 UTC+3, Andrew Milner wrote:
>
> the option is in wxcalculate section of weewx.conf:
>
> [StdWXCalculate]
>
> The calculation service calculates derived quantities such as dewpoint, 
> windchill, and heatindex.
>
> Some hardware provides derived quantities, others provide only raw 
> observations. The calculation service provides derived quantities for 
> hardware that does not provide them, and known algorithms for hardware that 
> provides unreliable or antiquated calculations.
>
> The section [StdWXCalculate] consists of a group of Observation defaults, 
> followed by a subsection [[Calculations]] that specifies the calculation 
> strategy to be used for each derived quantity.
>
> ignore_zero_wind
>
> Indicates whether the wind direction should be undefined when the wind 
> speed is zero. The default value is True: the wind direction will be 
> undefined when wind speed is zero.
>
> To report the wind vane direction even when there is no wind speed, change 
> this to False:
>
> [StdWXCalculate]
>     ...
>     ignore_zero_wind = False
>
>
> On Monday, 8 July 2019 17:41:28 UTC+3, Andrew Milner wrote:
>>
>> Right - looking at the first files you attached the wind speed was 0.  If 
>> windspeed is zero wind direction will also be set to None (unless you set 
>> the option and I forget what it is in weewx.conf.
>>
>> The live readout also has a windspeed of zero.  You cannot have a 
>> meaningful direction if you do not have a windspeed so the None is a 
>> correct value in this instance.
>>
>>
>>
>>
>> On Monday, 8 July 2019 17:19:19 UTC+3, Victor wrote:
>>>
>>> My bad forgot to mention that in the last post. The LOOP packets return 
>>> that the value of the  wind direction is 'None' (I've attached a file with 
>>> a sample of the returned packet). Looking through the database entries 
>>> everywhere where the windDir value is mentuned its value is 'NULL' ( Also 
>>> attached )
>>>
>>> On Monday, 8 July 2019 16:10:58 UTC+3, Andrew Milner wrote:
>>>>
>>>> do the LOOP packets contain the wind direction when you are running 
>>>> weewx manually (not as a daemon)??
>>>>
>>>> when you look at the database (use sqlite3) what do you get for wind 
>>>> direction?
>>>> select dateTime, windDir from archive where 1; 
>>>> should give you some indication
>>>>
>>>>
>>>> On Monday, 8 July 2019 14:50:46 UTC+3, Victor wrote:
>>>>>
>>>>> Thank you for the assistance Andrew, after calibration the pressure 
>>>>> sensor it works like a charm ( I had skimmed over that table in the wiki 
>>>>> and missed the proper settings for the sensors) , but still I wasn't able 
>>>>> to figure out where the problem with the missing wind direction data 
>>>>> comes 
>>>>> from. 
>>>>>
>>>>> On Monday, 8 July 2019 11:15:54 UTC+3, Andrew Milner wrote:
>>>>>>
>>>>>> To see what weewx is receiving from the station stop weewx and run it 
>>>>>> directly and not as a daemon.  The LOOP and REC packets should then be 
>>>>>> output onto the rpi console as they are received.  Set your station to a 
>>>>>> 5 
>>>>>> minute archive interval (300 seconds) using wee_device and set the 
>>>>>> archive 
>>>>>> interval in weewx.conf to also be 300 seconds.  You should then get 
>>>>>> approximately 5 LOOP records per REC archive record.  You will need to 
>>>>>> make 
>>>>>> sure that barometer and altimeter are specified as being 'software 
>>>>>> generated' because the 1080 only outputs pressure.  See the wiki for the 
>>>>>> difference between the 3.
>>>>>>
>>>>>> This should help you to see what is going on.  Sort out the inputs 
>>>>>> and the database before going on to the outputs and webpages!!  If you 
>>>>>> have 
>>>>>> not changed the archive interval to 300 seconds the default on the 1080 
>>>>>> is 
>>>>>> usually set for 30 minutes - so nothing would happen for 30 minutes in 
>>>>>> weewx.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Monday, 8 July 2019 10:41:27 UTC+3, Victor wrote:
>>>>>>>
>>>>>>>    Hello everyone, i recently found out about this project and 
>>>>>>> wanted to test it out to see how it would work for me, currently I'm 
>>>>>>> running pywws <https://github.com/jim-easterbrook/pywws> running on 
>>>>>>> a Tp-link router with OpenWrt. But to be honest I really wanted to 
>>>>>>> update 
>>>>>>> the way I get the data from the router, from printing out a .CSV file 
>>>>>>> to a 
>>>>>>> more readable/user friendly web page. 
>>>>>>>    The device I'm using to run weewx is a Raspberry Pi 3 B+ and the 
>>>>>>> weather station is a Tycon TP1080WC, the problems that I'm having is 
>>>>>>> reading out the stations values, using live output I can see the 
>>>>>>> program 
>>>>>>> can read out values properly. It can get the wind direction properly 
>>>>>>> and 
>>>>>>> the reading from the pressure sensor but it doesn't add their value 
>>>>>>> either 
>>>>>>> to the web page data , realtime.txt file or the CSV( comma separated 
>>>>>>> value) 
>>>>>>> file (for the pressure sensor it adds the maximum read out as the 
>>>>>>> current 
>>>>>>> value). Trying to debug the problem myself i went through and install 
>>>>>>> weewx 
>>>>>>> using both the debian install guide and the setup.py method bout to the 
>>>>>>> same effect. Using the minimal  knowledge I have in python I tried to 
>>>>>>> edit 
>>>>>>> both the crt, csv weewx extentions to try and print out the values the 
>>>>>>> programs are reading to try and get a basic understanding of the 
>>>>>>> problem 
>>>>>>> i'm getting, but sadly to no success. I've attached all the files I 
>>>>>>> think 
>>>>>>> will be needed to get a basic understanding in the configuration and 
>>>>>>> problem.
>>>>>>>
>>>>>>> P.S. Don't worry about the time and date not being the same on all 
>>>>>>> of the readouts , that my fault not the programs.
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5275bb27-1b82-4ca5-ab5d-33ab0aeb77fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to