Altium Import Library
Gracia Bradshaw
But this is going to end up with me having hundreds and libraries with just one part in each. How can I create one library and import the downloaded files from Ultra Libary (and others) into that library? Bearing in mind that I have no scripting experience.
We imported the project component model libraries into the Importing Project Components Chapter. Databases and other user data sources are also available in Altium 365. In particular, we will demonstrate how to import footprint libraries, symbol model libraries, and integrated libraries.
In the Library Importer that opens, click "+ Library" or "Choose a File" to locate and choose the path to the file. During this stage, we will migrate footprints from PCB libraries only.
Tip: Perform the above actions carefully when importing several libraries in different folders. Careful import will simplify finding the correct library to use and eliminate the possibility of footprint errors.
Tip: If you import libraries of the same components, select the category and all components and then set the required type. You will reduce the work on editing these components in Altium 365.
Tip: Some Symbol models contain links to footprints, and there is now no access to them. These types of components will cause import errors and will not be transferred.
It is important to note that any libraries available to users can be imported to Altium 365, such as libraries from a particular project, database libraries, the manufacturer's website, libraries included with the installed software, etc.
We have selected a project to use with Altium 365, so now we need a complete library containing all components and models of the project to import into Altium 365. We will start by creating an integrated library.
The next step is to check the library for possible errors by clicking the Validate button near the top right of the importer. The Messages panel displays all errors and warnings. The list is extensive; however, we will fix them quickly because they are the same errors.
The Library Importer offers a minimalist Simple interface mode where the selected database and file-based component libraries are imported to Workspace components through a single step, while the importer automatically takes care of type classification, the target source folder, parameter inclusion and value type, and the transfer of all relevant data. The interface is also available in an Advanced mode that provides a full preview of the proposed library import, and access to its related data and settings. And while the import is a single-click process by default, the importer also offers advanced configuration options through the Properties panel for enhanced control over exactly how that import is performed.
All information that is present in an original source library is imported to the Workspace components, including all referenced domain models (schematic symbols, PCB footprints, simulation models), parametric information, assigned part choices, datasheet files, etc. Component Templates are also created where necessary, and may then be refined and used for subsequent library imports.
While library import process needs to deal with database and file-based library sources that may use a range of formatting standards, its automated analysis processes detect the types of components in the source library (resistor, capacitor, etc.,) and also the parameters names and their value types (Volts, Ohms, etc.). The system conducts and handles a number of validations, for example, to ensure no duplicate IDs for the resulting Workspace library components, or to ensure no duplicate models or component templates are created, and that such entities are reused across (linked to) components where needed. And if issues do arise, the system flags them, with suggestions on how to resolve those issues, aiming to get the import back on track as quickly, and as smoothly as possible.
In the Components panel, choose the Import Library option from the menu. If a database or file-based library is currently selected in the panel's Categories column (or in the top drop-down menu when the panel is in compact mode), the Library Importer will open for this library. When a Workspace library component type is selected, the standard Windows Open dialog will open to browse to and select a library file to be imported.
The database and file-based libraries that are currently available to the software can be viewed and managed in the Available File-based Libraries dialog, which is accessed from the File-based Libraries Preferences option on the button menu in the Components panel.
The Library Importer's Simple mode preselects all aspects of the import process based on its analysis of the source library and the connected Workspace. The Library Importer dialog then presents a summary of the import structure, including a total number count for each item type. The library import is performed as a single step from the command.
The results of the library import, as newly created Workspace components, can be seen in both the Explorer and Components panels. Imported components include all models, parameters as interpreted by the applied Component Template(s), Part Choices derived from Supplier Link source data, and any reference links or files.
Monolithic libraries (those that contain multiple types of components) are automatically split into subgroups, where each group represents a type of component found in that library. The groups are processed as individual libraries.
The Library Importer's full GUI is presented when in Advanced mode, which offers detailed control over the management of libraries, component types, and component parameters. When combined with the Properties panel, the import of component libraries to the Workspace can be configured to your specific needs. Note that the importer's settings can be saved and restored by exporting/importing configuration files.
Advanced mode is enabled when the Library Importer is opened from the File Library Importer command, or when the button is selected while in Simple mode. Libraries are added to the importer's SOURCE LIBRARIES section (if not already populated) by dragging and dropping a library file onto the area, right-clicking on then selecting Add Library from the context menu, or by selecting the button.
Source libraries that contain multiple component types are detected by the importer's analysis routines and segregated into sub-library groups, where they can be processed as individual type libraries. The component type detection is based on the source component Designators (R?, C?, etc.,) and also keywords (Resistor, Res, etc.,) contained in the other main component parameters (Description, ID, etc.).
Click on the Filter icon () within a header entry to restrict the listing to an available parameter column value, blank/non-blank values, or a Custom filter setting. The applied filter is shown at the bottom of the listing where it can be enabled/disabled (using its associated checkbox), modified in the Filter Editor, or deleted. Selecting All via the header filter icon () will also remove the applied filter.
With the dialog's Map Designators option selected, choose the component type option that applies to the uncategorized components from the Component Type drop-down list (all available component types are included). Confirm the completed type-designator mapping (the Logic component type to U? designators) with the button.
With the component type now specified by the applied mapping, the importer will use the matching Component Template (Logic) to configure the library import as defined by the template settings (folder, naming, etc.).
To change the Component Type of an individual entry in the Components list, click in its Component Type cell then choose an alternative type from the drop-down menu or right-click on the component type then select Change Component Type from the context menu.
If you have excluded a component type from the import by using the above described Exclude from Importer command and you need to include that component type, after all, right-click on the grayed-out component type in the Types (or Folder Structure) list then select Include to Importer from the context menu. The component type will once again display in the Types list denoting it is not excluded.
Components that will not be imported to the Workspace correctly, or not at all, are indicated by warning or error tags in the Advanced UI when the Library Importer is run (), or an import Validation is performed (). Validation also checks for empty Workspace folder paths, conflicting system parameters, and duplicate models. A Fatal error will block the import.
When attempting to perform the import, the Messages panel is populated with the detected violation issues, and a dialog will offer the choice of abandoning or proceeding with the current import configuration. In the latter case, invalid components are not imported or the import process will fail.
In the case of a canceled import or when the manual Validation is run, any components that fail the import checks are then associated with error/warning icons plus further information in the lower Details area. Icons in the preview Status column indicate the specific component entries that are in violation of the import rule checks.
If you encounter a 'model not found' error (such as Footprint not found in available libraries) when attempting to import a schematic library, it means that the Library Importer cannot locate the models that are linked to components within the SCHLIB.
93ddb68554