the wmr300 emits partial packets, so not every loop record contains the data for all the sensors. this could be the reason why you are seeing NONE for some readings.
Have you done what Gary suggested, and run weewx directly from the command line and checked the contents of the LOOP records?? The archive records should, if the archive interval is large enough, contain the average readings for all sensors. On Friday, 16 November 2018 22:06:53 UTC+2, Vlad Mastenitsa wrote: > > my datatransfer sheme is; > > localserver > (weewxd)---------------------------------------------ISP------------------------------------------------VPS > > (weather.kozlovo.tk) > > weewx: loop - > | > crtservice <- > crtservice.ctr ------------------------ > | > gen. /localpath/realtime.txt <-- > weewx: RSYNC > ----------->----------------------------------------------------------------------->----------------------remotepath/realtime.txt > > local realtime.txt generate periodicaly as LOOP run > > remote realtime.txt update priodicaly as StdReports run > > пятница, 16 ноября 2018 г., 22:34:52 UTC+3 пользователь Vlad Mastenitsa > написал: >> >> Weather station is Oregon WMR300, log by weewx run directly access at >> http://weather.kozlovo.tk/jsondata/weatherlog.txt >> >> >> >> >> пятница, 16 ноября 2018 г., 16:35:09 UTC+3 пользователь Andrew Milner >> написал: >>> >>> Saying type of weather station and giving log extract would help. Also >>> did you try Gary's suggestion and run weewx directly rather than as daemon >>> and compare the loop records with the data actually output?? >>> >>> >>> >>> On Friday, 16 November 2018 15:17:59 UTC+2, Vlad Mastenitsa wrote: >>>> >>>> And you can see that realtime.txt content different data than >>>> weaterflow.txt >>>> >>>> пятница, 16 ноября 2018 г., 16:15:02 UTC+3 пользователь Vlad Mastenitsa >>>> написал: >>>>> >>>>> yes. Sometime weexwx upload to realtime.txt correct data, and sometime >>>>> it content NULL's. for control it i have parallel upload to >>>>> http://weather.kozlovo.tk/jsondata/weatherflow.txt. >>>>> >>>>> Any ideas to help? >>>>> >>>>> p.s. About weewx.wxservices.StdWXCalculate i got it now. Thanks. >>>>> >>>>> пятница, 16 ноября 2018 г., 2:30:46 UTC+3 пользователь gjr80 написал: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I am looking at your realtime.txt now (2:20am 16 November your time) >>>>>> and outTemp is showing as 0.7C and windSpeed is indeed Null which >>>>>> indicates that weeWX is not seeing a windSpeed value. Have you tried >>>>>> running >>>>>> weeWX directly >>>>>> <http://weewx.com/docs/usersguide.htm#Running_directly> and >>>>>> comparing the loop data windSpeed values against what you are seeing >>>>>> in realtime.txt? If they are both showing None/Null then I would >>>>>> look at your station console if you have one, does it show a wind speed >>>>>> value? This might point you to either the driver for your station or >>>>>> your >>>>>> station itself. >>>>>> >>>>>> I would do the same thing for outTemp, though like I said it is >>>>>> showing up fine for me just now. Perhaps you have some intermittent >>>>>> communications between your sensors and station? >>>>>> >>>>>> These issues will have nothing to do with >>>>>> weewx.wxservices.StdWXCalculate as outTemp and windSpeed are >>>>>> directly measured obs and not calculated by weeWX. >>>>>> >>>>>> Gary >>>>>> >>>>>> >>>>> -- 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]. For more options, visit https://groups.google.com/d/optout.
