![]() ![]() Things that could generate the issues that spring to mind in this test.įor you, there's also start.g, which maybe can be emptied, commented, or renamed while focusing on this issue using this GCODE.ġ0 tool changes according to previous video should generate a movement of 2mm with G29 enabled and 0mm movement with it disabled. The only question is whether you have G29 at the start or not. ![]() So the script will look something like this Why not create a script which just hammers this issue repeatedly. Next I'm thinking that your error is, we think, generated as a result of tool changes and bed levelling. ![]() I've never used M561 either.īut it seems that something about you bed leveling is causing the issue. I put the start GCODE in the slicer section for starting GCODE. Well I've never used start.g before - so that's interesting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |