Attached is my configuration.h.
I upgraded from Marlin 1.1.0-RC8, transfered the settings to the current version.
Now when a print job starts, the hotend heats up, the hot bed heats up, the carriage homes......
The print job starts - that is, the start G-code kicks off, the head/carriage moves to 0,0,0, begins to prime, the extruder moves...
But, in the terminal window it has already started to throw errors.
Here is the terminal window output from Octoprint just after the printer 'homes'-
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
Recv: X:120.00 Y:120.00 Z:0.00 E:5.00 Count X:9662 Y:9661 Z:0
Recv: ok
Send: N11 G1 X0 Y5 Z0.2 F3000*47
Recv: ok
Send: N12 G92 E0*116
Recv: X:0.00 Y:5.00 Z:0.20 E:0.00 Count X:9662 Y:9661 Z:0
Recv: ok
Send: N13 G1 X200 E25 F600*98
Recv: ok
Send: N14 G92 E0*114
Recv: X:120.00 Y:5.00 Z:0.20 E:0.00 Count X:9661 Y:9660 Z:1
Recv: ok
Send: N15 G1 E-1.2500 F207*31
Recv: ok
Send: N16 G1 Z0.180 F1000*37
Recv: ok
Send: N17 T0*12
[...]
Recv: echo:busy: processing
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor
Does this mean anything to anyone?
Here is my G code start script (works fine on my previous version of Marlin):
Arduino Build stats -
Previous Build I use -
Sketch uses 131688 bytes (51%) of program storage space. Maximum is 253952 bytes.
Global variables use 4711 bytes (57%) of dynamic memory, leaving 3481 bytes for local variables. Maximum is 8192 bytes.
Current build -
Sketch uses 133258 bytes (52%) of program storage space. Maximum is 253952 bytes.
Global variables use 4626 bytes (56%) of dynamic memory, leaving 3566 bytes for local variables. Maximum is 8192 bytes.
Thanks!
I upgraded from Marlin 1.1.0-RC8, transfered the settings to the current version.
Now when a print job starts, the hotend heats up, the hot bed heats up, the carriage homes......
The print job starts - that is, the start G-code kicks off, the head/carriage moves to 0,0,0, begins to prime, the extruder moves...
But, in the terminal window it has already started to throw errors.
Here is the terminal window output from Octoprint just after the printer 'homes'-
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
Recv: X:120.00 Y:120.00 Z:0.00 E:5.00 Count X:9662 Y:9661 Z:0
Recv: ok
Send: N11 G1 X0 Y5 Z0.2 F3000*47
Recv: ok
Send: N12 G92 E0*116
Recv: X:0.00 Y:5.00 Z:0.20 E:0.00 Count X:9662 Y:9661 Z:0
Recv: ok
Send: N13 G1 X200 E25 F600*98
Recv: ok
Send: N14 G92 E0*114
Recv: X:120.00 Y:5.00 Z:0.20 E:0.00 Count X:9661 Y:9660 Z:1
Recv: ok
Send: N15 G1 E-1.2500 F207*31
Recv: ok
Send: N16 G1 Z0.180 F1000*37
Recv: ok
Send: N17 T0*12
[...]
Recv: echo:busy: processing
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
[...]
No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor
Does this mean anything to anyone?
Here is my G code start script (works fine on my previous version of Marlin):
G21 ;metric values G90 ;absolute positioning M82 ;set extruder to absolute mode M107 ;start with the fan off G28 X0 Y0 ;move X/Y to min endstops G28 Z0 ;move Z to min endstops G1 Z15.0 F{travel_speed} ;move the platform down 15mm G92 E0 ;zero the extruded length G1 F200 E3 ;extrude 3mm of feed stock G92 E0 ;zero the extruded length again G1 F{travel_speed} ;Put printing message on LCD screen M117 Printing...
Arduino Build stats -
Previous Build I use -
Sketch uses 131688 bytes (51%) of program storage space. Maximum is 253952 bytes.
Global variables use 4711 bytes (57%) of dynamic memory, leaving 3481 bytes for local variables. Maximum is 8192 bytes.
Current build -
Sketch uses 133258 bytes (52%) of program storage space. Maximum is 253952 bytes.
Global variables use 4626 bytes (56%) of dynamic memory, leaving 3566 bytes for local variables. Maximum is 8192 bytes.
Thanks!