But to my supprise I’ve found that setting one axis with SET_KINEMATIC_POSITION also set others. My code will end up cleaning y but x and z will stay. Is it correct behaviour? Or am I doing something wrong?
Will that work if there are not homed? Because what I want is to avoid setting their position if they are not (or a bunch of ifs to always check their state, store it and clean position)
SET_KINEMATIC_POSITION is a low-level “diagnostic” tool that overrides everything. Your printer will believe it is at the position you entered, effectively overriding the coordinates determined by homing the printer.
Be aware that this might lead to damaged hardware.
FYI, SET_KINEMATIC_POSITION will not alter the X or Z position if they are not explicitly set - see: G-Codes - Klipper documentation .
If the original question was about the X and Z being considered in a “homed” state after the SET_KINEMATIC_POSITION command, then the CLEAR=XZ parameter can be used to undo that change.
As mentioned above, care should be used when using SET_KINEMATIC_POSITION.
That’s the thing: I use it in few places and this approach will always require checking what axis were homed before, storing it and then cleaning others in the end. I know you can force move on motor directly but with 4 motor Z that would be problematic
ps. I know Kinematic position is dangerous, but that’s calculated risk. If I’m in Y=0, which I’m almost never, moving axis to minus will just skip on motors (they are on lower current during homing). But if I’m on Y max and suddenly toolhead will decide that rubbing against cable or chain during x homing is perfect zero point them I’m screwed or… same applies if kinematic position resets my other axis
ps. I really thought that logical process will be if there is position - restor if it’s unassigned - keep it that way. Then we have kinematic position clear and suddenly works only on specified axis…
