I try to generate gerber for a board, and everything went ok until excellon
file for drill and holes. Viewmate show excellon layer about 10-20 times
bigger than any other layer (in gerber format), and with many phantom
drills. I have tryed the http://www.gerber-viewer.com/ with the same
results.
Only "gerbv" show the real size of excellon file.
It is a problem of Eagle output, or a viewmate problem?
eSilviu schrieb:
I try to generate gerber for a board, and everything went ok until excellon
file for drill and holes. Viewmate show excellon layer about 10-20 times
bigger than any other layer (in gerber format), and with many phantom
drills. I have tryed the http://www.gerber-viewer.com/ with the same
results.
Only "gerbv" show the real size of excellon file.
It is a problem of Eagle output, or a viewmate problem?
It's most probably a problem of viewmate. All those gerber viewers need
to "guess" the exact number format (number of digits, number of
decimals) and the unit (inch/mm) of the drill data. A wrong guess
results in a badly scaled display.
Normally, you can select those parameters when loading the drill file,
eventually you can also change them later to correct the view.
Besides that, I have heard of some more problems with viewmate. I am
using GCprevue which works pretty well (and guesses correctly most of
the time 
).
Tilmann
"Tilmann Reh" <usenet2007nospam@autometer.de> wrote in message
news:i2mc49$fgp$1@cheetah.cadsoft.de...
eSilviu schrieb:
>
>> I try to generate gerber for a board, and everything went ok until
>> excellon
>> file for drill and holes. Viewmate show excellon layer about 10-20 times
>> bigger than any other layer (in gerber format), and with many phantom
>> drills. I have tryed the http://www.gerber-viewer.com/ with the same
>> results.
>> Only "gerbv" show the real size of excellon file.
>> It is a problem of Eagle output, or a viewmate problem?
>
It's most probably a problem of viewmate. All those gerber viewers need
to "guess" the exact number format (number of digits, number of
decimals) and the unit (inch/mm) of the drill data. A wrong guess
results in a badly scaled display.
>
Normally, you can select those parameters when loading the drill file,
eventually you can also change them later to correct the view.
>
Besides that, I have heard of some more problems with viewmate. I am
using GCprevue which works pretty well (and guesses correctly most of
the time
).
>
Tilmann
>
In my case GCprevue show the same wrong result.
eSilviu schrieb:
>> Besides that, I have heard of some more problems with viewmate. I am
>> using GCprevue which works pretty well (and guesses correctly most of
>> the time 
).
In my case GCprevue show the same wrong result.
That's why I wrote "most of the time".
However, with GCprevue you get a file format selection window after you
selected the files for import, and before they are actually loaded.
There, you can see the format guesses and also adjust the parameters
according to the format you generated. I always use SM1000 format for
drill files, with "2.4" decimal notation, metric. If the format
selection window shows anything different, I fix it there - and then the
display is correct right from the start.
Tilmann
I used File/Import/Guess to import the *.drd file.
The defaults seemed to work:
Decimal Placement 1.4
English Data Units
Omit leading zeros
Absolute Position Coordinates
cheers,
Mike
On 7/27/2010 4:40 AM, Tilmann Reh wrote:
eSilviu schrieb:
>>> Besides that, I have heard of some more problems with viewmate. I am
>>> using GCprevue which works pretty well (and guesses correctly most of
>>> the time 
).
>>
>> In my case GCprevue show the same wrong result.
That's why I wrote "most of the time".
However, with GCprevue you get a file format selection window after you
selected the files for import, and before they are actually loaded.
There, you can see the format guesses and also adjust the parameters
according to the format you generated. I always use SM1000 format for
drill files, with "2.4" decimal notation, metric. If the format
selection window shows anything different, I fix it there - and then the
display is correct right from the start.
Tilmann
