<p>It seems, after checking the G-code file thoroughly, there was indeed an error in the G-code, that I didn’t find when I checked it the first time.</p>
<p>The Z-Axis suddenly moves from <code>Z13.3</code> to <code>Z9.175</code>. I have no idea how something like this can happen.</p>

CC BY-SA 4.0
2022-01-19T12:31:58.163Z
bad G-code can happen if you mistakenly overwrite only arts of a file or if you append G-code to other code messing up Z. usually it is manual interference or some massive error in the slicer
Trish
CC BY-SA 4.0
2022-01-19T10:33:25.330Z
2022-01-19T12:27:50.877Z
2022-01-19T12:27:50.877Z
jk1503
<p>So first of all I want to say, that I'm fairly new to 3D printing. I'm currently calibrating different things because I've got a little problem with rough walls. The last thing I did was increase the belt tension for X and Y a little bit. I now wanted to print a calibration cube with these new settings. Therefore I sliced the cube with Cura and started the print. Around 20 minutes into the print, I heard this weird sound and immediately stopped the print. Somehow the printer crashed into the printed cube. The adhesion to the plate was a little too good so the head got completely stuck.</p>
<p>I moved the head up and removed the print. It's pretty obvious looking at it, that for some weird reason the printer dropped the nozzle around 5 mm down. I tested all motors and axis, but everything seems to work alright. So the next thing I checked, was the G-code. I measured the height of my cube and found Z to be around 13.2 mm when it crashed. I don't know much about G-code, but I checked every Z movement between 12.7-13.5 mm and didn't find any value to be out of this range.</p>
<p>I have no idea what to check next. But I guess there has to be a major problem with my printer if this just happens. Maybe some of you have more ideas about what to check.</p>
<p>Printer: Anycubic i3 Mega S<br />
Firmware: Standard<br />
Slicer: Cura 4.13</p>
<p><a href="https://i.sstatic.net/Fs6rR.jpg" rel="nofollow noreferrer" title="Half printed model with burn marks"><img src="https://i.sstatic.net/Fs6rR.jpg" alt="Half printed model with burn marks" title="Half printed model with burn marks" /></a></p>
<p><a href="https://i.sstatic.net/N2i8W.jpg" rel="nofollow noreferrer" title="Another view of a half printed model with burn marks"><img src="https://i.sstatic.net/N2i8W.jpg" alt="Another view of a half printed model with burn marks" title="Another view of a half printed model with burn marks" /></a></p>

<z-axis><calibration><print-failure><anycubic-i3-mega>
Printer crashed into model
jk1503
# Printer crashed into model

(Asked by: username_0 on 2022-01-18)

So first of all I want to say, that I'm fairly new to 3D printing. I'm currently calibrating different things because I've got a little problem with rough walls. The last thing I did was increase the belt tension for X and Y a little bit. I now wanted to print a calibration cube with these new settings. Therefore I sliced the cube with Cura and started the print. Around 20 minutes into the print, I heard this weird sound and immediately stopped the print. Somehow the printer crashed into the printed cube. The adhesion to the plate was a little too good so the head got completely stuck.

I moved the head up and removed the print. It's pretty obvious looking at it, that for some weird reason the printer dropped the nozzle around 5 mm down. I tested all motors and axis, but everything seems to work alright. So the next thing I checked, was the G-code. I measured the height of my cube and found Z to be around 13.2 mm when it crashed. I don't know much about G-code, but I checked every Z movement between 12.7-13.5 mm and didn't find any value to be out of this range.

I have no idea what to check next. But I guess there has to be a major problem with my printer if this just happens. Maybe some of you have more ideas about what to check.

Printer: Anycubic i3 Mega S  
Firmware: Standard  
Slicer: Cura 4.13

[![Half printed model with burn marks](https://i.sstatic.net/Fs6rR.jpg "Half printed model with burn marks")](https://i.sstatic.net/Fs6rR.jpg "Half printed model with burn marks")

[![Another view of a half printed model with burn marks](https://i.sstatic.net/N2i8W.jpg "Another view of a half printed model with burn marks")](https://i.sstatic.net/N2i8W.jpg "Another view of a half printed model with burn marks")

**Tags:** z-axis, calibration, print-failure, anycubic-i3-mega


---

## 1 answers

### Answer by username_0 on 2022-01-19. Score: 3

It seems, after checking the G-code file thoroughly, there was indeed an error in the G-code, that I didn’t find when I checked it the first time.

The Z-Axis suddenly moves from `Z13.3` to `Z9.175`. I have no idea how something like this can happen.

> **Comments:**
> **username_1**: bad G-code can happen if you mistakenly overwrite only arts of a file or if you append G-code to other code messing up Z. usually it is manual interference or some massive error in the slicer  

---

