kicad:schematic_symbol_management
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
kicad:schematic_symbol_management [2016/03/04 00:22] – [KICAD quicklib gen] mithat | kicad:schematic_symbol_management [2018/09/09 07:54] (current) – mithat | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== KiCad Schematic Symbol Management ====== | ====== KiCad Schematic Symbol Management ====== | ||
+ | <WRAP center important 60%> | ||
+ | The stuff here was written for versions of KiCad preceding 4.0. The latest versions of KiCad have introduced new library management features, rendering some of what follows obsolete. | ||
+ | </ | ||
===== Symbols, components, libraries ===== | ===== Symbols, components, libraries ===== | ||
Line 5: | Line 8: | ||
KiCad places schematic symbols into //component libraries// | KiCad places schematic symbols into //component libraries// | ||
- | <WRAP center | + | <WRAP center tip 60%> |
KiCad uses the term " | KiCad uses the term " | ||
</ | </ | ||
- | <WRAP center | + | <WRAP center tip 60%> |
There are two kinds of libraries in KiCad: **component libraries** (i.e., schematic symbol libraries), which are stored in '' | There are two kinds of libraries in KiCad: **component libraries** (i.e., schematic symbol libraries), which are stored in '' | ||
</ | </ | ||
Line 39: | Line 42: | ||
You should add new components only to user component libraries. See [[#User component libraries]] below. | You should add new components only to user component libraries. See [[#User component libraries]] below. | ||
- | <WRAP center | + | <WRAP center important 60%> |
**Even though you can import components into system and third-party libraries, you are strongly advised against making any changes to system and third-party libraries.** | **Even though you can import components into system and third-party libraries, you are strongly advised against making any changes to system and third-party libraries.** | ||
Line 51: | Line 54: | ||
For creating new components and for making changes to components in system or third-party component libraries, it is highly recommended that you use only libraries you have created yourself---what we will call //user libraries// | For creating new components and for making changes to components in system or third-party component libraries, it is highly recommended that you use only libraries you have created yourself---what we will call //user libraries// | ||
- | <WRAP center | + | <WRAP center important 60%> |
**Even though you can create/ | **Even though you can create/ | ||
Line 82: | Line 85: | ||
=== Hidden pins and automatic connections === | === Hidden pins and automatic connections === | ||
- | Power pins that are marked as hidden (i.e., the //Visible// property is unchecked) will automatically connect to nets with that name in the schematic.((Section 5.5.4 in the [[http:// | + | Power pins that are marked as hidden (i.e., the //Visible// property is unchecked) will automatically connect to nets with that name in the schematic: |
+ | |||
+ | > Eeschema automatically connects invisible power pins of the same name to the power net of that name.(([[http:// | ||
+ | |||
+ | This is a tradition dating back to the early days of EDA and one that today is mired in controversy. | ||
Our preference is to avoid this kind of automatic connectivity. While it has its advantages (e.g., it makes circuits, especially logic circuits, appear cleaner), because modern designs frequently use a number of power supply rails and grounds as well as power supply bypass and treatment schemes, it can create schematics that are confusing at best and impossible to draw at worst. | Our preference is to avoid this kind of automatic connectivity. While it has its advantages (e.g., it makes circuits, especially logic circuits, appear cleaner), because modern designs frequently use a number of power supply rails and grounds as well as power supply bypass and treatment schemes, it can create schematics that are confusing at best and impossible to draw at worst. | ||
Line 96: | Line 103: | ||
==== KICAD part generators ==== | ==== KICAD part generators ==== | ||
- | Creating packages with many pins in KiCad' | + | Creating packages with many pins in KiCad' |
- | + | ||
- | A script that will generate individual parts or complete libraries from a CSV description is [[https:// | + | |
An Internet search should reveal other solutions if neither of the above is suited to your needs or they become unavailable. | An Internet search should reveal other solutions if neither of the above is suited to your needs or they become unavailable. | ||
Copyright ©2011-2016 Mithat Konar. All rights reserved. | Copyright ©2011-2016 Mithat Konar. All rights reserved. |
kicad/schematic_symbol_management.1457050926.txt.gz · Last modified: 2016/03/04 00:22 by mithat