KiCad es una herramienta software open-source para la creación de diagramas electrónicos y diseño de placas de circuito impreso. Bajo su singular fachada, KiCad incorpora un elegante conjunto con las siguientes herramientas software:

3 utility tools are also included:

Estas herramientas están generalmente se ejecuta desde el director del proyecto, pero pueden ser también funcionan como herramientas independientes.

KiCad no presenta limitación alguna en cuanto al tamaño de la placa y puede gestionar hasta 32 capas de cobre, 14 capas técnicas y 4 capas auxiliares.

KiCad can create all the files necessary for building printed circuit boards, including:

Al ser de código abierto (licencia GPL), KiCad representa la herramienta ideal para proyectos orientados a la creación de equipos electrónicos con estilo open-source.

KiCad is available for Linux, Windows and Apple macOS.

KiCad crea y utiliza archivos (y directorios) con las siguientes extensiones de archivos específicas para la edición de esquemas y placas.

Fichero del Gestor del proyecto:

Archivos del Editor de Esquemas

Ficheros y directorios del Editor de placas:

Ficheros comunes

Ficheros especiales

Otros ficheros

Son generados por KiCad para fabricación o documentación.

Hardware accelerated renderer in Pcbnew and Gerbview requires video card with support of OpenGL v2.1 or higher.

The default configuration file named kicad.pro is supplied in kicad/template. It serves as a template for any new project and is used to set the list of library files loaded by Eeschema. A few other parameters for Pcbnew (default text size, default line thickness, etc.) are also stored here.

Another default configuration file named fp-lib-table may exist. It will be used only once to create a footprint library list; otherwise the list will be created from scratch.

The default kicad.pro file can be freely modified, if desired.

Verifique que tiene acceso de escritura a kicad/template/kicad.pro

Run KiCad and load kicad.pro project.

Run Eeschema via KiCad manager. Modify and update the Eeschema configuration, to set the list of libraries you want to use each time you create new projects.

Run Pcbnew via KiCad manager. Modify and update the Pcbnew configuration, especially the footprint library list. Pcbnew will create or update a library list file called footprint library table. There are 2 library list files (named fp-lib-table): The first (located in the user home directory) is global for all projects and the second (located in the project directory) is optional and specific to the project.

In KiCad, one can define paths using an environment variable. A few environment variables are internally defined by KiCad, and can be used to define paths for libraries, 3D shapes, etc.

This is useful when absolute paths are not known or are subject to change (e.g. when you transfer a project to a different computer), and also when one base path is shared by many similar items. Consider the following which may be installed in varying locations:

For instance, the path to the connect.pretty footprint library, when using the KISYSMOD environment variable, would be defined as ${KISYSMOD}/connect.pretty

This option allows you to define a path using an environment variable, and add your own environment variables to define personal paths, if needed.

KiCad environment variables:

Note also the environment variable KIPRJMOD is always internally defined by KiCad, and is the current project absolute path.

For instance, ${KIPRJMOD}/connect.pretty is always the connect.pretty folder (the pretty footprint library) found inside the current project folder.

If you modify the configuration of paths, please quit and restart KiCad to avoid any issues in path handling.

You may define your favorite text editor and PDF viewer. These settings are used whenever you want to open a text or PDF file.

These settings are accessible from the Preference menu:

In order to manage a KiCad project consisting of schematic files, printed circuit board files, supplementary libraries, manufacturing files for photo-tracing, drilling and automatic component placement files, it is recommended to create a project as follows:

KiCad creates a file with a .pro extension that maintains a number of parameters for project management (such as the list of libraries used in the schematic). Default names of both main schematic file and printed circuit board file are derived from the name of the project. Thus, if a project called example.pro was created in a directory called example, the default files will be created:

KiCad is able to import files created using other software packages. Currently only Eagle 6.x or newer (XML format) is supported.

To import a foreign project, you need to select either a schematic or a board file in the import file browser dialog. Imported schematic and board files should have the same base file name (e.g. project.sch and project.brd). Once the requested files are selected, you will be asked to select a directory to store the imported files, which are going to be saved as a KiCad project.

La ventana principal KiCad se compone de una vista tipo árbol del proyecto, un panel que contiene botones que sirven para ejecutar las distintas herramientas del software, y una ventana de mensaje. El menú y la barra de herramientas se pueden utilizar para crear, leer y guardar archivos de proyecto.

KiCad allows you to run all standalone software tools that come with it.

El panel de herramientas esta compuesto por 8 botones que corresponden a los siguientes comandos (de 1 a 8, de izquierda a derecha)

Double-clicking on the schematic file runs the schematic editor, in this case opening the file pic_programmer.sch.

Double-clicking on the board file runs the layout editor, in this case opening the file pic_programmer.kicad_pcb.

Haciendo clic derecho sobre cualquiera de los archivos en el árbol del proyecto le permite ver las acciones genéricas de manipulación del archivo.

KiCad top toolbar allows for some basic file operations:

The File → New Project → New Project from Template menu will open the Project Template Selector dialog:

A single click on a template’s icon will display the template information, and a further click on the OK button creates the new project. The template files will be copied to the new project location and renamed to reflect the new project’s name.

Después de seleccionar una plantilla:

KiCad looks for template files in the following paths:

The template name is the directory name where the template files are stored. The metadata directory is a subdirectory named meta containing files describing the template.

All files and directories in a template are copied to the new project path when a project is created using a template, except meta.

When a new project is created from a template, all files and directories starting with the template name will be renamed with the new project file name, excluding the file extension.

The metadata consists of one required file, and may contain optional files. All files must be created by the user using a text editor or previous KiCad project files, and placed into the required directory structure.

Here is an example showing project files for raspberrypi-gpio template:

And the metadata files:

Eeschema v5 will automatically create a global symbol table when first started. You will be given a chance to skip this and create your own global symbol table by hand. You only need to do this if don’t use KiCad symbol libraries at all. Otherwise it is easier to modify the automatically generated global symbol table.

Automatic remapping of symbols will be executed whenever a schematic is opened that has not been remapped. There are a few steps you should take ahead of time in order for the remapping to be the most effective.

When remapping symbols, KiCad proceeds in the following order to assign the library to a symbol:

Symbol names may not contain <SPACE>, ':', '/'.

Library nicknames may not contain <SPACE>, ':'.

Existing symbol names with these characters must be renamed by manually editing the relevant schematic and library files.

If you track the footprint library repository, changes made to the default global footprint library table are not tracked by KiCad. You will have to manually keep the global footprint library table up to date.