KiCad does not track wich library components are imported from

[Stefan Olsson]

Dear sir or Madame

If i create a capacitor with the same Value in several libraries kicad always select the same capacitor regardless of choice

Platform: windows 7, build 7601, 64 bit
Kicad: kicad-product-r6055.fa29c62-x86_64.exe
Release build wxWidget version 3.0.2
Boost version 1.57.0

I have the libraries
capacitor_ceramic_16V_1608.lib
capacitor_ceramic_50V_1608.lib
capacitor_ceramic_100V_1608.lib
capacitor_ceramic_200V_2012.lib

and create a capacitor in each of them with the Value "1nF" (and the two visibly extra fields "voltage" and "package")
each 1nF extra field ("voltage" and "package") differes depedning on which library they are created in.

When I in the schematic editor press "Place component" and write 1nF I can see the 1nF capacitor in each of the libraries.
However, regardless of which 1nF capacitor I choose, kicad will always choose the capacitor from the same library
(in my case the 16V_1608.lib)

I can detect this by the voltage and package (in my specific case) kicad is always choosing "1nF,16V,1608" even if I choose
"1nF,200V,2012"

PS
I have attached the project , try to add "1nF with 200V and formfactor 2012 to the line.sch, it wont work for me
DS

Regards
/Stefan

[Stefan Olsson (stefan-olsson)]

I have also tested with version kicad-product-r6161.6b3ff2d-x86_64.exe and the behaviour is the same

[Wayne Stambaugh (stambaughw)]

On 9/7/2015 10:40 AM, Stefan Olsson wrote:
> I have also tested with version kicad-product-r6161.6b3ff2d-x86_64.exe and the behaviour is the same
>
This is a known issue with the current schematic editor design which has
been addressed many times before. See:

https://answers.launchpad.net/kicad/+question/187619

[Stefan Olsson (stefan-olsson)]

> This is a known issue with the current schematic editor design which has
> been addressed many times before. See:

Which indicates it is a fairly large issue

>>https://answers.launchpad.net/kicad/+question/187619
>There are plans to fix this problem once the new schematic file and library formats are implemented.

(This answear was 2012)

I could create uniquie names like 1uF_100V_2012_5% or wait with the bond between schematic and footprint til after the design is complete (which kinda spoil the idea of the field option for the components such as footprint)

or perhaps start to engage myself in the development of kicad for real ^^

/Stefan

[Wayne Stambaugh (stambaughw)]

On 9/8/2015 1:05 AM, Stefan Olsson wrote:
>> This is a known issue with the current schematic editor design which has
>> been addressed many times before. See:
>
> Which indicates it is a fairly large issue

Which is resolved by two fairly simple solutions, unique component names
or proper library ordering. This is why there has been no push to fix
it. It is annoying but not catastrophic.

>
>
>>> https://answers.launchpad.net/kicad/+question/187619
>> There are plans to fix this problem once the new schematic file and library formats are implemented.
>
> (This answear was 2012)

There have been much more important issues to resolve. Manpower is
limited so we tend to fix things that require coding. Things that can
be resolved by user configuration tend to get pushed back.

>
> I could create uniquie names like 1uF_100V_2012_5% or wait with the bond
> between schematic and footprint til after the design is complete (which
> kinda spoil the idea of the field option for the components such as
> footprint)
>
> or perhaps start to engage myself in the development of kicad for real
> ^^
>
>
> /Stefan
>

[Stefan Olsson (stefan-olsson)]

I checked the source code and it is failry simple to fix
(SCH_BASE_FRAME::SelectComponentFromLibrary return LIB_ALIAS* instead of wxString)

I am setting up my ubuntu machine to create a patch to fix the history stuff as well
(the test was done on a microsoft windows machine)

I hope i will be back in the next days or so with the patch

/Stefan

[Stefan (stol)]

Hi

The fix have been pushed to
bzr push lp:~stol/kicad/selectcomp1493071
Using default stacking branch /+branch-id/324654 at chroot-73847440:///~stol/kicad/
Created new stacked branch referring to /+branch-id/324654.

[Novak Tamas (novak-7)]

Stefan , I think that better practice is having a single "C" and a "Cpol" in device.lib, where Value is simply "C".
When you place the component, you may edit its properties with "E" key.
Set Value from "C" to "1nF", set Footprint by "Assign footprint", and "Add field" only if needed (e.g. "Voltage"= "50V").
Or simply set Value to all important things like "1n/50V/X7R/SMD1206".

No reason to make separate components for each capacitors (e.g. 1uF_100V_2012_5%).

[Stefan Olsson (stefan-olsson)]

Hi

Well, I want to "get ride off" the following things with this patch
1. The necessary to edit components when adding them
 which will for sure introduce errors in larger construction when you forget to edit the component correctly
2. Get a very easy process to generate BOM's with as little "hands on" as possibly.
3. Don’t have to redo 1 and 2 for each new construction

Note:
The idea of this patch is to have the possibility to have the same id in several libraries,
The process described below is just one way of utilize the possibility to have the same id in different libraries
the patch is not "locked" to this described process.
This patch is backward compatible, you can still have only one "capacitor" and edit the values each time you add the capacitor to a scheme.

-- The below described process is just an example that is impossible today but will work with patch --

The point with have several different libraries, such as
Capacitor_ceramic_100V_2012_5%
Capacitor_ceramic_100V_2012_10%
Capacitor_ceramic_50V_2012_20%

Is that you create these libraries one time, with all needed information in them, such as
right footprint, voltage demand, tolerances and even perhaps the manufacture and the supplier with right component number etc.
Already when you choose the capacitor you can, as in my example, all needed information is there.

It even get better when you generate a BOM, you get all the right information automatically.

Stefan Olsson
<email address hidden>
Mobile [phone]

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Novak Tamas
Sent: den 14 september 2015 00:23
To: Stefan Olsson
Subject: [Bug 1493071] Re: KiCad does not track wich library components are imported from

Stefan , I think that better practice is having a single "C" and a "Cpol" in device.lib, where Value is simply "C".
When you place the component, you may edit its properties with "E" key.
Set Value from "C" to "1nF", set Footprint by "Assign footprint", and "Add field" only if needed (e.g. "Voltage"= "50V").
Or simply set Value to all important things like "1n/50V/X7R/SMD1206".

No reason to make separate components for each capacitors (e.g.
1uF_100V_2012_5%).

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1493071

Title:
  KiCad does not track wich library components are imported from

Status in KiCad:
  New

Bug description:
  Dear sir or Madame

  If i create a capacitor with the same Value in several libraries kicad always select the same capacitor regardless of choice

  Platform: windows 7, build 7601, 64 bit
  Kicad: kicad-product-r6055.fa29c62-x86_64.exe
  Release build wxWidget version 3.0.2
  Boost version 1.57.0

  I have the libraries
  capacitor_ceramic_16V_1608.lib
  capacitor_ceramic_50V_1608.lib
  capacitor_ceramic_100V_1608.lib
  capacitor_ceramic_200V_2012.lib

  and create a capacitor in each of them with the Value "1nF" (and the two visibly extra fields "voltage" and "package")
  each 1nF extra field ("voltage" and "package") differes...

[Seth Hillbrand (sethh)]

Fixed in Wayne's symbol table work