-
Notifications
You must be signed in to change notification settings - Fork 3
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
pea export mostly fails with Eagle 7.5.0 #5
Comments
Greetings! I am using 7.3 here on some files that passed through 7.5 and I can report the same issues (I tested the exports, the only one working is png). |
Hi, I'm sorry I took some time off and did not attend the issue. I still have not upgraded to 7.5, so I'll first try to replicate the issue with 7.4.0 before upgrading |
Hey there! No worries, I think we can only thank you for the tool and the time you invest in it! (and happy new year btw) |
Just another note, what I find curious on the BoM export is that if I run the ULP code you generated inside Eagle it works (I grabbed the temp file that you are creating and copied it somewhere else). If the code is executed via |
sadly, I currently am without a proper eagle installation, and without the context in which I was able to work on the project, so it's a bit hard for me to replicate your issue. Though, I'm pretty positive that the exports and the diff are working for me, I've been using them a lot on my last electronics project. Issue ②About the BOM exports, I have to look again at the code, as I have been experimenting on the possibility to handle an alternative database outside of eagle, but I never really finished the implementation — and lacks proper documentation. So that issue might better be setup as an independent issue, and that explains the Issue ①About the export to pdf issue, there's a problem with the exceptions I'm using which leads to you not understanding what went wrong:
which originally is a Issue ③For your third issue, I'd need eagle source files that are similar to the project you're working on, as well as the |
Closing as I split this issue into new ones. |
Thank you for taking the time, good idea to split them up into individual issues - don't you want to add your explanations (issue 1-3) directly to them as well? And no worries for the delay! |
yup, good idea. Though for most of it I'll need to get a working eagle on that old computer, which I have no need of, besides eagle-automation. Also, if you could post a project similar (in terms of how you do things in eagle) to the one you're having issues with (for #9), that'd be great. |
no its me who is late - I was on holidays, sry. Concerning the project, I posted directly in #9. |
Hi!
Looking for automation tools for Eagle I stumbled upon this great package. Unfortunately I struggled upon quite a few problems with the
pea export
function. Being not fluent in Python I will write them down here, hoping to at least somehow contribute.Using the fairly new Eagle 7.5.0 I assume that most errors might be caused by changes in Eagle itself and these scripts not being adapted yet. Note that I use the current version of
pea
build from source.Schematic -> PNG
Works great!
Schematic -> PDF
I wonder if this is even possible but since the PNG export worked like a charm I suppose that I shouldn't get the following error:
Schematic -> Bill of Material
Trying to export the BOM of a schematic I get first prompted with the following error message in Eagle, clicking on ok the ok then leads to the exception as noted further down:
Layout -> PDF/PNG
When trying to export any layout to a pdf or png file Eagle prompts with two popups indicating a problem, whereby the second popup changes depending on which layer is selected:
![screen shot 2015-12-20 at 12 16 11](https://cloud.githubusercontent.com/assets/3830671/11917757/796b5b26-a715-11e5-8ffa-91dfc39ca0fa.png)
![screen shot 2015-12-20 at 12 16 27](https://cloud.githubusercontent.com/assets/3830671/11917758/7bbe90be-a715-11e5-9dcf-7dafd2733946.png)
Still an empty file is generated containing a timestamp and the file name.
It is worth noticing that while the png file is generated relative to path the command is launched, the pdf is always generated in the same folder as the layout:
leads to the file
folder/layout.pdf
, whileleads to the file
layout.png
.Layout -> Gerber
Nothing happens...
The text was updated successfully, but these errors were encountered: