# Strange issue with dual extruder today ("Machine not responding..") in mid of a print
**URL:** https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009
**Category:** Snapmaker 2.0 (3-in-1)
**Created:** [April 23, 2023, 3:38pm UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009 "2023-04-23T15:38:00Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@digitalfreak](https://forum.snapmaker.com/u/digitalfreak)
#### Post date: [April 23, 2023, 3:38pm UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/1 "2023-04-23T15:38:00Z")
Some weeks ago I installed my dual extruder to my A350 and did some test prints with dual collores and also some longer prints with only one extruder used.
This weekend I wanted to try the breakaway PLA. I also had some job that would realy profit from it. A simple model that I wanted to print in a certain orientation that would need support.
So far so good I set everything up, started the print. First layers looked good.
After about 1 hour of printing I was wondering why my printer stopped working. The light of the housing was off, the printhead was standing still everything was cold and the touchscreen showed “Machine not responding…”. reconnecting did nothing only a power cycle. I tried it again and the problem came again at the same place.
Coud this be problem with the g-code (done with the lates luban version, EDIT: the updater was not working I was on V4.5.1 not the latest, I will try again with 4.7.3)?
For me it more looks like a problem with the power supply overheating or the machine pulling to much power. But why does it apear exactly after the same time in multiple tries?
I am using V1.15.21 (just manualy downloading .23 now the printer doesn’t seem to “see” the new version) and was printing PETG (@235°C) and breakaway PLA (@220°C) printbed temp was set to 65°C.
If the power is the problem then the specs are not chosen good enough I would expect to theoreticly print with 300-300-80.
Did some ever expirienced an equal problem?
---
### Author:  [@digitalfreak](https://forum.snapmaker.com/u/digitalfreak)
#### Post date: [April 24, 2023, 5:39am UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/2 "2023-04-24T05:39:53Z")
I generated a fresh g-code with the latest 4.7. Version of luban. Now it stoped after 5 hours printing at 90%.
This module is totaly unreliable and a waste of money.
---
### Author:  [@dgatwood](https://forum.snapmaker.com/u/dgatwood)
#### Post date: [April 24, 2023, 5:51am UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/3 "2023-04-24T05:51:28Z")
I got a “Machine not responding” error shortly after I plugged the dual extruder in. I can’t remember if that was before or after I had to switch back to the original extruder to boot far enough to upgrade the firmware.
I haven’t seen any failures since, though, and that failure was at first boot, not while the unit was in operation.
In your case, it sounds like there’s some command in your G-code that is causing some component of the system to hang or crash. Your best bet is probably to reach out to Snapmaker support and provide them with a copy of the G-code so that they can figure out what’s going on.
Or it could be a loose toolhead cable that gets pulled loose at the same spot in the G-code for the same reason. Doubtful, but worth checking. 😁
---
### Author:  [@dgatwood](https://forum.snapmaker.com/u/dgatwood)
#### Post date: [April 24, 2023, 5:57am UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/4 "2023-04-24T05:57:20Z")
Also, don’t bother with V1.15.22 or V1.15.23. The release notes weren’t anything related to printing.
- 1.15.22 added info about the active Wi-Fi network and fixed a bug that can cause it to disconnect immediately whenever you connect remotely.
- 1.15.23 added RSSI info about Wi-Fi networks.
I’m pretty sure neither of those is relevant.
---
### Author:  [@digitalfreak](https://forum.snapmaker.com/u/digitalfreak)
#### Post date: [April 24, 2023, 11:46am UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/5 "2023-04-24T11:46:08Z")
Checking the cables was the first I have done after the initial failure. Writing a support ticket with the g-code was the second thing after I found out it was reproduceble.
So I hope I will get some solution for that.
---
### Author:  [@xchrisd](https://forum.snapmaker.com/u/xchrisd)
#### Post date: [April 24, 2023, 6:26pm UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/6 "2023-04-24T18:26:52Z")
You will have to share your logs, maybe post here with tripple backticks before and after?
```auto
```
`
---
### Author:  [@digitalfreak](https://forum.snapmaker.com/u/digitalfreak)
#### Post date: [April 24, 2023, 8:07pm UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/7 "2023-04-24T20:07:08Z")
Here is the log part that should show the error. The error must have happend at the last log entry from 23.04.
In the morning (first entry from 24.04.) I reconnected the touchscreen and tried to pause the job, what also failed with an error.
In the error state everything was off (head not moving and sitting on the moddel, hotends and bed cold, fans and enclosure light off) except the power supply.
> 1682288668880,2023.04.23 22:24:28.880,INFO,SC-FW,Set T0=209
> 1682288668882,2023.04.23 22:24:28.882,INFO,SC-FW,new E target temp: 215
> 1682288668884,2023.04.23 22:24:28.884,INFO,SC-FW,Set T1=215
> 1682288668886,2023.04.23 22:24:28.886,INFO,SC-FW,fan\_index: 1, speed: 255
> 1682288668888,2023.04.23 22:24:28.888,INFO,SC-FW,new E target temp: 220
> 1682288668891,2023.04.23 22:24:28.891,INFO,SC-FW,Set T1=220
> 1682288676451,2023.04.23 22:24:36.451,INFO,SC-FW,new E target temp: 230
> 1682288676459,2023.04.23 22:24:36.459,INFO,SC-FW,Set T0=230
> 1682288688392,2023.04.23 22:24:48.392,INFO,SC-FW,new E target temp: 215
> 1682288688398,2023.04.23 22:24:48.398,INFO,SC-FW,Set T1=215
> 1682288694211,2023.04.23 22:24:54.211,INFO,SC-FW,leveling OFF
> 1682288694217,2023.04.23 22:24:54.217,INFO,SC-FW,origin pos: 221.709, 264.244, 79.956
> 1682288694219,2023.04.23 22:24:54.219,INFO,SC-FW,raise: 1.000, endstop max: 332.596, z offset: -1.404
> 1682288694490,2023.04.23 22:24:54.490,INFO,SC-FW,raised pos: 221.709, 264.244, 80.956
> 1682288694682,2023.04.23 22:24:54.682,INFO,SC-FW,Unapply hotend[1] Z offset: 0.25
> 1682288696098,2023.04.23 22:24:56.098,INFO,SC-FW,offset pos: 195.790, 264.088, 82.359
> 1682288696945,2023.04.23 22:24:56.945,INFO,SC-FW,Apply hotend[0] Z offset: 0.25
> 1682288697243,2023.04.23 22:24:57.243,INFO,SC-FW,descent pos: 221.709, 264.244, 79.956
> 1682288697244,2023.04.23 22:24:57.244,INFO,SC-FW,leveling ON
> 1682288697245,2023.04.23 22:24:57.245,INFO,SC-FW,new E target temp: 150
> 1682288697246,2023.04.23 22:24:57.246,INFO,SC-FW,Set T1=150
> 1682288697247,2023.04.23 22:24:57.247,INFO,SC-FW,new E target temp: 230
> 1682288697257,2023.04.23 22:24:57.257,INFO,SC-FW,Set T0=230
> 1682288697258,2023.04.23 22:24:57.258,INFO,SC-FW,fan\_index: 0, speed: 127
> 1682288697259,2023.04.23 22:24:57.259,INFO,SC-FW,new E target temp: 235
> 1682288697260,2023.04.23 22:24:57.260,INFO,SC-FW,Set T0=235
> 1682311752943,2023.04.24 04:49:12.943,INFO,SC-FW,SC req PAUSE
> 1682311752944,2023.04.24 04:49:12.944,WARN,SC-FW,cannot pause in current status: 1
> 1682311752945,2023.04.24 04:49:12.945,INFO,SC-FW,SC req → Failed
> 39018,1970.01.01 00:00:39.018,INFO,SC-FW,Created marlin task!
> 39043,1970.01.01 00:00:39.043,INFO,SC-FW,SC req Exception
> 39134,1970.01.01 00:00:39.134,INFO,SC-FW,SC req enclosure sta
> 39136,1970.01.01 00:00:39.136,INFO,SC-FW,Eclosure: set LIGHT power 100
> 39140,1970.01.01 00:00:39.140,INFO,SC-FW,SC req emergency stop sta:1
> 39143,1970.01.01 00:00:39.143,INFO,SC-FW,SC req rotate sta:1
> 39649,1970.01.01 00:00:39.649,ERROR,SC-FW,purifier info update timeout:0 - 2!
> 39651,1970.01.01 00:00:39.651,INFO,SC-FW,SC req purifier sta:1, err:0x0
> 39654,1970.01.01 00:00:39.654,INFO,SC-FW,active\_probe\_sensor: 0
> 39656,1970.01.01 00:00:39.656,INFO,SC-FW,hotend\_type: 0: 1, 1: 1
> 39666,1970.01.01 00:00:39.666,INFO,SC-FW,hotend\_diameter: 0: 0.40, 1:0.40
> 39668,1970.01.01 00:00:39.668,INFO,SC-FW,Kp: 150.000, Ki: 1.000, Kd: 30000.000
> 39669,1970.01.01 00:00:39.669,INFO,SC-FW,z\_compensation: 0: 0.538, 1: 0.457
> 39728,1970.01.01 00:00:39.728,INFO,SC-FW,live Z offset 0: 0.25, 1: 0.25
> 40646,1970.01.01 00:00:40.646,ERROR,SC-FW,purifier info update timeout:0 - 2!
> 40648,1970.01.01 00:00:40.648,INFO,SC-FW,SC req purifier sta:1, err:0x0
> 1682311938627,2023.04.24 04:52:18.627,INFO,SC-FW,leveling OFF
> 1682311976960,2023.04.24 04:52:56.960,INFO,SC-FW,leveling ON
> 1682311977159,2023.04.24 04:52:57.159,INFO,SC-FW,Apply hotend[0] Z offset: 0.25
Edit, here is the other log at the same time:
> 1682288743486,2023.04.23 22:25:43.486,DEBUG,SC,batchGcodeResponse Request LineNo:388600
> 1682288743537,2023.04.23 22:25:43.537,DEBUG,SC,batchGcodeResponse Request LineNo:388602
> 1682288744719,2023.04.23 22:25:44.719,WARN,SC,Not getting machine status, replace with default status.
> 1682288745720,2023.04.23 22:25:45.720,WARN,SC,Not getting machine status, replace with default status.
> 1682288746719,2023.04.23 22:25:46.719,WARN,SC,Not getting machine status, replace with default status.
> 1682288747725,2023.04.23 22:25:47.725,WARN,SC,Not getting machine status, replace with default status.
> 1682288748718,2023.04.23 22:25:48.718,WARN,SC,Not getting machine status, replace with default status.
> 1682288749721,2023.04.23 22:25:49.721,WARN,SC,Not getting machine status, replace with default status.
> 1682288750719,2023.04.23 22:25:50.719,WARN,SC,Not getting machine status, replace with default status.
> 1682288751720,2023.04.23 22:25:51.720,WARN,SC,Not getting machine status, replace with default status.
> 1682288751723,2023.04.23 22:25:51.723,INFO,SC,onConnection, connected = false
> 1682288751725,2023.04.23 22:25:51.725,WARN,SC,Loss connection from machine.
> 1682288751735,2023.04.23 22:25:51.735,INFO,SC,Disable heartbeat.
> 1682304925839,2023.04.24 02:55:25.839,DEBUG,SC,Wi-Fi connected.
> 1682311695077,2023.04.24 04:48:15.077,INFO,SC,Try to reconnect machine…
> 1682311695084,2023.04.24 04:48:15.084,DEBUG,SC,Request 0x09 0x14
> 1682311695085,2023.04.24 04:48:15.085,DEBUG,SC,Requesting module info…
> 1682311695088,2023.04.24 04:48:15.088,DEBUG,SC,G-code Request Hex: AA 55 00 0A 01 0A 9D 4D 01 00 00 00 00 4D 31 30 30 35
> 1682311695090,2023.04.24 04:48:15.090,INFO,SC,onConnection, connected = true
> 1682311695094,2023.04.24 04:48:15.094,INFO,SC,Enable heartbeat.
> 1682311695585,2023.04.24 04:48:15.585,DEBUG,SC,Retry with delay number:1
> 1682311696117,2023.04.24 04:48:16.117,DEBUG,SC,Head type 5 found.
> 1682311696591,2023.04.24 04:48:16.591,DEBUG,SC,Request 0x09 0x14
> 1682311696610,2023.04.24 04:48:16.610,DEBUG,SC,Response 0x0a 0x14
> 1682311696611,2023.04.24 04:48:16.611,DEBUG,SC,Found emitter disposed, skip.
> 1682311696614,2023.04.24 04:48:16.614,DEBUG,SC,Machine model 3, size x 358 y 358 z 334
> 1682311752911,2023.04.24 04:49:12.911,INFO,SC,Pause print.
> 1682311752948,2023.04.24 04:49:12.948,WARN,SC,Unable to pause printing.
> 37794,1970.01.01 00:00:37.794,INFO,SC,Application started!
> 37796,1970.01.01 00:00:37.796,DEBUG,SC,Build SDK version: 25
> 37800,1970.01.01 00:00:37.800,DEBUG,SC,FabScreen version: V1.15.14
> 38962,1970.01.01 00:00:38.962,DEBUG,SC,HTTP server started.
> 38964,1970.01.01 00:00:38.964,INFO,SC,Connecting serial port…
> 39010,1970.01.01 00:00:39.010,DEBUG,SC,Request 0x09 0x14
> 39020,1970.01.01 00:00:39.020,DEBUG,SC,Requesting module info…
> 39024,1970.01.01 00:00:39.024,DEBUG,SC,G-code Request Hex: AA 55 00 0A 01 0A 9D 4D 01 00 00 00 00 4D 31 30 30 35
> 39035,1970.01.01 00:00:39.035,DEBUG,SC,Response 0x0a 0x14
> 39037,1970.01.01 00:00:39.037,DEBUG,SC,Machine model 3, size x 358 y 358 z 334
> 39039,1970.01.01 00:00:39.039,INFO,SC,onConnection, connected = true
> 39041,1970.01.01 00:00:39.041,INFO,SC,Enable heartbeat.
> 39053,1970.01.01 00:00:39.053,WARN,SC,Module 0x0C version (v1.13.12�,��) is invalid!
> 39061,1970.01.01 00:00:39.061,WARN,SC,Module 0x0C version (v1.13.12�,��) is invalid!
> 39069,1970.01.01 00:00:39.069,WARN,SC,Module 0x05 version (v1.13.12�,��) is invalid!
> 39084,1970.01.01 00:00:39.084,WARN,SC,Module 0x0C version (v1.13.12�,��) is invalid!
> 39093,1970.01.01 00:00:39.093,WARN,SC,Module 0x0C version (v1.13.12�,��) is invalid!
> 39103,1970.01.01 00:00:39.103,WARN,SC,Module 0x0C version (v1.13.12�,��) is invalid!
> 39111,1970.01.01 00:00:39.111,WARN,SC,Module 0x0D version (v1.13.12�,��) is invalid!
> 39138,1970.01.01 00:00:39.138,DEBUG,SC,Set Enclosure lighting true
> 39217,1970.01.01 00:00:39.217,DEBUG,SC,M1005
> Marlin SM2-4.5.34
> Compiled: Mar 9 2023, 17:08:07
> PACKAGE: Snapmaker\_V4.5.34
> Module Ver:
> Module 0x00C27B52: v1.13.12
> Module 0x00C27B78: v1.13.12
> Module 0x00509546: v1.13.12
> Module 0x00C84F3C: v1.13.12
> Module 0x00C84F48: v1.13.12
> Module 0x00C84F4C: v1.13.12
> Module 0x00D01B4A: v1.13.12
> linear\_tmc X1 length: 356 mm, lead: 20 mm
> linear\_tmc Y1 length: 356 mm, lead: 20 mm
> linear\_tmc Z1 length: 356 mm, lead: 8 mm
> linear\_tmc Y2 length: 356 mm, lead: 20 mm
> linear\_tmc Z2 length: 356 mm, lead: 8 mm
> Machine Size: L
>
> ok
>
> 39225,1970.01.01 00:00:39.225,DEBUG,SC,G-code Request Hex: AA 55 00 0A 01 0A 9D 4C 01 00 00 00 00 4D 31 30 30 36
> 39677,1970.01.01 00:00:39.677,DEBUG,SC,M1006
> Tool Head: 3DP
>
> echo:Hotend offsets: 0.00,0.00,0.000 25.92,0.16,-1.404
> ok
---
### Author:  [@xchrisd](https://forum.snapmaker.com/u/xchrisd)
#### Post date: [April 25, 2023, 4:36am UTC](https://forum.snapmaker.com/t/strange-issue-with-dual-extruder-today-machine-not-responding-in-mid-of-a-print/31009/8 "2023-04-25T04:36:56Z")
I am not so familiar with this logs but i guess the error appeared in the past of 22:24:28.880 your first log.
I see you tried to adjust the temperature and it may not work anymore?
In the second log the hotend was displaced for two seconds?
Are you on the latest firmware and update was ok?