My artisan keeps randomly resetting

Artisan (3-in-1) Artisan Troubleshooting guides
21

Hello Chris,
I have a similar problem. I’m using an Artisan and I have the same problem with Orca (also Snapmaker Orca) and also with Prusa Slicer. With large, complex prints, it starts to stutter at some point and gets progressively worse. Then the print head moves to the side, as if the pause button has been pressed. You can then resume the print, but this is always noticeable, especially if it happens several times during a single print.
The firmware log (actually all firmware log files) is full of the same message:
INFO,SC-FW,echo:Unknown command: ";
I suspect that the printer is overwhelmed by so many commands and starts to stutter.
If I restart the printer and resume the print, it works normally again.

Do you know what could be causing this?

Thanks,
Andreas

FW_2363.zip (21.9 KB)

22

May share a gcode when this happens?

Or search yourself for ”; or “ by opening the gcode in notepad++ (even normal notepad works if the gcode is not too big)?

Did you change any custom Gcode in these slicers?

Note, a normal semicolon ; works as barrier between Gcode-Commands to comments like:

G1 X100 Y100 F6000; comment here

23

150%_Japanese_Lantern_Top_v2_Large_0.2mm_11h24m.gcode.zip (12.4 MB)

Hello, no, I haven’t changed anything in the g-code.

24

I’m wondering about the arc moves in your gcode,- nothing else is obvious..

Maybe turning off arc moving would be worth a try..

Go to Settings > Advanced > Slicing > Arc fitting and turn it off.

image
image1501×1769 146 KB

May also share the SC logs?

25

31.10.2025.zip (2.3 MB)

sc log

26

One more suggestion, check your free memory of the touchscreen controller (at least 20% free, more is better). At this point i am unable to help you further..

If you tried diasbling the arc moves and it didn’t help, for further assistance, please ask support if not done yet.

27

Hello,
I still had 20 hours of printing with the G2-G3 settings and it stopped at around 90%. After the restart it continued to run without any problems. I now print exactly the same without G2-3
There were an incredible 500,000 entries in the first G-Code and sending an error message every time could overload the printer.
RAM is only 25% occupied. Since it always only happens after a long printing time, it seems to me as if some kind of cache or RAM is overloaded because after a restart everything is ok again.
According to the Snapmaker Wiki the command is supported but you shouldn’t use it and why are they enabled in the default profiles in Prusa and Orca?

image
image1136×479 43.2 KB

28

Does it printed correctly without G2 and G3?
I didn’t knew about this commands and am even not sure about the advantage but if it worked be sure to contact support and let them know please.

29

Hello,

