Part Manager

The part manager uses a relational database to store parts used in the development of electronic assemblies. The part manager also stores attributes for these parts and can place these attributes into a component or symbol for placement into schematics.

The part manager provides a GUI that allows the user to browse and edit the data in the part database. The user can select parts in the GUI, then cut and paste them into their schematic.

The following figure shows the relationship between the parts manager and other applications in the gEDA suite.

The part database can be configured as either local or remote. In the remote configuration, many users can access the part database concurrently.

The following figure shows the entity relationships for a part in the resistor category. The category does not reference any tables in the resistor category, but only contains the view name and stored procedures to manipulate a part within the resistor category. This mechanism allows the tables and relationships to vary by category.

The database always contains tables to store the following entities. The database contains additional tables to store specific categories of parts (e.g. a capacitor table, a diode table, a resistor table, etc…). This list excludes junction tables and metadata tables.

A class of parts (e.g. capacitors, diodes, resistors, transistors, etc…). A category can contain sub-categories (e.g. small-signal diodes, TVS diodes, zener diodes, etc…) Sub-categories can include additional sub-categories. All parts within a category or sub-category share the same set of attributes (e.g. forward voltage, maximum current, power dissipation, etc…). Sub-categories do not need to inherit the attributes of their parent.

The category stores metadata for mapping the part’s database columns to the component attributes. For numeric attributes, the category stores the column’s unit of measure (e.g. amps, farads, ohms, volts, etc…).

The category also stores the names of database views and stored procedures to access and manipulate the tables of parts within the category.

Currently, a company represents a part’s manufacturer.

A type of part. The device name only provides a mechanism to map parts to symbols. A part in the library of device resistor can use all the symbols in the library where device is resistor. Similarly, a symbol where device is resistor can represent any part of device resistor. When importing a symbol, the database uses the value of the symbol attribute DEVICE as the initial value for the device field. The user can change the device field after import using the part manager GUI.

Any file associated with a part. Documents can include datasheets, erata, user manuals, etc… This entity stores a path to the actual document file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.

The PCB artwork associated with a package. This entity stores a path to the actual PCB footprint file. The path could either be local or network. The path stored in the database is relative to the base path stored in the configuration file.

When instantiating a component or creating a heavy symbol that uses a Spice model, the following database columns map to the following attributes.

A part represents a class of components. The database uses this version of the part table when configured to use a flat part table. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.

Other columns TBD.

A part represents a class of components. The database uses this version of the part table when configured to use hierarchical part tables. The flat and hierarchical parts tables are mutually exclusive. The database uses one or the other.

The physical structure, or form-factor, of a part (i.e. 0603, SOT-23, PDIP16). Each package can associate with zero or more footprints. Also, each footprint could represent zero or more packages.

The graphical representation of a part. This entity uses the symbol base filename as the unique name of the symbol. This base filename is relative to one of the component libraries found in the configuration files. The component library paths can either be local or network.

Part categories break down classes of parts hierarchically. The category hierarchy exists separately than the part hierarchy. The category hierarchy only provides the user with a system to locate parts quickly. A child in the category hierarchy does not need to inherit the attributes of a parent.

The parts manager uses categories to keep the lists of parts manageable. If the list of parts in a particular category grows large, the category can be subdivided into sub-categories.

It may be difficult to change the categories, using a GUI, because of the part table abstraction through database views and stored procedures. It may be better to distribute the parts manager with a default configuration that works for most.

The default hierarchy of parts follow:

• Discretes
  • Diodes
    • Small-signal
    • TVS
    • Zeners
• Passives
  • Capacitors
  • Inductors
  • Resistors

The part hierarchy allows the database to attach additional attributes to a class of parts. These attributes provide a faster means to locate and select parts, especially commodity parts. The database only provides these additional attributes when configured to use hierarchical part tables.

These additional attributes, stored in numeric format, allow SQL to select parts. For example, to locate diodes with reverse voltage greater than 60 volts, use the following SQL statement.

SELECT * FROM DiodeV
    WHERE VR > 60;

The intent of the part hierarchy does not include exhaustively classifying all electronic parts or fully parameterizing any class of electronic part. The part hierarchy simply intends to allow the user to quickly locate a part, such as a 4.75 kΩ 1% 0603.

TODO: Develop guidelines for subclassing part.

Proposed guidelines for including attributes:

• Include attributes that are encoded in the manufacturer part number.
• Exclude attributes that are inconsistently characterized between manufacturers.
• Exclude attributes that must be either read from graphs, or calculated.

These attributes may not work for everyone, so the database allows the user to customize these part tables.

Bipolar Junction Transistors (BJTs) extend part with one additional table of attributes.

Table name: BJT

View name: BJTV

The same table contains small-signal and power BJTs. These transistors can be placed into separate views using the following criteria.

Capacitors extend part with one additional table of attributes.

When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.

Inductors extend part with one additional table of attributes.

When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.

MOSFETs extend part with one additional table of attributes.

Rectifier, small-signal and switching diodes extend part with one additional table of attributes. Most diodes can be placed into this table.

Table name: Diode

View name: DiodeV

The same table contains rectifier, small-signal and switching diodes. These diodes can be placed into separate views using the following criteria.

Resistors extend part with one additional table of attributes.

When instantiating a component or creating a heavy symbol, the following database columns map to the following attributes.

TVS diodes extend part with one additional table of attributes.

Zener diodes extend part with one additional table of attributes.

Table name: ZenerDiode

View name: ZenerDiodeV

The part manager GUI is the main component of the part management system. The part manager GUI allows the user to browse and manipulate the part database and to cut and paste symbols into the schematic editor.

Copy a part to the clipboard as a component (light symbol).

1. The user selects a part in the database.
2. The user selects a symbol to represent the part.
3. The GUI instantiates a component and overrides attributes.
4. The user previews the component to ensure the graphic looks correct.
5. The user selects the copy action.
6. The GUI copies the component to the clipboard.
7. The user pastes the component in gschem.

Export a part to a file as a heavy symbol.

1. The user selects a part in the database.
2. The user selects a symbol to represent the part.
3. The GUI clones the symbol and substitutes attributes.
4. The user previews the symbol to ensure the graphic looks correct.
5. The user selects the export action.
6. The GUI prompts the user for a filename and location.
7. The GUI writes the symbol to the given file.

Create a new part database.

1. TBD

Destroy an existing database.

1. The user selects the destroy database action.
2. The GUI prompts the user for confirmation.
3. The application drops the database.

Add a new document to the database.

1. The user selects the add document action.
2. The GUI prompts the user for a filename and location.
3. The application adds the document to the database.

Associate a document(s) with a part(s).

1. The user selects one or more parts from the database.
2. The user selects the attach document action.
3. The GUI prompts the user with a list of all the documents in the database.
4. The user selects one or more documents from the list.
5. The application attaches the given documents to the given parts.

Delete a document(s) from the database. Remove all references.

1. The user selects one or more documents in the database.
2. The user selects the delete action.
3. The GUI prompts the user for confirmation.
4. The application deletes the selected documents from the database.

Disassociate a document(s) from a part(s). All parts and documents remain in the database. Only the relationship is removed.

1. The user selects one or more parts from the database.
2. The user selects the detach document action.
3. The GUI prompts the user with a list of all the documents attached to the given parts.
4. The user selects one or more documents from the list.
5. The GUI prompts the user for confirmation.
6. The application detaches the given documents from the given parts, if attached.

Edit the metadata associated with a document.

1. TBD

View a document.

1. TBD

Delete a footprint(s) from the database. Remove all references.

1. The user selects one or more footprints in the database.
2. The user selects the delete action.
3. The GUI prompts the user for confirmation.
4. The application deletes the selected footprints from the database.

Edit the metadata associated with a footprint.

Import a single footprint file into the database.

1. The user selects the import footprint file action.
2. The GUI prompts the user for a footprint file.
3. The application creates a footprint in the database for a new footprint file.
4. The application updates a footprint in the database for an old footprint file.

Import all footprint files from the library into the database.

1. The user selects the import footprint library action.
2. The application searches all footprint libraries.
3. The application creates footprints in the database for new footprint files in the library.
4. The application updates footprints in the database for old footprint files in the library.

Add a new model to the database.

1. The user selects the add model action.
2. The GUI prompts the user for a model type, name, and filename.
3. The application adds the model to the database.

Associate a model(s) with a part(s).

