Octoprint Not Displaying "Actual Bed Temp"

[peregrin5]

I’m noticing that with Octoprint the “actual bed temp” is always displaying as zero.

Looking at the GCODE temp reports I think I see the bed temp, but maybe there is some formatting thing that is preventing it from showing?

Recv: T0:26.50 /0.00 B0:25.69 /0.00 B1:23.50 /0.00 M:29.09 /0.00 T0:26.50 /0.00 T1:27.00 /0.00 @:0 B0@:0 B1@:0 @0:0 @1:0 @B_ZONE: CENTER

I think it’s working as when I start the print the bed temp goes up the bed temp I specify, it’s just not showing in Octoprint.

Here is where I put the bed temp to 70:

“Recv: T0:240.50 /240.00 B0:70.00 /70.00 B1:33.10 /0.00 M:42.71 /0.00 T0:240.50 /240.00 T1:37.50 /0.00 @:127 B0@:0 B1@:0 @0:127 @1:0 @B_ZONE: CENTER”

Any tips?

[xchrisd]

I think it’s because of the possibility to heat the bed area-wise.

The inner area of the bed seems to be B0 and the outer area is B1.

Unfortunately I can’t find the setting for this right now.
It should be possible with the plug in “top temp”, this is customizable and you can see a graph as well.

[peregrin5]

Thanks! I’ll test that out!

[peregrin5]

So Top Temp can work. You need to create special reg ex’s to show the temp, but it doesn’t affect the temperature graph. This plugin does the trick of fixing the temperature graph with minimal configuration: OctoPrint-PlotlyTempGraph

[ochsi]

Hi all,

I know that this threat is quiet old, but I just got me a Snapmaker Artisan and encountered the same problems like bed temp not recognized, filament runout not detected or loosing Z position when pausing.

So I developed a plugin for Octoprint named Proxy4Artisan, which solves this problems. Regarding the bed temp, it at least enables Octoprint to interpret B0 (center) as the bed temp and shows this in the temp graph.

Installable via Octoprint‘s Plugin Manager Just search in the Repo

If anyone is interested…

Happy printing

[peregrin5]

Thanks I’ll test this out. But I don’t know how it can handle filament runout without a sensor for such feeding back into the Raspberry Pi.

[ochsi]

Thank you for testing. The artisan, with its dual extruder, actually has runout sensors. It‘s just that octoprint does not recognize when they got triggered. The plugin just looks for the trigger message in the communication and pauses the print. Furthermore the plugin makes sure, that octoprint can correctly populate the pause_position variable (don’t forget to activate logging position in octoprints settings), so you can safely use it in your pause and resume scripts.