and also:
http://wiki.wunderground.com/index.php/PWS_-_Upload_Protocol#RapidFire_Updates
On Tuesday, 30 January 2018 14:48:52 UTC+2, Andrew Milner wrote:
> http://wiki.wunderground.com/index.php/Troubleshooting_-_Rapid_fire
>
>
>
> On Tuesday, 30 January 2018 14:43:03 UTC+2, Yngve Andersson
http://wiki.wunderground.com/index.php/Troubleshooting_-_Rapid_fire
On Tuesday, 30 January 2018 14:43:03 UTC+2, Yngve Andersson wrote:
> 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:
>>
>>
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
Good to hear that both systems are now doing the same thing, and working as
you expect - in that respect it is progress!! If you try with the cumulus
realtime extension again - just change one thing at a time to avoid
confusion!! If you change many things at once it becomes very very
*Hello Andrew and others!*
*I have now found the problem of strange views of, among other things, air
pressure. After your point of view of the importance of the inequality of
non functioning and functioning systems with the weewx.conf and skin.conf
files, I have found aberration and a
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
combination of both factors.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe
If you are trying to compare why weewx works ok on one system and not the
other then I suggest you make sure that weewx.conf and skin.conf files are
the same. If there are differences then I have to ask you why they are
different. You cannot compare two systems if the conf files are
*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 station WMR300 is standard, *no extra*
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 station WMR300 is standard, *no extra* sensors!
> I joined WMR300 yesterday 28 Jan 3:15 pm to my desktop computer Mint 18.3
> and seems to have
Hi Cameron!
The station WMR300 is standard, *no extra* sensors!
I joined WMR300 yesterday 28 Jan 3:15 pm to my desktop computer Mint 18.3
and seems to have worked OK! Joined RaspberryPi today 29 Jan 4:30 pm and
now with no air pressure.
So it is obvious that my RaspberyPi does not fully work
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
They are quite odd readings.. Do you really have cloudbase and solar
radiation meters?
If not then maybe the mappings have gone awry?
Matthew will have a much better idea than me.
Cameron.
On Monday, 29 January 2018 19:41:53 UTC+10, Yngve Andersson wrote:
>
> Hey!
> I have logged the
Hello Yvgne,
my system logs to a CentOS 6 server that is always on.
Are you able to check the database that all three pressures are being
recorded?
Mine has pressure, barometer and altimeter. Maybe the system uses one to
display to you, but another to report to Weatherunderground.
With
Hi yngve, can you make rapidfire true for me? I wanna see how it will send data
to wunderground. Thanks
--
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
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,
If you look at my data from 16-Jan-2018, when the house lost power from
approx 7:00 until 10:00, you will see the same effect - history results
from the battery-backed console are logged on Wunderground at one-minute
intervals.
On Sunday, 28 January 2018 16:21:36 UTC+10, Cameron D wrote:
>
>
Hello Yngve,
I don't think the time interval should make a problem - I have been running
3.7.1 for ages at 1 minute log interval.
The Wunderground station is IBRISBAN102 .
Rapidfire is off.
log_success = False
DIsplayed data is updated once a minute (as seen on the Wunderground web
page), but
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
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 in weewx.conf is 300 seconds. the
archive interval of the wmr300 can be anything, but you might want to set
it to 5
On Saturday, January 20, 2018 at 8:52:44 AM UTC-5, gjr80 wrote:
>
> 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
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
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
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
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
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
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
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
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
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
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
30 matches
Mail list logo
