Hello,
EAGLE assumes that any part name is composed in the following way:
BASE_NAME|TECHNOLOGY|PACKAGE
some parts come with another order:
BASE_NAME|PACKAGE|TECHNOLOGY
How to handle this?
Thanks
Marco
Hello,
EAGLE assumes that any part name is composed in the following way:
BASE_NAME|TECHNOLOGY|PACKAGE
some parts come with another order:
BASE_NAME|PACKAGE|TECHNOLOGY
How to handle this?
Thanks
Marco
Marco Trapanese schrieb:
EAGLE assumes that any part name is composed in the following way:
BASE_NAME|TECHNOLOGY|PACKAGE
some parts come with another order:
BASE_NAME|PACKAGE|TECHNOLOGY
How to handle this?
IMHO, the "technology" is absolutely senseless/useless anyway. You get
the same effect just by setting a proper VALUE.
So all my libraries contain devices that are as generic as possible, and
none of them uses "technology". When putting them into the schematic, I
assign a meaningful value, and all is done.
Tilmann
Marco Trapanese schrieb:
EAGLE assumes that any part name is composed in the following way:
BASE_NAME|TECHNOLOGY|PACKAGE
some parts come with another order:
BASE_NAME|PACKAGE|TECHNOLOGY
How to handle this?
IMHO, the "technology" is absolutely senseless/useless anyway. You get
the same effect just by setting a proper VALUE.
So all my libraries contain devices that are as generic as possible, and
none of them uses "technology". When putting them into the schematic, I
assign a meaningful value, and all is done.
Tilmann
Il 08/04/2013 13:44, Tilmann Reh ha scritto:
IMHO, the "technology" is absolutely senseless/useless anyway. You get
the same effect just by setting a proper VALUE.
So all my libraries contain devices that are as generic as possible, and
none of them uses "technology". When putting them into the schematic, I
assign a meaningful value, and all is done.
My experience is different than yours. The technology field (since EAGLE
supports the "append" features for pin/pad) is very useful for me to
take care of the small differences among parts.
For example the C/I designator for temperature ranges is properly
handled with the technology fields, allowing you to have ONE part in the
library. Or think about an LDO or TVS family: they could have dozen of
different voltages. Each one with its own order code.
If you don't use the technology fields you must create a different part
for every variant!
The best would be to define the "part name" according to the
manufacturer specifications. But I admit this could be quite complex to
implement.
Marco