Two failed 12 hour prints

What is the problem?

Print halted with error message Unable to parse move "N407347 G1 X???????" (42.4 KB)

What did you already try to solve it?

Inspected the GCode fle and error log

Have you tried running in safe mode?


Did running in safe mode solve the problem?


Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)


Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Octoprint ver
Version 1.9.2

Octo pi
Build 2023.05.23.082504, based on OctoPi 1.0.0, running on Raspberry Pi 3 Model B Rev 1.2

Can you upload the gcode?
Zip it if the file is too big

Will do...just got to get my hair cut!

good luck :wink: :stuck_out_tongue:

That's done...Here is the gcode
G0ETP Main (2.8 MB)

The GCode looks ok to me. The printer (Voron running Klipper) is working OK on smaller prints. In the past, I have run longer prints like 23 hours with no problem.


Yeah I checked the line and it is ok.
It's no transmission error, the line was sent that way.
I really don't know how that happened. I think either some plugin modified the gcode or the gcode file on your pis sd card is faulty.
Was the gcode from the slicer or did you download it from the pi?
If it wasn't the gcode from the pi, also check that file.
Line 450488

The only plugin that I have is octopi. The gcode was generated by Prusaslicer.
The gcode file is quite big.......? any clue here?

You mean OctoKlipper, right?
Yeah that's the only explanation that I have besides of the corrupted filesystem / faulty sd card.

Well either jump to line 450488 or search for G1 E.16849 F2400. The line in question is three lines below that one.
any question marks or other weird stuff there?

I re loaded the gcode file to Octoprint and downloaded it and compared both versions. Both identical and no ????????'s.

I would nod to that.

OctoKlipper should not modify gcode files.

I doesn't necessarily need to be ??????'s - it could also be file corruption that resulted in other weird characters which were interpreted in a unpredictable way

Yeah it's unlikely that the plugin caused it.

Well the only thing left is some kind of hardware issue.
Let's check the kernel logs

SSH into the pi and run the following

sudo zip /var/log/kern.log*
sudo chown pi:pi 

Then connect to the pi with WinSCP and download the and upload it here

If you need help with ssh connection, follow this guide

username: pi
password: raspberry

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.