PavelM
June 15, 2023, 12:06pm
1
Basic Information:
Printer Model: Custom
Describe your issue:
Greetings. I am building a custom 3D-printer. Currently I decided to use “winch” kinematics, although it’s somewhat different. My printer uses 4 carriages. To move base in x axis all of them should move in sync. The problem is that “winch” kinematics doesn’t have rails. How should I change the code to add rails functionalities? I want to set up homing with G28 command. Thanks in advance!
P.S. - I have added a photo of my printer, so you can see how it moves, as my description is pretty basic.
Sineos
June 15, 2023, 3:29pm
2
The document Code overview - Klipper documentation contains some information on code organization and steps needed to define a new kinematic.
Maybe this will help as well:
opened 04:22PM - 17 Feb 18 UTC
closed 01:29AM - 21 Apr 19 UTC
First of all thank you for this fantastic program. It has done wonders for my li… ttle 28byj-48 steppers and enabled my project.
I am trying to add support for a new type of printer to Klipper.
I call it Tetra - a type of hangprinter (see Tetra 3D printer group on facebook). The effector is suspended in three anchors with a stepper driven spool at each anchor.
This means that the stepper position is effectively equal to the arm length of each wire.
I have made a fork with the hope to provide a pull request in the future [here](https://github.com/JonasForssell/klipper/blob/Tetra/klippy/tetra.py), and have managed to adjust most of the Delta class code but I am now stuck.
I need hints on how to adjust the code in the move method. The step_delta code runs deep into Klipper through stepper and mcu classes and I am unsure if I should use this or perhaps step_const instead. I do not understand why there are two ways to drive the steppers when the kinematics already have been done.
A little help would go a long way.
I hope posting this request here is not a problem. If so, please feel free to delete it.
Best Regards
/Jonas