unfortunately, the printing was interrupted even with G2-G3 disabled.
… In the logs, among all the (INFO,SC-FW,echo:Unknown command: ";)) entries, I keep finding these entries, which are becoming increasingly frequent:

SC: DEBUG,SC,G-code batch cache detected, response ResponseStructure{result=0, data=startLineNo
FW: -ERROR,SC-FW,nobody have registered handle for cmd[ac:2]
-INFO,SC-FW,no event queue for msg[ac:2]

Logs_18.11.2025.zip (3,2 MB)

What’s also strange is that the first few firmware logs were empty; normally, they’re all the same size except for the last one.

Does the printer have an additional cache that can fill up? Or is there only the one memory where the G-codes are stored? I’m asking because the on-screen settings have an option to reset G-codes and cache. Would that, or resetting to factory settings, help?

30

Why not, good idea to try :+1:

31

Hello,

Before the reset, I had 850 MB of storage used out of 3603 MB. After clearing the cache and memory and resetting to factory settings, I did two small test prints, and now I have 2743 MB of storage used out of 3603 MB.

These messages appeared again during the setup wizard. I think that was during bed leveling.

1763598147919,2025.11.20 08:22:27.919,INFO,SC-FW," <br> 
1763598147920,2025.11.20 08:22:27.920,INFO,SC-FW," <br> 
1763598147922,2025.11.20 08:22:27.922,INFO,SC-FW," <br> 
1763598147925,2025.11.20 08:22:27.925,INFO,SC-FW," <br> 
1763598147926,2025.11.20 08:22:27.926,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147927,2025.11.20 08:22:27.927,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147928,2025.11.20 08:22:27.928,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147929,2025.11.20 08:22:27.929,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147930,2025.11.20 08:22:27.930,INFO,SC-FW," <br> 
1763598147931,2025.11.20 08:22:27.931,INFO,SC-FW," <br> 
1763598147932,2025.11.20 08:22:27.932,INFO,SC-FW," <br> 
1763598147932,2025.11.20 08:22:27.932,INFO,SC-FW," <br> 
1763598147933,2025.11.20 08:22:27.933,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147934,2025.11.20 08:22:27.934,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147935,2025.11.20 08:22:27.935,INFO,SC-FW,echo:Unknown command: "; <br> 
1763598147935,2025.11.20 08:22:27.935,INFO,SC-FW,echo:Unknown command: "; <br>

This always happens in this combination during leveling.

I tried using chatgpt to figure out what it could be and came to the conclusion that it’s something to do with the web UI and the communication with the printer in connection with the comments in the gcode. Since the stuttering and freezing only happens with large files, it seems to me as if the cache is overflowing and then gets stuck.
Have you ever heard of such a problem?

I also find it strange that after resetting, when I exported the logs to a USB stick, it took a very long time. In the logs, I then saw this with thousands of lines:

1763598541311,2025.11.20 08:29:01.311,DEBUG,SC,File found, name is SC_451.log
1763598541312,2025.11.20 08:29:01.312,DEBUG,SC,File found, name is SC_1042.log
1763598541314,2025.11.20 08:29:01.314,DEBUG,SC,File found, name is FW_304.log
1763598541315,2025.11.20 08:29:01.315,DEBUG,SC,File found, name is FW_148.log
1763598541316,2025.11.20 08:29:01.316,DEBUG,SC,File found, name is SC_1497.log

Why are all log files ever created being searched for? Shouldn’t they be gone after a complete reset? PS: How much RAM does the Artisan actually have? I keep finding conflicting information online. I was pretty sure it was 8GB or something like that. Why am I only seeing 3603 MB displayed?

34

@XChrisd These messages appear before every change in action, such as switching from wall to fill or changing the speed.

Maybe I’m just too tired at 5 a.m., but unfortunately, I have no idea what you’re talking about. Did you mean me, and if so, which suppliers? Are several people having the same problem? Is it about faulty memory modules?

Sorry, I have to go to bed. Good night.

35

Since it’s already very late, I’ll keep it brief. When I use the search and replace function (^\s*;.*\R?) in Notepad++ to edit the g-code, all comments are deleted and the error messages disappear.

1 Like
36

Does it print successfully with a modified gcode?

37

Unfortunately not yet, I haven’t had a chance to print something that large. I’ll definitely print something large this weekend, since that’s where I had these problems last time. We’ll see, but I think all these errors are clogging up the memory.

Do you happen to know how much memory the Artisan has?

38

Hi Klabusterbaer，

https://snapmaker.formcrafts.com/support-ticket

You can submit a ticket at the same time in case the technical staff or fellow users in the forum don’t respond promptly.

39

Hi Klabusterbaer，

I checked with the software team for you—another user had a similar stuttering issue that might be linked to incompatibility with G2/G3. You can try the steps below to troubleshoot:

  1. First, make sure your machine is running the latest firmware version.
  2. Then follow the two steps shown in the image to adjust the settings and run another test print.

image
image1895×1283 297 KB

40

Hello,

For your information, this doesn’t yet apply to the latest version of Snapmaker Orcaslicer, which was just released and I haven’t tested it yet due to the unknown command messages. However, since the recent changes could be related to this problem, I’m mentioning it here:

Snapmaker Orca 2.1.2 Release Notes
Snapmaker Orca V2.1.2 aims to address several blocking issues present in the V2.1.1 version.

Bug Fix

  1. Fix for G-code files containing characters unrecognized by devices in European language environments.

  2. Fix for PCs Without Unicode-Based Global Language Support Failing to Connect to Devices

I had already disabled G2/G3 and Z-hop was set to normal. I’ve now also disabled the following functions (if they were enabled) to reduce memory usage:

  • Retract on shift change

  • Clean during retraction

  • Under print quality, I increased the resolution from 0.012 to 0.05 mm

  • I deleted the comments using Notepad++ and the search (^\s*;.*\R?) and replace () functions.

Currently, I’m printing a 40+ hour print without any problems, something I usually have issues with. It’s almost finished and so far, there haven’t been any problems. According to the monitor, the memory usage remains constant without filling up.

1
1638×990 195 KB

Once the print is finished, I’ll print almost the same model with the new version of Snapmaker Orca and won’t delete any comments. I’m curious to see what happens.

2 Likes
41

If there are any issues, please save the logs so we can optimize and troubleshoot!