PrusaSlicer 2.9.4 blocks on Prusa XL
Hello,
Since a few versions, PS adds some kind of priming tower at the beginning of the print, which is nice.
Just after doing them, it emits a beep. Strange, but it used to work.
But when I printed a large model, printing stopped just after printing it, before doing the first model move.
I activated logs and got:
```
Dec 11 18:40:48 10:9c:70:23:31:c4 buddy[Marlin] busy: processing
Dec 11 18:40:49 10:9c:70:23:31:c4 buddy[Marlin] T:224.00/225.00 B:80.08/80.00 C:-30.00/0.00 X2:36.00/36.00 A:81.20/0.00 T0:25.00/0.0
Dec 11 18:40:49 10:9c:70:23:31:c4 buddy[Marlin] B_1_0:80.00/80.00
Dec 11 18:40:49 10:9c:70:23:31:c4 buddy[Marlin] W:0
Dec 11 18:40:51 10:9c:70:23:31:c4 buddy[Dwarf_3] 2394.723s [INFO - ModbusControl:0] Set print fan PWM:: 0
Dec 11 18:40:56 10:9c:70:23:31:c4 buddy[Marlin] X:67.95 Y:1.76 Z:0.20 E:0.00 Count A:5581 B:5254 Z:234
Dec 11 18:40:58 10:9c:70:23:31:c4 buddy[Marlin] busy: paused for user
Dec 11 18:42:54 10:9c:70:23:31:c4 buddy[Marlin] message repeated 48 times: [busy: paused for user]
```
I traced the problem to the following G-code:
```
;WIPE_START
G1 F19200;_WIPE
G1 X67.977 Y3.3 E-.16;WIPE_END
M300 S800 P500
M1 Remove priming towers and click button.
M107;LAYER_CHANGE
;Z:0.2
;HEIGHT:0.2
```
There is a spurious M1 added (maybe left from devpt...), but it is NOT displayed on the XL display!!!
So the printer waits for user to resume, but the UI still shows the Tune/Pause/Abort screen, and we are stuck!
It looks like there are 2 bugs:
- `The 'M1 Remove priming towers and click button.` which should not be there (PS problem)
- When displaying the standard Tune/Pause/Abort screen, an M1 message is not displayed with the corresponding interaction. (XL firmware problem)
Hopefully, I found a workaround in PS:
In Print Settings / Other / G-code substitutions, add the following:
Find "M1 Remove priming towers and click button" and replace with "; M1 Remove priming towers and click button"
This comments the line and the print continues OK!
In addition, when trying to send Gcode metrics through the UI, the g-code option (#90) reset itself systematically; so it's not possible to trace the executed gcode in syslog.
Maybe it's a feature ...
Hope that it helps!
Michel