<p>I just assembled an FLSUN QQ-S pro printer and successfully printed two models from the supplied SD card. Everything works fine. However, I tried slicing my own model using PrusaSlicer and although the print head moves, the extruder motor does nothing. What could be the issue? Do I need to modify the G-code commands?</p>

CC BY-SA 4.0
2020-10-17T18:22:18.833Z
Is this a single-head (max) printer? Does your gcode have a T# argument, to direct extrusion commands to a particular head?
Davo
CC BY-SA 4.0
2020-10-17T20:57:14.260Z
It is a single head printer.
mr_js
CC BY-SA 4.0
2020-10-18T10:47:22.337Z
Do you see extruder movement G-codes in the file? e.g. lines with `G1 X... Y... E...`
0scar
CC BY-SA 4.0
2020-10-19T07:34:49.917Z
I solved the problem. The initialization code generated by the slicer wouldn't work with my machine. I replaced it with the init code from one of the test files.
mr_js
CC BY-SA 4.0
2020-10-19T08:24:10.427Z
Despite being solved, I want to note, that this was probaly due to using wrong extruder positioning. Prusa printers use relative positioning, whereas othe printers may use absolute positioning. I do not see any pros or cons for one or the other. Both the printer and the slicer can be configured to use either of them. In your case, it was probably that the printer was expecting absolute coordinates and the slicer was feeding relative coordinates resulting in no or very little movement. The configuration ussually happens at the start of the gcode by giving commands: M82 (abs) and M83 (rel).
TurgonTheKingOfGondolin
<g-code><slicing><prusaslicer>
Extruder motor not running when using G-code from PrusaSlicer with non Prusa printer
mr_js
# Extruder motor not running when using G-code from PrusaSlicer with non Prusa printer

(Asked by: username_0 on 2020-10-17)

I just assembled an FLSUN QQ-S pro printer and successfully printed two models from the supplied SD card. Everything works fine. However, I tried slicing my own model using PrusaSlicer and although the print head moves, the extruder motor does nothing. What could be the issue? Do I need to modify the G-code commands?

**Tags:** g-code, slicing, prusaslicer

> **Comments:**
> **username_1**: Is this a single-head (max) printer? Does your gcode have a T# argument, to direct extrusion commands to a particular head?  
> **username_0**: It is a single head printer.  
> **username_2**: Do you see extruder movement G-codes in the file? e.g. lines with `G1 X... Y... E...`  
> **username_0**: I solved the problem. The initialization code generated by the slicer wouldn't work with my machine. I replaced it with the init code from one of the test files.  
> **username_3**: Despite being solved, I want to note, that this was probaly due to using wrong extruder positioning. Prusa printers use relative positioning, whereas othe printers may use absolute positioning. I do not see any pros or cons for one or the other. Both the printer and the slicer can be configured to use either of them. In your case, it was probably that the printer was expecting absolute coordinates and the slicer was feeding relative coordinates resulting in no or very little movement. The configuration ussually happens at the start of the gcode by giving commands: M82 (abs) and M83 (rel).  

---

## 0 answers

