Selecting Connect crashes my Ender 5+

What is the problem?

Within the past two weeks, every time I power on my Ender 5+ with an SKR Mini 3 V2, the minute I select connect in Octoprint, my printer is shut down and disconnected.

What did you already try to solve it?

I've replaced the board in my Ender 5+ with a new SKR Mini 3 V3, replaced the usb cable between the Raspberry Pi and the printer and installed new printer firmware

Have you tried running in safe mode?

Yes, and Octoprint connects with the printer and allows me to control movement, heating, etc .I also can see the temperature graph as it heats, both extruder and bed.

Did running in safe mode solve the problem?

Yes

Systeminfo Bundle

octoprint-systeminfo-20220921003236.zip (255.6 KB)
mall>

WRITE HERE

Additional information about your setup

OctoPrint version, 1.8.3
OctoPi version,0.18.0, running on Raspberry Pi 4 Model B Rev 1.4
printer, Ender 5+
firmware, Marlin 2 modified for Ender 5+ by Kersey Fabrication
browser, Microsoft Edge
operating system, Windows 11 Pro version 22H2
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
64-bit operating system, x64-based processor

This is one set of codes I managed to capture:

Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /dev/ttyACM0@115200, /dev/ttyACM0@250000, /dev/ttyACM0@230400, /dev/ttyACM0@57600, /dev/ttyACM0@38400, /dev/ttyACM0@19200, /dev/ttyACM0@9600
Trying port /dev/ttyACM0, baudrate 115200
Connecting to port /dev/ttyACM0, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0xac1b5e90, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Recv: ok N0 P15 B3
Changing monitoring state from "Detecting serial connection" to "Operational"
Send: N0 M110 N0*125
Recv: ok N0 P15 B3
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin bugfix-2.0.8.2.x (Mar 12 2022 01:22:27) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:Ender-5+ EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff

Your printer's firmware is a development build of Marlin (build date
20220312). It might be more unstable than a release version and should be
kept up-to-date.

Learn more at OctoPrint tells me I'm running a firmware development version, why? - FAQ - OctoPrint Community Forum

Recv: Cap:SERIAL_XON_XOFF:0
Recv: Cap:BINARY_FILE_TRANSFER:0
Recv: Cap:EEPROM:1
Recv: Cap:VOLUMETRIC:0
Recv: Cap:AUTOREPORT_POS:0
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:PROGRESS:0
Recv: Cap:PRINT_JOB:1
Recv: Cap:AUTOLEVEL:1
Recv: Cap:RUNOUT:0
Recv: Cap:Z_PROBE:1
Recv: Cap:LEVELING_DATA:1
Recv: Cap:BUILD_PERCENT:1
Recv: Cap:SOFTWARE_POWER:0
Recv: Cap:TOGGLE_LIGHTS:0
Recv: Cap:CASE_LIGHT_BRIGHTNESS:0
Recv: Cap:EMERGENCY_PARSER:1
Recv: Cap:HOST_ACTION_COMMANDS:1
Recv: Cap:PROMPT_SUPPORT:1
Recv: Cap:SDCARD:1
Recv: Cap:REPEAT:0
Recv: Cap:SD_WRITE:1
Recv: Cap:AUTOREPORT_SD_STATUS:0
Recv: Cap:LONG_FILENAME:1
Recv: Cap:THERMAL_PROTECTION:1
Recv: Cap:MOTION_MODES:0
Recv: Cap:ARCS:0
Recv: Cap:BABYSTEPPING:1
Recv: Cap:CHAMBER_TEMPERATURE:0
Recv: Cap:COOLER_TEMPERATURE:0
Recv: Cap:MEATPACK:0
Recv: ok N1 P15 B3
Send: M21
Recv: echo:SD card ok
Recv: ok P15 B3
Send: M104 S215
Recv: ok P15 B3
Send: M140 S60
Recv: //action:notification Bed Heating...
Recv: ok P15 B3
Send: M155 S2
Recv: ok P15 B3
Send: M876 P1
Recv: ok P15 B3
Send: M20
Recv: Begin file list
Recv: End file list
Recv: ok P15 B3
Recv: Error:MINTEMP triggered, system stopped! Heater_ID: bed
Changing monitoring state from "Operational" to "Error"
Send: M112
Send: N2 M112*35
Send: N3 M104 T0 S0*34
Send: N4 M140 S0*97
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor
Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port /dev/ttyACM0, baudrate 115200
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0xabafe2b0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
No answer from the printer within the connection timeout, trying another hello
Send: N0 M110 N0*125
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor

Then it is one of your installed plugins that is causing this. Disable all third party plugins, then re-enable them one by one and see at which point the problem shows up again.

Disabling Preheat Helper has fixed the issue. Thank you!

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.