Library Migration: Onboarding Guide

An electronics design is a collection of connected components. The rewarding part of product development is coming up with cool ways of solving those engineering challenges and connecting those components to craft your unique design. However, a large part of the work, and to many designers, the more tedious part, is creating the components. While it might not be exciting, the components become a…

The schematic symbol typically includes a shape that can reflect the function of the component and one or more pins. How a component is represented, i.e., the look of the symbol and arrangement of component pins, is up to the designer. This should be done to comply with the requirements of your organization and the design standards you choose to adopt. One component symbol can represent the…

Concept & How to Pages Understanding Models, Components and Libraries Altium hosts a huge array of ready-made PCB Components both in the Vault as well as in several integrated and discrete libraries available through AltiumLive. However, even with this rich set of resources, it is likely that at some point in the designer's career they will need to create a custom PCB Component. PCB Component…

Parent page: Working with Managed Components Helping to streamline the creation of your managed components, Altium Designer, in conjunction with your managed content server, supports creating and defining Component Templates. Just as a schematic template can be used to predefine information on schematic sheets that reference it, a component template is referenced by a managed component, and…

Parent page: Working with Managed Components As a board designer, the components you use will have defined symbols (and other domain models) and some key parametric data, but at the end of the day they are just 'symbols of design intent' - having meaning in the context of the project design, but holding no physical meaning outside of that design. Each of these design entities needs to be …

Altium Designer, in conjunction with your managed content server caters for the ability to store component datasheets within that Server and, in doing so, link them to target Component Items. This allows you to more fully describe and support a component, in a centralized fashion, while reducing the reliance on external storage mediums (shared network drives for example). Storing datasheets next…

Parent page: Creating a New Component The number of design components available to an engineer when capturing their next design can vary from a few hundred scattered across individual symbol and model libraries to hundreds of thousands, stored in a dedicated company parts database. But no matter how many components are available to hand, there will always be more that aren't, and that need to be…

Parent page: Managed Components A managed component is defined/edited using the Component Editor, which can operate in two modes - Single Component Editing and Batch Component Editing. The former provides a streamlined interface when defining/editing a single component. This is the default mode when creating a new Component Item, or editing a single revision of an existing Component Item. The…

Parent page: Managed Components A managed component is defined/edited using the Component Editor, which can operate in two modes - Single Component Editing and Batch Component Editing. The latter provides the interface for defining/editing multiple components, but can be used to define/edit a single component, should you wish. With the Component Editor in its Single Component Editing mode, access…

Database component libraries, which derive their component parameters from a master database, can now be synchronized with that database when the library has been migrated to an Altium 365 Workspace. With the newly introduced Components Synchronization feature, the data from a selected table within the master database is used to create a fully configured and mapped synchronization profile that…