Octoprint on Ender 3 pro failing every 5-6 prints with a "communications error" - yeeeeelp :/

Hi awesome pplz of Octoprint,

Got my very first 3D printer (Creality Ender 3 Pro) this Dec. Awesome machine. Solved quite a few problems using google (like preheating the nozzle to remove fillament / DUH :smiley: )

Hitting an issue atm, and google is no longer my friend :frowning:

Printer halts every 5-6 prints with a "communication error", effectively ruining the print. Very annoying after a fine 10 hour run....

Setup: Ender 3 pro + octopi on Pi 4b+ webcam, upload prints via wi-fi to Pi, Pi then connected by cable to Ender 3. Poor wi-fi at the workshop :confused:

Already tried:

  1. Blocking USB slot pin 1, so the PI does not feed the motherboard.
  2. Printing from SD card alone - printed perfectly (luck?)

I'm adding the following log files/photos at https://gofile.io/d/nkEj6Z

  1. Octopi GUI terminal output - GUI output when printing
  2. IMG_20210126_191219 - failed print
  3. octoprint - Octopi log file
  4. serial - Octopi log file
  5. screenshot - Octopi GUI error screenshot

Any assistance much appreciated.

Hello @Skiedra123! Nice to meet you.

You may run in safe mode.
Also you may disable thespaghettidetective. (It also seems to to be configured).

Your serial connection seems to be ok:

2021-01-26 16:00:45,350 - Recv: ok
2021-01-26 16:00:45,352 - Send: N7460 G1 X92.437 Y155.272 E0.01951*102
2021-01-26 16:00:48,357 - 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.
2021-01-26 16:00:48,359 - Send: N7461 M105*19
2021-01-26 16:00:51,363 - 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.
2021-01-26 16:00:51,368 - Send: N7462 M105*16
2021-01-26 16:00:54,372 - 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.
2021-01-26 16:00:54,377 - Send: N7463 M105*17
2021-01-26 16:00:57,381 - 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.
2021-01-26 16:00:57,386 - Send: N7464 M105*22
2021-01-26 16:01:00,390 - 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.
2021-01-26 16:01:00,391 - Send: N7465 M105*23
2021-01-26 16:01:03,396 - 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.
2021-01-26 16:01:03,435 - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2021-01-26 16:01:03,453 - Connection closed, closing down monitor
2021-01-26 17:49:23,124 - Changing monitoring state from "Offline" to "Opening serial connection"
2021-01-26 17:49:23,138 - Connecting to port /dev/ttyUSB0, baudrate 115200
2021-01-26 17:49:23,217 - Changing monitoring state from "Opening serial connection" to "Connecting"
2021-01-26 17:49:23,221 - Connected to: Serial<id=0xa6bbc990, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2021-01-26 17:49:23,227 - Send: N0 M110 N0*125
2021-01-26 17:49:23,318 - Send: N0 M110 N0*125
2021-01-26 17:49:23,447 - Recv: start
2021-01-26 17:49:23,452 - Send: N0 M110 N0*125
2021-01-26 17:49:23,453 - Recv: echo: External Reset
2021-01-26 17:49:23,456 - Recv: Marlin 1.1.6.2
2021-01-26 17:49:23,457 - Recv: 
2021-01-26 17:49:23,460 - Recv: echo: Last Updated: 2019-07-26 | Author: Ender-3 Pro
2021-01-26 17:49:23,462 - Recv: echo:Compiled: Aug  4 2019
2021-01-26 17:49:23,464 - Recv: echo: Free Memory: 10078  PlannerBufferBytes: 1232
2021-01-26 17:49:28,681 - Recv: echo:TF init fail
2021-01-26 17:49:30,784 - Recv: echo:TF init fail
2021-01-26 17:49:30,786 - Recv: ok
2021-01-26 17:49:30,789 - Changing monitoring state from "Connecting" to "Operational"

But the printer stops to communicate.
Also, a SD card in the printer can cause trouble.

Thanks for a speedy reply, Ewald. SD card is out when PI is connected.
Can poor wi-fi /blackouts cause it?
I'll try disabling addons.

Normally not. That is another connection route.
There are times your printer is just not responding.

