2020-06-05 Strategy-FW Sync Up

Owned by Catherine Cai
Jun 06, 2020
1 min read

Necessary Components of Telemetry:

  • Calculate the power in the car (Battery state) (SoC)

    • Battery SoC Estimation:

      • Require the voltage across the battery (measured on the CAN BUS)

      • Current Draw

      • ^ Above two would provide the SoC Estimation

    • Battery temperature (Does this impact the SoC estimation?)

    • Coloumb counting and current draw - Clarke to talk to Micah Black and Jess

  • Velocity of the car (left/right off MCIs)

  • GPS data - depends on how much we want to implement in the car

  • Solar Power Input

  • Temperature:

    • MPPT SPV1020

    • Solar Array Thermistors

 

Implementation:

  • Strategy and Telemetry backend

    • Upload to a server that able to be queried (database query or API)

 

Requirements

  • Data Rate: Minimum 5 minutes, goal

    • Note that SoC changes very slowly but this is the most important in the race

    • Should not be dramatically changing throughout the race

    • Benefits: information/data for the

  • CAN BUS should be aggressively sampled to indicate when the car faults

 

Driver Display

  • Pi must be able to read in (Voltage, Current Draw) - calculations and output a float

  • Data Rate requirement: as fast as possible for drivers to receive

  • Something to tell them how fast to go

    • Motor RPM is tied to car velocity

    • Should the optimization model be on the car? No.

 

Infotainment

  • State of the Car (Driver, Neutral, etc.)

  • Battery State of Charge (without solar to empty --> rough estimation)

 

RPi Memory:

  • Reduce usage of external libraries

  • Half gig memory should be more than enough