Closed evilC closed 1 year ago
It's ok to post issues here. I've forwarded the feedback to our firmware developers.
Hi evilC, the reaason of this issues is that, a private error log with "ERROR" tag triggers OctoPrint shutdown the printer by sending M112, which cause the printer enter halted status.
Here is the logs when this problem come up:
1675146704623,2023.01.31 06:31:44.623,INFO,SC-FW,ERROR:heve no cmd_set:1, cmd_id:162
1675146704626,2023.01.31 06:31:44.626,INFO,SC-FW,echo:M112 Shutdown
1675146704627,2023.01.31 06:31:44.627,INFO,SC-FW,Error:Printer halted. kill() called!
We will fix this issues by changing the "ERROR" tag to "SNMK_ERROR" tag in next release version.
Have fixed this by commit id: 85904090539c15a3b4d1d6f9499b73ba12f4ea0e. We are goting to close this isssue.
Edit: I realized of course that this is not related to Cura - where do I post issues related to the firmware? The Snapmaker2-Controller repo?
Control
on the printer's screenYour printer's firmware reported an error. Due to that OctoPrint will disconnect. Reported error: heve no cmd_set:1, cmd_id:162
I can do this just fine with my other marlin printers. eg I can connect octoprint, then use the menu on the printer itself to load / unload filament etc, and it does not mess with the octoprint connection.