Error Code: 0003-0522-002-0012 using OrcaSlicer

U1 Toolchanger
1

Slicing in Orca slicer always causes the error “0003-0522-002-0012” when printing on the U1. I’ve tried:

  • The homing it suggests (several times although I’m willing to try it again in your way)
  • Powering down, unplugging, reset … sort of things
  • Many different models (tiny ones, simple ones). Snapmaker Orca alwas works but OrcaSlicer never works (always fails with the same error).
  • I’ve set the printer to snapmaker U1 in OrcaSlicer
    • Under: printer settings > Basic Information > printable height: I’ve changed this from 300 to 270 (not sure why this was this way but its wrong)
    • Under: printer settings > Extruder X (all) > Z-hop height: I’ve set this to 0
      • Note I did this for all Extruders
  • I’ve had this problem for a while the firmware update I did today did not help it.

I’m out of ideas. I’ve probably tried more things but if you suggest I will try it again.

Notes:

  • It fails before starting the print. I don’t think it even starts the calibration.
  • I’m new to OrcaSlicer so it could be something simple
2

Your issue is a machine failure and I guess it does not depend on the slicer.
This is the wiki information, but you already knew it obviously:

0003-0522-0000-0012 Axis Movement Anomaly Tap Home first, then move the X axis.
https://wiki.snapmaker.com/en/snapmaker_u1/troubleshooting/u1_error_codes

If you have the latest firmware as you mention the homing process should be already better then before.

I have read that it helped people to move the toolhead axis xand y in the middle of their machine bed before homing.

Anyway, feel free to contact support:
https://snapmaker.formcrafts.com/u1-troubleshooting-request

Edit, catched the false failure code:
0003-0522-0002-0012 Axis Movement Anomaly Tap Home first, then move the Z axis.

3

It’s definitely a slicer issue as it prints every time without problems if the g-code is generated by Snapmaker Orca.

I’ve never had this error using Snapmaker Orca and I’ve never had anything but this error using Orca Slicer. So I’ve never been able to get Orca Slicer g-code to get past even the calibration phase.

Thanks @xchrisd for taking the time to reply.

4

Please share this issue with support.
Edited my first post because of false error code..