WXforum.net
Weather Station Hardware => Ambient Weather and Ecowitt and other Fine Offset clones => Topic started by: olicat on January 20, 2023, 02:52:39 AM
-
Hi!
Also for the WS90 (https://www.ecowitt.com/api/quickstart/product?id=249) is a new firmware available: v1.3.0 (https://osswww.ecowitt.net/uploads/20230120/WS90%20Firmware%20V1.3.0%20Upgrade.zip). In the meantime, you can also find it on the sensor page (https://www.ecowitt.com/shop/goodsDetail/249) under "MANUAL & SOFTWARE".
Changelog:
- optimize low/no wind speed detection algorithm.
add:
This time, the update package actually does not contain any update instructions. And the corresponding programme dfuse_demo_v3.0.6_setup.exe is also missing. So just the firmware file(s).
Strangely, the older firmware packages are also no longer offered, from which one could use the instructions and the required programme.
The current update therefore requires a version that is already available.
But here (https://osswww.ecowitt.net/uploads/20220921/WS90_V1.2.6%20Firmware%20&%20Toolkit.zip) you may download the previous version v1.2.6 with update instructions and with the required software. After installing you should use the WS90_V1.3.0.dfu to update. But I have no idea what to do with the WS90_V1.3.0_0x006C01D0.hex.
edit:
In the meantime, a revised firmware update package v1.3.0 with the necessary software as well as the instructions is available here (https://www.ecowitt.com/api/quickstart/product?id=249).
Oliver
-
Thank you olicat just updated min [tup]
Martin
-
Hi
stupid question coming, so how do you update the firmware?
Mine says it has the latest version via the app
-
Hi!
This time, the update package actually did not contain any update instructions. And the corresponding programme dfuse_demo_v3.0.6_setup.exe was also missing.
Strangely, the older firmware packages are also no longer offered, from which one could use the instructions and the required programme.
The current update therefore requires a version that is already available.
I could offer an older package. But I don't know if that would be OK from Ecowitt's point of view.
Perhaps you should ask Ecowitt how you should install the update. There is no hurry.
BTW:
This is an update for the WS90 sensor - not for any console. I am not aware of any app that checks the firmware version of the WS90 and reports a possible update.
add:
Here (https://osswww.ecowitt.net/uploads/20220921/WS90_V1.2.6%20Firmware%20&%20Toolkit.zip) you may download the previous version v1.2.6 with update instructions and with the required software. After installing you should use the WS90_V1.3.0.dfu to update. But I have no idea what to do with the WS90_V1.3.0_0x006C01D0.hex.
Anybody?
Oliver
-
Is there any changelog for v1.2.6? I have yet to update my WS90 since I got it from the original Kickstarter campaign. Only The GW2000 itself via WSView.
-
Hi!
Try this (https://www.wxforum.net/index.php?topic=44429.msg451743#msg451743).
Oliver
-
Hi!
This time, the update package actually did not contain any update instructions. And the corresponding programme dfuse_demo_v3.0.6_setup.exe was also missing.
...
Made in China...
-
I want to make sure I’m understanding what this update is for. I have the Ambient WS 5000, which if I understand correctly, uses the Ecowitt WS 90 as its sensor array for wind and temps. If I further understand, this update is for the array only, and not the display. Interestingly, I don’t see any mention of updating the array in the instruction manual. Only for separately updating the wifi, and separately the display. According to the word file in the 1.2.6 version of the update, you must hook up the array directly to a pc, and run the .dfu program to update the array. Ugh…. What a pain for a roof mounted array! Is my understanding correct?
-
I want to make sure I’m understanding what this update is for. I have the Ambient WS 5000, which if I understand correctly, uses the Ecowitt WS 90 as its sensor array for wind and temps. If I further understand, this update is for the array only, and not the display. Interestingly, I don’t see any mention of updating the array in the instruction manual. Only for separately updating the wifi, and separately the display. According to the word file in the 1.2.6 version of the update, you must hook up the array directly to a pc, and run the .dfu program to update the array. Ugh…. What a pain for a roof mounted array! Is my understanding correct?
Yes.
Stuart
-
Yes, and in reality, once stabilized, firmware upgrades on sensors should be rare. This is still new(ish) , so a little more frequent.
-
OK I missed something
I want to make sure I’m understanding what this update is for. I have the Ambient WS 5000, which if I understand correctly, uses the Ecowitt WS 90 as its sensor array for wind and temps. If I further understand, this update is for the array only, and not the display. Interestingly, I don’t see any mention of updating the array in the instruction manual. Only for separately updating the wifi, and separately the display. According to the word file in the 1.2.6 version of the update, you must hook up the array directly to a pc, and run the .dfu program to update the array. Ugh…. What a pain for a roof mounted array! Is my understanding correct?
It uses the WS80, not the WS90
So update accordingly, you do not have a WS90
And as you have an AmbientWeather unit , I would wait until they post a firmware upgrade
This is just a caution as the AmbientWeather sensor units provide some extra data that allows them to be used by an Ambient Weather console. Using a firmware update on the WS80 from Ecowitt (although the units are the same) , may disrupt the usability of your sensor with your AmbientWeather console.
Others. may know more... as I don't have a WS5000
-
Thanks Rover1822! I had not noticed the WS80 config of hardware. Geez, between Ambient and Ecowitt, all the individual model numbers make my head spin!
-
Hi!
This time, the update package actually did not contain any update instructions. And the corresponding programme dfuse_demo_v3.0.6_setup.exe was also missing.
...
Maybe they had no right to include the whatever.exe file for installing the update? The name has a hint, why not: dfuse_demo_v3.0.6_setup.ex
Why would a modern network connected device, that talks to its developers site 24/7 (yes, check your network traffic) needs a 3rd party tool to do something as simple as updating a firmware? Especially for a device that is probably installed way out of reach.
Made in China...
Reported for nationalist BS! If you don't like things made in China, WHY are you in this forum, if not to stir up trouble?
LOL. This has to be the most absurd thing I have read today.... but the day is young.
And yes, I happened to own this device. It's badly constructed (as many have pointed out), it's firmware updates are causing problems and so on. As expected from something made in China.
And yes, for some reason, most stuff that comes from China is crap and there is nothing your full blown denial can do about that fact.
Cheers!
-
BaseLine this thread is about the firmware update nothing to do with the build quality which is entirely your opinion, i wonder how many people are happy with the build quality compared to those that are not... for the most people only harp about the negative not when a product is good, if your opinion is that all stuff made in China is not good then why buy it .... no one was forcing you to.
Martin
-
KC5JIM, I was not attacking you i am sorry if you feel that i was but my comment was clearly pointed at BaseLine.
Thank you
Martin
-
KC5JIM, I was not attacking you i am sorry if you feel that i was but my comment was clearly pointed at BaseLine.
Thank you
Martin
Of course not! My apologies for quoting the wrong reply! I've edited my post. I'm SO SORRY!
-
For Oliver (Olicat),
Hi!
This time, the update package actually did not contain any update instructions. And the corresponding programme dfuse_demo_v3.0.6_setup.exe was also missing.
Strangely, the older firmware packages are also no longer offered, from which one could use the instructions and the required programme.
The current update therefore requires a version that is already available.
I could offer an older package. But I don't know if that would be OK from Ecowitt's point of view.
Perhaps you should ask Ecowitt how you should install the update. There is no hurry.
BTW:
This is an update for the WS90 sensor - not for any console. I am not aware of any app that checks the firmware version of the WS90 and reports a possible update.
add:
Here (https://osswww.ecowitt.net/uploads/20220921/WS90_V1.2.6%20Firmware%20&%20Toolkit.zip) you may download the previous version v1.2.6 with update instructions and with the required software. After installing you should use the WS90_V1.3.0.dfu to update. But I have no idea what to do with the WS90_V1.3.0_0x006C01D0.hex.
Anybody?
Oliver
I'm wondering if the .hex may be something to be used with the WS90 Modbus RTU model that you announced in another topic?
-
Hi!
This time, the update package actually did not contain any update instructions. And the corresponding programme dfuse_demo_v3.0.6_setup.exe was also missing.
...
Maybe they had no right to include the whatever.exe file for installing the update? The name has a hint, why not: dfuse_demo_v3.0.6_setup.ex
Why would a modern network connected device, that talks to its developers site 24/7 (yes, check your network traffic) needs a 3rd party tool to do something as simple as updating a firmware? Especially for a device that is probably installed way out of reach.
Made in China...
Reported for nationalist BS! If you don't like things made in China, WHY are you in this forum, if not to stir up trouble?
LOL. This has to be the most absurd thing I have read today.... but the day is young.
And yes, I happened to own this device. It's badly constructed (as many have pointed out), it's firmware updates are causing problems and so on. As expected from something made in China.
And yes, for some reason, most stuff that comes from China is crap and there is nothing your full blown denial can do about that fact.
Cheers!
I'm leaving the forum because admins are allowing personal attacks and nationalism in the forum now, and I refuse to have my children and my students exposed to such utter trash. I'll be placing this forum on my school's blacklist, and removing it from my curriculum (Yes, I actually baked this forum into my lesson plans!)
I reported an incident yesterday, I can see that saratogaWX had logged in since then, yet took no action on my report, which obviously emboldened the user to then start attacking me. In fact, he's been on this morning for almost 30 minutes and still nothing.
It's a shame when even a forum about weather stations is allowed to be politicized and the inmates are allowed to run the asylum.
Only one who thought about nationalism is you and lets be honest for a second, with that you attacked me!
My feelings are severely hurt and you need to apologize!
I feel sorry for you students, who are probably indoctrinated by you daily. What a sad world we live in.
-
BaseLine this thread is about the firmware update nothing to do with the build quality which is entirely your opinion, i wonder how many people are happy with the build quality compared to those that are not... for the most people only harp about the negative not when a product is good, if your opinion is that all stuff made in China is not good then why buy it .... no one was forcing you to.
Martin
If you read the "And the corresponding programme dfuse_demo_v3.0.6_setup.exe was also missing."
you should realize that the latest update was also screwed up, especially for those who do not have the software witbboy guys included in their previous updates (probably) illegally.
-
I'm leaving the forum because admins are allowing personal attacks and nationalism in the forum now, and I refuse to have my children and my students exposed to such utter trash. I'll be placing this forum on my school's blacklist, and removing it from my curriculum (Yes, I actually baked this forum into my lesson plans!)
I reported an incident yesterday, I can see that saratogaWX had logged in since then, yet took no action on my report, which obviously emboldened the user to then start attacking me. In fact, he's been on this morning for almost 30 minutes and still nothing.
It's a shame when even a forum about weather stations is allowed to be politicized and the inmates are allowed to run the asylum.
I stand corrected. THIS is the most absurd and unhinged rant I have read today. No educator should behave like this. This is literally a kindergarten level temper-tantrum where you attack board members and admins because they do not share your confused view of the reality. No wonder American education system has collapsed.
-
Here is the upgrade manual, notice this is the one for the 1.1.9 firmware of the WS90, to upgrade to the latest, it should be the same way.
The dfuse demo program is downloadable, just google dfuse demo
-
I'm leaving the forum because admins are allowing personal attacks and nationalism in the forum now, and I refuse to have my children and my students exposed to such utter trash. I'll be placing this forum on my school's blacklist, and removing it from my curriculum (Yes, I actually baked this forum into my lesson plans!)
I reported an incident yesterday, I can see that saratogaWX had logged in since then, yet took no action on my report, which obviously emboldened the user to then start attacking me. In fact, he's been on this morning for almost 30 minutes and still nothing.
It's a shame when even a forum about weather stations is allowed to be politicized and the inmates are allowed to run the asylum.
I stand corrected. THIS is the most absurd and unhinged rant I have read today. No educator should behave like this. This is literally a kindergarten level temper-tantrum where you attack board members and admins because they do not share your confused view of the reality. No wonder American education system has collapsed.
Baseline - You add nothing to this thread of any value.
-
I'm leaving the forum because admins are allowing personal attacks and nationalism in the forum now, and I refuse to have my children and my students exposed to such utter trash. I'll be placing this forum on my school's blacklist, and removing it from my curriculum (Yes, I actually baked this forum into my lesson plans!)
I reported an incident yesterday, I can see that saratogaWX had logged in since then, yet took no action on my report, which obviously emboldened the user to then start attacking me. In fact, he's been on this morning for almost 30 minutes and still nothing.
It's a shame when even a forum about weather stations is allowed to be politicized and the inmates are allowed to run the asylum.
I stand corrected. THIS is the most absurd and unhinged rant I have read today. No educator should behave like this. This is literally a kindergarten level temper-tantrum where you attack board members and admins because they do not share your confused view of the reality. No wonder American education system has collapsed.
Contrary to popular views, I'm not available 24x7 for moderation duties. While I've been here since the founding of the forum (as a co-founder and administrator), I have other obligations to attend to than this forum.
BaseLine and KC5JIM: You're both behaving badly. Baseline for sniping at another country and KS5JIM for going ballistic over it, then ranting about timeliness of moderation. Geesh.. Both of you need to become more civil in your discourses. I remind you that the registration agreement still prohibits ad hominem attacks and political speech.
Now enjoy the rest of your Sunday, but BEHAVE!
-
Hi Rover,
I'm wondering if the .hex may be something to be used with the WS90 Modbus RTU model that you announced in another topic?
such a hex file (different size and content) is also included in the firmware update for the WS80. However, so far I have no information about a Modbus version for the WS80.
It is conceivable that there will (soon) be another type of firmware update program that requires this type of file. But who knows?
I'm afraid we have no choice but to wait for a statement from Ecowitt. (Just asked.)
Oliver
-
.dfu files are generated from .hex (or .s19j files. Supposedly.
-
Why would a modern network connected device, that talks to its developers site 24/7 (yes, check your network traffic) needs a 3rd party tool to do something as simple as updating a firmware? Especially for a device that is probably installed way out of reach.
Made in China...
And yes, I happened to own this device. It's badly constructed (as many have pointed out), it's firmware updates are causing problems and so on. As expected from something made in China.
And yes, for some reason, most stuff that comes from China is crap and there is nothing your full blown denial can do about that fact.
Cheers!
The sensor array does not talk to the developers, the console gateway is another story. The sensor array is a broadcast only device. It can not receive anything. And yes you need to program the microcontroller chip on that device via a USB cable. Yes that stinks, but be glad it’s possible and ecowitt actually tries to address firmware problems.
-
Hi Rover,
I'm wondering if the .hex may be something to be used with the WS90 Modbus RTU model that you announced in another topic?
such a hex file (different size and content) is also included in the firmware update for the WS80. However, so far I have no information about a Modbus version for the WS80.
It is conceivable that there will (soon) be another type of firmware update program that requires this type of file. But who knows?
I'm afraid we have no choice but to wait for a statement from Ecowitt. (Just asked.)
Oliver
If you are in contact with Eccowitt team, maybe they can provide the instructions how to update the firmware with dfu-util.
-
Hi!
maybe they can provide the instructions how to update the firmware with dfu-util
They will, I am sure.
But at the moment there are holidays in China, so I don't expect a timely reaction. But that is not critical - the update may bring improvements. However, even without this firmware update, everything works as before. So there is no need to rush.
If you want to install the update v1.3.0 in advance, you will have to use the previously valid instructions and the required software from the previous update package (https://osswww.ecowitt.net/uploads/20220921/WS90_V1.2.6%20Firmware%20&%20Toolkit.zip) but use the firmware file WS90_V1.3.0.dfu from current firmware package (https://www.ecowitt.com/api/quickstart/product?id=249).
As soon as I hear something new about this from Ecowitt, I will report it here.
Oliver
-
Changelog:
- optimize low/no wind speed detection algorithm.
I do see a significant change in the lower wind speeds. Today was almost no wind. But the wind speeds were never reported as 0m/s. Now I do see significantly lower wind speeds reported (and thus even zeroes).
Below the graph. The red line is de moment of the update to v1.3.0 today.
[ You are not allowed to view attachments ]
-
Changelog:
- optimize low/no wind speed detection algorithm.
I do see a significant change in the lower wind speeds. Today was almost no wind. But the wind speeds were never reported as 0m/s. Now I do see significantly lower wind speeds reported (and thus even zeroes).
Below the graph. The red line is de moment of the update to v1.3.0 today.
[ You are not allowed to view attachments ]
You see those 5 points that touch the "0" line? Those are your "almost no wind" moments.
I cant recall that I have ever seen or felt, outdoors, air standing absolutely still.
-
I have a WS80 but NOT with the latest f/w which does the same as this for the WS90 and last night I can see 0mph recorded on more that one short duration around 05:30 today. I do know that the air is quite still. So I would not be surprised at a reading of or very close to 0 and remember that for wind speeds less that 10m/s there is an accuracy of +-0.5m/s as well to consider. I suspect it is similar for the WS90.
Stuart
-
I cant recall that I have ever seen or felt, outdoors, air standing absolutely still.
Well, currently the western part of Europe is under a high-pressure area. It is foggy, gray and there is no wind at all. So yes, I'd say that the air from time to time is absolutely still. My weatherstation is also in a sheltered residential area, that also has it's influence ;)
-
Has any one needed to adjust wind speed gain settings??
-
Has any one needed to adjust wind speed gain settings??
No. Whats the reason of your question?
-
Hi!
In the meantime, a revised firmware update package v1.3.0 with the necessary software as well as the instructions is available for the WS90.
Download page: click (https://www.ecowitt.com/api/quickstart/product?id=249).
Direct download link: available here (https://osswww.ecowitt.net/uploads/20230201/WS90_V1.3.0%20Firmware%20&%20Tookit.zip).
add:
On closer inspection, it is noticeable that the firmware file is somewhat smaller and has an older file date than in the original update package. I have asked Ecowitt again for clarification.
Oliver
-
Hi!
I have received a reply from Ecowitt regarding the different file sizes of the firmware file:
Yes, you are right that the two files are not same in size, due to the debug printing code has been added with the previous released version.
So the current version has the debug code removed, and funcitonwise they are exactly same.
So the current (https://www.ecowitt.com/api/quickstart/product?id=249) version of the firmware file is functionally the same as the previously released version. There is nothing to stop you using the version in the package.
Ecowitt apologises for the slight chaos and promises improvement in the future.
Oliver
-
Hi!
maybe they can provide the instructions how to update the firmware with dfu-util
They will, I am sure.....
Oliver
and...
-
Hi!
maybe they can provide the instructions how to update the firmware with dfu-util
They will, I am sure.....
Oliver
and...
long done - see post #34
-
Hi!
maybe they can provide the instructions how to update the firmware with dfu-util
They will, I am sure.....
Oliver
and...
long done - see post #34
dfu-util is a command line application for Linux (and there is a port for Mac too).
-
Hi!
maybe they can provide the instructions how to update the firmware with dfu-util
They will, I am sure.....
Oliver
and...
long done - see post #34
dfu-util is a command line application for Linux (and there is a port for Mac too).
Forget that Windows exists?
https://dfu-util.sourceforge.net/
Releases of the dfu-util software can be found in the releases folder. The current release is 0.11.
We offer binaries for Microsoft Windows and some other platforms. dfu-util uses libusb 1.0 to access your device, so on Windows you have to register the device with the WinUSB driver (alternatively libusb-win32 or libusbK), please see the libusb wiki for more details.
-
Forget that Windows exists?
Yes, about 20 years ago.
We offer binaries for Microsoft Windows and some other platforms. dfu-util uses libusb 1.0 to access your device, so on Windows you have to register the device with the WinUSB driver (alternatively libusb-win32 or libusbK), please see the libusb wiki for more details.
We? Who is we and how is any of your verbiage related to device specific cli examples for using dfu-util...
PS! What happened to leaving?
-
Forget that Windows exists?
Yes, about 20 years ago.
We offer binaries for Microsoft Windows and some other platforms. dfu-util uses libusb 1.0 to access your device, so on Windows you have to register the device with the WinUSB driver (alternatively libusb-win32 or libusbK), please see the libusb wiki for more details.
We? Who is we and how is any of your verbiage related to device specific cli examples for using dfu-util...
maybe you just follow the link above the text portion you were quoting - the "we" text comes from there, from the dfu-util homepage;
then you will also know whom the dfu-util developers mean by "we"
-
Forget that Windows exists?
Yes, about 20 years ago.
We offer binaries for Microsoft Windows and some other platforms. dfu-util uses libusb 1.0 to access your device, so on Windows you have to register the device with the WinUSB driver (alternatively libusb-win32 or libusbK), please see the libusb wiki for more details.
We? Who is we and how is any of your verbiage related to device specific cli examples for using dfu-util...
maybe you just follow the link above the text portion you were quoting - the "we" text comes from there, from the dfu-util homepage;
then you will also know whom the dfu-util developers mean by "we"
Not sure what part of my original request for WS90 dev team to add cli command examples for dfu-util confuses you 2.
It's one of the few applications for Linux. MS Windows is irrelevant in this context.
-
Hi BaseLine,
I must admit that I misunderstood your originally question in post 26 (https://www.wxforum.net/index.php?topic=44938.msg456281#msg456281) and therefore answered it incorrectly.
We wondered about the lack of instructions and the update programme. But my statement referred precisely to that.
Sorry!
Ecowitt has a procedure for updating the WS80 & WS90 firmware using a Windows programme (DfuSeDemo.exe). This has apparently been tested by Ecowitt and approved for updates by the user.
I am not aware of any other way supported by Ecowitt.
I could imagine that it could also work with the command line version dfu-util. But this way is obviously not supported by Ecowitt - we can therefore not expect any guidance on this from the manufacturer.
If this is so important to you, you could of course ask Ecowitt directly in a friendly (!) way.
However, I cannot really estimate how much work Ecowitt will put into the wish of a single user who has rumbled around quite unfriendly here in the forum. What goes around comes around.
But try it, if you are really interested in a substantive solution and not just in grumbling and denigrating the manufacturer's work.
However, it would also contribute to a substantive solution if you would answer questions substantially.
It is still unclear to me whether you were able to successfully update with dfu-util or how you were finally able (https://www.wxforum.net/index.php?topic=43139.msg451276#msg451276) to update your WS90 to v1.2.5. I would be happy to read your answers in the original thread (https://www.wxforum.net/index.php?topic=44368.msg451194#msg451194).
This thread here should really only be about the release of firmware v1.3.0 for the WS90.
Thanks!
Oliver
-
Anyone any idea, I would like to update to 1.30 but windows 10 does not recognize the WS90. I've done everything according to the manual and this already 10 times. I can't figure it out, I suppose it's my PC. :cry:
-
Hi!
Please try:
- another cable (some cables are for power supply only)
- another port on your computer
- another computer
If the WS90 is connected to the computer via USB, is there any new device in the device manager?
Is there the typical Windows dingdong when connecting or disconnecting via USB?
Oliver
-
- another cable (some cables are for power supply only)
Those should be banned or marked as such, I have run into that as well.
On the subject of manual being followed, are you using the instructions that are in the zip file download of the firmware?
Also, I know this may seem redundant, but can you list the steps you are doing, being exact as possible, there may be something we can identify. Also if possible, provide screen caps of what you are doing, similar to what is in the instructions.
This is in addition to what Oliver said above.
-
did you follow the instructions in the included pdf file ?
https://osswww.ecowitt.net/uploads/20230201/WS90_V1.3.0%20Firmware%20&%20Tookit.zip
and - of course - the USB cable has to be a data cable 8-)
-
Hi, thanks for the reply, already tried.
Other cable = Yes
other usb port = yes
another computer = no, no other one in the house, maybe I'll try my mother-in-law's next week.
The computer makes the typical windows sound when plugging in the cable, but it just doesn't show up in the device manager. ](*,)
Hi!
Please try:
- another cable (some cables are for power supply only)
- another port on your computer
- another computer
If the WS90 is connected to the computer via USB, is there any new device in the device manager?
Is there the typical Windows dingdong when connecting or disconnecting via USB?
Oliver
-
Hi Roger,
Thanks for the answer, I followed the manual in the zip file step by step and 10 times. installed, uninstalled and reinstalled.
I'll try again next weekend and take screenshots.
- another cable (some cables are for power supply only)
Those should be banned or marked as such, I have run into that as well.
On the subject of manual being followed, are you using the instructions that are in the zip file download of the firmware?
Also, I know this may seem redundant, but can you list the steps you are doing, being exact as possible, there may be something we can identify. Also if possible, provide screen caps of what you are doing, similar to what is in the instructions.
This is in addition to what Oliver said above.
-
From what has been said it sounds like the correct driver is not being found. Are there driver files in the zip file?
Stuart
-
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)
-
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
-
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
-
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
-
You didn't install the driver ( as the image you posted shows ).
In my case the driver are situated in:
C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10
-
Thanks for the replies... Didn't look in C:\Program Files (x86)\STMicroelectronics
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
-
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 ...
-
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
-
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
[tup] helpful/useful links
- and the WS90 needs a USB data cable with micro USB B plug (male) to insert into the device
-
You didn't install the driver ( as the image you posted shows ).
In my case the driver are situated in:
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
-
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 )
-
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)
-
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
-
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
-
did you try to deactivate and uninstall the wrong driver in the device manager ?
-
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
-
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. \:D/
-
[tup] - patience and perseverance pays off :-)
-
Hi!
Ecowitt also updated the firmware update instructions and changelog for the WS90 today: click! (https://www.ecowitt.com/api/quickstart/product?id=249).
Oliver
-
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
-
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.