I upgraded to Cura 3.2.23 today and set up my machine. I have a TAZ6 with v3 dual extruder.
Previously in 3.2.21, I had two machine profiles defined. Both were TAZ6 with V3 Dual Extruder profiles, however, one of the profiles was named “LULZBOT TAZ6 DualExtruderv3 (T0 ONLY)” and had the gcode start and end blocks modified with all the commands for T1 removed. I used this machine profile when I didnt need both extruders active for a simple print. When I wanted to use both extruders, I used the standard LULZBOT TAZ6 DualExtruderv3 machine profile. This worked well, since there is no way to toggle dual extruder support easily. However, after the upgrade, I noticed that a print paused and started heating the second extruder (T1) right after the modified gcode start block was executed. I double checked the block and confirmed that all the T1 related commands were commented out. Then I checked the gcode file for the print and noticed that T1 gets set right before the skirt gets printed.
Original code from 3.2.21:
[b]<... end of start gcode block...>[/b] M117 TAZ Printing... ; LCD status message M221 S100 ;LAYER_COUNT:94 ;LAYER:0 M107 G0 F3600 X113.759 Y111.408 Z0.299 ;TYPE:SKIRT G1 F1800 X114.246 Y111.158 E0.01283
Code from 3.2.23:
<... end of start gcode block...> M117 TAZ Printing... ; LCD status message M221 S100 ;LAYER_COUNT:75 ;LAYER:0 G1 F600 E-5 G92 E0 T1 G92 E0 M109 S210 M107 M104 T0 S180 G0 F2250 X98.526 Y102.226 Z0.424 ;TYPE:SKIRT G1 F900 X98.712 Y101.971 E0.01049
In the code from 3.2.23, there are commands for T1 added now! So, I tried modifying the number of extruders in the Machine Settings for (T0 ONLY) from 2 to 1 hoping that this would eliminate the generation of gcode for T1, but when i went to slice, Cura crashed with an error message that states “CuraEngine.exe has stopped working”. So, its clear that setting the number of extruders to 1 on a machine profile setup for dual extruders puts the program in an invalid state. This behavior is also present in the newest 3.2.27 version. What was the reason for adding these commands? Is there a way to prevent them from generating or can this be addressed in future versions!!??