From: Paul Suomala (email@example.com)
Date: Fri Dec 13 2002 - 17:20:07 EET
In the design software one needs to execute a boolean unite operation. I
believe the STL was created without having completed that step.
On your end, if you have something like Magics RP (an stl manipulating
program), you can convert the parts to multiple shells, then execute a boolean
Scott Tilton wrote:
> Hi guys,
> I have a STL file of an assembly that was created in SDRC I-DEAS.
> The person who did all the design work on it, while still in I-DEAS, merged
> all the individual parts into one supposedly solid piece. Then he exported
> that merged piece out as an STL file and is asking me to make a model of it
> for him.
> The problem is that when I go and look at the preview of the laser scans for
> each layer, I can clearly see that it is still taking each individual part
> of the original assembly and treating it as if it were a separate element.
> Anywhere two of the elements overlap . .. the Sinterstation is actually
> going to scan those areas twice (or three times if there are three objects
> occupying the same space)
> I had the same problem with some architectural models that were sent to me
> one time . .and the architect was able unify or merge all the parts in a
> different way so they became one completely solid piece.
> He was working in some AutoDesk product or another though, so he couldn't
> help with IDEAS.
> Anyone have any sort of clue how to handle this?
> I'd hate to have to resort to exporting everything out in IGES (or some
> other format) and then importing it again and finally saving it as an STL.
> Any help would be greatly appreciated.
> Scott Tilton
This archive was generated by hypermail 2.1.4 : Tue Jan 21 2003 - 20:14:44 EET