The TMU documentation is captured in the User Guide below.
This is a document that captures an overview of each subsystem, use case, and relevant components. Similar to a User Guide, this document explains how to use a feature of a project. For example, it will explain the necessary hardware connections and how to communicate over CAN to the BMS. There may be several Function Descriptions (one for each revision).
This is a spreadsheet of each test that confirms that the project satisfies each engineering requirement.
Take some time here to explain where you went wrong in the project development. This is a chance to reflect on your shortcomings and share your solutions.
<Example: We did not use the correct resistor values for our power indicator diodes. We resolved this issue by carefully writing out the Ohm's Law equations, and used Digikey's calculator.>
Most EVT projects go through 2-3 revisions before the project is complete. Keep a record of changes for each revision. I recommend following the outline below:
Revision 2:
Recalculated resistor value for LED1, now the LED1 lights up when the board is powered up.
Found the correct measurement chip footprint and fixed it in Altium.
Revision 1:
Base project, ordered from PCBway and discovered that the measurement chip footprint was inverted. Also, the 3.3V LED1 would not light up.
<Team Lead> - Clayton Koppi - My number is (413) 284 7356, but you can call me anytime ;)
Team Member: - Greg Reiser - <Slack me at: [] >
Team Member: Magee Confronter - Dhimitri Kulira - Team Member Contact Info
Team Member: Team Lead (like the metal, he's heavy and weighs us down) - <Nick Kablier> - <Team Member Contact Info>
Team Member: - Bekah Thompson - Team Member Contact Info
Team Member: - Mira Hedley - Team Member Contact Info>
Team Member: Software Guy - <Diego Diaz Peon Gonzalez [Diego.lastName()] > - <Team Member Contact Info>