PDA

View Full Version : Rule In Power Pcb


phillipr
03-06-2002, 01:44 AM
Does anyone else have a bit of of a hang up about having the build and layer structure of the board being past over from the schematic.
I get a Schematic from the engineer with all the rules setup but the board layer structure cannot be define at that point.

I Know you can just modify the rules and send them back but the engineer might be working on the schematic still and updating rules as i work on the PCB, When you both make changes your stuffed.

It seems a lot of hassle going through all the rules you have put in to the Pcb and giving then to the engineer to put into the schematic.

Why Is it in the Schematic rules anyway??

Phillip Restall

petehouwen
03-06-2002, 07:20 AM
Setting up the rules in schematic is a handy way for the engineer to give you the information he needs. Once you get into layout and find that you really can't put all those BGA's on his single sided board, go ahead and change all of the rules. You don't need to pass them back to the schematic. When you synchronize the PCB, rules are not passed. That is a seperate operation. You can pass the rules back and forth if you wnat, but there really is no need to.

phillipr
03-06-2002, 07:37 AM
The Problem then arises when he changes his rules or adds new ones when you pass them though it changes all your Stackup info.

phillipr
03-06-2002, 07:40 AM
I understand that its useful to have all the net rules and extended rules i just don't understand why the build stack up needs to be specified.

Mark Larson
03-06-2002, 08:05 AM
The engineer needs to know the stackup so he can specify line widths and other parameters. He should be the one to do this upo front. it is then treated like any other design changes. You will need this info to run High Speed check under verify design

petehouwen
03-06-2002, 09:29 AM
Once an engineer hands over his schematic, it's ours. Any changes he needs made are input to the designer, who changes the schematic. That way, we don't get any of the strange route ripups and such during synchronize. It would be easier if the engineers knew enough about the programs to do this themselves, but they don't want to be bothered learning it.