CR6-SE Community firmware Release 6 & Octoprint m112 ERROR

What is the problem?

WRITE HERE: (i'm new to this so bear with me please). I'm running the latest revision of the community firmware on my CR-6 the firmware works great and had no issues until I started with Octoprint. Machine heats up and homes, goes to the front left corner prints a (purge?) line from front left to rear left and then starts rear left to front left corner gets about half way stops, beeps and comes up with M112 error and machine has to be reset. Error message on the laptop shows that it keeps trying to send Line 29 but in the log shows there's a checksum issue. No idea on how to resolve this

What did you already try to solve it?

Tried searching this forum, tried another file, printed same file directly from SD card a no issues so I know the file is good. Re-done ABL. Z axis when it stops jumps from 0.28mm to 2mm yet doesn't do this when running the machine standalone so believe it to be Octoprint issue and not hardware/firmware issue.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36
connectivity.connection_check: 8.8.8.8:53
connectivity.connection_ok: True
connectivity.enabled: True
connectivity.online: True
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: True
env.hardware.cores: 4
env.hardware.freq: 1800.0
env.hardware.ram: 1909063680
env.os.bits: 32
env.os.id: linux
env.os.platform: linux
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.5
env.plugins.pi_support.octopi_version: 1.0.0
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 21.3.1
env.python.version: 3.9.2
env.python.virtualenv: True
octoprint.safe_mode: False
octoprint.version: 1.7.2
systeminfo.generator: zipapi

Additional information about your setup

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36
connectivity.connection_check: 8.8.8.8:53
connectivity.connection_ok: True
connectivity.enabled: True
connectivity.online: True
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: True
env.hardware.cores: 4
env.hardware.freq: 1800.0
env.hardware.ram: 1909063680
env.os.bits: 32
env.os.id: linux
env.os.platform: linux
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.5
env.plugins.pi_support.octopi_version: 1.0.0
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 21.3.1
env.python.version: 3.9.2
env.python.virtualenv: True
octoprint.safe_mode: False
octoprint.version: 1.7.2
systeminfo.generator: zipapi

haproxy.log (622.9 KB)
octoprint.log (731.9 KB)
(upload://g215TjTCqzDxVcQSl16jyB6QtaN.log) (182.9 KB)
serial.log (76.7 KB)
webcamd.log (176.7 KB)

Hello @Dav-Tec !

The error is here:

2022-01-18 16:35:49,645 - Printer keeps requesting line 29 again and again, communication stuck
2022-01-18 16:35:49,646 - Changing monitoring state from "Printing" to "Error"
2022-01-18 16:35:49,651 - Send: M112

Caused by this:

2022-01-18 16:35:49,625 - Send: N29 M117 Printing CCR6SE Push-in_V-slot_covers_-_BackLeft eSUN PETG lw 0.4mm lh 0.2mm if 20.0% ext1 245.0C bed 80.0C - Layer 1 of 21*69
2022-01-18 16:35:49,644 - Recv: Error:No Checksum with line number, Last Line: 28
2022-01-18 16:35:49,645 - Recv: Resend: 29

That text for M117 is waaaaay toooo long and the firmware can't handle it.

P.S.: Please, next time send the bundle (systeminfo bundle) and not just the system info. All the logfiles are included and zipped. So less traffic.

so it's literally just the title it to long? sorry about files first time posting

Yes, there is a limit on the line length sent to the printer. It is configurable in the firmware, but usually for RAM related reasons it can't be ridiculously long. Something in your setup is trying to send this massive line to the firmware, maybe a plugin, or some gcode script.

Found it! some plugin in cura causing massive filenames, stopped it now and working spot on thanks!

1 Like

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