this post was submitted on 24 Dec 2024
46 points (100.0% liked)

3DPrinting

15770 readers
38 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: or [email protected]

There are CAD communities available at: [email protected] or [email protected]

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 2 years ago
MODERATORS
 

I'm just getting into 3d printing and I'm looking for some recommendations. My budget is $400 and I've narrowed it down to the sv06+ or the Ender-3 V3. I like that the print size is bigger on the sv06+ but all reviews point to the Ender, do you guys have any recommendations for me?

Also maybe the bambu a1? Or a1 mini? I don't like that the firmware isn't open source though.

I'm OK tinkering but just want some insight.

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 17 hours ago (1 children)

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?

[–] [email protected] 3 points 15 hours ago (2 children)

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

  1. Sets bed temp to 100 and extruder to 280

  2. Turns all fans to max

  3. 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).

[–] [email protected] 0 points 12 hours ago

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.

[–] [email protected] 3 points 14 hours ago

You can run and save custom gCode on Bambu printers. I've got a cold pull script that lives happily on my x1c, and can be triggered any time