XANSYS Message: 201 [Go back to message list]
[bookmark on del.icio.us]
No rating yet
Subject: Re: *GET,AREA
Author: John Swanson
Date: 1999-01-13 14:00:00Make sure you look at _ERROR right after the *GET
command. Any new command will reset it to zero.
For example, after *MSG it would be expected to be
zero, since there was no error in the *MSG command.
John
> -----Original Message-----
> From: Jean-Pierre Dube [SMTP:dubejp@n...]
> Sent: Wednesday, January 13, 1999 1:04 PM
> To: 'xansys@o...'
> Subject: [xansys] Re: *GET,AREA
> From: "Jean-Pierre Dube"
> John,
> I checked _ERROR
> It is always zero as well.
> I definitely get a warning though.
> I'm running 5.4 so maybe this is fixed in 5.5.x
> I'll have to re-think my approach.
> Thanks,
> Jean-Pierre Dube
> 0Q64 MCAD Tools and Methods
> Nortel Networks
> (613) 763-8019
> dubejp@n...
> > -----Original Message-----
> > From: John Swanson [SMTP:John.Swanson@a...]
> > Sent: Wednesday, January 13, 1999 7:44 AM
> > To: 'xansys@o...'
> > Subject: [xansys] Re: *GET,AREA
> > From: John Swanson
> > Look at _ERROR. If a warning was produced, _ERROR should be 1.
> > (It is 0 if no error, 1 for warning, 2 for error.)
> > John
> > > -----Original Message-----
> > > From: Jean-Pierre Dube [SMTP:dubejp@n...]
> > > Sent: Tuesday, January 12, 1999 8:12 PM
> > > To: 'xansys@o...'
> > > Subject: [xansys] Re: *GET,AREA
> > > From: "Jean-Pierre Dube"
> > > I guess ANSYS assumed that the *GET.....LOOP... would
> > > only be used by those who had created the areas,
> > > (But then you really don't need the *GET)
> > > If you try this
> > > *GET,l1,AREA,arg1,LOOP,1,LINE,5
> > > *MSG,INFO,5,l1,_STATUS
> > > position %I has line %I stat %I
> > > where the AREA arg1 has only 4 lines in loop 1
> > > you get a warning but _STATUS is always
> > > zero.
> > > Of course this is absolutely useless.
> > > Jean-Pierre Dube
> > > 0Q64 MCAD Tools and Methods
> > > Nortel Networks
> > > (613) 763-8019
> > > dubejp@n...
> > > > -----Original Message-----
> > > > From: Crawford, John [SMTP:John.Crawford@a...]
> > > > Sent: Tuesday, January 12, 1999 12:50 PM
> > > > To: ANSYS Users List
> > > > Subject: [xansys] Re: *GET,AREA
> > > > From: "Crawford, John"
> > > > I believe that the outer loop is always number 1. At least
> that's
> > > how
> > > > it's been when I've played around with this. Loops 2 through N
> are
> > > > internal. I have no idea how their order comes about, other
> than by
> > > the
> > > > sequence that the holes are created. Holes are made by Boolean
> > > > operations. Of course, we all think it would be cool to make
> > > multi-loop
> > > > areas. It's been known for some time that this can be done with
> an
> > > > undocumented command. I have clipped the following writeup from
> the
> > > > undocumented commands and secrets section of our AlliedSignal
> > > Toolbar.
> > > > John Crawford
> > > > AlliedSignal Engines
> > > > Phoenix, AZ
> > > > john.crawford@a...
> > > > * CREATE AREAS WITH HOLES IN THEM
> > > > ANSYS has an undocumented command for creating areas with
> holes in
> > > > them.
> > > > It's called "allp" and supports up to 4 internal loops and one
> > > > external
> > > > loop. Here's how to use it.
> > > > allp,3,1,3,4,7,11,14,6,8,9
> > > > where 3=the number of total loops (one external, two internal)
> and
> > > the
> > > > other
> > > > numbers are the line numbers in random order, but continuous
> for
> > > each
> > > > loop.
> > > > This means that loop one would be lines 1,3,4, loop two would
> be
> > > > 4,7,11, and
> > > > loop 3 would be 14,16,8,9. The listing of the lines can be
> random
> > > > within
> > > > each loop, but each loop must be grouped together.
> > > > From: Jean-Pierre Dube
> > > > To: 'xansys@o...'
> > > > Subject: [xansys] *GET,AREA
> > > > Date: Tuesday, January 12, 1999 1:21PM
> > > > From: "Jean-Pierre Dube"
> > > > APDL People,
> > > > *GET,l1,AREA,a1,LOOP,loop1,LINE,pos1
> > > > is documented as returning in l1 the line
> > > > number of the line at position pos1 of loop1 of
> > > > Area a1.
> > > > How do you find out how many loops and then how
> > > > many positions each loop has for an area?
> > > > Is the outer loop identified in some way? i.e. is it
> > > > always loop # 1
> > > > Thanks,
> > > > Jean-Pierre Dube
> > > > 0Q64 MCAD Tools and Methods
> > > > Nortel Networks
> > > > (613) 763-8019
> > > > dubejp@n...