Here are some quick notes that I found from looking up the gerber spec
(RS274X_revD).
-End every data block with an end-of-block character, typically '*'. (I do
not know how you would change it)
-Do not break a line within a block
from the parameter guidelines
-Parameters (things between "%") may
On Dec 2, 2007 9:08 PM, Julian <[EMAIL PROTECTED]> wrote:
> Frank,
>It looks like the RS274x manual has sloppy code in it. The G04 code
> in line 1 is supposed to end with a "*" at the end of the line to signal
> it is finished (see section on G-codes in the manual). gerbv keeps
> reading unt
> this a common (bad) convention? (DJ -- hint hint?)
No hints from me, I only produce them - I don't process them.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Frank, Julian,
Thanks for the bug report. It's interesting that sloppy code makes
gerbv choke. Moving forward I'd like gerbv to silently flag and
identify sloppy code, but keep processing. Later,
the user can request a "gerber check" window which presents him
statistics about codes and errors
Frank,
It looks like the RS274x manual has sloppy code in it. The G04 code
in line 1 is supposed to end with a "*" at the end of the line to signal
it is finished (see section on G-codes in the manual). gerbv keeps
reading until it finds a *, which made it advance past the FS statement
in the
Gerbv (including 1.0.3) seems to have difficulty reading the format string.
I've been trying to get gerbv to handle the first example Gerber code from the
file:
http://gerbv.sourceforge.net/docs/rs274xrevd_e.pdf :
*G04 EXAMPLE 1: 2 BOXES
%FSLAX23Y23*%
%MOIN*%
6 matches
Mail list logo
