| Both sides previous revision Previous revision Next revision | Previous revision |
| knowledge_base:professional:kicad [2023/06/21 23:50] – [Python Scripting] Normal User | knowledge_base:professional:kicad [2023/08/01 09:45] (current) – [Python Scripting] Normal User |
|---|
| * https://docs.kicad.org/doxygen-python-7.0/namespacepcbnew.html | * https://docs.kicad.org/doxygen-python-7.0/namespacepcbnew.html |
| * https://docs.kicad.org/7.0/en/pcbnew/pcbnew.html | * https://docs.kicad.org/7.0/en/pcbnew/pcbnew.html |
| | * (GERBER) https://gist.github.com/aster94/bd52972ab6dbf13a44fc046b4222f7e7 |
| | * (GERBER) https://gist.github.com/spuder/4a76e42f058ef7b467d9 |
| | * https://dev-docs.kicad.org/en/python/pcbnew/ (how to write pcbnew plugin) |
| |
| ==== Hide 3D Models ==== | ==== Hide 3D Models ==== |
| |
| https://gitea.isolo.org/cpan/KiCad_Plugins | https://gitea.isolo.org/cpan/KiCad_Plugins |
| | |
| | <code> |
| | # import pcbnew; print(pcbnew.PLUGIN_DIRECTORIES_SEARCH) |
| | |
| | C:\Program Files\KiCad\7.0\share\kicad\scripting |
| | C:\Program Files\KiCad\7.0\share\kicad\scripting\plugins |
| | C:\Users\TomWang\AppData\Roaming\kicad\7.0\scripting |
| | C:\Users\TomWang\AppData\Roaming\kicad\7.0\scripting\plugins |
| | C:/Users/TomWang/Documents/KiCad/7.0/scripting |
| | C:/Users/TomWang/Documents/KiCad/7.0/scripting\plugins |
| | C:\Users\TomWang\Documents\KiCad\7.0\3rdparty\plugins |
| | </code> |
| |
| <code> | <code> |
| </code> | </code> |
| |
| ==== Saving Configuration Files ==== | ===== Saving Configuration Files ===== |
| | |
| | https://docs.google.com/document/d/1Rq8i2Ay7qpGpffaj-AQmE-Xp88ikHhgyt0Ygpi8717o/edit#heading=h.osuronu74isn |
| | |
| | https://docs.kicad.org/7.0/en/kicad/kicad.html |
| |
| KICAD_CONFIG_HOME - If we consider how KiCad is started and how the path variables are defined, this is the most important of those variables. Namely, every other variable can be defined from within KiCad so that they are stored into KiCad's own configuration. But naturally you can't store the location of the configuration into the configuration. This is the only variable you absolutely must set from outside KiCad itself if you want to change it. Every other variable you can change through KiCad's Configure Paths dialog, provided that the variable hasn't already been set from outside KiCad as an actual system environment variable. | KICAD_CONFIG_HOME - If we consider how KiCad is started and how the path variables are defined, this is the most important of those variables. Namely, every other variable can be defined from within KiCad so that they are stored into KiCad's own configuration. But naturally you can't store the location of the configuration into the configuration. This is the only variable you absolutely must set from outside KiCad itself if you want to change it. Every other variable you can change through KiCad's Configure Paths dialog, provided that the variable hasn't already been set from outside KiCad as an actual system environment variable. |
| |XDG_RUNTIME_DIR|Unix only (excluding OSX). Directory for the lockfile (used for the "kicad is already running" warning). If this is not set, XDG_CACHE_HOME is used. If that is not set, either, $HOME/.cache is used. On non-Unix systems the lockfile is saved to a system specific fixed location. See *NOTE below.| | |XDG_RUNTIME_DIR|Unix only (excluding OSX). Directory for the lockfile (used for the "kicad is already running" warning). If this is not set, XDG_CACHE_HOME is used. If that is not set, either, $HOME/.cache is used. On non-Unix systems the lockfile is saved to a system specific fixed location. See *NOTE below.| |
| |
| | === Using Template to Save Board Settings === |
| | |
| | |
| | === GERBER out procedure === |
| | |
| | https://www.circuitstate.com/tutorials/how-to-get-your-kicad-pcb-design-ready-for-automated-assembly-kicad-6-tutorial/ |
| | |
| | https://www.pcbway.com/blog/help_center/How_to_Generate_Gerber_and_Drill_Files_in_KiCad_7_0_ab0d12bb.html |
| |
| ==== References ==== | ==== References ==== |