You are not logged in.
Pages: 1
Hi. I have been importing several STL part models into VERICUT without a problem, up to now. I have got two models which display the blue boundary box when highlighted in the component tree, but refuse to display themselves as solid models in VERICUT. I am exporting SOLIDWORKS models into STL for importing to VERICUT. Can you tell me if there are any bugs or things to watch for when importing models with the aforementioned procedure? Thanks Peter Blythe
Offline
Hi Peter
From the description you give it sounds like a bad STL, probably has holes in it.
I am not familiar with Solidworks, many on here are, more likely there are some fixing tools available inside.
Best regards
Gavin
Offline
look under
files, Convert, Polyfix
it may take a couple of passes to fix the polygon file.
Louis
Offline
Hello Peter,
A STL model is made of a multitude of triangles to reproduce the shape of the part. Each triangle has a normal vector. The vector indicates which side of the triangle is inside or out.
For VERICUT to display the model correctly, the normal vectors of all the triangles must be consistants (all outward or all inward). Also the model must be all closed (watertight).
Polyfix is a converter that works on the mormal vectors. As Louis mentionned, sometimes it takes 3-4 iterations to fix a model. If there is a hole in the model, Polyfix will no repair it. You then might have to improve the STL output from SolidWork.
Note: I worked on the initial demo for your company. I used Polyfix to repair you model, it took 2 passes.
Offline
I have seen similar problems. The difference is that when I import an STL it looks pretty good. However, when I start the similator at least half of the STL disappears. It was also a problem when I tried using auto-diff. I am using Cimatron.
Offline
It is the same problem. Either gaps or inverted normal vectors. You can also try File > Properties > Stock Consistency Check. VERICUT will then verify for small holes in the model and will fix it. This is not a permanent change, it is done every time the simulation is started. It can cause a slight delay.
Offline
O/K....
So the question in my mind is...
why do you not copy that bit of
"repair/non manifold solid" code
up into the polygon repair program?
Louis
Offline
When the simulation is started, VERICUT takes the stock model (STL, Polygon or parametric) and creates an internal solid representation. VERICUT does not change the STL model but simply disregard small gaps.
Offline
o/k...
Louis
Offline
I often find that if a triangle model isn't watertight Vericut has problems with it. I have to go back to the source file, make the surfaces watertight (using the master data model, that contains surfaces and not triangles) and re-export to a triangle file.
STL and other Triangle files do not contain any surfaces. They're a pain.
Offline
Pages: 1