Good testimony of just how great a program WeeWx is by catching the gap and
doing the calcs for MADIS and MW. I am really impressed with this
application. Given the context of this application's complexity, this
upgrade was spectacularly smooth.
I was wondering why CWOP did rain as they do an
You could put the following in the [StdCalibrate] section of weewx.conf:
[StdCalibrate]
[[Corrections]]
dayRain = daily_rain
This will set type dayRain to what is being emitted by your hardware. It
will then be passed on to CWOP, instead of looked up in the database.
Unfortunately, C
You are correct - From weewxd after dumping some water into the bucket,
the display reports .14 and in the output of weewxd 'daily_rain: 0.14'
and 'rain_total 5.84' which was at 5.7 until I added the water for today's
test. I have attached the output. So, is there a way for the hardware
Will do. I will work with it tomorrow. Can't wait to dig in!
Thanks Tom,
Burt
On Friday, May 1, 2020 at 11:23:59 AM UTC-4, Tom Keffer wrote:
>
> I think the problem is differences in what "today's rain" means.
>
> The ultimeter driver emits observation types rain_total and daily_rain.
> Thes
I think the problem is differences in what "today's rain" means.
The ultimeter driver emits observation types rain_total and daily_rain.
These are direct from the hardware, so they should match what you're seeing
on the console. You can check by running weewxd directly from the command
line. It wi
Hi, Burt
Unless you're sending sensitive password information, I'd prefer to keep
the exchange here. That way, others can learn, and it becomes a
thread-of-record should someone have a similar problem in the future.
-tk
On Thu, Apr 30, 2020 at 12:12 PM Burt Wizeman wrote:
> Hey Tom,
> Earlier
Hey Tom,
Earlier my numbers to you were wrong. I caught it between updates from
when I first noticed it. The numbers were .53 at CWOP and PWS, .83 on the
display. Sorry, I was in a rush to get to work. If I could have an email
to contact you at, I am reviewing the app for our West Central Fl
Will do,
Thanks,
Burt
On Thursday, April 30, 2020 at 10:09:49 AM UTC-4, Tom Keffer wrote:
>
> 0x53 is actually 83 decimal.
>
> Looking through the Ultimeter code, it seems to be converted from
> hexadecimal to decimal correctly.
>
> Try running with debug=2. The driver will include the raw data
0x53 is actually 83 decimal.
Looking through the Ultimeter code, it seems to be converted from
hexadecimal to decimal correctly.
Try running with debug=2. The driver will include the raw data in the
system log.
-tk
On Thu, Apr 30, 2020 at 6:24 AM Burt Wizeman wrote:
> Still looking into the r
Still looking into the rain. To refresh the discussion, as of the moment
of this writing, the Ultimeter is displaying .82 inches since midnight. It
is at midnight that the daily data is reset to 0. Yet, WeeWx in Linux and
CWOP show .53. 53 HEX is 82 Decimal! What is happening is that the nu
10 matches
Mail list logo
