2017-11-05 Fall 2017 Review/Winter 2018 Planning

Participants

TL;DR

We need to differentiate between what are blockers for the race and nice-to-haves. Race blockers:

  • DC-DCs working
  • Killswitch tested and reliable
  • Power distribution + driver controls integration working reliably
  • BMS voltage/current/temperature sensing accurate enough for faulting
  • Driver controls + CAN interface + motor controller integration working reliably
  • Driver controls full integration (all components of system working together)
  • Telemetry basic CAN dumping

Nice to have:

  • SOC estimation
  • Sensors
  • Solar sensing
  • Additional telemetry data
  • Bootloaders
  • Aux battery charging - Power distribution will already do pack-scale voltage + current limits

Board Status/Task List

BoardPriorityStatusTask List (Hardware)Task List (Firmware)
Controller BoardHigh

Rev 6 - ordered

Should be done by EOT



Power DistributionHighRev 2 - completed
  • Test at the DC-DC's power limit (250W) and check for any overheating or other issues
  • Calder Kitagawa FW - probably want to fill this out more
  • Check integration with driver controls
  • Test power sequencing
BMS LV CarrierHigh

Rev 2 ordered

Should be done by EOT?

  • Bring up isoSPI (AFEs)
  • Bring up isoSPI (current sense)
  • HV battery relay testing w/ killswitch integration?
  • Check accuracy of voltage readings
  • Supply current pulled through the same voltage sense wire, potentially causing a voltage drop? (Need to add offset?)
    • 4-wire sense or disable balancing?
  • Calibrate and check accuracy of thermistors
  • Figure out what is going on with Charging/Charge Port
  • Charging modes: CV/CC
  • Integrate with telemetry
BMS AFEHigh

Rev 2 ordered

Should be tested by EOT 

  • Test for functionality and accuracy

N/A

BMS Current SenseHigh

Rev 1 ordered

Should be tested by EOT

  • Check slew rates of isolated DC-DC
  • Check accuracy of current sense
    • Can we trust the high ranges for basic current limiting?
    • High accuracy at low ranges are nice to have
  • Check isoSPI
  • Check BMS testing method
  • Do we need protection?
  • Communicate with ADC over isoSPI
Aux BMSMediumRev 1 - Started block diagrams and part selection
  • Finish schematic and PCB layout
  • Need to figure out how we're doing charging - do we need to connect the DC-DCs?
    • Make sure we address this on our DC-DC board
N/A
LightsmediumRev 1 - Finished block diagram and part selection
  • Ensure the board supports front and back
    • Front includes horn
    • Back includes strobe?
  • Ensure the harness includes an IO for determining front vs. back
  • Support front/back with the same FW
  • Support signal synchronization
Driver Controlshigh

Rev 1 ordered

Rev 2 - not started

  • Redo with LIN
    • This is a nice to have?
    • Would require redoing the pedal board as well
  • Integrate Pedal + Steering Wheel into FW
  • Add CAN output
    • Test integration with CAN interfaces
  • Add steering angle sensor support
    • This is a nice to have
  • Build LIN master stack
    • Work out scheduling and ID assignment
Driver DisplaymediumRev 1 - not started
  • Convert CAN to UART
  • Power Pi from 12V

Driver Controls Pedalhigh

Rev 1 ordered

Rev 2 - not started

  • Look into using rotary encoder or similar instead of magnetic sensor
  • Redo with LIN
  • Decide on STM32F0 vs STM32L0
    • Use F031 - more straightforward, supports LIN explicitly, should integrate with build system better
  • Build LIN slave stack
  • Support whatever new MCU we chose in our build system
  • Process magnetic sensor readings and convert them to angles
    • Need to add calibration routine
  • Probably convert raw pedal data to percentage
Driver Controls IO (steering wheel)very high

Rev1 - not started

  • Flesh out design - what are we using (control stalk vs. regular GPIO)
  • Figure out where we are locating this board
  • Decide on LIN vs. I2C
    • LIN would allow us to do all processing on-board
  • Integrate steering angle encoder into this board?
  • Read in control stalk voltage - determine which buttons were pressed
  • Report IO back to the master board
CAN InterfacehighRev 1 - Started PCB layout
  • Make sure that we have the necessary hardware for talking to the charger 
  • Build prototype with two breakouts
  • Make sure that we have the hardware for controlling precharge
  • Need main FW and slave FW
    • Main FW will need to communicate on the main system CAN
    • Slave FW will need to communicate on the motor/charger CAN
  • Define UART protocol for comms between the two boards
Precharge Controllermedium

Rev 2 completed

Rev 3 is a nice to have

  • Look into common-mode voltage
N/A
TelemetrymediumRev 1- Not started
  • Order Eval modules and solder them onto a perfboard
  • Build receiver?
    • XBee + UART-USB adapter for now
  • GPS driver
  • Design protocol for receiver
DC-DChighRev 1 - Not started
  • How do we want to connect this to our Aux BMS board? 

Solar Sense (Master)mediumRev 1 - Not started
  • LIN master
  • Solar relay control
  • Receive relay control from CAN
  • Send solar slave data to telemetry
Solar Sense (Slave)lowRev 1 - Started part selection
  • Make sure there's no significant voltage drop if we're daisy chain our boards
  • Look into analog isolation
    • Class D amp + digital isolator
  • Implement LIN auto-addresing
IMU SenselowRev 1 - Started schematic
  • Do we want any other sensors? (humidity, temperature, etc?)