14.3. XSLT approach

    The document that describes XSL Transformations (XSLT) is available here:

    http://www.w3.org/TR/xslt

    The pads-pcb format is comprised of two sections.

    • The footprint list.
    • The Nets list: grouping pads references by nets.

    Immediately below is a style-sheet which converts the Intermediate Netlist file to a pads-pcb netlist format:

    And here is the pads-pcb output file after running xsltproc:

    2. *PART*
    3. P1 unknown
    4. U2 unknown
    5. U1 unknown
    6. C1 unknown
    7. R1 unknown
    8. *NET*
    9. *SIGNAL* GND
    10. U1.7
    11. C1.2
    12. U2.7
    13. P1.4
    14. *SIGNAL* VCC
    15. R1.1
    16. U1.14
    17. U2.4
    18. U2.1
    19. U2.14
    20. P1.1
    21. *SIGNAL* N-4
    22. U1.2
    23. U2.3
    24. *SIGNAL* /SIG_OUT
    25. P1.2
    26. U2.5
    27. U2.2
    28. *SIGNAL* /CLOCK_IN
    29. R1.2
    30. C1.1
    31. U1.1
    32. P1.3
    34. *END*

    The command line to make this conversion is:

    The Cadstar format is comprised of two sections.

    • The footprint list.
    • The Nets list: grouping pads references by nets.

    Here is the style-sheet file to make this specific conversion:

    1. <?xml version="1.0" encoding="ISO-8859-1"?>
    2. <!--XSL style sheet to Eeschema Generic Netlist Format to CADSTAR netlist format
    3.     Copyright (C) 2010, Jean-Pierre Charras.
    4.     Copyright (C) 2010, SoftPLC Corporation.
    5.     GPL v2.
    7. <!DOCTYPE xsl:stylesheet [
    8.   <!ENTITY nl  "&#xd;&#xa;"> <!--new line CR, LF -->
    9. ]>
    11. <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    12. <xsl:output method="text" omit-xml-declaration="yes" indent="no"/>
    14. <!-- Netlist header -->
    15. <xsl:template match="/export">
    16.     <xsl:text>.HEA&nl;</xsl:text>
    17.     <xsl:apply-templates select="design/date"/>  <!-- Generate line .TIM <time> -->
    18.     <xsl:apply-templates select="design/tool"/>  <!-- Generate line .APP <eeschema version> -->
    19.     <xsl:apply-templates select="components/comp"/>  <!-- Generate list of components -->
    20.     <xsl:text>&nl;&nl;</xsl:text>
    21.     <xsl:apply-templates select="nets/net"/>          <!-- Generate list of nets and connections -->
    22.     <xsl:text>&nl;.END&nl;</xsl:text>
    23. </xsl:template>
    25.  <!-- Generate line .TIM 20/08/2010 10:45:33 -->
    26. <xsl:template match="tool">
    27.     <xsl:text>.APP "</xsl:text>
    28.     <xsl:apply-templates/>
    29.     <xsl:text>"&nl;</xsl:text>
    30. </xsl:template>
    32.  <!-- Generate line .APP "eeschema (2010-08-17 BZR 2450)-unstable" -->
    33. <xsl:template match="date">
    34.     <xsl:text>.TIM </xsl:text>
    35.     <xsl:apply-templates/>
    36.     <xsl:text>&nl;</xsl:text>
    37. </xsl:template>
    39. <!-- for each component -->
    40. <xsl:template match="comp">
    41.     <xsl:text>.ADD_COM </xsl:text>
    42.     <xsl:value-of select="@ref"/>
    43.     <xsl:text> </xsl:text>
    44.     <xsl:choose>
    45.         <xsl:when test = "value != '' ">
    46.             <xsl:text>"</xsl:text> <xsl:apply-templates select="value"/> <xsl:text>"</xsl:text>
    47.         </xsl:when>
    48.         <xsl:otherwise>
    49.             <xsl:text>""</xsl:text>
    50.         </xsl:otherwise>
    51.     </xsl:choose>
    52.     <xsl:text>&nl;</xsl:text>
    53. </xsl:template>
    55. <!-- for each net -->
    56. <xsl:template match="net">
    57.     <!-- nets are output only if there is more than one pin in net -->
    58.     <xsl:if test="count(node)>1">
    59.     <xsl:variable name="netname">
    60.         <xsl:text>"</xsl:text>
    61.         <xsl:choose>
    62.             <xsl:when test = "@name != '' ">
    63.                 <xsl:value-of select="@name"/>
    64.             </xsl:when>
    65.             <xsl:otherwise>
    66.                 <xsl:text>N-</xsl:text>
    67.                 <xsl:value-of select="@code"/>
    68.         </xsl:otherwise>
    69.         </xsl:choose>
    70.         <xsl:text>"&nl;</xsl:text>
    71.         </xsl:variable>
    72.         <xsl:apply-templates select="node" mode="first"/>
    73.         <xsl:value-of select="$netname"/>
    74.         <xsl:apply-templates select="node" mode="others"/>
    75.     </xsl:if>
    76. </xsl:template>
    77. <!-- for each node -->
    78. <xsl:template match="node" mode="first">
    79.     <xsl:if test="position()=1">
    80.        <xsl:text>.ADD_TER </xsl:text>
    81.     <xsl:value-of select="@ref"/>
    82.     <xsl:text>.</xsl:text>
    84.     <xsl:text> </xsl:text>
    85.     </xsl:if>
    86. </xsl:template>
    88. <xsl:template match="node" mode="others">
    89.     <xsl:choose>
    90.         <xsl:when test='position()=1'>
    91.         </xsl:when>
    92.         <xsl:when test='position()=2'>
    93.            <xsl:text>.TER     </xsl:text>
    94.         </xsl:when>
    95.         <xsl:otherwise>
    96.            <xsl:text>         </xsl:text>
    97.         </xsl:otherwise>
    98.     </xsl:choose>
    99.     <xsl:if test="position()>1">
    100.         <xsl:value-of select="@ref"/>
    101.         <xsl:text>.</xsl:text>
    102.         <xsl:value-of select="@pin"/>
    103.         <xsl:text>&nl;</xsl:text>
    104.     </xsl:if>
    105. </xsl:template>
    107. </xsl:stylesheet>

    Here is the Cadstar output file.

    This format has only one section which is the footprint list. Each footprint includes its list of pads with reference to a net.

    Here is the style-sheet for this specific conversion:

    1. <?xml version="1.0" encoding="ISO-8859-1"?>
    2. <!--XSL style sheet to Eeschema Generic Netlist Format to CADSTAR netlist format
    3.     Copyright (C) 2010, SoftPLC Corporation.
    4.     GPL v2.
    6.     How to use:
    7.         https://lists.launchpad.net/kicad-developers/msg05157.html
    8. -->
    10. <!DOCTYPE xsl:stylesheet [
    11.   <!ENTITY nl  "&#xd;&#xa;"> <!--new line CR, LF -->
    12. ]>
    14. <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    15. <xsl:output method="text" omit-xml-declaration="yes" indent="no"/>
    17. <!--
    18.     Netlist header
    19.     Creates the entire netlist
    20.     (can be seen as equivalent to main function in C
    21. -->
    22. <xsl:template match="/export">
    23.     <xsl:text>( { Eeschema Netlist Version 1.1  </xsl:text>
    24.     <!-- Generate line .TIM <time> -->
    25. <xsl:apply-templates select="design/date"/>
    26. <!-- Generate line eeschema version ... -->
    27. <xsl:apply-templates select="design/tool"/>
    28. <xsl:text>}&nl;</xsl:text>
    30. <!-- Generate the list of components -->
    31. <xsl:apply-templates select="components/comp"/>  <!-- Generate list of components -->
    33. <!-- end of file -->
    34. <xsl:text>)&nl;*&nl;</xsl:text>
    35. </xsl:template>
    37. <!--
    38.     Generate id in header like "eeschema (2010-08-17 BZR 2450)-unstable"
    39. -->
    40. <xsl:template match="tool">
    41.     <xsl:apply-templates/>
    42. </xsl:template>
    44. <!--
    45.     Generate date in header like "20/08/2010 10:45:33"
    46. -->
    47. <xsl:template match="date">
    48.     <xsl:apply-templates/>
    49.     <xsl:text>&nl;</xsl:text>
    50. </xsl:template>
    52. <!--
    53.     This template read each component
    54.     (path = /export/components/comp)
    55.     creates lines:
    56.      ( 3EBF7DBD $noname U1 74LS125
    57.       ... pin list ...
    58.       )
    59.     and calls "create_pin_list" template to build the pin list
    60. -->
    61. <xsl:template match="comp">
    62.     <xsl:text> ( </xsl:text>
    63.     <xsl:choose>
    64.         <xsl:when test = "tstamp != '' ">
    65.             <xsl:apply-templates select="tstamp"/>
    66.         </xsl:when>
    67.         <xsl:otherwise>
    68.             <xsl:text>00000000</xsl:text>
    69.         </xsl:otherwise>
    70.     </xsl:choose>
    71.     <xsl:text> </xsl:text>
    72.     <xsl:choose>
    73.         <xsl:when test = "footprint != '' ">
    74.             <xsl:apply-templates select="footprint"/>
    75.         </xsl:when>
    76.         <xsl:otherwise>
    77.             <xsl:text>$noname</xsl:text>
    78.         </xsl:otherwise>
    79.     </xsl:choose>
    80.     <xsl:text> </xsl:text>
    81.     <xsl:value-of select="@ref"/>
    82.     <xsl:text> </xsl:text>
    83.     <xsl:choose>
    84.         <xsl:when test = "value != '' ">
    85.             <xsl:apply-templates select="value"/>
    86.         </xsl:when>
    87.         <xsl:otherwise>
    88.             <xsl:text>"~"</xsl:text>
    89.         </xsl:otherwise>
    90.     </xsl:choose>
    91.     <xsl:text>&nl;</xsl:text>
    92.     <xsl:call-template name="Search_pin_list" >
    93.         <xsl:with-param name="cmp_ref" select="@ref"/>
    94.     </xsl:call-template>
    95.     <xsl:text> )&nl;</xsl:text>
    96. </xsl:template>
    98. <!--
    99.     This template search for a given lib component description in list
    100.     lib component descriptions are in /export/libparts,
    101.     and each description start at ./libpart
    102.     We search here for the list of pins of the given component
    103.     This template has 2 parameters:
    104.         "cmplib_id" (reference in libparts)
    105.         "cmp_ref"   (schematic reference of the given component)
    106. -->
    107. <xsl:template name="Search_pin_list" >
    108.     <xsl:param name="cmplib_id" select="0" />
    109.     <xsl:param name="cmp_ref" select="0" />
    110.         <xsl:for-each select="/export/libparts/libpart">
    111.             <xsl:if test = "@part = $cmplib_id ">
    112.                 <xsl:apply-templates name="build_pin_list" select="pins/pin">
    113.                     <xsl:with-param name="cmp_ref" select="$cmp_ref"/>
    114.                 </xsl:apply-templates>
    115.             </xsl:if>
    116.         </xsl:for-each>
    117. </xsl:template>
    120. <!--
    121.     This template writes the pin list of a component
    122.     from the pin list of the library description
    123.     The pin list from library description is something like
    124.           <pins>
    125.             <pin num="1" type="passive"/>
    126.             <pin num="2" type="passive"/>
    127.           </pins>
    128.     Output pin list is ( <pin num> <net name> )
    129.     something like
    130.             ( 1 VCC )
    131.             ( 2 GND )
    132. -->
    133. <xsl:template name="build_pin_list" match="pin">
    134.     <xsl:param name="cmp_ref" select="0" />
    136.     <!-- write pin numner and separator -->
    137.     <xsl:text>  ( </xsl:text>
    138.     <xsl:value-of select="@num"/>
    139.     <xsl:text> </xsl:text>
    141.     <!-- search net name in nets section and write it: -->
    142.     <xsl:variable name="pinNum" select="@num" />
    143.     <xsl:for-each select="/export/nets/net">
    144.         <!-- net name is output only if there is more than one pin in net
    145.              else use "?" as net name, so count items in this net
    146.         -->
    147.         <xsl:variable name="pinCnt" select="count(node)" />
    148.         <xsl:apply-templates name="Search_pin_netname" select="node">
    149.             <xsl:with-param name="cmp_ref" select="$cmp_ref"/>
    150.             <xsl:with-param name="pin_cnt_in_net" select="$pinCnt"/>
    151.             <xsl:with-param name="pin_num"> <xsl:value-of select="$pinNum"/>
    152.             </xsl:with-param>
    153.         </xsl:apply-templates>
    154.     </xsl:for-each>
    156.     <!-- close line -->
    157.     <xsl:text> )&nl;</xsl:text>
    158. </xsl:template>
    160. <!--
    161.     This template writes the pin netname of a given pin of a given component
    162.     from the nets list
    163.     The nets list description is something like
    164.       <nets>
    165.         <net code="1" name="GND">
    166.           <node ref="J1" pin="20"/>
    167.               <node ref="C2" pin="2"/>
    168.         </net>
    169.         <net code="2" name="">
    170.           <node ref="U2" pin="11"/>
    171.         </net>
    172.     </nets>
    173.     This template has 2 parameters:
    174.         "cmp_ref"   (schematic reference of the given component)
    175.         "pin_num"   (pin number)
    176. -->
    178. <xsl:template name="Search_pin_netname" match="node">
    179.     <xsl:param name="cmp_ref" select="0" />
    180.     <xsl:param name="pin_num" select="0" />
    181.     <xsl:param name="pin_cnt_in_net" select="0" />
    183.     <xsl:if test = "@ref = $cmp_ref ">
    184.         <xsl:if test = "@pin = $pin_num">
    185.         <!-- net name is output only if there is more than one pin in net
    186.              else use "?" as net name
    187.         -->
    188.             <xsl:if test = "$pin_cnt_in_net>1">
    189.                 <xsl:choose>
    190.                     <!-- if a net has a name, use it,
    191.                         else build a name from its net code
    192.                     -->
    193.                     <xsl:when test = "../@name != '' ">
    194.                         <xsl:value-of select="../@name"/>
    195.                     </xsl:when>
    196.                     <xsl:otherwise>
    197.                         <xsl:text>$N-0</xsl:text><xsl:value-of select="../@code"/>
    198.                     </xsl:otherwise>
    199.                 </xsl:choose>
    200.             </xsl:if>
    201.             <xsl:if test = "$pin_cnt_in_net &lt;2">
    202.                 <xsl:text>?</xsl:text>
    203.             </xsl:if>
    204.         </xsl:if>
    205.     </xsl:if>
    207. </xsl:template>

    Here is the OrcadPCB2 output file.

    One can add a new netlist plug-in user interface tab by clicking on the Add Plugin button.

    Here is what the configuration data for the PadsPcb tab looks like:

    eeschema_plugin_padspcb_png

    The Eeschema plug-in configuration dialog requires the following information:

    • The title: for instance, the name of the netlist format.
    • The command line to launch the converter.

    Once you click on the netlist button the following will happen:

    1. Eeschema creates an intermediate netlist file *.xml, for instance test.xml.
    2. Eeschema runs the plug-in by reading test.xml and creates test.net.

    Assuming we are using the program xsltproc.exe to apply the sheet style to the intermediate file, xsltproc.exe is executed with the following command:

    xsltproc.exe -o <output filename> < style-sheet filename> <input XML file to convert>

    In KiCad under Windows the command line is the following:

    f:/kicad/bin/xsltproc.exe -o “%O” f:/kicad/bin/plugins/netlist_form_pads-pcb.xsl “%I”

    Under Linux the command becomes as follows:

    xsltproc -o “%O” /usr/local/kicad/bin/plugins/netlist_form_pads-pcb.xsl “%I”

    The command line format accepts parameters for filenames:

    The supported formatting parameters are.

    • %B ⇒ base filename and path of selected output file, minus path and extension.
    • %I ⇒ complete filename and path of the temporary input file (the intermediate net file).

    %I will be replaced by the actual intermediate file name

    %O will be replaced by the actual output file name.

    The command line format for xsltproc is the following:

    <path of xsltproc> xsltproc <xsltproc parameters>

    under Windows:

    f:/kicad/bin/xsltproc.exe -o “%O” f:/kicad/bin/plugins/netlist_form_pads-pcb.xsl “%I”

    under Linux:

    xsltproc -o “%O” /usr/local/kicad/bin/plugins/netlist_form_pads-pcb.xsl “%I”

    The above examples assume xsltproc is installed on your PC under Windows and all files located in kicad/bin.

    Because the intermediate netlist file contains all information about used components, a BOM can be extracted from it. Here is the plug-in setup window (on Linux) to create a customized Bill Of Materials (BOM) file:

    The path to the style sheet bom2csv.xsl is system dependent. The currently best XSLT style-sheet for BOM generation at this time is called bom2csv.xsl. You are free to modify it according to your needs, and if you develop something generally useful, ask that it become part of the KiCad project.