I just got my printer, got it all set up, followed all the instructions, and it looks like it should be working, but it’s not.

I’ve gone through the auto bed leveling, then adjusted the height with a piece of paper. Now, trying to run my first test print, the only thing the printer will do is attempt to auto-level itself. If I let it go, it will just do it over and over. If I hit the stop button, it gives me error message 203 (Probing Failed), the screen locks up, and the printer keeps attempting to auto-level over and over. The only thing I can do is turn it off.

What am I missing?

Edit: So it turns out the included test files are no good. I downloaded a benchy and it printed just fine.

  • Moose@moose.best
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    This sounds like it could be a start gcode issue. What slicer are you using and did you use a preset profile or set it up yourself? Have you tried printing with the included test files that were on the SD card, and if so, did it start correctly?

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

      This is with one of the included test files. I even followed the set up video that goes through the leveling process. I haven’t touched anything else outside of the printer itself and the included SD card.

      If I manually start the ABL process from the settings menu, it completes it fine. But when I try to start printing, it just does it again and again and gives me an error if I stop it.

      • Moose@moose.best
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Yeah thats weird, I was thinking instead of recalling the mesh it was re-running it instead. It may still be from that but I figured the pre-sliced test files would work fine if that were the case. I’ve set up about 10 S1 Pro’s at this point and haven’t encountered that before. As someone else mentioned it may be worth looking into aftermarket 3rd party firmware options. If its not a gcode issue that leads me to think its something with the printer firmware. At work right now but let me know if you need any help and I’ll try to reply tonight.