-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Parts are being incorrectly grouped #494
Comments
Hi @andreasWallner ! Before anything: If you have LCSC part numbers for all your components I suggest grouping them using it. This will solve issues like "I have 12k 1% automotive grade and 12k 1% industrial grade ..." Now: The recommended use is to separate the 1% from the 12k, you can even do it using KiBot filters. I don't consider what you describe as a bug. You say "I tried both using the default group_fields as well as manually specifying group_fields." but you don't show what you tried. If you separated the tolerance in a different field, and you only defined it for the 1% resistor, them you must disable |
Thanks, that solved my issue:
Doing that now, works as expected - not sure why I didn't think of that when I was already playing with
Sorry - didn't put it into the description, only in the linked repo.
Switching Closing this, but I'd still like to ask/understand where the original behavior that I saw comes from: Which setting/behavior causes the values |
The KiBoM idea is to merge components in the same group even when some (optional) field is filled in one of the components, but not in the others. In this way you could fill the digikey P/N of one 12k resistor and propagate it to all the others, no need to edit all of them. This is a way to see the situation, the other is your case, but in this case you can: fill the digikey P/N for one of the 12k resistors and also for the particular "12k 1%", all the other "12k" will be grouped with "12k" (assuming you group by value AND digikey P/N). Now an extra note: in the original KiBoM "12k" and "12k 1%" doesn't match their value. But for KiBot both are 12 kilo ohms resistors. If 1% is really important (and not juist garbage) you should separate it. As I said before: you can even ask KiBot to try to separate it parsing the value. In this case KiBot will understand this is the tolerance. |
Thanks! |
- Better explanation about what affects group_fields - Added warning about extra information in the value See #494
I have a resistor in my schematic that differs only in tolerance specification from some others. During generation of the BOM this resistor is grouped together with the others though.
I tried two options of specifying the tolerance, both failed (see screenshot at the end):
Value
field as12k 1%
(whereas the other resistors have aValue
of12k
)Tolerance
with a value of1%
(the other resistors don't have that field)I tried both using the default
group_fields
as well as manually specifyinggroup_fields
.To Reproduce
Issue can be reproduced by running
kitbot
(w/o parameters) on https://github.com/andreasWallner/ft232-syncfifo-pmod.Log output:
The resistor in question is R10, the BOM that is generated for me:
Expected behavior
R10 should have a separate BOM entry with part number
C269386
.Screenshots
![image](https://private-user-images.githubusercontent.com/40345/266874045-b275c016-5995-4c85-b9d0-2f60a946151c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA3MzI2NzMsIm5iZiI6MTcyMDczMjM3MywicGF0aCI6Ii80MDM0NS8yNjY4NzQwNDUtYjI3NWMwMTYtNTk5NS00Yzg1LWI5ZDAtMmY2MGE5NDYxNTFjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzExVDIxMTI1M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWIwOWI5YWVhYzFkOGY3OThlZmMzN2U3YWEwZTlhZDlhYmU3OTgxN2M5MmMzMDc4MGMyZDQ0ZWQ4YzRhNmIwZTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.87pAYvAGRAFZWmpYK9IrJodktHAeUM7N5XFa31nzOY8)
Environment (please complete the following information):
Where are you running KiBot:
I'm running KiBot on Ubuntu 22.04.2, installed via the official repo.
(interestingly I do have
kiauto
andkikit
installed via apt:The text was updated successfully, but these errors were encountered: