'Too many consecutive timeouts, printer still connected and alive?'

First time asking for support. Stock board and firmware Anycubic Mega X with the latest octoprint.

Timed out last few prints

Forgive me if this has already been resolved, I can't find a solution, but please link me to any that might help.

What is the problem?

Prints are failing due to timeouts

What did you already try to solve it?

reinstalled octoprint
Safe mode tried with just one plugin at a time
tried increasing the number of timeouts

Have you tried running in safe mode?

Yes for a few prints

Did running in safe mode solve the problem?

NO, have gotten the error in safe mode now.

Terminal:

Send: N108557 G1 X23.390 Y122.001 E0.07555*101
Recv: ok
Send: N108558 G1 X23.863 Y119.956 E0.07555*110
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.
Send: N108559 M105*23
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.
Send: N108560 M105*29
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.
Send: N108561 M105*28
Changing monitoring state from "Printing" to "Pausing"
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.
Send: N108562 M105*31
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
No response from printer after 16 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Pausing" to "Offline after error"
Connection closed, closing down monitor

Octoprint.log:
2021-08-17 11:59:41,846 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-08-17 11:59:49,431 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 15306, 'printer_state': 'PRINTING'}
2021-08-17 11:59:49,494 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
repeated lines deleted
filament = False input = 18
2021-08-17 12:14:10,560 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:14:16,554 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:14:20,573 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:14:30,587 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:14:37,369 - octoprint.server.util.flask - INFO - Passively logging in user 3Dprinter from 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:14:37,370 - octoprint.access.users - INFO - Logged in user: 3Dprinter
2021-08-17 12:14:37,545 - octoprint.server.util.sockjs - INFO - Client connection closed: 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:14:37,851 - octoprint.server.util.sockjs - INFO - New connection from client: 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:14:37,869 - octoprint.server.util.flask - INFO - Passively logging in user 3Dprinter from 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:14:37,869 - octoprint.access.users - INFO - Logged in user: 3Dprinter
2021-08-17 12:14:38,941 - octoprint.server.util.sockjs - INFO - User 3Dprinter logged in on the socket from client 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:14:40,600 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:14:41,847 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-08-17 12:14:46,586 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:14:49,431 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 16206, 'printer_state': 'PRINTING'}
2021-08-17 12:14:50,615 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:15:00,408 - octoprint.server.util.sockjs - INFO - Client connection closed: 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:15:00,626 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:15:10,639 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:15:16,619 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:15:18,132 - octoprint.server.util.flask - INFO - Passively logging in user 3Dprinter from ::ffff:192.168.0.242
2021-08-17 12:15:18,133 - octoprint.access.users - INFO - Logged in user: 3Dprinter
2021-08-17 12:15:18,988 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.0.242
2021-08-17 12:15:19,017 - octoprint.server.util.flask - INFO - Passively logging in user 3Dprinter from ::ffff:192.168.0.242
2021-08-17 12:15:19,018 - octoprint.access.users - INFO - Logged in user: 3Dprinter
2021-08-17 12:15:20,657 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:15:20,728 - octoprint.server.util.sockjs - INFO - User 3Dprinter logged in on the socket from client ::ffff:192.168.0.242
2021-08-17 12:15:30,674 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:15:37,363 - octoprint.util.comm - INFO - Pausing/resuming job on behalf of user 3Dprinter
2021-08-17 12:15:37,364 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Pausing"
2021-08-17 12:15:40,687 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:15:46,635 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:15:50,701 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:16:00,714 - octoprint.plugins.filamentreload - INFO - The value of the pin is 0. No filament = False input = 18
2021-08-17 12:16:16,667 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:16:46,699 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:17:15,245 - octoprint.server.util.flask - INFO - Passively logging in user 3Dprinter from 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:17:15,245 - octoprint.access.users - INFO - Logged in user: 3Dprinter
2021-08-17 12:17:15,596 - octoprint.server.util.sockjs - INFO - New connection from client: 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:17:15,613 - octoprint.server.util.flask - INFO - Passively logging in user 3Dprinter from 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:17:15,614 - octoprint.access.users - INFO - Logged in user: 3Dprinter
2021-08-17 12:17:16,673 - octoprint.server.util.sockjs - INFO - User 3Dprinter logged in on the socket from client 2001:8003:6822:b000:3071:67f4:a766:d8bb
2021-08-17 12:17:16,725 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:17:46,756 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:18:16,785 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:18:46,805 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:19:16,837 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:19:25,437 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.0.242
2021-08-17 12:19:46,868 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:20:16,885 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:20:46,895 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:21:16,927 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-08-17 12:21:46,958 - octoprint.util.comm - INFO - No response from printer after 16 consecutive communication timeouts, considering it dead.
2021-08-17 12:21:47,008 - octoprint.util.comm - INFO - Changing monitoring state from "Pausing" to "Offline after error"
2021-08-17 12:21:47,021 - octoprint.plugins.filamentreload - INFO - Error: Disabling filament sensor.
2021-08-17 12:21:47,040 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-08-17 12:21:48,044 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_timeout, payload: {'commerror_text': 'Too many consecutive timeouts, printer still connected and alive?'}

