XANSYS Message #: 26595

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

Subject: Re: IGES Import on HP-UX 11.0: defeaturing vs. non defeaturing
Author: Markus Lengauer
Date: 2001-08-01 03:44:00

Agree, Cadfix is the quickest and cleanest, although not the cheapest solution therefore. nevertheless, the designers facial expressions after having been asked for a 'better quality iges file' is always worth a look ;) Dipl.-Ing. Markus Lengauer - Technische Berechnung FH Joanneum GmbH Studiengang Fahrzeugtechnik / Automotive Engineering Alte PoststraÃŸe 149 8020 Graz Tel.: +43 316 5453-8413 Fax: +43 316 5453-8401 e-mail: markus.lengauer@f... ----- Original Message ----- To: Sent: Wednesday, August 01, 2001 9:14 AM defeaturing > Usually this kind of error is associated with a bad IGES file. I would > suggest to try using a different workstation, some times it works, or to try > to repair the IGES in a CAD code (Pro/E does a goof job most of the times) > or CADFIX, with works great in 90% of the cases. > Of course the best solution will be to go back to the designer and ask him > to provide a better quality IGES file. If he will be able to regenerate his > part with an accuracy lower than 0.001 will work out great. > What I have used to do, I always asked the CAD guy to read first the IGES > back in the CAD and see the quality. > If the CAD geometry is bad, then you should try CADFIX anyway. > Also, as far as I know ARFILL is an ANSYS command, available in the IGES > database, when imported with the defeaturing option on, so it might be > useful. > Hope this helps. > Kind regards. > Bogdan Balasa > General Manager > INAS SA > 1 Tehnicii Street, 1100 Craiova, Dolj > Romania > Tel: ++40 51 438 789 > Fax: ++40 51 438 906 > E-mail: bbalasa@i... > ----- Original Message ----- > From: "Thomas Kipf" > To: > Sent: Wednesday, August 01, 2001 10:04 AM > Subject: [xansys] IGES Import on HP-UX 11.0: defeaturing vs. non defeaturing > > Hi fellow list members, > > when trying to import iges files with the non defeaturing option, > > ansys crashes with a segmentation violation message. > > Is this a known HP-UX 11.0 problem? With 32bit HP-UX import seemed > > to be more stable. > > Switching to the defeaturing option leaves me in a trap: > > ANSYS suggests to use ARFILL in order to repair the geometry, but as You > > probably know, the database created with the defeaturing option doesn't > > allow me to perform any prep7 action. > > There is just 1 area left to create in order to get a closed volume ... > > Thus, if only ANSYS would let me perform the AL or A command, things > > would be o.k. > > CDWRITE didn't do the trick, because no IGES export is possible with > > this kind of database > > Any hints would be highly appreciated > > Kind regards > > Tom > > Thomas Kipf > > Ulmer Str. 130 > > D-73431 Aalen > > Tel.: 0049-(0)7361-931838

Posts possibly associated with message #26595		Author	Date
`26590`	`IGES Import on HP-UX 11.0: defeaturing vs. non defeaturing`	`Thomas Kipf`	`2001/08/01`
`26593`	`Re: IGES Import on HP-UX 11.0: defeaturing vs. non defeaturing`	`Bogdan Balasa`	`2001/08/01`
`26595`	`Re: IGES Import on HP-UX 11.0: defeaturing vs. non defeaturing`	`Markus Lengauer`	`2001/08/01`
`26596`	`Re: IGES Import on HP-UX 11.0: defeaturing vs. non defeaturing`	`Markus Lengauer`	`2001/08/01`