Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Thank you for that suggestion, I will expeditiously follow up! On Saturday, 13 March 2021 at 14:05:03 UTC+13 gjr80 wrote: > So you are back using the original Envoy that was 'tripping the fuse'? > Regards the two beeps from the Envoy I understand the first indicates > successful startup of the processor and the second verifies the > installation of the logger so it seems your single beep does point to an > issue with the logger. Given you have things working again it might be > worthwhile contacting Davis in slower time and finding out if you do have > an incompatible Envoy/logger or if there is some other issue with one or > the other. If your original Envoy just started working again it could just > as easily stop as well; having a backup would be handy. > > Gary > On Saturday, 13 March 2021 at 10:38:16 UTC+10 monmul wrote: > >> A big THANK YOU to all who helped me out on this, I really appreciate the >> help and guidancesorry it turned into a wild goose chase! >> >> On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote: >> >>> Yep fully functional againupdating on the website...WTF!.are >>> these things sent to us to just test our patience!! >>> >>> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote: >>> >>>> Hmmm! even more curiouserI notice from my webpage that data was >>>> collected and posted yesterdayafter having nothing updated for almost >>>> 2 >>>> weeks! >>>> >>>> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote: >>>> >>>>> So, if it is the RPi then it is either a sofward corruption on the >>>>> card caused by the repeated rebooting after the fuse tripsor else >>>>> some >>>>> hardward failure on the board was the cause of the tripping. Its strange >>>>> that since reassembling the Envoy, RPi etc there has not been a fuse trip. >>>>> >>>>> One other thought occurs to me...I have a powered USB Hub attached to >>>>> the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy >>>>> directly into the RPi..if minicom works that would point to the Hub >>>>> as >>>>> being the culpit!!?? >>>>> >>>>> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote: >>>>> >>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>> pi@WeatherPi:~ $ wee_device --clear-memory >>>>>> Using configuration file /etc/weewx/weewx.conf >>>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage) >>>>>> Proceeding will erase all archive records. >>>>>> Are you sure you wish to proceed (y/n)? y >>>>>> Erasing all archive records ... >>>>>> Archive records erased. >>>>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>>>>> >>>>>> >>>>>> Welcome to minicom 2.7 >>>>>> >>>>>> OPTIONS: I18n >>>>>> Compiled on Apr 22 2017, 09:14:19. >>>>>> Port /dev/ttyUSB0, 12:49:30 >>>>>> >>>>>> Press CTRL-A Z for help on special keys >>>>>> . >>>>>> . >>>>>> . >>>>>> >>>>>> >>>>>> Again no return of TEST or NVER >>>>>> >>>>>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote: >>>>>> >>>>>>> So, having put the old Envoy back on the Rpi (having shown it worked >>>>>>> on the PC) this is what I getlooks like some kind of continuous >>>>>>> Loop >>>>>>> situation. >>>>>>> >>>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>>>>>> >>>>>>> >>>>>>> >>>>>>> Welcome to minicom 2.7 >>>>>>> >>>>>>> OPTIONS: I18n >>>>>>> Compiled on Apr 22 2017, 09:14:19. >>>>>>> Port /dev/ttyUSB0, 12:42:51 >>>>>>> >>>>>>> Press CTRL-A Z for help on special keys >>>>>>&
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
A big THANK YOU to all who helped me out on this, I really appreciate the help and guidancesorry it turned into a wild goose chase! On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote: > Yep fully functional againupdating on the website...WTF!.are these > things sent to us to just test our patience!! > > On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote: > >> Hmmm! even more curiouserI notice from my webpage that data was >> collected and posted yesterdayafter having nothing updated for almost 2 >> weeks! >> >> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote: >> >>> So, if it is the RPi then it is either a sofward corruption on the card >>> caused by the repeated rebooting after the fuse tripsor else some >>> hardward failure on the board was the cause of the tripping. Its strange >>> that since reassembling the Envoy, RPi etc there has not been a fuse trip. >>> >>> One other thought occurs to me...I have a powered USB Hub attached to >>> the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy >>> directly into the RPi..if minicom works that would point to the Hub as >>> being the culpit!!?? >>> >>> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote: >>> >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ wee_device --clear-memory >>>> Using configuration file /etc/weewx/weewx.conf >>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage) >>>> Proceeding will erase all archive records. >>>> Are you sure you wish to proceed (y/n)? y >>>> Erasing all archive records ... >>>> Archive records erased. >>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>>> >>>> >>>> Welcome to minicom 2.7 >>>> >>>> OPTIONS: I18n >>>> Compiled on Apr 22 2017, 09:14:19. >>>> Port /dev/ttyUSB0, 12:49:30 >>>> >>>> Press CTRL-A Z for help on special keys >>>> . >>>> . >>>> . >>>> >>>> >>>> Again no return of TEST or NVER >>>> >>>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote: >>>> >>>>> So, having put the old Envoy back on the Rpi (having shown it worked >>>>> on the PC) this is what I getlooks like some kind of continuous Loop >>>>> situation. >>>>> >>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>>>> >>>>> >>>>> >>>>> Welcome to minicom 2.7 >>>>> >>>>> OPTIONS: I18n >>>>> Compiled on Apr 22 2017, 09:14:19. >>>>> Port /dev/ttyUSB0, 12:42:51 >>>>> >>>>> Press CTRL-A Z for help on special keys >>>>> >>>>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >>>>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >>>>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2 >>>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> >>>>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> >>>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>>> >>>>> Á LOO1 =vŠ 4I Àÿÿ
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Yep fully functional againupdating on the website...WTF!.are these things sent to us to just test our patience!! On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote: > Hmmm! even more curiouserI notice from my webpage that data was > collected and posted yesterdayafter having nothing updated for almost 2 > weeks! > > On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote: > >> So, if it is the RPi then it is either a sofward corruption on the card >> caused by the repeated rebooting after the fuse tripsor else some >> hardward failure on the board was the cause of the tripping. Its strange >> that since reassembling the Envoy, RPi etc there has not been a fuse trip. >> >> One other thought occurs to me...I have a powered USB Hub attached to the >> RPi(its a 3B)maybe I should disconnect the hub and try the Envoy >> directly into the RPi..if minicom works that would point to the Hub as >> being the culpit!!?? >> >> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote: >> >>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>> pi@WeatherPi:~ $ wee_device --clear-memory >>> Using configuration file /etc/weewx/weewx.conf >>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage) >>> Proceeding will erase all archive records. >>> Are you sure you wish to proceed (y/n)? y >>> Erasing all archive records ... >>> Archive records erased. >>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>> >>> >>> Welcome to minicom 2.7 >>> >>> OPTIONS: I18n >>> Compiled on Apr 22 2017, 09:14:19. >>> Port /dev/ttyUSB0, 12:49:30 >>> >>> Press CTRL-A Z for help on special keys >>> . >>> . >>> . >>> >>> >>> Again no return of TEST or NVER >>> >>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote: >>> >>>> So, having put the old Envoy back on the Rpi (having shown it worked on >>>> the PC) this is what I getlooks like some kind of continuous Loop >>>> situation. >>>> >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>>> >>>> >>>> >>>> Welcome to minicom 2.7 >>>> >>>> OPTIONS: I18n >>>> Compiled on Apr 22 2017, 09:14:19. >>>> Port /dev/ttyUSB0, 12:42:51 >>>> >>>> Press CTRL-A Z for help on special keys >>>> >>>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >>>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >>>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2 >>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>>> >>>> /‚LOO1 =vŠ 4I Àÿÿ
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Hmmm! even more curiouserI notice from my webpage that data was collected and posted yesterdayafter having nothing updated for almost 2 weeks! On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote: > So, if it is the RPi then it is either a sofward corruption on the card > caused by the repeated rebooting after the fuse tripsor else some > hardward failure on the board was the cause of the tripping. Its strange > that since reassembling the Envoy, RPi etc there has not been a fuse trip. > > One other thought occurs to me...I have a powered USB Hub attached to the > RPi(its a 3B)maybe I should disconnect the hub and try the Envoy > directly into the RPi..if minicom works that would point to the Hub as > being the culpit!!?? > > On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote: > >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ wee_device --clear-memory >> Using configuration file /etc/weewx/weewx.conf >> Using Vantage driver version 3.2.1 (weewx.drivers.vantage) >> Proceeding will erase all archive records. >> Are you sure you wish to proceed (y/n)? y >> Erasing all archive records ... >> Archive records erased. >> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >> >> >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 12:49:30 >> >> Press CTRL-A Z for help on special keys >> . >> . >> . >> >> >> Again no return of TEST or NVER >> >> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote: >> >>> So, having put the old Envoy back on the Rpi (having shown it worked on >>> the PC) this is what I getlooks like some kind of continuous Loop >>> situation. >>> >>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >>> >>> >>> >>> Welcome to minicom 2.7 >>> >>> OPTIONS: I18n >>> Compiled on Apr 22 2017, 09:14:19. >>> Port /dev/ttyUSB0, 12:42:51 >>> >>> Press CTRL-A Z for help on special keys >>> >>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2 >>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> >>> >>> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >>> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½ b 2 >>> ¾LOO1 =vŠ 4I Áÿÿÿ >>> >>> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote: >>> >>>> But from the tests on my PC, it seems the old Envoy is workingdoes >>>> it not.(so we do not have to worry about the new Envoy for now!)...so it >>>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
So, if it is the RPi then it is either a sofward corruption on the card caused by the repeated rebooting after the fuse tripsor else some hardward failure on the board was the cause of the tripping. Its strange that since reassembling the Envoy, RPi etc there has not been a fuse trip. One other thought occurs to me...I have a powered USB Hub attached to the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy directly into the RPi..if minicom works that would point to the Hub as being the culpit!!?? On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote: > pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop > [ ok ] Stopping weewx (via systemctl): weewx.service. > pi@WeatherPi:~ $ wee_device --clear-memory > Using configuration file /etc/weewx/weewx.conf > Using Vantage driver version 3.2.1 (weewx.drivers.vantage) > Proceeding will erase all archive records. > Are you sure you wish to proceed (y/n)? y > Erasing all archive records ... > Archive records erased. > pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 > > > Welcome to minicom 2.7 > > OPTIONS: I18n > Compiled on Apr 22 2017, 09:14:19. > Port /dev/ttyUSB0, 12:49:30 > > Press CTRL-A Z for help on special keys > . > . > . > > > Again no return of TEST or NVER > > On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote: > >> So, having put the old Envoy back on the Rpi (having shown it worked on >> the PC) this is what I getlooks like some kind of continuous Loop >> situation. >> >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 >> >> >> >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 12:42:51 >> >> Press CTRL-A Z for help on special keys >> >> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 >> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2 >> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> >> >> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 >> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½ b 2 >> ¾LOO1 =vŠ 4I Áÿÿÿ >> >> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote: >> >>> But from the tests on my PC, it seems the old Envoy is workingdoes >>> it not.(so we do not have to worry about the new Envoy for now!)...so it >>> would appear as if the RPi is the culpithave I deducted correctly? >>> >>> On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote: >>> >>>> They did, but it was about 7 or 8 years ago. >>>> >>>> You really need to call Davis. >>>> >>>> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy wrote: >>>> >>>>> i do recall that davis introduced an incompatability between old >>>>> firmware and new datalogger but i don’t recall the details. i’m sure a >>>>> sea
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ wee_device --clear-memory Using configuration file /etc/weewx/weewx.conf Using Vantage driver version 3.2.1 (weewx.drivers.vantage) Proceeding will erase all archive records. Are you sure you wish to proceed (y/n)? y Erasing all archive records ... Archive records erased. pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 Welcome to minicom 2.7 OPTIONS: I18n Compiled on Apr 22 2017, 09:14:19. Port /dev/ttyUSB0, 12:49:30 Press CTRL-A Z for help on special keys . . . Again no return of TEST or NVER On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote: > So, having put the old Envoy back on the Rpi (having shown it worked on > the PC) this is what I getlooks like some kind of continuous Loop > situation. > > pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop > [ ok ] Stopping weewx (via systemctl): weewx.service. > pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 > > > > Welcome to minicom 2.7 > > OPTIONS: I18n > Compiled on Apr 22 2017, 09:14:19. > Port /dev/ttyUSB0, 12:42:51 > > Press CTRL-A Z for help on special keys > > LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 > v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 > ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2 > /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > > > ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 > âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½ b 2 > ¾LOO1 =vŠ 4I Áÿÿÿ > > On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote: > >> But from the tests on my PC, it seems the old Envoy is workingdoes it >> not.(so we do not have to worry about the new Envoy for now!)...so it would >> appear as if the RPi is the culpithave I deducted correctly? >> >> On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote: >> >>> They did, but it was about 7 or 8 years ago. >>> >>> You really need to call Davis. >>> >>> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy wrote: >>> >>>> i do recall that davis introduced an incompatability between old >>>> firmware and new datalogger but i don’t recall the details. i’m sure a >>>> search of the forum archive would see if that was relevant >>>> >>>> On 11 Mar 2021, at 2:17 pm, monmul wrote: >>>> >>>> Yes I am using the original data logger and cable that came with the >>>> old EnvoyI take out the data logger from he old one and put it in the >>>> new one...I suspect that the data logger may not be compatible with the >>>> new >>>> Envoy >>>> >>>> >>>> -- >>>> 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. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com?utm_medium=email_source=footer> >>>> . >>>> >>> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1f558dfd-e64d-4b9c-9345-65914fbe7743n%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
So, having put the old Envoy back on the Rpi (having shown it worked on the PC) this is what I getlooks like some kind of continuous Loop situation. pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0 Welcome to minicom 2.7 OPTIONS: I18n Compiled on Apr 22 2017, 09:14:19. Port /dev/ttyUSB0, 12:42:51 Press CTRL-A Z for help on special keys LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ b 2 ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2 âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½ b 2 ¾LOO1 =vŠ 4I Áÿÿÿ On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote: > But from the tests on my PC, it seems the old Envoy is workingdoes it > not.(so we do not have to worry about the new Envoy for now!)...so it would > appear as if the RPi is the culpithave I deducted correctly? > > On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote: > >> They did, but it was about 7 or 8 years ago. >> >> You really need to call Davis. >> >> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy wrote: >> >>> i do recall that davis introduced an incompatability between old >>> firmware and new datalogger but i don’t recall the details. i’m sure a >>> search of the forum archive would see if that was relevant >>> >>> On 11 Mar 2021, at 2:17 pm, monmul wrote: >>> >>> Yes I am using the original data logger and cable that came with the old >>> EnvoyI take out the data logger from he old one and put it in the new >>> one...I suspect that the data logger may not be compatible with the new >>> Envoy >>> >>> >>> -- >>> 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. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com?utm_medium=email_source=footer> >>> . >>> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4bd182b2-7e47-4507-bc37-157f3682da8an%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
But from the tests on my PC, it seems the old Envoy is workingdoes it not.(so we do not have to worry about the new Envoy for now!)...so it would appear as if the RPi is the culpithave I deducted correctly? On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote: > They did, but it was about 7 or 8 years ago. > > You really need to call Davis. > > On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy wrote: > >> i do recall that davis introduced an incompatability between old firmware >> and new datalogger but i don’t recall the details. i’m sure a search of the >> forum archive would see if that was relevant >> >> On 11 Mar 2021, at 2:17 pm, monmul wrote: >> >> Yes I am using the original data logger and cable that came with the old >> EnvoyI take out the data logger from he old one and put it in the new >> one...I suspect that the data logger may not be compatible with the new >> Envoy >> >> >> -- >> 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. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com >> >> <https://groups.google.com/d/msgid/weewx-user/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com?utm_medium=email_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/43c5919c-9ec8-4e89-b2e0-a7a1efa2d180n%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Yes I am using the original data logger and cable that came with the old EnvoyI take out the data logger from he old one and put it in the new one...I suspect that the data logger may not be compatible with the new Envoy.the new one was purchased about 3 years ago and was just put in storage and never used or tested. The product numbers are slightly different the old one being 6316 and the new one being 6316NZ On Thursday, 11 March 2021 at 16:12:21 UTC+13 graha...@gmail.com wrote: > how much is ‘new’ and much much ‘old’? i.e. with the new envoy, are you > using the old known-working data logger and cable? > > On 11 Mar 2021, at 2:09 pm, monmul wrote: > > New Envoy shows no response to TEST or NVER...so that one is definately > dead I think! > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9e31efdd-ba9e-4300-8e34-040ee7fd6d27n%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
I notice the old Envoy beeps twice when I plug it in but the new one only beeps once. On Thursday, 11 March 2021 at 16:01:11 UTC+13 monmul wrote: > New Envoy shows no response to TEST or NVER...so that one is definately > dead I think! > > On Thursday, 11 March 2021 at 15:39:36 UTC+13 monmul wrote: > >> "WRD"<0x12><0x4d>, ACK .not sure hot to use this commandis it >> just "WRD"? >> This is the old Envoy >> >> No data as such comes backherefrom the first "TEST" is the result >> of all the commands above in turn. >> TEST >> >> >> OK >> 2363 7 0 1316 1 >> >> OK >> >> >> OK >> >> >> >> OK >> >> Dec 30 2008 >> >> >> >> OK >> >> 1.82 >> >> >> >> >> >> On Thursday, 11 March 2021 at 15:04:01 UTC+13 gjr80 wrote: >> >>> Ok, that sounds promising. Was that the old or the new Envoy? >>> >>> FYI the other testing commands are: >>> >>> Testing commands >>> "TEST" Sends the string “TEST\n” back. >>> "WRD"<0x12><0x4d>, ACK Responds with a weather station type that is >>> backward compatible with earlier Davis weather products. >>> "RXCHECK" Sends the Console Diagnostics report. >>> "RXTEST" Moves the console from the “Receiving from” screen to the >>> main current conditions screen. >>> "VER" >>> "RECEIVERS" Sends the bit map of station IDs that the console can >>> hear, This is not the byte for indicating what the console selects to >>> listen from. >>> "NVER" Sends the firmware version number as a text string. This >>> command is only supported by Vantage Pro2 (Firmware 1.90 or later) and >>> Vantage Vue. >>> >>> >>> Gary >>> On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote: >>> >>>> j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0 >>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>> /run/user/1000/gvfs >>>> Output information may be incomplete. >>>> lsof: WARNING: can't stat() fuse.pcloud file system >>>> /tmp/.mount_pcloudpeaisz >>>> Output information may be incomplete. >>>> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc >>>> Output information may be incomplete. >>>> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive >>>> Output information may be incomplete. >>>> pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200 >>>> sudo: screen: command not found >>>> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0 >>>> >>>> Command 'minicom' not found, but can be installed with: >>>> >>>> sudo apt install minicom >>>> >>>> pj@pj-selgbuild:~$ sudo apt install minicom >>>> Reading package lists... Done >>>> Building dependency tree >>>> Reading state information... Done >>>> The following additional packages will be installed: >>>> lrzsz >>>> The following NEW packages will be installed: >>>> lrzsz minicom >>>> 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. >>>> Need to get 313 kB of archives. >>>> After this operation, 1,486 kB of additional disk space will be used. >>>> Do you want to continue? [Y/n] y >>>> Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 >>>> lrzsz amd64 0.12.21-10 [74.8 kB] >>>> Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 >>>> minicom amd64 2.7.1-1.1 [239 kB] >>>> Fetched 313 kB in 1s (603 kB/s) >>>> Selecting previously unselected package lrzsz. >>>> (Reading database ... 289378 files and directories c
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
New Envoy shows no response to TEST or NVER...so that one is definately dead I think! On Thursday, 11 March 2021 at 15:39:36 UTC+13 monmul wrote: > "WRD"<0x12><0x4d>, ACK .not sure hot to use this commandis it just > "WRD"? > This is the old Envoy > > No data as such comes backherefrom the first "TEST" is the result > of all the commands above in turn. > TEST > > > OK > 2363 7 0 1316 1 > > OK > > > OK > > > > OK > > Dec 30 2008 > > > > OK > > 1.82 > > > > > > On Thursday, 11 March 2021 at 15:04:01 UTC+13 gjr80 wrote: > >> Ok, that sounds promising. Was that the old or the new Envoy? >> >> FYI the other testing commands are: >> >> Testing commands >> "TEST" Sends the string “TEST\n” back. >> "WRD"<0x12><0x4d>, ACK Responds with a weather station type that is >> backward compatible with earlier Davis weather products. >> "RXCHECK" Sends the Console Diagnostics report. >> "RXTEST" Moves the console from the “Receiving from” screen to the main >> current conditions screen. >> "VER" >> "RECEIVERS" Sends the bit map of station IDs that the console can hear, >> This is not the byte for indicating what the console selects to listen from. >> "NVER" Sends the firmware version number as a text string. This command >> is only supported by Vantage Pro2 (Firmware 1.90 or later) and Vantage Vue. >> >> >> Gary >> On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote: >> >>> j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0 >>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>> /run/user/1000/gvfs >>> Output information may be incomplete. >>> lsof: WARNING: can't stat() fuse.pcloud file system >>> /tmp/.mount_pcloudpeaisz >>> Output information may be incomplete. >>> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc >>> Output information may be incomplete. >>> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive >>> Output information may be incomplete. >>> pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200 >>> sudo: screen: command not found >>> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0 >>> >>> Command 'minicom' not found, but can be installed with: >>> >>> sudo apt install minicom >>> >>> pj@pj-selgbuild:~$ sudo apt install minicom >>> Reading package lists... Done >>> Building dependency tree >>> Reading state information... Done >>> The following additional packages will be installed: >>> lrzsz >>> The following NEW packages will be installed: >>> lrzsz minicom >>> 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. >>> Need to get 313 kB of archives. >>> After this operation, 1,486 kB of additional disk space will be used. >>> Do you want to continue? [Y/n] y >>> Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 >>> lrzsz amd64 0.12.21-10 [74.8 kB] >>> Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 >>> minicom amd64 2.7.1-1.1 [239 kB] >>> Fetched 313 kB in 1s (603 kB/s) >>> Selecting previously unselected package lrzsz. >>> (Reading database ... 289378 files and directories currently installed.) >>> Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ... >>> Unpacking lrzsz (0.12.21-10) ... >>> Selecting previously unselected package minicom. >>> Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ... >>> Unpacking minicom (2.7.1-1.1) ... >>> Setting up minicom (2.7.1-1.1) ... >>> Setting up lrzsz (0.12.21-10) ... >>> Processing triggers for mime-support (3.64ubuntu1) ... >>> Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... >>> Processing triggers for man
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
"WRD"<0x12><0x4d>, ACK .not sure hot to use this commandis it just "WRD"? This is the old Envoy No data as such comes backherefrom the first "TEST" is the result of all the commands above in turn. TEST OK 2363 7 0 1316 1 OK OK OK Dec 30 2008 OK 1.82 On Thursday, 11 March 2021 at 15:04:01 UTC+13 gjr80 wrote: > Ok, that sounds promising. Was that the old or the new Envoy? > > FYI the other testing commands are: > > Testing commands > "TEST" Sends the string “TEST\n” back. > "WRD"<0x12><0x4d>, ACK Responds with a weather station type that is > backward compatible with earlier Davis weather products. > "RXCHECK" Sends the Console Diagnostics report. > "RXTEST" Moves the console from the “Receiving from” screen to the main > current conditions screen. > "VER" > "RECEIVERS" Sends the bit map of station IDs that the console can hear, > This is not the byte for indicating what the console selects to listen from. > "NVER" Sends the firmware version number as a text string. This command > is only supported by Vantage Pro2 (Firmware 1.90 or later) and Vantage Vue. > > > Gary > On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote: > >> j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0 >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> lsof: WARNING: can't stat() fuse.pcloud file system >> /tmp/.mount_pcloudpeaisz >> Output information may be incomplete. >> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc >> Output information may be incomplete. >> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive >> Output information may be incomplete. >> pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200 >> sudo: screen: command not found >> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0 >> >> Command 'minicom' not found, but can be installed with: >> >> sudo apt install minicom >> >> pj@pj-selgbuild:~$ sudo apt install minicom >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> The following additional packages will be installed: >> lrzsz >> The following NEW packages will be installed: >> lrzsz minicom >> 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. >> Need to get 313 kB of archives. >> After this operation, 1,486 kB of additional disk space will be used. >> Do you want to continue? [Y/n] y >> Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 lrzsz >> amd64 0.12.21-10 [74.8 kB] >> Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 >> minicom amd64 2.7.1-1.1 [239 kB] >> Fetched 313 kB in 1s (603 kB/s) >> Selecting previously unselected package lrzsz. >> (Reading database ... 289378 files and directories currently installed.) >> Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ... >> Unpacking lrzsz (0.12.21-10) ... >> Selecting previously unselected package minicom. >> Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ... >> Unpacking minicom (2.7.1-1.1) ... >> Setting up minicom (2.7.1-1.1) ... >> Setting up lrzsz (0.12.21-10) ... >> Processing triggers for mime-support (3.64ubuntu1) ... >> Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... >> Processing triggers for man-db (2.9.1-1) ... >> Processing triggers for desktop-file-utils (0.24-1ubuntu3) ... >> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0 >> minicom: cannot open /dev/ttyUSB0: Permission denied >> pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0 >> >> >> Welcome to minicom 2.7.1 >> >> OPTIONS: I18n >> Compiled on Dec 23 2019, 02:06:26. >> Port /dev/ttyUSB0, 14:14:37 >> >> Press CTRL-A Z for help on special keys >> >> >> >> >> >> >> >> >> >>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.pcloud file system /tmp/.mount_pcloudpeaisz Output information may be incomplete. lsof: WARNING: can't stat() fuse file system /run/user/1000/doc Output information may be incomplete. lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive Output information may be incomplete. pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200 sudo: screen: command not found pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0 Command 'minicom' not found, but can be installed with: sudo apt install minicom pj@pj-selgbuild:~$ sudo apt install minicom Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: lrzsz The following NEW packages will be installed: lrzsz minicom 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded. Need to get 313 kB of archives. After this operation, 1,486 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 lrzsz amd64 0.12.21-10 [74.8 kB] Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 minicom amd64 2.7.1-1.1 [239 kB] Fetched 313 kB in 1s (603 kB/s) Selecting previously unselected package lrzsz. (Reading database ... 289378 files and directories currently installed.) Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ... Unpacking lrzsz (0.12.21-10) ... Selecting previously unselected package minicom. Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ... Unpacking minicom (2.7.1-1.1) ... Setting up minicom (2.7.1-1.1) ... Setting up lrzsz (0.12.21-10) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu3) ... pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Permission denied pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0 Welcome to minicom 2.7.1 OPTIONS: I18n Compiled on Dec 23 2019, 02:06:26. Port /dev/ttyUSB0, 14:14:37 Press CTRL-A Z for help on special keys TEST TEST OK 1.82 On Thursday, 11 March 2021 at 14:14:18 UTC+13 monmul wrote: > Hmm! nothiing shows...I have a USB port plugged into this pc...and none of > the USBs show?!?! > > pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0 > [sudo] password for pj: > lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs > Output information may be incomplete. > lsof: WARNING: can't stat() fuse.pcloud file system > /tmp/.mount_pcloudpeaisz > Output information may be incomplete. > lsof: WARNING: can't stat() fuse file system /run/user/1000/doc > Output information may be incomplete. > lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive > Output information may be incomplete. > pj@pj-selgbuild:~$ > > > On Tuesday, 9 March 2021 at 21:58:49 UTC+13 monmul wrote: > >> Been MS free since 2008. Never used Apple. Got Lineage on my phone. >> >> On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote: >> >>> Someone who has seen the light! :) >>> >>> On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote: >>> >>>> Thanks, I only have Ubuntuand I use VNC client. >>>> >>>> >>>> >>>> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote: >>>> >>>>> PuTTY (https://www.putty.org/), which is a free SSH/telnet client >>>>> works on Windows devices and can also connect to serial devices. >>>>> >>>>> -- >>>>> David >>>>> >>>>> On Tue, Mar 9, 2021 at 5:15 PM monmul wrote: >>>>> >>>>>> Cool, thanks, will get on that with my laptop in the next day or >>>>>> sothank you! >>>>>> >>>>>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote: >>>>>> >>>>>>> Anything will do, no grunt needed, all you need is a terminal >>>>>>> program of some sort, minicom will do the job on anything Linux. >>>>>>> Windows >>>>>>> used to come with some sort of terminal program. Not sure about a Mac. >>>>>>> Certainly no need to install WeeWX, you just want to run the >>>>>>> connectivity >>>>>>> test with your Envoy(s) to prove it(they) respond(s). >>>>>>> >>>>>>&
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Hmm! nothiing shows...I have a USB port plugged into this pc...and none of the USBs show?!?! pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0 [sudo] password for pj: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.pcloud file system /tmp/.mount_pcloudpeaisz Output information may be incomplete. lsof: WARNING: can't stat() fuse file system /run/user/1000/doc Output information may be incomplete. lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive Output information may be incomplete. pj@pj-selgbuild:~$ On Tuesday, 9 March 2021 at 21:58:49 UTC+13 monmul wrote: > Been MS free since 2008. Never used Apple. Got Lineage on my phone. > > On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote: > >> Someone who has seen the light! :) >> >> On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote: >> >>> Thanks, I only have Ubuntuand I use VNC client. >>> >>> >>> >>> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote: >>> >>>> PuTTY (https://www.putty.org/), which is a free SSH/telnet client >>>> works on Windows devices and can also connect to serial devices. >>>> >>>> -- >>>> David >>>> >>>> On Tue, Mar 9, 2021 at 5:15 PM monmul wrote: >>>> >>>>> Cool, thanks, will get on that with my laptop in the next day or >>>>> sothank you! >>>>> >>>>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote: >>>>> >>>>>> Anything will do, no grunt needed, all you need is a terminal program >>>>>> of some sort, minicom will do the job on anything Linux. Windows used to >>>>>> come with some sort of terminal program. Not sure about a Mac. Certainly >>>>>> no >>>>>> need to install WeeWX, you just want to run the connectivity test with >>>>>> your >>>>>> Envoy(s) to prove it(they) respond(s). >>>>>> >>>>>> Gary >>>>>> >>>>>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote: >>>>>> >>>>>>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that >>>>>>> likely to have enough grunt to do the job? Oh! do you mean I could >>>>>>> attach >>>>>>> the "new" Envoy to a PC (running Ubuntu) and do the connectivity test? >>>>>>> >>>>>>> >>>>>>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote: >>>>>>> >>>>>>>> Possibly, but if you are using the same RPi with the same cable as >>>>>>>> you have used with your new unresponsive Envoy then perhaps the issue >>>>>>>> is >>>>>>>> with the RPi or the cable. I would be looking for another RPi or PC >>>>>>>> (Windows (ugh), Mac or whatever) and run a terminal window/program and >>>>>>>> do >>>>>>>> the basic connectivity test (send ENTER and get a response from the >>>>>>>> Envoy). >>>>>>>> I would even try a different cable if you have another. Two different >>>>>>>> RPis/PCs/cables etc not working would be unusual. If that fails to get >>>>>>>> a >>>>>>>> response from your new Envoy then as Tom said it's time to get in >>>>>>>> touch >>>>>>>> with Davis or their agent. >>>>>>>> >>>>>>>> Gary >>>>>>>> >>>>>>>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote: >>>>>>>> >>>>>>>>> Is this telling me that my "old" Envoy is indeed broken? >>>>>>>>> >>>>>>>>> pi@WeatherPi:~ $ wee_device --clear-memory >>>>>>>>> Using configuration file /etc/weewx/weewx.conf >>>>>>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage) >>>>>>>>> Unable to wake up console... sleeping >>>>>>>>> Unable to wake up console... retrying >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File "/usr/share/weewx/wee_device", line 78, in >>>>>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Been MS free since 2008. Never used Apple. Got Lineage on my phone. On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote: > Someone who has seen the light! :) > > On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote: > >> Thanks, I only have Ubuntuand I use VNC client. >> >> >> >> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote: >> >>> PuTTY (https://www.putty.org/), which is a free SSH/telnet client works >>> on Windows devices and can also connect to serial devices. >>> >>> -- >>> David >>> >>> On Tue, Mar 9, 2021 at 5:15 PM monmul wrote: >>> >>>> Cool, thanks, will get on that with my laptop in the next day or >>>> sothank you! >>>> >>>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote: >>>> >>>>> Anything will do, no grunt needed, all you need is a terminal program >>>>> of some sort, minicom will do the job on anything Linux. Windows used to >>>>> come with some sort of terminal program. Not sure about a Mac. Certainly >>>>> no >>>>> need to install WeeWX, you just want to run the connectivity test with >>>>> your >>>>> Envoy(s) to prove it(they) respond(s). >>>>> >>>>> Gary >>>>> >>>>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote: >>>>> >>>>>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely >>>>>> to have enough grunt to do the job? Oh! do you mean I could attach the >>>>>> "new" Envoy to a PC (running Ubuntu) and do the connectivity test? >>>>>> >>>>>> >>>>>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote: >>>>>> >>>>>>> Possibly, but if you are using the same RPi with the same cable as >>>>>>> you have used with your new unresponsive Envoy then perhaps the issue >>>>>>> is >>>>>>> with the RPi or the cable. I would be looking for another RPi or PC >>>>>>> (Windows (ugh), Mac or whatever) and run a terminal window/program and >>>>>>> do >>>>>>> the basic connectivity test (send ENTER and get a response from the >>>>>>> Envoy). >>>>>>> I would even try a different cable if you have another. Two different >>>>>>> RPis/PCs/cables etc not working would be unusual. If that fails to get >>>>>>> a >>>>>>> response from your new Envoy then as Tom said it's time to get in touch >>>>>>> with Davis or their agent. >>>>>>> >>>>>>> Gary >>>>>>> >>>>>>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote: >>>>>>> >>>>>>>> Is this telling me that my "old" Envoy is indeed broken? >>>>>>>> >>>>>>>> pi@WeatherPi:~ $ wee_device --clear-memory >>>>>>>> Using configuration file /etc/weewx/weewx.conf >>>>>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage) >>>>>>>> Unable to wake up console... sleeping >>>>>>>> Unable to wake up console... retrying >>>>>>>> Traceback (most recent call last): >>>>>>>> File "/usr/share/weewx/wee_device", line 78, in >>>>>>>> main() >>>>>>>> File "/usr/share/weewx/wee_device", line 74, in main >>>>>>>> device.configure(config_dict) >>>>>>>> File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in >>>>>>>> configure >>>>>>>> self.do_options(options, parser, config_dict, not >>>>>>>> options.noprompt) >>>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in >>>>>>>> do_options >>>>>>>> station = Vantage(**config_dict[DRIVER_NAME]) >>>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in >>>>>>>> __init__ >>>>>>>> self._setup() >>>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in >>>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Thanks, I only have Ubuntuand I use VNC client.
On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:
> PuTTY (https://www.putty.org/), which is a free SSH/telnet client works
> on Windows devices and can also connect to serial devices.
>
> --
> David
>
> On Tue, Mar 9, 2021 at 5:15 PM monmul wrote:
>
>> Cool, thanks, will get on that with my laptop in the next day or
>> sothank you!
>>
>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>>
>>> Anything will do, no grunt needed, all you need is a terminal program of
>>> some sort, minicom will do the job on anything Linux. Windows used to come
>>> with some sort of terminal program. Not sure about a Mac. Certainly no need
>>> to install WeeWX, you just want to run the connectivity test with your
>>> Envoy(s) to prove it(they) respond(s).
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>>>
>>>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely
>>>> to have enough grunt to do the job? Oh! do you mean I could attach the
>>>> "new" Envoy to a PC (running Ubuntu) and do the connectivity test?
>>>>
>>>>
>>>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>>>>
>>>>> Possibly, but if you are using the same RPi with the same cable as you
>>>>> have used with your new unresponsive Envoy then perhaps the issue is with
>>>>> the RPi or the cable. I would be looking for another RPi or PC (Windows
>>>>> (ugh), Mac or whatever) and run a terminal window/program and do the
>>>>> basic
>>>>> connectivity test (send ENTER and get a response from the Envoy). I would
>>>>> even try a different cable if you have another. Two different
>>>>> RPis/PCs/cables etc not working would be unusual. If that fails to get a
>>>>> response from your new Envoy then as Tom said it's time to get in touch
>>>>> with Davis or their agent.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>>>>>
>>>>>> Is this telling me that my "old" Envoy is indeed broken?
>>>>>>
>>>>>> pi@WeatherPi:~ $ wee_device --clear-memory
>>>>>> Using configuration file /etc/weewx/weewx.conf
>>>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>>>>> Unable to wake up console... sleeping
>>>>>> Unable to wake up console... retrying
>>>>>> Traceback (most recent call last):
>>>>>> File "/usr/share/weewx/wee_device", line 78, in
>>>>>> main()
>>>>>> File "/usr/share/weewx/wee_device", line 74, in main
>>>>>> device.configure(config_dict)
>>>>>> File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in
>>>>>> configure
>>>>>> self.do_options(options, parser, config_dict, not
>>>>>> options.noprompt)
>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in
>>>>>> do_options
>>>>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in
>>>>>> __init__
>>>>>> self._setup()
>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in
>>>>>> _setup
>>>>>> self.hardware_type = self._determine_hardware()
>>>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in
>>>>>> _determine_hardware
>>>>>> raise weewx.WeeWxIOError("Unable to read hardware type")
>>>>>> weewx.WeeWxIOError: Unable to read hardware type
>>>>>>
>>>>>>
>>>>>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>>>>>
>>>>>>> *WeeWX generates HTML pages, but it does not update them
>>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them>*
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Mar 6, 2021 at 10:27 PM monmul wrote:
>>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Cool, thanks, will get on that with my laptop in the next day or
sothank you!
On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
> Anything will do, no grunt needed, all you need is a terminal program of
> some sort, minicom will do the job on anything Linux. Windows used to come
> with some sort of terminal program. Not sure about a Mac. Certainly no need
> to install WeeWX, you just want to run the connectivity test with your
> Envoy(s) to prove it(they) respond(s).
>
> Gary
>
> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>
>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely to
>> have enough grunt to do the job? Oh! do you mean I could attach the "new"
>> Envoy to a PC (running Ubuntu) and do the connectivity test?
>>
>>
>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>>
>>> Possibly, but if you are using the same RPi with the same cable as you
>>> have used with your new unresponsive Envoy then perhaps the issue is with
>>> the RPi or the cable. I would be looking for another RPi or PC (Windows
>>> (ugh), Mac or whatever) and run a terminal window/program and do the basic
>>> connectivity test (send ENTER and get a response from the Envoy). I would
>>> even try a different cable if you have another. Two different
>>> RPis/PCs/cables etc not working would be unusual. If that fails to get a
>>> response from your new Envoy then as Tom said it's time to get in touch
>>> with Davis or their agent.
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>>>
>>>> Is this telling me that my "old" Envoy is indeed broken?
>>>>
>>>> pi@WeatherPi:~ $ wee_device --clear-memory
>>>> Using configuration file /etc/weewx/weewx.conf
>>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>>> Unable to wake up console... sleeping
>>>> Unable to wake up console... retrying
>>>> Traceback (most recent call last):
>>>> File "/usr/share/weewx/wee_device", line 78, in
>>>> main()
>>>> File "/usr/share/weewx/wee_device", line 74, in main
>>>> device.configure(config_dict)
>>>> File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in
>>>> configure
>>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in
>>>> do_options
>>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in
>>>> __init__
>>>> self._setup()
>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
>>>> self.hardware_type = self._determine_hardware()
>>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in
>>>> _determine_hardware
>>>> raise weewx.WeeWxIOError("Unable to read hardware type")
>>>> weewx.WeeWxIOError: Unable to read hardware type
>>>>
>>>>
>>>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>>>
>>>>> *WeeWX generates HTML pages, but it does not update them
>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them>*
>>>>>
>>>>>
>>>>> On Sat, Mar 6, 2021 at 10:27 PM monmul wrote:
>>>>>
>>>>>> Even curiouserthe photo which is supposed to update every 20
>>>>>> minutes does updatebut not the weather data...still stuck on
>>>>>> 21/2/2021
>>>>>>
>>>>>> www.wilsonbayweather.com
>>>>>>
>>>>>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>>>>>
>>>>>>> Mar 7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>>>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>>>>>>> Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>>>> Retry #0 failed
>>>>>>> Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>>>> Rude wake up of console successful
>>>>>>> Mar 7 19:20:19 WeatherPi dhcp
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely to
have enough grunt to do the job? Oh! do you mean I could attach the "new"
Envoy to a PC (running Ubuntu) and do the connectivity test?
On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
> Possibly, but if you are using the same RPi with the same cable as you
> have used with your new unresponsive Envoy then perhaps the issue is with
> the RPi or the cable. I would be looking for another RPi or PC (Windows
> (ugh), Mac or whatever) and run a terminal window/program and do the basic
> connectivity test (send ENTER and get a response from the Envoy). I would
> even try a different cable if you have another. Two different
> RPis/PCs/cables etc not working would be unusual. If that fails to get a
> response from your new Envoy then as Tom said it's time to get in touch
> with Davis or their agent.
>
> Gary
>
> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>
>> Is this telling me that my "old" Envoy is indeed broken?
>>
>> pi@WeatherPi:~ $ wee_device --clear-memory
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>> Unable to wake up console... sleeping
>> Unable to wake up console... retrying
>> Traceback (most recent call last):
>> File "/usr/share/weewx/wee_device", line 78, in
>> main()
>> File "/usr/share/weewx/wee_device", line 74, in main
>> device.configure(config_dict)
>> File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in configure
>> self.do_options(options, parser, config_dict, not options.noprompt)
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in
>> do_options
>> station = Vantage(**config_dict[DRIVER_NAME])
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
>> self._setup()
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
>> self.hardware_type = self._determine_hardware()
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in
>> _determine_hardware
>> raise weewx.WeeWxIOError("Unable to read hardware type")
>> weewx.WeeWxIOError: Unable to read hardware type
>>
>>
>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>
>>> *WeeWX generates HTML pages, but it does not update them
>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them>*
>>>
>>>
>>> On Sat, Mar 6, 2021 at 10:27 PM monmul wrote:
>>>
>>>> Even curiouserthe photo which is supposed to update every 20
>>>> minutes does updatebut not the weather data...still stuck on 21/2/2021
>>>>
>>>> www.wilsonbayweather.com
>>>>
>>>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>>>
>>>>> Mar 7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>>>>> Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>> Retry #0 failed
>>>>> Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude
>>>>> wake up of console successful
>>>>> Mar 7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement
>>>>> from fe80::724f:57ff:feb7:82a1
>>>>> Mar 7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>>>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>> Retrieving 513 page(s); starting index= 0
>>>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>> DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800)
>>>>> less
>>>>> than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
>>>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>> Catch up complete.
>>>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>>>>> reports for latest time in the database.
>>>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>>>> Requesting 200 LOOP packets.
>>>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>>>>> report 'StandardReport'
>>>>> Mar 7 19:20:20 WeatherPi w
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Is this telling me that my "old" Envoy is indeed broken?
pi@WeatherPi:~ $ wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console... retrying
Traceback (most recent call last):
File "/usr/share/weewx/wee_device", line 78, in
main()
File "/usr/share/weewx/wee_device", line 74, in main
device.configure(config_dict)
File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in configure
self.do_options(options, parser, config_dict, not options.noprompt)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
self._setup()
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
self.hardware_type = self._determine_hardware()
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in
_determine_hardware
raise weewx.WeeWxIOError("Unable to read hardware type")
weewx.WeeWxIOError: Unable to read hardware type
On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
> *WeeWX generates HTML pages, but it does not update them
> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#weewx-generates-html-pages-but-it-does-not-update-them>*
>
>
> On Sat, Mar 6, 2021 at 10:27 PM monmul wrote:
>
>> Even curiouserthe photo which is supposed to update every 20 minutes
>> does updatebut not the weather data...still stuck on 21/2/2021
>>
>> www.wilsonbayweather.com
>>
>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>
>>> Mar 7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>>> Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry
>>> #0 failed
>>> Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude
>>> wake up of console successful
>>> Mar 7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from
>>> fe80::724f:57ff:feb7:82a1
>>> Mar 7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>> Retrieving 513 page(s); starting index= 0
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: DMPAFT
>>> complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less than
>>> final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch
>>> up complete.
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>>> reports for latest time in the database.
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>>> Requesting 200 LOOP packets.
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>>> report 'StandardReport'
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found
>>> configuration file /etc/weewx/skins/Standard/skin.conf for report
>>> 'StandardReport'
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using
>>> search list ['weewx.cheetahgenerator.Almanac',
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
>>> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Gentle
>>> wake up of console successful
>>> Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary
>>> version is 4.0
>>> Mar 7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator:
>>> Generated 15 files for report StandardReport in 2.42 seconds
>>> Mar 7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary
>>> version is 4.0
>>> Mar 7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from
>>> fe80::724f:57ff:feb7:82a1
>>> Mar 7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>>> Mar 7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator:
>>> Generated 24 images for report StandardReport in 5.17 seconds
>>> Mar 7 19:20:28 WeatherPi weewx[789] INFO weewx.reportengine: Copied 0
>>> files to /var/www/html/weewx
>>> Mar 7 19:20:28 WeatherPi weewx[789] DE
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Even curiouserthe photo which is supposed to update every 20 minutes does updatebut not the weather data...still stuck on 21/2/2021 www.wilsonbayweather.com On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote: > Mar 7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Getting > archive packets since 2021-02-21 08:00:00 NZDT (1613847600) > Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry #0 > failed > Mar 7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude > wake up of console successful > Mar 7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: > Retrieving 513 page(s); starting index= 0 > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: DMPAFT > complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less than > final timestamp 2021-02-21 08:00:00 NZDT (1613847600) > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch up > complete. > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running > reports for latest time in the database. > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: > Requesting 200 LOOP packets. > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running > report 'StandardReport' > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found > configuration file /etc/weewx/skins/Standard/skin.conf for report > 'StandardReport' > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using > search list ['weewx.cheetahgenerator.Almanac', > 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', > 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', > 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics'] > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Gentle > wake up of console successful > Mar 7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary > version is 4.0 > Mar 7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator: > Generated 15 files for report StandardReport in 2.42 seconds > Mar 7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary > version is 4.0 > Mar 7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator: Generated > 24 images for report StandardReport in 5.17 seconds > Mar 7 19:20:28 WeatherPi weewx[789] INFO weewx.reportengine: Copied 0 > files to /var/www/html/weewx > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running > report 'xstats' > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found > configuration file /etc/weewx/skins/xstats/skin.conf for report 'xstats' > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using > search list ['weewx.cheetahgenerator.Almanac', > 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', > 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', > 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics'] > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary > version is 4.0 > Mar 7 19:20:28 WeatherPi weewx[789] INFO weewx.cheetahgenerator: > Generated 1 files for report xstats in 0.08 seconds > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report > 'SeasonsReport' not enabled. Skipping. > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report > 'SmartphoneReport' not enabled. Skipping. > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report > 'MobileReport' not enabled. Skipping. > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running > report 'FTP' > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found > configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP' > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Attempting > connection to 43.245.53.39 > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Connected to > 43.245.53.39 > Mar 7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded > file /var/www/html/weewx/dayradiation.png to /public_html/dayradiation.png > Mar 7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded > file /var/www/html/weewx/index.html to /public_html/index.html > Mar 7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded > file /var/www/html/weewx/weekrain.png
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
weeutil.ftpupload: Uploaded file /var/www/html/weewx/RSS/weewx_rss.xml to /public_html/RSS/weewx_rss.xml Mar 7 19:20:36 WeatherPi weewx[789] INFO weewx.reportengine: ftpgenerator: Ftp'd 41 files in 7.70 seconds Mar 7 19:20:36 WeatherPi weewx[789] DEBUG weewx.reportengine: Running report 'RSYNC' Mar 7 19:20:36 WeatherPi weewx[789] DEBUG weewx.reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' Mar 7 19:20:36 WeatherPi weewx[789] DEBUG weewx.reportengine: rsyncgenerator: Rsync upload not requested. Skipped. Mar 7 19:20:40 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:20:41 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:20:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:20:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:20:54 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:20:54 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:02 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:02 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:07 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:07 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:16 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:16 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:31 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:31 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:36 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:36 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:46 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:46 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:54 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:21:54 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:21:59 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:00 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:09 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:09 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:17 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:17 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:21 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:21 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:28 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:28 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:37 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:37 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:45 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:45 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:47 WeatherPi ntpd[519]: 122.252.188.99 local addr 10.1.1.8 -> Mar 7 19:22:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 19:22:55 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 19:22:55 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease On Sunday, 7 March 2021 at 19:19:41 UTC+13 monmul wrote: > Weather Underground also not updating and showing station as > offline.Hmmm! > > On Sunday, 7 March 2021 at 19:17:32 UTC+13 monmul wrote: > >> Hmmm! while it appears to be working with the "old" Envoy (if my reading >> of the log is correct)..the website is not updatingso I am >> wondering if any data is getting through! >> >> On Sunday, 7 March 2021 at 18:45:08 UTC+13 monmul wrote: >> >>> OK, so I decided to put the "old" Envoy back on the one that seemed >>> to be causing the tripping of the fuse (the fuse has not tripped since I >>> took this "old" Envoy out...It now looks as if the "old" Envoy is >>> working..is that what this log is saying? Weird or what? >>> >>> >>> Mar 7 18:33:48 Weat
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Weather Underground also not updating and showing station as offline.Hmmm! On Sunday, 7 March 2021 at 19:17:32 UTC+13 monmul wrote: > Hmmm! while it appears to be working with the "old" Envoy (if my reading > of the log is correct)..the website is not updatingso I am > wondering if any data is getting through! > > On Sunday, 7 March 2021 at 18:45:08 UTC+13 monmul wrote: > >> OK, so I decided to put the "old" Envoy back on the one that seemed >> to be causing the tripping of the fuse (the fuse has not tripped since I >> took this "old" Envoy out...It now looks as if the "old" Envoy is >> working..is that what this log is saying? Weird or what? >> >> >> Mar 7 18:33:48 WeatherPi systemd[1]: Time has been changed >> Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp >> 0xe3eea886.b0043efc does not match aorg 00. from >> ser...@103.106.65.219 xmt 0xe3eee43c.47439f60 >> Mar 7 18:33:48 WeatherPi systemd[1]: apt-daily-upgrade.timer: Adding >> 22min 56.174539s random time. >> Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp >> 0xe3eea886.bab7752e does not match aorg 00. from >> ser...@103.242.70.4 xmt 0xe3eee43c.4df29247 >> Mar 7 18:33:48 WeatherPi systemd[866]: Time has been changed >> Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp >> 0xe3eea886.babc71d5 does not match aorg 00. from >> ser...@203.99.128.48 xmt 0xe3eee43c.4e0fc836 >> Mar 7 18:33:48 WeatherPi systemd[1]: apt-daily.timer: Adding 9h 58min >> 38.719051s random time. >> Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp >> 0xe3eea886.babae406 does not match aorg 00. from >> ser...@103.239.8.21 xmt 0xe3eee43c.4d91500b >> Mar 7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 2min >> 39.415226s random time. >> Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp >> 0xe3eea886.bab509f8 does not match aorg 00. from >> ser...@202.46.185.18 xmt 0xe3eee43c.4ef41ef6 >> Mar 7 18:33:48 WeatherPi systemd[1]: Started Run anacron jobs. >> Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp >> 0xe3eea886.bab93b56 does not match aorg 00. from >> ser...@162.159.200.1 xmt 0xe3eee43c.4fa4370e >> Mar 7 18:33:48 WeatherPi anacron[1474]: Anacron 2.3 started on 2021-03-07 >> Mar 7 18:33:48 WeatherPi anacron[1474]: Normal exit (0 jobs run) >> Mar 7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 4min >> 53.491534s random time. >> Mar 7 18:33:49 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP >> try #1; error: Expected to read 99 chars; got 14 instead >> Mar 7 18:33:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Mar 7 18:33:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease >> Mar 7 18:33:51 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP >> try #2; error: LOOP buffer failed CRC check >> Mar 7 18:33:53 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP >> try #3; error: LOOP buffer failed CRC check >> Mar 7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP >> try #4; error: LOOP buffer failed CRC check >> Mar 7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP >> max tries (4) exceeded. >> Mar 7 18:33:55 WeatherPi weewx[789] INFO weewx.engine: Main loop >> exiting. Shutting engine down. >> Mar 7 18:33:55 WeatherPi weewx[789] DEBUG weewx.restx: Shut down >> Wunderground-PWS thread. >> Mar 7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Caught >> WeeWxIOError: Max tries exceeded while getting LOOP data. >> Mar 7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Waiting >> 60 seconds then retrying... >> Mar 7 18:33:59 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Mar 7 18:33:59 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease >> Mar 7 18:34:04 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Mar 7 18:34:04 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease >> Mar 7 18:34:09 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Mar 7 18:34:09 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease >> Mar 7 18:34:14 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Mar 7 18:34:14 WeatherPi dhcpcd[361]: wlan
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Hmmm! while it appears to be working with the "old" Envoy (if my reading of the log is correct)..the website is not updatingso I am wondering if any data is getting through! On Sunday, 7 March 2021 at 18:45:08 UTC+13 monmul wrote: > OK, so I decided to put the "old" Envoy back on the one that seemed to > be causing the tripping of the fuse (the fuse has not tripped since I took > this "old" Envoy out...It now looks as if the "old" Envoy is > working..is that what this log is saying? Weird or what? > > > Mar 7 18:33:48 WeatherPi systemd[1]: Time has been changed > Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp > 0xe3eea886.b0043efc does not match aorg 00. from > ser...@103.106.65.219 xmt 0xe3eee43c.47439f60 > Mar 7 18:33:48 WeatherPi systemd[1]: apt-daily-upgrade.timer: Adding > 22min 56.174539s random time. > Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp > 0xe3eea886.bab7752e does not match aorg 00. from > ser...@103.242.70.4 xmt 0xe3eee43c.4df29247 > Mar 7 18:33:48 WeatherPi systemd[866]: Time has been changed > Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp > 0xe3eea886.babc71d5 does not match aorg 00. from > ser...@203.99.128.48 xmt 0xe3eee43c.4e0fc836 > Mar 7 18:33:48 WeatherPi systemd[1]: apt-daily.timer: Adding 9h 58min > 38.719051s random time. > Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp > 0xe3eea886.babae406 does not match aorg 00. from > ser...@103.239.8.21 xmt 0xe3eee43c.4d91500b > Mar 7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 2min > 39.415226s random time. > Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp > 0xe3eea886.bab509f8 does not match aorg 00. from > ser...@202.46.185.18 xmt 0xe3eee43c.4ef41ef6 > Mar 7 18:33:48 WeatherPi systemd[1]: Started Run anacron jobs. > Mar 7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp > 0xe3eea886.bab93b56 does not match aorg 00. from > ser...@162.159.200.1 xmt 0xe3eee43c.4fa4370e > Mar 7 18:33:48 WeatherPi anacron[1474]: Anacron 2.3 started on 2021-03-07 > Mar 7 18:33:48 WeatherPi anacron[1474]: Normal exit (0 jobs run) > Mar 7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 4min > 53.491534s random time. > Mar 7 18:33:49 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try > #1; error: Expected to read 99 chars; got 14 instead > Mar 7 18:33:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:33:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:33:51 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try > #2; error: LOOP buffer failed CRC check > Mar 7 18:33:53 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try > #3; error: LOOP buffer failed CRC check > Mar 7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try > #4; error: LOOP buffer failed CRC check > Mar 7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP max > tries (4) exceeded. > Mar 7 18:33:55 WeatherPi weewx[789] INFO weewx.engine: Main loop exiting. > Shutting engine down. > Mar 7 18:33:55 WeatherPi weewx[789] DEBUG weewx.restx: Shut down > Wunderground-PWS thread. > Mar 7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Caught > WeeWxIOError: Max tries exceeded while getting LOOP data. > Mar 7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Waiting > 60 seconds then retrying... > Mar 7 18:33:59 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:33:59 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:34:04 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:34:04 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:34:09 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:34:09 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:34:14 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:34:14 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:34:20 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:34:20 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:34:26 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from > fe80::724f:57ff:feb7:82a1 > Mar 7 18:34:26 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease > Mar 7 18:34:34 WeatherPi dhcpcd[361]: wlan0:
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
LOOP try #2; error: Expected to read 99 chars; got 0 instead Mar 7 18:35:21 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 18:35:21 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 18:35:23 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead Mar 7 18:35:27 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 18:35:27 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 18:35:31 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 18:35:31 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 18:35:37 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 18:35:37 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 18:35:44 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 18:35:44 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease Mar 7 18:35:48 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Mar 7 18:35:48 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease On Sunday, 7 March 2021 at 00:34:16 UTC+13 tke...@gmail.com wrote: > Nothing that we haven't seen before: your RPi cannot connect with the > logger. > > On Fri, Mar 5, 2021 at 7:18 PM monmul wrote: > >> Thanks for that, I will get around to setting up another Pi in a few >> days. In the meantime, does this give us any useful information >> >> Mar 6 12:53:29 WeatherPi weewx[870] INFO __main__: Using configuration >> file /etc/weewx/weewx.conf >> Mar 6 12:53:29 WeatherPi weewx[870] INFO __main__: Debug is 1 >> Mar 6 12:53:29 WeatherPi weewx[870] DEBUG __main__: Initializing engine >> Mar 6 12:53:29 WeatherPi weewx[870] INFO weewx.engine: Loading station >> type Vantage (weewx.drivers.vantage) >> Mar 6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Driver >> version is 3.2.1 >> Mar 6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Option >> loop_request=1 >> Mar 6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Opened >> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00 >> Mar 6 12:53:30 WeatherPi lightdm[918]: Error getting user list from >> org.freedesktop.Accounts: >> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name >> org.freedesktop.Accounts was not provided by any .service files >> Mar 6 12:53:33 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry >> #0 failed >> Mar 6 12:53:37 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry >> #1 failed >> Mar 6 12:53:41 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry >> #2 failed >> Mar 6 12:53:43 WeatherPi vncserver-x11[515,root]: ServerManager: Server >> started >> Mar 6 12:53:44 WeatherPi vncserver-x11[515,root]: ConsoleDisplay: Found >> running X server (pid=789, binary=/usr/lib/xorg/Xorg) >> Mar 6 12:53:45 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry >> #3 failed >> Mar 6 12:53:45 WeatherPi weewx[870] ERROR weewx.drivers.vantage: Unable >> to wake up console >> Mar 6 12:53:45 WeatherPi weewx[870] ERROR weewx.engine: Import of driver >> failed: Unable to wake up Vantage console () >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> Traceback (most recent call last): >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> self.console = loader_function(config_dict, self) >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> return VantageService(engine, config_dict) >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__ >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> Vantage.__init__(self, **config_dict[DRIVER_NAME]) >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__ >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> self._setup() >> Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/d
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Thanks for that, I will get around to setting up another Pi in a few days.
In the meantime, does this give us any useful information
Mar 6 12:53:29 WeatherPi weewx[870] INFO __main__: Using configuration
file /etc/weewx/weewx.conf
Mar 6 12:53:29 WeatherPi weewx[870] INFO __main__: Debug is 1
Mar 6 12:53:29 WeatherPi weewx[870] DEBUG __main__: Initializing engine
Mar 6 12:53:29 WeatherPi weewx[870] INFO weewx.engine: Loading station
type Vantage (weewx.drivers.vantage)
Mar 6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Driver
version is 3.2.1
Mar 6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Option
loop_request=1
Mar 6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Opened up
serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Mar 6 12:53:30 WeatherPi lightdm[918]: Error getting user list from
org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 6 12:53:33 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #0
failed
Mar 6 12:53:37 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #1
failed
Mar 6 12:53:41 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #2
failed
Mar 6 12:53:43 WeatherPi vncserver-x11[515,root]: ServerManager: Server
started
Mar 6 12:53:44 WeatherPi vncserver-x11[515,root]: ConsoleDisplay: Found
running X server (pid=789, binary=/usr/lib/xorg/Xorg)
Mar 6 12:53:45 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #3
failed
Mar 6 12:53:45 WeatherPi weewx[870] ERROR weewx.drivers.vantage: Unable to
wake up console
Mar 6 12:53:45 WeatherPi weewx[870] ERROR weewx.engine: Import of driver
failed: Unable to wake up Vantage console ()
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
Traceback (most recent call last):
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
self.console = loader_function(config_dict, self)
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
return VantageService(engine, config_dict)
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
self._setup()
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
self.port.wakeup_console(max_tries=self.max_tries)
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in
wakeup_console
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
raise weewx.WakeupError("Unable to wake up Vantage console")
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:
WakeupError: Unable to wake up Vantage console
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL __main__: Unable to load
driver: Unable to wake up Vantage console
Mar 6 12:53:45 WeatherPi weewx[870] CRITICAL __main__: Exiting...
Mar 6 13:53:57 WeatherPi vncserver-x11[515,root]: Connections: connected:
10.1.1.155::58448 (TCP)
Mar 6 13:53:57 WeatherPi vncserver-x11[515,root]: Connections:
authenticated: 10.1.1.155::58448 (TCP), as (anonymous) (d permissions)
Mar 6 13:53:57 WeatherPi vncserver-x11[515,root]: SPrintConnMgr: Failed to
add printer: server-error-service-unavailable
Mar 6 15:00:14 WeatherPi vncserver-x11[515,root]: Connections:
disconnected: 10.1.1.155::58448 (TCP) ([IdleTimeout] This connection has
timed out through inactivity.)
Mar 6 15:49:17 WeatherPi vncserver-x11[515,root]: Connections: connected:
10.1.1.155::35098 (TCP)
Mar 6 15:49:17 WeatherPi vncser
On Saturday, 6 March 2021 at 14:23:11 UTC+13 tke...@gmail.com wrote:
> Yes, you definitely have a connectivity problem that has nothing to do
> with WeeWX. There is an outside chance the problem is with your RPi. If you
> have an extra RPi around, try using it to connect through minicom.
>
> If nothing works, a call to Davis is in order.
>
> -tk
>
> On Fri, Mar 5, 2021 at 5:00 PM monmul wrote:
>
>>
>> So everything reseated and restarted..
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
So everything reseated and restarted...unplugged USB to ensure that the Pi was seeing the USB..used "screen /dev/ttyUSB0 19200" after shutting down weewxstill blank screen (after a number Enters) with no echo back to TEST and NVR On Friday, 5 March 2021 at 17:29:45 UTC+13 monmul wrote: > pi@WeatherPi:~ $ lsusb > Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash > drive > Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub > 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. SMC9514 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > pi@WeatherPi:~ $ > > Having pulled out the line from the Envoy, rebooted, and hit lsusb, by > elimination the "Future Technology" must be the one! > > On Friday, 5 March 2021 at 15:38:45 UTC+13 graha...@gmail.com wrote: > >> or just note which /dev/ttyUSB* comes and goes >> >> once identified i like to put in a udev rule to create a known device >> file such as /dev/vp2 >> >> > On 5 Mar 2021, at 12:33 pm, vince wrote: >> > >> > One good way to identify a USB device is to unplug it, plug it back in, >> and see what the 'dmesg' command reported. You'll tend to be able to figure >> out which USB port it connected to that way. >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/52535b0d-df10-4281-a5e8-420e8b84a701n%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ lsusb Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash drive Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub 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. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@WeatherPi:~ $ Having pulled out the line from the Envoy, rebooted, and hit lsusb, by elimination the "Future Technology" must be the one! On Friday, 5 March 2021 at 15:38:45 UTC+13 graha...@gmail.com wrote: > or just note which /dev/ttyUSB* comes and goes > > once identified i like to put in a udev rule to create a known device file > such as /dev/vp2 > > > On 5 Mar 2021, at 12:33 pm, vince wrote: > > > > One good way to identify a USB device is to unplug it, plug it back in, > and see what the 'dmesg' command reported. You'll tend to be able to figure > out which USB port it connected to that way. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f7d99875-d320-48d0-96bf-678f06efb18dn%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Not using serial...using USB. On Friday, 5 March 2021 at 10:34:32 UTC+13 monmul wrote: > pi@WeatherPi:~ $ lsusb > Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, > Ltd FT232 Serial (UART) IC > Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash > drive > Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub > 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. SMC9514 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > pi@WeatherPi:~ $ > > > On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote: > >> Well, if you're sure you have the right port (/dev/ttyUSB0), and you have >> correctly completed the test (a couple of enters, followed by ENTER, all >> caps) and you got nothing back, then that is as definitive a test that I >> know of that you have a connectivity problem. >> >> Do you have a USB version of the logger? Or, if you have a serial >> version, are you using a serial-to-usb converter? Either way, make sure >> your computer is recognizing the USB connection to the logger: >> >> *lsusb* >> >> If you have a serial version of the logger (very rare these days), then >> what serial port are you plugging it into? >> >> >> >> On Thu, Mar 4, 2021 at 11:59 AM monmul wrote: >> >>> Yes, apologieswas in a rush typing and did not review."new >>> envoy"..it should be...and "initiation" is the other typo! >>> >>> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote: >>> >>>> ‘new’ envoy? >>>> >>>> Gary >>>> >>>> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote: >>>> >>>>> What do you mean by "net Envoy"? If you are using a serial port like >>>>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a >>>>> network connector. Or, are you using an IP logger? >>>>> >>>>> On Wed, Mar 3, 2021 at 8:38 PM monmul wrote: >>>>> >>>>>> I have not had time to do the reseating yethopefully later today. >>>>>> One thing strikes me (probably becuase it has been so long since I set >>>>>> it >>>>>> up) I just switched envoys, how does the net envoy know what to do...I >>>>>> have >>>>>> not gone to any itiation or set up page etcI just plugged and >>>>>> supposed >>>>>> it would go. Am I missing something? >>>>>> >>>>>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote: >>>>>> >>>>>>> Thank you, I will give that a try! >>>>>>> >>>>>>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote: >>>>>>> >>>>>>>> Reseat means to remove the logger from the Envoy and then reinstall >>>>>>>> the logger in the Envoy. Sometimes you can get a dodgy connection >>>>>>>> between >>>>>>>> pins on the logger and the socket in the Envoy (or console) and >>>>>>>> remaking >>>>>>>> the connection by reseating can sometimes fix this. >>>>>>>> >>>>>>>> Gary >>>>>>>> >>>>>>>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote: >>>>>>>> >>>>>>>>> Sorry, I don't quite understand what you mean by "reseat"? >>>>>>>>> >>>>>>>>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> You can try reseating the logger. >>>>>>>>>> >>>>>>>>>> On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: >>>>>>>>>> >>>>>>>>>>> Neither TEST nor NVER returns anythingso, I guess I have a >>>>>>>>>>> connectivity problemwhich seems strange as I did a straight >>>>>>>>>>> swap out >>>>>>>>>>> of the Envoys! >>>>>>>>>>> >>>>>>>>>>> On Sunda
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ lsusb Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash drive Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub 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. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@WeatherPi:~ $ On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote: > Well, if you're sure you have the right port (/dev/ttyUSB0), and you have > correctly completed the test (a couple of enters, followed by ENTER, all > caps) and you got nothing back, then that is as definitive a test that I > know of that you have a connectivity problem. > > Do you have a USB version of the logger? Or, if you have a serial version, > are you using a serial-to-usb converter? Either way, make sure your > computer is recognizing the USB connection to the logger: > > *lsusb* > > If you have a serial version of the logger (very rare these days), then > what serial port are you plugging it into? > > > > On Thu, Mar 4, 2021 at 11:59 AM monmul wrote: > >> Yes, apologieswas in a rush typing and did not review."new >> envoy"..it should be...and "initiation" is the other typo! >> >> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote: >> >>> ‘new’ envoy? >>> >>> Gary >>> >>> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote: >>> >>>> What do you mean by "net Envoy"? If you are using a serial port like >>>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a >>>> network connector. Or, are you using an IP logger? >>>> >>>> On Wed, Mar 3, 2021 at 8:38 PM monmul wrote: >>>> >>>>> I have not had time to do the reseating yethopefully later today. >>>>> One thing strikes me (probably becuase it has been so long since I set it >>>>> up) I just switched envoys, how does the net envoy know what to do...I >>>>> have >>>>> not gone to any itiation or set up page etcI just plugged and >>>>> supposed >>>>> it would go. Am I missing something? >>>>> >>>>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote: >>>>> >>>>>> Thank you, I will give that a try! >>>>>> >>>>>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote: >>>>>> >>>>>>> Reseat means to remove the logger from the Envoy and then reinstall >>>>>>> the logger in the Envoy. Sometimes you can get a dodgy connection >>>>>>> between >>>>>>> pins on the logger and the socket in the Envoy (or console) and >>>>>>> remaking >>>>>>> the connection by reseating can sometimes fix this. >>>>>>> >>>>>>> Gary >>>>>>> >>>>>>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote: >>>>>>> >>>>>>>> Sorry, I don't quite understand what you mean by "reseat"? >>>>>>>> >>>>>>>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com >>>>>>>> wrote: >>>>>>>> >>>>>>>>> You can try reseating the logger. >>>>>>>>> >>>>>>>>> On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: >>>>>>>>> >>>>>>>>>> Neither TEST nor NVER returns anythingso, I guess I have a >>>>>>>>>> connectivity problemwhich seems strange as I did a straight >>>>>>>>>> swap out >>>>>>>>>> of the Envoys! >>>>>>>>>> >>>>>>>>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> If the cursor went down the screen, then the console is sending >>>>>>>>>>> something back. Make sure you press a few times, then >>>>>>>>>>> "TEST", all >>>>>>>>>>> in capital letters. >>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Yes, apologieswas in a rush typing and did not review."new envoy"..it should be...and "initiation" is the other typo! On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote: > ‘new’ envoy? > > Gary > > On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote: > >> What do you mean by "net Envoy"? If you are using a serial port like >> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a >> network connector. Or, are you using an IP logger? >> >> On Wed, Mar 3, 2021 at 8:38 PM monmul wrote: >> >>> I have not had time to do the reseating yethopefully later today. >>> One thing strikes me (probably becuase it has been so long since I set it >>> up) I just switched envoys, how does the net envoy know what to do...I have >>> not gone to any itiation or set up page etcI just plugged and supposed >>> it would go. Am I missing something? >>> >>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote: >>> >>>> Thank you, I will give that a try! >>>> >>>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote: >>>> >>>>> Reseat means to remove the logger from the Envoy and then reinstall >>>>> the logger in the Envoy. Sometimes you can get a dodgy connection between >>>>> pins on the logger and the socket in the Envoy (or console) and remaking >>>>> the connection by reseating can sometimes fix this. >>>>> >>>>> Gary >>>>> >>>>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote: >>>>> >>>>>> Sorry, I don't quite understand what you mean by "reseat"? >>>>>> >>>>>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> You can try reseating the logger. >>>>>>> >>>>>>> On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: >>>>>>> >>>>>>>> Neither TEST nor NVER returns anythingso, I guess I have a >>>>>>>> connectivity problemwhich seems strange as I did a straight swap >>>>>>>> out >>>>>>>> of the Envoys! >>>>>>>> >>>>>>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com >>>>>>>> wrote: >>>>>>>> >>>>>>>>> If the cursor went down the screen, then the console is sending >>>>>>>>> something back. Make sure you press a few times, then "TEST", >>>>>>>>> all >>>>>>>>> in capital letters. >>>>>>>>> >>>>>>>>> You can also type "NVER". Again, all in capital letters. This will >>>>>>>>> return the firmware version number. >>>>>>>>> >>>>>>>>> If neither of those work, then you have a connectivity problem. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sat, Feb 27, 2021 at 3:54 PM monmul wrote: >>>>>>>>> >>>>>>>>>> The screen shows blank when I get to the point above.after >>>>>>>>>> hitting enter a few times, it just sends the cursor down the >>>>>>>>>> screen..I >>>>>>>>>> tried typing TEST but no response...just a dark screen in the CL >>>>>>>>>> window. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: >>>>>>>>>> >>>>>>>>>>> That’s a better start, did you hit enter a few times and then >>>>>>>>>>> send TEST as per the wiki article >>>>>>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? >>>>>>>>>>> >>>>>>>>>>> You should get a response from the Envoy. >>>>>>>>>>> >>>>>>>>>>> Gary >>>>>>>>>>> >>>>>>>>>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
After reseating, I get the exact same as before. pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo killall screen screen: no process found pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 Welcome to minicom 2.7 OPTIONS: I18n Compiled on Apr 22 2017, 09:14:19. Port /dev/ttyUSB0, 18:49:36 Press CTRL-A Z for help on special keys On Thursday, 4 March 2021 at 17:38:18 UTC+13 monmul wrote: > I have not had time to do the reseating yethopefully later today. One > thing strikes me (probably becuase it has been so long since I set it up) I > just switched envoys, how does the net envoy know what to do...I have not > gone to any itiation or set up page etcI just plugged and supposed it > would go. Am I missing something? > > On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote: > >> Thank you, I will give that a try! >> >> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote: >> >>> Reseat means to remove the logger from the Envoy and then reinstall the >>> logger in the Envoy. Sometimes you can get a dodgy connection between pins >>> on the logger and the socket in the Envoy (or console) and remaking the >>> connection by reseating can sometimes fix this. >>> >>> Gary >>> >>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote: >>> >>>> Sorry, I don't quite understand what you mean by "reseat"? >>>> >>>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote: >>>> >>>>> You can try reseating the logger. >>>>> >>>>> On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: >>>>> >>>>>> Neither TEST nor NVER returns anythingso, I guess I have a >>>>>> connectivity problemwhich seems strange as I did a straight swap >>>>>> out >>>>>> of the Envoys! >>>>>> >>>>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> If the cursor went down the screen, then the console is sending >>>>>>> something back. Make sure you press a few times, then "TEST", >>>>>>> all >>>>>>> in capital letters. >>>>>>> >>>>>>> You can also type "NVER". Again, all in capital letters. This will >>>>>>> return the firmware version number. >>>>>>> >>>>>>> If neither of those work, then you have a connectivity problem. >>>>>>> >>>>>>> >>>>>>> On Sat, Feb 27, 2021 at 3:54 PM monmul wrote: >>>>>>> >>>>>>>> The screen shows blank when I get to the point above.after >>>>>>>> hitting enter a few times, it just sends the cursor down the >>>>>>>> screen..I >>>>>>>> tried typing TEST but no response...just a dark screen in the CL >>>>>>>> window. >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: >>>>>>>> >>>>>>>>> That’s a better start, did you hit enter a few times and then send >>>>>>>>> TEST as per the wiki article >>>>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? >>>>>>>>> >>>>>>>>> You should get a response from the Envoy. >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote: >>>>>>>>> >>>>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>>>>>> pi@WeatherPi:~ $ sudo killall screen >>>>>>>>>> pi@WeatherPi:~ $ sud
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
I have not had time to do the reseating yethopefully later today. One thing strikes me (probably becuase it has been so long since I set it up) I just switched envoys, how does the net envoy know what to do...I have not gone to any itiation or set up page etcI just plugged and supposed it would go. Am I missing something? On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote: > Thank you, I will give that a try! > > On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote: > >> Reseat means to remove the logger from the Envoy and then reinstall the >> logger in the Envoy. Sometimes you can get a dodgy connection between pins >> on the logger and the socket in the Envoy (or console) and remaking the >> connection by reseating can sometimes fix this. >> >> Gary >> >> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote: >> >>> Sorry, I don't quite understand what you mean by "reseat"? >>> >>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote: >>> >>>> You can try reseating the logger. >>>> >>>> On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: >>>> >>>>> Neither TEST nor NVER returns anythingso, I guess I have a >>>>> connectivity problemwhich seems strange as I did a straight swap out >>>>> of the Envoys! >>>>> >>>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote: >>>>> >>>>>> If the cursor went down the screen, then the console is sending >>>>>> something back. Make sure you press a few times, then "TEST", >>>>>> all >>>>>> in capital letters. >>>>>> >>>>>> You can also type "NVER". Again, all in capital letters. This will >>>>>> return the firmware version number. >>>>>> >>>>>> If neither of those work, then you have a connectivity problem. >>>>>> >>>>>> >>>>>> On Sat, Feb 27, 2021 at 3:54 PM monmul wrote: >>>>>> >>>>>>> The screen shows blank when I get to the point above.after >>>>>>> hitting enter a few times, it just sends the cursor down the >>>>>>> screen......I >>>>>>> tried typing TEST but no response...just a dark screen in the CL window. >>>>>>> >>>>>>> >>>>>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: >>>>>>> >>>>>>>> That’s a better start, did you hit enter a few times and then send >>>>>>>> TEST as per the wiki article >>>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? >>>>>>>> >>>>>>>> You should get a response from the Envoy. >>>>>>>> >>>>>>>> Gary >>>>>>>> >>>>>>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote: >>>>>>>> >>>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>>>>> pi@WeatherPi:~ $ sudo killall screen >>>>>>>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>>>>>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>>>>>>> /run/user/1000/gvfs >>>>>>>>> Output information may be incomplete. >>>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>>> >>>>>>>>> >>>>>>>>> Welcome to minicom 2.7 >>>>>>>>> >>>>>>>>> OPTIONS: I18n >>>>>>>>> Compiled on Apr 22 2017, 09:14:19. >>>>>>>>> Port /dev/ttyUSB0, 11:00:42 >>>>>>>>> >>>>>>>>> Press CTRL-A Z for help on special keys >>>>>>>>> >>>>>>>>> >>>>>>>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com >>>>>&g
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Thank you, I will give that a try! On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote: > Reseat means to remove the logger from the Envoy and then reinstall the > logger in the Envoy. Sometimes you can get a dodgy connection between pins > on the logger and the socket in the Envoy (or console) and remaking the > connection by reseating can sometimes fix this. > > Gary > > On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote: > >> Sorry, I don't quite understand what you mean by "reseat"? >> >> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote: >> >>> You can try reseating the logger. >>> >>> On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: >>> >>>> Neither TEST nor NVER returns anythingso, I guess I have a >>>> connectivity problemwhich seems strange as I did a straight swap out >>>> of the Envoys! >>>> >>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote: >>>> >>>>> If the cursor went down the screen, then the console is sending >>>>> something back. Make sure you press a few times, then "TEST", all >>>>> in capital letters. >>>>> >>>>> You can also type "NVER". Again, all in capital letters. This will >>>>> return the firmware version number. >>>>> >>>>> If neither of those work, then you have a connectivity problem. >>>>> >>>>> >>>>> On Sat, Feb 27, 2021 at 3:54 PM monmul wrote: >>>>> >>>>>> The screen shows blank when I get to the point above.after >>>>>> hitting enter a few times, it just sends the cursor down the >>>>>> screen..I >>>>>> tried typing TEST but no response...just a dark screen in the CL window. >>>>>> >>>>>> >>>>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: >>>>>> >>>>>>> That’s a better start, did you hit enter a few times and then send >>>>>>> TEST as per the wiki article >>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? >>>>>>> >>>>>>> You should get a response from the Envoy. >>>>>>> >>>>>>> Gary >>>>>>> >>>>>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote: >>>>>>> >>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>>>> pi@WeatherPi:~ $ sudo killall screen >>>>>>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>>>>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>>>>>> /run/user/1000/gvfs >>>>>>>> Output information may be incomplete. >>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>> >>>>>>>> >>>>>>>> Welcome to minicom 2.7 >>>>>>>> >>>>>>>> OPTIONS: I18n >>>>>>>> Compiled on Apr 22 2017, 09:14:19. >>>>>>>> Port /dev/ttyUSB0, 11:00:42 >>>>>>>> >>>>>>>> Press CTRL-A Z for help on special keys >>>>>>>> >>>>>>>> >>>>>>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Monmul, we have not definitively heard whether or not you are able >>>>>>>>> to do the test listed under *Establishing connectivity >>>>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>* >>>>>>>>> in >>>>>>>>> the Wiki.That is an essential first step. >>>>>>>>> >>>>>>>>> Use either screen or minicom. You may have to preface the command >>>>>>>>> with 'sudo'. For example, >>>>>&
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Sorry, I don't quite understand what you mean by "reseat"? On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote: > You can try reseating the logger. > > On Sat, Feb 27, 2021 at 5:16 PM monmul wrote: > >> Neither TEST nor NVER returns anythingso, I guess I have a >> connectivity problemwhich seems strange as I did a straight swap out >> of the Envoys! >> >> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote: >> >>> If the cursor went down the screen, then the console is sending >>> something back. Make sure you press a few times, then "TEST", all >>> in capital letters. >>> >>> You can also type "NVER". Again, all in capital letters. This will >>> return the firmware version number. >>> >>> If neither of those work, then you have a connectivity problem. >>> >>> >>> On Sat, Feb 27, 2021 at 3:54 PM monmul wrote: >>> >>>> The screen shows blank when I get to the point above.after hitting >>>> enter a few times, it just sends the cursor down the screen..I tried >>>> typing TEST but no response...just a dark screen in the CL window. >>>> >>>> >>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: >>>> >>>>> That’s a better start, did you hit enter a few times and then send >>>>> TEST as per the wiki article >>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? >>>>> >>>>> You should get a response from the Envoy. >>>>> >>>>> Gary >>>>> >>>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote: >>>>> >>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>> pi@WeatherPi:~ $ sudo killall screen >>>>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>>>> /run/user/1000/gvfs >>>>>> Output information may be incomplete. >>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>> >>>>>> >>>>>> Welcome to minicom 2.7 >>>>>> >>>>>> OPTIONS: I18n >>>>>> Compiled on Apr 22 2017, 09:14:19. >>>>>> Port /dev/ttyUSB0, 11:00:42 >>>>>> >>>>>> Press CTRL-A Z for help on special keys >>>>>> >>>>>> >>>>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Monmul, we have not definitively heard whether or not you are able >>>>>>> to do the test listed under *Establishing connectivity >>>>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>* >>>>>>> in >>>>>>> the Wiki.That is an essential first step. >>>>>>> >>>>>>> Use either screen or minicom. You may have to preface the command >>>>>>> with 'sudo'. For example, >>>>>>> >>>>>>> >>>>>>> *sudo screen /dev/ttyUSB0 19200* >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Thu, Feb 25, 2021 at 7:34 PM monmul wrote: >>>>>>> >>>>>>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather >>>>>>>> system... >>>>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing >>>>>>>> weewx version 4.4.0 >>>>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python >>>>>>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >>>>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform >>>>>>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >>>>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is >>>>>>>> 'en_NZ.UTF
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
Neither TEST nor NVER returns anythingso, I guess I have a connectivity problemwhich seems strange as I did a straight swap out of the Envoys! On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote: > If the cursor went down the screen, then the console is sending something > back. Make sure you press a few times, then "TEST", all in capital > letters. > > You can also type "NVER". Again, all in capital letters. This will return > the firmware version number. > > If neither of those work, then you have a connectivity problem. > > > On Sat, Feb 27, 2021 at 3:54 PM monmul wrote: > >> The screen shows blank when I get to the point above.after hitting >> enter a few times, it just sends the cursor down the screen..I tried >> typing TEST but no response...just a dark screen in the CL window. >> >> >> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: >> >>> That’s a better start, did you hit enter a few times and then send TEST >>> as per the wiki article >>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? >>> >>> You should get a response from the Envoy. >>> >>> Gary >>> >>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote: >>> >>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ sudo killall screen >>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>> /run/user/1000/gvfs >>>> Output information may be incomplete. >>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>> >>>> >>>> Welcome to minicom 2.7 >>>> >>>> OPTIONS: I18n >>>> Compiled on Apr 22 2017, 09:14:19. >>>> Port /dev/ttyUSB0, 11:00:42 >>>> >>>> Press CTRL-A Z for help on special keys >>>> >>>> >>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com >>>> wrote: >>>> >>>>> Monmul, we have not definitively heard whether or not you are able to >>>>> do the test listed under *Establishing connectivity >>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>* >>>>> in >>>>> the Wiki.That is an essential first step. >>>>> >>>>> Use either screen or minicom. You may have to preface the command >>>>> with 'sudo'. For example, >>>>> >>>>> >>>>> *sudo screen /dev/ttyUSB0 19200* >>>>> >>>>> -tk >>>>> >>>>> On Thu, Feb 25, 2021 at 7:34 PM monmul wrote: >>>>> >>>>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather >>>>>> system... >>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing >>>>>> weewx version 4.4.0 >>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python >>>>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform >>>>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is >>>>>> 'en_NZ.UTF-8' >>>>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is >>>>>> /var/run/weewx.pid >>>>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather >>>>>> system: weewx. >>>>>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather >>>>>> system. >>>>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using >>>>>> configuration file /etc/weewx/weewx.conf >>>>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1 >>>>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing >>>>>> engine >>>>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading >>>>>> station type Vantage (weewx.drivers.vantage) >>&
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
The screen shows blank when I get to the point above.after hitting enter a few times, it just sends the cursor down the screen..I tried typing TEST but no response...just a dark screen in the CL window. On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote: > That’s a better start, did you hit enter a few times and then send TEST as > per the wiki article > <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>? > > You should get a response from the Envoy. > > Gary > > On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote: > >> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >> minicom: cannot open /dev/ttyUSB0: Device or resource busy >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ sudo killall screen >> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >> >> >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 11:00:42 >> >> Press CTRL-A Z for help on special keys >> >> >> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote: >> >>> Monmul, we have not definitively heard whether or not you are able to do >>> the test listed under *Establishing connectivity >>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>* >>> in >>> the Wiki.That is an essential first step. >>> >>> Use either screen or minicom. You may have to preface the command with ' >>> sudo'. For example, >>> >>> >>> *sudo screen /dev/ttyUSB0 19200* >>> >>> -tk >>> >>> On Thu, Feb 25, 2021 at 7:34 PM monmul wrote: >>> >>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather >>>> system... >>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing >>>> weewx version 4.4.0 >>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python >>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform >>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is >>>> 'en_NZ.UTF-8' >>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is >>>> /var/run/weewx.pid >>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: >>>> weewx. >>>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system. >>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using >>>> configuration file /etc/weewx/weewx.conf >>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1 >>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing >>>> engine >>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading >>>> station type Vantage (weewx.drivers.vantage) >>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Driver version is 3.2.1 >>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Option loop_request=1 >>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00 >>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >>>> fe80::724f:57ff:feb7:82a1 >>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >>>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Retry #0 failed >>>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Retry #1 failed >>>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Retry #2 failed >>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >>>> fe80::724f:57ff:feb7:82a1 >>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >>>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >>>> Retry #3 failed >>>&g
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo killall screen pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 Welcome to minicom 2.7 OPTIONS: I18n Compiled on Apr 22 2017, 09:14:19. Port /dev/ttyUSB0, 11:00:42 Press CTRL-A Z for help on special keys On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote: > Monmul, we have not definitively heard whether or not you are able to do > the test listed under *Establishing connectivity > <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#establishing-connectivity>* > in > the Wiki.That is an essential first step. > > Use either screen or minicom. You may have to preface the command with ' > sudo'. For example, > > > *sudo screen /dev/ttyUSB0 19200* > > -tk > > On Thu, Feb 25, 2021 at 7:34 PM monmul wrote: > >> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather >> system... >> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx >> version 4.4.0 >> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 2.7.13 >> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform >> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is >> 'en_NZ.UTF-8' >> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is >> /var/run/weewx.pid >> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: >> weewx. >> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system. >> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using configuration >> file /etc/weewx/weewx.conf >> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1 >> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing engine >> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading station >> type Vantage (weewx.drivers.vantage) >> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >> Driver version is 3.2.1 >> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >> Option loop_request=1 >> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: >> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00 >> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry >> #0 failed >> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry >> #1 failed >> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry >> #2 failed >> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry >> #3 failed >> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: >> Unable to wake up console >> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of >> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>) >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> Traceback (most recent call last): >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> self.console = loader_function(config_dict, self) >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> return VantageService(engine, config_dict) >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__ >> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >> Vantage.__init__(self, **config_dict[
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
7ff:feb7:82a1 Feb 26 16:32:15 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease On Friday, 26 February 2021 at 11:19:41 UTC+13 vince wrote: > So go ahead and restart it now. > > On Thursday, February 25, 2021 at 1:02:41 PM UTC-8 monmul wrote: > >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ sudo killall screen >> screen: no process found >> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> pi@WeatherPi:~ $ ps -ef | grep -e weewxd -e screen >> pi3809 11222 0 10:01 pts/100:00:00 grep --color=auto -e >> weewxd -e screen >> pi@WeatherPi:~ $ >> >> On Thursday, 25 February 2021 at 21:57:53 UTC+13 graha...@gmail.com >> wrote: >> >>> vnc makes no relevant difference. >>> command = ‘screen’ below shows program ‘screen’ has a ‘pi’ user process >>> open on /dev/ttyUSB0 at the moment. not weewxd. probably left over from >>> earlier troubleshooting. >>> kill it with “sudo killall screen”. >>> check if any weewxd’s or screen’s hanging around with “ps -ef | grep -e >>> weewxd -e screen”. kill them if you find any. >>> you should now be back to a clean state with /devttyUSB0 ready for >>> opening. do “sudo lsof /dev/ttyUSB0” to be sure >>> >>> On 25 Feb 2021, at 5:24 pm, gjr80 wrote: >>> >>> I don't know, I'm a SSH only person, I am getting out of my depth now. >>> >>> Gary >>> >>> On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote: >>> >>>> I am using VNC Viewer (and always have) rather than SSHnot sure if >>>> that makes any difference? >>>> >>>> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote: >>>> >>>>> Hmm, different to my Davis on my RPi which shows weewxd rather than >>>>> screen. I will have to defer to Tom or someone who knows about screen. >>>>> >>>>> Gary >>>>> >>>>> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote: >>>>> >>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>>>> /run/user/1000/gvfs >>>>>> Output information may be incomplete. >>>>>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >>>>>> screen 16582 pi6u CHR 188,0 0t0 20196 /dev/ttyUSB0 >>>>>> pi@WeatherPi:~ $ >>>>>> >>>>>> >>> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/73f28622-be3d-4e50-b6fa-644811a22b2bn%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo killall screen screen: no process found pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. pi@WeatherPi:~ $ ps -ef | grep -e weewxd -e screen pi3809 11222 0 10:01 pts/100:00:00 grep --color=auto -e weewxd -e screen pi@WeatherPi:~ $ On Thursday, 25 February 2021 at 21:57:53 UTC+13 graha...@gmail.com wrote: > vnc makes no relevant difference. > command = ‘screen’ below shows program ‘screen’ has a ‘pi’ user process > open on /dev/ttyUSB0 at the moment. not weewxd. probably left over from > earlier troubleshooting. > kill it with “sudo killall screen”. > check if any weewxd’s or screen’s hanging around with “ps -ef | grep -e > weewxd -e screen”. kill them if you find any. > you should now be back to a clean state with /devttyUSB0 ready for > opening. do “sudo lsof /dev/ttyUSB0” to be sure > > On 25 Feb 2021, at 5:24 pm, gjr80 wrote: > > I don't know, I'm a SSH only person, I am getting out of my depth now. > > Gary > > On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote: > >> I am using VNC Viewer (and always have) rather than SSHnot sure if >> that makes any difference? >> >> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote: >> >>> Hmm, different to my Davis on my RPi which shows weewxd rather than >>> screen. I will have to defer to Tom or someone who knows about screen. >>> >>> Gary >>> >>> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote: >>> >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >>>> /run/user/1000/gvfs >>>> Output information may be incomplete. >>>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >>>> screen 16582 pi6u CHR 188,0 0t0 20196 /dev/ttyUSB0 >>>> pi@WeatherPi:~ $ >>>> >>>> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/0cb90854-d683-4fb3-8ac3-aa8b1d48fb20n%40googlegroups.com.
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
I am using VNC Viewer (and always have) rather than SSHnot sure if that makes any difference? On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote: > Hmm, different to my Davis on my RPi which shows weewxd rather than > screen. I will have to defer to Tom or someone who knows about screen. > > Gary > > On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote: > >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> screen 16582 pi6u CHR 188,0 0t0 20196 /dev/ttyUSB0 >> pi@WeatherPi:~ $ >> >> >> >> On Thursday, 25 February 2021 at 17:46:35 UTC+13 gjr80 wrote: >> >>> I thought it was installed by default on RPi OS but seems lt it is not - >>> it works on my RPi, I must have installed it manually. Try: >>> >>> $ sudo apt update >>> $ sudo apt install lsof >>> >>> then try running lsof. >>> >>> Gary >>> >>> On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote: >>> >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >>>> bash: lsof: command not found >>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >>>> bash: lsof: command not found >>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >>>> sudo: lsof: command not found >>>> pi@WeatherPi:~ $ >>>> >>>> >>>> >>>> On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote: >>>> >>>>> Try prefixing lsof with sudo. >>>>> >>>>> Gary >>>>> >>>>> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote: >>>>> >>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >>>>>> bash: lsof: command not found >>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >>>>>> bash: lsof: command not found >>>>>> pi@WeatherPi:~ $ >>>>>> >>>>>> >>>>>> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Make sure you stop weewx first before trying minicom. There cannot >>>>>>> be anything else using the port. To see what devices are using a port: >>>>>>> >>>>>>> *lsof /dev/ttyUSB0* >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 23, 2021 at 9:19 PM monmul wrote: >>>>>>> >>>>>>>> No change in USB port. >>>>>>>> >>>>>>>> pi@WeatherPi:~ $ >>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>>>> pi@WeatherPi:~ $ >>>>>>>> pi@WeatherPi:~ $ >>>>>>>> pi@WeatherPi:~ $ >>>>>>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >>>>>>>> >>>>>>>> [screen is terminating] >>>>>>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME screen 16582 pi6u CHR 188,0 0t0 20196 /dev/ttyUSB0 pi@WeatherPi:~ $ On Thursday, 25 February 2021 at 17:46:35 UTC+13 gjr80 wrote: > I thought it was installed by default on RPi OS but seems lt it is not - > it works on my RPi, I must have installed it manually. Try: > > $ sudo apt update > $ sudo apt install lsof > > then try running lsof. > > Gary > > On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote: > >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >> bash: lsof: command not found >> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >> minicom: cannot open /dev/ttyUSB0: Device or resource busy >> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >> bash: lsof: command not found >> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 >> sudo: lsof: command not found >> pi@WeatherPi:~ $ >> >> >> >> On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote: >> >>> Try prefixing lsof with sudo. >>> >>> Gary >>> >>> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote: >>> >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >>>> bash: lsof: command not found >>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >>>> bash: lsof: command not found >>>> pi@WeatherPi:~ $ >>>> >>>> >>>> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com >>>> wrote: >>>> >>>>> Make sure you stop weewx first before trying minicom. There cannot be >>>>> anything else using the port. To see what devices are using a port: >>>>> >>>>> *lsof /dev/ttyUSB0* >>>>> >>>>> >>>>> >>>>> On Tue, Feb 23, 2021 at 9:19 PM monmul wrote: >>>>> >>>>>> No change in USB port. >>>>>> >>>>>> pi@WeatherPi:~ $ >>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>>>> pi@WeatherPi:~ $ >>>>>> pi@WeatherPi:~ $ >>>>>> pi@WeatherPi:~ $ >>>>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >>>>>> >>>>>> [screen is terminating] >>>>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> [screen is terminating] >>>>>> pi@WeatherPi:~ $ TEST >>>>>> bash: TEST: command not found >>>>>> pi@WeatherPi:~ $ >>>>>> >>>>>> >>>>>> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote: >>>>>> >>>>>>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but >>>>>>> I am told they behave just like a console. First thing I would do is >>>>>>> test >>>>>>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on >>>>>>> a >>>>>>> different USB port? Not sure if you remember the Establishing >>>>>>> connectivity >
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ lsof /dev/ttyUSB0 bash: lsof: command not found pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ lsof /dev/ttyUSB0 bash: lsof: command not found pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0 sudo: lsof: command not found pi@WeatherPi:~ $ On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote: > Try prefixing lsof with sudo. > > Gary > > On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote: > >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >> bash: lsof: command not found >> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >> minicom: cannot open /dev/ttyUSB0: Device or resource busy >> pi@WeatherPi:~ $ lsof /dev/ttyUSB0 >> bash: lsof: command not found >> pi@WeatherPi:~ $ >> >> >> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com wrote: >> >>> Make sure you stop weewx first before trying minicom. There cannot be >>> anything else using the port. To see what devices are using a port: >>> >>> *lsof /dev/ttyUSB0* >>> >>> >>> >>> On Tue, Feb 23, 2021 at 9:19 PM monmul wrote: >>> >>>> No change in USB port. >>>> >>>> pi@WeatherPi:~ $ >>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >>>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy >>>> pi@WeatherPi:~ $ >>>> pi@WeatherPi:~ $ >>>> pi@WeatherPi:~ $ >>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >>>> >>>> [screen is terminating] >>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> [screen is terminating] >>>> pi@WeatherPi:~ $ TEST >>>> bash: TEST: command not found >>>> pi@WeatherPi:~ $ >>>> >>>> >>>> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote: >>>> >>>>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I >>>>> am told they behave just like a console. First thing I would do is test >>>>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a >>>>> different USB port? Not sure if you remember the Establishing >>>>> connectivity >>>>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> >>>>> >>>>> testing Tom got you to work through a couple of years back, but that is a >>>>> good place to start. The instructions are now in the wiki rather than the >>>>> User Guide but the link I have provided should work. >>>>> >>>>> Gary >>>>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote: >>>>> >>>>>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather >>>>>> system... >>>>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing >>>>>> weewx version 4.4.0 >>>>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python >>>>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >>>>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform >>>>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >>>>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is >>>>>> 'en_NZ.UTF-8' >>>>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is >>>>>> /var/run/weewx.pid >>>>>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather >>>>>> system: weewx. >>>>>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather >>&
Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ lsof /dev/ttyUSB0 bash: lsof: command not found pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ lsof /dev/ttyUSB0 bash: lsof: command not found pi@WeatherPi:~ $ On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com wrote: > Make sure you stop weewx first before trying minicom. There cannot be > anything else using the port. To see what devices are using a port: > > *lsof /dev/ttyUSB0* > > > > On Tue, Feb 23, 2021 at 9:19 PM monmul wrote: > >> No change in USB port. >> >> pi@WeatherPi:~ $ >> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >> minicom: cannot open /dev/ttyUSB0: Device or resource busy >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 >> minicom: cannot open /dev/ttyUSB0: Device or resource busy >> pi@WeatherPi:~ $ >> pi@WeatherPi:~ $ >> pi@WeatherPi:~ $ >> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >> >> [screen is terminating] >> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> [screen is terminating] >> pi@WeatherPi:~ $ TEST >> bash: TEST: command not found >> pi@WeatherPi:~ $ >> >> >> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote: >> >>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am >>> told they behave just like a console. First thing I would do is test >>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a >>> different USB port? Not sure if you remember the Establishing >>> connectivity >>> <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> >>> >>> testing Tom got you to work through a couple of years back, but that is a >>> good place to start. The instructions are now in the wiki rather than the >>> User Guide but the link I have provided should work. >>> >>> Gary >>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote: >>> >>>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather >>>> system... >>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing >>>> weewx version 4.4.0 >>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python >>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform >>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is >>>> 'en_NZ.UTF-8' >>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is >>>> /var/run/weewx.pid >>>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: >>>> weewx. >>>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system. >>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using >>>> configuration file /etc/weewx/weewx.conf >>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1 >>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing >>>> engine >>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading >>>> station type Vantage (weewx.drivers.vantage) >>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >>>> Driver version is 3.2.1 >>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >>>> Option loop_request=1 >>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00 >>>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >>>> fe80::724f:57ff:feb7:82a1 >>>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >>>> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >>>> Retry #0 failed >>>> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >>>> Retry #1 failed >>>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan
[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
No change in USB port. pi@WeatherPi:~ $ pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0 minicom: cannot open /dev/ttyUSB0: Device or resource busy pi@WeatherPi:~ $ pi@WeatherPi:~ $ pi@WeatherPi:~ $ pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 [screen is terminating] pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200 [screen is terminating] pi@WeatherPi:~ $ TEST bash: TEST: command not found pi@WeatherPi:~ $ On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote: > OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am > told they behave just like a console. First thing I would do is test > connectivity from your RPi to the Envoy. Any chance the Envoy is now on a > different USB port? Not sure if you remember the Establishing connectivity > <https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station> > > testing Tom got you to work through a couple of years back, but that is a > good place to start. The instructions are now in the wiki rather than the > User Guide but the link I have provided should work. > > Gary > On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote: > >> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather >> system... >> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx >> version 4.4.0 >> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 >> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516] >> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform >> Linux-4.19.66-v7+-armv7l-with-debian-9.13 >> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is >> 'en_NZ.UTF-8' >> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is >> /var/run/weewx.pid >> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: >> weewx. >> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system. >> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration >> file /etc/weewx/weewx.conf >> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1 >> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine >> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station >> type Vantage (weewx.drivers.vantage) >> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >> Driver version is 3.2.1 >> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >> Option loop_request=1 >> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: >> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00 >> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry >> #0 failed >> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry >> #1 failed >> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry >> #2 failed >> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry >> #3 failed >> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: >> Unable to wake up console >> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of >> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>) >> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: >> Traceback (most recent call last): >> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation >> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: >> self.console = loader_function(config_dict, self) >> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: >> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader >> Feb 22 22:39:19 WeatherPi weewx[
[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection
7ff:feb7:82a1 Feb 22 22:39:35 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease Feb 22 22:39:42 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Feb 22 22:39:42 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease Feb 22 22:39:50 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Feb 22 22:39:50 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease Feb 22 22:39:54 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Feb 22 22:39:54 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease Feb 22 22:40:00 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Feb 22 22:40:00 WeatherPi dhcpcd[372]: On Monday, 22 February 2021 at 21:43:34 UTC+13 gjr80 wrote: > Hi, > > We need to see the log from when you try starting WeeWX. Restart WeeWX and > let it run for an archive period or two, then goto the log and take an > extract from when WeeWX was restarted through until the two archive periods > have passed. Post the log back here without alteration. It’s important you > capture the full WeeWX startup. > > Gary > > On Monday, 22 February 2021 at 18:28:14 UTC+10 monmul wrote: > >> My Davis system has been running really well for the last 2 years. Needed >> no maintenance from me etc. Then the Envoy started tripping the circuit >> fuse (I think it was the Envoy rather than the power chord as I replaced >> with new Envoy and tripping stopped). I directly changed out the Envoy and >> rebooted the system expecting that all would be back to normal. Nope! >> >> No data appears to be coming through: >> >> Here are my diagnostic so far: >> >> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@WeatherPi:~ $ sudo weewxd >> pi@WeatherPi:~ $ ps -a >> PID TTY TIME CMD >> 15482 pts/100:00:00 ps >> pi@WeatherPi:~ $ kill -HUP 15482 >> bash: kill: (15482) - No such process >> pi@WeatherPi:~ $ tail -f /var/log/syslog >> Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease >> Feb 22 21:17:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from >> fe80::724f:57ff:feb7:82a1 >> >> Any guidance would be much appreciated. >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1b57e2d2-07ba-4c2a-9819-c8cb1c309addn%40googlegroups.com.
[weewx-user] Replaced Davis Envoy (tripping) and replaced with another - no connection
My Davis system has been running really well for the last 2 years. Needed no maintenance from me etc. Then the Envoy started tripping the circuit fuse (I think it was the Envoy rather than the power chord as I replaced with new Envoy and tripping stopped). I directly changed out the Envoy and rebooted the system expecting that all would be back to normal. Nope! No data appears to be coming through: Here are my diagnostic so far: pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@WeatherPi:~ $ sudo weewxd pi@WeatherPi:~ $ ps -a PID TTY TIME CMD 15482 pts/100:00:00 ps pi@WeatherPi:~ $ kill -HUP 15482 bash: kill: (15482) - No such process pi@WeatherPi:~ $ tail -f /var/log/syslog Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease Feb 22 21:17:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from fe80::724f:57ff:feb7:82a1 Any guidance would be much appreciated. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/acc70090-16ae-4423-80e9-e992d6bc1910n%40googlegroups.com.
[weewx-user] Re: Booting existing RPi3b from USB rather than SD
OK! Thank you for that! On Thursday, 9 April 2020 04:21:13 UTC+12, Rob Cranfill wrote: > > monmul, > > I’ll go ahead and answer your question even though I have nothing of great > value to add, because I happen to have done exactly this about 2 weeks ago. > > Yes, you can copy your SD card-based filesystem that is running weewx to > an SSD, as detailed in various places on the ‘net, and it works just fine. > Nothing special about weeex there. > > (I will add that I was unable to get this box, a “Raspberry Pi 3 Model B > Rev 1.2”, to boot entirely without an SD card, as is supposedly possible. > That is, I still have an SD card with the /boot partition on it, where > cmdline.txt then points to the /dev/sda1 (or whatever it was) for the rest > of the filesystem on the SSD. So in that sense I’m not doing a full USB > boot, but for the most part the filesystem is on SSD, not SD, so I’m happy. > Not sure why this is, but I’ve given up trying to fix it.) > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ec1d67b9-0734-4d12-8bc8-72db77d831fd%40googlegroups.com.
[weewx-user] Re: Booting existing RPi3b from USB rather than SD
Thank you for that Wes, very interesting, I had not come across that particular solution before! On Wednesday, 8 April 2020 04:38:39 UTC+12, Wes Witt wrote: > > for usb boot i recommend using an MSATA drive. 100% reliable, easy to > install. i'm using the following products: > > https://www.amazon.com/gp/product/B073CHHFMP/ > > https://www.amazon.com/gp/product/B07JPK75X4/ > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a8ae66ce-c3fa-4e5e-a593-d077758204a1%40googlegroups.com.
[weewx-user] Re: Booting existing RPi3b from USB rather than SD
Yes, I agree some parts of my question are answered (and I already know that partapologies if I did not make myself clear) by a Google search. I have no problem (I hope - fingers crossed) with the hardware part ...rather it is software part (and specifically the Weewx part) that concerns me. Can I just a) set up the USB boot b) copy and paste all the weewx folders from the SD card to the USB and, c) expect it all to run just as smoothly as before (at least in theory?). On Wednesday, 8 April 2020 04:04:00 UTC+12, vince wrote: > > On Tuesday, April 7, 2020 at 12:45:23 AM UTC-7, monmul wrote: >> >> I have weewx running, very happily and very successfully, (thanks to all >> here who helped me!) on a Rpi3B. The Pi is running Raspian and the standard >> SD card. Now, I got to thinking that this is probably not the most secure >> long tern setup - due to wear and tear on the SD card etc. So, I was >> thinking of setting up the Pi to run off a USB drive, I have all the Weewx >> folders backed up. What would be the most sensible way of transferring the >> whole boot and Home directory etc to the USB drive. As the system is >> running so well, I am a tad reluctant to go fiddling with it.but I know >> I will have to sooner or later. Your thoughts and suggestions would be >> appreciated. >> > > I would suggest asking Google. This is VERY well documented in dozens of > Howto documents online for many years, and has nothing specifically to do > with weewx. The procedures online work fine. I used to run my pi3+ that > way. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dfea8689-72b6-49d3-8e63-3e60084757ee%40googlegroups.com.
[weewx-user] Booting existing RPi3b from USB rather than SD
I have weewx running, very happily and very successfully, (thanks to all here who helped me!) on a Rpi3B. The Pi is running Raspian and the standard SD card. Now, I got to thinking that this is probably not the most secure long tern setup - due to wear and tear on the SD card etc. So, I was thinking of setting up the Pi to run off a USB drive, I have all the Weewx folders backed up. What would be the most sensible way of transferring the whole boot and Home directory etc to the USB drive. As the system is running so well, I am a tad reluctant to go fiddling with it.but I know I will have to sooner or later. Your thoughts and suggestions would be appreciated. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/32cfbe26-20e1-4b7e-9dfc-b12cf385be52%40googlegroups.com.
[weewx-user] Re: Temp showing N/A
Thank you Garyyour analysis was spot onas usual! On Sunday, 16 June 2019 14:10:21 UTC+12, gjr80 wrote: > > Hi, > > Mirabile Dictu! > > > Sort of guessed what that meant but had to look that one up to be sure! > > A few comments. Pressure comes from a sensor in the console as does inside > temperature so it is possible that if your ISS cannot be contacted by the > console WeeWX may still have communications with the console and pressure > and inside temperature may well still be recorded and posted to WU - > everything else will likely be None or N/A (or a WU default in the case of > WU). Since you mention a solar panel I presume you are referring to the > solar panel on your ISS meaning you have the wireless version. I don't have > one myself but I understand there was a super cap (high capacity capacitor) > in the ISS that stores solar energy to keep the ISS running overnight. If > that fails the ISS falls back to a non-rechargeable lithium battery. Could > be lack of sun or the super cap failing has meant it did not have enough > energy to keep your ISS running overnight and if your lithium battery > happens to be dead your ISS would die. It would then take until there was > enough solar power to get the ISS running (and maybe charging the super cap > to a certain extent) before things came back again. Given it's winter and > depending on your solar panel orientation/location/shielding, it could take > until around 11:30am before it had sufficient power to get the ISS running > again. Super caps do fail (Google replace Davis super cap) as do lithium > batteries. It could be a case of the super cap (largely) failing some time > ago and the lithium battery has been carrying the ISS overnight for a while > and now it is finally flat. > > If WeeWX was posting pressure data to WU overnight then WeeWX must have > had good comms with the console (which you would expect even if the ISS > failed). In the log extract you post there is a repeated and seemingly > continuous failure to obtain loop packets from the console: > > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console > successful > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console > successful > Jun 16 10:26:03 WeatherPi weewx[583]: vantage: LOOP try #1; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:03 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:08 WeatherPi weewx[583]: vantage: LOOP try #2; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:08 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:14 WeatherPi weewx[583]: vantage: LOOP try #3; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:14 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP try #4; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded > . > Jun 16 10:26:19 WeatherPi weewx[583]: engine: Main loop exiting. Shutting > engine down. > Jun 16 10:26:19 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS > thread. > Jun 16 10:26:19 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max > tries exceeded while getting LOOP data. > Jun 16 10:26:19 WeatherPi weewx[583]: Waiting 60 seconds then > retrying... > > Without a connection to the ISS there is no data to put in a loop packet > but I am not sure what the console does in this case, maybe if just refuses > to send loop packets but does send archive records (which would contain > pressure and inside temperature). Maybe those log entries are as a a result > of your efforts to get things working again in the morning and they did not > go on all night. > > I would be inclined to give it the benefit of the doubt for now, but I > expect it will happen again and it might then be a case of replacing one or > both of the super cap and lithium battery. If your ISS is easily accessible > it might be worth a look inside for any signs of leakage or bulging of the > super cap. > > Gary > > > On Sunday, 1
[weewx-user] Re: Temp showing N/A
Oh! Mirabile Dictu!...it has started recording temp again.I am
wondering if the battery has run out and when the sun started hitting the
solar panel of the weather station, it started recording againbut why
would the pressure have continued recordinghmmm! more mysteries!
On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote:
>
> Around midnight last night - after months of operating properly my ststem
> started recording N/A for temperature. I have tried dumping memory etc and
> restartedit has restarted but the problem is the same. Here is the log.
> What has happened and how do I fix it please.
>
> base 'weewx.sdb'
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
> summaries
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdArchive
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
> not requested.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
> station IOTAGOQU2 will be posted
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
> enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
> 3.9.1
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
> (positive is fast)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
> since 2019-06-16 10:10:00 NZST (1560636600)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
> starting index= 0
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:52
[weewx-user] Re: Temp showing N/A
I notice the signal quality went from 100 to 0 at midnight also!!the
Barometer is still reading as normal and posting to the template!
On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote:
>
> Around midnight last night - after months of operating properly my ststem
> started recording N/A for temperature. I have tried dumping memory etc and
> restartedit has restarted but the problem is the same. Here is the log.
> What has happened and how do I fix it please.
>
> base 'weewx.sdb'
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
> summaries
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdArchive
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
> not requested.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
> station IOTAGOQU2 will be posted
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
> enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
> 3.9.1
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
> (positive is fast)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
> since 2019-06-16 10:10:00 NZST (1560636600)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
> starting index= 0
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16
[weewx-user] Temp showing N/A
Around midnight last night - after months of operating properly my ststem
started recording N/A for temperature. I have tried dumping memory etc and
restartedit has restarted but the problem is the same. Here is the log.
What has happened and how do I fix it please.
base 'weewx.sdb'
Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
summaries
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdArchive
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdStationRegistry
Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
not requested.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdStationRegistry
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdWunderground
Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
station IOTAGOQU2 will be posted
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdWunderground
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdPWSweather
Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdPWSweather
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdCWOP
Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdCWOP
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdWOW
Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdWOW
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdAWEKAS
Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdAWEKAS
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.engine.StdPrint
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdPrint
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.engine.StdReport
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdReport
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
3.9.1
Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
(positive is fast)
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
since 2019-06-16 10:10:00 NZST (1560636600)
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
starting index= 0
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP try #4; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded.
Jun 16 10:24:58 WeatherPi weewx[583]: engine: Main loop exiting. Shutting
engine down.
Jun 16 10:24:58 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS
thread.
Jun 16 10:24:58 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max
tries exceeded while getting LOOP data.
Jun 16 10:24:58 WeatherPi weewx[583]: Waiting 60 seconds then
retrying...
Jun 16 10:25:58
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
That worked a treatthank you! On Monday, 15 April 2019 15:20:37 UTC+12, gjr80 wrote: > > Hi, > > Chances are you have suffered corrupted station memory due to the power > outage. Have a read of the *Corrupt station memory* section under WeeWX > generates HTML pages, but it does not update them > <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated> in > the User's Guide. Before doing anything stop WeeWX and use wee-device to > dump the station memory > <http://weewx.com/docs/hardware.htm#vantage_dumping_the_logger_memory>, > this is your best bet at minimising any data loss. Once you have dumped the > station memory work through the two steps listed under *Corrupt station > memory*. > > It's worth making a note of this condition and it's symptoms, it is a > common occurrence for Davis stations that have a power interruption. > > Gary > > On Monday, 15 April 2019 12:32:46 UTC+10, monmul wrote: >> >> I have run into a problem. I have been overseas for some time and just >> got back today. There was a power failure yesterday and weewx is stuck on >> mid night. See attached details. The photo on my website updatesbut nor >> the weather information? www.wilsonbayweather.com. What am I missing? >> >> On Wednesday, 6 March 2019 17:07:01 UTC+13, Andrew Milner wrote: >>> >>> That's Chrome and Google for you!! >>> >>> I've got a pic of a nice sunny verandah now also ….. >>> >>> >>> >>> On Wednesday, 6 March 2019 00:30:07 UTC+2, monmul wrote: >>>> >>>> Yes it was!how freakin weird! Thanks for the help and the prompts! >>>> >>>> On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote: >>>>> >>>>> Surely it cannot be something to do with clearing the cache on my >>>>> browsersthat does not seem realistic! >>>>> >>>>> On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote: >>>>>> >>>>>> Hah! If I look it up on my phoneI get the correct jpg? >>>>>> >>>>>> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: >>>>>>> >>>>>>> I am browsing from 2 different pcsone a chromebook using Chrome >>>>>>> and one my desktop using Chromium. I have tried both >>>>>>> www.wilsonbayweather.com and >>>>>>> www.wilsonbayweather.com/index.html..both give the same >>>>>>> image.this is weird!why would the various weather icons and >>>>>>> data >>>>>>> change but not the jpg.I will contact my web host and see if they >>>>>>> can >>>>>>> throw any light on it. Thanks again! >>>>>>> >>>>>>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >>>>>>>> >>>>>>>> So when I look at your site I see ChangeImage.jpg. Since that is >>>>>>>> what is on your WeeWX server it sounds to me like FTP and your web >>>>>>>> site are >>>>>>>> working as they should. Certainly Australia is seeing the correct >>>>>>>> page/image! It sounds like when you are looking at a page locally that >>>>>>>> it >>>>>>>> is not working. When you are browsing and seeing that wrong image what >>>>>>>> address are you entering in your browser and what device are you >>>>>>>> browsing >>>>>>>> from? >>>>>>>> >>>>>>>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Yes it was!how freakin weird! Thanks for the help and the prompts! On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote: > > Surely it cannot be something to do with clearing the cache on my > browsersthat does not seem realistic! > > On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote: >> >> Hah! If I look it up on my phoneI get the correct jpg? >> >> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: >>> >>> I am browsing from 2 different pcsone a chromebook using Chrome and >>> one my desktop using Chromium. I have tried both >>> www.wilsonbayweather.com and >>> www.wilsonbayweather.com/index.html..both give the same >>> image.this is weird!why would the various weather icons and data >>> change but not the jpg.I will contact my web host and see if they can >>> throw any light on it. Thanks again! >>> >>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >>>> >>>> So when I look at your site I see ChangeImage.jpg. Since that is what >>>> is on your WeeWX server it sounds to me like FTP and your web site are >>>> working as they should. Certainly Australia is seeing the correct >>>> page/image! It sounds like when you are looking at a page locally that it >>>> is not working. When you are browsing and seeing that wrong image what >>>> address are you entering in your browser and what device are you browsing >>>> from? >>>> >>>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Surely it cannot be something to do with clearing the cache on my browsersthat does not seem realistic! On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote: > > Hah! If I look it up on my phoneI get the correct jpg? > > On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: >> >> I am browsing from 2 different pcsone a chromebook using Chrome and >> one my desktop using Chromium. I have tried both www.wilsonbayweather.com >> and www.wilsonbayweather.com/index.html..both give the same >> image.this is weird!why would the various weather icons and data >> change but not the jpg.I will contact my web host and see if they can >> throw any light on it. Thanks again! >> >> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >>> >>> So when I look at your site I see ChangeImage.jpg. Since that is what is >>> on your WeeWX server it sounds to me like FTP and your web site are working >>> as they should. Certainly Australia is seeing the correct page/image! It >>> sounds like when you are looking at a page locally that it is not working. >>> When you are browsing and seeing that wrong image what address are you >>> entering in your browser and what device are you browsing from? >>> >>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Hah! If I look it up on my phoneI get the correct jpg? On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: > > I am browsing from 2 different pcsone a chromebook using Chrome and > one my desktop using Chromium. I have tried both www.wilsonbayweather.com > and www.wilsonbayweather.com/index.html..both give the same > image.this is weird!why would the various weather icons and data > change but not the jpg.I will contact my web host and see if they can > throw any light on it. Thanks again! > > On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >> >> So when I look at your site I see ChangeImage.jpg. Since that is what is >> on your WeeWX server it sounds to me like FTP and your web site are working >> as they should. Certainly Australia is seeing the correct page/image! It >> sounds like when you are looking at a page locally that it is not working. >> When you are browsing and seeing that wrong image what address are you >> entering in your browser and what device are you browsing from? >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I am browsing from 2 different pcsone a chromebook using Chrome and one my desktop using Chromium. I have tried both www.wilsonbayweather.com and www.wilsonbayweather.com/index.html..both give the same image.this is weird!why would the various weather icons and data change but not the jpg.I will contact my web host and see if they can throw any light on it. Thanks again! On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: > > So when I look at your site I see ChangeImage.jpg. Since that is what is > on your WeeWX server it sounds to me like FTP and your web site are working > as they should. Certainly Australia is seeing the correct page/image! It > sounds like when you are looking at a page locally that it is not working. > When you are browsing and seeing that wrong image what address are you > entering in your browser and what device are you browsing from? > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Curiouser and curiouser. Attached the image I see from my public website (staticJpg.jpg)...and also the weewx native output on the Pi (ChangeImage.jpg) file:///var/www/html/weewx/index.html On Wednesday, 6 March 2019 10:13:50 UTC+13, gjr80 wrote: > > So at 7:10 my time 10:10 (?) your time I am seeing a daytime photo of a > verandah with water and mountains in the background. That is quite > different to the night time image I first saw last night and the 'black > box' later last night. Give you image only updates on your WeeWX server > once an hour just wondering what basis you have for thinking it is not > working. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
So this was after I had gone to bedstill showing image1 uploadingand still getting a static image (the source of which I cannot find on the web server) on my web page. 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Attempting connection to 43.245.53.39 Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Connected to 43.245.53.39 Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayradiation.png Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/index.html Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayrain.png Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daywinddir.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daywindvec.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daywind.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daytempdew.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/image1.jpg Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayinside.png Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayuv.png Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/mobile.html Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/week.html Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daybarometer.png Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/month.html Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daytempchill.png Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayrx.png Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayhumidity.png Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/year.html Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/alltime.html Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/xstats/index.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/wind.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/index.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/radar.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/rain.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/barometer.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/temp_outside.html Mar 6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/NOAA/NOAA-2019.txt Mar 6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/NOAA/NOAA-2019-03.txt Mar 6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/RSS/weewx_rss.xml Mar 6 01:20:27 WeatherPi weewx[19404]: ftpgenerator: ftp'd 29 files in 5.46 seconds Mar 6 01:20:27 WeatherPi weewx[19404]: reportengine: Running report 'RSYNC' Mar 6 01:20:27 WeatherPi weewx[19404]: reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' Mar 6 01:20:27 WeatherPi weewx[19404]: rsyncgenerato On Tuesday, 5 March 2019 23:55:29 UTC+13, gjr80 wrote: > > Ok, but now when I look at your site image1.jpg does not the display. When > you deleted your jpg files you didn't touch anything on your WeeWX machine > did you? Your image is only produced every hour so if you did delete it on > the WeeWX machine then it could take up to an hour for it to be re-created > and subsequently uploaded to the web server. Keep an eye on your WeeWX log > to see if/when image1.jpg is uploaded. Guess it is getting late there now, > I will have a look later and see what is there. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thanks I will give that a try tomorrowits late here. I am thinking that you are right...and the problem lies in the FTP server. I will investigate and get back to you. Thank you for all your help! On Tuesday, 5 March 2019 23:07:12 UTC+13, gjr80 wrote: > > Yes the former, your web host on the internet. Some folks can ssh into > their web server but I am gu swing you haven't done that. Do you have a > login that you can use via a browser to manage your hosting? That should > have some sort of file management tool. > > I am not convinced that the FTP is not working, I think it is. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
By "delete image1.jpg from your web server" do you mean from the www.wilsonbayweather.com web server on the net or do you you mean the /var/www/html/weewx/ folder where it resides on my Pi? If the formernot sure how I would even do that? On Tuesday, 5 March 2019 22:45:26 UTC+13, gjr80 wrote: > > Hang on, missed this in the log you posted: > > Mar 5 21:30:30 WeatherPi weewx[19404]: ftpupload: Uploaded file > /public_html/image1.jpg > > Looks like it is being uploaded. What happens if you delete image1.jpg > from your web server, does it get replaced (albeit with an old file) on the > next report cycle? > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
weewx.conf attached - passwords etc changed. On Tuesday, 5 March 2019 22:07:12 UTC+13, gjr80 wrote: > > Sorry I am a bit slow in this but I don't use ftp myself. I see files are > being uploaded from /public_html, just wondering if perhaps something is in > the wrong place. Can you post a copy of weewx.conf being careful to take > out any sensitive info, user names, passwords etc. > > 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 CONFIGURATION FILE # # Copyright (c) 2009-2015 Tom Keffer # See the file LICENSE.txt for your rights. ## # This section is for general configuration information. # Set to 1 for extra debug info, otherwise comment it out or set to zero debug = 1 # Root directory of the weewx data file hierarchy for this station WEEWX_ROOT = / # Whether to log successful operations log_success = True # Whether to log unsuccessful operations log_failure = True # How long to wait before timing out a socket (FTP, HTTP) connection socket_timeout = 20 # Do not modify this. It is used when installing and updating weewx. version = 3.9.1 ## # This section is for information about the station. [Station] # Description of the station location location = "Wilson Bay, Queenstown, NZ" # Latitude and longitude in decimal degrees latitude = -45.0595 longitude = 168.567 # Altitude of the station, with unit it is in. This is downloaded from # from the station if the hardware supports it. altitude = 320, meter # Set to type of station hardware. There must be a corresponding stanza # in this file with a 'driver' parameter indicating the driver to be used. station_type = Vantage # If you have a website, you may specify an URL #station_url = http://www.example.com # The start of the rain year (1=January; 10=October, etc.). This is # downloaded from the station if the hardware supports it. rain_year_start = 1 # Start of week (0=Monday, 6=Sunday) week_start = 6 ## [Vantage] # This section is for the Davis Vantage series of weather stations. # Connection type: serial or ethernet # serial (the classic VantagePro) # ethernet (the WeatherLinkIP or Serial-Ethernet bridge) type = serial # If the connection type is serial, a port must be specified: # Debian, Ubuntu, Redhat, Fedora, and SuSE: # /dev/ttyUSB0 is a common USB port name # /dev/ttyS0 is a common serial port name # BSD: # /dev/cuaU0 is a common serial port name port = /dev/ttyUSB0 # If the connection type is ethernet, an IP Address/hostname is required: host = 1.2.3.4 ## # The rest of this section rarely needs any attention. # You can safely leave it "as is." ## # Serial baud rate (usually 19200) baudrate = 19200 # TCP port (when using the WeatherLinkIP) tcp_port = 2 # TCP send delay (when using the WeatherLinkIP): tcp_send_delay = 0.5 # The id of your ISS station (usually 1). If you use a wind meter connected # to a anemometer transmitter kit, use its id iss_id = 1 # How long to wait for a response from the station before giving up (in # seconds; must be greater than 2) timeout = 4 # How long to wait before trying again (in seconds) wait_before_retry = 1.2 # How many times to try before giving up: max_tries = 4 # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2 model_type = 2 # The driver to use: driver = weewx.drivers.vantage ## # This section is for uploading data to Internet sites [StdRESTful] [[StationRegistry]] # To register this weather station with weewx, set this to true register_this_station = false [[AWEKAS]] # This section is for configuring posts to AWEKAS. # If you wish to do this, set the option 'enable' to true, # and specify a username and password. # To guard against parsing errors, put the password in quotes. enable = false username = replace_me password = replace_me [[CWOP]] # This section is for configuring posts to CWOP. # If you wish to do this, set the option 'enable' to true, # and
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
It gets there via a cron hourly script #!/bin/sh # # Simple cron script sudo rm /var/www/html/weewx/image1.jpg #rm /var/www/html/weewx/640x480 sudo raspistill -w 640 -h 480 -o /var/www/html/weewx/image.jpg sudo mv /var/www/html/weewx/image.jpg /var/www/html/weewx/image1.jpg On Tuesday, 5 March 2019 18:41:47 UTC+13, gjr80 wrote: > > One thing 3.9.0 changed was the log_success and log_failure settings in > weewx.conf. Just to make sure nothing is being hidden from you edit > weewx.conf and under [StdReport] set log_failure = True. Also set debug = > 1, I don't think debug is going to tell us much more but let's give it a > go. Save weewx.conf. In the /vat/www/html/weewx directory find and delete > the file #FTPlast. Restart WeeWX. > > See what happens, if no change post the log from startup showing the > entire startup and at least a couple of complete report cycles. > > I don't see copy_always helping, that applies to the CopyGenerator only > and since the file concerned is already in /var/www/html/weewx we don't > need to copy it there. Just out of interest, can you give us an outline of > how image1.jpg arrives in /var/www/html/weewx ? > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
OK, so I seem to be on 3.9.1what has changed that would make the FTP keep working from the previous version but not carry the jpeg across? On Tuesday, 5 March 2019 10:19:24 UTC+13, Tom wrote: > > To determine the weewx version try: > > wee_config --version > > > -- > Tom > > > On Mon, Mar 4, 2019 at 1:54 PM monmul > > wrote: > >> I am thinking...maybe I accidentally updated to the latest version and >> that has broken something? How do I check what version I am running? >> >> On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote: >>> >>> So this is the FTP section of my weewx.conf..I have not changed >>> anything. It used to transfer across no problem until the camera needed >>> replacingand the photo from the new camera appears on the internal >>> website but not transferred across...weird! >>> >>> [[FTP]] >>> # FTP'ing the results to a webserver is treated as just another >>> report, >>> # albeit one with an unusual report generator! >>> skin = Ftp >>> >>> # If you wish to use FTP, uncomment and fill out the next four >>> lines. >>> # Use quotes around passwords to guard against parsing errors. >>> user = abcdefgh >>> password = 123456789 >>> server = 43.245.53.39 >>> path = /public_html >>> >>> # Set to True for an FTP over TLS (FTPS) connection. Not all >>> servers >>> # support this. >>> secure_ftp = False >>> >>> # To upload files from something other than what HTML_ROOT is set >>> # to above, specify a different HTML_ROOT here. >>> #HTML_ROOT = /var/www/html/weewx >>> >>> # Most FTP servers use port 21 >>> port = 21 >>> >>> # Set to 1 to use passive mode, zero for active mode >>> passive = 1 >>> >>> >>> On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote: >>>> >>>> you did not give us a directory listing from the external website - but >>>> assuming the file has not been transferred there maybe you need to include >>>> image.jpeg in the copy always list in weewx.conf >>>> >>>> >>>> >>>> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote: >>>>> >>>>> I have run into a problem with posting a photo on my website. The >>>>> photo shows on file:///var/www/html/weewx/index.html but not on >>>>> www.wilsonbayweather.com - this shows an old photo that never >>>>> changes! Attached are screenshots that may help. Why is it updating on >>>>> one >>>>> and not the other? >>>>> >>>>> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> There are a few steps involved in achieving what you want to do. >>>>>> First the historical max/min - by this I presume you mean all time >>>>>> statistics - those that cover all of your weeWX data and not just the >>>>>> last >>>>>> day, month or year. >>>>>> >>>>>> If I have this right you need to extend weeWX so that you can access >>>>>> stats from all of your data, this is most easily achieved by installing >>>>>> the >>>>>> xstats example extension. You will find the xstats files are in the >>>>>> /usr/share/doc/weewx/examples directory. I would install manually >>>>>> and just follow step 1 in the readme.txt remembering later that you >>>>>> will need to enable the alltime stats for your templates/reports by >>>>>> following step 2. You can install xstats using wee_extension but >>>>>> that will also install the example web page which you probably do not >>>>>> want. >>>>>> >>>>>> Now that you have xstats installed you can use tags like >>>>>> $alltime.outTemp.max in report templates to display the maximum >>>>>> outside temperature. The time it occurred will be >>>>>> $alltime.outTemp.maxtime. Just like $day, $month and $year tags but >>>>>> you use $alltime. If you are not familiar with weeWX tags it is worth >>>>>> r
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I am thinking...maybe I accidentally updated to the latest version and that has broken something? How do I check what version I am running? On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote: > > So this is the FTP section of my weewx.conf..I have not changed > anything. It used to transfer across no problem until the camera needed > replacingand the photo from the new camera appears on the internal > website but not transferred across...weird! > > [[FTP]] > # FTP'ing the results to a webserver is treated as just another > report, > # albeit one with an unusual report generator! > skin = Ftp > > # If you wish to use FTP, uncomment and fill out the next four > lines. > # Use quotes around passwords to guard against parsing errors. > user = abcdefgh > password = 123456789 > server = 43.245.53.39 > path = /public_html > > # Set to True for an FTP over TLS (FTPS) connection. Not all > servers > # support this. > secure_ftp = False > > # To upload files from something other than what HTML_ROOT is set > # to above, specify a different HTML_ROOT here. > #HTML_ROOT = /var/www/html/weewx > > # Most FTP servers use port 21 > port = 21 > > # Set to 1 to use passive mode, zero for active mode > passive = 1 > > > On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote: >> >> you did not give us a directory listing from the external website - but >> assuming the file has not been transferred there maybe you need to include >> image.jpeg in the copy always list in weewx.conf >> >> >> >> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote: >>> >>> I have run into a problem with posting a photo on my website. The photo >>> shows on file:///var/www/html/weewx/index.html but not on >>> www.wilsonbayweather.com - this shows an old photo that never changes! >>> Attached are screenshots that may help. Why is it updating on one and not >>> the other? >>> >>> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >>>> >>>> Hi, >>>> >>>> There are a few steps involved in achieving what you want to do. First >>>> the historical max/min - by this I presume you mean all time statistics - >>>> those that cover all of your weeWX data and not just the last day, month >>>> or >>>> year. >>>> >>>> If I have this right you need to extend weeWX so that you can access >>>> stats from all of your data, this is most easily achieved by installing >>>> the >>>> xstats example extension. You will find the xstats files are in the >>>> /usr/share/doc/weewx/examples directory. I would install manually and >>>> just follow step 1 in the readme.txt remembering later that you will >>>> need to enable the alltime stats for your templates/reports by following >>>> step 2. You can install xstats using wee_extension but that will also >>>> install the example web page which you probably do not want. >>>> >>>> Now that you have xstats installed you can use tags like >>>> $alltime.outTemp.max in report templates to display the maximum >>>> outside temperature. The time it occurred will be >>>> $alltime.outTemp.maxtime. Just like $day, $month and $year tags but >>>> you use $alltime. If you are not familiar with weeWX tags it is worth >>>> reading the Tags section <http://weewx.com/docs/customizing.htm#Tags> >>>> of the Customization Guide. >>>> >>>> To use the $alltime tags you will probably want to create a new page >>>> or modify an existing one. It is really up to you want you want to do. To >>>> modify an existing page have a look at the .tmpl files in you Standard >>>> skin directory /etc/weewx/skins/Standard. These are the files weeWX >>>> uses to generate a corresponding .html page. You will see how tags are >>>> used >>>> in a template, in a nutshell where you place a tag weeWX will replace that >>>> with the relevant data when the reports are generated. The process is a >>>> little more involved if you want to create a new page as not only do you >>>> need to modify/create a page but you also need to modify skin.conf to >>>> have weeWX generate the new page. You may also need to modify other pages >>>> to include a link to your new page.
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
So this is the FTP section of my weewx.conf..I have not changed anything. It used to transfer across no problem until the camera needed replacingand the photo from the new camera appears on the internal website but not transferred across...weird! [[FTP]] # FTP'ing the results to a webserver is treated as just another report, # albeit one with an unusual report generator! skin = Ftp # If you wish to use FTP, uncomment and fill out the next four lines. # Use quotes around passwords to guard against parsing errors. user = abcdefgh password = 123456789 server = 43.245.53.39 path = /public_html # Set to True for an FTP over TLS (FTPS) connection. Not all servers # support this. secure_ftp = False # To upload files from something other than what HTML_ROOT is set # to above, specify a different HTML_ROOT here. #HTML_ROOT = /var/www/html/weewx # Most FTP servers use port 21 port = 21 # Set to 1 to use passive mode, zero for active mode passive = 1 On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote: > > you did not give us a directory listing from the external website - but > assuming the file has not been transferred there maybe you need to include > image.jpeg in the copy always list in weewx.conf > > > > On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote: >> >> I have run into a problem with posting a photo on my website. The photo >> shows on file:///var/www/html/weewx/index.html but not on >> www.wilsonbayweather.com - this shows an old photo that never changes! >> Attached are screenshots that may help. Why is it updating on one and not >> the other? >> >> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >>> >>> Hi, >>> >>> There are a few steps involved in achieving what you want to do. First >>> the historical max/min - by this I presume you mean all time statistics - >>> those that cover all of your weeWX data and not just the last day, month or >>> year. >>> >>> If I have this right you need to extend weeWX so that you can access >>> stats from all of your data, this is most easily achieved by installing the >>> xstats example extension. You will find the xstats files are in the >>> /usr/share/doc/weewx/examples directory. I would install manually and >>> just follow step 1 in the readme.txt remembering later that you will >>> need to enable the alltime stats for your templates/reports by following >>> step 2. You can install xstats using wee_extension but that will also >>> install the example web page which you probably do not want. >>> >>> Now that you have xstats installed you can use tags like >>> $alltime.outTemp.max in report templates to display the maximum outside >>> temperature. The time it occurred will be $alltime.outTemp.maxtime. >>> Just like $day, $month and $year tags but you use $alltime. If you are >>> not familiar with weeWX tags it is worth reading the Tags section >>> <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide. >>> >>> To use the $alltime tags you will probably want to create a new page or >>> modify an existing one. It is really up to you want you want to do. To >>> modify an existing page have a look at the .tmpl files in you Standard >>> skin directory /etc/weewx/skins/Standard. These are the files weeWX >>> uses to generate a corresponding .html page. You will see how tags are used >>> in a template, in a nutshell where you place a tag weeWX will replace that >>> with the relevant data when the reports are generated. The process is a >>> little more involved if you want to create a new page as not only do you >>> need to modify/create a page but you also need to modify skin.conf to >>> have weeWX generate the new page. You may also need to modify other pages >>> to include a link to your new page. A good starting point may be to take a >>> copy of /etc/weewx/skins/Standard/year.html.tmpl, save it as >>> alltime.html.tmpl and start modifying. Have a good poke around the >>> templates and skin.conf (and [StdReport] in weewx.conf) to see how it >>> comes together. >>> >>> Including an image in a weeWX generated page can be relatively >>> straightforward. If you have a look in index.html.tmpl you will see >>> lines such as: >>> >>> >>> >>> This line creates a HTML img tag that displays the daily temperature and >>> dewpo
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Is there anyway I can help in getting the WeatherDisplay csv data into the weewx database..I have been away for a while so might have missed any updates on this project. On Thursday, 17 January 2019 22:40:45 UTC+13, monmul wrote: > > AwesomeI thought that weeimport could only deal with csv files and so > went and converted them allbut kept the txt files for backup! > > On Thursday, 17 January 2019 22:35:30 UTC+13, gjr80 wrote: >> >> Ok, that explains the csv file you provided having a different name >> structure to what I had found. I believe that there was/is the ability for >> WD to publish csv format log files and that is what I have. Weeimport will >> happily work with the MMlg.txt files just as they are. No need to dig >> anything out of an old machine. You will be the 1st so it will work with >> your logs and I guess we see where it goes from there. Weeimport is fairly >> flexible in structure and can easily be adapted. >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
For those following on from me.the two power packs - 1 feeding the Rpi 3 and the other feeding the USB hub has made a tremendous difference.no problems shown in the log, no time problems, no voltage problemsit just flows and operates really well. I wish I had known this from the start it would have saved me so much grief! On Tuesday, 29 January 2019 15:27:46 UTC+13, monmul wrote: > > Yes it was, apologies to those I doubted! > > On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote: >> >> Congratulations! Looks like it was a power supply problem. >> >> USB power supplies fail. I had one that would show +5V under no load, but >> it would sag to near nothing with just a modest load. >> >> On Mon, Jan 28, 2019 at 5:26 PM monmul wrote: >> >>> It is working again!.This time I used both official power >>> units...one to power the Pi and one to power the hub. >>> >>> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: >>>> >>>> Then you definitely have a connectivity problem! >>>> >>>> -tk >>>> >>>> On Mon, Jan 28, 2019 at 4:32 PM monmul wrote: >>>> >>>>> Welcome to minicom 2.7 >>>>> >>>>> OPTIONS: I18n >>>>> Compiled on Apr 22 2017, 09:14:19. >>>>> Port /dev/ttyUSB0, 13:15:39 >>>>> >>>>> Press CTRL-A Z for help on special keys >>>>> >>>>> Even after lots or s nothing happens on TEST >>>>> >>>>> Similarly for screen... >>>>> >>>>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>>>>> >>>>>> The "establishing connectivity" instructions don't mention it, but be >>>>>> sure to hit a few times before typing TEST. >>>>>> >>>>>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>>>>> >>>>>>> Tried both screen and minicom.no TEST echo backso must be >>>>>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>>>>> been >>>>>>> replaced.have another pi on orderbut in the meantime I guess I >>>>>>> will >>>>>>> go back to scratch and start all over againat least it has worked >>>>>>> before with this set upmaybe something has become corrupted! >>>>>>> >>>>>>> >>>>>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>>>>> >>>>>>>> Try to communicate directly with the Envoy, without going through >>>>>>>> WeeWX. For how to do this, see the section *Establishing >>>>>>>> connectivity >>>>>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>>>>> the User's Guide. If you are unable to do that, then this is >>>>>>>> definitely a >>>>>>>> hardware problem. >>>>>>>> >>>>>>>> -tk >>>>>>>> >>>>>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks, but no I don't I use VNC. >>>>>>>>> >>>>>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>>>>> >>>>>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in >>>>>>>>>> touch screen) attached that is running off the same power supply as >>>>>>>>>> the Pi? >>>>>>>>>> I had a setup like that which used a splitter to power both the >>>>>>>>>> monitor and >>>>>>>>>> Pi from one power pack. My setup kept complaining of undervolting >>>>>>>>>> until I >>>>>>>>>> removed the splitter and plugged the monitor and pi each into their >>>>>>>>>> own >>>>>>>>>> power supply. >>>>>>>>>> >>>>>>>>>> phil >>>>>>>>>> >>>>>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>>&g
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Yes it was, apologies to those I doubted! On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote: > > Congratulations! Looks like it was a power supply problem. > > USB power supplies fail. I had one that would show +5V under no load, but > it would sag to near nothing with just a modest load. > > On Mon, Jan 28, 2019 at 5:26 PM monmul > > wrote: > >> It is working again!.This time I used both official power units...one >> to power the Pi and one to power the hub. >> >> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: >>> >>> Then you definitely have a connectivity problem! >>> >>> -tk >>> >>> On Mon, Jan 28, 2019 at 4:32 PM monmul wrote: >>> >>>> Welcome to minicom 2.7 >>>> >>>> OPTIONS: I18n >>>> Compiled on Apr 22 2017, 09:14:19. >>>> Port /dev/ttyUSB0, 13:15:39 >>>> >>>> Press CTRL-A Z for help on special keys >>>> >>>> Even after lots or s nothing happens on TEST >>>> >>>> Similarly for screen... >>>> >>>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>>>> >>>>> The "establishing connectivity" instructions don't mention it, but be >>>>> sure to hit a few times before typing TEST. >>>>> >>>>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>>>> >>>>>> Tried both screen and minicom.no TEST echo backso must be >>>>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>>>> been >>>>>> replaced.have another pi on orderbut in the meantime I guess I >>>>>> will >>>>>> go back to scratch and start all over againat least it has worked >>>>>> before with this set upmaybe something has become corrupted! >>>>>> >>>>>> >>>>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>>>> >>>>>>> Try to communicate directly with the Envoy, without going through >>>>>>> WeeWX. For how to do this, see the section *Establishing >>>>>>> connectivity >>>>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>>>> the User's Guide. If you are unable to do that, then this is definitely >>>>>>> a >>>>>>> hardware problem. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>>>>>> >>>>>>>> Thanks, but no I don't I use VNC. >>>>>>>> >>>>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>>>> >>>>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in >>>>>>>>> touch screen) attached that is running off the same power supply as >>>>>>>>> the Pi? >>>>>>>>> I had a setup like that which used a splitter to power both the >>>>>>>>> monitor and >>>>>>>>> Pi from one power pack. My setup kept complaining of undervolting >>>>>>>>> until I >>>>>>>>> removed the splitter and plugged the monitor and pi each into their >>>>>>>>> own >>>>>>>>> power supply. >>>>>>>>> >>>>>>>>> phil >>>>>>>>> >>>>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>>>> >>>>>>>>>> I have replaced the power unit, taken it off the power strip an >>>>>>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>>>>>> powered hub (official RPi one...with another official RPi one) >>>>>>>>>> ...and here >>>>>>>>>> is what I am getting...very dispirited! I have another Davis >>>>>>>>>> Weather >>>>>>>>>> Envoy which I will soon substitute for the one I am currently >>>>>>>>>> using.but >>>>>>>>>> nothing seems to m
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
It is working again!.This time I used both official power units...one to power the Pi and one to power the hub. On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: > > Then you definitely have a connectivity problem! > > -tk > > On Mon, Jan 28, 2019 at 4:32 PM monmul > > wrote: > >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 13:15:39 >> >> Press CTRL-A Z for help on special keys >> >> Even after lots or s nothing happens on TEST >> >> Similarly for screen... >> >> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>> >>> The "establishing connectivity" instructions don't mention it, but be >>> sure to hit a few times before typing TEST. >>> >>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>> >>>> Tried both screen and minicom.no TEST echo backso must be >>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>> been >>>> replaced.have another pi on orderbut in the meantime I guess I >>>> will >>>> go back to scratch and start all over againat least it has worked >>>> before with this set upmaybe something has become corrupted! >>>> >>>> >>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>> >>>>> Try to communicate directly with the Envoy, without going through >>>>> WeeWX. For how to do this, see the section *Establishing connectivity >>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>> the User's Guide. If you are unable to do that, then this is definitely a >>>>> hardware problem. >>>>> >>>>> -tk >>>>> >>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>>>> >>>>>> Thanks, but no I don't I use VNC. >>>>>> >>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>> >>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>>>>>> screen) attached that is running off the same power supply as the Pi? I >>>>>>> had >>>>>>> a setup like that which used a splitter to power both the monitor and >>>>>>> Pi >>>>>>> from one power pack. My setup kept complaining of undervolting until I >>>>>>> removed the splitter and plugged the monitor and pi each into their own >>>>>>> power supply. >>>>>>> >>>>>>> phil >>>>>>> >>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>> >>>>>>>> I have replaced the power unit, taken it off the power strip an >>>>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>>>> powered hub (official RPi one...with another official RPi one) ...and >>>>>>>> here >>>>>>>> is what I am getting...very dispirited! I have another Davis >>>>>>>> Weather >>>>>>>> Envoy which I will soon substitute for the one I am currently >>>>>>>> using.but >>>>>>>> nothing seems to make a difference and the Envoy just will not wake up! >>>>>>>> >>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>>>>>> Failed to add printer: server-error-service-unavailable >>>>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>>>>>> available >>>>>>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage >>>>>>>> normalised (0x) >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>>>>>> console >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: >>>>>>>> Unable
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
This is with debug set to 1 - see attached.does that give us any further information on the situation? On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: > > Then you definitely have a connectivity problem! > > -tk > > On Mon, Jan 28, 2019 at 4:32 PM monmul > > wrote: > >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 13:15:39 >> >> Press CTRL-A Z for help on special keys >> >> Even after lots or s nothing happens on TEST >> >> Similarly for screen... >> >> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>> >>> The "establishing connectivity" instructions don't mention it, but be >>> sure to hit a few times before typing TEST. >>> >>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>> >>>> Tried both screen and minicom.no TEST echo backso must be >>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>> been >>>> replaced.have another pi on orderbut in the meantime I guess I >>>> will >>>> go back to scratch and start all over againat least it has worked >>>> before with this set upmaybe something has become corrupted! >>>> >>>> >>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>> >>>>> Try to communicate directly with the Envoy, without going through >>>>> WeeWX. For how to do this, see the section *Establishing connectivity >>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>> the User's Guide. If you are unable to do that, then this is definitely a >>>>> hardware problem. >>>>> >>>>> -tk >>>>> >>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>>>> >>>>>> Thanks, but no I don't I use VNC. >>>>>> >>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>> >>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>>>>>> screen) attached that is running off the same power supply as the Pi? I >>>>>>> had >>>>>>> a setup like that which used a splitter to power both the monitor and >>>>>>> Pi >>>>>>> from one power pack. My setup kept complaining of undervolting until I >>>>>>> removed the splitter and plugged the monitor and pi each into their own >>>>>>> power supply. >>>>>>> >>>>>>> phil >>>>>>> >>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>> >>>>>>>> I have replaced the power unit, taken it off the power strip an >>>>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>>>> powered hub (official RPi one...with another official RPi one) ...and >>>>>>>> here >>>>>>>> is what I am getting...very dispirited! I have another Davis >>>>>>>> Weather >>>>>>>> Envoy which I will soon substitute for the one I am currently >>>>>>>> using.but >>>>>>>> nothing seems to make a difference and the Envoy just will not wake up! >>>>>>>> >>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>>>>>> Failed to add printer: server-error-service-unavailable >>>>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>>>>>> available >>>>>>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage >>>>>>>> normalised (0x) >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>>>>>> console >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: >>>>>>>> Unable
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Welcome to minicom 2.7 OPTIONS: I18n Compiled on Apr 22 2017, 09:14:19. Port /dev/ttyUSB0, 13:15:39 Press CTRL-A Z for help on special keys Even after lots or s nothing happens on TEST Similarly for screen... On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: > > The "establishing connectivity" instructions don't mention it, but be sure > to hit a few times before typing TEST. > > On Mon, Jan 28, 2019 at 4:11 PM monmul > > wrote: > >> Tried both screen and minicom.no TEST echo backso must be >> hardwarebut totally flummoxed as all hardware (apart from Rpi) has been >> replaced.have another pi on orderbut in the meantime I guess I will >> go back to scratch and start all over againat least it has worked >> before with this set upmaybe something has become corrupted! >> >> >> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>> >>> Try to communicate directly with the Envoy, without going through WeeWX. >>> For how to do this, see the section *Establishing connectivity >>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>> the User's Guide. If you are unable to do that, then this is definitely a >>> hardware problem. >>> >>> -tk >>> >>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>> >>>> Thanks, but no I don't I use VNC. >>>> >>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>> >>>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>>>> screen) attached that is running off the same power supply as the Pi? I >>>>> had >>>>> a setup like that which used a splitter to power both the monitor and Pi >>>>> from one power pack. My setup kept complaining of undervolting until I >>>>> removed the splitter and plugged the monitor and pi each into their own >>>>> power supply. >>>>> >>>>> phil >>>>> >>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>> >>>>>> I have replaced the power unit, taken it off the power strip an >>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>> powered hub (official RPi one...with another official RPi one) ...and >>>>>> here >>>>>> is what I am getting...very dispirited! I have another Davis Weather >>>>>> Envoy which I will soon substitute for the one I am currently >>>>>> using.but >>>>>> nothing seems to make a difference and the Envoy just will not wake up! >>>>>> >>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>>>> Failed to add printer: server-error-service-unavailable >>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>>>> available >>>>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage normalised >>>>>> (0x) >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>>>> console >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: >>>>>> Unable to wake up Vantage console () >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load >>>>>> driver: Unable to wake up Vantage console >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: Exiting... >>>>>> Jan 29 09:14:27 raspberrypi kernel: [ 39.511958] Under-voltage >>>>>> detected! (0x00050005) >>>>>> Jan 29 09:14:31 raspberrypi kernel: [ 43.671921] Voltage normalised >>>>>> (0x) >>>>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 103.239.8.22 >>>>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 202.46.185.18 >>>>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 203.99.128.48 >>>>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 103.106.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Tried both screen and minicom.no TEST echo backso must be hardwarebut totally flummoxed as all hardware (apart from Rpi) has been replaced.have another pi on orderbut in the meantime I guess I will go back to scratch and start all over againat least it has worked before with this set upmaybe something has become corrupted! On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: > > Try to communicate directly with the Envoy, without going through WeeWX. > For how to do this, see the section *Establishing connectivity > <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in the > User's Guide. If you are unable to do that, then this is definitely a > hardware problem. > > -tk > > On Mon, Jan 28, 2019 at 2:41 PM dunbrokin > > wrote: > >> Thanks, but no I don't I use VNC. >> >> On Tue, Jan 29, 2019 at 11:35 AM > wrote: >> >>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>> screen) attached that is running off the same power supply as the Pi? I had >>> a setup like that which used a splitter to power both the monitor and Pi >>> from one power pack. My setup kept complaining of undervolting until I >>> removed the splitter and plugged the monitor and pi each into their own >>> power supply. >>> >>> phil >>> >>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>> >>>> I have replaced the power unit, taken it off the power strip an plugged >>>> both it and the Vanatage into the mains. I have replaced the powered hub >>>> (official RPi one...with another official RPi one) ...and here is what I >>>> am >>>> getting...very dispirited! I have another Davis Weather Envoy which I >>>> will soon substitute for the one I am currently using.but nothing >>>> seems >>>> to make a difference and the Envoy just will not wake up! >>>> >>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>> Failed to add printer: server-error-service-unavailable >>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>> available >>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage normalised >>>> (0x) >>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>> console >>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable >>>> to wake up Vantage console () >>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver: >>>> Unable to wake up Vantage console >>>> Jan 29 09:14:12 raspberrypi weewx[506]: Exiting... >>>> Jan 29 09:14:27 raspberrypi kernel: [ 39.511958] Under-voltage >>>> detected! (0x00050005) >>>> Jan 29 09:14:31 raspberrypi kernel: [ 43.671921] Voltage normalised >>>> (0x) >>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.239.8.22 >>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>> 202.46.185.18 >>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>> 203.99.128.48 >>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.106.66.123 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.242.68.69 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.106.65.219 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.242.70.5 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 122.252.188.99 >>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server >>>> 130.217.226.51 >>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.242.68.68 >>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server >>>> 203.99.128.34 >>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server >>>> 202.46.177.18 >>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server >>>> 2407:f100:0:4::3 >>>> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I guess the best thing to do now is to start all over from scratch!!
On Tuesday, 29 January 2019 10:27:59 UTC+13, monmul wrote:
>
> pi@raspberrypi:~ $ wee_device --dumpUsing configuration file
> /etc/weewx/weewx.conf
> Using Vantage driver version 3.0.11 (weewx.drivers.vantage)
> Traceback (most recent call last):
> File "/usr/bin/wee_device", line 54, in
> main()
> File "/usr/bin/wee_device", line 51, in main
> device.configure(config_dict)
> File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1970, in
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 487, in __init__
> self._setup()
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1278, in _setup
> self.port.wakeup_console(max_tries=self.max_tries)
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 94, in
> wakeup_console
> raise weewx.WakeupError("Unable to wake up Vantage console")
> weewx.WakeupError: Unable to wake up Vantage console
> pi@raspberrypi:~ $
>
> On Tuesday, 29 January 2019 10:25:31 UTC+13, monmul wrote:
>>
>> Sorry, I think you are on the wrong thread!
>>
>> On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote:
>>>
>>> May i have an url for a web page running weewx v3.9.0 with the new
>>> skin to see what is look like
>>> Jean-Pierre
>>>
>>> Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit :
>>>>
>>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a
>>>> Davis Vantage weather station. I have a serial Envoy data logger attaced
>>>> to
>>>> my Rpi with a serial/usb converter. In following the set up instructions,
>>>> I
>>>> get these errors!
>>>>
>>>> sudo weewxd weewx.conf
>>>> Traceback (most recent call last):
>>>> File "/usr/bin/weewxd", line 64, in
>>>> weewx.engine.main(options, args)
>>>> File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>>> sane = os.stat(config_path).st_ctime
>>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>>> Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered:
>>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>>> Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>>> Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>>> Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>>> Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>>> Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>>> next retry is Sun Jan 6 13:41:35 2019 [try
>>>> http://www.rsyslog.com/e/2007 ]
>>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx
>>>> version 3.8.2
>>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9
>>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform
>>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>>> Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary
>>>> Directories...
>>>> Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>>> next retry is Sun Jan 6 13:53:04 2019 [try
>>>> http://www.rsyslog.com/e/2007 ]
>>>> Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary
>>>> Directories.
>>>> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>> Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>>> next retry is Sun Jan 6 13:55:58 2019 [try
>>>> http://www.rsyslog.com/e/2007 ]
>>>> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>>
>>>> Please where have I gone wrong?
>>>>
>>>>
>>>> .
>>>>
>>>> Hi,
>>>>
>>>> It appears that you are in the /home/pi directory and hence weewxd is
>>>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf
>>>> ie:
>>>>
>>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>>
>>>> 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: Getting the RPi 3 with Davis Vantage up and running
pi@raspberrypi:~ $ wee_device --dumpUsing configuration file
/etc/weewx/weewx.conf
Using Vantage driver version 3.0.11 (weewx.drivers.vantage)
Traceback (most recent call last):
File "/usr/bin/wee_device", line 54, in
main()
File "/usr/bin/wee_device", line 51, in main
device.configure(config_dict)
File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1970, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
File "/usr/share/weewx/weewx/drivers/vantage.py", line 487, in __init__
self._setup()
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1278, in _setup
self.port.wakeup_console(max_tries=self.max_tries)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 94, in
wakeup_console
raise weewx.WakeupError("Unable to wake up Vantage console")
weewx.WakeupError: Unable to wake up Vantage console
pi@raspberrypi:~ $
On Tuesday, 29 January 2019 10:25:31 UTC+13, monmul wrote:
>
> Sorry, I think you are on the wrong thread!
>
> On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote:
>>
>> May i have an url for a web page running weewx v3.9.0 with the new
>> skin to see what is look like
>> Jean-Pierre
>>
>> Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit :
>>>
>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis
>>> Vantage weather station. I have a serial Envoy data logger attaced to my
>>> Rpi with a serial/usb converter. In following the set up instructions, I
>>> get these errors!
>>>
>>> sudo weewxd weewx.conf
>>> Traceback (most recent call last):
>>> File "/usr/bin/weewxd", line 64, in
>>> weewx.engine.main(options, args)
>>> File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>> sane = os.stat(config_path).st_ctime
>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>> Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered:
>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>> Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>> Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>> Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>> Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>> Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan 6 13:41:35 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx
>>> version 3.8.2
>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9
>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform
>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>> Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary
>>> Directories...
>>> Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan 6 13:53:04 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary
>>> Directories.
>>> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>> Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan 6 13:55:58 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>
>>> Please where have I gone wrong?
>>>
>>>
>>> .
>>>
>>> Hi,
>>>
>>> It appears that you are in the /home/pi directory and hence weewxd is
>>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> 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: Getting the RPi 3 with Davis Vantage up and running
Sorry, I think you are on the wrong thread! On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote: > > May i have an url for a web page running weewx v3.9.0 with the new skin > to see what is look like > Jean-Pierre > > Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit : >> >> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis >> Vantage weather station. I have a serial Envoy data logger attaced to my >> Rpi with a serial/usb converter. In following the set up instructions, I >> get these errors! >> >> sudo weewxd weewx.conf >> Traceback (most recent call last): >> File "/usr/bin/weewxd", line 64, in >> weewx.engine.main(options, args) >> File "/usr/share/weewx/weewx/engine.py", line 835, in main >> sane = os.stat(config_path).st_ctime >> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf' >> pi@Weatherpi:~ $ tail -f /var/log/syslog >> Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: >> sender=:1.16 path=/MediaEndpoint/A2DPSink >> Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available >> Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available >> Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed >> Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed >> Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, >> next retry is Sun Jan 6 13:41:35 2019 [try http://www.rsyslog.com/e/2007 >> ] >> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version >> 3.8.2 >> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 >> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2] >> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform >> Linux-4.9.35-v7+-armv7l-with-debian-8.0 >> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8' >> Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary >> Directories... >> Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, >> next retry is Sun Jan 6 13:53:04 2019 [try http://www.rsyslog.com/e/2007 >> ] >> Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary >> Directories. >> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying >> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] >> Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, >> next retry is Sun Jan 6 13:55:58 2019 [try http://www.rsyslog.com/e/2007 >> ] >> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying >> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] >> >> Please where have I gone wrong? >> >> >> . >> >> Hi, >> >> It appears that you are in the /home/pi directory and hence weewxd is >> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie: >> >> $ sudo weewxd /etc/weewx/weewx.conf >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Nothing coming through! pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop[ ok ] Stopping weewx (via systemctl): weewx.service. pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf pi@raspberrypi:~ $ lsusb Bus 001 Device 006: ID 13fe:4100 Kingston Technology Company Inc. Flash drive Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC 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. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:~ $ On Tuesday, 29 January 2019 10:11:51 UTC+13, monmul wrote: > > pi@raspberrypi:~ $ for id in core sdram_c sdram_i sdram_p ; do \ > > echo -e "$id:\t$(vcgencmd measure_volts $id)" ; \ > done > bash: : command not found > core: volt=1.2000V > bash: : command not found > bash: : command not found > sdram_c: volt=1.2000V > bash: : command not found > bash: : command not found > sdram_i: volt=1.2000V > bash: : command not found > bash: : command not found > sdram_p: volt=1.2250V > bash: : command not found > > > On Tuesday, 29 January 2019 10:04:38 UTC+13, monmul wrote: >> >> I have now replaced the old Envoy with a new envoy I had lying around. I >> have dug our the Vantage Pro 2 console from the basement and it is now up >> and running and displaying data. But this is what I get in my syslog!! Sigh! >> >> >> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Jan 29 09:44:48 raspberrypi kernel: [ 18.711659] Voltage normalised >> (0x) >> Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available >> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: >> connected: 10.1.1.155::47050 (TCP) >> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: >> authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions) >> Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: >> Failed to add printer: server-error-service-unavailable >> Jan 29 09:44:52 raspberrypi kernel: [ 22.871779] Under-voltage >> detected! (0x00050005) >> Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console >> Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable >> to wake up Vantage console () >> Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: >> Unable to wake up Vantage console >> Jan 29 09:44:54 raspberrypi weewx[495]: Exiting... >> Jan 29 09:45:00 raspberrypi kernel: [ 31.191813] Voltage normalised >> (0x) >> Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server >> 103.106.66.123 >> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.185.18 >> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server >> 130.217.226.51 >> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server >> 203.99.128.34 >> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.177.18 >> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.178.18 >> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server >> 103.106.65.219 >> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server >> 2407:f100:0:4::3 >> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.179.18 >> Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed >> Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin >> timestamp 0xdff9e880.d9ce150e does not match aorg 00. from >> server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9 >> Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed >> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >> 37min 9.646374s random time. >> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min >> 10.183019s random time. >> >> On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote: >>> >>> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote: >>>> >>>> I have replaced the power unit, taken it off the power strip an plugged >>>> both it and the Vanatage into the mains. I have replaced the powered hub >>>> (official RPi one...with another official RPi one) ...and here is what I >>>> am >>>> getting...very dispirited! I have another Davis Weather Envoy which I >>>> will soon substitute for the one I am currently
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
pi@raspberrypi:~ $ for id in core sdram_c sdram_i sdram_p ; do \ > echo -e "$id:\t$(vcgencmd measure_volts $id)" ; \ > done bash: : command not found core: volt=1.2000V bash: : command not found bash: : command not found sdram_c: volt=1.2000V bash: : command not found bash: : command not found sdram_i: volt=1.2000V bash: : command not found bash: : command not found sdram_p: volt=1.2250V bash: : command not found On Tuesday, 29 January 2019 10:04:38 UTC+13, monmul wrote: > > I have now replaced the old Envoy with a new envoy I had lying around. I > have dug our the Vantage Pro 2 console from the basement and it is now up > and running and displaying data. But this is what I get in my syslog!! Sigh! > > > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog > Jan 29 09:44:48 raspberrypi kernel: [ 18.711659] Voltage normalised > (0x) > Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available > Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: > connected: 10.1.1.155::47050 (TCP) > Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: > authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions) > Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: Failed > to add printer: server-error-service-unavailable > Jan 29 09:44:52 raspberrypi kernel: [ 22.871779] Under-voltage detected! > (0x00050005) > Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console > Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable to > wake up Vantage console () > Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: > Unable to wake up Vantage console > Jan 29 09:44:54 raspberrypi weewx[495]: Exiting... > Jan 29 09:45:00 raspberrypi kernel: [ 31.191813] Voltage normalised > (0x) > Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server > 103.106.66.123 > Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 202.46.185.18 > Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server > 130.217.226.51 > Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 203.99.128.34 > Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.177.18 > Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.178.18 > Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server > 103.106.65.219 > Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server > 2407:f100:0:4::3 > Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 202.46.179.18 > Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed > Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin > timestamp 0xdff9e880.d9ce150e does not match aorg 00. from > server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9 > Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed > Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding > 37min 9.646374s random time. > Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min > 10.183019s random time. > > On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote: >> >> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote: >>> >>> I have replaced the power unit, taken it off the power strip an plugged >>> both it and the Vanatage into the mains. I have replaced the powered hub >>> (official RPi one...with another official RPi one) ...and here is what I am >>> getting...very dispirited! I have another Davis Weather Envoy which I >>> will soon substitute for the one I am currently using.but nothing seems >>> to make a difference and the Envoy just will not wake up! >>> >>> >>> >> Still sounds like you have insufficient power to me. >> You might try measuring it. >> >> >> https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption >> >> (there are many such devices) >> > -- 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: Getting the RPi 3 with Davis Vantage up and running
I have now replaced the old Envoy with a new envoy I had lying around. I have dug our the Vantage Pro 2 console from the basement and it is now up and running and displaying data. But this is what I get in my syslog!! Sigh! pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 29 09:44:48 raspberrypi kernel: [ 18.711659] Voltage normalised (0x) Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: connected: 10.1.1.155::47050 (TCP) Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions) Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable Jan 29 09:44:52 raspberrypi kernel: [ 22.871779] Under-voltage detected! (0x00050005) Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable to wake up Vantage console () Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: Unable to wake up Vantage console Jan 29 09:44:54 raspberrypi weewx[495]: Exiting... Jan 29 09:45:00 raspberrypi kernel: [ 31.191813] Voltage normalised (0x) Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server 103.106.66.123 Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 202.46.185.18 Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 130.217.226.51 Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 203.99.128.34 Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.177.18 Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.178.18 Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 103.106.65.219 Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 2407:f100:0:4::3 Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 202.46.179.18 Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin timestamp 0xdff9e880.d9ce150e does not match aorg 00. from server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9 Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 37min 9.646374s random time. Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min 10.183019s random time. On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote: > > On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote: >> >> I have replaced the power unit, taken it off the power strip an plugged >> both it and the Vanatage into the mains. I have replaced the powered hub >> (official RPi one...with another official RPi one) ...and here is what I am >> getting...very dispirited! I have another Davis Weather Envoy which I >> will soon substitute for the one I am currently using.but nothing seems >> to make a difference and the Envoy just will not wake up! >> >> >> > Still sounds like you have insufficient power to me. > You might try measuring it. > > > https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption > > (there are many such devices) > -- 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: Getting the RPi 3 with Davis Vantage up and running
an 29 09:35:16 raspberrypi ntpd[467]: 103.106.65.219 local addr 10.1.1.7 -> Jan 29 09:38:17 raspberrypi kernel: [ 1316.645409] rpi_firmware_get_throttled: 12 callbacks suppressed Jan 29 09:38:17 raspberrypi kernel: [ 1316.645416] Under-voltage detected! (0x00050005) Jan 29 09:38:26 raspberrypi kernel: [ 1324.965452] rpi_firmware_get_throttled: 12 callbacks suppressed Jan 29 09:38:26 raspberrypi kernel: [ 1324.965457] Voltage normalised (0x) Jan 29 09:38:28 raspberrypi kernel: [ 1327.045547] Under-voltage detected! (0x00050005) Jan 29 09:38:32 raspberrypi kernel: [ 1331.205544] Voltage normalised (0x) Jan 29 09:38:36 raspberrypi kernel: [ 1335.365722] Under-voltage detected! (0x00050005) Jan 29 09:38:55 raspberrypi kernel: [ 1354.085857] Voltage normalised (0x) On Tuesday, 29 January 2019 08:51:01 UTC+13, vince wrote: > > On Monday, January 28, 2019 at 11:34:08 AM UTC-8, monmul wrote: >> >> I do have a spare official power supply, so I will swap out that and >> test. ... I have a Pi3B+ on the way >> > > Reminder, the pi3b+ need 'more' power and runs a little hotter than the > others, so definitely be certain you have a quality power supply. > > I have had great luck with > https://www.amazon.com/CanaKit-Raspberry-Power-Supply-Listed/dp/B07BC6WH7V > just as one example. Also like the nice on/off switch dongle that came > with it. > -- 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: Getting the RPi 3 with Davis Vantage up and running
Apologies, you may well be right...it seems the most obvious culprit now! I don't have an RTC attached to my RPias I was told (much earlier in this thread) that the software changes I made to the resolv.conf files would suffice. On Tuesday, 29 January 2019 00:32:59 UTC+13, Andrew Milner wrote: > > I beg to differ regarding the voltage issue. If your RPi is suffering > from voltage going out of spec as the log implies then this will almost > definitely result in corruption over usb and possibly on the memory card > also. Any corruptions can then result in timestamp issues. Do you also > have a RTC installed on the RPi - this is almost an essential item. The > times on the RPi and the Vantage must remain almost in sync for things to > work seamlessly. If the volyage issue causes a reboot, for example, it is > possible for the rpi to get an erroneous time for a period which could > either get written to the database or prevent satisfactory restart and > catchup from the vantage befpre resuming normal operations. > > I'm sorry but I still think you need to solve the voltage issue first and > ensure that is 100% stable before starting to chase other issues such as > time stamps. I can virtually guarantee the issues you see are most > unlikely to be a result of anything wrong within weewx itself - and > especially with a Davis Vantage for which weewx was originally developed > many moons ago. > > > > > On Monday, 28 January 2019 12:08:56 UTC+2, monmul wrote: >> >> Thank you, yesbut where will I find this log that I needas in >> which folder and what will it be called? >> >> On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote: >>> >>> Hi, >>> >>> Yep the logs are your friend. Usually you are interested in what >>> happened in the lead up to the event. You mentioned 19:20 but your log >>> extract is from around 21:44, what do the logs show around 19:20? Try and >>> find the point where WeeWX exited and work backwards from time there, may 5 >>> or 10 minutes. The log extract you posted showed an issue at 21:44:02 but >>> there is only one unrelated entry before that, what else is in the log in >>> the lead up to 21:44:02? Maybe paste the log from reboot until error. >>> >>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
No, Vantage has its own power supply. On Tuesday, 29 January 2019 06:01:14 UTC+13, vince wrote: > > > On Monday, January 28, 2019 at 1:56:14 AM UTC-8, monmul wrote: >> >> To be honest, I don't think it is the voltage problemI think it is a >> time stamp problem, I had to go through the whole --dump and -- >> clear-memory again to get reporting restarted.less than a week since >> this last happened! >> >> >> > Are you perhaps powering your Davis console off the same USB hub ? > -- 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: Getting the RPi 3 with Davis Vantage up and running
I do have a spare official power supply, so I will swap out that and test. I notice that after doing the -dump (after stopping weewx) and --clear-memory routine and then reboot, that the missing data does not appear in the graphs! The official power units supplies the official USB hub with power and the Pi is powered from this USB hub. The Vantage, which has its own power supply and battery backup) sends the data through the USB hub to the Pi..I have tried connecting it directly to the Pi also...does not seem to make any difference. I have a Pi3B+ on the way, so I can swap out the current SD card and try it in that.Nothing else, apart from a USB (for back up purposes via Deja Dup). I am running the power from a socket strip..so might try plugging the Pi directly into the mains. On Monday, 28 January 2019 23:41:14 UTC+13, gjr80 wrote: > > Hmm, not too much to pinpoint the culprit there. Could it be a power > supply issue, of course, official power supply or not it could still be the > culprit. You could check the output with a meter but will unlikely show any > transient fluctuations that could be causing a problem. Worth doing if you > can though. Swapping out the power supply or RPi itself is probably not > feasible unless you happen to have a spare. > > Could be an issue with the logger, can help by reseating it/making sure it > is inserted securely. Could be power to your console (you have an envoy if > I remember correctly), what is your mains like? Do you have an UPS from > which you can power both RPi and station. > > What is plugged into the RPi, powered hub, keyboard? monitor? Might sound > odd but can you run without the hub and plug the station into the RPi > direct. Are there any long cable runs, obvious one to look at is 5V to the > RPi but if that is the official power supply probably not much to be done > there. > > Sorry these are all a bit woolly but these sorts of issues can be > difficult to nail down. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank youI did not understand that is what I was doing..here from 19.10 last good report to when the next report was expected. Jan 28 19:10:19 raspberrypi weewx[531]: manager: Added record 2019-01-28 19:10:00 NZDT (1548655800) to database 'weewx.sdb' Jan 28 19:10:19 raspberrypi weewx[531]: manager: Added record 2019-01-28 19:10:00 NZDT (1548655800) to daily summary in 'weewx.sdb' Jan 28 19:10:19 raspberrypi weewx[531]: restx: Wunderground-PWS: Published record 2019-01-28 19:10:00 NZDT (1548655800) Jan 28 19:10:20 raspberrypi weewx[531]: cheetahgenerator: Generated 15 files for report StandardReport in 1.65 seconds Jan 28 19:10:21 raspberrypi weewx[531]: imagegenerator: Generated 12 images for StandardReport in 0.88 seconds Jan 28 19:10:21 raspberrypi weewx[531]: copygenerator: copied 0 files to /var/www/html/weewx Jan 28 19:10:21 raspberrypi weewx[531]: cheetahgenerator: Generated 1 files for report xstats in 0.04 seconds Jan 28 19:10:27 raspberrypi weewx[531]: ftpgenerator: ftp'd 28 files in 5.27 seconds Jan 28 19:12:01 raspberrypi kernel: [6.033449] rpi_firmware_get_throttled: 1 callbacks suppressed Jan 28 19:12:01 raspberrypi kernel: [6.033457] Under-voltage detected! (0x00050005) Jan 28 19:12:07 raspberrypi kernel: [77782.273481] rpi_firmware_get_throttled: 1 callbacks suppressed Jan 28 19:12:07 raspberrypi kernel: [77782.273487] Voltage normalised (0x) Jan 28 19:13:08 raspberrypi vncserver-x11[465,root]: Connections: disconnected: 10.1.1.155::33538 (TCP) ([IdleTimeout] This connection has timed out through inactivity.) Jan 28 19:15:53 raspberrypi weewx[531]: vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead Jan 28 19:16:00 raspberrypi kernel: [78015.235265] Under-voltage detected! (0x00050005) Jan 28 19:16:06 raspberrypi kernel: [78021.475297] Voltage normalised (0x) Jan 28 19:16:09 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:16:09 raspberrypi weewx[531]: vantage: LOOP try #2; error: Unable to wake up Vantage console Jan 28 19:16:25 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:16:25 raspberrypi weewx[531]: vantage: LOOP try #3; error: Unable to wake up Vantage console Jan 28 19:16:41 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:16:41 raspberrypi weewx[531]: vantage: LOOP try #4; error: Unable to wake up Vantage console Jan 28 19:16:41 raspberrypi weewx[531]: vantage: LOOP max tries (4) exceeded. Jan 28 19:16:41 raspberrypi weewx[531]: engine: Shutting down StdReport thread Jan 28 19:16:41 raspberrypi weewx[531]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. Jan 28 19:16:41 raspberrypi weewx[531]: Waiting 60 seconds then retrying... Jan 28 19:17:01 raspberrypi CRON[10729]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jan 28 19:17:41 raspberrypi weewx[531]: engine: retrying... Jan 28 19:17:41 raspberrypi weewx[531]: engine: Using configuration file /etc/weewx/weewx.conf Jan 28 19:17:41 raspberrypi weewx[531]: engine: Loading station type Vantage (weewx.drivers.vantage) Jan 28 19:17:57 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:17:57 raspberrypi weewx[531]: import of driver failed: Unable to wake up Vantage console () Jan 28 19:17:57 raspberrypi weewx[531]: engine: Unable to load driver: Unable to wake up Vantage console Jan 28 19:17:57 raspberrypi weewx[531]: Exiting... Jan 28 19:23:12 raspberrypi kernel: [78447.878557] Under-voltage detected! (0x00050005) Jan 28 19:23:19 raspberrypi kernel: [78454.118624] Voltage normalised (0x) Jan 28 19:24:50 raspberrypi kernel: [78545.639346] Under-voltage detected! (0x00050005) Jan 28 19:24:54 raspberrypi kernel: [78549.799434] Voltage normalised (0x) Jan 28 19:40:26 raspberrypi kernel: [79481.646371] Under-voltage detected! (0x00050005) Jan 28 19:40:32 raspberrypi kernel: [79487.886450] Voltage normalised (0x) On Monday, 28 January 2019 23:11:24 UTC+13, gjr80 wrote: > > We you tailed it here: > > > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog > > /var/log/syslog might be a good place to look :) > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank you, yesbut where will I find this log that I needas in which folder and what will it be called? On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote: > > Hi, > > Yep the logs are your friend. Usually you are interested in what happened > in the lead up to the event. You mentioned 19:20 but your log extract is > from around 21:44, what do the logs show around 19:20? Try and find the > point where WeeWX exited and work backwards from time there, may 5 or 10 > minutes. The log extract you posted showed an issue at 21:44:02 but there > is only one unrelated entry before that, what else is in the log in the > lead up to 21:44:02? Maybe paste the log from reboot until error. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
How can I find our (from the logs I presume) what caused the Pi to go down in the first place after running well for 2 or 3 days? On Monday, 28 January 2019 22:23:41 UTC+13, monmul wrote: > > I am using a powered hub and I am using the official RPi power source. > > On Mon, Jan 28, 2019 at 10:05 PM Andrew Milner < > andrew.s.r.mil...@gmail.com> wrote: > >> I would suggest you work on eliminating the under voltage errors before >> trying to work out why you cannot communicate with the weather station. >> The implication is that the RPi is having trouble coping with whatever you >> have got connected via usb and/or network. This is not unusual and >> indicates you may need either a larger power supply or a powered usb hub to >> cope with your usb loads. >> >> >> >> On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote: >>> >>> My Pi stopped reporting at 19.20 today and despite rebooting twice, it >>> does not seem to be able to wake up the console..is there a way/log I >>> can query to find out why it might have stopped at 19.10it was working >>> fine for 2 or 3 days. Here is the syslog... >>> >>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>> Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available >>> Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up >>> console >>> Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable >>> to wake up Vantage console () >>> Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: >>> Unable to wake up Vantage console >>> Jan 28 21:44:02 raspberrypi weewx[510]: Exiting... >>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: >>> connected: 10.1.1.155::40108 (TCP) >>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: >>> authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions) >>> Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: >>> Failed to add printer: server-error-service-unavailable >>> Jan 28 21:44:04 raspberrypi kernel: [ 27.031827] Under-voltage >>> detected! (0x00050005) >>> Jan 28 21:44:10 raspberrypi kernel: [ 33.271789] Voltage normalised >>> (0x) >>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>> 88.191.250.97 >>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4 >>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>> 103.106.66.123 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 103.106.65.219 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 203.159.70.33 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 103.242.70.5 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 203.86.206.43 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 103.242.70.4 >>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>> 185.242.56.3 >>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>> 103.242.68.69 >>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>> 130.217.226.49 >>> Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server >>> 122.252.188.99 >>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>> 202.78.240.38 >>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>> 202.46.179.18 >>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>> 2407:f100:0:1::2 >>> Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server >>> 130.217.226.51 >>> Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed >>> Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed >>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min >>> 19.972590s random time. >>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >>> 37min 57.400920s random time. >>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin >>> timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from >>> ser...@203.159.70.33 xmt 0xdff93f94.5a13b23a >>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin >>> timestamp 0xdff93f8c.e1319bed does not match aorg 00. from >>> ser...@37.187.18.4 xmt
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
My Pi stopped reporting at 19.20 today and despite rebooting twice, it does not seem to be able to wake up the console..is there a way/log I can query to find out why it might have stopped at 19.10it was working fine for 2 or 3 days. Here is the syslog... pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up console Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable to wake up Vantage console () Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: Unable to wake up Vantage console Jan 28 21:44:02 raspberrypi weewx[510]: Exiting... Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: connected: 10.1.1.155::40108 (TCP) Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions) Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable Jan 28 21:44:04 raspberrypi kernel: [ 27.031827] Under-voltage detected! (0x00050005) Jan 28 21:44:10 raspberrypi kernel: [ 33.271789] Voltage normalised (0x) Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 88.191.250.97 Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4 Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 103.106.66.123 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.106.65.219 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.159.70.33 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.5 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.86.206.43 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.4 Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 185.242.56.3 Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 103.242.68.69 Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 130.217.226.49 Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server 122.252.188.99 Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.78.240.38 Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.46.179.18 Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 2407:f100:0:1::2 Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server 130.217.226.51 Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min 19.972590s random time. Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 37min 57.400920s random time. Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from server@203.159.70.33 xmt 0xdff93f94.5a13b23a Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin timestamp 0xdff93f8c.e1319bed does not match aorg 00. from server@37.187.18.4 xmt 0xdff93f94.62dbcbad Jan 28 21:47:56 raspberrypi kernel: [ 251.674064] Under-voltage detected! (0x00050005) Jan 28 21:48:02 raspberrypi kernel: [ 257.914050] Voltage normalised (0x) On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote: > > Not a problem, you pointed me in the right direction which was all I > needed..thanks again! > > On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote: >> >> My apologies if I lead you astray, I did mentioning dumping but did not >> list the command. Was out at the time and on the mobile. >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Not a problem, you pointed me in the right direction which was all I needed..thanks again! On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote: > > My apologies if I lead you astray, I did mentioning dumping but did not > list the command. Was out at the time and on the mobile. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank you both for your help.I seem to be up and running now without any hitches apart from some lost data. Thanks again, I will know what to do now if happens again. On Saturday, 26 January 2019 15:04:13 UTC+13, Thomas Keffer wrote: > > The Envoy acts exactly like the regular Vantage console. > > On Fri, Jan 25, 2019 at 5:58 PM gjr80 > > wrote: > >> Ok, so archive records are being saved and pages being generated with >> current data? The log in your previous post still showed an archive record >> being skipped at 13:20:00. >> >> Annoying to lose data but sometimes it happens, doing the dump before you >> do anything destructive dumps all of the archive records out of the logger >> and any that are not in your archive are saved to archive, any that are >> already in your archiv are ignored (well you get a duplicate key error). >> From my limited experience a dump tends to result in loss of maybe one or >> two records only unless something catastrophic has occurred. It seems that >> the archive record is still saved in the logger it just doesn't send it to >> WeeWX when weeWX asks for it. Having an envoy may be slightly different, I >> don't have one, Tom may be able to shed some more light on it. >> >> Not sure what you meant about deleting records. Did you mean your archive >> or the logger/envoy? As far as I know it's all or nothing in terms of >> clearing the logger/envoy. And you weren't getting any records into your >> archive. >> >> 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+...@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: Getting the RPi 3 with Davis Vantage up and running
OK, we are back up after wee-device --clear-memory. Lost 12 hours of data though.maybe should have tried deleting the records with time stamp older than X. On Saturday, 26 January 2019 13:42:56 UTC+13, monmul wrote: > > Another log after reboot. > > On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote: >> >> Here is 5 minutes of the console logis that long enough? I can do >> much longer if required? >> >> On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote: >>> >>> After removing batteries from Envoy console and unplugging itand >>> then sudo reboot of Rpi this is what I get. >>> >>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>> Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available >>> Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up >>> console >>> Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable >>> to wake up Vantage console () >>> Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: >>> Unable to wake up Vantage console >>> Jan 26 12:14:50 raspberrypi weewx[494]: Exiting... >>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >>> connected: 10.1.1.155::38928 (TCP) >>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >>> authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions) >>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: >>> Failed to add printer: server-error-service-unavailable >>> Jan 26 12:14:54 raspberrypi kernel: [ 29.111831] Under-voltage >>> detected! (0x00050005) >>> Jan 26 12:15:01 raspberrypi kernel: [ 35.351863] Voltage normalised >>> (0x) >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 103.242.68.68 >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 103.239.8.22 >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 103.106.65.219 >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 202.78.240.38 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 103.242.68.69 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 203.86.206.43 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 202.46.185.18 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 202.46.177.18 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 202.46.179.18 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 203.99.128.34 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 2407:f100:0:4::3 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 203.99.128.48 >>> Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server >>> 130.217.226.51 >>> Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed >>> Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed >>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >>> timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from >>> server@103.239.8.22 xmt 0xdff6172a.80071bf6 >>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min >>> 59.082661s random time. >>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >>> timestamp 0xdff61722.e1af360e does not match aorg 00. from >>> server@202.46.185.18 xmt 0xdff6172a.80d85adc >>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >>> 27min 28.579939s random time. >>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >>> timestamp 0xdff61722.d7adc312 does not match aorg 00. from >>> server@130.217.226.51 xmt 0xdff6172a.7d37a242 >>> Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD ( cd / && run-parts >>> --report /etc/cron.hourly) >>> >>> Next should I try deleting future records as recommended in the >>> "generated but not updated" section of the user guide. >>> >>> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop >>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >>> pi@raspberrypi:~ $ sudo t
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Another log after reboot. On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote: > > Here is 5 minutes of the console logis that long enough? I can do much > longer if required? > > On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote: >> >> After removing batteries from Envoy console and unplugging itand then >> sudo reboot of Rpi this is what I get. >> >> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available >> Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console >> Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable >> to wake up Vantage console () >> Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: >> Unable to wake up Vantage console >> Jan 26 12:14:50 raspberrypi weewx[494]: Exiting... >> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >> connected: 10.1.1.155::38928 (TCP) >> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >> authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions) >> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: >> Failed to add printer: server-error-service-unavailable >> Jan 26 12:14:54 raspberrypi kernel: [ 29.111831] Under-voltage >> detected! (0x00050005) >> Jan 26 12:15:01 raspberrypi kernel: [ 35.351863] Voltage normalised >> (0x) >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >> 103.242.68.68 >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22 >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >> 103.106.65.219 >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >> 202.78.240.38 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 103.242.68.69 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 203.86.206.43 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 202.46.185.18 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 202.46.177.18 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 202.46.179.18 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 203.99.128.34 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 2407:f100:0:4::3 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 203.99.128.48 >> Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server >> 130.217.226.51 >> Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed >> Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed >> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >> timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from >> server@103.239.8.22 xmt 0xdff6172a.80071bf6 >> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min >> 59.082661s random time. >> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >> timestamp 0xdff61722.e1af360e does not match aorg 00. from >> server@202.46.185.18 xmt 0xdff6172a.80d85adc >> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >> 27min 28.579939s random time. >> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >> timestamp 0xdff61722.d7adc312 does not match aorg 00. from >> server@130.217.226.51 xmt 0xdff6172a.7d37a242 >> Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD ( cd / && run-parts >> --report /etc/cron.hourly) >> >> Next should I try deleting future records as recommended in the >> "generated but not updated" section of the user guide. >> >> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx >> version 3.8.2 >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 >> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform >> Linux-4.14.79-v7+-armv7l-with-debian-9.6 >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8' >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file >> /etc/weewx/weewx.conf
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
After removing batteries from Envoy console and unplugging itand then sudo reboot of Rpi this is what I get. pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable to wake up Vantage console () Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: Unable to wake up Vantage console Jan 26 12:14:50 raspberrypi weewx[494]: Exiting... Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: connected: 10.1.1.155::38928 (TCP) Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions) Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable Jan 26 12:14:54 raspberrypi kernel: [ 29.111831] Under-voltage detected! (0x00050005) Jan 26 12:15:01 raspberrypi kernel: [ 35.351863] Voltage normalised (0x) Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.68 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.106.65.219 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 202.78.240.38 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.69 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 203.86.206.43 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.185.18 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.177.18 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 202.46.179.18 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.34 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 2407:f100:0:4::3 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.48 Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server 130.217.226.51 Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from server@103.239.8.22 xmt 0xdff6172a.80071bf6 Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min 59.082661s random time. Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 0xdff61722.e1af360e does not match aorg 00. from server@202.46.185.18 xmt 0xdff6172a.80d85adc Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 27min 28.579939s random time. Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 0xdff61722.d7adc312 does not match aorg 00. from server@130.217.226.51 xmt 0xdff6172a.7d37a242 Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Next should I try deleting future records as recommended in the "generated but not updated" section of the user guide. pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx version 3.8.2 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform Linux-4.14.79-v7+-armv7l-with-debian-9.6 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8' Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file /etc/weewx/weewx.conf Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Loading station type Vantage (weewx.drivers.vantage) Jan 26 12:25:05 raspberrypi weewx[1810]: vantage: Unable to wake up console Jan 26 12:25:05 raspberrypi weewx[1810]: import of driver failed: Unable to wake up Vantage console () Jan 26 12:25:05 raspberrypi weewx[1810]: engine: Unable to load driver: Unable to wake up Vantage console Jan 26 12:25:05 raspberrypi weewx[1810]: Exiting... Jan 26 On Saturday, 26 January 2019 11:51:41 UTC+13, gjr80 wrote: > > Yes, you appear to be getting loop packets. Corrupt station memory usually > results in loop packets continuing to come through but there are no archive > records coming from the logger. If you are using hardware record generation > then WeeWX gets no archive records, nothing is saved to database but > reports are still generated and anything 'loop based' still goes on. The > proof will be a longer console output (are there any archive records?) or a > longer log extract. > > If corrupt station
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
5,1V 2.5A - the official RPi power unit! On Saturday, 26 January 2019 11:42:00 UTC+13, Dave Webb wrote: > > What size power supply are using? Try at least a 2amp unit. > > Dave-KB1PVH > > > Sent from my Galaxy S9 > > On Fri, Jan 25, 2019, 5:22 PM monmul > wrote: > >> I seem to be getting a lot of these voltage issuesI am using the Rpi >> official power pack!! >> Jan 26 11:15:00 raspberrypi systemd[1]: Starting Cleanup of Temporary >> Directories... >> Jan 26 11:15:00 raspberrypi systemd[1]: Started Cleanup of Temporary >> Directories. >> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644829] >> rpi_firmware_get_throttled: 6 callbacks suppressed >> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644836] Under-voltage >> detected! (0x00050005) >> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804876] >> rpi_firmware_get_throttled: 6 callbacks suppressed >> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804883] Voltage normalised >> (0x) >> Jan 26 11:17:01 raspberrypi CRON[1883]: (root) CMD ( cd / && run-parts >> --report /etc/cron.hourly) >> Jan 26 11:17:03 raspberrypi kernel: [ 1052.485382] Under-voltage >> detected! (0x00050005) >> Jan 26 11:17:08 raspberrypi kernel: [ 1056.645441] Voltage normalised >> (0x) >> Jan 26 11:18:29 raspberrypi kernel: [ 1137.766503] Under-voltage >> detected! (0x00050005) >> Jan 26 11:18:35 raspberrypi kernel: [ 1144.006449] Voltage normalised >> (0x) >> >> >> >> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote: >>> >>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis >>> Vantage weather station. I have a serial Envoy data logger attaced to my >>> Rpi with a serial/usb converter. In following the set up instructions, I >>> get these errors! >>> >>> sudo weewxd weewx.conf >>> Traceback (most recent call last): >>> File "/usr/bin/weewxd", line 64, in >>> weewx.engine.main(options, args) >>> File "/usr/share/weewx/weewx/engine.py", line 835, in main >>> sane = os.stat(config_path).st_ctime >>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf' >>> pi@Weatherpi:~ $ tail -f /var/log/syslog >>> Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: >>> sender=:1.16 path=/MediaEndpoint/A2DPSink >>> Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available >>> Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available >>> Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed >>> Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed >>> Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Sun Jan 6 13:41:35 2019 [try >>> http://www.rsyslog.com/e/2007 ] >>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx >>> version 3.8.2 >>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 >>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2] >>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform >>> Linux-4.9.35-v7+-armv7l-with-debian-8.0 >>> Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8' >>> Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary >>> Directories... >>> Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Sun Jan 6 13:53:04 2019 [try >>> http://www.rsyslog.com/e/2007 ] >>> Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary >>> Directories. >>> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group >>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] >>> Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, >>> next retry is Sun Jan 6 13:55:58 2019 [try >>> http://www.rsyslog.com/e/2007 ] >>> Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group >>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] >>> >>> Please where have I gone wrong? >>> >>> >>> . >>> >>> Hi, >>> >>> It appears that you are in the /home/pi directory and hence weewxd is >>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie: >>> >>> $ sudo weewxd /etc/weewx/weewx.conf >>> >>> 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+...@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: Getting the RPi 3 with Davis Vantage up and running
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf LOOP: 2019-01-26 11:35:35 NZDT (1548455735) appTemp: 61.9209615592, barometer: 29.7, cloudbase: 4921.41993274, consBatteryVoltage: 3.02, dateTime: 1548455735, dayET: 0.0, dayRain: 0.031496063, dewpoint: 47.665752296, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 3, forecastRule: 163, heatindex: 64.7, humidex: 65.9643612986, inDewpoint: 47.0050615695, inHumidity: 43.0, insideAlarm: 0, inTemp: 70.6, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 2.6929133865, outHumidity: 54.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 64.7, rain: None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.031496063, stormStart: 1548414000, sunrise: 1548432420, sunset: 1548485400, trendIcon: -60, txBatteryStatus: 0, usUnits: 1, windchill: 64.7, windDir: 139.0, windGust: 4.0, windGustDir: 139.0, windSpeed: 4.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 35.4724409537 LOOP: 2019-01-26 11: Well that appears to be working! On Saturday, 26 January 2019 11:24:16 UTC+13, gjr80 wrote: > > You can run WeeWX directly ( > http://weewx.com/docs/usersguide.htm#Running_directly) to see loop and > archive data on screen. The other thing to do is look at the logs over at > least a few archive periods, you will likely see reports being run but no > data being saved to archive. Quite possibly you have corrupt station > memory, especially if you have had a mains power outage, have a read > through this > http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated > > 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: Getting the RPi 3 with Davis Vantage up and running
Is there a way to see whether the data is getting through from the Vantage to weewx, my Rpi has not undated the skins or WU since last night. I have tested all connectionsthere seems to be ftp happeningbut nothing gets updated!! On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote: > > I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis > Vantage weather station. I have a serial Envoy data logger attaced to my > Rpi with a serial/usb converter. In following the set up instructions, I > get these errors! > > sudo weewxd weewx.conf > Traceback (most recent call last): > File "/usr/bin/weewxd", line 64, in > weewx.engine.main(options, args) > File "/usr/share/weewx/weewx/engine.py", line 835, in main > sane = os.stat(config_path).st_ctime > OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf' > pi@Weatherpi:~ $ tail -f /var/log/syslog > Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: > sender=:1.16 path=/MediaEndpoint/A2DPSink > Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available > Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available > Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed > Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed > Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:41:35 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version > 3.8.2 > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 > (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2] > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform > Linux-4.9.35-v7+-armv7l-with-debian-8.0 > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8' > Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary > Directories... > Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:53:04 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary > Directories. > Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying > completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] > Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:55:58 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying > completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] > > Please where have I gone wrong? > > > . > > Hi, > > It appears that you are in the /home/pi directory and hence weewxd is > looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie: > > $ sudo weewxd /etc/weewx/weewx.conf > > 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: Getting the RPi 3 with Davis Vantage up and running
Jan 26 11:07:46 raspberrypi kernel: [ 495.038468] Voltage normalised (0x) Jan 26 11:07:48 raspberrypi kernel: [ 497.118527] Under-voltage detected! (0x00050005) Jan 26 11:08:15 raspberrypi kernel: [ 524.158906] Voltage normalised (0x) Jan 26 11:10:31 raspberrypi ntpd[461]: 202.78.240.38 local addr 10.1.1.7 -> Jan 26 11:10:33 raspberrypi weewx[501]: cheetahgenerator: Generated 15 files for report StandardReport in 11.88 seconds Jan 26 11:10:35 raspberrypi weewx[501]: imagegenerator: Generated 12 images for StandardReport in 1.65 seconds Jan 26 11:10:35 raspberrypi weewx[501]: copygenerator: copied 9 files to /var/www/html/weewx Jan 26 11:10:35 raspberrypi weewx[501]: cheetahgenerator: Generated 1 files for report xstats in 0.17 seconds Jan 26 11:10:42 raspberrypi weewx[501]: ftpgenerator: ftp'd 37 files in 6.99 seconds On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote: > > I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis > Vantage weather station. I have a serial Envoy data logger attaced to my > Rpi with a serial/usb converter. In following the set up instructions, I > get these errors! > > sudo weewxd weewx.conf > Traceback (most recent call last): > File "/usr/bin/weewxd", line 64, in > weewx.engine.main(options, args) > File "/usr/share/weewx/weewx/engine.py", line 835, in main > sane = os.stat(config_path).st_ctime > OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf' > pi@Weatherpi:~ $ tail -f /var/log/syslog > Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: > sender=:1.16 path=/MediaEndpoint/A2DPSink > Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available > Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available > Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed > Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed > Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:41:35 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version > 3.8.2 > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 > (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2] > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform > Linux-4.9.35-v7+-armv7l-with-debian-8.0 > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8' > Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary > Directories... > Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:53:04 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary > Directories. > Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying > completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] > Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:55:58 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying > completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] > > Please where have I gone wrong? > > > . > > Hi, > > It appears that you are in the /home/pi directory and hence weewxd is > looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie: > > $ sudo weewxd /etc/weewx/weewx.conf > > 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: Getting the RPi 3 with Davis Vantage up and running
It would appear (from comparing the data to the gust speed actually occurring) that, despite the wind speed recorder operating on a real time basis, the record of the gust speed is the speed when the set reading interval occurs rather than the max speed during the time between "official" readings. Is this the case? Is there a way I can get the live gust speed? On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote: > > I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis > Vantage weather station. I have a serial Envoy data logger attaced to my > Rpi with a serial/usb converter. In following the set up instructions, I > get these errors! > > sudo weewxd weewx.conf > Traceback (most recent call last): > File "/usr/bin/weewxd", line 64, in > weewx.engine.main(options, args) > File "/usr/share/weewx/weewx/engine.py", line 835, in main > sane = os.stat(config_path).st_ctime > OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf' > pi@Weatherpi:~ $ tail -f /var/log/syslog > Jan 6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: > sender=:1.16 path=/MediaEndpoint/A2DPSink > Jan 6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available > Jan 6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available > Jan 6 13:37:57 Weatherpi systemd[852]: Time has been changed > Jan 6 13:37:57 Weatherpi systemd[1]: Time has been changed > Jan 6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:41:35 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version > 3.8.2 > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 > (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2] > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Platform > Linux-4.9.35-v7+-armv7l-with-debian-8.0 > Jan 6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8' > Jan 6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary > Directories... > Jan 6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:53:04 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary > Directories. > Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying > completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] > Jan 6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, > next retry is Sun Jan 6 13:55:58 2019 [try http://www.rsyslog.com/e/2007 > ] > Jan 6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying > completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP] > > Please where have I gone wrong? > > > . > > Hi, > > It appears that you are in the /home/pi directory and hence weewxd is > looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie: > > $ sudo weewxd /etc/weewx/weewx.conf > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
AwesomeI thought that weeimport could only deal with csv files and so went and converted them allbut kept the txt files for backup! On Thursday, 17 January 2019 22:35:30 UTC+13, gjr80 wrote: > > Ok, that explains the csv file you provided having a different name > structure to what I had found. I believe that there was/is the ability for > WD to publish csv format log files and that is what I have. Weeimport will > happily work with the MMlg.txt files just as they are. No need to dig > anything out of an old machine. You will be the 1st so it will work with > your logs and I guess we see where it goes from there. Weeimport is fairly > flexible in structure and can easily be adapted. > > 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.
