We all know what a pain it can be to work with incompatible file types and applications. When you need to bring parts into your assembly that were designed using a different CAD system, you don’t want to lose important data, and you especially don’t want to deal with files that won’t load into your assembly at all.
But with PTC Creo 3.0, there’s good news. Not only can you successfully load parts into your PTC Creo assembly that were not designed using the same application, you can also use PTC Creo Simulate to run the following analyses:
Best of all, PTC Creo doesn’t create a new or intermediate file for each non-native file that you bring into your assembly. Try these examples out:
Suppose you previously set the material definition for your model, but then added parts that were designed in another CAD system. No problem. To apply the material definition to your entire assembly, including non-native parts, follow these steps.
Image: The Model Tree specifies which parts are not native to PTC Creo. For example, HALTER CATPART was designed using CATIA.
Suppose your assembly has defined constraints, loads, and material properties, you can perform an analysis on the entire assembly—even if it includes non-native parts. To perform the analysis, follow these steps:
Image: The analysis is applied to all of the assembly’s parts, including those that were designed outside of PTC Creo.
You can see a demonstration of these steps in the video below:
See more videos like the one above by visiting PTC University Learning Exchange. Note that you may need to create a PTC University Learning Exchange account if you don’t already have one. The good news is that it’s free and after creating your new login, you’ll find hundreds and hundreds more in-depth demonstrations and tutorials for PTC products.
Find a class