Stats

  • Locked Locked
  • Replies 15
  • Subscribers 164
  • Views 21727
  • 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

Document Control questions with Variant Schematics

archive

I have a number of questions about how cadence intends to deal with document and revision control. I have searched the forums, sourcelink and the help documentation to no avail. So I hope someone on this forum has experience with document control and cadence.

This post has very basic questions. I'll get to more difficult items later.

The variant schematic editor looks to be a very smart tool and it allows me to store the master board along with all daughter stuffings in one project file. This is very cool, but I have questions about how to do ECOs on the daughters.

We normally have a part number for each daughter schematic. This part number matches the number of the assembly. Each part number under the project can obviously be at different revision levels.

How do I show a daughter part number and revision on the variant schematic?

It looks to me that cadence treats the whole project as one item and does not have provisions to have sub part numbers and sub revisions.

I found that I can annotate variant schematics and add text notes to them that contain the part number and revision. But if I have to make a change to the base which then has to be reloaded to the variants, all of the text added to the variant is replaced by what was on the base.

Is there a way to manage custom text variables so that they can be populated with values through the variant editor?

We normally have ECO information contained on each daughter schematic, but I can't see how to do that with variants in cadence.

Thank you in advance for your help,

Ian Overholt
QSC Audio Products


Originally posted in cdnusers.org by IanO
  • archive

    Richard,

    I can understand how the variant editor changes the values on variants. And I have seen how the variant information can be backannotated to a variant schematic. But I still don't understand how to show any revision information on that variant.

    The only handle I currently see available to identify variant part numbers and revisions is in the name of the variant file itself. If the variant is backannotated to schematic named version. But this still doesn't allow me to say anywhere on the variant that ECO 8923 changed it from Rev A to Rev B and it happened last week.

    Using the file name to identify the part number and revision is a fairly low-tech document control situation - one we had to use with PCAD. I had higher hopes for cadence because it is a much more powerful tool.

    Thank you!
    -Ian


    Originally posted in cdnusers.org by IanO
  • archive

    "Whoops! I forgot cadence is composed of 10,000 tools that don't work the same way. :)"

    No you did not forget, I guess it went missing on me that CIS OrCAD and HDL are identical tools with differnt names!!!!!

    Thank You,


    P.


    Originally posted in cdnusers.org by pantheon
  • archive

    It sounds like we need to have a "custom text" definition section in the variant.dat files. Then you can edit the variant.dat to capture the ECO rev for each variant individually.


    Originally posted in cdnusers.org by dallas
  • archive

    Hello Dallas,

    Custom text in the variant.dat file could work. I would imagine the difficulty in implementing this would come from trying to place it somewhere on the schematic drawing. The custom text would have to be setup in such a way that you place the field on the base and update that field on the variant.

    Right now if you create a custom text variable, that variable applies to the whole project. So you can't have 2 values for the same variable in two separate schematics.

    I can't shake the feeling that there is a solution already built into concept hdl and I just haven't found it. It seems like this is a basic documentation need and therefore it is probably addressed already. But I'm a new cadence user, so maybe I'm giving too much credit.  :)

    -Ian


    Originally posted in cdnusers.org by IanO
  • archive

    Why do you not use one .cpm file per variant?
    Custom texts are store in cpm file, so:
    - One "master" cpm file to creta the "full board"
    - Several cpm's just to manage custom variables. It cans be used just for the "outputs": plots, pdf,....

    I have never use variant module (maybe in future?)

    Jean-Charles


    Originally posted in cdnusers.org by jcteyssier
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.