You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read before that Auto Speed is not made for CoreXY printers, but I wanted to try it out anyway.
What it does with a Cartesian printer is that it executes the Z_Tilt_Adjust and then does not home the Z axis normally via G28 Z but instead moves the Z axis completely upwards and waits until it bumps into nothingness, which does not work with a Cartesian for homing the Z axis, as it would have to go downwards.
I would therefore recommend that before the script does anything at all, you let it look in the config to see what is set for [printer] and only execute a G28 Z accordingly, in my [printer] section for example it cleary starts that the used Kinematics are cartesian.
The text was updated successfully, but these errors were encountered:
I'm not sure what would cause this issue.
From the code below it looks like I have it do a "G28 Z0" instead of just G28. Could you try running "G28 Z0" and see if it gives you the same result? Maybe I just need to remove that 0.
I have read before that Auto Speed is not made for CoreXY printers, but I wanted to try it out anyway.
What it does with a Cartesian printer is that it executes the Z_Tilt_Adjust and then does not home the Z axis normally via G28 Z but instead moves the Z axis completely upwards and waits until it bumps into nothingness, which does not work with a Cartesian for homing the Z axis, as it would have to go downwards.
I would therefore recommend that before the script does anything at all, you let it look in the config to see what is set for [printer] and only execute a G28 Z accordingly, in my [printer] section for example it cleary starts that the used Kinematics are cartesian.
The text was updated successfully, but these errors were encountered: