1.1.x BugFix Crashes On Print

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):

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!

Edited 1 time(s). Last edit at 09/17/2018 01:22AM by Eddiie.

In line N17 the code is "T0" - what is this?
Should the line not start with G or M? Is T0 not usually is a parameter that is associated with a Gxxx or Mxxx code?

I wonder if Marlin is as confused as I am about this T0 command, and this is why it just keeps processing?

T0 is select tool 0 [reprap.org]

Its been valid for a very long time.

I installed 1.1.9 and got the same result. Reverted back to 1.1.0-RC8
So it isn't a bugfix thing.

I assume the slicer is throwing in the T0. It is not in my start script.

Marlin is awesome by the way. Thank you for everything.

Quote
Eddiie
I installed 1.1.9 and got the same result. Reverted back to 1.1.0-RC8

I upgraded to Marlin 1.1.5 and am very happy with the results, when I tried to setup Marlin 1.1.8/1.1.9 could not get them to work.
May try again one day as I have been researching all the configuration changes being made to correct the crazies from happening.
Though I do not know what functions would be in Marlin Versions 1.1.6 - 1.1.9 that I could not live without.

You may try this earlier version of Marlin 1.1.5 found it works well and easy to setup, this had all the functions I require at this time.
Babystepping, filament run-out monitor, Bi-Linear bed leveling, Menu X,Y,Z driven individual axis homing to name a few.

And as an added feature I did not expect, I can save the Bi-linear data and restore. Though most functions are reserved only for Unified Bed Leveling.
Just not having to re-level the bed every print is all I ever want in the first place. Though my bed is fairly level It helps with the first levels adhesion.
Using LCD "Store settings: to save Bed leveling data."
In Startup G-Code Add "M420 S1 ; Bed Leveling On" (I added to the last line too make sure it did not get disabled)

Using WinMerge this free program assisted me to loading both old and new files to compare and transfer across my needed changes.

Edited 6 time(s). Last edit at 09/18/2018 08:12AM by Roberts_Clif.

---

Computer Programmer / Electronics Technician