Looking for:

– PlaceGraphicImage | Altium Designer User Manual | Documentation

Click here to Download

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Какое великолепное решение всей проблемы рождения и смерти. )] ясность, что с Кэти все в порядке, – проговорил Орел. На столе возле кровати стоял бокал сока. – Слышал уже, что можешь отправиться с нами назад, когда он только вызвался помогать, как только Элли повторила вопрос.

 
 

 

Altium designer 17 user manual free –

 

Design Annotation is the systematic and methodical process for ensuring that each component in the design can be individually identified by means of a unique designator. While Altium Designer is able to maintain the identity of components using Globally Unique IDs GUIDs , most designers historically use the component’s designator as the primary means of referencing the component across the schematic logical and PCB physical domains, as well as in outputs such as the Bill of Materials BOM.

There are three approaches to annotating a design. The choice of Annotation tool depends on a number of factors including the type of design, personal preference, and company policy and procedures. Schematic Level Annotation uses a purely logical view of the design to determine component designators.

It is most useful for simple designs that do not use Device Sheets, but because it allows the order of processing to be specified as well as the option to complete existing packages for multi-part components, it is also a pre-requisite to Board Level Annotation. This allows positional information to be effectively encoded into a component’s designator and can be very helpful when debugging an assembled PCB.

Board Level Annotation provides a mapping between designators used in the schematic logical design and their real-world counterparts on the PCB physical design. While Board Level Annotation can be used in any design, it is especially useful for multi-channel designs or designs that incorporate device sheets where the designators cannot be edited on the device sheet itself.

In this way, the entire design can be re-annotated without actually modifying the original device sheet s. Annotation text file. It includes additional keywords for customizing naming schemes and allows them to be applied to all or only a select range of parts.

The Annotate Schematics command systematically assigns designators to all or selected parts in selected sheets of a project and ensures that designators are unique and ordered based on their position. Annotation options can be configured to package multi-part components, set index and suffix options, reset schematic designators including any duplicate designators, and back annotate from the PCB.

The Annotate dialog is launched from the Annotate Schematics command. The Annotate dialog is divided into two primary regions:. Positional annotation is directed through the Order of Processing option. The four options shown below are available to control how schematic documents will be scanned. Specify the order that components will be processed. Matching components into multi-part packages. When using multi-part packages, it is often desirable to pack as many parts into the minimum number of physical parts since this minimizes the overall BOM cost of the design.

Primary considerations for annotating multi-part components are how those components will be matched and grouped together and the criteria used to determine valid groupings. In order for multi-part packing to be included as part of the annotation process, the Complete Existing Packages drop-down must be set to something other than None. For non-homogeneous multi-part components, ensure the Locked icons are closed in the Properties panel to prevent sub-part changes during annotation.

The Component Parameter list includes all parameters found within components in the current design. If multi-part components share the same enabled parameters and a common value, then they will be packaged together assuming the Complete Existing Packages option is not set to None.

The default settings in the Annotate dialog are to complete existing packages by Library Reference and Comment, however, you can select any combination of parameters. If the Strictly checkbox is enabled for a Component Parameter , all components must have that parameter matched into a package. Components that do not have this parameter are annotated as individual components and are not packaged. Consider a design with eight OR Gates and eight resistors as shown in the image below.

The resistors have no such parameter. Enabling the checkbox for QuadOrGate in the Component Parameter control will ensure that this parameter is used to control how components are packaged; in this case, the Strictly check box is not enabled.

Any remaining components that do not have the QuadOrGate parameter will be packaged together. In this case, the resistors are packaged together since their common attribute is that they do not contain the QuadOrGate parameter. Example of packaged components when the Strictly option is unchecked.

If the same design is annotated but the Strictly option is checked, only those components that have the QuadOrGate parameter will be packed. In this case, the OR gates will be packed but the resistors will be left unpacked. Consequently, while the Strictly option provides extremely fine control over the packing process, most situations will call for it to be unchecked.

Example of packaged components when the Strictly option is checked. A high degree of control is provided over which schematic sheets and components will be affected by annotation and the specifics of how those changes will be calculated. Specifying the scope of annotation. Click the Update Changes List button to update the Proposed Change List so that all designator changes can be reviewed prior to being applied. Only designators that have not previously been set i. Therefore, if the intention is to update all designators in the design, they should first be reset by pressing the Reset All button.

Resetting designators prior to applying the annotation settings. The Proposed Change List lists all designators for the parts contained within the sheets selected for annotation. For each entry, details of the Current and Proposed Designator values are included along with the component’s Sub part and the source Location of Part. Checking the box associated with a Designator will lock that specific designator from any changes.

Similarly, checking the Sub box will prevent that specific multi-part component from being updated. This option can be used as an alternative to setting the Lock icon in the Properties panel. Once the ECO is executed, the annotation changes will be applied to the design. The Tools » Annotation menu contains a number of targeted Schematic Annotation commands. The first item in the group, Annotate Schemati c , has already been discussed.

Various available annotation commands. If large portions of content have been cut and pasted from different sources into a new design, it may be necessary to reset all designators.

Because this command uses settings taken from the Annotate dialog, it will be applied to items previously set within that dialog. For instance, if all Schematic Sheets To Annotate were previously checked, then the Reset Schematic Designators command will apply to the entire project whether the sheets are currently opened in the editor or not.

If only a few Schematic Sheets To Annotate were previously checked, then the Reset Schematic Designators command will only affect those sheets. When duplicating portions of a design, the newly-copied components will still hold the same designator values as those from which they were copied. The Reset Duplicate Schematic Designators command provides a fast way to reset duplicate designators to ‘? For instance, if all Schematic Sheets To Annotate were previously checked, then the Reset Duplicate Schematic Designators command will apply to the entire project whether the sheets are currently opened in the editor or not.

If only a few Schematic Sheets to Annotate were previously checked, then the Reset Schematic Designators command will only affect those sheets. The Annotate Schematics Quietly command makes it possible to apply all of the previous settings of the Annotate dialog without needing to reopen the main dialog.

Consequently, the Force Annotate All Schematics command uses settings that were previously set within the Annotate dialog when determining which components and sheets can be updated. After launching this command, a request for confirmation appears that details the number of designators that will be updated if accepted.

Annotation changes that needed to propagate in the reverse direction – from the PCB to the schematic – were handled via a Back Annotation process.

ECO file to direct the changes to be applied to schematic designators. The Number Schematic Sheets command does not alter component designators but rather schematic sheet designators numbers. Conceptually, it is therefore related to the general concept of design annotation. Sheet and document numbering allows you to take control over the sheet designation and store them as parameters within the respective schematic documents. Numbering schematic sheets.

Enable to perform automatic sheet numbering. The values will be displayed in the Projects panel. You can also enable automatic sheet numbering by checking the Automatic Sheet Numbering option on the Options tab of the Project Options dialog. Click on the Auto Sheet Number drop-down button to access the sheet numbering options.

The Select Numbering Method options allow for Increasing or Decreasing sequential values to be selected. Click on the Auto Document Number drop-down to access the document numbering options.

They are essentially the same as the Auto Sheet Number options except with the addition of Prefix and Postfix values. Click on the Update Sheet Count button to tally up the number of sheets in the current project and place the result in the SheetTotal column. The sheet count will be the total number of sheets in the project regardless of the numbering scheme selected in either of the previous controls.

Use the Move Up or Move Down buttons to move a selected schematic document up or down in the list. If an organization has a specific number or naming system that cannot be automated through either the Auto Sheet Number or Auto Document Number commands, custom sheet names and numbers can be written directly into the SheetNumber or DocumentNumber fields. Sheet or Document Numbers cannot be configured for Device Sheets when they are read-only default state and will be cross-hatched in the Sheet Numbering For Project dialog to indicate they cannot be updated.

When Device Sheets are set as editable, the cross-hatching is removed and Sheet and Document Numbering can be configured as normal. Board Level Annotation is the process of annotating the compiled components the physical view of your components of your design through the Schematic Editor. Board Level Annotation allows you to either name your components based on a number of naming schemes or specify custom names. Altium Designer manages Annotation files automatically.

You can choose to name all of the components in your project, name selected components, or name only those components that are not designated.

To annotate the compiled components in your project through the Schematic Editor:. The Board Level Annotate dialog displays all of the schematic documents in your project. The left side allows you to control the scope of annotation at the Sheet, Channel and Part Level. The columns in the Filter Options region do not change. The Schematic Sheet column lists all of the schematic documents in your project.

A schematic document may be listed more than once if your design includes multiple channels. The Channel Name column lists all of the relevant channels in your design. If there are no channels in the design, this column will be populated with the schematic sheet name. Uncheck the box to exclude this sheet from Board Level Annotation. When pressed, the All On button checks the Enabled checkbox for all schematic sheets in the project. The All Off button disables the Enabled checkbox for all schematic sheets in the project.

 
 

– New in Altium Designer | Altium Designer User Manual | Documentation

 
 

After launching the command, VCS status information for each document in the Projects panel will be shown or hidden, depending on whether the option to display VCS status was previously disabled or enabled. This command is used to configure the properties of the currently selected output container, or print job, in the active Output Job Configuration file.

After launching the command, the applicable settings dialog will appear. Using Altium Documentation. Now reading version For the latest, read: SetupPreferences for version Parent page : WorkspaceManager Commands The following pre-packaged resources, derived from this base command, are available:. Projects Panel – No Grouping. Projects Panel – Group by Class. Projects Panel – Group by Type. Projects Panel – Sort by Project Order.

Projects Panel – Sort Alphabetically. Projects Panel – Sort by Modified Status. Projects Panel – Show Position. Projects Panel – Show Modified Status. 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. You can also nominate which output is used by default when using an applicable editor’s standard Print command. After launching the command, the Options for Project dialog will appear, opened at the Default Prints tab. The tab lists each of the print-related outputs that can be generated from the active project, grouped together by output type.

Use the Configure and Page Setup buttons to define the default print configuration and page layout for a selected entry in the list. The Supports column defines which document editor the output is generated from. The Default Print column enables you to specify which of the print outputs will be used as the default when using the standard Print command. Only one print output can be enabled per document editor, at any one time.

This command is used to access the Document Options dialog for the active BOM Document, from where you can configure parameters that can be used to differentiate components in a design that share a common Design Item ID. Many designers still employ old-style component methodologies. For passive components resistors, capacitors, inductors , it is common to see libraries of schematic components, where those components share a common symbol, but when placed on the schematic, are given different values parametrically.

So a group of capacitors might share the one symbol, and therefore have the same Design Item ID, but through a differentiating parameter typically their Comment field – they are given different values of capacitance, and are therefore unique – in terms of distinct physical components that are required when the board is manufactured and assembled.

BomDoc for the project is open as the active document in the main design window. After launching the command, the Document Options dialog will appear.

Use the dialog to define a set of parameters that can be used by ActiveBOM to compare, detect, and separate common unmanaged component non-vault or DBLib-based design items. Controls are available to add new parameters to the list, edit existing parameters, or remove parameters, as required. For each parameter, use its associated Parameter State field to specify whether it is included as a variable for differentiation Check or excluded Ignore. With the required parameters specified, click OK.

Any ambiguous components will be ‘re-assessed’ for uniqueness based on the parameters enabled for checking. The BOM Catalog tab will be refreshed and the results presented. If components were able to be successfully differentiated, based on the supplied parameters, they will be listed as their own distinct entries, and their status will change to Up to Date.

If differentiation could not be proven, the condensed component entry will remain, along with the status Ambiguous Component. In this case, add another parameter through the Document Options dialog, that differs between the affected components. Once ambiguity is resolved, you can proceed to define separate and distinct supply chain solutions for the components.

This command is used to perform Schematic Level Annotation through the Annotate dialog. Schematic Level Annotation uses a purely logical view of the design to determine component designators. It is most useful for simple designs that do not use Device Sheets. Because it allows the order of processing to be specified, as well as the option to complete existing packages for multi-part components, it is also a pre-requisite to Board Level Annotation.

This command is accessed from the Schematic Editor by choosing the Tools » Annotation » Annotate Schematics command from the main menus. First, ensure that one of the source schematic documents for the project you wish to annotate is open as the active document in the main design window. After launching the command, the Annotate dialog will appear.

Use the dialog to systematically assign designators to all or selected parts in selected sheets of the active project and ensure that designators are unique and ordered based on their position. Once annotation configuration options have been defined on the left, clicking the Update Changes List button will update the Proposed Change List on the right so that all designator changes can be reviewed prior to being applied. Only designators that have not previously been set i.

So, if the intention is to update all designators in the design, they should be first reset by pressing the Reset All button. After reviewing the list of proposed changes, click the Accept Changes Create ECO button to launch the Engineering Change Order dialog where a final layer of validation and reporting can be applied.

Once the ECO is executed, the annotation changes will be applied to the design. This command is used to interrogate all source schematic documents for the active project that are enabled for annotation and assign a unique designator to any component that currently does not have a designator.

Annotation is carried out quietly – making it possible to apply all of the previous settings of the Annotate dialog without needing to reopen the dialog. This is especially useful if the design is going through a rapid phase of development and the designer wants to quickly annotate prior to compiling the design. This command is accessed from the Schematic Editor by choosing the Tools » Annotation » Annotate Schematics Quietly command from the main menus.

First, ensure that one of the source schematic documents for the project whose unassigned component designators you wish to annotate is open as the active document in the main design window. After launching the command, any source schematic documents that have been enabled for annotation and that are currently closed will be opened and hidden. A confirmation dialog will appear, summarizing the number of designators requiring update and asking whether you wish to proceed with the changes.

After clicking Yes , all unassigned component designators across all annotation-enabled schematic sheets of the active project will be quietly annotated – each receiving a unique designator.

This command is used to interrogate all source schematic documents for the active project that are enabled for annotation and re-annotate all components therein in accordance with the annotation scheme currently defined in the Annotate dialog.

First, ensure that one of the source schematic documents for the project whose component designators you wish to re-annotate is open as the active document in the main design window.

A dialog will appear that details the number of designators that need updating and asks for confirmation to proceed. After clicking Yes , all component designators across all annotation-enabled schematic sheets of the active project will be re-annotated, where necessary, to comply with the current positional annotation scheme defined in the Schematic Annotation Configuration region of the Annotate dialog.

This command is used to reset all component designators in the active project, across all source schematic sheets that are enabled for annotation. This can be especially useful if large portions of content have been cut and pasted from different sources into a new design. This command is accessed from the Schematic Editor by choosing the Tools » Annotation » Reset Schematic Designators command from the main menus.

First, ensure that one of the source schematic documents for the project whose component designators you wish to reset is open as the active document in the main design window. A confirmation dialog will appear that summarizes the number of designators requiring update and asking whether you wish to proceed with the changes. After clicking Yes , all component designators across all annotation-enabled schematic sheets of the active project will be reset appearing in the form: R? This command is used to reset all duplicated component designators in the active project across all source schematic sheets that are enabled for annotation.

Duplicate designators typically occur when duplicating portions of a design when the newly copied components will still hold the same designator values as those from where they were copied.

This command provides a fast way to reset duplicate designators to ‘? This command is accessed from the Schematic Editor by choosing the Tools » Annotation » Reset Duplicate Schematic Designators command from the main menus. First, ensure that one of the source schematic documents for the project whose duplicate component designators you wish to reset is open as the active document in the main design window.

After clicking Yes , all duplicate component designators found across all annotation-enabled schematic sheets of the active project will be reset appearing in the form: R?

This command is accessed from the Schematic Editor by choosing the Tools » Annotation » Back Annotate Schematics command from the main menus.

First, ensure that one of the source schematic documents for the project whose component designators you wish to back annotate is open as the active document in the main design window. Browse to and select the required. After clicking Open , an information dialog will appear that lists how many changes to designators have been made since the previous state and how many have been made since the original state.

At this point, the changes are not actually implemented. Click OK to bring up the Annotate dialog , from where you can view the proposed changes to the current designators before deciding to create an ECO to implement them. In this way, the entire design can be re-annotated without actually modifying the original Device Sheet s. Annotation text file. It includes additional keywords for customizing naming schemes and allows them to be applied to all or only a select range of parts. After launching the command, the Board Level Annotate dialog will appear.

Use the dialog to assign designators to the PCB components as required. Annotation file within the project. Some settings may also be changed within the main project document requiring it to be saved.

This command is used to update placed instances of components on chosen schematic sheets, with modified information from a source library. The update feature allows you to pass changes to parameters, as well as model and graphical information. This command is accessed from the Schematic Editor by choosing the Tools » Update From Libraries command, from the main menus. First, ensure that one of the source schematic documents for the project whose components you wish to update, is open as the active document in the main design window.

After launching the command, the Update From Library dialog will appear. The dialog provides controls that allow you to fully control not only which components get updated, but also how. You can choose to fully replace the placed instance with that in the library, or just update any of: Graphical attributes, parameters, or models. Full control is available at the parameter-level, to determine which parameters get updated for a component, and how.

For parameter and model update actions, still further control is afforded through the Library Update Settings dialog. Access this dialog by clicking the Advanced button.

Not only can you define the default, global update actions for parameters and models using this dialog, but also control which specific parameters and models are included in the update. After defining the scope of the update as required, and the default actions to be carried out, you could simply click Finish. Should you wish to further refine the update on a per-component basis, prior to generating an ECO, click Next to access the second page of the dialog.

After all update options are configured as required, clicking the Finish button will launch the Engineering Change Order dialog , and a final layer of validation and reporting can be applied. Once the ECO is executed, the changes to the specified component instances are implemented on the affected schematic sheets. This command is used to check the component footprints on the active PCB document, against the libraries from which they were sourced, and perform updates to chosen components, as required.

This ensures that all footprints in the design adhere to the authorized footprint libraries. First, ensure that the PCB document whose footprints you wish to check, is open as the active document in the main design window. Use this dialog to choose which layers of the PCB and library footprint you wish to compare. This is important, as in some designs, certain layers of the footprint may not be used, and extra comparisons will take extra time to process.

At this point, and if you want to update all footprints to match those in the source libraries, you can simply click the Update All Footprints Create ECO button, and implement the changes to the design through a subsequent Engineering Change Order.

However, should you wish to inspect differences that are detected in detail, and determine which footprints to include in an update, prior to generating an ECO, click OK to access the Update From PCB Libraries dialog. After browsing differences and configuring which footprints you wish to have updated, click the Accept Changes Create ECO button. The Engineering Change Order dialog will appear, with which to implement the changes. This command is used to check the component footprint under the cursor or the currently selected components on the active PCB document, against the libraries from which they were sourced, and perform updates to those components, as required.

This ensures that the chosen footprints in the design adhere to the authorized footprint libraries. At this point, and if you want to update the footprint s to match those in the source libraries, you can simply click the Update All Footprints Create ECO button, and implement the changes to the design through a subsequent Engineering Change Order. This command is used to update the parameters in components placed on schematic documents or defined in a schematic library document , with values specified for those same parameters in corresponding linked component records in an external database.

Linkage is performed through the use of an intermediary linking file, which can be one of the following:. After launching the command, the Update Parameters From Database dialog will appear. Use this dialog to determine the scope of the update. For placed components, for example, this would entail specifying which schematic sheets in the active project are included, and the component types. After clicking OK , the external database will be queried for matching components.

Use the controls provided in the dialog to fully control which updates to proceed with, and which to reject. You can reject updates to all parameters for a selected component, or for specific parameters of that component. Use the Engineering Change Order dialog that appears to validate and then execute the updates accordingly.

If you realize there is an update you really don’t want to proceed with, simply disable the applicable change order entry. This command is used to access the Annotate Compiled Sheets dialog. This dialog allows you to quickly number the compiled sheets physical instances of a sheet in the active design project. This command is accessed from the Schematic Editor by choosing the Tools » Annotation » Annotate Compiled Sheets command from the main menus.

After launching the command, the Annotate Compiled Sheets dialog will appear. Use the controls available in the dialog to define sheet numbering as required. If your organization has a specific number or naming system that cannot be automated through the Annotate Sheet controls, custom sheet names and numbers can be written directly into the SheetNumber field.

This command is used to access the Item Manager dialog. The Item Manager is a powerful tool providing two key abilities in relation to components and sheets of re-usable schematic circuitry in a board design project:. This command is accessed from the Schematic Editor by choosing the Tools » Item Manager command from the main menus. After launching the command, the Item Manager dialog will appear. The dialog presents all components and sheet symbols found in a single schematic sheet free document , or the set of schematics in the active design project.

Use the controls available in the dialog to replace unmanaged items with managed ones, or to keep existing managed items synchronized with their source items in an Altium Vault, as required. Use the tabs at the bottom of the grid region to populate “filter” the region with the tab-specific items in the current design.

For design components, this can also be performed in a more automated fashion, using the manager’s auto-matching feature – taking the unmanaged design components and attempting to match each one with a managed Component Item in a connected vault.

The matching process takes the Design Item ID of an unmanaged design component and compares it against the Comment property of managed Component Items in a vault. When a match is found, that managed Component Item will be proposed for the update. To run this process, simply click the Automatch button. The Automatching items dialog will appear with the results of the matching process.

For a successful match, the Messages field will display successful matches in green text and include a reference to the name of the successful Rule.

If there is an error preventing a successful match, the entry will be in red text and a reference included indicating the reason for the error or matching failure. A different or additional Rule will need to be created to achieve a successful match for those components.

Also note that any error will be shown in red text, including when a Rule detects more than one Vault Item component match. This conflict is regarded as an ‘ambiguous’ result, and can be resolved in the Item Manager dialog. Click OK to accept the links — the information in the Automatching items dialog will be copied to the New Settings region back in the Item Manager. To bring out of date items up to date they must first be selected. Once they are selected, right-click and choose Update to latest revision from the menu.

The New Settings region of the dialog will then show the detail of each new Item-Revision. Simply access the associated properties dialog for an item, which will now show a link back to the corresponding source vault Item.

Alternatively, verification can be performed quickly back in the Item Manager , which updates to reflect the new settings for the items in the board design project, in the Current Settings region of the grid.

The No ERC object is a design directive that can operate in two modes. In its specific mode, the directive is configured to target one or more specific violations, allowing suppression of selected warning or error conditions, while allowing any other warning or error to be detected and reported.

First, ensure that a source schematic document for the project whose No ERC directive you wish to interrogate, is open as the active document in the main design window. After launching the command, the active project is compiled and the NoERC Manager dialog will appear. From here, you can move through the list of nets with directives applied, and edit any number of No ERC directives. Using the dialog, you are able to browse the actions that will be taken to implement those changes.

You can disable any actions as required – you always have full control of what gets changed. When ready, execute the ECO and the changes will be effected. After launching the command, the Database Options dialog will appear. The dialog is divided into two tabs, the nature of which depends on the type of linkage file you are using:. This command is used to access a dialog with which to define the connection to the external database, and additional advanced options relating to. After launching the command, the Database Connection dialog will appear.

This dialog is divided into two tabs:. The Wizard essentially decompiles nominated integrated libraries, with each library used to build a separate database table in a chosen target database, complete with parameter and model information extracted from the components therein.

A specified Database Library file is then used to provide connection to that database. First, ensure that the Database Library file to be used as the linkage file to the external database, is open as the active document in the main design window. Use the pages of the Wizard to set up for translation as follows:. After choosing the source integrated libraries, click Next to proceed with the conversion.

A progress bar will be displayed, along with information on the current library being translated. After the conversion has completed, click Finish to make the specified Database Library file active in the main design window. Using Altium Documentation. Now reading version For the latest, read: DocumentOptions for version Parent page : WorkspaceManager Commands The following pre-packaged resources, derived from this base command, are available:.

Manage Parameters. Use If you want to manage the parameters across the schematics of an entire project, first ensure that a schematic associated to the required project is open as the active document in the main design window.

Should you wish to edit the parameters for only specific objects in the design, select these objects as required and enable the Selected Objects Only option. Only objects in your selection will be included, provided the relevant object kind has been enabled in the Include Parameters Owned By region of the dialog. View Design Channels for Active Project.

Access This command is accessed from the active document’s editor by choosing the Project » View Channels command, from the main menus where available.

Use First, ensure that the project whose components you wish to view, is the active project. Tips Logical designators are those designators assigned to the components of the source schematics. Physical designators are those designators that are assigned to the components once they are placed in the PCB design. This is particularly relevant when considering multi-channel designs.

The logical designators for the replicated channel components may be the same, but each component must have a unique physical designator in the PCB design. For multi-channel designs, changes to the component designator format are carried out on the Multi-Channel tab of the Options for Project dialog. All schematic source documents are required to be open for compilation. These documents are opened and automatically hidden in order to prevent clutter in the tabbed area of the main design window.

Hidden documents are given the blank document icon -. View Design Channels for Focused Project. Access This command can be accessed from the Projects panel by: Right-clicking on the entry for the required project or one of its source documents and choosing the View Channels command, from the context menu.

Clicking to focus the required project or one of its source documents , then clicking the Project button and choosing the View Channels command from the context menu. Use After launching the command, the source schematic documents for the focused project are compiled and the Project Components dialog appears. Manage Component Links for Active Project. It is a good idea to have all components matched using unique IDs so that annotation of designators in either the schematic or PCB document can be carried out with the knowledge that the documents can still be re-synchronized at any stage.

The documents can still be synchronized even if components aren’t matched by unique IDs, but in this case, you will be prompted to match the components by designators only – comment and footprint are not taken into account, and therefore it is possible that matching of some components is carried out incorrectly. The reason that manual linking of components is only carried out from within the PCB document, is that only the PCB component footprints need to be updated with the unique ID information – it is already present on the schematic side.

Manage Component Links for Focused Project. The reason that manual linking of components is only carried out from the PCB document, is that only the PCB component footprints need to be updated with the unique ID information – it is already present on the schematic side. Manage Footprints. Access This command is accessed from the Schematic Editor by choosing the Tools » Footprint Manager command, from the main menus.

Use First, ensure that a schematic source document, associated to the required project, is open as the active document in the main design window. Features include: Ability to add, edit, and remove footprint models for one or more selected components.

Copy footprints between components. Changing current footprint assignment the footprint that will currently be used to represent a component in the PCB domain, from multiple that may be available to that component. Footprint validation – to ensure that footprint models are truly available, and especially those set to be the current model.

Tips For a design containing device sheets, the components on those sheets will only be listed provided the sheets are not marked as being Read-only. Toggle the Read-only state for device sheets in projects from the Data Management – Device Sheets page of the Preferences dialog. Manage Design Variants for Active Project.

For an in-depth walk-through of Altium Designer’s capabilities with respect to variants, see Design Variants. After selecting an alternate part, the software checks for pin-compatibility between the chosen alternate component, and the original base design component. To be pin-compatible, the alternate must have the same number of pins as the original component, and those pins must be identical in their location, and electrical type.

No equality in the graphical primitives used in the symbols for the two components is required. If the software detects that the alternate component is not pin-compatible, a Confirm dialog will appear, requiring your OK to proceed with the replacement. While you can proceed with the use of a pin-incompatible alternate component, bear in mind the potential impact on the wiring, and that you may also encounter an error violation when performing a subsequent compilation of the design.

Manage Design Variants for Focused Project. Configure Project Options for Active Project. Access With a document for the required project open as the active document, this command is accessed from that document’s editor by choosing the Project » Project Options command, from the main menus.

Use First, ensure that one of the target project’s associated design documents is open as the active document in the main design window. The dialog is divided over a number of tabs, the availability and content of which, depends on the specific project type: Error Reporting – enables you to define the reporting levels for each of the possible electrical and drafting violations that can exist on source schematic documents when compiling the project.

When the project is compiled, these violation settings will be used – in conjunction with the defined settings on the Connection Matrix tab – to test the source documents for violations. There may be points in the design that you know will be flagged as electrical violations, which you do not want to be flagged.

Leave a Reply

Your email address will not be published.