Sovol Cura Dual mode bug (Ext 2 hits parked Ext 1)

Just an FYI for anyone who has experienced this…I haven’ found (yet) where this has been mentioned in any posts.

When printing in dual mode I have found that Sovol’s version of Cura will often insert a somewhat random G0 T1 X0.0 etc… command in the code. This causes the right extruder to zip across and ‘kiss’ the left extruder which is in its parked position. This results in shifting the physical X offset of the heads and continued dual printing on that job is ruined.

Once I found it had entered a G0 T1 X-25 in the code which was much worse than the X0.0.

I’m finally migrating to Cura 5.7 but if anyone is still using Sovol’s version they will need to inspect and remove that line of code in their print file if they’ve had that happen.

Well, Cura 5.7 wasn’t quite the improvement I thought it would be over Sovol’s version.

I started up a two-color print and after making sure the brim of the first layer was being laid down satisfactorily I had to go out on some errands. The #2 print head would come into play on or about layer 62.

When I returned I found the #2 print head hovering over the center of the bed and #1 busily laying down filament on the part with the part hanging slightly off the left edge of the bed. There had evidently been a shoving match where the right bested the left (I have a small ball of clay stuck on the side of the left extruder so I can tell if they have collided and they had). The right now thought it was ‘home’ where the left though it was at center of the bed where the model should have been.

From what I can tell, the right extruder was commanded to the left side of the bed while the left was still finishing the first layer in the center of the bed. The Sovol version was guilty of sending #2 to the left but never when #1 was out from its parked position.

I experienced the same issue with the latest Cura version for Mac. In my case the reason is a line of code sending the extruder to X0 when presenting the print. If the active extruder happens to be #2 it will hit the parked #1 extruder. By sending #1 to X0 and #2 to X280 I was able to solve the issue. Maybe not the most elegant solution, but it works …

I recently updated to CURA 5.8 supposed to have all the fixes. The problem im having with this CURA and all the others is; it seems to stall and/or quit when I try slicing a print. Anyone have any ideas how to get it to proceed?