Force Move problem

General Discussion
1

Just playing with Klipper for the first time and realised that when force move is enabled on a multi z setup, only z1 works. Not sure if it’s a known bug or not?

Cheers,
Jay.

2

Hello @JaySom !

Very hard to say without the requested klippy.log

1 Like
3

This is known and is not a bug, it is by design:

  • The FORCE_MOVE command is a debugging/diagnostic tool and is not aware of the printer’s kinematics.
  • It is not intended to provide kinematic functionality, nor is it intended for regular operation.
  • If you need to move before homing, you can use SET_KINEMATIC_POSITION to fake a home position.
  • SET_KINEMATIC_POSITION is also a debugging/diagnostic tool and must be followed by a regular G28, or it will leave the printer in an undefined state. Also note that you can easily crash your axes this way. Regular usage is not recommended.
  • If you have special homing requirements, you should have a look at homing_override.