Extruder 2 doesn't like some specific models

[mlitzkow 1]

With some 2-part models, I can bring in both .stl files, assign one to Extruder 1 and the other to Extruder 2, merge, and slice and print.  No problem.

 

With other 2-part models, I can bring in both .stl files and assign one to Extruder 1, but the when I assign the other to Extruder 2, immediately one of the models gets "hatched out".

• A specific one of the models doesn't like Extruder 2 in use, and it will "hatch out" regardless of which model I assign to Extruder 2.
• Cura immediately objects to this model when extruder 2 is used, regardless of which model is assigned to which extruder.
• If I just bring in this model by itself and assign to extruder 2, it Cura also objects. 
• I have the two extruders configured identically except for a very minor change in the extruder switching code. (One should heat up and the other one cool down when I make the switch, so the switching codes are symmetric rather than identical.)

 

Does anyone have an idea what might be wrong here?

Is there an error log or someplace else where I can get more information about what Cura is objecting to?

I am attaching both .stl files for reference.  My intention is to print the "Base" file with extruder 1 and the "Letters" file with extruder 2.

 

Thanks in advance,

-- mike

Base_Embossed_V15.stl Letters_Embossed_V15.stl

[nallath 1,123]

I can't really reproduce the issue. I've done the following

1. Load both files

2. Select both of the objects

3. RIght mouse -> merge models
4. Ctrl + click on the letters to select it

5. Select second extruder for the letters

 

[mlitzkow 1]

Many thanks for taking a look at my problem.  I'm sorry that you were unable to reproduce the issue.  That always makes things so much harder. (I have 35 years experience as a software developer.)  Since you did things in a slightly different order than I had, I tried following your procedure exactly to see if that would solve the issue.  Unfortunately, no.

 

I was not aware that you can still select the two models separately after merging them.  So I had tried to set extruder 2 before merging the models, and you did it after merging the models.  Now I have learned that you can still access the two models separately even after the merge, so I tried it that way.  I still get the error when I select Extruder 2 for the "Base" model.

 

One thing I try to do when debugging an issue like this is try to come up with a simpler scenario where the same thing will go wrong,  I now find that bringing the "Letters" file is not necessary for demonstrating the problem.  All I have to do is bring in the "Base" file, and then set Extruder 2, and the model immediately gets "hashed out".  As that requires fewer steps and will interface with Cura in fewer places, I suggest we continue looking at this problem using the simpler example.

 

For the record, I am using Cura version 4.7.1.  I first made sure that I have both extruders enabled and set to valid materials. I simply brought in the "Base" model (which is automatically selected).  Then I right-clicked and checked the box for Extruder 2.  The error appeared.  For good measure, I hit "Slice" so that I could see what Cura would say about the error.  Please see the screen shots below.  Also, you should know that I only recently built up my printer with the E3D Chimera and started trying to use dual extrusion printing.  I am a moderately experienced Cura user with single extruder printers. I have succeeded with dual extrusion on a couple of other models.  Still, I am new to dual extrusion, and may be making some stupid mistake. 

 

I wonder if there is a way to get Cura to tell us what it is objecting to?  Is there a logfile I can read or forward to you?  Is there some option for turning on additional debugging?

 

best regards,

-- mike

 

 

[Tomahawk_101 1]

Hi,

Based off of your most recent pictures it looks like you have a "Prime Tower" touching your model. It prints in the circled area. You can change the X and y position of this so it doesn't touch your model and that should fix it.

 

Edited September 30, 2020 by Tomahawk_101

[mlitzkow 1]

You got it! That's perfect!  It was indeed a stupid mistake on my part.  Thank you so much for your help.

 

best regards,

-- mike