Recently got a snap maker artisan, the premium with the 40 w laser. Have been doing some testing of the 3d printer and have had a number of fails already. But not in the normal way i have with printers in the past. Have several hours my machine with just reset its self. Go all the way to the left and forget its progress like its been deleted from memory. This has happen 7 times now. Its never at the same point but it is wasting a lot of material. For 3 grand i expect this thing not to do stuff like this.
Is all your FW etc up to date?
It is. It is currwntly running 2.7.3. I just got the machine and that was the first thing it had me do.
Check all your cables are in properly and not loose, or pulling out when the machine moves.
Check your Power supply cables as well.
Are you using Luban? If so are you connected via Wifi? USB can be more reliable.
1 Like
I have checked the cables. Unplugged and replugged all of them in. I have been running on luban connected by wifi, i will try using usb to see if that fixes anything!
Printing from the touchscreen would be the safest way to not getting interrupted.
Export your logs and share it here and with support:
https://wiki.snapmaker.com/en/snapmaker_artisan/troubleshooting/export_log_artisan
Shoot a support-ticket to get a replacement fast (unfortunately Chinese new year will slow the process down a bit):
https://snapmaker.formcrafts.com/support-ticket
For whatever reason since i am a new poster i cant post my logs? I had chatgpt help me analyze the last one that failed. I was running it off usb from the machine. Chatp analyzed this last lines of code and said this: * The printer was executing G-code normally.
- There were routine controller status checks and network scans.
- Around
09:33:05, the software seems to have restarted or reinitialized, possibly due to a network event, firmware check, or an app restart. - The printer continued running but detected that no filament was present in the extruders.
I was thinking maybe it could be a power issue? Ive read some places that dirty power could have a restart effect on the machine. But also maybe this sounds like a firmware bug? its printed shorter prints but anything over 3 hours it wont make it.
I am taking it back one firmware now to try that.
Trying a different firmware did not work. I guess i can push i back more?
Why not share the log here?
Like i said earlier, For whatever reason since i am a new poster i cant post my logs? I dont really understand why i get that message. I can post snippets of it?
You can use a hoster of your choice like we transfer or google cloud and share the link here.
SC-34 is the latest failure that i had. This is a zip of my logs
Please let me know if yall see anything because i am getting pretty discouraged by this machine sadly.
I had a little look to your logs.
It seems your machine ran out of power and the recovery process was not successful because of a gcode parsing error.
1738200787725,2025.01.30 09:33:07.725,DEBUG,SC,Route: Create HomePrintIdleModuleFragment
1738200787797,2025.01.30 09:33:07.797,DEBUG,SC,Requesting Print Power Outage…
1738200787831,2025.01.30 09:33:07.831,WARN,SC,Machine is printing while touchscreen start up.
1738200787923,2025.01.30 09:33:07.923,ERROR,SC,sacp-debug-e normalACK :
PARSE ERROR!
byte is: aa55090001026001011100ac07d02741
payload is d0
structure is: ResponseStructure{result=208, data=md5:Len is: 0 content is:
filename:Len is: 0 content is:
}
error msg is: java.io.EOFException
commandSet is: ac
commandId is: 7
1738200787964,2025.01.30 09:33:07.964,DEBUG,SC,Route: Create HomePrintingModuleFragment
I see a lot of
INFO,SC-FW,echo:Unknown command: "; < br>
in the fw file what slicer do you use? (Wondering why a semicolon should be a unknown command.
Unfortunately it seems only support could help you further.
Im curious as to why its randomly running out of power. I have been using luban to do slicing though so maybe its a problem with the gcode its generating?
Thanks for taking a look, support is sending my files to the devs so we will see what ideas they come up with once they respond.
I do have cura installed, should i try running a file from there?
How long was your print and what was the size of the gcode? I could imagine, if your gcode is huge that this could lead to problems (it shouldn’t but who knows).
I would suggest to try the power loss recovery while printing a 1h or less print.
Slice something like a benchy, let it print a few lines and cut the power and switch off the socket. I am curios about if it works.
Because it’s a new machine, the touchscreen memory couldn’t be full, correct?
On luban it was giving me 15 hour eatimates and would continue to go up until maybe 21 hour. Actualy just ran the same model sliced from cura and it gave me a faster print time and made it longer through the print before doing the same restting itself problem.
Not sure what to make of that but could just be random.
Ive been able to successfully print small print jobs but i will try the power loss recovery and see if it works. The memory shouldnt be full i wouldnt think.
So it did a power loss recovery. Its not perfect but it was able to get the power cut and then start back where it left off with the benchy. Im gonna try it with the large print and see if it still can recover.
Did it with the large file as well.