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