How do you version your PCBs and schematics?

On 11/26/2012 08:54 AM, Matias Sjögren wrote:

Hi.

 

I just want to know how you decide versions on your PCBs and

schematics.

 

For example: 1. You have a PCB version A and schematic version A and

you just need to do a tiny fix(wich doesnt need anything in the

schamatic to be changed) on the PCB wich will become version B.

Generally, anything that required a board layout change gets a bump in

the revision.  So if you changed a resistor from an 0603 to an 0805, for

example, it goes to Rev B.

2. You have a PCB version A and schematic version A, and then you

have to change a component value(wich doesnt need anything in the PBC

to be changed) in the schematic wich will become version B.

Again, generally, a component value change (whether it's value,

tolerance, rating, etc), we append a digit to the revision.  So if all

you're doing is changing the value of a resistor, it goes from Rev A to

Rev A1.  The BOM is updated to the new component and always states the

revision (A, A1, B, etc) to which it applies.

I will even go so far as to list the changes between Rev A and Rev A1 in

a was/is format.  Something like

    "R43 WAS 4.7k 5% our P/N 1234, IS 4.7k 1% our P/N 1235"

It keeps it clear to my vendor what the differences are and makes it

easier and more accurate for them to know which part to load in place of

the old part.

The major revision tells us and our assembly house that a new stencil is

being used, and the part coordinates may be different.

A change in the minor revision (scenario 2 above), doesn't change the

stencil, or part coordinates, so the assembly house can use the same

pick-and-place program that was used in the prior revision.

Now that Eagle stores its data in XML format (since v6.0), it's much

easier to determine all the changes that were applied since the previous

release.

How do you handle versions on your PCB and schematic in these

scenarios?

These are policies that work well for us.  Perhaps it will help you

develop your own policy.  No matter what policy you develop for your own

use, stick to it with minimal exceptions.

Rules should not be broken without 500 layers of management approval.

Policies, however, are intended to be more flexible.

HTH,

    - Chuck

On 11/26/2012 08:54 AM, Matias Sjögren wrote:

Hi.

 

I just want to know how you decide versions on your PCBs and

schematics.

 

For example: 1. You have a PCB version A and schematic version A and

you just need to do a tiny fix(wich doesnt need anything in the

schamatic to be changed) on the PCB wich will become version B.

Generally, anything that required a board layout change gets a bump in

the revision.  So if you changed a resistor from an 0603 to an 0805, for

example, it goes to Rev B.

2. You have a PCB version A and schematic version A, and then you

have to change a component value(wich doesnt need anything in the PBC

to be changed) in the schematic wich will become version B.

Again, generally, a component value change (whether it's value,

tolerance, rating, etc), we append a digit to the revision.  So if all

you're doing is changing the value of a resistor, it goes from Rev A to

Rev A1.  The BOM is updated to the new component and always states the

revision (A, A1, B, etc) to which it applies.

I will even go so far as to list the changes between Rev A and Rev A1 in

a was/is format.  Something like

    "R43 WAS 4.7k 5% our P/N 1234, IS 4.7k 1% our P/N 1235"

It keeps it clear to my vendor what the differences are and makes it

easier and more accurate for them to know which part to load in place of

the old part.

The major revision tells us and our assembly house that a new stencil is

being used, and the part coordinates may be different.

A change in the minor revision (scenario 2 above), doesn't change the

stencil, or part coordinates, so the assembly house can use the same

pick-and-place program that was used in the prior revision.

Now that Eagle stores its data in XML format (since v6.0), it's much

easier to determine all the changes that were applied since the previous

release.

How do you handle versions on your PCB and schematic in these

scenarios?

These are policies that work well for us.  Perhaps it will help you

develop your own policy.  No matter what policy you develop for your own

use, stick to it with minimal exceptions.

Rules should not be broken without 500 layers of management approval.

Policies, however, are intended to be more flexible.

HTH,

    - Chuck

Chuck Huber schrieb:

Generally, anything that required a board layout change gets a bump in

the revision.  So if you changed a resistor from an 0603 to an 0805, for

example, it goes to Rev B.

...

Again, generally, a component value change (whether it's value,

tolerance, rating, etc), we append a digit to the revision.  So if all

you're doing is changing the value of a resistor, it goes from Rev A to

Rev A1.  The BOM is updated to the new component and always states the

revision (A, A1, B, etc) to which it applies.

...

The major revision tells us and our assembly house that a new stencil is

being used, and the part coordinates may be different.

 

A change in the minor revision (scenario 2 above), doesn't change the

stencil, or part coordinates, so the assembly house can use the same

pick-and-place program that was used in the prior revision.

We do it exactly the same way, except for using numbers for the board

revisions and letters if there are value changes (e.g. -R1, -R1a).

Tilmann