← Back to team overview

kicad-developers team mailing list archive

Library woes (was Symbol library for FTDI chips)

 

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

> 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
> 



Follow ups

References