[BUG] (bug summary) M75 {{ event.name }} - causes an error, kill printer error M112

[Roboct424]

Did you test with a precompiled firmware?

Yes, and the problem still exists.

Bug Description

I've been using this firmware for a very long time, and just the other day I discovered that there is a recommended starting Gcode for octoprint. When I applied it, i.e. inserted: M75 {{ event.name }}, everything was fine. The next day, I sliced a model in Prusa slicer, uploaded it to octoprint, clicked on print, and the printer screen displayed the error M112, indicating that the printer had been killed. I'll tell you right away, Settings > Printer > Behaviour item: What to do on a firmware error - I've completely rearranged it, tried what's recommended in the repository, but it doesn't work. It gives me an error: Recv: Error:No Checksum with line number, Last Line: 0. I've found a solution by disabling the startup script in octoprint. Can you tell me why this is happening? Thank you

Bug Timeline

A couple of days ago, when I used the starter Gcode octoprint from the firmware repository.

Expected behavior

The printer will start printing quietly.

Actual behavior

Sometimes the octoprint simply disconnects from the printer, and sometimes the printer displays an M112 error.

Steps to Reproduce

1. The starting Gcode octoprint must have the command: M75 {{ event.name }}
2. Upload and run the attached Gcode file converted to txt in the octoprint:
   4_models_m3_3_segmenr_detail_CLASIC_KIT_IDEAL_RELEASE_2h58m_0,20mm_200C_PETG_ENDER3S1.txt

Version of Professional Firmware

I'll add it later.

Printer model

Creality Ender 3 S1

Electronics

I don't remember, but it's the most common one.

LCD/Controller

No response

Other add-ons

No response

Bed Leveling

UBL Bilinear mesh

Your Slicer

Prusa Slicer

Host Software

OctoPrint

Additional information & file uploads

No response

[mriscoc]

Check the Octoprint console to know the cause of the M112 command.

[Roboct424]

M112 is caused by a message from the printer: Recv: Error:No Checksum with line number, Last Line: 0
I tried to enable the option to ignore printer errors and to prevent octoprint from sending M112

[mriscoc]

I was unable of reproduce the issue in my installation so maybe this bug was fixed by another change in the current sources.

[grantd1987]

This looks awfully familiar to this Reddit thread from 3 year ago: https://www.reddit.com/r/Ender3v2Firmware/s/b5dv8CSXgw

In short, your event name is too long. I did notice that the truncate part appears to have stopped working at some point, just means the OctoPrint file name isn't being send in the M75 and it is blank and I haven't revisited the issue as it still prevents long file names from causes the M112 fault:

M75 {{ event.name | truncate:85:... }}