Hi, A few things to consider:
(1) The WMR300 driver is still being actively worked on so there is a possibility it may still have some bugs. (2) Noting point 1, are you using the latest version of the WMR300 driver or just the version included in the weeWX release you are using? The WMR300 driver in the latest weeWX release was v0.18 (not sure what version of weeWX you are using), there have been 4 commits since then and the driver is currenly at v0.19rc4. You can use something like this to download the latest version of the driver: $ cd /usr/share/weewx/weewx/drivers $ sudo mv wmr300.py wmr300.py.orig $ sudo wget https: //raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/almanac.py> to use the new driver just stop then start weeWX. If you have problems just delete wmr300.py and rename the .orig copy to revert to your original driver. (3) The WMR300 emits what is known as partial loop packets ie the loop packets do not contain all observations. WU has issues if it receives data that does not contain all fields, so when using rapidfire partial packet stations usually do not produce the desired result. In an attempt to deal with this the weeWX WU uploader uses caching of loop packets so even though the WMR300 emits partial packets rapidfire should work. There have been some issue with this caching since it was implemented so it is possible some issues remain. (4) The real test is to monitor the data being sent to WU by weeWX. This can achieved by editing weewx.conf and setting debug = 2, save weewx.conf then stop/start weeWX. If you monitor the log you will see the data being sent by weeWX to WU. If the correct data is there the issue is WU, if not then its most likely the driver/station. If in any doubt post the log from weeWX startup, don't delete anything. (5) You can run weeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly> to monitor the loop data being generated by weeWX and the driver. It might be worthwhile to do this and see whether you are getting the 2.5 second wind updates you think you are. The loop data is on the lines starting with LOOP:, feel free to post a screen capture of the output if you have trouble interpreting it. Gary On Tuesday, 23 January 2018 17:52:07 UTC+10, sina...@gmail.com wrote: > > weewx and underground im talking about, the wind gust updates every 2.5 > seconds but wind and wind direction updates every 5 minute.. > > 22 Ocak 2018 Pazartesi 14:19:48 UTC+3 tarihinde Andrew Milner yazdı: >> >> are you talking about a problem between the weather station and weewx, or >> between weewx and wunderground? >> >> since the wmr300 emits partial packets it is not really the best station >> to be using rapid fire - I would suggest uploading just the archive >> records, and not use rapidfire to get more consistent results. >> >> On Monday, 22 January 2018 13:14:56 UTC+2, Andrew Milner wrote: >> >>> i don't understand your exact problem - can you explain more please >>> >>> >>> On Monday, 22 January 2018 12:56:36 UTC+2, sina...@gmail.com wrote: >>> >>>> It is true, wind gust sends every 2.5 second but I cant say this for >>>> wind and direction... :( >>>> >>>> 22 Ocak 2018 Pazartesi 12:17:03 UTC+3 tarihinde Andrew Milner yazdı: >>>>> >>>>> set rapidfire = True in wunderground section of weewx.conf >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Monday, 22 January 2018 08:32:31 UTC+2, sina...@gmail.com wrote: >>>>> >>>>>> Hi, I am senior school student and I cant disable send avg winddir >>>>>> and wind speed to wunderground. How can I send wind direction what it >>>>>> measures in every 2.5 seconds? 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
