Print Job Terminates Before Completion

Snapmaker 2.0
1

We’re using A350’s in my classroom, and I have a student who designed and tried to print a chunk of Swiss cheese - I didn’t ask why or what for. Regardless, he started the print job during class, and it should have completed sometime overnight. When I came in this morning, the job had terminated, but the print wasn’t complete.

IMG_2550
IMG_25501920×2560 331 KB

I know this isn’t a Fusion forum, but I can post his Fusion file if that would help.

This is not the first time one of my students has experienced this problem, and I have no better idea now what caused it than I did the first time I saw it.

Any pointers would be appreciated.

2

Export your logs to a USB thumb drive and upload it here or have a look at it yourself.
https://wiki.snapmaker.com/en/Snapmaker_2/manual/export_logs

3

Unbeknownst to me, my student restarted his job again last evening, and no surprise, it failed at the same spot. I glanced at the log file, but since I don’t know exactly what I’m looking for, I don’t know how to interpret the data. I see the following quite a bit:

ERROR,SC-FW,purifier info update timeout:0 - 2!

The last log file is quite large, but I believe these are the entries created during the student’s print job:

37105,1970.01.01 00:00:37.105,INFO,SC-FW,Created marlin task!
37108,1970.01.01 00:00:37.108,INFO,SC-FW,Created HMI task!
37110,1970.01.01 00:00:37.110,INFO,SC-FW,Created heartbeat task!
37115,1970.01.01 00:00:37.115,INFO,SC-FW,Created can receiver task!
37117,1970.01.01 00:00:37.117,INFO,SC-FW,Created can event task!
37119,1970.01.01 00:00:37.119,INFO,SC-FW,Scanning modules ...
37151,1970.01.01 00:00:37.151,INFO,SC-FW,SC req Exception
37222,1970.01.01 00:00:37.222,INFO,SC-FW,SC req enclosure sta
37224,1970.01.01 00:00:37.224,INFO,SC-FW,Eclosure: set LIGHT power 100
37231,1970.01.01 00:00:37.231,INFO,SC-FW,SC req emergency stop sta:1
37239,1970.01.01 00:00:37.239,INFO,SC-FW,SC req rotate sta:1
37741,1970.01.01 00:00:37.741,ERROR,SC-FW,purifier info update timeout:0 - 2!
37744,1970.01.01 00:00:37.744,INFO,SC-FW,SC req purifier sta:1, err:0x0
37748,1970.01.01 00:00:37.748,INFO,SC-FW,hmi get kit status, quick_change_adapter: 0, integration_toolhead: 0
37824,1970.01.01 00:00:37.824,INFO,SC-FW,live Z offset 0: 0.00, 1: 0.00
37839,1970.01.01 00:00:37.839,INFO,SC-FW,X_MAX_POS: 358.000000, Y_MAX_POS: 358.000000, Z_MAX_POS: 334.000000
38716,1970.01.01 00:00:38.716,ERROR,SC-FW,purifier info update timeout:0 - 2!
38717,1970.01.01 00:00:38.717,INFO,SC-FW,SC req purifier sta:1, err:0x0
46660,1970.01.01 00:00:46.660,INFO,SC-FW,leveling OFF
50593,1970.01.01 00:00:50.593,INFO,SC-FW,leveling ON
50602,1970.01.01 00:00:50.602,INFO,SC-FW,Apply hotend[0] Z offset: 0.00
60103,1970.01.01 00:01:00.103,INFO,SC-FW,new E target temp: 200
60281,1970.01.01 00:01:00.281,INFO,SC-FW,enable nozzle fan
60283,1970.01.01 00:01:00.283,INFO,SC-FW,fan_index: 1, speed: 255
1731501536515,2024.11.13 12:38:56.515,INFO,SC-FW,new E target temp: 0
37057,1970.01.01 00:00:37.057,INFO,SC-FW,SC req Exception
37143,1970.01.01 00:00:37.143,INFO,SC-FW,SC req enclosure sta
37145,1970.01.01 00:00:37.145,INFO,SC-FW,Eclosure: set LIGHT power 100
37156,1970.01.01 00:00:37.156,INFO,SC-FW,SC req emergency stop sta:1
37163,1970.01.01 00:00:37.163,INFO,SC-FW,SC req rotate sta:1
37643,1970.01.01 00:00:37.643,ERROR,SC-FW,purifier info update timeout:0 - 2!
37645,1970.01.01 00:00:37.645,INFO,SC-FW,SC req purifier sta:1, err:0x0
37647,1970.01.01 00:00:37.647,INFO,SC-FW,hmi get kit status, quick_change_adapter: 0, integration_toolhead: 0
37713,1970.01.01 00:00:37.713,INFO,SC-FW,live Z offset 0: 0.00, 1: 0.00
37723,1970.01.01 00:00:37.723,INFO,SC-FW,X_MAX_POS: 358.000000, Y_MAX_POS: 358.000000, Z_MAX_POS: 334.000000
38633,1970.01.01 00:00:38.633,ERROR,SC-FW,purifier info update timeout:0 - 2!
38635,1970.01.01 00:00:38.635,INFO,SC-FW,SC req purifier sta:1, err:0x0
1731522934984,2024.11.13 18:35:34.984,INFO,SC-FW,leveling OFF
1731522938923,2024.11.13 18:35:38.923,INFO,SC-FW,leveling ON
1731522938926,2024.11.13 18:35:38.926,INFO,SC-FW,Apply hotend[0] Z offset: 0.00
1731522949838,2024.11.13 18:35:49.838,INFO,SC-FW,new E target temp: 200
1731522950210,2024.11.13 18:35:50.210,INFO,SC-FW,enable nozzle fan
1731522950212,2024.11.13 18:35:50.212,INFO,SC-FW,fan_index: 1, speed: 255
1731523069580,2024.11.13 18:37:49.580,INFO,SC-FW,new E target temp: 0
1731523078941,2024.11.13 18:37:58.941,INFO,SC-FW,SC get env: 4
1731523078946,2024.11.13 18:37:58.946,INFO,SC-FW,live z offset: 0.000
1731523094446,2024.11.13 18:38:14.446,INFO,SC-FW,SC get env: 4
1731523094448,2024.11.13 18:38:14.448,INFO,SC-FW,live z offset: 0.000
1731523101668,2024.11.13 18:38:21.668,INFO,SC-FW,SC get env: 4
1731523101670,2024.11.13 18:38:21.670,INFO,SC-FW,live z offset: 0.000
1731523114127,2024.11.13 18:38:34.127,INFO,SC-FW,SC get env: 4
1731523114131,2024.11.13 18:38:34.131,INFO,SC-FW,live z offset: 0.000
1731523121878,2024.11.13 18:38:41.878,INFO,SC-FW,SC get env: 4
1731523121879,2024.11.13 18:38:41.879,INFO,SC-FW,live z offset: 0.000
1731523132279,2024.11.13 18:38:52.279,INFO,SC-FW,SC get env: 4
1731523132280,2024.11.13 18:38:52.280,INFO,SC-FW,live z offset: 0.000
1731523150292,2024.11.13 18:39:10.292,INFO,SC-FW,SC req is leveled:1
1731523157199,2024.11.13 18:39:17.199,INFO,SC-FW,SC get env: 4
1731523157201,2024.11.13 18:39:17.201,INFO,SC-FW,live z offset: 0.000
1731523157582,2024.11.13 18:39:17.582,INFO,SC-FW,new laser power: -1.00
1731523157587,2024.11.13 18:39:17.587,INFO,SC-FW,SC req START work
1731523157602,2024.11.13 18:39:17.602,INFO,SC-FW,SC req -> Success
1731523157743,2024.11.13 18:39:17.743,INFO,SC-FW,leveling OFF
1731523161683,2024.11.13 18:39:21.683,INFO,SC-FW,leveling ON
1731523161684,2024.11.13 18:39:21.684,INFO,SC-FW,Apply hotend[0] Z offset: 0.00
1731523161686,2024.11.13 18:39:21.686,INFO,SC-FW,new E target temp: 200
1731523161695,2024.11.13 18:39:21.695,INFO,SC-FW,new B target temp: 60
1731523161698,2024.11.13 18:39:21.698,INFO,SC-FW,new E target temp: 200
1731523237417,2024.11.13 18:40:37.417,INFO,SC-FW,new B target temp: 60
1731523469661,2024.11.13 18:44:29.661,INFO,SC-FW,fan_index: 0, speed: 0
1731524059289,2024.11.13 18:54:19.289,INFO,SC-FW,new E target temp: 205
1731524061138,2024.11.13 18:54:21.138,INFO,SC-FW,new B target temp: 50
1731524061140,2024.11.13 18:54:21.140,INFO,SC-FW,fan_index: 0, speed: 255
1731554795333,2024.11.14 03:26:35.333,INFO,SC-FW,End of the print
1731554795338,2024.11.14 03:26:35.338,INFO,SC-FW,new B target temp: 0
1731554795340,2024.11.14 03:26:35.340,INFO,SC-FW,new E target temp: 0
1731554795342,2024.11.14 03:26:35.342,INFO,SC-FW,new E target temp: 0
1731554795345,2024.11.14 03:26:35.345,INFO,SC-FW,fan_index: 0, speed: 0
1731554795347,2024.11.14 03:26:35.347,INFO,SC-FW,QS recorded pos X: 0.000, Y: 0.000, Z: 0.000, E: 0.000
1731554795349,2024.11.14 03:26:35.349,INFO,SC-FW,QS at logical pos: X: 136.012, Y: 181.955, Z: 21.560, E: 2148.801
1731554795350,2024.11.14 03:26:35.350,INFO,SC-FW,leveling OFF
1731554815045,2024.11.14 03:26:55.045,INFO,SC-FW,leveling ON
1731554815052,2024.11.14 03:26:55.052,INFO,SC-FW,Finish stop
1731554815589,2024.11.14 03:26:55.589,ERROR,SC-FW,purifier info update timeout:0 - 2!
1731554815591,2024.11.14 03:26:55.591,INFO,SC-FW,SC req purifier sta:1, err:0x0
1731555081916,2024.11.14 03:31:21.916,INFO,SC-FW,disable nozzle fan
1731555081918,2024.11.14 03:31:21.918,INFO,SC-FW,fan_index: 1, speed: 0
4

Please share the files, it would be helpful if the last operation was the error.
I can’t see a failed operation in the shared data so I guess the error occurs in the other file.

If you share a codeblock, please give it three back ticks before and after the code.
“```”

5

Here is the last log file in its entirety.

DC3DP1 Log.pdf (1.2 MB)

6

Please share the sc or fw log files too, not sure what you have shared.

How do you print the job, any connection?
Do you have the beta firmware running?
What speed do you print?

It seems your memory is faulty or the response is too slow:
1730745795124,2024.11.04 18:43:15.124,ERROR,SC-FW,wait gcode pack timeout and
req:0
1730745796139,2024.11.04 18:43:16.139,ERROR,SC-FW,wait gcode pack timeout and
req:0

7

What I forwarded was the tail end of what I thought was the last/latest FW log file. I went back again and regenerated all of the log files and placed them in ​this folder​, to which you should have read access. If you have any issues accessing the folder, please let me know and I’ll find another way to get the files to you.

Thanks!

8

Do you use a USB stick for print transfer?
I have problems to view your files on the phone but I have seen some USB drive errors, maybe try a different one?