Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Latest commit

 

History

History
231 lines (156 loc) · 12 KB

README.md

File metadata and controls

231 lines (156 loc) · 12 KB

NOTICE

These plugins work only on old KiCad version (5.1.x).

The plugins that work under newer versions (V5, V6, ...) should be available under the KiCad's built in Plugin and Content Manager (PCM).

Currently (2023) there are four plugins available:

KiCad Action Plugins

This repository contains KiCad pcbnew Action Plugins.

All plugins have been tested on Kicad 5.1.x on Windows 7 / Windows 10. You need to have KICAD_SCRIPTING_WXPYTHON enabled. They should also work on GNU/Linux distributions and MacOS, even with Python3.

KiCad V6 info

Plugins for KiCad V6 will be avialible in KiCads Plugin and Content Manager as they are ported. Some of them will not be ported.

Installation

The following instructions are for KiCad 5.1.x

Windows 7/Windows 10

Install the plugins in: %APPDATA%\scripting\plugins (which most commonly translates to C:\Users\username\AppData\Roaming\kicad\scripting\plugins)

GNU/Linux

Install the plugins in: ~/.kicad/scripting/plugins or ~/.kicad_plugins

If you have no other action plugins, you can use this script:

 SPDIR=~/.kicad_plugins
 mkdir -pv `dirname ${SPDIR}` 2>/dev/null
 cd `dirname ${SPDIR}` && git clone --depth 1 [email protected]:MitjaNemec/Kicad_action_plugins.git && \
  ln -s Kicad_action_plugins `basename ${SPDIR}` && cd ${SPDIR} && echo && \
  echo "Installed action plugins:" && find . -d 1 -type d |grep -v '.git' |sed 's/^\.\// * /'

To update your action plugins from this repository in future:

 SPDIR=~/.kicad_plugins
 cd ${SPDIR} && git pull

Mac

Install the plugins in: ~/Library/Application Support/kicad/scripting/plugins or on newer versions (eg. 5.1.10) ~/Library/Preferences/kicad/scripting/plugins

If you have no other action plugins, you can use this script:

 SPDIR=~/Library/Preferences/kicad/scripting/plugins
 mkdir -pv `dirname ${SPDIR}` 2>/dev/null
 cd `dirname ${SPDIR}` && git clone --depth 1 [email protected]:MitjaNemec/Kicad_action_plugins.git && \
  ln -s Kicad_action_plugins `basename ${SPDIR}` && cd ${SPDIR} && echo && \
  echo "Installed action plugins:" && find . -d 1 -type d |grep -v '.git' |sed 's/^\.\// * /'

To update your action plugins from this repository in future:

 SPDIR=~/Library/Preferences/kicad/scripting/plugins
 cd ${SPDIR} && git pull

Plugins

Replicate layout

The purpose of this plugin is to replicate layout sections. The replication is based upon hierarchical sheets in eeschema. The basic requirement for replication is that the section to be replicated (source) is completely contained within a single hierarchical sheet, and replicated sections (destination) are just copies of the same sheet. Complex hierarchies are supported therefore replicated sheet can contain subsheets. The plugin replicates footprints, zones, tracks, text adn drawings.

After the section for replication (source section) has been laid out (footprints, tracks, text objects and zones placed) you need to:

  1. Place the anchor footprints for the destiantion sections you want to replicate. This defines the position and orientation of replicated sections. You can use [Place footprints] action plugin for this.
  2. Select the same anchor footprint within the source section.
  3. Run the plugin.
  4. Choose which hierarchical level you wish to replicate.
  5. Select which sheets you want to replicate (default is all of them)
  6. Select whether you want to replicate also tracks, zones and/or text objects.
  7. Select whether you want to replicate tracks/zones/text which intersect the pivot bounding box or just those contained within the bounding box.
  8. Select whether you want to delete already laid out tracks/zones/text (this is useful when updating an already replicated layout).
  9. Hit OK.

By default, only objects which are fully contained in the bounding box constituted by all the footprints in the section will be replicated. You can select to also replicate zones and tracks which intersect this bounding box. Additionally, tracks, text and zones which are already laid out in the replicated bounding boxes can be removed (useful when updating). Note that bounding boxes are squares aligned with the x and y axis, regardless of section orientation.

Example replication of a complex hierarchical project. Replicating inner sheet first, then outer.

Replication

Place footprints

This plugin will place footprints in:

  • in line
  • circular
  • in square matrix

The plugins for placement are selected either by consecutive reference numbers or by same ID on different hierarchical sheets.

If you want to place the footprints by consecutive reference numbers you have to

  1. select a footprint which is first in the sequence to be placed
  2. run the plugin
  3. select which place by reference number
  4. choose which footprint in the sequence you want to place
  5. select the arrangement (linear, matrix, circular)
  6. select place dimension (step in x and y axes in linear and matrix mode and angle step and radius in circular mode)
  7. run the plugin

If you want to place the footprints by same ID with

  1. select a footprint which is first in the sequence to be placed
  2. run the plugin
  3. select the hierarchical level by which the footprints will be placed (in complex hierarchies)
  4. choose from which sheets you want the footprint to place
  5. select the arrangement (linear, matrix, circular)
  6. select place dimension (step in x and y axes in linear and matrixc mode and angle step and radius in circlar mode)
  7. run the plugin

Example of place by reference number Place by reference number

Example of place by sheet ID Place by sheet ID

Delete Selected

This plugin deletes selected items. Items can be: zones and/or tracks and/or footprints. The main intention is to delete selected tracks in order to redo parts of the layout.

To run the plugin:

  1. Select items you want to delete (note that in KiCad it is different if you start your selection box from left or right)
  2. Run the plugin
  3. Select what you want to delete
  4. Hit OK

Delete selected tracks and zones

pad2pad track distance

This plugin calculates the shortest distance between two pads. Use with caution because the result is not always correct as the algorithm follows the track layout. Also, the Via distance is not accounted for. The following picture shows an example where the distance is not correct. Here, the algorithm calculates the distance from the first pad to pin #4 and then to the other pad. It does not consider the connection between the two tracks at the encircled area where they actually branch off making the measured distance longer than it actually is. Track layout which confuses the algorithm

For complex tracks (GND, Supply rails) the calculation can take quite some time.

To run the plugin:

  1. Select two pads to measure the distance between
  2. Run the plugin
  3. Select what you want to delete
  4. Hit OK

Measure pad to pad distance

net2net min distance

This plugin calculates the shortest distance between two tracks on different nets. To use, select one pad on first net and one pad on second net and run the plugin.

Archive project

This plugin archives the project thus making it portable.

The schematics archive is achieved via the project cache library. The project cache library is copied to project-archive.lib which is modified and added to the project symbol library table (if the table does not exist it is created). Also the links to the symbols within the schematics are modified so that they point to the symbols within the archive library. Afterwards, the cache library is deleted. Eeschema will recreate a correct cache library the next time the schematics are edited.

The archiving of the pcb and its footprints is already implemented within pcbnew.

The 3D models archive is placed in "shapes3D" subfolder where all 3D models are copied. Then, the links to the models within the layout (.kicad_pcb) file are modified so that they point to the archived 3D models with a path relative to the project folder.

The plugin is run from pcbnew. When the plugin is run, eeschema has to be closed. If the plugin finished successfully, it automatically closes pcbnew. This behaviour is expected and required to perform the operation.

If the project is modified later it should be archived again in order to stay portable. If a symbol of a unit has to be replaced, all units with the same symbol have to be deleted.

Swap pins

This plugin swaps two pads (in layout) and their corresponding pins (in schematics). The pins in the schematics have to be connected to a local or global label or hierarchical label either directly or through a short wire segment. The plugin also works across multi-unit parts and/or across different hierarchical levels.

Only one pin can be connected. Currently "no connection" flags are not supported. Eeschema has to be closed when the plugin is executed in pcbnew. Once the plugin is done, you should save the layout. Note that using undo will only undo the change in the layout, but not the change in the schematics. To reverse the operation, you can run the plugin again.

Example of pin swapping swapping of pins on local labels

Swap units

This plugin swaps two units (in layout) and r units (in schematics). Eeschema has to be closed when the plugin is executed in pcbnew. Unit swapping work across hierarchical pages. Note that using undo will only undo the change in the layout, but not the change in the schematics. To reverse the operation, you can run the plugin again.

Example of unit swapping

swapping units in different hierarchical pages

Length stats

This plugin displays length of all tracks on selected nets. This can be used for length matching.

Workflow:

  1. Select tracks or pads on nets you want the length displayed. You can also select a footprint(s)
  2. Run the plugin. You can remove redundant nets
  3. Lay the tracks
  4. Close the track length window

Example: length stats

Save/Restore Layout

This plugin saves the partial layout of a selected pcb (only specific hierarchical level is saved). This layout can be imported into another pcb, if it is based upon the same hierarchical subsheets. The equality is tested and checked.

Workflow:

  1. Select one footprint which is in the hierarchy that you want to save the layout for.
  2. Run the plugin and choose "Save layout"
  3. Select into which file should the layout be saved
  4. Create a new project. Copy the chosen .sch files used for hierarchy to the project folder and link it into schematics
  5. Create a new layout.
  6. Place and select the anchor footprint. This defines the position and orientation of restored layout.
  7. Run the plugin.
  8. Choose "Restore layout" 9: Select in which file is tha layout data stored
  9. Voila, observe restored layout

Example: length stats