By testing a bit with a 0805 footprint and version 20091103
I got the impression, that only the suffix of the 1st number
in a pad/element is relevant and all other numbers in that pad
are treated the same.
Could you/someone verify this?
DJ Delorie wrote:
From my memory, DJ posted a message
Hm, appart from the fact, this is no good 0805-footprint, the below
--
Element(0x00 SMD 0805 smd0805 0 100 0 100 0x00)
(
# Pad[x1, y1, x2, y2, thickness, clearance, mask, name , pad number,
flags]
Pad(1000um 0um 1000um 0um 600um 1 0x0100)
Pad(3000um
On Tue, 2010-07-27 at 20:56 +0200, Armin Faltl wrote:
By testing a bit with a 0805 footprint and version 20091103
I got the impression, that only the suffix of the 1st number
in a pad/element is relevant and all other numbers in that pad
are treated the same.
Could you/someone verify this?
By testing a bit with a 0805 footprint and version 20091103
I got the impression, that only the suffix of the 1st number
in a pad/element is relevant and all other numbers in that pad
are treated the same.
That wasn't my intention. The scale from the units isn't saved
anywhere, it can't
On Tue, 2010-07-27 at 21:07 +0200, Armin Faltl wrote:
Hm, appart from the fact, this is no good 0805-footprint, the below
--
Element(0x00 SMD 0805 smd0805 0 100 0 100 0x00)
(
# Pad[x1, y1, x2, y2, thickness, clearance, mask, name , pad number,
flags]
Armin Faltl:
Hm, appart from the fact, this is no good 0805-footprint, the below
--
Element(0x00 SMD 0805 smd0805 0 100 0 100 0x00)
(
# Pad[x1, y1, x2, y2, thickness, clearance, mask, name , pad number,
flags]
Pad(1000um 0um 1000um 0um 600um 1
Stefan Salewski:
...
Please see
...
http://www.ssalewski.de/PcbFootprintRef.txt
$ grep 'or nm' www.ssalewski.de/PcbFootprintRef.txt
program may allow to specify a unit like mm, mil or nm for each coordinate
$
Maybe you meant um in the line above.
Regards,
/Karl Hammar
-
Aspö Data
On Tue, 2010-07-27 at 21:52 +0200, Karl Hammar wrote:
Stefan Salewski:
...
Please see
...
http://www.ssalewski.de/PcbFootprintRef.txt
$ grep 'or nm' www.ssalewski.de/PcbFootprintRef.txt
program may allow to specify a unit like mm, mil or nm for each coordinate
$
Maybe you meant um
Stefan:
On Sun, 2010-07-25 at 19:10 +0200, Karl Hammar wrote:
...
But my naive try did not succeed:
$ cat aa.fp
Element[ jumper_10 R? 0 0 0 0 0 100 ]
(
Pin [ 0 0 2.2mm 0.5mm 2.4mm 1.0mm 1 1 ]
Pin [ 4 0 2.2mm 0.5mm 2.4mm 1.0mm 1 2 ]
Robert Spanton:
I'm a European under the age of 40, and as such my brain works in
metric. So I'll write footprints for PCB in metric, then do the
conversion over to those weird units as a last step. So I banged the
attached script together. This replaces all instances of Nmm (e.g.
Best would be if pcb could parse these mm's on input.
It does.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
DJ:
Best would be if pcb could parse these mm's on input.
It does.
Great!!, but how?
I cannot see any reference of mm for the file format in doc/pcb.pdf
I can see that there should be some support:
$ grep FLOATINGMM src/parse_l.l
FLOATINGMM {FLOATING}[mM][mM]
{FLOATINGMM}
On Sun, 2010-07-25 at 19:10 +0200, Karl Hammar wrote:
DJ:
Best would be if pcb could parse these mm's on input.
It does.
Great!!, but how?
I cannot see any reference of mm for the file format in doc/pcb.pdf
I can see that there should be some support:
$ grep FLOATINGMM
On Sun, 2010-07-25 at 20:31 +0200, Stefan Salewski wrote:
Yes, this is how it should work, as DJ told us, in this thread again.
Works fine for 2009 PCB snapshot shipped with Gentoo-Linux. If I
remember correctly, this syntax was introduced about two years ago, so
2007 snapshot and earlier
Hi,
I'm a European under the age of 40, and as such my brain works in
metric. So I'll write footprints for PCB in metric, then do the
conversion over to those weird units as a last step. So I banged the
attached script together. This replaces all instances of Nmm (e.g.
'0.127mm') with their
On Thu, 2010-06-10 at 13:59 +0100, Robert Spanton wrote:
Hi,
I'm a European under the age of 40, and as such my brain works in
metric. So I'll write footprints for PCB in metric, then do the
conversion over to those weird units as a last step. So I banged the
attached script together.
On Thu, 2010-06-10 at 16:39 +0200, Stefan Salewski wrote:
I think recent PCB program can use mm and nm units in footprint files.
Maybe someone can confirm this?
From my memory, DJ posted a message about that file format extension
long time ago, and I think I have seen a PCB footprint file
From my memory, DJ posted a message about that file format extension
long time ago, and I think I have seen a PCB footprint file
containing nm units. But I was not able to verify this with a short
inspection of the PCB manual.
It works, for mm, um, in, and mil suffixes on any number:
On Thu, 10 Jun 2010 12:15:09 -0400, DJ Delorie wrote:
From my memory, DJ posted a message about that file format extension
long time ago, and I think I have seen a PCB footprint file containing
nm units. But I was not able to verify this with a short inspection of
the PCB manual.
It works,
Can't find anything about this in the docs.
Not surprising.
How is this supposed to be used?
Like 10mm instead of 39370
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
DJ Delorie d...@delorie.com writes:
It works, for mm, um, in, and mil suffixes on any number:
{FLOATINGMM} { return parse_number(3937.0079); }
{FLOATINGUM} { return parse_number(3.9370079); }
{FLOATINGIN} { return parse_number(10.0); }
On Thu, 2010-06-10 at 16:39 +0200, Stefan Salewski wrote:
I think recent PCB program can use mm and nm units in footprint files.
Wow! Excellent.
Do you really create the footprints files with an editor, without the
help of scripts? My sfg.rb script works fine with mm unit.
Well no, I'd
22 matches
Mail list logo
