-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation of Delta Keops Kinematics #3216
Comments
Hi @ReprapRyn, It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions). Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days. For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md The log can still be attached to this ticket - just add a comment and attach the log to that comment. Best regards, PS: I'm just an automated script, not a human being. |
Interesting. This would require both python and C host code to be written. (It would not require new micro-controller code though.) At a quick glance it does not seem too difficult to implement the C kinematics code. (If the angle and position of each rail is known, then I think one should be able to rotate the desired cartesian coordinate into a coordinate system where the rail is at the origin and then use the Pythagorean formula to calculate the rail position.) I should be able to assist with the low-level kinematic code. If you're looking for this help, it will be necessary to have the robot built and the steppers functional. (When ready, configure the robot using cartesian kinematics, verify stepper_buzz works on all the steppers, and then attach the resulting klippy.log file here.) I'd also need to know the dimensions and locations of all the rails and endstops. FWIW, I suspect the calibration of this type of robot will be harder than a typical linear delta robot. I'd guess it will have similarities to the rotary delta (discussed a little bit at #1610). Cheers, |
Got it Kevin, thanks. I should have the robot design finalized and start building it soon. |
Hello, It looks like there hasn't been any recent updates on this Best regards, ~ Your friendly GitIssueBot PS: I'm just an automated script, not a human being. |
I am currently developing a new type of Delta printer, based off the Delta Keops delta robot system as seen in several research papers and manufactured commercially by Igus and Dierre Robotics
https://www.dierrerobotics.com/en/delta-robot-series/
https://www.igus.com/info/robotics-delta-robot
IEEE explore had an article from Dr Clavel (the original developer of linear delta technology) about the strengths of this style of linear delta robot, such as increased system rigidity and increased movement space in the X and Y plane (sacrifices some Z). It also can work as a component robot lending itself to future toolchanger and belt printer systems.
https://ieeexplore.ieee.org/document/5756938
Inverse kinematics information is in the information below from the original research paper from the University of Pamplona. also useful information from Servotronix
http://softmc.servotronix.com/wiki/DELTA_robot_-_linear_model
http://www.unipamplona.edu.co/unipamplona/portalIG/home_40/recursos/04_v19_24/revista_23/27092014/15.pdf
I would like some help with implementing the Klipper kinematics side while I build the necessary hardware. goal would be to release as a new Reprap variant. Would the Klipper delta planner be able to support this style of linear delta robot or would I need a new C file as well?
The text was updated successfully, but these errors were encountered: