Travel feedrate. This is the default setting which I have been using in Repetier since I first got my bot. Is this standard and what does it really indicate?
The travel feedrate describes the speed the printer uses for moving the printhead from one printing area to the next. It is additionally limited by your firmware, so whichever value you enter there will be used as long as the firmware thinks it can handle it. It should be set as high as possible (mitigates oozing), but not so high that your bot starts to skip steps during long travel moves.
And it’s kind of non-standard for it to be in minutes. Usually it’s mm/s - which 2400mm/min is 40mm/s - which is REALLY slow. Most bots have a travel speed of 100mm/s (6000mm/min in this case). Travel feedrate is ok, but I’m usually hitting 240mm/min (4mm/s) – it depends on your thread pitch how fast you can go.
Alright. Thanks. Starting to understand some of these numbers and setting a bit better now. Now I need to figure out why Repetier lists EEPROM settings in the drop down but won’t allow me to select it. I was hoping to be able to change the z-steps here, instead of having to mess with firmware
@boog_nish You wont be able to change them if the eeprom feature is disabled in your firmware. It’s somewhere in the config.h file in Marlin.
Sorta like Thomas said, Travel Feed Rate is the X/Y speed when the extruder is off. Feed Rate is the X/Y speed when it’s on.
mm/minute is pretty much the standard units in gcode files. When people talk/type about rates, we use mm/s. Probably because it’s easier to visualize.
Few points on feedrate / travel rate
In Marlin you can issue the following code:
M203 X### Y### Z### E###
Which will TEMPORARILY change your MAXIMUM feed rates.
I’m not sure on the mechanical setup of your machine, but on my mendel I use M203 X150 Y150 Z4 E40 - which limits each of those axes to the value specified (in mm per SECOND, in repetier for some reason they specify it in mm per MINUTE)
You can then send a M500 code to the machine to save the new values to your EEPROM.
This all works on my bot, take care setting them on yours!
Perhaps try something like M203 X10 Y10 Z1 E5 and see if it slows everything down - then try higher values and see if they speed up - if that seems to work I’d say your bot works the same as mine and you’re done, without a firmware re-flash 