I started now with using two independent rails for the x steppers. Seems
not that complicated as I had thought first. I currently don't know how
the new rail gets its axis. Is the name of the stepper used (in my case
"stepper_x1") ? Have to find out.
Am 22.09.19 um 10:39 schrieb Gerald Dachs:
Am 22.09.19 um 06:36 schrieb Jeffrey B. Rogers:
I'm not speaking from a position of knowledge or authority by anyThat would be a problem.
means, but from my understanding, a two X motor Cartesian
configuration simply steps both motors in unison. Klipper just
assumes they are mechanically in phase with each other.
I'm not sure I understand your setup completely. You have two Xyes
carriages on the same rail that are independently movable?
I recently rewired my printer to have its two Z motors on separateMaybe that could be a workaround. I could home both steppers to the
drivers, and I was able to add a "z tilt" section to my config to
allow klipper to home both motors using my bed probe. Maybe you can
take a look at how the z tilt routine is implemented for some insight?
same side and the z_tilt would be the width of the first X carriage.
Also, if you can only define one endstop per rail, maybe you can
define two rails that just happen to be the same and always move in
unison?
Maybe even the cleanest solution, but I would have to dig into the
code much deeper.
In cartesian.py there is the support for dual_carriage_rails, but this
expects the steppers to be in one multirail, but then again I don't
understand the homing of that.
Before I make big changes I just want to know whether that is really
necessary. I am afraid I just don't understand the current code. I am
a lousy Python programmer.
On Sat, Sep 21, 2019 at 3:27 PM Gerald Dachs <gda@xxxxxx
<mailto:gda@xxxxxx>> wrote:
Hello,
I have build a printer with a new kinematic. It is a CoreXY IDEX
printer, I named it Core2XY ;).
I started to change the current corexy kinematic in Klipper to my
needs.
I have not tested it, but
I should at least be able to move one X Stepper without moving the
second one, what is not trivial on a CoreXY.
To understand what I have to do for homing the X steppers I
looked into
the cartesian kinematic, but I don't understand how it works. My X
steppers are both in one rail, like with the cartesian
kinematics. The
endstop_position is saved it the rail and not in the stepper
class. So I
can't have two different endstop_positions for the X steppers.
My idea was to home the first stepper on X min and the other on X
max.
Kevin, please explain how dual X steppers home in the cartesian
kinematics. That might help me to understand what I have to do.
Thank you
Gerald
