10 minutes ago, SandervG said:Hi @chuckmcgee,
Have you also created a support ticket besides posting here? If you haven't, I would like to ask you to do so. You can do so via this link
Just completed. Thank you!
10 minutes ago, SandervG said:Hi @chuckmcgee,
Have you also created a support ticket besides posting here? If you haven't, I would like to ask you to do so. You can do so via this link
Just completed. Thank you!
The ER998 is something to look into, it is a difficult ER message in that regard. It is good to have it logged in our support systems and to get our product experts involved too.
Regarding removing material, in the release notes of this firmware we describe that filament will not be retracted entirely anymore, because a significant amount of people print with the same 1, 2 or 3 materials and it would save some time unloading/loading and it is for the better for the filament, to run it less passed those feeders all the time.
The option to manually trigger the unload will be added in the next firmware version, I believe this was a slight oversight. Can you test what happens if you start a new print, and just leave the filament there after a print? I think it should switch it out for the new one, or continue with the filament that is parked.
2 hours ago, SandervG said:The ER998 is something to look into, it is a difficult ER message in that regard. It is good to have it logged in our support systems and to get our product experts involved too.
Yes, er998 is a so called uncaught exception, that means something went wrong and the system had no way of "catching" this situation, the trouble with it is: It can be all sorts of things.. In the last couple of months (and in version 5.8) we have already solved a couple of causes for er998, but not all.. So working with support to give us the logfiles greatly helps us finding the root causes.
Hello all.
As a matter of follow up, I have done about 3 more prints, each lasting 12 hours or more…I have used spool slots A, B, and D, in the subsequent prints - each with Ultimaker ABS (the same as before), and the error has not returned. Things seem to be fine as it relates to this odd error.
I have seen the behavior other people are reporting with the filament eject buttons being unresponsive, but that seems to be confirmed as a shortcoming of the 5.8.0 firmware (and something I can live with until the next firmware).
I am going to go ahead and call this issue resolved for now. I didn’t do anything since seeing the errors, but the issue has gone away. Each successful print now shows the “Confirm Removal” button with a green circled checkmark on the touch screen.
Thank you for your follow ups.
Once again, fabulous community response!
I have been facing the similar kind of problem. There's the material stuck in the Bowden tube and there's no way to remove it.
It's constantly throwing the ER60 and asking to reboot. I have also gone through the Error description for the ER60 on the Ultimaker Support. In the troubleshooting steps, it's asking to manually removing the filament from the starting point but I cannot do this.
See the attached pictures.
I am the beginner at doing the troubleshooting for the 3D Printer so please let me know the step by step process if anyone can.
Recommended Posts
UlrichC-DE 115
This is exactly what I observed with version 5.8.0.
Afterwards I pulled the main plug on the MS. But nothing more.
Unloading happens automatically after 2 hours or when changing the material by another print job.
Ultimaker wants to fix this problem in the next two versions.
I've only had the error once before. But fortunately not the error when changing the print core.
Link to post
Share on other sites
SandervG 1,522
Hi @chuckmcgee,
Have you also created a support ticket besides posting here? If you haven't, I would like to ask you to do so. You can do so via this link
Link to post
Share on other sites