Hi Steve and all,
So if I understand this correctly, you are asking for someone to write
an exporter for pcb which outputs a file with XY-values of pads(pins)
with an ID-reference to be able to check for copper conductivity etc.
and maybe even frequency related impedance/capacitance (nelma ?).
Some of the elements in my generated (by gsch2pcb) board.pcb have parse
errors. (for a new project, but it already has many elements)
After Element(blah) (body) there's stray text:
ERROR parsing file 'board.pcb'
line:1058
description: 'parse error'
Element(0x00203 0 3 100
Hi Ben,
On Sat, 2 Jun 2007 04:14:46 -0700
Ben Jackson [EMAIL PROTECTED] wrote:
Some of the elements in my generated (by gsch2pcb) board.pcb have parse
errors. (for a new project, but it already has many elements)
After Element(blah) (body) there's stray text:
ERROR parsing file
I created this for LT1764A and friends, it's a DD5. This is exactly
their recommended footprint, plus an outline I made up. It's very
tight to the part, more so than some I looked at on professionally
made boards using the same package.
It's twice as far from the part as outlines I use,
I didn't need to place anything on a sub-mil location, so I didn't
use that. Is there another advantage?
Metric parts need the extra resolution, else the pins bounce back and
forth due to the 0.025mm grid.
___
geda-user mailing list
I tend to make my centers be the center of what ver is the first
pad.
I try to make the snap-to points on the pads line up with the grid, so
I don't end up with snap points 0.1 mil away from grid points.
___
geda-user mailing list
Bert,
A high end (Diamond Quality) fab and assembly shop uses the ascii file
to program their flying probe tester. There is an existing standard
which I have an example off at the office which is based upon the pads
file format. If you are interested I can probably get you an example
early next
I've used this part and several others in the same package. My $.02
worth...
- I would also recommend using the .01 mil resolution co-ordinate syntax.
- My experience is that most shops like the part co-ordinate origin to be
the centroid, not on pin 1. I've also had problems setting the mark
Hi Steve,
Please do post to my private e-mail as to save bandwith on the list.
TIA, and kind regards,
Bert Timmerman.
On Sat, 2007-06-02 at 06:14 -0700, Steve Meier wrote:
Bert,
A high end (Diamond Quality) fab and assembly shop uses the ascii file
to program their flying probe tester.
I am trying to build the CVS geda/gaf module. The autogen.sh scripts
test for required version of autotools etc but they actually require
even newer versions to successfully build.
Since I just upgraded to the latest in an effort to build, I can't tell
you what the requirements actually are, but
Friends -
On Sat, Jun 02, 2007 at 09:08:22AM +0200, L.J.H. Timmerman wrote:
Or does a defacto standard format already exist ?
Together with a netlist of connecting traces this would give enough
information for testing conductity in an automated fashion.
Does IPC 356 do what you want? A shop
On Sat, Jun 02, 2007 at 04:14:46AM -0700, Ben Jackson wrote:
After Element(blah) (body) there's stray text:
Element(0x00203 0 3 100 0x00)
(
...
).fp(SOT89.fp,U301,unknown)
Well, I upgraded a million prereqs and build geda/gaf from source.
The only change is now the same command also
Ok, gnetlist is writing an intermediate m4 file like this:
PKG_QFP208_28.fp(`QFP208_28.fp',`U402',`unknown')
The first part PKG_QFP208_28 becomes a m4 call to the function with no
arguments. It also does this with my package:
PKG_DD5.fp(`DD5.fp',`U501',`3.3V/3A')
however mine
13 matches
Mail list logo
