checksum mismatch
Second time this happens, I'm running 3.0.1RC and Octoprint.
Never happened with 3.0.12.
The printer just stops moving, standing still. Below error found in Octoprint Log.
Recv: Error:checksum mismatch, Last Line: 10117 | Recv: Resend: 10118
I can see in Octoprint that the complete GCODE is there.
Printing the GCODE again and it finish just fine.
i'm puzzled.
---
Gert
Re: checksum mismatch
I had this before when I tried to run the serial interface (theoretically possible) at above 115200 baud.
Seems that either the printer firmware is returning an incorrect request or the Pi is not capable of receiving properly at the selected baud rate.
More of the logs would be helpful (a few lines either side of the error). There's also a command you can add to the Pi config script to make serial comms "more stable", but it didn't work for me.
Peter
EDIT: One other thought (this was a firmware fault I reported over 6 months ago...) OctoPi settings/Serial Connection/Advanced Options/Simulate an additional OK for resend requests - make sure you have ticked the box.
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: checksum mismatch
I always had my com settings fixed at 115200. It was a long time since i rebooted the PI so i have done that now.
Lets see what happens.
---
Gert
Re: checksum mismatch
Gert - did you see my edit?
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: checksum mismatch
Forgott this one:
Send: N10119 G1 X116.409 Y135.017 E0.0149*92 | Recv: Error:checksum mismatch, Last Line: 10117 | Recv: Resend: 10118
Thats all just before and after.
---
Gert
Re: checksum mismatch
Gert - did you see my edit?
Got it, thanks. Pushed in now.
---
Gert
Re: checksum mismatch
Thinking about it, I am pretty sure it's the firmware fault causing this problem (workaround in Octi as above).
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: checksum mismatch
Hi,
the Prusa firmware 3.1.0-RC1 is a beta and one new fix is BUSY/NOT BUSY messages for Octoprint/Astroprint/ESP3D and so on.
Saw that Pavel Sindler made some related fixes in the last few days:
https://github.com/prusa3d/Prusa-Firmware/pull/230
https://github.com/prusa3d/Prusa-Firmware/pull/233
Re: checksum mismatch
It was last March when I had this issue; Gina replied:
Your printer requests a resend here, but never "clears" OctoPrint for sending, causing the timeout and the following issues - the ok after the resend request is missing. That's a bug in the printer's firmware.
OctoPrint has a setting to get around this firmware bug, try checking "Simulate an additional ok for resend requests" under "Settings" > "Serial Connection" > "Advanced options". Save and reconnect to your printer, see if that helps and please report back.
This was reported to Pavel at the time (as of 11 May - last time I asked - it was not fixed)..
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…