I have not had time to do the reseating yet....hopefully 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 etc....I 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 <dunb...@gmail.com> wrote: >>>> >>>>> Neither TEST nor NVER returns anything....so, I guess I have a >>>>> connectivity problem....which 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 <enter> 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 <dunb...@gmail.com> 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 <dunb...@gmail.com> 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 (<class >>>>>>>>>>> '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[DRIVER_NAME]) >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line >>>>>>>>>>> 515, in >>>>>>>>>>> __init__ >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** self._setup() >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line >>>>>>>>>>> 1317, in >>>>>>>>>>> _setup >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** self.port.wakeup_console(max_tries=self.max_tries) >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** File "/usr/share/weewx/weewx/drivers/vantage.py", line >>>>>>>>>>> 118, in >>>>>>>>>>> wakeup_console >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** raise weewx.WakeupError("Unable to wake up Vantage >>>>>>>>>>> console") >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: >>>>>>>>>>> **** WakeupError: Unable to wake up Vantage console >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL __main__: Unable >>>>>>>>>>> to load driver: Unable to wake up Vantage console >>>>>>>>>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL __main__: >>>>>>>>>>> **** Exiting... >>>>>>>>>>> Feb 26 16:31:50 WeatherPi dhcpcd[372]: wlan0: Router >>>>>>>>>>> Advertisement from fe80::724f:57ff:feb7:82a1 >>>>>>>>>>> Feb 26 16:31:50 WeatherPi dhcpcd[372]: wlan0: soliciting a >>>>>>>>>>> DHCPv6 lease >>>>>>>>>>> Feb 26 16:31:58 WeatherPi dhcpcd[372]: wlan0: Router >>>>>>>>>>> Advertisement from fe80::724f:57ff:feb7:82a1 >>>>>>>>>>> Feb 26 16:31:58 WeatherPi dhcpcd[372]: wlan0: soliciting a >>>>>>>>>>> DHCPv6 lease >>>>>>>>>>> Feb 26 16:32:07 WeatherPi dhcpcd[372]: wlan0: Router >>>>>>>>>>> Advertisement from fe80::724f:57ff:feb7:82a1 >>>>>>>>>>> Feb 26 16:32:07 WeatherPi dhcpcd[372]: wlan0: soliciting a >>>>>>>>>>> DHCPv6 lease >>>>>>>>>>> Feb 26 16:32:15 WeatherPi dhcpcd[372]: wlan0: Router >>>>>>>>>>> Advertisement from fe80::724f:57ff: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 >>>>>>>>>>>>> pi 3809 11222 0 10:01 pts/1 00: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 <gjrod...@gmail.com> 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 >>>>>>>>>>>>>>> SSH....not 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 pi 6u 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+...@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 >>>>>>>>>>> >>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/73f28622-be3d-4e50-b6fa-644811a22b2bn%40googlegroups.com?utm_medium=email&utm_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+...@googlegroups.com. >>>>>>> >>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/weewx-user/2c9f4cbf-dfb1-479e-ba2a-8220395d01can%40googlegroups.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/weewx-user/2c9f4cbf-dfb1-479e-ba2a-8220395d01can%40googlegroups.com?utm_medium=email&utm_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+...@googlegroups.com. >>>>> >>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/6782a2fa-7d0a-40ab-ac17-f3ed2890d018n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/weewx-user/6782a2fa-7d0a-40ab-ac17-f3ed2890d018n%40googlegroups.com?utm_medium=email&utm_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/e95e4c56-9997-4106-b8b9-4256b3b64219n%40googlegroups.com.
