[sdiy] eagle.go Euro panel application (was Re: Anyone alive?)

john slee indigoid at oldcorollas.org
Sat Jul 13 07:09:46 CEST 2019

Hi Brian,

Perhaps, yes.

Perpendicular panels are indeed unsupported, and while I've considered it,
I don't intend to build any more modules that way, so I probably won't
bother. Would need a Z-offset attribute on each relevant component, and a
global attribute indicating which edge of the board the panel was to be
attached to. I don't think any other inputs would be required, unless the
component origin was inexplicably off-centre. Are you building modules in
the Doepfer style, with Cliff jacks and 16mm pots on opposing sides of the


On Sat, 13 Jul 2019 at 14:32, <rsdio at audiobanshee.com> wrote:

> The are a few User Language Programs for generating CAM outputs in Eagle,
> and if you had a ULP for Front Panel Express then you wouldn’t have to load
> another board to see the panel in FPE.
> But, hey, I never got too fancy with ULP that I recall. I’ve just found
> other people’s plugins.
> I have used the Scripting, and it’s basically the same as the commands
> that you can type inside Eagle. So, any time I find myself typing the same
> things over and over - especially selecting a whole group of nets to rip up
> or lay out - then I create a quick script to automate that and reduce
> errors.
> Anyway, if I can get the whole Go runtime installed on this laptop without
> too much headache, I’ll try your program next time I need a panel. Thanks!
> I’m already creating layers in Eagle that represent the front panel
> outlines. Since I’ve used Go before, I might even modify it to utilize my
> existing custom layers.
> By the way, some of my PCB modules mount perpendicular to the front panel,
> rather than parallel. I assume your tool doesn’t support perpendicular
> panels because that would require 3D information, or at least center
> offsets for each part as well as a way to specify where you want to align
> the PCB with the panel.
> Brian
> On Jul 12, 2019, at 8:18 PM, john slee <indigoid at oldcorollas.org> wrote:
> > No, I didn't. I've been using Eagle for some years now but have never
> delved into its scripting language. Conversely I'm quite comfortable
> writing things in Go.
> >
> > In hindsight I'm glad I went this way. One rather irritating limitation
> of Eagle is not being able to open more than one board file concurrently.
> Today I figured out command-line CAM job invocation, so now I can generate
> both the panel board file and its corresponding zipped Gerbers in one very
> fast operation. This means I can keep working on my board in Eagle and
> preview [with a gerber viewer] the front panel on another screen, without
> no more workflow interruption than hitting Save.
> >
> > I've a few more features in the pipeline. TBA!
> >
> > John
> >
> > On Sat, 13 Jul 2019 at 12:09, <rsdio at audiobanshee.com> wrote:
> >> Hi John,
> >>
> >> That sounds very interesting. Thanks for sharing the GitHub link.
> >>
> >> Did you try writing any of these features as an EAGLE Script or User
> Language Program that would run inside Eagle? I’ve dabbled in those
> options, and they can be very handy.
> >>
> >> Brian
> >>
> >>
> >> On Jul 10, 2019, at 6:08 AM, john slee <indigoid at oldcorollas.org>
> wrote:
> >> > I am also still here. I was working on a PCB layout recently and
> finally got sufficiently frustrated at the effort involved in making a
> corresponding front panel that I decided to do something about it. I wrote
> a little command-line application that:
> >> >
> >> > 1. reads your Autodesk Eagle XML board files (only XML, not the older
> file format)
> >> > 2. finds the board outline and determines what width Eurorack panel
> you need
> >> > 3. looks for components with PANEL_DRILL_MM attributes and saves
> their names/locations/sizes
> >> > 4. creates a new Eagle board file of appropriate Eurorack dimensions,
> with system holes, based on Dieter Doepfer's specs
> >> > 5. adds holes and legend text to the generated board file
> >> >
> >> > From this point you can load the generated (front panel) board file
> into Eagle and use it to emit Gerbers.
> >> >
> >> > It was surprisingly easy to do! My real goal here was to have panel
> file generation be a step that can be quickly run again and again while
> working on a project — to eliminate the kinds of errors (eg. moving a pot
> slightly but forgetting to make a corresponding panel adjustment) I'd made
> previously when generating panel files manually with QCAD or Front Panel
> Designer. I think it worked out well. I ordered some boards from Seeed and
> when they arrived the only problems I found were where I had specified the
> wrong hole size!
> >> >
> >> > https://github.com/jsleeio/go-eagle
> >> >
> >> > Hopefully this is useful for other folks also.
> >> >
> >> > John
> >> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20190713/b1ef6844/attachment.htm>

More information about the Synth-diy mailing list