Communication Error

Ewald_Ikemann · February 14, 2020, 1:33pm

This start and end g-codes, you have them in the slicer or in OctoPrint?
The codes seem to belong to the slicer because the slicer has to fill in the values for the placeholders in brackets: [something] and do the if cases.

When there are no values for the temperatures, the printer assume 0 (zero) for them and a cold printer does not print.

Zoombeee · February 14, 2020, 1:50pm

Those are code for slicer I am wondering if anything could go wrong there. Can u help me to take a look

jneilliii · February 14, 2020, 8:03pm

Upload your output gcode file so we can take a look at how those placeholders are getting interpreted by Slic3r. Please also verify if you are using Prusa Slic3r, the regular Slic3r application, or some other "slicer" application like Cura, Ideamaker, Simplify3D, etc. There are lots of slicers and they all have different feature sets.

Zoombeee · February 15, 2020, 2:02am

Sorry where can I get the output gcode... I am using prusa slicer

Zoombeee · February 25, 2020, 3:51pm

can anyone help me here please

jneilliii · February 25, 2020, 4:17pm

Open your prusa slicer, add a stl file to the build area, slice, export the file to gcode and upload here.

Zoombeee · February 25, 2020, 4:36pm

Tyre Hugger_PET0.12mm.gcode (3.5 MB)

there you go.. hopefully that can help

i paste the gcode scripts in OctoPrint as well
before print job starts

M140 S[bed0_temperature] T0 ; Start heating bed
M190 S[bed0_temperature] T0 ; Heat bed and wait for temperature to stabilize
M104 S[extruder0_temperature] T0 ; Start heating right extruder
M109 S[extruder0_temperature] T0 ; Heat right extruder and wait for temp to stabilize
G28 XYZ
G1 Z0.25
G92 E0
G1 X100 E10 F600
M201 X1000 Y1000

Zoombeee · February 25, 2020, 4:40pm

also my serial.log

2020-02-25 16:38:52,103 - Connecting to: /dev/ttyUSB0
2020-02-25 16:38:52,178 - Changing monitoring state from "Offline" to "Opening serial port"
2020-02-25 16:38:52,180 - Connected to: Serial<id=0xa900e930, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2020-02-25 16:38:52,183 - Changing monitoring state from "Opening serial port" to "Connecting"
2020-02-25 16:38:52,191 - Send: N0 M110*35
2020-02-25 16:38:52,193 - Send: N0 M110*35
2020-02-25 16:38:52,209 - Recv: ok N:0
2020-02-25 16:38:52,215 - Changing monitoring state from "Connecting" to "Operational"
2020-02-25 16:38:52,225 - Send: N0 M110*35
2020-02-25 16:38:52,230 - Recv: ok N:0
2020-02-25 16:38:52,237 - Recv: ok N:0
2020-02-25 16:38:52,237 - Send: N1 M115*39
2020-02-25 16:38:52,257 - Send: N2 M21*18
2020-02-25 16:38:52,261 - Recv: ok CBD make it.Date:Aug 29 2019 Time:11:00:30
2020-02-25 16:38:52,274 - Recv: ok N:2
2020-02-25 16:38:54,643 - Changing monitoring state from "Operational" to "Starting"
2020-02-25 16:38:54,689 - Send: N3 M140 S[bed0_temperature] T0*116
2020-02-25 16:38:54,702 - Send: N0 M110*35
2020-02-25 16:38:54,708 - Recv: //sd cmd error cnt:124 len:35 :N3 M140 S[bed0_temperature] T0*116
2020-02-25 16:38:54,710 - Recv: 
2020-02-25 16:38:54,712 - Recv: ok
2020-02-25 16:38:54,720 - Recv: ok N:0
2020-02-25 16:38:54,720 - Send: N1 M190 S[bed0_temperature] T0*123
2020-02-25 16:38:54,723 - Send: N2 M104 S[extruder0_temperature] T0*11
2020-02-25 16:38:54,738 - Recv: //sd cmd error cnt:125 len:74 :N1 M190 S[bed0_temperature] T0*123
2020-02-25 16:38:54,749 - Recv: N2 M104 S[extruder0_temperature] T0*11
2020-02-25 16:38:54,755 - Recv: 
2020-02-25 16:38:54,759 - Recv: ok
2020-02-25 16:38:54,765 - Send: N3 M109 S[extruder0_temperature] T0*7
2020-02-25 16:38:54,780 - Recv: //sd cmd error cnt:126 len:38 :N3 M109 S[extruder0_temperature] T0*7
2020-02-25 16:38:54,783 - Recv: 
2020-02-25 16:39:09,781 - Recv: ok
2020-02-25 16:39:09,794 - Send: N4 G28 XYZ*108
2020-02-25 16:39:09,807 - Recv: //sd cmd error cnt:127 len:15 :N4 G28 XYZ*108
2020-02-25 16:39:09,809 - Recv:

jneilliii · February 25, 2020, 5:37pm

That's the problem. Remove that from OctoPrint GCODE scripts section, your gcode is fine.

Zoombeee · February 26, 2020, 12:04am

i removed that gcode from before print job starts

the printer did try to heat up the bed and extruder for about 1 sec then disconnected with the below msg

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 16 again and again, communication stuck

OutsourcedGuru · February 26, 2020, 1:58am

Shall we consult our crystal ball so that it will tell us what line 16 is?

Zoombeee · February 26, 2020, 1:59am

I accidentally deleted octoprint.log now and it doesn't exist now... Can advice me how to get it back before I can paste the log here. Sorry for trouble

OutsourcedGuru · February 26, 2020, 2:55am

Run the job again...?

Zoombeee · February 26, 2020, 3:03am

Ya I did but somehow the octoprint.log file not created again... Anyway I can create the file manually

foosel · February 26, 2020, 8:02am

Open OctoPrint's settings. Navigate to "Serial Connection" > "General". Make sure "Log communication to serial.log" is checked.

Connect to your printer. Reproduce your problem. Share serial.log (can be found in the Settings under "Logging").

Do not just blindly delete logs, ever. They get deleted automatically. Read precisely what people tell you here. Remember that we cannot see what your printer is doing and we need information from you in order to tell you what's going wrong.

Zoombeee · February 26, 2020, 8:13am

thanks how about the OctoPrint.log if it was accidentally deleted how do i get it or create the file back again.

this is in my serial.log

2020-02-25 16:38:52,103 - Connecting to: /dev/ttyUSB0
2020-02-25 16:38:52,178 - Changing monitoring state from "Offline" to "Opening serial port"
2020-02-25 16:38:52,180 - Connected to: Serial<id=0xa900e930, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2020-02-25 16:38:52,183 - Changing monitoring state from "Opening serial port" to "Connecting"
2020-02-25 16:38:52,191 - Send: N0 M110*35
2020-02-25 16:38:52,193 - Send: N0 M110*35
2020-02-25 16:38:52,209 - Recv: ok N:0
2020-02-25 16:38:52,215 - Changing monitoring state from "Connecting" to "Operational"
2020-02-25 16:38:52,225 - Send: N0 M110*35
2020-02-25 16:38:52,230 - Recv: ok N:0
2020-02-25 16:38:52,237 - Recv: ok N:0
2020-02-25 16:38:52,237 - Send: N1 M115*39
2020-02-25 16:38:52,257 - Send: N2 M21*18
2020-02-25 16:38:52,261 - Recv: ok CBD make it.Date:Aug 29 2019 Time:11:00:30
2020-02-25 16:38:52,274 - Recv: ok N:2
2020-02-25 16:38:54,643 - Changing monitoring state from "Operational" to "Starting"
2020-02-25 16:38:54,689 - Send: N3 M140 S[bed0_temperature] T0*116
2020-02-25 16:38:54,702 - Send: N0 M110*35
2020-02-25 16:38:54,708 - Recv: //sd cmd error cnt:124 len:35 :N3 M140 S[bed0_temperature] T0*116
2020-02-25 16:38:54,710 - Recv: 
2020-02-25 16:38:54,712 - Recv: ok
2020-02-25 16:38:54,720 - Recv: ok N:0
2020-02-25 16:38:54,720 - Send: N1 M190 S[bed0_temperature] T0*123
2020-02-25 16:38:54,723 - Send: N2 M104 S[extruder0_temperature] T0*11
2020-02-25 16:38:54,738 - Recv: //sd cmd error cnt:125 len:74 :N1 M190 S[bed0_temperature] T0*123
2020-02-25 16:38:54,749 - Recv: N2 M104 S[extruder0_temperature] T0*11
2020-02-25 16:38:54,755 - Recv: 
2020-02-25 16:38:54,759 - Recv: ok
2020-02-25 16:38:54,765 - Send: N3 M109 S[extruder0_temperature] T0*7
2020-02-25 16:38:54,780 - Recv: //sd cmd error cnt:126 len:38 :N3 M109 S[extruder0_temperature] T0*7
2020-02-25 16:38:54,783 - Recv: 
2020-02-25 16:39:09,781 - Recv: ok
2020-02-25 16:39:09,794 - Send: N4 G28 XYZ*108
2020-02-25 16:39:09,807 - Recv: //sd cmd error cnt:127 len:15 :N4 G28 XYZ*108
2020-02-25 16:39:09,809 - Recv:

foosel · February 26, 2020, 8:25am

You still have placeholders that aren't being replaced in your GCODE. E.g.

M190 S[bed0_temperature] T0

It won't work like this. This [bed0_temperature] stuff needs to be a value BEFORE it gets sent to the printer. OctoPrint doesn't know what to do with this stuff. Make sure your GCODE scripts in OctoPrint don't contain any of that stuff... best just reset them to the defaults for now and keep your hands off of them until you've gotten a better grasp of GCODE:

So, only "After print job is cancelled" should be configured out-of-the-box, with these contents:

; disable motors
M84

;disable all heaters
{% snippet 'disable_hotends' %}
{% snippet 'disable_bed' %}
;disable fan
M106 S0

(note that the placeholders in there are different from your slicer stuff and in OctoPrint's own format, they won't work in your slicer, your slicer's placeholders won't work in OctoPrint, there's no standard there)

Everything else just leave empty, you don't need it, your slicer takes care of that stuff for you.

Your slicer needs to replace these placeholders for you, which from the looks of the GCODE file you provided it actually is doing just fine, so just get rid of the broken stuff you configured in the GCODE scripts, don't forget to save and reconnect to your printer and that should hopefully do it.

Once something gets written to it it will get created on its own, you should never have to mess with it at all in any way. Just "recreating it" would also not really help a whole ton, given that we require the contents of this file to help you, so if you just create an empty one that wouldn't be really helpful now, would it?

Zoombeee · February 26, 2020, 11:40am

Yes now all my gcodes are empty except for the "after print job is cancelled" box which has the same value as you mentioned.

i still get this error

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 16 again and again, communication stuck

the OctoPrint.log as below

2020-02-26 11:36:18,044 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2020-02-26 11:36:18,053 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Left_Arm_PET0.2mm.gcode, owner: jansenchua, user: jansenchua
2020-02-26 11:36:18,067 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2020-02-26 11:36:18,086 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-02-26 11:36:18,279 - octoprint.plugins.excluderegion - INFO - File selected, resetting internal state
2020-02-26 11:36:18,388 - octoprint.plugins.excluderegion - INFO - Printing started
2020-02-26 11:36:18,691 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 16, current line = 19
| Last lines in terminal:
| Send: N10 M205 X10 Y10 Z0.3 E5.0*13
| Recv: ok N:9
| Send: N11 M205 S0 T0*19
| Recv: ok N:10
| Recv: ok N:11
| Send: N12 M300 S2500 P100*38
| Send: N13 M104 S220*87
| Recv: ok N:12
| Recv: ok N:13
| Send: N14 M140 S85*109
| Recv: ok N:14
| Send: N15 G1 Z20*100
| Send: N16 G28 X Y*37
| Recv: ok N:15
| Send: N17 M84*41
| Recv: //sd cmd error cnt:9 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Recv: Resend:16
| Send: N18 M190 S85*108
2020-02-26 11:36:18,697 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,706 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 16, current line = 19
| Last lines in terminal:
| Send: N12 M300 S2500 P100*38
| Send: N13 M104 S220*87
| Recv: ok N:12
| Recv: ok N:13
| Send: N14 M140 S85*109
| Recv: ok N:14
| Send: N15 G1 Z20*100
| Send: N16 G28 X Y*37
| Recv: ok N:15
| Send: N17 M84*41
| Recv: //sd cmd error cnt:9 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Recv: Resend:16
| Send: N18 M190 S85*108
| Recv: //last:15 curr:17 rcv:N17 M84*41
| Recv: 
| Recv: //callback_pf error
| Recv: Resend:16
| Send: N16 G28 X Y*37
2020-02-26 11:36:18,712 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,731 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 16, current line = 19
| Last lines in terminal:
| Recv: 
| Recv: ok
| Recv: Resend:16
| Send: N18 M190 S85*108
| Recv: //last:15 curr:17 rcv:N17 M84*41
| Recv: 
| Recv: //callback_pf error
| Recv: Resend:16
| Send: N16 G28 X Y*37
| Recv: //last:15 curr:18 rcv:N18 M190 S85*108
| Send: N16 G28 X Y*37
| Recv: 
| Recv: //callback_pf error
| Recv: //sd cmd error cnt:10 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Send: N17 M84*41
| Recv: //sd cmd error cnt:11 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: Resend:16
2020-02-26 11:36:18,736 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,769 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 16, current line = 19
| Last lines in terminal:
| Recv: //last:15 curr:18 rcv:N18 M190 S85*108
| Send: N16 G28 X Y*37
| Recv: 
| Recv: //callback_pf error
| Recv: //sd cmd error cnt:10 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Send: N17 M84*41
| Recv: //sd cmd error cnt:11 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: Resend:16
| Recv: //last:15 curr:17 rcv:N17 M84*41
| Recv: 
| Recv: //callback_pf error
| Send: N16 G28 X Y*37
| Recv: //sd cmd error cnt:12 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Send: N17 M84*41
| Recv: Resend:16
2020-02-26 11:36:18,774 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,805 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 16, current line = 19
| Last lines in terminal:
| Recv: 
| Recv: Resend:16
| Recv: //last:15 curr:17 rcv:N17 M84*41
| Recv: 
| Recv: //callback_pf error
| Send: N16 G28 X Y*37
| Recv: //sd cmd error cnt:12 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Send: N17 M84*41
| Recv: Resend:16
| Recv: //last:15 curr:17 rcv:N17 M84*41
| Send: N16 G28 X Y*37
| Recv: 
| Recv: //callback_pf error
| Recv: //sd cmd error cnt:13 len:15 :N16 G28 X Y*37
| Recv: 
| Recv: ok
| Send: N17 M84*41
| Recv: Resend:16
2020-02-26 11:36:18,808 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,832 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,859 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,892 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,934 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,961 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...
2020-02-26 11:36:18,984 - octoprint.util.comm - WARNING - Printer keeps requesting line 16 again and again, communication stuck
2020-02-26 11:36:18,985 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Error: Printer keeps requesting line 16 again and again, communication stuck"
2020-02-26 11:36:18,993 - octoprint.util.comm - INFO - Force-sending M112 to the printer
2020-02-26 11:36:19,003 - octoprint.plugins.excluderegion - INFO - Printing stopped: event=Error
2020-02-26 11:36:19,015 - octoprint.util.comm - INFO - Changing monitoring state from "Error: Printer keeps requesting line 16 again and again, communication stuck" to "Offline (Error: Printer keeps requesting line 16 again and again, communication stuck)"
2020-02-26 11:36:19,063 - octoprint.plugins.excluderegion - INFO - Printing stopped: event=PrintFailed
2020-02-26 11:36:19,531 - octoprint.util.comm - INFO - Firmware didn't send an 'ok' with their resend request. That's a known bug with some firmware variants out there. Simulating an ok to continue...

and the serial.log

2020-02-26 11:36:18,044 - Changing monitoring state from "Operational" to "Starting"
2020-02-26 11:36:18,065 - Changing monitoring state from "Starting" to "Printing"
2020-02-26 11:36:18,091 - Send: N0 M110*35
2020-02-26 11:36:18,093 - Send: N1 M201 X9000 Y9000 Z500 E10000*59
2020-02-26 11:36:18,097 - Recv: ok N:0
2020-02-26 11:36:18,105 - Recv: ok N:1
2020-02-26 11:36:18,108 - Send: N2 M203 X500 Y500 Z12 E120*14
2020-02-26 11:36:18,114 - Send: N3 M204 P1500 R1500 T1500*84
2020-02-26 11:36:18,117 - Recv: ok N:2
2020-02-26 11:36:18,122 - Recv: ok N:3
2020-02-26 11:36:18,123 - Send: N4 M205 X10.00 Y10.00 Z0.20 E2.50*59
2020-02-26 11:36:18,135 - Send: N5 M205 S0 T0*38
2020-02-26 11:36:18,137 - Recv: ok N:4
2020-02-26 11:36:18,142 - Send: N6 M107*35
2020-02-26 11:36:18,143 - Recv: ok N:5
2020-02-26 11:36:18,149 - Send: N7 M201 X500 Y500 Z100 E5000*13
2020-02-26 11:36:18,149 - Recv: ok N:6
2020-02-26 11:36:18,154 - Send: N8 M203 X500 Y500 Z5 E25*6
2020-02-26 11:36:18,157 - Recv: ok N:7
2020-02-26 11:36:18,160 - Send: N9 M204 S500 T500*43
2020-02-26 11:36:18,161 - Recv: ok N:8
2020-02-26 11:36:18,167 - Send: N10 M205 X10 Y10 Z0.3 E5.0*13
2020-02-26 11:36:18,168 - Recv: ok N:9
2020-02-26 11:36:18,174 - Send: N11 M205 S0 T0*19
2020-02-26 11:36:18,176 - Recv: ok N:10
2020-02-26 11:36:18,181 - Recv: ok N:11
2020-02-26 11:36:18,183 - Send: N12 M300 S2500 P100*38
2020-02-26 11:36:18,187 - Send: N13 M104 S220*87
2020-02-26 11:36:18,193 - Recv: ok N:12
2020-02-26 11:36:18,197 - Recv: ok N:13
2020-02-26 11:36:18,199 - Send: N14 M140 S85*109
2020-02-26 11:36:18,205 - Recv: ok N:14
2020-02-26 11:36:18,216 - Send: N15 G1 Z20*100
2020-02-26 11:36:18,220 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,676 - Recv: ok N:15
2020-02-26 11:36:18,680 - Send: N17 M84*41
2020-02-26 11:36:18,681 - Recv: //sd cmd error cnt:9 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,684 - Recv: 
2020-02-26 11:36:18,686 - Recv: ok
2020-02-26 11:36:18,689 - Recv: Resend:16
2020-02-26 11:36:18,693 - Send: N18 M190 S85*108
2020-02-26 11:36:18,695 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,700 - Recv: 
2020-02-26 11:36:18,703 - Recv: //callback_pf error
2020-02-26 11:36:18,705 - Recv: Resend:16
2020-02-26 11:36:18,705 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,709 - Recv: //last:15 curr:18 rcv:N18 M190 S85*108
2020-02-26 11:36:18,714 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,714 - Recv: 
2020-02-26 11:36:18,716 - Recv: //callback_pf error
2020-02-26 11:36:18,718 - Recv: //sd cmd error cnt:10 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,719 - Recv: 
2020-02-26 11:36:18,721 - Recv: ok
2020-02-26 11:36:18,722 - Send: N17 M84*41
2020-02-26 11:36:18,723 - Recv: //sd cmd error cnt:11 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,725 - Recv: 
2020-02-26 11:36:18,728 - Recv: Resend:16
2020-02-26 11:36:18,734 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,738 - Recv: 
2020-02-26 11:36:18,741 - Recv: //callback_pf error
2020-02-26 11:36:18,742 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,754 - Recv: //sd cmd error cnt:12 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,755 - Recv: 
2020-02-26 11:36:18,756 - Recv: ok
2020-02-26 11:36:18,758 - Send: N17 M84*41
2020-02-26 11:36:18,764 - Recv: Resend:16
2020-02-26 11:36:18,772 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,775 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,776 - Recv: 
2020-02-26 11:36:18,784 - Recv: //callback_pf error
2020-02-26 11:36:18,792 - Recv: //sd cmd error cnt:13 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,794 - Recv: 
2020-02-26 11:36:18,796 - Recv: ok
2020-02-26 11:36:18,797 - Send: N17 M84*41
2020-02-26 11:36:18,804 - Recv: Resend:16
2020-02-26 11:36:18,807 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,809 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,811 - Recv: 
2020-02-26 11:36:18,812 - Recv: //callback_pf error
2020-02-26 11:36:18,817 - Recv: //sd cmd error cnt:14 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,819 - Recv: 
2020-02-26 11:36:18,820 - Recv: ok
2020-02-26 11:36:18,821 - Send: N17 M84*41
2020-02-26 11:36:18,828 - Recv: Resend:16
2020-02-26 11:36:18,831 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,834 - Recv: 
2020-02-26 11:36:18,834 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,836 - Recv: //callback_pf error
2020-02-26 11:36:18,844 - Recv: //sd cmd error cnt:15 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,845 - Recv: 
2020-02-26 11:36:18,846 - Recv: ok
2020-02-26 11:36:18,847 - Send: N17 M84*41
2020-02-26 11:36:18,854 - Recv: Resend:16
2020-02-26 11:36:18,858 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,860 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,862 - Recv: 
2020-02-26 11:36:18,863 - Recv: //callback_pf error
2020-02-26 11:36:18,870 - Recv: //sd cmd error cnt:16 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,871 - Recv: 
2020-02-26 11:36:18,872 - Recv: ok
2020-02-26 11:36:18,873 - Send: N17 M84*41
2020-02-26 11:36:18,889 - Recv: Resend:16
2020-02-26 11:36:18,891 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,892 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,900 - Recv: 
2020-02-26 11:36:18,902 - Recv: //callback_pf error
2020-02-26 11:36:18,903 - Recv: //sd cmd error cnt:17 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,904 - Recv: 
2020-02-26 11:36:18,905 - Recv: ok
2020-02-26 11:36:18,907 - Send: N17 M84*41
2020-02-26 11:36:18,912 - Recv: Resend:16
2020-02-26 11:36:18,930 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,933 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,935 - Recv: 
2020-02-26 11:36:18,937 - Recv: //callback_pf error
2020-02-26 11:36:18,942 - Recv: //sd cmd error cnt:18 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,944 - Recv: 
2020-02-26 11:36:18,945 - Recv: ok
2020-02-26 11:36:18,948 - Send: N17 M84*41
2020-02-26 11:36:18,954 - Recv: Resend:16
2020-02-26 11:36:18,958 - Recv: //last:15 curr:17 rcv:N17 M84*41
2020-02-26 11:36:18,961 - Send: N16 G28 X Y*37
2020-02-26 11:36:18,964 - Recv: 
2020-02-26 11:36:18,969 - Recv: //callback_pf error
2020-02-26 11:36:18,972 - Recv: //sd cmd error cnt:19 len:15 :N16 G28 X Y*37
2020-02-26 11:36:18,973 - Recv: 
2020-02-26 11:36:18,974 - Recv: ok
2020-02-26 11:36:18,976 - Send: N17 M84*41
2020-02-26 11:36:18,982 - Recv: Resend:16
2020-02-26 11:36:18,984 - Printer keeps requesting line 16 again and again, communication stuck
2020-02-26 11:36:18,985 - Changing monitoring state from "Printing" to "Error: Printer keeps requesting line 16 again and again, communication stuck"
2020-02-26 11:36:18,996 - Send: M112
2020-02-26 11:36:18,999 - Send: N19 M112*25
2020-02-26 11:36:19,002 - Send: N20 M104 T0 S0*19
2020-02-26 11:36:19,005 - Send: N21 M140 S0*86
2020-02-26 11:36:19,014 - Changing monitoring state from "Error: Printer keeps requesting line 16 again and again, communication stuck" to "Offline (Error: Printer keeps requesting line 16 again and again, communication stuck)"
2020-02-26 11:36:19,032 - Connection closed, closing down monitor
2020-02-26 11:36:19,531 - Closing down send loop

foosel · February 26, 2020, 11:48am

You still haven't changed G28 X Y to G28 X0 Y0 like I told you a couple of times in the very first replies to this thread almost two weeks ago.

Open your slicer's start GCODE configuration. Look for the line that says

G28 X Y; Home XY

Turn it into a line that says

G28 X0 Y0; Home XY

Save. Reslice your files. Try with the new ones.

Also scream at your printer's vendor that they are selling a product with broken firmware.

Zoombeee · February 26, 2020, 12:07pm

omg you are a genius its finally working