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
For dual extruder RepRap style clones the extruded blobs are too tall and get hit by the extruder when the extruder moved from one location to another.
In slicers when printing items one at a time there is a setting which has to be taken into account to avoid hitting the gantry for the extruder. for example "gantry height" in cura. For my printer BIBO 2 this is about 12mm in z. The area of the dual extruder print head could also be considered as should the X and Y rails. but generally just the 12mm gantry height is considered to avoid hitting parts and knocking them off the build plate.
Sadly due to this issue I can't run this profiling tool. please consider adding a "gantry height" interference check.
The text was updated successfully, but these errors were encountered:
Also adjusting the Z lift in the gcode from 10.5 to 12.5 corrected example from first blob at 2mm3/s G0 X5 Y5 Z12.5 F7800 and G0 Z12.5; Lift
adjusting the first Z lift G0 Z10 ; Lift nozzle to G0 Z12.5 ; Lift nozzle
I believe The z lift here should reflect the "gantry height" value plus some value
For dual extruder RepRap style clones the extruded blobs are too tall and get hit by the extruder when the extruder moved from one location to another.
In slicers when printing items one at a time there is a setting which has to be taken into account to avoid hitting the gantry for the extruder. for example "gantry height" in cura. For my printer BIBO 2 this is about 12mm in z. The area of the dual extruder print head could also be considered as should the X and Y rails. but generally just the 12mm gantry height is considered to avoid hitting parts and knocking them off the build plate.
Sadly due to this issue I can't run this profiling tool. please consider adding a "gantry height" interference check.
The text was updated successfully, but these errors were encountered: