This weather station is not powered by the usb but by it's own 5V power supply(or by internal nimh rechargeable battery) and it draw a little bit less than 200ma if i don't mistake. i just check the syslog and the forecast error does not appear. so maybe i forgot to restart weewx after the modif. sorry about that. for now the system is running since last reboot and i wont change the genrator tonight to check if it has any influence.
thanks for your help. On Tuesday, January 17, 2017 at 6:28:57 PM UTC+7, Andrew Milner wrote: > > Raspberry changed to a 5.1v from 5v supply for the rpi3, and the network > and usb radio for the weatherstation probably use more than keyboard/mouse > anyway!! > > Did you check forecast to see if there was another occurrence of the error > Matthew found? The error message in the log is the same variable!! > > have you tried the usb radio interface on a hub away from the pi rather > than on the pi itself - just to see if it makes any difference?? > > On Tuesday, 17 January 2017 13:09:02 UTC+2, Marc Aubry wrote: > >> Hi >> there is only the weatherstation running on the rpi usb. >> The other system you are referring are running on other rpi. >> this one is dedicated to weewx only. there is no other usb device >> connected on it. , no keyboard, no screen, simple headless rpi without any >> other software installed on it except for the one installed by default by >> raspbian plus screen and vncserver. >> the power supply is a branded 3A USB power supply and i did try with >> other power supply. >> i did change the file /home/weewx/user/forrecat.py nd the /etc/ >> i did change the /etc/rsyslog.conf as suggested >> >> >> >> >> On Tuesday, January 17, 2017 at 4:57:14 PM UTC+7, Andrew Milner wrote: >>> >>> Are you certain you applied the changes? >>> >>> The log still shows the error Matthew corrected occurred just around the >>> time it stopped reporting >>> and >>> The log started to give the error that should have been cleared by my >>> change. >>> >>> However - the I/O error you got from the USB does imply a USB error >>> situation is lurking somewhere >>> >>> Since you appear to be running with network, USB radio and other >>> possible USB devices - are you using the official WHITE 5.1V 2.5A RPi3 >>> power supply?? The RPi is very finicky when it comes to power supplies and >>> power spikes etc - especially where network and USB power is concerned. I >>> always use a powered USB hub for usb devices. As you are running off a >>> generator could this be a cause of issues? The other Pis you have running >>> do not appear to be working as hard as your weather station one will be. >>> >>> Matthew did suggest disabling the foprecasting whilst trying to resolve >>> your problems - but I see you still have forecasting enabled. >>> >>> Running wioth the simulator would not be exercising the RPi in the same >>> way as running with the station, and like Matthew I would be more >>> suspicious of the RPi and the environment than weewx and the driver. Keep >>> all usb cables well away from the RPi, power supplies, screens etc. >>> >>> >>> >>> On Tuesday, 17 January 2017 10:18:08 UTC+2, Marc Aubry wrote: >>> >>>> Hi, >>>> Just stop reporting 12:15 local time >>>> please find attached syslog. >>>> there is a new interesting message in the syslog >>>> >>>> weatherstation weewx[1508]: wh23xx: get_current: could not detach >>>> kernel driver from interface 0: No data available >>>> >>>> >>>> i was running weewx directly on the console with weewxd >>>> the console was showing: >>>> >>>> 4630124, dewpoint: 18.1644912704, heatindex: 31.7465325172, humidex: >>>> 36.9270806694, inDewpoint: 61.3511118401, inHumidity: 44, inTemp: 29.9, >>>> luminosity: 163463.4, maxSolarRad: 1049.29595861, outHumidity: 47, >>>> outTemp: >>>> 30.8, pressure: 1010.7, radiation: 1291.36086, rain: 0.0, rainRate: 0.0, >>>> usUnits: 16, UV: 11, uv_raw: 4707, windchill: 30.8, windDir: 180, >>>> windGust: >>>> 2.52000626344, windSpeed: 1.08000268433 >>>> REC: 2017-01-17 12:15:00 WIB (1484630100) altimeter: 1011.05970952, >>>> appTemp: 32.2804131054, barometer: 1011.32893478, cloudbase: >>>> 1566.52849627, >>>> dateTime: 1484630100.0, dewpoint: 17.9667744592, ET: 0.00931318400731, >>>> heatindex: 31.3295548186, humidex: 36.4708326323, inDewpoint: >>>> 62.1629006698, inHumidity: 45.1, inTemp: 29.97, interval: 5, luminosity: >>>> 157830.85, maxSolarRad: 1048.23640656, outHumidity: 47.25, outTemp: 30.49, >>>> pressure: 1010.76, radiation: 1246.863715, rain: 0.0, rainRate: 0.0, >>>> usUnits: 16, UV: 11.0, uv_raw: 4707.0, windchill: 30.49, windDir: >>>> 185.798196225, windGust: 12.960064424, windGustDir: None, windrun: >>>> 15.3518033795, windSpeed: 5.09402532221 >>>> LOOP: 2017-01-17 12:15:24 WIB (1484630124) altimeter: 1010.99968069, >>>> appTemp: 33.4553572395, barometer: 1011.26832054, cloudbase: >>>> 1580.52915436, >>>> dateTime: 1484630124, dewpoint: 18.1644912704, heatindex: 31.7465325172, >>>> humidex: 36.9270806694, inDewpoint: 61.3511118401, inHumidity: 44, inTemp: >>>> 29.9, luminosity: 163463.4, maxSolarRad: 1049.29595861, outHumidity: 47, >>>> outTemp: 30.8, pressure: 1010.7, radiation: 1291.36086, rain: 0.0, >>>> rainRate: 0.0, usUnits: 16, UV: 11, uv_raw: 4707, windchill: 30.8, >>>> windDir: >>>> 180, windGust: 2.52000626344, windSpeed: 1.08000268433 >>>> >>>> >>>> I hope it will help.... >>>> >>>> >>>> On Tuesday, January 17, 2017 at 12:04:46 PM UTC+7, Andrew Milner wrote: >>>>> >>>>> Marc - if it freezes again you should post a new log - especially >>>>> since you have now made changes to both the forecast module (which should >>>>> eliminate forecast related error messages) and also to syslog.conf (which >>>>> hopefully removes even more logged messages). We don't want to be >>>>> looking >>>>> at the wrong log for the current situation!! >>>>> >>>>> >>>>> >>>>> On Tuesday, 17 January 2017 06:33:46 UTC+2, Marc Aubry wrote: >>>>> >>>>>> Yes i did. >>>>>> Wait and see >>>>>> So far so good >>>>>> thanks >>>>>> >>>>>> >>>>>> On Tuesday, January 17, 2017 at 10:38:36 AM UTC+7, Andrew Milner >>>>>> wrote: >>>>>>> >>>>>>> Yes, that's what I was referring to ..... >>>>>>> >>>>>>> Have you tried amending the syslog.conf as I suggested in previous >>>>>>> posting to see if that is causing your weewx to freeze? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, 17 January 2017 05:26:20 UTC+2, Marc Aubry wrote: >>>>>>> >>>>>>>> Hi andrew >>>>>>>> are your referring to this forecast error? >>>>>>>> >>>>>>>> Jan 16 22:40:27 weatherstation weewx[645]: forecast: OWMThread: >>>>>>>> OWM: forecast failure: global name 'periods' is not defined >>>>>>>> Jan 16 22:40:27 weatherstation weewx[645]: File >>>>>>>> "/home/weewx/bin/user/forecas .py", line 1173, in do_forecast >>>>>>>> >>>>>>>> I do not know where it' is coming from... >>>>>>>> My forecast install is standard as described in the forecast >>>>>>>> instrucrion. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Monday, January 16, 2017 at 6:37:29 PM UTC+7, Andrew Milner >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> PS - in case you are unaware there are errors in the log connected >>>>>>>>> to the forecast module and forecast page ..... don't think they are a >>>>>>>>> direct cause of your problem though. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, 16 January 2017 13:08:37 UTC+2, Marc Aubry wrote: >>>>>>>>> >>>>>>>>>> Hi >>>>>>>>>> The weewx has just stop reporting and i did a lsusb command and >>>>>>>>>> it look the same then before it stop reporting. >>>>>>>>>> so it is not a problem of usb port changing name or order. >>>>>>>>>> >>>>>>>>>> Bus 001 Device 004: ID 10c4:8468 Cygnal Integrated Products, Inc. >>>>>>>>>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >>>>>>>>>> SMSC9512/9514 Fast Ethernet Adapter >>>>>>>>>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >>>>>>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Monday, January 16, 2017 at 9:48:58 AM UTC+7, Marc Aubry wrote: >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> Thanks for this info >>>>>>>>>>> i have listed the usb devices with lsusb >>>>>>>>>>> >>>>>>>>>>> Bus 001 Device 004: ID 10c4:8468 Cygnal Integrated Products, Inc. >>>>>>>>>>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. >>>>>>>>>>> SMSC9512/9514 Fast Ethernet Adapter >>>>>>>>>>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. >>>>>>>>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>>>>>>>> >>>>>>>>>>> I guess that my weather station is Device 004: ID 10c4:8468 >>>>>>>>>>> I will wait the next time the weewx stop reporting to check if >>>>>>>>>>> the device number has changed. >>>>>>>>>>> I check in my weewx.conf file and i have no such thing as >>>>>>>>>>> "device link" i just have the following lines referring to the >>>>>>>>>>> driver i'm >>>>>>>>>>> using: >>>>>>>>>>> [WH23xx] >>>>>>>>>>> # This section is for Fine Offset WH23xx stations >>>>>>>>>>> # The model name such as Tycon, or TP2700 >>>>>>>>>>> model = WH2310 >>>>>>>>>>> # The driver to use >>>>>>>>>>> driver = user.wh23xx >>>>>>>>>>> >>>>>>>>>>> Do i have to add the following "port = /dev/mydevice" in the >>>>>>>>>>> weewx.conf file? >>>>>>>>>>> >>>>>>>>>>> thanks for your help >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sunday, January 15, 2017 at 8:58:57 PM UTC+7, Per Edström >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Apparently my USB-to-COM-port converter is not stable hence >>>>>>>>>>>> causing weewx to stop (when the device changes). SO I made a link >>>>>>>>>>>> to the >>>>>>>>>>>> current device for use in weewx.conf (details in a new thread here >>>>>>>>>>>> in the >>>>>>>>>>>> forum). >>>>>>>>>>>> It seems to work for 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
