Altium NEXUS Documentation


Created: 07.07.2022 | Updated: 07.07.2022
На этой странице документации упоминается Altium NEXUS/NEXUS Client (часть развернутого решения NEXUS), поддержка которого прекращена. Все ваши потребности в проектировании печатных плат, управлении данными и совместной работе теперь могут быть реализованы с помощью Altium Designer (с подпиской Altium Designer Enterprise) и подключенного рабочего пространства Altium 365 Workspace. Посетите страницу часто задаваемых вопросов (FAQs) для получения дополнительной информации.

Parent page: WorkspaceManager Commands

The following pre-packaged resource, derived from this base command, is available:

Applied Parameters: Context=Document


This command is used to access the Offline Intergated Library Maker Wizard. The wizard facilitates generation of an integrated library directly from a database library - either a non-version-controlled Database Library (DbLib), or a version-controlled SVN Database Library (SVNDbLib). In this way, your CAD Librarians can still use database/version-controlled libraries, while your designers use regularly regenerated integrated libraries, working in an 'offline' fashion as it were.


This command is accessed from the Database Library Editor, and SVN Database Library Editor, by choosing the Tools » Offline Integrated Library Maker command from the main menus.


After launching the command, the Offline Integrated Library Maker wizard will appear. Follow the wizard's set of progressive (and intuitive) pages to collectively gather the information required to generate the integrated library(ies). The process of conversion to an integrated library is carried out on a per-database-table basis. You have full control over which tables in the database - linked to your database library - are considered in this process. A separate integrated library will be generated for each included table.

After choosing the database library and setting the related conversion options as required, click Next to proceed with the conversion. A progress bar will be displayed, along with information on the current database table being converted. Remember that the conversion process is carried out for each database table you have nominated to convert. The following is essentially a breakdown of this process:

  • An integrated library package (*.LibPkg) is created and opened in the Projects panel. The package is named using the name of the table. For a table named AD Differential Amplifier for example, this would give AD Differential Amplifier.LibPkg.
  • A schematic library document is created and added to the LIBPKG. The schematic is again named using the table's name (e.g. AD Differential Amplifier.SchLib).
  • Each record in the table is then considered and the appropriate Altium NEXUS component built. To do this, the referenced schematic symbol is retrieved from the appropriate source library and added as a component to the new schematic library document. Parameter and model link information defined in the record is then added to that component.
  • The referenced footprint models for the record are retrieved and added to a PCB library document. This document is again named after the table (e.g. AD Differential Amplifier.PcbLib). The PCB library document is then added to the LIBPKG.
  • If Simulation model links have been defined in a database record, the referenced Simulation model files are also added to the LIBPKG. The location of such models remains unchanged. The full path to a model is specified as part of its corresponding model link.
  • The LIBPKG is then compiled to give the integrated library (e.g. AD Differential Amplifier.IntLib), which is subsequently added to Altium NEXUS's Installed Libraries.


  1. The active library from which the wizard was accessed will be specified as the library to convert by default. You can freely browse for, and choose, a different DbLib or SVNDbLib, if required.
  2. All database tables are included in the conversion by default. To exclude a table, simply ensure that its associated Convert option is disabled.
  3. The generated output (integrated library) for each included database table will be stored in its own sub-folder within the specified output directory, named using the table's name.


Обнаружили проблему в этом документе? Выделите область и нажмите Ctrl+Enter, чтобы оповестить нас.

Связаться с нами

Связаться с нашими Представительствами напрямую

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
Вы сообщаете о проблеме, связанной со следующим выделенным текстом
и/или изображением в активном документе: