Communication timeout while printing. Ender 2 Pro. Advice required

Get Help
2

It does look like a generic communication problems with the printer. The printer is complaining about things OctoPrint is sending it not reaching it. The resends and timeouts are definitely going to be causing the blobs on prints.

With Creality printers it is not uncommon to have communication issues, as their hardware can be questionable. I would recommend to go ahead with buying a high quality smaller cable, that's a common fix. You can search the forum for many posts about various fixes people use. Creality's software is not known for being high quality and bug free, so if you are using stock firmware it may be that non-Creality provided firmware would work better.

Trying safe mode might help because I think you have some plugins (DisplayLayerProgress) that would also send stuff to the serial connection. It doesn't look like it is choking on any particular lines, just normal movement commands.

Finally, the Pi is reporting at some points that it has had undervoltage, so you may need a better power supply on the Pi or use less peripherals.

1 Like
3

I tried safe mode after thinking the DisplayLayerProgress might be causing problems and it still has the issue.
I fixed the undervoltage issue by changing the Pi's USB power cable.

4

For you are using a Creality machine, one of the common tricks may help:

  • Put tape on the 5V pin - Why and how

  • Run with/without SD card in the printer's SD card slot.

  • Relocating the USB cable away from stepper motors and their cables and from the LCD and it's cable. Using ferrite beads on the USB cable.

5

I've so far tried running without the SD card, moving the USB cable and adding ferrite beads. Nothing seems to work.

6

Also tried putting tape on the 5V pin. The printer still worked, but it didn't stop the errors.

7

Creality printers are very susceptible to EMI and they are also generators of EMI. This is often a deadly combination. The USB cable should be short, shielded, and have ferrite beads. The routing of the USB cable can also be crucial as well as the routing of other cables inside the printer. You can search this forum for "communication" and find numerous topics and a collection of things to try to resolve this issue.

All I can say is keep trying things until it starts working.

8

I'm still trying various things - moving the pi, changing USB cables etc. Very difficult finding a decent micro USB cable on Amazon.

9

Looking at the serial log, it is always lines like this that cause the issue:

2022-07-27 12:36:02,282 - Recv:  T:200.00 /200.00 (109.00) B:60.00 /60.00 (857.00) @:92 B@:38
2022-07-27 12:36:04,281 - Recv:  T:200.00 /200.00 (109.00) B:60.00 /60.00 (857.00) @:92 B@:38
2022-07-27 12:36:06,281 - Recv:  T:200.00 /200.00 (109.00) B:60.00 /60.00 (857.00) @:92 B@:38
2022-07-27 12:36:06,283 - 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.
10

Here's one on Amazon, https://www.amazon.com/Monoprice-3-Feet-Micro-24AWG-Ferrite/dp/B004C4WEVI?th=1. Other lengths are available.

You might also look at this topic, https://community.octoprint.org/t/usb-cable-quality-necessary/32589/14. Note the part about shielding the cable that goes from the printer mainboard to the display of the printer.

11

Unfortunately that cable isn't available in the UK unless you order the 4.5m one!
I could try screening the display cable.

12

I resolved communication timeouts that are caused by EMI messing with the printer by installing an EMI filter on the mains cable to the printer. Was originally going to fit the filter in the printer but space a bit tight. You can also use a multibox that has the filter built in. Solved all my problems :wink:

1 Like
13

Do you have power loss recovery enabled on the printer?

That is also known to cause pauses which result in small blobs.

14

I turned that off as I heard it caused issues.

15

@mfraz74 Did you find any solution for your problem?

16

Hello @Ahnungsloser !

You have read the OP's last post?

17

I've given up for now. Going to try replacing the motherboard with a 4.2.3 board that I purchased a while ago next.

1 Like
18

I finally replaced the CR-FDM-v2.4.S4.170 motherboard with a 4.2.3 and OctoPrint works how it should. This needs to be added to the FAQ - if you have a CR-FDM-v2.4.S4.170 motherboard, don't expect it to work with OctoPrint.

1 Like
19

@mfraz74 DId you at any point flash a new Firmware onto the old board.
I have the same problem and would like to know if that's something worth trying.
Br

20

Before I bought the 4.2.3 board, Creality hadn't released any new firmware for the 2.4.S4. I see they have now, but I don't know if it fixes this issue.

21

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