[Kicad-lib-committers] Libraries converted to Pretty on GitHub

Hi people, My name is Carl Poirier. I have been subscribed to the KiCad developers mailing list for a few months now, and a few days ago I have given a hand at converting the existing libraries to the new pretty format. In case you either are not subscribed to this list or haven't read the

[Kicad-lib-committers] Question about libcms

Hi people, As discussed in previous topics, I'm going through a rename of most libraries to have some consistency and also a more beautiful library table. Looking at the library named "libcms", I can't really see what it is exactly, as I see no relation between its parts. Furthermore, its name sa

Re: [Kicad-lib-committers] Question about libcms

Thanks for the explanation. On Tue, Nov 19, 2013 at 1:59 AM, jp charras wrote: > Le 18/11/2013 20:49, Carl Poirier a écrit : > > Hi people, > > > > As discussed in previous topics, I'm going through a rename of most > > libraries to have some consistency a

Re: [Kicad-lib-committers] Names of KiCad footprint libraries

No they don't. It is because I have not yet updated them, following last week's refactoring and renaming of the libraries. They will bear the same names as in the bazaar legacy repository. On Wed, Nov 27, 2013 at 11:35 AM, Povilas Kanapickas wrote: > Currently the libraries in the Carl's reposit

Re: [Kicad-lib-committers] Names of KiCad footprint libraries

Hi Bernd, The names for the pdf previews should follow up shortly. On Wed, Nov 27, 2013 at 1:39 PM, Bernd Wiebus wrote: > Hello Povilas. > > > Currently the libraries in the Carl's repository on GitHub[1] have > > names like this: > > > > VML0806_Housing_Rohm_RevA_26Oct2012 > > > > This is a l

Re: [Kicad-lib-committers] Names of KiCad footprint libraries

I'm also in favor of the "lib_" prefix. On Wed, Nov 27, 2013 at 1:50 PM, Carl Poirier wrote: > Hi Bernd, > > The names for the pdf previews should follow up shortly. > > > On Wed, Nov 27, 2013 at 1:39 PM, Bernd Wiebus wrote: > >> Hello Povilas. >

Re: [Kicad-lib-committers] Names of KiCad footprint libraries

ortly. > > I fear not so fast. Because i have to recreate the pdfs, I named/cited > the files inside the documents. > So renaming the files will not help for this. > > With best regards: Bernd Wiebus alias dl1eic > > > Am Mittwoch, den 27.11.2013, 13:50 -0500 schrieb Carl

Re: [Kicad-lib-committers] Names of KiCad footprint libraries

modules, i would enjoy a copy. just to avoid this trouble at future. > > With best regards: Bernd Wiebus alias dl1eic > > > > > Am Mittwoch, den 27.11.2013, 15:17 -0500 schrieb Carl Poirier: > > Oh, thanks for the information. > > > > > > > > >

[Kicad-lib-committers] Move to pretty libraries on Github

Hi guys, It's now time to move to the pretty libraries on Github. As you may have noticed, Dick has very recently taken ownership of the library repository on bzr. He has made it read-only and renamed it to " library-read-only". The

Re: [Kicad-lib-committers] Move to pretty libraries on Github

ar for anyone. If someone has any questions, please don't hesitate to ask. Carl On Tue, Dec 3, 2013 at 11:58 AM, Kerusey Karyu wrote: > W dniu 02.12.2013 19:06, Carl Poirier pisze, i pisze, i czytać trzeba dużo: > > Hi guys, >> >> It's now time to move to the pre

Re: [Kicad-lib-committers] Library support

I'm in a hurry right now, but I'll look into that tomorrow if not done! On Sun, Dec 22, 2013 at 5:55 AM, Marco Serantoni wrote: > Hi, > I’ve seen that the library was missing the APPLE support in CMake, i’ve > added it and you can see the patch at the end of this mail. > Could someone add this o

Re: [Kicad-lib-committers] How to contribute?

Hi Jorge, The libraries have moved to Github, under the KiCad organization. Please send me your files and I will look into committing them. Carl On Sat, Jun 23, 2012 at 1:38 PM, Jorge Aparicio wrote: > Hello everyone, > > I'd like to contribute schematic symbols of stm32 microcontrollers, me

Re: [Kicad-lib-committers] Move to pretty libraries on Github

Hi Bernd, You've been added to the Librarians team. As for PDF, it's supposed to work. The footprint-docs are already uploaded. Carl On Sun, Dec 22, 2013 at 4:22 AM, Bernd Wiebus wrote: > Hello Carl. > > > The first step you guys can do is register at Github. Then, please > > send me your ID

Re: [Kicad-lib-committers] Library support

Hi Marco, Sorry for the delay. I got caught up by Christmas. It's committed now. Carl On Sun, Dec 22, 2013 at 8:56 AM, Carl Poirier wrote: > I'm in a hurry right now, but I'll look into that tomorrow if not done! > > > On Sun, Dec 22, 2013 at 5:55 AM, Marco

[Kicad-lib-committers] Adding a new library

Hi people, I just committed some footprints and their 3D models, under the new libraries "Pin_Headers" and "Socket_Strips". The first one is a more complete version of the Pin_Arrays library, which, if no one objects, we could delete. I prefered to rename it because it's clearer that a header mate

Re: [Kicad-lib-committers] Library build process

I'm not sure to understand why you would need symlinks. Just set KISYSMOD to the directory containing all your .pretty footprints. We can assume the fp_libtable in kicad-library/template directory to be up to date. We, the librarians, have to keep it in sync will the .pretty repos. On Sat, Jan 4

Re: [Kicad-lib-committers] launchpad "kicad-lib-commiters" cleanup

Worst case, one will simply recreate it. I say yes. On Sun, Jan 5, 2014 at 1:13 AM, Johannes Spanier wrote: > Hi Librarians, > > Just a quick question: > OK to delete the launchpad repo lp:~kicad-lib-committers/+ > junk/library-experiment? > There is no code in it and it has never been pushed t

Re: [Kicad-lib-committers] Fwd: Re: Library build process

You can also not use python to get the repo list. Curl and the github API will do it. Have a look here . On Sun, Jan 5, 2014 at 2:54 PM, Johannes Spanier wrote: > Hi Cirilo, > > >I think that script is pretty good for the

Re: [Kicad-lib-committers] Fwd: Re: Library build process

You can examine that header, and query page by page. See here . I just wanted to point that out, but it's now obvious the python way is much simpler. On Mon, Jan 6, 2014 at 2:31 AM, Johannes Spanier wrote: > Hi C

[Kicad-lib-committers] More Renaming and Complete fp-lib-table

x27;t do a dumb-merge right away. Lastly and FYI, the naming of libraries goes in this order: 1. Part type (resistors, capacitors, etc), must be in plural form 2. Package type (SOIC, SMD, etc) 3. Manufacturer 4. Part number Regards, Carl Poirier -- Mailing list: https://launchpad.net/~kicad-lib-

Re: [Kicad-lib-committers] module format conversion

Hi Johannes, To convert a library programmatically, you have to build KiCad with python scripting enabled. Then, in kicad/scripts, you have a file called lib_convert.py which can do the conversion. I did a script, a while ago, that simply called this . It's on the developer's mailing list here

Re: [Kicad-lib-committers] VRML models

The GITHUB plugin is now part of the default build so the configuration is supposed to be minimal. As for package maintainers, if they do not like it, they can make a local libraries package that will need to be updated very often to stay up to date. Let's recall that the GITHUB plugin has been mad

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

I just noticed I had sent this to you only instead of the list: I believe for now the only convention-like we have is this: > https://lists.launchpad.net/kicad-developers/msg11729.html > > We should first elaborate a bit more on that convention, and then we could > write it down on the wiki. > Re

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

Let's continue our discussion about this. Lorenzo, do you have access to the relevant documents? Carl On Wed, Feb 26, 2014 at 2:22 PM, Vesa Solonen wrote: > 26/02/14 11:00, Kerusey Karyu kirjoitti: > > > > In 25 lutego 2014 19:46 Carl Poirier wrote: > > > >>

[Kicad-lib-committers] Contributing to Github Libraries

. There are lots of things to do, some of which are in progress already. We'll discuss some of them if you guys are alright with all of this. Regards, Carl Poirier -- Mailing list: https://launchpad.net/~kicad-lib-committers Post to : kicad-lib-committers@lists.launchpad.net Unsubscrib

[Kicad-lib-committers] Complete set of connectors

Hi folks, A contributor by the name of Michal Stec has sent updates to kicad-library. Specifically, he has sent a complete set of connectors from 1x1 to 2x40, made to match the fixed Pin_Arrays.pretty and Socket_Strips.pretty. I am wondering what would be best to do with the symbols. You can have

Re: [Kicad-lib-committers] Complete set of connectors

M, jp charras wrote: > Le 19/03/2014 03:38, Carl Poirier a écrit : > > Hi folks, > > > > A contributor by the name of Michal Stec has sent updates to > > kicad-library. Specifically, he has sent a complete set of connectors > > from 1x1 to 2x40, made to

Re: [Kicad-lib-committers] [Kicad-developers] Environment Variables

use it to make kicad lib better. Is it doable? How? > What do u think? > Fabrizio > On 18/03/2014 1:32 PM, "Carl Poirier" wrote: > >> Hi Fabrizio, >> >> does >> this<https://lists.launchpad.net/kicad-lib-committers/msg00078.html>answer &

Re: [Kicad-lib-committers] Contributing to Github Libraries

;. A video is a good idea. I'll look into that. Regards, Carl On Mon, Mar 17, 2014 at 6:38 PM, Carl Poirier wrote: > Hi everybody, > > We have recently got some offer to contribute to Github librairies either > by adding more parts or helping with the validation process. There wer

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

That works for me. > And don't forget about the zero orientation :D (hint: ISO, JEDEC and IPC > differs :D) On Mon, Mar 10, 2014 at 2:44 PM, John Beard wrote: > On 10/03/14 15:10, Carl Poirier wrote: > > Let's continue our discussion about this. Lorenzo, do you have access

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

an be appended, separated by an underscore. Every acronym has all of its letters capitalized, obviously. Manufacturer name depends on how it's written normally. Ex: NEC, Microchip I'm waiting for comments. Regards, Carl On Thu, Mar 20, 2014 at 7:10 PM, Carl Poirier wrote: > Sim

Re: [Kicad-lib-committers] [Kicad-developers] Environment Variables

git is made for developers > not for pcb designers who we are trying to take advantage of for > improving kicad lib quality. > > So, is a solution to ease this lib contrib process needed needed? > > If you do not mind I'd like to pose this question on the kicad dev mailing > li

Re: [Kicad-lib-committers] [Kicad-developers] Environment Variables

nt? > > thanks for the many info. > > > > On Fri, Mar 21, 2014 at 2:26 PM, Carl Poirier > wrote: > > You have to replace "yourUsername" in the URL by your actual Github > > username. So that it leads to your forked repo. Sorry if I was not clear. > &

Re: [Kicad-lib-committers] [Kicad-developers] Environment Variables

gt; you get my point? > > I have the feeling that if you want to take advantage of some guy > helping us updating the standard kicad lib, we can't expect him to > create a github account. > > my 2c > > Cheers > Fabrizio > > > On Fri, Mar 21, 2014 at 3:53 PM, Ca

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

rough-hole components, origin is set on pad 1. 4. For surface-mount devices, origin is placed in the middle of the chip. I'd like to hear your thoughts about all of this. Regards, Carl On Thu, Mar 20, 2014 at 7:53 PM, Carl Poirier wrote: > OK, here is a small something to begin with.

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

esistors 2. 150mil for everything needing pin numbers. Regards, Carl On Mon, Mar 24, 2014 at 2:40 PM, Kerusey Karyu wrote: > In 23.03.2014 20:57, Carl Poirier wrote: > > > Symbols: > > > > 1. Default 300mil pin length is used. > > > Why? Why? Why? I need only

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

ppending the reason. Names for devices that have their own footprint 1. Name of part. 2. Part number. Ex: "Oscillator_SI570" 4. Any modification to the original footprint, indicated by appending the reason. I would like to hear any concerns and comments. Regards, Carl On Tue, Mar 25,

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

On Sat, Apr 5, 2014 at 4:28 AM, Kerusey Karyu wrote: > W dniu 03.04.2014 02:24, Carl Poirier pisze: > > > About pin length, what about using SI units? >> >> At this point, we shall to ask: How many users use SI units when drawing > schematics? Most of them will lo

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

Kerusey, I would like you to reply to my previous message, if possible. On Sat, Apr 5, 2014 at 7:55 PM, Carl Poirier wrote: > > > > On Sat, Apr 5, 2014 at 4:28 AM, Kerusey Karyu wrote: > >> W dniu 03.04.2014 02:24, Carl Poirier pisze: >> >> >> Abou

Re: [Kicad-lib-committers] Fwd: Re: About library naming conventions

Hi Kerusey, In order to reach more people, I restarted the conversation on the developer's mailing list. I will reply there. Carl On Sat, Apr 19, 2014 at 1:43 AM, Kerusey Karyu wrote: > W dniu 06.04.2014 01:55, Carl Poirier pisze: > > >> At this point, we shall to ask

