Jamie you are right, it is an "UGS NX IGES V5" file with > 2500 single surfaces.

Anis I have send the STEP file and I hope you can use it. :)

Hi Ralf,

How do you the file come from NX, I have opened the file use notepad but cant any phrase with "NX"...
Thanks for sent to me the STEP file, I have open it and still the same condition. I mean contains many disjoint surfaces.

I am appreciate your help, thanks.... :)

Hi Anis & Ralf - is the STEP file you are referring to recently one created by a conversion from the IGES file?

Instead of that you want to get a STEP (and possibly an SAT) file created from the original application that exported this IGES file, exported from the original native model data.

That may help keep the data all connected together as a solid more easily rather than trying to deal with the individual surfaces in the IGES file.

- Michael

Hi Michael...

I think Ralf export from Iges.
Which do you think better comparing export to iges, step or sat ?

Thanks

Hi Anis,

> Which do you think better comparing export to iges, step or sat ?

Each of these formats has some complexities in slightly different areas, so I would suggest getting as many different formats as possible.

So instead of choosing one between IGES, STEP, and SAT, instead request getting the same model data in each of those formats, including 3DM and Parasolid if they are able to do those.


But if the original data is messy and possibly contains holes and overlaps in it then of course that will not get automatically solved by using some particular file format.

If the original model data is ok then one of the formats that contains solid information (STEP or SAT) will save you some joining work.

- Michael

Ok, then how about the precision / which is more accurate ?

Hi Anis, are you talking just about numeric accuracy? They are all pretty close to equivalent in the representation of numbers.

Those formats are text file formats and I think the number of digits to use for the text representation of numbers is something that is up to the particular application generating the file.

But it is very unlikely that you will run into problems with not enough digits in the number formatting used in any of those formats.

- Michael

thanks Michael... :)

I recently ran into a model that appeared the same. It "appears to be a simply constructed solid, the many of the fillets are naked. There doesnt appear to be anything like overlapping trim boundries or fincky edges or anything. I'm thinking this might be something related to "Tolerances" set in other apps that then dont propogate unless the same tolerance is known in the receiving app.

We've discussed this before Michael, with regard to Rhino and you described your thoughts that having that variable tolerance value was a design mistake that lead to these types of situations.

I've requested the file from Anis also to have a looksee at it.

Hi Burr, well tolerances come into play mostly when various kinds of geometry is created.

Many operations cannot be calculated directly, they go through a kind of iterative refinement until the result is close enough to the desired accuracy, with the desired accuracy being the tolerance.

Various things like general surface/surface intersection, fillet surface creation, sweeping, etc... are all things that use that kind of refinement.

If you have set a tolerance that is too loose, then it means the the surfaces that you generated will kind of sag away by some significant amount away from where their ideal locations would be. That's something that happens at the time that the surface is created, it doesn't have a whole lot to do with just saving data that has already been created.

Various kinds of systems can also have an error tolerance value that is associated with edges, which kind of marks the distance of the maximum gap between the 3D edge and the surfaces that are associated with it. This kind of error value assigned to an edge is not really too crucial to be sent down by export processes because it can be calculated later.


- Michael

Hi Burr,

> We've discussed this before Michael, with regard to Rhino
> and you described your thoughts that having that variable
> tolerance value was a design mistake that lead to these
> types of situations.

Yeah, what can happen is if someone fiddles with the tolerance it can easily lead to geometry being too saggy or it's also bad for someone to make it super tight and get things like 100,000 control points on every single trim curve.

It's especially surprising when you receive a file from someone else when they have messed with the tolerance and you are not aware of it, and then you start to create new things after loading in their file, getting things like sags in your fillets.

- Michael

Hi Burr....

BTW I dont receive yet any request from you.
PM me and provide your email if you want....

Thanks

Hi Michael,
It must be a saggy thing with regard to the model I'm refering to. It is a simple revolved solid with holes punched in it and fillets on the holes. Nothing manually created. You would think that the fillets would create a nice edge as opposed to naked. I do suppose you could still punch holes that would cause it to be faulty fillets too though... Many factors there.


Anyway, mine is not a MoI model, so I will wait for Anis's to see if I can conjure up anything....

Thanks again.

Hi Burr, does the one you have join up if you scale it down by 1/10 or 1/2 using the steps from here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=3593.3

Possibly that model was built to a tolerance of 0.01 units, maybe making the fillets just sagging away by slightly more than MoI's max join tolerance. A sag of 0.01 units is not particularly visually bad, it can be tough to see it unless you examine things more closely.

The reason why scaling down can make things join up is that when you scale an object down, the gaps between pieces also get smaller as well, so it can put them within the tolerance distance if they were just outside of it before.

In the future I would like to make a way to override MoI's tolerance, but probably something like an override that lasts just for the current command or modeling session rather than something that gets stored in the file and set once the file is loaded - that particular method of having a changed tolerance get set on someone when they don't expect it is the thing that tends to cause trouble.

- Michael

Hi Michael,
I did try the scale and it would join more than without the scale, but never make a solid.

This is the model I refer to. It is not something I need to fix. It is being used for a question regarding machining....But it just seemed to be the same thing so thats why I mentioned it. If you want to peek and refer to it to see if anything stands out, that would be nice. But there is no need to "work it" to try and make a solid. Only to see if you can see why it is not.

Thanks

Hi Burr, I'm not 100% sure what is happening there, the edges do not seem to sag away from one another, but also the edges between different pieces are not exactly aligned with one another, some of them have different endpoints although not very far away.

I took a close look into one problem area and it looks like there is some crossing overlap between some of the edge curves, that may be the problem.

Like for here I marked the end of this edge with a point:



Now if I go select the edge right next to it you can see this:




I'm not entirely sure if that is the problem though.

- Michael

Hi Anis,

I had a look at this model and unfortunately it's a mess, it seems that the person who modeled this part has had the modeling tolerance set very loose in their cad program.
Ralf was correct, it was exported from NX, I've highlighted it in the picture attached.

I did run some analysis in NX, also NX has a feature called heal geometry, what that does is it tries to fix geometry by tightening tolerances, removing tiny objects and various other surface repairs, it works quite well when there a few geometry abnormalities, I've also attached the output result of that operation and you can see how many things are wrong with this model, but there were still a lot of naked edges after this operation, the best you could get was to sew(join) the surfaces in NX using a tolerance of 0.1mm(0.004") which in my opinion is way too loose, I wouldn't trust the quality of any of the surfaces and it still resulted in a lot of naked edges that would take some hours to fix.

Anyhow there is no quick fix for this file, I suggest if your client is using NX 5.0 I can't see why they can't output it as a STEP to see if that is any better.






-

Hello,

This is the basic result from an import to SCE and a stitching command. I think it almost might be better for you to try to defeature the model and build it back up. Even it its somewhat whole state it has hundreds of geometry errors. Is this for rendering purposes?

OSTexo, was it hard job to stich the surfaces with SC?

""""""""""" but also the edges between different pieces are not exactly aligned with one another, some of them have different endpoints although not very far away.""""""""""""""

Thanks for looking at that Michael. I thought I inspected those endpoints of edges and didnt see any. I need more practice!

Anyway, it seems that with this, and Anis's model, it's not really what I was looking for, but more construction issues, or the export didnt handle the solid creation well. "STEP" up to solids :o

Thanks again.