Adding components of the same series can be time and library space consuming.To prevent that every engineer uses his own variant of a corporate standard.To make sure that every engineer works with the same up-to-date library.To maintain your libraries: keep them up-to-date and uniform.To keep a consistent and clean structured library so that components are easy to find.The challenges with standalone libraries are: Or maybe you are using a dedicated library for every project, whatever works best for you. So, you better split them up into categories like capacitors, resistors, IC’s, diodes, transistors, etc. However, this may become a big file which is difficult to maintain over some time. You may have one library to store all your components in. Other tools like Altium do have both options. Some EDA tools like Eagle do have one single library for symbols and footprints, while other tools do have separated libraries for symbols and footprints. Components may consist of schematic symbols, PCB footprints (shapes), simulation models and a lot of other parameters, like MPN (Manufacturer Part Number), manufacturer, value, etc. Libraries are containers to store components in. We want to make this transition because we are growing and running against some challenges. As you may know we, and also the majority of design houses, are still using standalone libraries. We share this blog because we are currently in the transition of moving from standalone libraries to database libraries for our EDA (Electronic Design Automation) tool Altium. Laura van Hoof // EDA libraries: the transition from standalone to database libraries
0 kommentar(er)
