Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert EAGLE files to XML #47

Open
electron271 opened this issue Jun 19, 2022 · 10 comments
Open

Convert EAGLE files to XML #47

electron271 opened this issue Jun 19, 2022 · 10 comments

Comments

@electron271
Copy link

I know that this won't benifit MI much, but considering that MI is shutting down (bye pichenettes, I'll really miss you, you have been an amazing figure in the Eurorack community), I think converting them to XML would make it easier for people to study the MI products (this way you can import into something like KiCAD).

@electron271
Copy link
Author

I have EAGLE free on my other computer, so I can try converting some of them myself and then open a PR

@electron271
Copy link
Author

@pichenettes, I'll install EAGLE on my computer and make a PR for this issue, I'll send the number when I start it

@electron271
Copy link
Author

#48

@electron271
Copy link
Author

Will be closed by #48

@luzpaz
Copy link
Contributor

luzpaz commented Jul 31, 2023

KiCAD files are also an option.

@nissaba
Copy link

nissaba commented Aug 9, 2024

Eagle is dead (no longer free, and only available as part of Fusion 360), the PCB files are in a binary format and it would be useful for everyone to update the PCB file to the XML format so that software like Kicad can read it.

@forestcaver
Copy link

Eagle is dead (no longer free, and only available as part of Fusion 360), the PCB files are in a binary format and it would be useful for everyone to update the PCB file to the XML format so that software like Kicad can read it.

If you do that, how do you verify the files ? You are asking pichenettes to essentially build every module with the new files to verify them which is unreasonable or to verify them in some other way (can think of some but it’s a lot of work). If you want to use kicad then why not just import the eagle files yourself or just use the files from the pull request !???

@nissaba
Copy link

nissaba commented Aug 9, 2024

Eagle is dead (no longer free, and only available as part of Fusion 360), the PCB files are in a binary format and it would be useful for everyone to update the PCB file to the XML format so that software like Kicad can read it.

If you do that, how do you verify the files ? You are asking pichenettes to essentially build every module with the new files to verify them which is unreasonable or to verify them in some other way (can think of some but it’s a lot of work). If you want to use kicad then why not just import the eagle files yourself or just use the files from the pull request !???

I’ve encountered an issue with KiCad where it refuses to accept files in binary format, as it requires them to be in XML format. I tried this myself earlier today, and unfortunately, KiCad was unable to read the files.

Given that the project has 722 forks, I was hoping that pichenettes (the original creator) had received some pull requests to address this issue.

However, after speaking with my co-worker, who is an electronics/electrical engineer, I learned that while Eagle is essentially discontinued, it is now integrated into Fusion 360 as part of a paid subscription for the full-featured version.

Interestingly, Fusion 360 for personal use does include a basic version of Eagle. To access it, you need to go to the File menu and select the new “Electronic Design” option. From there, you can import files from the PCB folder.

My hope is that we can use Fusion 360 to convert the files to a non-binary (XML) format and test whether KiCad can then accept them.

So, Eagle isn’t really dead—it has just been absorbed into Fusion 360.

@btomwhitehead
Copy link

Eagle is dead (no longer free, and only available as part of Fusion 360), the PCB files are in a binary format and it would be useful for everyone to update the PCB file to the XML format so that software like Kicad can read it.

If you do that, how do you verify the files ? You are asking pichenettes to essentially build every module with the new files to verify them which is unreasonable or to verify them in some other way (can think of some but it’s a lot of work). If you want to use kicad then why not just import the eagle files yourself or just use the files from the pull request !???

I’ve encountered an issue with KiCad where it refuses to accept files in binary format, as it requires them to be in XML format. I tried this myself earlier today, and unfortunately, KiCad was unable to read the files.

Given that the project has 722 forks, I was hoping that pichenettes (the original creator) had received some pull requests to address this issue.

However, after speaking with my co-worker, who is an electronics/electrical engineer, I learned that while Eagle is essentially discontinued, it is now integrated into Fusion 360 as part of a paid subscription for the full-featured version.

Interestingly, Fusion 360 for personal use does include a basic version of Eagle. To access it, you need to go to the File menu and select the new “Electronic Design” option. From there, you can import files from the PCB folder.

My hope is that we can use Fusion 360 to convert the files to a non-binary (XML) format and test whether KiCad can then accept them.

So, Eagle isn’t really dead—it has just been absorbed into Fusion 360.

When you open EAGLE (standalone) theres a nice big heading saying:

On June 7, 2026, EAGLE will no longer be available - click here for more information

I would recommend reading such notices.

@nissaba
Copy link

nissaba commented Aug 9, 2024

Eagle is dead (no longer free, and only available as part of Fusion 360), the PCB files are in a binary format and it would be useful for everyone to update the PCB file to the XML format so that software like Kicad can read it.

If you do that, how do you verify the files ? You are asking pichenettes to essentially build every module with the new files to verify them which is unreasonable or to verify them in some other way (can think of some but it’s a lot of work). If you want to use kicad then why not just import the eagle files yourself or just use the files from the pull request !???

I’ve encountered an issue with KiCad where it refuses to accept files in binary format, as it requires them to be in XML format. I tried this myself earlier today, and unfortunately, KiCad was unable to read the files.
Given that the project has 722 forks, I was hoping that pichenettes (the original creator) had received some pull requests to address this issue.
However, after speaking with my co-worker, who is an electronics/electrical engineer, I learned that while Eagle is essentially discontinued, it is now integrated into Fusion 360 as part of a paid subscription for the full-featured version.
Interestingly, Fusion 360 for personal use does include a basic version of Eagle. To access it, you need to go to the File menu and select the new “Electronic Design” option. From there, you can import files from the PCB folder.
My hope is that we can use Fusion 360 to convert the files to a non-binary (XML) format and test whether KiCad can then accept them.
So, Eagle isn’t really dead—it has just been absorbed into Fusion 360.

When you open EAGLE (standalone) theres a nice big heading saying:

On June 7, 2026, EAGLE will no longer be available - click here for more information

I would recommend reading such notices.

In my case Eagle is gone from the system as I had to reformat my HD (so I can not get the warning you are talking about ), afther witch I was only able to install Fusion to do some 3d modelling. I was not aware of the changes as I had not opened Eagle in the last 2 years. When I tried to get re-install Eagle back I was hitting the web page informing that is will no longuer be availeble out side of the Fisuin 360 subscription. And Since I had always used Eagle as a stand alone software it was not clear that it would be inbedded in the Fission app.

I am not using it as often as my only use case for Eagle is to get a print out of the pads on paper so I can cut out the pads with an exacto out of a transparency sheet, so I can use it as a soder paste mask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants