Open lost-carrier opened 1 year ago
I fixed mine (Octoprint 1.8.4) using my Ender 3 S1 by adding M155
to the ignore commands
option in the plug in.
https://marlinfw.org/docs/gcode/M155.html M155 is the temperature report that spits out that date you referenced:
I noticed that the M155
command is kicked off in the terminal at Octoprint startup.
Would need full DEBUG logs (not snippets) and serial logs. If the plugin you mention does anything to interfere with GPIO state of another pin then that might be an issue. This plugin only interfaces with the GPIO pins specified whereas some other plugins may wipe or modify the entire GPIO config across the board.
@mdeeter a single M155
won't or at least shouldn't make a difference
What were you doing?
I've installed PSU Control with Tasmota Plugin which works fine.
Now I also installed OctoPrint-Emc2101 Plugin (https://github.com/JeremyLaurenson/octoprint-emc2101) to control a fan on the enclosure and also monitor enclosure temperature.
What did you expect to happen?
PSU Control turning off the PSU after idle - just as without Emc2101 plugin enabled
What happened instead?
When activating that Emc2101 PSU Control will not longer succede in turning off.
(reproduceable: Emc2101 plugin disabled -> power-off works, Emc2101 plugin enabled -> power-off does not work)
As I've found this https://github.com/kantlivelong/OctoPrint-PSUControl/issues/68 (old) bug, I guess that OctoPrint-Emc2101 is somehow providing an additional temparature, which PSU control is waiting for, but somehow fails in interpreting stuff from Emc2101. Enclosure temperature reported from EMC2101 is around 23°C, so way below the 50°C specified for PSU Control.
Version of OctoPrint-PSUControl
Operating System running OctoPrint
Printer model & used firmware incl. version
Prusa i3 MK3S+ Firmware 3.11.0
Link to octoprint.log with octoprnt.plugins.psucontrol set to DEBUG
Not entierly sure how to interpret this, but I maybe important: