naikymen,
sorry for the late reply, I have been very, very busy working on creating the machine I would use your fork for. |
- |
I will be in touch when I can give your fork a real try as I need the corexy built before I can test the corexy bit unless someone else has already.
-/retnel
I am developing a farm that supports simultaneous 5-axis control of corexy-bc. I have also implemented a simple tool tip control (I have not uploaded a video of this yet). It still takes some time to develop, but I plan to upload it to my github soon. The current version on github also supports simultaneous 6-axis control.
I am getting this error i have fresh installed klipper and installed klipper for cnc, used all your configs and i have a skr pico and a rp pico for 4 external drivers.
trying to use XYZE+A mode which was working till yesterday i think i updated it was giving this error so i reinstalled now i am getting same error again.
klippy(17).log (266.3 KB)
im also getting error to add stepper_b when i use xyzabc, i dont have any more pins left to assign b and c motor
Hi! Thanks for trying it out ad sharing the log. The error is cryptic but the traceback in the logfile is much better. 
The intended syntax for the axis parameter for your use case is just XYZA (no plus signs, no addditional BC, and no E for the extruder).
Sorry if this was confusing in the examples, please point out any errors. I have just cleaned up the cnc_shield_xyza example for you, and added notes to the readme (along with other new parameters).
I have also just pushed to raise a clear config error if any axis letter is not allowed.
It may be that the recent commits use that string for other new stuff, and now fails as it should have. I have also merged upstream.
For any cutting-knife machines out there, I have tried to fix the “shared acceleration” issue that was apparent when the XYZA machine made a sharp turn on XY, and the A axis had to accelerate very quickly to follow. More info here.
I have also added a “symmetric extruder speed limits” option, such that the extruder speed and acceleration limits are always enforced for a particular extruder. This makes sense in some cases. More info here.
also im not using a axis for knife , was planning to use only 1 axis not extra axis for my machine but couldnt get only 1 axis working and had to put stepper_b and stepper_c to for klipper to turn on
Please try something like this:
[printer]
# Regular pritner configuration.
kinematics: cartesian_abc
# Units: mm/s and mm/s^2:
max_velocity: 5000 # F120000
max_z_velocity: 250 # F30000
max_accel: 1000
# Add ABC kinematics to the toolhead:
kinematics_abc: cartesian_abc
axis: XYZA
Note the axis: XYZA setting.
You will then be able to remove the dummy B and C steppers form your config.
Error loading toolhead with ‘XYZA’ (4) axes is unsupported. Use either XYZ (3) or XYZABC (6) axes.
im still getting the error, are you working on this part of this project, should i try this later ?
That’s progress I just pushed a fix for that last bit, and the partial ABC specification seems to be working (with my simulated environment).
Thanks a lot for testing!
I’ve not touched that part in a while, I think it’s good to go. What just happened is that I forgot to stop raising configuration errors on partial ABC specifications when I implemented them (because I was testing on partial XY only) even though they were working. Whoops… 
I’ve not tested homing yet. Are you using dual carriage? I’ve not tested this at all!
i got XYZA working. will try to run gcode.
actually want to using 2 z axis for each toolhead, so im trying to build a cnc router like shapeoko with 2 z axis on x carriage.
with A-Axis i was going to replace letter z with a where ever i needed in code using python script which replaces all z with after T1 in gcode, so A-axus was going to act like my 2nd z axis.
been trying to use dual carriage with z axis as which have been a complete solution for such application with a cnc of 2 or 3 z axis on single x carriage.
edit-
i tried to add
[toolhead_stepper abc]
axis: A
gcode_prefix: U
kinematics: cartesian_abc
max_velocity: 5000 # F120000
max_z_velocity: 250 # F30000
max_accel: 100
and it gives this error
Internal error during connect: cannot import name ‘MoveQueue’ from ‘toolhead’ (/home/pi/klipper/klippy/toolhead.py)
Interesting. How did you arrive at [toolhead_stepper]?
The [toolhead_stepper] section activates an entirely different toolhead class, it was meant to control (and possibly syncrhonize) multiple independent toolheads.
But please don’t use it, as it does not currently work. I’ve just removed it from the default branch to make it clear.
Cool machine
BTW, I just pushed a bunch of fixes for homing with partial ABC specification, and tested them in proper hardware. Enjoy!
i found it here, and thought it would add a axis in toolhead section in dashboard
That would be great, but I’m not familiar with frontend stuff for now.
If someone know who to ping about this, it would be great to add ABC controls to mainsail, if they have been configured.
Thought I’d give it a shot and, surpisingly enough, got somewhere within an hour:
Consider droping a comment over here if you thin this should be in official Mainsail: Toolhead controls for extra ABC axis in dashboard · Issue #1810 · mainsail-crew/mainsail · GitHub
wow, i was going to try it, but you already did it, i feel we can build mainsail for cnc ?
with few more necessary options in web interface such as for probing and spindle, while still keeping all the functions which are already there making it a firmware for cnc and 3d printers
klippy.log (87.5 KB)
i was testing the with all the updates installed, when i added [extruder] and [tmc2209_extruder] in config it would stuck at initializing and did not boot.
edited config over ssh and removed all extruder config it was working again
earlier i had not added extruder in config
edit- I just reinstalled and got it working!
It’s fixed. It has been a while since I tested the fork with a non-homeable extruder config.
Thanks for the report, keep them coming!
this looks interesting. Does it support endstops for 2 x motors and 2 y motors when homing to square a system?
Hmm I don’t remember breaking that feature, but I also don’t have the hardware to test it exactly (I’m also on a month-long holiday).
Given past experiences from this thread, I’d suggest giving it a go and sharing results.
Thanks, I’ll give it a go.
Hi,
Just found this picture, and wanted to let you know.
Klipper would greatly benefit in all aspect from having convenient JOG and MDI tools that are present on almost all traditionnal CNC tools
Here is what that looks like
This comes from page 6-8 of
Before I was permanently banned from reddit, I had asked if there was a proper “Feed Hold” function in klipper, basically a pause button . It seems there is not.
I think this is because “it’s always supposed to be fully automatic” and there’s never supposed to be any error or manual. Or weird things going on with “FULL CONTROL” and the like.
For the experimenters, I believe these capabilities would be invaluable.
Also, there are many CNC pendants available that might easily work with Klipper
Like this wireless one
or that simpler but more ergonomic one
As for MDI mode, perhaps that could be ripped out of LinuxCNC
As I asked in this old post
https://old.reddit.com/r/klippers/comments/151u1zo/is_there_a_klipper_frontend_that_looks_like_an/
