For less-common parts, I would think the schematic symbols would be
generated _from_ data in the parts database. Let's say you're
interested in using a particular 80-pin IC with a pinout that doesn't
resemble any other part that is in the database or the symbol
library. Here's an example of a possible work flow... not everyone
will want something this complicated, but various people will various
parts of this flow:
-enter all known data about the part into the database (pinout, package
options, full part number, operating temperature range, possible
suppliers and supplier part numbers, etc.)
-generate a .sym file from the database to match the part's pinout --
could be done automatically with options to cover different work flows
and user preferences.
* make a schematic
* select generic parts from the database by spec and attach them to the
symbols
- Generate a BOM. query database for purchasing info.
- Run checks. query the database for more info about parts in BOM. Do
they all meet operating temperature requirement?
* run the conversion to netlists, proto-board, model
(* run model and re-select parts, re-run conversion)
* layout the board
The point is, I think the parts database will be accessed at several
points in the process, not just post-gschem and
pre-layout/simulation/BOM generation. Also, there's no reason for a
parts database to be tied to gEDA specifically (as it would be if it
was integrated in gschem); it is a very generic function and could be
useful to all EDA users.
Note that in this flow, the schematic symbols stay fairly 'light' but
additional info is available from the database for tasks that otherwise
would require 'heavy' symbols.
__________________________________________________________________
From: Armin Faltl <armin.fa...@aon.at>
To: gEDA user mailing list <geda-user@moria.seul.org>
Sent: Thu, May 6, 2010 11:41:18 AM
Subject: Re: gEDA-user: Database on symbols, footprints and other (was
"Re: gattrib")
>> I think even a lot of the database stuff is possible in Guile.
I've used a Guile interface layer to MySQL and PostgreSQL, it works
very well. It's called Guile-DBI:
>>
>> [1]http://home.gna.org/guile-dbi/
>>
>
> Hmm. Could a parts database utility be constructed to be logically
inserted ahead of the gnetlist back end (using -l or -m options)?
Plug-in...
>
Understandig the details of slots etc. or not, this is the way I want
to
work:
* make a schematic
* select parts by spec and attach them to the symbols
* run the conversion to netlists, proto-board, model
(* run model and re-select parts, re-run conversion)
* layout the board
Is this what you mean with "ahead of the gnetlist back end" ?
_______________________________________________
geda-user mailing list
[2]geda-u...@moria.seul.org
[3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
References
1. http://home.gna.org/guile-dbi/
2. mailto:geda-user@moria.seul.org
3. http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
_______________________________________________
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
