Component management is always a problem, and the question really is, is the parts in eeschema the right place to do this?
There are probably as many answers to this as there are people who want to manage components:-) My two-pennyworth on the matter: eeschema is a generic schematic package, where the same symbol can be used to represent a wide range of devices. So if you want to include things like manaf and ordering info, then you will have to create an individual component for every different version of a device. Things get even more complex if you have multiple sources for a component. This always seems to be a clumsy method to me, especially if you are dealing with a lot of products. A more general method would be to use the component list output, and import that into a more conventional database. Then you will not be limited in data entry and other options. You may also find that things such as the component file generated by pcbnew will give you enough info as is, it lists the reference, value and module used. It needs a bit more processing for importing into a database, but it's fairly trivial. The main drawback with this method is that you have to maintain the database and ensure that any changes are applied correctly. However the ability to combine this with existing stock control systems and so on may outweigh this extra work. As for parts and footprints, talking to other designers who use all sorts of design tools, not just Kicad, the general opinion is that it takes very little time to draw up a device or footprint, and you only have to do this once. Doing this and creating your own libraries and modules, is the only way to be sure that you have the correct device/dimensions for your particular needs. (this is aside from 3D representations which is another matter). Maintaining your own libs and so on also safeguards yourself from things being overwritten during software upgrades. Andy On Mon, 05 Apr 2010 03:29:38 -0000 "Frank" <[email protected]> wrote: > Looking for parts - Checkout per your mosfet example: > http://octopart.com/parts/search?q=2SK1058&js=on > This type of web site, I've been looking for for some time. > These guys have also not said no to the possibility of > someday including Kicad (and others) symbols and footprints > for each part. > -Frank > > --- In [email protected], "marcmendezbermond" <marcmen...@...> > wrote: > > > > Hi all ! > > > > Progressing on my project, I have a question about component/library > > management. > > > > The "Component list" feature of eeschema is quite convenient but is there a > > way to accelerate data input ? I would like to use custom fields of > > components to store manufacturer, part number, ordering info and doing it a > > component at a time is quite annoying ... > > > > My idea would be to input this straight in my custom library, then using > > its symbols would replicate those info to my schematic. > > > > In the end, when I inserting a 2SK1058 mosfet that would result in a > > component with Manufacturer field set to Hitachi, Part No 2SK1058, Ordering > > No 1234567 in my favorite store, and so on ... > > > > Thanks in advance for pointing me out any method, > > M. > > > > > > > ------------------------------------ > > Please read the Kicad FAQ in the group files section before posting your > question. > Please post your bug reports here. They will be picked up by the creator of > Kicad. > Please visit http://www.kicadlib.org for details of how to contribute your > symbols/modules to the kicad library. > For building Kicad from source and other development questions visit the > kicad-devel group at http://groups.yahoo.com/group/kicad-develYahoo! Groups > Links > > >
