A
Andy Peters
Guest
Active8 <mTHISREMOVEcolasono@earthlink.net,invalid> wrote in message news:<MPG.1a5983ed94d0b8f3989787@news.west.earthlink.net>...
order parts to put on the board!
library"? I'm advocating the latter.
Consider a tool that has a footprint library, a symbol library, and a
"component libary" that marries the two. Say you have cheeseball quad
op-amps in your library: a TL074_SO is the SOIC version, and the
TL074_DIP is the DIP version. When you draw the schematic, place the
specific part you want, and all the info is there. No editing of
property fields (easily forgotten) needed.
with questions like, "What's the part number?" And if you want the
PCB layout person to know the footprint without having to ask you.
Again: think *component* library, not just symbol library and
footprint library.
field of that instance? And also edit the footprint field, too?
or even PCAD, to Eagle.
'em, or whatever. As long as you know which one is which.
Really, tho', you should work whichever way works for you. I prefer
having to look up part numbers once.
--a
Yeah, that makes you want to ask them for help.One of the most important features of an EDA tool is the components
library. A good library makes everyone's life easier.
I prefer good looking librarians.
OK, that's just PCB layout. If you're building PCAs, you need toThe idea is that the every component in the library has all of the
information needed to build a board.
Nope. Just that little piece of real estate within the place and/or
insertion outline, whichever is greater. Design rules dictate what
other objects can get inside or near that area. It also won't
specify plating type, thickness, or hole tolerance. Just Drill
size, pad dimensions, plated or non, electrical or non, silkscreen,
soldermask, assembly view, various text like reference, component,
and footprint... assembly view artwork, power plane clearance.
Place and insertion outline. Drill symbol. Orientation/place datum.
Lotta stuff for a part.
order parts to put on the board!
What, your tools don't have library browsers?When you place a symbol on the
schematic, that component will also have footprint info (for PCB
layout),
Only if the part was designed with default footprint name. You can
add or change it or make 2 identical parts with diff FPs so you
don't have to remember the LIB name.
Download/buy a footprint library, or download/buy a "componentmanufacturer part numbers (if your tools can spit out
bills-of-materials, which it damn well should!), perhaps even links to
spice models, Verilog sources, etc. The idea is that you do all of
that work upfront building your library.
Or download or buy a library if what you have sucks or is
incomplete.
library"? I'm advocating the latter.
Consider a tool that has a footprint library, a symbol library, and a
"component libary" that marries the two. Say you have cheeseball quad
op-amps in your library: a TL074_SO is the SOIC version, and the
TL074_DIP is the DIP version. When you draw the schematic, place the
specific part you want, and all the info is there. No editing of
property fields (easily forgotten) needed.
Well, if you want to avoid having your purchasing person pester youA good library will have a component for each and every
resistor/capacitor/etc.
Why? Because each part contains the part
number you use to order it, and the package info.
*Do* they, now?
Yep,
Oh. So I need a separate part for the 20 different 10k resistors I
use, each with a special name so I know which part I'm selecting
into the schem?
with questions like, "What's the part number?" And if you want the
PCB layout person to know the footprint without having to ask you.
Again: think *component* library, not just symbol library and
footprint library.
Yeah, but the PCB is only part of the design.because it's real easy to take a
generic resistor out of the generic library and modify its "value"
field, but at some point, you've got to make the PCB, and the PCB guy
needs to know if you want a through-hole 5% 10K resistor, or an 0805
1%, or whatever.
The PCB house doesn't care about component tolerance, a prototype
house does. Gerbers and drill files, mainly. Plating instructions
or take their default.
That's a different problemAnd, of course, the purchasing people need to have
an orderable part number.
That's still in production and not just collecting dust in the mfgs
catalog, muRata.
So, you place a TL074 on your schematic, and then edit the partnumI have a special partnum property field
field of that instance? And also edit the footprint field, too?
So, what do you do now that Jenny's not making your life easier?otherwise, I'd just
run the BOM and import it into excel where you can hand it off to a
serving wench to look up the numbers I had a gal at Newark who
would look up her nums for stuff like 74HC00 or 1N4004 and ask
which mfg and suffix and look up the suffixes meanings. Jenny.
Gone, AFAIK. A real gem. Made my life easier.
Ah, Eagle. That explains things. It's kinda hard going from Mentor,This may be redundant, but i wrote this first. TFB
Eagle is PCB only. With a suite, you set the footprint properties
in the schematic capture program or if you just want to do a board,
you place the footprint as a component.
or even PCAD, to Eagle.
Exactly my point.But just having a good footprint library doesn't mean you can just
go from BOM to ordering.
Right -- you could give the footprints the same names that TI givesMy libraries have pathname-like names and
there is no "SOIC" per se. and there's other numbers in the name
like the width and length of the package which is important for
placement and insertion.
'em, or whatever. As long as you know which one is which.
G-d forbid that there'd be a standard for package suffixes!Manufacturers and distributors use a suffix like SO for SOIC or ML
for QFN.
Really, tho', you should work whichever way works for you. I prefer
having to look up part numbers once.
--a