Andrew and Gary
Longer times does not seem to solve the problem of the presentation of
pressure!
I have now tried a totally crazy idea without any knowledge, I hope you
have an earning with my ignorance ... I set the time weewx.conf back to 300
seconds and the WMR300 logging to 1 minute ... then I manually do the
command restart (stop o start) by weewx ?? I have no idea what restart does
and when it breaks and restarts program execution, sometimes there is
something wrong message, but by the way, the program will be back. I
suppose this command entails some mess in program execution depending on
where in the program execution is located?
However, tried to give the command at a certain sequence in syslog and
after a certain time. Result results in new values being displayed
positively and also pressure shows values.
However, this is not a solution to the problem, so ... I'll get even more
say that pressure can be read manually on the WMR300 display!
Den lördag 20 januari 2018 kl. 15:52:44 UTC+2 skrev gjr80:
>
> Matthew,
>
> Would this situation not be able to be resolved if the WMR300 driver was
> subjected to the (for want of a better term) 'removal of unnecessary
> output' treatment that the vantage driver was given under 3.7.0? I see
> there are archive records and loop packets where all 3 'pressures' are
> None. If we follow the vantage model this should not happen, if or more of
> these is known any of the missing 'pressures' should be calculated and if
> all three are unknown (unreported) then all 3 should be omitted from the
> loop packet/archive record. The user could then use the $latest tag in
> reports to get the lastest barometer, altitude or pressure and for WU the
> cached values added in (I think) 3.6.2 should cater for pressure only being
> reported every 15 minutes.
>
> To me going to a 15 or 30 minute or longer archive period is not much of a
> solution.
>
> Gary
>
> On Saturday, 20 January 2018 21:23:27 UTC+10, Yngve Andersson wrote:
>>
>> Andrew
>>
>> I have now changed the time in weewx.conf to 1800 sec=30 minutes and
>> WMR300 to 15 minutes (WMR300 can only select storage frequency to 1 minute,
>> 5 minutes, 15 minutes and 60 minutes). We wait for results in an hour and
>> then see.
>>
>>
>> Thank you so much / Yngve
>>
>>
>>
>> Den lördag 20 januari 2018 kl. 12:37:27 UTC+2 skrev Andrew Milner:
>>>
>>> The .conf you posted had the interval set to 900 = 15 minutes, not 5,
>>> but the station only outputs the pressure every 15 minutes - so perhaps
>>> your archive interval needs to be 20-30 minutes in order to contain at
>>> least one pressure reading
>>>
>>> Does the weather station have its interval set to the same value??
>>>
>>> I see that the station only supplies barometer in loop and rec packets,
>>> and pressure in loop data and for rec packets weewx has to calculate
>>> altimeter and pressure
>>>
>>> If you have a long archive interval (eg 30 minutes rather than the 5 i
>>> suggested originally), and the station set to the same value, does it help??
>>>
>>> On Saturday, 20 January 2018 11:37:52 UTC+2, Yngve Andersson wrote:
>>>
>>>> Andrew
>>>>
>>>> Ok! has now changed the WMR300 logging interval to 5 minutes. I have
>>>> waited a period of 900 seconds for the first REC, giving unchanged results.
>>>> Attaches weewx.conf as it is running now!
>>>>
>>>> Best regards / Yngve
>>>>
>>>> Den lördag 20 januari 2018 kl. 10:52:28 UTC+2 skrev Andrew Milner:
>>>>>
>>>>> Can you post your weewx.conf - with sensitive passwords removed of
>>>>> course.
>>>>>
>>>>> Weewx can be set to either generate archive records from hardware or
>>>>> generate them by software. If the hardware rec always has the right data
>>>>> then ensure that in weewx.conf - stdArchive section - you have got record
>>>>> generation set to hardware
>>>>>
>>>>> 60 second archive interval is very small - usually one uses 5 minutes
>>>>> (300 secs) - and may lead to other issues in generating reports etc which
>>>>> is done at the archive interval - so at 60 seconds the reports may start
>>>>> to
>>>>> backlog a little
>>>>>
>>>>>
>>>>>
>>>>> On Saturday, 20 January 2018 10:41:05 UTC+2, Yngve Andersson wrote:
>>>>>
>>>>>>
>>>>>> Notes on ...
>>>>>>
>>>>>> After the Weewx program has stopped (for some reason?) And been
>>>>>> turned off for a few hours, I now restart with the command "*sudo
>>>>>> weewxd weewx.conf*".
>>>>>>
>>>>>> There is now a list of "REC" with historically stored values from
>>>>>> the time weewx stopped. Measurement values displayed here with a range
>>>>>> of
>>>>>> 60 seconds and up to the current time look correct (see attached print).
>>>>>> (WMR300 is initially set to log 1 time/60seconds... if now this may
>>>>>> be important?). These historical "REC" are now scrolling to return to
>>>>>> normal running ("LOOP" and "REC, every 900 seconds") and now again with
>>>>>> "altimeter: None and barometer: None" display.
>>>>>>
>>>>>>
>>>>>> It's tricky to describe the procedure, but I hope it's understandable.
>>>>>>
>>>>>>
>>>>>> A thought and wonder from a novice ... if the 60 seconds measured
>>>>>> values in the WMR300 are correct why not read and present the
>>>>>> nearest historically stored value?
>>>>>>
>>>>>> Sincerely Yngve
>>>>>>
>>>>>> Den lördag 20 januari 2018 kl. 02:12:02 UTC+2 skrev Yngve Andersson:
>>>>>>>
>>>>>>> The time between two "REC" 01:45:00 - 02:00:00 is exactly 900
>>>>>>> seconds. The reading was done manually from the terminal. Also noted
>>>>>>> that
>>>>>>> reading values showed "altimeter: None, appTemp: 19.6444928978,
>>>>>>> barometer:
>>>>>>> None"
>>>>>>>
>>>>>>> Den fredag 19 januari 2018 kl. 22:01:42 UTC+2 skrev Yngve Andersson:
>>>>>>>>
>>>>>>>> Thank you, *mwall *for your quick response and dedication!
>>>>>>>>
>>>>>>>>
>>>>>>>> The time is set to 900 seconds, also tested 1200 seconds with the
>>>>>>>> same result.
>>>>>>>>
>>>>>>>> I'm not familiar with the "sqlite3" program, so it needed an
>>>>>>>> installation. Then I come so far.
>>>>>>>>
>>>>>>>>
>>>>>>>> p...@raspberrypi:~$ sqlite3 /var/lib/weewx.sdb
>>>>>>>>
>>>>>>>> SQLite version 3.16.2 2017-01-06 16:32:41
>>>>>>>>
>>>>>>>> Enter ”.help” for usage hints.
>>>>>>>>
>>>>>>>> Sqlite> select dateTime,pressure,barometer,altimeter from archive
>>>>>>>>
>>>>>>>> - - >
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Den fredag 19 januari 2018 kl. 20:42:39 UTC+2 skrev mwall:
>>>>>>>>>
>>>>>>>>> yngve,
>>>>>>>>>
>>>>>>>>> thank you for a detailed problem description!
>>>>>>>>>
>>>>>>>>> wu can be very unreliable about displaying data, so we should
>>>>>>>>> first ensure that weewx is getting correct data from the hardware.
>>>>>>>>>
>>>>>>>>> as you know, the wmr300 emits a pressure reading only every 900
>>>>>>>>> seconds. so if you have an archive interval of 300 seconds, only
>>>>>>>>> every 3rd
>>>>>>>>> archive record will have a value for pressure.
>>>>>>>>>
>>>>>>>>> however, your archive interval of 900 seconds should address this.
>>>>>>>>>
>>>>>>>>> how often do you have records (REC not LOOP) with no
>>>>>>>>> pressure/altimeter/barometer?
>>>>>>>>>
>>>>>>>>> you can find out easily by doing a query on the weewx database:
>>>>>>>>>
>>>>>>>>> sqlite3 /var/lib/weewx.sdb
>>>>>>>>> select dateTime,pressure,barometer,altimeter from archive
>>>>>>>>>
>>>>>>>>> m
>>>>>>>>>
>>>>>>>>>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
