3DPrinting
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: or [email protected]
There are CAD communities available at: [email protected] or [email protected]
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
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 
Moderation policy: Light, mostly invisible
view the rest of the comments
I agree with most of your points, but I do wanna say that in regards to the last mark, there are reasons besides contributing to the code and building your own firmware to want to use something like Klipper. I'm not a programmer at all but the amount of customization and QOL tools I can achieve compared to what you're able to do with Bambu's software is insane. I can never go back to a printer without custom macros
What is a macro in this context that requires custom firmware?
My googling makes it just look like gcode stuff to work around hardware issues, but I'm confused how that requires Klipper, since you can drop any gcode block you want into any slicer I've ever seen?
You can drop any block of g-code into your slicer, but that would require running the file to get the commands to run. In Klipper, you can just run the macro.
For example I've got a "enclosure heat" macro that
Sets bed temp to 100 and extruder to 280
Turns all fans to max
Moves my print head in front of my webcam (there is an ambient temp display on the print head)
I can do all of these manually, of course, but with a macro I can just push a button and it does all of it.
It also makes it so you don't have to paste those entire g-code command blocks into whatever file you're slicing, and so that you can retroactively change commands. (Instead of having the entire startup sequence at the beginning of every g-code, I have a "START_PRINT" macro at the beginning; if I change the macro, all of the files I already sliced will have the updated behavior).
Oh, that's neat and I can certainly see why that's useful.
I have to do a little gcode header swapping by hand because I'm cheap and bought a p1p and am certainly making it do things it's not really designed to do, and that kind of functionality could save a bit of time.