-
Notifications
You must be signed in to change notification settings - Fork 119
Description
What were you doing?
- Use Klipper
- Switch on PSU
- Connect via Auto-Connect
- FIRMWARE_RESTART is necessary to send after connecting but has to be delayed.
What did you expect to happen?
Klipper should be used with the plugin to switch on the printer automatically.
Should be solved with #269
or #269
What happened instead?
Klipper breaks with the following error:
Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 2 port/baudrate candidates: /tmp/printer@250000, VIRTUAL@250000
Trying port /tmp/printer, baudrate 250000
Connecting to port /tmp/printer, baudrate 250000
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0x99ed35e0, open=True>(port='/tmp/printer', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0125
Recv: // Lost communication with MCU 'mcu'
Recv: // Once the underlying issue is corrected, use the
Recv: // "FIRMWARE_RESTART" command to reset the firmware, reload the
Recv: // config, and restart the host software.
Changing monitoring state from "Detecting serial connection" to "Operational"
Recv: // Printer is shutdown
Recv: !! Lost communication with MCU 'mcu'
Send: N0 M110 N0125
Changing monitoring state from "Operational" to "Error"
Dieser Fehler wurde nicht von OctoPrint verursacht, es ist ein Problem, das von der Firmware deines Druckers gemeldet wurde, auf das OctoPrint reagiert hat!
Version of OctoPrint-PSUControl
PSU Control (1.0.6)
Operating System running OctoPrint
OctoPrint 1.10.2Python 3.9.2OctoPi* 1.0.0 (build 2024.06.18.085851)
Printer model & used firmware incl. version
Anycubic Mega S - Klipper Firmware version: v0.12.0-290-g14a83103c

