XANSYS Message: 18506 [Go back to message list]
[bookmark on del.icio.us]
No rating yet
Rate item:

Subject: Re: ESURF & TARGET170/CONTACT173 elements...
Author: Mark Rodamaker
Date: 2000-11-30 04:44:00

Just a further comment on creating contacting elements by "esurfing". This
is definitely the preferable way to create these contact elements because
esurf will always orient the contact elements facing out from the underlying
solid elements. If you were to amesh the areas, the elements would be
oriented the same as the area which would not necessarily be pointing
outwards. Proper oreintation is necessary for the contact elements towork
properly.

Mark Rodamaker
MCR Associates
Sunnyvale,California
voice: 408-736-1636

----- Original Message -----
To:
Sent: Thursday, November 30, 2000 6:42 AM

> Chris Andersen wrote:

> > Jim:

> > The contact elements are not associated with the areas.

> I agree with Chris and want to point out one subtle detail. The reason
> that the elements are not associated with the underlying areas is
> because the elements were generated with the ESURF command, not because
> they are 'contact' elements. ESURF basically does a 'direct' generation
> of elements from the underlying pattern of selected nodes and elements.
> I.e. it is similar to creating elements by hand via the 'E' command, in
> contrast to using the various 'MESH' commands, which do associate the
> nodes and elements with the underlying solid model entities.

> > I don't see a problem with deleting some 170's and 173's, but I've
> never
> > done this before.

> > Chris Andersen
> > DRD Technology

> I concur with Chris on this. Since the elements created via ESURF are
> not associated with the underlying solid model entities, there is no
> reason why you cannot delete some/all of them in order to reduce the
> geometric size of the region involved in the contact calculations. In
> fact, I believe that I may have done this on occasion.

> > > -----Original Message-----
> > > From: JPatterson@h...
> > > [SMTP:JPatterson@h...]
> > > Sent: Monday, November 27, 2000 10:53 AM
> > > To: xansys
> > > Subject: [xansys] ESURF & TARGET170/CONTACT173 elements...

> > > Hello All,

> > > I have a question about the ESURF command and it's application to
> > > TARGET170
> > > and CONTACT173 elements. Here's the situation...

> > > 1. I have a shell model with certain regions requiring contact
> elements.
> > > 2. I select the areas of interest, which are already meshed with
> > > SHELL63's,
> > > and use ESURF,,TOP to mesh them with 170's or 173's as required.

> > > Now my questions...

> > > 1. Are these new elements associated with the areas? It seems like
> if I
> > > select the areas, and then use ALLSEL,BELOW,AREA, I get the 63's,
> but not
> > > the 170's or 173's.
> > > 2. If they aren't associated with the areas, is there anything wrong
> with
> > > deleting "extra" 170/173 elements from these areas? By extra I mean
> any
> > > elements that are created by ESURF that are part of the area, but
> that I'm
> > > sure won't be involved in the contact (i.e. elements outside the
> common
> > > region of the areas that should come into contact). It seems like
> > > sometimes I can, and sometimes I can't delete them, which is adding
> to my
> > > confusion.

> > > Thanks in advance,

> Mitch Voehl Email: voehl@c...
> Engineering Consultant

> CEC Corporation WWW: www.concurrent.com
> 4640 Slater Road, Suite 112 Phone: 651-894-1863
> Eagan, MN 55122 Fax: 651-894-1818
> (Call to alert us to pick up the fax)

Posts possibly associated with message #18506AuthorDateScore
18310ESURF & TARGET170/CONTACT173 elements...Jim Patterson2000/11/27 
18312Re: ESURF & TARGET170/CONTACT173 elements...Chris Andersen2000/11/27 
18466Re: ESURF & TARGET170/CONTACT173 elements...Mitch Voehl2000/11/30 
18506Re: ESURF & TARGET170/CONTACT173 elements...Mark Rodamaker2000/11/30