Is there an easy way to fix an imported model that has faults?

S_Regula · July 2023

Hi All,
I have imported a model that includes this shaft which OS is saying has faults. When I cut a section view, I see the red area that is the culprit. Is there an easy way to fix this? I can use the part in another assembly, but it will show up as red in the instance list, and because I'm kind of particular about my assemblies not containing any errors, I would prefer to fix it if there's an easy way to do so.

I've tried the "export to ACIS and re-import" workaround, but it still shows up as faulty when I bring it back in as that file type. TIA!

Image: https://us.v-cdn.net/5022071/uploads/editor/lt/vl6dsbi1cf5c.png

Image: https://us.v-cdn.net/5022071/uploads/editor/ei/kvazpf49lxun.png

S1mon · July 2023

Are you sure that red section is the problem? That could just be another part which is coincident with the shaft, and showing as interfering. There may be an issue with the shaft somewhere else. Look very carefully at any fillets or very small surfaces.

eric_pesty · July 2023

Hard to tell without seeing the model, not sure the red bit is the problem though... can you share a link?
Does it show several solids (looks like it's creating at least one)?
This will probably take some delete/relace body/faces...

wayne_sauder · July 2023

Here is a bit of code that I find helpful at times. I forget who gave it to me

.

FeatureScript 1660;

import(path : "onshape/std/geometry.fs", version : "1660.0");

annotation { "Feature Type Name" : "Find Laminar Edges" }

export const myFeature = defineFeature(function(context is Context, id is Id, definition is map)

precondition

{

annotation { "Name" : "Select surface", "Filter" : EntityType.BODY && BodyType.SHEET }

definition.surfaces is Query;

}

{

debug(context, qEdgeTopologyFilter(qOwnedByBody(definition.surfaces, EntityType.EDGE), EdgeTopology.LAMINAR));

});

S1mon · July 2023

@wayne_sauder

How is this different from the built in "Highlight boundary edges" command on the view menu?

pmd · July 2023

For something that is not too important with import errors (i.e. some fitting like a lock) where I just wanted to lose the red feature I created a big block around the imported item and did a boolean subtract of item from block. I then deleted item and created another block and did a boolean subtract of block 1 from block 2 - this left an item shaped object which was not red.

This is kind of a terrible workaround but it did remove the red...

S_Regula · July 2023

S1mon said:

Are you sure that red section is the problem? That could just be another part which is coincident with the shaft, and showing as interfering. There may be an issue with the shaft somewhere else. Look very carefully at any fillets or very small surfaces.

I'm 99% sure that's the problem. When I hide the shaft, there is no part overlapping it

wayne_sauder · July 2023

@S1mon
Good point, I'm not sure it is any different. I think if I remember right I got the code from support some years ago when I was trying to fix a import that was really bad. Not sure if the tool "Highlight boundary edges" was around then or not?

S1mon · July 2023

@S_Regula

I would first try getting a STEP file to re-import. It’s generally the most robust neutral format (after Parasolid). If that red bit is somehow part of the same body, it sounds like it’s creating the volume twice in the part. I would also try the other import options to create separate part studios. I would also report this to support. It sounds like an import bug.

S_Regula · July 2023

@S1mon It was imported as a STEP file initially. Would exporting it as the same file type and re-importing change it? I tried exporting as ACIS and re-importing it because I figured the same file type wouldn't change anything, but that didn't fix it.

S1mon · July 2023

If you re-import, but select different options in the import dialog, you should get different results. It may not solve the issue, but it will be different. I normally don’t use it, but in this case I would try “split into multiple documents” and see if that helps.

Is there an easy way to fix an imported model that has faults?

Answers

Categories