-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Printer occasionally gets lost #63
Comments
Sure, here you go. Printer settings have changed a little since the export (bed calibration Z0 offsets of corners and center), cannot access the machine right now. And no, the print came out just fine from the same Gcode after scraping off the raft and starting again, so it does not look like a Cura problem.. |
Not sure if this is related, but I've noticed that my Micro will occasionally "forget" to bring Z down to the bed at the start of the print. With Octoprint the normal start of print looks like this:
Normally at this point it will wait about 10-15s then start the print, moving to position while coming down to the bed. The printer will sometimes "forget" to move the extruder down to the bed and the print will start up in the air. |
Hi,
first of all, thank you for iMe and M33Fio! I've come to really like this combination on my Micro, especially the print quality due to the different approach to backlash compensation is a big plus for me!
Now to the issue I am experiencing (1.0.0.25): Rarely the printer gets lost, meaning an axis seems to move a full step too far, causing a print to split somewhere in between. It just starts extruding a few mm too far to the right or back (I've had both). This problem only occurs sporadically; I've had it 3 or 4 times in the last 2 or 3 months.
Just now it occurred while printing the first layer of a raft, there you can see the problem pretty clearly. After the 5th line in the Y direction the printer skipped roughly 4mm and kept this offset for the remaining print until I aborted it. Image is oriented as the part was in the printer, bottom being the device front.
I know sporadically occuring bugs are a b*tch to fix, but maybe you can look into this if you've got the time..
Thank you!
The text was updated successfully, but these errors were encountered: