WorkspaceManager_Err-MissingComponentModelsMissing Component Models_AD

您正在阅读的是 1.0. 版本。关于最新版本,请前往 WorkspaceManager_Err-MissingComponentModels((Missing Component Models))_AD 阅读 4 版本

This documentation page references Altium NEXUS/NEXUS Client (part of the deployed NEXUS solution), which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer and a connected Altium 365 Workspace. Check out the FAQs page for more information.

 

Parent category: Violations Associated with Components

Default report mode:

Summary

This violation occurs when compiling an Integrated Library Package (*.LibPkg) and a linked model for a component in the source schematic library could not be found.

Notification

If compiler errors and warnings are enabled for display on the schematic (enabled on the Schematic - Compiler page of the Preferences dialog), an offending object will display a colored squiggle beneath it. Hovering over the object will display a pop-up hint that summarizes the violation. When the linked model is a footprint model, or simulation model, the message a notification is also displayed in the Messages panel in one of the following formats:

<ComponentName>: Could not find <ModelName> - when the model search scope is Any.

<ComponentName>: Could not find <ModelName> in <LibraryName> - when the model search scope is Library Name.

<ComponentName>: Could not find <ModelName> in <Path> - when the model search scope is Library Path.

where:

  • ComponentName is the name of the component in the source schematic library.
  • ModelName is the name of the footprint, or simulation model, that is linked to the source component and which could not be found.
  • LibraryName is the name of the library file specified to contain the linked model.
  • Path is the absolute path to a library file specified to contain the linked model.

When the linked model is a signal integrity model, the message is displayed in the Messages panel in the following format:

<ComponentName>: Could not find 'GenericEntity'in <Path>

where:

  • ComponentName is the name of the component in the source schematic library.
  • Path is the absolute path to a library/model

Recommendation for Resolution

When the problem is a linked footprint, or simulation model

This issue is typically caused by one of the following scenarios:

  • The model name is incorrectly specified when defining the model link.
  • The linked model does not reside in the specified library file.
  • The library file containing the linked model has been moved or deleted.

The first port of call in resolving this violation is the associated setup dialog for the model type you are linking to - the PCB Model dialog, or the Sim Model dialog. In each case, check and ensure:

  • The name of the model to which you are linking is correct, and
  • The correct option is used to locate the library/model file in which that model resides.

The format of the displayed error message depends on the search scope you have enabled when locating the model, and can be of great help when tracking down the problem with the model link:

  • If the model could not be found in a specified path (search scope: Library path), ensure that the library/model file you have specified actually exists at that location and also check the library/model file to see if the model with the specified name exists within.
  • If the model could not be found in a specified library/model file (search scope: Library name), ensure that the library/model file has been added to the Available Libraries list (Project Libraries, Installed Libraries, Project Search Paths). Also check to make sure the library/model file contains the model with the same name specified in the link.
  • If the model could simply not be found (search scope: Any), ensure that a library/model file - containing a model with the same name as that specified in the link - has been added to the Available Libraries list.

When the problem is a linked signal integrity model

Typically caused when the type of signal integrity model (e.g., diode, IC) is not specified, this is resolved in the associated setup dialog for signal integrity models. The easiest way to access this is through the Properties panel when viewing the properties for the selected component. Check that you are using the correct model in the Models section on the General tab of the panel and amend if necessary. The Add and  buttons can be used to create a new model (choose Signal Integrity from the list) or modify the existing signal integrity model. This will give access to the Signal Integrity Model dialog, where the Import Ibis button allows pins models to be imported from an Ibis model file.

You can add an Ibis model directly by clicking Add - Ibis model and using the subsequent Ibis Model dialog to define the link to the model and file.

Tip

  • Object hints will only appear provided the Enable Connectivity Insight option is enabled on the System - Design Insight page of the Preferences dialog. Use the controls associated with the Object Hints entry in the Connectivity Insight Options region of the page to determine the launch style for such hints (Mouse Hover and/or Alt+Double Click). 
If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.
Content