1. The user selects one or more parts from the database.
2. The user selects the attach model action.
3. The GUI prompts the user with a list of all the models in the database.
4. The user selects one or more models from the list.
5. The application attaches the given models to the given parts.

Delete a model(s) from the database. Remove all references.

1. The user selects one or more models in the database.
2. The user selects the delete action.
3. The GUI prompts the user for confirmation.
4. The application deletes the selected models from the database.

Disassociate a model(s) from a part(s). All parts and models remain in the database. Only the relationship is removed.

1. The user selects one or more parts from the database.
2. The user selects the detach model action.
3. The GUI prompts the user with a list of all the models attached to the given parts.
4. The user selects one or more models from the list.
5. The GUI prompts the user for confirmation.
6. The application detaches the given models from the given parts, if attached.

Import all Spice files from the library into the database.

1. The user selects the import Spice library action.
2. The application searches all Spice library directories for files.
3. The application parses files to extract model names.
4. The application creates Spice models in the database for new models in the library.
5. The application updates Spice models in the database for old models in the library.

TBD

Add a new package to the database.

1. TBD

Delete a package(s) from the database. Remove all references.

1. The user selects one or more packages in the database.
2. The user selects the delete action.
3. The GUI prompts the user for confirmation.
4. The application deletes the selected packages from the database.

Edit the package data.

1. TBD

Add a new part to the database.

1. TBD

Delete a part(s) from the database. Remove all references.

1. The user selects one or more parts in the database.
2. The user selects the delete action.
3. The GUI prompts the user for confirmation.
4. The application deletes the selected parts from the database.

Edit the part data.

1. TBD

Search for a part in the database using the manufacturer part number.

Delete a symbol(s) from the database. Remove all references.

1. The user selects one or more symbols in the database.
2. The user selects the delete action.
3. The GUI prompts the user for confirmation.
4. The application deletes the selected symbols from the database.

Edit the metadata associated with a symbol.

1. TBD

Import a single symbol file into the database.

1. The user selects the import symbol file action.
2. The GUI prompts the user for a symbol file.
3. The application creates a symbol in the database for a new symbol file.
4. The application updates a symbol in the database for an old symbol file.

Import the contents of the component library into the database.

1. The user selects the import symbol library action.
2. The application searches all component libraries specified in the configuration file for symbol files.
3. The application creates symbols in the database for new symbol files in the library.
4. The application updates symbols in the database for old symbol files in the library.

The company view lists all the companies in the database.

The device view lists all the devices stored in the database.

The documentation view shows all the documents stored in the database.

The footprint view shows all the footprints stored in the database.

The package view shows all the packages stored in the database.

The part view shows parts stored in the database. The user selects the category from the left pane. The parts within the given category show in the middle pane. After selecting a part from the middle pane, the symbols available for that part show in the lower right pane. The upper right pane shows the symbol preview.

The edit→copy command places the component on the clipboard. The component can then be pasted into gschem.

The symbol view shows all the symbols stored in the database. The upper right pane shows the symbol preview.

The parts manager reads gaf's Scheme configuration files using Guile-1.8. The parts manager reads the following configuration files in order. The parts manager attempts reading the file in each of the given paths in order.

1. system-gafrc
   1. the path specified in the environment variable GEDADATARC
   2. the paths retrieved from g_get_system_config_dirs() + “gEDA”
   3. the paths retrieved from g_get_system_data_dirs() + “gEDA”
2. gafrc
   1. the path specified in the environment variable HOME
   2. ~/.gEDA
3. gafrc
   1. .
4. system-gpartsrc
   1. the path specified in the environment variable GPARTSDATARC
   2. the paths retrieved from g_get_system_config_dirs() + “gparts”
   3. the paths retrieved from g_get_system_data_dirs() + “gparts”
5. gpartsrc
   1. the path specified in the environment variable HOME
   2. ~/.gEDA
6. gpartsrc
   1. .

The parts manager supports the following configuration items from gaf.

The parts manager supports the following private configuration items.

The parts manager uses dynamically loadable modules to support the various database engines. The parts manager uses a separate module to support each database engine.

• MySQL
• PostgreSQL
• SQLite

Adds a directory to the list of directories where documentation is stored.

Adds a directory to the list of directories where footprints are stored. The parts manager can import newlib footprints from these directories.

Adds a directory to the list of directories where SPICE models are stored. The parts manager can import these models from these directories.