Skip to content

config: define generic_cartesian corexy example#7201

Open
nefelim4ag wants to merge 1 commit intoKlipper3d:masterfrom
nefelim4ag:generic-cartesian-corexy
Open

config: define generic_cartesian corexy example#7201
nefelim4ag wants to merge 1 commit intoKlipper3d:masterfrom
nefelim4ag:generic-cartesian-corexy

Conversation

@nefelim4ag
Copy link
Collaborator

@nefelim4ag nefelim4ag commented Feb 17, 2026

Simply config reference for CoreXY over generic_cartesian.
Where it should be pretty straightforward to add additional steppers to enable a ratrig-like hybrid CoreXY kinematics.

I did one print after the migration :D

I personally like generic cartesian defenitions for CoreXY over existing CoreXY, because there is no inherently confusing stepper_x and stepper_y definitions.

Thanks,
-Timofey

Ref: https://klipper.discourse.group/t/support-for-hybrid-corexy/25641


Where RatRig style hybrid probably should work with additional:

[stepper stepper_y0]
carriage: carriage_y

[stepper stepper_y1]
carriage: carriage_y

Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
@nefelim4ag nefelim4ag force-pushed the generic-cartesian-corexy branch from 5b07a53 to f24fcb7 Compare February 17, 2026 17:53
@github-actions
Copy link

github-actions bot commented Mar 4, 2026

Thank you for your contribution to Klipper. Unfortunately, a reviewer has not assigned themselves to this GitHub Pull Request. All Pull Requests are reviewed before merging, and a reviewer will need to volunteer. Further information is available at: https://www.klipper3d.org/CONTRIBUTING.html

There are some steps that you can take now:

  1. Perform a self-review of your Pull Request by following the steps at: https://www.klipper3d.org/CONTRIBUTING.html#what-to-expect-in-a-review
    If you have completed a self-review, be sure to state the results of that self-review explicitly in the Pull Request comments. A reviewer is more likely to participate if the bulk of a review has already been completed.
  2. Consider opening a topic on the Klipper Discourse server to discuss this work. The Discourse server is a good place to discuss development ideas and to engage users interested in testing. Reviewers are more likely to prioritize Pull Requests with an active community of users.
  3. Consider helping out reviewers by reviewing other Klipper Pull Requests. Taking the time to perform a careful and detailed review of others work is appreciated. Regular contributors are more likely to prioritize the contributions of other regular contributors.

Unfortunately, if a reviewer does not assign themselves to this GitHub Pull Request then it will be automatically closed. If this happens, then it is a good idea to move further discussion to the Klipper Discourse server. Reviewers can reach out on that forum to let you know if they are interested and when they are available.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

@PLMD86
Copy link

PLMD86 commented Mar 4, 2026

I am looking for a solution for the ratrig v core 4 hybrid without using ratos because I have to make a multitool system using klipper....do you think using the Cartesian system could work?

@nefelim4ag
Copy link
Collaborator Author

@PLMD86, as mentioned in the topic and in the PR, this is an example intended for RatRig V4 Hybrid.

Hope that helps,
-Timofey

@PLMD86
Copy link

PLMD86 commented Mar 4, 2026

@PLMD86, as mentioned in the topic and in the PR, this is an example intended for RatRig V4 Hybrid.

Hope that helps, -Timofey

I'll do some testing tomorrow and see if I can figure it out. Thanks for your input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants