If you want to use xsltproc, please refer “Installing an XSLT processor”. There is a nice Web page for this(written in Japanese), but I excluded that because I am new here and can include only two URLs.
I noticed the same issue. It is caused by spaces in the output file (path)name.
xsltproc is not able to handle this. I didn’t try yet but probably saxonHE9-5 is a good solution. Another option is to change the “%O.csv” parameter to fixed file in a path without spaces and then copy this manually.
For me this error occured when there were non ASCII characters (like é, á) in the folder name of the project. Other parts of KiCad worked fine with this name, only the BOM generation not. Changing the folder name solved this issue for me.
Yes it is on x64 PCs and 686 PCs. It looks like the OP was using a 32 bit build on a 64 bit Windows as the install was in
“C:\Program Files (x86)\KiCad”, which introduces a second space and brackets.
The actual project directory should be under C:\Users\Yourname…
Several programs don’t like nonascii(7bit) characters in the Username
The actual project name should also stick to ascii(7bit)
Hi, I have same issue with you.
After i try clear space character in file name & file path, the issue was still there.
So, I met some issue similar with argument before. One of them is file parth too long. So I tried to move project to shorter folder path.
It is success now.
One thing is not professional is output of plugin is file name without sub-fix, as expecting .csv, I need to change extension file name from binary type to .csv to onpen in Excel.
The problem is on the output path, so to fix this error just use this next command and it will work fine, after that you can just convert file, importing data from CSV to a XLSX file if you want: