How do you find crashed layer hight?

Get Help
1

What is the problem?
I had a mid print crash and I would like to continue the print.

What did you already try to solve it?
I inspected the terminal log. I did vind where the crash occurred but could not find any z axis indication that would tell me the layer where it stoped.

Additional information about your setup
octoprint Version 1.3.10

Send: N1498167 G1 X183.628 Y121.877 E2.0367*90

Recv: T:195.11 /195.00 B:55.11 /55.00 @:52 B@:0

Recv: ok

Send: N1498168 G1 X183.418 Y122.490 E2.0538*94

Recv: ok

Send: N1498169 G1 X183.096 Y123.289 E2.0765*88

Recv: ok

Send: N1498170 G1 X182.647 Y124.313 E2.1060*93

Recv: ok

Send: N1498171 G1 X181.960 Y125.765 E2.1483*88

Recv: ok

Send: N1498172 G1 X181.394 Y126.882 E2.1812*91

Recv: ok

Send: N1498173 G1 X181.045 Y127.472 E2.1993*95

Recv: ok

Send: N1498174 G1 X180.959 Y127.596 E2.2033*86

Recv: ok

Send: N1498175 G1 X180.568 Y128.027 E2.2186*86

Recv: ok

Send: N1498176 G1 X180.233 Y128.359 E2.2310*91

Recv: ok

Send: N1498177 G1 X179.853 Y128.716 E2.2448*85

Recv: ok

Send: N1498178 G1 X179.368 Y129.134 E2.2616*87

Recv: ok

Send: N1498179 G1 X178.654 Y129.703 E2.2857*84

Recv: ok

Send: N1498180 G1 X178.144 Y130.068 E2.3022*93

Recv: ok

Send: N1498181 G1 X177.669 Y130.380 E2.3172*90

Recv: ok

Send: N1498182 G1 X176.859 Y130.864 E2.3420*86

Recv: ok

Send: N1498183 G1 X176.035 Y131.303 E2.3666*94

Recv: ok

Send: N1498184 G1 X173.692 Y132.432 E2.4351*87

Recv: ok

Send: N1498185 G1 X173.131 Y132.685 E2.4513*86

Recv: ok

Send: N1498186 G1 X172.948 Y132.668 E2.4562*87

Recv: ok

Send: N1498187 G1 X172.690 Y132.758 E2.4634*94

Recv: ok

Send: N1498188 G1 X172.572 Y132.765 E2.4665*84

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.

Send: N1498189 M105*35

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.

Send: N1498190 M105*43

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.

Send: N1498191 M105*42

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.

Send: N1498192 M105*41

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.

Send: N1498193 M105*40

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

Connecting to: /dev/ttyUSB0

Changing monitoring state from "Offline" to "Opening serial port"

Connected to: Serial<id=0x6e917150, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor

Starting baud rate detection...

Changing monitoring state from "Opening serial port" to "Detecting baudrate"

Trying baudrate: 115200

Send: N0 M110 N0*125

Recv: start

Changing monitoring state from "Detecting baudrate" to "Operational"

Recv: echo: External Reset

Recv: Marlin TH3D U1.R2.7

Send: N0 M110 N0*125

Recv:

Recv: echo: Last Updated: | Author: (TH3D)

Recv: echo:Compiled: Mar 22 2019

Recv: echo: Free Memory: 3445 PlannerBufferBytes: 1232

Recv: echo:EEPROM version mismatch (EEPROM=? Marlin=V55)

Recv: echo:Hardcoded Default Settings Loaded

Recv: echo:SD init fail

Recv: ok

Send: N1 M115*39

Recv: FIRMWARE_NAME:Marlin TH3D U1.R2.7 SOURCE_CODE_URL: PROTOCOL_VERSION:1.0 MACHINE_TYPE:TH3D U1.R2.7 EXTRUDER_COUNT:1 UUID:

Recv: Cap:SERIAL_XON_XOFF:0

Recv: Cap:EEPROM:1

Recv: Cap:VOLUMETRIC:0

Recv: Cap:AUTOREPORT_TEMP:1

Recv: Cap:PROGRESS:0

Recv: Cap:PRINT_JOB:1

Recv: Cap:AUTOLEVEL:0

Recv: Cap:Z_PROBE:0

Recv: Cap:LEVELING_DATA:0

Recv: Cap:BUILD_PERCENT:1

Recv: Cap:SOFTWARE_POWER:0

Recv: Cap:TOGGLE_LIGHTS:0

Recv: Cap:CASE_LIGHT_BRIGHTNESS:0

Recv: Cap:EMERGENCY_PARSER:0

Recv: Cap:AUTOREPORT_SD_STATUS:0

Recv: Cap:THERMAL_PROTECTION:1

Recv: ok

Send: M21

Recv: echo:SD init fail

Recv: ok

Send: M105

Recv: ok T:195.00 /0.00 B:54.60 /0.00 @:0 B@:0

Send: M155 S2

Recv: ok

Recv: T:193.49 /0.00 B:54.55 /0.00 @:0 B@:0

Recv: T:192.19 /0.00 B:54.33 /0.00 @:0 B@:0

Recv: T:190.68 /0.00 B:54.39 /0.00 @:0 B@:0

Recv: T:189.71 /0.00 B:54.31 /0.00 @:0 B@:0

Recv: T:188.33 /0.00 B:54.13 /0.00 @:0 B@:0

Recv: T:186.43 /0.00 B:54.28 /0.00 @:0 B@:0

Recv: T:185.44 /0.00 B:54.07 /0.00 @:0 B@:0

