Цитата(cioma @ Feb 27 2009, 17:26)
How it works:
When component is placed into the DxDesigner schematic over the DxDataBook, a symbol with an appropriate name in the DxDataBook table field in the symbol search path. When found, a part is taken from PDB (according to DEVICE field in the DxDataBook table). Pin numbers from the part are annotated to the symbol on the schematic, attributes from the DxDataBook table and from the part are added to the symbol on the schematic.
1. Within the database to which DxDataBook connects, each component must have a unique identifier. This identifier is usually a corporate part number. If not a corporate part number, then some other identification method must be decided upon.
2. Parts in DxDataBook are linked to PDB parts in a central library by part number (DxD DEVICE attribute). The location of the central library is contained in the viewdraw.ini file for the project (which is how DxDataBook locates the central library).
Enabling the CDB flow reduces the amount of attribute information associated with a symbol at the schematic level. The only attribute information retained on the symbol in a DxDesigner schematic is the following:
- Part number
- Part name/label
7. When adding symbols to DxD, only "symbols" are added. Parts (PDB) have only indirect relation to this process (e.g. when using "add device" command, Part's attributes are added to symbol (DEVICE, optionally physical pin numbers etc)). At schematic development stage we are in general untied from Parts. This is true for adding symbols over DxDB, which is completely unrelated to Parts data. When scheme is finished, developer performs "packaging" process (see outlook:DxDesigner, tip 7). Packaging uses DEVICE attribute to relate symbol to package over part (PDB). That's why it's necessary to have DEVICE attribute value on the symbol the same as PartNumber attribute of a part (PDB).
I mean where i can find something similar to this~~
Информация о компонентах, DxDesigner
Mar 6 2009, 08:59
