thank you . works very well
1 Like
Version 2.7.0 released and is available in the plugin manager.
This will be last release supporting python 2 and kicad 5.1 (at least on windows).
New features:
- Option to highlight pin 1 only on currently chosen component row
- Reset config button in export menu
- Configurable net colors in netlist bom mode
8 Likes
Hello. Please let me know how to resolve this event.
I put a checkbox in a part with a newly set field as an extra field.
However, when I check the output html, I see that the newly set field has been created, but no data is set in it.
Please help me, I would appreciate it.
- Field in bom is called “Part number” but in field editor screenshot it’s “Model Number”. They should be the same.
- After updating the fields in eeschema did you update the pcb from schematic? You need to push that info to pcb and save it. Then use the plugin.
4 Likes
Thanks for the reply.
You are right, I did not realize that the field names were different.
I followed your instructions and re-output the file, problem solved! Thank you very much, I appreciate it.
1 Like
Version 2.8.0 is released and is available in kicad’s plugin manager.
Fixed compatibility with kicad testing build, new features:
- Improved eagle zone and variants handling
- Tented/untented vias support (kicad/eagle/generic parser)
- Collapsible top bar to save space
- Native kicad dnp field support
11 Likes
I’m not sure if this is a KiCad or Interactive Html Bom plugin issue, but seeing this on 2 machines when upgrading from 2.7.0 to 2.8.0
It seems a cosmetic error as the new version seems to be working fine after clicking OK
Application: KiCad x86_64 on x86_64
Version: 7.0.8-7.0.8~ubuntu23.04.1, release build
Libraries:
wxWidgets 3.2.2
FreeType 2.12.1
HarfBuzz 6.0.0
FontConfig 2.14.1
libcurl/7.88.1 OpenSSL/3.0.8 zlib/1.2.13 brotli/1.0.9 zstd/1.5.4 libidn2/2.3.3 libpsl/0.21.2 (+libidn2/2.3.3) libssh/0.10.4/openssl/zlib nghttp2/1.52.0 librtmp/2.3
Platform: Ubuntu 23.04, 64 bit, Little endian, wxGTK, ubuntu, x11
Build Info:
Date: Sep 30 2023 13:54:00
wxWidgets: 3.2.2 (wchar_t,wx containers) GTK+ 3.24
Boost: 1.74.0
OCC: 7.6.3
Curl: 7.88.1
ngspice: 38
Compiler: GCC 12.3.0 with C++ ABI 1017
Build settings:
KICAD_SPICE=ON
Yes, that’s safe to ignore. Looks like a minor bug in kicad’s plugin manager. Do you have any ibom customization files by chance? I.e. did you manually add any user* files in web directory of the plugin?
Thanks. No - haven’t manually added an extra files to the web directory.
Hello, how dnp is supposed to work in KiCad? I have ticked “Do not populate” attribute in eeschema and propagate changes into pcbnew. In pcbnew, I can see it is synced properly, “Do not populate” checkbox is also ticked. When I run ibom plugin with default settings, part with “Do not populate” ticked still appers in the generated bom. If I go to the ibom settings, there is “DNP field name” option set to “”. In the dropdown menu, I can select kicad field to mark components as dnp, but there is no option to use the KiCad build-in “Do not populate” attribute.
Is it possible to use kicad build-in attribute to mark components as dnp for ibom?
I guess I could workaround this by creating custom field for DNP and tell the ibom to use it. I would prefer not to that workaround, for two reasons:
- eeschema draws nice red cross to components with “Do not poulate” attribute - it is visually clear, which components are present and which are not
- I am also using KiVar plugin for assembly variant management. This plugin is designed to work with “Do not populate” attribude
Btw. it looks like ibom is correctly working with “exclude from bom” attribute, if I tick this attribute, part will not show in generated bom.
I am using KiCad 7.99.0-3657-g5cf244dd90 (Nov 20 2023) and newest Ibom plugin - commit c77c74a (Nov 11 2023)
you have to select the “field” kicad_dnp, it acts as a parser for the attribute. (source)
you may have to update the ibom tool, if the field is not there.
@Tojan thanks for reply. It works, as you described for KiCad 7.08 and iBom 2.8.0 installed via PCM. But it does not work for KiCad 7.99.0-3657-g5cf244dd90 (either iBom 2.8.0 installed via PCM, not the newest commit in master branch of iBom repository). See picture below:
Does someone have idea, what is going on? Just to try it before submitting issue …
probably something has changed in how the attribute is named/handled in 7.99 compared to 7.0.x so it stopped working. The iBom officially does not support 7.99 versions as far as I know, so something not working is to be expected. An issue maybe still a good idea to highlight required changes for KiCad 8.x, but don’t expect it to be fixed before that release.
1 Like
Agree with Tojan.
It is unrealistic to expect a plugin to support an unstable development program that may have radical changes on a daily basis.
Any issue would have to be taken up with the plugin author, not Kicad. Again, what is the point of the plugin author trying to keep up with an unstable development program that changes on a daily basis.
My stance towards supporting nightly is: as long as you make sure that issue exists in the latest commit of plugin on latest version of nightly, report any issues you run into. I may not fix it immediately but there is a good chance that I will. Kicad API is not stable in nightly but I can usually predict what changes are likely to stay unchanged until the release, in such cases it’s easier to fix them as they pop up.
Also it’s not uncommon that an issue with the plugin actually needs a change in kicad code to be fixed properly, in such cases the earlier this is reported the better are chances of fix in kicad making it into release.
For the DNP thing in particular, I just fixed it, pull latest from github.
6 Likes
understand. Thanks for promt reply and for the fix. I tried it with today build of kicad 7.99 and it is working.
Wondering if there’s a way to make the “DNP Outlined” parts use a different color? I tried finding something to edit in ibom.css but no luck. Currently it appears like the center of the part gets filled with white (leaving a grey outline). But all the other parts have grey pads too. Thought maybe the outline of DNP’s might have a different color setting somewhere (if not the outline, the center filled area. Thanks!
Short answer: no. “DNP Outlined” draws the pads of a dnp component in outline mode. It does not fill anything with any color, just instead of filled grey pads you only get grey outline of the pads. Purpose is to make it less visible, which I think is achieved.
There is no single color to draw footprint with because footprint is not one single thing.
Hi.
KiVar is really designed for KiCad v8 as it makes use of KiCad’s latest features regarding footprint fields (previously called properties) and new attributes (such as DNP) and their back-annotation from the PCB to the schematic.
This allows you to select choices for variations (KiVar’s term for variant aspects) in the PCB (because KiVar is a pcbnew plugin) and then annotate these changes back to the schematic and get the “red crosses” on the DNP parts.
For a future native assembly variant feature in KiCad, I hope that the KiCad developers get some inspiration from KiVar, especially regarding the multi-aspect concept, which makes variants much more manageable.
KiVar is now listed in the official repo of the Plugin & Content Manager. All forum readers are invited to give it a try if they require assembly variant support.