Hi,

I use this version now:

weewx.drivers.wmr300x-v19rc6+f3

All ok... but.. in weewx 3.9.1 driver change¿, can i use wmr300 driver 
default?

thanks.

El jueves, 4 de octubre de 2018, 16:22:22 (UTC+2), Cameron D escribió:
>
> The rc5 and rc6 drivers shjipped with the weewx releases had issues where, 
> after some time (days to weeks) the system would stop reporting any data.
> That was addressed in this update of 24th September 
> <https://groups.google.com/d/topic/weewx-user/jUF4J6tRxPU/discussion>.
>
> At least two users have reported a different problem, where there is only 
> partial loss, for example wind or temperature and humidity.
>
>    1. Juan Antonio Mosquera reports wind data missing 
>    <https://groups.google.com/d/msg/weewx-user/jUF4J6tRxPU/ABecLDR6AQAJ>.
>    2. Markus Biewer reports temperature/humidity, and sometimes other data 
>    going missing after about a week 
>    <https://groups.google.com/d/msg/weewx-user/7QUNDdqbHHE/z7Rr5lqZAgAJ>.
>
> Initially it looked like it might have been related to Belchertown skin, 
> but it is reported to also be an issue with the standard skin.
>
> The attached zip file has 3 files:
>
>    1. *wmr300-v19rc6+f3.py*  - and updated version of the main wmr300 
>    driver - this has a couple of minor bug fixes as well as extra diagnostic 
>    code for this problem.
>    2. *summ-pkt-data.awk*  -   an awk script to  convert the new 
>    diagnostic logfile data into a csv file.
>    3. *wmr300x-v19rc6+f3.py* - note the 'x'. This is the experimental 
>    driver that uses pyusb 1 and libusb1 if available.  It also contains the 
>    extra diagnostics, but is included for the other issue where the pi locks 
>    up completely.
>    
> *New Diagnostics*:
>
> In your weewx.conf file, enable
>   debug=1
>
> and in the WMR300 section I would suggest the following:
>     debug_counts = 1
>     debug_decode = 0
>     debug_comm = 0
>     debug_history = 0
>     debug_timing = 1
>     debug_rain = 0
>
> The debug_counts setting will output a summary of each packet type read 
> from the USB  in a specified time interval (default 20 seconds) as well as 
> the number of loop packets sent to weewx.
>
> Here is my WMR300 section
>
> ##############################################################################
>
> [WMR300]
>     # This section is for WMR300 weather stations
>
>     # The station model, e.g., WMR300A
>     model = WMR300
>
>     # The driver to use:
>     driver = user.wmr300-v19rc6+f3
>
>     history_limit = 6
>
>     debug_counts = 1
>     debug_decode = 0
>     debug_comm = 0
>     debug_history = 1
>     debug_timing = 1
>     debug_rain = 0
>
>
> ##############################################################################
>
> Note that I recommend placing these drivers in the "user" directory of the 
> weewx installation.
> You can also create a similar section named *[WMR300x]* to use the 
> experimental driver, and select between them by editing this line in the 
> *[Station]* section:
>  station_type = WMR300
>
> *Experimental driver:*
> This driver uses the PyUSB version 1 API, which allows it to use libusb1 
> or other usb libraries.
> It will default to libusb1 if possible, but otherwise will fall back to 
> libusb0.
>
> Note that some versions of Ubuntu seemed to ship with a beta version of 
> PyUSB-1 that did not seem to support the full api.  If it reports a version 
> beginning "1.0.0b..." then the driver will use libusb0.
>
> If you enable the experimental version then check the log file when it 
> starts up:
> It will always show pyusb_version, and the experimental driver will print 
> which usb backend library is selected.
>
> grep -i pyusb (your-logfile)
>
> will display both.
>

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

Reply via email to