tjjfvi / octoprint-betterheatertimeout Goto Github PK

Getting spammed with "heater time out" While doing a UBL bed mesh, I can't find an option to tell it to ignore when long commands are running. Its not turning my heater off (thankfully, as i do a 100 point UBL mesh and it takes 30 minutes) bit its just rapid firing and very angry trying to time out my heaters during a UBL.

its a non stop stream of angry.

When printer is in paused state, I'd like the bed to stay heated to preserve adhesion.
I found out when The Spaghetti Detective plugin paused a print overnight and I came back to a cold bed.
So an option to not timeout as long as printer is in a paused state would be ideal. Thanks!

Please add Python 3 Compatibility as outlined here.

Please add Python 3 Compatibility as outlined here.

This plugin fails the Python 3 compatibility check performed by this plugin:
https://github.com/jneilliii/OctoPrint-Python3PluginCompatibilityCheck

Have you considered adding the ability to turn off the fan as well after the heaters are shut off? My fans are always blazing away and seemed like a logical choice to build it into this plugin.

Would it be possible to implement individual timeouts per heater? I'd like to put a shorter timeout for the extruder to avoid filament degradation but a longer one for the bed so I can use it to preheat the enclosure and just use the timeout as a failsafe in case I forget turning it off.

Right now, the only two options are to start the timeout either when the heating starts, or when the target temperature is changed. Would it be possible to add an option to start the timeout when all temperatures reached their target?

Please add Python 3 Compatibility as outlined here.

I have a Prusa MK3S with the Multi-Material Unit (2S). The MMU2S requires that multiple extruders/"tools" be set up in the OctoPrint interface, under Printer Profiles. Only one "tool" (i.e: filament) is used at a time, and "shared nozzle" is selected.

I discovered an issue where I'd paused a print with OctoPrint, and then this script kicked in, killing the temperature after 600 seconds and saying the "tool timed out" on the display. This also interrupted the GCode and effectively trashed the print, causing the printer to home itself in the middle of the bed. (It wasn't too important, don't worry.)

I haven't investigated it yet but my educated guess is that it thinks that the other four tools aren't "in use" and kills the print based on their statuses.

In summary:

1. OctoPrint set up with multiple extruders/"tools" for multimaterial printing, handled via the Slicer's GCode.
2. Job is paused for a time over the limit of the timeout (600s by default).
3. BetterHeaterTimeout doesn't accurately detect that the print is paused, and kills the print.

Theory:

1. BHT can't handle multiple "tools" and decides that because the other "tools" aren't in use, it kills the print.

Please add Python 3 Compatibility as outlined here.

Please add Python 3 Compatibility as outlined here.

I don't have proof because I couldn't find my log, it wasn't in the normal place, but I suspect this plugin of crashing my octoprint service installation, it's the only thing I have changed in many days and I woke up this morning to the server on with the service not running. I have removed the plugin for now and if it doesn't happen again I think this must be the culprit.

Hi, I see there are a couple of requests about timeout. I was tempted to add mine to one of those but I can't seem to find a good fit. If this is covered bu one of those, then please close this.

I find that when I've almost finish in CAD, I go to OP and hit preheat. But then, as always I underestimate how long it'll take before slicer ready and Preheat times out. I understand that I can change the timeout but I can't find a period that suits all cases. Would it be possible to add the option of custom GCode on timeout (so I can do something to get my attention).

Thanks in advance, George

Thanks for the app! :)

I usually want to start a new print project soon after one is finished but I am usually right there so I don't need a long timeout. So setting different intervals for different events would be useful: successful print, printer error, aborts, a manual preheat from the printer's controls (maybe I'm just measuring/calibrating), etc.

Alternatively, maybe it can scan gcode or other terminal commands so I can send it a new 'temporary' timeout value. It could also scan the preset on the printer so that I can maybe preheat the bed to 1, 2, 3, etc. which I could specify as 10min, 20min, 30min, etc.

Thanks again

Steps to reproduce

Pre-heat from Octopi, then start a print from the printer's SD card using the printer's display (tested on Ender 3).

Expected behaviour

Tool and Bed should stay on during print.

Actual behaviour

Tool and Bed shut off mid-print with message "Tool0 timed out" on display.

Would it be possible to add an option to disable the heater shutoff thus leaving timeout handling purely to the GCode scripts?

I would like to turn the bed down to 40C instead of off to preserve bed adhesion of any print I potentially leave on. I may find with a different material that I just don't want to change bed temp on a timeout.

I sometimes disable this if I'm doing some tuning or messing with the hotend but I'm forgetful and forget to re-enable it. Would it be possible to add a "Disable for XXX Time" so that the timeout re-enable's itself after a period of time?