Re: gEDA-user: exporting netlist for PCAD

["Duncan Drennan" <duncan.drennan@xxxxxxxxx>]

In case anyone wants to know in the future, I got around this by
modifying the gnet-tango.scm to place the device first and the
footprint name second. This allows one to use the footprint name as
the PCAD library component name, which provides enough differentiation
to work with. Obviously any particular attribute could be placed in
the "Device" place holder which would allow for any specific library
names.

On 7/23/07, Duncan Drennan <duncan.drennan@xxxxxxxxx> wrote:
> Hi,
>
> I've been looking at the netlist formats and trying to figure out
> which one would work best for creating a netlist that can be imported
> into PCAD.
>
> PCAD allows one of three netlist formats to be imported, PCAD-ASCII
> (which is ACCEL_ASCII), Master Designer ALT, and Tango. Having a look
> through the options offered by gnetlist the immediately obvious choice
> is the tango format.
>
> The tango format for components is something like this,
>
> [
> RefDes
> Pattern (footprint)
> Device
> Value
> ]
>
> When one gets to PCAD this can present a little bit of a problem. PCAD
> takes the Device value to determine which component to use, so if
> device says RESISTOR it looks for the RESISTOR part in its library.
> One way to solve it is to change all the device values to be some sort
> of footprint reference, e.g. change RESISTOR to R0603, or CAPACITOR to
> C0805 etc.
>
> Are there any better ways of doing this, or is it just a limitation of
> working with PCAD as a layout tool?
>
> Thanks,
> Duncan
>


-- 
Engineer Simplicity, create better products - http://www.engineersimplicity.com
The Art of Engineering - http://blog.engineersimplicity.com


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user