kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #09114
Re: Library woes (was Symbol library for FTDI chips)
On Sat, 10 Nov 2012, Alex G. wrote:
On 11/10/2012 10:40 AM, Simon Turner wrote:
The problem is made worse by the fact that when you edit a footprint or
symbol in the schematic of pcb it can revert back later so it is very
frustrating.
That is because any edits are saved in the project's cache, not in the
"system" libraries.
If you look at the TO-220 footprint it is number 231 rather
than 123. I'd be happy to submit corrections, tell me how to.
http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/view/head:/HOW_TO_CONTRIBUTE.txt
has some information.
A branch on launchpad (like I did), or a [PATCH] to the mailing list.
For the TO-220 footprint specifically, I strongly suggest you try
Oyvind's library.
https://code.launchpad.net/~oyvind-aabling/kicad-newlib/mod
It should be able to solve your issues. I've been trying to get this
library into kicad for about two years. However, the author still feels
additional testing is needed. Let's just say the last correction was
made about a year and a half ago.
Alex
Hi ! I know I've been quiet for quite a while, but I'm
still around, following the awesome progress of KiCad :-)
Hmm, has it really been that long ?-(
Oh well ... time flies (like an arrow, etc.) ...
Great work with the nanometer stuff - nice to get
rid of those annoying metric rounding errors :-)
I haven't had time to try out the scripting stuff yet
(have to learn Python first ...), but it also looks
very interesting - too bad it isn't perl, though ;-(
What I'd *really* like to see in KiCad (pcbnew) is parametric modules :-)
Some modules, like SMD chip components exists only in a
few sizes (Note 1), but others, like pinarrays exists in hundreds,
if not thousand of variations: <pin pitch> * <pin count>
* <# of rows> * <row pitch> * <pin diameter> * <pin length above>
* <pin length below> * <body height> * <straight/bent pins>.
Instead of defining each and everyone of these (and the one you need
might be missing in the lib ...), it would be nice with a (scripted)
class instead, with a popup for defining the parameters. In many cases
with a list of popular/common variants (e.g. for axial resistors).
Each parameter should be selectable from a list of
standard values with a field for entering a custom value.
I guess, this must be written in Python, using the new scripting interface ?
Note 1: And, if I've understood it correctly, even those have variants, as
the optimal pad size/position for SMDs depends on the soldering technique ?
I've been working on a little embedded system and other stuff, so
I've been using my own lib for a while (a good way to discover bugs :-)
I've noticed a problem with the AEC SMD capacitors,
that must be corrected before inclusion in KiCad:
The important stuff (silkscreen and pads) is OK, but the 3D body
is rotated 180deg (dunno how I could have missed that ... :-(
I've defined a few more parts, but some of them are
only of interest to me, so I wanna weed those out
of the (public) lib before I upload my changes.
I don't think anyone will be interested in e.g. the
inductors in the Bang & Olufsen UltraSound Remote
(no, not IR ...) for the B&O BeoVision 6002 TV ;-)
Simon
On 11/10/2012 4:26 PM, Alex G. wrote:
On 11/06/2012 06:26 AM, Simon Turner wrote:
It would be good to look at all schematic and footprint libraries as
many are wrong or basic shapes are missing. For example the vertical
TO-220 footprint has a rather unusual pinout numbering that screws
things up and many symbols come with no pin mumbers so they don't
associate and the netlist info is missing. The problem is even if I
correct this it reverts back later. You can have the best software you
like but if the connections are all coming out wrong no one will want to
use it.
The problem with looking at all schematic symbols is that it's a
daunting, meticulous, and time-consuming task. I think a "we'll cross
that bridge when we get to it" approach is much more suitable in this
case. We just need an easy way for users to submit corrections/improvements.
The problem with weird pin naming also stems from the fact that the
transistor pin-out is in no way standardized. Some TO-92 for example are
EBC, while others are CBE, so the only way to make sure you get the
correct pin-out is to name both symbol and footprint pins E, B, and C,
and choose the correct footprint (EBC or CBE in our case). It still
confuses me.
Going back to the FTDI symbols, I am hoping to maybe get a couple of
"field tests" of the symbols. I should have all of them withished within
a week or so.
Alex
Simon
On 06/11/2012 01:08, Alex G. wrote:
I've recently started working on a symbol library for FTDI chips. I'm
not sure if there is anyone already working on this or not. I do know
we have a few older FTDI symbols in interface.lib, but nothing recent.
My goal is to have symbols that have the same pin arrangement as and
and look consistent with the symbols in the FTDI datasheets.
I've created a branch here:
https://code.launchpad.net/~mrnuke/kicad/ftdi_symlib
I would like to ask interested people to have a look at the library
and give me feedback. I'm certain some of you could tell me "Alex, you
idiot, you're doing _this_ wrong".
I'm looking forward to hearing some fresh ideas.
Alex
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Øyvind.
**************************************************************************
* Øyvind Aabling E-mail : Oyvind.Aabling@xxxxxxxx /~\ The ASCII *
* UNI-C Lyngby Phone : +45 35 87 88 89 \ / Ribbon *
* DTU Building 304 Phone : +45 35 87 89 51 (direct) X Campaign *
* DK-2800 Lyngby Fax : +45 35 87 89 90 / \ Against *
* Denmark Web : http://www.uni-c.dk/ HTML Email! *
**************************************************************************
Quidquid latine dictum sit, altum viditur.
Follow ups
References
