Mail Archives: geda-user/2017/12/26/11:13:40
--Apple-Mail=_7E721CE8-D0D8-4491-A5A6-5F2B843E03BD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On Dec 26, 2017, at 8:40 AM, Nicklas Karlsson =
(nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] =
<geda-user AT delorie DOT com> wrote:
>=20
> On Tue, 26 Dec 2017 13:20:09 +0100 (CET)
> karl AT aspodata DOT se wrote:
>=20
>> Why must one have a pinnumber attribute for each pin i a sym file:
>> http://wiki.geda-project.org/geda:master_attributes_list#pinnumber
>>=20
>> Wouldn't it suffice to have pinseq and pinlabel ?
>=20
> I think pinlabel would suffice.
Except that there=E2=80=99s not, at present, a requirement that pinlabel =
attributes are unique, or even present in general. So, there would be =
large problems with existing symbol libraries.
> pinseq is needed for footprint
Only for slotted components. You may also want pinseq for SPICE =
simulation.
> and if I got it correct in cschem they use some kind of mapping =
mechanism for this so it's not part of the symbol.
>=20
>> Wouldn't it be useful to allow to have just a function (pinlabel)
>> attached to the pin without knowing which pinnumber it will end up on =
?
>=20
> Yes it would if there is a mapping mechanism.
The essential problem is that (refdes,pinnumber) is the fundamental =
identifier of connections in gnetlist/lepton-netlist. If you change =
this, you need some way to be backward compatible, or change all of the =
back ends.
We have a mapping mechanism: the slotting mechanism. You can use it for =
more than slotting, but it=E2=80=99s not so flexible that it covers all =
cases, and it uses the already overloaded pinseq attribute.
>=20
> I think I only use pinlabel fo hierachical drawings. It's hard to =
distinguish between two pins with same label and different pin numbers. =
The visible label is essentially a rather good identifier for pin since =
schematics are read by humans.
>=20
> Pinlabel as default identifier and pinnumber for the unusual case then =
there is a need to distinguish between pins with same label might be =
useful but I do not know about any case.
>=20
>> E.g. dc/dc converters with single output usually have four pins
>> +/-Vin and +/-Vout in all sorts of packages where the pinnumber (from
>> the datasheet) can be anything but 1,2,3,4, but their pin names are
>> +/-Vin/Vout. So, it would be nice if one could map sym -> fp with
>> just the "pinlabel" (gschem) -> pin "Name" (pcb). But pcb doesn't =
seem
>> to support that idea.
>=20
> Agree.
I=E2=80=99d love to be able to create generic, parameterized schematics: =
why should I need more than one Sallen-Key schematic? Why should I need =
to duplicate it four times on a page to get a bank of four using a quad =
amp?
>=20
>> Any suggestions or pointers ?
>=20
> Look at cschem or write your own mapping mechanism.
In lepton-netlist, the underlying machinery is in Scheme, and thus =
accessible to a plug-in.
>=20
>> Regards,
>> /Karl Hammar
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_7E721CE8-D0D8-4491-A5A6-5F2B843E03BD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Dec 26, 2017, at 8:40 AM, Nicklas Karlsson (<a =
href=3D"mailto:nicklas DOT karlsson17 AT gmail DOT com" =
class=3D"">nicklas DOT karlsson17 AT gmail DOT com</a>) [via <a =
href=3D"mailto:geda-user AT delorie DOT com" =
class=3D"">geda-user AT delorie DOT com</a>] <<a =
href=3D"mailto:geda-user AT delorie DOT com" =
class=3D"">geda-user AT delorie DOT com</a>> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
Tue, 26 Dec 2017 13:20:09 +0100 (CET)<br class=3D""><a =
href=3D"mailto:karl AT aspodata DOT se" class=3D"">karl AT aspodata DOT se</a> =
wrote:<br class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""> =
Why must one have a pinnumber attribute for each pin i a sym file:<br =
class=3D""><a =
href=3D"http://wiki.geda-project.org/geda:master_attributes_list#pinnumber=
" =
class=3D"">http://wiki.geda-project.org/geda:master_attributes_list#pinnum=
ber</a><br class=3D""><br class=3D"">Wouldn't it suffice to have pinseq =
and pinlabel ?<br class=3D""></blockquote><br class=3D"">I think =
pinlabel would suffice.</div></div></blockquote><div><br =
class=3D""></div>Except that there=E2=80=99s not, at present, a =
requirement that pinlabel attributes are unique, or even present in =
general. So, there would be large problems with existing symbol =
libraries.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""> pinseq is needed for =
footprint </div></div></blockquote><div><br class=3D""></div>Only for =
slotted components. You may also want pinseq for SPICE =
simulation.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">and if I got it correct in =
cschem they use some kind of mapping mechanism for this so it's not part =
of the symbol.<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Wouldn't it be useful to allow to have just a function =
(pinlabel)<br class=3D"">attached to the pin without knowing which =
pinnumber it will end up on ?<br class=3D""></blockquote><br =
class=3D"">Yes it would if there is a mapping mechanism.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>The =
essential problem is that (refdes,pinnumber) is the fundamental =
identifier of connections in gnetlist/lepton-netlist. If you change =
this, you need some way to be backward compatible, or change all of the =
back ends.</div><div><br class=3D""></div><div>We have a mapping =
mechanism: the slotting mechanism. You can use it for more than =
slotting, but it=E2=80=99s not so flexible that it covers all cases, and =
it uses the already overloaded pinseq attribute.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">I think I only use pinlabel fo hierachical =
drawings. It's hard to distinguish between two pins with same label and =
different pin numbers. The visible label is essentially a rather good =
identifier for pin since schematics are read by humans.<br class=3D""><br =
class=3D"">Pinlabel as default identifier and pinnumber for the unusual =
case then there is a need to distinguish between pins with same label =
might be useful but I do not know about any case.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""> E.g. dc/dc converters =
with single output usually have four pins<br class=3D"">+/-Vin and =
+/-Vout in all sorts of packages where the pinnumber (from<br =
class=3D"">the datasheet) can be anything but 1,2,3,4, but their pin =
names are<br class=3D"">+/-Vin/Vout. So, it would be nice if one could =
map sym -> fp with<br class=3D"">just the "pinlabel" (gschem) -> =
pin "Name" (pcb). But pcb doesn't seem<br class=3D"">to support that =
idea.<br class=3D""></blockquote><br class=3D"">Agree.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>I=E2=80=99d =
love to be able to create generic, parameterized schematics: why should =
I need more than one Sallen-Key schematic? Why should I need to =
duplicate it four times on a page to get a bank of four using a quad =
amp?</div><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Any suggestions or pointers ?<br class=3D""></blockquote><br =
class=3D"">Look at cschem or write your own mapping mechanism.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>In =
lepton-netlist, the underlying machinery is in Scheme, and thus =
accessible to a plug-in.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">Regards,<br =
class=3D"">/Karl Hammar<br class=3D""></blockquote><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><p style=3D"margin: =
0.0px 0.0px 0.0px 0.0px" class=3D""><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica" class=3D"">John Doty<span =
class=3D"Apple-converted-space"> <span =
class=3D"Apple-converted-space"> </span><span =
class=3D"Apple-converted-tab"> <span =
class=3D"Apple-converted-space"> </span></span></span>Noqsi =
Aerospace, Ltd.</font></p><p style=3D"margin: 0.0px 0.0px 0.0px 0.0px" =
class=3D""><a href=3D"http://www.noqsi.com/" =
class=3D"">http://www.noqsi.com/</a></p><p style=3D"margin: 0.0px 0.0px =
0.0px 0.0px" class=3D""><font face=3D"Helvetica" size=3D"3" style=3D"font:=
12.0px Helvetica" class=3D""><a href=3D"mailto:jpd AT noqsi DOT com" =
class=3D"">jpd AT noqsi DOT com</a></font></p><br =
class=3D"Apple-interchange-newline"></span></span>
</div>
<br class=3D""></body></html>=
--Apple-Mail=_7E721CE8-D0D8-4491-A5A6-5F2B843E03BD--
- Raw text -