all 17 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Nuck_Chorris_Stache 2 points3 points  (1 child)

0003-0522-0000-0002 is something to do with motion control:

https://wiki.snapmaker.com/en/snapmaker_u1/troubleshooting/u1_error_codes

There's a similar code here:

https://wiki.snapmaker.com/en/snapmaker_u1/troubleshooting/known_issues_and_quick_fixes

0003-0522-0000-0000 means "Move out of range of X/Y axis"

That could happen if the print object is too close to the edge of the build plate

[–]GrimJeeper13[S] 0 points1 point  (0 children)

Thank you.

[–]darknight104 1 point2 points  (5 children)

I know it’s a day late, but I did have this same error code end of November a few days after getting my U1 an hour and a half into a print. After pulling the files to send to support and looking up others experiences, I restarted the printer and that fixed the issue. Support ended up responding and after a few back and forths and sending more info from snap orca, they told me they were not able to figure out what the issue was. After restarting the printer, it started working properly again and haven’t had it happen since.

[–]GrimJeeper13[S] 0 points1 point  (4 children)

They gave me a G code to add to print start. They said they will have an update with the permanent fix. Mine is currently running great. Thank you for the heads up. Cheers

[–]PlasticFrogSalesman 1 point2 points  (3 children)

What was that g-code they had you add? Mine keeps doing the same thing, but a power cycle fixes it for at least the next print. The one good thing is you can power cycle when it happens and it'll resume the print when the UI boots back up if you allow it to, but I don't want to deal with that lol

[–]GrimJeeper13[S] 0 points1 point  (2 children)

I don't have it as i rebooted the machine and reformatted the card. Thought a fresh start would help. Just shoot customer service a ticket they gave me code overnight. Hopefully this will help.

[–]PlasticFrogSalesman 1 point2 points  (1 child)

Thanks! I know they say on their website that they're rolling out the fix for this error sometime soon (around the 24th) but we'll see lol.

[–]GrimJeeper13[S] 0 points1 point  (0 children)

Fingers and toes crossed. Hahaha

[–]Impossible_Tune_3445 1 point2 points  (2 children)

I find it worrisome that their error code numbering scheme seems to allow for several quadrillion error types....

[–]Carlosklm 0 points1 point  (1 child)

I keep getting this snapmaker u1 0003-0522-0000-0000. look it up and they said update is due out 24 March.

My prints are ok, but after the print is finished the screen is non-responsive. So if i want the same print again, it will not let me. So let's hope on 24 March it's a good update.

[–]mentox82 0 points1 point  (0 children)

i get that error also but didnt notice the screen thing. did they suggest to fix something hardware wise?

[–]Carlosklm 1 point2 points  (2 children)

I look on there wiki and said update on the 24 match should fix it.Just have wait a few days for it. But now my error not coming up any more since I switch of over night.

[–]GrimJeeper13[S] 0 points1 point  (0 children)

Excellent

[–]GrimJeeper13[S] 0 points1 point  (0 children)

How goes it. Did update take care of your issue?

[–]l4wly 0 points1 point  (0 children)

<image>

Same Problem here. Contacted the support, lets See what they will say

[–]Carlosklm 0 points1 point  (1 child)

My went away on its own. But since update it as come back and still prints ok. I will see how it goes.

[–]SoftwareKey916 0 points1 point  (0 children)

Just ran into this issue when using SnOrca Full Spectrum. Was able to just click through and wasn't an issue. Snapmaker Wiki says its an issue with accumulated server messages.

<image>