Import libraries from EAGLE into your hub
If you are migrating from EAGLE, use this method to import your libraries into your Fusion hub. This ensures all team members have access to the components based on project folder permissions. This operation preserves the link information with Library.io.
Prerequisites
Steps
- In the Electronics Library Manager, click the Hub Libraries tab.
- In the top right of the table, click the Sync libraries
button.
- Select Import EAGLE Libraries in the dropdown menu.
- In the Add EAGLE Libraries to Library Manager dialog, verify the path to your
libraries.rc file. The correct path is typically selected by default.
- If the path needs to be changed, click Browse to locate the correct
libraries.rc file.
- Click OK to proceed.
- In the Import Private Libraries dialog, review the list of found local and managed libraries that have not yet been imported into your hub.
- Confirm the selection is correct and deselect any libraries you do not want to import.
- In the Location field, click Change Location to select the project and folder where the imported libraries will be stored.
- Click Import Into Fusion Hub.
The selected libraries are uploaded in the background. This operation may take some time depending on the number of libraries being imported.
Missing libraries
If a library you expect to see is not shown in the Import Private Libraries dialog, there are two ways to get it into Fusion, depending on whether it is a managed library:
- Managed library (Library.io): Make sure the library is found in the Private Libraries tab, then import it from the Private Libraries tab of the Library Manager.
- Restore the Library Manager: If the library is not shown in the Private Libraries tab, click the Sync libraries
button and select Restore All Library.io Libraries to scan Library.io and restore any missing libraries.
- Non-managed library (local only): Upload the
.lbr file directly into your Fusion hub via the Data Panel.
Next steps
- Update existing designs: If you have designs using components from private libraries, use the swap libraries feature to make sure your designs only use components from hub libraries.
- Import private packages: It is recommended that you import the private packages used by these libraries into your hub to avoid permission errors for team members when building 3D boards. When you first open the library in the library editor you will be prompted to import the private packages from the library.