Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Requirements

module testing v1: a lot of learnings about assembly, module design, testing procedure

https://docs.google.com/presentation/d/1JDEer-u4Yr4Mk4oCo_1GBLdfuhWZVZmIjVZzzzjlBpI/edit#slide=id.g24659019c9b_0_12

  • testing documentation

  • assembly documentation

module testing v2: shits getting serious

  • mechanical design
    • fit check
      • boards
      • taps
      • current sense
      • wiring
      • thermistors
      • busing
      • cells
      • fixturing (screws, inserts, etc)
      • module to module
        • fixturing???
      • module to enclosure
        • fixturing???
    • electrical performance
      • busbar to cell
        • thermal/electrical performance (<60C)
        • protection? fuse capabilities?
        • manufacturability/reproducibility
      • module to module
        • electrical/thermal performance
          • pressure & SA calcs (hard to test)
          • <60C
    • monitoring & bms
      • balance taps
        • location
        • quantity
        • wiring
      • thermistors
        • location
        • quantity
        • wiring
      • current sense
        • location
        • quantity
        • wiring
      • boards
        • AFE’s…

Overall, I think we should focus on getting the entire system rolling, rather than optimizing thermals, etc…

  1. BMS

    1. get mitch all the info he needs

  2. Motor Testing (since we can’t push modules with e-loads, lets just push it with the motor…)

    1. Motor controller

  3. Pack characterization

    1. coulomb counting

  4. Update documentation as we go

Kostubh’s Time Allocation

  • Module R&D completion oversight

    • All focus on Eric’s CAD

    • Down to redesign busing

    • Calcs

    • Oversight…

  • Coulomb Counting

  • Telemetry (Not really)

  • Anything else? How can I be most helpful

Onboarding

  • Focus on trial & error don't bombard kids with info, I think we do too much research

  • Design logs/documentation (helps the team and you)

  • No labels