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.
If you’re still on stock firmware I’d suggest taking a look at mriscoc professional firmware since it includes UBL. Which will probe the 4 corner which your crtouch and then show you a visualisation of how much each needs to be adjusted up or down.
When I first got my Ender 3 S1 Plus (same motherboard AFAIK), it would similarly freeze during the ABL. In my case, the issue was that I’d actually leveled the bed too low, and the machine was freaking out because it had to pass the software Z limit to home the printer. I loosened all the bed screws (raised the bed) by as many full turns as it took to have the bed’s screws just barely fully through the adjustment knobs, then releveled, reran the ABL routine, and finally all worked without a crash. This may or may not be your problem.
In any case, I do recommend checking to make sure you’re on the latest official factory firmware version, and if not update it with the latest firmware from here. The instructions are there, too.
Ultimately I got it working, but I ended up moving away from the janky stock firmware and putting Klipper on it instead after a few weeks.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !3dprinting@lemmy.world
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:
!functionalprint@kbin.social
or !functionalprint@fedia.io
There are CAD communities available at:
!cad@lemmy.world or !freecad@lemmy.ml
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 
I have a Ender 3 S1 plus and I can help you but next week (very busy this week-end). If you’re not in hurry, I’ll help you monday. Sorry
If you’re still on stock firmware I’d suggest taking a look at mriscoc professional firmware since it includes UBL. Which will probe the 4 corner which your crtouch and then show you a visualisation of how much each needs to be adjusted up or down.
Can you post your start g code?
When I first got my Ender 3 S1 Plus (same motherboard AFAIK), it would similarly freeze during the ABL. In my case, the issue was that I’d actually leveled the bed too low, and the machine was freaking out because it had to pass the software Z limit to home the printer. I loosened all the bed screws (raised the bed) by as many full turns as it took to have the bed’s screws just barely fully through the adjustment knobs, then releveled, reran the ABL routine, and finally all worked without a crash. This may or may not be your problem.
In any case, I do recommend checking to make sure you’re on the latest official factory firmware version, and if not update it with the latest firmware from here. The instructions are there, too.
Ultimately I got it working, but I ended up moving away from the janky stock firmware and putting Klipper on it instead after a few weeks.