Altium NEXUS Documentation


Created: July 7, 2022 | Updated: July 7, 2022
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 (with Altium Designer Enterprise Subscription) and a connected Altium 365 Workspace. Check out the FAQs page for more information.

Parent page: MultiBoardAssembly Commands

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

Applied Parameters: None


This feature is used to check for collisions between the various constituent entities of the multi-board assembly. Collision checking is performed between each PCB and the top and bottom enclosures/cases, as well as between the PCBs themselves.

For a high-level look at multi-board design within Altium NEXUS, see Designing Systems with Multiple Boards.


This command can be accessed from the Multi-board Assembly Editor by:

  • Choosing the Tools » Check Collisions command from the main menus.
  • Using the Ctrl+K keyboard shortcut.


After launching the command, the software checks for collisions between the various entities involved in the multi-board assembly. First, each board is checked for collision with the upper and lower enclosure/case parts (STEP parts), followed by checking between the boards themselves (PCBs). Any collisions will be reported through the Messages panel, and the offending objects highlighted using the Violation system color.

Use the Details region of the Messages panel to investigate which component on a board involved in a conflict is causing the collision.


Collision checking will be carried out between all boards and the enclosure/case parts, regardless of a board's/part's visibility in the workspace.

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: