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!

  • schizo@forum.uncomfortable.business
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 days ago

    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?

    • papalonian@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      2
      ·
      2 days ago

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

      • Paradox@lemdro.id
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        2 days 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

        • fubbernuckin@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          I don’t use Bambu printers, but don’t they use a modified version of gcode and still refuse to let anyone see the documentation?

          • Paradox@lemdro.id
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 days ago

            Nope, they still use bog standard gCode, but they do have some custom commands for things that are unique to the printer

      • schizo@forum.uncomfortable.business
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        2 days 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.