M220 can be a double edge sword because it also affects the speed of retraction movements. If you are performing something like a retraction test, M220 is not suitable. In this case, however, due to the use of vase mode, M220 is a simple way for us to start with a slower feedrate and easily increase it throughout the print at set height intervals.
-Every firmware has a safety feature to limit the feedrate to a user set maximum. This prevents a typo in the slicer or terminal command from producing a move so fast it damages the printer. Use the following instructions to check what feedrate limit is in place for your firmware and temporarily raise it if necessary.
+Every firmware has a safety feature to limit the feedrate and acceleration to user set maximums. This prevents a typo in the slicer or terminal command from producing a move so fast it damages the printer. Use the following instructions to check what feedrate/acceleration limits are in place for your firmware and temporarily raise them if necessary.
+Please note that for this test, you would typically only alter feedrate limits. Acceleration limits are also covered here for completeness.
If you wish to raise these limits, re-enter 203 and use the X and Y arguments to set the max feedrate, typically in mm/sec. eg:
M203 X500 Y500
where 500 is a feedrate of 500 mm/sec.
-If you wish this change to be permanent, save to EEPROM with M500.
+Marlin limits the acceleration with the M201 and M204 gcodes.
+You can enter M503 into a terminal and these values will be reported.
+M204 sets target acceleration for print, retraction and travel moves, however M201 values impose limits per axis. For example, if you set the M204 print acceleration to 1000 but the M201 Y acceleration limit is only 800, then the M204 P value will be capped at 800 for Y while printing. If you have a bed slinger with a heavy y axis, M201 can be used in this way to combat ringing.
+If you wish this changes to be permanent, save to EEPROM with M500.
You can change this value and restart Klipper to raise it, or temporarily override it by entering:
SET_VELOCITY_LIMIT VELOCITY=500
in the terminal where 500 is a max feedrate of 500 mm/sec.
+Klipper limits acceleration in printer.cfgwith MAX_ACCEL and MAX_ACCEL_TO_DECEL.
+You can change these values and restart Klipper to raise them, or temporarily override by entering:
+SET_VELOCITY_LIMIT ACCEL=600+
or
+SET_VELOCITY_LIMIT ACCEL_TO_DECEL=600+
in the terminal where 600 is a max acceleration/accel to decel of 600 mm/sec/sec.
M201 X3000 Y3000
Remember that RRF uses mm/min instead of mm/sec, so this example uses a value of 500 mm/sec. Convert from mm/sec to mm/min by multiplying by 60. When editing config.g, do not omit the arguments for Z and E. Only X and Y potentially need modifiying for this test so leave the values for Z and E untouched.
Later versions of RRF also use the I argument to set the minimum overall feedrate. It may be necessary to lower this value if you want a particularly slow feedrate for segments of the tuning tower.
+RRF limits acceleration with the M201 and M204 gcodes.
+You can see your current value in config.g under M201 and M204.
+M204 sets target acceleration for print, and travel moves, however M201 values impose limits per axis. For example, if you set the M204 print acceleration to 1000 but the M201 Y acceleration limit is only 800, then the M204 P value will be capped at 800 for Y while printing. If you have a bed slinger with a heavy y axis, M201 can be used in this way to combat ringing.
+For acceleration, RRF uses mm/sec, despite using mm/min for feedrate. When editing config.g for M201, be sure to include values for each axis (typically X, Y, Z and E). When editing config.g for M204, be sure to include values for both P and T.
The STL for this test is available here: speedtower.stl