Altium NEXUS Documentation

WorkspaceManager_Err-DifferentNetNamesDifferent Net Names_AD

Created: August 3, 2021 | Updated: August 3, 2021
All Contents

Parent category: Violations Associated with Connections

Default report mode:

Summary

This violation occurs when the name of the net associated with a connection on the Multi-board Schematic is not the same as the net associated with the corresponding pin of the connector on the child design project.

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:

Net Name "<ConnectionNetName>" for connection "<ConnectionDesignator>" does not match with Net "<ConnectorPinNetName>" of "Pin <ConnectorDesignator-PinNumber>" in child project "Module <ModuleDesignator>(<ChildProjectName>)"

where:

  • ConnectionNetName - is the name of the net (on the Multi-board Schematic) associated with the connection that connects from the indicated pin.
  • ConnectionDesignator - is the designator of the connection.
  • ConnectorPinNetName - is the name of the net associated to the indicated pin of the connector on the child design project.
  • ConnectorDesignator-PinNumber is the designator of the connector component in the child design represented by the module's entry and the pin of that connector.
  • 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 typically arises when the name of the net on the connector pin in one child project is different from that in the mated connector pin in another child project, i.e. the two boards being connected by a connection between the relevant parent modules on the Multi-board Schematic document.

Use the Connection Manager dialog to view the net names currently being used. The Net Name entry shows the name used for the connection on the Multi-board Schematic document. With the connection selected, this can also be seen visually in the Conflict Resolution area of the dialog. Where the connector pins have different nets associated to them in both child projects, the Net Name for the connection defaults to <FromPinNetName>/<ToPinNetName>. These net names are reflected in the Module Net fields for the From and To pins respectively. Resolution can be in two ways:

  • Use the Rename buttons in the Conflict Resolution area for both modules to quickly set the module net in each case to be the same as the net name for the connection. Then apply the changes and pass those changes back to the child projects using the Design » Update Child Projects command. The nets associated to the respective connector pins in those projects will be updated accordingly through use of an ECO.
  • Change the naming for the net associated to the relevant connector pin in one of the child projects to be the same as that used for the connector pin in the other project. Then compile the child project and bring the change back to the Multi-board Schematic by using the Design » Import From Child Projects command. The net name for the connection will be updated accordingly through use of an ECO.

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). 
Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: