Efficiently manage electronic components with centralized libraries, ensuring consistent sourcing, versioning, and integration for streamlined PCB design.
This video demonstrates how to acquire a component from a manufacturer part search and add it to a workspace in Altium Designer.
This video demonstrates using component templates to bring components into a managed library in Altium 365.
This video demonstrates how to create an Altium Designer Library from a project to add to Altium 365.
Summary: In Altium 365, the component library is an essential place to store your electronic design data. The library is
This video demonstrates how to create a managed BOM and select an alternate part in Altium 365.
This video shows users how to move a project and components in Altium Designer to Altium 365.
This video demonstrates the version control system in Altium 365. In this system, projects are available in the web interface in folders. Sharing rights are set up per folder or per project, and can be set by editor, or by viewer. A new project template is created in Altium Designer and saved to the Altium 365 Workspace, and the Altium 365 version control system is enabled to view the project history. In Altium Designer, the project is created locally on the C Drive for quick access, and it is saved to Altium 365. A schematic is opened and two parts are placed with an annotation and saved to the server. The project history in the version control is opened, and the history of the project is discussed. A tag is created, and a comparison of the tag to a previous commit is made. Other options in the history are discussed as well, including reverting to a previous version. Likewise, a where used for components feature is demonstrated to trace parts across a project, and the process to prevent users from making duplicate conflicting changes is also shown. These history changes are also available on the web on Altium 365. Next, the process to create a personal version control server via a template on an SVN server is demonstrated. The project is committed to the SVN locally and moved into Altium 365 to utilize the web viewer and Altium 365 capabilities. However, this disables web viewer history visibility. Finally, the local version control system is migrated to the Altium 365 git version control to once again view the full project history.