Nozzle moves very slowly from home to start position
I´m currently working on a custom delta printer running Marlin 1.0.2 firmware. To control it I´m using the Repetier Host software with the onboard Cura software to slice my objects. The printing works fine but it takes the nozzle nearly 5 minutes to move from the homing position at 250 mm to the starting position of the print near z=0.
I already tried to increase the travel speed but nothing changed. Can you guys please tell me how to increase the speed of my nozzle to move down to my starting point of the print?
As @TomvanderZanden says, the problem and the fix are most likely in your "start gcode" setting. You said "increase travel speed", but I think you meant you changed the travel speed setting in Cura, not in the specific line in the "start gcode" that actually does the travel from home to z=0. The start gcode will have something like G28 X Y Z F{some number} maybe twice, once fast and once slow. And then it may have a move to some start position (G1 X0 Y0 Z5 F{some number}) and it is that feedrate that matters here. (Perhaps you're using a snippet of start.gcode meant for a cartesion printer.)
Is this during a G0, a G1, or a G28? Your max G0 speed may be set low; have you tried adding an F value on that homing move?
Without the G-code this is guessing, to follow up @MarkWalker, start G-code for CuraEngine from within Repetier-Host is found here.
I had the same problem, and I solved it by changing the Z-Axis Feed Rate to a much higher value (1000 mm/min.) in Repetier Host via Config -> Printer Settings -> Printer.
I think the travel speed and z axis feed rate are different things though; the travel speed is used during the print to move the print head without printing while the z axis feed rate is used before the print starts. Either way, I've encountered the same problem as OP and my answer worked for me.
my bad, I stand corrected, +1! :)
License under CC-BY-SA with attribution
Content dated before 7/24/2021 11:53 AM
Tom van der Zanden 5 years ago
Please share the exact G-code that causes this problem. Without it we just have to take guesses at what is wrong in your settings.