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
Parents
  • archive

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

    We're using SPB 15.7 with concept hdl and allegro pcb.

    Concept has the ability to repopulate the base schematic on demand and not maintain separate variant schematics. But how will the service department service the variant models without schematics? And when a variant is revised per an ECO, where is that ECO number and date recorded on the variant?

    I can think of ways around this by using external (not with the cadence database) control documents, but I really hope that cadence has better document control capabilities than this.

    Thank you!

    -Ian


    Originally posted in cdnusers.org by IanO
Reply
  • archive

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

    We're using SPB 15.7 with concept hdl and allegro pcb.

    Concept has the ability to repopulate the base schematic on demand and not maintain separate variant schematics. But how will the service department service the variant models without schematics? And when a variant is revised per an ECO, where is that ECO number and date recorded on the variant?

    I can think of ways around this by using external (not with the cadence database) control documents, but I really hope that cadence has better document control capabilities than this.

    Thank you!

    -Ian


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