config: define generic_cartesian corexy example#7201
config: define generic_cartesian corexy example#7201nefelim4ag wants to merge 1 commit intoKlipper3d:masterfrom
Conversation
Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
5b07a53 to
f24fcb7
Compare
|
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:
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, PS: I'm just an automated script, not a human being. |
|
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? |
|
@PLMD86, as mentioned in the topic and in the PR, this is an example intended for RatRig V4 Hybrid. Hope that helps, |
I'll do some testing tomorrow and see if I can figure it out. Thanks for your input. |
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: