Skip to content

Summer Meeting Notes

Seiya Ono edited this page Jun 7, 2017 · 3 revisions

Summer Meeting Notes

PiElectrical Project Structure

Each staff will be fully in charge of one board that they see from start to production:

  1. Learn Eagle
  2. Learn their board
  3. Understand the previous iteration of the board if it exists and its flaws
  4. Fix the flaws, think of ways to make it better (a stretch)
  5. Once board layout is done, generate a BOM of the board, and send to Sourcing
  6. Send out for Rev A
  7. Ask people to help out to fabricate Rev A
  8. Creating a simple testing platform to test new boards
  9. Software should be developed for the sensors to interface with Hibike
  10. Talk to Mechanical about enclosures
  11. Touch up silkscreen to ready for production
  12. Send out Rev B
  13. Fabricate and test to make sure it works 100% under student use conditions
  14. Touch up silkscreen and finalize enclosures with Mechanical
  15. Send out final production sized order
  16. Compile production BOM and send to Sourcing
  17. Organize all the components to prep EProd
  18. Create a guide to fabricate the board in house for staff
  19. Lead a one week EProd session to finish the board (Fab, Enclose, Flash)
  20. Documentation! Make demos or small code tid bits for students and staff.
  21. Make the project easy to hand off next year.

Staff Recruiting/Retention

  • Have the repo ready for new staff to tackle head on
  • Let them know they'll be mentored on how to use Eagle and basic EE
  • You'll learn industry electrical engineering tools
  • Learn Github pretty well
  • How to scale production sized orders and lead fabrication
  • Become the specialist on your board and document it
  • Learn to communicate with many different team members at a professional level

Quick Tips

  • Don't Change anything on the board for production
  • When designing the board, remember to find actual parts that exist and add them to the BOM as you populate your schematic
  • Always be thinking about enclosures as you design the board
  • Read all the things provided in the Useful Links part in the README
  • There's not much room for error, be meticulous and precise
  • Make sure to bond as a team; it's a lot of work and a small food run can really help the team

This is where long guides will be posted aside from everything on the README.

Read up on all this to get a vague grasp on things.

Clone this wiki locally