Confusion about running KiBOM in eeschema [SOLVED]

[KarlZeilhofer]

Hi,

until v5.1.2 I used to have a list of script commands configured in the BOM dialog:

But as you can see, the Generate button is inactive, and I have no idea why (‘kicad-join-bom2-parts’ is a program in my system path). I even changed from a linux AppImage (V5.1.4) to the currently released PPA version V5.1.5, without any changes.

Now I found out, I could do the same thing I’ve been doing in the BOM dialog now in the Netlist dialog:

I’m I missing here something essential, or are the dialog names just messed up and confusing?

I’d like to stick with the old KiBOM, as our process works with this very well, even though there are many new scripts, that come with a current default KiCad installation.

Thanks in advance for your help.
Greets, Karl

[KarlZeilhofer]

I found the solution:

The file format of ~/.config/kicad/eeschema seems to be changed.

Until 5.1.2 (or maybe only 5.0.x ???) a BOM Plugin was stored like this (my custom script):

bom_plugins=
(plugins  
  (plugin bom1_single 
    (cmd "python \\"/home/karl/Team14/sf/kicad/tools/KiBoM/KiBOM_CLI.py\\" -s \\";\\" --cfg \\"%P/bom1.ini\\" \\"%I\\" \\"%P/bom1-single.csv\\"")  
    (opts nickname=bom1_single)
  )
)

At least since V5.1.4 it is now (preinstalled example script):

bom_plugins=
(plugins  
  (plugin /usr/share/kicad/plugins/bom_csv_grouped_by_value_with_fp.py 
    (cmd "python \\"/usr/share/kicad/plugins/bom_csv_grouped_by_value_with_fp.py\\" \\"%I\\" \\"%O\\"")  
    (opts nickname=bom_csv_grouped_by_value_with_fp))  
  )
)

So the main difference is the value for plugin, which seems, that it has to be an executable file path.
If one wants to keep the old custom configured scripts, some minor migration work is necessary in that config file for eeschema.

Greets, Karl