[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: hierarchy refdes's
On Jun 16, 2008, at 8:40 PM, gene wrote:
> I'm already pretty deep into a hierarchical design and am wondering
> how
> the refdes is handled. Here's a simplified breakdown of the
> hierarchy:
>
> 2ch_top
> |_______Front-End
> |_______Front-End
>
> where Front-End is identical, instantiated twice.
>
>
> Eventually, I had intended to instantiate 2ch_top, 4 times:
>
> System_top
> |___________2ch_top
> |___________2ch_top
> |___________2ch_top
> |___________2ch_top
>
>
> So what happens to the reference designators? For example, if R1 is in
> the first front-end, how does that change in front-end #2, and
> furthermore in each instantiation under System_top? I recall reading
> about fully qualified names. Does that mean that the path info gets
> prefixed to each refdes?
Yes. Here's a fragment from a bill of materials from one of my projects:
refdes device value spec footprint
X12/R4 RESISTOR 470 5% 1/10W 0603
X8/R6 RESISTOR 5 5% 35W TO220SMD
X12/R3 RESISTOR 300k 1% 1/10W 0603
X8/R5 RESISTOR 300 5% 1W 2512
X12/R2 RESISTOR 100k 1% 1/10W 0603
X8/R4 RESISTOR 300 5% 1W 2512
X12/R1 RESISTOR 100k 1% 1/10W 0603
X8/R3 RESISTOR 300 5% 1W 2512
X8/R2 RESISTOR 300 5% 1W 2512
X8/R1 RESISTOR 300 5% 1W 2512
X3/Q2 IRLR014N unknown unknown TO252
I give all my higher level symbols "X" refdeses.
>
> Is it perhaps better to create identical copies of each schematic,
> label
> the refdes's on each. That'll be more schematics overall and
> harder to
> maintain changes.
>
Depends on what the customer prefers. Of late, they've been happy
with gEDA-style hierarchy.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd@xxxxxxxxx
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user