Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....  

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

FWIW, I am using PrusaSlicer with my Sidewinder X1 and am not having any issues. I am printing via OctoPrint.

Easiest would be to compare the gcode produced by PrusaSlicer and that produced by Simplify 3D. Open each file in a text editor and examine the top 100 lines or so. This will contain the startup gcode, including temps and printing of the prime line. 

Have you customized the firmware on your Sidewinder? I have noticed that enabling mesh bed leveling can have an impact on the nozzle position. If I do the 4 corner leveling, then enable MBL, I need to set a Z offset (usually a negative value to lower the nozzle) in my printer settings. If I inadvertently leave MBL enabled before doing the 4 corners, it can really throw things off. Depending on whether and where you enable MBL in startup gcode, this might have an effect similar to what you're seeing.

If you want to zip up a SMALL gcode file from each slicer and attach it to a reply here, we can take a look. It would also be helpful if you would save a 3MF project file in PrusaSlicer, zip it up and attach it to a reply so we can see your settings.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

@bobstro

Thanks for taking your time for my problem.

Some with whom I have spoken also use Prusaslicer with their sidewinder and that without problem.

I installed this:
https://cults3d.com/fr/mod%C3%A8le-3d/outil/firmware-tft-artillery-x1-france

I don't think this changes the firmware, just the pictures in my opinion.

I am attaching you a Simplify3D gcode (which works) and a Prusalicer gcode where I have the problem.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

 A few things stand out...

In Simplify 3D, your startup gcode is using:

M420 S1 Z2 ; Enable ABL using saved Mesh and Fade Height

In PrusaSlicer, your startup gcode is using:

G29; ABL (Auto Bed Leveling)

So in Simplify 3D, you are reading in and restoring the saved ABL values which can include a Z offset. In PrusaSlicer, you are doing ABL but not doing any Z offset. The Z offset is roughly equivalent to Prusa's Live-Z, and offset that is applied after mesh bed leveling. In this case, if your saved values -- those retrieved by M420 -- include a Z offset, that is not being applied in your PrusaSlicer gcode. If that offset is a positive value, it is raising the nozzle away from the glass.

You should be able to identify the saved values by entering M503 into a terminal interface on the Sidewinder. In my Sidewinder output, I have this:

G29 S4 Z-0.02000

That is an offset lowering my "Live-Z" (1st layer nozzle height) by 0.02mm. I suspect yours is a positive/non-negative value.

You're welcome to take a look at my PrusaSlicer start gcode for my Sidewinder. Notice I have at the bottom:

M420 S1 Z3 ; reload and fade mesh bed leveling at 3mm

This reads in my saved MBL (I do it manually) values including the Z offset.

I recommend setting your 1st layer height high enough so that WITHOUT restoring the firmware settings, the nozzle will not hit the bed. Then use a NEGATIVE Z offset in your settings or gcode to make adjustments to the 1st layer height at print time. That way, you won't damage the bed if something occurs in the wrong order. Notice in my current start gcode, I do the prime line BEFORE issuing M420. This is just a personal preference so I know the nozzle is at the right height even if the print is off. I want it set so any Z offset adjustments only LOWER the nozzle. (I learned the value of this approach from using my Prusa printer.)

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

Update: Just to clarify, when my startup gcode includes:

M420 S1 Z3 ; reload and fade mesh bed leveling at 3mm

That includes the stored value in:

G29 S4 Z-0.02000

as well as a G29 setting for each ABL test point.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

I have trouble understanding, I'm new to code.

It would appear that you are acting on the code but one thing is not consistent. IF I modify the starting code, with several different alues, that does not change the behavior of the nozzle which always comes to be placed in the same place, besides, another strange thing, a member send me a gcode file which works at home, on his sidewinder with prusaslicer, but when I print this code on my sidewinder, the nozzle always behaves the same way, namely comes to be placed on the plate, in front, in the left corner and heats up before from the print.

To sum up, whether I change the starting code or use a gcode made by another member (while it works well for him), it has no effect on my sidewinder.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

1. ; PrusaSlicer start gcode for Artillery Sidewinder x1
2. ; Last updated 20200814
3. M300 S60 P10 ; chirp
4. M117 Initializing
5. ; Set coordinate modes
6. G90 ; use absolute coordinates
7. M83 ; extruder relative mode
8. ; Reset speed and extrusion rates
9. M200 D0 ; disable volumetric e
10. M220 S100 ; reset speed
11. ; Set print temps
12. M117 Heating nozzle & bed
13. M104 S160 ; set no-ooze nozzle temp while bed heats
14. M140 S[first_layer_bed_temperature] ; set heatbed temperature
15. M109 S160 ; wait until nozzle is warm to avoid bed damage
16. ; Home
17. M300 S60 P10 ; chirp
18. G1 Z3 F3000 ; move z up little to prevent scratching of surface
19. M117 Homing
20. G28 ; home all axes
21. ; Present bed for final cleaning
22. M300 S60 P10 ; chirp
23. G1 Z3 F3000 ; move z up little to prevent scratching of surface
24. G0 X155 Y310 F7200 ; Present bed for cleaning
25. ; Wait for final bed heating
26. M190 S[first_layer_bed_temperature] ; wait for the bed to heat up
27. ; Return to prime position and wait for nozzle to heat up
28. M300 S60 P10 ; chirp
29. G1 Z3 F3000 ; move z up little to prevent scratching of surface
30. G1 X0 Y-5 F7200.0 ; go outside print area
31. M104 S[first_layer_temperature] ; set final nozzle print temp
32. M109 S[first_layer_temperature] ; wait for the nozzle to heat up
33. ; Prime line routine
34. M300 S60 P10 ; chirp
35. M117 Printing prime line
36. M900 K0; Disable Linear Advance for prime line
37. G92 E0.0 ; reset extrusion distance
38. G1 Z0.2 F3000 ; lower nozzle to printing height
39. G1 E5 F1000 ; de-retract and push filament to trap ooze
40. G1 X0 Y-3 F7200 ; move to prime line position
41. G1 X20.0 E10 F7200.0 ; fat 20mm intro line @ 0.5
42. G1 X60.0 E3.2 F3600.0 ; thin +40mm intro line @ 0.08
43. G1 X100.0 E6 F3600.0 ; fat +40mm intro line @ 0.15
44. G1 E-0.8 F3000; retract to avoid stringing
45. G1 X99.5 E0 F3600.0 ; -0.5mm wipe action to avoid string
46. G1 X110.0 E0 F3600.0 ; +10mm intro line @ 0.00
47. G1 E0.4 F1500; de-retract
48. G92 E0.0 ; reset extrusion distance
49. ; Final print adjustments
50. M300 S60 P10 ; chirp
51. M117 Preparing to print
52. ; Adjust extrusion rate if desired
53. M221 S{if layer_height >= 0.1}90{else}100{endif} ; compensate for thick layer heights
54. M92 E415 ; compensate for extrusion error
55. ;M85 S300 ; activate 300-second idle timeout
56. ; Adjust PID values
57. ;M301 P14.93 I1.27 D43.27
58. ;M304 P88.75 I11.17 D176.30
59. M420 S1 Z3 ; reload and fade mesh bed leveling at 3mm
60. M117 Print in progress

I add this code in the starting code ( https://pastebin.com/dR48YjZ6), and it looks like it works, the nozzle does not move, it starts to heat up to 160 °

Do you think I can use it without risk?

For information, I am in stock and without BL-touch.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

I do not understand the increase in temperature to 160 °, then in the Prusaslicer parameters, there are different

Look: http://prntscr.com/wik8hd

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

Posted by: @allan-fonroques

[...] I add this code in the starting code ( https://pastebin.com/dR48YjZ6), and it looks like it works, the nozzle does not move, it starts to heat up to 160 °

It's a 2-step nozzle warmup to prevent oozing. It works like this:

1. Start heating the nozzle to 160C. This is warm enough to soften filament in case you have some on the nozzle, but not hot enough to let the filament to ooze out of the nozzle.
2. Start heating the bed.
3. Wait for the nozzle to get up to 160C. 
4. Raise the nozzle and move it to the back-center of the bed while we wait for the bed to finish heating. This gives you one last chance to inspect and clean the bed. (On the Sidewinder, the bed heats quickly, so this may only be for a moment.)
5. Wait for the bed to get up to the print temperature.
6. Move the nozzle back to the home position.
7. Wait for the nozzle to get up to the print temperature.
8. Print the prime line and continue the print.

You can remove these lines if you don't like them, but it works very well for me on my Sidewinder X1.

Do you think I can use it without risk?

For information, I am in stock and without BL-touch.

Ah, I thought you had a BL-touch or something similar based on the G29 codes in the Simplify 3D gcode. I see that you only modified the LCD screen firmware, not the Marlin firmware that controls the printer. In that case, you need to adjust the 4 corners so the nozzle is at the right height and REMOVE the M420 line from your gcode (line 59 in your post).

I think your problem is that you're using gcode commands that only make sense if you have ABL. Remove those and you should be OK. 

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

Yes i understand better 🙂

which line controls the temperature rise of 160 °?

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

You may also need to remove the comments in the startup code.  The buffer fills up and you will lose some commands being sent to the printer.  It usually shows up when printing the skirt.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

The 160C temperature is set in line 13 of your code posted above:

M104 S160 ; set no-ooze nozzle temp while bed heats

Disable lines 21-25 if you don't like the bed movement.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

Posted by: @davidsteinman

You may also need to remove the comments in the startup code.  The buffer fills up and you will lose some commands being sent to the printer.  It usually shows up when printing the skirt.

One of the under-appreciated features of OctoPrint is that it does "minification" of the gcode before sending it on to the printer. It removes all comments from the gcode stream on the fly. 

I haven't had an issue on the Sidewinder with comments in gcode though. The board seems to keep up well. The faster serial speeds probably help.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

I  use OctoPrint also, and I think the problem does not occur with it.  It definitely did when using the USB drive.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

Posted by: @davidsteinman

I  use OctoPrint also, and I think the problem does not occur with it.  It definitely did when using the USB drive.

Ah, I dumped the touch screen and have an SD card reader on the LCD screen that replaced it. I never played with the USB much. I suppose it could be slower. I'm sure the speed of the USB flash drive and SD cards matters as well. I chucked the little USB key that came with the Sidewinder and use Samsung EVO SD cards.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

@bobstro
I have removed this line, but it still preheats to 160 °

M104 S160 ; set no-ooze nozzle temp while bed heats

Here is the code I put:

; PrusaSlicer start gcode for Artillery Sidewinder x1
; Last updated 20200814
M300 S60 P10 ; chirp
M117 Initializing
; Set coordinate modes
G90 ; use absolute coordinates
M83 ; extruder relative mode
; Reset speed and extrusion rates
M200 D0 ; disable volumetric e
M220 S100 ; reset speed
; Set print temps
M117 Heating nozzle & bed
M140 S[first_layer_bed_temperature] ; set heatbed temperature
M109 S160 ; wait until nozzle is warm to avoid bed damage
; Home
M300 S60 P10 ; chirp
G1 Z3 F3000 ; move z up little to prevent scratching of surface
M117 Homing
G28 ; home all axes
M190 S[first_layer_bed_temperature] ; wait for the bed to heat up
; Return to prime position and wait for nozzle to heat up
M300 S60 P10 ; chirp
G1 Z3 F3000 ; move z up little to prevent scratching of surface
G1 X0 Y-5 F7200.0 ; go outside print area
M104 S[first_layer_temperature] ; set final nozzle print temp 
M109 S[first_layer_temperature] ; wait for the nozzle to heat up
; Prime line routine
M300 S60 P10 ; chirp
M117 Printing prime line
M900 K0; Disable Linear Advance for prime line
G92 E0.0 ; reset extrusion distance
G1 Z0.2 F3000 ; lower nozzle to printing height
G1 E5 F1000 ; de-retract and push filament to trap ooze
G1 X0 Y-3 F7200 ; move to prime line position
G1 X20.0 E10 F7200.0 ; fat 20mm intro line @ 0.5
G1 X60.0 E3.2 F3600.0 ; thin +40mm intro line @ 0.08
G1 X100.0 E6 F3600.0 ; fat +40mm intro line @ 0.15
G1 E-0.8 F3000; retract to avoid stringing
G1 X99.5 E0 F3600.0 ; -0.5mm wipe action to avoid string
G1 X110.0 E0 F3600.0 ; +10mm intro line @ 0.00
G1 E0.4 F1500; de-retract
G92 E0.0 ; reset extrusion distance
; Final print adjustments
M300 S60 P10 ; chirp
M117 Preparing to print
; Adjust extrusion rate if desired
M221 S{if layer_height >= 0.1}90{else}100{endif} ; compensate for thick layer heights
M92 E415 ; compensate for extrusion error
;M85 S300 ; activate 300-second idle timeout
; Adjust PID values
;M301 P14.93 I1.27 D43.27
;M304 P88.75 I11.17 D176.30
M117 Print in progress

Here's how she behaves now:

It stays in the same position, heats up to 160 °, once the temperature of 160 ° is reached, the nozzle moves to the left corner and in front and slightly lifts the nozzle and heats up to 200 °, and once at 200 ° it starts the print by making a test line.

Here is what I would like to change:
Which does not heat to 160 ° but to the one indicated in Prusaslicer, and which makes a longer and slower test line.

What do you think ?

I attach the gcode to show you.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

@bobstro

I'd like to have your opinion please 🙂

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

Problems with the Prusa forums are preventing me from posting the fix. Wordfence keeps blocking my posts. 

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

@bobstro

Ha thin, hope this will be resolved quickly, I really need your expert advice.

RE: Prusaslicer 2.3 rc2 and Sidewinder X1, problem ....

@allan-fonroques - Try this startup gcode.

If you want to slow the prime line down, change the E parameter to a lower value. That is mm per minute (mm per second * 60). For example:

G1 X20.0 E10 F1500.0 ; fat 20mm intro line @ 0.5