Supporting the broad range of the design tasks performed through the electronic development process requires numerous model kinds and library formats.īelow is a summary of each model and library kind.
These are referred to as model libraries. Others, like PCB footprints, are stored in a file that accepts one or many footprints.
Some model kinds, like SPICE, are stored one-model-per-file, these are referred to as model files. Some of these use a standardized file format, like SPICE, while others use a proprietary format, like the schematic library file, which is used to store schematic symbols or components. Models and Model LibrariesĮach type of model and component needs to be stored in a model file or library. The 3D model is actually placed within the footprint. The symbol model links to the other models to fully describe that component in each domain. Parameters then add the additional detail needed to identify the real-world physical component, such as the wattage, tolerance, purchasing details, datasheet references, etc. Because the design environment is built around the idea that the design starts with the schematic, the schematic symbol is used to tie the various models together. For schematic capture, the model is referred to as a symbol. One component, with a different representation for each design domain.Įach design domain requires a specialized model. During the design capture and implementation processes, a component is represented as a symbol on the schematic, as a footprint on the PCB, as a SPICE model for simulation, as a signal integrity description to analyze the quality of the signals, and as a three-dimensional model for 3D component and PCB visualization. But in the virtual world of design, components have to be abstracted into a range of models that can be used across the various design domains. In the real world, components are tangible objects and are, therefore, relatively easy to identify.
So what exactly is a component and where are they stored? The components are the basic building blocks of that product. The components and how they are connected are what creates your unique, electronic product.
For information regarding other component management methodologies, for example, Workspace library components, refer to the following pages. This page describes file-based libraries only.
0 kommentar(er)
