Firmware version 4.2.5.20180102
Cura version 3.1.0
The printer is currently in use. Maybe I can download the logs tomorrow.
20 hours ago, macio said:The printer is currently in use. Maybe I can download the logs tomorrow.
That is fine, no rush.
@Marco_TvM Send logs as PM
Thanks, checking ...
- 1
- 2 months later...
- 1 month later...
Update on this one. We've found the problem related to abort and too much or too little priming in the next print.
We're still working on the proper fix, as it's a complex interaction of motion being aborted while the rest of the system is continuing with movements to abort the print. All this causes filament positions to be out of sync and thus the large amount of priming later on.
- 3
Great! Thanks for keeping us posted/updated @Daid ?
- 1
- 8 months later...
@Daid
Just ran into the issue again yesterday. Are you still working on a fix?
We are continuously improving the software of our printers and many stability improvements for the S5 will become available for the UM3 too. To our regret the last release for the UM3 has been delayed way more than anticipated.
The problem we are facing is that the S5 and UM3 are very similar, but differ in a few important ways. We are working hard to give the UM3 an update to the same code base as the S5, but we can only release this when we are absolutely sure the update process will never brick your machine. Tests have been going on for some time now, but new edge cases did pop up again-and-again.
We are working hard to release a new UM3 version, but I can't say anything about the timing. It will get there when we feel confident.
- 1 year later...
Any update on this? Just had it occur again to me. Huge mess, and clogged nozzle.
- 2 years later...
Any update on this?
Just had the exact same issue (huge prime blob at next print attempt after an aborted print).
Using the latest firmware on UM3 (being 5.2.11.20190503 at this time).
Recommended Posts
Marco_TvM 34
It would help to get the logs when this happens, using System -> Maintenance -> Diagnostics -> Dump logs to USB and send them either by using something like WeTransfer or attach them.
That way we can see which firmware is being used (missing in the report) and the state of the printer logic being used.
Link to post
Share on other sites