Re: [Kicad-lib-committers] Hi people

Lorenzo, please read my last email on the developer's mailing list. I suggested we use it :D On Fri, May 2, 2014 at 3:13 PM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Fri, May 02, 2014 at 09:37:31PM +0300, Vesa Solonen wrote: > > Wonderful work, especially the character set.

Re: [Kicad-lib-committers] Decoded fp-lib-table and re-organisation ideas

Thanks for the initiative, John, for starting the conversation with your own observations. > > * Printtrafo_CHK: Some sort of PCB transformers, but not sure about > > the meaning of "CHK". The rest of the description seems rather > > generic to metric PCB transformers (EI38, etc). > CHK ist j

Re: [Kicad-lib-committers] Remarks to KiCad Library Convention

> Maybe CamelCase would save some space. But Underscores would be nice > to separate different types of information in the name. More, a dash could > be used to seperate two following capital letters, where you cannot see > the separation by CamelCase. Also a dash could be used instead of a > decim

Re: [Kicad-lib-committers] Remarks to KiCad Library Convention

t; On Sat, May 17, 2014 at 09:39:39PM -0400, Carl Poirier wrote: > > We had decided to follow JEDEC Publication Number 95, Section 1.6 > "Outline > > Classification" which contains the dash, for more legibility. > > Given how JEDEC names are built there is never ambig

Re: [Kicad-lib-committers] Mailing list access

I do think so. Anyway, their stuff will need to be approved before committing, following the git work flow of committing and creating a pull request. Carl On Thu, May 22, 2014 at 11:25 AM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > I have received a request for joining the maili

Re: [Kicad-lib-committers] Hi all

On Thu, May 22, 2014 at 5:31 PM, Paweł Dras wrote: > On Thu, 22.05.2014 10:03, Lorenzo Marcantonio wrote: > >> On Thu, May 22, 2014 at 09:49:38AM +0200, Paweł Dras wrote: >> >>> - Make a rule for module creation that footprint outlines can't be made >>> on >>> >> Side note: pcbnew can erase the

[Kicad-lib-committers] Cleannig Footprint Libraries

Hi folks, With our recent library convention, we can start cleaning the footprint libraries. Here is a list of all footprint libraries: 1. Air_Coils_SML_NEOSID.pretty 2. Buzzers_Beepers.pretty 3. Capacitors_Elko_ThroughHole.pretty 4. Capacitors_SMD.pretty 5. Capacitors_Tantalum_SMD

Re: [Kicad-lib-committers] Remarks to KiCad Library Convention

to...@logossrl.com> wrote: > On Mon, May 19, 2014 at 07:50:31PM -0400, Carl Poirier wrote: > > Does anyone have any objection to using the IEEE/ANSI standard for > > designator letters? > > AFAIK these are the most used ones > > -- > Lorenzo Marcantonio > Logos Srl &

Re: [Kicad-lib-committers] Mailing list access

Okay good, thanks. On Fri, May 30, 2014 at 9:24 AM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Fri, May 30, 2014 at 09:19:58AM -0400, Carl Poirier wrote: > > Lorenzo, > > > > Did you reply to the prospective member? Is it someone with email "

Re: [Kicad-lib-committers] Cleannig Footprint Libraries

d > be Housing_TO-220. This is important to see all this housings close to each > other. > > The same situation is with the names Sockets_*, Terminal_Blocks and even > with Pin arrays. I suggest to change in all prefix to Connectors_ > > Regards, > Paweł > > > 2014-

Re: [Kicad-lib-committers] Cleannig Footprint Libraries

Hi John, I renamed the library to "Connectors_Molex.pretty". You can go on and at the same time incorporate what you were working on previously. On Fri, May 30, 2014 at 6:09 AM, John Beard wrote: > I'd like to take Connectors_Serial_MOLEX.pretty for the moment, please. > > Would it be possible

Re: [Kicad-lib-committers] Cleannig Footprint Libraries

On Fri, May 30, 2014 at 4:05 PM, Vesa Solonen wrote: > 30/05/14 03:42, Carl Poirier kirjoitti: > > Hi folks, > > > For those of you who have expressed their interest to give a hand, > > please voice in, saying which library you would like to tackle. > > Basically,

Re: [Kicad-lib-committers] Cleannig Footprint Libraries

d a new job and > have much to do. But for first, i would like to have good strukturated > library conventions, which is written down offically somewhere. > > There should also some rules for pdf previews, mesh models and boards, > because there is a (not so bad) way to distribute footprints with > boards, which can used for pdf footprints, too. > If you looked about the librarys, you will have noticed my pdf previews, > and there should be some rules for them, too. (like having always a > scale for checking printer distorsion, hints about CC or > I have them written down last year or so, and i will search for them and > give them to you. They are incomplete, but might help you save some > time. > Good, I'll wait to hear back from you on that matter. > > At last, here is one library left over at my harddisc, and i wonder, > wether it is not at your list: > "TO-12_TO-18_TO-43_TO-42_Housings_11Jun2013.mod". There are also mesh > models for TO18, too. I will rename and transfer it to > "Housings_TO-12_TO-18_TO-43_TO-42.pretty". ;O) > > With best regards: Bernd Wiebus alias dl1eic > Took care of the renaming. Also, footprints from SMD_Packages should all be put in the more specific libraries. Then we will delete that one. It's big and takes a significant amount of time to load anyway. Your input is really appreciated. Thanks a bunch, Carl Poirier -- Mailing list: https://launchpad.net/~kicad-lib-committers Post to : kicad-lib-committers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-lib-committers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-lib-committers] Silk screens over pads and naming

About the footprint names, this is a specific device. As per rules 9.x you just go with the name and part number. Connector_Molex_PicoBlade_53398-0271.kicad_mod On Mon, Jun 2, 2014 at 6:06 PM, John Beard wrote: > On 02/06/14 22:37, Jean-Paul Louis wrote: > >> I was talking about the engineerin

Re: [Kicad-lib-committers] Silk screens over pads and naming

Nothing like that yet AFAIK. On Mon, Jun 2, 2014 at 6:55 PM, John Beard wrote: > On 02/06/14 23:21, Carl Poirier wrote: > >> About the footprint names, this is a specific device. As per rules 9.x >> you just go with the name and part number. >> >> Connector_Molex_

Re: [Kicad-lib-committers] Silk screens over pads and naming

I like it! I will write this down in the convention shortly if that's what we settle for. On Tue, Jun 3, 2014 at 4:59 AM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Tue, Jun 03, 2014 at 09:44:53AM +0100, John Beard wrote: > > How about this for an example of how the SMD heade

Re: [Kicad-lib-committers] Silk screens over pads and naming

About these rules for the silkscreen, are they only for SMD? I am under the impression it does not apply well to THT components, for example an electrolytic capacitor where we often see a circle with one half full to indicate polarity. This would be partly hidden once the board is assembled. On T

Re: [Kicad-lib-committers] Silk screens over pads and naming

area. > > my $0.02, > > Jean-Paul > AC9GH > > > On Jun 8, 2014, at 11:14 AM, Carl Poirier > wrote: > > > About these rules for the silkscreen, are they only for SMD? I am under > the impression it does not apply well to THT components, for example an > el

[Kicad-lib-committers] Library convention for symbols

Hi people, There is some stuff left to do in the library about symbols. I had not gotten to it yet, so here are my first ideas for the missing sections: 2. Symbol Library Names (.lib files) 2.1. Category of parts, may be shortened for common components. ex: "

Re: [Kicad-lib-committers] Library convention for symbols

t of shapes. > > > Just a thought, > > Jean-Paul > AC9GH > > On Jul 18, 2014, at 7:40 PM, Carl Poirier > wrote: > > > Hi people, > > > > There is some stuff left to do in the library about symbols. I had not > gotten to it yet, so here are my first

Re: [Kicad-lib-committers] Library convention for symbols

mbol for each package. For example, one chip might very well have the same pinout between its SOIC-8 and TSOP-8 variant. On Sat, Jul 19, 2014 at 5:00 AM, Kerusey Karyu wrote: > W dniu 19.07.2014 01:40, Carl Poirier pisze: > >> >> 2. Symbol Library Names (.lib files) >>

Re: [Kicad-lib-committers] Library convention for symbols

In this case it's not much of a problem because the extra letters indicating the footprint are official names from the datasheet. But are there cases where a part is manufactured in many packages and doesn't have a distinction for it in the name? On Sun, Jul 20, 2014 at 3:35 AM, Kerusey Karyu wr

Re: [Kicad-lib-committers] Library convention for symbols

riginal footprint, indicated by appending the reason. Ex: different pin ordering: "transistor_PNP_pinswap1" 4.5. Indication of quantity if symbol is an array. ex: resistor array: "Resistor_x8" Any other comments? On Sat, Jul 26, 2014 at 2:13 AM, Kerusey Karyu wrote: > W

Re: [Kicad-lib-committers] Library convention for symbols

e prefilled with the object name." in the general rules, whereas I believe it applies only to symbols. Actually most of them if not all are filled with the reference designator by default. On Sat, Jul 26, 2014 at 11:05 AM, Carl Poirier wrote: > Let's use the full name, then. So here a

Re: [Kicad-lib-committers] Rule 6.5

Hi Kerusey, Yes it is a good adjustment. I will add it to the next revision. Thanks for making the convention better. ;-) Regards, Carl On Mon, Aug 4, 2014 at 4:45 PM, Kerusey Karyu wrote: > Carl. I have some attention to rule 6.5. You wrote: > "6.5. Silkscreen it is not superposed pads, is

