Print fails - Error: Line Number or Gibbersh, never the same spot

What is the problem?

System specs below. No major changes to any of my setup but prints just started failing about 80-90% of the time. From the terminal I see it happening for one of two reasons, cannot tell which is ultimately causing the failure. I'm getting the "Error:Line Number is not Last Line Number+1.... " and also "Recv: echo:Unknown command: "}wÃ/­µúþ¾?ü¨µ)Ã%º–¬µ¤¥¡^Áì+ÿ{/9ý½ß‰°ê)¨­¸J" or similar unknown commands with gibberish. Seems like everything is too chatty, and things get overwhelmed to the point it's just too much for one end or the other to digest and interpret correctly with line resends and gibberish in the mix.

What did you already try to solve it?

  • Read multiple forum posts and tried the following:
  • Tried different STL files, re-sliced the same files, issue still persist
  • Lots of articles reference EMI or bad power supply and/or cable to Rpi, I've tried 4 different power supplies and even more cables, issue still persists
  • Ran in SAFE mode, same issues persists
  • Prints sometimes fail near the same layer, but it's not exactly the same spot... sometimes they fail early (15-20% complete) or sometimes it's 90% complete.
  • Tried to diagnose when the issue started and what Octoprint or Plugin updates may occurred when issue started, but could not find make any correlations. Not saying this isn't the issue, just nothing there I can see (albeit I'm not the most technical).

Have you tried running in safe mode?

YES

Did running in safe mode solve the problem?

Print was successful, but errors/issues are still showing in logs that I think are the issue. How can I narrow down the issue, maybe it's a plugin?

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
octoprint-systeminfo-20250813132135.zip (2.1 MB)

I've also uploaded some of the files from failure last night below. The "bundle" attached above is from SAFE mode print where I'm still seeing the same errors/issues, but the print did complete successfully (after it failed x5 not in SAFE mode).

Other_Files.zip (1.4 MB)

Additional information about your setup

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

  • Ocotprint = v1.11.2
  • OctoPi = Build 2023.07.18.111854 with "webcamd", based on OctoPi 1.0.0, running on Raspberry Pi 3 Model B Rev 1.2
  • Printer = Ender3 Pro running Marlin v1.1.2 (2020-04-25)
  • Printer HW Addons = CR Sprite Direct Drive extruder with integrated CRTouch and dual Z axis
  • Browser = Issue persists across both Chrome and FireFox
  • Laptop OS = Win 11
  • Slicer = Cura v5.2.1

2025-08-13T05:00:00Z

First, this is appears to be a random bad USB connection from the Pi to the printer.
It has nothing to do with the STL files.

This occurs for a certain time: 20 seconds, 3 seconds, sometimes just one line,

You may check the USB cable: Proper seating of the plugs, damages, high quality product...
Check for high power devices near by (ACs, fridges etc) -> EMI

TBH, I did not think to attempt different cables between PI and Printer, only the power cable. The cable from the printer to Pi is high quality, but it is 3-4 years old... I bought it for the sole purpose of running Ocotoprint. I did previously make sure it was not running near any power cables/lines. Was I just lucky it successfully printed in SAFE mode after x5 failures out of SAFE mode? I will try a different cable and report back.

I want to thank you for your help. Changing the USB cable between the printer and Rpi solved all my issues. 3 successful different prints, not in SAFE mode. Frustrating the tinkering I did and it turns out to be nothing related to printer, Ocotoprint, etc... just a simple cable. Thanks again!

1 Like