Homebrew PCBs

So it was time finally to teach Eagle to export the images I want. It turned
out there is no need. Someone else had already perceived my wants, and wrote
just what I was going to write, but better. :) I also learned a few related
things along the way. (Trace outlines for milling, for one. I'll mention
these again at the end.)

cam2images.ulp exports images of sets of layers defined in CAM jobs. The
trick now is to set up a CAM job that defines the views you want. Read the
docs if you don't already know how. (I recall now why I never read them; the
docs are simply AWFUL!) Here's a short summary:

** Click the "CAM processor" icon on the toolbar to open the CAM editor.
** Add a job section for each set of layers you want to image.
** Select the layers you want printed.
** Name the output file ".XXXXX" to write to file
"<yourboardname>.XXXXX.YYY". Without the quotes, of course, and note the
leading '.'. Substitute a meaningful string instead of XXXXX (".TOP" or
".cmp", for example, for top copper). YYY will be replaced with the
appropriate extension for the image file type you'll select later.

The ULP ignores the other job information. Which is nice, because it limits
what you need to learn about. Alas, it also doesn't honor the "mirror"
option, which makes sense since you likewise can't tell Eagle to mirror the
image.

Save the CAM file. Run cam2image.ulp. Select the CAM job you created. Set
the image options. You'll likely want a different resolution than the
default 75 dpi. Click OK.

I changed the default options in the ULP to select monochrome, PNG, and 600
dpi. You might want to do the same, since the idea is to automate your
preferences.

=============

Along the way, I also "discovered" these things about Eagle:

outlines.ulp creates a millable outline of your copper on a new layer.
Search help for "outlines data" for more info.

ULP operates on the board or schematic by returning a string back to Eagle,
which it tries to run as a script. It seems simple enough once someone
points it out to you, but easy to miss in the docs, if it's in there at all.

There seems to be no easy way to delete items in ULP or scripts, which might
be just as well. There's a lot of potential for harm there. OTOH, it seems
not unreasonable to create some objects and then delete them afterward to
clean up.

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=7565135735&rd=1&sspagename=STRK%3AMEWN%3AIT&rd=1

  Have a board off here now, will post a pic or two when it gets here.  
Gets 29 of my smaller 2.6" square boards for $90, -$6 from Paypal 
coupon.  Still only one board, and a bit more than CustomPCB, but with 
mask etc.  But lower initial cost than their full panel order, and not a 
bad deal for prototyping even at the 155 sq inch special, and the Ebay 
one is 200" sq.  Should do ok for starting up on these, looking through 
the feedback for other people selling after ordering from them, their 
boards look pretty good.  Tighter specs than CustomPCB too, don't need 
it much on this board but SMT ones may work out better here..  Will only 
get 12 of my next 4" sq larger version, but that's still not too 
terrible on a price/board basis   CustomPCB 10 panels works out a bit 
better, I think even after adding the mask.

  Might even decide to run off a batch of my motor controller here, 
it'll get 16 of the 3"x4".  If so, I'll put up the extra here at cost, 
after a little testing.  Should do 5 or 6 axes after a little more 
tweaking, 3 full drivers up to 5 phase bipolar or unipolar motors, and 
2-3 that will just be 4 bottom FETs for 5 or 6 wire unipolars, for 
rotary or other additional use.  I have another board or two to finish 
first, but they should only take a week, then the motor controller only 
needs a few minor mods for the other axes before it's ready to make.

Later,
Alan

Mike Young wrote:

>So it was time finally to teach Eagle to export the images I want. It turned
>out there is no need. Someone else had already perceived my wants, and wrote
>just what I was going to write, but better. :)
>
  That's quite often the case, sometimes it's nice to use the popular 
choice!  :)


>
>cam2images.ulp exports images of sets of layers defined in CAM jobs. The
>trick now is to set up a CAM job that defines the views you want. Read the
>docs if you don't already know how. (I recall now why I never read them; the
>docs are simply AWFUL!) Here's a short summary:
>  
>
  Yep they are better now but still fairly lame, fortunately Google is 
your friend.  Someone else has done almost everything, and even been 
kind enough to put it on the net too.  Ends up working out rather well too.

Alan