Re: [Kicad-lib-committers] Library convention for symbols

I moved that rule 1.6 away and into the symbols section. On Wed, Jul 30, 2014 at 11:51 AM, Carl Poirier wrote: > This has been committed. > > BTW, is there any particular reason to having the value field of a > footprint default to "VAL**", besides indicating it has not

[Kicad-lib-committers] rectangular passive components

Hi people, Is there any reason to have various footprints such as 0805, 0603, etc. for every component type? I got a suggestion by Simon Gansen to unify them into a single library, which would be "Passive_SMD.pretty". If no one objects, we will go that route. Carl -- Mailing list: https://laun

Re: [Kicad-lib-committers] rectangular passive components

Oh yes, I didn't think about that. We'll leave it as it is for now, then. On Wed, Aug 13, 2014 at 1:02 PM, Kerusey Karyu wrote: > Is there any reason to have various footprints such as 0805, 0603, etc. >> for every component type? >> >> There is one rational reason for this, but not such impor

Re: [Kicad-lib-committers] rectangular passive components

So you mean having the "Passive_SMD.pretty", but having in it "C_0805.kicad_mod", "R_0805.kicad_mod" and so on? Why would this be better than having them in "Capacitors_SMD.pretty" and "Resistors_SMD.pretty", along with other SMD footprints? On Wed, Aug 13, 2014 at 1:17 PM, Vesa Solonen wrote:

Re: [Kicad-lib-committers] rectangular passive components

see the benefit of doing so if we cannot remove duplicates for different types of components (0805, etc.). The original suggestion was intended to remove those duplicates. On Wed, Aug 13, 2014 at 1:55 PM, Vesa Solonen wrote: > 13/08/14, 20:43, Carl Poirier kirjoitti: > > So you mean ha

Re: [Kicad-lib-committers] Kicad-library Wiki page

Hi Kerusey, It's a good idea. I will add the content to it shortly. In the documents, does it look good if we simply put a link to the wiki? Carl On Sat, Aug 23, 2014 at 1:19 AM, Kerusey Karyu wrote: > The kicad-library repo on GitHub has a Wiki. > > I think we could use this Wiki system to a

Re: [Kicad-lib-committers] Kicad-library Wiki page

Hi Kerusey, This is very great. Thanks a bunch for taking care of it. I am not sure to understand what you are talking about for the home page. Are you talking about describing what a repository is? This would be like explaining what github is all about. By the way, thanks for managing the bunch

Re: [Kicad-lib-committers] Kicad-library Wiki page

On Sun, Aug 31, 2014 at 2:48 AM, Kerusey Karyu wrote: > >> I am not sure to understand what you are talking about for the home >> page. Are you talking about describing what a repository is? This would >> be like explaining what github is all about. >> >> I'm talking about this particular reposi

Re: [Kicad-lib-committers] Kicad-library Wiki page

I added a few more words on the wiki. Doing so, I was wondering something. What are the .kicad_pcb and .brd files in the modules directory? Opening them with pcbnew doesn't seem to yield much. On Sun, Aug 31, 2014 at 8:29 AM, Carl Poirier wrote: > > > > On Sun, Aug 31, 2014 at

Re: [Kicad-lib-committers] Kicad-library Wiki page

Oh wait. There clearly seems to be a display problem in my pcbnew. It's not the files. On Sun, Sep 7, 2014 at 9:12 PM, Carl Poirier wrote: > I added a few more words on the wiki. Doing so, I was wondering something. > What are the .kicad_pcb and .brd files in the modules directo

Re: [Kicad-lib-committers] Kicad-library Wiki page

at 9:21 PM, Carl Poirier wrote: > Oh wait. There clearly seems to be a display problem in my pcbnew. It's > not the files. > > On Sun, Sep 7, 2014 at 9:12 PM, Carl Poirier > wrote: > >> I added a few more words on the wiki. Doing so, I was wondering >> som

[Kicad-lib-committers] Adhesive for SMD components

Hi folks, The SMD resistors and capacitors have an adhesive dot in the middle. Should all SMD components have one? If so, is there a recommended size? Regards, Carl -- Mailing list: https://launchpad.net/~kicad-lib-committers Post to : kicad-lib-committers@lists.launchpad.net Unsubscribe :

Re: [Kicad-lib-committers] Adhesive for SMD components

, 2014 at 7:57 AM, jp charras wrote: > Le 15/09/2014 08:30, Lorenzo Marcantonio a écrit : > > On Sun, Sep 14, 2014 at 07:09:32PM -0400, Carl Poirier wrote: > >> The SMD resistors and capacitors have an adhesive dot in the middle. > Should > >> all SMD components have one?

Re: [Kicad-lib-committers] Adhesive for SMD components

I want to avoid exceptions as much as possible. Thus, I suggest we put all LGA, CGA and BGA at 0.5. Is QFN also at 0.15? On Mon, Sep 15, 2014 at 9:35 AM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Mon, Sep 15, 2014 at 08:41:16AM -0400, Carl Poirier wrote: > > &g

Re: [Kicad-lib-committers] Adhesive for SMD components

1mm. Right? Since, I believe, we don't have any CGA in our libraries, I say we just don't write it until it happens. On Mon, Sep 15, 2014 at 5:52 PM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Mon, Sep 15, 2014 at 02:10:39PM -0400, Carl Poirier wrote: >

Re: [Kicad-lib-committers] Adhesive for SMD components

On Tue, Sep 16, 2014 at 1:12 AM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Mon, Sep 15, 2014 at 06:38:27PM -0400, Carl Poirier wrote: > > What I mean is I want it to be as simple as possible for potential > > contributors. I don't want to require

[Kicad-lib-committers] Fwd: question about SMD_Packages

een. Any comments? I have attached the file. Regards, Carl -- Forwarded message -- From: nnn Date: Fri, Sep 19, 2014 at 6:39 PM Subject: Re: question about SMD_Packages To: Carl Poirier This one looks ok. I looked at my msp430 programmer, and I saw that they've done sth like t

Re: [Kicad-lib-committers] Fwd: question about SMD_Packages

What I don't like is we have to extend the courtyard solely for the purpose of the pin one marking. On Sat, Sep 20, 2014 at 12:34 PM, Kerusey Karyu wrote: > W dniu 20.09.2014 o 17:58, Carl Poirier pisze: > > We have some great contributions here prepared by Michal Stec. He'

Re: [Kicad-lib-committers] Fwd: question about SMD_Packages

f the courtyard, as it could potentially collide with some other silkscreen. On Sat, Sep 20, 2014 at 7:10 PM, John Beard wrote: > On 20/09/14 16:58, Carl Poirier wrote: > >> Hi folks, >> >> We were unsure how to make the silkscreen for QFN packages. If it's >> d

Re: [Kicad-lib-committers] Adhesive for SMD components

Just a quick question, is there any problem with the courtyard exceeding the PCB edges? In this case, is the DRC supposed to fail? I'm thinking about board edge connectors. On Tue, Sep 16, 2014 at 8:49 AM, Carl Poirier wrote: > > > On Tue, Sep 16, 2014 at 1:12 AM, Loren

Re: [Kicad-lib-committers] Some symbols adjusted to Library Convention

Hi Kerusey, Great job on these. Indeed, going through these disruptive moments might be though, but required. I believe you are the first applying the convention to existing symbol libraries. If some particular symbols raise questions or have some uncovered aspects in the convention, please let u

Re: [Kicad-lib-committers] Adhesive for SMD components

Hi Lorenzo, Thanks for the information. This question arose when looking at a pull request. Regards, Carl On Tue, Oct 14, 2014 at 2:37 AM, Lorenzo Marcantonio < l.marcanto...@logossrl.com> wrote: > On Mon, Oct 13, 2014 at 11:14:48AM -0400, Carl Poirier wrote: > > Just a qui

Re: [Kicad-lib-committers] The Microchip Mess and how to clean it up

Hi Kerusey, I totally support these changes. My argument is always the same: If we don't do the disruptive cleaning now, we'll have to do it later down the road when there will be more users. So the earlier the better. On Wed, Nov 5, 2014 at 3:26 PM, Javier Serrano < javier.serrano.par...@gmail

Re: [Kicad-lib-committers] Octopart common parts list library

Hi Jon, Sorry to be a bit late to the party. Thanks for pointing out our library convention to them. I was thinking we could add a "CPL" tag in the description of the approved elements in our library. This way people would just have to enter this tag in the search box, and they will get all their

Re: [Kicad-lib-committers] Octopart common parts list library

library > with that extra tag. > > > Jon > > On Sat, Nov 8, 2014 at 11:02 AM, Carl Poirier > wrote: > >> Hi Jon, >> >> Sorry to be a bit late to the party. Thanks for pointing out our library >> convention to them. >> >> I was thinking we

Re: [Kicad-lib-committers] library cleaning - massive attack proposition

fter > modification, so I'd like to ask also what do you think about changing > lines width of silkscreen to 0.15 and changing sizes of fonts to some > default value. > > If you like the idea and nobody else will write the script, I will start > writing it in C. > > >

Re: [Kicad-lib-committers] library cleaning - massive attack proposition

onal: add searching > 3d models > It works, but it would be better if somebody could improve it. Finding and > replacing is a bit complicated. > If my code is ok and can be accepted I can do the rest. > > W dniu 13.11.2014 14:50, Carl Poirier pisze: > > I think it sounds goo

Re: [Kicad-lib-committers] library cleaning - massive attack proposition

; What will be font size? Will you set some value, or leave empty (to be > taken from kicad defaults)? > How do you modify all repositories? If you have some method to do it > easily, can you modify repositories with my script (when I finish it)? > > W dniu 21.11.2014 22:28, Carl Po

[Kicad-lib-committers] Authors of AFF_2x7SEG-DIGIT_10mm and LCD_ALPHA

Hi guys, Is any of you responsible for the footprints AFF_2x7SEG-DIGIT_10mm and LCD_ALPHA? Michal sorted the 7-segment displays and he couldn't find any information on the Internet about these displays. Carl -- Mailing list: https://launchpad.net/~kicad-lib-committers Post to : kicad-lib-c

Re: [Kicad-lib-committers] Library cleaning - changes applied

Hi Michal, Thanks for your great contribution. You however forgot to change the commit message in the script I sent you. It's not dramatic, however ;-) On Tue, Dec 9, 2014 at 11:30 AM, nnn wrote: > Cleaned up: 3d models names and paths, footprints values, references, > names, 3d links, text siz

Re: [Kicad-lib-committers] Library cleaning - changes applied

Hi Michal, Permissions should be fixed now. Sorry for the inconvenience. On Tue, Dec 23, 2014 at 12:24 PM, michal stec wrote: > I've no permission to make changes on: > > Connectors_Molex.pretty > Crystals.pretty > Converters_DCDC_ACDC.pretty > Displays_7-Segment.pretty > Crystals_Oscillators

[Kicad-lib-committers] TO-220 mounting tab

Hi librarians, In the Transistors_TO-220.pretty library, is there any reason why the pad for the mounting tab was not added with the same number as the one it's connected to? I'd like to solve in the KLC the issue raised here . Carl -- Mailing lis

Re: [Kicad-lib-committers] TO-220 mounting tab

What I'm talking about is simply this: [image: Inline image 1] The pad size for the tab is approximate. Carl On Fri, Dec 26, 2014 at 8:09 PM, Carl Poirier wrote: > Hi librarians, > > In the Transistors_TO-220.pretty library, is there any reason why the pad > for the mou

Re: [Kicad-lib-committers] TO-220 mounting tab

Vesa, If I understand correctly, you say the oyvind-aabling library is a good example of having multiple variants of the same housing, which you don't like. Right? On Mon, Dec 29, 2014 at 3:39 AM, Vesa Solonen wrote: > > On Fri, Dec 26, 2014 at 8:09 PM, Carl Poirier wrote: > >

Re: [Kicad-lib-committers] TO-220 mounting tab

Vesa Solonen wrote: > 31/12/14, 04:01, Carl Poirier kirjoitti: > > Vesa, > > > > If I understand correctly, you say the oyvind-aabling library is a good > > example of having multiple variants of the same housing, which you don't > > like. Right? > >

  1   2   >