Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

How do generic components now work? #174

Closed
JustEnoughDucks opened this issue Jan 18, 2018 · 7 comments
Closed

How do generic components now work? #174

JustEnoughDucks opened this issue Jan 18, 2018 · 7 comments

Comments

@JustEnoughDucks
Copy link

I have been using kicad-symbols as my library now in addition to kicad-library.

It seems the generics are either not put in yet or using a different convention. I am trying to understand it.

Currently, the generics of inductors, resistors, caps, etc... are all under the pspice library (only non-CamelCase library) and the diode and capacitor at least are unusably large. Is it against the convention to put all passive components around the size of the resistor so common components like capacitors are actually usable with most IC schematic components?

Pictured is the difference.
component_size

@jkriege2
Copy link
Collaborator

The lib has been transfered sometime before christmas, so it should be there, if you update:
https://github.com/KiCad/kicad-symbols/blob/master/Device.lib

@poeschlr
Copy link
Collaborator

If you update the lib files, you still need to add them to kicad. For kicad version 4 you need to do this for every project via eeschema->preferences->component libs.
For kicad nightly (after sym-lib-table addition) you can add the libs to your global sym-lib-table.

@JustEnoughDucks
Copy link
Author

JustEnoughDucks commented Jan 18, 2018

I have already added them to kiCAD. You are correct. It wasn't showing up in the filter as none of them have descriptions anymore.

If I specifically search for C_small though I can find it. I would recommend the addition of descriptions to generic parts.

@poeschlr
Copy link
Collaborator

This happens if the lib is saved with a recent nightly build. It changes the library version information. This results in older kicad versions not seeing the dcm file content.

@JustEnoughDucks
Copy link
Author

JustEnoughDucks commented Jan 18, 2018

So this will be fixed at the next update? If so, then there is no issue here.

@poeschlr
Copy link
Collaborator

I created a pull request to fix this particular problem. #175

@poeschlr
Copy link
Collaborator

We will create a separate branch for kicad 4 compatibility. See discussion in #191. Commit e60f1f1 should be save to use until then.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants