What is the problem?
octoprint receive messages from the printer for about 30 seconds and after that nothing at all.
this cause octoprint to didn't send any new command.
all
What did you already try to solve it?
-Change usb cable with a shielded cable.
-reinstall octoprint inside my raspberry pi 3 B+
-re-flash firmware inside my printer (tevo tarantula running marlin 1.1.9)
-removed auto-recognize firmware from settings.
Additional information about your setup
-OctoPrint version 1.3.10
-OctoPi version: 0.16.0
-printer: TevoTarantula
-firmware: marlin 1.1.9
-octoprint log:https://pastebin.com/MdsYVxQs
-serial log: https://pastebin.com/d2z1Zm2q
NB: brefore restart i've tried to print forcing "ok" from the blue button above the terminal.
After the restart the communication stopped after the last temperature log, i've also sended another g28 and another g29 but they arent logged yet.
oh, right, i forgot to write that i've already tried both to change the ports on the rasp berry and to manually set the baudrate and port from octoprint.
It it were me, I'd camp out on the Terminal tab while it's connecting and look for responses from my firmware. I'd review my OctoPrint -> Settings -> Gcode Scripts to see which one happens on startup and if there are any blocking commands which could make the printer unresponsive upon handshaking with it.
I tried to change the printer firmware baud rate.
Initially it was set to 15200, I tried to increase it to 250000 but after exactly two answers it was blocked again.
later I tried with a lower baudarate, 38400 and it seems to have gone better. I received almost twice as many messages as I did in 15200, but it stopped after a while.
furthermore, I noticed (baud 15200) that when it crashes if I press the blue button"fake acknowledgment"below the terminal, it considers the command executed and sends the next one, the printer receives it without problems, executes it but does not respond.
If it were me, I'd add a ferrite core to my serial cable. Either it's a serial connection problem or it's a problem with the printer board or firmware; it should keep responding. You might also try verifying that all connections are sound (like the thermistor).
i use a shielded calbe, changed 2 times.
Anyway with pronterface or Cura from a pc work fine without any kind of problem i don't think the problem come from the printer.
It may be a power problem on the raspberry?