Hybridcorexy kinematic issue during ztilt/quad gantry level

Basic Information:

Printer Model:custom speedcore
MCU / Printerboard:bigtreetech kraken
Host / SBC
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I made a 1m3 idex printer with hybrid kinematics. I made similar to the follow, but i use 2 Y motors Y1 &Y2. in total 4 motors. during setup I had a kinematic issue for the calculation of movements, X1 was increasing from left to right and x2 from right to left in order to mantain position during Y movement. I tried different changes into !dir and polarity without success: during movement of Y X1 or X2 or both they where moving wrong , moving for example during the clean movement of Y. so i decided to modify the file hybridcorexy.py

I changed the polarity of

self.rails[0].setup_itersolve(‘corexy_stepper_alloc’, b’+')

and

cal position def calc_position(self, stepper_positions):
pos = [stepper_positions[rail.get_name()] for rail in self.rails]
if (self.dc_module is not None and ‘PRIMARY’ ==
self.dc_module.get_status()[‘carriage_1’]):
return [pos[1] - pos[3], pos[1], pos[2]]
else:
return [pos[1] - pos[0], pos[1], pos[2]]

speedcore kinematic.txt (6.5 KB)

in this way all the movements are correct and both homings are in the left corner. if i set a position with both x1 and dual carriage they go as expected.

now the issue: when I set whatever point to probe with ztilt or qgl or bedmesh ,the kinematic is broken, during a clean movement of Y, X1 is not following and goes in a wrong direction ( seems that the x1 motor doesn’t move. is it possible that only ztilt probing use another kinematics? or position calulation? do you have an idea how to fix the issue? do I have to modify set_position?

Welcome clrobotix,

do you have a klippy.log? If yes, please post it.

1 Like

The printer is in the lab, I cannot before next week

1 Like

JFYI: most custom kinematics should be possible and better to implement with generic-cartesian-kinematics, instead of touching the low-level kinematic stuff.
(CoreXY and others are still there for convenience).

1 Like

klippy.log (2.6 MB) log is quite big due to 8 canbus tractors for the custom ams

In such cases you can use ZIP to shrink them.

I fixed the issure. it was the position calc into the kinematic file.

now is fixed as attached

speed_core.zip (1.9 KB)

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.