Cancel
Showing results for 
Search instead for 
Did you mean: 

How to set default IMAN RELATION for Direct Model in different CAD systems

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Experts,

 

Customer wants to use MultiCAD based on JT - Direct Model.

Process is, that 3D data created in SolidWorks will be used in NX or Solid Edge - it works, NX, SW or SE can open DirectModel and vice versa (if preference foreign_dataset ... is set correctly)

 

Issue is, how to set common IMAN Relation for DirectModel. SWIM need DirectModel in IMAN_Specification relation (it looks like hardcoded), but OOTB is IMAN_Rendering (if NX or SolidEdge create DirectModel during save). So, we want to set relation between ItemRevision an DirectModel to IMAN_Specification for NX, SE, SW.

 

Who knows?

 

Thank you in advance.

 

 

4 REPLIES 4

Re: How to set default IMAN RELATION for Direct Model in different CAD systems

Phenom
Phenom

In SolidWorks this is controlled by the swim.xml:

Capture.JPG

Cheers,

Rich

Richard Bennett
Prospect PLM

Re: How to set default IMAN RELATION for Direct Model in different CAD systems

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Hello Rich,

 

thank you, what about NX and Solid Edge, there is not any xml configuration file. So is it there any preference?

 

thank you in advance.

Highlighted

Re: How to set default IMAN RELATION for Direct Model in different CAD systems

Siemens Genius Siemens Genius
Siemens Genius

Hi,

 

Let me explain a few things about the SolidWorks integration's MultiCAD support, first introduced in the latest 12.0.0 version, requiring the Enterprise-level license (TC030506).

 

The feature is oriented toward 'direct' reuse of non-native CAD models, because for SolidWorks, this has significant value over 'indirect' reuse, where the non-native CAD models are first translated to a neutral format, such as JT, and then referenced into your native SolidWorks assemblies.  Namely, 'direct' reuse of SolidEdge, Creo, Inventor, and possibly other MCAD allows us to leverage the SolidWorks 3D Interconnect technology, to support a truly associative MultiCAD capability.  As non-native models are changed in their authoring tools, mates and other constraints are automatically adjusted in the SolidWorks assembly.   Today this is not possible with indirect formats such as JT, and we are not aware of any future SolidWorks plans to support it.

 

As of today this strategy works well with Creo, SolidEdge and Inventor, although we have a couple of gaps due to SolidWorks API limitations, and we are working to get those filled.  We do have serious issues with both JT and NX files.

 

  • You've already identified one of the major JT limitations.  The integration is hard-coded to follow only the IMAN_specification relation, and JTs are usually attached with a Rendering relation.  This is something we can and will fix, in a future release.  The other limitation is that SolidWorks will only open part-level JT files, unless the integration builds the JT assembly structure on-the-fly (as we do with the Creo integration).   Once again, we are developing plans to fill this gap.
  • With NX, we face a more challenging situation, because NX is hard-coded to append the revision extension to its CAD files.  Outside of the NX integration, this means that the component file names will change based on the revision rule selected, and this makes them unrecognizable to a SolidWorks assembly that was last saved while referencing a different set of NX files.  For example, if you start with an NX assembly where every component is at revision A, add that to a parent SolidWorks assembly, and save the SolidWorks assembly, what happens when the NX parts are revised to B, C, D, and so on?  The next time the assembly is opened with a revision rule that does not select the Precise clause, a combination of *_B, *_C, *_D, etc. NX parts are downloaded, and the NX assembly is broken, both in standalone NX and in SolidWorks.  I have an ER9348877 requesting NX support for suppressing the revision extension on its file names, but in the meantime, it is likely that we will only be able to reuse NX parts and assemblies in their JT representation, by filling the JT gaps outlined in the previous paragraph.


In summary, today you should be able to reuse SolidEdge design data directly in SolidWorks, without relying on the JT file format.  As you've already noted, the required configuration settings are documented in the Admin guide.  For NX support, I would ask you to submit an enhancement request against the SolidWorks integration, so that we can link our internal planning to real customer requirements for MultiCAD reuse.

 

Thanks,

Paul

 

 

Re: How to set default IMAN RELATION for Direct Model in different CAD systems

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Hello Paul,

 

thank you for exhaustive answer!