Improving Cura for Klipper and Smooth Motion Firmware 🏃 #16012
Replies: 8 comments 8 replies
-
I personally maintain Fluidd (Klipper web interface) and regularly contribute to Klipper, Moonraker (Klipper API server), and even Mainsail (another Klipper web interface). I use Cura exclusively as my go-to slicer when I want to print in "Klipperized" printer, and have used quite a few hacks to make it compliant with Klipper (most of those hacks are currently pinned posts on the I also have a Cura script that "prepares" gcode for Klipper: https://github.com/pedrolamas/klipper-preprocessor Here are some things to consider: Output Moonraker compatible metadataCura could automatically include print metadata so that Moonraker can read it. Currently, users can it manually following this procedure Output
|
Beta Was this translation helpful? Give feedback.
-
I'm a Cura Klipper user. My thoughts are.
https://gist.github.com/ChipCE/95fdbd3c2f3a064397f9610f915f7d02 |
Beta Was this translation helpful? Give feedback.
-
I'm a newbie hobbyist (1 year now) with only an Ender 3 v2. (Now moderately modified. But still on Marlin.) But since you asked... Whatever you do for Klipper, please keep it simple, like Cura is already. Continue to keep it so that my mom can easily use it. (Which covers me as well.) For example, although Prusa 2.6.0 has arguably leap-frogged Cura in features/enhancements - and so is "better," I still use Cura because I like the way that Cura has "compartmentalized" the multitude of settings. (E.g., putting all the filament settings in one place, independent of the model. (Making it more ergonomic to use.)) So whatever you do, please don't clutter Cura when you add Klipper stuff. It should be transparent (invisible) to those of us using Marlin. (So perhaps a plug-in that users have to add themselves?) Next, is Klipper support really necessary? Although I don't need Klipper for what I do, I've thought about it. But when I watch the (hour long) videos on how to run Klipper, my eyes glaze over. I'm reminded why Linux has never caught on. I am NOT going read a "ton" of (arcane?) documentation nor hack my way through a bunch of code to run Klipper. (While I can modify config.h for Marlin and build a "custom" firmware, hacking at Klipper and jumping through a great many hoops But is post-processing for Klipper truly important right now? With the recent additions of LA and IS to Marlin, I don't need Klipper. My Benchy time is already down to 1 hour, from 1:43. And for those who do need the scripts/tweaks for Klipper, they have demonstrated here that they already know what to do. So there doesn't seem to be an urgent need at this time. Certainly if UltiMaker goes Klipper, and perhaps if a majority of new printers come stock with Klipper someday, then you'll have to offer a solution. But for now, while I'm glad that you all are looking ahead, I suggest spending your resources on continuing to improve the ease of use of Cura for the majority of your users. |
Beta Was this translation helpful? Give feedback.
-
I use klipper and one of the things that keep me away from using cura now is that nonsense of using "EXCLUDE_OBJECT_DEFINE NAME=NOMESH" |
Beta Was this translation helpful? Give feedback.
-
@MariMakes and Cura Team: Would you be so kind to share some more information on the new |
Beta Was this translation helpful? Give feedback.
-
How do I set up Cura to work with my new Wanhao D12/500 pro max? |
Beta Was this translation helpful? Give feedback.
-
@MariMakes I see that there is a new 5.6.0-beta.1 and it bring improved variable handling on the start g-code - thank you for that!! I would however like to enquire if there has been any improvement on the multi-part markers on the g-code? The existing Cura comments on the g-code are all that we have right now, but this is insufficient to allow for proper part cancellation on a multi-part print... |
Beta Was this translation helpful? Give feedback.
-
As my predecessors have already written here, I would like to see the following list of things (sorted by personal priority)
I would be very happy. I have only used Prusa (sometimes OrcaSlicer) for a long time. However, I often find that the many parameters are often implemented incorrectly. With Cura, I have not noticed any comparable errors, e.g. with overhang and bridging or travel routes through the support structures. Less is more. Let's go, Cura team ;-) |
Beta Was this translation helpful? Give feedback.
-
When developing Cura 5.4 we spend quite some time resolving unwanted microsegments that would show up on curved surfaces. These would result in drops in printed part quality. It was not something that would show up on all 3D printers but for 3D printers that run on Klipper, Smooth Motion, or Jerk Limited firmware. This should now be resolved in Cura 5.4 stable.
We see that there is a rise in 3D printers that are running Klipper firmware. As UltiMaker employees we focus on the motion controller that our UltiMaker printers use. So we are less exposed to the finer details of Klipper. But we are interested and want Cura and Klipper to work smoothly together.
Our amazing community member @jjgraphix worked on a plugin that already covers a lot.
We highly recommend checking them out here: https://github.com/jjgraphix/KlipperSettingsPlugin
But we've also seen feature requests on Github and on our Forums that mention things like this;
We cannot make any promises that we can resolve them all, but leaving a comment would help us understand what we can do better and what has priority.
What can we do to make Cura better for Klipper printers?
Beta Was this translation helpful? Give feedback.
All reactions