Validating a Component

Before saving a Workspace Library component defined/edited in the component editor (in its Single Component Editing or Batch Component Editing mode) to the connected Workspace and making the component be available for use in designs, it is essential to make sure that this component meets the requirements in accordance with the configured settings. When you attempt to save a component back to the Workspace, the component editor runs a validation – a Component Rule Check. This feature can also be run at any time, manually, by choosing the Tools » Component Rule Check command from the main menus. Be sure to have saved your component locally (File » Save) before you do.

The Component Rule Check command is also available from the editor's main File menu and from the component entry's right-click menu in the Projects panel.

Just as a board project has the validation process to detect any violations, the component editor has a component validation functionality. Any violations that are found are listed in the Messages panel.

Javascript ID: ExampleResultsfromRunningComponentRuleCheck_AD22_2

Detecting issues with a component prior to saving to the Workspace. Running the Component Rule Check command from the Component Editor in its Single Component Editing mode is shown here.

Detecting issues with a component prior to saving to the Workspace. Running the Component Rule Check command from the Component Editor in its Batch Component Editing mode is shown here.

The component validation tests for an array of potential issues with the component and its defined models – both hardwired tests, as well as a range of violation types that can be user-defined at the global level.

The following hardwired validation checks all carry a report mode of :

User-definable checks are configured on the Data Management – Component Rule Checks page of the Preferences dialog.

User-definable violation checks that can be configured as part of global preferences, for use when validating a component.
User-definable violation checks that can be configured as part of global preferences, for use when validating a component.

Any of the hardwired tests that fail or user-defined checks at a level of Fatal Error will prevent the saving of the component to the Workspace.

The default settings of the user-defined checks may not suit your components, so it is important to become familiar with the options and how to configure them to suit your designs. Information about each user-defined error check can be found below.

Violations Associated with Components

Violations Associated with Footprints

Violations Associated with Symbols

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

The features available depend on your Altium product access level. Compare features included in the various levels of Altium Designer Software Subscription and functionality delivered through applications provided by the Altium 365 platform.

If you don’t see a discussed feature in your software, contact Altium Sales to find out more.