Octoprint no longer hold its connection to my printer

What is the problem?
I am using my printer and octoprint fore a while now no problems till now.
Had bin printing to day no problems at all.
Dit a manual bed level and then a auto bed leveling becos the Z axe moved becos i prest to hard on the bed to get a print off.
When i did no longer hear my printer i sow that the lever resolts did not end in the popup screan.
And the connection to the printer was closed.
Reconected, bit later on it closed again.
After octopi closes the connection to the printer the printer continues on its last comnand.

What did you already try to solve it?
I started unplugging all but the usb to the printer from the raspberry pi 3.
Only had a webcam and the printer on it.
Same thing.
Taken a new usb cable new port on the pi and conecter again same problem.
Restarted pi printer and pc same problem

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6a6a2a30, open=True>(port='/dev/ttyUSB0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125
Send: N0 M110 N0*125
Recv: start
Recv: echo:Marlin 1.1.4
Send: N0 M110 N0*125
Recv: 
Recv: echo: Last Updated: 2017-07-04 12:00 | Author: (none, default config)
Recv: Compiled: Jan  8 2020
Recv: echo: Free Memory: 3653  PlannerBufferBytes: 1232
Recv: echo:V39 stored settings retrieved (493 bytes; crc 10628)
Recv: echo:  G21    ; Units in mm
Recv: echo:  M149 C ; Units in Celsius
Recv: 
Recv: echo:Filament settings: Disabled
Recv: echo:  M200 D3.00
Recv: echo:  M200 T1 D3.00
Recv: echo:  M200 D0
Recv: echo:Steps per unit:
Recv: echo:  M92 X100.00 Y100.00 Z400.00 E150.00
Recv: echo:Maximum feedrates (units/s):
Recv: echo:  M203 X300.00 Y300.00 Z5.00 E25.00
Recv: echo:Maximum Acceleration (units/s2):
Recv: echo:  M201 X3000 Y3000 Z100 E10000
Recv: echo:Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
Recv: echo:  M204 P3000.00 R3000.00 T3000.00
Recv: echo:Advanced: S<min_feedrate> T<min_travel_feedrate> B<min_segment_time_ms> X<max_xy_jerk> Z<max_z_jerk> E<max_e_jerk>
Recv: echo:  M205 S0.00 T0.00 B20000 X20.00 Y20.00 Z0.40 E5.00
Recv: echo:Home offset:
Recv: echo:  M206 X0.00 Y0.00 Z0.00
Recv: echo:Auto Bed Leveling:
Recv: echo:  M420 S0 Z0.00
Recv: echo:Material heatup parameters:
Recv: echo:  M145 S0 H240 B60 F0
Recv:   M145 S1 H240 B60 F0
Recv: echo:PID settings:
Recv: echo:  M301 P22.20 I1.08 D114.00
Recv: echo:  M304 P10.00 I0.02 D305.40
Recv: echo:Z-Probe Offset (mm):
Recv: echo:  M851 Z-1.42
Recv: echo:SD init fail
Recv: ok
Changing monitoring state from "Connecting" to "Operational"
Send: N0 M110 N0*125
Recv: ok
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin 1.1.4 (Github) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:3D Printer EXTRUDER_COUNT:2 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
Recv: Cap:EEPROM:1
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:PROGRESS:0
Recv: Cap:PRINT_JOB:1
Recv: Cap:AUTOLEVEL:1
Recv: Cap:Z_PROBE:1
Recv: Cap:LEVELING_DATA:1
Recv: Cap:SOFTWARE_POWER:0
Recv: Cap:TOGGLE_LIGHTS:0
Recv: Cap:CASE_LIGHT_BRIGHTNESS:0
Recv: Cap:EMERGENCY_PARSER:0
Recv: ok
Send: M21
Recv: echo:SD init fail
Recv: ok
Send: M420V1
Recv: Bilinear Leveling Grid:
Recv:       0      1      2      3
Recv:  0 -0.013 +0.070 -0.015 -0.018
Recv:  1 -0.108 +0.077 -0.088 -0.155
Recv:  2 -0.090 +0.002 -0.018 -0.160
Recv:  3 -0.005 +0.045 -0.058 -0.123
Recv: 
Recv: echo:Bed Leveling Off
Recv: echo:Fade Height Off
Recv: ok
Send: M851
Recv: echo:Z Offset : -1.42
Recv: ok
Send: M155 S2
Recv: ok
[...]
Send: M104 S220
Recv: ok
[...]
Send: M140 S80
Recv: ok
[...]
Send: G28
[...]
Recv: echo:busy: processing
Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
Recv: X:85.00 Y:104.00 Z:11.42 E:0.00 Count X:8500 Y:10400 Z:4568
Recv: ok
Send: G29
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Changing monitoring state from "Operational" to "Offline"
Connection closed, closing down monitor

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
I am using a raspberry pi 3 and the Flsun Cube 3d with the mks gen l v1.0 board running marlin

Please don't remove parts of the logs, and please post a link instead of copy/pasting the logs into the message. For all we know, the interesting parts are in that last [...], or before the first line you posted.

Yes, will do.
Do you nead a new log?
Becos the [...] ar Suppress temperature messages
Thats the only thing i suppresst.

Thats the only thing i supressed

We can't smell that :wink:

Note that the actual logs requested are not copy/pastes from the terminal tab, but octoprint.log which can be downloaded from the OctoPrint Settings window under the "Logging" section.

and a serial.log or indeed at the very least the (unfiltered) contents of the terminal tab, especially in case of any kind of communication issues.

My english is not so good, please hold that in mind :slight_smile:
I did not ment in that way as it soundet.
I am not at home at the moment and cant upload those files :slight_smile:
When i get home i will upload them.
I hope its not the main board of my printer, had alredy replaced my 12v and 24v powersuply..

Sorry fore the late come back, had a migrane.
I have turnd on the serial log, becos it was still off it seems...
octoprint.log (8.8 KB) serial (1).log (5.3 KB)

I hope i did it the right way this time?

This ime i also went in to marlin to check if i have the "keep alive" setting unabled.
And it is.
But i also was thinking that that could not be it or i could not have bin printing with this setup fore so long.

The problem is still there.
I hope some one can help :slightly_smiling_face: