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

    Hello Richard,

    We also build many variants from one board. One project had 78 variants using one board. We typically pull a part number for the board at the beginning of the project. Usually during the course of adding variants, changes have to be made to the circuit board. At those times, we pull a new part number for the circuit board and build new variants from that. Eventually, the older variants will migrate to the newer circuit board. The project with 78 variants used three different board part numbers over its development lifetime. The variant migration is a much more difficult issue with cadence, but I'm first trying to grasp the more basic concepts of cadence document control.

    In the case of cadence, I could put the part number of the variant as the variant name. But I do not see how to populate any ECO information (ECO number, date, approval stamp) onto the variant schematics. There are custom text variables, but they only apply to the whole project - not to just a specific variant.

    We used PCAD in the past and we had to have a separate schematic for each variant. We had to maintain a separate master schematic which netlisted to the board. It was very difficult to keep the daughter schematics netlistable to the board. Often during migration from one board to another, we would lose some of the original variant information.

    My hope is that cadence can manage this information better than PCAD did (which wasn't very well). The variant editor gives me hope, but I need to be able to pass more than component value changes to the variants. I know cadence must have been programmed to deal with ECOs, I just don't understand how it's supposed to work.

    Thank you,
    Ian Overholt


    Originally posted in cdnusers.org by IanO
Reply
  • archive

    Hello Richard,

    We also build many variants from one board. One project had 78 variants using one board. We typically pull a part number for the board at the beginning of the project. Usually during the course of adding variants, changes have to be made to the circuit board. At those times, we pull a new part number for the circuit board and build new variants from that. Eventually, the older variants will migrate to the newer circuit board. The project with 78 variants used three different board part numbers over its development lifetime. The variant migration is a much more difficult issue with cadence, but I'm first trying to grasp the more basic concepts of cadence document control.

    In the case of cadence, I could put the part number of the variant as the variant name. But I do not see how to populate any ECO information (ECO number, date, approval stamp) onto the variant schematics. There are custom text variables, but they only apply to the whole project - not to just a specific variant.

    We used PCAD in the past and we had to have a separate schematic for each variant. We had to maintain a separate master schematic which netlisted to the board. It was very difficult to keep the daughter schematics netlistable to the board. Often during migration from one board to another, we would lose some of the original variant information.

    My hope is that cadence can manage this information better than PCAD did (which wasn't very well). The variant editor gives me hope, but I need to be able to pass more than component value changes to the variants. I know cadence must have been programmed to deal with ECOs, I just don't understand how it's supposed to work.

    Thank you,
    Ian Overholt


    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.