Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 3572
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

variant editor won't see my DNI components

saipan59

Hi,

I am trying to use Variant Editor to make a DNI BOM report, as per our organization's process. I open Variant Editor, do a New Variant, fill in the four fields, click OK. My new variant appears in the left pane, with sub-folders of Components and Functions.

The problem is that the Components folder is empty - it does not populate with my DNI components as I expect it to.

I have an older project which works fine doing the same thing. I've checked every setting and dialog that I can think of that might possibly be related, but I can't find a difference. The newer project just doesn't work. I opened the various dialogs side-by-side, looking for a setting that is different, but found nothing different except the name.

Another hint: When I run Packager / Bill of Materials, select Variant BOM, and view the output, at the end of the file is "DNI Component List:", but the list is empty. On the older project, my DNI parts show up in the file as expected.

What could be set incorrectly in the project?

I'm running 16.6-S013 (v16-6-112AL), dated 7/1/2013 .

Thanks for any advice,

Pete

Parents
  • saipan59

    UPDATE:

    [This makes reference to a small test project that I was using for experiments.]

    With some experimenting, and talking to folks on another project, I just discovered this:

    The Variant Editor has a problem with using a part attribute named "VARIANT". In my project, DNI parts are identified with an attribute of VARIANT, and a value of DNI.

    As an experiment, I changed R701 and R728 attributes to be BOM_IGNORE=DNI, instead of VARIANT=DNI.

    In Variant Editor, select View / Customize Columns.

    Note that it allows you to add columns for various things, including BOM_IGNORE and VARIANT and others.

    *** But when I click Apply, the VARIANT column does not display. ***   The BOM_IGNORE column works as expected.

    Note that "VARIANT" is an option in the drop-down, and it lets you move it to the right-side box by clicking the right arrow, but it ignores it when try to display it.

    With the BOM_IGNORE column visible, I can now see the parts that have the BOM_IGNORE=DNI property (in this case, R701 and R728, which I manually changed). This makes it easy to select them as a group, and set them to be "DNI".

    SO, I think this allows me to move forward, knowing that using "VARIANT=DNI" is a problem.

    Pete

Reply
  • saipan59

    UPDATE:

    [This makes reference to a small test project that I was using for experiments.]

    With some experimenting, and talking to folks on another project, I just discovered this:

    The Variant Editor has a problem with using a part attribute named "VARIANT". In my project, DNI parts are identified with an attribute of VARIANT, and a value of DNI.

    As an experiment, I changed R701 and R728 attributes to be BOM_IGNORE=DNI, instead of VARIANT=DNI.

    In Variant Editor, select View / Customize Columns.

    Note that it allows you to add columns for various things, including BOM_IGNORE and VARIANT and others.

    *** But when I click Apply, the VARIANT column does not display. ***   The BOM_IGNORE column works as expected.

    Note that "VARIANT" is an option in the drop-down, and it lets you move it to the right-side box by clicking the right arrow, but it ignores it when try to display it.

    With the BOM_IGNORE column visible, I can now see the parts that have the BOM_IGNORE=DNI property (in this case, R701 and R728, which I manually changed). This makes it easy to select them as a group, and set them to be "DNI".

    SO, I think this allows me to move forward, knowing that using "VARIANT=DNI" is a problem.

    Pete

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.