Release 1.10.3 seems to cause comms errors?

Get Help
1

What is the problem?

Upgraded to 10.3.1, printer connection lost when starting mesh probing, 10.2.1 no problems. Solved it for now, by manually setting the temperature high enough to end up at the correct temp when the printer wants to start printing.
If no one else reports issues, consider it a fluke and I'll look into it later. For now I needed to get a print finished.

What did you already try to solve it?

Reboot/restarted the lot

Have you tried running in safe mode?

no

Did running in safe mode solve the problem?

unknown

Systeminfo Bundle

octoprint-systeminfo-20241114140700.zip (100.0 KB)

WRITE HERE

Trident 350 system has been without errors. During Bedmesh you see that the Temps are not longer reported in the Temp window (dashes only) . Manually changing the temps does not show any reaction. After probing is complete, the following error is reported: (the 180/60 were pushed manually) I needed 200C for the Hotend.

Recv: // Mesh Bed Leveling Complete
Recv: // Bed Mesh state has been saved to profile [default]
Recv: // for the current session. The SAVE_CONFIG command will
Recv: // update the printer config file and restart the printer.
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N4 M10535
Recv: ok
Send: N5 M10534
Recv: ok B:59.9 /60.0 T0:180.1 /180.0
Recv: ok B:59.9 /60.0 T0:180.1 /180.0
Recv: ok B:59.9 /60.0 T0:180.1 /180.0
Recv: ok B:59.9 /60.0 T0:180.1 /180.0
Send: N6 M104 S20196
Recv: ok
Send: N7 M104 S20096
Recv: ok
Send: N8 G92 E079
Recv: ok
Send: N9 G92 E078
Recv: ok
Send: N10 G1 F1800 E-0.75*34
Recv: // Extrude below minimum temp
Recv: // See the 'min_extrude_temp' config option for details
Recv: !! Extrude below minimum temp
Changing monitoring state from "Printing" to "Cancelling"

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Ubuntu, and OctoPrint 1.10.3 Python 3.9.2 OctoPi* 1.0.0 (build 2023.10.09.151442
Browser independant, same issue with IPAD/Safari.

2

this is not a comm error, this is a printer error that OctoPrint is responding to. Based on the communication I'm seeing, this appears to be a klipper install. It also appears you didn't attempt the print while running in safe mode, so it could also be a plugin acting up with the newer version. I recommend reattempting the upgrade, running in safe mode, with serial log enabled and see where that gets you.

1 Like
3

If this error persists, you should consult the Klipper forum:

I assume an error in the START_PRINT parameters.

4

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