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?
3DPrinting
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 ![](URL)
Moderation policy: Light, mostly invisible
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.
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.
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.
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.
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
Adjust with paper and the knobs first to get it mostly level then use the ABL probe. "Auto bed leveling" is a misnomer. It generates a mesh of the bed and then compensates in software but it can only do so much.
I've tried that already, no matter what order I do things in, instead of printing it just keeps going through the ABL process. It will heat up the nozzle and the bed, and then just probe the bed in 16 different places, then center itself, and start over.