Terminal buffer fills up causing the print to stop

What is the problem?

If I turn off autoscroll to look at something in the terminal, it will keep going until full.
Then the printer just stops. I can't resume the print because it wasn't paused properly, but that's more of a klipper issue.

How can I prevent a terminal buffer overflow from accidentally ruining a print?

System info

octoprint-systeminfo-20220927190937.zip (289.6 KB)

Octoprint 1.8.3, Octopi 0.18.0, python 3.7.3, Octoklipper with Raspberry Pi 4B, modded Prusa MK3S+

Hello @Amplifryer !

But why?
There are better ways to investigate a fault.

The cause of the cancelled print was a cold hotend:

2022-09-27 18:52:29,521 - octoprint.util.comm - WARNING - Received an error from the printer's firmware: Extrude below minimum temp
| Last lines in terminal:
| Send: N21613 G1 X181.425 Y88.137 E.01532*110
| Recv: ok
| Send: N21614 G1 F649.243*110
| Recv: ok
| Send: N21615 G1 X181.331 Y88.359 E.01453*102
| Recv: ok
| Send: N21616 G1 F640.995*101
| Recv: ok
| Send: N21617 G1 X181.22 Y88.452 E.00879*92
| Recv: ok
| Send: N21618 G1 F677.05*95
| Recv: ok
| Send: N21619 G1 X181.109 Y88.546 E.00824*102
| Recv: ok
| Send: N21620 G1 F720*124
| Recv: ok
| Send: N21621 G1 X180.998 Y88.64 E.00772*85
| Recv: // Extrude below minimum temp
| Recv: // See the 'min_extrude_temp' config option for details
| Recv: !! Extrude below minimum temp

It's hard to tell, what this caused - but the extruder was switched off.
And I assume not by a (whatever) buffer overflow.

Curious if the printer is powered off and @Amplifryer thinks it's on because of backpowering from the Pi? That could cause something like that to happen.

1 Like

Did not know this is also a thing with Klipper.

I had autoscroll turned off because occasionally I'll need to read some recent lines in the terminal.
Normally I would turn it on again, but I forgot and so the buffer filled up.
Just seems like a silly way to scrap a print to me. I figured maybe there was a setting that could prevent this from happening.

Where did you find those last lines? I only got to N1399 before it stopped. I didn't export that system info until after I restarted everything and already had another print going.

Edit: scratch that, reviewing the gcode and octoprint log, looks like those were the final lines. Maybe they just didn't show in the terminal because it filled up a while before I even noticed the printer stopped.
I've never seen the hotend cool down unexpectedly, so I'll look into that some more.

I will try to replicate the problem after my print finishes to confirm.

Autoscroll in the terminal is a front-end UI-only feature. It doesn't have any impact on the gcode sent with the OctoPrint server, in the same way that you can close the tab and it carries on printing. It has no impact outside allowing you to look at what was sent without it scrolling down.



Today my terminal got stuck on a line. This happened:


The print is not effected by this.
and: Also on Klipper.

I think you have to escape / commands a special way in M117 messages IIRC. Not sure how klipper handles those.

You mean concerning the -/- characters?

yeah, but I see that was after the buffer was cut off, so probably unrelated.

1 Like

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