SCH and BRD file names

Robert schrieb:

Can the schematic and the board file in a project have different

names? The reason for asking this is that I consider the SCH file as

a representation of a populated board and the BRD file basically

represents the bare board, i.e. 2 different items and hence 2

different part numbers. There may even be multiple assembly options

resulting in different part numbers for each board assembly variant.

 

For example :

 

Assembled board, variant 1 part number : PBA-1601-01

Assembled board, variant 2 part number : PBA-1602-01

Assembled board, variant 3 part number : PBA-1603-01

...

 

Bare board part number : PCB-2600-01 used on all the above assemblies

 

My ideal file names would be PBA-160X-01.sch for the schematic (X

being a wildcard) and PCB-2600-01.brd for the associated board.

 

Is this possible with Eagle? I have to say I haven't tried it, just

wanted to ask first.

It just wouldn't make any sense. Note that schematic and board always

share the same netlist (they are consistent and automatically annotated

if you apply changes to one of the files). With which of your schematic

variants should the board be consistent?

If you don't need consistency, you can of course make (differently

named) copies of your schematic for the different variants. There will

be no annotation then, however.

And, to your last question: no, EAGLE detects schematic/board file pairs

only by their identical file names (and activates annotation only if the

files are consistent). If you use assembly variants, always draw the

"complete" (maximum) circuit in the schematic, and distinguish the

variants by the BOM.

(BTW, please don't post HTML here, and correct your line length.)

Tilmann

"Tilmann Reh" <tilmannreh@despammed.com> wrote in message

news:g8m94n$3qh$1@cheetah.cadsoft.de...

Robert schrieb:

 

Can the schematic and the board file in a project have different

names? The reason for asking this is that I consider the SCH file as

a representation of a populated board and the BRD file basically

represents the bare board, i.e. 2 different items and hence 2

different part numbers. There may even be multiple assembly options

resulting in different part numbers for each board assembly variant.

 

For example :

 

Assembled board, variant 1 part number : PBA-1601-01

Assembled board, variant 2 part number : PBA-1602-01

Assembled board, variant 3 part number : PBA-1603-01

...

 

Bare board part number : PCB-2600-01 used on all the above assemblies

 

My ideal file names would be PBA-160X-01.sch for the schematic (X

being a wildcard) and PCB-2600-01.brd for the associated board.

 

Is this possible with Eagle? I have to say I haven't tried it, just

wanted to ask first.

 

It just wouldn't make any sense. Note that schematic and board always

share the same netlist (they are consistent and automatically annotated

if you apply changes to one of the files). With which of your schematic

variants should the board be consistent?

 

If you don't need consistency, you can of course make (differently

named) copies of your schematic for the different variants. There will

be no annotation then, however.

 

And, to your last question: no, EAGLE detects schematic/board file pairs

only by their identical file names (and activates annotation only if the

files are consistent). If you use assembly variants, always draw the

"complete" (maximum) circuit in the schematic, and distinguish the

variants by the BOM.

 

(BTW, please don't post HTML here, and correct your line length.)

 

Tilmann

 

OK, I understand but I also think you misunderstood the first part of my

question. I don't want to have multiple schematic files but just 1 file that

comprises all the build options and from which the board is generated.

My "problem" is more of an administrative nature. I need to document

assembled boards as well as bare boards and obviously these must have

different part numbers. In my example I would have 1 schematic with document

ID = PBA-160x-01.sch containing all build options and I would make separate

BOM's for each build option (not from within Eagle but with Excel for

instance).

All files (gerbers & excellon...) related to the bare board would ideally

have the board's part number as a common file name and would be

distinguished by their extension.

Anyway, I'll continue using the board's part number for both schematic and

board as I have been doing so far and make a PDF of the schematic using the

assembled board's p/n as the file name for documentation purposes only.

Robert