You will reduce the work on editing these components in Altium Click the Validate button to check for possible errors that may be caused by the migration. In this case, you will need to disable links to footprints in the migrated library manually.
To do this, open the library file. In the lower grid, right-click on models with Footprint types then select Remove from the context menu.
After correcting errors and warnings, click the Migrate button in the Library Migrator. After the migration is complete, a window opens, stating the migration was successful and displaying the total number of components, models, and templates that were migrated. The steps to migrate an integrated library are the same as described for migrating project libraries in the Migrating Project Components Chapter. It is important to note that any libraries available to users are capable of being migrated to Altium , such as libraries from a particular project, database libraries, libraries from the manufacturer's website, and libraries included with the installed software, etc.
Learn more through our comprehensive documentation. Choose your Topic Opening and Saving Projects. Migrating Project Components. Altium Workspace Organization. Watch Video Component Search and Placement. Component Properties in the Schematic Editor. Replacing Placed Components. Watch Video Project Release to Manufacturing.
Reviewing Projects in Your Web Browser. Migrating Libraries To Altium Watch Video Creating a New Component. If you've created components from the data in these libraries, you can also access these parts through the Components Panel in Altium Designer. However, there may be a time when you still need to send a library file to a collaborator or client. In this case, you need to download component data from your Workspace as an SchLib file or PcbLib file.
If you go into your Workspace through the web instance or the Explorer panel, you can still download a specific set of symbols or footprints as library files and hand these off to another designer. Once you select the data you need, it can be saved to your local machine as a PcbLib file for PCB footprints or as a SchLib file for schematic symbols.
To do this through Altium Designer, navigate to your managed Symbols or Footprints folder and highlight the group of components you need. Once you enter a filename and click Save, the component data will be downloaded to your local machine and can be imported into any new Altium Designer project. The image below shows a typical footprint for a 6-pin connector that would be used for multiple sensors.
Other symbols have selected for download as well. You can use these symbols to create brand new components within the Explorer Panel or with the standard parts creation tools in Altium Designer.
Simply select the symbols or footprints you want to use during component creation. If your component data originally included sourcing information, it will be visible within your supply chain management tools and can be imported into your bill of materials when you create a project release.
The steps shown above provide a simple way to quickly compile new symbol and footprint libraries directly from data stored on a shared server. Once these components are in your Workspace, you can access these components through the Components Panel in Altium Designer and start placing them in your design documents.
To learn more about this process for library migration, take a look at this tech doc for guidance. Rather than emailing copies of libraries to your design team, simply use the features shown in this tutorial within Altium Designer. Altium Designer on Altium is bringing an unprecedented amount of integration to the electronics industry until now relegated to the world of software development, allowing designers to work from home and reach unprecedented levels of efficiency.
We have only scratched the surface of what is possible to do with Altium Designer on Altium You can check the product page for a more in-depth feature description or one of the On-Demand Webinars. Zachariah Peterson has an extensive technical background in academia and industry. He currently provides research, design, and marketing services to companies in the electronics industry.
One of the practical outcomes is that all components of a particular type will now be available when that type is selected under Categories in the Components panel. Note that the component entries are not affected in any other way. They remain in their existing folders, which are associated with the Component Template created during migration, and the templates themselves remain available.
The Folder entry for the Resistors component type corresponds to the target folders of those multiple templates. When a new component is being created File » New » Component , those Templates are offered as sub-entries for the Resistors Component Type in the Create new component dialog.
The Edit Templates dialog, accessed from the button, allows you to update the Template to Component Type mapping from that indicated in the Data Management — Component Types page. The mapping, as shown in the dialog's column entries, represents which Component Type be will be applied when the associated Template is used — or conversely, which Template is used when a Component Type is chosen such as when creating a new component.
For a selected Template entry in the dialog, the association is changed by choosing an alternative Component Type from the entry's drop-down menu.
When the dialog and page are then closed, the template's ComponentType parameter value and its Default Folder setting will be changed to correspond with the newly specified type. This is equivalent to editing the Template manually. The result of the updated template-type mapping is shown in the Data Management — Components Types page , which has a Name orientated listing — where Name represents Component Type. The Library Migrator may be switched to a special Models Only migration mode that detects and processes the available component models in a source library.
To change to this migrator mode, check the LibraryMigrator. When the Library Migrator is switched to its Advanced mode or opened in its Advanced mode File » Library Migrator , full details of the proposed model migration are available.
The Migration Preview area shows the Folder Structure that will be used in the target Workspace, which may be modified from the default settings in the Folder field for each model type in the Properties panel. The applied naming schemes and Lifecycle definition for each model can be selected from the available system types see Properties panel , below.
The migration of component models to the Workspace can be limited by type if desired, by disabling or enabling specific model types in the Properties panel using their associated buttons. Once the Library Migrator is configured, select the button to complete the migration of the listed component models. The results can be reviewed in the migration log file, as offered by the Library Migrator progress dialog , or by viewing the migrated models in the Explorer panel.
The Library Migrator's associated Properties panel settings provide advanced control over the migration configuration for the selected library or sub-library group. The panel's option settings are defined by the default system settings or those specified by the applied Component Template , which in turn is set by the library's detected component type — LED in the example shown here.
The settings are also user-editable, allowing you to tailor the migration process as required, and may be restored with the Reset to Default link top right. Component Template — the Workspace Component Template that will be applied to the migrated components, and by association, their Component Type setting. Overrule this setting by selecting an alternative template using the drop-down menu options or via the button. Set this option to [Create new] for the automatic creation of a template derived from the source library parameters and the Library Migrator's current settings, or choose [ No Template ] to prevent a template from being applied or created.
Parameter Mapping — the parameter matching between the library parameters and those in the applied component template or the default settings where no template is available , and also the Type of value for each parameter Text or a unit-aware type.
Use the Source Library Parameter column drop-down menu options to change the mapping, and the Type column menu options to overrule the existing setting determined by the template or defaults. Parameter names can be edited, and Parameter sets can be added, edited, and removed. The base component parameters ID , Name , Description may be remapped, but are otherwise read-only.
The panel's Advanced tab offers settings for all migrated data object items, as set by the system defaults or the applied Component Template. These include component Models, Datasheet files, and any created Component Templates.
The Library Migrator features the ability to export a detailed text-based file that captures the current configuration setup, which includes all configurable migration settings such as target paths, parameter mapping, naming scheme, lifecycles definitions, target component types, and so on. The ability to restore a configuration is particularly useful when the source database or file-based library has been updated and those changes need to be migrated to the Workspace.
If the configuration was exported when the library was first migrated, the restored imported configuration will re-establish the exact configuration settings that were used, which guarantees a consistent data transfer scheme for that library or libraries. Using Altium Documentation. Contents What Gets Migrated?
The migration of pin mapping information for simulation models is not currently supported. As such, this functionality will not be available with this level of access to Altium You can change the component type by right-clicking on a type in the Components Type list. When connected to an Altium Workspace , note that configuration and use of lifecycle definitions is not supported with the Standard Subscription Plan.
Use the button top left to refresh the Library Migrator. This will reload all source libraries and Workspace data to pick up any changes that have occurred since the migrator was opened. Use the Search field upper right to filter the Components entries by a matched parameter value. If the migration is run, the components are migrated as an uncategorized type without interpretation. To do so, select the dialog's Parameter Grouping option and then an appropriate parameter from the drop-down menu.
Alternatively, a library's Component Type can be manually selected in the General section of the Properties panel. Note that the Migration Checks section in the Properties panel shows which issues are detected Violation Types and how they are indicated Report Mode — use the Report Mode drop-down menu to choose a different report level for the associated violation type. Note that it is not necessary, or even desirable, to migrate a PCB Library along with its Schematic Library counterpart, since the required model migration and linking will be performed by the Library Migrator itself.
The migration process identifies, locates, and transfers the correct model s for each component to create a unified component in the target Workspace. The effect of the merge is more straightforward if a single Template is initially associated with all of the source component types — say, the Resistors Template is associated with the Resistor , Resistor and Resistor component types.
In this case, when the component types are merged with the Resistors type, its singular Template and target Folder settings remain unchanged. Use the Update existing components for changed templates option to automatically apply the updated Component Type entry to components that used the prior type. Existing Component Templates are not altered by the migration process.
This results in component IDs automatically created based on the Naming Template specified in the panel's Component section, found under the panel's Advanced tab. The ID mapping can be changed to use any parameter in the source library that is unique for each component entry by choosing an alternative from the Source Library Parameter drop-down menu.
Note that the base component parameters ID , Name , Description may be remapped, but are otherwise read-only. The Component object section includes the setting for Duplicates Detection , as outlined above. Note that an exported saved Migration Configuration file includes references to the library files that were open as source libraries when the configuration was exported.
0コメント