There can be various reasons for this problem:
A Datakit user account enables you to access all features offered by Datakit.Register as end user to:
In the register form, we ask you to select an account type.
A dialog box will appear with the mention 'part not found a and the reference of the part'.
Then, our solution allows you to choose one from the 3 available options :
- cancel : give up to look for the file
- do not display this dialog box anymore - as a consequence it will no more appear during the current session
- add files. Our solution will look for the file in the mentionned directory.
While using Datakit exchange menu, you can either decide to search or not to search missing files. It is an option.
It was important for us to make sure that the structural matches between Catia V5 and Inventor were maintained, but we also wanted to address cases a structural difference between the two environments: for example, Inventor considers a Catia V5 Cat.Part containing multibodies as an assembly.
It understands the different types of Catia V5 assembly and supports the assembly tree structure. This includes the following assembly types:
All the names used in Catia V5 are kept in the Inventor iam or ipt files.
Designers often see importing data as a laborious, uncreative chore. Automation helps creative people to save precious time and energy. Don't forget that this plug-in has a further advantage: Rhino users do not need a Catia V5 licence in order to run it. Users can opt to import all the available files in a list without wasting time moving files, or selecting them from a directory.
Sub directories will aso be procesed if that's what the user initially chose to do.
The interface processes all Catia V5 entities, assemblies, topological, surface, and wireframe data and attributes.
CATParts, CATShapes and CATProducts can all be imported. With the directory mode, users can also confine processing to just the file types they are particularly interested in.
The results of the conversion (.3dm) are stored in the same directory as the original files unless the user specifies another location.
FD&T are not indispensable at every design stage. They can even unnecessarily crowd the information displayed on the screen. The option box saves users the trouble of going into configuration files. All you have to do is to specify in the box whether or not you want to keep the FD&T.
If the designer initially chose to hide or to desactivate the FD&T in the construction tree, we can force the processing of FD&T data (even when it is invisible or deactivated). We try to respect the Catia format as scrupulously as possible while leaving users the freedom to choose the data they want to process.