› ›

Multiple errors in console "checksum mismatch"

belloclabellocla
in Questions & Answers
Good evening, i'm printing a model (17h  :'( ) and in the console i'm looking some errors like this:
-------------------------------------------
Recv:15:24:05.126: ok
Send:15:24:05.126: N52016 G1 F3000 X88.53 Y77.524 E763.04558
Recv:15:24:05.131: Error:checksum mismatch, Last Line: 52012
Recv:15:24:05.131: Resend: 52013
Recv:15:24:05.133: Ignore due to resend: ok
Recv:15:24:05.137: Ignore due to resend: Error:Line Number is not Last Line Number+1, Last Line: 52012
Recv:15:24:05.140: Ignore due to resend: Resend: 52013
Recv:15:24:05.140: Ignore due to resend: ok
Recv:15:24:05.163: Waiting for resend requests finished. Starting resends ...
Send:15:24:05.163: Resend: N52013 G0 F7200 X131.179 Y142.67
Recv:15:24:05.351: ok
Send:15:24:05.351: Resend: N52014 G1 F3000 X88.817 Y142.67 E761.66296
Recv:15:24:05.464: ok
Send:15:24:05.464: Resend: N52015 G0 F7200 X88.53 Y142.477
Recv:15:24:05.689: ok
Send:15:24:05.689: Resend: N52016 G1 F3000 X88.53 Y77.524 E763.04558
Send:15:24:05.689: N52017 G1 F4800 E762.24558
--------------------------------------------
I've used the "wizard" of repetier server to set communication baud etc....
...what does it mean? 
any suggest is appreciate!
(Printer Creality Ender 3 S-1 model sliced with Creality Slicer)

Comments

  • RepetierRepetier
    Just communication errors that got detected and fixed. Can happen from time to time which is why checksums are used. So if it is not constantly appearing that is nothing to worry about. Only if it is frequent and buffer is greater 127 try reducing it to 127 and see if it improves. As ultimate test enable ping-pong then you are at lowest rate possible since no overflows can happen. So what remains is from real communication errors.
  • belloclabellocla
    I don't know why but now th print is blocked....here console messages:
    Recv:17:10:50.127: T:194.96 /195.00 B:60.02 /60.00 @:255 B@:24 FAN0@:255 FAN1@:255
    Recv:17:10:51.128: T:194.91 /195.00 B:59.99 /60.00 @:255 B@:26 FAN0@:255 FAN1@:255
    Recv:17:10:51.618: echo:busy: paused for user
    Recv:17:10:52.127: T:195.00 /195.00 B:60.01 /60.00 @:255 B@:25 FAN0@:255 FAN1@:255
    Recv:17:10:53.127: T:194.93 /195.00 B:60.02 /60.00 @:255 B@:24 FAN0@:255 FAN1@:255
    Recv:17:10:53.618: echo:busy: paused for user
    ....
    don't know why :(
  • RepetierRepetier
    Recv:17:10:51.618: echo:busy: paused for user

    Means printer is waiting that you do something on the printer display and blocks communication until you do. E.g. select filament spool on prusa can trigger this. Without seeing the commands send and knowing the printer hard to guess.
  • belloclabellocla
    Repetier said:
    Just communication errors that got detected and fixed. Can happen from time to time which is why checksums are used. So if it is not constantly appearing that is nothing to worry about. Only if it is frequent and buffer is greater 127 try reducing it to 127 and see if it improves. As ultimate test enable ping-pong then you are at lowest rate possible since no overflows can happen. So what remains is from real communication errors.
    Thank you...i've changed the connection settings and i've enabled "PING-PONG" mod...now it's all right.

    Repetier said:
    Recv:17:10:51.618: echo:busy: paused for user

    Means printer is waiting that you do something on the printer display and blocks communication until you do. E.g. select filament spool on prusa can trigger this. Without seeing the commands send and knowing the printer hard to guess.
    Don't know why...there wasn't messages on the printer...probably a fault GCODE.



Sign In or Register to comment.