- Multi-board design projects in Altium Designer | PCB Design Blog | Altium

Looking for:

Altium designer 17 multiboard free.Multi-board Design with Multi-board Assembly 

Click here to DOWNLOAD

     

Altium Designer - PCB Design Software - Creating a Multi-board Assembly

 

Parent page: Capturing the Logical System Design. The software checks for logical, electrical, and drafting errors between the design content and project checking settings. There are a number of checks that can be performed on the validated Multi-board design. These are configured as part of the project options. Select the Project » Project Options command from the main menus to open the Project Options dialog and select its Error Reporting tab. The Report Mode of each violation can be changed to one of four values by clicking on it and selecting the desired value in the drop-down.

Configure the required violation checks on the Error Reporting tab of the Project Options dialog. If validation errors and warnings are detected in the design, a notification is displayed in the Messages panel.

Note that the Messages panel will only open automatically if there is at least one Error or Fatal Error condition. To check for a Warning , you will need to open the panel manually by clicking the Panels button on the bottom-right of the design space then choose Messages.

Once the project has been validated, the panel will list any warnings and errors that have been detected. The Messages panel displays the warnings and errors detected in the Muli-board design project.

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.

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

These net names are reflected in the Module Net fields for the From and To pins, respectively. Resolution can be in two ways:. This violation occurs when a connector pin represented in a module entry on the Multi-board Schematic is not connected to any net in the child design project referenced by that module. This violation can arise in a number of situations.

Consider the following when resolving a violation of this type:. This violation occurs when a conflict exists in the connectivity between two connected boards in the system. This violation typically arises when a change has been made in relation to the connector in one child project, and when that change is imported back to the Multi-board Schematic document, it will break the existing connectivity defined between two connected boards.

For example, the nets assigned to two pins of the connector might have been swapped in one child project, meaning that there is now a mismatch when following those pins through to another target board's connector. Use the Connection Manager dialog to view unresolved conflicts. Select a highlighted Net entry in the list to see a graphic representation of the Conflict and to access a range of button options that can be used to resolve it. The options include:. When a conflict resolution option has been selected, an affirmative answer in the following Confirmation dialog will cause the conflict resolution action to be applied to all conflicts of the same type.

The corrected net assignments will be highlighted in green and also reflected in the dialog's lower connection graphic. Select the Apply Changes button to apply the updated assignments to the Multi-board Schematic. If the resolution choice results in changes required to a child project, use the Design » Update Child Projects command to do this. This violation occurs when a module entry does not currently reference a connector component in the child design project referenced by its parent module.

This violation occurs when a module entry is not currently connected to another module in the design. 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:. Using Altium Documentation.

Different Net Names. ConnectionDesignator — is the designator of the connection. ConnectorPinNetName — is the name of the net associated with 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.

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 with the respective connector pins in those projects will be updated accordingly through use of an ECO.

Change the naming for the net associated with 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.

No Net. ChildProjectName — is the name, including extension, of the child project referenced by the module, and containing the connector whose indicated pin is not connected to a net.

Recommendation for Resolution This violation can arise in a number of situations. Consider the following when resolving a violation of this type: If the pin of the referenced connector is not to be used within the design, tie it to the appropriate power line e.

Ensure that any wiring to the connector pin is making electrical contact, i. If the connector pin is intended to have a short wire and a net label, ensure that the net label exists and has been attached to the wire correctly. Unresolved Conflict. NewModuleNetName — is the name of the net now associated with the indicated pin of the connector on the child design project, after importing changes made to that child 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.

Recommendation for Resolution This violation typically arises when a change has been made in relation to the connector in one child project, and when that change is imported back to the Multi-board Schematic document, it will break the existing connectivity defined between two connected boards.

The options include: Confirm — the module nets on the pins for the connection in the Multi-board Schematic design document will be changed to match the updated assignments as shown in the dialog the changes that were made in the child project.

Revert — the current net to pin relationship for the connection in the Multi-board Schematic design document will be retained. The proposed change is ignored by the system design. Note that the system design will then not match the net assignments in the child design s. The Conflict Resolution options that are available will depend on the type of connection that is selected. The Swap Wires option, for example, will not be offered for a Direction Connection between module entries where the PCBs are directly plugged together rather than wired together.

Entry Is Empty. Recommendation for Resolution This violation can arise when: A connector component in the referenced child project and currently associated with 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. 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. No Mated Part. EntryDesignator — is the designator of the offending module entry which is reflective of, and synchronized with, the underlying connector in the referenced child project.

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

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.

Printer-friendly version. Found an issue with this document? 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? Connect to Support Center for product questions. I do not want to leave feedback.