Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Orcad Capture/Layout multiple boards

345 views
Skip to first unread message

Spehro Pefhany

unread,
Nov 20, 2001, 5:18:25 PM11/20/01
to
What's the correct way to organize a project that has multiple boards with
one sheet per board? I have three boards, three schematics and want to
generate three netlists and three different boards in Layout. Is it
necessary to make each board a separate project?

Best regards,
--
Spehro Pefhany --"it's the network..." "The Journey is the reward"
sp...@interlog.com Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog Info for designers: http://www.speff.com
/.-.\
(( * ))
\\ // Please help if you can:
\\\ http://dailynews.yahoo.com/fc/US/Emergency_Information/
//\\\
/// \\\
\/ \/

Don K.

unread,
Nov 21, 2001, 12:56:45 AM11/21/01
to
Spehro Pefhany wrote:
>
> What's the correct way to organize a project that has multiple boards with
> one sheet per board? I have three boards, three schematics and want to
> generate three netlists and three different boards in Layout. Is it
> necessary to make each board a separate project?


No. When you generate each netlist, you get to check a block whether the
netlist is for that one sheet or for the entire design.

My documentation and configuration techniques are still evolving,
but for now, I've decided to keep each layout in a separate directory
from its schematic to allow schematic revisions to be made without changing
the layout revision.

So far I've been keeping each board schematic in a separate project. My
schematics get changed a lot. I think things would get confusing
if I kept multiple revisions of several schematics within the same project,
along with their associated BOM's, etc.

So as it is now, to make a new revision I copy the project to a new directory
and rename it. This lets me ultimately archive old versions of the schematic.
The netlist can still point to the old Layout if that hasn't changed. If the
Layout is affected, I make a new directory for it, rename it and update it
from the new netlist.

Don
To reply by email, remove the postage.

steve

unread,
Nov 21, 2001, 12:03:15 PM11/21/01
to
Spehro,
I'm not sure if this is what you mean, but we have a project with many pcb's
in one design. To generate a pcb, we select the page in the design view of
capture, and tell it to make it the root. Then choose create netlist for
that sheet. That way, the netlist starts there, and goes down the hierarchy
if there is one. Then create pcb from that netlist. As far as layout, I
don't know anymore. We had to change to pads. I hate it. Very difficult to
get a good default board, unlike orcad.
Best,
Steve
"Spehro Pefhany" <sp...@interlog.com> wrote in message
news:REAK7.220205$YL3.69...@news3.rdc1.on.home.com...

Spehro Pefhany

unread,
Nov 21, 2001, 12:40:37 PM11/21/01
to
The renowned steve <s...@twcny.rr.com> wrote:
> Spehro,
> I'm not sure if this is what you mean, but we have a project with many pcb's
> in one design. To generate a pcb, we select the page in the design view of
> capture, and tell it to make it the root. Then choose create netlist for
> that sheet. That way, the netlist starts there, and goes down the hierarchy
> if there is one. Then create pcb from that netlist. As far as layout, I
> don't know anymore. We had to change to pads. I hate it. Very difficult to
> get a good default board, unlike orcad.

Yes, that's what I'm looking to do. Thanks Steve! I see the Design->Make
Root (which only shows up when the relevant folder is selected in the
design view, not when the the sheet is selected).

Thanks again & Best Regards,

Francesco

unread,
Nov 22, 2001, 3:32:57 PM11/22/01
to
On Wed, 21 Nov 2001 17:03:15 GMT, "steve" <s...@twcny.rr.com> wrote:

>if there is one. Then create pcb from that netlist. As far as layout, I

When I want to create more pcb/netslist in a design
I use a schematic folder for each pcb/netlist but
I don't use any hierarchical block, in order to avoid that netlist
follows the hierarchy by mean of some hierarchical block.
Bye.

0 new messages