Stats

Locked Locked
Replies 15
Subscribers 164
Views 21727
Members are here 0

Document Control questions with Variant Schematics

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 over 18 years ago

Hi Ian,

You did not specify which of Cadence tool you are using for schematic.

We are using OrCad, which can handle Variants. Most our designs are used in different assemblies and Engineer Designers here preferred to deal with ONE schematic rather different schematic for each variant. To do this we opted to add User Property to symbols in OrCad to identify which variant build any given component is used.
On Documentation side they have written a customized tool that recognizes UP field out put in BOM. This customized tool can dump a separate BOM for each variant into company inventory database.

We find out handling ECO/ECR are much easier this way.

Regards,

Pantheon

Originally posted in cdnusers.org by pantheon
Cancel
Vote Up 0 Vote Down

Cancel

Reply

archive over 18 years ago

Hi Ian,

You did not specify which of Cadence tool you are using for schematic.

We are using OrCad, which can handle Variants. Most our designs are used in different assemblies and Engineer Designers here preferred to deal with ONE schematic rather different schematic for each variant. To do this we opted to add User Property to symbols in OrCad to identify which variant build any given component is used.
On Documentation side they have written a customized tool that recognizes UP field out put in BOM. This customized tool can dump a separate BOM for each variant into company inventory database.

We find out handling ECO/ECR are much easier this way.

Regards,

Pantheon

Originally posted in cdnusers.org by pantheon
Cancel
Vote Up 0 Vote Down

Cancel

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.