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

WorkspaceManager_Err-NoMatedPartNo Mated Part_AD

Created: September 22, 2017 | Updated: August 04, 2021 | Applies to versions: 1.0, 1.1, 2.0, 2.1, 3.0, 3.1 and 3.2
Now reading version 3.2. For the latest, read: WorkspaceManager_Err-NoMatedPart((No Mated Part))_AD for version 4

Nexus message

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 is not currently connected to another module in the design.

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:

Part "<ConnectorDesignator>" (Entry <EntryDesignator>) doesn't have Mated Part in "Module <ModuleDesignator>(<ChildProjectName>)"

where:

  • ConnectorDesignator - is the designator of the connector component in the referenced child project.
  • EntryDesignator - is the designator of the offending module entry (which is reflective of, and synchronized with, the underlying connector in the referenced child project).
  • 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

Ensure that the offending module entry is connected to the required entry in a target module - making a connection between the connector on one child board with that on another. Choose the type of connection and wire it up between the two module's entries accordingly. Available connection types are:

  • Direct Connection - a direct connection is used whenever the connector on one board is to plug in directly to the connector on another board without the use of a physical connection (wire, cable, or harness).
  • Cable Connection - a cable is a physical connection, providing a conduit for net signals between two boards in a multi-board system, and that cable plugs into a connector on each of those boards.
  • Wire Connection - a wire is a physical connection, providing a conduit for a single signal between two boards in a multi-board system, and that wire is attached directly into a connector on each of those boards. Although placing a single wire on the document, in reality a series of wires will be used, in accordance with the number of signals/pins being connected between the connectors of the two boards.
  • Harness Connection - a harness is a physical connection, providing a conduit for net signals between two boards in a multi-board system, and that harness plugs into a connector on each of those boards.

 

If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.
Content