Customizing the Policy File to Generate Derived Data
To generate derived data to your specifications, you can create a custom policy file for your Cadence Team Design Option project. For your convenience, a Cadence-supplied policy file template named sdm_policy.xml is available at:%CDSROOT%\share\cdssetup\sdm\policies.
|
|
Do not modify the Cadence-supplied policy file template. Rather, copy it as your custom policy file to the following location:<adw_conf_root>\<Company>\<Site>\cdssetup\sdm\policies\sdm_policy.xml, and make your changes there.
|
In addition to creating a custom policy file with the required derived object definitions and commands, you must also modify the
ADWSchemaConfig file on the client systems where the derived data generation is invoked. This mapping file specifies how design objects are expected to pass data between the
Cadence Team Design Option client and
Windchill server. For more information, see
Customizing the ADWSchemaConfig.xml File to Generate Derived Data.
You can generate the following types of derived data:
• Master BOM (logical or physical)
• Variant BOM (logical or physical)
|
|
The Windchill preference: Default Part Structure Source must be set to determine whether BOMs are generated from the schematic or the physical board object. For additional information, see Setting Preferences in Windchill. |
• PDF (logical)
• Generic (user-defined)
• Viewable (graphical)
The following derived object definition section is provided for your reference. This section is annotated and contains all the derived data definitions that are currently available for Cadence Team Design Option. When editing your custom policy file, you can add (if not already included), or modify the existing derived object definitions to define the derived data objects that you want to generate. For a description of the definition code syntax, see the Cadence document “Allegro Design Authoring Team Design Option User Guide”.
|
|
Modification of the existing derived object definitions in your custom policy file must be carefully considered. That is, do not modify the Includes and Excludes sections of derived object definitions unless you are sure about the impact of the changes. If necessary, contact your Cadence Support or Services team for assistance.
|
\\ **************************Derived Object Definition Section************************
\\ Master BOM Derived Object (Logical)
<derivedObject label="BOM" name="LogicalBom" type="ADWDerivedDataLogicalBom">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}
/derived_data/logical.bom"/>
</includes>
</attachment>
<tools>
<tool args="${projdir}/${design_lib}/${design_name}/derived_data/logical.bom"
label="Open" name="notepad"/>
</tools>
</derivedObject>
\\ Master BOM Derived Object (Physical)
<derivedObject label="BOM" name="PhysicalBom" type="ADWDerivedDataPhysicalBom">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}/derived_data/physical.bom"/>
</includes>
</attachment>
<tools>
<tool args="${projdir}/${design_lib}/${design_name}/derived_data/physical.bom"
label="Open" name="notepad"/>
</tools>
</derivedObject>
\\ Variant BOM Derived Object (Logical)
<derivedObject label="BOM" name="LogicalBom" type="ADWDerivedDataLogicalBom">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}/derived_data/*.rpt"/>
<include path="${projdir}/${design_lib}/${design_name}/bom/*"/>
<include path="${projdir}/${design_lib}/${design_name}/variant/*"/>
</includes>
</attachment>
<tools>
<tool args="-proj,${projdir}/${cpm}" label="Open" name="vedit"/>
</tools>
</derivedObject>
\\ Variant BOM Derived Object (Physical)
<derivedObject label="BOM" name="PhysicalBom" type="ADWDerivedDataPhysicalBom">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}/derived_data/*.rpt"/>
<include path="${projdir}/${design_lib}/${design_name}/bom/*"/>
<include path="${projdir}/${design_lib}/${design_name}/variant/*"/>
</includes>
</attachment>
<tools>
<tool args="-proj,${projdir}/${cpm}" label="Open" name="vedit"/>
</tools>
</derivedObject>
\\ PDF Derived Object (Logical)
<derivedObject label="PDF" name="LogicalPDF" type="ADWDerivedDataLogicalPDF">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}/derived_data/sch.pdf"/>
</includes>
</attachment>
<tools>
<tool args="${projdir}/${design_lib}/${design_name}/derived_data/sch.pdf"
label="Open" name="AcroRd32"/>
</tools>
</derivedObject>
\\ Viewable Derived Object (graphical)
<derivedObject label="Viewable" name="Creo View ECAD"
type="ADWDerivedDataViewable">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}
/viewable/${design_name}.pvz"/>
</includes>
</attachment>
<checkin>
<all>
</all>
</checkin>
<tools>
</tools>
</derivedObject>
\\ Generic Derived Object (Artwork example shown here - others possible with the
\\ modification of this code such as MFG, ASSY, Gerber, ICtest, CM)
<derivedObject label="Artwork" name="Artwork" type="ADWDerivedDataGeneric">
<attachment>
<includes>
<include path="${projdir}/${design_lib}/${design_name}/derived_data/artwork.art"/>
</includes>
</attachment>
<tools>
<tool args="${projdir}/${design_lib}/${design_name}/derived_data/artwprk.art"
label="Open" name="vedit"/>
</tools>
</derivedObject>
The following tools section is provided for your reference. This section is annotated and contains all the derived object command definitions that are currently available for Cadence Team Design Option. When editing your custom policy file, you can add (if not already included), or modify the existing command definitions to define the derived data objects that you want to generate. For a description of the definition code syntax, see the Cadence document “Allegro Design Authoring Team Design Option User Guide”.
\\ ***********************************Tools Section**********************************
\\ Defines elements (commands or tools) that can be launched on a design object.
\\ The following commands define how derived objects are generated.
\\ Master BOM Generation (Logical)
<command args="-proj,${projdir}/${cpm}, -nographic,-f,SS, -t,
C:/Cadence/ADWLIB/scripts/ptc_ewwgm.bom,-delim,${COMMA},-o,
${projdir}/${design_lib}/${design_name}/derived_data/logical.bom"
cond="${design_name},==,${root_design}"
label="Generate BOM" name="bomhdl" type="ADWDerivedDataLogicalBom"/>
\\ Master BOM Generation (Physical)
<command args="-proj,${projdir}/${cpm}, -nographic,-f,SS, -t,
C:/Cadence/ADWLIB/scripts/ptc_ewwgm.bom,-delim,${COMMA},-o,
${projdir}/${design_lib}/${design_name}/derived_data/physical.bom"
cond="${design_name},==,${root_design}"
label="Generate BOM" name="bomhdl" type="ADWDerivedDataPhysicalBom"/>
\\ Variant BOM Generation (Logical)
<command args="-proj,${projdir}/${cpm},-f,SS,-t,
C:/Cadence/ADWLIB/script/ptc_ewwgm_schematic.bom,-delim,${COMMA},-o,
${projdir}/${design_lib}/${design_name}/derived_data/Design.rpt"
cond="${design_name},==,${root_design}"
label="Generate BOM" name="bomhdl" type="ADWDerivedDataLogicalBom"/>
\\ Variant BOM Generation (Physical)
<command args="-proj,${projdir}/${cpm},-f,SS,-t,
C:/Cadence/ADWLIB/script/ptc_ewwgm_board.bom,-delim,${COMMA},-o,
${projdir}/${design_lib}/${design_name}/derived_data/Design.rpt"
cond="${design_name},==,${root_design}"
label="Generate BOM" name="bomhdl" type="ADWDerivedDataPhysicalBom"/>
\\ PDF Generation (Logical)
<command args="-proj,${projdir}/${cpm}, -cell,${design_name},
-view,${sch_view}, -mode,hier, -all,-file,${projdir}/${design_lib}/
${design_name}/derived_data/sch.pdf" label="Generate PDF" name="publishpdf"
type="ADWDerivedDataLogicalPDF"/>
\\ Generic Generation (Artwork example shown here - others possible with the
\\ modification of this code, such as MFG, ASSY, Gerber, ICtest, CM)
<command args="-p,${projdir}/${design_lib}/${design_name),
-o,${design_name},${projdir}/${cpm}"
label="Generate Artwork" name="C:\Cadence\ADWLIB\scripts\adw_artwork.bat"
type="ADWDerivedArtwork"/>
To Generate a Viewable Through the TDO Application
|
|
• Viewables are Windchill specific and provide a thumbnail graphic of the schematic or board.
• PTC Creo View must be installed on the client machine.
• adw_pvs.bat is used on the client to generate the viewable as a .pvz file.
• The adw_pvs.bat file contains the following commands:
@ECHO ON
cd /D "C:\Program Files\PTC\Creo 3.1\View ECAD Adapters\bin"
"C:\Program Files\PTC\Creo 3.1\View ECAD Adapters\bin\pvecad2pvs.exe"
"%1" "%2" "%3" "%4" "%5">"%2/pvecad2pvs.log"
cd /D %2
cdsZip %4.pvz %4.eda %4.pvs
The above commands specify the default Creo View ECAD adapters installation path. Modify the path to specify your installation directory.
|
To generate a viewable for TDO board/schematic object through the TDO application, you need to configure/install the following:
1. Install Creo View ECAD adapters on the client system.
2. Create a bat file in which you define the viewable generation related command and place it on client system. [See above note for the content of adw_pvs.bat, and edit the path for Creo View ECAD Adapter installation as per current environment.]
3. Add ADWDerivedDataViewable derived object type in the ADWSchemaConfig.xml file. [It can be available at %ADW_CONF_ROOT%\@Company_name@\@site_name@\cdssetup\sdm\config location.]
Add the below lines to the ADWSchemaConfig.xml file:
4. From the TDO Policy file, invoke this bat file so it generates the viewable file for the respective object. [It can be available at %ADW_CONF_ROOT%\@Company_name@\@site_name@\cdssetup\sdm\policies location.]
In the policy file, add the following below highlighted part to viewable generation:
|
|
• The <command args> line is used for generating viewable file from design. [This defines RMB action name as Generate Viewable and run the script mentioned in the bat file. User needs to edit path as per bat file location].
• The <derivedObject label> line is used for defining the document type for viewable object.
• The <include path> line is used for including the viewable generated file during check-in as an attachment. [Attachment sent to Windchill.]
|
Related Topics