Recv: T:183.65 /0.00 B:54.09 /0.00 @:0 B@:0

Recv: T:182.36 /0.00 B:53.88 /0.00 @:0 B@:0

Recv: T:180.87 /0.00 B:54.04 /0.00 @:0 B@:0

Recv: T:179.42 /0.00 B:53.88 /0.00 @:0 B@:0

Recv: T:178.35 /0.00 B:53.93 /0.00 @:0 B@:0

Recv: T:176.90 /0.00 B:53.86 /0.00 @:0 B@:0

Recv: T:175.85 /0.00 B:53.77 /0.00 @:0 B@:0

Recv: T:174.39 /0.00 B:53.62 /0.00 @:0 B@:0

Recv: T:173.38 /0.00 B:53.57 /0.00 @:0 B@:0

Recv: T:171.99 /0.00 B:53.41 /0.00 @:0 B@:0

Recv: T:171.02 /0.00 B:53.31 /0.00 @:0 B@:0

Recv: T:169.77 /0.00 B:53.20 /0.00 @:0 B@:0

Recv: T:168.65 /0.00 B:53.11 /0.00 @:0 B@:0

Recv: T:167.43 /0.00 B:52.99 /0.00 @:0 B@:0

Recv: T:166.44 /0.00 B:52.89 /0.00 @:0 B@:0

Recv: T:165.17 /0.00 B:52.84 /0.00 @:0 B@:0

Recv: T:164.03 /0.00 B:52.87 /0.00 @:0 B@:0

Recv: T:162.88 /0.00 B:52.73 /0.00 @:0 B@:0

Recv: T:161.94 /0.00 B:52.62 /0.00 @:0 B@:0

Recv: T:160.79 /0.00 B:52.63 /0.00 @:0 B@:0

Recv: T:159.60 /0.00 B:52.48 /0.00 @:0 B@:0

Recv: T:158.53 /0.00 B:52.54 /0.00 @:0 B@:0

Recv: T:157.69 /0.00 B:52.38 /0.00 @:0 B@:0

Recv: T:156.58 /0.00 B:52.30 /0.00 @:0 B@:0

Recv: T:155.51 /0.00 B:52.33 /0.00 @:0 B@:0

Recv: T:154.54 /0.00 B:52.24 /0.00 @:0 B@:0

Recv: T:153.56 /0.00 B:52.21 /0.00 @:0 B@:0

Recv: T:152.76 /0.00 B:52.10 /0.00 @:0 B@:0

Recv: T:151.86 /0.00 B:52.44 /0.00 @:0 B@:0

Recv: T:150.60 /0.00 B:51.54 /0.00 @:0 B@:0

Recv: T:149.64 /0.00 B:51.89 /0.00 @:0 B@:0

Recv: T:148.86 /0.00 B:51.88 /0.00 @:0 B@:0

Recv: T:147.95 /0.00 B:51.59 /0.00 @:0 B@:0

Recv: T:147.02 /0.00 B:51.52 /0.00 @:0 B@:0

Recv: T:146.10 /0.00 B:51.35 /0.00 @:0 B@:0

Recv: T:145.26 /0.00 B:51.40 /0.00 @:0 B@:0

Recv: T:144.41 /0.00 B:51.34 /0.00 @:0 B@:0

Recv: T:143.50 /0.00 B:51.31 /0.00 @:0 B@:0

Recv: T:142.62 /0.00 B:51.23 /0.00 @:0 B@:0

Recv: T:141.75 /0.00 B:51.16 /0.00 @:0 B@:0

Recv: T:140.88 /0.00 B:51.10 /0.00 @:0 B@:0

Recv: T:140.13 /0.00 B:51.12 /0.00 @:0 B@:0

Recv: T:139.24 /0.00 B:50.97 /0.00 @:0 B@:0

Recv: T:138.38 /0.00 B:50.93 /0.00 @:0 B@:0

Recv: T:137.58 /0.00 B:50.88 /0.00 @:0 B@:0

Recv: T:136.66 /0.00 B:50.82 /0.00 @:0 B@:0

2

Since you have some of the GCode sent at the time of the failure you can open the GCode file in a text editor and search for those commands. The N number at the beginning is the line number may also be useful if your text editor has a line count. This N number is generated and is not in the original GCode file. Same with the * number at the end which is a checksum also generated to help detect bad communications.

Once you find the location in the GCode file, you can search backwards for a Z command. Depending on your slicer, you may also find some layer comments inserted by the slicer.

Now that you know what of the GCode has been printed and what still needs to be done. You have the much harder task of preparing the "rest" of the GCode and the printer for an attempt at recovery. I have seen some articles that discuss this process in more detail but I don't have any links to share.

I think you will find that the chances of success are low and that in most cases, it's faster to just clear the bed and start over.

1 Like
3

Don't forget to turn off any G29 autoleveling commands when trying to start up the second print job to complete it. And you also want to add your own G0/G1 commands to safely bring the hotend over and then down to resume printing. Otherwise, the assembly will just plow right into your part.

4

Thanks for the tips. I felt a bit unsure about the gcode edit. Last time I tried it, it smashed into the print. The auto home before print code was still in the fff settings. Almost wrecked my printer.

I ended up removing the failed print, measuring it and dropping the model through the bed to let I start at the (hopefully) correct hight. If it’s a success I’ll have to glue them together.

Would be nice if octo print would be more helpful in case of a fail. Give a nice clean readout of the layer and a resume option.

5

Why haven't I thought of that? Good Idea!!