Print Stops at 3%

ThirstyDragon · September 25, 2021, 8:15am

Hi There,

Currently I have had multiple failed attempts to 3d print an object on the snapmaker a350. It seems to print a few layers and unexpectedly stops around 3% without any notification then returns the printing module to home.

Once stopped, it still shows the touchscreen at 3% with the “Pause” and “Stop” options, but pressing these buttons does nothing and the touchscreen will not change from this “in progress” screen. I end up having to power off in order to reset the device.

I have seen multiple threads with similar experiences and I have tried the following to remedy the situation to no avail:

Modified extrusion/gcode settings
Updated Luban
Updated Firmware
Sent File over WIFI to snapmaker for printing
Connected over WIFI from luban for printing
Connected File using USB for printing
Recalibrated multiple times

I have exported the logs, although I am not sure which one I should need (SC_0 or FW_0). I am at the moment currently unable to upload the log files as the forum will not allow uploads by new users.

I can provide an alternate link for the logs or wait until I am able to upload them, but am not sure whether there are errors.

I do see multiple of:
37193,1970.01.01 00:00:37.193,WARN,SC,Module 0x03 version (v1.10.3�) is invalid!

as well as:
1632538835773,2021.09.25 03:00:35.773,WARN,SC,No reply for 43501 ms since last response (#36: M109 S200;Wait for Hotend Temperature)

I assume the “Wait for Hotend Temperature” is simply waiting for the nozzle to heat up to the desired temp before starting though.

after some time though, There are alot of no reply warnings here:

1632552941487,2021.09.25 06:55:41.487,INFO,SC,line 24000: G1 X139.133 Y265.894 E2261.76355
1632552987477,2021.09.25 06:56:27.477,INFO,SC,line 25000: G1 X222.841 Y233.866 E2280.88734
1632553356305,2021.09.25 07:02:36.305,INFO,SC,line 26000: G1 F1500 X199.191 Y132.441 E2510.04499
1632553779513,2021.09.25 07:09:39.513,INFO,SC,line 27000: G0 F4200 X159.17 Y253.074
1632554030291,2021.09.25 07:13:50.291,WARN,SC,No reply for 28219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554040289,2021.09.25 07:14:00.289,WARN,SC,No reply for 38218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554050289,2021.09.25 07:14:10.289,WARN,SC,No reply for 48218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554060290,2021.09.25 07:14:20.290,WARN,SC,No reply for 58219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554070290,2021.09.25 07:14:30.290,WARN,SC,No reply for 68219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554080290,2021.09.25 07:14:40.290,WARN,SC,No reply for 78220 ms since last response (#27352: G1 X121.412 Y119.149)
1632554090290,2021.09.25 07:14:50.290,WARN,SC,No reply for 88219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554100290,2021.09.25 07:15:00.290,WARN,SC,No reply for 98219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554110290,2021.09.25 07:15:10.290,WARN,SC,No reply for 108219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554120290,2021.09.25 07:15:20.290,WARN,SC,No reply for 118219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554130290,2021.09.25 07:15:30.290,WARN,SC,No reply for 128219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554140290,2021.09.25 07:15:40.290,WARN,SC,No reply for 138220 ms since last response (#27352: G1 X121.412 Y119.149)
1632554150291,2021.09.25 07:15:50.291,WARN,SC,No reply for 148220 ms since last response (#27352: G1 X121.412 Y119.149)
1632554160290,2021.09.25 07:16:00.290,WARN,SC,No reply for 158219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554170290,2021.09.25 07:16:10.290,WARN,SC,No reply for 168219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554180290,2021.09.25 07:16:20.290,WARN,SC,No reply for 178219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554190290,2021.09.25 07:16:30.290,WARN,SC,No reply for 188219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554200290,2021.09.25 07:16:40.290,WARN,SC,No reply for 198219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554210290,2021.09.25 07:16:50.290,WARN,SC,No reply for 208219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554220290,2021.09.25 07:17:00.290,WARN,SC,No reply for 218219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554230290,2021.09.25 07:17:10.290,WARN,SC,No reply for 228218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554240290,2021.09.25 07:17:20.290,WARN,SC,No reply for 238220 ms since last response (#27352: G1 X121.412 Y119.149)
1632554250290,2021.09.25 07:17:30.290,WARN,SC,No reply for 248218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554260291,2021.09.25 07:17:40.291,WARN,SC,No reply for 258220 ms since last response (#27352: G1 X121.412 Y119.149)
1632554270292,2021.09.25 07:17:50.292,WARN,SC,No reply for 268219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554280290,2021.09.25 07:18:00.290,WARN,SC,No reply for 278219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554290290,2021.09.25 07:18:10.290,WARN,SC,No reply for 288218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554300290,2021.09.25 07:18:20.290,WARN,SC,No reply for 298219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554310291,2021.09.25 07:18:30.291,WARN,SC,No reply for 308218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554310527,2021.09.25 07:18:30.527,INFO,SC,Stop print.
1632554320290,2021.09.25 07:18:40.290,WARN,SC,No reply for 318219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554330289,2021.09.25 07:18:50.289,WARN,SC,No reply for 328218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554340290,2021.09.25 07:19:00.290,WARN,SC,No reply for 338219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554350290,2021.09.25 07:19:10.290,WARN,SC,No reply for 348218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554360290,2021.09.25 07:19:20.290,WARN,SC,No reply for 358218 ms since last response (#27352: G1 X121.412 Y119.149)
1632554370290,2021.09.25 07:19:30.290,WARN,SC,No reply for 368219 ms since last response (#27352: G1 X121.412 Y119.149)
1632554380290,2021.09.25 07:19:40.290,WARN,SC,No reply for 378220 ms since last response (#27352: G1 X121.412 Y119.149)

Any ideas on what the issue may be?

Artezio · September 25, 2021, 8:23am

It could just be bad gcode. Have you tried regenerating the gcode? Also try another slicer like Cura? I also see an instance of the 3D printer module firmware being out of date. When you updated the firmware of the machine, was the print head attached and connected?

Here the machine thinks it’s 1970, common for any computer that has its internal clock reset, usually by power loss.

This is where it’s saying your print head module firmware is out of date and not matching the machine firmware on the controller and touchscreen, update the firmware again with the print head attached but you’ll have to do it via usb stick since the controller firmware is up to date so it won’t do anything if you try it via WiFi.

ThirstyDragon · September 25, 2021, 8:41am

This has happened with multiple gcodes for the same model I am trying to print, When printing the full model it stopped at something like 10%, but afterwards I ended up trying to split the model in half in order to get a lower time on printing. This is when it started stopping on 3% consistently.

Is there a way to change the date, or will it be updated with the firmware update? Like I said I had to hard reset in order to get out of the stuck screen so maybe that reset the time?

I did update the firmware with the print head attached, however because it was not FAT32 formatted could this have been why it didn’t update?

I saw that the firmware recommended be on a FAT32 usb stick, but I unfortunately only have a exFAT formatted usb (over 32gb). I’ve currently ordered a usb stick that can be formatted to FAT32 to try updating with that instead.

I have not tried another slicer like cura due to snapmaker’s statement that if a non-supported slicer causes damage to snapmaker, it will void any warranty.

I appreciate your quick reply!

Artezio · September 25, 2021, 8:45am

@ThirstyDragon its a big possibility that that’s why it didn’t work. Fat32 is required for Snapmaker to be able to read it, do you know how to partition a drive? Bigger thumb drives can still be Fat32, it just won’t show up in the format options where you normally go to format it. If you partition it, you can make it Fat32, it’ll just turn it into a 32gb drive effectively, and the rest just turns into null space that won’t be seen. For the sake of convenience, here’s an article that guides you how to do a partition. (Sorry, first link was bad.)

ThirstyDragon · September 25, 2021, 9:03am

Hmm I can look into this. I saw that Windows didn’t allow/show FAT32 formatting on anything over 32gb and the alternate software suggestions to bypass that did not look the most reliable.

I’ll take a look at this and see if I can format it this way though. If nothing else I should get the smaller sticks within a day or two. I’ll reply to the thread again once I get this part sorted.

Again, I appreciate the feedback!

Artezio · September 25, 2021, 9:47am

@ThirstyDragon out of curiosity… what happened to the thumb drive that came with your Snapmaker? It’s only a 16gb and perfectly suited for it. It should’ve come in your toolbox inside of a small case, it’s a shiny chromed metal usb drive, kind of looks like a coaches whistle really lol.

Also I forgot to mention that Cura is fully supported and will not void your warranty.

scyto · September 25, 2021, 6:54pm

two things to try:

slice in luban and use it to drive the gcode via serial (just to eliminate all things usb drive as source of issue and eliminate the touchscreen controller as issue).
alternately send by wifi to avoid just the USB able.

good luck.

Artezio · September 25, 2021, 11:06pm

@scyto it’s conflicting firmware, the head firmware is outdated which is causing a conflict with the updated controller firmware. He needs to flash it again to get the heads firmware updated but because the controller is up to date he can’t do it via WiFi, he has to do it via usb stick, but he doesn’t have one in Fat32 and so I explained how to partition it which brings us to now. Hopefully this summary helped lol. I think it was actually a failed firmware flash because of the usb file system being exFAT, so it screwed it all up when he tried to update firmware with an exFAT thumb drive.

ThirstyDragon · September 26, 2021, 12:03am

Update here,

I’ve done a couple things now. First I partitioned the 64gb flash to a 32gb with FAT32, downloaded the latest firmware and tried installing it via usb. I then restarted the machine and exported the log to check and saw that it still gave the invalid error:

36388,1970.01.01 00:00:36.388,INFO,SC,Application started!
36390,1970.01.01 00:00:36.390,DEBUG,SC,Build SDK version: 25
36396,1970.01.01 00:00:36.396,DEBUG,SC,FabScreen version: V1.13.2
36469,1970.01.01 00:00:36.469,DEBUG,SC,Reset overrides.
36517,1970.01.01 00:00:36.517,INFO,SC,SessionManager, load sessions...done
36992,1970.01.01 00:00:36.992,INFO,SC,Connecting serial port...
37029,1970.01.01 00:00:37.029,DEBUG,SC,Requesting module info...
37036,1970.01.01 00:00:37.036,INFO,SC,onConnection, connected = true
37037,1970.01.01 00:00:37.037,INFO,SC,Enable heartbeat.
37039,1970.01.01 00:00:37.039,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
37043,1970.01.01 00:00:37.043,DEBUG,SC,HTTP server started.
37072,1970.01.01 00:00:37.072,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
37080,1970.01.01 00:00:37.080,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
37083,1970.01.01 00:00:37.083,WARN,SC,Module 0x00 version (v1.10.3�) is invalid! 
37092,1970.01.01 00:00:37.092,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
37096,1970.01.01 00:00:37.096,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
37103,1970.01.01 00:00:37.103,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
37127,1970.01.01 00:00:37.127,DEBUG,SC,Set Enclosure lighting true
38058,1970.01.01 00:00:38.058,DEBUG,SC,Head type 1 found.
38210,1970.01.01 00:00:38.210,DEBUG,SC,Route: Create HomeFragment
38212,1970.01.01 00:00:38.212,DEBUG,SC,Route: Create LauncherFragment

I’ve found the 16gb flash drive included with snapmaker tools and tried using this usb as well, but same results.

36066,1970.01.01 00:00:36.066,INFO,SC,Application started!
36068,1970.01.01 00:00:36.068,DEBUG,SC,Build SDK version: 25
36070,1970.01.01 00:00:36.070,DEBUG,SC,FabScreen version: V1.13.2
36118,1970.01.01 00:00:36.118,DEBUG,SC,Reset overrides.
36174,1970.01.01 00:00:36.174,INFO,SC,SessionManager, load sessions...done
36636,1970.01.01 00:00:36.636,INFO,SC,Connecting serial port...
36662,1970.01.01 00:00:36.662,DEBUG,SC,Requesting module info...
36670,1970.01.01 00:00:36.670,INFO,SC,onConnection, connected = true
36672,1970.01.01 00:00:36.672,INFO,SC,Enable heartbeat.
36675,1970.01.01 00:00:36.675,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
36680,1970.01.01 00:00:36.680,DEBUG,SC,HTTP server started.
36692,1970.01.01 00:00:36.692,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36707,1970.01.01 00:00:36.707,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36718,1970.01.01 00:00:36.718,WARN,SC,Module 0x00 version (v1.10.3�) is invalid! 
36721,1970.01.01 00:00:36.721,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36728,1970.01.01 00:00:36.728,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36738,1970.01.01 00:00:36.738,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36767,1970.01.01 00:00:36.767,DEBUG,SC,Set Enclosure lighting true
37689,1970.01.01 00:00:37.689,DEBUG,SC,Head type 1 found.
37838,1970.01.01 00:00:37.838,DEBUG,SC,Route: Create HomeFragment
37841,1970.01.01 00:00:37.841,DEBUG,SC,Route: Create LauncherFragment
1632613653877,2021.09.25 23:47:33.877,DEBUG,SC,NetworkManager: found Wi-Fi configuration #0 "WIFIConnection", state = CURRENT.
1632613653878,2021.09.25 23:47:33.878,DEBUG,SC,NetworkManager: current Wi-Fi configuration is #0 "WIFIConnection"
1632613653916,2021.09.25 23:47:33.916,DEBUG,SC,Wi-Fi connected.
1632613653917,2021.09.25 23:47:33.917,DEBUG,SC,Start checking new version…
1632613654308,2021.09.25 23:47:34.308,DEBUG,SC,Route: Create SettingsHomeFragment
1632613657125,2021.09.25 23:47:37.125,INFO,SC,Export log to U-disk.

Do I need to reset the firmware to factory defaults before attempting to install the firmware? It just seems like the printer head won’t update when running the firmware update. I assume the printer head only needs to be plugged into the machine via the usual cable in order to be updated?

Artezio · September 26, 2021, 12:10am

@ThirstyDragon yeah it just needs to be connected to the machine as normal. When it was updating, did you see it do each module one by one? It flashes each individually so it’ll show an installation progress bar like 3 times (4 if you have the enclosure).

@brent113 what do you think? I’ve seen this happen only once before a while back but I don’t recall what the issue was.

ThirstyDragon · September 26, 2021, 12:28am

I believe I saw one with a count of ~88 and an update around ~471, If I recall it was the main controller and controller head?

I just tried it again and recorded a video of the process, as well as a latest export log. (Note that I did not hit the power switch here, I left it running from the previous attempt. You can see it sync up with the previous log I posted).

Short video of the update here: 20210925_191511.mp4 - Google Drive

Here is the result of the log:

1632613654308,2021.09.25 23:47:34.308,DEBUG,SC,Route: Create SettingsHomeFragment
1632613657125,2021.09.25 23:47:37.125,INFO,SC,Export log to U-disk.
1632613670442,2021.09.25 23:47:50.442,DEBUG,SC,Device detached UsbDevice[mName=/dev/bus/usb/001/002,mVendorId=3544,mProductId=14081,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=Netac,mProductName=OnlyDisk,mVersion=2.0,mSerialNumber=6263351056282507128,mConfigurations=[ <br> UsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=50,mInterfaces=[ <br> UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=8,mSubclass=6,mProtocol=80,mEndpoints=[ <br> UsbEndpoint[mAddress=1,mAttributes=2,mMaxPacketSize=512,mInterval=0] <br> UsbEndpoint[mAddress=130,mAttributes=2,mMaxPacketSize=512,mInterval=0]]]]
1632615204882,2021.09.26 00:13:24.882,DEBUG,SC,Device attached UsbDevice[mName=/dev/bus/usb/001/003,mVendorId=3544,mProductId=14081,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=Netac,mProductName=OnlyDisk,mVersion=2.0,mSerialNumber=6263351056282507128,mConfigurations=[ <br> UsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=50,mInterfaces=[ <br> UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=8,mSubclass=6,mProtocol=80,mEndpoints=[ <br> UsbEndpoint[mAddress=1,mAttributes=2,mMaxPacketSize=512,mInterval=0] <br> UsbEndpoint[mAddress=130,mAttributes=2,mMaxPacketSize=512,mInterval=0]]]]
1632615208942,2021.09.26 00:13:28.942,DEBUG,SC,Route: Back from SettingsHomeFragment
1632615210904,2021.09.26 00:13:30.904,DEBUG,SC,Route: Create BrowseFragment
1632615315762,2021.09.26 00:15:15.762,INFO,SC,Click file directory false path /Snapmaker2_V1.13.2.bin
1632615315768,2021.09.26 00:15:15.768,DEBUG,SC,Route: Create UpdateFragment
1632615315803,2021.09.26 00:15:15.803,INFO,SC,Opening file /Snapmaker2_V1.13.2.bin for upgrade.
1632615316112,2021.09.26 00:15:16.112,DEBUG,SC,Start saving update file into cache…
1632615353310,2021.09.26 00:15:53.310,INFO,SC,Disable heartbeat.
1632615443903,2021.09.26 00:17:23.903,INFO,SC,Application started!
1632615443906,2021.09.26 00:17:23.906,DEBUG,SC,Build SDK version: 25
1632615443908,2021.09.26 00:17:23.908,DEBUG,SC,FabScreen version: V1.13.2
1632615443947,2021.09.26 00:17:23.947,DEBUG,SC,Reset overrides.
1632615443983,2021.09.26 00:17:23.983,INFO,SC,SessionManager, load sessions...done
1632615444277,2021.09.26 00:17:24.277,DEBUG,SC,Finishing up last update...
1632615447467,2021.09.26 00:17:27.467,DEBUG,SC,Firmware update finish.
1632615447633,2021.09.26 00:17:27.633,DEBUG,SC,HTTP server started.
1632615447675,2021.09.26 00:17:27.675,INFO,SC,Connecting serial port...
1632615447705,2021.09.26 00:17:27.705,DEBUG,SC,Requesting module info...
1632615447711,2021.09.26 00:17:27.711,INFO,SC,onConnection, connected = true
1632615447712,2021.09.26 00:17:27.712,INFO,SC,Enable heartbeat.
1632615447749,2021.09.26 00:17:27.749,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
1632615447759,2021.09.26 00:17:27.759,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
1632615447764,2021.09.26 00:17:27.764,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
1632615447782,2021.09.26 00:17:27.782,WARN,SC,Module 0x00 version (v1.10.3�) is invalid! 
1632615447805,2021.09.26 00:17:27.805,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
1632615447808,2021.09.26 00:17:27.808,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
1632615447811,2021.09.26 00:17:27.811,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
1632615447824,2021.09.26 00:17:27.824,DEBUG,SC,Set Enclosure lighting true
1632615448737,2021.09.26 00:17:28.737,DEBUG,SC,Head type 1 found.
1632615448896,2021.09.26 00:17:28.896,DEBUG,SC,Route: Create HomeFragment
1632615448898,2021.09.26 00:17:28.898,DEBUG,SC,Route: Create LauncherFragment
1632615449005,2021.09.26 00:17:29.005,INFO,SC,Upgrade successfully
1632615449452,2021.09.26 00:17:29.452,DEBUG,SC,NetworkManager: found Wi-Fi configuration #0 "AlohaSnackbar", state = CURRENT.
1632615449454,2021.09.26 00:17:29.454,DEBUG,SC,NetworkManager: current Wi-Fi configuration is #0 "AlohaSnackbar"
1632615449461,2021.09.26 00:17:29.461,DEBUG,SC,Wi-Fi connected.
1632615449462,2021.09.26 00:17:29.462,DEBUG,SC,Start checking new version…
1632615461828,2021.09.26 00:17:41.828,DEBUG,SC,Route: Create SettingsHomeFragment
1632615465776,2021.09.26 00:17:45.776,DEBUG,SC,Route: Create SettingsAboutFragment
1632615465876,2021.09.26 00:17:45.876,DEBUG,SC,Package version Snapmaker2_V1.13.2_20210913
1632615465880,2021.09.26 00:17:45.880,DEBUG,SC,Touch screen version V1.13.2
1632615465908,2021.09.26 00:17:45.908,DEBUG,SC,Controller version V4.3.2
1632615474290,2021.09.26 00:17:54.290,DEBUG,SC,Route: Back from SettingsAboutFragment
1632615477028,2021.09.26 00:17:57.028,DEBUG,SC,Route: Create SettingsFirmwareFragment
1632615480292,2021.09.26 00:18:00.292,DEBUG,SC,version Snapmaker2_V1.13.2_20210913, url https://s3-us-west-2.amazonaws.com/snapmaker.com/download/firmware/Snapmaker2_V1.13.2.bin, machine_size 63406080 summary [New G-code command support, Support Heated-Leveling, bug fixes and improvements, and more]
1632615484791,2021.09.26 00:18:04.791,DEBUG,SC,Route: Back from SettingsFirmwareFragment
1632615488729,2021.09.26 00:18:08.729,INFO,SC,Export log to U-disk.

I get the feeling if I restart the machine again it’ll give that invalid error once more.

Artezio · September 26, 2021, 12:35am

@ThirstyDragon home the machine, then turn it off and back on, see if that saves it.

ThirstyDragon · September 26, 2021, 12:42am

I went to control and it auto homed, then I hit the home button again just to make sure. I then restarted the machine and exported the log. This is what I got:

1632615488729,2021.09.26 00:18:08.729,INFO,SC,Export log to U-disk.
1632615697508,2021.09.26 00:21:37.508,DEBUG,SC,Device detached UsbDevice[mName=/dev/bus/usb/001/003,mVendorId=3544,mProductId=14081,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=Netac,mProductName=OnlyDisk,mVersion=2.0,mSerialNumber=6263351056282507128,mConfigurations=[ <br> UsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=50,mInterfaces=[ <br> UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=8,mSubclass=6,mProtocol=80,mEndpoints=[ <br> UsbEndpoint[mAddress=1,mAttributes=2,mMaxPacketSize=512,mInterval=0] <br> UsbEndpoint[mAddress=130,mAttributes=2,mMaxPacketSize=512,mInterval=0]]]]
1632616644332,2021.09.26 00:37:24.332,DEBUG,SC,Device attached UsbDevice[mName=/dev/bus/usb/001/004,mVendorId=3544,mProductId=14081,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=Netac,mProductName=OnlyDisk,mVersion=2.0,mSerialNumber=6263351056282507128,mConfigurations=[ <br> UsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=50,mInterfaces=[ <br> UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=8,mSubclass=6,mProtocol=80,mEndpoints=[ <br> UsbEndpoint[mAddress=1,mAttributes=2,mMaxPacketSize=512,mInterval=0] <br> UsbEndpoint[mAddress=130,mAttributes=2,mMaxPacketSize=512,mInterval=0]]]]
1632616648117,2021.09.26 00:37:28.117,DEBUG,SC,Route: Back from SettingsHomeFragment
1632616649675,2021.09.26 00:37:29.675,DEBUG,SC,Route: Create Control3DPFragment
1632616650094,2021.09.26 00:37:30.094,INFO,SC,update coordinate system...
1632616650114,2021.09.26 00:37:30.114,INFO,SC,Coordinate system updated, CS#0 X = 0.0, Y = 0.0, Z =0.0
1632616663157,2021.09.26 00:37:43.157,INFO,SC,update coordinate system...
1632616663180,2021.09.26 00:37:43.180,INFO,SC,Coordinate system updated, CS#0 X = 0.0, Y = 0.0, Z =0.0
                                                                                   36300,1970.01.01 00:00:36.300,INFO,SC,Application started!
36302,1970.01.01 00:00:36.302,DEBUG,SC,Build SDK version: 25
36304,1970.01.01 00:00:36.304,DEBUG,SC,FabScreen version: V1.13.2
36367,1970.01.01 00:00:36.367,DEBUG,SC,Reset overrides.
36415,1970.01.01 00:00:36.415,INFO,SC,SessionManager, load sessions...done
36888,1970.01.01 00:00:36.888,INFO,SC,Connecting serial port...
36916,1970.01.01 00:00:36.916,DEBUG,SC,Requesting module info...
36927,1970.01.01 00:00:36.927,INFO,SC,onConnection, connected = true
36929,1970.01.01 00:00:36.929,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
36930,1970.01.01 00:00:36.930,INFO,SC,Enable heartbeat.
36939,1970.01.01 00:00:36.939,DEBUG,SC,HTTP server started.
36942,1970.01.01 00:00:36.942,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36955,1970.01.01 00:00:36.955,WARN,SC,Module 0x00 version (v1.10.3�) is invalid! 
36963,1970.01.01 00:00:36.963,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36975,1970.01.01 00:00:36.975,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36982,1970.01.01 00:00:36.982,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36993,1970.01.01 00:00:36.993,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
37020,1970.01.01 00:00:37.020,DEBUG,SC,Set Enclosure lighting true
37953,1970.01.01 00:00:37.953,DEBUG,SC,Head type 1 found.
38085,1970.01.01 00:00:38.085,DEBUG,SC,Route: Create HomeFragment
38088,1970.01.01 00:00:38.088,DEBUG,SC,Route: Create LauncherFragment
1632616749255,2021.09.26 00:39:09.255,DEBUG,SC,NetworkManager: found Wi-Fi configuration #0 "WIFIConnection", state = CURRENT.
1632616749256,2021.09.26 00:39:09.256,DEBUG,SC,NetworkManager: current Wi-Fi configuration is #0 "WIFIConnection"
1632616749274,2021.09.26 00:39:09.274,DEBUG,SC,Wi-Fi connected.
1632616749276,2021.09.26 00:39:09.276,DEBUG,SC,Start checking new version…
1632616776377,2021.09.26 00:39:36.377,DEBUG,SC,Route: Create SettingsHomeFragment
1632616778868,2021.09.26 00:39:38.868,INFO,SC,Export log to U-disk.

Would a factory reset help? Maybe it won’t update the printer head because the touchscreen is up to date?

ThirstyDragon · September 26, 2021, 2:49am

So I have been trying resetting the settings through the experimental modes, and reinstalling lower versions of the firmware.

I’ve gone into experimental mode and then to the settings and preferences and reset all, then gone through the initial configurations. Once that was done, checking the about machine section shows no change to the touchscreen and controller versions, although the firmware line was blank. After doing this, I installed version 1.13.1 via usb and it did indeed update the controller version 4.3.0, touchscreen 1.13.1, and at least displayed the firmware as 1.13.1, but the invalid warnings were still there.

I did this a few more times to no changes regarding the module warnings, but just now I downgraded the firmware on the machine to 1.9 and I do not see any warnings now in the log. I am unsure if this will cause conflicts regarding the luban software, but at least it’s something different.

I’m going to try a print using the older firmware and we’ll see if it fails. Will update then. I’m curious at which point in the firmware updates do these module warnings begin appearing and what exactly they mean.

For reference these are the warnings in question.

36942,1970.01.01 00:00:36.942,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36955,1970.01.01 00:00:36.955,WARN,SC,Module 0x00 version (v1.10.3�) is invalid! 
36963,1970.01.01 00:00:36.963,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36975,1970.01.01 00:00:36.975,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36982,1970.01.01 00:00:36.982,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
36993,1970.01.01 00:00:36.993,WARN,SC,Module 0x03 version (v1.10.3�) is invalid! 
3702

UPDATE:

Unfortunately it was a very fast result. It did not even complete 1% before producing the same results. I was using 1.9.0 firmware and luban 3.8. I’m concerned about the issue since it does not seem to be dependent on the versions of luban and the firmware?

I know that I see the temperatures go to 0 on the right side of the temp gauges once it locks up like this, (199/0c, 70/0c) but I am not sure if that is due to it stopping the print or if that’s an error. The left measurement seems accurate so I don’t think it’s the thermistor or heating tube.

Here is the log.

1632626408866,2021.09.26 03:20:08.866,INFO,SC,Start print.
1632626408887,2021.09.26 03:20:08.887,INFO,SC,Print started.
1632626408890,2021.09.26 03:20:08.890,INFO,SC,set line number takes 0 ms
1632626408905,2021.09.26 03:20:08.905,DEBUG,SC,Override M104 S200.0
1632626408924,2021.09.26 03:20:08.924,DEBUG,SC,Override M140 S70.0
1632626438872,2021.09.26 03:20:38.872,WARN,SC,No reply for 29932 ms since last response (#32: G28 ;home)
1632626451190,2021.09.26 03:20:51.190,DEBUG,SC,Override M109 S200.0
1632626478872,2021.09.26 03:21:18.872,WARN,SC,No reply for 27683 ms since last response (#36: M109 S200;Wait for Hotend Temperature)
1632626488872,2021.09.26 03:21:28.872,WARN,SC,No reply for 37682 ms since last response (#36: M109 S200;Wait for Hotend Temperature)
1632626498872,2021.09.26 03:21:38.872,WARN,SC,No reply for 47683 ms since last response (#36: M109 S200;Wait for Hotend Temperature)
1632626508871,2021.09.26 03:21:48.871,WARN,SC,No reply for 57682 ms since last response (#36: M109 S200;Wait for Hotend Temperature)
1632626518871,2021.09.26 03:21:58.871,WARN,SC,No reply for 67682 ms since last response (#36: M109 S200;Wait for Hotend Temperature)
1632626522385,2021.09.26 03:22:02.385,DEBUG,SC,Override M190 S70.0
1632626548869,2021.09.26 03:22:28.869,WARN,SC,No reply for 26485 ms since last response (#37: M190 S70;Wait for Bed Temperature)
1632626558872,2021.09.26 03:22:38.872,WARN,SC,No reply for 36487 ms since last response (#37: M190 S70;Wait for Bed Temperature)
1632626568871,2021.09.26 03:22:48.871,WARN,SC,No reply for 46486 ms since last response (#37: M190 S70;Wait for Bed Temperature)
1632626578871,2021.09.26 03:22:58.871,WARN,SC,No reply for 56486 ms since last response (#37: M190 S70;Wait for Bed Temperature)
1632626588871,2021.09.26 03:23:08.871,WARN,SC,No reply for 66486 ms since last response (#37: M190 S70;Wait for Bed Temperature)
1632626598873,2021.09.26 03:23:18.873,WARN,SC,No reply for 76488 ms since last response (#37: M190 S70;Wait for Bed Temperature)
1632626713750,2021.09.26 03:25:13.750,INFO,SC,line 1000: G1 X176.439 Y108.541 E45.84494
1632626756469,2021.09.26 03:25:56.469,INFO,SC,line 2000: G1 X208.693 Y156.294 E71.15676
1632626817401,2021.09.26 03:26:57.401,INFO,SC,line 3000: G1 X229.058 Y136.019 E98.85737
1632626848870,2021.09.26 03:27:28.870,WARN,SC,No reply for 20746 ms since last response (#3397: G1 X216.49 Y259.741 E105.13469)
1632626857431,2021.09.26 03:27:37.431,DEBUG,SC,Print drawer opened.
1632626858873,2021.09.26 03:27:38.873,WARN,SC,No reply for 30747 ms since last response (#3397: G1 X216.49 Y259.741 E105.13469)
1632626866310,2021.09.26 03:27:46.310,DEBUG,SC,Print drawer closed.
1632626868376,2021.09.26 03:27:48.376,INFO,SC,Stop print.
1632626868870,2021.09.26 03:27:48.870,WARN,SC,No reply for 40746 ms since last response (#3397: G1 X216.49 Y259.741 E105.13469)
1632626878872,2021.09.26 03:27:58.872,WARN,SC,No reply for 50748 ms since last response (#3397: G1 X216.49 Y259.741 E105.13469)
1632626888872,2021.09.26 03:28:08.872,WARN,SC,No reply for 60748 ms since last response (#3397: G1 X216.49 Y259.741 E105.13469)

brent113 · September 26, 2021, 5:41am

Something’s broken, contract support for replacement parts. Any additional posts here will have to be repeated to support, you’re better off just talking to them.

Artezio · September 26, 2021, 7:23pm

@ThirstyDragon Yeah, with it still not flashing the firmware of the head correctly, the head is most likely suffering from a bad memory issue, I was suspecting it but wanted to cover all possible bases so you could just tell support that you already did it if/when they ask you to do it. Hoping it cuts down on the turnaround time for you to get a new head since support takes a few days to respond. Only solution is to contact them and get a new module like @brent113 said.

Edit: I just noticed something, the firmware error is no longer in the log when you used 1.9, that makes me think controller.

ThirstyDragon · September 27, 2021, 12:25am

@Artezio I sent in a support request to snapmaker and they responded relatively quickly. They checked the FW log and saw a runaway hotend temp error. When I first looked at the FW log it must have not exported properly because it was blank so I had been posting the SC log here. This doesn’t exclude the fact that it was still throwing warnings in the SC log, but the support rep did find an error in the FW log, so they told me to check the thermistor wire on the hot end.

I just replaced it with the spare hotend in general since I saw nothing strange with the wiring, and am testing a print now. This is what my previous one looked liked. I don’t know if that brown stuff is bad or just normal.

ElloryJaye · September 27, 2021, 1:20am

Pretty sure the brown stuff is not normal. Have you been using brown filament?

Artezio · September 27, 2021, 1:26am

@ThirstyDragon that brown stuff is cooked silicone, or more specifically the adhesive, the thermal runaway error never made it to the logs on here did it? I don’t recall seeing it. Sure would’ve made it easier lol. But it still doesn’t explain the firmware error on the head, did you update the firmware back to 1.13.2, or is it still at 1.9?

ThirstyDragon · September 27, 2021, 3:35am

I updated it back to 1.13.2, and I’m currently doing a print with fully updated firmware/luban, which is running fine as far as I can tell. I’m recording it on a cam right now since it’s going to be moderately long print, but so far it looks good.

The invalid errors are still there last I checked, but they don’t seem to be causing any issues at the moment. Very strange.

Yes the FW log never made it on here unfortunately, I think that’s my fault, from what I can tell sometimes the export log fails for whatever reason and it creates a blank log file. I saw this and thought it was just empty, so that’s why we never really looked at it.

Topic		Replies	Views
Snapmaker A350 printing stops / freezes at 2/3 Snapmaker 2.0	21	1561	January 9, 2025
Prints randomly stopping Snapmaker 2.0	7	571	February 11, 2021
Print Fails After First Few Layers (3% - 8%) Snapmaker 2.0	12	973	September 8, 2021
Snapmaker 2.0 freezing at 66% whenever I print a certain object Snapmaker 2.0	2	491	May 20, 2022
57% Print, Fabscreen Has Stopped Working A350 Snapmaker 2.0	6	451	January 7, 2021

Print Stops at 3%

Related topics