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 (<class 'weewx.WakeupError'>)
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 [email protected] 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 <[email protected]> wrote:
>
>>
>> So everything reseated and restarted...unplugged USB to ensure that the 
>> Pi was seeing the USB......used "screen /dev/ttyUSB0 19200" after shutting 
>> down weewx....still 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 [email protected] 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 <[email protected]> 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 [email protected].
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/52535b0d-df10-4281-a5e8-420e8b84a701n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/52535b0d-df10-4281-a5e8-420e8b84a701n%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5bab4c8f-1bc4-46bd-9adf-6635547ad10fn%40googlegroups.com.

Reply via email to