Since it supports multiple stages of product development from conceptualization, design and engineering to manufacturing, it is considered a CAx-software and is sometimes referred to as a 3D product lifecycle management software suite. Like most of its competition it facilitates collaborative engineering through an integrated cloud service and have support to be used across disciplines including surfacing & shape design, electrical, fluid and electronic systems design, mechanical engineering and systems engineering.
Besides being used in a wide range of industries from aerospace and defence to packaging design, CATIA has been used by architect Frank Gehry to design some of his signature curvilinear buildings[2] and his company Gehry Technologies was developing their Digital Project software based on CATIA.[3]
Dassault Systmes purchased CADAM from IBM in 1992, and the next year CATIA CADAM was released. During the nineties CATIA was ported first in 1996 from one to four Unix operating systems, and was entirely rewritten for version 5 in 1998 to support Windows NT.[9] In the years prior to 2000, this caused problems of incompatibility between versions that led to $6.1B in additional costs due to delays in production of the Airbus A380.[10]
i would like the opinion of some Catia V5 surfacing guru. I just had a conversation with a master of class A surfacing on Catia V5 and his assessment was that Rhino to Catia in STP ( forget IGES it s crap we all know that ) the rhino surfaces are not that great. Work needs to be redone in some instances.
From my experience I didn t find it horrible. I was pretty satisfied ( maybe I m not as perfectionist as others or I m completely missing something) But are there any Catia V5 surfacing guru who sees that working with Rhino surfaces is not ideal ? and why exactly ?
Yeah i Guess you guys are right. I also had in the past had to clean up catia surfaces before sending it to a cnc. Too many gaps. I guess i m a bit paranoid. But one thing i noticed is that exported rhino surfaces are broken in multiple surfaces in Catia, whereas Alias surfaces come out really nice in Catia. Yet they re all Nurbs surfaces.
Agreed, i d like to look at the surfaces. I m surprised to hear that some experts in Catia say they need to rework rhino surfaces but are happy with Alias surfaces. They say rhino surfaces are broken down into much smaller ones in Catia.
We used Icem previously moving away from it due to the yearly maintenance costs, instead we purchased the Rhino plugins called VSR before they were purchased by Autodesk. We are also users of Catia, Unigraphics, Ideas and Creo.
The good point on Rhino is the direct and easy modification of a NURBS surface like in Blender and the easy transformation of a curve or surface from one degree to an other.
The good point on Catia was/is the easy analyse of the curveture by a section through the surface. But in those time Catia had problem generate or keep a closed a highlevel non-uniform surface pipe with a kink or without a kink. Every time it broke up the pipe by an Iso-line.
To add even more confusion I found that if I used code to generate my CATIA surfaces they sometimes seemed to be of higher quality with fewer IGES export issues that the same surface made the traditional way.
I remember wHen i imported Catia V 4 to rhino v3 and then rhino v4 it was a nightmare. I would import surfaces broken down into tiny tiny ones and hundreds to clean up as well. Catia v5 improved because it was working on windows platform wHereas catia V4 was Unix based. Airbus had huge problems with the a380 design because the french were using v5 and germans were on v4. I wonder how Alias does it. Never heard people complain when importing in CatiaV 5.
Hello All,
I'm having a problem with importing Catia v5 files. As I import them the ipt files are all empty, but I'm 100% sure that the Catia files are ok and I used to make imports like this a couple of times with no problam. Has anybody faced this problem? Is there a fix or a method to import Catia files correctly? I'm using Inventor 2014 Service Pack 2 Update 8.
In your Inventor browser there should be a 3rd party report on the translation (just below the browser name of your file). Expand and click on the report. It should provide you with the translation info, expand the report and it should tell you what has happened. Post an image here of the info and we can tell you what's going on if you don't understand the info.
In the Translation Report the status is "Error". I have already tried to import it on more PCs with nearly the same configuration and all of them fails. It creates the ipt file (it is set to save during import) but there's nothing in it and there's no error message during the import.
You were right, I haven't expanded it... Unfortunately it says it is not supported file format.... however I would expect other warning during the import from Inventor....
Anyway, thanks for you help...
Hi! You could either upgrade to newer Inventor releases which support this version of Catia V5. Or, you could use A360 to translate the Catia file and export it to STEP, which you could import to Inventor 2014.
Hi!
Thanks for you help, unfortunately I can't use newer version of Inventor. But the A360 could be a good solution, but I can't find where can I export the file in different filetype. As I searched about it I saw screenshots that when you click on the download button, a list shows up and you can select the file type you would like to download. Is it an old feature and not available now or is there a setting where you can select STEP?
We run loads of different CAD packages with our Windchill System but are having problems with just one of them - CATIA. Since our recent upgrade to WC 12.0.2 and WGM version 12.1.2.0 our CATIA (particularly V5-6R2017) users working on large assemblies are suffering continual freezing/lockups of the WGM and CATIA. Which stops them working until it unfreezes - ranging from 3 to 30 minutes with no warning. The WGM and CATIA usually come back (not always) but this intermittent, can affect just small bracket parts as well as large assys. The CAD users say the behaviour has changed since WGM 12.1 as now CATIA freezes when the WGM freezes - whereas they could continue to work in CATIA at WC11.0 whilst the WGM was doing a background refresh.
We are not sure what the WGM &CATIA is doing to cause the freezing - it occurs on the regular half hour Workspace Refresh (sometimes these will complete in a second with no issue, then next time it will freeze for 5 minutes with the same models open). We also see long freezes in CATIA and WGM on Check-In / Check-Out and Opening.
Our Windchill App & SQL Servers are fine and so are the network links - indeed Creo/NX users report no performance issues, it only affects CATIA users. We have tried tweaking the various WGM preferences for refresh, item rename etc. but to no avail). We use a new Workspaces at least once per day,
We suspect that this gets more frequent the more members in the team are Checking-In / Modifying data as we approach design Gateways that have to be met. We also wonder whether this has to do with inter-part linking - as we suspect that the WGM struggles with this (any best practices to recommend here?). We also wonder whether it could be to do with updating multiple child parts and their siblings across the design team without updating the assembly that contains them (any best practice to share here)?
I have a call with PTC Tech support and have uploaded logs capturing the issues, but they have not been very forthcoming yet - so I thought I might raise this with the experts in the Community. Also, PTC are not likely to be experts at using CATIA with Windchill - us end-users may know more.
Unfortunately, we have to work in our customer's CAD package and version (Ricardo is an Engineering Consultancy), so upgrading CATIA version is not a solution for us (I think it unlikely that this is a CATIA version specific issue FWIW).
We originally had the issue at 12.1.1.0 WGM, and have had to upgrade affected users to 12.1.2.0 WGM (so we were on a supported config) in case that fixed the issue (it didn't) and so that I could log a call with PTC about the issue.
Am a bit stuck really because the WGM is not very informative about what it is doing most times with CATIA - it just locks up and looks like it has crashed, but usually comes back in time (trouble is you don't know if it will, nor how long to give it before you crash it out). What is more frustrating for the users is the CATIA hang since WC12 - they tell me that at WC11, they could continue working in CATIA whilst the WGM was doing a workspace refresh, now they can't and they are at stop waiting for it to come back.
Windchill 12.0.0.0 is also not a long term version but i still think the compatibility of R2016 and R2017 is strange. If i were you, i would install at least R2019 or latest R2022 on a test computer and check.
Unfortunately, the design team is at full stretch trying to hit an urgent Gateway - so they don't have the capacity to take someone off of the team to save the Assembly as a different version of CATIA into our TEST Windchill system and then work with it to see if this fixes the issue. Especially as (even if it did fix the issue) we could not supply the customer with models in this newer version - the project has to be carried out in CATIA 2017 version.
TBH, I don't think this is the same behaviour that my users are seeing - it seems to be related to WebGL (which is not involved in the WGM/CATIA), and my user's WGM's do (usually) come back from their freeze ups (eventually).
Unfortunately, we cannot install/run any versions of WGM older than 12.1.1.0 - due to the three high severity Chromium embedded browser security issues which were fixed in that release, and which are present in all previous releases.
WebGL is the 3D Graphics rendering engine in Chromium (and other browsers) that provides the interactive 3D Creo View model in the Structure Tab in the Windchill web page (per the article you linked to). WebGL is not used to render the the default /working view of the WGM to display workspace contents - so its unlikely to be related.
7fc3f7cf58