Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing PostConnectDelay breaks Klipper integration #273

Open
NilsRo opened this issue Sep 12, 2024 · 0 comments
Open

Missing PostConnectDelay breaks Klipper integration #273

NilsRo opened this issue Sep 12, 2024 · 0 comments

Comments

@NilsRo
Copy link

NilsRo commented Sep 12, 2024

What were you doing?

https://community.octoprint.org/t/octoprint-cannot-connect-to-klipper-after-psu-is-switched-on-by-plugin-psu-control/60551

  1. Use Klipper
  2. Switch on PSU
  3. Connect via Auto-Connect
  4. FIRMWARE_RESTART is necessary to send after connecting but has to be delayed.

image
image

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 N0
125
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

Link to octoprint.log with octoprnt.plugins.psucontrol set to DEBUG

octoprint.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant