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: [email protected] or [email protected]
There are CAD communities available at: [email protected] or [email protected]
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 
Moderation policy: Light, mostly invisible
view the rest of the comments
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?
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.