-
Notifications
You must be signed in to change notification settings - Fork 33
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
How do you use this with EasyEDA Gerber files #38
Comments
This is intended behavior. When gerbolyze doesn't recognize a file, it will ignore it and not copy it to the output. This is necessary since some CAD tools export formatting information for Gerber or Excellon files in separate files. If Gerbolyze would ever not recognize such an auxiliary file, and copy it while modifying the Gerber or Excellon file it is referring to, the output would be broken. My recommendation is to manually copy over these files afterwards. I might add a command line option in the future.
That is slightly surprising, as in my EasyEDA test files gerbolyze's output is larger. Would you mind sharing one of these files before and after so I can have a look? In general, the output files will not be the same, since Gerbolyze parses and re-writes every layer. Even for layers without changes this is intended behavior since this way we can make sure that the output files' file format settings are all consistent with one another. Otherwise it could happen that you get different precision or even units in gerbolyze'd and copied files. When serializing, gerbolyze applies "sane defaults" for some settings, normalizing the file format. Using the default settings, the output files should be readable to any board house. I still recommend you closely check the generated files before submitting them to production. I have made a number of boards using Gerbolyze, but there's always a chance of a terrible bug somewhere, and Gerbolyze comes without warranty. Besides your fab's online Gerber viewer, for validation I can recommend gerbv (which gerbolyze itself is tested against). As a "gold standard", you can use ucamco's reference viewer at https://gerber-viewer.ucamco.com/ .
This was a bug in the CI pipeline of resvg-wasi. Do a |
That would be helpful since presumably some layers like Gerber_TopAssemblyLayer.GTA would be helpful if you want the pcb fab to assemble your board.
Sure. Can you send me a private email as I do not want to post my boards to the world :)
Would this then create a problem with unrecognized layers like Gerber_TopAssemblyLayer.GTA
Thanks for the recommendation!
This indeed fixed it. |
Tbh, I might actually add support for assembly layers anyway, since gerbolyze's gerber library supports moving and rotating boards, too, which would require the same operation on the assembly layer.
My email is [email protected]
Probably not in this case, since that layer isn't read together with the other layers anyway. Overall easyEDA's files are well-behaved and unlikely to cause issues here, I'm much more worried about tools like Allegro or CR-9000 that can produce very peculiar output. |
I sent it you the example before/after Gerber files. Thanks |
Ok, for documentation here's my observations on the files:
In summary, you should of course check the gerbolyze'd files closely before submitting them to your fab, but as far as I can tell, gerbolyze did everything right and the differences are really just down to EasyEDA's handling of the file format. |
So, after finally getting gerbalyze template & paste to install and run in an Ubuntu Docker python3.10-pip environment (both using a full 'git' install and separately just using 'pip install'), I loaded the output files in several different Gerber viewers but the image I added in Inkscape didn't show up in the newly created Gerber file.
My steps were as follows:
gerbalyze template --bottom easyeda.zip output.svg
- No errors though a couple of warnings (see below)gerbalyze paste easyeda.zip output-image.svg easyeda-image.zip
- No errors though a couple of warnings (see below)The resulting top and bottom board views looked the same as the original -- i.e., no image added.
When I looked inside and compared the new and original zip files, I found that
Specifically, the files before looked like:
The text was updated successfully, but these errors were encountered: