[weewx-user] Re: Releasing V3.7.0

[Darryn Capes-Davis]

Great work to you, Matt and Gary & other contributors. Trying it out now.

-- 
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.

[weewx-user] Re: Releasing V3.7.0

[ponolan]

Thank you! You guys rock. 

-- 
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.

[weewx-user] Releasing V3.7.0

[Tom Keffer]

Hot off the FTP upload! Version 3.7 is ready. Lots of new features and lots 
of little bug fixes!

Get it in the usual place .

Weewx has grown explosively over the last few years. We now average well 
over 3,000 downloads a month and dominate our niche: Unix weather software. 
With its open source license, support for a wide variety of weather 
hardware, and its ability to run on inexpensive platforms such as the 
Raspberry Pi, weewx is the most common choice for hobbyists world wide.

Many thanks to our growing and enthusiastic user base! Hope you enjoy this 
new release.

-Tom & Matthew & Gary


Change log

The tag $current now uses the record included in the event 
NEW_ARCHIVE_RECORD,
rather than retrieve the last record from the database. This means you can
use the tag $current for observation types that are in the record, but not
necessarily in the database. Fixes issue #13.

Most aggregation periods now allow you to go farther in the past. For
example, the tag $week($weeks_ago=1) would give you last week. You
can also now specify the start and end of an aggregation period, such
as $week.start and $week.end.

Can now do SummaryByDay (as well as SummaryByMonth and SummaryByYear).
NB: This can generate *lots* of files --- one for every day in your 
database!
Leaving this undocumented for now. Fixes issue #185.

When doing hardware record generation, the engine now augments the record 
with
any additional observation types it can extract out of the accumulators.
Fixes issue #15.

It's now possible to iterate over every record within a timespan.
Fixes issue #182.

Use schema_name = hardware_name pattern in sensor map for drivers that 
support
extensible sensor suites, including the drivers for cc3000, te923, wmr300,
wmr100, wmr200, wmr9x8

Simplified sensor mapping implementation for wmr100 and wmr200 drivers.  For
recent weewx releases, these are the default mappings for wmr200:
  3.6.0: in:0, out:1, e2:2, e3:3, ..., e8:8   hard-coded
  3.6.1: in:0, out:1, e1:2, e2:3, ..., e7:8   hard-coded
  3.7.0: in:0, out:1, e1:2, e2:3, ..., e7:8   sensor_map
and these are default mappings for wmr100:
  3.6.2: in:0, out:1, e1:2, e2:3, ..., e7:8   hard-coded
  3.7.0: in:0, out:1, e1:2, e2:3, ..., e7:8   sensor_map

Enabled battery status for every remote T/H and T sensor in wmr100 driver.

Enabled heatindex for each remote T/H sensor in wmr200 driver.

Fixed inverted battery status indicator in wmr200 driver.

Fixed 'Calculatios' typo in wmr100, wmr200, wmr9x8, and wmr300 drivers.

Fixed usb initialization issues in the wmr300 driver.

Added warning in wmr300 driver when rain counter reaches maximum value.

Decode heatindex and windchill from wmr300 sensor outputs.

Report the firmware version when initializing the cc3000 driver.

Fixed bug in vantage driver that would prevent console wake up during
retries when fetching EEPROM vales. Thanks to user Dan Begallie!

The vantage driver no longer emits values for non-existent sensors. 
As a result, LOOP and archive packets are now much smaller. If this works
out, other drivers will follow suit. Partial fix of issue #175.

The vantage driver now emits the barometer trend in LOOP packets as 
field 'trendIcon'.

The engine now logs locale. Additional information if a TERM signal is 
received.

Removed the site-specific "Pond" extensions from the Standard skin.

The Standard skin now includes plots of outside humidity. Fixes 
issue #181.

Fixed reference to index.html.tmpl in the xstats example.

Changed algorithm for calculating ET to something more appropriate for
hourly values (former algorithm assumed daily values). Fixes issue #160.

Fixed bug in Celsius to Fahrenheit conversion that affected pressure
conversions in uwxutils.py, none of which were actually used.

Fixed bug that was introduced in v3.6.0, which prevented wee_reports from
working for anything other than the current time.

Documented the experimental anti-alias feature, which has been in weewx
since v3.1.0. Fixes issue #6.

Fixed problem where multiple subsections under [SummaryBy...] stanzas could
cause multiple copies of their target date to be included in the Cheetah
variable $SummaryByYear and $SummaryByMonth. Fixes issue #187.

Moved examples out of bin directory.  Eliminated experimental directory.
Reinforce the use of user directory, eliminate use of examples directory.
Renamed xsearch.py to stats.py.

OS uptime now works for freeBSD. Thanks to user Bill Richter!
PR #188.

Broke out developer's notes into a separate document.

Added @media CSS for docs to improve printed/PDF formatting.  Thanks to user
Tiouck!

Added a 0.01 second delay after each read_byte in ws23xx driver to reduce
chance of data spikes caused by RS232 line contention.  Thanks 
lionel.sylvie!

The observation windGustDir has been removed from wmr100, wmr200, te923, and
fousb drivers.  These drivers were simply assigning windGustDir to windDir,
since none of the hardware reports an actual windGustDir.

Re: [weewx-user] Re: Last WMR-300 driver hangs my raspberry

[Ruben Navarro Huedo]

It doesn't tell anything
After boot all is fine

I don't have to power cycle the weather station

El 11 mar. 2017 10:35 PM, "mwall"  escribió:

> On Saturday, March 11, 2017 at 4:08:35 PM UTC-5, Ruben Navarro Huedo wrote:
>>
>> No it doesn't recover
>> It locks all the system hangs the Linux
>> I must the turn power off and on again
>>
>
> after you power cycle the computer, what happens?
>
> did you also power cycle the weather station?
>
> it is extremely unlikely that weewx or the weather station is causing your
> computer to hang.  it is much more likely that something else (defective sd
> card?  flaky power?) is causing the hang and the random bytes on the usb.
>
> what does the log say after a restart?
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/Xh7z8Xo038s/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.

Re: [weewx-user] driver fousb.py

[Dario Verdi]

:) im sorryThanks a lot !! Now weewx is started !!

Il giorno sabato 11 marzo 2017 17:26:13 UTC+1, Tom Keffer ha scritto:
>
> Simple typo. You want
>
> weewx.drivers.fousb
>
> not
>
> weexwx.drivers.fousb
>
> Incidentally, it is much easier to change drivers by using the tool 
> wee_config with the --reconfigure option. It will prevent these kinds of 
> errors.
>
>
>
> On Sat, Mar 11, 2017 at 8:19 AM, Dario Verdi  > wrote:
>
>> Hi, im installed with succes the weewx on my raspberry. Ihave a WH1080 
>> meteostation. I setting the file weewx.conf for this station but when i 
>> start ther service weewx in the syslog appear this information:
>>
>> ar 11 17:03:25 meteostation weewx[1375]: engine: Initializing weewx 
>> version 3.6.2
>> Mar 11 17:03:25 meteostation weewx[1375]: engine: Using Python 2.7.9 
>> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
>> Mar 11 17:03:25 meteostation weewx[1375]: engine: Platform 
>> Linux-4.4.50-v7+-armv7l-with-debian-8.0
>> Mar 11 17:03:25 meteostation weewx[1375]: engine: pid file is 
>> /var/run/weewx.pid
>> Mar 11 17:03:25 meteostation weewx[1380]: engine: Using configuration 
>> file /home/weewx/weewx.conf
>> Mar 11 17:03:25 meteostation weewx[1380]: engine: Loading station type 
>> FineOffsetUSB (weexwx.drivers.fousb)
>> Mar 11 17:03:25 meteostation weewx[1380]: engine: Caught unrecoverable 
>> exception in engine:
>> Mar 11 17:03:25 meteostation weewx[1380]:   No module named 
>> weexwx.drivers.fousb
>> Mar 11 17:03:25 meteostation weewx[1380]:   Traceback (most 
>> recent call last):
>> Mar 11 17:03:25 meteostation weewx[1380]: File 
>> "/home/weewx/bin/weewx/engine.py", line 841, in main
>> Mar 11 17:03:25 meteostation weewx[1380]:   engine = 
>> engine_class(config_dict)
>> Mar 11 17:03:25 meteostation weewx[1380]: File 
>> "/home/weewx/bin/weewx/engine.py", line 70, in __init__
>> Mar 11 17:03:25 meteostation weewx[1380]:  
>>  self.setupStation(config_dict)
>> Mar 11 17:03:25 meteostation weewx[1380]: File 
>> "/home/weewx/bin/weewx/engine.py", line 94, in setupStation
>> Mar 11 17:03:25 meteostation weewx[1380]:   __import__(driver)
>> Mar 11 17:03:25 meteostation weewx[1380]:   ImportError: No 
>> module named weexwx.drivers.fousb
>> Mar 11 17:03:25 meteostation weewx[1380]:   Exiting.
>> Mar 11 17:03:25 meteostation systemd[1]: Started LSB: weewx weather 
>> system.
>>
>> with command: ./wee_config --list-drivers i obtain this:
>>
>> weewx@meteostation:~/bin $ ./wee_config --list-drivers
>> Module name  Driver nameVersion  Status
>>   weewx.drivers.acuriteAcuRite0.24
>>   weewx.drivers.cc3000 CC3000 0.12
>>   weewx.drivers.fousb  FineOffsetUSB  1.9
>>   weewx.drivers.simulator  Simulator  3.0
>>   weewx.drivers.te923  TE923  0.22
>>   weewx.drivers.ultimeter  Ultimeter  0.16
>>   weewx.drivers.vantageVantage3.0.9
>>   weewx.drivers.wmr100 WMR100 3.1
>>   weewx.drivers.wmr200 WMR200 3.1.1
>>   weewx.drivers.wmr300 WMR300 0.13
>>   weewx.drivers.wmr9x8 WMR9x8 3.0
>>   weewx.drivers.ws1WS10.25
>>   weewx.drivers.ws23xx WS23xx 0.25
>>   weewx.drivers.ws28xx WS28xx 0.35
>>
>> sorry but i dont understood
>> help me
>> thanks in advance
>>
>> Dario
>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.

[weewx-user] Re: Last WMR-300 driver hangs my raspberry

[mwall]

On Saturday, March 11, 2017 at 4:08:35 PM UTC-5, Ruben Navarro Huedo wrote:
>
> No it doesn't recover 
> It locks all the system hangs the Linux
> I must the turn power off and on again 
>

after you power cycle the computer, what happens?

did you also power cycle the weather station?

it is extremely unlikely that weewx or the weather station is causing your 
computer to hang.  it is much more likely that something else (defective sd 
card?  flaky power?) is causing the hang and the random bytes on the usb.

what does the log say after a restart?

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.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.8 'gauge-data.txt' Issues

[gjr80]

Thank Bob, all the daily high issues are completely due to/within rtgd.py. 

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.8 'gauge-data.txt' Issues

[tempus]

Gary, I had a problem with weewx this morning. Troubleshooting that problem 
reminded me that I installed weewx 3.7.0b2-1 a while back.  The weewx 
problem was found to be due to a bug in that beta version and was fixed by 
upgrading to weewx 3.7.0-1.  I don't know whether the daily-highest-gust 
vs. ten-minute-highest-gust discrepancies I have reported have had anything 
to do with using weewx beta software, but thought they might and wanted to 
let you know what I have been using.

Bob

On Thursday, March 9, 2017 at 10:27:25 PM UTC-8, tempus wrote:
>
> The issue is not only at midnight. It occurs throughout the day whenever 
> the wind speed reaches a new daily high.
>
> Bob
>
> On Thursday, March 9, 2017 at 10:08:15 PM UTC-8, gjr80 wrote:
>>
>> That would give you (in most cases) the same result. The issue is that 
>> 'weewxDailyHigh' does not reset until weeWX saves the 00:00 archive record 
>> to database which (by default) occurs at 00:00:15. After that 15 second 
>> period everything is as it should be. The issue can certainly be fixed but 
>> for a small issue that presents itself for 15 seconds at midnight I am 
>> loathed to spend more time altering an already complex system of loop 
>> stats. The new approach I am working on should do away with the 
>> (continuous) reliance on the the weeWX daily summaries and I will wait 
>> until I have that nailed down before dealing with this issue.
>>
>> Gary
>>
>> On Friday, 10 March 2017 15:55:52 UTC+10, tempus wrote:
>>>
>>> It seems that merely setting "wgustTM" in 'gauge-data.txt' to the 
>>> highest of the daily-high-gust-value from weewx and the current rtgd 
>>> "wgust" value would be an easy fix.  I am not fluent in Python, so this may 
>>> not be technically correct, but in principle like this:
>>>
>>> IndicatedDailyHigh = max(weewxDailyHigh, rtgdTenMinuteHigh)
>>>
>>> -Bob
>>>
>>> On Thursday, March 9, 2017 at 2:49:06 AM UTC-8, gjr80 wrote:

 I observed again at midnight just gone, yes the daily high gust pointer 
 does take a number of seconds before resetting, this is due to the 
 (default) 15 second delay weeWX has from an archive record being generated 
 until the data is saved to archive and the daily summaries updated (rtgd 
 uses a combination of the daily summaries and the loop data since the last 
 archive record to determine daily highs). I am working on a better method 
 of keeping various stats (highs/lows/avg etc) in a loop environment for a 
 separate project, when I get that working I may roll the new approach into 
 rtgd which may improve this. In the meantime the delay can be lessened by 
 reducing the archive delay using the archive_delay option in 
 [StdArchive] in weewx.conf. Whilst the option can be safely reduced 
 from 15 how far it can be safely reduced will, I expect, be station and 
 system dependent.

 Gary 

 On Thursday, 9 March 2017 17:19:06 UTC+10, tempus wrote:
>
> Each time the wind reaches a higher value than previously reached 
> since midnight, both the gauge-hand and the 10-minute-gust-indicator move 
> simultaneously to the new high, but the daily-high-wind-gust-pointer does 
> not. It remains at the previous daily-high until expiration of the 
> current 
> weewx 300-second archive interval when it then also moves to the new high.
>
> I will be traveling the next 24-hours and not able to respond quickly.
>
> -Bob
>
> On Tuesday, March 7, 2017 at 4:04:37 PM UTC-8, gjr80 wrote:
>>
>> I would say that this will quite often be the case.
>>
>> The daily high wind gust pointer should always indicate the highest 
>> wind speed seen after midnight at the start of the day and up to and 
>> including midnight at the end of the day. In other words it will reflect 
>> the highest wind speed indicated by the gauge hand throughout the day. 
>> At 
>> midnight the daily high wind gust pointer is reset to 0 and it will 
>> again 
>> start tracking the highest wind speed seen throughout the new day. On 
>> the 
>> other hand, the 10 minute gust value is the highest wind speed seen over 
>> the last 10 minutes, it is not constrained by day boundaries. So 
>> consider 
>> the first packet that arrives after midnight, say at 2 seconds after 
>> midnight. Assuming its windSpeed value is >0, the daily high wind gust 
>> pointer will move the this new value. Now if the 10 minute wind gust 
>> value 
>> is currently higher than this latest windSpeed (in other words the 10 
>> minute wind gust occurred some time in the last 10 minutes of the 
>> previous 
>> day), the daily high wind gust pointer will not be affected by the 10 
>> minute wind gust and nor should it (because it occurred yesterday). If 
>> the 
>> 2 seconds after midnight windSpeed value is higher than the 10 minute 
>> wind 
>> gust 

[weewx-user] Re: Last WMR-300 driver hangs my raspberry

[Ruben Navarro Huedo]

I see it only these showed times before full system hang 

-- 
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.

[weewx-user] Re: Last WMR-300 driver hangs my raspberry

[Ruben Navarro Huedo]

No it doesn't recover 
It locks all the system hangs the Linux
I must the turn power off and on again 

-- 
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.

[weewx-user] Re: Keeping custom software calcs over update

[Karl Grant]

Thanks for your detailed reply. It was working in 3.5, though I didn't document 
any other changes. 
Now that I'm typing I remember sonething about using degree days as a unit as 
that converts okay.
Iif I get time I might look at creating a temperature difference group 

-- 
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.

[weewx-user] Re: Spike detection - any willing testers

[Ruben Navarro Huedo]

i sent you an email.

El sábado, 21 de enero de 2017, 13:11:30 (UTC+1), Darryn Capes-Davis 
escribió:
>
> Hi All,
>
> I have modified the SqtQC service so it can do spike detection. I am after 
> anyone who is having regular annoying spikes to be a tester. If you have 
> spikes and would like to test changed qc.py code then please let me know. 
> Code written on v 3.6.2 base. Direct email to 
> weather@carlingfordweather.sydney best.
>
> Regards
>
> Darryn
>

-- 
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.

Re: [weewx-user] driver fousb.py

[Thomas Keffer]

Simple typo. You want

weewx.drivers.fousb

not

weexwx.drivers.fousb

Incidentally, it is much easier to change drivers by using the tool
wee_config with the --reconfigure option. It will prevent these kinds of
errors.



On Sat, Mar 11, 2017 at 8:19 AM, Dario Verdi  wrote:

> Hi, im installed with succes the weewx on my raspberry. Ihave a WH1080
> meteostation. I setting the file weewx.conf for this station but when i
> start ther service weewx in the syslog appear this information:
>
> ar 11 17:03:25 meteostation weewx[1375]: engine: Initializing weewx
> version 3.6.2
> Mar 11 17:03:25 meteostation weewx[1375]: engine: Using Python 2.7.9
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Mar 11 17:03:25 meteostation weewx[1375]: engine: Platform
> Linux-4.4.50-v7+-armv7l-with-debian-8.0
> Mar 11 17:03:25 meteostation weewx[1375]: engine: pid file is
> /var/run/weewx.pid
> Mar 11 17:03:25 meteostation weewx[1380]: engine: Using configuration file
> /home/weewx/weewx.conf
> Mar 11 17:03:25 meteostation weewx[1380]: engine: Loading station type
> FineOffsetUSB (weexwx.drivers.fousb)
> Mar 11 17:03:25 meteostation weewx[1380]: engine: Caught unrecoverable
> exception in engine:
> Mar 11 17:03:25 meteostation weewx[1380]:   No module named
> weexwx.drivers.fousb
> Mar 11 17:03:25 meteostation weewx[1380]:   Traceback (most recent
> call last):
> Mar 11 17:03:25 meteostation weewx[1380]: File
> "/home/weewx/bin/weewx/engine.py", line 841, in main
> Mar 11 17:03:25 meteostation weewx[1380]:   engine =
> engine_class(config_dict)
> Mar 11 17:03:25 meteostation weewx[1380]: File
> "/home/weewx/bin/weewx/engine.py", line 70, in __init__
> Mar 11 17:03:25 meteostation weewx[1380]: 
>  self.setupStation(config_dict)
> Mar 11 17:03:25 meteostation weewx[1380]: File
> "/home/weewx/bin/weewx/engine.py", line 94, in setupStation
> Mar 11 17:03:25 meteostation weewx[1380]:   __import__(driver)
> Mar 11 17:03:25 meteostation weewx[1380]:   ImportError: No module
> named weexwx.drivers.fousb
> Mar 11 17:03:25 meteostation weewx[1380]:   Exiting.
> Mar 11 17:03:25 meteostation systemd[1]: Started LSB: weewx weather system.
>
> with command: ./wee_config --list-drivers i obtain this:
>
> weewx@meteostation:~/bin $ ./wee_config --list-drivers
> Module name  Driver nameVersion  Status
>   weewx.drivers.acuriteAcuRite0.24
>   weewx.drivers.cc3000 CC3000 0.12
>   weewx.drivers.fousb  FineOffsetUSB  1.9
>   weewx.drivers.simulator  Simulator  3.0
>   weewx.drivers.te923  TE923  0.22
>   weewx.drivers.ultimeter  Ultimeter  0.16
>   weewx.drivers.vantageVantage3.0.9
>   weewx.drivers.wmr100 WMR100 3.1
>   weewx.drivers.wmr200 WMR200 3.1.1
>   weewx.drivers.wmr300 WMR300 0.13
>   weewx.drivers.wmr9x8 WMR9x8 3.0
>   weewx.drivers.ws1WS10.25
>   weewx.drivers.ws23xx WS23xx 0.25
>   weewx.drivers.ws28xx WS28xx 0.35
>
> sorry but i dont understood
> help me
> thanks in advance
>
> Dario
>
> --
> 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.
>

-- 
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.

[weewx-user] Re: Last WMR-300 driver hangs my raspberry

[Ruben Navarro Huedo]

Driver version 0.18rc7

El sábado, 11 de marzo de 2017, 17:21:23 (UTC+1), Ruben Navarro Huedo 
escribió:
>
> Hello friends.
>
> I think last WMR-300 driver hags my raspberry.
> This is the last i can see in syslog file before it.
>
> Mar 11 16:52:34 raspberrypi kernel: [76709.282773] dwc_otg: DEVICE:004 : 
> update_urb_state_xfer_intr:1435:trimming xfer length
> Mar 11 16:52:34 raspberrypi weewx[9034]: engine: Shutting down StdReport 
> thread
> Mar 11 16:52:34 raspberrypi kernel: [76709.284417] dwc_otg: DEVICE:004 : 
> update_urb_state_xfer_comp:742:trimming xfer length
> Mar 11 16:52:34 raspberrypi weewx[9034]: engine: Caught WeeWxIOError: 
> unknown packet type c0: c0 74 42 b8 0b 10 33 01 00 15 00 7f 00 1c 00 65 00 
> 60 7f fd 11 03 0b 10 1c 00 a4 00 61 11 03 06 08 14 00 f9 01 19 11 03 0b 00 
> 00 7f ff 11 03 04 07 19 00 2b 08 f7 00 00 00 00 00 00 00 00 00 00
> Mar 11 16:52:34 raspberrypi weewx[9034]:   Waiting 60 seconds then 
> retrying...
>
> A lot of thank's
>

-- 
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.

[weewx-user] Last WMR-300 driver hangs my raspberry

[Ruben Navarro Huedo]

Hello friends.

I think last WMR-300 driver hags my raspberry.
This is the last i can see in syslog file before it.

Mar 11 16:52:34 raspberrypi kernel: [76709.282773] dwc_otg: DEVICE:004 : 
update_urb_state_xfer_intr:1435:trimming xfer length
Mar 11 16:52:34 raspberrypi weewx[9034]: engine: Shutting down StdReport 
thread
Mar 11 16:52:34 raspberrypi kernel: [76709.284417] dwc_otg: DEVICE:004 : 
update_urb_state_xfer_comp:742:trimming xfer length
Mar 11 16:52:34 raspberrypi weewx[9034]: engine: Caught WeeWxIOError: 
unknown packet type c0: c0 74 42 b8 0b 10 33 01 00 15 00 7f 00 1c 00 65 00 
60 7f fd 11 03 0b 10 1c 00 a4 00 61 11 03 06 08 14 00 f9 01 19 11 03 0b 00 
00 7f ff 11 03 04 07 19 00 2b 08 f7 00 00 00 00 00 00 00 00 00 00
Mar 11 16:52:34 raspberrypi weewx[9034]:   Waiting 60 seconds then 
retrying...

A lot of thank's

-- 
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.

[weewx-user] driver fousb.py

[Dario Verdi]

Hi, im installed with succes the weewx on my raspberry. Ihave a WH1080 
meteostation. I setting the file weewx.conf for this station but when i 
start ther service weewx in the syslog appear this information:

ar 11 17:03:25 meteostation weewx[1375]: engine: Initializing weewx version 
3.6.2
Mar 11 17:03:25 meteostation weewx[1375]: engine: Using Python 2.7.9 
(default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Mar 11 17:03:25 meteostation weewx[1375]: engine: Platform 
Linux-4.4.50-v7+-armv7l-with-debian-8.0
Mar 11 17:03:25 meteostation weewx[1375]: engine: pid file is 
/var/run/weewx.pid
Mar 11 17:03:25 meteostation weewx[1380]: engine: Using configuration file 
/home/weewx/weewx.conf
Mar 11 17:03:25 meteostation weewx[1380]: engine: Loading station type 
FineOffsetUSB (weexwx.drivers.fousb)
Mar 11 17:03:25 meteostation weewx[1380]: engine: Caught unrecoverable 
exception in engine:
Mar 11 17:03:25 meteostation weewx[1380]:   No module named 
weexwx.drivers.fousb
Mar 11 17:03:25 meteostation weewx[1380]:   Traceback (most recent 
call last):
Mar 11 17:03:25 meteostation weewx[1380]: File 
"/home/weewx/bin/weewx/engine.py", line 841, in main
Mar 11 17:03:25 meteostation weewx[1380]:   engine = 
engine_class(config_dict)
Mar 11 17:03:25 meteostation weewx[1380]: File 
"/home/weewx/bin/weewx/engine.py", line 70, in __init__
Mar 11 17:03:25 meteostation weewx[1380]:  
 self.setupStation(config_dict)
Mar 11 17:03:25 meteostation weewx[1380]: File 
"/home/weewx/bin/weewx/engine.py", line 94, in setupStation
Mar 11 17:03:25 meteostation weewx[1380]:   __import__(driver)
Mar 11 17:03:25 meteostation weewx[1380]:   ImportError: No module 
named weexwx.drivers.fousb
Mar 11 17:03:25 meteostation weewx[1380]:   Exiting.
Mar 11 17:03:25 meteostation systemd[1]: Started LSB: weewx weather system.

with command: ./wee_config --list-drivers i obtain this:

weewx@meteostation:~/bin $ ./wee_config --list-drivers
Module name  Driver nameVersion  Status
  weewx.drivers.acuriteAcuRite0.24
  weewx.drivers.cc3000 CC3000 0.12
  weewx.drivers.fousb  FineOffsetUSB  1.9
  weewx.drivers.simulator  Simulator  3.0
  weewx.drivers.te923  TE923  0.22
  weewx.drivers.ultimeter  Ultimeter  0.16
  weewx.drivers.vantageVantage3.0.9
  weewx.drivers.wmr100 WMR100 3.1
  weewx.drivers.wmr200 WMR200 3.1.1
  weewx.drivers.wmr300 WMR300 0.13
  weewx.drivers.wmr9x8 WMR9x8 3.0
  weewx.drivers.ws1WS10.25
  weewx.drivers.ws23xx WS23xx 0.25
  weewx.drivers.ws28xx WS28xx 0.35

sorry but i dont understood
help me
thanks in advance

Dario

-- 
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.

Re: [weewx-user] Re: Barometer calculation

[Thomas Keffer]

That's pretty much correct. See the function
wxformulas.sealevel_pressure_Metric()

-tk

On Sat, Mar 11, 2017 at 7:25 AM, wysiwyg  wrote:

> Hello Tom,
>
> My question is more related to understand theoritical calculations   :-)
> Weewx works perfectly !
>
>  but I try to understand what is done in stdWXCalculate.
>
> I may have misunderstand, but my understanding is that calculation is:
>
> barometer = pressure /  exp (-elev_meter / (t_K * 29.263))
>
> is this correct?
> t_K is current temp in Kelvin or ?
>
>
>
>
>
>
>
>
>
> Le samedi 11 mars 2017 16:13:10 UTC+1, Tom Keffer a écrit :
>>
>> As explained in the weewx Wiki, *barometer* depends on the temperature
>> 12 hours ago, but *altimeter* does not.
>>
>> If your station emits *pressure*, that is, the raw gauge pressure, the
>> others should be calculated by StdWXCalculate. Is that not happening?
>>
>> -tk
>>
>> On Sat, Mar 11, 2017 at 2:49 AM, wysiwyg  wrote:
>>
>>> ok, I found some more informations.
>>>
>>> The formula here:
>>> https://barani.biz/apps/sea-level-pressure/
>>>
>>> seems to be a so called "international barometric leveling formula"
>>>
>>> at least, it's stated with this name in french wikipedia
>>> https://fr.wikipedia.org/wiki/Formule_du_nivellement_barom%C3%A9trique
>>>
>>>
>>> I was not able to find it as clear in english wiki
>>> https://en.wikipedia.org/wiki/Barometric_formula
>>>
>>>
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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.
>

-- 
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.

Re: [weewx-user] Re: Barometer calculation

[wysiwyg]

Hello Tom,

My question is more related to understand theoritical calculations   :-)
Weewx works perfectly !

 but I try to understand what is done in stdWXCalculate.

I may have misunderstand, but my understanding is that calculation is:

barometer = pressure /  exp (-elev_meter / (t_K * 29.263))

is this correct?
t_K is current temp in Kelvin or ?









Le samedi 11 mars 2017 16:13:10 UTC+1, Tom Keffer a écrit :
>
> As explained in the weewx Wiki, *barometer* depends on the temperature 12 
> hours ago, but *altimeter* does not.
>
> If your station emits *pressure*, that is, the raw gauge pressure, the 
> others should be calculated by StdWXCalculate. Is that not happening?
>
> -tk
>
> On Sat, Mar 11, 2017 at 2:49 AM, wysiwyg  
> wrote:
>
>> ok, I found some more informations.
>>
>> The formula here:
>> https://barani.biz/apps/sea-level-pressure/
>>
>> seems to be a so called "international barometric leveling formula"
>>
>> at least, it's stated with this name in french wikipedia
>> https://fr.wikipedia.org/wiki/Formule_du_nivellement_barom%C3%A9trique
>>
>>
>> I was not able to find it as clear in english wiki
>> https://en.wikipedia.org/wiki/Barometric_formula
>>
>>
>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.

Re: [weewx-user] Re: Barometer calculation

[Thomas Keffer]

As explained in the weewx Wiki, *barometer* depends on the temperature 12
hours ago, but *altimeter* does not.

If your station emits *pressure*, that is, the raw gauge pressure, the
others should be calculated by StdWXCalculate. Is that not happening?

-tk

On Sat, Mar 11, 2017 at 2:49 AM, wysiwyg  wrote:

> ok, I found some more informations.
>
> The formula here:
> https://barani.biz/apps/sea-level-pressure/
>
> seems to be a so called "international barometric leveling formula"
>
> at least, it's stated with this name in french wikipedia
> https://fr.wikipedia.org/wiki/Formule_du_nivellement_barom%C3%A9trique
>
>
> I was not able to find it as clear in english wiki
> https://en.wikipedia.org/wiki/Barometric_formula
>
>
>
> --
> 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.
>

-- 
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.

[weewx-user] Re: Barometer calculation

[wysiwyg]

ok, I found some more informations.

The formula here:
https://barani.biz/apps/sea-level-pressure/

seems to be a so called "international barometric leveling formula"

at least, it's stated with this name in french wikipedia
https://fr.wikipedia.org/wiki/Formule_du_nivellement_barom%C3%A9trique


I was not able to find it as clear in english wiki
https://en.wikipedia.org/wiki/Barometric_formula



-- 
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.

[weewx-user] Re: Barometer calculation

[wysiwyg]

>
> also found this:
>

https://barani.biz/apps/sea-level-pressure/

and this:

http://barani.biz/apps/sea-level-pressure-advanced/?


1st one seems same complexity as weewx but slightly different result... 
(very slightly,  with same data input, I found 0.016mbar difference)

 

-- 
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.

[weewx-user] Barometer calculation

[wysiwyg]

Hello !

I just setup a pressure sensor on my orange pi (with the plan to make it 
work with weewx in the future).
My sensor is a MS5611, it reports absolute pressure, so some calculation 
have to be done to get the barometer value.
I try to check if I can do it by myself or if I shall rely on weewx 
calculation for that.

Here is what I found so far:

- weewx 
wiki https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter
it is stated here that barometer depends also on Temp, Temp 12h ago and 
even humidity.

- weewx code: if I understood correctly the content of formulas code, it's 
more simple. only use current temp, I didnt see temp -12h or humidity.

- I found a documennt on the web that explain how davis station calculate 
barometer (this time with temp, temp -12h and humidity)

- I tried to find how official weather organisation (like meteofrance for 
my country) calculate barometer, but no success til now.

- on some forum I found a simple formula using only altitude ( baro = 
pressure + 1mbar/8.36meter )


The MS5611 is a very accurate sensor, it can reach +/-1.5mbar accuracy (max 
value, at 25°C which is pretty true if used inside house).
So I would like to use the much accurate algorythm possible "at home". 
1st step could be to use weewx formula but then ? 
I wonder if the davis formula is really much better (as I was not able to 
confirm with any "official" weather organisation) or if some other 
algorythm could be more reliable ?

if possible I would like to make the calculation on my sensor side, so I 
can deliver the value to other than weewx ( in case I want to build my own 
TFT display one day).


PS: it's slightly confusing that the wiki talk about temp -12h and humidity 
while it's not used in weewx, (still If I understood correctly) , it may 
worth to display the weewx formula in the wiki


Best regards,

-- 
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.