-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Issue converting EasyEDA's files using "export as Altium Designer" #115
Comments
I have this same issue. Did you ever figure out the issue |
Same here, maybe someone has a solution? |
Hmm, you could try to rename the files to .PcbDoc if you are running on a case-sensitive filesystem. If that doesn't help, can you provide me some test-files please? |
I used the online tool (and tried to rename) but same issue.
|
Ahh, those files are in the Protel ASCII format, not in the Altium Binary format. You could convert them to the binary format if you had an Altium license, and then use my converter. I had been working on improving the converter to be able to handle the ASCII format in the past, but it does not seem to work at the moment, I will look into that again. |
Ok, thanks for the reply :) |
Thank you for looking at a possible solution! This is very frustrating, I like the ease of using EasyEDA with the parts and JLCPCB integration, but I don't want my work locked to a software platform. I would rather store them as a back up in a general format so anyone can use them. Anything you can do would be a huge help! |
I get error code:
"File format not understood. Please upload ZIP files which contain .PcbDoc or .SchDoc files. "
EasyEDA -> Export as Altium -> .ZIP -> A2K
This is the file extension(s) I get from EasyEDA:
Arduino VU meter skit_2021-04-10.pcbdoc - 1254 kB
Arduino VU meter skit_2021-04-10.schdoc - 310 kB
I tried converting both PCB/SCH files together and one at a time, always inside a ZIP folder.
Does EasyEDA differ from files generated by Altium Designer? Or have I missed something in the readme?
The text was updated successfully, but these errors were encountered: