Comms error Printer keeps requesting line 70923 again and again, communication stuck

Get Help
1

[

Communication error

There was a communication error while talking to your printer. Please consult the terminal output and octoprint.log for details. Error: Printer keeps requesting line 70923 again and again, communication stuck

State: Offline after error
Printer keeps requesting line 70923 again and again, communication stuck

---Recv: echo:busy: processing
Recv: T:199.20 /0.00 B:58.89 /0.00 @:0 B@:0
Recv: ok
Changing monitoring state from "Printing" to "Finishing"
Send: N70921 M117 0% L=224/22498
Recv: ok
Send: N70922 M40041
Recv: ok
Send: {if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+2, max_print_height)} F600
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}17
Recv: echo:Unknown command: "{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+2, max_print_height)} F600"
Recv: ok
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Send: N70924 M117 100% L=224/224102
Recv: ok
Send: N70924 M117 100% L=224/224*102
Recv: Error:Line Number is not Last Line Number+1, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}17
Recv: Error:Line Number is not Last Line Number+1, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70924 M117 100% L=224/224102
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}17
Recv: Error:No Line Number with checksum, Last Line: 70922
Send: N70924 M117 100% L=224/224102
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}*17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}*17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}*17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}*17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Recv: ok
Send: N70923 G1 X5 Y{print_bed_max[1]0.85} F{travel_speed60}17
Recv: Error:checksum mismatch, Last Line: 70922
Recv: Resend: 70923
Printer keeps requesting line 70923 again and again, communication stuck
Changing monitoring state from "Finishing" to "Error"
Send: M112
Send: N70925 M11240
Send: N70926 M104 T0 S043
Send: N70927 M140 S0110
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor
Closing down send loop

2

Instead of supplying the information requested in the template, you deleted it. This makes it hard for us to help as we don't have the information we need.

From what you did post, it looks like the gcode you are sending to the printer contains lines which are not gcode and are not recognized by your firmware. I suspect your slicer isn't configured correctly.

2 Likes
3

Hi Brad
Thanks for your responce
Oops apologies new to this type of communication
Maybe I should not be using Prusa 2.7.0
your thoughts
Cheers
Oliver

4

Oliver,

Until you are more forthcoming with details about your environment, my thoughts are irrelevant.

What slicer you choose to use is often influenced by what printer you have.

I strongly suggest that you click on the blue text in the blue shaded area just above the window you type a reply in (they are links). Take some time to read them and then follow their suggestions.

5

You may have a look at this line:

The should be a numeric value and not this:: {travel_speed*60}

Seems there are wrong settings in the slicer gcode scripts (wrong arithmetic).
Maybe adding spaces?

1 Like
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.