Line Number is not Last Line Number

HiI have a problem
What means this errors:

Error:checksum mismatch, Last Line: 2
Error:Line Number is not Last Line Number+1, Last Line: 2
Error:No Line Number with checksum, Last Line: 2
error: line number is not last line number+1, last line: 12
error: no line number with checksum, last line:12

Waiting for reply


  • It is a communication error.

    checksum mismatch => The given checksum could not be verified.
    Error:No Line Number with checksum => If we send a checksum we need also a line number. So the command got split on transfer in 2 halfes as it seems. One with line number and no checksum and the othe rhalf.
    Host fixes these error automatically. I expect there is a Resend somewhere near the messages.
  • Hi, I have a similar problem.

    Using: windows 10 pro, Repetier Host 2.0.1 with CuraEngine

    For a long time I didn't have any problems with printing even over 10 hours long prints, but for some reason in the last days I can't leave the print unattended. Every now and then this error occurs:

    12:03:36.019 : Printing layer 27 of 96
    12:04:33.791 : Error:checksum mismatch, Last Line: 14166
    12:04:33.791 : Resend: 14167
    12:04:33.807 : Error:Line Number is not Last Line Number+1, Last Line: 14166
    12:04:33.807 : Resend: 14167
    12:04:41.608 : Error:Line Number is not Last Line Number+1, Last Line: 14170
    12:04:41.608 : Resend: 14171
    12:04:47.733 : Error:Line Number is not Last Line Number+1, Last Line: 14175
    12:04:47.733 : Resend: 14176

    and so on. If I pause/continue the print the error goes away, but returns after a while.
    In some cases it even stops the print for no visible reason.

    any help would be appreciated.

  • You need to enable logging and check errors in that log. This error in general happens if communication errors happen. But question is here what was send in line 14166? How did all the problem started.

    One known thing is that sending M117 for ETA/Layer through host causes problems with some old firmwares. You then need to disable sending this in host printer config.  But that would be an error happening already at the beginning.

    Other question is did you change something? New usb cable, firmware update, new position of printer?
  • As far as I see I have checked logging and errors and this is all I get to see.

    Firmware wasn't updated for a long time, same USB cable, same printer settings.
    I got a new PLA filament, different colour, from the same manufacturer as before.
    I had to change the nozzle, thermistor and nozzle throat because they were worn out and thermistor broke.
  • The log is a file written in work directory (repetier.log). What you see at the bottom is a filtered subset of the last 2000 lines of communication.

    BTW: Does the error fix it self? I mean host resends the line in question and  the problem should be fixed. That is why we use line numbers and checksums to detect com errors.
  • Oh, ok. Next time I'll check the work directory, thanks.

    Well up until a few days ago, that error has appeared every now and then, but there were no issues. Last print I did,the error started and then the print just simply froze and I had to to emergency stop.
Sign In or Register to comment.