Difference between revisions of "MISC-TN-023: Altium Designer-based workflow"
(→Introduction) (Tag: Visual edit) |
(Tag: Visual edit) |
||
| Line 17: | Line 17: | ||
==Introduction== | ==Introduction== | ||
| − | Unlike most of the Technical Notes (TN for short) available in this wiki, this one does not refer to any DAVE Embedded Systems' product. Instead, | + | Unlike most of the Technical Notes (TN for short) available in this wiki, this one does not refer to any DAVE Embedded Systems' product. Instead, this article deals with one of the tools we use for hardware designing, namely [https://www.altium.com/altium-designer Altium Designer]. In particular, this article describes how DAVE Embedded Systems conceived an Altium Designer-based design workflow, which is integrated with the existing company's IT infrastructure. The result is depicted in the following image. |
TBD | TBD | ||
== Requirements == | == Requirements == | ||
| − | + | In order to implement a glueless integration towards all the company's departments, the workflow had to satisfy the following requirements: | |
| + | * Technical documents for manufacturing: At the end of the designing process, a set of standardized technical documents has to be generated automatically for the manufacturing department. This set must be equivalent to the ones produced by the other hardware designing workflows already in use. | ||
| + | * Database interfacing: The hardware projects must be interfaced to the existing component's database, which is shared across all the company departments (purchasing, manufacturing, R&D, etc.). From this database, several data are retrieved and stored in the project for each instantiated component such as the manufacturer code, the operating temperature range, the nominal value in case of passive components, etc. | ||
== Implementation == | == Implementation == | ||
TBD | TBD | ||
Revision as of 13:36, 16 June 2022
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
History[edit | edit source]
| Version | Date | Notes |
|---|---|---|
| 1.0.0 | June 2022 | First public release |
Introduction[edit | edit source]
Unlike most of the Technical Notes (TN for short) available in this wiki, this one does not refer to any DAVE Embedded Systems' product. Instead, this article deals with one of the tools we use for hardware designing, namely Altium Designer. In particular, this article describes how DAVE Embedded Systems conceived an Altium Designer-based design workflow, which is integrated with the existing company's IT infrastructure. The result is depicted in the following image.
TBD
Requirements[edit | edit source]
In order to implement a glueless integration towards all the company's departments, the workflow had to satisfy the following requirements:
- Technical documents for manufacturing: At the end of the designing process, a set of standardized technical documents has to be generated automatically for the manufacturing department. This set must be equivalent to the ones produced by the other hardware designing workflows already in use.
- Database interfacing: The hardware projects must be interfaced to the existing component's database, which is shared across all the company departments (purchasing, manufacturing, R&D, etc.). From this database, several data are retrieved and stored in the project for each instantiated component such as the manufacturer code, the operating temperature range, the nominal value in case of passive components, etc.
Implementation[edit | edit source]
TBD
