If the slicer specifies a larger area than is actually available to the printer. Neither the slicer nor the clipper swears. The clipper gets a move error only when it reaches this command. 6 hours of printing and a lot of plastic lost. The default setting in the slicer was 230x230 on Ender-3 v2. The printer with the head mod actually has a 236x223 area available to it.
Hello @SileNTViP !
Honestly, you have to take care to set the slicer to the correct printer profile so that this does not happen.
How should it do? It does exactly what is set in the profiles.
The slicer can be set to these values.
However, this is not Klipper’s (not the clipper) task to do a check. It more a task to the frontend.
Already measured the maximum coordinates where the head can reach and replaced the default Ender-3 v2 profile with my parameters.
Please attach the klippy.log to your next post.
This is by design of gcode as it uses relative coordinates. To avoid this, Klipper would have to simulate the entire print in order to check if something is wrong WRT this.
Technically Klipper is able to do this, but of course it takes time. The bigger the file, the more time it takes.
Introducing such a time penalty, just to catch an obvious misconfiguration, seems not necessary. Once corrected, it will not pop up again.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.