Hard machine limits ignored by gcode
Maybe I need an explanation. I considered the machine limits set in the printer.cfg as hard and absolute limits. Usually these limits are set higher than the sliced gcode, so no probbs. No I wanted to testrun a gcode slower, set the machine limits to half the former speed and started the gcode.
Well, apparently, the accs of the gcode counted and overwrote the machine limits.
Is that actually correct?
Solution:Jump to solution
klipper max_accel is overridden by M204 (which sets max accel). Yes, see: https://www.klipper3d.org/Config_Reference.html#printer
```
max_accel:
Maximum acceleration (in mm/s^2) of the toolhead (relative to the...
4 Replies
Solution
klipper max_accel is overridden by M204 (which sets max accel). Yes, see: https://www.klipper3d.org/Config_Reference.html#printer
M204 S10000
= SET_VELOCITY_LIMIT ACCEL=10000
Also generic klipper questions are better suited for #klipper
Ok, thanks for the explanation. So, I need to use PrusaSlicer more carefully, when doing something like this
Yeah just use the "advanced acceleration control" as it was intended
ie, set it to the acceleration you want to use, if you want it changed, reslice.