Differences

This shows you the differences between two versions of the page.

--- software:eagle_cadsoft [2011/06/08 23:45] – [File location as recommendation by Eagle] admin
+++ software:eagle_cadsoft [2019/09/22 10:59] (current) – admin
@@ Line 1: / Line 1: @@
 ====== Eagle cadsoft ======
-This page is about Eagle((Easy Applicable Graphic Layout Editor)) Cadsoft, a computer program which helps designing schematic diagrams (schematics) and circuit boards (pcb)((Presuming one has the correct license for that)).
+This page is about using libraries with Eagle((Easy Applicable Graphic Layout Editor)) Cadsoft, a computer program which helps designing schematic diagrams (schematics) and circuit boards (pcb)((Presuming one has the correct license for that)).
-===== Using Custom Libraries ====
+===== Custom Libraries ====
 During a design process it is sometimes necessary to add components which are not available in the ready supplied libraries. For this, components can be created manually and imported in the design. The method for this requires some fundamental understanding how components are organized in Eagle, both in the application itself as on disk. Guidelines about library design and recommendations how to use consistent nomenclature should help a user to successfully manage such collections of components, upgrade or extend them with other packages.
 ===== Libraries within Eagle =====
-In the Control Panel within Eagle, one or more library folders may contain libraries with a long list of IC manufacturers, group of generic components or group specific symbols which can be browsed through.\\ When opening an existing library((a file with an .lbr extension, residing in a library folder)), one will observe that an item in such a library has for each device or device breed (i.e. equivalent components sharing the same functions but having different packages and/or symbols) primarily three entities:
+In the Control Panel within Eagle, library folders contain files with IC manufacturers, group of generic components or group of specific symbols (Like ground, power supply and drawing frames). Eagle treats each of these files as a library, containing devices ((These are components having a link between one or more Symbols and a Package)) or device sets((i.e. equivalent components sharing the same functions but having different packages and/or symbols, like a LM555D and LM555N\\ Please note that the definition of device sets is not very clear. A closer match would be device breed, which specifies more precise that devices which belong to the same breed share a common function.)). If a library is available in Eagle and opened((Shown in a library folder at the Control Panel, visible as a file with an .lbr extension and by clicking on the small triangle preceding the filename which unfolds the folder)) one will observe that a selected device or device set has primarily three entities:
-  * device: The real component, residing in a specific package with a specific symbol
+  * Device: The real component, residing in a specific package with a specific symbol.
-  * package: Footprint in the layout
+  * Package: Footprint in the layout
-  * symbol: Drawing in the schematic
+  * Symbol: Drawing in the schematic
-Each of these entities characterize a specific aspect of a component or component breed residing in a library.
+Each of these entities characterize a specific aspect of a component or component breed. The image below shows a selected library with the 555 timer IC component breed (Or in the Eagle jargon called device set).
-==== File location as recommendation by Eagle ====
+|  {{https://www.auditeon.com/xyz/projects/20110610_dev_lib_p01.png?404x260}}  |
-The default libraries which come together with the other installation files, can be found when clicking on Options->Directories. On OSX, this is in $EAGLEDIR/lbr, where $EAGLEDIR represents the application installation directory from Eagle. It is important to keep this directory unchanged, as software updates may overwrite files in this folder.\\ A suitable location to put your own libraries in, would be in a subfolder within your Eagle projects folder like the following structure:
+| Library example with the 555 timer IC, residing in the library\\ from linear and is defined in eight different devices, each\\ having different characteristics  |
-  * $Home/Backup/eagle
+===== Recommendations from Eagle for File Locations =====
+The default location for libraries which are created when installing Eagle, can be found when clicking on Options->Directories. On OSX, this is in $EAGLEDIR/lbr, where $EAGLEDIR represents the application installation directory from Eagle. Eagle recommends to keep this directory unchanged, as software updates may overwrite files in this folder.\\ Your own libraries should therefore be at another location. A suitable one would be in a subfolder within your Eagle projects folder like the following structure:
+  * $Home/Backup/eagle/
     * eagle_custom_libraries
       * dev_mylibrary1
@@ Line 25: / Line 27: @@
   $EAGLEDIR/lbr:$HOME/Backup/eagle/eagle_custom_libraries
-While we are configuring the libraries folder, one could do something similar for the projects folder:
+While configuring the libraries folder, one could do something similar for the projects folder:
   $HOME/Backup/eagle/eagle_projects:$EAGLEDIR/projects/examples
+If none of the libraries appear when adding a part, verify in the control panel at Libraries if the default libraries are enabled. To do this, in the control panel right click on a library and if not enabled, select Use.
+===== Design process =====
+Before the practical designing can be done, consideration should be made for a naming scheme. A consistent nomenclature will keep custom libraries in a healthy state.
+==== Nomenclature ====
+A consistent naming scheme can be best explained with the following example:
+^  Library Folder  | -> ^  Library  | -> ^  Device(s) or device set(s)  |
+|  %%$HOME/Backup/eagle/eagle_custom_libraries%%  | -> |  %%dev_marc.lbr%%  | -> |  ..., *555, NE5534, LM385, ...  |
+If we now look closer to the *555, we can draw the following scheme:
+^  Symbol  | <- ^  Device set  | -> ^  Device  ^  Package  ^
+| {{https://www.auditeon.com/xyz/projects/20110610_dev_lib_p02.png?77x92}}  | <- ^  *555  | -> | LM555D\\ LM555N\\ NE555D  | SO08\\ DIL08\\ SO08  |
+On the left side from the device set, we see a symbol from the timer IC. On the right side we see a list with devices and their packages. For each device within a device set, Eagle designates a different package to a separate device.\\ \\
+The placeholder '*' is not ideal because it also refers to devices which contain the number 555 but are not timer ICs. A better example can be made for example with an LM385 voltage reference diode:
+^  Library Folder  | -> ^  Library  | -> ^  Device(s) or device set(s)  |
+|  %%$HOME/Backup/eagle/eagle_custom_libraries%%  | -> |  %%dev_marc.lbr%%  | -> |  ..., *555, NE5534, LM385, ...  |
+If we now look closer to the [[http://www.ti.com/lit/ds/symlink/lm385-2.5-n.pdf|data sheet of the LM385]] or [[http://www.ti.com/lit/ds/symlink/lm285-adj.pdf|adjustable (LM385-adj)]], we see it contains one symbol with 3 pins and another with 8 pins, depending on the kind of package. With that information we draw the following scheme:
+^  Symbol  | <- ^  Device set  | -> ^  Device  ^  Package  ^
+|  | ^  LM385  | | | |
+| {{https://www.auditeon.com/xyz/projects/20110610_dev_lib_p03.png?46x32}}  | <- ^ | -> | LM385AYZ-2.5\\ LM385BXM-2.5\\ LM385M3-2.5  | TO-92\\ SO-8\\ SOT-23  |
+| {{https://www.auditeon.com/xyz/projects/20110610_dev_lib_p04.png?50x55}}  | <- ^ | -> | LM385BXZ\\ LM385BYZ\\ LM385BZ\\ LM385Z\\ LM385M\\ LM385BM  | TO-92\\ TO-92\\ TO-92\\ TO-92\\ SO-8\\ SO-8  |
+===== Component custom design =====
+A component must reside in a library. Therefore, to create or edit existing components, either -from the control panel- create first a new library or open an existing one via the menu. This will invoke the Library Editor window.
+|  {{https://www.auditeon.com/xyz/projects/20110611_dev_lib_p05.png?404x168}}  |
+^ Empty Library Editor window  ^
+In this window, from left to right you will find these basic commands:
+|  {{https://www.auditeon.com/xyz/projects/20110611_dev_lib_p06.png?200x70}}  |
+^ Library Editor commands ^
+  - Edit a drawing: With this button you can load a device or package for editing
+  - Edit a device or device set: In this window you do not draw anything, but only define which Package is used, which Symbol(s) is/are used (called Gate within a Device), which names are provided for the Gates (e.g. A, B), which technologies are available (E.g. 74L00, 74LS00, 74HCT00), whether the Device has additional user-definable attributes, whether there are equivalent Gates which can be interchanged (Swaplevel), how the Gate behaves when added to a schematic (AddLevel), the prefix for the component name (if a prefix is being used), whether the value of the component can be changed or whether the value should be fixed to the Device name, which pins relate to the pads of the Package (CONNECT command), whether a description for this component should be stored in the library.
+  - Edit a package
+  - Edit a symbol
+A device, device set, package or symbol can be removed from a library via the Library menu. To remove, you must open that device in the type Library Editor window first and then select from the menu the option Library -> Remove... and enter the name which refers to what you want to delete. (The package, symbol or device.) If it stills shows up in the concerning Library in the Control Panel, save the Library with the removed item.
+===== Links and more information =====
+  * [[https://learn.adafruit.com/eagle-tutorial-how-to-add-a-new-package-to-a-component/]] How to add a new package to an existing component

Auditeon

User Tools

Site Tools

Differences

Page Tools