Thanks mate! 
I’ve addeed paypal to the donation/sponsor links on the repo.
Note that at the moment only the “cartesian” kinematic works. Converting others shouldn’t be much work, but you’d have to volunteer for testing.
Cool, I bought you some beer. I am going corexy with linear rails, not cross bars. I would really appreciate your help, and I absolutely volunteer to test. It crashes, it crashes, no biggie.
If you can help me get klipper working with for my mousetrap, I would be happy to give you a a way better tip.
Respect,
/retnel
Thanks @retnel that’s really encouraging, thanks a lot.
I think I got corexy kinematics working, hopefully. Perhaps these stepper positions (right panel) make sense to you, given the position of the toolhead (left panel).
Here is the adapted kinematic: corexy_abc.py
It’s included in the latest commit of the default branch of my repo.
Note that, for now, it can only be used with the full XYZ specification in the printer config section (meaning no partial axes, and no option for ABC, though this could be added). For example this would suffice (since XYZ is implicitly the default):
[printer]
kinematics: corexy_abc
# The rest of your config...
I used simulavr to test that it runs and moves a bit. Full config here, just for reference.
Let me know how it goes. 
So I see the tool head is at X=10 Y=10 Z=10, but in the console I see X=10, Y=0 Z=10. Not sure if that is what is expected from what you have shown me. Is it in subtractive mode?
I am still printing out the parts to put my frame together and get the motors and belts on it. Then I will be able to really test. Until then I can bench test. I think I have a week or more of printing.
I will uninstall my klipper, add your repo, and run KIAUH again to reinstall. Is the correct way to start testing your fork with the latest corexy_abc commits?
/retnel
So I got it configure, but I keep getting this error:
"Error loading kinematics ‘cartesian’. Currently supported kinematics: [‘cartesian_abc’, ‘corexy_abc’, ‘none’]
Once the underlying issue is corrected, use the “RESTART”
command to reload the config and restart the host software.
Printer is halted"
This was my working Printer.cfg, I just changed:
[printer]
kinematics: corexy_abc
As instructed.
my_corexy_printer.cfg (4.5 KB)
I did a full system reboot, and still gives that error.
not my wheel house, so I will just wait to hear from you Below is the klippy.log
klippy.log (139.2 KB)
Thanks,
/retnel
Not sure what subtractive mode is. I was asking about the numbers because I’m not familiar with the CoreXY math I did expect the toolhead position to be different from the stepper positions in that kinematic (which did show).
Thanks for sharing! At first glance, it seems that the config file has duplicate sections for the printer and mcu entries, while the log shows no usage of the *_abc kinematics.
Let us resolve this by PM.
Hi. I am currently building a 4-head 3D printer based on your slightly modified Klipper fork. But I found some various types of errors in the software, which, despite new versions, are not corrected. Where can I report such things? Currently, the bug found in the toolhead.py file in the calc_junction function was quite annoying, but in fact it could not have been noticed by anyone… Overall, great respect for the attempt to create a 7-axis Klipper… with a little refinement, I think the project of my printer will be completed become a success
Hello @Lord! I really appreciate the involvement. I’ll have a look at it over the weekend.
Please create issues over here: Sign in to GitHub · GitHub
Thanks a lot!
Just pushed a fix for that bug. Awesome catch!
There are a few more of them, this one is the current one that I spent two days trying to find 
1 Like
I can see why… sorry about it, and thanks a lot for sharing. I’ve been really busy building machines for most of 2023, and haven’t had time to test stuff thoroughly.
Would you mind telling me what the symptoms were? I only barely understand that part of the code.
I’m now also worried about the other bugs. Looking forward to your reports.
I can even show you how it looks in real machine In simply words, this function calculates the velocity change at junction of two separate move sections. It calculates start and end velocity of each part of particular section. With this bug, all stright lines eg. rectangle, etc… was printing good. Problem shows up when i want to print circle. Where is a lot of lot of short lines. Print head starts to behave strange… but it was a long two days until i found that is problem with velocity and not with something else. Look, this is pure klipper - it behave normal: https://youtu.be/MydhYkmbndg and this is with bug: https://youtu.be/JIJIeGc-HPU After all it’s obvious … but then… it wasn’t Other bugs isn’t that scary They became already when you wanted to use some functions, eg. bedmesh, bltouch, etc… Well, maybe it’s not bugs… i think that you simply didn’t touched that part of code But… wait, one thing was serious… G92 command… there is big mistake, maybe intentionaly, maybe not. G92 should reset/set selected axis eg. G92 E0, but in your code it’s reset all axis to 0 ignores any parameters. It’s huge problem with 3D printers, where you reset only E axis
1 Like
Yes I too recently noticed that bedmesh does not work. I’ve not updated most extras modules to work with my changes, and bedmesh fails because of the changes to the probing module.
Fixing that is on the back of my mind. Bed meshing would be nice for PCB milling too.
Excellent catch! Not intentional at all, 100% honest mistake.
Just pushed your fix for it . Let me know if you are considering opening a merge request and I’ll wait for it instead.
I see that meanwhile you patched the probe.py file, that bltouch can run now properly - good In bed_mesh.py there is a bunch of lines to change… and this will be hard to do that by screenshots 
But i can’t send you the whole file cause it contain also the specific addons only for my machine. About “opening a merge” - i completly don’t understand what does it mean 
I don’t use GitHub that way and i can’t do anything there beside copy the code and download files But i will think something
Ok, let’s do this in old fashion way… i don’t have another idea
I know that in modern days it should be done something different… but… i was born in previous century… It most important, that we both know what is all about
In extruder.py file there is also a couple of thing to change… but here I can add only one image per post and only 3 replies one by another… i’ll wait for your answer or try to do something on GitHub meanwhile
Ok, i’m thinking that i learn something new I think i created “pull request” for the extruder.py file at GitHub Can you confirm this? I’ve never done this before
1 Like
Wonderful thanks!
I’ve pushed a bunch of changes and merged upstream while I was at it. The bed mesh seems to be working on my lab’s Ender3 with BLTouch (or at least does not fail hehe). 
You’ll notice the changes are a bit different from your patch (thanks again!). I’m trying to keep stuff flexible around the number of axes in the toolhead. Time and users will tell if this is useful or not.
I’m happy bed mesh is working, kudos to you.
I will definitely use this eventually for microbiology stuff (i.e. drawing on agar plates).
Thanks to Klipper @naikymen was able to create a virus that turned 80% of humanity into 3D printing addicts.
Not sure if our marketing department will like it, but then again, we have none. 
3 Likes
Flawless! Merged just now. 
Good to know From now on i’ll make all corrections in this correct way by GitHub It’s a pleasure for me to could make my small part to develop such great thing like 7-axis klipper In a free time i will compare current code to mine and maybe i will suggest something new But i think that was all for now what dosn’t allow to work with bltouch, bed_mesh and four extruders on XABC axis
1 Like
No market? Oh…no marketing.
Got it. I think you guys should hire me to say it works no matter what you think!
Now, will it sell? No clue, I am not a salesman but I am a person with a lackluster for all things that are relative to something.
If I find others like me who hold no view on others or have no others having a good view on me, I could make something out of it. heh?
Seth
P.S. Anyway, build here and build there. Build everywhere! I am not passing by. I am staying, i.e. although I seem perturbed or upset, I am not. I am more reluctant to understand another’s plight. Okay…done for now. As you were!