kicad-developers team mailing list archive

[Alex G <mr.nuke.me@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/06/2010 10:04 PM, Vesa Solonen wrote:
> On Fri, 6 Aug 2010, Alex G wrote:
> 
>> I've been struck by Kicad's lack of all but the most basic footprints.
>> As such, I have started drawing some footprints, and would like to get
>> them into the official Kicad release ASAP.
> 
> I might put some prerelease directory for unchecked libraries, but I
> fear no symbol-footprint associations will get there. Maybe I'll spend
> my sunday pondering the library structure. Any ideas from everybody are
> appreciated. In short form, please.
> 
>> Here's a short list of the footprints I'm currently working on
>>
>> TDFN-EP 6, 8, 10, and 14 pin
>> This is a 3x3mm package, and I also have a basic 3D model for it
>> More info on this package at:
>> http://pdfserv.maxim-ic.com/package_dwgs/21-0137.PDF
> 
> This is definitely something to be added to the generating script for:
> http://www.uni-c.dtu.dk/~univind/kicad/oaa_smd_qfn.brd
> 
>> Sharp S202S02 - Solid-State relay
>> I have a beta 3D-model and footprint for this.
>> More at:
>> http://www.parallax.com/Portals/0/Downloads/docs/prod/compshop/400-00053Datasheet.pdf
>>
>>
>> Molex Micro-fit connectors
>> Nothing yet here, but am plannig to get footprints and 3D models for the
>> entire line (SMD and throughhole; single-row and double-row).
>> (Luckily, Molex provides 3D models for these).
>> http://www.molex.com/molex/common/staticLoader.jsp?fileName=/cmc_upload/0/000/0-8/368/w-b-matrix/wtb-matrix.html&pageTitle=Introduction&chanName=family&channel=products&key=microfit_30
>>
> 
> With these I'm happy with hand drawn stuff, but for the connectors I'd
> suggest working with Oyvind. Just in case a scripted way can be
> developed easily enough. I've used those SSRs with just very rudimentary
> fooprint, so I thank you in advance :)
> 
I've forwarded the discussion to Oyvind. Took some time as Gmail
IMAP/SMTP was down for several hours. I'll see what he has to say, and
get back as soon as I hear from him.

>> As you may tell by now, I am the definition of noob.
>> I draw the footprints with Inventor, export them as IGES, import the
>> IGES in FreeCAD, export it as .obj, and finally import that into Wings
>> 3D.
>> I'm not very good with applying colors, so help from someone with more
>> experience is greatly appreciated.
>>
>> I've been hearing some fuss about a scripted approach to generating
>> footprints. Does anyone have examples on that?
> 
> Please take a look at http://www.uni-c.dtu.dk/~univind/kicad/
> 
>> Then, how do I get the files to the right place? Can I just attach them
>> to the emails, or should I rather upload them to a public place and only
>> send the link?
> 
> Kicad-newlib on Launchpad for bigger work, but ocassional stuff is fine
> on the list or even directly to me. Ping on the list first is a good
> practice.
> 
>> There's also a question on 3D-modles for packages that don't have
>> protruding pins, such as TDFN. Should I draw the pins on the model, or
>> will a rectangular box do? This is more a matter of aestethics. I'm not
>> lazy, just trying to avoid extra work if it has no meaning.
> 
> Again I'd like to point you to Oydvind's work.
> 
>> I've been hearing discussions about a format change for library files. I
>> think that getting the footprints in properly with the current format,
>> and then converting them if/when that happens is the best choice. Having
>> to import several libraries in each project is time consuming, and it
>> would be nice to have them in the default install.
> 
> I'm leaning towards incomplete newlib as a branch in release library.
> Just a bunch of symbols with coherent style, footprints and 3D without
> association data. When file format features get ready, we'll start
> actual component specific data gathering for pin/part swap etc. When the
> branch is strong enough we may chop the old trunk away. Any objections
> to that?
> 
If that means that the footprints will be in the official release, no
objection. We can always add the associations later.

Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMXK5pAAoJEOYeVCFxnjTcs5wIALxqIamrIQooWvlZ5BLz7HlE
DjTf7gYBo5mf1/O2pY4cFROb2g7n55PX6B9FtxZD6kg99n92PCR+BlevqD4NjBY4
Li1Tlfu4QRhpbkmNn2TR9hKRfUigOhuxnbQOq4q7jsHI1oxk1TTLCVKcZwKqjTdo
6ubIif2atfPjQU+HOOfbc7d6zDq47ywa8onpIjPWl2pZO/BTCUXbMBrAPtCm7mbh
hBMHPJPQfOfLCMPB01sbbHZLKDUGBHTM+/e47Uc9XGS8sjF2RIyA7JUly8rYuJv+
IK0BF+n4Pu48yutqhVVUGorZwzUtGapowTnaV5yTViqzqyEGSSCO8TN+rfT0se8=
=InjH
-----END PGP SIGNATURE-----