Others have that issue too with a Ender 3 (pro)

An problem could be EMI (Electro Magnetic Interference) from a power device nearby -like an AC, washing machine etc.

1 Like

There are power sources nearby (quite a few of them, actually). Testing all solutions one by one. Will update.
Thanks alot, I really value your feedback!

Dang, crashed on safe mode as well :frowning: .

You may try another location in your home, at leas another mains power outlet.
A high quality USB cable as short as possible.
Addition ferrite beads. Also on the power cables of the Pi and printer.

Although this is Ender 3 and I own an Ender 3 v2, the problem seems identical...

Hope we can get this figured out.

1 Like

I see excatly the same issue on my Ender 5. Did any of you manage to figure out what the problem was?

I think so, Peter.

For me it's the electrical power fluctuations in the wires

What I've tried:

  1. Moved the printer away from the boiler room, with lots and lots of electrical devices (boiler, water filters/softeners, furnace, etc.) . Helped somewhat.
  2. Moved it outside to my garden shed. Works well.
    Managed to re-create the stop-print-communications-error when putting in extra lights with a plug into a nearby socket. Printing stopped instantly.

So my tip would be to move it to a more "quiet" place electrically or get some sort of power filter to protect against fluctuations. In my town they're 10-20€ a piece.

2 Likes

And, btw, I'm on full setup now - Ender 3D Pro + Octoprint. Haven't had an issue repeat in the last 50+ prints (printed that loooooong magnetic Catan project)

3D NERDZ CAN I HAVE YOUR SERIAL .....IM HUNGRY, ok no more bourbn , my 3D friends who are constantly pulling there hair out or turning grey then pulling your hair out may i please just give some not so Einstien advice about Serial COMM and Connections..... now i know in Computers and Electronics there can be a thousand different reasons to fault find, though i would like to give you one minor-maybe a cause of some peoples issues. My OCO was working fine all day Decided to go and see if i could print my misses a rubber toy in to keep her occupied and i got the Connection jumble serial Bull Shiz i did read a post on here if you log back in in safe mode it shall work and yes whilst amazingly so simple and i much appreciate that help , if you have the motivation ask yourself what keeps causing it , Could be firmware yes, Could be Printer obviously , It is definetley not OCTOPRINT we already know that ,(i never have had not once any MAJOR annoying issues with OCO, so there could be numerous different troubleshooters, but there is one though i think we should all leave in the back of our minds and that is.......... believe it or not try if you wish a headache will; insue so, crossing cables crossing extension leads on top of USB extensions Low power DC ETC ETC these wires causing interfiernce is a pain in the as you wanna be neat and tidy put all the power leads together and all data and communication leads try keep them seperate from each other, and i know this sounds a bit loopy (no pun intended) try not to loop your connections around iscolate all Applications that may have conflict with each others needs IE using your pc to a USB relay to the PSU and another REplay on same board to your printer from stepped down DC volatgwe and then your raspberry pi ON OCO plugged into your printer aswell thats what i call lazy just made more confusion for yourself trouble, thats not something i would do, or have done its just an example, and possible after a few drinks :slight_smile: if you think thats not possible it is think about how many time you hear the USB or DATA cables GHOSTING sound of connec disconnect.. YES NO connecting to your PC numerous times , look down there be cross wires or maybe we cross eyed its still a possibility , and no need to thank me for the time it took me to write this very informative Formula it took me only 2 and a half bourbns so its my gift to all of us and yes ill leave the common sense to the smart ones BE SAFE 3D PRINT NERDS....(sorry no RETRACTION available for this comment) Back to printing and designing my misses a rubbery toy , THOUGHTS ON TPU anyone.

Hi. Wow that's a wall of text ;)

Please open a new thread and fill out the template so we're able to help you and try to describe your problem as clearly as possible (the Connection jumble serial Bull Shiz doesn't really help us :wink: )
Remember to attach a systeminfo bundle

I think his issue was resolved by not crossing the lines...avoiding EMI basically.

1 Like

I had the same problem on ender 3 v2 and the issue was that the lcd ribbon cable was crossing the 24v cables from the psu.
The retries dropped to 0% after rerouting the cables