Serial.log:
2021-08-17 12:13:46,523 - Recv: ok
2021-08-17 12:13:46,525 - Send: N108558 G1 X23.863 Y119.956 E0.07555*110
2021-08-17 12:14:16,555 - 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-08-17 12:14:16,561 - Send: N108559 M105*23
2021-08-17 12:14:46,587 - 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-08-17 12:14:46,593 - Send: N108560 M105*29
2021-08-17 12:15:16,619 - 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-08-17 12:15:16,623 - Send: N108561 M105*28
2021-08-17 12:15:37,364 - Changing monitoring state from "Printing" to "Pausing"
2021-08-17 12:15:46,636 - 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-08-17 12:15:46,638 - Send: N108562 M105*31
2021-08-17 12:16:16,667 - 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-08-17 12:16:46,699 - 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-08-17 12:17:16,725 - 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-08-17 12:17:46,757 - 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-08-17 12:18:16,786 - 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-08-17 12:18:46,806 - 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-08-17 12:19:16,837 - 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-08-17 12:19:46,869 - 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-08-17 12:20:16,887 - 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-08-17 12:20:46,895 - 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-08-17 12:21:16,927 - 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-08-17 12:21:46,959 - No response from printer after 16 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-08-17 12:21:47,007 - Changing monitoring state from "Pausing" to "Offline after error"
2021-08-17 12:21:47,017 - Connection closed, closing down monitor

Heyho :slight_smile:

Most of the time the usb cable is responsible for this kind of problems.
Try it with another cable - if you can with a quality one with ferrit beads.

Also the length and the routing of the cable plays a role - the shorter the better and try to keep it away from noisy (EMI) things like the stepper motors.

Then things next to the printer could also effect the connection. For example a fridge, an AC or florescence lights.

I, for example, had an issue with florescence lights. Every time I turned them off the connection timed out.

1 Like

Ran another long print in safe mode and it lost the connection again. The cable ran under the printer and not directly next to any motors or anything.

Grabbed a short cable from an arduino it is shielded but doesn't have the ferrite things on it.

Trying again with the new cable and ran it in front and around the printer, so hopefully this will confirm or eliminate the cable being the issue.

octoprint log

2021-08-17 22:17:30,788 - octoprint.util.comm - ERROR - Unexpected error while reading from serial port
Traceback (most recent call last):
  File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 3860, in _readline
    ret = self._serial.readline()
  File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/util/comm.py", line 6488, in readline
    c = self.read(1)
  File "/home/pi/oprint/lib/python3.7/site-packages/serial/serialposix.py", line 596, in read
    'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-08-17 22:17:30,838 - octoprint.util.comm - ERROR - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
2021-08-17 22:17:30,846 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline after error"

Serial log

2021-08-17 22:17:30,838 - Unexpected error while reading serial port, please consult octoprint.log for details: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:3860
2021-08-17 22:17:30,840 - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
2021-08-17 22:17:30,845 - Changing monitoring state from "Operational" to "Offline after error"
2021-08-17 22:17:30,848 - Connection closed, closing down monitor


Shortest insulated cable I had, added the ferrite beads, no problems yet!

2 Likes

Hey thanks for that, couldn't replicate the problem with the shortest cable I had, added ferrite beads to it, and got a 4 pack so put some on my long cable that was having regular errors as well. Back to using the long cable that is zip tied to run under/through the printer frame with the added ferrite beads, have done several long prints, have paused and resumed as well and have had no timeouts so far.

So unless there was a solar storm or something, it seems that the cable was the source of the issue, and now the two cables I have seem fixed now.

1 Like

I am getting the "Too many consecutive timeouts, printer still connected and alive?" and have tried different cables and adding cable ferrites. Needless to say I am epic failing; I am new to Octoprint so any help please.

Changing monitoring state from "Detecting serial connection" to "Operational"
Send: N0 M110 N0125
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1 M115
39
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N2 M21*18
No response from printer after 3 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Operational" to "Offline after error"
Connection closed, closing down monitor

What printer do you have?

Prusa i3 MK3S+

That confirms my suspicions - check this topic:

Make sure the RPi Port is set to 'off'

Thank you; this seems to have solved the problem.

Thanks for this. I accidentally enabled RPI while trying to select live Z adjust. Went back in and disabled and good again. * PHEW * !