You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever this plugin is enabled, Octoprint sets the E0 temp to 400 then to 260, ignoring the gcode parameters. Lucky overheating prevention in the firmware stops before something bad happens.
I've tried safe mode and it doesn't happen there. Then I disabled every plugin and enabled one at a time, and FilamentManager specifically triggers this issue.
Steps to reproduce
Load any gcode.
Print.
Expected behavior
Temperature is not heater-melting high.
Did the same happen when all other 3rd party plugins are disabled?
Yep.
Additional context
This happened to me before, and I always fixed it by reconnection to the printer. Disconnecting and connecting to the printer always fixed this, but now it doesn't.
OctoPrint 1.7.0
Python 3.7.3
OctoPi 0.17.0
Ender 3
SKR Mini E3 V1.2
Marlin 2.0.7.2
Other plugins installed:
ABL Expert Plugin (0.6)
Arc-Welder (1.0.0+u.bb71e8f)
Autoscroll (0.0.3)
BLTouch Plugin (0.3.4)
Bed Visualizer (1.1.0)
BetterHeaterTimeout (1.3.0)
Camera Settings (0.3.0)
Cancel Objects (0.4.6)
Cost Estimation (3.3.0)
DisplayProgress (0.1.3)
Dragon Order (0.1.7)
DryRun Plugin (1.2.0)
Filament Manager (1.9.0)
Firmware Updater (1.12.0)
Floating Navbar (0.3.7)
GcodeEditor (0.2.12)
Navbar Temperature Plugin (0.14)
Preheat Button (0.8.0)
PrettyGCode (1.2.4)
PrintTimeGenius Plugin (2.2.8)
PrinterAlerts (0.7.5)
Resource Monitor (0.3.5)
Telegram Notifications (1.6.5)
Terminal Messaging (0.1.0)
Themeify (1.2.2)
TouchUI (0.3.18)
Tuya Smartplug (0.3.0)
WiFi Status (1.7.2)
Z Probe Offset (0.5)
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever this plugin is enabled, Octoprint sets the E0 temp to 400 then to 260, ignoring the gcode parameters. Lucky overheating prevention in the firmware stops before something bad happens.
I've tried safe mode and it doesn't happen there. Then I disabled every plugin and enabled one at a time, and FilamentManager specifically triggers this issue.
Steps to reproduce
Expected behavior
Temperature is not heater-melting high.
Did the same happen when all other 3rd party plugins are disabled?
Yep.
Log file
octoprint.log
Screenshots


Additional context
This happened to me before, and I always fixed it by reconnection to the printer. Disconnecting and connecting to the printer always fixed this, but now it doesn't.
Other plugins installed:
The text was updated successfully, but these errors were encountered: