kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

Hi JP,

What are you considering the “description” in that?

Here’s what I’m seeing (interesting bits highlighted in red):

  <comp ref="U1">
    <value>ECC83</value>
    <footprint>Valves:VALVE-NOVAL_</footprint>
    <datasheet>http://www.r-type.org/pdfs/ecc83.pdf</datasheet>
    <libsource lib="analog_devices" part="ECC83"/>
    <sheetpath names="/" tstamps="/"/>
    <tstamp>5B141B34</tstamp>
  </comp>

  ...
  
  <libpart lib="analog_devices" part="ECC81">
    <aliases>
      <alias>ECC83</alias>
    </aliases>
    <description>double triode ECC81 (root part)</description>
    <docs>http://www.r-type.org/pdfs/ecc81.pdf</docs>
    <footprints>
      <fp>VALVE*NOVAL*P*</fp>
    </footprints>
    <fields>
      <field name="Reference">U</field>
      <field name="Value">ECC81</field>
      <field name="Footprint">Valves:VALVE-NOVAL_</field>
    </fields>
    <pins>
      <pin num="1" name="A" type="output"/>
      <pin num="2" name="G" type="input"/>
      <pin num="3" name="K" type="BiDi"/>
      <pin num="4" name="F1" type="power_in"/>
      <pin num="5" name="F1" type="power_in"/>
      <pin num="6" name="A" type="output"/>
      <pin num="7" name="G" type="input"/>
      <pin num="8" name="K" type="BiDi"/>
      <pin num="9" name="F2" type="power_in"/>
    </pins>
  </libpart>

The Python code does a lookup of libparts & aliases to make a connection and then reads the (single) description.


> On 3 Jun 2018, at 19:12, jp charras <jp.charras@xxxxxxxxxx> wrote:
> 
> Le 03/06/2018 à 19:08, Jeff Young a écrit :
>> That when folks produce a BOM including descriptions all aliased parts have the wrong descriptions.
> 
> Are you sure? Have you tested it?
> 
> I just tested a alias in  a netlist:
> Here is the description in  (components ... ) section:
> 
>    (comp (ref JP101)
>      (value ALIAS_OF_JUMPER)
>      (datasheet "doc of alias_of_jumper")
>      (libsource (lib pic_programmer_schlib) (part ALIAS_OF_JUMPER))
>      (sheetpath (names /) (tstamps /))
>      (tstamp 5B14DAFF))
> 
> the description looks good to me and is the description of the alias I entered in library.
> 
>> 
>> (I don’t know if anyone has produced 3rd-party tools to do footprint selection, but the footprint filters would also be wrong if they did.)
> 
> Aliases share the footprint filters.
> 
>> 
>>> On 3 Jun 2018, at 17:46, jp charras <jp.charras@xxxxxxxxxx> wrote:
>>> 
>>> Le 03/06/2018 à 18:10, Jeff Young a écrit :
>>>> We currently export library components the same way we store them (ie: just the root, with a list of aliases).
>>>> 
>>>> We do not output the alias descriptions, documentation links or footprint filters.  The missing documentation links are OK since these are copied to the datasheet fields of the individual components; the missing descriptions and footprint filters are a problem for BOM generators.
>>>> 
>>>> Since aliases are mainly a way to ease authoring, I propose that we write out a flattened version of the library components — that is we write out a component for each alias.  (We can still list the aliases in the root component for 3rd-party readers that are looking for it.)
>>>> 
>>>> Thoughts?
>>> 
>>> What is the *actual* problem to solve?
>>> 
>>> -- 
>>> Jean-Pierre CHARRAS
> 
> -- 
> Jean-Pierre CHARRAS
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>