Hi Dan and all, On Dienstag, 30. Oktober 2007, Dan McMahill wrote: > This is a clear case of why you need the concept of a component that > provides the mapping from symbol pins to footprint pins and also from > symbol pins to netlist pins for various simulators. Its really the > same problem. There is a patch at SF that adresses this concept for spice. It adds a spice-syntax attribut to the symbols and that attribut is interpreted by the netlister. http://sourceforge.net/tracker/index.php?func=detail&aid=1758382&group_id=161080&atid=818428 > It is why I generally believe in using a script to generate heavy > symbols for each component. Me too, I'm currently playing with spice-models and template symbols. I'm just overwriting some attributes to match the current model/device. Template attached. All parameters are set by a script. The parameters are stored in an ini-style file that is easier to maintain: [Q2PA1576Q,NXP00001] symbol=pnp.sym value=Q2PA1576Q modelname=Q2PA1576Q file=2PA1576Q.prm refdes=Q? pinseq_c=1 pinseq_b=2 pinseq_e=3 pinnr_c=C pinnr_b=B pinnr_e=E footprint=none I'll write more in a few weeks, I have to play a little bit more with it. Regards Werner
Attachment:
pnp.sym
Description: application/sym-geda
_______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user