Firmware 1.19 released
-
Will 2.0 continue to support the beta Wifi boards? I assume they will since very little was changed between beta and release.
-
Yes
-
Are series 2 Duets what ships now or a newer rev. not yet out? I only just got mine.
-
I believe they are the duetwifi and duet ethernet, but not the duet 0.6 and duet 0.85. Correct me if Im wrong Tony, DC42.
-
I believe they are the duetwifi and duet ethernet, but not the duet 0.6 and duet 0.85. Correct me if Im wrong Tony, DC42.
That is correct.
-
1.19 working perfectly for me. Many thanks. I can see this has been a very busy period with the PCB effector as well as this update. Don't work too hard.
-
Thanks for the feedback!
-
Upgraded nicely, thank you for all the hard work
-
The Web UI still showing Vin instead of CPU temp and interval of Vin is in degrees Celsius.
-
It is supposed to display VIN where CPU temp used to be. It displays the units as V for me, not degC. Please go to the Settings page of DWC and verify which version of the web interface you are running.
You can see the MCU temperature if you click on "Extra" near the top left corner.
-
I am running DWC 1.19 final. Here's the output for a grep (unarchived the .zip and the language.xml.gz inside it). I am talking about the tooltip.
grep -i Minimum language.xml <string t="Minimum: {0} °C Maximum: {1} °C">Minimum: {0} °C Maximum: {1} °C</string> <string t="Minimum">MÃnimo</string> <string t="Minimum: {0} °C Maximum: {1} °C">Minimum: {0} °C Maximum: {1} °C</string>
Regardless of this bug, isn't the MCU temperature more important because it can vary a lot? Chances that Vin varies are small (toasted or underpowered supply). Motor EMF surges are short so they will not be displayed nor seen on the UI.
-
I am running DWC 1.19 final. Here's the output for a grep (unarchived the .zip and the language.xml.gz inside it). I am talking about the tooltip.
grep -i Minimum language.xml <string t="Minimum: {0} °C Maximum: {1} °C">Minimum: {0} °C Maximum: {1} °C</string> <string t="Minimum">MÃnimo</string> <string t="Minimum: {0} °C Maximum: {1} °C">Minimum: {0} °C Maximum: {1} °C</string>
Regardless of this bug, isn't the MCU temperature more important because it can vary a lot? Chances that Vin varies are small (toasted or underpowered supply). Motor EMF surges are short so they will not be displayed nor seen on the UI.
Thanks, I didn't spot that. Will fix it in the next version.
-
Chris moved the CPU temperature display to the Extra list because there is now the facility to display up to 10 additional temperatures, and there isn't room for all of them on the main page.
-
I am getting the error that "DuetWifiFirmware.bin is not valid for these electronics" HELP! I have done the erase and reset, but no luck.
I have tried it over Wifi and USB but I m getting the same issue.
Edit: I may have solved it, I have just seen that there is an additional few steps for upgrading firmware from 18.2 and below. I will give that a try!
-
Nope still the same problem:
SENT: M997 S0:1
READ: Error: Firmware binary "DuetWiFiFirmware.bin" is not valid for this electronics. -
My guess is that you have not downloaded the firmware file correctly. It should be 321Kb in size.
-
Spot on seems there was a issue with the download. Now I have it all installed but apparently M587 is not recognized?
-
M587 will not work until you have enabled the WiFi module with M552 S0.
-
Ok I have followed everything and installed both firmwares simultaneously. Run the set Network macro and still M587 says unsupported?
Done!! Found the issue. The update support file (I can't recall it's name) was also corrupt when it was downloaded. Downloaded again. Now it all works like a charm!
-
David,
1. Are there any significant changes from the final RC to the release version?
2. Can you update using the web system from RC to release version?
Thanks!