Development of ECAD libraries is a groundbraking basis of electronics design, a very first brick in a future medical device or scientific instrument. Therefore, our customers tend to ask lots of various questions trying to assess the approach we use in component library development. The present FAQ page provides answers on some typical questions we get.
Yes, we build 3D-models of components and deliver them in STP, STEP or any other popular formats based on the requirements of our partners.
- Is EDALITY capable of delivering library symbols and footprints that adhere to provided strict specifications and design rules?
Yes, the ECAD library team of EDALITY works exactly this way with some of our long-term partners providing them with the component libraries based on agreed requirements.
In some cases, these guidelines reach hundreds of pages full of specific requirements and obligations that should be followed on every step of ECAD library development.
The capacity and speed of processing requests can be defined for a specific type of components with regards to the complexity of requirements implied by a customer. Therefore, it is impossible to provide a universal and helpful indicative number.
The most reasonable way of starting permanent cooperation in the field of component library development is with a test period during which our partners themselves have a chance to evaluate the speed and quality of ECAD library parts EDALITY delivers.
We are able to support multiple stages of quality check procedures, these stages may include:
- Manual crosscheck by another engineer or engineer
- Quick pre-delivery check (general accuracy and completeness of deliverables)
- Automated DFA check
- Full part number
- Actual full datasheet
- Expected delivery time (tags “urgent” or “regular” may be used instead)
- Any specific requirements and recommendations
We have a lot of design translation experience on the level of PCBs, so we dealt with library translation issues a lot as well. When there is no good translator available (which is a typical situation) it can be a pretty complex task.
For migration of big libraries certain automation may be needed, we have some experience of writing scripts for these matters as well.
- EDALITY’s or Customer’s FTP server
- Third-party (cloud) data storage services
- Via VPN/Remote Desktop
Normally we stick to the preferences of our partners.
For big components, we always make pin lists, we then use them while building library parts and can deliver them with the component library if needed. For simple parts, we do not prepare pin lists, but can start doing that upon request.