I have a problem when I lunch a printing gcode with octoprint interface, the printer have a problem when it goes from layer 1 to 2. The connection is close and my ender reboot ...
THis message in octoprint :
"Communication error
There was a communication error while talking to your printer. Please consult the terminal output and octoprint.log for details. Error: Too many consecutive timeouts, printer still connected and alive?"
I have last update of rapsberry and octoprint is in 1.5.0
But when i lunch same gcode in SD card directily from ender, I don't have problem.
And the USB connection don't have 5V just GND, D+, D-.
Your printer stops responding to OctoPrint altogether here:
Send: N2568 G1 X132.188 Y85 E153.68361*116
Recv: ok
Send: N2569 G1 X132.403 Y86.076 E153.72011*96
Recv: ok
Send: N2570 G1 X133.012 Y86.988 E153.75658*105
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: N2571 M105*22
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: N2572 M105*21
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: N2573 M105*20
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: N2574 M105*19
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: N2575 M105*18
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.
Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor
OctoPrint needs a reliable serial communication with the printer to work. Could be a firmware issue maybe, but it's hard to say since your serial.log doesn't contain an actual connection to the printer, only a failed connection attempt.
I have test many impression today and I change the USB cable.
In this impression have 6 rest for 10 printng without change setting or configuration ....
The rest is between 1 and 2 layer. If the layer 2 printing; I don't have problem of all impression.
Do you have any ideas ? Or other log for help me ?
I have check firmeware, and i change this for 1.1.6, same problem, 1.1.9 the same ....
It's possible that Octoprint is the problem ? If I reinstall all It'possible to solve my problem ?
I'm not aware of any way that OctoPrint can make the printer stop responding by simply streaming a gcode file to it, and that is the problem here. Your firmware stops responding. Maybe it crashes, maybe it just takes really long to process whatever it is processing, but the result is, it stops to reply to OctoPrint and OctoPrint gives up after a while.
Current mainline Marlin is 2.x. You should ignore anything provided by Creality as it's known to be broken anyhow and instead go with a build of the current mainline Marlin release.