...
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Project ScopingBefore starting any project at NER we must determine the scope, constraints, timeline and otherwise the overall definition of the project. This is typically completed by leadership such as the chief engineer, system head, and potential project leads. A project at a high level (general function, budget, timeline) will be defined in FinishLine, and the details regarding actual electrical I/O level decisions may be elaborated on in further meetings and documented in Confluence. Project CreationActually creating the project in Altium Designer to be shared via 365! This is typically done by the project lead and only requires coming up with a project name and filling in some basic parameters. Details on this can be found here: https://nerdocs.atlassian.net/wiki/spaces/NER/pages/136314883/Schematic+Capture#Project-Creation Schematic DesignDesign of the actual electronics circuits. This encompasses picking components, digging into their datasheets to learn how to implement them, completing the wiring required, and even simulating when necessary to validate behavior. Critical setup and organization of the schematics should be done by the project lead, and then sub-circuits can be more easily divided between any available team members. Schematics should follow the Vault Guidelines Details on this can be found here: Schematic Capture We’ve recently changed that component build-out will not be required until the layout stage rather than during schematic design. For schematics “Draft” components are okay! Asynchronous Schematic ReviewReview of the electrical design of the system. This review will be completed by everyone on the team who can contribute their time! Contents should be the electrical design itself, component choices (function as well as cost and solderability), and general schematic cleanliness & organization. Details on this can be found here: {link to schematic review checklist}
Component Build-outDuring schematic design you may have selected some part numbers and assigned a symbol to it for schematic purposes, but not associated further data to the part. Component build-out is when all components are fully filled in to be used for layout. Typically this includes adding a footprint, filling in parameters, and updated supplier part numbers (SPNs). All members should participated in this, and given their modularity, this is a common task for new members to get familiar with Altium. Details on this can be found here: Component Creation PCB Layout DesignDesigning the way components and copper are placed on the board. Similar to the schematic design, the project lead will be responsible for critical actions, such as importing the schematics, and organization of efforts across the project team. All members should be able to participate in layout, but it can vary depending on board size and timeline demands. Layouts should follow the Vault Guidelines Details on this can be found here: PCB Layout (Matt Edition)
Component ReviewAs components are built out, they all must undergo a review. This can happen in parallel with layout and other processes, as long as all components are reviewed before release. These are completed by senior members/leaders of the team to ensure that all components in the library are robust. In summary, this just consists of checking every component thoroughly against the Component Review Checklist before a board is fabricated with the parts. Asynchronous Layout ReviewDesign review of the completed board. Similar to the schematic, all members of the EE team are encouraged to participate! At this stage the board should be ready for fabrication, so the entire board is open to feedback, but the focus is primarily on the layout of the board. Details on this can be found here: {link to layout review checklist}
Project ReleaseOnce fully reviewed, the board needs to be made! Our Altium vault has been setup with OutJob templates that enable easy board exports for fabrication, alongside marking in the version control that the board is being released as a formal revision. This is typically done by the project lead or relevant head/chief. Details on this can be found here: https://nerdocs.atlassian.net/wiki/spaces/NER/pages/156205064/PCB+Layout+Matt+Edition#Export-for-Fabrication-(Out-Jobs) |
Navigating Altium
On Startup
...
More tips are highlighted in the Quick Reference & Tips page. Additionally, official documentation on selection is provided by https://www.altium.com/documentation/altium-designer/design-object-selection.
Object Properties & Parameters
Almost everything in Altium has properties and parameters. What you can do with these will be discussed throughout these Confluence pages, but below will explain how to open the properties panel.
By default, the Properties panel will be hidden and needs to be opened. This is done via the panels button in the bottom right of the window. It can also be accessed from the toolbar “View” dropdown.
{2 images for these methods}
Once open, the panel can be accessed by clicking on its tab (wherever you decide to place it), or the panel can be “pinned” open, using the pin button at the top of the window. Pinning prevents the panel from minimizing itself.
{image of pinned panel}
If the properties panel is open, an object properties can be viewed simply by clicking on something. Anything that is selected (even the files themselves) will have properties that will show in the panel.
When working in schematics or layouts, if you have the panel closed, any component properties can be opened by double clicking the component. This will automatically expand the panel and show the properties of the selected component.
Multiple objects can also be highlighted at once, with varying results depending on what was selected. Only common fields will be shown, and those will differing values will be displayed with an * rather than an exact value.
Using selection filters (https://nerdocs.atlassian.net/wiki/spaces/NER/pages/153026566/Intro+to+Altium#Selection-Filters) or queries (Altium Query Language) is the best way to select multiple objects and successfully edit properties of all of them at once
Component Workflow
To ensure consistency in our components, a lot of effort goes into keeping them organized. A large part of this is using Altium’s ple built in state flows to indicate status of components. Below is an example of where you see these states:
...