. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 Footprint Libraries Management 6 5.1 Important remark: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Footprint Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2.2 Project Specific Footprint Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 KiCad project manager or when Eeschema is started as a stand alone application. Running CvPcb from Eeschema launched from the KiCad Manager is generally better because: • Cvpcb needs the project config

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 Footprint Libraries Management 6 5.1 Important remark: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2.2 Project Specific Footprint Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KiCad project manager or when Eeschema is started as a stand alone application. Running CvPcb from Eeschema lauched from the KiCad Manager is generally better because: • Cvpcb needs the project config

KiCad project manager or when Eeschema is started as a stand alone application. Running CvPcb from Eeschema launched from the KiCad Manager is generally better because: Cvpcb needs the project config Cvpcb initializes the components footprint fields of the current schematic project. This is possible only if the project file is in the same path as the open schematic. Launching CvPcb from an Eeschema stand alone Eeschema session though, but please note that any schematic opened that does not have a project file in the same path may be missing components due to missing libraries which will not show up in

KiCad project manager or when Eeschema is started as a stand alone application. Running CvPcb from Eeschema lauched from the KiCad Manager is generally better because: Cvpcb needs the project config Cvpcb initializes the components footprint fields of the current schematic project. This is possible only if the project file is in the same path as the open schematic. Lauching CvPcb from an Eeschema stand alone Eeschema session though, but please note that any schematic opened that does not have a project file in the same path may be missing components due to missing libraries which will not show up in

Footprint Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.3.2 Project Specific Footprint Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.9.1 Modifying footprints in a PCB project . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Pcbnew iv 3 General operations 15 3.1 . . 117 12.11Footprint Libraries Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 12.123D Shapes Libraries Management . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4 General Top Toolbar 23 4.1 Sheet management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.1.2 Project Specific Symbol Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.1.7 Legacy Project Remapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Eeschema

Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.4.2 Project Specific Footprint Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 12.11Footprint Libraries Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 12.123D Shapes Libraries Management . . . . . . . . . . . . . . . . library list: You can use this to add all the libraries that contain the footprints required for your project. You should also remove unused libraries from new projects to prevent footprint name clashes. Please

. . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4 General Top Toolbar 22 4.1 Sheet management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eeschema is an integrated application where all functions of drawing, control, layout, library management and access to the PCB design software are carried out within Eeschema itself. Eeschema is intended If Eeschema is run from the project manager (KiCad), this is the available tool set: Tools to initialize a project are not available, because these tools are in the Project Manager. Eeschema 9 / 139

Eeschema is an integrated application where all functions of drawing, control, layout, library management and access to the PCB design software are carried out within Eeschema itself. Eeschema is intended Eeschema is run in standalone mode, this is the available tool set: Note that when KiCad runs in project mode, the first two icons are not available as they work with individual files. Create a new schematic (only in standalone mode). Open a schematic (only in standalone mode). Save complete schematic project. Select the sheet size and edit the title block. Open print dialog. Paste a copied/cut item or

and the project one. 2.3.1. Global Footprint Library Table The global footprint library table contains the list of libraries that are always available regardless of the currently loaded project file. The 2.3.2. Project Specific Footprint Library Table The project specific footprint library table contains the list of libraries that are available specifically for the currently loaded project file. The The project specific footprint library table can only be edited when it is loaded along with the project board file. If no project file is loaded or there is no footprint library table file in the project