Unstable connectivity to engraver

[sanchosk]

Describe the bug
After boot, the laser engraver works OK. After I unplug and re-plug it, the USB device is detected, I can connect, but Octoprint does not allow the jog commands and after short time the communication error shows and the engraver disconnects
Testing using GNU screen, I can communicate with the device, send commands "?" or "$$" and I get the answer.

To Reproduce
Steps to reproduce the behavior:

1. Turn on Octoprint
2. Disconnect the engraver
3. Connect engraver back
4. Error message pops up after ~30 seconds with "Communication error" label and the serial connection disconnects.

Expected behavior
After short time, jog commands will be available and I will have no error.

Screenshots
N/A

Logs

Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 1 port/baudrate candidates: /dev/ttyUSB0@115200
Trying port /dev/ttyUSB0, baudrate 115200
Connecting to port /dev/ttyUSB0, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0x7f84434190, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: 

\x18
Recv: ok
Changing monitoring state from "Detecting serial connection" to "Operational"
Send: $$
Recv: 
Recv: Grbl 1.1h ['$' for help]
Send: $I
Send: $G
Send: $#
Recv: [VER:1.1h.2022070601:]
Recv: [OPT:VZ,15,128]
Recv: ok
Recv: [GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
Recv: ok
Recv: [G54:10.000,60.000,0.000]
Recv: [G55:0.000,0.000,0.000]
Recv: [G56:0.000,0.000,0.000]
Recv: [G57:0.000,0.000,0.000]
Recv: [G58:0.000,0.000,0.000]
Recv: [G59:0.000,0.000,0.000]
Recv: [G28:0.000,0.000,0.000]
Recv: [G30:0.000,0.000,0.000]
Recv: [G92:0.000,0.000,0.000]
Recv: [TLO:0.000]
Recv: [PRB:0.000,0.000,0.000:0]
Recv: ok
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

Additional context
N/A

[clevetbs]

i think if you did not do this https://community.octoprint.org/t/put-tape-on-the-5v-pin-why-and-how/13574 you will have that issue