...
| View file | ||||
|---|---|---|---|---|
|
Schematic
- Block Diagram to follow the function of the board and quickly understand
- Ensure that none of the GPIOs from the controller board have pins sharing the same number while requiring different interrupt controllers (e.g. do not have PB1 and PA1 as separate inputs triggered by the interrupt controller)
Board - Traces
- Run DRC to verify spacing, make sure all traces are connected and find any net antenna. (All silk errors are not important as long as the silkscreen is thoroughly verified already for spacing).
- Make sure to set the rules for trace widths to be relevant for the max and min for your board.
- Check for any right angles in tracks
- Does not make a difference in performance, but looks terrible
- Check thickness of traces
- Any high current traces should be sized appropriately
- Go through the high current path through the board, around all components, etc. to make sure that there are no thin traces
- Make sure there are absolutely no acute angles between traces and traces, and traces and pads.
- Ensure differential signals (CAN, isoSPI) run parallel and as close together as possible
...
- Make sure there is a keep out layer surrounding your board.
- Make sure all these layers are selected when generating your gerbers.
Silkscreen
- All components are labeled in a logical manner
- Maybe get someone else to look at it and make sure that they can follow the placement if any names had to be placed in weird orientations, etc.
- Connectors are labeled
- With function on top side (power input, CAN, Thermistor, etc.)
- With pinout on bottom side (or top side if possible)
- MSXIV Logo is on the board
- Correct board Rev is listed
- Pin 1 labeled on all ICs
- Ensure bottom silkscreen is mirrored
- Optional parts (such as CAN termination) is labeled
- Ensure all polarized components are labelled
- Double-check all of silkscreen in 3D mode
...