KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #ai-agents #dsh-plugin #codex #developer-tools #claude-code #windows #desktop-app #typescript #rust #ai-agent #cli

eagle-to-kicad

★ 427 Open GitHub ↗

Eagle SCH/LIB to KiCad SCH/LIB ULP conversion script

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

### **Converting from Eagle to KiCad.**
*    [Quick Introduction Video (DEAD LINK, MOVING to NEW SERVER)](http://cosmosc.com/video/testtital.mp4)  
     *Recommended video player [Firefox 87.0+](https://www.mozilla.org/en-US/firefox/desktop/) with [VLC video player plugin](http://www.videolan.org/vlc/)*

* The following 5 **ulp** (eagle *user script file*) and one **ulp** include file, work together or stand alone to convert **Eagle** *sch/pcb* version 6.xx*(7.xx-8.xx maybe?)* file(s) and any version of Eagle lib(*lbr*) to **KiCad** *sch/pcb* and *lib/mod* files.

* The Programs will do
    * Eagle multi sheet schematic to KiCad multi sheets.  
	* Global and local net labels for multi sheets. *(This is a real nasty bit of hacking!)*
	* Multi part gates.  
	* Build KiCad PCB modules and sch libs from Eagle sch.  
	* Make project director to store all the converted files.  
	* And basic error checking.  
	* Eagle 6.xx(7.xx-8.xx?) PCB files can be directly import to KiCad.  
	* Eagle *LBR*s (any version of Eagle libs or size ) can be converted to KiCad lib/mod using eagle-lbr2kicad-1.0.ulp see [Eagle Lib conversion]( https://github.com/lachlanA/eagle-to-kicad-libs) for more details.  
	* Converts VIA to Pads, which helps with KiCad's flood fill, when VIAs have no connections.  
	* Documents fills over SMD pads on Eagle Layer 155,156  
	* Documents on layer's 150,152,153,154 of (Eagle) the unconnected VIAs and tracks.  
	* The **[examples](https://github.com/lachlanA/eagle-to-kicad/tree/master/examples)** directory contains a number of converted schematics/boards.

* By using the following **ulp**s  a consistent link from the schematic to PCB is maintained so forward and backward net-list annotations work under KiCad!

* **WARNINGS, AND NASTY SURPRISES, PLEASE READ!!!**
* **Only works correctly for version 4.7, or 5.1.(X?) of KiCad, it may not on other version.**
* **In KiCad Eagle PCB import of vias and tracks don't retain their NET information if they are not connected to a pad with a track, whereas they do in Eagle, (KiCad assigns a null net-name on Eagle PCB import in KiCad's Pcbnew).***  
***The result will be KiCad flood fill will not connect to them!!! There is an option to convert and document on layers 150,152,153,154 of (Eagle) the unconnected VIAs and tracks which will make finding and fixing the problem much easier.***
* ***Schematics wire's/nets can terminate in a bus or onto another wire/net/pad and not be connected in Eagle!!
Whereas in KiCad schematic wires to wires and wires to pads which terminates at the same location will be connected!!***  
* ***Eagle oval pad shapes are not supported in KiCad, you will only end up with a round pad!!***  
* ***Eagle PCB design rules are not imported by KiCads Pcbnew.***

### Installing.
* Download the zip file, and unzip using your favorite zip program to your target directory *OR* if your prefer git:

git clone https://github.com/lachlanA/eagle-to-kicad.git

* **WARNING:**  The ULPs file-name will conflict with Eagles ULPs file-names so  
  **DO NOT install them in Eagle's ULP directory**

* There are 5 **ULPs** and one **ULP** include file have been hack together.  
***run-me-first-from-eagle-sch.ulp*** .....   stage 1: Start here,  script missing number(s) to parts prefixes.  
***fix_via_hack.ulp*** ..............................   stage 2: Converts unconnected VIAs to pads.  
***eagle6xx-sch-to-kicad-sch.ulp*** ....    stage 3: Build sch and project files, etc  
***exp-lbrs.ulp*** .......................................   stage 4: Extract libs from eagle schematic/PCB  
***eagle-lbr2kicad-1.0.ulp***....................  stage 5: Converts Eagle lbr to KiCad lib/mod  
***eagle_to_kicad_include.inc*** ..........  Include file used by the other 4 ULP\s

### HOW TO RUN THE ULPs 
 
 **WARNING Always backup your Eagle sch/PCB files before running this program!**  
 
1. Start your Eagle program *(Make sure your using  version 6.xx of Eagle)*

2. Open the eagle sch/PCB  file you wish to convert. Make sure the eagle sch and PCB files are both, Correct and pass all ERC/DRC checks in Eagle.

3. Next Open the top left hand  **File menu** and select  **Run ULP**

4. A file requester window will open. Use this to find the location of the ***run-me-first-from-eagle-sch.ulp*** ULP you download from this website. We use this script to make sure all part prefixes are ending in a number  IE:   R0,  X1   etc. as KiCad will ask to renumber any prefix which does not end in a number. *(It may do this any way, but don't worry it won't change any prefixes which have already been numbered unless you tell it too!)*  Keeping prefixes consistent from schematic to PCB will allow net-list forward and back annotation to work in KiCad. Select **OK** *(this will run the script)*.  When this completes all references without a number should have a number appended to them. Note: This number will start from the largest reference number on the sch/PCB.

5. Next stage will run automatically, ***fix_via_hack.ulp*** This will check for free unconnected VIAs and convert them to pads,  this is very much a hack, as it changes the Eagle sch/PCB files.  The changed files are saved in ***targetdir/modified_eagle_files/*** There are 2 option's Document the VIAs/pads buy putting a ***>*** and net lable name on the VIA/pad on **layer 51** for Eagle, and **Dwgs.User** for KiCad. Second option is to Not to convert the VIAs to pads.  
The ulp hack adds pad's to the sch file, at **X,Y 0,0** this may conflict with any net/part at this location, so please move the sch/PCB contents so there are no parts/nets at this location before running the script.
You may getting warnings from Eagle about connecting net??? to a power plan net, just click OK, as this is normal for this script.

6. Next stage will run automatically. Set the option/location of the download ULP. And also Make sure you make/select a ***clean target directory*** where all the KiCad files will be put. Select OK, And with luck you should have sch part done. The previous ULP will link automatically to ***exp-lbrs.ulp*** for the  next step: If you have selected extract the KiCad lib's from Eagle sch/PCB *(The default).* This ULP will build Eagle lbr file, *Note: this can be a very slow process,  and will leave the Eagle PCB editor window open when complete*. Just ignore this for the moment. If this complete OK, the previous ULP will link to ***eagle-lbr2kicad-1.0.ulp*** which will convert the Eagle lbr file to a KiCad lib/mod files.  The ***eagle-lbr2kicad-1.0.ulp*** window will open with quite a few options. Just select OK for the moment.  And if *Murphy's Law is sound asleep* we should have the target directory with all the converted files, including KiCad project files. But with one exception, it will be missing KiCad PCB file.

7. For this, we need to Open KiCad's **pcbnew** program directly, at the command prompt ("c:\Program Files\KiCad\bin\pcbnew.exe"). *If you make the mistake of not opening **pcbnew** directly, and instead chose to run it from KiCad's **pcbnew**  menu. You will have no option for importing the Eagle 6 PCB file!*  In Pcbnew click on **File->Import Non-KiCad Board File...**, a window will pop-up. Select the PCB eagle file linked to the eagle sch file we used at the beginning. On the lower right side you will have a drop down menu box option, select **Eagle ver. 6.x XML PCB files (\*.b**, and press OK. After importing the Eagle PCB file, (without errors I hope). Do a **SAVE AS** to **PROJECTNAME.kicad_pcb** to the new target directory *(where you saved the output from to preceding ULP's to).* **PROJECTNAME** being the name you give to your project early on. As a helper a dummy kicad_pcb file with the correct name has been created in the target directory which you can use to do a Save-As to.

8. Next step is to check the KiCad **sch** and KiCad **PCB** are consistent for parts and nets. Start **KiCad**, and open the project in the newly created target directory. Open the sch file. And if it was converted from the single sch file, you should have the **sch** file in the display. Or multi sheet **sch** file you will have a number of small boxes spread across the page. Each one of those boxes being a converted Eagle sub-sheet. Click on the first one and check for errors. All being good, click on Generate Net-list, and click OK. It may ask to Annotate the **schematic**. If so do the Annotation step. And then come back and click on Generate net-list. And Generate it.

9. Next click on **CvPcb**, this assigns the PCB footprints with the sch parts. Most likely you will get the following warning: *Some of the assigned footprints are legacy entries (are missing lib nicknames). Would you like CvPcb to attempt to convert them to the new required FPID format? (If you answer no, then these assignments will be cleared out and you will have to re-assign these footprints yourself.)* Just click the yes button. And a window will open up listing all the parts and footprints which it has assigned. Under FILE menu click Save. And then File Close.

10. Next Clink on **PcbNew** button on the top menu, and the PCB should open up. Now click on the **NetList** and a window should open up, from there click on Read Current Net-list. All going well you should not have any extra parts added, and only a few warning's about changing net list names.  And you should be done. Please check over the converted **sch/PCB** as there are many things which can go wrong! While I have tried to catch as many conversion problem, I expect there many still waiting to be found. ***So check and triple check the results!!!***

**NOTES:**   For more info on KiCad https://www.kicad.org/display/KICAD/Installing+KiCad  
As KiCad is the process of major upgrade, and enhancement. Please be nice when asking questions of the Development team. I think you will love the new Push and shove router. This feature alone makes it worth while moving from Eagle to KiCad. I hope these ULPs make the job a lot easier.

eagle-to-kicad

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README