Modeling prerequisites - Solid Edge

Version 4

    An Important Note

    As of VeSys 2.0 2016.1 SP1710, integration with Solid Edge ST9 is supported and qualified. This is a Wiring only flow. A Harness flow is in the road map.

    While the wiring integration is not qualified with ST10, or ST8 and lower, we expect that the flow will work.

    If you need explicit qualification, please contact Mentor Support.

    Capital currently does not support Solid Edge.


    As changes or additional support is added, this document will be updated.



    Here is a link to a video that explains the flow.  In the video, we indicate some prerequisites currently required for the VeSys 2.0 - Solid Edge wiring flow. These are also described below. As the integration is matured over time, we expect to do away with some of the prerequisites.


    Modify SEHarness.txt

    In your Solid Edge installation, edit <SE_install_folder>\Siemens\Solid Edge ST9\Preferences\SEHarness.txt.

    Add the highlighted Connection Definition:


    Copy to

    Navigate to C:\MentorGraphics\VeSys\adaptors\resources folder, and copy the file to


    Typically the * files in the resources folder are updated in each Service Pack (SP) if new functionality is added that requires configuring or defect fixes require modification of existing property-value pairs.

    After a new SP is installed, it is good practice to do a file compare between your own file, and the to see if there are changes. If there are, you may choose to copy the new property-value pairs into your file.


    This file contains some property names that need to be on connection objects (wires, multicores and their innercores; nesting of multicores is not currently supported in Solid Edge). This is described in the video. We recommend you read the comments in the document carefully.


    Three properties are needed on wire and multicore objects. There are SE_Color, SE_Material, SE_WireType. 

    The SE_Material and SE_WireType values are to match exactly the values in the <SE_install_folder>\Siemens\Solid Edge ST9\Preferences\SEConductors.txt.

    The SE_Color value is to match the color number from Solid Edge. 


    Attached is a sample project and sample VeSys Components parts that you can use to test the flow. The project is designed in such a way that the exported .con and .cmp files will work exactly with the default Solid Edge Harness tutorial assembly.


    Handling Multicores

    Note that although VeSys supports nesting of multicores, Solid Edge currently does not.


    The handling of multicores between VeSys and Solid Edge will be enhanced in later service packs as the integration is made more robust. For the time being, the work around is slightly tricky. This is because VeSys Components can currently only assign a four letter Color Code, and properties cannot be added to the innercores of a multicore. In other words, it is not currently possible in VeSys Components to assign the SE_Color color value to innercores, so you will need to do a slight work around in Solid Edge.


    Import the MCPN1.xml into VeSys Components and take a look at its definition, both at the parent MC level and the innercore levels. The choices are made to match as far as possible the values of wires and cables existing in SEConductors.txt.

    Import the project xml from Solid Edge, and you will find an additional harness3 design. This is identical to harness2, except the wires are replaced with a multicore.


    When you import the .con and .cmp for harness3, and after you assign the terminals as needed, you will see in orange:


    Select the Solid Edge and Cable Attributes from their drop-downs, corresponding to the VeSys multicore description and the innercore color and spec, like so:


    When done, in thin (virtual) and physical mode, you will see the following:






    On the other hand, if you prefer to add the three required properties to the instance level of the innercores that is certainly possible, but is more time consuming.


    As and when improved multicore handling and other enhancements are added, this document will be updated.