After my last printer broke, I am considering getting this one for it’s high precision, vibration stabilisation, and other good features, but wanted to check your experience with it before going ahead.

  • kek_w_lol@lemmy.one
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    So I have used the sv06 and had a bit of a run in with the sv07. Both are decent machines with their own quirks. The sv06 needs bearings replaced after 3 months of use at the latest, after that runs perfectly. The sv07 uses v-wheels, and is therefore lower maintenance. They both use the same toolhead design and both print well enough. sv07 is a bit more finnicky with cooling (special klipper command for the big fan) but they are both decent machines. I personally run a heavily modified Ender 3 v2, but currently, the Sovols are some of the best bang for the buck. Right now, I would buy the sv06, change the bearings from day one and that’s it. It is basically a 1:1 copy of a Prusa, and printing replacement parts for it is extremely easy, if anything ever breaks. The only thing it “lacks” is a filament sensor (haven’t had the need for one in the time I have been printing), but that is easily added. Do your own research though. Lost in Tech has some great reviews on both machines.

    • JackGreenEarth@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      The SV07 (just now) the firmware almost immediately broke after I put it together, powered it on, started it autoleveleling and the stopped it because it was screeching, and the rebooted it. Now it won’t power on without showing green text, or doesn’t progress past the loading screen, or doesn’t turn on at all. It’s different every time.

        • JackGreenEarth@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Uk. The firmware suddenly resolved itself, but now the y axis (the bed) doesn’t seem to be moving properly, it tries to move off where it can’t, and says ‘out of range’ to moving where it can.

          • kek_w_lol@lemmy.one
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Just in case, check the PSU Voltage. Check the plugs on the Y axis motor. Worst case, you might need to redownload the CFG file for your printer. Try that. Write again if none of that works.

            • JackGreenEarth@lemm.eeOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Thanks for outlining the steps, but I’m not sure what each thing you recommended entails. Are you able to explain it in more detail please?

              • kek_w_lol@lemmy.one
                link
                fedilink
                English
                arrow-up
                2
                ·
                edit-2
                1 year ago

                So, the PSU voltage switch is for setting input voltage. You might be running it on 110V instead of 230V, though unlikely but it doesn’t hurt to check.

                Checking the y motor and endstop wiring I recommended because I had a similar problem on my x-axis when my motor wire and endstop wire came loose, where the motor was jittering and buzzing, but not moving.

                The .cfg file is the configuration file for Klipper firmware, which is taylored for your printer. Since you said that your firmware issues got fixed I don’t think that’s it, but if nothing else, redownload and reinstall the .cfg file and if that does not help, reinstall klipper as a last resort. Do so only if nothing else helps.

                If you need more help, I could help you through video chat. Just DM me.

                • kek_w_lol@lemmy.one
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  1 year ago

                  If anyone is interested, the problem was due to packing material not being completely removed from under the printbed.