Console displaying current data but no USB found

[tgilb...@gmail.com]

I've a Fine Offset WS3080 which was working fine with an earlier pywws version and a RaspberryPi B+ (aside from the occasional USB lockup).

I moved house and it was decomissioned for some months, but the weatherstation is setup again and working fine with current, reasonable, changing values to the console.

I've configured a RaspberryPi ZeroW with pywws 19.7.1 using Jim's Jottings and today updated to 20.1.0.  Unfortunately, both pywws (both versions) and EasyWeather on Windows, don't recognise data on the USB port.  Windows takes some time to go away and think and then reports "the device on your USB port is configured" or something similar, and it beeps to acknowledge that it knows that the USB connection stopped, once I disconnect, so the USB port is not TOTALLY dead, but here's my sudo pywws-testweatherstation -vvv output which suggests to me that the problem lies in the console somwhere.

pywws@chalk:/ $ sudo pywws-testweatherstation -vvvv

12:42:28:pywws.logger:pywws version 20.1.0, build 1673 (92d8868)

12:42:28:pywws.logger:Python version 3.5.3 (default, Jan 19 2017, 14:11:04)

[GCC 6.3.0 20170124]

12:42:28:pywws.weatherstation:using pywws.device_libusb1

Traceback (most recent call last):

  File "/usr/local/bin/pywws-testweatherstation", line 8, in <module>

    sys.exit(main())

  File "/usr/local/lib/python3.5/dist-packages/pywws/testweatherstation.py", line 117, in main

    ws = pywws.weatherstation.WeatherStation()

  File "/usr/local/lib/python3.5/dist-packages/pywws/weatherstation.py", line 464, in __init__

    self.cusb = CUSBDrive()

  File "/usr/local/lib/python3.5/dist-packages/pywws/weatherstation.py", line 318, in __init__

    self.dev = USBDevice(0x1941, 0x8021)

  File "/usr/local/lib/python3.5/dist-packages/pywws/device_libusb1.py", line 79, in __init__

    raise IOError("Weather station device not found")

OSError: Weather station device not found

I've disconnected the power (both USB and battery removal) overnight without success and then I've done a factory reset (hold down the "up" key for 20+ seconds) but my outcome is unchanged.

I'm able to scroll through valid history records on the console SINCE the factory reset, so the data is being recorded in the console, just not accessible via USB currently.

So, bottom line, should I persist or replace?   There's been no rough treatment so I can't imagine what could go wrong with a USB port short of physical damage.

Cheers,

Tony

PS   - I see reference in the docs to a script called USBQualityTest.py but can't find it anywhere on my system, although I'm guessing it might be pointless until the device is found anyhow?

[Jim Easterbrook]

On 02/01/2021 06:12, tgilb...@gmail.com wrote:
>
> I've configured a RaspberryPi ZeroW with pywws 19.7.1 using Jim's
> Jottings and today updated to 20.1.0.  Unfortunately, both pywws (both
> versions) and EasyWeather on Windows, don't recognise data on the USB
> port.  Windows takes some time to go away and think and then reports
> "the device on your USB port is configured" or something similar, and it
> beeps to acknowledge that it knows that the USB connection stopped, once
> I disconnect, so the USB port is not TOTALLY dead, but here's my sudo
> pywws-testweatherstation -vvv output which suggests to me that the
> problem lies in the console somwhere.

> "/usr/local/lib/python3.5/dist-packages/pywws/weatherstation.py", line
> 318, in __init__
>     self.dev = USBDevice(0x1941, 0x8021)
>   File
> "/usr/local/lib/python3.5/dist-packages/pywws/device_libusb1.py", line
> 79, in __init__
>     raise IOError("Weather station device not found")
> OSError: Weather station device not found

'lsusb' is the Linux command to list all detected USB devices - the
weather station has ID 1941:8021

You could also use 'dmesg' to look at system messages just after
plugging in the station. It should show the USB device being detected.

Windows I wouldn't know anything about.

> So, bottom line, should I persist or replace?   There's been no rough
> treatment so I can't imagine what could go wrong with a USB port short
> of physical damage.

Try it on another computer (all you need is lsusb) to see if it really
is dead.

> PS   - I see reference in the docs to a script called USBQualityTest.py
> but can't find it anywhere on my system, although I'm guessing it might
> be pointless until the device is found anyhow?

It still exists, but is now called usbtest.py It's not useful in your
circumstances though.
https://github.com/jim-easterbrook/pywws/blob/master/src/pywws/usbtest.py

--
Jim Easterbrook <http://www.jim-easterbrook.me.uk/>

[tgilb...@gmail.com]

Thanks Jim.  I was able - eventually - to prove the console worked on another rPi, but to do that, I had to use a different cable (due to micro USB on Pi zeroW but USB-A on other Pis).

Turns out, FOUR different cables failed to give me WS3080 USB-detection (via lsusb) on the Pi Zero W.  But eventually, a weird converter that I've had for years makes the weatherstation recognizable.  I haven't yet proven what is the difference between the one that works and the other four that don't although I *think* I've tried two OTG and two "traditional" cables that have all failed.   Nonetheless, I'm recording data and if I discover what's different between the working and non-working cables, I'll post again.

pywws@chalk:~ $ pywws-testweatherstation

12:02:29:pywws.logger:pywws version 20.1.0, build 1673 (92d8868)

0000 55 aa ff ff ff ff 10 01 01 12 00 10 01 01 12 00 1e 20 02 20 09 00 00 00 00 00 00 be 00 18 c4 0f

0020 f7 27 5a 27 00 00 00 00 00 00 00 10 01 05 10 48 41 23 c8 00 00 00 46 2d 2c 01 64 80 c8 00 00 00

0040 64 00 64 80 a0 28 80 25 a0 28 80 25 00 b4 00 00 68 01 00 0a 00 f4 01 12 00 c0 c6 2d 0a ff ff ff

0060 ff 00 49 32 61 1b 0d 01 ad 00 42 01 82 00 42 01 82 00 d8 00 64 00 5e 27 af 26 fb 27 4c 27 0a 00

0080 18 00 18 00 18 00 18 00 00 00 21 00 00 10 01 04 11 41 10 01 01 13 48 10 01 02 10 12 10 01 01 13

00a0 45 10 01 01 13 48 10 01 05 08 08 10 01 02 14 31 10 01 05 05 20 10 01 02 14 31 10 01 05 05 20 10

00c0 01 02 12 06 10 01 01 13 45 10 01 05 09 40 10 01 02 16 36 10 01 05 09 40 10 01 02 16 36 10 01 01

00e0 14 04 10 01 01 12 16 10 01 02 00 00 10 01 02 00 00 10 01 03 00 00 10 01 01 12 00 10 01 05 06 20

Cheers,

Tony

[Jim Easterbrook]

On 06/01/2021 03:23, tgilb...@gmail.com wrote:
> Thanks Jim.  I was able - eventually - to prove the console worked on
> another rPi, but to do that, I had to use a different cable (due to
> micro USB on Pi zeroW but USB-A on other Pis).
>
> Turns out, FOUR different cables failed to give me WS3080 USB-detection
> (via lsusb) on the Pi Zero W.

The "OTG" USB port on Pi Zeros is a bit weird. On mine I had to stop it
switching to client mode after 5 seconds of inactivity by setting
dtoverlay=dwc2,dr_mode=host in /boot/config.txt. I wonder if yours is
defaulting to client mode and then not seeing the weather station for
some reason.

[Tony Gilbert]

Thanks Jim,  but I already followed your sage advice and made this mod a year ago in an initial attempt that got put on hold, although I am now wondering if this should be on two separate  Iines without the comma or if the space after the comma  is making any difference but I suspect it's to do with the cable rather than the port.

>[config.txt]

>[...]

># From Jim's Jottings via [me] to fix the USB port in "host" mode for pywws.  

># 19-DEC-2019

>

>    dtoverlay=dwc2, dr_mode=host

I own almost every model of pi and this definitely seems to be specific to that OTG port on the Zero W although I haven't tested on all models. 

Interestingly, in the 3080's last working config, say ~2018 on a model 3b (maybe), I used a right-angle USB A cable from the console to a micro USB plug (to get it through a small hole into a cabinet), and THEN a little female-micro-USB to male-USB-A converter (smaller than matchbox-size) into the model 3.  The only difference in hardware now WAS that I removed the little converter and - using the same cable as previously - connected to a Zero W, but that does not work.  To get it working, I'm again using an OTG converter (this time converting F-A to M-micro) connected to a regular USB A-A cable.  Seems like I'll need to do more learning about OTG cables/converters if I'm to understand,  but I may just leave "well enough alone".

Thanks for your help. 

--
You received this message because you are subscribed to the Google Groups "pywws" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pywws+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pywws/0131784b-d093-5c1d-56ff-09af7adba3bc%40jim-easterbrook.me.uk.