|
> On Thu, Sep 12, 2024, 11:21 Robert via groups.io <birmingham_spider= > [email protected]> wrote: > > > When you generate the BOM from eeschema, the dialog box lists a number > > of BOM generator scripts.?? Did you pick one of them? None were listed. All the sub-boxes in the dialogue box were blank. I repeat: All the sub-boxes in the dialogue box were blank. I therefore had no option but to press "generate" and take what came. It is some alternative to this paucity of options that I hoped to find. > > I do have my own scripts if you are interested, but they date back to > > stone-age Kicad in that they use a tool called xsltproc.?? These days > > Kicad uses Python scripts. I have yet to upgrade from "5.0.2+dfsg1-1 release build". (2018, so pretty recent.) All I needed was for kicad to do nothing. Just dump plain text to a file, if that is not too hard for it to achieve without plugins and python. (To filter the text, I'll just use Awk.) It is the damn XML which was clogging up the works, as I had nothing to decrypt that obfuscation. > > BTW, I use a pivot table to create a grouped BOM from a simple CSV list, > > as personally I found that better than trying to do the grouping in the > > script.?? Things may have improved in kicad since I got this working, > > but what I have works, so I'm not going to fix it! If kicad would only issue a CSV - in plain text - then I could do anything and everything with that, elegantly and simply, using Awk. Many thanks for your interest, Robert. I've now installed the Linux package "xml2", which should be able to provide a CSV by means of xml2 and 2csv, but the latter borks, no manpage is provided, and the nominated doco link is a 404. So it is abandonware. But just xml2 does convert to a simpler looking list of 99% extraneous gumpf interspersed with 1% real BOM data, i.e. Part Number, Description, Package. I'm amazed that a simple shopping list is more than kicad can manage by itself? On 12.09.24 12:16, Lev wrote: > You should use the provided BOM generators, or write your own. I recommend > exporting BOM to csv, and opening it in Libreoffice. Then you can pretty > print it. That is what I have done. Kicad provided no alternative to the XML output. If it could do CSV, I would pounce on it instantly. It is the lack of BOM generator options which was the issue. That may be less of a problem once I update, but there's a lot on the plate ATM, and finishing the job with the version on hand didn't look impossible, as it didn't look completely broken - just lacking anything other than XML. If it can't be tickled into more useful output, then I've found a way to reduce the hoo-hah in XML, and a few lines of Awk can filter out 99% of the remaining obfuscation, giving Part Number, Description, Package, and even distilling Quantity of identical components, if I'm inclined. Erik |
