Topic: new firmware for WS90: v1.3.0

[broadstairs]

From what has been said it sounds like the correct driver is not being found. Are there driver files in the zip file?

Stuart

[Gyvate]

the device (WS80/WS90) is only recognized once you reset the array after having established the USB connection
1. install the interface
2. select the Win10 64 bit driver
3. reboot the PC
4. connect the WS90 with USB
5. press the WS90 reset button for 5-10 seconds (the LED becomes constant blue)

[Gyvate]

one more thing
other cable alone may not be sufficient - it MUST be a data cable
the other cable may also be just another charging cable with only two wires connected.
How to find out ?
Connect to a data device (e.g. Smartphone with a mini-USB port - the new ones have USB-C, then you may need a converter) and see if is recognized by Windows. If you have a data cable, it will be recognized

[2thepoint]

the device (WS80/WS90) is only recognized once you reset the array after having established the USB connection
1. install the interface -installed/opened -dfuse_demo_v3.0.6._setup.exe/unistalled & reinstalled a number of times
2. select the Win10 64 bit driver - NEVER received an option to install driver (see attachment)
3. reboot the PC - rebooted after every install/uninstall
4. connect the WS90 with USB - tried a variety of usb cables, never once did my win 10 desktop recognize the WS90
5. press the WS90 reset button for 5-10 seconds (the LED becomes constant blue) -numerous resets, flashes blue (approx 2X per second) after pressing button for 5-10 seconds

I'm having a chronic problem updating my WS90.  I fall into the category of some other posters, "problems encountered".  My story......

-downloaded the firmware update package, WS90_v1.3.0 Firmware & Toolkit
-unzipped and extracted to a folder
-per the instructional pdf contained in the package, I ran dfuse_demo_v3.0.6_setup.exe and launched the app.  All fields were blank with NO options to select a device or add drivers.
-Device Manager - under "other devices" it shows STM32 Download Firmware that's disabled.  I tried manually installing a driver but came up dry after searching ALL relative folders.
-File Explorer  -no connectivity/recognition when WS90 was USB attached to my desktop.  Tried a variety of cables.  No new USB device was found.
-WS90 - reset depressed 5-10 seconds results in a flashing blue light, not a steady one.

The above process was repeated numerous times.  Uninstalling, rebooting, reinstalling, repeat over again.

I'm hoping one successful install folks in this forum can shed some light on the issue.  Is it me??  What haven't I tried?? 

Thanks,
Phil

machine: Win 10 /AMD 64bit

[Rocketman]

Make sure you’re using usb 3.0 type c data cable and make sure you have installed the drivers for win 10 ( have a look in all the folders and you should see driver for win 10 .
Once your install you should see a connection under usb in your device manager

[davidefa]

You didn't install the driver ( as the image you posted shows ).
In my case the driver are situated in:

Code: [Select]

C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10

[2thepoint]

Thanks for the replies... Didn't look in C:\Program Files (x86)\STMicroelectronics

Code: [Select]

C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10

Tried quite a few usb cables ........also have a 3.0 type c on order, arriving today.

Make sure you’re using usb 3.0 type c data cable and make sure you have installed the drivers for win 10 ( have a look in all the folders and you should see driver for win 10 .
Once your install you should see a connection under usb in your device manager

[Gyvate]

Make sure you’re using usb 3.0 type c data cable and make sure you have installed the drivers for win 10 ( have a look in all the folders and you should see driver for win 10 .
Once your install you should see a connection under usb in your device manager

usb 3.0 type c is misleading and wrong ! - these cables have a type C end piece and not the micro USB which is needed to connect to the WS90 - at least with my models.... - or you use a Type-c to micro USB adapter in addition

@2thepoint: sent you a PM ...

[BaseLine]

How to tell a USB charge-only cable from a USB data cable
https://www.dignited.com/50330/usb-data-cable-vs-usb-charging-cable/

(buy a cheap thin cable and you probably got a charger cable)

and here is a link for those who keep inventing their own terminology and USB cable types  https://en.wikipedia.org/wiki/USB_hardware

and USB-C
https://en.wikipedia.org/wiki/USB-C

[Gyvate]

How to tell a USB charge-only cable from a USB data cable
https://www.dignited.com/50330/usb-data-cable-vs-usb-charging-cable/

(buy a cheap thin cable and you probably got a charger cable)

and here is a link for those who keep inventing their own terminology and USB cable types  https://en.wikipedia.org/wiki/USB_hardware

and USB-C
https://en.wikipedia.org/wiki/USB-C

helpful/useful links
- and the WS90 needs a USB data cable with micro USB B plug (male) to insert into the device

[2thepoint]

You didn't install the driver ( as the image you posted shows ).
In my case the driver are situated in:

Code: [Select]

C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10

Windows isn't smart enough to detect the drivers with its search tool.  They were sitting in "C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10" doing nothing!!  Finally installed them from Device Manager.  Once the drivers loaded, the update to v1.3.0 was simple

Thanks everyone for the replies & the fix.

Phil

[Rocketman]

Sorry I said USB type C , but it should have been Micro B - glad you got it sorted
( I sell the cables in my Jaycar retail shop )

[jerre_77]

Hello everyone, here we are back, just bought another cable just to be sure, it said power & data so I think and hope it's a good one. So tried again today and unfortunately the same story, windows makes a sound and I think the WS90 appears but not in the right place, have tried everything. If there are no other tips, I will try one more time next week, but then on my mother-in-law's computer. If it doesn't work I'll gif up. On the picture you see more. (sorry it's in dutch)

[Gyvate]

that's the wrong device ....
when you start the DfuSe_Demo_3.0.6_setup.exe program, it creates a directory tree on your boot disk:
 [ You are not allowed to view attachments ]
you then need to go there and start the dpinst_amd64.exe program
this should install the proper driver

another option is to re-install the driver from the fancy device you have found:
click on the 2nd option in the Properties of .... DFU Device window - which say in Dutch "update driver"
next window choose 2nd option "look for driver on my computer" and then go the folder shown on the picture above - the x64 folder has to be chosen.
then Windows should install the proper driver

best to restart the PC once this is successfully done (the driver may not be visible in the device manager at that time)
then connect the WS90, press the reset button for 5-10 seconds - then driver and the device should appear in the device manager
name: STM32 Download Firmware Update

[jerre_77]

thanks for your help, tried everything again and checked based on your explanation. But unfortunately, the drivers are in the place where they should be, but the computer does not recognize the device correctly as a USB device but as a sound system. 

that's the wrong device ....
when you start the DfuSe_Demo_3.0.6_setup.exe program, it creates a directory tree on your boot disk:
 [ You are not allowed to view attachments ]
you then need to go there and start the dpinst_amd64.exe program
this should install the proper driver

another option is to re-install the driver from the fancy device you have found:
click on the 2nd option in the Properties of .... DFU Device window - which say in Dutch "update driver"
next window choose 2nd option "look for driver on my computer" and then go the folder shown on the picture above - the x64 folder has to be chosen.
then Windows should install the proper driver

best to restart the PC once this is successfully done (the driver may not be visible in the device manager at that time)
then connect the WS90, press the reset button for 5-10 seconds - then driver and the device should appear in the device manager
name: STM32 Download Firmware Update

[Gyvate]

did you try to deactivate and uninstall the wrong driver in the device manager ?

[davidefa]

Seems other are having problems with this Guillemot driver: https://support.pimax.com/en/support/solutions/articles/60000694699-how-to-uninstall-guillemot-stm-dfu-device
The proposed solution is to delete the guillemot directories, uninstall driver, reinstall the correct diriver ( in your case not the pimax driver but the one supplied by ecowitt ), reboot the computer

[jerre_77]

hello Guys, I just want to say that it finally made it to update tot 1.30, thanks to the still fairly new (windows 11) computer of my mother-in-law. And how simple it is, just follow the manual in less than 5 minutes and you're done. It's a pity that I lost so much time on it. Thanks again for your tips and help. 

[Gyvate]

  - patience and perseverance pays off 

[olicat]

Hi!

Ecowitt also updated the firmware update instructions and changelog for the WS90 today: click!.

Oliver

[rromanchuk]

I have a triple whammy of factors making this update a PITA.

arm/m1/m2 architectures: only have very recent virtual box/parallels support for windows 11 only.
intel: Old MBP with USB-C in (F) only. DFU absolutely hates micro (WS90) <-> USB HUB <-> USB-C, have not tried micro to usb-c direct yet, will need to order it. Tried win10/bootcamp with two different hubs, and about 5 different micro/usb cables

Still haven't tried dfu-utils or vm on the pi though.

WS90 (shipped) windSpeed is so outrageous not sure how it got released. 

For 221835Z AUTO 26011G16KT, out of box  WS90: -13knt  WH68: +/- 1knt error. Based on the CHANGELOG seems safe to say my p_rain is going to have similar margin of error against WH40, or such a nonsensical floor sensitivity that is not an offset fix, but SOC flash.  Good news is temp was great and relative pressure was a +0.81inHg offset

Going to decode ws90 and wh40 and tail 915 MHz on the next rain event to verify

[Gyvate]

I have a triple whammy of factors making this update a PITA.

arm/m1/m2 architectures: only have very recent virtual box/parallels support for windows 11 only.
intel: Old MBP with USB-C in (F) only. DFU absolutely hates micro (WS90) <-> USB HUB <-> USB-C, have not tried micro to usb-c direct yet, will need to order it. Tried win10/bootcamp with two different hubs, and about 5 different micro/usb cables

I don't get your point - I did the update with Win11 in 1-2 minutes and no issue with the micro USB. As a cable I just used the charger cable (which is also a data cable) which came with an earlier smartphone which still had this interface. Just worked like a charm. Even via a USB hub. So the architecture you use cannot be blamed on Ecowitt ...
But as you chose to have such an architecture, you have to manage the challenges that come with it. If your VM doesn't have the proper drivers to establish the USB connection, too bad.

A simple solution would be to find a friend or acquaintance who owns a normal Win11 laptop and ask them to help you out for a few minutes. 

Regarding the WS90 wind speed readings:
did you put the sensor powered up inside a box and pressed the CAL button to establish a baseline ?

what does "For 221835Z AUTO 26011G16KT, out of box  WS90:" mean ?
Are we readers supposed to understand that "out of the box" ?
Please, if you are using such details unknown to most readers, can you also explain what this means in this context ?

Also, you don't seem to fully understand the hardware you are using.
The WS90 doesn't read any pressure - and particularly no relative pressure.
Pressure is read by the console (e.g. GW2000, GW1100, HP25x0) - and read is only absolute (=local) pressure. Relative pressure only comes after calibration which you have to do in your console.