Tomaz Solc <[EMAIL PROTECTED]> writes:
> I can confirm that gerber files now work properly with CircuitCAM
> version 3.2 (258).
Thanks!
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> I checked in a patch for this today, which has a globl aperture list
> yet shares definitions across files. Please try it and see if
> CircuitCAM likes it.
I can confirm that gerber files now work properly with CircuitCAM
version 3.2 (258).
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
>> I'm guessing that it would be a simple change to fix aperture naming
>> in PCB - it seems that most of the other PCB software out there
>> takes care not to share names.
>
> I checked in a patch for this today, which has a globl aperture list
>
> I'm guessing that it would be a simple change to fix aperture naming
> in PCB - it seems that most of the other PCB software out there
> takes care not to share names.
I checked in a patch for this today, which has a globl aperture list
yet shares definitions across files. Please try it and se
Try this patch, which is against the latest cvs pcb. It has a global
list of apertures, but they're shared for all layers. The layers just
keep track of which ones they use. Thus, the 256 aperture limit is a
"global unique" limit.
Index: gerber.c
===
> The right way to do it is to have every file use the same D code for
> the same shape and size. That's the way it used to be.
I agree, I'll work on it.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> I'm not sure if this is really fair to call a bug in
> CircuitCAM. It's a little ambiguous as to whether
> multiple layers of the same design should have a
> common aperture definitions.
Other gerber software I tried (gerbv and GCPrevue) don't h
I'm not sure if this is really fair to call a bug in
CircuitCAM. It's a little ambiguous as to whether
multiple layers of the same design should have a
common aperture definitions.
pcb's gerber driver that I wrote (before the HID was
introduced) used a common table for all gerber files
within the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
> That's nasty, but yeah, we can work around it.
Here's a patch that adds an option that enables a workaround:
http://sourceforge.net/tracker/index.php?func=detail&aid=1634337&group_id=73743&atid=538813
Best regards
Tomaz
-BEGIN PGP SIGNATUR
> The problem we were having was caused because CircuitCAM updated D11
> aperture for the first layer from the second layer we imported. It
> looks like aperture definitions are shared between layers in this
> software.
That's nasty, but yeah, we can work around it.
I just hit this issue too with 20060822, except it is Wise Software
GerbTool Version 15.0 SR2 that is reporting the no clearances on vias
and through-holes. I am going to try another viewer, but I am currently
worried...
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone
>
> Ye
It sounds to me like PCB is outputting correct Gerber and CircuitCAM
is wrong. It may be as simple as finding a "preferences" menu in
CircuitCAM and setting it up correctly. If your CAM personnel will
let you touch the program, that is..
I'm a little confused about what you mean here:
The
> A larger issue for the PCB developers is this: If so many CAM
> programs/operators can't read our perfectly valid Gerber files, then
> should we perhaps modify our Gerber output so that it can be read by
> even the most creaky, antique CAM program, and be imported
> successfully by the most brai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stuart
> My heretical suggestion: Download GCPrevue and inspect your Gerbers
> with it. GCPrevue is a very powerful freeware [1] Windoze program for
> Gerber viewing. It has never failed me. If the polygons look bad in
> GCPrevue, the PCB has a
I haven't had experience with polygons and PCB. However, I did have a
problem once with thermals not making it to the FR-4. It turned out
that the PCB fab house needed to set a switch on their CAM software in
order to read PCB's Gerbers properly.
The issue is that PCB exports Gerbers which use
I have had a similar problem when using gerbers made with PCB with Circuit
CAM (this is the software package for LPKF mechanical etching machines). I
found the polygon support to be a little flaky, but I also did not use
polygons very much. I was only using 1 or 2 polygons per PCB and they were
16 matches
Mail list logo
