Search In: Doc:Documentation: NEXUS Client
Altium DesignerAltium 365Altium MCAD CoDesignerAltium CircuitMakerCompany DashboardAltium On-Prem Enterprise ServerAltium Infrastructure Server
Ver: Version: 4
43.23.13.02.12.01.11.0
Close
Search Search on Documentation

Entry Is Empty

Created: August 03, 2021 | Updated: August 03, 2021 | Applies to version: 4

This document is no longer available beyond version 4. Information can now be found here: Entry Is Empty for version 5

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 Mated Parts

Default report mode:

Summary

This violation occurs when a module entry does not currently reference a connector component in the child design project referenced by its parent module.

Compiler violations associated with Multi-board Design projects are only presented after running an Electrical Rules Check from the project's Multi-board Schematic document (*.MbsDoc). Do this by choosing the Design » Run ERC command from the main menus.

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. A notification is displayed in the Messages panel in the following format:

Entry "<EntryDesignator>" is empty in "Module <ModuleDesignator>(<ChildProjectName>)"

where:

  • EntryDesignator - is the designator of the offending module entry.
  • ModuleDesignator is the designator of the module on the Multi-board Schematic that is used to reference the child design project.
  • ChildProjectName - is the name, including extension, of the child project referenced by the module.

Recommendation for Resolution

This violation can arise when:

  • A connector component in the referenced child project and currently associated to an existing module entry has had its special System:Connector parameter removed, and that change has been inadvertently imported to the Multi-board Schematic document. In this case, add the parameter back to the component then import the change back to the Multi-board Schematic document.
  • A new entry has been placed manually within the parent module. In this case, import changes from the child project to synchronize the required entries with their underlying connectors then remove the redundant entry.
Typically, you would ensure that the connector(s) in the child project are placed and have been given the System:Connector parameter. Then use one of the Import from Child Project commands to have the entries automatically created in the empty/shell parent module referencing that child project. This is the quickest and safest method to have the module entries in the system-level design created in-sync with their underlying connectors in the child projects.

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). 
Content