Print aborted with error message from Marlin "Error:No Checksum with line number" #490
Comments
|
I just pushed a commit making sure commands are always sent with checksum during printing (as discussed on the mailinglist), how ever on further look I think the issue might rather be caused by both the resend request and the ok that follows it being interpreted as a go ahead by OctoPrint to send the next command, whereas the printer is not of that opinion. As a workaround until that bloody new comm layer is finally done (it's getting close, had my first successful prints with it on monday, pretty consistent :)) I introduced the "swallow ok after resend" option under Settings > Features -- do you have that enabled? |
|
For reference: 3ee745d <- always sends checksum while printing |
|
I don't have access via the web interface at the moment, but I didn't see anything in my config.yaml that would indicate the "swallow ok after resend" has been changed from whatever its default value is. |
|
If it was different from the current default it would have to look something like this: So if you really don't have it set to false and the default applies, you should have that enabled. Now that's odd. Do you have a bit more above the first quoted lines from the terminal log by chance? |
|
from my config.yaml: Sorry,. I don't have any more of the terminal log. |
|
Please test if that still occurs with current |
foosel
added
needs information
|
I'm getting similar looking errors with current git master, with 'swallow first OK after resend' enabled: |
|
@thaytan I took the liberty to format your log to make it more readable. That looks like a valid communication problem to me. The "No Line Number with checksum" implicates that your printer did not receive the |
|
Switching to a different USB port and moving the USB cable seems to work better indeed. |
|
Closing since assuming this is now fixed by the extensive changes in the comm layer (no feedback, no choice) |
|
I'm not the opener of this issue but i had the same problem. After updating this was solved for me. Thanks. |
|
I'm getting a similar lockup. Here is my log: Recv: ok I've been developing a plugin, and I thought it might be causing problems, but I uninstalled it, rebooted and got the same issue at a different point during my print. Any ideas? |
|
Original Prusa? See #2285 and prusa3d/Prusa-Firmware#331. In any case a firmware issue (your firmware is missing an ok after the resend request). Workaround for that firmware bug is available and described in both of the tickets linked above. |
|
You are 100% correct. I investigated the logs and see the same problem you have discovered. I'm SO glad it's not my plugin (or your wonderful print server). Also, thank you for being so responsive! |
|
The workaround does not seem to work in my case (octoprint 1.3.6. on octopi 0.14, Prusa i3 MK2s, FW: 2.13) |
|
@hoegge, slice without the 'Linear Advance' profile and turn the workaround you were using off. I've had the most success that way myself. Not sure if it's necessary, but I also changed the Filament Settings->Custom G-Code to: M900 K0 |
|
@FormerLurker not sure why one would consider changing the "Linear Advance" on the slicing on this issue. That does not make much sense to me at all. |
|
Odd isn't it. It seems as though linear advances taxes the CPU and causes serial issues on the mk2 and mk3 using the latest firmware. See: prusa3d/Prusa-Firmware#331 |
I'm running:
pi@m2 ~/OctoPrint $ git log
commit 244128c
Merge: 9c9b98d 7bba1dc
Author: Gina Häußge osd@foosel.net
Date: Sun May 25 20:19:03 2014 +0200
I was in the middle of printing something and the print suddenly stopped for no apparent reason. I use a Raspberry Pi running Octoprint to control the printer, but it's not obvious whether it's the gcode, Octoprint, or firmware to blame. Here's the log.
Send: N6429 G1 X41.025 Y245.824 E3.5575_85
Recv: ok
Send: M105
Recv: ok
Send: N6430 G1 X41.857 Y246.406 E3.6066_91
Recv: ok
Send: N6431 G1 X53.331 Y234.932 E4.3909_95
Recv: Error:No Checksum with line number, Last Line:6428
Recv: Resend:6429
Send: N6429 G1 X41.025 Y245.824 E3.5575_85
Recv: ok
Recv: Error:Line Number is not Last Line Number+1, Last Line:6428
Recv: Resend:6429
Send: N6429 G1 X41.025 Y245.824 E3.5575_85
Recv: ok
Recv: ok
Send: N6430 G1 X41.857 Y246.406 E3.6066_91
Recv: Error:Line Number is not Last Line Number+1, Last Line:6429
Recv: Resend:6430
Send: N6430 G1 X41.857 Y246.406 E3.6066_91
Recv: ok
Recv: ok
Send: N6431 G1 X53.331 Y234.932 E4.3909_95
Recv: Error:Line Number is not Last Line Number+1, Last Line:6430
Recv: Resend:6431
Send: N6431 G1 X53.331 Y234.932 E4.3909*95
Recv: ok
Recv: ok
Send: M105
Recv: Error:Line Number is not Last Line Number+1, Last Line:6431
Recv: Resend:6432
Changing monitoring state from 'Printing' to 'Error: Printer requested li...'
Recv: ok
The text was updated successfully, but these errors were encountered: