Communication timeout with prusaslicer

DJVibezzz · April 26, 2021, 7:55am

What is the problem?

If I start my print it only "primes" the nozzle and then disconnects when sliced with prusaslicer. If I slice using cura it works fine.

What did you already try to solve it?

Changed some settings in prusaslicer.
Tried exporting directly from prusaslicer and tried it with just uploading.

Have you tried running in safe mode?

No

Did running in safe mode solve the problem?

Complete Logs

octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)

Serial.log:

2021-04-24 19:20:44,598 - Changing monitoring state from "Operational" to "Starting"
2021-04-24 19:20:44,698 - Send: N0 M110 N0*125
2021-04-24 19:20:44,717 - Recv: ok
2021-04-24 19:20:44,719 - Changing monitoring state from "Starting" to "Printing"
2021-04-24 19:20:44,723 - Send: N1 M107*36
2021-04-24 19:20:44,729 - Recv: ok 1
2021-04-24 19:20:44,731 - Send: N2 M117 Initializing*43
2021-04-24 19:20:44,745 - Recv: ok 2
2021-04-24 19:20:44,751 - Send: N3 M83*27
2021-04-24 19:20:44,769 - Recv: ok 3
2021-04-24 19:20:44,770 - Send: N4 M107*33
2021-04-24 19:20:44,774 - Recv: ok 4
2021-04-24 19:20:44,775 - Send: N5 G28*22
2021-04-24 19:20:44,782 - Recv: ok 5
2021-04-24 19:20:44,783 - Recv: busy:processing
2021-04-24 19:20:44,783 - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-04-24 19:20:44,784 - Send: N6 M140 S80*91
2021-04-24 19:20:45,842 - Recv: SelectExtruder:0
2021-04-24 19:20:45,849 - Recv: FlowMultiply:100
2021-04-24 19:20:45,851 - Recv: X:0.00 Y:0.00 Z:217.175 E:40.0000
2021-04-24 19:20:45,852 - Recv: ok 6
2021-04-24 19:20:45,855 - Send: N7 M113 S2*102
2021-04-24 19:20:45,862 - Recv: ok 7
2021-04-24 19:20:45,864 - Send: N8 M105*47
2021-04-24 19:20:45,866 - Recv: Unknown command:N7 M113  S2
2021-04-24 19:20:45,870 - Recv: ok 8
2021-04-24 19:20:45,872 - Send: N9 M190 S80*89
2021-04-24 19:20:45,875 - Recv: T:239.74 /240 B:80.00 /80 B@:0 @:175
2021-04-24 19:20:45,877 - Recv: ok 9
2021-04-24 19:20:45,879 - Send: N10 M104 S240*82
2021-04-24 19:20:45,902 - Recv: ok 10
2021-04-24 19:20:45,904 - Recv: TargetExtr0:240
2021-04-24 19:20:45,907 - Send: N11 M109 S240*94
2021-04-24 19:20:45,914 - Recv: ok 11
2021-04-24 19:20:45,917 - Send: N12 G92 E0*116
2021-04-24 19:20:45,917 - Recv: TargetExtr0:240
2021-04-24 19:20:45,923 - Recv: ok 12
2021-04-24 19:20:45,925 - Send: N13 G1 X-98 Y0 Z0.2 F4000*51
2021-04-24 19:20:45,931 - Recv: ok 13
2021-04-24 19:20:45,933 - Send: N14 G3 X0 Y-98 I98 Z0.2 E40 F400*15
2021-04-24 19:20:46,967 - Recv: ok 14
2021-04-24 19:20:46,970 - Send: N15 G0 Z1*86
2021-04-24 19:20:49,974 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-04-24 19:20:49,980 - Send: N16 M105*16
2021-04-24 19:20:52,979 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-04-24 19:20:52,984 - Send: N17 M105*17
2021-04-24 19:20:55,983 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-04-24 19:20:55,989 - Send: N18 M105*30
2021-04-24 19:20:58,988 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-04-24 19:20:58,993 - Send: N19 M105*31
2021-04-24 19:21:01,993 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-04-24 19:21:01,998 - Send: N20 M105*21
2021-04-24 19:21:04,997 - No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2021-04-24 19:21:05,062 - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2021-04-24 19:21:05,070 - Connection closed, closing down monitor

Octoprint.log:

2021-04-24 19:20:44,481 - octoprint.filemanager.analysis - INFO - Starting analysis of local:shifter_unit_top_PETG_50m.gcode
2021-04-24 19:20:44,482 - octoprint.filemanager.analysis - INFO - Invoking analysis command: /home/pi/oprint/bin/python3 -m octoprint analysis gcode --speed-x=6000 --speed-y=6000 --max-t=10 --throttle=0.0 --throttle-lines=100 /home/pi/.octoprint/uploads/shifter_unit_top_PETG_50m.gcode
2021-04-24 19:20:44,549 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: shifter_unit_top_PETG_50m.gcode, owner: _api, user: _api
2021-04-24 19:20:44,598 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2021-04-24 19:20:44,642 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: shifter_unit_top_PETG_50m.gcode, owner: _api, user: _api
2021-04-24 19:20:44,697 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-04-24 19:20:44,719 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-04-24 19:20:44,783 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-04-24 19:20:44,910 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {'origin': 'local', 'file': '3ce033a2b182a1213ee2793ae58a179d9d31d500'}
2021-04-24 19:20:45,857 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-04-24 19:20:49,974 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-04-24 19:20:52,979 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-04-24 19:20:55,982 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-04-24 19:20:58,987 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-04-24 19:21:01,992 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-04-24 19:21:04,997 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2021-04-24 19:21:05,062 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Octoprint version 1.5.3
OctoPi version 0.18.0
Raspberry Pi 4B 2GB
FLSun Q5 (MKS 2.5)
Google Chrome
Windows 10
Prusaslicer
Standard PETG profile on prusaslicer

Ewald_Ikemann · April 26, 2021, 8:42am

Hello @DJVibezzz !

Maybe G3/G4 is not or bad implied into the printers firmware.

Just after sending

2021-04-24 19:20:45,933 - Send: N14 G3 X0 Y-98 I98 Z0.2 E40 F400*15

communication stalls.

DJVibezzz · April 26, 2021, 8:55am

G3 creates an arc and it stops after the arc.

Ewald_Ikemann · April 26, 2021, 9:15am

So, when the arc is printed and the printer gets unresponsive atter that, I assume there is a fault in the firmware.
Any chance to get a newer version in the net?

DJVibezzz · April 26, 2021, 9:17am

The printer firmware is the latest available.
When I slice with cura it works without interuptions

Ewald_Ikemann · April 26, 2021, 9:20am

As far as I know neither Cura nor PrusaSlicer generate G3/G4 commands on their self.
Do you have the ArcWelder installed?

DJVibezzz · April 26, 2021, 9:35am

I don't have it installed.
I used default flsun profile on prusaslicer and it makes an arc because it is a round bed

Charlie_Powell · April 26, 2021, 9:37am

What's in your start gcode in the slicer? Remove any G2/G3 commands there, your printer clearly doesn't support them.

DJVibezzz · April 26, 2021, 9:47am

I will try to remove the g2/g3 commands.
Why is it implemented in the default profile if it doesn't work?

DJVibezzz · April 26, 2021, 9:50am

;STARTGCODE
M117 Initializing
; G90 ; use absolute coordinates
M83 ; extruder relative mode
M107
G28 ;Home
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp
M104 S[first_layer_temperature] ; set extruder temp
M109 S[first_layer_temperature] ; wait for extruder temp

G92 E0
G1 X-98 Y0 Z0.2 F4000 ; move to arc start
G3 X0 Y-98 I98 Z0.2 E40 F400 ; lay arc stripe 90deg
G0 Z1 
G92 E0.0

this is standard start g-code

fieldOfView · April 26, 2021, 9:50am

It isn't implemented in the default profile. PrusaSlicer does not create G2/G3 commands, unless you postprocess the GCode with ArcWelder (either from PrusaSlicer, or on the OctoPrint side of things).

DJVibezzz · April 26, 2021, 9:51am

I got a clean install with default flsun profile and I didn't add that

Ewald_Ikemann · April 26, 2021, 10:13am

How does the profile/startcode of Cura looks like?

