kicad-developers team mailing list archive

[jp charras <jp.charras@xxxxxxxxxx>]

Le 03/06/2018 à 22:52, Jeff Young a écrit :
> 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>

>From the point of view of a BOM, "<datasheet>http://www.r-type.org/pdfs/ecc83.pdf</datasheet>" is
the only one description info.

The string fields stored in libpart section are the default values, not the actual values (that can
be edited by the designer inside the schematic).

> 
>   ...
>   
>   <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.
> 
> 



-- 
Jean-Pierre CHARRAS