Three-fold thanks: for confirming the bug, for announcing a fix, and for providing a workaround.
- 3 weeks later...
Hi guys, i encountered the same problem, this info was very useful for me too. thx!
- 3 weeks later...
Hi! I am also having this blob issue (I’m on a Mac, using Cura 3.2.1). Could someone please tell me the exact code I would need to enter in the ‘End Gcode’ section of my Cura machine settings to fix things? I would really appreciate the help - thanks!!
Time has progressed....
Easiest solution right now is to download the Cura v3.3 beta release which should have the longer type of gcode files again and so hiding the UM2 bug. Note that the bug in the UM2 firmware has also been fixed but I didn't spend time in confirming it was included with this Cura beta version (there is a new firmware released with this Cura beta but it isn't mentioned in the release notes. It will sure be fixed and released in the final Cura 3.3 release).
Tip: You could even update your printer with the firmware from the Cura 3.3 beta and then revert to Cura v3.2 if you can't work with the beta.
Edited by Indy31- 1
Recommended Posts
CarloK 205
Recently this problem was reported in the Cura 3.2 subject forum.
The problem is caused by a change in Cura which exposes a bug in the UM2(+) firmware: At the end of the gcode file, Cura used to save a few lines with the used Cura settings. These settings were removed making the file a few lines shorter and this exposes the bug where the UM2(+) finishes the print while still a few moves are in the motion controller buffer.
The bug will soon be fixed and consists of two changes:
1) We will fix the bug in the UM2(+) firmware.
2) Cura will make the gcode files a bit longer again so the UM2(+) bug will not occur on older firmware versions.
For now the workaround is to revert to Cura v3.1. Or add about 10 extra comment lines at the end of your gcode file, or add an M400 command at the end of your gcode. These commands can be set in the 'End Gcode' section of your Cura machine settings.
Here a link with more info about the UM2 bug:
Link to post
Share on other sites