Are you printing from USB?
The line nr. errors often are caused by a usb stick with memory errors.
Are you printing from USB?
The line nr. errors often are caused by a usb stick with memory errors.
12 hours ago, CarloK said:Are you printing from USB?
The line nr. errors often are caused by a usb stick with memory errors.
No, I am printing over WIFI.
It gives error if I play with number of models (1 to 9 and reverse) in CURA when One at a time is active. If I do not change number of models, it works fine repeatedly.
An old topic, but besides a bad USB drive we recently discovered another root cause for the weird error messages with 'line nr = xxx'. When the line number refers to a gcode line with 'G0' or 'G1' in it, then this is a late error message from Active Leveling. In an earlier stage the Active Level probing failed and that software error wasn't handled. We will have to fix that in software and show a better message, but also check your build plate as it might have a curvature out of specifications.
A curved build plate might explain how the error disappeared; perhaps the build plate was moved, flipped or turned? Also printing the object on a different region of the build plate would create another probing pattern skipping the curved part.
I'm having the same issue... Is there any update on this matter?
Have you figured everything out yet?
This problem is still there also with Cura 4.6.1. The print failed on my S5 right after completing the print of the first part. Also the slicer shows weird lines as you can see in the screenshot. I suspect that this visualizes the improper gcode.
I would appreciate a fix. especially with small parts like those in the screenshot this helps a ton.
thanks!
Recommended Posts
Janek 1
Still, S5 keeps failing and failing to print objects "One at a Time" again and again. Printer restart helps to overcome this since next failure.
Additionally, if printer says "Out of material" or something similar and if you then abort print, then the bed is raised to top and the printed part hits the printhead! Happened to me several times - a bug?
Link to post
Share on other sites