1. Got a question or need help troubleshooting? Post to the troubleshooting forum or Search the forums!

Printing Error:No Line Number with checksum

Discussion in 'Troubleshooting' started by Francesco, Jan 20, 2014.

Thread Status:
Not open for further replies.
  1. Francesco

    Francesco New Member

    Joined:
    Feb 21, 2013
    Messages:
    9
    Likes Received:
    0
    Hi Guys,
    On the last days I had an issue with my extruder, I found the problem, order the PTFE part and fixed it. In the meanwhile I was waiting the part I got a really stupid idea and I checked how to flash the firmware, I downloaded the one on the forum, followed the instructions and flashed it, after that the printer was responding at the commands as usual, so, everything looked fine.
    I tried to use again my Robo 3D with the extruder fixed and I got an issue that never happened before, during the printing i got different error messages like below:
    15:48:44.429 : echo:pID settings:
    15:48:44.429 : echo: M301 P22.20 I1.08 D114.00
    15:48:47.767 : echo:SD init fail
    15:48:47.768 : echo:Unknown command: ""
    15:48:47.843 : FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for gen6 FIRMWARE_URL:http://www.mendel-parts.com PROTOCOL_VERSION:1.0 MACHINE_TYPE:RoBo 3D EXTRUDER_COUNT:1
    15:48:48.104 : FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for gen6 FIRMWARE_URL:http://www.mendel-parts.com PROTOCOL_VERSION:1.0 MACHINE_TYPE:RoBo 3D EXTRUDER_COUNT:1
    15:53:39.855 : echo:Active Extruder: 0
    15:54:03.536 : Printing layer 1 of 303
    15:54:03.570 : Printing layer 2 of 303
    15:58:57.881 : Error:No Line Number with checksum, Last Line: 276
    15:58:59.497 : Error:Line Number is not Last Line Number+1, Last Line: 276
    15:58:59.497 : Resend: 277
    I looked at the command panel and the problem in the gcode is like this:
    15:58:47.258 : N275 M105 *7
    15:58:57.631 : N276 M105 *4
    15:58:57.871 : N277 G1 X194.07 Y167.96 E180.3226 *120
    15:58:57.881 : Error:No Line Number with checksum, Last Line: 276
    15:58:59.490 : N278 M105 *10
    15:58:59.497 : Error:Line Number is not Last Line Number+1, Last Line: 276
    15:58:59.497 : Resend: 277
    15:58:59.509 : Resend: N277 G1 X194.07 Y167.96 E180.3226 *120
    15:58:59.511 : Resend: N278 M105 *10
    After the error message the printer continued to work, but I stopped because in the previously print I got 4 times a similar error message and at one point the printer stopped. After the stop I can use the controls of the printer and everything looks fine.
    What can it be ? Problem in the gcode ? Firmware?
    I also tried to switch the usb cable but the problem remain, so, I don't think it's a communication issue.
    Please, if anybody has suggestion for solving it let me know.
    Frenky
     
  2. Mike Kelly

    Mike Kelly Volunteer

    Joined:
    Mar 11, 2013
    Messages:
    6,967
    Likes Received:
    2,276
    You got the error but it didn't kill the print? I think that's a pretty generic message that's mostly an internal check. If the print keeps working I wouldn't worry about it.


    I believe that's a communication error though, you'd need to google the error message a bit I think.
     
  3. Francesco

    Francesco New Member

    Joined:
    Feb 21, 2013
    Messages:
    9
    Likes Received:
    0
    I got the error and I stopped the printer, during the previously prints, after few errors, the printer stopped itself.
    So, I'm worrying just because I would like to have the printer working as before, I need to print models for my architectural thesis ...
    For what I understood the problem can be related to the communication then, with google I didn't find so much.
    What are the possible solutions for fixing it ?
     
  4. Mike Kelly

    Mike Kelly Volunteer

    Joined:
    Mar 11, 2013
    Messages:
    6,967
    Likes Received:
    2,276
    Reinstall driver, reinstall repetier, use a different usb port, use a different usb cable, don't use an extension cord on your usb cable, don't use a hub.

    Barring those you could try reflashing your arduino but that's less likely to fix it since i don't think it's on the board.
     
Thread Status:
Not open for further replies.

Share This Page