this post was submitted on 04 Aug 2024
17 points (94.7% liked)

3DPrinting

15600 readers
223 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago
MODERATORS
 

Hi all, got a bit of a technical problem I'm trying to solve and I've got very little programming experience.

Basically, I'm trying to create a folder with a bunch of filament profile cfg files, with things like retraction distance, temperature, flow rate etc preloaded into them. That way, I can slice a model for a 0.6mm nozzle, send it to Klipper, and run it with any filament I want without having to re-slice, just change which cfg file is loaded.

This is going pretty well and I've figured out how to get most of what I want into the cfg. However, I want to limit my print speed by my maximum volumetric flow rate, a variable that Klipper does not support (and Kevin has more or less denied requests to have it added). To solve this issue, I want to limit the max speed instead, using a formula like this:

print speed = (max vol. flow) / (nozzle width) / (layer height)

(max vol. flow) and (nozzle width) would be defined manually by me for each profile. The only issue is (layer height), which of course can change from print to print. I know that my slicer puts the layer height and total number of layers in the header of the gcode, I also understand that that's where Klipper gets this info from and how it displays those numbers once you've selected a file. What I'm having trouble figuring out is how I can send that number into the above formula; I found this which seems to be almost what I need, but I can't figure out how to use the "print_stats object" in my cfg.

A potential workaround is to find my maximum layer height for each nozzle/filament combo and set the max speed assuming that later height, but if I'm printing something at say half my maximum layer height that's going to severely unnecessarily reduce my print speed.

Any advice?

you are viewing a single comment's thread
view the rest of the comments
[–] papalonian@lemmy.world 3 points 3 months ago (7 children)

I've managed to get Cura to display the layer height in the startup code, what I can't do is get Klipper to do anything with that value.

If I try to create a variable and define it's value as {layer_height}, Cura doesn't pass the variable's value, instead it just defines the new variable's value as "layer_height"

[–] anguo@lemmy.ca 2 points 3 months ago (6 children)

Could you set the speed in the slicer instead of Klipper?

[–] papalonian@lemmy.world 1 points 3 months ago (5 children)

I could, but the entire purpose of what I'm doing is to avoid having any material-specific settings set in the slicer, so that re-slicing between filaments isn't necessary.

I actually got this working last night, I had to learn a lot about how variables work but it works like a charm:

  1. Slicer names a variable for layer height in the start gcode of every print

  2. cfg file for each filament contains a max volumetric flow for that filament/nozzle

  3. a macro takes these values and the layer height and finds a max speed for the given parameters

  4. a second macro assigns this value to the "speed factor" percentage

  5. print speed in slicer is set to 100mm/s, travel speed is set to 9999mm/s; say the equation limits my speed to 55mm/s, it sets speed factor to 55%, now moves with extrusion will be 55mm/s (travel will be 5500mm/s but limited to 500mm/s by printer's max speed)

All other filament/nozzle settings were really easy to bake into the cfg file, there's just no official Klipper support for a max volumetric flow so I had to jank this system together.

[–] anguo@lemmy.ca 1 points 3 months ago

Glad to hear you got it working!

load more comments (4 replies)
load more comments (4 replies)
load more comments (4 replies)