wrote:<BR>>
> >> David Geesaman
wrote:<BR>>
> >>> KA
wrote:<BR>>
> >>>>
Hi<BR>> >
>>>> Is it possible to remove a surface region in pro/m?
Thanks<BR>>
> >>>>
Konrad<BR>>
> >>> Yes. There is a group of
features only visible in Pro/M,<BR>>
>
unfortunately<BR>>
> >>> I don't recall the name of
that group. Any geometry and<BR>>
> surface
regions<BR>>
> >>> defined in the mechanica
environment can be found there.<BR>>
> >> Thanks Dave. That's Simulation
Features and I didn't have a<BR>>
> right-click<BR>>
> >> menu over my Surface Regions.
After an investigation I found<BR>>
> that it was<BR>>
> >> a family table instance, and the
regions were set up in<BR>> the
Generic.<BR>>
>
>><BR>>
> >>
Konrad<BR>>
> ><BR>>
> > Interesting, thanks for the
info. I would have tripped<BR>> over
that<BR>> >
too.<BR>> >
><BR>>
><BR>> > One
more interesting info: Material assignments in parts
were<BR>> meant
to<BR>> > be
detected and used in assembly pro/m. Meshing goes good,
but<BR>> >
sometimes<BR>> >
solver gets problems with stability of the structure. I
got<BR>> "the
model<BR>> > is
insufficiently constrained for the analysis" error many
times-<BR>> > and
it<BR>> > was
kinda hard to trace. It took me ages to discover
this<BR>> bug. Now
I<BR>> > alway
assign material at assembly level.<BR>>
> Konrad<BR>>
><BR>>
><BR>> > But then does the material
assignment show up in Pro/e for model<BR>>
analysis?<BR>> > <BR>>
<BR>> Normally, when an assembly's part has its
material assigned in part<BR>> only- you don't see
the assignment icon on screen. The whole
assembly<BR>> gets meshed. It wouldn't mesh if it
didn't have the material. And it<BR>> gets
calculated by the solver- but sometimes with
error.<BR>> If you assign the material in the
assembly- you have the yellow<BR>>
material<BR>> icon attached to the
part.<BR>> Konrad<BR>> <BR>> Sounds like the
necessary and superior way to deal with material <BR>> assignment for
Pro/M. Historically, (don't know if it continued into the <BR>> WF product)
Pro/M and Pro/e came with separate and completely different <BR>> material
files. I always assumed that Pro/M's were the most official and <BR>>
reliable; Pro/e's seemed more like a do-it-yourself project as they were
<BR>> distributed in dozens of individual, customizable ASCII files. No one
<BR>> who used the Pro/e material files ever assumed they were correct; you
<BR>> always has to check them and they were often wrong by several decimal
<BR>> places, especially after they'd been around for a while and units had
<BR>> been changed back and forth a few times or the files had been
manually <BR>> edited without record. So, even to get a complete and
accurate set of <BR>> material files to use in Pro/e, I've taken to
exporting Pro/M materials <BR>> to Pro/e while in the system of units of
choice. But, maybe this is <BR>> unnecessary. Maybe the material definition
"sticks" from Pro/M to Pro/e <BR>> and I don't need to give it ANOTHER
material assignment for Pro/e!?! <BR>> Would be nice, anyway, if Pro/M's
material assignment carried over into <BR>> Pro/e.<BR><BR>Thank you Dave
for the historical trait.<BR>The new philosophy is one material assignment for
pro/e (mass, bend <BR>table etc) pro/m (young modulus, poisson's ratio etc),
rendering <BR>(colours, decals etc). I would be happier to have possibility to
enter <BR>Young modulus as a function of temperature, because I have now
materials <BR>like "316L_forging_300F", "316L_forging_400F",
316L_forging_500F" and so <BR>on. Physically few grades, but in the end of the
day it makes hundreds <BR>of material files.<BR>Konrad<BR><BR>PS for the issue
of material not assigned in the analysed assembly in <BR>pro/m: sometimes it
gives also "internal error" message without any <BR>closer
explanation.</BLOCKQUOTE><BR>
<DIV><FONT face=Garamond>Don't know whether Pro/e-Pro/M will solve this
problem of many material states (seems like a table ought to apply
here). But I've heard that WF3 has at least unfied the material source files of
the two modules. Hopefully your customizations can be imported into the
database.</FONT></DIV>
<DIV><FONT face=Garamond></FONT> </DIV>
<DIV><FONT face=Garamond>David Janes</FONT></DIV></BODY></HTML>
------=