Cameron!
What is the meaning of rapidfire? I have put it active now!
Yngve
Den tisdag 30 januari 2018 kl. 02:05:07 UTC+2 skrev Cameron D:
>
> Yngve,
> you have rapidfire enabled on the pi - I would first turn that off.
>
> Also disable cumulusrealtime and see if that is related. It might be the
all other respects they should be identical.
>
> What are the differences??
>
>
>
> On Monday, 29 January 2018 19:34:57 UTC+2, Yngve Andersson wrote:
>
>> Hello Andrew!
>> There is a certain difference of weewx.conf between Raspberry and
>> Mint18.3! I do not kn
*Andrew!*
*weewx.conf*
Den måndag 29 januari 2018 kl. 17:57:26 UTC+2 skrev Andrew Milner:
>
> have you checked that weewx.conf is IDENTICAL on both systems?
>
>
>
> On Monday, 29 January 2018 17:43:58 UTC+2, Yngve Andersson wrote:
>
>> Hi Cameron!
>> The stat
me.
>
> Cameron.
>
>
> On Monday, 29 January 2018 19:41:53 UTC+10, Yngve Andersson wrote:
>>
>> Hey!
>> I have logged the following information from Raspberry and WMR300 with
>> command:
>> *sudo PYTHONPATH=/usr/share/weewx python
>> /usr/share/weewx/weewx/driv
Hi sinantc34!
I have now put true on rapidfire in weewx.conf. I have no idea what
rapidfire does?
Thank you for helping Yngve
Den måndag 29 januari 2018 kl. 00:45:40 UTC+2 skrev sina...@gmail.com:
>
> Hi yngve, can you make rapidfire true for me? I wanna see how it will send
> data to
Hello Cameron!
Thank you for your dedication. Missing info at your weather station, for
example, where you run the program from.
It's very frustrating that the air pressure is not presented! As I note,
however, the print information is retrieved from the sensor and stored
during the weewx run,
Ok ... I'll be back tomorrow
Thanks / Yngve
Den lördag 20 januari 2018 kl. 20:03:41 UTC+2 skrev mwall:
>
> yngve,
>
> what is the 'altitude' entered in your wmr300 console?
>
> please try the following:
>
> 1) stop weewx
>
> sudo /etc/init.d/weewx stop
>
> 2) ensure that the archive interval
s 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:
>>
>
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 log
log 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 "*sud
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 th
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
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.
pi@raspberrypi:~$ sqlite3 /var/lib/weewx.sdb
SQLite
Hey!
I need help getting forward with displaying the information from "barometer
= pressure" that is missing and showing "none" in log file and at
presentation. The values show only at the first registration after
starting the program.
When I searched for information online, I realized that
14 matches
Mail list logo
