Error with communication timeout
Here is the log of my print. Or at least the part im concerned about:
< 3:41:40.192: N44 M109 S215 ; Set extruder temp and wait to be reached
> 3:41:40.197: ok
< 3:41:40.197: N45 M532 X0.1092 L0
> 3:41:40.206: T:215.05 /215.00 B:70.00 /70.00 @:55 B@:54 W:?
> 3:41:40.289: T:215.05 /215.00 B:70.00 /70.00 @:55 B@:54
> 3:41:41.203: T:215.10 /215.00 B:69.99 /70.00 @:53 B@:58 W:2
> 3:41:41.290: T:215.00 /215.00 B:70.00 /70.00 @:56 B@:54
> 3:41:42.195: echo:busy: processing
> 3:41:42.203: T:215.05 /215.00 B:69.97 /70.00 @:54 B@:67 W:1
> 3:41:42.289: T:214.95 /215.00 B:69.95 /70.00 @:57 B@:76
> 3:41:43.202: T:215.00 /215.00 B:69.96 /70.00 @:55 B@:73 W:0
> 3:41:43.202: ok
< 3:41:43.202: M117 ETA 03:56:46 day 4
> 3:41:43.293: T:215.00 /215.00 B:69.91 /70.00 @:55 B@:91
> 3:41:44.292: T:215.00 /215.00 B:69.96 /70.00 @:55 B@:75
> 3:41:45.201: echo:busy: processing
> 3:41:45.292: T:215.16 /215.00 B:69.92 /70.00 @:52 B@:91
> 3:41:46.291: T:215.16 /215.00 B:69.97 /70.00 @:52 B@:76
> 3:41:47.200: echo:busy: processing
> 3:41:47.290: T:215.00 /215.00 B:69.96 /70.00 @:55 B@:83
> 3:41:48.286: T:215.00 /215.00 B:69.96 /70.00 @:55 B@:85
> 3:41:49.198: echo:busy: processing
> 3:41:49.285: T:215.00 /215.00 B:69.98 /70.00 @:55 B@:79
> 3:41:50.285: T:215.00 /215.00 B:69.96 /70.00 @:55 B@:90
> 3:41:51.193: echo:busy: processing
> 3:41:51.284: T:215.00 /215.00 B:69.98 /70.00 @:55 B@:83
> 3:41:52.284: T:215.05 /215.00 B:70.00 /70.00 @:54 B@:75
> 3:41:53.193: echo:busy: processing
> 3:41:53.284: T:215.10 /215.00 B:69.98 /70.00 @:52 B@:84
> 3:41:54.283: T:215.00 /215.00 B:70.00 /70.00 @:55 B@:77
> 3:41:55.204: echo:busy: processing
> 3:41:55.283: T:215.05 /215.00 B:69.97 /70.00 @:53 B@:91
> 3:41:56.626: T:214.90 /215.00 B:70.05 /70.00 @:57 B@:59
> 3:41:57.204: echo:busy: processing
> 3:41:57.626: T:215.16 /215.00 B:69.89 /70.00 @:0 B@:0
> 3:41:58.625: T:215.05 /215.00 B:69.85 /70.00 @:0 B@:0
> 3:42:01.210: Warning: Communication timeout - resetting communication buffer.
As you can see right after it sets the bed temp it runs the line: M532 X0.1092 L0
This is not in my gcode and I dont know what its doing... but its causing the communication timeout by the looks of things.
Any ideas to what this is?
As you can see right after it sets the bed temp it runs the line: M532 X0.1092 L0
This is not in my gcode and I dont know what its doing... but its causing the communication timeout by the looks of things.
Any ideas to what this is?
Comments
Im not so sure that this is the command it hangs. Server sends several commands in advance. Question is what is the command that takes so long. Temperatures are in target range all the time. I think the command is not visible in the log here that makes the problem, if it is any command at all.
Does communication come back? Is firmware responsible on lcd?