Temperature settings are sporadically set incorrectly

Hello together,

I have been using Octoprint for a few weeks. On the whole, it works great.

A small problem I have from time to time, obviously a sporadic error possibly a bug. Maybe someone else has observed this problem and knows a solution or Maybe you have to report it to the developers.

What is the problem?

When I start a print, sometimes it happens that the printer starts, but the nozzle temperature is set to 0 and the heating bed to 150°C. If I don't notice it right away, the printer stops extruding after a few minutes because the nozzle is too cold. If I start the same GCODE again, everything works fine. This does not happen all the time, but only every 5-10 prints. I have attached the system info bundle.

What did you already try to solve it?

I do not really have an idea

Have you tried running in safe mode?

No, I just read here that there must be... what restrictions does this create? I would have to use the first some time and observe whether this sporadic error is then gone.

Did running in safe mode solve the problem?

I do not know

Systeminfo Bundle

octoprint-systeminfo-20230402113632.zip (218.7 KB)

Additional information about your setup

OctoPrint version : 1.8.7; OctoPi version : 0.18.0; RaspberryPi 4 16Gbyte; Linux raspberrypi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l; Ender3 S1 Pro; Print start via Cura plugin

Thank you very much, everyone who takes care of this.

Greetings Stefenzo

Safe mode (click the blue text for additional information and instructions) runs just the core OctoPrint. It does not load any of the user installed plugins. If a plugin is causing your issue, then safe mode will help verify that.

A quick look at your bundle shows lots of plugin errors. I'm afraid I don't know how to fix the errors but I'm sure someone more knowledgeable than myself will respond.

1 Like

@b-morgan is right, you should for sure try running things without a few of the plugins you have. Safe mode would be a good way to ensure that there are no plugins causing issues. At a minimum, I would turn off the ones you see erroring and start there.

The Plugins I see throwing exceptions are:

Also looks like there is an issue with how your system handles shutdown/reboots commands.
This is in your log.

octoprint.server.api.system - WARNING - Command for core:reboot failed with return code -15:

Additionally, since the issue you are having relates to sending commands to the Printer, it would be good to turn on serial logging so we can see what is going to your printer when you have the issue.

serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log

First of all, thanks for the tips.

Currently I am somewhat limited in what I can try, as a larger print is running.

subsequently I will first


uninstall, because I don't really need these PlugIns. Note to myself, things that turn out to be useless for me, directly remove again....

The Telegram plugin, on the other hand, I would miss painfully, it is extremely convenient to be informed without effort in the running print, on the road.

Serial log I have now activated, with there namely occurs to me, it could well be a bug in the firmware of the Ender3 in the interpretation of the serial received GCode. One would be able to recognize that in the serial log surely. So, whether here at all a command for these temperatures was sent. Because apart from that, according to my understanding, the Ender should not accept a command for 150°C bed temperature at all, its limit is at 110°C.

I myself have a hard time to read the logs, I would not have found the problematic plugins... Can you see more about the reboot problem? Since I can somehow nothing at all with start.

Thanks for the support, I'll get back to you as soon as I know something new.

Greetings Stefenzo

Edit, just tested in running print, 150°C bed temperature the printer accepts without grumbling...

The log just shows what I sent. Its only in there once. What I would say is that if you ask Octoprint to reboot your device, make sure it does it. If it does not and you think it has, you are now in an unknown state. Many plugins require at least a restart of OctoPrint. If you are not using a Rpi or you are not using the default user setups, you may have a permissions issue. I did a very quick look for the return code but did not see anything specific around that. You code do a better splunk than I did and likely at least come up with the definition for return code 15.

1 Like

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