fieldOfView · April 26, 2021, 10:33am

That does not look like the flsun start gcode that is specified here:

github.com

prusa3d/PrusaSlicer/blob/5783cc62fb02c7433b119026ffcbd574d853fd6d/resources/profiles/FLSun.ini#L777


machine_max_jerk_z = 5,10
max_print_height = 360
nozzle_diameter = 0.4
printer_model = QQSP
printer_variant = 0.4
printer_notes = Don't remove the following keywords! These keywords are used in the "compatible printer" condition of the print and filament profiles to link the particular print and filament profiles to this printer profile.\nPRINTER_VENDOR_FLSun\nPRINTER_MODEL_QQSP\nPRINTER_HAS_BOWDEN\n
retract_length = 5
retract_speed = 30
retract_lift = 0.4
silent_mode = 1
start_gcode = ;STARTGCODE\nM117 Initializing\n; Set coordinate modes\nG90 ; use absolute coordinates\nM83 ; extruder relative mode\n; Reset speed and extrusion rates\nM200 D0 ; disable volumetric E\nM220 S100 ; reset speed\n; Set initial warmup temps\nM117 Nozzle preheat\nM104 S100 ; preheat extruder to no ooze temp\nM140 S[first_layer_bed_temperature] ; set bed temp\nM190 S[first_layer_bed_temperature] ; wait for bed final temp\nM300 S40 P10 ; Bip\n; Home\nM117 Homing\nG28 ; home all with default mesh bed level\n; For ABL users put G29 for a leveling request\n; Final warmup routine\nM117 Final warmup\nM104 S[first_layer_temperature] ; set extruder final temp\nM109 S[first_layer_temperature] ; wait for extruder final temp\nM190 S[first_layer_bed_temperature] ; wait for bed final temp\nM300 S440 P200     ; 1st beep for printer ready and allow some time to clean nozzle\nM300 S0 P250       ; wait between dual beep\nM300 S440 P200     ; 2nd beep for printer ready\nG4 S10             ; wait to clean the nozzle\nM300 S440 P200     ; 3rd beep for ready to start printing\n; Prime line routine\nM117 Printing prime line\n;M900 K0; Disable Linear Advance (Marlin) for prime line\nG92 E0.0; reset extrusion distance\nG1 X-54.672 Y-95.203 Z0.3 F4000; go outside print area\nG92 E0.0; reset extrusion distance\nG1 E2 F1000 ; de-retract and push ooze\nG3 X38.904 Y-102.668 I54.672 J95.105 E20.999\nG3 X54.671 Y-95.203 I-38.815 J102.373 E5.45800\nG92 E0.0\nG1 E-5 F3000 ; retract 5mm\nG1 X52.931 Y-96.185 F1000 ; wipe\nG1 X50.985 Y-97.231 F1000 ; wipe\nG1 X49.018 Y-98.238 F1000 ; wipe\nG1 X0 Y-109.798 F1000\nG1 E4.8 F1500; de-retract\nG92 E0.0 ; reset extrusion distance\n; Final print adjustments\nM117 Preparing to print\n;M82 ; extruder absolute mode\nM221 S{if layer_height<0.075}100{else}95{endif}\nM300 S40 P10 ; chirp\nM117 Print [input_filename]; Display: Printing started...
thumbnails = 16x16,260x260
use_relative_e_distances = 1
use_volumetric_e = 0

[printer:FLSun QQS Pro 0.6 nozzle]
inherits = FLSun QQS Pro
printer_variant = 0.6
nozzle_diameter = 0.6
max_layer_height = 0.40
min_layer_height = 0.15

But I never used PrusaSlicer, so what do I know?

DJVibezzz · April 26, 2021, 10:39am

That's the QQS.
It also has g3 code

DJVibezzz · April 26, 2021, 10:40am

This is my cura start gcode:

G28 ;Home
G1 Z15.0 F6000 ;Move the platform down 15mm
;Prime the extruder
G92 E0
G1 F200 E3
G92 E0

Ewald_Ikemann · April 26, 2021, 11:08am

As you see, there is no G3 command in that script.
You should delete that line in the PrusaSlicer gcode start script.

DJVibezzz · April 26, 2021, 11:27am

I will try that. Thank you