Internal Error on "FIRMWARE_RESTART" on second connection attempt to /tmp/printer

General Discussion
1

Basic Information:

Printer Model: Anycubic Mega S
MCU / Printerboard: Trigorilla 0.0.2
Host / SBC: Octoprint 1.10.2 / Raspberyy PI 4 / OctoPI 1.0.0
klippy.log
logs.txt (120.5 KB)

Describe your issue:

Using FIRMWARE_RESTART command after establishment of a connection to /tmp/printer from Octoprint. I am doing it like this to reset the printer to have it running after reconnection after a M112 shutdown.

This run into an Internal error on command:“FIRMWARE_RESTART” on the “second” connection attempt. The first one is fine and if I disconnect manually without a M112 the second connection to /tmp/printer runs into this error.

This is annoying as I have to restart Klipper and connect to it manually every time.

As I am using Klipper since 3 days and are still in the setup phase please correct me if this is the wrong place for reporting bugs.

Cheers,
Nils

2

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