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

Filenames from Allegro 17.2-060 not recognized as layer types #371

Open
rgetz opened this issue Jul 26, 2021 · 5 comments
Open

Filenames from Allegro 17.2-060 not recognized as layer types #371

rgetz opened this issue Jul 26, 2021 · 5 comments
Labels
whats-that-gerber Tickets for the whats-that-gerber package

Comments

@rgetz
Copy link

rgetz commented Jul 26, 2021

I have a few gerbers from Allegro, which fail to render/load.

Entire fab package:
cn0536-designsupport.zip

specific files:

  • CN0536-DesignSupport/fab/1_primary.art
  • CN0536-DesignSupport/fab/l2_gnd.art
  • CN0536-DesignSupport/fab/l3_vcc.art
  • CN0536-DesignSupport/fab/l4_secondary.art
  • CN0536-DesignSupport/fab/silk_prm.art
  • CN0536-DesignSupport/fab/silk_sec.art
  • CN0536-DesignSupport/fab/ncdrill-1-4.drl

those were able to be loaded with gerbv (except for the drill files).

Thanks

@jaseg
Copy link

jaseg commented Jun 21, 2022

@rgetz I have included your files in the gerbonara testsuite at https://gitlab.com/gerbolyze/gerbonara/-/commit/0f70b225cc394338e9c37c1b1c34c3e73609f7d6 . I hope that's ok with you, otherwise please ping me and I'll remove them.

gerbonara is a python gerber library unrelated to tracespace, but I found this issue while working on a comprehensive test suite.

@mcous
Copy link
Member

mcous commented Jun 21, 2022

@jaseg cool project! I'd give it a ⭐ but I don't have a GitLab account

@rgetz it looks like tracespace is capable of rendering this board*, but the problem is that it doesn't know how to associate these file names (e.g. 1_primary.art) with a layer type (e.g. "top copper layer"). If, after uploading to tracespace, you open the render settings and set the layer associations, it renders!

*Except for the drill file. The drill file is very poorly generated, and does not contain drill sizes anywhere other than in a non-standard format in comments. This explains why they do not render in gerbv nor in tracespace

Screen Shot 2022-06-21 at 09 54 39

Screen Shot 2022-06-21 at 09 54 45

@mcous mcous added the whats-that-gerber Tickets for the whats-that-gerber package label Jun 21, 2022
@mcous mcous changed the title fails to load gerbers from Allegro 17.2-060 (Gerber RS274X*) Filenames from Allegro 17.2-060 not recognized as layer types Jun 21, 2022
@rgetz
Copy link
Author

rgetz commented Jun 21, 2022

Thanks for feedback.

It’s totally fine to use these for any purposes - I get that Allegro isn’t exactly the most popular tool in the community - but it is the one that most semiconductor manufactures use - so many eval boards and other semiconductor reference designs are in that format.

  • Robin

@jaseg
Copy link

jaseg commented Jun 27, 2022

@mcous FWIW, I am not a fan of Allegro's gerber export style either, but it can be parsed unambiguously. The tool definition comments in the excellon file are always the same format, and the excellon file's number format can be read from either the accompanying nc_params.txt or ncdrill.log file. Here is how gerbonara parses Allegro tool definition comments and here is how gerbonara parses Allegro's ncparam.txt and ncdrill.log files (next function below).

I think the greater issue with Allegro is that it does not seem to ship with a pre-defined gerber file naming scheme, so everyone just makes up their own and automatically matching allegro gerbers to layers is mostly guesswork.

@mcous
Copy link
Member

mcous commented Jul 25, 2022

Drill file support for allegro now tracked in #392

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
whats-that-gerber Tickets for the whats-that-gerber package
Projects
None yet
Development

No branches or pull requests

3 participants