The 16.6–2015 (also known as 16.6 QIR#9) Design Entry HDL (DEHDL) release contains upgraded capabilities for the Variant Editor – namely: Dynamic viewing of variants in the schematic editor Capturing variants on schematics Replacing a part with any other part using the Component Browser Support for hierarchical variants Here are a couple videos detailing these new capabilities. Read on for more details… Dynamic viewing of variants in the schematic editor A new toolbar and menus have been added for viewing variants. All available variants for the design are listed and the selection of a variant leads to the annotation of variant-specific information (properties) on the schematic sheets (e.g. Do Not Install, Option to Cross Out). It’s easy to switch between any of the variants as well as base views: True hierarchical schematic support is now available with occurrence-specific data and Cross Referencer data present in plots/PDF Publishing of any of the variants with complete data. User-defined properties/custom text can be assigned variant-specific data in the Variant Editor (placeholders on schematics are updated with variant-specific data). The Attribute form displays the variant name in the source column for variant-specific properties: There is an option on DNI Components - Cross Out DNI Property All Properties Visibility There is also color customization - Variant Specific Component Variant Specific Properties DNI Component DNI Cross When you perform a Save in the Variant Editor, it generates files specific to each variant containing variant-specific information. These files are used for dynamic display of data in DEHDL schematics. The variant details can be defined at the time of creating a new variant or editing existing variant details - Variant Name Variant Property Name-Value to be annotated on schematics DNI property value Variant-specific Custom Text values Special characters [/, ., =, , /, +, (, )] are now supported in the variant name and property values: Capturing variants on schematics Features available in the schematic Base View: Create Variant Edit Variant Remove Variant Launch Variant Editor View Schematic Variant Mark for Variant Features available in Schematic Variant View: Launch Variant Editor View Schematic Variant Mark for Variant Remove from Variant Mark as Do Not Install Make Preferred Modify Component Add Alternate Modify Properties When you create a new variant, the new variant dialog box appears and is pre-seeded with entries from the project and/or site .cpm file - Variant Property Name Variant Property Value DNI Value Custom Variables Specify Variant Name Modify any of the pre-seeded data, click OK, and the new variant is created and can be viewed in the Variant Editor. The DEHDL menus get updated to allow working on the new variant. You can edit and remove a variant as well. Launching the Variant Editor displays all the variant details: You can mark part instances for variant(s) by selecting one of more packaged instances on the schematic and mark them for variant(s). A context menu also available on instance(s). When block instance(s) are selected, the command operates on packaged instances of the block instances which are not packaged are ignored for all variant operations: When you’re in the schematic base view, a sub-menu shows all the available variants for selection. You have the option to select multiple variants and mark them. When you’re in the schematic variant view, only the current variant is shown in the sub-menu. Selected instance(s) are added to a variant and can be seen in the Variant Editor. When an instance(s) is part of a function or group, then a message is reported and that instance is ignored. The Remove from Variant is available in the schematic variant view. You can select one of more instances on schematic which are part of the variant and remove them. A context menu is also available on instance(s). When block instance(s) are selected, the command operates on packaged instances of the block. When instance(s) is not part of the variant, then a message is reported and that instance is ignored. When instance(s) is part of a function or group, then a message is reported and that instance is ignored. The Mark as Do Not Install is available in the schematic variant view. You can select one of more instances on schematic and mark them as DNI. A context menu is also available on instance(s). When block instance(s) are selected, the command operates on packaged instances of the block. When instance(s) are not part of variant, they are added to the variant and marked DNI. When instance(s) is part of a function or group, then the message is reported and that instance is ignored. The Make Preferred is available in the schematic variant view. You can select one or more instances on schematic and mark them as Preferred. A context menu is also available on instance(s). This does not work on block instance(s). When instance(s) are not part of a variant, they are added to the variant. When an instance(s) has been modified (part of a function or group or has a changed value or modified), then a message is reported and that instance is ignored. The Modify Component is available in the schematic variant view. You can select one or more instances on schematic and modify them. A context menu is also available on instance(s). It works on the same logical components, but does not work on block instance(s). When instance(s) are not part of a variant, they are added to the variant and modified. Part Table rows corresponding to the part are displayed for a new selection. The footprint of a newly selected component should be compatible with the original footprint. When an instance(s) is part of a function or group or has a DNI status, then a message is reported and that instance is ignored. The Add Alternate is available in the schematic variant view. You can select one instance on the schematic and add an alternate for it. A context menu is also available on the instance. It does not work on block instance(s). When an instance is not part of a variant, it is added to the variant and an alternate is added. Part Table rows corresponding to the part are displayed for an alternate selection. When an instance is part of a function or group or has DNI status, then a message is reported and that instance is ignored. The Modify Properties is available in the schematic variant view. You can select one instance on the schematic and Modify Properties for it. A context menu is also available on the instance. It does not work on block instance(s). Properties are added/modified specific to a variant for a selected instance. Property names to be displayed can be configured using a .cpm file directive. When an instance is part of a function or group or has DNI status, then a message is reported and that instance is ignored. Replacing a part with any other part using the Component Browser You have the ability to replace a part by selecting any part using the Component Browser: Verification ID is performed to check that the selected replacement part has the same footprint (JEDEC_TYPE property) and a compatible footprint file (\cdssetup\cjedectype.txt): There is an option to run custom code for further verification of the replacement part: Script File path can be specified using a project .cpm file directive Script File takes footprint names (Original and New) as Input Script File generates a log file which can be viewed Script File returns code, which is displayed You still have an option to continue replacing with the part not having a compatible footprint. The variant BOM reports display information about the replaced part. You can specify Replacement Component by just specifying a KEY property value for a new part. The property name can be configured using a .cpm file directive. You also have an option to specify a replacement component with no part table entry (this is useful for programmable devices). Support for hierarchical variants The variant definition from lower level hierarchical blocks is available for use at the top level. A one time import of variant data is required. The Variant Editor view changes to show the instances part of the lower level variant as separate groups / functions. There is the ability to include a variant coming from a lower level block in the top-level variant and the ability to mark the complete block instance as DNI. There is an option to generate hierarchical BOM reports (with a single entry for each block instance, and components coming from a block instance excluded from the main BOM). You have the ability to apply variants on block Instances. Variants defined inside a block are available for application on the block instance. Block variants can be specified on instances of Reuse Blocks only. Block Names are defined in the USE_SUBDESIGN or FORCE_SUBDESIGN directives. An additional property can be identified which needs to be present on the block instance for enabling the hierarchical variant application (the property name can be configured using a .cpm file directive): The hierarchical variant BOM report generated for a design displays a single entry for a block instance, the block name, the SUBDESIGN_SUFFIX property value for identifying the block instance, the applied variant name, and any variant-specific properties. The applied variant data is visible on the schematic canvas and in the Variant Editor. When a block instance is marked DNI, it is removed from the hierarchical variant BOM report. Each block has its own BOM report which can be referenced from the root design BOM Report. There is an option to generate a hierarchical BOM report available as a check box in the BOM UI. The report contains a single entry for each block instance. Only reuse blocks are listed as hierarchical block instances. Block names are defined in the USE_SUBDESIGN or FORCE_SUBDESIGN directives. Components coming from a block instance are excluded from the BOM report. An additional property can be specified for identifying hierarchical block instances. Properties on a block instance can be part of the BOM report: Please share your experience using these new features. Jerry “ GenPart ” Grzenia![]()
![]()
↧