Firmware 1.21 release candidate 2 now available
-
I renamed the .bin file for my Ethernet board. It seems to upload but the version on DWC does not reflect the change. M115 shows 1.20. It uploaded to my 2) WIFI boards fine
It sounds that the upgrade failed. Are you certain that you got the name right? Use the System Editor page of DWC to check.
-
there is no Duet Ethernet build for this version…RC1 yes, not RC2
-
there is no Duet Ethernet build for this version…RC1 yes, not RC2
OK, I see what you did – you combined ethernet and wifi builds -- I renamed the Wifi bin to DuetEthernetFirmware.bin and it worked
-
DuetEthernetFirmware.bin confirmed on DWC system editor. It copied to the config file and I even tried M997 S0. When I click "yes" to update the panel Due flashes briefly but the update does not happen. M115 still shows V1.20 I thought I had installed 1.21 RC1 but that must not have taken either.
-
Try uploading the new iap4e.bin file first.
-
I tried that. now the board will not start. I removed the SDcard and copied the iap4e and the DuetEthernetFirmware.bin to the card. How do I install the .bin file using the console on the panel due? M997 is for the WIFI.
-
Not sure if this is related to new firmware or existing issue – I've uploaded a large gcode file ~100mb and now duet is stuck with it on loading for all parameters in DWC and DWC then disconnects (ps file is called Part1.gcode) -- nothing special about the name
-
I tried that. now the board will not start. I removed the SDcard and copied the iap4e and the DuetEthernetFirmware.bin to the card. How do I install the .bin file using the console on the panel due? M997 is for the WIFI.
M997 S1 is for the WiFi. M997 S0 (or just M997) installs the main firmware.
-
Not sure if this is related to new firmware or existing issue – I've uploaded a large gcode file ~100mb and now duet is stuck with it on loading for all parameters in DWC and DWC then disconnects (ps file is called Part1.gcode) -- nothing special about the name
Does the disconnection message say that there was no response from the Duet, or something else?
Please put the GCode file on a file sharing site and post a link to it, so that I can try uploading it.
-
I tried a smaller file and it chokes it as well – 67mb this time. I pulled the sd card, and this time just copied it
I'll share both https://www.dropbox.com/sh/7m1eemyx6ofj3hi/AACh0wYFdcqfqlzr8mERoICZa?dl=0 -
I kept getting disconnect messages because duet was busy, then it finally loaded the 67mb file, and I got:
Error: Cannot read file.
Error: Failed to read footer from G-Code file "0:/gcodes/Part1V2.gcode" -
After it finally read it – I started printing it -- and it fell of the network entirely, but the screen said it was printing -- then i disconnected the network cable and plugged it back in, and it came back, and DWC is back and responsive.
-
I uploaded your files to one of my printers, and they uploaded OK and are displayed in the file list. However, no object height or filament usage is displayed. The reason according to Notepad++ is that both files contain vast quantities of null characters shortly before the end, within the footer comments region. If these are as S3D generated them, then I suspect a bug in S3D.
The error message you received suggests to me that you should replace the SD card.
-
I have seen this before with S3D especially with large files. I will try to re-save them – this is a new high speed card. I think the null characters are confusing duet...I'll try to re-save them and upload them.
-
I edited the file and got rid of the nulls, and it got loaded right away. I'll report this bug to S3D. Thanks for checking.
-
I updated, changed my probe type to 9, removed my M401s and M402s from bed.g, homez.g and homeall.g. Everything is working as expected on my IDEX cartesian.
-
I updated, changed my probe type to 9, removed my M401s and M402s from bed.g, homez.g and homeall.g. Everything is working as expected on my IDEX cartesian.
Thanks for the feedback. Be aware the the multi touch Z probing is not compatible with bltouch in this release.
-
I have a BL touch and have had the probe type set to 5 and was using multi-touch and it works fine, what is the benefit of using type 9?
-
Some bltouch users had the problem of the bltouch extending too soon again after probing.
-
I updated, changed my probe type to 9, removed my M401s and M402s from bed.g, homez.g and homeall.g. Everything is working as expected on my IDEX cartesian.
Thanks for the feedback. Be aware the the multi touch Z probing is not compatible with bltouch in this release.
I don't use multi touch at this point, but I may check it out at some point in the future. I seem to get pretty good results with my setup without it. Maybe I got lucky and got a pretty consistent bltouch.
Larry
