For the record: I made a quick and dirty utility to connect it to an empty part in a model. usually I would have tried to convert the CAD file to a Parasolids file and use it in a more elegant way (allowing export to a *.cmd file with only a singe parasolids file in stead of a wealth of *.shl files etc etc.).
I spent some time to try this on the *obj files but then half the CAD data was lost in the parasolids export/import. :(
Q's:
How much effort do you typically invest in making 'stable' parasolids CAD input files ?
Do you use tools like SimX or Apex to convert to parasolids CAD files, or do you typically import any CAD format and leave it like that ?
Importing CATParts internally converts it to parasolids; i.e. if you save the model from ADAMS, a parasolid file will be automatically created.
The geometry appears as "solid" when right-clicking, i.e. you can assign a density and will get a mass and/or you can use them for contacts.
On the downside model handling becomes severly affected with huge geometry (i.e. a fit command takes ages).
You can avoid that by using a mesher (I use ANSA) to create a wavefront (obj), import it into ADAMS and then export the created shell as a .shl file. Then open the "real" model and import the .shl. It will look the same than before, but handles much faster (also you could coarsen the geometry on meshing).
Sometimes you may get away with the option "consolidate to shells", but the outcome is usually not as pretty as what ANSA creates.
Only culprit here: The entity is now of type shell and cannot be used for all contacts as before.
It's like always in life: You can't have the cake and eat it ...