Support for Hybrid CoreXY

General Discussion
1

Basic Information:

Printer Model: Vcore3.1 to Vcore 3.2h
MCU / Printerboard: Octopus Max
Host / SBC rPi4
klippy.log - Not necesary

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:

Hi

I’m in the process of updating my printer, and the kinematics are changing.

The previous version, Vcore 3.1, is (was) a coreXY.

But… After the update, Vcore 3.2H becomes a Frankenstein’s monster, a HybridXY. I think Makeforge printers use a similar kinematic.

However… when looking into how to configure it, I read (at least I did before; I don’t know if they support it now) that Klipper doesn’t natively support this kinematic, and I don’t want to use RatOS. It’s a very customized distribution, with many links and difficult to follow if you want to change something. I’d like to continue as I am, with Fluidd and Klipper.

I have several questions:

  • Does Klipper already natively support the kinematics of Vcore 3.2h?

  • Are there any plans for it to support it in the future?

  • This idea is possible… (take that kinematics and install it on a regular Klipper, or install RatOS and use my current configuration files, keeping the new kinematics)

  • What other options do I have? (To avoid using RatOS and still have that kinematics)

…

2

natively support the kinematics of Vcore 3.2h

You have to use generic_cartesian, it should support all possible kinematics, corexy & etc.
Old kinematics code here is for backward compatibility. to not break existing confings.

-Timofey

3

Where i can find info for use these model?

4

Well, there is documentation and some posts on the discourse.

I think I will write the example generic CoreXY config and make a PR.
Then, later, it can be reused to define additional motors to make it work as a hybrid.

I guess, here is some example: Issue with hybrid_corexy

-Timofey

1 Like
5

I think I’ll try another approach. I’ve looked at the post and it’s not clear to me…

Would this other approach be possible? I suppose so, but…

  • Install RatOS, the Ratrig fork of Klipper, which supposedly has support for the Hybrid CoreXy.
  • Delete all the *.cfg configuration files (there are dozens) except for those related to the printer configuration, which I think are in [printer].
  • Copy my current configuration files.
  • Adjust the automatic update paths, leaving only the Klipper one, and the rest only the ones I currently have.

Do you think this might work?

6

I did an example CoreXY anyway.

Where RatRig style hybrid probably should work with additional:

[stepper stepper_y0]
carriage: carriage_y

[stepper stepper_y1]
carriage: carriage_y
1 Like
7

I don’t quite understand this machine definition thing… I’m putting what I think it is here, and please correct me if I’m misunderstanding anything.

  • To start configuring a 3D printer in Klipper, you have to define it.

  • To define the machine’s characteristics, you do it under the [config] section of the *.cfg files.

  • One of the most important definitions is the machine type, which is done in [config] kinematics:

  • Kinematics can be (cartesian, corexy, corexz, hybrid_corexy, hybrid_corexz, generic_cartesian, rotary_delta, delta, deltesian, polar, winch, or none)

  • The Vcore 3.2H has a kinematic called (hybrid_corexy)… but that kinematic is NOT the one used by the Vcore 3.2H. The vcore 3.2h uses a cinematic called (hybrid-corexy) “note the hyphen”, which is not (hybrid_corexy), the latter being used by Stratasys printers.

  • If I used that cinematic on my printer, it wouldn’t work properly; I might even risk damaging something.

  • To use the cinematic that vcore 3.2h uses, I have to redefine it, which I have no idea how to do. Alternatively, I could install RatOS, a fork of Klipper modified by RatRig, the creators of the project, to support their cinematic.

  • The other option I’m considering is installing RatOS, which already includes the cinematic, and deleting all the configuration files, replacing them with the ones I already have, but keeping the one that defines the printer, the one with the (printer) section.

  • nefelim4ag has already done this work; he has defined the machine.

More info, another option:

In my research process I’ve read that I can install (SankOilXY Klipper extended corexy module) which supports this kinematics… could someone confirm this for me?