Long filename cause checksum mismatch and M112 error

[felinh]

Hi, First of all , thank you for this nice and valuable plugin.

Plugin version is "Detailed Progress (0.2.7)"/ OctoPrint: 1.6.1 Marlin 2.0.8.2 (Jul 12 2021 20:14:29)/ Baud Rate 115200 Creality/CR-10S/BigTreeTech SKR 1.4 Turbo TMC2209"

It appears that when Gcode file with long string are loaded: error appears randomly / almost systematically like below (checksum mismatch followed by M112 HALT ERROR).

I presume it is because the file name is long to display and cause error. This does not happen with short names. Is there a way to shorten filename with compatible lenght? Thank you

2021-10-17 17:00:52,042 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 669, current line = 670
| Last lines in terminal:
| Recv: ok N668 P0 B3
| Send: N669 M117 part_TypeElement_Id_129_Enjoliveur_Pile_(contre_moule)_pla_flex_Thermo_LEGRAND.gcode*21
| Recv: Error:checksum mismatch, Last Line: 668
| Recv: Resend: 669
| Recv: ok
| Send: N669 M117 part_TypeElement_Id_129_Enjoliveur_Pile_(contre_moule)_pla_flex_Thermo_LEGRAND.gcode*21
| Recv: Error:checksum mismatch, Last Line: 668
| Recv: Resend: 669
| Recv: ok
| Send: N669 M117 part_TypeElement_Id_129_Enjoliveur_Pile_(contre_moule)_pla_flex_Thermo_LEGRAND.gcode*21
| Recv: Error:checksum mismatch, Last Line: 668
| Recv: Resend: 669
| Recv: ok
| Send: N669 M117 part_TypeElement_Id_129_Enjoliveur_Pile_(contre_moule)_pla_flex_Thermo_LEGRAND.gcode*21
| Recv: Error:checksum mismatch, Last Line: 668
| Recv: Resend: 669
| Recv: ok
| Send: N669 M117 part_TypeElement_Id_129_Enjoliveur_Pile_(contre_moule)_pla_flex_Thermo_LEGRAND.gcode*21
| Recv: Error:checksum mismatch, Last Line: 668
| Recv: Resend: 669
2021-10-17 17:00:52,079 - octoprint.util.comm - WARNING - Printer keeps requesting line 669 again and again, communication stuck
2021-10-17 17:00:52,080 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Error"
2021-10-17 17:00:52,090 - octoprint.util.comm - INFO - Force-sending M112 to the printer

[OllisGit]

Hi @felinh,

this issue tracker is for the Plugin "DisplayLayerProgress" and not for "Detailed Progress" ;-)

But DLP has the same issue...or maybe the issue of the printers firmware: Each Firmware has a different message-limit which is send to the Printer via M117-command. That is also the reason why I added in my plugin-settings this "disclaimer":

Maybe I can improve the behavior, if I cut too long messages or cut and replace the last chars with ...

[stale[bot]]

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.