Snapmaker Orca V1.2.1 Beta: Issues Report & Discussions

Snapmaker Orca Beta
1

Hello Snapmaker Orca Beta users,

We’re collecting the issues you’ve encountered when using Snapmaker Orca Beta V1.2.1 and trying to solve them asap.

Here’s how you can share your feedback:

  1. Submit a Support Ticket: Contact our support team directly by submitting a support ticket or emailing us at support@snapmaker.com.

  2. Post in This Thread: Feel free to discuss any issues or concerns here.

  3. Avoid posting feature requests here. Discuss them in the dedicated thread: Snapmaker Orca Beta : Features Request & Discussions

We appreciate your feedback!

3 Likes
2

Few things for me, A more refind start gcode… that matches Luban, 2- Definite direct gcode sending, tested uploader, and using Luban, not massive but work flow its a definite benefit…it is actually working very well, gratz to the team! I had an issue where cut didn’t appear but then it came back, cant explain that one…

1 Like
3

Thank you for your feedback! If the issue occurs again, please provide more detailed information. I will report it to the support team for further investigation. Thanks for your support!

4

Is this an issue with the start & stop gcode mentioned above?

  • Printer shows 100% while print is in progress
  • No way to stop print remotely because Luban also showing print is done
  • Printer does not handle disconnects well with this gcode - print will continue but interface will revert to UI as if no print is in progress.

Here’s a screenshot showing:

  1. >200K lines in the gcode file
  2. both the printer and Luban displaying 100% with no “STOP” button
  3. print is still in progress with around 47K lines having been completed
    Screenshot 2025-06-15 141448
    Screenshot 2025-06-15 1414481720×1440 360 KB
5

Variable total_toolchanges=0 even both tools are used when no wipe tower is selected

I have found this bug in Orcaslicer but the same problem is with latest beta of Snapmaker Orca. It is already reported at Orcaslicer Github (issues #8580, #8805 and #10099) but none of these bugs are assigned to anybody. This bug limits the posibilities of slicer for multi-tool printers (such Snapmaker’s J1 and U1).

Prusaslicer (v2.9.2) generates total_toolchanges variable correctly.

6

One more issue: do you plan the full implementation of SACP protocol into Snapmaker Orca or directly into Orcaslicer? It will be very useful to have full control of printer here like in Luban.

7

We have heard your feedback. Our software engineers have reviewed it and agree that it is a valid feature request. Currently, both the official Orcaslicer and Snapmaker Orca rely on the wipe tower to calculate the total_toolchanges count. We plan to include this improvement in a future update. For now, the focus remains on adapting the U1 and improving its stability, so this feature will not be added in the current official release.

8

We do not plan to integrate the SACP protocol into Snapmaker Orca or Orcaslicer. However, we are planning firmware updates that will enable direct connection between Snapmaker Orca and printers like J1, Artisan, A250, and A350. This will provide common 3D printing control features within Snapmaker Orca.

9

Hi, we have noted this issue before, though it does not happen consistently. In the future, we plan to move printer control, including file upload and printing, into Orca. Because of this, there is currently no plan to fix this specific problem in the existing system.

10

OK, this is better, great.

Let me know if you need betatesters for this upgrade. I am ready to help, including tests with dedicated Octoprint server :wink:

1 Like