Hm… I don’t know how this works under the hood really.
When I try any of the other options in that dialog there is no extra .xml file created.
CadStar, OrCAD… the files for those are .frp and .net respectively.
Only for the PADS I get the .xml and depending on the command line setting a file without or with .pads extension.
I’m using a nightly version of KiCAD though, dunno if this is different for the normal v4 versions?
Question, do you select a different folder in that destination dialog than the project folder?
I don’t change anything in there, just hit [Save] actually…
The .pads file then is {project-name}.pads and located in the project folder, right next to {project-name}.pro, {project-name}.sch and {project-name}.kicad_pcb
The way the custom exports works is that KiCad always generates an XML corresponding to the net list. That XML file is then processed by xsltproc, which takes as input the XML file and transform it according to the XSL file, hence the name “XSLT processor”.
The XML file is not the intended final output, it is the “intermediate file” mentioned in the docs.
Assuming that xsltproc ran correctly, then there should be a file somewhere on your PC with the name specified by “%O.pads” or whatever. Depending on your OS and settings the file might be easy or hard to find.
Personally I check this sort of thing by running from the command line, to ensure I know where everything is and see all the output. xsltproc is great for programmers but a very unfriendly tool to inflict on regular users, but there you are.
XSLT (Extensible Stylesheet Language Transformations) is a language for transforming XML documents into other XML documents
I had the same issue. From what I can tell it looks like KiCAD was producing the PADS netlist but it was a file with no extension with the same name as every other file in my project root directory so I just couldn’t find it.
The script I wrote works pretty good for me. I can’t upload the .exe as it’s too big. But if you install python you can run the attached script. It makes a nicer formatted netlist anyways. You do have to manually input footprint names though.
it’s a development version… you can get it here (at least for windows):
But it’s not supposed to be used for production, as there can be stability issues (or better there are) and bugs. It’s the newest stuff that the devs want to be tested by a wider audience essentially. So don’t use it for anything, unless you know what you’re doing.
Joan, thank you for the feedback, If I got this right then:
** After I create the design in version 4.0.4
** I will archive the project ,
** Install nightly version on a old computer to make sure i don’t corrupt the production version
** open the archived project with the nightly version
** Then hopefully i can create the PADS file
Sounds about right, but I don’t get why you can’t go hunting for that file on your system?
As has been mentioned, that xsltprog program is being called and does what it’s being told.
Should be no difference between the latest stable and the latest (buggy) nightly there, really.
That code currently is not changing afai-aware.
You might do this all for nothing…
Which OS you’re on?
Windows?
What is the xsltprog command line in the PADS export dialog?
Still this?
Where is your KiCAD installed?
Where is your project located?
What happens if you change the command line to this?
xsltproc -o “C:\Users\{YOUR USER NAME HERE}\AppData\Roaming\kicad\test.pads” “C:\Program Files\KiCad\bin\scripting\plugins\netlist_form_pads-pcb.xsl” “%I”
Do you get a test.pads file in C:\Users\{YOUR USER NAME HERE}\AppData\Roaming\kicad?
If so, you got some kind of access problem with the location the xsltproc.exe wants to write to.
I for example can’t just use “C:\test.pads” - if there is an error message, it’s not long enough visible for me to check it. The file is not being created in that location.
If I instead use “E:\test.pads” it works… that’s why all my data is on E:, an extra partition.
Next thing I would like to know if your FileExplorer - if you’re under Windows - does hide extensions for known file types?
Maybe it even hides files without extension, thinking they could be system files?
When you update Windows PATH environment variable, be sure to set the system version, not the user version.
I’m still not able to run it from the netlist dialog in EESchema. Similar to the other users on this thread, it creates the .xml file, but no other output files. I was able to run it from the command line by replacing %O with the desired output filename and %I with the input file name, which is the .xml file.
Thanks Der.ule, xlstproc is there. I guess it’s not in my path. I can run the script from command line from the Kicad directory.
However, I still can’t get it to work from the netlist dialog, even when I specify input and output files instead of %I and %O. I just get the .xml file, no .asc file.