Installing & Configuring CoDesigner

Parent page: ECAD-MCAD CoDesign

Supported MCAD Software

The following MCAD platforms and versions are currently supported:

• Autodesk Inventor Professional®
• Autodesk Fusion 360® (Microsoft Windows version only. Fusion 360 Personal license only supported by Altium CircuitMaker)
• Dassault Systemes SOLIDWORKS® (Standard, Pro & Premium)
• PTC Creo Parametric®
• Siemens® NX™ - (for designers with an Altium Enterprise Solution)

Installing and Configuring CoDesigner

Altium CoDesigner is an interface for transferring printed circuit board designs between the ECAD and MCAD design domains. Once the CoDesigner extension/add-in has been added to the ECAD and MCAD software, CoDesigner can pass design changes back and forth. Design changes are passed through an Altium Workspace, which acts as a bridge between the ECAD and MCAD domains, as shown below.

Installing the CoDesigner Extension and Add-In

• The MCAD CoDesigner extension is included in the standard Altium Designer installation, so the MCAD CoDesigner panel is always available in the PCB editor.
• To access the Altium CoDesigner panel in your MCAD software you must install an Add-In, as detailed in the relevant Preparing for CoDesign page, listed below. You can download the MCAD CoDesigner plugin for your MCAD software from the Altium website download page.
• Refer to the Note in the right-hand pane for information on which features will be available in your installation of MCAD CoDesigner.

Installing CoDesigner in your MCAD software

Use these links to access detailed information about installing and configuring CoDesigner in your MCAD software.

• Preparing AutoDesk Fusion 360 for CoDesign
• Preparing AutoDesk Inventor for CoDesign
• Preparing PTC Creo for CoDesign
• Preparing SOLIDWORKS for CoDesign
• Preparing Siemens NX for CoDesign

Updating the MCAD Add-In

The MCAD Add-In includes an Auto-Update feature. During start-up, the following dialog will appear automatically whenever a newer version of the Add-In is available for your MCAD software.

The MCAD Add-In can also be updated by downloading a new version from the Altium website download page and installing it over the top of the current Add-In.

CoDesigner License Usage

CoDesigner is included as part of your Altium design software, so there are no additional licensing requirements on the ECAD side.

On the MCAD side, license usage depends on the type of Workspace that CoDesigner is connecting to:

• Altium 365 Workspace - the CoDesigner MCAD Add-in does not consume a license. 
• Altium Enterprise Server Workspace - the CoDesigner MCAD Add-in consumes an Altium license CAL (Client Access License) when you sign in to the Enterprise Server Workspace via the Altium CoDesigner panel in your MCAD software. All CoDesigner features are available when you use an Enterprise Server Workspace.
• Concord Pro Workspace - the CoDesigner MCAD Add-in consumes an Altium license CAL (Client Access License) when you sign in to the Concord Pro Workspace via the Altium CoDesigner panel in your MCAD software. All CoDesigner features are available when you use a Concord Pro Workspace.
• NEXUS Server Workspace - the CoDesigner MCAD Add-in consumes an Altium license CAL (Client Access License) when you sign in to the NEXUS Server Workspace via the Altium CoDesigner panel in your MCAD software. All CoDesigner features are available when you use a NEXUS Server Workspace.

Configuring your Workspace Settings

Accessing your Workspace in your Browser

CoDesigner transfers PCB design changes through a Workspace. To check and change your project and team settings, you can log in to your Workspace via a web browser. The approach you use to log in depends on how your Workspace is hosted. An Altium 365 Workspace is hosted on Altium 365, in the cloud. You can also use an Altium on-site Workspace, such as an Enterprise Server Workspace.

Your Workspace can be configured and managed through a web browser.

Configuring the Workspace Members

Each person who needs access to your shared Workspace (directly, or from a design open in their ECAD or MCAD software) must be added to the Workspace Members and assigned a Role that gives them the appropriate permissions to access the files stored in the Workspace. Although their interfaces are slightly different, the process for adding a team member and assigning a role is essentially the same for an Altium 365 Workspace or an on-prem Altium Workspace, such as an Enterprise Server Workspace. These tasks are performed in the Workspace web interface, accessed through your preferred browser.

Adding New Members and Assigning Roles

The approach is to Invite Workspace Members (Users in an on-prem Server Workspace). As part of adding the team member, they can be assigned a Role; such as Mechanical Engineer, Librarian, Engineer, and so on. New Roles can also be defined. The image below shows where you add a new team member to an Altium 365 Workspace. The process is similar in on-prem Workspaces.

Check your team members and assign their roles.

► Learn more about Managing Your Team in an Altium 365 Workspace

► Learn more about Adding Users and Assigning Roles in an Enterprise Server Workspace

► Learn more about Adding Users and Assigning Roles in a Concord Pro Workspace

► Learn more about Adding Users and Assigning Roles in a NEXUS Server Workspace

Configuring the MCAD Component Model Naming

As CoDesigner converts each component to a Parasolid model, they are named using the following scheme:

<Footprint Name>_<ComponentDesignItemID>_<ItemRevision>

The following special characters, along with other control symbols, are replaced with an underscore (_):

\, /, :, %, [whitespace], |, [, ], *, ", ', \t

The default naming scheme used for component models.

Controlling the Naming of Component Models

CoDesigner supports four options for controlling how component models are named, during their initial transfer from ECAD to MCAD:

1. <FootprintName>, then <ComponentID> (the default mode)
2. <ComponentID>, then <FootprintName>
3. <FootprintName>, then <CustomComponentProperty>
4. <CustomComponentProperty>, then <FootprintName>

Configure the Naming of Component Models option in the MCAD CoDesigner section of the Workspace Settings.

Select the Naming option and if it includes a Custom Component Property (parameter), define the parameter name.

These options simplify the interaction with the components in MCAD, allowing the MCAD engineer to add meaningful information such as part numbers into the Component ID, or the ECAD engineer can add a Custom Component Property in the ECAD component library.

The MCAD model is named based on the naming option configured in the Workspace.

Configuring the ECAD-MCAD Component Linkage

Main page: Linking Native ECAD and MCAD Design Components

Refer to the Note in the right-hand pane for information on feature availability.

One of the challenges of transferring design data between the MCAD and ECAD environments is managing how the components are transferred. In many companies, the ECAD and MCAD teams create and manage their own separate component libraries and need to be able to link between the MCAD and ECAD versions of that component.

The default behavior is when a design is Pushed from either the MCAD or ECAD domains, CoDesigner converts each component to a Parasolid format model and stores them all in the Workspace. When that design is Pulled, CoDesigner then builds a model of each component in the format required by the target tool. This approach gives an accurate representation of each component in both the ECAD and the MCAD design spaces. The disadvantage of this approach is that the model may not fully represent the component as it needs to be represented in that tool. For example, when a design is Pulled into Altium Designer the component will not include the pads, silkscreen, and other entities typically included in a PCB component. Nor will it be linked to a schematic symbol, or into the supply chain.

To manage the requirement for each design tool to be able to use native components, CoDesigner supports linking between the MCAD and ECAD components. The links are defined in the Workspace, which acts as a bridge between the ECAD and domains.

Configuring the Component Linkage in an Altium 365 Workspace

MCAD to ECAD and ECAD to MCAD component linkage is enabled and configured in your Workspace. This image shows a workspace hosted on Altium 365.

Configuring the Component Linkage in an On-Prem Enterprise Server Workspace

MCAD to ECAD and ECAD to MCAD component linkage is enabled and configured in an on-prem Enterprise Workspace.

► Learn more about Linking Native ECAD and MCAD Design Components

Where to Next?

Now that CoDesigner is installed and your Workspace is configured, you're ready to start exploring the process of transferring your design between your ECAD and MCAD software.

► Learn more about Direct ECAD-MCAD Design with Altium CoDesigner